Question 240
The HPE AOS-CX switching case is: One of two LAG ports negotiates a different speed and the aggregate reports a rejected or suspended member. Select TWO: a corrective switching action and separate evidence that the correction worked. (Select TWO.)
Explanation
Correct Answers
The targeted correction for One of two LAG ports negotiates a different speed and the aggregate reports a rejected or suspended member is: Form LAG interfaces with consistent LACP settings, eligible member speeds and partner wiring, then evaluate per-flow hashing limitations. It reduces the risk that a partially formed aggregation can strand traffic or produce surprising throughput because a single flow usually hashes to one member.
A separate operational validation for One of two LAG ports negotiates a different speed and the aggregate reports a rejected or suspended member is: The operational LACP partner and member states agree and a controlled link-failure and multi-flow throughput test passes. It proves intended behavior instead of accepting configuration presence alone.
Incorrect Answers
This alternative concerns vlan trunk tagging and permitted vlan filters; its associated risk is: A missing tagged VLAN on one hop silently isolates clients, while unintended VLAN allowance bridges security domains. The observed case One of two LAG ports negotiates a different speed and the aggregate reports a rejected or suspended member requires the more specific lacp member selection and load distribution control. The targeted action is: Form LAG interfaces with consistent LACP settings, eligible member speeds and partner wiring, then evaluate per-flow hashing limitations.
This alternative concerns vsf single-logical-switch stack service; its associated risk is: Incorrect member order or split handling can leave orphaned interfaces and interrupt a shared access stack. The observed case One of two LAG ports negotiates a different speed and the aggregate reports a rejected or suspended member requires the more specific lacp member selection and load distribution control. The targeted action is: Form LAG interfaces with consistent LACP settings, eligible member speeds and partner wiring, then evaluate per-flow hashing limitations.
This alternative concerns mstp configuration and loop control; its associated risk is: A mismatched MSTP region or unintended root can block critical trunks or increase convergence disruption. The observed case One of two LAG ports negotiates a different speed and the aggregate reports a rejected or suspended member requires the more specific lacp member selection and load distribution control. The targeted action is: Form LAG interfaces with consistent LACP settings, eligible member speeds and partner wiring, then evaluate per-flow hashing limitations.