VMware

This Question is Answered

1 "helpful" answer available (6 pts)
1 2 Previous Next 20 Replies Last post: Nov 12, 2009 3:10 AM by swisst  

problems using iSCSI in vSphere. posted: Nov 3, 2009 3:01 AM

Click to view swisst's profile Enthusiast 29 posts since
Jan 26, 2007

Some background, I have a working, live esx 3.5 cluster (5 nodes, with 4 SAN provisioned LUNS) as well as stand alone instances using the software iSCSI to connect to a SAN.
These all work marvellously !!

Am having problems with the trial standard version of vSphere attaching to the SAN.
I have read several discussion threads regarding
multipathing...these talk of needing to utilise the esxcli...but I
don't want to multipath...yet anyhow.

what am i missing ?
is there some switch (not in 3.5) that isn't obviously marked.
are there some design considerations/limitations that I have missed?
Or is iSCSI even available in this version of vSphere.

thanks in advance.


Re: problems using iSCSI in vSphere.

1. Nov 3, 2009 5:39 AM in response to: swisst
Click to view Andy Banta's profile Hot Shot 128 posts since
Feb 19, 2006
If you don't want storage multipathing, you don't need to do anything special. Create a vmkernel network port, enable SW iSCSI and use it just like 3.5.
The advantage with vSphere 4 is that you don't need to have service console access to the iSCSI storage. Otherwise, it should be about the same experience.

Enjoy,
Andy

Re: problems using iSCSI in vSphere.

2. Nov 3, 2009 6:35 AM in response to: swisst
Click to view byoung111's profile Hot Shot 63 posts since
Jun 20, 2007
What kind of problems are you having? I migrated 15 ESX servers from 3.5 to 4.0 both using Standard and Enterprise licensing. I had no problem connecting to my iSCSI SAN on any of my servers. Setup for iSCSI was the same in 4 as it is in 3.5. All of my ESX servers were using the software iSCSI initiator. I am starting to switch to a hardware initiator, and I'm not having a problem with that either.

Re: problems using iSCSI in vSphere.

4. Nov 3, 2009 7:21 AM in response to: swisst
Click to view byoung111's profile Hot Shot 63 posts since
Jun 20, 2007

Ok. Are you using a hardware or software iSCSI initiator? Have you done a rescan of your datastore to pick up the LUNs?

Re: problems using iSCSI in vSphere.

6. Nov 3, 2009 7:55 AM in response to: swisst
Click to view byoung111's profile Hot Shot 63 posts since
Jun 20, 2007

Help is what we're all here for!!!

Ok, lets see. In you iSCSI initiator properties, is your SAN target IP listed in the Dynamic Discovery tab? On your SAN did you grant access to your ESX servers initiator? I know you said you checked your CHAP settings, but are you using CHAP? I'm sure I'll come up with more questions.

Re: problems using iSCSI in vSphere.

7. Nov 3, 2009 7:58 AM in response to: swisst
Click to view athlon_crazy's profile Expert 524 posts since
Oct 28, 2007
swisst wrote:
....the problems are focussed around the obtaining of targets from my SAN.

My config is quite simple i have a single esx host. with two nics.

The first nic hosts a shared configuration of Console access and virtual switch (on our production LAN) with the second hosting a VMKernel with SAN vLAN access.

Whilst logged on with root access onto the console of my box I can ping mystorage target. so connectivity/routing is proven not to be a problem.

I have checked all the obvious; security profiles, iSCSI initiator names, CHAP, etc...

ping only doesn't mean your vmkernel is working. Use vmkping instead.

vcbMC-1.0.6 Beta
vcbMC-1.0.7 Lite
http://www.no-x.org

Re: problems using iSCSI in vSphere.

9. Nov 3, 2009 8:05 AM in response to: swisst
Click to view athlon_crazy's profile Expert 524 posts since
Oct 28, 2007
aha, problem spotted! solve that first. Perhaps end to end connection got some configuration issue.

vcbMC-1.0.6 Beta
vcbMC-1.0.7 Lite
http://www.no-x.org

Re: problems using iSCSI in vSphere.

10. Nov 3, 2009 8:07 AM in response to: swisst
Click to view Andy Banta's profile Hot Shot 128 posts since
Feb 19, 2006
tried the vmkping and that hasn't worked.....100% packet loss

Ok. Is the address of your vmkernel port on the same subnet as the storage?

If not, have you added a route for the vmkernel interface?

Re: problems using iSCSI in vSphere.

12. Nov 3, 2009 8:28 AM in response to: swisst
Click to view athlon_crazy's profile Expert 524 posts since
Oct 28, 2007
do u able to vmkping vmkernel ip for another ESX hosts?

vcbMC-1.0.6 Beta
vcbMC-1.0.7 Lite
http://www.no-x.org

Re: problems using iSCSI in vSphere.

13. Nov 3, 2009 8:29 AM in response to: swisst
Click to view Andy Banta's profile Hot Shot 128 posts since
Feb 19, 2006
You're down to some sort of connectivity or network issue. Can you ping the other direction, from the storage to the host?

VLAN mismatch?

Cabling issue?

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities