Cisco IOS Embedded Event Manager is like some automation within a switch or router. They generally work on this way :
Step 1 :
Event happen.
Step 2 :
Action to be take when above event happen.
The best part of Embedded Event Manager is that you can define set of CLI commands which Cisco router/switch will perform when it catch certain "Event".
Event examples are like : syslog message, interface down , interface up etc.
Action examples are like : run specific CLI commands etc.
In this post I am taking very simple example of Cisco IOS Embedded Event Manager. In this example , it will catch "track status" as Event and put interface to shut or no shut as Action.
IP SLA and TRACKING are another topics which I will discuss in separate blog.
Please find the simple example of Embedded Event Manager :
In above example, Embedded Event Manager will check the status of "track 50" if it is down than it will put Gig 0/1 to no shut. Have you notice CLI commands which are to be run ?
Second related example is :
By reading above Embedded Event Manager commands you can understand what it will do.Embedded Event Manager will check the status of "track 50" if it is UP than it will put Gig 0/1 to shut.
In this post, I tried to give you just a little bit description of Cisco IOS Embedded Event Manager and its action. You can do lot more things with it.
Step 1 :
Event happen.
Step 2 :
Action to be take when above event happen.
The best part of Embedded Event Manager is that you can define set of CLI commands which Cisco router/switch will perform when it catch certain "Event".
Event examples are like : syslog message, interface down , interface up etc.
Action examples are like : run specific CLI commands etc.
In this post I am taking very simple example of Cisco IOS Embedded Event Manager. In this example , it will catch "track status" as Event and put interface to shut or no shut as Action.
IP SLA and TRACKING are another topics which I will discuss in separate blog.
Please find the simple example of Embedded Event Manager :
event manager applet port_up
description When my track status is down
event track 50 state down
action 0.1 cli command "enable"
action 1.0 cli command "conf term"
action 2.0 cli command "interface GigabitEthernet0/1"
action 3.0 cli command "no shut"
In above example, Embedded Event Manager will check the status of "track 50" if it is down than it will put Gig 0/1 to no shut. Have you notice CLI commands which are to be run ?
Second related example is :
event manager applet port_down
description when my track is UP
event track 50 state up
action 0.1 cli command "enable"
action 1.0 cli command "conf term"
action 2.0 cli command "interface GigabitEthernet0/1"
action 3.0 cli command "shut"
!
By reading above Embedded Event Manager commands you can understand what it will do.Embedded Event Manager will check the status of "track 50" if it is UP than it will put Gig 0/1 to shut.
In this post, I tried to give you just a little bit description of Cisco IOS Embedded Event Manager and its action. You can do lot more things with it.
This comment has been removed by the author.
ReplyDelete