- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Server migration-server rename with ISCSI connecti...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2016 12:22 PM
08-24-2016 12:22 PM
I'm using Nimble connection manager within a virtual server to connect to volumes. During a server migration, I configured 3 ISCSI volumes to the Nimble SAN via IP and IQN name. After the migration, I renamed the server name. Everything is working fine. However, afterwards, I noticed that the initiator name has changed on the server with the server rename. 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. I would think this would break the ISCSI connection, but it has not. Should I be concerned that something might happen in the future that it will break? 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? Maybe I just don't understand how ISCSI makes the connection to the volume. Comments. Thanks.
Rod
Example:
SAN Initiator group configuration:
IQN: iqn.1991-05.com.microsoft:servername-2012r2.city.st
IP address: 10.10.10.1
Virtual Server Configuration:
IQN: iqn.1991-05.com.microsoft:servername.city.st
IP address: 10.10.10.1
Solved! Go to Solution.
- Tags:
- iSCSI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2016 03:05 AM
08-26-2016 03:05 AM
SolutionHello,
Yes, absolutely disconnect and reconnect. Ensure you have the new iqn added to the initiator group before doing this.
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.
Another area to be careful is capitalisation of iqn's, they are case sensitive.
Many thanks,
Chris