Solved

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

Posted on 2009-04-03
2
1,133 Views
Last Modified: 2012-05-06
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
Comment
Question by:Florescu
2 Comments
 
LVL 7

Expert Comment

by:C-Shadows
ID: 24196260
0
 

Accepted Solution

by:
Florescu earned 0 total points
ID: 24197232
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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have been working as System Administrators since 2003. I recently started working as a FreeLancer and was amazed to find out that very few people are taking full advantage of their Windows Server Machines. Microsoft Windows Server comes with so…
To effectively work with Diskpart on a Server Core, it is necessary to write some small batch script's, because you can't execute diskpart in a remote powershell session. To get startet, place the Diskpart batch script's into a share on your loca…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now