In the Segment Routing vs LDP in Hub-and-Spoke Networks blog post I explained why you could get into interesting scaling issues when running MPLS with LDP in a large hub-and-spoke network, and how you can use Segment Routing (MPLS edition) to simplify your design.
Now imagine you’d like to offer VPLS services between hubs and spokes, and happen to be using equipment that uses targeted LDP sessions to signal pseudowires. Guess what happens next…
Even though the network was supposed to be using Segment Routing to propagate labels for loopback interfaces, a label will be assigned to every applicable prefix in the IP forwarding table1 the moment the LDP process is started, and all those labels will be advertised to every LDP peer (whoever you configured targeted LDP sessions with). In our case (assuming Cisco IOS/XE deployment), the hub routers yet again receive label assignments for every prefix in the global routing table.
You can use the tricks described in the previous blog post to limit the label allocation or advertisement, but if you happen to be using IOS XR there’s another nerd knob to tweak: with mpls ldp capabilities sac configuration command you can disable IPv4 and/or IPv6 label bindings. I couldn’t find a similar configuration command for IOS XE, a pointer to relevant documentation would be appreciated.
It Gets Worse
Jeff Tantsura pointed out a particularly nasty implementation detail in a LinkedIn comment:
If you run older software of a particular vendor, it won’t resolve tLDP over SR LSPs and requires full LDP configuration, with as consequence - LDP to SR mapping and SRMS deployment. Talk to your vendor before deployment.
- Added tLDP-over-SR implementation gotcha