No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Windows hostname change making LUN lost

Publication Date:  2012-10-16 Views:  198 Downloads:  0

Issue Description

System environment:
OceanStor V1800 ,system edition V100R001C02;
Windows Server 2003 Enterprise Edition sp2 server,server hostname slot2;
Microsoft Initiator-2.06-build3497-x86fre iSCSI initiator software;iSCSI Initiator IQN is system default;
when configure log on option in iscsi_initiator property window,the option of Automatically restore this connection when the system boots is selected;
1 LUN from V1800 is discovered successfully in server slot 2
After changed the hostname to slotlab and reboot, LUN mapped to this server cannot be discovered anymore.

Alarm Information


Handling Process

Inspect the configuration on S5500 and server, and the name of iqn in Microsoft iSCSI Initiator is automatically changed to; the option of Automatically restore this connection when the system boots is selected, making original initiator name valid during the connection to storage devices after initiator reboot. Change the iqn name back and log on again, the host can use LUN resource.

Root Cause

There is possibility that after hostname change, some iSCSI configuration in server is also changed.


System automatically generate iqn name in the format of iqn + date + reverse Domain name or naming authorization + hostname, if Windows name is changed, hostname part of iqn will change relatively. System default iqn name can be modified manually, and the iqn name will not change as the hostname change.