Hello there, everyone!
This post is about the UPE PWA traffic loop. Please see more details below.
PHYSICAL NETWORK TOPOLOGY
FAULT DESCRIPTION
A customer deploys a VIP private line service to access a VSI; a VLL is configured on the ATN and a VSI is configured on both CX. After the customer deploys the services, a traffic loop occurs and the port traffic is 100%.
CONFIGURATION FILES
N/A.
TROUBLESHOOTING
Procedure
Step 1. Log in to the ATN 950B (214.99) and run the display current-configuration interface GigabitEthernet0/2/26.1010 command to check the configurations on the ATN 950B (214.99). Ensure that the configurations are correct.
interface
GigabitEthernet0/2/26.1010
vlan-type dot1q 1010
description FTTH_ME_VIC013SRT01
mtu 9000
mpls l2vc 10.137.126.150 322411
mpls l2vc 10.137.126.150 322410 secondary
mpls l2vpn redundancy master
mpls l2vpn reroute delay 120
The
standard solution configuration is as follows:
interface
GigabitEthernet0/4/2.601
mpls l2vc 3.3.3.3 106001 //Configure a PW between the CSG and the master
ASG.
mpls l2vc 3.3.3.3 106101 secondary// Configure a PW between the CSG and
the slave ASG.
mpls l2vpn redundancy master// Configuring PW Redundancy in
Active/Standby Mode
mpls l2vpn reroute delay 500// Set the WTR time for PW switchback.
Step 2. Log in to CX and run the display current-configuration configuration vsi command to check the VSI
configuration. It is found that the VSI configuration is incorrect. Two UPE PWs are configured between ASG1 and ASG2. The
traffic of UPE PW is not isolated. This configuration results in loopback between the PWs between 3.226021 million
and ASG2.
ASG1:
vsi
F_VIC038_VIC033_R01
mac-withdraw enable
pwsignal ldp
vsi-id 322601
peer 10.9.66.7 negotiation-vc-id 322611 ignore-standby-state
peer 10.137.126.150 negotiation-vc-id 322602 upe
peer 10.137.126.152 tnl-policy IPRAN upe ignore-standby-state
peer 10.137.126.151 tnl-policy IPRAN upe ignore-standby-state
peer 10.137.126.164 negotiation-vc-id 322411 ignore-standby-state
peer 10.137.126.150 negotiation-vc-id 322402 upe
mtu 9000
ignore-ac-state
ASG2:
vsi
F_VIC038_VIC033_R01
mac-withdraw enable
pwsignal ldp
vsi-id 322601
peer 10.9.66.7 negotiation-vc-id 322611 ignore-standby-state
peer 10.137.126.153 negotiation-vc-id 322602 upe
peer 10.137.126.152 tnl-policy IPRAN upe ignore-standby-state
peer 10.137.126.151 tnl-policy IPRAN upe ignore-standby-state
peer 10.137.126.164 negotiation-vc-id 322411 ignore-standby-state
peer 10.137.126.153 negotiation-vc-id 322402 upe
mtu 9000
ignore-ac-state
The correct configuration is as follows (can only have one UPE pw between two vsi peer):
vsi
vsi_601 static
pwsignal ldp
vsi-id 601
mac-withdraw enable
upe-npe mac-withdraw enable
peer 3.3.3.3
peer 9.9.9.9
peer 10.10.10.10
peer 1.1.1.1 negotiation-vc-id 106101 ignore-standby-state
ignore-ac-state// Because the VSI is not bound to an AC interface on the SPE,
you need to run the VSI UP command to configure the VSI on the SPE.
ROOT CAUSE
Configuring multiple data records UPE PW. As a result, VSI becomes Ring, resulting in traffic 100%.
