[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1168
  • Last Modified:

Windows 2008- iSCSI does not automatically connect to targets after reboot

I have 2 Windows 2008 servers that are configured in a cluster using iSCSI disks.  The iSCSI initiator is configured to Automatically connect to the targets after a reboot.  

I am trying to test failover and it works successfully.  i.e. I reboot the 1st node and the 2nd node takes over.  However, after 1st node comes back up, iSCSI does not reconnect to the targets.  

All the validation tests pass just fine.
0
Florescu
Asked:
Florescu
1 Solution
 
FlorescuAuthor Commented:
I figured it out.  I had to go to the iSCSI Initiator, Targets tab, then click on Logon.  Check the automatically restore and enable multi path.  Then I had to go to Advanced   I selected the iSCSI Initator as the Local Adapter and the Source IP to be the 1st iSCSI NIC ip address.  

I repeated the process for the 2nd iSCSI NIC by clicking on the target again (even though it says Connected) and logging on to the target but this time going to Advanced and selecting the 2nd iSCSI NIC.  I still had to select automatically reconnect and multipath IO.  

The reason it was happening is because the iSCSI SAN was only setup to accept connections from certain IPs.  I looked in the Event viewer on the SAN and I noticed that as the server was rebooting, it was trying to connect via the Local Area connection, instead of the ISCSI NICs.  Once I followed the above steps, it started working just fine.

You only have to select Automatically reconnect the 1st time you logon to the target with an ip address.  You don't need to do it after that because it will establish multiple sessions to the same target and that's unneeded.  I had a bunch of sessions that were established so I had to remove those from the Favorites tab, log off all of the other sessions, then start from scratch and logon as outlined above.

For some reason the Multpath IO was not configured right either.  I had to go to Control Panel, Multipath IO and add add an MPIO end device as EQLOGIC 100E-00.  
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now