Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Monitoring only infrastructure interfaces

I'm doing an evaluation of NPM. I want to monitor infrastructure interfaces/ports. These are interfaces/ports that connect to other network devices. I'd rather not have to manually determine which these are, because that's an ongoing manual maintenance headache and we're sure to eventually miss a critical interface.

CDP is a great way to identify these interfaces automatically. Is it possible to identify interfaces/ports that have appropriate CDP neighbors (want to exclude phones) and alert when they go down?

Thanks!

Find more posts tagged with

cdp

port

infrastructure

cdp_neighbors

interface

Accepted answers

All comments

bleearg13

NPM does not do anything with CDP. Unfortunately, you're going to have to add them all manually and track them using a Custom Property. We basically monitor every interface on a router/switch and have a checklist that must be filled out prior to completing an install. The checklist includes ensuring that all the proper Custom Properties are filled out. We have a Custom Property called 'Service' and core interfaces are labeled as 'core', internet-facing interfaces are labeled 'internet', transport interfaces are 'transport', etc.

brian_crypto

I am in process of doing discovery now and agree that what Terry is asking about would make a great feature.

Identifying discovered interfaces as having CDP enabled is a great way to determine that the interfaces are "infrastructure" ports. And this is precisely what I would want to monitor. On even a small discover I am liable to end up with thousands of "Ethernet", 99% of which will be user access ports which are not desirable to monitor. So the only real choice from a discovery import perspective is to choose to monitor none of them and then deal with the tedium of going back to each device individually to select which ports are those uplink ports.

Please take this as a product feature request!