Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4229
Views
0
Helpful
5
Replies

problem with implemanting eem track for ip sla

Go to solution
ran.malevsky
Level 1
Level 1

‎06-07-2011 03:21 AM

hi

i'm trying to implement a track for is sla

which will put a notice (later i will change it to restart the interface) on screen

the tracking is working however the applet doesn't recognize the state change

below are config and logging

do  you see a mistake?

what am i doing wrong?

thanks

ran

config

1.my ip sla config is :

ip sla 2

icmp-echo 1.1.1.1 source-interface Loopback1

ip sla schedule 2 life forever start-time after 00:00:05

2. my track config is :

track 1 ip sla 2 reachability

track 3 ip sla 2

3. my eem applets are :

event manager applet lostcell

event track 1 state down

action 1.0 puts "cellular_is-down"

action 2.0 end

event manager applet cell3

event track 3 state down

action 1.0 puts "cellular3"

action 2.0 end

some sh and tell

clear logg

sh track brief

Track   Object                           Parameter        Value Last Change

1       ip sla      2                    reachability     Up    00:03:07

2       ip route    1.1.1.1/24           reachability     Down  01:05:54

3       ip sla      2                    state            Up    00:03:07

conf t

int cell 0

sh

end

sh track brief
Track   Object                           Parameter        Value Last Change
1       ip sla      2                    reachability     Down  00:00:00
2       ip route    1.1.1.1/24           reachability     Down  01:06:48
3       ip sla      2                    state            Down  00:00:00

sh logg (from interface shut)

.Jun  7 10:08:14.410: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel1, changed state to down

.Jun  7 10:08:14.410: fh_fd_syslog_event_match: num_matches = 0

.Jun  7 10:08:14.410: fh_fd_data_syslog: num_matches = 0

.Jun  7 10:08:23.606: cli_history_entry_add: free_hist_list size=0, hist_list size=7

.Jun  7 10:08:23.606: check_eem_cli_policy_handler: command_string=show track brief

.Jun  7 10:08:23.606: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

.Jun  7 10:08:34.763: cli_history_entry_add: free_hist_list size=0, hist_list size=7

.Jun  7 10:08:34.763: check_eem_cli_policy_handler: command_string=show track brief

.Jun  7 10:08:34.763: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

.Jun  7 10:08:36.935: cli_history_entry_add: free_hist_list size=0, hist_list size=7

.Jun  7 10:08:36.935: check_eem_cli_policy_handler: command_string=show track brief

.Jun  7 10:08:36.935: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

.Jun  7 10:08:38.095: cli_history_entry_add: free_hist_list size=0, hist_list size=7

.Jun  7 10:08:38.095: check_eem_cli_policy_handler: command_string=show track brief

.Jun  7 10:08:38.095: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

.Jun  7 10:08:44.479: %TRACKING-5-STATE: 3 ip sla 2 state Up->Down

.Jun  7 10:08:44.479: %TRACKING-5-STATE: 1 ip sla 2 reachability Up->Down

.Jun  7 10:08:44.479: fh_fd_syslog_event_match: num_matches = 0

.Jun  7 10:08:44.479: fh_fd_data_syslog: num_matches = 0

.Jun  7 10:08:44.479: fh_fd_syslog_event_match: num_matches = 0

.Jun  7 10:08:44.479: fh_fd_data_syslog: num_matches = 0

.Jun  7 10:08:45.011: cli_history_entry_add: free_hist_list size=0, hist_list size=7

.Jun  7 10:08:45.011: check_eem_cli_policy_handler: command_string=show track brief

.Jun  7 10:08:45.011: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

.Jun  7 10:09:00.003: fh_fd_timer_process_async

.Jun  7 10:09:00.003: cron_tick: num_matches 0

.Jun  7 10:09:01.819: cli_history_entry_add: free_hist_list size=0, hist_list size=7

.Jun  7 10:09:01.819: check_eem_cli_policy_handler: command_string=show logging

.Jun  7 10:09:01.819: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

.Jun  7 10:10:00.004: fh_fd_timer_process_async

.Jun  7 10:10:00.004: cron_tick: num_matches 0

