A factory IoT network host sits in the active zoneset, yet it has no Fibre Channel address and does not appear in the name server. The host has not completed fabric login. What assigns the 24-bit address?
Select an answer to reveal the explanation.
Short Explanation
Being on the guest list does not hand you a room key. You get the 24-bit Fibre Channel address only when fabric login succeeds, and this host has not done that, so the name server has nothing to list. Activating the zoneset again does not mint an address for a host that has not logged in.
Full Explanation
A Fibre Channel address is 24 bits, and the switch assigns it when the node completes fabric login. Zoning can already include the host's port WWN in the active zoneset, and that membership does not create an address. Until this factory host finishes fabric login, it has no address and the name server has no registration to show. Zoneset activation copies the configured zones into the enforcement database. It does not allocate a 24-bit address for each member or insert silent hosts into the name server. Process login is how an N port opens a session to another N port, and it happens after the initiator already has an address. It is not how the switch assigns the address, and it is not a request the host sends before talking to the switch. The principal switch coordinates domain IDs for the fabric. It does not stamp addresses onto zoned hosts that have never logged in. Caveat: a host that logged in and then went silent can keep an old address until the login is cleared, so absence from the name server means there is no current registration. Operational check: watch the host attempt fabric login, confirm an address appears at that moment, and only then look for the name-server entry.