ALM-3276800215 A loop is detected on the L2VPN network connected to the interface
Description
LOOPDETECT/4/DetectLoop: OID [OID] The port detected L2VPN loop. (InterfaceIndex=[INTEGER], InterfaceName=[OCTET], VsiName=[OCTET], LoopPeVlan=[OCTET], LoopCeVlan=[OCTET])
The device detected a loop on the L2VPN network connected to its interface.
Attribute
Alarm ID |
Alarm Severity |
Alarm Type |
---|---|---|
3276800215 |
Warning |
environmentalAlarm |
Parameters
Name |
Meaning |
---|---|
OID |
Indicates the MIB object ID of the alarm. |
InterfaceIndex |
Indicates the interface index. |
InterfaceName |
Indicates the interface name. |
VsiName |
Indicates the name of the VSI that is bound to the interface. |
LoopPeVlan |
Indicates the outer ID of the VLAN in which a loop occurs. |
LoopCeVlan |
Indicates the inner ID of the VLAN in which a loop occurs. |
Impact on the System
After the interface is blocked, all the traffic except protocol packets will be blocked.
Possible Causes
Cause 1: Two interfaces on the CE are connected to the same PE, leading to an L2VPN loop.
Cause 2: One interface on the CE is dual homed to the same VPLS network, leading to an L2VPN loop.
Procedure
Find the VSI name and VLAN IDs related to the L2VPN loop according to the alarm information. Check whether the loop occurs on the L2VPN network to which the interface connects. If so, eliminate the loop.
Related Information
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot