Unsolved

This post is more than 5 years old

2 Intern

 • 

172 Posts

1458

July 3rd, 2019 12:00

Can't connect to iscsi target after server migration

I've migrated a Windows 2008 terminal server to 2016. It's a vm connected to a PS6210 group. I've reused the name and IP, so I disconnected the old server from iscsi and shut it down, then brought the new one up and set the name and IP, etc. The same iqn name was set by default. I can discover targets using the EQ group IP address, and the target I'm looking for shows up in the list, but it times out when I try to connect. I removed the basic iqn access point and copied the one from the new server just to be on the safe side (even though it was the same), but still no dice. I know the new server recognizes the target itself - I removed the access point from the LUN and refreshed the discovered targets in the initiator, and the target I want disappeared. I added the access point back and refreshed the target list, and it showed up again.

Any ideas? Should I change the iqn name manually and try again? If so, are there any guidelines for changing the name?

4 Operator

 • 

1.5K Posts

July 3rd, 2019 13:00

Hello,

 This sounds like an access control issue.  Try adding ACL entries for the IP addresses of the NICs used for iSCSI then see if that works.   What specific error do you get on Windows server?  Any error messages on the array side?

 Regards,

Don

 

2 Intern

 • 

172 Posts

July 11th, 2019 05:00

Thanks for the response, and sorry for the delay. It turned out to be yet another victim of one of the Windows KB updates that broke iscsi. Another update (KB4509475) fixed it.

Thanks.

4 Operator

 • 

1.5K Posts

July 11th, 2019 12:00

Hello, 

 Great!  Just glad you figured it out!   Thank you for the update. 

 Regards,

Don

 

No Events found!

Top