Trying to wrap my head about the following Viptela scenario

Hey guys,

I am not that savvy on Service Provider stuff, and I'm trying to study a little bit of Viptela (Cisco SD-WAN) using their documentation. The question is not really on the product itself but in the way private WAN's work, because the following section on " Allow Data Traffic Exchange across Private WANs" is throwing me off:

https://sdwan-docs.cisco.com/Product_Documentation/Software_Features/Release_18.1/04Segmentation/03Segmentation_(VPN)_Configuration_Examples

If I understand correctly, a data tunnel cannot be formed between two edge routers on the same private transport (MPLS, for example) IF THE NETWORK SEGMENT that connects the two routers to the transport is NOT advertised over the Service Provider network. This makes sense to me because if the two subnets are not advertised, both routers are not able to reach each other, fine.

The solution, however, as per the document, is to use a loopback interface instead? It reads:

" Because the loopback interfaces are advertised across the overlay network, the vEdge routers are able to learn reachability information, and they can exchange data traffic over the private network. "

But why does the loopback get advertised when the physical interface did not? The article doesn't explain well why by using a loopback, both routers are now able to reach each other's said loopbacks, and it does not mention those loopbacks being advertised through the MPLS network.

Am I missing something here?

Posted Aug 4, 2020, 3:58 AM UTC

88
JL421•

When you are peering with the service provider in MPLS, the SP is generally already aware of all addressing within their end of the network, including the handoff they gave you. They normally don't need you to advertise your physical interface since they are already routing to that subnet on their end.

1
bugxterOP•

Okay, but if that's true then there should be connectivity between the two CE's from the start no?

Also, how could there possibly be connectivity between the two loopbacks if they are not advertised through the MPLS cloud? Or does the article imply that the loopbacks belong to the same "handoff" network and as such it's also known by the MPLS network?

Sorry if I'm getting things terribly wrong, the WAN is such a wild beast to me.

1
JL421•

Yes, but maybe no. It's rare, but MPLS can peer over other routing protocols like OSPF or EIGRP. In those scenarios, where peering is dynamically formed your physical address could be transient. Again that's an edge case, but still a possibility.

By advertising a Loopback into the provider cloud that ensures that no matter what topology changes they make on their end, up to and including changing the peering addresses, your Loopback is always reachable.

Similar concept to managing your gear from a Loopback address instead of an SVI. The physical network is always subject to change (SVI goes down (I know technically still logical, but you get what I mean)) but the logical address is always accessible as long as one feasible route exists.

1
bugxterOP•

Okay so you are agreeing that communication between the two loopbacks require those same loopbacks to be advertised somehow through the MPLS network?

1
LarrBearLVCCNP•

Sounds like what it is saying is that with MPLS you are peered to the provider at each end and not with your remote site edge IP. Whereas using a loopback that is advertised through the providers network to peer to, makes it seem like you are directly peered to the remote side. So tunnel is peered through the provider peering. This is only if the provider is not advertising your physical interface IPs through its network. Our MPLS provider does advertise these. Not sure about others.

1
bugxterOP•

Thanks for the answer.

> Whereas using a loopback that is advertised through the providers network to peer to, makes it seem like you are directly peered to the remote side.

This is what confuses me however; the problematic scenario implies that the network segment between the CE and the PE *are not* advertised through the MPLS network, but then the solution implies using the Loopbacks instead... but those need to be advertised as well in order for the tunnel to work, right? So why would those loopbacks be advertised when the actual, physical subnet between the CE and the PE did not get advertised?

1
LarrBearLVCCNP•

Because the MPLS provider doesn't advertise it. It's just a scenario with a solution.

1
abhi923•

Loopback always remains UP. Whereas physical interfaces could go down.

1