Lost connectivity to storage device

[Jordan Woods]

so you lost connection to the storage that sits behind your vmware host? is that what I’m understanding here? what storage do you have? Maybe I’m out of the loop on this one, but I think it would be good to have a bit more information.

-jw

[Irrani Dam]

Hello,

The storage device reading (vmhba35:C1:T0:L7) mentioned in the
example
earlier contains several potential failure points:
• vmhba35 – HBA (Host Bus Adapter)
• C1 – Channel
• T0 – Target (Storage processor port)
• L7 – LUN (Logical Unit Number or Disk Unit)
To determine the actual failure or to eliminate possible issues:
1. Identify the available storage paths to the reported storage
device
by running the esxcfg-mpath -l command
2. Check that a rescan does not restore visibility to the targets.
3. Determine whether the connectivity issue is with the iSCSI storage
or the fiber storage. Perform one of the following depending on what
your connectivity issue is:
o To troubleshoot the connectivity to the iSCSI storage using the
software initiator:
a. Check whether a ping to the storage array fails from ESX.
b. Check whether a vmkping to each network portal of the the storage
array fails.
c. Check that the initiator is registered on the array. Contact your
storage vendor for instructions on this procedure.
d. Check that the following physical hardware is correctly
functioning:
? Ethernet switch
? Ethernet cables between the switch and the ESX host
? Ethernet cables between the switch and the storage array
o To troubleshoot the connectivity to the fiber attached storage,
check the following:
a. The fiber switch zoning configuration permits the ESX host to see
the storage array. Consult your switch vendor if you require
assistance.
b. The fiber switch propagates RSCN messages to the ESX hosts
4. Check the physical hardware for the following:
o The storage processors on the array.
o The fiber switch and the Gigabit Interface Converter (GBIC) units
in
the switch.
o The fiber cables between the fiber switch and the array.
o The array itself.
Important: A rescan is required after any change is made to see if
the
targets are detected.

kind regards,
Irrani

[Edwards Willeam]

We have stonefly’s opti SAN.Physically verified the all connections.checked the path also all things are perfect.

[Irrani Dam]

I guess it is caused by ESX multipathing. If ESX has issue to connect to one target portal and it happens to use round-robin load balance policy, you will see this error. Any virtual machines using the affected datastore may become unresponsive. However, since there are still path to the lun, VMs are not affected. You can check load balance policy on ESX and use Fixed policy. This will make it active/passive. If you have multiple LUNs, you can force ESX to use different active path for each LUN.