QuestionQ17

VerifiedInfrastructure Configuration and Management

A customer design requires link aggregation. Although the consultant has verified that every host is correctly configured for fallback according to Nutanix best practices, initial testing shows that the aggregate bond does not pass traffic and has a status of configured.

What is the most likely reason the bond is disabled and reports a "configured" status?

Explanation

An AHV Active-Active bond uses LACP with link aggregation and requires LAG and LACP to be enabled and correctly matched on the corresponding ToR switch ports. Nutanix also recommends ToR fallback behavior so interfaces can pass traffic if LACP negotiation fails. Therefore, a configured bond that cannot pass traffic after host fallback has been validated most likely reflects failed LACP negotiation caused by a ToR switch misconfiguration.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!