mikerunkel
asked on
iSCSI problems with VMWare
I am having these issues with 2 VMWare esxi installation using iSCSI to connect to a Windows Storage Server box. They both connect to the same target. I keep seeing the following errors show up...
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm1 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm1 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:1:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:1:0
vm1 machine - vmkernel:)WARNING: VSCIFs235 Failed reset of virtual target
The fix is to restart the iSCSI Target service on the Storage Server box and that seems to get things working again. This is happening about twice per day now though!
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm2 machine - vmkernel: 2115)WARNING: UserSocketiNet. 588: waiters list is not empty
vm1 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm1 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:1:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:0:0
vm2 machine - vmkernel )ALERT:SCSI 4506: Cannont find a path to device vmhba32:0:) in a good state. Trying path vmhba32:1:0
vm1 machine - vmkernel:)WARNING: VSCIFs235 Failed reset of virtual target
The fix is to restart the iSCSI Target service on the Storage Server box and that seems to get things working again. This is happening about twice per day now though!
xperttech
Are you listing more than one path to your iSCSI initiator? Is multipath support listed in the HCL for your Storage?
ASKER
I simplified from using 2 NICs for the DMZ(1 subnet on a different switch) storage path and 1 NIC for(another subnet on a another switch) the iSCSI network path down to just 1 NIC on the dmz side. Neither configuration option seemed to affect the reliability.
ASKER
Woops missed that, I don't know if they are on the HCL or not.
My comment was more about multi-path configuration support and not the number of NICs supporting you connectivity.
ASKER
I don't believe they are setup in an MPIO setup. At least I don't see anything referencing that in the configuration.
What about your "Dynamic Discovery" tab under your initiator? Do you have more than one IP listed for the same box?
Under the dynamic discovery you need to have every single IP address listed that the server could potentially connect to. What is the make and model of your switches and iSCSI enclosure?
ASKER
We are using a Cisco 3750 switch, and the iSCSI enclosure is a StorageFlex unit running Windows Storage Server edition. I will check the dynamic discovery too. As a temporary solution we have stopped using iSCSI for the VMs and are using NFS instead.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.