In this article, I will explain how we can configure Cisco routers for WAN redundancy and automatic change routing using IP SLA (Service level agreement). IP SLA is a feature that enable the network administrators to analyze ip service levels for ip applications and services, and understand the network performance. It measures some parameters such as delay, jitter, packet loss, path, connectivity and other parameters, thus creating accurate statistics and depending on these measurements or statistics, the routers can take an action as we will see in this article. In our Scenario, we have branch site connected to the main site using two links, one of them will be used as primary link that will carry all the data from the branch to the main site, and backup link (Secondary link) that will be used if the primary link goes down. in this article we will be covering just the icmp-echo feature used by IP SLA. The idea of this lab is configuring two routes on the branch router R3 to get the the main site -destination network 192.168.40.0/24, and using SLA icmp-echo feature to send icmp-echo to R1. if R3 didn't receive reply from R1, R3 will consider it down and automatically uses the other route or link to reach the main site network. Configuration Steps 1-Conguring IP SLA to ping a target : the target is R1 in the main site that has ip 192.168.20.2.This ping that shown in the image below will be sent every 10 second using frequency 10 command. R3 will consider R1 down if it didn't receive reply from it within 6 seconds using timeout 6000 command. It is possible schedule the SLA operation in different ways but in this article I want to start the ip SLA operation immediately and forever. 2-Track the state of the IP SLA Reachability: the “track state” will be down only in case of a ICMP timeout using track 1 ip sla 1 reachability command. By using the above command, we define an object that tracks the SLA probe (track object number is 10 in this example). This can be accomplished by using the IOS Track Object as shown above. The above command will track the state of the IP SLA operation. If there are no ping responses from the next-hop IP -defined in sla 1- the track will go down and it will come up when the ip sla operation starts receiving ping response. To show the state of the Reachability use sh track command. 3- Define the tracked route : add the track statement to the route pointing to R1 , The track number specifies that the static route will be installed only if the state of the configured track object is up. Hence if the track status is down the secondary route will be used to forward all the traffic. 4- verify your configuration : The commands in the image below are issued after making sure that all the links (primary and secondary is up) between the branch and the main site. The image below shows that R3 can ping to R1, the track state is up as shown in the show track command, and the router uses R1 IP address 192.168.20.2 as a next hop to reach the main site destination network 192.168.40.0/24. Now , i removed the link between R3 and R1, Let's see what happened in R3. As you see in the image below, R3 changes the route automatically to R2 ip address 192.168.30.2. More explanation about the configuration, watch the video at top of this article or visit the following links Cisco router dual wan redundancy/failover using ip sla tracking https://youtu.be/x3xZhbrX7Ww To download the configuration file, click on the following link cisco router wan failover configuration file Keywords: cisco wan redundancy design ; cisco wan failover ; cisco wan failover config ; cisco wan failover configuration ; cisco wan failover ip sla ; cisco wan failover to vpn ; cisco wan failover nat ; cisco wan link redundancy ; cisco failover wan connections ; cisco wan redundancy ; cisco wan failover configuration via ip sla ; cisco dual wan failover config single router ; cisco dual wan redundancy ; cisco wan failover example ; cisco wan link failover ; cisco wlc redundancy over wan ; cisco dual wan failover using sla tracking ; cisco asa wan failover vpn in the upcoming articles ; cisco wan failover configuration ; cisco wan failover ip sla ; cisco wan failover config ; cisco failover wan connections ; cisco asa wan failover in the upcoming articles ; cisco dual wan failover ; cisco router wan failover ; cisco 1921 wan failover ; cisco 881 wan failover ; cisco 2911 wan failover ; cisco wan failover ; cisco wan failover configuration via ip sla ; cisco dual wan failover config single router ; cisco 1811 dual wan config failover ; cisco dual wan failover using sla tracking ; cisco router dual wan failover ; cisco asa dual wan failover in the upcoming articles ; cisco ios dual wan failover ; cisco 891w dual wan failover ; cisco 881 dual wan failover ; cisco rv042 dual wan failover ; cisco 1841 dual wan failover ; cisco wan failover example ; wan failover in cisco router ; cisco wan link failover ; cisco multi wan failover ; cisco wan failover nat ; cisco dual wan failover config on single router ; wan failover on cisco router ; cisco asa failover over wan in the upcoming video ; cisco dual wan router failover ; cisco router automatic wan failover ; cisco wan failover to vpn ; cisco asa wan failover vpn in the upcoming articles ; cisco dual wan vpn failover ; cisco router with wan failover ; cisco 1941 wan failover ; cisco 1841 wan failover ; cisco 1812 wan failover ; cisco 2811 wan failover ; cisco 5505 wan failover ; cisco asa 5510 wan failover in the upcoming articles ; cisco asa 5500 wan failover in the upcoming articles ; cisco 871 wan failover ; cisco 861 wan failover ; cisco wan failover configuration via ip sla ; cisco failover ip sla ; isco wan failover ip sla ; cisco dual wan failover using sla tracking ;