Print | Rate this content

HP ProCurve Managed Switch -- Loop Protection vs. Spanning Tree Protocol

AskProCurve Article


HP ProCurve Managed Switch -- Loop Protection vs. Spanning Tree Protocol

Available Part Numbers:


Issue Description:

Is Loop Protection different than Spanning Tree? Can I use Loop Protection to prevent loops but without causing any computing issues among the switches or ports? Any pros or cons?


Loop Protection can be used independently of Spanning Tree Protocol and is targeted for use on ports to which unmanaged devices are connected. Unmanaged devices will typically drop Spanning Tree BPDUs. Loop Protection serves by transmitting loop protocol packets outward from the ports on which it is enabled. Should a switch receive a loop-protocol packet back on a port for which you have set the action to “send-disable,” then the port will be shut down.

You can configure a disable-timer parameter that will allow you to specify the amount of time you want the port to remain disabled (0 to 6048000 seconds). The default value of the “disable-timer” parameter is “0,” meaning that the port will not be re-enabled without manual intervention on your part.

Loop Protection should not impact end-nodes, and is not intended for ports that serve as uplinks between Spanning Tree-aware switches.

Modified Date:


Provide feedback

Please rate the information on this page to help us improve our content. Thank you!