An engineer implemented a new VSAN and examined the F-mode trunks connecting an upstream switch. The engineer noticed that the new VSAN is stuck in initializing. Which two options explain why this…

On Cisco MDS F-mode trunks, a VSAN transitions from 'initializing' to 'active' only after an end device performs a FLOGI on that VSAN through the trunk link. Until a login attempt is made the switch has no trigger to bring the VSAN to active state, so it stays in initializing indefinitely.

There is no primary/subordinate VSAN hierarchy on MDS trunks; all VSANs are peers in trunk negotiation and none is held in initializing because another is designated primary.

Disabling and re-enabling the trunk is not required for a newly added VSAN to join; VSANs can be added dynamically to an active trunk without a link reset.

There is no secondary/primary VSAN designation in MDS VSAN trunking that would cause primary VSANs to stay initializing while a secondary becomes active.

If the new VSAN is not defined or not present in the allowed VSAN list on the upstream switch, trunk negotiation for that VSAN cannot complete successfully. The local MDS will continue reporting the VSAN as initializing because the remote end of the trunk does not acknowledge the VSAN as valid.