Please Help Iscsi question

[stilmon]

Quick question guys not even sure if im in right part of site but here it goes... I have vmware esxi 4.0 I have 2 switches 1 for public and 1 for private iscsi. i set up a nmkernal port with a free ip from my public network. my ip for my iscsi are 208.70.187.72 and 208.70.187.92  I cannot seem to connect to them when they are on the private network with current config only if i put a patch cable the both switches and private becomes public then it will start working. is vkernal wrong?  how do the iscsi get an ip on private network? keep in mind they are setup for san

[AndreTheGiant]

Welcome to the community.

Use a different network for your iSCSI LAN.

Then you will se the the vmk1 interface will be used, instead of vmk0.

Andre

[stilmon]

thts how I had it hooked up was on a seperate lan but it wasnt allowing me to ping the sans or even connect to them...

[maup33]

So you made a vmkernel port, assgned a networkadapter, associated the vmkernel with the iscsci initiator and when you run the discovery you see the san on your private range but your unable to ping it?

esxcli swiscsi nic add -n vmk1 -d vmhba3?

[stilmon]

Yes, I did everything you stated except asociate the vmkernal with iscsi. is there a certain way to do that? is it ok to use the ips I assigned ? reason I ask is they are IpS on my public network that where unused... or does it not matter what the scsi IPs are on the private? sorry for so many questions this is fjrst time ive delt with a private network setup like this

[stilmon]

anyone?

[AndreTheGiant]

The command to do a vmkernel bind to the iSCSI  initiator is show in previous post (esxcli).

It can be different in your case (check the vmkernel name and iSCSI interface name).

For more info: http://www.vmware.com/pdf/vsphere4/r41/vsp_41_iscsi_san_cfg.pdf

Andre

[stilmon]

From research ive done this may be the solution. just having trouble binding still. not able to follow how to bind

[maup33 · Accepted solution]

Hmm, you really should read though the document; it's all in there. In a nutshell;

The first thing to do is to note the vmhba# of the iSCSI Software Initiator. This can be seen in the vCenter GUI on the ESX host under Configuration -> Storage Adapters.

example vmhba33

To determine the vmk# of each VMkernel port from the vCenter GUI navigate to Configuration ->Networking.

in your example (printscreen) that's vmk1

Now that we know the vmhba# and the vmk# we can map the VMkernel Port to the iSCSI

Software Initiator. This is done through the CLI by typing the following command:

esxcli swiscsi nic add –n vmk1 –d vmhba33

To verify that all of the vmk# are bound properly to the vmhba run the following command:

esxcli swiscsi nic list –d vmhba33

Now that the advanced configuration for the vSphere iSCSI Software Initiator has been completed, the next stage is to connect to the SAN and to the volumes it contains.

From the vCenter GUI on the ESX host navigate to Configuration -> Storage Adapters. Select the iSCSI Software Adapter and click Properties. Add the IP address of your SAN to the dynamic discovery.

On your SAN make a lun, or a volume or whatever add the iqn or whatever your using an do a rescan on your host.

[stilmon]

well this is where im at now I typed the command in and it keeps giving me this error when I type my user info.. My server is Deff 4.0

is there a diff rout I have to type?

[maup33]

you're using 4? Run it from the host..

http://communities.vmware.com/thread/235841

[stilmon]

well all is good on the iscsi issue thanks guys for help !!!   but now when I add this SAn to my network I see this

now it only does this when I try to add this particular iscsi to another host(2 hots only)  but I added the one that says .92 to both hosts and it worked fine just this one keeps getting error

[maup33]

Nice!

try mounting it directly from your host; http://kb.vmware.com/kb/1015986