Solved

iSCSI problems with VMWare

Posted on 2008-10-16
9
2,645 Views
Last Modified: 2013-11-14
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!
0
Comment
Question by:mikerunkel
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
9 Comments
 
LVL 5

Expert Comment

by:xperttech
ID: 22741685
Are you listing more than one path to your iSCSI initiator? Is multipath support listed in the HCL for your Storage?
0
 

Author Comment

by:mikerunkel
ID: 22741947
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.  
0
 

Author Comment

by:mikerunkel
ID: 22741952
Woops missed that, I don't know if they are on the HCL or not.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 5

Expert Comment

by:xperttech
ID: 22741994
My comment was more about multi-path configuration support and not the number of NICs supporting you connectivity.
0
 

Author Comment

by:mikerunkel
ID: 22742096
I don't believe they are setup in an MPIO setup. At least I don't see anything referencing that in the configuration.
0
 
LVL 5

Expert Comment

by:xperttech
ID: 22742155
What about your "Dynamic Discovery" tab under your initiator? Do you have more than one IP listed for the same box?
0
 
LVL 13

Expert Comment

by:SagiEDoc
ID: 22773524
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?
0
 

Author Comment

by:mikerunkel
ID: 22830702
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.
0
 

Accepted Solution

by:
mikerunkel earned 0 total points
ID: 22908430
Unfortunately that didnt work either SaqiEDoc...we gave up and purchased local storage for the ESXi machine to host the machines on.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question