WAN MPLS port hanging until reboot, IP SLA configured

[uzair.baig]

Dear All,

We have three sites each are connected to two MPLS connection(Full Mesh). And we have configured routing by static and default routes. and configured IP SLA for failover and PBR for specific traffic.

Router on each site is 2811 

Each router is having two MPLS links connected via different ISP i.e., Tata and Reliance

We have configured routing to prefer Tata first and Reliance as backup.

When Tata link goes down, we are getting access over from reliance.

But when once Tata link comes back then we are unable to rollback to Tata MPLS. Even we are not able to ping the next hop IP address until reboot.

Once we reboot we are getting access over TATA link.

Please Suggest..... 

Thanks,

Uzair

[Akash Agrawal]

Please provide router config. Also share preliminary troubleshooting done.

Is ping failing to wan ip?

Is ARP getting completed?

If we configure static ARP, are we able to ping?

If ARP not getting completed, debug arp may help. Check ARP status on ISP side as well

Regards,

Akash

[uzair.baig]

Thanks Akash,

Self Ping of wan ip is working but not ISP side IP, even interface is UP and Line Protocol is UP

ARP is showing incomplete for ISP side IP.

IOS on the router c2800nm-entbasek9-mz.150-1.M10.bin

R1(fa0/1)------Reliance(ISP)------(g0/0)R2

R1(fa0/1/0)---TATA(ISP)------(fa0/0/1)R2

*************************************************************

R1 Config

interface FastEthernet0/1
 description ***Reliance-MPLS-link***
 ip address 10.24.7.41 255.255.255.252
 duplex auto
 speed auto

interface FastEthernet0/1/0
 description ***TATA-MPLS-link***
 ip address 10.5.10.9 255.255.255.252
 duplex auto
 speed auto

ip route 192.168.80.0 255.255.255.0 10.5.10.10 track 333
ip route 192.168.80.0 255.255.255.0 10.24.7.42 20

track 333 ip sla 333 reachability

ip sla 333
 icmp-echo 10.5.10.1 source-ip 10.5.10.9
ip sla schedule 333 life forever start-time now

***********************************************************

R2 Config

************

interface GigabitEthernet0/0

 description ***Reliance-MPLS-link***
 ip address 10.24.7.33 255.255.255.252
 duplex auto
 speed auto

interface FastEthernet0/0/1
 description ***Connect-tata***
 ip address 10.5.10.1 255.255.255.252
 duplex auto
 speed auto

ip route 0.0.0.0 0.0.0.0 10.5.10.2 track 333

ip route 0.0.0.0 0.0.0.0 10.24.7.34 50

track 333 ip sla 333 reachability

ip sla 333
 icmp-echo 10.5.10.9 source-ip 10.5.10.1
ip sla schedule 333 life forever start-time now

********************************************************

sh processes cpu sorted 
CPU utilization for five seconds: 2%/1%; one minute: 4%; five minutes: 3%

[Akash Agrawal]

Thanks for sharing config, I am confused with config. Why are you tracking TATA link of R2 on R1 and vice versa.

[uzair.baig]

For Static Rotue failover.