nerdexam
HP

HPE7-A08 · Question #79

An Aruba CX8100 VSX has the following state for LACP: What can be observed based on the output?

The correct answer is B. The peer lag253 needs to have a valid AGGR key. LAG253 on the local switch shows ASFNCD (indicating it is not synchronized) and the partner AGGR key is 0, which is invalid. A partner must advertise a valid aggregation key for a multi-chassis LAG to form correctly. Because the remote device is sending an AGGR key of 0, the…

Implement and Troubleshoot HPE Aruba Networking CX Switch Solutions

Question

An Aruba CX8100 VSX has the following state for LACP:

What can be observed based on the output?

Exhibit

HPE7-A08 question #79 exhibit

Options

  • AThe local lag253 configuration is set as a custom
  • BThe peer lag253 needs to have a valid AGGR key
  • CThe local lag253 configuration is set as default
  • DThe local lag27 would need to have individual AGGR key

How the community answered

(23 responses)
  • A
    13% (3)
  • B
    61% (14)
  • C
    22% (5)
  • D
    4% (1)

Explanation

LAG253 on the local switch shows ASFNCD (indicating it is not synchronized) and the partner AGGR key is 0, which is invalid. A partner must advertise a valid aggregation key for a multi-chassis LAG to form correctly. Because the remote device is sending an AGGR key of 0, the LAG cannot come up, and this is the condition observed in the output.

Topics

#LACP#VSX#LAG#AGGR key

Community Discussion

No community discussion yet for this question.

Full HPE7-A08 Practice