PE on ESXi host "has a non "ok" operational state: inaccessible" event in vCenter
search cancel

PE on ESXi host "has a non "ok" operational state: inaccessible" event in vCenter

book

Article ID: 386942

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vSphere ESXi 7.0 VMware vSphere ESXi 8.0

Issue/Introduction

  • vCenter Server Events shows the following message:

    Storage Provider [<Name of SP>] raised an alert type 'Object' on vvol:#### : SAN PE is not operational: PE with naa id naa.#### on ESXi host host.example.com has a non "ok" operational state: inaccessible

  • PE is listed under "esxcli storage vvol protocolendpoint list"

  • ESXi - /var/log/vvold.log reports that the PE LUN is inaccessible.

  • The following excerpt from ESXi - /var/log/vvold.log shows one accessible PE LUN and two which are incorrectly presented and reported inaccessible.

    VVold[2103009] [Originator@6876 sub=Default OpId=Session] VasaOp[#7] ===> FINAL SUCCESS queryProtocolEndpoint VP (NetApp-VP) Container (NetApp.clustered.Data.ONTAP.VP:####) timeElapsed=43 msecs (#outstanding 1)
    VVold[2103009] [Originator@6876 sub=Default OpId=Session] ProtocolEndpoint::InitializeFromVasaPE Initing SCSI PE (27000001) with peMapKey (naa.####)
    VVold[2103009] [Originator@6876 sub=Default OpId=Session] HostManager::AddPEs@777  PE updated in map:
    VVold[2102949] --> SCSI PE, ID (host: naa.####, vasa: 27000001) (accessible, configured)
    VVold[2102949] --> ArrayIds:NetApp.clustered.Data.ONTAP.VP:####
    VVold[2102949] -->  Lun Id: naa.####
    In(166) VVold[2103009] [Originator@6876 sub=Default OpId=Session] ProtocolEndpoint::InitializeFromVasaPE Initing SCSI PE (27000002) with peMapKey (naa.####)
    In(166) VVold[2103009] [Originator@6876 sub=Default OpId=Session] HostManager::AddPEs@777  PE added to map:
    In(166) VVold[2102949] --> SCSI PE, ID (host: Not yet initialized, vasa: 27000002) (inaccessible, not configured)
    In(166) VVold[2102949] --> ArrayIds:NetApp.clustered.Data.ONTAP.VP:####
    In(166) VVold[2102949] -->  Lun Id: naa.####
    In(166) VVold[2103009] [Originator@6876 sub=Default OpId=Session] ProtocolEndpoint::InitializeFromVasaPE Initing SCSI PE (27000003) with peMapKey (naa.####)
    [Originator@6876 sub=Default OpId=Session] HostManager::AddPEs@777  PE added to map:
    VVold[2102949] --> SCSI PE, ID (host: Not yet initialized, vasa: 27000003) (inaccessible, not configured)
    VVold[2102949] --> ArrayIds:NetApp.clustered.Data.ONTAP.VP:####
    VVold[2102949] -->  Lun Id: naa.####
    VVold[2103009] [Originator@6876 sub=Default OpId=Session] StorageArrayMgr::Add Successfully configured array NetApp.clustered.Data.ONTAP.VP:#### [Num PEs 3]

Cause

At the VASA Provider level, the Protocol Endpoint LUN is configured for ESXi host access to vVOL storage containers. However, the Protocol Endpoint LUN is not seen on the ESXi host. The LUN is not presented correctly to host and thus no paths are seen to the LUN.

Resolution

Ensure that the PE LUNs are correctly presented to the ESXi host.