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

18

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.

Other related questions:
Solution if LUNs fail to be detected after the host initiator or HBA card is changed
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.

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

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.

Problem and solution when some LUNs fail to be mapped when LUNs are mapped in batch
After LUN mappings are canceled in batch in a storage system, the LUNs generated on a host still exist. As a result, the storage system returns "Unmapped" with error code 0x05/0x25/0x00 due to I/Os sent using these LUNs. The interface protocol indicates that the error code performs a LUN switchover but the storage system uses a system lock for the LUN switchover. As a result, LUN mapping fails because no system lock can be obtained. To solve this problem, map the LUNs again. Then check whether the number of LUNs that are successfully mapped is correct.

Problem and solution when the WWN of the application server cannot be detected on the storage device due to the point-to-point mode of the HBA port
You can perform the following operations when WWN of the application server cannot be detected on the storage device due to the point-to-point mode of the HBA port: by going Failure to Detect the WWN of the Application Server Because the HBA Port Is Set to Point to Point page.

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