WAN cct redundancy - primary and secondary routers - IP SLA / BGP?

[mozmarr124]

Hi, im trying to work out how my redundancy works - Primary router with WAN cct and failover to Secondary cct with a different WAN cct

We need to failover from primary router to backup router as primary cct needs checks. We need to get the site running on the backup router / cct.

I cant see any HSRP or other FHRP running. I can see ip sla config and BGP as routing protocols.

I need to know how it works and how I can verify traffic and routes have moved over to the other router and are working. If I just shut the WAN link, this would automatically failover right?

Can anyone assist if I was to post configs?

We have vrf;s

e.g. router 1

#sh track
Track 240
IP SLA 240 reachability
Reachability is Up
66 changes, last change 10:20:49
Latest operation return code: OK
Latest RTT (millisecs) 146
Tracked by:
Static IP Routing 0

router 2

#show track

Track 240
IP SLA 240 reachability
Reachability is Up
8 changes, last change 5d09h
Latest operation return code: OK
Latest RTT (millisecs) 143
Tracked by:
Static IP Routing 0

[Reza Sharifi]

Hi,

Can you post a diagram of your network and how everything the setup?

HTH

[mozmarr124]

Hi, 2 routers at same site configured as below

R1

#show ip int brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 172.31.224.18 YES NVRAM up up    PRIMARY WAN
GigabitEthernet0/0/1 unassigned YES NVRAM up up      LAN
Gi0/0/1.308 10.86.15.147 YES NVRAM up up
GigabitEthernet0/0/2 unassigned YES unset administratively down down
GigabitEthernet0 unassigned YES NVRAM administratively down down
Loopback99 10.80.2.193 YES NVRAM up up     VRF 2061999 Management Loopback
Tunnel99 10.81.1.193 YES NVRAM up up          Management VRF transport
Vlan1 unassigned YES unset administratively down down

show vrf
Name Default RD Protocols Interfaces
1061901 53315:1 ipv4 Gi0/0/0
Gi0/0/1.308
2061999 53315:99 ipv4 Lo99
Tu99

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.81.1.253 4 56460 4107 4093 1974 0 0 10:49:34 22
10.81.1.254 4 56460 4103 4100 1974 0 0 10:49:29 22
172.31.224.17 4 4755 3831 4095 1974 0 0 10:49:40 35

R2

#show ip int brie
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0/0 172.31.224.14 YES NVRAM up up   SECONDARY LAN
GigabitEthernet0/0/1 unassigned YES NVRAM up up    LAN
Gi0/0/1.308 10.86.15.62 YES NVRAM up up
GigabitEthernet0/0/2 unassigned YES NVRAM administratively down down
GigabitEthernet0 unassigned YES NVRAM administratively down down
Loopback99 10.80.2.194 YES NVRAM up up   2061999 Management Loopback
Tunnel99 10.81.1.194 YES NVRAM up up  Management VRF transport
Vlan1 unassigned YES unset administratively down down

#show vrf
Name Default RD Protocols Interfaces
1061901 53315:1 ipv4 Gi0/0/0
Gi0/0/1.308
2061999 53315:99 ipv4 Lo99
Tu99

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.81.1.253 4 56460 113327 113261 249 0 0 1w5d 22
10.81.1.254 4 56460 113332 113254 249 0 0 1w5d 22
172.31.224.13 4 4755 105751 113275 249 0 0 1w5d 35

[Joseph W. Doherty]

BTW, if you have dynamic routing, using IP SLA often isn't needed as the dynamic routing should detect a path breakage and reroute around it.