This page contains answers to some frequently asked questions when running sFlowTrend-Pro.
The dashboard (Section 3.1, “Status”)
displays the current sFlow sample rate being received by
sFlowTrend-Pro. If this shows a sample rate of
then no samples are being received. This can happen because no
switch is configured to send sFlow, because there is
insufficient network traffic on the switch to generate any
sFlow, or because a firewall is blocking the sFlow data.
First, make sure that a switch is configured to send sFlow to sFlowTrend-Pro. With some switches, this can be done automatically, using sFlowTrend-Pro. Use the menu option Section A.2, “Using the switch CLI to configure sFlow”.→ , and then . For other switches, sFlow must be configured through the switch's command line interface - refer to the manual for the switch. See also
If you think that sFlow is configured correctly, then try to ensure that sufficient network traffic is flowing through the switch. See Section 14.1.6, “sFlowTrend-Pro is not receiving sFlow from a switch or host”.
sFlow works by sending network packets to an sFlow collector, in this case sFlowTrend-Pro. The network packets are sent using UDP, on port 6343. If a firewall, either on the system running sFlowTrend-Pro or in the network, is blocking port 6343, then no sFlow data will reach sFlowTrend-Pro. Make sure that both the firewall on the system and all network firewall are allowing sFlow data through - see Section 14.2.4, “What firewall requirements does sFlowTrend-Pro have?” for more information.
This error message almost always means that another application is already using the default sFlow port, which is UDP 6343. A port can be used by only one application. If you try to run sFlowTrend-Pro more than once on the same system or another sFlow collector is already running on the same system, then you will see this error. Examples of other sFlow collectors are InMon Traffic Sentinel, a switch vendor's element manager, or one of the other sFlow applications available.
To find out which application is already using the sFlow port, follow these instructions:
On Microsoft Windows, in a command prompt window, run the command:
netstat -p udp -a -b
This command takes a while to run. When it has completed, in the output look for a line like the following, containing 6343:
UDP PCNAME:6343 *:* 2428 [javaw.exe]
This is saying that the program javaw.exe is using port 6343. Any Java application will appear as javaw.exe on Microsoft Windows, or if the application is not written in Java, then the name of the application will be shown. The number at the right (2428 in this case) is the process ID of the application.
On Linux, from a terminal window, run the command:
netstat -l -p -u | grep sflow
This should produce a (long) line like:
udp 0 0 *:sflow *:* 26680/java
The very last part of this line is telling us that the process with ID 26680 is running java, using port 6343. Again, if the application using the port is not written in Java, then the name of the program would be shown here.
Once you have identified which application is using the sFlow port, you can decide which application to run at any one time, or you can change the port that sFlowTrend-Pro uses, by entering a new port number in the dialog.
If you change the port that sFlowTrend-Pro uses and your switches are configured using SNMP to send sFlow; (see Section A.1, “Using SNMP to configure the switch to send sFlow”), sFlowTrend-Pro will automatically reconfigure your switches to send sFlow to the new port. However, if your switches are configured via the CLI to send sFlow and you change the port used by sFlowTrend-Pro, you must also manually reconfigure your switches to send sFlow to the new port (see Section A.2, “Using the switch CLI to configure sFlow”).
Occasionally, a host firewall can also cause this error message. If you could not find another program using the sFlow port, then refer to the section on firewalls: Section 14.2.4, “What firewall requirements does sFlowTrend-Pro have?”.
The grey part of a bar in a Top N chart indicates that the activity was from contributors not in the top N for the currently selected interval. See Section 4.3.3, “Understanding the Top N traffic chart” or Section 6.2.3, “Understanding the Top N services chart”.
sFlowTrend-Pro requires two network ports be available through all host or network firewalls between it and monitored switches, for the following purposes:
Reception of sFlow data. Without sFlow connectivity, sFlowTrend-Pro will not show any data. By default, sFlow uses UDP port 6343 (this can be changed if required - see Section 13.2.2, “sFlow configuration”). Only reception of sFlow traffic is required, sFlowTrend-Pro will never generate any sFlow traffic.
SNMP connectivity between sFlowTrend-Pro and the monitored switches. This is strictly not required, but without it sFlowTrend-Pro will not be able to display friendly names for interfaces, and other similar features.
Also required is connectivity to a DNS server (to allow reverse IP address lookup), and http connectivity to the Internet (for license and product alert information; a proxy can be configured if required, and a license key manually entered if no Internet connectivity is available). There must also be connectivity over the web server ports between the client system and server (TCP ports 8087 and 8443 by default).
If the server running sFlowTrend-Pro has a host firewall, then this must allow sFlowTrend-Pro to access these ports. The firewall must allow the service connectivity, which may be different from the currently logged in user. Under Windows, the service runs as user Administrator.
By default, sFlowTrend-Pro stores the last 7 days' of data. If required, this can be changed using the server custom configuration setting database.hoursPersistent.