03-18-2020 12:02 PM
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
03-18-2020 09:03 PM
Hi,
See fig16 and 17 and also corresponding tables explaining the routing that should be configured.
Hasham
SD-WAN community resource page
https://community.cisco.com/t5/networking-documents/sd-wan-community-resources/ta-p/3745752
03-19-2020 02:28 AM
Hi Dear,
Please find the below some documents for if its help you.
https://www.youtube.com/watch?v=Tc5kxEqaT2o
https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/SD-WAN-End-to-End-Deployment-Guide.pdf
Thanks,
Jitendra
03-20-2020 03:41 PM
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.
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: