S9300 configuration of VPLS direct connecting PC business failure

Publication Date:  2012-11-06 Views:  214 Downloads:  0
Issue Description
Topology:
PC1-----(ACCESS PORT)NE40E---(VPLS)---S9300(ACCESS PORT)-----PC2
NE40E and S9300 side VSI bind on the VLANIF, connect PC through access, vsi state is up, interface state is normal, PC1 and PC2 cannot ping each other.
If add one switch between S9300 and PC2, PC1 and PC2 can ping each other.
PC1-----(ACCESS PORT)NE40E---(VPLS)---S9300(TRUNK PORT)-----(TRUNK PORT)SWITCH(ACCESS PORT)------PC2
Alarm Information
NULL
Handling Process
Modify the configuration that bind VSI on the physic interface, the problem is solved, configuration is as follows:
interface GigabitEthernet6/0/30
undo portswitch
l2 binding vsi test
mpls l2vpn default vlan 1001
Root Cause
Do the packet capturing on PC2, although the interface of S9300 connecting PC2 configured as access interface, but the packet sent from S9300 side have the vlan tag, which caused PC2 discard these packet, business is not interworking. Because of S9300 chip inner process, when it connect to VPLS by VLANIF way, it handle the packet as follows:
1. Inbound accessing packet must take VLAN with itself.
2. The behavior of packet outbound: if the packet take vlan, it replaces to accessing vlan, if there is no vlan in the packet, add one layer vlan outbound interface, and it does not linkage with the access and trunk state of interface.

Suggestions
The topology that S9300 VPLS directly connecting PC, it need to bind the VSI on the physic interface, and configure mpls l2vpn default vlan, it will work normally.

END