|
Author
|
Topic: IOS IP SLA
|
The Mongoose
Elite
Member # 28888
Rate Member
|
posted November 09, 2011 11:15 AM
I'm trying to understand why my icmp-echo reaction entry isn't behaving the way I want...
If I configure an icmp-echo probe its a single ping ever x seconds. But I don't really want my track object to go down if it misses a single ping. (What if I have a small amount of loss).
So if I configure:
ip sla reaction-configuration 200 react timeout threshold-type consecutive 3 action-type trapAndTrigger
It still marks it down after 1 failure. I can not configure the reaction-trigger since the entry and operation # can not be the same.
Is there a easy way to do this with the icmp-echo probe or am I forced into using jitter operations (which seem to be more flexible)?
-M-
Posts: 307 | From: Canada | Registered: Sep 2009
| IP: Logged
|
|
Venkat Ragothaman
Member
Member # 31347
Rate Member
|
posted November 09, 2011 01:57 PM
quote: Originally posted by The Mongoose: I don't really want my track object to go down if it misses a single ping. (What if I have a small amount of loss).
How about configuring a delay under the track object in announcing 'down' like below?
track 2 ip sla 1 reachability delay down 30
Thanks.
Posts: 24 | From: Bangalore | Registered: Sep 2011
| IP: Logged
|
|
The Mongoose
Elite
Member # 28888
Rate Member
|
posted November 09, 2011 03:02 PM
Yep that would be one way of doing it...just surprises me the way they've implemented this.. especially compared to ASAs config.
Posts: 307 | From: Canada | Registered: Sep 2009
| IP: Logged
|
|
Venkat Ragothaman
Member
Member # 31347
Rate Member
|
posted November 09, 2011 09:03 PM
As you would know, IOS IP SLA is a much larger feature with a variety of options under it. End to end jitter measurement is one. ASA, ofcourse, draws from IOS IP SLA, doesn't implement everything and takes a divergence to implement 'num-packets' instead of more complex jitter options.
Posts: 24 | From: Bangalore | Registered: Sep 2011
| IP: Logged
|
|