EEM + IPSLA UDP-Jitter

[RededorTI]

Hi Fellows,

I'm trying to shutdown an interface in case of high packet loss.

I'm using IPSLA UDP jitter (PacketLossDS - PacketLossSD) to detect the losses and EEM to shutdown the interface.

the IPSLA is working fine, I can see there are losses through it, but the interface doesn't goes down.

Here is what I did:

ip sla 20110

udp-jitter 192.168.80.201 20000 num-packets 1000

request-data-size 1500

frequency 1800

ip sla schedule 20110 life forever start-time now

ip sla 20140

udp-jitter 192.168.80.197 20000 num-packets 1000

request-data-size 1500

frequency 1800

ip sla schedule 20140 life forever start-time now

ip sla reaction-configuration 20140 react packetLossDS threshold-value 10 1 threshold-type immediate action-type triggerOnly

ip sla reaction-configuration 20140 react packetLossSD threshold-value 10 1 threshold-type immediate action-type triggerOnly

event manager applet shutdown_tunnel

event tag packetLossDS_20140 ipsla operation-id 20140 reaction-type packetLossDS

event tag packetLossSD_20140 ipsla operation-id 20140 reaction-type packetLossSD

trigger

  correlate event packetLossSD_20140 or event packetLossDS_20140

  action 0 cli command "enable"

  action 1 cli command "configure terminal"

  action 2 cli command "interface tunnel20140"

  action 3 cli command "shutdown"

  action 4 cli command "end"

Am I missing something?

Thanks in advance!!!

[Jason Pfeifer]

Hi,

Can you tell if the EEM is triggering the applet, and the actions are just failing?  You can check that with

"show event manager history events". 

If the applet is triggering I would suggest turning on cli debugging with:

"debug event manager action cli"    This will let you see what the applet is doing line by line in its cli interaction.

Thanks!

[RededorTI]

Hi Jason,

Thanks for the answer!

The applet wasn't triggered, even with a match condition (Loss Source to Destination: 29).

here is the output of the IP SLA

IPSLA operation id: 20140

Type of operation: udp-jitter

        Latest RTT: 22 milliseconds

Latest operation start time: 17:50:11 UTC Mon Oct 14 2013

Latest operation return code: OK

RTT Values:

        Number Of RTT: 971              RTT Min/Avg/Max: 13/22/236 milliseconds

Latency one-way time:

        Number of Latency one-way Samples: 0

        Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds

        Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds

Jitter Time:

        Number of SD Jitter Samples: 941

        Number of DS Jitter Samples: 970

        Source to Destination Jitter Min/Avg/Max: 0/1/10 milliseconds

        Destination to Source Jitter Min/Avg/Max: 0/3/78 milliseconds

Packet Loss Values:

        Loss Source to Destination: 29

        Source to Destination Loss Periods Number: 29

        Source to Destination Loss Period Length Min/Max: 1/1

        Source to Destination Inter Loss Period Length Min/Max: 3/106

        Loss Destination to Source: 0

        Destination to Source Loss Periods Number: 0

        Destination to Source Loss Period Length Min/Max: 0/0

        Destination to Source Inter Loss Period Length Min/Max: 0/0

        Out Of Sequence: 0      Tail Drop: 0

        Packet Late Arrival: 0  Packet Skipped: 0

Voice Score Values:

        Calculated Planning Impairment Factor (ICPIF): 0

        Mean Opinion Score (MOS): 0

Number of successes: 1

Number of failures: 0

Operation time to live: Forever

Regards,

Raphael