A media blade's fabric B vHBA logs in and is zoned to the array in the correct VSAN. The boot policy names a SAN boot target only on fabric A, and no target exists there. The blade never boots from the LUN. What should change?
Select an answer to reveal the explanation.
Short Explanation
You’re already reaching the LUN through fabric B; the mismatch is that the boot policy sends you to fabric A, where no target exists. Point the boot target to the fabric B vHBA and the array WWPN that is actually zoned, and you’ll be directing the blade to the available path.
Full Explanation
A SAN boot target in the boot policy identifies the vHBA, target WWPN, and LUN the blade should use. The fabric B vHBA’s login and zoning show that its path to the array works, but they do not change the boot policy. Point the boot target to that fabric B vHBA and the array WWPN that is actually zoned, so the blade can attempt to boot from the LUN. The chassis power policy does not determine whether SAN boot is enabled; grid power is not the cause. The array zones and masks the port WWN that FLOGIs—the WWPN—not the node name, so changing the vHBA node name does not correct a boot target aimed at the wrong fabric. Server ports connect the chassis to the fabric interconnect; because the blade already FLOGIs and is zoned in the correct VSAN, the uplink role is not preventing this path. Exam caveat: the boot order must still try this SAN target before a bootable local disk, or the blade may not reach the named LUN. Practical check: after changing the boot policy, confirm that its target WWPN matches the array WWPN zoned and masked for the fabric B vHBA.