Teamed Network

Owned by Martin Moghadam
Last updated: Nov 21, 2019

In a correctly configured teamed network setup the agent web interface's View > Adapters menu will show something like:

Network Adapterlist

Adapter IP   Bit/s  Mac  Name
------------------------------------------------------------------
1 000.000.000.000/ 0 0 00-00-00-00-00-00 Generic NdisWan adapter \Device\PGNPF_GenericNdisWanAdapter
2 000.000.000.000/ 0 100000000 00-02-B3-E7-43-FD Intel(R) PRO/100 S Server Adapter (Microsoft's Packet Scheduler) \Device\PGNPF_{13BA53FE-DEED-4033-898F-A3EB17FAB60D}
3 192.168.101.148/ 24 100000000 00-02-B3-E7-43-FD Intel(R) Advanced Networking Services (iANS) NDIS Intermediate Driver (Microsoft's Packet Scheduler) \Device\PGNPF_{DA4AB7AC-241A-405A-B5EF-B962C15D61E3}
4 000.000.000.000/ 0 100000000 00-02-B3-E7-43-6F Intel(R) PRO/100 S Server Adapter (Microsoft's Packet Scheduler) \Device\PGNPF_{D85760B5-4AA5-4929-856F-627D0AADE34D}


The only adapter with a valid IP address is the "Intel(R) Advanced Networking Services (iANS) NDIS Intermediate Driver (Microsoft's Packet Scheduler)", which is the virtual adapter on which the agent listens. This adapter will make sure that whenever a cable is unplugged on either of the "Intel(R) PRO/100 S Server Adapter," the IP traffic is still measured.

When using the agent in a teamed network configuration, it's strictly necessary to restart the pgnpf.sys driver after each reconfiguration of the teamed-driver, that is when you initially create the team or if the setup of primary/secondary adapters is changed.

  1. Stop the PerformanceGuard Agent service using the Services panel.

  2. In a command prompt type net stop pgnpf

  3. Start the PerformanceGuard Agent service using the Services panel. This will automatically reload the pgnpf.sys driver.


Search this documentation

On this page

In this section