NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
iSCSI not connecting upon wake-up
Hi all.
I am running ReadyNAS 2120 with the latest OS, and connecting iSCSI to Windows Server 2008R2, as the E: drive on the server. I have the ReadyNAS schedule to go down several times each week, and when it comes up, it often will not connect E-drive on the server. The server itself stays up all the time, and when I look at the iSCSI Initiator on the server, it shows the connection, but in Computer, you can obviously see that there is no E-drive. This means I must manually disconnect in iSCSI Initiator, and then reconnect. While connected, everything runs fine.
As added information, I also have an F: drive configured for iSCSI. This one is a little different, as each computer (including the server) gets a mapped F-drive. That works flawlessly. This is really not used in production, but is more of a test area, as a common F-drive for every computer will result in corrupted data.
I am running ReadyNAS 2120 with the latest OS, and connecting iSCSI to Windows Server 2008R2, as the E: drive on the server. I have the ReadyNAS schedule to go down several times each week, and when it comes up, it often will not connect E-drive on the server. The server itself stays up all the time, and when I look at the iSCSI Initiator on the server, it shows the connection, but in Computer, you can obviously see that there is no E-drive. This means I must manually disconnect in iSCSI Initiator, and then reconnect. While connected, everything runs fine.
As added information, I also have an F: drive configured for iSCSI. This one is a little different, as each computer (including the server) gets a mapped F-drive. That works flawlessly. This is really not used in production, but is more of a test area, as a common F-drive for every computer will result in corrupted data.
3 Replies
Replies have been turned off for this discussion
- Having the NAS shutdown with an active iSCSI connection is a very bad idea. You will get corruption at some point. If you must shut it down, have a similar scheduled task on the Windows server to disconnect the initiator first. PowerShell CLI should have some scripting to connect/disconnect iSCSI targets.
- I'm amazed that the 2120 performs the scheduled shutdowns ... the 3200 won't do them which i find a right pain ... Why oh why can't the scheduled shutdown simply ignor 'warnings'
I've got 12 x 100GB iSCSI targets on 1 NAS but they're all used by Linux systems so don't experience the same issues with needing reconnection after rebooting the NAS whilst they were active and provided multipath is configured correctly any writes will simply queue if the iSCSI target isn't available temporarily.
Maybe there's some retry options in the Windows iSCSI initiator setup or an option you can switch off dropping the target if it appears unavailable (which seems to be what Windows is doing) ... I've looked quickly at the iSCSIinitiator on my Win7 PC but the MPIO options button is greyed out probably because i only have a single NIC on the PC and the NIC's on my NAS are bonded and Windows hasn't considered doing round robin on a single path as a valid method of multipathing. - To refresh the target and connect all iSCSI targets, use:
iscsicli refreshtargetportal your.ip.or.host.name.here 3260
for /f %%i in ('iscsicli ListTargets ^| find "iqn"') do iscsicli QLoginTarget %%i
To disconnect all iSCSI targets, use:for /f "tokens=3 delims=: " %%i in ('iscsicli SessionList ^| find "Session Id"') do iscsicli LogoutTarget %%i
Powershell not needed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
