No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

MPLS L2VPN is not Reachable because of Raw of L2VC is not Configured

Publication Date:  2012-07-27 Views:  58 Downloads:  0
Issue Description
Phenomenon: NE40E can ping 5200G. L2vc is established, but users on L2 switch 1 cannot ping through users on 5200G.
Topology:
loop:1.1.1.9/32                      loop:3.3.3.9/32
   NE40E--NE80E--5200G
          |                                             |
L2 switch 1                         L2 switch 2
(VLAN10 access)       (VLAN20 access)
Alarm Information
Null
Handling Process
When configuring mpls l2vc at sub-interface between NE40E and 5200G, add raw, as follows:
[5200G-GigabitEthernet1/0/0.1] vlan-type dot1q 20
[5200G-GigabitEthernet1/0/0.1] mpls l2vc 1.1.1.9 101 raw
[NE40E-GigabitEthernet1/0/0.1] vlan-type dot1q 10
[NE40E-GigabitEthernet1/0/0.1] mpls l2vc 3.3.3.9 101 raw
Root Cause
1. NE40E can ping through 5200G and L2vc is set up. The intermediate between NE40E and L2 switch 1 is problematic or 5200G and L2 switch 2. Check display mpls l2vc on NE40E. VC Type is vlan attribute. The access of both sides is different vlan, add parameter raw to divide VLAN label after configuring mpls l2vc 1.1.1.9 101. (Note: raw is for dividing VLAN signal.)
Suggestions
Null

END