A domain ID conflict is detected on a switch. Which action resolves the issue in the shortest possible time after the preferred domain ID is changed to a static domain ID?

Question

Options

• AIssue an fcdomain disruptive restart.
• BIssue an fcdomain nondisruptive restart.
• CEnter the commands for a VSAN suspend / no-suspend.
• DEnter the commands to complete a domain manager fast restart.

• A
  73% (29)
• B
  15% (6)
• C
  8% (3)
• D
  5% (2)

Explanation

Issuing an fcdomain disruptive restart forces an immediate fabric reconfiguration, causing all switches in the VSAN to renegotiate domain IDs from scratch - this is the fastest way to enforce a newly configured static domain ID and clear the conflict. Option B (nondisruptive restart) is wrong because it attempts to preserve existing domain assignments, meaning the conflicting domain ID is not immediately forced out, leaving the conflict unresolved in the near term. Option C (VSAN suspend/no-suspend) does trigger a re-initialization but is a slower, more heavy-handed approach that is less efficient than targeting the fcdomain process directly. Option D ("domain manager fast restart") is not a valid NX-OS command construct for this scenario and is a distractor combining real concepts incorrectly.

Memory tip: Match the urgency to the action - a static domain ID is a firm, non-negotiable assignment, so you need a disruptive restart to match that forcefulness. "Nondisruptive" = preserve existing state = preserve the conflict.

No community discussion yet for this question.