Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

EEM event track is not supported (version 3.2)

Hello,

I'm replacing a router 2911 by IE3010 (with IP service) and trying to transfer configurations across. I have noticed that on the IE3010 EEM , I can't trigger an event based on Object Tracking. 

IE3010(config-applet)#event ?
  application         Application specific event
  cli                       CLI event
  config                Configuration policy event
  counter             Counter event
  env                 Environmental event
  gold                GOLD event
  identity            Identity event
  interface           Interface event
  ioswdsysmon         IOS WDSysMon event
  ipsla               IPSLA Event
  mat                 MAC address table event
  neighbor-discovery  Neighbor Discovery event
  nf                  NF Event
  none                Manually run policy event
  oir                 OIR event
  routing             Routing event
  rpc                 Remote Procedure Call event
  snmp                SNMP event
  snmp-notification   SNMP Notification Event
  snmp-object         SNMP object event
  syslog              Syslog event
  tag                 event tag identifier
  timer               Timer event

I do have a track that monitors (ICMP-echo) of two IP addresses and I want to do some action when the track is down and this has been working quite well on the 2911.  I have found  in the IE3010 event detector that tracking event is not available while the same is available in the 2911

Any advise how can I solve this problem and how can I do action based on the status of the tracked object in the IE3010 ?

 

The software version of the IE3010 is as follows 

IE3010 Software (IE3010-IPSERVICESK9-M), Version 15.0(2)SE6, RELEASE SOFTWARE (fc2). 

 

Embedded Event Manager Version 3.20
Component Versions:
eem: (320_rel3)1.0.0
eem-gold: (v320_rel1)1.0.0
eem-call-home: (v320_rel1)1.0.2
Event Detectors:
Name                Version   Node        Type    
application         01.00     node0/0     RP      
identity            01.00     node0/0     RP      
neighbor-discovery  01.00     node0/0     RP      
mat                 01.00     node0/0     RP      
syslog              01.00     node0/0     RP      
routing             03.00     node0/0     RP      
cli                 01.00     node0/0     RP      
counter             01.00     node0/0     RP      
interface           01.00     node0/0     RP      
ioswdsysmon         01.00     node0/0     RP      
none                01.00     node0/0     RP      
oir                 01.00     node0/0     RP      
snmp                01.00     node0/0     RP      
timer               01.00     node0/0     RP      
snmp-object         01.00     node0/0     RP      
snmp-notification   01.00     node0/0     RP      
ipsla               01.00     node0/0     RP      
nf                  01.00     node0/0     RP      
test                01.00     node0/0     RP      
config              01.00     node0/0     RP      
env                 01.00     node0/0     RP      
gold                01.00     node0/0     RP      
rpc                 01.00     node0/0     RP     

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Yes, switches tend not to

Yes, switches tend not to support the track ED.  However, you should be able to react to changes in tracked objects using the syslog ED.  When your tracked object transitions, you should get a syslog message about a change from Up->Down and vice versa.  That can be as effective as the track ED.

5 REPLIES
Cisco Employee

Yes, switches tend not to

Yes, switches tend not to support the track ED.  However, you should be able to react to changes in tracked objects using the syslog ED.  When your tracked object transitions, you should get a syslog message about a change from Up->Down and vice versa.  That can be as effective as the track ED.

New Member

Hi Joseph,Many thanks for

Hi Joseph,

Many thanks for your valuable advice. I thought about that for a while but were not sure if it works. Will give it a go and inform

Regards

Baranan

New Member

Hi Joseph,It is working like

Hi Joseph,

It is working like a charm !

Below is the tested config for the EEM that implement shut/no shut an interface based on tracking of two objects using Cisco IE3010 industrial switch in case someone else got similar issue

track 18 list threshold weight
 object 118 weight 30
 object 250 weight 70
 threshold weight up 70

track 118 ip sla 118
 delay down 60

track 250 ip sla 250
 delay down 60
!
ip sla 118
 icmp-echo 10.2.105.2
ip sla schedule 118 life forever start-time now
!
ip sla 250
 icmp-echo 192.168.200.5
ip sla schedule 250 life forever start-time now

event manager applet Remote_Site_Down
 event syslog pattern "TRACKING-5-STATE: 18 list threshold weight Up->Down"
 action 1.0 cli command "enable"
 action 2.0 cli command "config t"
 action 3.0 cli command "interface vlan 18"
 action 4.0 cli command "shut"
 action 5.0 cli command "end"
event manager applet Remote_Site_Up
 event syslog pattern "TRACKING-5-STATE: 18 list threshold weight Down->Up"
 action 1.0 cli command "enable"
 action 2.0 cli command "config t"
 action 3.0 cli command "interface vlan 18"
 action 4.0 cli command "no shut"
 action 5.0 cli command "end"

 

 

Best regards

 

Baranan 

New Member

I need to track if an IP is

I need to track if an IP is up with ICMP,  Source IP: 192.168.249.1 Dest IP: 192.168.249.2 on port FastEthernet fa0/19

I do not understand how the weights work here with the UP or Down Status can you please explain. I modified your commands a bit and this is what I got, can you let me know if I am on the right path:

 

track 10 ip sla 10
 delay down 10
!
track 19 list threshold weight
 object 10 weight 70
 threshold weight down 30 up 70
authentication mac-move permit

ip sla 10
 icmp-echo 10.13.249.2 source-ip 10.13.249.1
 timeout 300
 frequency 5
ip sla schedule 10 life forever start-time now
ip sla enable reaction-alerts
 

event manager applet Remote_Site_Up
 event syslog pattern "TRACKING-5-STATE: 19 list threshold weight Down->Up"
 action 1.0 cli command "enable"
 action 2.0 cli command "config t"
 action 3.0 cli command "interface FastEthernet0/19"
 action 4.0 cli command "no shut"
 action 5.0 cli command "end"
event manager applet Remote_Site_Down
 event syslog pattern "TRACKING-5-STATE: 19 list threshold weight Up->Down"
 action 1.0 cli command "enable"
 action 2.0 cli command "config t"
 action 3.0 cli command "interface FastEthernet0/19"
 action 4.0 cli command "shut"
 action 5.0 cli command "end"

--------------------------

This is the status with the show track command:

Track 10
  IP SLA 10 state
  State is Up
    1 change, last change 00:29:35
  Delay down 10 secs
  Latest operation return code: OK
  Latest RTT (millisecs) 1
Track 19
  List threshold weight
  Threshold Weight is Up (70/70)
    2 changes, last change 00:29:34
    object 10 weight 70 Up (70/70)
  Threshold weight down 30 up 70

 

 

 

 

Cisco Employee

Please start a new thread for

Please start a new thread for this question.

982
Views
0
Helpful
5
Replies
CreatePlease to create content