cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
707
Views
0
Helpful
1
Replies

WAN Redundancy between MPLS & Point to Point Links

venkie_pai
Level 1
Level 1

Hi All,

We have a number of sites in connected via an MPLS network with SP1. We are trying to set up WAN redundancy  and have point to point links via SP2 (which we might ultimately use as primary links down the line, based on performance of the links). For this discussion, I have considered 3 sites, HeadOffice, Branch1 & Branch2. [Please see attached diagram - PS: these are just dummy subnets I've included :) ]

 

HeadOffice: 

Cisco 3850 Stack --> Cisco 3900 routers --> PE 

  • Has 2 links to MPLS cloud (Pri & Backup) which are managed by SP1, and are running BGP between CE & PE. 
  • Has 2 point to point links - to branch1 & branch2
  • Subnets : 10.1.1.0/24 & 192.168.120.0/24

Branch 1:

2 Cisco 3560CX connected via trunk (& running HSRP for some interfaces) --> Cisco 3900 router --> PE

  • Has 1 link to MPLS cloud managed by SP1, and is running BGP between CE & PE. 
  • Has 2 point to point links - to HeadOffice & Branch2
  • Subnets : 10.1.2.0/24 & 192.168.122.0/24

Branch 2:

Cisco 3560CX --> Cisco 3900 router --> PE

  • Has 1 link to MPLS cloud managed by SP1, and is running BGP between CE & PE. 
  • Has 2 point to point links - to HeadOffice & Branch1
  • Subnets : 10.1.3.0/24 & 192.168.124.0/24

 

Currently the primary links will be MPLS and the back-up will be point to point (which as mentioned earlier, we may change later). This is the design we have for failover, but I'm not sure if it will work well. 

Use static routes for the MPLS network and track using IP SLA. Use BGP between Point to Point links as failover.

 

HeadOffice - 3850 Stack config :

ip sla1
icmp-echo 10.1.2.10 source-interface vlan 250
frequency 10
timeout 6000
ip sla schedule 1 start-time now life forever

track 10 ip sla1 reachability 


ip route 10.1.2.0 255.255.255.0 10.1.1.10 track 10
ip route 192.168.122.0 255.255.255.0 10.1.1.10 track 10


router bgp 64550
 bgp log-neighbor-changes
 timers bgp 10 30
 redistribute connected
 redistribute static
 neighbor 172.23.254.2 remote-as 64560

 

Branch 1 - 3560CX config :

ip sla 2
icmp-echo 10.1.1.10 source-interface vlan 250
frequency 10
timeout 6000
ip sla schedule 1 start-time now life forever

track 20 ip sla1 reachability 


ip route 10.1.1.0 255.255.255.0 10.1.2.10 track 20
ip route 192.168.120.0 255.255.255.0 10.1.2.10 track 20


router bgp 64560
 bgp log-neighbor-changes
 timers bgp 10 30
 redistribute connected
 redistribute static
 neighbor 172.23.254.2 remote-as 64550

 

And similarly for routing between Branch 2 and other sites. Will  this work? I am yet to test it out. Does anyone have better suggestions and any config examples which would work better than this? 

Thanks in advance. 

 

 

 

1 Reply 1

trfinkenstadt
Level 1
Level 1

Hello,

 

Are you able to run BGP (or any other routing protocol) with your provider?  If so then you can let BGP manage the routes as you can prepend, weight, local_pref, etc across your point-to-point links all you want.  Also, I would probably do eBGP between your branches instead of iBGP.  

 

best regards,

 

tim

 

Review Cisco Networking for a $25 gift card