iSCSI Initiator does not connect to first iSCSI target on boot up

  • 3778731
  • 12-Feb-2008
  • 30-Apr-2012

Environment

Novell Open Enterprise Server 2 (OES 2)

SUSE Linux Enterprise Server 10 SP1

Situation

There is a timing issue where the iSCSI initiator comes up directly after the network and there has not been enough time for the router/switch on the network to build the route from the iSCSI initiator to the iSCSI target. So the iSCSI initiator sees this as a real connection failure.
If you have more than one iSCSI initiator the other ones will connect.
Another symptom is that after boot up if you restart open-iscsi it will reconnect to all targets.

Resolution

This can be addressed by doing either of the following.
1. Add a delay to the open-iscsi script. This will give the network enough time to find its route.
Add "sleep 5" in the /etc/init.d/open-iscsi file in the"iscsi_login_all_nodes" section.
2. Modify /etc/sysconfig/boot and change RUN_PARALLEL="yes" to"no". This will slow the boot process by not allowing it to use multiple processors on boot up and shutdown. This will not limit the using of multiprocessors while the system is running, just boot up and shutdown.

Change Log

4-5-2010 - Juston Mortenson - removed "reported to engineering" tag.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.