A media company vHBA logs into the fabric, but the zone and the array mask were built from the vHBA node name. The port name issued from the WWPN pool is a different value. Which name should the zone and the mask use?
Select an answer to reveal the explanation.
Short Explanation
The building has one street address and several doors, and the guard list was written for the street. You put the port WWN from the WWPN pool in the zone and on the array mask, because that is the identity the vHBA presents at login. The node name identifies the adapter as a whole, and it is not the door the fabric checked.
Full Explanation
A vHBA has a node WWN from the WWNN pool and a port WWN from the WWPN pool. Fabric login, zoning, and array LUN masking all key off the port WWN, which is the name the media company vHBA actually presents. The zone and the mask were built from the node name, so they do not match the logged-in port even though the login itself succeeded. The node WWN stays with the HBA as a node identity. It is not the value zoning and masking should use when the port name is different. A server UUID is a compute identity stored with the service profile. The array does not read it as a Fibre Channel port name, and FLOGI does not carry it. The fabric interconnect virtual IP is the UCS Manager address. A zone is a list of Fibre Channel members, not a management IP, and naming that IP does not present a LUN to the vHBA. Caveat: if the vHBA has two ports, each port WWN needs its own zone and mask entry, and fixing only the node name still leaves both ports unknown. Operational check: copy the WWPN shown on the logged-in vHBA into the zone and the array mask, activate the zoneset, and rescan from the host.