From: Mark Lasarko (mlasarko@co.ba.md.us)
Date: Sun Mar 19 2006 - 23:03:13 GMT-3
I've used it to send traps (CISCO-EMBEDDED-EVENT-MGR-MIB)
There's a white paper with a TCL example on a white paper @ www.cisco.com/go/eem
HTH,
Mark J. Lasarko, Sr.
CCDP, CCNP, CCSE, CNE, INFOSEC, MCSE, NSA, et al.
Senior Network Systems Engineer - Baltimore County Government
Office of Information Technology
400 Washington Avenue
Towson, Maryland 21204
United States of America
Email: mlasarko@co.ba.md.us
Voice:410.887.6202 | Pager:410.408.5949
Alpha page: 4104085949@archwireless.net
"Any fool can know. The point is to understand." (Albert Einstein)
"Failure only occurs at the point in which one stops trying." (Anonymous)
"There is no such thing as security - There are only various levels of risk management" (Me)
>>> "Aaron Pilcher" <apilcher@itgcs.com> 03/19/06 8:49 PM >>>
This is not directly related to studies, however maybe you guys have seen
this...
EEM doesn't seem to be too well documented, at least for the CLI features.
Looks like everything is working however, I do not fully trust that this is
operational. Is there something that I am missing or another way to verify?
I have configured..
track 100 interface Serial0/2/0 line-protocol
delay down 15 up 120
event manager applet IPX_REFRESH
event track 100 state any
action 1 cli command "clear ipx route *"
action 2 cli command "clear ipx sap *"
What seems to be my only useful verification is..
NS-LAB# sh event manager history events detailed
No. Time of Event Event Type Name
1 Sat Mar18 18:23:11 2006 track applet: IPX_REFRESH
track 100 state {up}
2 Sat Mar18 18:24:27 2006 track applet: IPX_REFRESH
track 100 state {down}
3 Sat Mar18 18:28:54 2006 track applet: IPX_REFRESH
track 100 state {up
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3