There are at least three good ways to run an Embedded Event Manager policy every time a device boots up. Two of the methods involve using timer policies while one uses a syslog policy. These methods will work for any device running EEM 2.0 or higher. See https://supportforums.cisco.com/docs/DOC-8799 on how to determine your version of EEM. Let's look at the syslog policy first.
When a device boots, it will generate a %SYS-5-RESTART syslog message. EEM can intercept this message and take your required boot up actions. The following are example event registration lines for this method.
The second method involves using a countdown timer. When the timer policy is registered it will begin to countdown the specified number of seconds. At boot time, the policy will be read from the startup configuration and registered with EEM. At that point, the timer begins. The advantage of this approach is that you can inject some delay after the device comes online before the EEM policy runs. However, there is a down side. When you configure this policy, it will countdown to zero then run. If you'd rather not have this run after first configuring it, download the startup-config, and add the commands to register your policy. Then copy that configuration back into the startup-config.
The following are example event registration lines for this method. They will run the policy ten seconds after the device boots and configures itself.
event timer countdown time 10
::cisco::eem::event_register_timer countdown time 10
The final example uses a cron timer with a special cron-entry. A policy registered in such a way will generally run within a minute after the device is booted. The following are example event registration lines for this method.
Whether you're attending VMworld 2019 on-site or from afar, read the latest on the key themes to expect. They are also the key themes for IT management today, from software defined everything to cloud and automation to IoT and edgecomputing : http:...
Hi All,our backup server is connect with cisco 3750. that port is configued as Trunk VLAN100. for other sw to sw links we are using VLAN1 trunk. my question is trunk allows all vlan traffic to pass then why they have put vlan100 instead of vlan1 ...
We have a Shoretel VOIP system and I want to ensure I have QOS properly in place on my 3850 and 2960 stacks. We want dscp 46 to have higher priority from what I understand. We basically did "auto qos voip trust" on all user ports, and "au...