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.
Tonight I tried it again, vVOL now shows the right size, which is 150GB, and it has connection to all three hosts, but only esx3 has sustainable connection, esx1, esx2 quickly lose connection after 305 minutes.
I went to /var/log/vvold.log and I found the following, the same thing was not found in the vvold.log on esx3. Looks to me there are some issues with VASA, but I don't know how to resolve this issue, as of right now, HA has been turned off, and there is really no different between esx1, esx2 and esx3.
The esxi6 server (Lenovo H50-55 Desktop, with dual-core AMD A8‑7600 CPU) where I installed vVNX has 16G RAM, and it is partially shared with VRAM, and I managed to create an vVNX VM with 12GB RAM, but the RAM is tight. On the same esxi6 host, I installed another copy of vVNX without VVOL, two iSCSi LUNS were created without any issues. This esxi6 server is NOt managed by the same vCenter managing esx1/2/3, in fact, I am using C# client to manage it.
On esx1 and esx2, when I run command: esxcli storage vvol protocolendpoint list, it is still empty
On esx3, this is what I got:
rfc4122.822ebe79-f151-4374-bbd2-e22fbd93e483
Host Id: e0992541-a79e6176
Array Id: EMC:VIRT1609T88K43
Type: NFS
Accessible: true
Configured: true
Lun Id:
Remote Host: 192.168.1.72
Remote Share: /NAS_PE
Storage Containers: 24790a2e-47b8-4d76-aab7-570bcb008dcf
/var/log/vvold.log content:
2016-03-08T06:09:29.230Z info vvold[FFFAFB70] [Originator@6876 sub=Default] VasaSession::Initialize url is empty
2016-03-08T06:09:29.230Z warning vvold[FFFAFB70] [Originator@6876 sub=Default] VasaSession::DoSetContext: Empty VP URL for VP (VASA)!
2016-03-08T06:09:29.230Z info vvold[FFFAFB70] [Originator@6876 sub=Default] Initialize: Failed to establish connection https://192.168.1.70:8443/vasa/version.xml
2016-03-08T06:09:29.230Z error vvold[FFFAFB70] [Originator@6876 sub=Default] Initialize: Unable to init session to VP VASA state: 0
2016-03-08T06:09:46.117Z info vvold[FFF6EB70] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols called
2016-03-08T06:09:46.117Z info vvold[FFF6EB70] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols done for 0 VVols
2016-03-08T06:09:59.245Z info vvold[FFD672E0] [Originator@6876 sub=Default] VasaSession::GetEndPoint: with url https://192.168.1.70:8443/vasa/version.xml
2016-03-08T06:09:59.252Z error vvold[FFF6EB70] [Originator@6876 sub=HttpConnectionPool-000000] [ConnectComplete] Connect failed to <cs p:1f07f7a8,
TCP:192.168.1.70:8443>; cnx: (null), error: N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: 3C:A5:90:95:C0:54:C1:5A:7C:C5:2D:BD:3F:25:C3:63:AE:01:A9:BA
--> ExpectedThumbprint:
--> ExpectedPeerName: 192.168.1.70
--> The remote host certificate has these problems:
-->
--> * self signed certificate in certificate chain)
2016-03-08T06:09:59.252Z warning vvold[FFD672E0] [Originator@6876 sub=Default] VasaSession::GetEndPoint: failed to get endpoint, err=SSL Exception: Verification parameters:
--> PeerThumbprint: 3C:A5:90:95:C0:54:C1:5A:7C:C5:2D:BD:3F:25:C3:63:AE:01:A9:BA
--> ExpectedThumbprint:
--> ExpectedPeerName: 192.168.1.70
--> The remote host certificate has these problems:
-->
--> * self signed certificate in certificate chain, using default
