Closed

Closed due to inactivity. Received 21 votes with last vote on 31 Jan 2013.

NPM Discovery Interface Filter for WAN Miniport

When you reboot a 2008 Server the WAN Miniport interfaces get recreated and therefore Discovery picks them up as new interfaces again.  As with a regular patching cycle servers often require reboots so it would be nice to be able to filter out the WAN Miniport drivers at a discovery level.

2012-08-27_WAN_Miniport.png

Parents
  • My biggest problems with interface discovery are as follows:

    • Virtual interfaces (i.e. port-channel and sub-interfaces) that are created need to be added automatically but all other interfaces discovered (that aren't currently being monitored) need to be ignored.
    • Interfaces with specific descriptions need to be added, but others need to be ignored (e.g. Nexus 1000v vethernet interfaces)
    • Lastly, in some cases, I need the ability for interfaces (similar to the ones above) to be removed automatically when they are removed/deleted from the switch configuration (and the status is unknown). Please consider the automatic removal of interfaces in large environments (based on rules) where switches can easily have 2000+ interfaces.

    Does the new interface discovery mechanism that is currently in progress handle all of these scenarios?

  • hi SamuelB,

    first two cases should be covered by the new interface filtering mechanism. third one - interface removal is something that won't be there, but we can create a feature request for this. Just to make sure you would like to automatically remove all interfaces that are not "access" correct?

  • I would imagine it would be similar to the feature to automatically add interfaces. You would be able to create a filter that specified which interfaces to remove and (hopefully) be able to apply it across multiple devices (by device type for instance) or to a single device. This would allow me to automatically remove any "virtual" (non-physical) interfaces that change their status to 'unknown'. These non-physical interfaces in my environment show up as 'unknown' 99% of the time because they have been deleted/removed from the device being monitored. The other 1% is when all the interfaces (including physical ones) show up as 'unknown' because the device can't be reached or SNMP isn't working properly.

Comment
  • I would imagine it would be similar to the feature to automatically add interfaces. You would be able to create a filter that specified which interfaces to remove and (hopefully) be able to apply it across multiple devices (by device type for instance) or to a single device. This would allow me to automatically remove any "virtual" (non-physical) interfaces that change their status to 'unknown'. These non-physical interfaces in my environment show up as 'unknown' 99% of the time because they have been deleted/removed from the device being monitored. The other 1% is when all the interfaces (including physical ones) show up as 'unknown' because the device can't be reached or SNMP isn't working properly.

Children