Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Secondary route

We have a router (ROUTER1) that is managed by our software provider that creates a site to site VPN

connection. The router has an internal and external IP and we have the external address setup in BGP

as a network. This setup allows us to provide online services.

We have created a DR site and have a secondardy router (ROUTER2) setup there. I need to be able to

have all traffic go to ROUTER2 if the ROUTER1 is unable to make a connection or in a worst case

scenario, if that main location no longer exists.

As an example:

ROUTER1 IP: 10.20.102.125
ROUTER2 IP: 10.20.128.125

Then end IP address the routing needs to route to: 10.15.1.199

Currently, we have that setup as a network in BGP. We also have a static route setup at our main

location as such:

IP ROUTE 10.15.1.0 255.255.255.0 10.20.102.125


Since we have multiple sites (10 +), what would be the best way to provide the required failover?


Hope this makes sense.

Chris

Everyone's tags (4)
1 REPLY

Re: Secondary route

If I understand what you want to do correctly, you want to advertise networks out of the main site and the DR site in BGP.  If the main site goes down, you want all traffic to be redirected to the DR site.  If that is the case, advertise the same networks out of both routers (ROUTER1 and ROUTER2) in BGP, but use a route-map to as-path prepend the DR site a couple of times so the preferred route is going out of the main store, when that connection goes down the routes will go across to the DR site.

For example:

ip access-list standard local-site-networks

permit 10.10.10.0 0.0.0.255

ip access-list standard remote-site-networks

permit 10.10.20.0 0.0.0.255

router bgp 64722 (change your AS number here, and in the route-map below)

   neighbor 10.200.63.66 route-map BGP-to-ATT out

route-map BGP-to-ATT permit 10
  match ip address local-site-networks
route-map BGP-to-ATT permit 20
  match ip address remote-site-networks
  set as-path prepend 64722 64722 64722 64722


If that's not what you want to do, you can also use IP SLAs to do tracked routes for the 10.15.1.0/24 network.  If you run EIGRP between all of the remote stores and redistribute static into EIGRP, if the tracked route fails, the secondary route will install itself into the table and populate across EIGRP to all routers.

739
Views
0
Helpful
1
Replies
CreatePlease to create content