3Com 8807 Configuration Manual page 651

Expansion session is abnormal: verify that the commands used to configure the
■
expansion session are executed on both ends, and the configurations are all
right.
The interface of the private VLAN is not bound with the corresponding VPLS
■
instance, or is DOWN: make sure the interface is UP, or the PW to the UPE is UP.
The parameters for the peer or the MTU value of the VPLS instance is
■
inconsistent: verify that the MTU value configured for the VPLS instance is
consistent on both end, and the VC-ID and transmission mode for the peer is
also consistent.
The VPLS service processor card is not in Normal state: make sure that VPLS
■
service processor card is in Normal state.
Symptom 2: Packets cannot be forwarded.
Solution:
The service processor card is not in place: use the display device command to
■
verify that the service processor card is in Normal state.
The service processor card version is inconsistent with the SRP version: verify
■
the service processor card version.
The flow template and redirection are not correctly configured on the public
■
side: verify the port for the public network is correctly configured.
Symptom 3: Packets get lost during the course of forwarding
Solution:
Traffic exceeds VPN bandwidth restriction: Increase the VPN bandwidth.
■
Broadcast/multicast/unicast traffic exceeds the bandwidth set by broadcast
suppression ratio: Modify the broadcast suppression ratio and verify by checking
the broadcast suppression of the VPN and the broadcast traffic within the VPN.
Troubleshooting VPLS 651