In network environments where users might connect unauthorized, " dumb " (unmanaged) switches or hubs, standard Spanning Tree Protocol (STP) may not be sufficient to prevent loops.
The Limitation of STP and BPDU Guard: BPDU Guard is an excellent feature that disables a port if it receives a Bridge Protocol Data Unit (BPDU). However, many unmanaged switches do not participate in STP and therefore do not originate BPDUs. Some may simply forward BPDUs or drop them entirely. If a loop is created through an unmanaged switch that doesn ' t send BPDUs, BPDU Guard will never trigger.
How Loop Protection Works: AOS-CX Loop Protection is specifically designed for this scenario. The switch sends out proprietary Loop Protection packets at a configured interval. If the switch receives its own Loop Protection packet back on the same port (or a different port in the same VLAN), it knows a loop exists.
Action on Detection: Upon detecting the loop, the switch can be configured to send an SNMP trap and, more importantly, disable the port to stop the broadcast storm and prevent a network outage.
Best Practice: Loop protection is commonly recommended for " Access " or " Colorless " ports where end-user devices connect, as it provides a safety net against loops caused by non-STP aware devices.