With the CX 6000 48G switch with uplinks of 1/1/47 and 1/1/48, what does the switch do when a client port detects a loop and tx-disable parameter is used?

Question

Options

• AThe ports that confirmed the loop are disabled.
• BThe ports that transmitted and received the loop are disabled.
• CThe port that transmitted the loop is disabled.
• DThe port that received the loop is disabled.

• A
  3% (2)
• B
  5% (3)
• C
  10% (6)
• D
  82% (49)

Explanation

With the tx-disable parameter in Aruba CX loop protection, when a loop PDU sent out of a port comes back and is received on another port, only that receiving port is disabled - not the sender. The logic is that the port where the looped frame arrives is the one whose transmission is then blocked (disabled), making D the correct answer.

Why the distractors are wrong:

• A is wrong because "ports that confirmed the loop" implies multiple ports being shut down, but tx-disable targets only one specific port.
• B is wrong because both the transmitting and receiving ports are not disabled - only the receiver goes down.
• C is the most tempting trap: tx-disable sounds like it disables the transmitting port, but it actually disables the port that received the returning loop frame.

Memory tip: Despite the name "tx-disable," think of it this way - the port that gets the loop PDU back has its TX shut off. The keyword tx refers to what's being disabled on the receiving end, not which port originally transmitted. Flip your instinct: receiver gets disabled.

No community discussion yet for this question.