On an Aruba CX 6000 switch, when a client port detects a loop and the do-not-disable parameter is used, what is the immediate consequence?

On an Aruba CX 6000 switch, when a client port detects a loop and the do-not-disable parameter is used, what is the immediate consequence?

• A. Port status will be validated once status is cleared
• B. An event log message is created
• C. The network analytics engine is triggered
• D. Port status led blinks in amber with 100hz

Answer: (B)

When a loop is detected on a client port and the do-not-disable setting is configured, the switch does not shut the port down immediately. Instead, it creates an event log entry to notify administrators about the loop condition. This provides visibility and allows manual intervention without an automatic port disable. The port remains up and traffic keeps flowing until you intervene. The other options don’t describe the immediate action here: there isn’t an automatic re-validation of port status on clearance, nor an automatic triggering of the network analytics engine, nor an amber LED blink as the immediate consequence.

When a loop is detected on a client port and the do-not-disable setting is configured, the switch does not shut the port down immediately. Instead, it creates an event log entry to notify administrators about the loop condition. This provides visibility and allows manual intervention without an automatic port disable. The port remains up and traffic keeps flowing until you intervene. The other options don’t describe the immediate action here: there isn’t an automatic re-validation of port status on clearance, nor an automatic triggering of the network analytics engine, nor an amber LED blink as the immediate consequence.