A SaaS platform blade completes Fibre Channel login, but its vHBA is in a different VSAN from the array it must reach. Zoning in the array's VSAN is already correct. What should change on the service profile?
Select an answer to reveal the explanation.
Short Explanation
The vHBA logged into the wrong neighborhood. You pointed it at a VSAN that does not contain the array, so a correct zone in the array's VSAN never sees this login. Move the vHBA into the array's VSAN rather than changing an Ethernet VLAN or a power policy.
Full Explanation
A vHBA is placed in a VSAN by the service profile, usually through the vHBA template or the SAN connectivity policy. FLOGI then happens in that VSAN only. The SaaS blade is logging in successfully, just not in the VSAN where the array and the correct zone live, so the target never sees this port. The SAN connectivity policy is the object that stores this VSAN when the vHBA is built from a template. Moving the vHBA to the array's VSAN puts the login in the same fabric as the target. A UUID identifies the service profile and is not a VSAN selector. An Ethernet VLAN on a vNIC is a LAN membership. It is not the VSAN number, and clearing it does not move a Fibre Channel login. Grid is a chassis power-feed policy. It does not change the VSAN programmed on a vHBA. Caveat: after the VSAN is corrected, the WWPN still has to be zoned to the array port and the LUN has to be masked, or the login will be in the right VSAN and still see no disk. Operational check: set the vHBA VSAN, reassociate if the profile requires it, and confirm the name server in the array's VSAN shows this WWPN.