With Aruba CX 6200 switches, which command sequence protects client ports from forming layer-2 loops when uplinks are configured on 1/1/25 and 1/1/26?

With Aruba CX 6200 switches, which command sequence protects client ports from forming layer-2 loops when uplinks are configured on 1/1/25 and 1/1/26?

• A. int 1/1/1-1/1/24, loop-protect
• B. int 1/1/1-1/1/28, loop-protect
• C. int 1/1/1-1/1/28, loop-guard
• D. int 1/1/1-1/1/24, loop-guard

Answer: (A)

Protecting client ports from layer-2 loops is about applying loop protection at the edge so that any loop involving the access ports is stopped before it can broadcast across the network. On Aruba CX, loop-protect proactively detects a loop on a port and blocks that port to prevent a storm from spreading into the user-facing network. Because the uplinks are on 1/1/25 and 1/1/26, you apply loop protection specifically to the client-facing ports, 1/1/1 through 1/1/24. This confines the protective action to the access ports where loops are most likely to start, while leaving the uplinks to handle topology with the switches above them. Loop-guard, by contrast, is more about behavior when BPDUs stop arriving and is less about actively stopping a loop on access ports, so it’s not the best fit for this edge-protection scenario. Limiting the range to the 24 client ports avoids unnecessary protection of the uplinks and directly addresses the risk.

Protecting client ports from layer-2 loops is about applying loop protection at the edge so that any loop involving the access ports is stopped before it can broadcast across the network. On Aruba CX, loop-protect proactively detects a loop on a port and blocks that port to prevent a storm from spreading into the user-facing network. Because the uplinks are on 1/1/25 and 1/1/26, you apply loop protection specifically to the client-facing ports, 1/1/1 through 1/1/24. This confines the protective action to the access ports where loops are most likely to start, while leaving the uplinks to handle topology with the switches above them. Loop-guard, by contrast, is more about behavior when BPDUs stop arriving and is less about actively stopping a loop on access ports, so it’s not the best fit for this edge-protection scenario. Limiting the range to the 24 client ports avoids unnecessary protection of the uplinks and directly addresses the risk.