IP SLA Tracking with Configuration Example

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(New page: {{Template:Required Metadata}} ==Introduction== <!--Describe the purpose of the example and any unique characteristics of this configuration--> ==Design== <!--Describe any setup detail...)
(Related Information)
 
(7 intermediate revisions not shown)
Line 1: Line 1:
{{Template:Required Metadata}}
{{Template:Required Metadata}}
-
==Introduction==
 
-
<!--Describe the purpose of the example and any unique characteristics of this configuration-->
 
-
==Design==
 
-
 
-
<!--Describe any setup details of this configuration and include a topology-->
 
-
 
-
[[Image:sample_topology.jpg]]
 
-
 
==Configuration==
==Configuration==
Line 56: Line 48:
-
==Show running-config==
 
-
<pre>Add show running config of your device</pre>
 
==Related Information==
==Related Information==
-
[http://www.cisco.com/web/psa/products/index.html Technical Support & Documentation - Cisco Systems]
+
[http://www.cisco.com/cisco/web/support/index.html Technical Support & Documentation - Cisco Systems]
<!--List links to related information-->
<!--List links to related information-->
<!--Add appropriate categories-->
<!--Add appropriate categories-->
 +
[[Category:IOS Software and NX-OS Software Configuration Examples]]

Latest revision as of 19:33, 18 November 2011


Configuration

<ip sla 1 < The number 1 here is arbitrary, used only to identify this sla. It is otherwise known as the operation number>


icmp-echo 4.2.2.2 < 4.2.2.2 is a DNS server that responds to pings out on the internet>


timeout 500 < This is how long to wait for a response from the ping>

frequency 3 < This is the repeat rate for the SLA>

ip sla schedule 1 start-time now life forever < This command says "start SLA 1 now and keep it running forever>

track 1 rtr 1 reachability < This comand creates the track object "1" and monitors the SLA 1>

now for the routing, we need to change the default route and associate it with the tracker

no ip route 0.0.0.0 0.0.0.0 1.1.1.1

and then put it back with the tracking

ip route 0.0.0.0 0.0.0.0 1.1.1.1 track 1

Then we need to add our secondary route


ip route 0.0.0.0 0.0.0.0 1.1.1.2 10 <we set this route with a higher metric than the tracked route>

ip route 4.2.2.2 255.255.255.255 1.1.1.1 ==> 1.1.1.1 being your primary next hop ip address

Now when the ping to 4.2.2.2 fails the primary route is removed and the secondary route with the higher metric becomes the default.

The route will be reinstated when the connectivity is restored.

>

Related show Commands

This section provides information you can use to confirm your configuration is working properly.

Certain show commands are supported by the Output Interpreter Tool (registered customers only), which allows you to view an analysis of show command output.



Related Information

Technical Support & Documentation - Cisco Systems

Rating: 4.6/5 (16 votes cast)

Personal tools