monitoring only etherchannels, trunks, and routed links

I would like to configure an alert to monitor etherchannels, trunks, and routed links on all of my cisco switches. My question is how to configure the alert so that i can capture these interfaces without the need for a manually entered description per interface? This would greatly reduce the amount of initial setup time and ongoing matenance.

thanks for any useful information!!!

Find more posts tagged with

Alert

Accepted answers

All comments

mcbridea

If there is some commonality in the interface naming you could use an "Interface Name contains xyz" simple condition in the trigger. Otherwise you could create a Yes/no custom property and mark the interfaces you need with yes check box in the custom property editor.

Another method would be to create a dynamic service group using some common element, like a "name contains xyz" then you will probably want to choose the "show worst" as the group roll up option. From there create the alert for that group.

If this seems like a lot at once check these out:

http://www.solarwinds.com/documentation/Orion/docs/Groupsanddependencies.pdf

http://www.solarwinds.com/documentation/Orion/docs/UnderstandingOrionAdvancedAlerts.pdf

netlogix

This one is suppose to look to see if it has more than two mac addresses discovered on the interface. So that should give you part of what you want. The only other way I could think is to use "sh interfaces trunk" then put a description on each of those that are gig or fast. I can't think of what to do for the portchannel, except to just go through the config and find the port with something like "sh run | inc Ether|channel-group"

pivot11

netlogix,

thanks for the information. I am wanting to make sure i understand your recommendation. You are running a script to find the interfaces and then you are manually adding a unique description. Once you have a description then you can then use orion polling and alerting features for the specific interfaces?

thanks again!

netlogix

I thought you also needed to figure out how to add them to Orion to be monitored. I guess we ought to clear up what we are talking about. If you have a them in Orion, you would do it like mcbride said, but if you don't have them in Orion, then run discovery to list all the ports out, then use the post I linked to import the interfaces, but the etherchannels ports need a description to import for that one. The trunks shouldn't need a description because they should have more than two MACs and would be picked up. It will be some manual work, but these tips can help to reduce it.