Software iSCSI adapter will not see storage array. vmkiscsi.conf missing!

[chet201110141]

I am trying to connect to iSCSI array (MD3200i) from a ESX4.1(Dell R710).

The storage array has already been configured, and is working with another similar host(ESX4.1 on a R710 through the software iSCSI adpater).

I am using the software iSCSI adapter on the host to initiate the connection.

The appropriate networking has been setup and care has been taken to make sure that the iniator and the targets are in the same subnet.

Binding has been setup on the adapter as well.

Here's the issue: As per VMWare KB article 8858900, when I try to edit the vmkiscsi.conf file, I found that it was missing.

Another thing to note: As part of the troubleshooting, I put the host in maintenance mode, deleted all the networking for iSCSI, removed the Dynamic Discovery targets from the iSCSI adapter, disabled it,  rebooted the host, added appropriate networking elements and enabled the iSCSI adapter (all the above configuration steps were done from the console). HOWEVER, when I listed the port bindings for the softare iSCSI adapter (which at this stage should have been none?), there were already two vmkernel ports on there.

I removed them and added them again, just to be sure. But I am wondering why it still showed up since the iSCSI adapter had been disabled already.

When I tried to kill the ISCSI stack ("esxcfg-swiscsi -k"), I get a message "kill not supported yet".

I am lost and am thinking of reinstalling ESX on the host as the last step. Please advice!

I would appreciate any leads. Thanks!

[AndreTheGiant]

The MD3200i has a specific configuration for VMware.

Use Dell document "md-family-deployment-guide.pdf"

Andre

[john23]

I don't think you need reinstall esx. Start iscsi configuration again . After providing the vmkernel ip, try to do vmkping to your iscsi target.

[chet201110141]

Andre/John,

Yes, I used the MD Deployment Guide for ESX 4.1 to confiugure the environment.

Also, I am able to vmkping the targets on the array but not able to ping them  for some reason.

Is there a way to delete the software iSCSI adapter and start from scratch again. That seems to be the only thing I haven't done so far.

[AndreTheGiant]

You can disable it, reboot the host and then re-enable again.

Remember that you must create the LUN mapping on the storage side!

Andre

[chet201110141]

Andre,

I have disabled it, restarted the host, enabled the adapter again, but with the same result.

I would think that if that were to effectively delete the software iscsi adapter, it would lose the previous state information (dynamic discovery addresses and Alias). But it hasn't. It remembers it from the last time for some reason.

After disabling the adapter from the CLI and trying to kill the iSCSI stack (esxcfg-swiscsi -k) it throws up an error message "kill not supported yet".

Looking at the /var/log/iscsid.log shows that the discovery is failing on this host.

On the storage array side of things, all the configuration steps have been taken.The LUN mapping has been created for this partucluar host.

It just isn't seeing the iqn for this host in the list of initiators.

Chet

[JasonFSVM]

I'm on hold (surprise) with VMware support right now with the same issue and I found the following, hopefully it will help:

http://kb.vmware.com/kb/1038065