I am developping a EEM TCL script (let's say; "INT.tcl" based on a syslog event which has to occur 3 times in less that 60 seconds to be executed
::cisco::eem::event_register_syslog tag e1 pattern "xxxxxxx" occurs 3 period 60.
The event is correlated with ::cisco::eem::event_register_none, in order to execute this script from another script (let's say: LAUNCH.tcl)
I am trying to find a solution to stop INT.tcl execution (exit 0) after 60 seconds (if I am not wrong, by default, if the event ::cisco::eem::event_register_none happens one (execution from LAUNCH.tcl), the it continues indefinitely to monitor syslogs up to have 3 events in less than 60s.
I really don't have a clear picture of what you're wanting to do. It would be helpful to see the full contents of your scripts in addition to more details. My initial gut answer is that by default an EEM policy will terminate after 20 seconds (default maxrun). You can extend that to 60 or any other value if you want.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...