NPM Network Discovery to discover ONLY Trunk ports

Is there a way to use the Network Discovery tool, to discover and then ONLY monitor the trunk ports on my nodes?

We have a multivendor environment, and are currently moving infrastructure to new locations, while also simultaneously swapping out older equipment with newer equipment. For ease of use, and due to licensing restrictions, we would like to only monitor our trunk ports between our distribution layer, and access layer switches. I have set and verified, when I log into my Aruba switches, that the interface "mode" is clearly set to either "access" or "trunk." When I do a network discovery, the SNMPv3 credentials I am using, lets me "see" the vendor on the switches, but ALL of the interfaces show up as "unknown." If there is an option to select and deselect "trunk," "access," and "unknown" interfaces after the discovery, why am I unable to discover and differentiate those interfaces?

The example I have given is specific to our Aruba devices, but we also use Cisco, Brocade, and Juniper devices that I would like this also to work on. Has ANYONE been able to get this functioning properly? I cannot find anything on the web, other than similar posts from TWELVE years ago, with no answer.

Find more posts tagged with

Trunk Ports

npm

network discovery

Accepted answers

All comments

rleonar7

We're in a similar multivendor situation on our campus. We are trying to set up Network Discovery "Monitoring Settings" for Interfaces using "Advanced filtering options" -- Specifically, we are trying to use Regular Expressions to automatically monitor our uplink interfaces for us on our switches.

This has not been working at all... yet. (I've opened a 2nd ticket for support on this topic today. We initially got the response of "this is advanced... and too hard to reproduce," and then the ticket closed when I didn't respond quickly enough.)

The workflow I am using for testing is shown in the (2+ minute long) GIF animation below:

GIF animation showing the long process we use to test Network Discovery "Advanced filtering options" for "Monitoring Settings"

chad.every

Do the interfaces show as Unknown when using SNMPv2? I've seen issues in the past where a vendor did a good job exposing OIDs on SNMPv2 but did not follow the same path on SNMPv3. Even an SNMPWalk between SNMP versions might give you an idea on the differences.