NPM Discovery Interface Filter for WAN Miniport

Hi folks,

we are working on this feature and one of the improvements we would like to add are VLANs per interface. We would need you to download our small diagnostics utility - http://thwack.solarwinds.com/servlet/JiveServlet/downloadBody/170583-102-1-7323/VLANsInventory.zip-  and run it on your environment so we can understand how much time the discovery process takes on your side.

Output of the test is a simple text file which you may send to my email address: michal.hrncirik at solarwinds.com

thanks for your help!

Michal

Hi Michal,

For us its not the discovery time that takes additional time but more having the server flag up new interfaces that its discovered post a reboot.  Normally we would need to go through and select each WAN Miniport and add it to the ignore list.  Typically there is at least 6 per server on a reboot.

I'm also with brookslaw on a changeable filter(s) would be very useful for other devices, possibly like filter rules (top down) with a default rule of show in discovery.

Rule # - SWQL - Action

Rule 1 - Vendor=Windows and InterfaceName like %MINIPort% - Ignore

Rule 2 - Vendor=Windows and InterfaceName like %Intel% - Discover

Rule 3 - Vendor=Cisco and InterfaceName = Null0 - Ignore

etc

What do you think?

Hi Michal,

For us its not the discovery time that takes additional time but more having the server flag up new interfaces that its discovered post a reboot.  Normally we would need to go through and select each WAN Miniport and add it to the ignore list.  Typically there is at least 6 per server on a reboot.

I'm also with brookslaw on a changeable filter(s) would be very useful for other devices, possibly like filter rules (top down) with a default rule of show in discovery.

Rule # - SWQL - Action

Rule 1 - Vendor=Windows and InterfaceName like %MINIPort% - Ignore

Rule 2 - Vendor=Windows and InterfaceName like %Intel% - Discover

Rule 3 - Vendor=Cisco and InterfaceName = Null0 - Ignore

etc

What do you think?

Hi Peter,

your condition with these three rules above is something that our new interface discovery mechanism should handle.

The VLAN stuff is not directly related to WAN miniports but it's something that useful for the other users - for example Rule: import all interfaces in VLAN 100 - 104. Unfortunately VLAN discovery itself takes a lot of time and we would like to keep our discovery process fast as much as possible so that's the reason why I would like to get a data from real environments.

Hi Michal,

I just completed my upgrades to 10.5 etc but think I must be missing something.  I ran a discovery and all my WAN Miniport interfaces are still showing up.  However when I go to import the Nodes/Interfaces I get the ability to filter out the different types - this is great but it has a flaw (unless I am doing something wrong).

So here's my scenario -

I reboot ServerA and my nightly discovery runs.

Then I get the "Scheduled Discovery: 39 new nodes found. 9 nodes were changed. »" message at the top.  So I know now that I have actions to perform.

I enter the "Scheduled Discovery Results" and see my already imported Node sitting there with the re-discovered WAN interfaces. (if I don't go through manually and Ignore these interfaces they will always show as actions I have to perform)

Am I doing it wrong or is this the way its meant to work?

Peter, I dont think Michal is trying to solve the MiniPort problem, just the VLAN problem