When adding SNMP Traffic sensors via the auto-discovery, this feature does not behave like I expect it to behave. For example, the auto-discovery adds interfaces that were either deliberately deactivated in the device’s configuration, or interfaces that are currently disconnected (not used).
What is the reason for this and what can I do about it?
Created on May 24, 2019 8:21:18 AM by
1 Reply
This article applies as of PRTG 22
The auto-discovery always creates SNMP Traffic sensors for all interfaces whose SNMP traffic counters are above 0. As a result, every interface that has had traffic since the last restart of the monitored device is added, even if it is currently disconnected or disabled.
For more information, see NICs not as intended after autodiscovery and Auto-Discovery adds disabled interface.
Conversely, interfaces that have seen no traffic (their SNMP traffic counters are still 0) are not automatically added when you run the auto-discovery. See also Cisco Switching auto discovery ports.
The reason for this behavior is that we do not want to miss interfaces that are relevant (still in use), but might be disconnected because of a failure or disabled by mistake at the time that the auto-discovery takes place.
If you do not want the auto-discovery to add SNMP Traffic sensors for deactivated or disabled interfaces, for example, you need to restart the device or its SNMP traffic counters before you run the auto-discovery.
Note: Resetting SNMP traffic counters too often is not advisable as it results in the loss of data or in erratic readings for existing SNMP Traffic sensors that monitor said device.
Also be aware that for Cisco devices, the SNMP traffic counters are not the same as the interface counters displayed within IOS. For more detailed information, see Auto-Discovery adds disabled interface.
Created on May 24, 2019 8:31:40 AM by
Last change on Jun 30, 2022 11:56:46 AM by
Please log in or register to enter your reply.
Add comment