iScsi Initiator Weirdness

SUSE Linux Enterprise Server SLES Configure-Administer
1

Hello,

I have a newly installed OES11 cluster. To connect to the shared storage, we’re using the built in SLES11 sp1 initiator software. The cluster nodes are virtual machines running on ESXi 5.

When the virtual machine is rebooted, it will not reconnect to the iscsi target devices. There are a dozen target devices that each node connect to. Each target entry is set to log in automatically. When they don’t log in, the startup is set back to manual. If I set them to automatic again and reboot, they will connect properly.

I’m at a loss as to why this seems to be happening.

Help!

2

imc,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

3

[QUOTE=imc;6942]Hello,

I have a newly installed OES11 cluster. To connect to the shared storage, we’re using the built in SLES11 sp1 initiator software. The cluster nodes are virtual machines running on ESXi 5.

When the virtual machine is rebooted, it will not reconnect to the iscsi target devices. There are a dozen target devices that each node connect to. Each target entry is set to log in automatically. When they don’t log in, the startup is set back to manual. If I set them to automatic again and reboot, they will connect properly.

I’m at a loss as to why this seems to be happening.

Help![/QUOTE]

I’m assuming you have patched the server to the latest possible versions for SLES 11 SP1? I remember a bug in iSCSI where targets where getting set to manual after a reboot, but it was cosmetic from what I experienced.

I do usually set the node-startup to automatic in the iscsi.conf. But I can do this as only those targets will get exposed in my setups that the servers are granted access to. If you have a similar setup where your OES cluster can not “grab” unintended volumes, it might be a workaround? Again, patching solved the issue for me (and I was seeing this with SLES 11 SP1 mid 2011).

-Willem