VVOL Inaccessible - PE's Ok - Qlogic HBA driver updated

[mhdganji]

Hi,

One of my hosts see's a Unity 300 VVOL as inactive (inaccessible)

FC HBA : Qlogic ISP2532 : Detailed info: 0000:08:00.1 1077:2532 103c:3263 vmkernel vmhba3

At the command line I see Protocol Endpoints (PE) are present but Accessibe: False

Host Id:

   Array Id: EMC:CKM0017

   Type: SCSI

   Accessible: false

   Configured: false

   Lun Id: naa.60060160feb04400176a2064ed094543

   Remote Host:

   Remote Share:

   Storage Containers: 19e13b36-adb6-4937-9551-9adf1d15a8f9

rfc4122.60060160-feb0-4400-94f4-bc480ba6455f

   Host Id:

   Array Id: EMC:CKM0017

   Accessible: false

   Configured: false

   Lun Id: naa.60060160feb0440094f4bc480ba6455f

Updated the firmware to 2.8 (latest Qlogic firmware for ESXi 6 U3) and it is stated in site that it supports VVOL (Secondary LUN)

Restarted host

Still no chance

Any idea?

[daphnissov]

As now multiple people have advised here, you need to open a SR on this case.

[mhdganji]

That's myvery own post whihc I myself answered but here is another story

In a nutshell, Why a 2352 Qlogic which detects protocol endpoints and can connect to non-vvol datastores flawlessly cannot connect to vvol

Seems to be a driver problem as many forums like this in EMC state

EMC Community Network - DECN: VMAX: Block VVol datastore is inactive

But Vmware compatibility says it is supported by this HBA model on new firmwaresand on ESXi 6 U3

[saurabh1985]

The Datastore shwos as inaccessible. When I click on the host and go to Protocol endpoints it shows as blank. However when I click on the datastore it does show the protocol endpoints. Everything looks normal on the storage front. If I create a file volume then it gets mounted and is accessible without any issue. However when I create block volume it goes inaccessible. Below is the error messagein the vvold.log:

2019-01-24T05:10:27.810Z info vvold[2101835] [Originator@6876 sub=Default] HostManager::GetContainerPEAccessibility arrayId: EMC:CKM00171904290, cid: 06c180f1-8474-4da3-b3e5-ca2963264113, accessible: 2,checkAllPEsAccessibility: false containerType: NFS, APD: 0

2019-01-24T05:10:27.810Z info vvold[2101835] [Originator@6876 sub=Default] HostManager::GetContainerPEAccessibility arrayId: EMC:CKM00171904290, cid: b2492970-2397-428c-b125-5604a7a5d548, accessible: 0,checkAllPEsAccessibility: false containerType: SCSI, APD: 0

2019-01-24T07:19:00.031Z info vvold[2101853] [Originator@6876 sub=Default] ProtocolEndpoint::GetPEInfo PE info (

--> SCSI PE, ID (host: Not yet initialized, vasa: rfc4122.60060160-96f1-4400-1664-4e06bca44bbb) (inaccessible, not configured))

2019-01-24T07:19:00.031Z info vvold[2101853] [Originator@6876 sub=Default] ProtocolEndpoint::GetPEInfo PE info (

--> SCSI PE, ID (host: Not yet initialized, vasa: rfc4122.60060160-96f1-4400-41f4-8276d48344c3) (inaccessible, not configured))

2019-01-24T07:19:00.031Z info vvold[2101853] [Originator@6876 sub=Default] SI:GetVvolContainer successful for Datastore, id=rfc4122.b2492970-2397-428c-b125-5604a7a5d548, maxVVol=16777216 MB

2019-01-24T07:19:01.344Z info vvold[2101837] [Originator@6876 sub=Default] HostManager::GetContainerPEAccessibility arrayId: EMC:CKM00171904290, cid: b2492970-2397-428c-b125-5604a7a5d548, accessible: 0,checkAllPEsAccessibility: false containerType: SCSI, APD: 0

2019-01-24T07:19:06.345Z info vvold[2101883] [Originator@6876 sub=Default]

Checked compatibility list and it is compatible for secondary LUNID  (enablevvols). Also updated the firmware and drivers still the same issue. Can someone advise?