I built a special group in NPM for monitoring and alerting that contains Critical Interfaces. My definition of a Critical Interface includes:
- All physical interfaces that are members of port-channels between switches and/or routers
- All firewall physical interfaces
- All resilient interfaces (must have an alternate path that still works when a primary interface fails)
- All WAN physical interfaces
It took a long time to tweak & tune it, but it worked well, alerting me when port resilience was lost in channel-groups.
After several mergers and migrating my Orion solution to new servers I see those solutions did not migrate with the boxes.
I'd like an option in NPM to automatically discover the above types of interfaces and add them into the Critical Interfaces group. Without that automated way I've got to search through 70,000 physical ports and manually select the resilient uplinks on hundreds of switches and routers and firewalls. It's possible, but this is the kind of a work a computer should be able to do quickly.
Is there a way to do this already?
Unfortunately the interfaces do not all have the same label or name. The most common item is that they'd show up as members of Cisco channel-groups / port-channels.
Top Comments