VMware Cloud Community
kevintmpm
Contributor
Contributor

Failed to enable software iSCSI

I am trying to enable the software iSCSI initiator, but got the above error message. Even running the 'esxcfg-swiscsi -e' at the command line results in the following error message:

  1. esxcfg-swiscsi -e

Enabling software iSCSI...

Using /usr/lib/vmware/vmkmod/iscsi_mod.o

Failed to load module 'iscsi_mod': Invalid argument

Check system logs for more information.

Exec of command '/usr/sbin/vmkload_mod /usr/lib/vmware/vmkmod/iscsi_mod.o ' suceeded, but returned with non-zero status: 1

Any ideas what's causing this?

Reply
0 Kudos
9 Replies
bhadzik
Enthusiast
Enthusiast

Have you tried it through the VI client? You should be able to do all of it from there.

In the client it also gives you a reminder about the service console needed to be able to see the iscsi target. Make sure your service console can see the iscsi target, even if you have to add another service console on the san network.

Reply
0 Kudos
kevintmpm
Contributor
Contributor

Yes, I have tried it through the VI client and I get the same error message.

I am able to ping the iscsi target just fine from the service console. I have another ESX 3.0.2 server that works just fine with the iSCSI. My problem is I can't even enable the software iSCSI on the ESX server.

Reply
0 Kudos
divintas
Enthusiast
Enthusiast

Hi,

did you create a VMkernel port? This is requirement for software iscsi.

http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_iscsi_san_cfg.pdf

page 50.

regards,

Reply
0 Kudos
kevintmpm
Contributor
Contributor

Yes, I have the VMkernel created with the VMotion enabled on it. I followed the exact instruction for when I enabled the software iscsi on the ESX 3.0.2 server that currently has the software iscsi working. Is it possible that I have a corrupted install?

Reply
0 Kudos
mstansberry
Contributor
Contributor

I am experiencing the same issues on 3 seperate ESX boxes trying to get iSCSI configured. After reading the documentation, it appears that I should be able to set the iSCSI name while enabling the software adapter but this option is greyed out. Any other ideas as we are trying to evaluate an iSCSI solution this week and testing it on ESX is imperative. Thanks for any help that you can give.

Reply
0 Kudos
kevintmpm
Contributor
Contributor

It sounds to me in your case that you don't have the VMKernel port created. You'll need to have it created before you are able to enable iSCSI. In my case, I am able to attempt enabling iSCSI but it errors out.

Reply
0 Kudos
ctfoster
Expert
Expert

There are some suggestions in this thread that may be some assistance.

Reply
0 Kudos
kevintmpm
Contributor
Contributor

Tried all the suggestions in that thread and none of them is helping. Good thing we decided to do some thorough testing with the 3.5 before upgrading our 3.0.2 box.

Reply
0 Kudos
opbz
Hot Shot
Hot Shot

looks like either something went wrong during update or there is something wrong with your networking config.

I notice several broadcom nic patches for ESX 3.5 out there might want to try them if you are using a broadcom nic for it also I assume you have rebooted by now right?

what happens if you just query it?

esxcfg-swiscsi -q

I also found several issues with the firewall blocking the iscsi port even after you enqble it so ensure its open

esxcfg-firewall -q swISCSICLient to query and -e to enable it

Reply
0 Kudos