Solution if LUNs fail to be detected after the host initiator or HBA card is changed

0

Solution if LUNs fail to be detected after the host initiator or HBA card is changed:
1. Description: What can I do if LUNs fail to be detected after the host initiator or HBA card is changed?
a. The iSCSI Initiator Node Name value of the host is changed.
b. The HBA card (Fibre Channel or SAS) of the host is replaced.
2. Solution:
a. For the iSCSI connection in the front end, change the name of the host initiator to the changed iSCSI Initiator Node Name value.
b. For the Fibre Channel or SAS connection in the front end, add the WWN of the current host's port to the storage array.

Other related questions:
Online expansion methods when LUNs cannot be detected on the host of an OceanStor V3 storage system
SmartThin provides two methods for online expansion: storage pool expansion and thin LUN expansion.

Solution if the host fails to detect LUNs
Solution if the host fails to detect LUNs: Determine the connection mode at the front end. If the Fibre Channel switch is connected, check whether the switch mode has been configured. If the front end uses the Fibre Channel switch, check with the customer that the switch has been correctly configured with zones and assign the storage system and the host to the same zone. If the port WWN is bonded during zone division, check whether the port binding is correct. Alternatively, use optical fibers to directly connect the storage system to the switch and re-scan for LUNs.

Solution to the problem that LUNs fail to be detected when the Emulex FC HBA card is connected to the storage system of R5 or earlier version using switches
Problem description: The host uses the Emulex FC HBA card to connect to the storage system through switches. The storage software version is V100R005C02SPC006 or earlier. The Emulex HBA card does not respond to the query command according to the standard protocol. When the host scans for LUNs, only some LUNs can be detected, or no LUNs can be detected. Product versions corresponding to V100R005C02SPC006 are as follows: S2600: 1.04.05.126.T03; S5000: 1.03.05.126.T03; S6800E: 1.03.03.526.T03 Solution: The array of V100R005C02SPC006 or later has been modified to adapt to the non-standard command format of the HBA card. This problem can be solved by upgrading the version of the array. If the array system software cannot be upgraded, take measures as follows: 1. If no switch is used, use the direct-connection networking mode. 2. Connect the optical fiber between the host and the switch, and then connect the optical cable between the switch and the array.

Solution when the host fails to connect to the array directly using a Brocade HBA card because the rate is modified or the host is restarted
1. Run chgportparam to set a latency of 500 μs for link setting. You can run help -c chgportparam to query the usage. 2. Run chgfcmode to change the port mode of the disk array to P2P.

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