Advanced LDP
Last updated
Last updated
In this lab, you will configure more advanced LDP features. IP addressing, OSPF, and LDP are already pre-configured.
If the R1-R3 link goes down, R1 should retain the label bindings learned from R3. Find three ways to achieve this.
When R1’s Gi2 interface goes down, it should retain label bindings from neighbor R3 (3.3.3.3)
Additionally, configure the topology so that R4’s cost to 3.3.3.3/32 is 65536. You can make any change except for directly configuring the interface metrics. R4’s OSPF metrics and R3’s OSPF metrics should appear as below:
Repeat the exercise for the XR topology.
Method 1, use LDP session protection on R1, and accept targeted hellos on R3.
Method 2, use a manually configured targeted LDP session to R3. On R3, also form a targeted session to R1 or accept targeted hellos.
Method 3, create an xconnect between R1 and R3 which will automatically form a targeted LDP neighborship.
The simplest way to do this is go under an unused interface, no shut, and configure xconnect under the interface.
Use LDP/IGP sync on R4, and bring down the LDP neighborship between R3-R4. You can do this by setting a password on one side or perhaps using an inbound ACL denying port 646 traffic.
