A new LUN from an existing storage array is presented to a vSphere cluster. A vSphere administrator determines that the LUN is visible on all but one ESXi host in the cluster. The affected host is able to see existing LUNs presented from the same storage array. What is the most likely cause?

Question

Accepted Answer

A. LUN Masking is improperly configured on the storage array. LUN masking is a storage array-side control that restricts which host initiators can access a specific LUN. Because the affected host can see other LUNs from the same array, the SAN fabric zoning and the host HBA are both functioning correctly, narrowing the problem to the new LUN's access list - the host's WWN or IQN was simply not added during the LUN masking configuration for that new LUN.

Answer

B. The SAN fabric is improperly zoned. Improper SAN fabric zoning would prevent the host from seeing any LUNs on that storage array, not selectively block only the newly presented LUN.

Answer

C. The ESXi host has NOT been rebooted. A reboot is not required to detect new LUNs; an HBA rescan is sufficient, and the host's ability to see existing LUNs confirms it is operating correctly without a reboot.

Answer

D. The HBA in the host is incompatible with ESXi. An incompatible HBA would prevent the host from accessing any LUN on the array, not just a single newly added one.

A new LUN from an existing storage array is presented to a vSphere cluster. A vSphere administrator determines that the LUN is visible on all but one ESXi host in the cluster. The affected host is abl

Question

Options

How the community answered

Why each option

Topics

Community Discussion