Sequence of installing iSCSI initiators and UltraPath software on a Windows application server for OceanStor T Series storage systems

0

For the sequence of installing iSCSI initiators and UltraPath software on a Windows application server for T series storage systems, visit the following website:
FAQ-On a Windows application server, what is the installation sequence of iSCSI initiator and UltraPath software for T series storage system

Other related questions:
iSCSI initiator software supported by the application server running various operating systems
iSCSI initiator software supported by the application server running various operating systems: FAQ-Which iSCSI initiator is installed on different operating systems

Method used to query available paths in a storage system after the UltraPath software is installed
You can query available paths in the current storage system after the UltraPath software is installed by going to the FAQ-How Can I Query Which Link is Active in the Current Storage System After the UltraPath Software Is Installed website.

Method used to configure the iSCSI initiator in Windows
You can configure the iSCSI initiator in Windows as follows: Perform basic iSCSI configurations as follows: 1. Check whether the Microsoft iSCSI service has been started. If the iSCSI service has not been started, set the service to automatically start. 2. Open the iSCSI initiator configuration tool. Choose Start > Control Panel and double-click the iSCSI Initiator icon. 3. (Optional) Change the initiator name. On the General tab page, click Change... and modify Initiator node name. The node name must be unique. Note: When the service is running properly, do not modify the node name. Otherwise, services will be interrupted. 4. Add targets. Under Target Portal of the Discovery tab page, click Add. In the Add Target Portal dialog box that is displayed, configure Target IP and the port number. The port number of iSCSI is 3260 by default. 5. On the Targets tab page, click Refresh. You can see all targets. Select all targets in the inactive status and click Logon. Select the first item. 6. On the Computer Management page, choose Storage > Disk management. You can view the LUNs on the disk array. Configure Challenge Handshake Authentication Protocol (CHAP) as follows: 1. On the disk array, configure the CHAP name and password of the initiator. 2. In the Log On to Target dialog box, click Advanced... and configure the CHAP user name and password.

Why does the Windows Multi-Path I/O service remain enabled after the Multi-Path I/O software is uninstalled from and then UltraPath software is installed on a Windows Server 2008 application server?
The multipathing software for Windows Server 2008 relies on the Multi-Path I/O service; therefore, UltraPath software for Windows Server 2008 inherits Windows Multi-Path I/O service architecture and cooperates with Windows Multi-Path I/O service.

Why does an application server fail to detect the mapped virtual disks after being configured with the UltraPath for Windows software?
The possible causes for a virtual disk detection failure include: ? The UltraPath for Windows software is incompatible with the Windows operating system installed on the application server. ? The UltraPath for Windows software is incompatible with the storage array. ? The LUNs are mapped to the application server before being formatted. ? The bit version of the UltraPath for Windows installation package is incompatible with that of the operating system running on the application server. For example, the application server runs a 32-bit operating system but uses a 64-bit installation package. ? The application server does not detect any physical disks, so it cannot produce virtual disks. ? The driver of physical disks is not replaced. The respective troubleshooting measures to the previous six causes are: 1. Confirm that the UltraPath software is installed on its supported operating system. The UltraPath for Windows-supported operating systems are Windows Server 2008 Enterprise Edition x86 SP1 and later, Windows Server 2008 Enterprise Edition AMD64, Windows Server 2003 Enterprise Edition x86 SP1 and later, Windows Server 2003 Enterprise Edition AMD64 SP1 and later, and Windows Server 2000 SP4. 2. UltraPath for Windows only supports the storage arrays from Technologies Co., Ltd. 3. Wait until the LUNs are formatted, and then scan for them on the application server. 4. Ensure that the operating system version is compatible with the installation package. If an inappropriate installation package has been installed, uninstall it first, restart the operating system, and then install the package of the proper version. 5. Check whether the physical links are normal. If they are normal, ensure that the LUNs are normal in the storage array and successfully mapped to the application server. 6. Check that the driver of physical disks is replaced. ? If the UltraPath software is not installed, before the installation, go to the C:\windows\inf directory and open all the inf files starting with oem. In each file, search for the following keywords: MPIODisk, Detected\MPIO, and Root\HWDSM. If a file contains one of the keywords, delete this oem.inf file and its related oem.pnf file. After ensuring that none of the oem.inf files contains the keywords, you can install the UltraPath software. ? If the UltraPath software is already installed, choose Computer Management > Device Manager > Disk Drivers to view the driver information of physical disks. If the driver of a physical disk is not mpdev.sys, the driver has not been replaced. Uninstall the faulty physical disk and rescan for disks. ? During service idle hours, restart the application server.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top