Troubleshooting A Slow Probe System; A Probe Is Not Connecting To The Analyzer Or Vice Versa - Network Instruments GigaStor User Manual

Troubleshooting a slow probe system

If a probe is overloaded, consider whether any of the following affect the system. You can clear these one at a
time to see if that resolves the system's issue.
Although all of the settings discussed in this section are configured in the Observer analyzer, they are saved to
the probe.
A scheduled capture can be causing a system slow down. Determine if any scheduled capture is
occurring. Capture > Packet Capture > Settings > Schedule tab.
Some extra processing happens when you have triggers and alarms configured. Determine what alarms
are enabled by clicking the Alarm Settings button in the lower left.
Are you running real-time Expert Analysis? Observer requires some processing resources to get through
the data, which could be a lot of data. Real-time expert processes data as it is received. This requires
continuous processing of incoming data while the real-time expert is running.
Are you collecting combined station statistics or protocol distribution summary for your network? If
so, these could be causing the system to slow down. To determine if you are, click Options > Observer
General Options > General tab. Scroll to the "Startup and runtime settings" and uncheck these, if
necessary:
Collect combined station statistics at all times
Collect protocol distribution for the whole network
Are you collecting network trending statistics? If so, is the sampling divider less than 10? If so, increase
the sampling divider to 10 or greater. To determine your sampling divider, click Trending/Analysis >
Network Trending > Settings > General tab. In the Collection Settings section, change the sampling
divider.

A probe is not connecting to the analyzer or vice versa

If the probe is not connecting, it could be one of several reasons. The log window in the Observer analyzer has
useful information to give you an idea of why the connection is failing. If the log window is hidden, choose View
> Log Window to show it.
Verify the following:
The probe is licensed. See
Ports firewall and the traffic is actually passing through it. Observer uses these ports to communicate
with the probe. See
firewall as well as any network firewall. See also the information in
89).
Security and encryption settings match between the Observer analyzer and the probe. If the settings
do not match, you will get a message that says "Probe redirection Error <IPAddress> Authentication
Negotiation Error" or "Probe authentication failed <IPAddress>." Either the security feature has been
turned off for one side of the connection (but not the other), or their encryption keys do not match. In
Observer, click Options > Observer General Options from the menu, then click the Security tab. On the
probe, click the Security tab. Verify that the security properties match. If necessary, generate a new key
and use that on both the probe and analyzer.
The user name you are using from the analyzer exists on the probe. Although very uncommon,
the default "Anyone" account can disappear. If it does and you use that account to connect, your
connections are prohibited. If the Anyone account has been deleted, you can recreate it on the probe by
clicking the Security tab, then the New User button. Click the "Create Anyone Account" button.
Licensing and updating.
Ports used by Network Instruments products (page 26). Check any local system
Suspected NAT or VPN issues (page
Troubleshooting a slow probe system | 85