IP SLA Stopped Polling

[Carlton Patterson]

Hello Community,

I have configured the following ip sla:

ip sla 7

icmp-echo 195.1xxx.xxx.xxx

tag sla7_DLR_Package6_DMVPN_195.xxx.xxx.xxx

ip sla schedule 7 life forever start-time now

ip sla 8

The actual configuration is as follows:

UK00132-DM05-MapleCross#show ip sla configuration 7

IP SLAs, Infrastructure Engine-II.

Entry number: 7

Owner:

Tag: sla7_DLR_Package6_DMVPN_195.xxx.xxx.xxx

Type of operation to perform: icmp-echo

Target address/Source address: 195.xxx.xxx.xxx/0.0.0.0

Type Of Service parameter: 0x0

Request size (ARR data portion): 28

Operation timeout (milliseconds): 5000

Verify data: No

Vrf Name:

Schedule:

   Operation frequency (seconds): 60  (not considered if randomly scheduled)

   Next Scheduled Start Time: Start Time already passed

   Group Scheduled : FALSE

   Randomly Scheduled : FALSE

   Life (seconds): Forever

   Entry Ageout (seconds): never

   Recurring (Starting Everyday): FALSE

   Status of entry (SNMP RowStatus): Active

Threshold (milliseconds): 5000 (not considered if react RTT is configured)

Distribution Statistics:

   Number of statistic hours kept: 2

   Number of statistic distribution buckets kept: 1

   Statistic distribution interval (milliseconds): 20

History Statistics:

   Number of history Lives kept: 0

   Number of history Buckets kept: 15

   History Filter Type: None

Enhanced History:

Everything was working fine i.e. it was polling the the ip address 195.xxx.xxx.xxx and when the wasn't available I would get a message through my application.

However, for some reason the ip sla has stopped working. The interface with ip address 195.xxx.xxx.xxx is down, but the ip sla isn't responding.

Is there some kind of timeout?

Cheers

Carlton

[Peter Paluch]

Hi Carlton,

Can you also post the output of show ip sla statistics related to this probe? Also, if the results of this probe are fed into a track object, can you post its configuration and the output of show track status? Thank you!

Best regards,

Peter

[Carlton Patterson]

Hi Peter

Thanks for responding:

UK00132-DM05-MapleCross#show ip sla statistics 7

IPSLAs Latest Operation Statistics

IPSLA operation id: 7

Type of operation: icmp-echo

        Latest RTT: NoConnection/Busy/Timeout

Latest operation start time: 13:19:26.120 BST Fri Sep 6 2013

Latest operation return code: Timeout

Number of successes: 0

Number of failures: 28

Operation time to live: Forever

[Carlton Patterson]

Peter,

The results aren't fed into a track object.

[cadet alain]

Hi,

Can you ping the IP manually ? Is there a route to it in the RIB ?

Regards

Alain

Don't forget to rate helpful posts.

[Carlton Patterson]

Hi Cadet,

No I can't ping the IP manually. Which is why I should get a message back....

Weird, as it was working before.

I think its a configuration issue as none of my ip sla's appear to be working...

[cadet alain]

Hi,

Have you got a route to this IP ? sh ip route 195.1xxx.xxx.xxx and sh ip cef 195.1xxx.xxxx.xxxx

Regards

Alain

Don't forget to rate helpful posts.

[Carlton Patterson]

Hi Cadet,

There isn't a route to the ip. However, I thought the point of the ip sla in this instance is to send an alert if its not able to ping the the address:

ip sla 7

icmp-echo 195.1xxx.xxx.xxx

tag sla7_DLR_Package6_DMVPN_195.xxx.xxx.xxx

ip sla schedule 7 life forever start-time now

ip sla 8

[cadet alain]

Hi,

if you've got no route then the icmp echo won't even leave the router as it is unroutable so IP SLA will tell you nothing, it will only pop a log if the probe didn't receive a reply within the timeout but I don't think it will tell you something if it doesn't even send the probe.

Regards

Alain

Don't forget to rate helpful posts.

[Carlton Patterson]

Cadet,

The router uses a default route to get to 195.1xx.xx.xxx, and every other network.

[Carlton Patterson]

Cadet,

I don't think you're correct in what you're saying. IP SLA should kick in if it can't ping the ip address no matter what...

[cadet alain]

Hi,

I just labbed it and IP SLA never gives a console message, you can use ip sla logging trap but this will send syslog traps(SNMP) to NMS.Now if you configure a track object linked to the IP SLA instance then you get a log when the track object goes up/down.

Regards

Alain

Don't forget to rate helpful posts.

[cadet alain]

Hi,

then  show ip cef would have given the info but you told me there was no route to this address so my previous reply.

Can you trace this IP  from this device, what about pinging from another subnet(interface) ?

Regards

Alain

Don't forget to rate helpful posts.

[Carlton Patterson]

Hi Cadet,

I recreated the exact same ip sla on another device. The device wasn't able to ping 195.1xx.xxx.xxx as expected and I got a message.

So my thoughts are that there might be some timeout on the sla?

[cadet alain]

Hi,

I hadn't the same behaviour as you , on which platform/IOS are you testing ?

Regards

Alain

Don't forget to rate helpful posts.