cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
692
Views
0
Helpful
3
Replies

Branch migration configuration

agredanoen
Level 1
Level 1

Hi,

 

Could someone please share some document or link reference for an example about configuring a remote vEdge branch that besides of communicating with other sd-wan sites, be able to:

 

Connect directly to non SD-WAN sites (MPLS sites),  via the MPLS underaly itself, this is, NOT via SD-WAN to DC and then to MPLS?

 

Hope you can help

 

Thanks in advance

 

Best Regards

 

Enrique Agredano

3 Replies 3

HashamM
Cisco Employee
Cisco Employee

Hi,

 

See fig16 and 17 and also corresponding tables explaining the routing that should be configured.

https://www.cisco.com/c/dam/en/us/td/docs/routers/sdwan/migration-guide/cisco-sd-wan-migration-guide.pdf

 

Hasham

SD-WAN community resource page

https://community.cisco.com/t5/networking-documents/sd-wan-community-resources/ta-p/3745752

I would recommend following the Cisco guide of using HUBs for a more controlled rollout.

 

Technically there is another way where you can connect a Back2Back cable between ports in the same vEdge chassis but configured in different VPNs.

 

If you have BGP in VPN0 for the MPLS you can configure eBGP between the ASN in VPN0 to a different ASN in VPN1,  the BGP routes in VPN0 will be "leaked" into the routing table of VPN1,this way you can reach your non-sdwan site directly through the underlay.

 

The AD for the BGP routes would have to be taken into consideration as they have better AD that OMP so i you have more specific BGP routes in VPN 1 they will prevail over OMP what can cause undesired routing.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: