Solution#1 (ugly): syslog messages can be sent as SNMP traps. You'll get the whole syslog message on your NMS.
Solution#2: use EEM to match syslog UP/DOWN messages, extract interface description and generate a custom SNMP trap. You can do it with EEM applets if your IOS supports EEM 3.0 (12.4(late)T, 12.5, 12.2SRE), otherwise you have to use a Tcl EEM policy (pre-EEM 3.0 applets are too dumb). These posts could be useful: http://blog.ioshints.info/2009/12/send-snmp-trap-from-eem-applet.html http://blog.ioshints.info/2009/10/report-interface-loss-based-on-ospf.html You can generate custom SNMP trap from an EEM applet with "action snmp-trap" command (I haven't covered that one yet in my blog). Hope it helps Ivan Pepelnjak blog.ioshints.info / www.ioshints.info > -----Original Message----- > From: Walter Keen [mailto:walter.k...@rainierconnect.net] > Sent: Friday, January 08, 2010 1:43 AM > To: 'Cisco-nsp' > Subject: [c-nsp] customizing snmp-traps (interface description as well as > physical name) > > Is customizing snmp-traps possible through rmon or some other means so > that the delivered message not only has the physical name (gi0/1, etc) > but also the description of that port as named in the interface config? > Dealing mostly with 2960's and 7600's, and trying to figure out if this > is possible. > Even if I have to specify an rmon entry per physical interface, I'm > dealing with small enough numbers that would work. > Something like '<int-name> <int-descr> is <down/up>' or similar would be > ideal. > > Going to want to have this for link up/down initially, and then also > setup some traps for taking on interface errors, etc. > > -- > > > Walter Keen > Network Technician > Rainier Connect > > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
