EEM version 4.0 syslog issues

[surama123]

Good evening,

I have a new issue with a policy that used to work fine but has stopped working when I upgraded the IOS and EEM changes from version 3.2 to 4.0.

The policy was waiting for a syslog pattern (specified by _syslog_pattern environment variable) to execute but now will not execute. The purpose of the policy was to initialise some values at boot time and start the http server automatically.

The little documentation I can find about version 4.0 is at:

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6815/datasheet_c78-692254.html

This document states that 'EEM resource management' blocks new EEM policy execution when the system is already busy. As the system is very busy at start up I am wondering if this is what is preventing my boot up script from executing.

Any pointers would be appreciated.

Perhaps there is an easier way to launch my tcl http server automatically?

Ian

[Joe Clarke · Accepted solution]

There may be a problem if your script uses SYS-5-RESTART as this message may now be generated before EEM is configured.  You should consider switching to a cron policy and use "@reboot" as your cron entry.  However, it's hard to know for certain what the problem is since you didn't post your script.

[surama123]

Thanks Joseph, so Cron may be the way forward? Yes, I will try that and let you know the outcome.

[surama123]

Hi Joseph,

I can confirm that it works even in the latest IOS version. Thank you very much.

I now have in the router config:

event manager environment _cron_entry @reboot

and in the policy:

::cisco::eem::event_register_timer cron name crontimer2 cron_entry $_cron_entry maxrun_sec 600