05-29-2015 07:26 PM
Good evening gentlemen,
I've noticed that, on one of my L3 switchs, my EEM scripts that are using timer as a detector simply aren't triggering at all.
I don't know if there is something wrong with the syntax or if it is a bug.
I have tried a simpler version of what I need and isn't working either, which is the following:
event manager applet test event timer countdown time 30 action 005 syslog msg "test" action 010 cli command "end"
Nothing goes to logging or terminal output.
I also tried to enable the debug to see if I could catch anything but the output doesn't ring any bell to me. The output is the following:
May 29 23:01:09: fh_send_timer_fd_msg: msg_type=2 May 29 23:01:09: fh_fd_timer_event_create: re=0x660D87C, sid=196 May 29 23:01:09: fh_send_timer_fd_msg: sval=0 May 29 23:01:42: fh_send_timer_fd_msg: msg_type=114 May 29 23:01:42: fh_send_timer_fd_msg: sval=0 May 29 23:02:48: fh_send_timer_fd_msg: msg_type=10 May 29 23:02:48: fh_fd_timer_event_unregister: re=0x65B98D0, sid=195 May 29 23:02:48: fh_send_timer_fd_msg: sval=0 May 29 23:02:48: fh_send_timer_fd_msg: msg_type=6 May 29 23:02:48: fh_fd_timer_event_register: re=0x660D87C, sid=196 May 29 23:02:48: fh_send_timer_fd_msg: sval=0 May 29 23:02:48: fh_send_timer_fd_msg: msg_type=4 May 29 23:02:48: fh_send_timer_fd_msg: sval=0 May 29 23:02:48: fh_send_timer_fd_msg: msg_type=32 May 29 23:02:48: fh_fd_timer_event_arm: re=0x660D87C, sid=196 May 29 23:02:48: fh_send_timer_fd_msg: sval=0
I've searched known bugs under Cisco bugsearch and Google but couldn't find a similar scenario.
Does anyone know what is wrong?
Additional information:
- Switch: WS-C3750X-48T-S
- IOS Version: 12.2(53)SE2
- Embedded Event Manager Version 3.20
- License: ipservices
Solved! Go to Solution.
05-31-2015 03:27 AM
I haven't seen any issues in 15.0(2)SE relating to timers. There is a bug in 15.2 code where the timer ED is missing, though.
05-30-2015 10:18 AM
This sounds vaguely familiar, but I don't think a bug was ever filed given that the code is fairly old, it was hard to reproduce, and a reboot recovered the issue. That said, a countdown timer only executes once, so make sure that you're reregistering the policy to get the timer to rearm.
05-30-2015 10:23 AM
Thanks for answering Joseph.
Yes, I've tested several times and in several switchs. Only that one fails to do anything at all which makes me think it is a bug.
If I change to event none and trigger it manually it works just fine.
Is there a way to check if the policy was registered correctly? Maybe check the remaining timer until it is triggered or even if there is any process that should be running?
05-30-2015 04:00 PM
show event manager policy registered will show if it's registered properly. Unfortunately, seeing the remaining timer seconds is not yet implemented (though I have requested it).
05-30-2015 04:10 PM
I just tested once again and no dice. Is this the output expected?
switch#sh run | begin applet event manager applet test event timer countdown time 60 action 005 syslog msg "test" action 010 cli command "end" ! end switch#sh clock 20:06:26.219 BRT Sat May 30 2015 switch#show event manager policy registered No. Class Type Event Type Trap Time Registered Secu Name 1 applet user timer countdown Off Sat May 30 20:03:02 2015 none test time 60.000 maxrun 20.000 action 005 syslog msg "test" action 010 cli command "end"
I should be able to get a window to reboot it next week.
I wonder if the last available ios fixes this.
05-31-2015 03:27 AM
I haven't seen any issues in 15.0(2)SE relating to timers. There is a bug in 15.2 code where the timer ED is missing, though.
05-31-2015 09:24 AM
Thanks again Joseph. I'll give it a try.
Hopefully it works.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide