c1sc0m4n
asked on
BGP Disaster Recovery Scenario
I'm not sure if any BGP expert out there has come accross this before but I will give my scenario:
I have one main site with multiple remotes (6 or so) in a hub and spoke topology. BGP running as the routing protocol as the network runs over MPLS VPN and thus the protocol needs to be TCP based.
There is HSRP and ISDN Backup at the centre. My question is this:
Can I have a DR Site that runs BGP via another AS (or can be iBGP) that will advertise the same network as the main site but that network is weighted so that it becomes live if centre fails? i.e. If the link into the WAN from the centre site goes down (say 192.168.1.0/24), the backup network (192.168.1.0/24 Same but weighted?) becomes active?? So DR is automated? Or is this not possible?
Any help would be greatfully received.
I have one main site with multiple remotes (6 or so) in a hub and spoke topology. BGP running as the routing protocol as the network runs over MPLS VPN and thus the protocol needs to be TCP based.
There is HSRP and ISDN Backup at the centre. My question is this:
Can I have a DR Site that runs BGP via another AS (or can be iBGP) that will advertise the same network as the main site but that network is weighted so that it becomes live if centre fails? i.e. If the link into the WAN from the centre site goes down (say 192.168.1.0/24), the backup network (192.168.1.0/24 Same but weighted?) becomes active?? So DR is automated? Or is this not possible?
Any help would be greatfully received.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
At the moment I have:
router bgp 100 < ------- Main Site
no synchronization
bgp log-neighbor-changes
network 195.183.203.0
redistribute static
neighbor 172.16.1.40 remote-as 400 < ----------- Carrier
neighbor 172.16.1.40 ebgp-multihop 255
neighbor 172.16.1.40 update-source Loopback0
neighbor 172.16.1.40 default-originate
no auto-summary
!
router bgp 200 < ------------- DR Site (When Main Fails Network Below becomes active somehow??)
no synchronization
bgp log-neighbor-changes
network 195.183.203.0
redistribute static
neighbor 172.16.1.40 remote-as 400
neighbor 172.16.1.40 ebgp-multihop 255
neighbor 172.16.1.40 update-source Loopback0
neighbor 172.16.1.40 default-originate
no auto-summary
!