Once Usage monitoring is started, you should expect to see the charts being populated after five minutes and every five minutes thereafter until monitoring is stopped. If you are not seeing the results you expect, check the table below for symptoms and things to check.

Symptom Meaning Things to check
‘0 kbps’ in Traffic Rate column of details charts. Monitoring Point has established a connection with APM but has not seen traffic on the Usage port. Check your Usage monitoring cabling and, if you are using port mirroring, the port mirroring configuration on your switch.
’-’ in Traffic Rate column of details charts. Monitoring Point connection to APM is down. Confirm this by checking the Monitoring Point’s status. If the status is (Connection Lost), troubleshoot the connectivity problem.
Lower than expected packet counts Usage is unable to see inside some encapsulated traffic to capture packet counts, so it is likely that some of the traffic is encapsulated and is not captured in the counts. For example, traffic encapsulated using capwap, Q-in-Q, or with Cisco MetaData (Ethertype: 0x8909) headers is not currently counted. Check for encapsulations by reviewing the configuration of network devices that may encapsulate traffic and/or reviewing packet captures of the traffic in question.
Very low packet counts When connecting to a switch in an “out-of-band” setup, low packet counts will be seen if you connect to a regular access port on a switch rather than to a mirror port (also known as a “SPAN” port). Confirm that the switch port the Monitoring Point is connected to is a mirror port that is mirroring the port you want to monitor and not to a regular access port. If this is the issue, you’ll also notice that the Usage traffic seen is primarily broadcast traffic like DHCP or Netbios.

If you are unable to determine why Usage monitoring is not working, contact AppNeta Support for help.