Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-VPLS Troubleshooting Guide | 146.97 KB |
Troubleshooting MPLS
Troubleshooting VPLS
Only the VSI on one PE device on the two ends of a PW is in up state
Symptom
Only the VSI on one PE device on the two ends of a PW is in up state.
Common causes
A VSI is up when at least one PW and one AC is up or at least two ACs are up in the VSI.
The common causes of this type of issue are:
· On an up VSI on a PE, PWs are down but two up ACs exist.
· On a down VSI, PWs are down and no AC or only one AC is up.
Solution
To resolve the issue:
1. Execute the display l2vpn vsi command to check the state of the ACs and PWs on a VSI.
<Sysname> display l2vpn vsi verbose
VSI Name: vpls1
VSI Index : 0
VSI Description : vsi for vpls1
VSI State : Down
MTU : 1500
Bandwidth : -
Broadcast Restrain : -
Multicast Restrain : -
Unknown Unicast Restrain: -
MAC Learning : Enabled
MAC Table Limit : -
MAC Learning rate : -
Drop Unknown : -
PW Redundancy : Master
Flooding : Enabled
Statistics : Disabled
VXLAN ID : -
LDP PWs:
Peer PW ID Link ID State
192.3.3.3 1 8 Down
ACs:
AC Link ID State Type
GE2/0/3 srv1 1 Up Manual
2. Execute the display l2vpn pw verbose command to identify the reason why the PW is down.
<Sysname> display l2vpn pw verbose
VSI Name: aaa
Peer: 2.2.2.9 Remote Site: 2
Signaling Protocol : BGP
Link ID : 9 PW State : Down
In Label : 1420 Out Label: 1419
MTU : 1500
PW Attributes : Main
VCCV CC : -
VCCV BFD : -
Flow Label : Send
Control Word : Disabled
Tunnel Group ID : 0x800000960000000
Tunnel NHLFE IDs : 1038
Admin PW : -
E-Tree Mode : -
E-Tree Role : root
Root VLAN : -
Leaf VLAN : -
Down Reasons : Control word not match
The common causes of this type of issue are as follows:
¡ BFD session for PW down—The BFD session for PW detection is down. To resolve this issue, execute the display bfd session command to display BFD session information. Check and edit BFD configuration or check the physical link for link failure or link quality issues.
¡ BGP RD was deleted—The BGP RD has been deleted. To resolve this issue, execute the route-distinguisher route-distinguisher command in auto-discovery VSI view.
¡ BGP RD was empty—No BGP RD is configured. To resolve this issue, execute the route-distinguisher route-distinguisher command in auto-discovery VSI view.
¡ Control word not match—The control word configuration on the two ends of the PW is inconsistent. To resolve this issue, execute the control-word enable command to enable the control word feature on both ends.
¡ Encapsulation not match—The encapsulation types on the two ends of the PW are inconsistent. To resolve this issue, execute the pw-type command to configure the same encapsulation type for the two ends.
¡ LDP interface parameter not match—The LDP negotiation parameters on the two ends of the PW are inconsistent. To resolve this issue, execute the vccv cc command to specify the same VCCV control channel (CC) type. Alternatively, specify the same CEM class for the CEM interfaces on both ends of the PW.
¡ Non-existent remote LDP PW—The remote device has deleted the LDP PW. To resolve this issue, reconfigure the PW on the remote device.
¡ Local AC Down—The local AC is down. To resolve this issue, check and edit the configuration on the AC interface or troubleshoot the issue on the interface where the AC is located and make sure the interface is in up state.
¡ Local AC was non-existent—No local AC is configured. To resolve this issue, configure a local AC and associate it with a VSI.
¡ MTU not match—The MTU configuration on the two ends of the PW is inconsistent. To resolve this issue, configure the same MTU at both ends of the PW or use the mtu-negotiate disable command to disable MTU negotiation.
¡ Remote AC Down—The remote AC is down. To resolve this issue, check and edit the configuration on the remote AC interface or troubleshoot the issue on the interface where the AC is located and make sure the interface is in up state.
3. If the issue persists, collect the following information and contact Technical Support:
¡ Results of each step.
¡ The configuration file, log messages, and alarm messages.
Related alarm and log messages
Alarm messages
N/A
Log messages
· L2VPN/2/L2VPN_PWSTATE_CHANGE
· L2VPN/4/L2VPN_BGPVC_CONFLICT_LOCAL
· L2VPN/4/L2VPN_BGPVC_CONFLICT_REMOTE
· L2VPN/4/L2VPN_HARD_RESOURCE_NOENOUGH
· L2VPN/2/L2VPN_HARD_RESOURCE_RESTORE
· L2VPN/4/L2VPN_LABEL_DUPLICATE
VPLS traffic failed to be forwarded
Symptom
VPLS traffic failed to be forwarded.
Common causes
The following are the common causes of this type of issue:
· The AC is not up.
· The PW is not up.
· The PW did not generate forwarding information.
· No public tunnels are available for the PW.
· The public tunnel for the PW is abnormal.
Troubleshooting flowchart
Figure 1 shows the troubleshooting flowchart.
Figure 1 Flowchart for troubleshooting VPLS traffic forwarding failure
Solution
To resolve the issue:
1. Execute the display l2vpn vsi command to check the status and quantity of the AC and PW associated with a VSI.
<Sysname> display l2vpn vsi verbose
VSI Name: vpls1
VSI Index : 0
VSI Description : vsi for vpls1
VSI State : Up
MTU : 1500
Bandwidth : -
Broadcast Restrain : -
Multicast Restrain : -
Unknown Unicast Restrain: -
MAC Learning : Enabled
MAC Table Limit : -
MAC Learning rate : -
Drop Unknown : -
PW Redundancy : Master
Flooding : Enabled
Statistics : Disabled
VXLAN ID : -
LDP PWs:
Peer PW ID Link ID State
192.3.3.3 1 8 Down
ACs:
AC Link ID State Type
GE2/0/3 srv1 1 Up Manual
2. If the state of the AC is down, verify that the AC configuration is correct and the interface where the AC is located is up. If the AC configuration is incorrect or the interface where the AC is located is down, edit the AC configuration or troubleshoot the interface failure.
3. If the PW is down, execute the display l2vpn pw verbose command to check the reason why the PW is down.
<Sysname> display l2vpn pw verbose
VSI Name: aaa
Peer: 2.2.2.9 Remote Site: 2
Signaling Protocol : BGP
Link ID : 9 PW State : Down
In Label : 1420 Out Label: 1419
MTU : 1500
PW Attributes : Main
VCCV CC : -
VCCV BFD : -
Flow Label : Send
Control Word : Disabled
Tunnel Group ID : 0x800000960000000
Tunnel NHLFE IDs : 1038
Admin PW : -
E-Tree Mode : -
E-Tree Role : root
Root VLAN : -
Leaf VLAN : -
Down Reasons : Control word not match
The common causes of this type of issue are as follows:
¡ BFD session for PW down—The BFD session for PW detection is down. To resolve this issue, execute the display bfd session command to display BFD session information. Check and edit BFD configuration or check the physical link for link failure or link quality issues.
¡ BGP RD was deleted—The BGP RD has been deleted. To resolve this issue, execute the route-distinguisher route-distinguisher command in auto-discovery VSI view.
¡ BGP RD was empty—No BGP RD is configured. To resolve this issue, execute the route-distinguisher route-distinguisher command in auto-discovery VSI view.
¡ Control word not match—The control word configuration on the two ends of the PW is inconsistent. To resolve this issue, execute the control-word enable command to enable the control word feature on both ends.
¡ Encapsulation not match—The encapsulation types on the two ends of the PW are inconsistent. Execute the pw-type command to configure the same encapsulation type for the two ends.
¡ LDP interface parameter not match—The LDP negotiation parameters on the two ends of the PW are inconsistent. To resolve this issue, execute the vccv cc command to specify the same VCCV control channel (CC) type. Alternatively, specify the same CEM class for the CEM interfaces on both ends of the PW.
¡ Non-existent remote LDP PW—The remote device has deleted the LDP PW. To resolve the issue, reconfigure the LDP PW on the remote device.
¡ Local AC Down—The local AC is down. To resolve this issue, check and edit the configuration on the AC interface or troubleshoot the issue on the interface where the AC is located and make sure the interface is in up state.
¡ Local AC was non-existent—No local AC is configured. To resolve this issue, configure a local AC and associate it with a VSI.
¡ Remote AC Down—The remote AC is down. To resolve this issue, check and edit the configuration on the remote AC interface or troubleshoot the issue on the interface where the AC is located and make sure the interface is in up state.
4. If both the AC and PW are up, execute the display l2vpn forwarding pw verbose command to identify whether PW forwarding information exists. If the information exists, the Tunnel NHLFE IDs field displays the NHLFE IDs of the public tunnels that carry the PW.
¡ If PW forwarding information exists, go to step 6.
¡ If no PW forwarding information exists, go to step 5.
<Sysname> display l2vpn forwarding pw verbose
VSI Name: aaa
Link ID: 8
PW Type : VLAN PW State : Up
In Label : 1272 Out Label: 1275
MTU : 1500
PW Attributes : Main
VCCV CC : Router-Alert
VCCV BFD : Fault Detection with BFD
Flow Label : Send
Tunnel Group ID : 0x960000000
Tunnel NHLFE IDs: 1034
MAC limit : maximum=2000 alarm=enabled action=discard
5. Execute the display mpls lsp command to check for the tunnel that carries the PW. The tunnel is an LSP with the FEC as the PW peer IP address. If it does not exist, establish the tunnel that carries the PW.
<Sysname> display mpls lsp
FEC Proto In/Out Label Out Inter/NHLFE/LSINDEX
100.100.100.100/24 LDP -/1049 GE2/0/1
6. If the issue persists, collect the following information and contact Technical Support:
¡ Results of each step.
¡ The configuration file, log messages, and alarm messages.
¡ Use the display diagnostic-information command to collect diagnostic information.
Related alarm and log messages
Alarm messages
N/A
Log messages
· L2VPN/2/L2VPN_PWSTATE_CHANGE
· L2VPN/4/L2VPN_BGPVC_CONFLICT_LOCAL
· L2VPN/4/L2VPN_BGPVC_CONFLICT_REMOTE
· L2VPN/4/L2VPN_HARD_RESOURCE_NOENOUGH
· L2VPN/2/L2VPN_HARD_RESOURCE_RESTORE
· L2VPN/4/L2VPN_LABEL_DUPLICATE
A PW in up state failed to forward packets between two PEs
Symptom
When a PW is in up state, it failed to forward packets between two PEs.
Common causes
The following are the common causes of this type of issue:
· The number of MAC addresses that a PW learned reached the upper limit, and the PW is configured to drop frames with unknown source MAC addresses when the maximum is reached.
· PW information has not been deployed to the forwarding module.
Troubleshooting flowchart
Figure 2 shows the troubleshooting flowchart.
Solution
To resolve the issue:
1. Execute the display l2vpn mac-address command to identify whether corresponding MAC address entries exist and the total number of learned MAC address entries. You can specify an AC interface or PW to display the total number of MAC address entries learned from that AC interface or PW.
¡ Display MAC address table information for VSIs.
<Sysname> display l2vpn mac-address
* - The output interface is issued to another VSI
MAC Address State VSI Name Link ID/Name Aging
0000-0000-000a Dynamic vpn1 GE2/0/1 Aging
0000-0000-0009 Dynamic vpn1 GE2/0/1 Aging
--- 2 mac address(es) found ---
¡ Display the number of MAC address entries.
<Sysname> display l2vpn mac-address count
2 mac address(es) found
2. Check for the maximum number of MAC addresses allowed to be learned, and the action to be taken on frames with unknown source MAC addresses when the PW has learned the maximum number of MAC addresses.
¡ Execute the display this command in VSI view to identify whether the mac-table limit and mac-table limit drop-unknown commands are configured for the VSI. If these commands are configured and the number of learned MAC addresses has reached the upper limit, increase the maximum number of MAC addresses that the VSI can learn or delete the mac-table limit drop-unknown command.
¡ Execute the display this command in AC view and PW view to check for the mac-limit command are configured for the VSI. If this command is configured and the number of learned MAC addresses has reached the upper limit, increase the maximum number of MAC addresses that can be learned or delete the action discard option.
3. Execute the display l2vpn forwarding pw verbose command to identify whether PW forwarding information exists. If the information exists, the Tunnel NHLFE IDs field displays the NHLFE IDs of the public tunnels that carry the PW.
¡ If forwarding information exists, go to step 5.
¡ If no forwarding information exists, go to step 4.
<Sysname> display l2vpn forwarding pw verbose
VSI Name: aaa
Link ID: 8
PW Type : VLAN PW State : Up
In Label : 1272 Out Label: 1275
MTU : 1500
PW Attributes : Main
VCCV CC : Router-Alert
VCCV BFD : Fault Detection with BFD
Flow Label : Send
Tunnel Group ID : 0x960000000
Tunnel NHLFE IDs: 1034
MAC limit : maximum=2000 alarm=enabled action=discard
4. Execute the display mpls lsp command to check for the tunnel that carries the PW. The tunnel is an LSP with the FEC as the PW peer IP address. If it does not exist, establish the tunnel that carries the PW.
<Sysname> display mpls lsp
FEC Proto In/Out Label Out Inter/NHLFE/LSINDEX
100.100.100.100/24 LDP -/1049 GE2/0/1
5. If the issue persists, collect the following information and contact Technical Support:
¡ Results of each step.
¡ The configuration file, log messages, and alarm messages.
¡ Use the display diagnostic-information command to collect diagnostic information.
Related alarm and log messages
Alarm messages
N/A
Log messages
· L2VPN/4/L2VPN_MACLIMIT_MAX_AC
· L2VPN/4/L2VPN_MACLIMIT_MAX_PW
· L2VPN/4/L2VPN_MACLIMIT_MAX_VSI
An LDP PW cannot become up
Symptom
In a VPLS network, an LDP PW cannot become up.
Common causes
The following are the common causes of this type of issue:
· The encapsulation types at both ends of the PW are inconsistent.
· The MTU values at both ends of PW are inconsistent.
· The LDP session state is not Up.
· No public tunnels are available for the PW.
· The AC interface is not up.
Solution
To resolve the issue:
1. Use the display l2vpn pw verbose command to check for the peer IP address of the PW and the reason why the PW is down.
<Sysname> display l2vpn pw verbose
VSI Name: aaa
Peer: 2.2.2.9 VPLS ID: 100:100
Signaling Protocol : LDP
Link ID : 8 PW State : Down
In Label : 1553 Out Label: 1553
MTU : 1500
PW Attributes : Main
VCCV CC : -
VCCV BFD : -
Flow Label : -
Tunnel Group ID : 0x800000960000000
Tunnel NHLFE IDs : 1038
Admin PW : -
E-Tree Mode : -
E-Tree Role : root
Root VLAN : -
Leaf VLAN : -
Down Reasons : Control word not match
Table 1 shows the common causes of this type of issue.
Table 1 Common causes and solutions
|
Down Reasons |
Symptom |
Solution |
|
BFD session for PW down |
The BFD session for PW detection is down. |
Execute the display bfd session command to display BFD session information. Check and edit BFD configuration or check the physical link for link failure or link quality issues. |
|
Control word not match |
The control word configuration on the two ends of the PW is inconsistent. |
Execute the control-word enable command to enable the control word feature on both ends. |
|
Encapsulation not match |
The encapsulation types on the two ends of the PW are inconsistent. |
Execute the pw-type command to configure the same encapsulation type for the two ends. |
|
LDP interface parameter not match |
The LDP negotiation parameters on the two ends of the PW are inconsistent. |
Execute the vccv cc command to specify the same VCCV control channel (CC) type or specify the same CEM class for the CEM interfaces on both ends of the PW. |
|
Non-existent remote LDP PW |
The remote device has deleted the LDP PW. |
Reconfigure the PW on the remote device. |
|
Local AC Down |
The local AC is down. |
Check and edit the configuration on the AC interface or troubleshoot the issue on the interface where the AC is located and make sure the interface is in up state. |
|
Local AC was non-existent |
No local AC is configured. |
Configure a local AC and associate it with a VSI. |
|
Remote AC Down |
The remote AC is down. |
Check and edit the configuration on the remote AC interface or troubleshoot the issue on the interface where the AC is located and make sure the interface is in up state. |
|
Label not allocated |
No label is allocated. |
Contact Technical Support. |
|
Local VSI Down |
The local VSI is down. |
See "Only the VSI on one PE device on the two ends of a PW is in up state." |
|
Local and remote LDP PWs have different AII |
The local SAII and remote TAII are different. |
See "LDP session down" in LDP Troubleshooting Guide. |
|
Local LDP PW was not sent mapping message |
The local end did not send the LDP mapping message. |
See "LDP session down" in LDP Troubleshooting Guide. |
|
Local LDP PW Virtual Nexthop defect |
The local LDP PW has virtual next hop defects. |
See steps 2 and 3. |
|
Remote LDP PW Virtual Nexthop defect |
The remote LDP PW has virtual next hop defects. |
See steps 2 and 3. |
|
Tunnel Down |
The tunnel that carries the PW is down. |
See step 3. |
2. Execute the display l2vpn forwarding pw verbose command to identify whether PW forwarding information exists. If the information exists, the Tunnel NHLFE IDs field displays the NHLFE IDs of the public tunnels that carry the PW.
¡ If forwarding information exists, go to step 4.
¡ If no forwarding information exists, go to step 3.
<Sysname> display l2vpn forwarding pw verbose
VSI Name: aaa
Link ID: 8
PW Type : VLAN PW State : Up
In Label : 1272 Out Label: 1275
MTU : 1500
PW Attributes : Main
VCCV CC : Router-Alert
VCCV BFD : Fault Detection with BFD
Flow Label : Send
Tunnel Group ID : 0x960000000
Tunnel NHLFE IDs: 1034
MAC limit : maximum=2000 alarm=enabled action=discard
3. Execute the display mpls lsp command to check for the tunnel that carries the PW. The tunnel is an LSP with the FEC as the PW peer IP address as described in step 1. If it does not exist, establish the tunnel that carries the PW. If not, create a tunnel for carrying the PW. Supported public tunnel types include LSP, MPLS TE, and GRE tunnels. For how to create LSP, MPLS TE, and GRE public tunnels, see "Configuring a static LSP" and "Configuring LDP," "Configuring MPLS-TE" in MPLS Configuration Guide, and "Configuring GRE" in Layer 3—IP Services Configuring Guide, respectively.
<Sysname> display mpls lsp
FEC Proto In/Out Label Out Inter/NHLFE/LSINDEX
100.100.100.100/24 LDP -/1049 GE2/0/1
4. If the issue persists, collect the following information and contact Technical Support:
¡ Results of each step.
¡ The configuration file, log messages, and alarm messages.
¡ Use the display diagnostic-information command to collect diagnostic information.
Related alarm and log messages
Alarm messages
N/A
Log messages
N/A
A VSI cannot become up when VPLS uses LDP
Symptom
A VSI cannot become up when VPLS uses LDP
Common causes
The VSI is in the Up state if any of the following conditions are met:
· Under VSI, there is at least one PW Up and one AC Up.
· In the VSI, at least two ACs are up.
· In VSI, there are at least two PW Up (multi-section PW networking).
The following are the common causes of this type of issue:
· The total number of ACs and Pws in up state in a VSI is less than 2.
· The shutdown command was executed in the VSI.
Solution
To resolve the issue:
1. Execute the display this command in VSI view to check for the shutdown command.
¡ If shutdown command is configured, execute the undo shutdown command.
¡ If the shutdown command is not configured, go to the next step.
2. Execute the display l2vpn vsi command to check the status and quantity of the AC and PW associated with the VSI.
<Sysname> display l2vpn vsi verbose
VSI Name: vpls1
VSI Index : 0
VSI Description : vsi for vpls1
VSI State : Up
MTU : 1500
Bandwidth : -
Broadcast Restrain : -
Multicast Restrain : -
Unknown Unicast Restrain: -
MAC Learning : Enabled
MAC Table Limit : -
MAC Learning rate : -
Drop Unknown : -
PW Redundancy : Master
Flooding : Enabled
Statistics : Disabled
VXLAN ID : -
LDP PWs:
Peer PW ID Link ID State
192.3.3.3 1 8 Down
ACs:
AC Link ID State Type
GE2/0/3 srv1 1 Up Manual
¡ If the sum of ACs and PWs associated with the VSI is less than 2, create ACs and PWs first.
¡ If the state of the AC is down, verify that the AC configuration is correct and the interface where the AC is located is up. If the AC configuration is incorrect or the interface where the AC is located is down, edit the AC configuration or troubleshoot the interface failure.
¡ If the state of the PW is down, see "An LDP PW cannot become up" to troubleshoot the issue.
3. If the issue persists, collect the following information and contact Technical Support:
¡ Results of each step.
¡ The configuration file, log messages, and alarm messages.
Related alarm and log messages
Alarm messages
N/A
Log messages
N/A
