vSphere 5.1/EMC VNXe 3150 Partial/No Redundancy

[duhaas]

Having completed the setup/configuration of our new cluster along with our new EMC VNXe 3150 Array, I'm puzzeled as to why I'm seeing Partial/NoRedudancy after moving some VM's over to new host:

vSwitch configuration using used/unused configuration:

Initiator bound to two seperate vmkernel ports:

Target Side VNXe, multiple ISCSI servers with Multiple interfaces used on each Storage processor:

The number of paths seems to indicate multiple paths back to array:

Status of the VM's

Any thoughts or input would be great.

[duhaas]

According to VMware this is an open issue??

PR 957273 is the internal issue

Thoughts?

[anthonie_rozari]

The PR # 957273 that you mentioned here is  with respect to iSCSI connectivity to the storage, whereas with my case few VMs are FC connected storage and having same issue :smileyconfused:

I would like to know if all these VMs are residing on the same datastore or are they on different datastores.

Have you checked the HostBusAdapter info ? Is that ONLINE? And check the multi-pathing information of the LUNs as ACTIVE or not.

Example :

HostBusAdapterInfo-3-Key: 3

HostBusAdapterInfo-3-BUS: 3

HostBusAdapterInfo-3-Device: vmhba3

HostBusAdapterInfo-3-Driver: qla2xxx

HostBusAdapterInfo-3-Model: ISP2432-based 4Gb Fibre Channel to PCI Express HBA

HostBusAdapterInfo-3-Pci: 03:00.0

HostBusAdapterInfo-3-Status: online

[admin · Accepted solution]

You should never see full redundency when using the software iSCSI initiator. It is a single point of failure. If you want full redundency using iSCSI use hardware dependent adapters or true physical iSCSI initiators. What you are seeing is absolutely correct and expected due to a single point of failure.

Regards,

Corey

[duhaas]

Thanks drysdale, not sure why I get conflicting reports from the VMware support team, but it makes sense what your saying.