Having consistent LUN IDs for volumes in ESXi has historically been a gotcha–though over time this requirement went away.
These days, the need for consistent LUN IDs is mainly gone. The lingering use case for this is Microsoft Clustering and how persistent SCSI reservations are handled. The below KB doesn’t mention 6.5, but I believe it to still be relevant to 6.5:
https://kb.vmware.com/s/article/2054897 Continue reading Issue with Consistent LUN ID in ESXi 6.5
A customer pinged me the other day and said they could not see a volume on their ESXi host. Running ESXi version 6.5. All of the normal stuff checked out, but the volume was nowhere to be seen. What gives? Well it turned out to be the LUN ID was over 255 and ESXi couldn’t see it. Let me explain.
The TLDR is ESXi does not support LUN IDs above 255 for your average device.
UPDATE (8/15/2017) I have been meaning to update this post for awhile. Here are the rules:
ESXi 6.5 does support LUN ID higher than 255, but only if those addresses are configured using peripheral LUN addressing. If your array uses flat addressing, it will not work (which is common for higher level LUN IDs).
ESXi 6.7 does now support flat LUN addressing so this problem goes away entirely.
See this post for more information on ESXi 6.7 flat support.
*It’s not actually aliens, it is perfectly normal SCSI you silly man.
Continue reading ESXi and the Missing LUNs: 256 or Higher