Reset Search
 

 

Article

EOS - Enabling loop protect caused uplink port to stop forwarding traffic

« Go Back

Information

 
TitleEOS - Enabling loop protect caused uplink port to stop forwarding traffic
Symptoms
  • Enabled STP Loop Protect Feature
  • Uplink port was correctly configured as a non-edge port
  • Uplink port was no longer passing traffic
Environment
  • SecureStack
  • All Firmware
Cause
  • Uplink port was connected to a transparent mesh network that had multiple source BPDU packets.
  • This shared media port created a conflict with Multisource Detection and caused the port to go into a listening/discarding state.
Resolution
  • Loop Protect is not supported on shared media ports
Additional notes
Multisource Detection, which is always enabled, will recognize the multiple source MAC addresses and set the port’s operational point-to-point status to false, treating the port as a shared media device.
The port is constantly monitored. If the situation is resolved, as determined by receiving a unique address for a sufficient amount of time, the port’s operational point-to-point status will revert to true.

When loop protect is configured for the port, if multisource detection is triggered, the port will go to the listening state and no longer be part of the active topology. Loop protect does not operate on shared media ports.

 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255