You need an Aruba CX solution that will warn the helpdesk when devices behind unmanaged switches cause outages on edge ports. Which configuration option is correct?

You need an Aruba CX solution that will warn the helpdesk when devices behind unmanaged switches cause outages on edge ports. Which configuration option is correct?

• A. Configure spanning tree on the Aruba CX 8325 switches Set the trap-option
• B. Configure loop protection on all edge ports of the Aruba CX 6200 and CX 6300 switches No trap option is needed
• C. Configure loop protection on all edge ports of the Aruba CX 6200 and CX 6300 switches Set up the trap-option
• D. Configure spanning tree on the Aruba CX 6200 and CX 6300 switches No trap option is needed

Answer: (C)

Detecting and alerting about edge-loop issues requires two things: first, the switch must actively protect the edge ports from loops, and second, there must be a way to notify the helpdesk when that protection kicks in. Enabling loop protection on all edge ports of the Aruba CX 6200 and CX 6300 switches ensures that exposed devices behind unmanaged switches don’t create broadcast loops unchecked. Pairing that with the trap-option makes the switch generate SNMP traps (alerts) to the monitoring system, so the helpdesk is warned as soon as a loop is detected or a port is blocked. Relying solely on spanning tree won’t automatically provide timely alerts to the helpdesk, and leaving out trap notifications means the incident may go unnoticed. The combination of edge loop protection plus trap notifications is what provides both prevention and visibility, which is why configuring loop protection on the 6200/6300 edge ports and setting up trap-option is the right approach.

Detecting and alerting about edge-loop issues requires two things: first, the switch must actively protect the edge ports from loops, and second, there must be a way to notify the helpdesk when that protection kicks in. Enabling loop protection on all edge ports of the Aruba CX 6200 and CX 6300 switches ensures that exposed devices behind unmanaged switches don’t create broadcast loops unchecked. Pairing that with the trap-option makes the switch generate SNMP traps (alerts) to the monitoring system, so the helpdesk is warned as soon as a loop is detected or a port is blocked.

Relying solely on spanning tree won’t automatically provide timely alerts to the helpdesk, and leaving out trap notifications means the incident may go unnoticed. The combination of edge loop protection plus trap notifications is what provides both prevention and visibility, which is why configuring loop protection on the 6200/6300 edge ports and setting up trap-option is the right approach.