Full Mesh Dynamic Auto-Tunnels
Load mpls.te.base.config.with.ospf.cfg
Using the full mesh dynamic auto-tunnel feature, configure CSR4, CSR5, and CSR8 for a full mesh of TE tunnels. Do not use an ACL to specify the tunnel destinations on the routers. They should dynamically learn of the TE tunnel endpoints.
Answer
Explanation
Using auto-tunnel mesh with OSPF is even more scalable than regular auto-tunnel mesh. With “regular” auto-tunnel mesh, we must specify the tunnel destinations using an ACL. This ACL is referenced by the auto-template tunnel destination.
IOS-XE supports doing dynamic discovery of auto-tunnel mesh endpoints using OSPF. XRv does not support this. This feature is also not supported in ISIS. The router advertises a type 4 Opaque-Area LSA (router information) that includes the mesh-group and its loopback IP address. Any other routers that have an auto-template using the mesh-group number as a the tunnel destination build a dynamic tunnel to the specified IP address in the LSA.
For example, we can see R8’s advertised type 4 Opaque-Area LSA which advertises the mesh group (10) and Lo0 address:
This is very similar to BGP auto-discovery of VPN endpoints, for example for VPLS or EVPN.
We can prove that IOS-XR does not support this feature because it cannot decode the TLV in R8’s Router Information Opaque-Area LSA:
CSR4, CSR5, and CSR8 should now have a full mesh of tunnels. We were able to use the exact same config template on all routers, which is extremely scalable from a configuration standpoint. (Although not very scalable in terms of state in the network for a full mesh of TE tunnels). But the drawback is that this is not supported on IOS-XR.
Last updated