Communication Issues

NetProfilers communicate with each other on select ports. These ports must be open between the NetProfiler and the remote device for all functions to work correctly. The following primary ports are used for communications among devices:

TCP/41017 - Used to pass data back and forth between the NetProfiler and remote devices such as the NetShark and Flow Gateway. You must open this port bidirectionally between devices.

UDP/123 - Used for NTP synchronization between the NetProfiler and the remote devices such as the NetShark and Flow Gateway. The NetProfiler acts as the NTP server for the remote devices.

If anything is blocking communications on the specified ports, that portion of the NetProfiler system does not work correctly. For example, if UDP/123 (NTP) is blocked between the NetProfiler and NetShark, the time on the NetShark is likely to drift, resulting in inaccurate reports.

To ensure that a port is open, use the following telnet and CLI commands:

[mazu@cascade-gateway etc]$ telnet 10.38.7.8 41017

Trying 10.38.7.8...

Connected to 10.38.7.8.

Escape character is '^]'.

^]

telnet> quit

Connection closed.

In this example, the connection was successful, and the CLI output shows port TCP/41017 is open between the host and 10.38.7.8. Had the port been closed, the conversation might have looked like this:

[mazu@cascade-gateway etc]$ telnet 10.38.7.2 41017

Trying 10.38.7.2...

telnet: connect to address 10.38.7.2: connection refused

The connection was rejected by 10.38.7.2 on port TCP/41017.