A factory IoT network creates an fcalias in one VSAN and expects that same name to exist in a second VSAN on the same MDS. The second VSAN does not have the name. Which alias is fabric-wide rather than VSAN-local?
Select an answer to reveal the explanation.
Short Explanation
An fcalias is a nickname written in one VSAN's notebook. You want a device alias when the same name must be available fabric-wide, including in the other VSAN. Raising the principal priority does not copy nicknames between VSANs.
Full Explanation
An fcalias is part of the zoning configuration and belongs to the VSAN where it was created. The factory name in the first VSAN is invisible to the second VSAN because that is how fcalias scope works. A device alias lives in a separate database that is fabric-wide and is distributed with CFS, so the same name can be referenced from zones in more than one VSAN. Creating the name as a device alias is what makes it available beyond the original VSAN. Another fcalias does not appear in every VSAN by itself. Each VSAN needs its own fcalias if that is the tool you keep using. The high byte of an FCID is the domain ID of the switch that assigned the address at FLOGI. It does not store friendly names. The principal priority elects the switch that coordinates domain IDs. It does not replicate zone aliases between VSANs. Caveat: a device alias still has to be committed if distribution is enabled, or the local switch can show a name the rest of the fabric does not have yet. Operational check: create the device alias, commit it, and confirm a zone in the second VSAN can reference that name.