topic Re: Server migration-server rename with ISCSI connection to volume--possible issue. in Array Setup and Networking https://community.hpe.com/t5/array-setup-and-networking/server-migration-server-rename-with-iscsi-connection-to-volume/m-p/6984085#M1144 <HTML><HEAD></HEAD><BODY><P>Hello,</P><P></P><P>Yes, absolutely disconnect and reconnect. Ensure you have the new iqn added to the initiator group before doing this.</P><P></P><P>iqn's are only authenticated at the point at which they login, this is a frequent issue we get in support. Customers only find out when there is a controller failover or they reboot their hosts.</P><P></P><P>Another area to be careful is capitalisation of iqn's, they are case sensitive.</P><P></P><P>Many thanks,</P><P></P><P>Chris</P></BODY></HTML> Fri, 26 Aug 2016 10:05:25 GMT chris24 2016-08-26T10:05:25Z Server migration-server rename with ISCSI connection to volume--possible issue. https://community.hpe.com/t5/array-setup-and-networking/server-migration-server-rename-with-iscsi-connection-to-volume/m-p/6984084#M1143 <HTML><HEAD></HEAD><BODY><P>I'm using Nimble connection manager within a virtual server to connect to volumes.&nbsp; During a server migration, I configured 3 ISCSI volumes to the Nimble SAN via IP and IQN name.&nbsp; After the migration, I renamed the server name.&nbsp; Everything is working fine.&nbsp; However, afterwards, I noticed that the initiator name has changed on the server with the server rename.&nbsp; In my Nimble volume configuration, I configured for IQN and IP address in which the IQN is different from the actual server since the server rename.&nbsp; I would think this would break the ISCSI connection, but it has not.&nbsp; Should I be concerned that something might happen in the future that it will break?&nbsp; I'm wondering if I should disconnect the volumes, reconfigure the Initiator name on the SAN or server, then reconnect the volumes or leave it be?&nbsp; Maybe I just don't understand how ISCSI makes the connection to the volume.&nbsp; Comments.&nbsp; Thanks.</P><P>Rod</P><P></P><P>Example: </P><P>SAN Initiator group configuration:</P><P>IQN:&nbsp; iqn.1991-05.com.microsoft:servername-2012r2.city.st</P><P>IP address:&nbsp;&nbsp;&nbsp; 10.10.10.1</P><P></P><P>Virtual Server Configuration:</P><P>IQN:&nbsp; iqn.1991-05.com.microsoft:servername.city.st</P><P>IP address:&nbsp;&nbsp; 10.10.10.1</P></BODY></HTML> Wed, 24 Aug 2016 19:22:08 GMT https://community.hpe.com/t5/array-setup-and-networking/server-migration-server-rename-with-iscsi-connection-to-volume/m-p/6984084#M1143 rodmn98 2016-08-24T19:22:08Z Re: Server migration-server rename with ISCSI connection to volume--possible issue. https://community.hpe.com/t5/array-setup-and-networking/server-migration-server-rename-with-iscsi-connection-to-volume/m-p/6984085#M1144 <HTML><HEAD></HEAD><BODY><P>Hello,</P><P></P><P>Yes, absolutely disconnect and reconnect. Ensure you have the new iqn added to the initiator group before doing this.</P><P></P><P>iqn's are only authenticated at the point at which they login, this is a frequent issue we get in support. Customers only find out when there is a controller failover or they reboot their hosts.</P><P></P><P>Another area to be careful is capitalisation of iqn's, they are case sensitive.</P><P></P><P>Many thanks,</P><P></P><P>Chris</P></BODY></HTML> Fri, 26 Aug 2016 10:05:25 GMT https://community.hpe.com/t5/array-setup-and-networking/server-migration-server-rename-with-iscsi-connection-to-volume/m-p/6984085#M1144 chris24 2016-08-26T10:05:25Z