Hello, everyone!
This is post will share with you how to solve the direct connection between the storage device and Emulex is not automatically recovered issue.
Symptoms
Directly connect hosts to storage devices，after the server is restarted, the initiator is offline in DM, and the multipath software has few paths. The fault can be rectified after the link corresponding to the offline initiator is removed and then inserted.
By default, only one or none of the two paths can be viewed.
Cause
The storage device and Emulex driver are incompatible with the standard protocol. The HBA startup process is abnormal. As a result, the process is suspended and the link establishment is not initiated. The storage device keeps waiting.
Analysis
1. Check the storage alarms. The storage device does not receive the PRLI link setup request from the host.
236495 2020-07-31 08:10 0x100F00D40001 Event Major -- None Host FC initiator (Local port ID CTE0.A.IOM0.P1, Remote port NportID 0xd6, Remote port wwpn 0x100000109b9e79db) has the pure initiator attribute. In the process of setting up the connection, it does not send the PRLI to the array FC driver, so the connection cannot be established successfully.
2. Check the corresponding log. The link setup request sent by the host is not received after the link setup PLOGIN, and the remote end does not send the PRLI alarm.
3. Analyze the debug logs of the host HBA driver. The HBA needs to manually enable and collect the debug logs. The procedure for handling link setup exceptions is as follows:
Solution
1. Emergency recovery: Remove and insert the board and reconnect the board.
2. Workaround: The FC-AL mode change port fc fc_port_id=* mode=FC-AL is recommended for direct connection.
3. Solution: Update the HBA driver or use a switch network.
https://www.broadcom.com/support/download-search?pg=Storage+Adapters,+Controllers,+and+ICs&pf=Storage+Adapters,+Controllers,+and+ICs&pn=LPe16000B+FC+Host+Bus+Adapter&pa=&po=&dk=&pl=
This is my solution, how about yours? Go ahead and share it with us!
