R2511-HP MSR Router Series MPLS Configuration Guide(V5)

103
[PE2-ospf-1] quit
# Configure a VC on Ethernet 1/2.2 (the interface connected to PE 3), and specify the VC
encapsulation type as Ethernet.
[PE2] interface Ethernet1/2.2
[PE2-Ethernet1/2.2] mpls l2vc 192.2.2.2 101 ethernet
# Configure Ethernet 1/2.2 to terminate VLAN-tagged packets with VLAN ID 2.
[PE2-Ethernet1/2.2] vlan-type dot1q vid 2
[PE2-Ethernet1/2.2] quit
3. Configure PE 3:
# Configure Ethernet 1/1 as a trunk port, and allow all VLANs to pass through the port.
<Sysname> system-view
[Sysname] sysname PE3
[PE3] interface ethernet 1/1
[PE3-Ethernet1/1] port link-type trunk
[PE3-Ethernet1/1] port trunk permit vlan all
[PE3-Ethernet1/1] quit
# Configure Ethernet 1/2 as an access port, and assign the port to VLAN 2.
[PE3] vlan 2
[PE3-vlan2] quit
[PE3] interface ethernet 1/2
[PE3-Ethernet1/2] port access vlan 2
# Disable STP on Ethernet 1/2, and enable BPDU tunneling for STP on the port.
[PE3-Ethernet1/2] undo stp enable
[PE3-Ethernet1/2] bpdu-tunnel dot1q stp
[PE3-Ethernet1/2] quit
# Configure the destination multicast MAC address for BPDUs as 0x0100-0CCD-CDD0.
[PE3] bpdu-tunnel tunnel-dmac 0100-0ccd-cdd0
Verifying the configuration
# Verify that CE 1 and CE 2 can ping each other. (Details not shown.)
# Verify that a spanning tree has been calculated based on the two customer networks on CE 1 and CE
2.
Troubleshooting MPLS L2VPN
This section describes troubleshooting techniques for MPLS L2VPN.
Symptom 1
After the L2VPN configuration, the peer PEs cannot ping each other. The display mpls l2vc command
output shows that the VC is down and the remote VC label is invalid (displayed as --).
Analysis
The reason the VC is down might be that the PEs are configured with different encapsulation types.
Solution
1. Verify that the local PE and the peer PE are configured with the same encapsulation type.
2. Verify that each PE has a remote peer configured.