Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.
Verify that the LUN is presented to the ESXi host. You may need to contact your array vendor for assistance.
Verify that the LUN is in the same storage group as all the ESXi hosts (if applicable to the array).
Verify that the LUN is configured correctly for use with the ESXi host.
Note: Consult the appropriate SAN configuration guide for your array (listed in the Additional Information section).
Verify that the LUN is not set to read-only on the array.
If you are presenting LUN IDs that are higher than 255, please ensure Disk.MaxLUN setting on the ESXi host is set higher than the range you are using. Please see:Changing the Disk.MaxLUN parameter on ESXi Hosts . Further...
If you are presenting (in total) more than 255 LUNs from an array, please make sure that your HBA driver supports it, for example Cisco UCS manager has a "Max LUNs Per Target" field that is defaulted to 256, but is recommended to be 1024 for ESXi hosts.
File a support request with VMware Support and note this Knowledge Base article ID (1003955) in the problem description. For more information, see Creating and managing Broadcom support cases.