I have been banging my head against the wall trying to get VVOL's established in my test environment. The setup is as follows, 3 hosts, two with HBA iSCSI broadcoms and one Software iSCSI adapter. The SAN is a mixed group, one Dell 6100 w SSD and one 4100 spinning disk. I have the Dell VSM loaded and configured, I've built a storage container on the EQL, and I can configure the access rules for hosts. I have also added the EQL as a VASA provider.
Hosts vSphere 6.0, vCenter 6.0, EQL 8.0.4, VSM 4.5.1.700
For the sake of clarity we'll call the hosts HBA1 and HBA2 and SOFT1
The protocol endpoints show up in the storage devices on all three hosts, but the only machine that can see the PE's and access them is the SOFT1 host. Its also the only one that can mount the VVOL. If I mount it via SOFT1 and choose 'mount this datastore on additional hosts' the process completes without errors, but on HBA1 and HBA2 the VVOL is in accessible.
This is from one of the two HBA hosts (HBA2):
esxcli storage vvol protocolendpoint list
naa.6019cb71d121ed38e33165924a54c38b
Host Id:
Array Id: com.dell.storageprofile.equallogic.std:MASTER
Type: SCSI
Accessible: false
Configured: false
Lun Id: naa.6019cb71d121ed38e33165924a54c38b
Remote Host:
Remote Share:
Storage Containers: 6019cb71-d121-cd52-7f62-05a43b05e04d
esxcli storage vvol storagecontainer list
MasterVMDK
StorageContainer Name: MasterVMDK
UUID: vvol:6019cb71d121cd52-7f6205a43b05e04d
Array: com.dell.storageprofile.equallogic.std:MASTER
Size(MB): 1048590
Free(MB): 1048200
Accessible: false
Default Policy:
This is from SOFT1
esxcli storage vvol protocolendpoint list
naa.6019cb71d121ed38e33165924a54c38b
Host Id: naa.6019cb71d121ed38e33165924a54c38b
Array Id: com.dell.storageprofile.equallogic.std:MASTER
Type: SCSI
Accessible: true
Configured: true
Lun Id: naa.6019cb71d121ed38e33165924a54c38b
Remote Host:
Remote Share:
Storage Containers: 6019cb71-d121-cd52-7f62-05a43b05e04d
esxcli storage vvol storagecontainer list
MasterVMDK
StorageContainer Name: MasterVMDK
UUID: vvol:6019cb71d121cd52-7f6205a43b05e04d
Array: com.dell.storageprofile.equallogic.std:MASTER
Size(MB): 1048590
Free(MB): 1048200
Accessible: true
Default Policy:
Secondly the datastore is listed in alarm with this error:
Issue,Type,Trigger Time,Status
vSphere HA failed to create a configuration vVol for this datastore and so will not be able to protect virtual machines on the datastore until the problem is resolved. Error: (vim.fault.InaccessibleDatastore) ,Configuration Issue,"10/22/15, 10:33:12 AM GMT",
I'm guessing that error will clear once I get the vvol working on all three hosts.
In addition if I try and zero out my config to rebuild the mess the VSM leaves behind access lists that I cannot destroy.
Any thoughts would be appreciated.
DT
Clik here to view.