In an HPE network, which scenarios can indicate a configuration issue with Link Aggregation (LACP)?

Question

Options

• AUnstable link state
• BIncreased latency on traffic paths
• CPort flapping
• DSpanning tree topology changes

• A
  83% (25)
• D
  17% (5)

Explanation

LACP misconfiguration directly manifests as unstable link state (A), increased latency (B), and port flapping (C) because when LACP parameters are mismatched between peers (e.g., one side in active mode, the other passive or static), the protocol fails to properly negotiate the link bundle - causing ports to cycle up and down (flapping), the logical aggregate to appear unreliable (unstable link state), and traffic to be funneled through fewer member links than intended, creating congestion and higher latency. These three symptoms share a direct causal chain: misconfigured LACP → failed bundle negotiation → degraded or unstable traffic behavior.

Option D (Spanning tree topology changes) is incorrect because STP topology changes are a direct indicator of spanning tree protocol issues - such as BPDU misconfigurations, bridge priority problems, or a port transitioning between STP states - not LACP. While severe port flapping from LACP could trigger STP topology changes as a secondary side effect, STP changes themselves point to an STP-layer problem first.

Memory tip: Think of LACP issues as "ALP problems" - Aggregation failures cause Link instability, Latency spikes, and Port flapping. Spanning tree changes belong to the STP layer, one level above LACP's concern.

No community discussion yet for this question.