.Jun  7 10:11:00.005: fh_fd_timer_process_async

.Jun  7 10:11:00.005: cron_tick: num_matches 0

.Jun  7 10:12:00.002: fh_fd_timer_process_async

.

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to ran.malevsky

‎06-08-2011 06:47 AM

Your policies didn't register.  Try:

no event manager applet lostcell

event manager applet lostcell

event track 1 state down

action 1.0 syslog msg "cellular is down"

no event manager applet cell3

event manager applet cell3

event track 3 state down

action 1.0 syslog msg "cellular3"

What version of IOS is this?

View solution in original post

0 Helpful
5 Replies 5

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee

‎06-08-2011 01:01 AM

I don't see any problem with the applets (other than not needing an "end" action).  The puts should go to syslog, but you might try changing the puts action to a syslog action:

action 1.0 syslog msg "cellular is down"

Post the output of "show event manager policy registered" and "show event manager history event"

0 Helpful

Go to solution
ran.malevsky
Level 1
Level 1
In response to Joe Clarke

‎06-08-2011 01:17 AM

ok

it looks like nothing is running

the lines return empty

any clues?

sh track brief

Track   Object                           Parameter        Value Last Change

1       ip sla      2                    reachability     Up    00:01:59

2       ip route    1.1.1.1/24           reachability     Down  00:04:12

3       ip sla      2                    state            Up    00:01:59

sh track brief

Track   Object                           Parameter        Value Last Change

1       ip sla      2                    reachability     Down  00:00:00

2       ip route    1.1.1.1/24           reachability     Down  00:04:13

3       ip sla      2                    state            Down  00:00:00

sh event manager policy registered

No.  Class     Type    Event Type          Trap  Time Registered           Name

sh event manager history events   

No.  Job Id Proc Status   Time of Event            Event Type        Name

*Jun  8 08:07:01.607: %LINK-5-CHANGED: Interface Cellular0, changed state to administratively down

*Jun  8 08:07:03.503: %SYS-5-CONFIG_I: Configured from console by console

*Jun  8 08:07:16.331: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel1, changed state to down

*Jun  8 08:07:48.880: %TRACKING-5-STATE: 3 ip sla 2 state Up->Down

*Jun  8 08:07:48.880: %TRACKING-5-STATE: 1 ip sla 2 reachability Up->Down

*Jun  8 08:13:34.865: cli_history_entry_add: free_hist_list size=0, hist_list size=7

*Jun  8 08:13:34.865: check_eem_cli_policy_handler: command_string=show logging

*Jun  8 08:13:34.865: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

*Jun  8 08:14:00.002: fh_fd_timer_process_async

*Jun  8 08:14:00.002: cron_tick: num_matches 0

*Jun  8 08:14:07.526: cli_history_entry_add: free_hist_list size=0, hist_list size=7

*Jun  8 08:14:07.526: check_eem_cli_policy_handler: command_string=show clock

*Jun  8 08:14:07.526: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

*Jun  8 08:14:13.382: cli_history_entry_add: free_hist_list size=0, hist_list size=7

*Jun  8 08:14:13.382: check_eem_cli_policy_handler: command_string=show logging

*Jun  8 08:14:13.382: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to ran.malevsky

‎06-08-2011 06:47 AM

Your policies didn't register.  Try:

no event manager applet lostcell

event manager applet lostcell

event track 1 state down

action 1.0 syslog msg "cellular is down"

no event manager applet cell3

event manager applet cell3

event track 3 state down

action 1.0 syslog msg "cellular3"

What version of IOS is this?

0 Helpful

Go to solution
ran.malevsky
Level 1
Level 1
In response to Joe Clarke

‎06-08-2011 09:27 AM

it worked

did the

no event manager ...

thanks

what do you think was the cause?

by the way

Version 15.1(1)T1, RELEASE SOFTWARE (fc2)

thanks again

ran

0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to ran.malevsky

‎06-08-2011 10:02 AM

I think that "end" was bogus.  The end action is for terminating a control or condition block.

0 Helpful
Customers Also Viewed These Support Documents

Review Cisco Networking for a $25 gift card