How to check that VPLS tunnel connection cannot be built?
The steps of VPLS troubleshooting are as follows:
1. Check LSP on PE with display mpls lsp command. If command line is vacant or LSP has no mapping of network route of opposite PE, it indicates that LSP has not been built or label mapping is problematic. It is related with software protocol or configuration.
2. If there is no LSP of opposite PE on PE, check configuration of MPLS with dis c c mpls command. MPSL must enable under global view and configure Lsr-id, otherwise LSP cannot be built. If basic configuration is correct, read the following step.
3. Check whether the interface enables MPLS and MPLS LDP or not. Change command view as interface view and check MPLS enable with display this command. If the interface does not enable MPLS and MPLS LDP, LSP cannot be built. If MPLS enables, read the fourth step.
4. Check whether there is route information of opposite PE in routing tabel or not. Use dis ip routing-table command. If routing information of opposite PE does not exist, it indicates that IP route is problematic.
5. Check VSI state and VPN label distribution on PE. If VSI is down, it indicates that signaling protocol of VPLS fails to negotiate. There are many reasons. e.g. IP route problem, MPLS forwarding problem and the mismatch of PE1 and PE1 link encapsulation. Check the reason of VSI down with display vsi <VSI-Name> verbose debugging command.
6. If it is still problmatic, check the state of port connecting CE and PE (sub-interface/Vlanif) and the configuration. The access port must be UP and configure l2 binding vsi <VSI-NAME>.