I've seen an issue with the timer policy between EEM versions. The absolute timer "time" field is supposed to be the number of seconds since January 1 1970. This is the behaviour i am seeing on EEM 4.0.
I have 2 older devices, a 3600 and a 1700 that i am testing with and I am seeing different behaviour.
When i view the configured policy it shows the date as being 26 Jan 1970 whereas the same policy on the device with EEM 4.0 shows the date as being today.
Was there a version of EEM where the meaning of the time field was changed, e.g. went from milliseconds since epoch to seconds since epoch or could there have been a bug with earlier EEM versions?
C1700 Software (C1700-ENTSERVICESK9-M), Version 12.4(15)T, RELEASE SOFTWARE (fc3)
::cisco::eem::event_register_timer absolute time 1355148240 name timerets maxrun 0
Gives a date of
Mon Jan 26 1970 20:25:41.760
Version 15.2(2r)T, RELEASE SOFTWARE (fc1)
::cisco::eem::event_register_timer absolute time 1355147040 name timertest maxrun 0
Gives a date of
Mon Dec 10 2012 13:44:00.000
This document is what i follow for the correct use of variables:
I know of no one else using this timer, so it's very likely that you have found a bug. I couldn't locate one that describes this, though. From what I've seen, it doesn't appear to me milliseconds exactly. When I take 1355148.240 ms, I get
Fri Jan 16 11:25:48 1970. I see a lot of code changes in this area, so it wouldn't surprise me if this bug was squashed anonymously.
I have applied the same policy as Joe on a 2691 with similar results:
::cisco::eem::event_register_timer absolute time 1355218200 name timertest15 maxrun 0