I've used both methods in the past...
Method 1 (threshold alerts) is a pain to maintain if you don't care about ALL
interface state changes. I.e., by using a threshold in a template that will
(usually) be used by all devices you'll get alerts for "unimportant"
interfaces. Sure, you can apply customized templates to the "important"
interfaces (or the opposite), but IMO there's a better way..
Method 2 (SNMP linkDown traps) suffers from the same flaw of alerting on ALL
interfaces. However, a method I use to differentiate interface "importance" is
to have the event transform lookup the given interface's textual description
and search for a flag that denotes critical links. When a match is found,
event Severity is changed appropriately. The main benefit here is that the
ownership of maintaining/determining interface "importance"is placed on the
network administrator(s) rather than the Zenoss admin(s).
Example [crude] transform:
Code:
if hasattr(evt, 'component'):
fs_id = device.prepId(evt.component)
for iface in device.os.interfaces():
if iface.id == fs_id:
myDescr = iface.description
myDescr.lower
if myDescr.find('(dot1q)') >= 0:
evt.severity = 5
elif myDescr.find('(transit)') >= 0:
evt.severity = 5
elif myDescr.find('(egress)') >= 0:
evt.severity = 5
Example matching Cisco router interface config:
Code:
interface POS1/0/0
description OC-3 Internet to Sprint (egress)
ip x.x.x.x
Disclaimer: Much of this concept & code was derived from previous forum posts..
> I would want interface alerting from core routers, but not from switches.
In this case you could also set the Transform code to match device name for
your core routers (not scalable), or match based on Systems or Groups (eg,
Systems = "/Core Routers" or Groups = "/Workgroup Switches").
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=37158#37158
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
