A storage administrator manually configures a storage switch to use a new static domain ID. After issuing an fcdomain restart vsan 1 command, the administrator sees that the switch is still using…

Question

Options

• AStatic domain IDs apply only after a switch is rebooted.
• BThe disruptive keyword was not used on the command.
• CBuild fabric notifications were not sent to the other switches.
• DDomain manager fast restart is not enabled on the switch.

• A
  77% (27)
• B
  3% (1)
• C
  14% (5)
• D
  6% (2)

Explanation

Static domain IDs in Fibre Channel storage switches are applied during the switch's initialization process - they are read at boot time, so changing the configured value has no effect on the currently running domain ID until the switch is fully rebooted. The fcdomain restart vsan 1 command only triggers a non-disruptive fast restart of the fcdomain process, which does not re-initialize the domain negotiation from scratch and therefore does not apply the new static value.

Why the distractors are wrong:

• B is tempting but incorrect here - the disruptive keyword triggers a fabric-disruptive domain restart, not the mechanism through which static domain IDs are loaded; a full reboot is still required for a static configuration to take hold.
• C is irrelevant - Build Fabric (BF) notifications are part of normal fabric convergence and are not a prerequisite for the administrator's configuration to apply.
• D is a red herring - Domain manager fast restart is a fabric feature that speeds up convergence after topology changes and has no bearing on whether a static domain ID is activated.

Memory tip: Think of "static" literally - a static domain ID is frozen at boot, just like a static IP on a server requires a service restart or reboot to apply. If it's static, it's set in stone until the switch starts fresh.

No community discussion yet for this question.