I downloaded the latest vVNX to test the vVOL, my lab has 3 hosts with ESXi6 U1b and vCSA 6.0.0.10200. The vVNX is deployed to another esxi 6 and with one virtual HDD ( carved from 240G SSD drive using Thick provision Eager zero) is used to create a single storage pool, I strictly followed the instructions demonstrated in the following video, I did not create extra Storage Profile beyond these required for setting up vVOL. When vVOL is added to the three hosts, everything seems to be fine, but when I look at the storage size, it is 0 B, but when I looked at the storage devices attached to esx1 host, notice it says "inaccessible". I also chchecked the time, my vCenter, ESXi, vVNX all NTPed to the same server, and their time skew is less than 1 min.
For these small 3 host lab, I did not configure anything thing such as LUN masking or path selection rules. Also the Protocol Endpoint ip address can be seen from the hosts and vcenter, When I ssh to any host and type
" esxcli storage vvol protocolendpoint list " , the result is blank, so it appears that ProtocolEndPoint has some issues, but yesterday, when I had two storage pools, for 30 min, everything worked ( I later destroyed that vVOL due to other mistakes).
Does anyone have clue? I mean the vVOL ver1.0 does seem to have some rough edges.
