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

Modify configuration to let VPLS clients can visit each other with different VLAN Tag

Publication Date:  2014-08-29 Views:  113 Downloads:  0
Issue Description
Clients which connected to different CPEs can't visit each other if they belong to different VLANs, and even they belong to the same VSI on PW.

The topology is as following , OKE-S93 is PW 1 and GAUS-S93 is PW 2. we can find that CPE-1/PC/CPE-2 all belong to one VSI "RADIO-PRIME-HALDEN".  But we found that CPE-1 can visit PC but can't visit CPE-2.
.
Alarm Information
Null
Handling Process
And finally, I found a solution to solve this issue,  I modified the configuration as following,

interface GigabitEthernet X/X/XX.X
vlan-mapping vlan 1153 map-vlan 1000
l2 binding vsi RADIO-PRIME-HALDEN# 

interface GigabitEthernet 2/0/7.14
vlan-mapping vlan 1173 map-vlan 1111
l2 binding vsi RADIO-PRIME-HALDEN#

interface GigabitEthernet 2/0/7.4
vlan-mapping vlan 1153 map-vlan 2222
l2 binding vsi RADIO-PRIME-HALDEN#

And the process should be changed like this, 
A. when the packets from CPE-1 to PW OKE-S93 and enter from interface gX/X/X.X, the encapsulation of VPLS
would keep the original VLAN tag and add another outer tag as 1000 then add  MPLS header .
B. And when the packets arrived PW GAUS-S93 and go out through interface g2/0/7.14, the encapsulation of VPLS would remove MPLS header and the outer vlan tag 1000 and then replace the inner VLAN tag as 1173 which configured under the local sub-interface.

In this case, the packets from CPE-1 would change the vlan tag as 1173 which is the same with CPE-2,  and they can visit each other now.
Root Cause
1. As the topology above, we tried to capture the packets and found that the VLAN tag didn't change  and still keep as 1153  when packets from CPE-1 arrived PW GAUS-S93 and out from the interface 2/0/7.14.  And the packets would not  reach  CPE-2 because CPE-2 has a vlan tag as 1173,

2. The process is like this ,
 A. when the packets from CPE-1 to PW OKE-S93 and enter from interface gX/X/X.X, the encapsulation of VPLS
 would keep the original VLAN tag and add MPLS header directly, even if there are temination configuration under this sub-interface.
B. And when the packets arrived PW GAUS-S93 and go out through interface g2/0/7.14, the encapsulation of VPLS would remove MPLS header and keep the original VLAN tag as 1153 and forward directly.
Suggestions
For VPLS, the encapsulation of MPLS and changing for VLAN tag is totally different with the normal interfaces.  We should pay more attention to this and different kinds of interfaces has different performance when binding VSI.

END