Hi there!
In fact, you better create a ticket to support you solve this problem. Currently, we can only provide you with some suggestion.
Under What Conditions Can a VSI Be Up in a VPLS
Network?
In the case that the configurations are correct, VPLS can be up when one of
the following conditions is met:
How to Locate the Cause of the Problem that the Martini or PWE3 VLL Connection Fails to Go Up?
Take the VLL on GE 1/0/0.1 as an example. Perform the following operations:
Check whether the VC IDs, encapsulation types, MTUs, and control words on both ends of a VSI are the same, and whether the VLL or VPLS on both ends are configured in Martini mode.
Solution
If not, set the same parameters on both ends. If the peer is configured with the Martini VPLS, the control word must be Disable.
Check whether the AC interface (GE 1/0/0.1 in this example) bound to a VLL is Up.
Check whether an LDP session is Up.
Solution
If not, run the display mpls ldp session command to check whether the LDP session is in the Operational state. If the LDP session is not in the Operational state, check the public network links and LDP configurations according to FAQs of MPLS LDP.
Check whether the PW has selected a tunnel.
Run the display mpls l2vc vc-id command.
Check the VC tunnel/token info field in the command output. If VC tunnel/token info is displayed as 0 tunnels/tokens, it indicates that no tunnel is selected by a PW.
Check the tunnel policy name field in the command output.
If tunnel policy name is displayed as "-", it indicates that an LDP LSP is used as the tunnel for a PW or no tunnel policy is configured. An MPLS TE tunnel can be used for a PW only after a tunnel policy is configured.
If tunnel policy name is not displayed as "-", it indicates that a tunnel policy is adopted. In this case, you can run the display this command in the tunnel policy view to view the tunnel policy configuration.
[HUAWEI-tunnel-policy-p1] display this
#
tunnel-policy p1
tunnel select-seq cr-lsp load-balance-number 1
#
NOTE:
If the tunnel binding destination dest-ip-address te { tunnel interface-number } command is configured in the tunnel policy view, you also need to run the mpls te reserved-for-binding command on the tunnel interface.
Check whether the remote label exists.
Solution
If the remote label is 0, check the peer device according to the preceding p***edure.
In PWE3 mode, check and ensure that the forwarding status on the local and remote ends is 'forwarding'.
display mpls l2vc interface gigabitethernet 1/0/0.1
*client interface : GigabitEthernet1/0/0.1 is up
session state : up
AC state : up
VC state : up
VC ID : 100
VC type : VLAN
destination : 192.3.3.3
local group ID : 0 remote group ID : 0
local VC label : 21504 remote VC label : 21504
local AC OAM State : up
local PSN State : up
local forwarding state : forwarding
remote AC OAM state : up
remote PSN state : up
remote forwarding state: forwarding
BFD for PW : unavailable
manual fault : not set
active state : active
forwarding entry : exist
link state : up
local VC MTU : 1500 remote VC MTU : 1500
local VCCV : Disable
remote VCCV : Disable
local control word : disable remote control word : disable
tunnel policy : --
traffic behavior : --
PW template name : --
primary or secondary : primary
VC tunnel/token info : 1 tunnels/tokens
NO.0 TNL type : lsp , TNL ID : 0x2002003
create time : 0 days, 0 hours, 7 minutes, 16 seconds
up time : 0 days, 0 hours, 5 minutes, 6 seconds
last change time : 0 days, 0 hours, 5 minutes, 6 seconds