What is the recommended configuration to ensure link aggregation is consistent in a campus topology using VSX with two aggregation switches and downlinks to access switches?

Question

Options

• AUse the command "vsx-sync active-gateways" under the VSX context.
• BUse a custom LACP hash algorithm for improved load balancing.
• CUse the command "vsx-sync mclag-interfaces" from the global context.
• DUse the command "vsx-sync mclag-interfaces" under the VSX context.

• A
  9% (2)
• B
  4% (1)
• C
  13% (3)
• D
  74% (17)

Explanation

Option D is correct because in HPE Aruba VSX deployments, the vsx-sync mclag-interfaces command must be issued under the VSX context (not global config) to synchronize Multi-Chassis LAG interface configurations between the two aggregation peers - this ensures both switches present a consistent, unified LAG to downstream access switches.

Why the distractors fail:

• A is wrong because vsx-sync active-gateways synchronizes Layer 3 Active Gateway (virtual IP) state, not LAG/MCLAG interface config - it serves a different purpose entirely.
• B is wrong because a custom LACP hash algorithm only affects traffic distribution within an existing LAG; it does nothing to synchronize LAG configuration consistency across VSX peers.
• C is the classic trap - the command and keyword are right, but the context is wrong. Running vsx-sync mclag-interfaces from global config instead of VSX context will not achieve the intended synchronization.

Memory tip: Remember "VSX sync lives in VSX" - any vsx-sync synchronization command must be scoped inside the VSX context, and pair mclag with "multi-chassis LAG" to confirm it's the right keyword when the question involves link aggregation across two switches.

No community discussion yet for this question.