List of "Physical Interfaces" retains old network interfaces even after they are no longer on the host
Description
Environment
Acceptance / Success Criteria
Attachments
Lucidchart Diagrams
Activity
David Alston December 15, 2011 at 6:20 PM
I thought I'd double-check.. is there something I can do to provide more information?
David Alston December 5, 2011 at 11:35 AM
I've only tried rescanning the network interface manually. I have not tried waiting for the 24h
automatic re-scan. Is the 24hour scan different from the manual scan in some way?
Seth Leger December 5, 2011 at 10:21 AM
Are you rescanning the node manually (by using the button on the node page) or waiting 24h for the capsd rescan of the nodes? Otherwise, OpenNMS will not be aware of the changes to the interface list.
David Alston November 10, 2011 at 7:02 PM
It is interesting that the Net-SNMP agent increases the "index" number in the list of "Physical Interfaces". Maybe OpenNMS is only keeping track of the interfaces by the "index" value?
If it is a feature that OpenNMS keeps track of interfaces that the SNMP agent is no longer reporting I would very much like to know how to make it forget about individual interfaces.. hopefully through the ReST API.
David Alston November 10, 2011 at 6:58 PM
OpenNMS showing old physical interfaces on a node that has had net-snmp agent restarted already (to refresh the snmp-agent's list of network interfaces)
Attempting to monitor the addition/removal of network interfaces associated with virtual machines on a Xen Hypervisor.
The Net-SNMP agent on Dom0 (the virtual machine with special privileges to control the other virtual machines) becomes aware of new interfaces automatically. Apparently the Net-SNMP agent does not remove these interfaces when they disappear. Restarting the Net-SNMP agent cleans out the network interfaces that no longer exist on the client, but OpenNMS still remembers them.