Agent Network Traffic Is Missing

Symptom: In the PerformanceGuard web interface, you can’t see any network traffic measurements from a particular PerformanceGuard agent.

Possible causes and solutions

Caution

You can only do this if you’re a PerformanceGuard administrator.

Computer isn’t online

To check: Select ANALYZE > Computers > Computer Search, and search for the computer in question. In the search results, click the name of the computer. On the Computer Info tab, select Agent Info, and compare the Last Delivery time with the Delivery Interval. If, for example, the agent is set to deliver data every 180 seconds, and it hasn’t done so, then the computer is in all likelihood not online.

To fix: Further troubleshooting should focus on finding out why the computer isn’t online. See Agent Can’t Connect.

Packet capture driver isn’t working

To check: Select ANALYZE > Computers > Computer Search, and search for the computer in question. In the search results, click the name of the computer. On the Computer Info tab, select Agent Info, and check the Options. For a correctly working agent, the options include Winpcap Driver OK. If you see Winpcap Driver Could not initialize or Winpcap Driver Not installed, the agent can’t capture network traffic.

To fix: Select the Message Log tab to see if there are any log messages that explain the problem. If not, go to the computer that has the agent installed, open a browser and go to http://localhost:4007. In the agent information page that opens, select View > Errors and check if that detailed log of the agent’s activity contains any messages that explain the problem. To check and start the driver on the computer, see WinPcap Packet-Capture Driver. A restart of the computer may be required.

Caution

4007 is the default port number. If the port number has been changed in your organization, PerformanceGuard administrators can view it in the PerformanceGuard web interface: Select ADMINISTRATION > Agent Configuration > Configurations, click the Edit link next to the agent configuration group that the agent belongs to, select the Agent configuration tab, scroll down to the Agent Service Parameters section and look for the Web Server TCP port number.

Aggregation job isn’t running

To check: Select ADMINISTRATION > Status > System Status, select the Scheduled Jobs tab, and verify that the Traffic Data Aggregation job is enabled and has the status OK.

To fix: The Backend server runs the aggregation jobs. On the computer that runs the Backend server, select Start, type services.msc and press ENTER. Then make sure that the PerformanceGuard Backend Server service is started. If the job still fails, check the Backend server log in [PerformanceGuard installation folder]\notification\logs\.

Agent monitors the wrong adapter

The PerformanceGuard agent only monitors network traffic going to and from a single network adapter. Many computers have more than one adapter, so the agent chooses the adapter that it uses to connect to PerformanceGuard.

To check: On the computer that has the agent installed, open a browser and go to http://localhost:4007. In the agent information page that opens, select View > Adapters to view a list of available adapters on the computer. Then select View > Errors to view a detailed log of the agent’s activity (including non-errors) and search for Opened adapter to see which adapter the agent currently monitors.

Caution

Remember that the log lists the most recent messages at the bottom.

To fix: If the agent doesn’t monitor the adapter that you want it to monitor, you can force the agent to monitor a specific adapter with the MonitoredNicIP registry value. See Agent Registry Keys.