H31-341_V2.5 · Question #916
When static aggregation adds or deletes member ports, the LACP protocol must be run
The correct answer is A. True. A is correct because even in static aggregation mode, the Link Aggregation Control Protocol (LACP) must still be active to handle membership changes - specifically, when ports are added to or removed from the bundle, LACP PDUs are exchanged to negotiate and synchronize the link…
Question
When static aggregation adds or deletes member ports, the LACP protocol must be run
Options
- ATrue
- BFalse
How the community answered
(23 responses)- A74% (17)
- B26% (6)
Explanation
A is correct because even in static aggregation mode, the Link Aggregation Control Protocol (LACP) must still be active to handle membership changes - specifically, when ports are added to or removed from the bundle, LACP PDUs are exchanged to negotiate and synchronize the link state between the two ends of the aggregation group.
Option B is wrong because simply omitting LACP when modifying static aggregation membership would leave the remote switch unaware of the topology change, potentially causing traffic black-holing or inconsistent port states on each side of the link.
Memory tip: Think of LACP as the "handshake" that keeps both sides of a trunk in sync. Even when the aggregation bundle is manually (statically) defined, the handshake still needs to happen whenever membership changes - "static" describes how ports are chosen, not whether LACP runs.
Topics
Community Discussion
No community discussion yet for this question.