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

How to identify and enable trunk ports for already added nodes(switches) by easy method, like bulk update.

we have 600+ switches in our environment we want to cross check if all the trunk ports are added under monitoring. Is there any easy way to identify the trunk ports and enable it?

I know it can be done by bulk discovery. But all these nodes are already added, so Is there any other way to identify trunk port?

Find more posts tagged with

Accepted answers

All comments

silverbacksays

Hey chandd. This thread is a little old, so I hope you already have a working solution to this, but if not, the easiest way would be to run a discovery against all your network hardware, using a scheduled discovery in Discovery Central.

When you get to the 'Monitoring Settings' part, as long as you are running NPM 12.0+, you can set the discovery to automatically monitor trunk ports. If you schedule this discovery to run semi-regularly, this will capture any new links you add it, should you expand your switching infrastructure.

Let me know if you need any further information on this process, and I'd be happy to assist.

debjyoti.ghosh

Sorry for this late post . But We have installed "Solarwinds" In our environment . Version :-2019.4

Our OEM has configured as below attached for "Trunk" Interfaces. But for some reason its not working . Its throwing lot of alarms but not the fruitful or actual one . Need help urgently for this .

TRUNK PORT CONDITION.PNG

christopher.t.jones123

If you're only interested in receiving an alert when these interfaces go down then you should change the trigger condition from not equal to "Up" to equal to "Down" this should reduce some of the false alarms like if an interface goes unknown, etc.