A new LUN has been created on an iSCSI array and assigned to an ESXi 5.x server . However, when the administrator logs in to the vSphere Web Client the LUN is not visible. Other LUNs on the iSCSI arra

Because other LUNs on the same iSCSI array are already visible, the host demonstrably has valid network connectivity, correct switch zoning, and working CHAP credentials to that array - none of those elements are the problem. The only remaining explanation is that the ESXi host has not yet queried the array for newly provisioned storage, and running a rescan from the vSphere Web Client causes the host to rediscover all available LUNs including the new one.

Zoning cannot be the issue because the same host already accesses other LUNs on that same iSCSI array, which confirms the fabric path to the array is already open.

Adding a target to the Static Discovery list is used to manually specify iSCSI targets for the software initiator, but is not a requirement for discovering a new LUN on an already-reachable array.

CHAP settings are confirmed working because the host can already authenticate to and read other LUNs on the same array using those credentials.