Why does an application server lose all the LUNs mapped to it after being configured with the 360 Safe software?

5

The cause is that the 360 Safe software disables the iSCSI services. You can manually restart the iSCSI services and scan for the disks, and then the LUNs mapped to the application server can be detected again.

The 360 Safe software disables the iSCSI services; therefore, you are advised to uninstall the 360 Safe software from the application server, and install another security software.

Other related questions:
Method used to safely delete a LUN mapping from an AIX application server
Perform the following operations to delete a LUN mapping from an AIX application server: On the storage device side, delete the LUN mapping with the AIX application server. On the AIX application server side, run rmdev -dl diskName to delete the virtual disk of the mapped LUN. For example, you can run rmdev -dl disk3 to delete the virtual disk disk3. Note: If the virtual disk is not deleted and a new LUN is mapped to the AIX application server, a fault occurs, indicating that the virtual disk path is missing. Rectify the fault as follows: Unmount the file systems of the original LUN and the newly mapped LUN. Close the volume group of the newly mapped LUN. Delete the virtual disks of the original LUN and the newly mapped LUN. Run cfgmgr to re-scan for disks.

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.

For V3 series unified storage V300R001, how can I query the mapping relationship between LUNs and hosts?
For V3 series unified storage systems V300R001, you can obtain the information about LUNs and its mapped hosts from the mapping view. You can identify the corresponding relationship between storage systems' hosts and their connected application servers in the live network through parameters such as host names and host operating systems. You are advised to use a host name that is easy for you to recognize the host's corresponding application server. For details about how to view mapping views, see Viewing Mapping View Information.

Method to query the mapping relationship between LUNs and hosts on T series V100R005 devices
On the T series V100R005 storage system, you can view information about mapped LUNs by checking the host information. You can identify the corresponding relationship between storage systems' hosts and their connected application servers in the live network through parameters such as host names and host operating systems. You are advised to use a host name that is easy for you to recognize the host's corresponding application server. For details about how to check the host information, see Viewing Host Information.

The application server connected to the OceanStor V3 storage system fails to detect LUNs
Refer to Revelations of Troublesolving cases on the right.

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