CISCO C3825 link failover issue

Publication Date:  2012-07-18 Views:  251 Downloads:  0
Issue Description
In this case, customer used USG2100BSR in their branch office and used CISCO C3825 router in their HQ. And customer had two links from different ISP, they requested these two links can did the link failover.
After we configured failover founction with ip-link in our USG2100BSR, tested link failover in branch office, it's working.But in their HQ, the link failover didn't happen in C3825.
Alarm Information
NA
Handling Process
After check CISCO device and documents, C3285 router support SLA like IP-link founction.

Suggest customer to add SLA configuration in C3825. The main content is below:

ip sla monitor 1
type echo protocol ipIcmpEcho 172.32.2.82 source-ipaddr 172.32.2.22
frequency 10   //172.32.2.82 is the other side gateway ip of ISP1 link.
ip sla monitor schedule 1 life forever start-time now
ip sla monitor 2
type echo protocol ipIcmpEcho 10.0.59.25 source-ipaddr 10.0.59.29
frequency 10   //10.0.59.25 is the other side gateway ip of ISP2 link.
ip sla monitor schedule 2 life forever start-time now

ip route 192.168.126.0 255.255.255.0 172.32.2.21 10 track 1  //172.32.2.21 is next hop IP
ip route 192.168.126.0 255.255.255.0 10.0.59.30 30 track 2   //10.0.59.30  is next hop IP

Then test both sides link failover, it's working.
Root Cause
When we tested link failover in branch office, after we pull out the ISP1 cable from USG2100BSR, our box can failover to ISP2 link automatically. But at the same time, customer HQ C3825 device can't detect what happen in branch office, and ISP1 link still up, can't failover to ISP2 timely.
Suggestions
Sometimes, we also need to know something about other vendor product, and can give some good suggestions to customer. Customer will appreciate it and we can close project in early time.

END