I am attempting to have a diskless iscsi-based server stay alive
during a target host failover.  Basically, my situation is as follows:
  * The iscsi target is on a 2-node HA cluster.
  * I can boot the initiator against either machine in the node.
  * I can disconnect and reconnect the network cable on the initiator
node, and it resumes communication with its chosen node.
  * Migrating the iscsi target from one node to the other causes the
connection to completely die.

I have configured other iscsi targets and initiators that are able to
reconnect in the event of a resource migration or target-node
failover.  However, I suspect there is something to the fact that my
diskless server is using iscsistart, and not iscsid, to make the
connection.  Obviously, starting iscsid after boot brings terrible
evil to my server, causing it to go insane and die for lack of file
system access.

I am using Ubuntu 11.10 Server; the iscsi-install went beautifully,
the machine can boot, run, and reboot without issue.  Only when the
target is failed-over from one backing node to the other do I see this
failure occur.  (I have the IP address migrating with the target, and
verified that everything works correctly for at least booting - as I
said, I've done this before with non-boot iscsi initiators, and it
works wonderfully there.)

Any ideas on what I could/should be doing to make this work correctly?
-- Matthew

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to