<-

SETTINGS > MANAGE DEVICES

Available Languages: English

Overview

This option allows you to manage your netflow sources that are currently sending data to Scrutinizer Netflow Analyzer.

Click Here if you need a license key. Be sure to email us the IP address of the machine Scrutinizer is installed on. We generate activation keys based on IP addresses.

will be displayed if no NetFlow or SFlow is being received. Make sure the software is listening on all the necessary ports the flows are being sent on.

NOTE: SNMP Real Time will not work if a valid SNMP Community string is not specified below.

Topics

top

Options

SNMP

SNMPv1, v2 and v3 are all supported:

In the below screen capture, SNMP information is displayed when clicking on the Wrench icon.

In the Manage Devices view, click on this icon to view the full utilization of the interface. This icon will pop up a window displaying the full utilization in and out on this interface in daily, weekly, monthly and full year format or in real time. To learn more about this feature Click Here.

Interfaces can be renamed and it must be done on the router. When looking at a router with the wrong interface information, click on the wrench icon . This will display the SNMP information.

You will 5 columns for each interface on the NetFlow capable router/switch:

Scrutinizer will attempt to build the drop down boxes based on whether or not the following information is available in this order:

If the Custom Description is filled in, it will over ride the use of the SNMP descriptions. This is also true when the Custom (Mb) is filled in, it will over ride the use of the SNMP ifSpeed.

Again, to update the interfaces on the router/switch, it is generally done with a telnet to the router/switch. After saving and applying the changes to the running configuration on the router/switch, go back to Scrutinizer, click on the wrench icon.

VERY IMPORTANT By default, Scrutinizer does not regularly SNMP poll the switches and routers it is receiving NetFlows from. Scrutinizer was engineered to be a passive collection tool with minimal SNMP requirements. The best way to update the SNMP information including the information on the interfaces is to click on the "UPDATE" button displayed in the screen capture above.

Scheduled SNMP Update on all devices can be scheduled using the CRON service installed by the software.
Put the following in a script or call (207)324-8805 and support will provide assistance:
~\scrutinizer\mysql\bin\mysql –u root –p
mysql> use scrutinizer;
mysql> update netflows set state = ‘2’;

Virtual Interfaces Not Showing Up (e.g. VLANs, VPNs, etc.)

The Cisco IOS will allow the configuration of NetFlow on virtual interfaces however, it is not supported. To get virtual interfaces to show up in the Status page NetFlow must be configured on the physical interfaces. The sub "virtual" interfaces will then appear automatically.

Configuring NetFlow

Click Here to learn more on how to configure NetFlow on a router or switch.

Add Device

Use this option to launch the wizard and enable netflow on a router or switch.

Add the IP address of the router or switch. Select a SNMP credential or use the wizard to create a new one. Click Next:

It is suggested that the defaults be taken. Make any necessary changes and click "Save" below:

flow-export source

If a loopback interface is not configured on the router, the router will use it's local routing table to determine which interface to send the netflow out of. The netflow packets will have a source IP address of the interface used for the export. If this interface goes down, the router will try to find another route and the source IP address will change to that of the new interface. This will often result in a red icon in the netflow collector and a new icon (i.e. IP address) showing up as a new netflow device!

How can the above problem be avoided? If a loopback interface is setup on the router with an IP address, it can be specified as the "flow-export source".

The global commands: 'ip flow-export source ' should be used. Any interface can be specfied however, the loopback is ideal as it is the least likely to enter a 'down' state. Netflow will not be exported if a specified source is down. For this reason, we suggest the Loopback interface as this also avoids the router from using the selected interfaces IP address as the source of the netflow packets. By specifying 'ip flow-export source loopback' if an interface goes down and the router has another route to get the netflow to the collector, the source IP address will not change!

Next Topic: Mapping or go back to the Settings Table of Contents

Would you like to see a feature added to Scrutinizer? Click Here and tell us about your feature request.

Available Languages: English