nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

I'd like an easy way to discover interfaces that are members of Cisco port-channels or Channel Groups, and to have NPM automatically monitor and alert on their status changes.

rschroeder

I build at least two interfaces into every switch's uplink as members of a port-channel so the device has some resilience in case one of its upstream distribution or core switches experiences problems, or in case there are fiber or transceiver problems.

When one port fails for any reason, the switch stays up and running, but its resilience and throughput are cut in half.

How can NPM easily/automatically discover port-channel members and monitor them and the port-channel to which they are assigned?

In the past I manually added every port-channel and member interface manually into a special group I called "Critical Interfaces". It not only included port-channel interfaces between switches or between switch and router, or between firewalls and switches, but it also contained LACP or other port-channels between switches and servers.

I'm not finding a way to make this happen automatically or easily--only manually.

If you have a way to make it happen, please share it with me.

If there's not a pre-planned / canned way to accomplish this, please consider this a Feature Request for it.

Find more posts tagged with

Status: None

Comments

designerfx

Is this different than the newer nexus polling?

rschroeder

Say more about the newer Nexus polling, please? If I'm using NPM and NCM to manage non-Nexus interfaces that are port-channeled between switches, I want to find an easy way to discover and group them all, and to alert when one goes down.

Similarly, I want the same thing for Nexus and ACI ports. I don't know how to do it simply and with grouping and automation--I only know how to do it manually, port by port, switch by switch. With a thousand switches in my network, I'd love to find better ways to use my time than to manually add one interface at a time to a "Critical Interfaces" group, and then set up alerting for them all.

What have you got that I can learn from?

rschroeder

Bump.