Chapter 6: MPLS Layer 3 VPN Troubleshooting Lab Solutions
This section contains solutions for MPLS Layer 3 VPN Troubleshooting Labs 1, 2, and 3. Note that the directory MPLSL3VPN/LabSolution directory contains working configuration files for all routers for your reference.
Troubleshooting Lab 1 Solution
| 1: | RIP is used as the PE-CE routing protocol between mjlnet_CE1 and Chengdu_PE, but RIP parameters are configured globally, and not under an address family (address-family ipv4 vrf mjlnet_VPN). Reconfigure RIP parameters under the address family on Chengdu_PE. More information about troubleshooting this issue can be found in the section entitled “Routing Protocol Is Configured Globally” on page 516. |
Troubleshooting Lab 2 Solution
| 1: | CEF is disabled on Guangzhou_P. Enable CEF on Guangzhou_P using the ip cef global configuration command. See the section entitled “Verifying CEF” on page 481 for more details on troubleshooting this issue.
Additionally, redistribution of RIP (the PE-CE routing protocol) into MP-BGP is not configured on HongKong_PE. Enter the redistribute rip command under the address family (address-family ipv4 vrf mjlnet_VPN) in router bgp 64512. More information about troubleshooting this issue can be found in the section entitled “Redistribution of Customer Routes into MP-BGP Is Not Successful on the Egress PE Router” on page 518. |
Troubleshooting Lab 3 Solution
| 1: | MPLS is disabled on the interface serial 0/0 on Guangzhou_P (connected to Chengdu_P). MPLS should be enabled on this interface using the mpls ip command. More information on troubleshooting this issue can be found in the section entitled “MPLS Is Disabled on an Interface” on page 485.
Conditional label advertisement is also configured on Chengdu_PE. This is blocking the advertisement of a label binding for prefix 10.1.1.1. In this example, conditional label advertisement can be removed using the no tag-switching advertise-tags for 1 command. See the section entitled “Conditional Label Advertisement Blocks Label Bindings” on page 506. for more details on troubleshooting this issue. |