A factory IoT network engineer created an fcalias in one VSAN and cannot use that name when zoning a second VSAN on the same MDS pair. Which object is fabric-wide instead?
Select an answer to reveal the explanation.
Short Explanation
An fcalias is a nickname written in one VSAN's zoning notebook. You cannot carry that name into a second VSAN, because it was never fabric-wide. A device alias is the fabric-wide name, distributed so both VSANs can use it.
Full Explanation
An fcalias is part of the zoning configuration and belongs to one VSAN. Creating it in the first VSAN does not create it in the second, so the factory engineer cannot resolve that name while zoning the other VSAN. A device alias is a fabric-wide name for a WWPN, distributed by Cisco Fabric Services, and the same name can be referenced from zones in more than one VSAN. That is the object that matches the request. Adding another fcalias still inside the first VSAN does not make the name visible in the second VSAN, and an fcalias does not automatically span every VSAN. The name server lists devices that have logged in. It is not where zone aliases are edited, and editing a directory entry would not create a zoning name. Principal switch priority affects domain-manager election. The principal does not copy fcaliases into other VSANs when it wins. Caveat: a device alias still has to be committed after distribution is enabled, or the peer MDS keeps the old name database. Operational check: create the device alias for the WWPN, commit it, and confirm both VSANs can reference that name in a zone.