[T Series]Connecting a Storage Device to an Emulex LP1150 HBA

Publication Date:  2012-07-19 Views:  253 Downloads:  0
Issue Description
Product and version information: 
S5500T V100R001 V100R002
S5600T V100R001 V100R002
S6800T V100R001 V100R002
Application server operating system: Windows Server 2008 R2 Enterprise

The storage device and the application server were on a DAS network as shown in Figure1.

  Figure 1 DAS network



In this networking environment, when we performed the following operations, we found on the storage device that the host initiator's status was Link Down.

HBA: Emulex LP1150 (driver:, FC HBA Firmware version: 2.10A10, FC HBA BIOS version: 1.70a3)
Modify the rates or modes of the FC host port on the storage device and the HBA on the host.
Remove and reinsert the optical fiber that connects the storage device to the application server.
Alarm Information
Handling Process
1. Log in to the CLI and run the setportparam command to change the latency for the FC host port to send FLOGI commands to 500 μs.
   To change to the latency, use the command
   setportparam -c controller ID -b subboard ID -p port ID -d flogin delay times
       where -c controller ID is the ID of the controller managing the FC host port that is connected to the Brocade 825 FC HBA, -b subboard ID is the ID of the interface module housing the FC host port, -p port ID is the ID of the FC host port, and -d flogin delay times is the latency for sending FLOGI commands. For example, setportparam -c a -b 1 -p 1 -d 500 changes the latency to 500 μs for FC host port 1 on interface module 1 managed by controller A to send FLOGI commands.
2. Log in to the ISM and expand the storage node, and then choose Device Info > Ports in the navigation tree.
3. Select the FC host port and right-click it.
4. Choose Modify in the shortcut menu.
5. In the Modify FC Port dialog box, set Mode to Point to Point.
Root Cause
The driver of the Emulex LP1150 HBA does not comply with protocol criterion. This led to the initiator's Link Down.
To avoid this trouble, do not modify the rate or mode of any FC host ports that are connected to application servers.
The following shows the storage device log analysis:
//[2011-06-03 15:10:33][208904][15000040e1022][WARN][DRV_SPEED_AUTO
//[2011-06-03 15:10:35][209314][15000040e0e4f][WARN][PortID(0x110100) O
nline and bad alpa receive reg is 0xff00f7][FC_TGT][PF_PortOnlineAction
//[2011-06-03 15:10:35]<----FLOGI(0x0):0x22fffffe 0x00000000 0x01290000
 0x00000000 0x11ecffff 0x00000000 0x04000000 0x20090029 0x00000800 
//[2011-06-03 15:10:35]---->LS_ACC:0x23000000 0x00fffffe 0x01980000 0x4
d000000 0x11ec01a6 0x00000000 0x02000000
//[2011-06-03 15:10:35]---->FLOGI:0x22fffffe 0x00000000 0x01290
000 0x4e
000000 0x01a7ffff 0x00000000 0x04000000 0x09080010 0xe0000800 
//[2011-06-03 15:10:35]<----PLOGI(0x0):0x220000ef 0x000000d6 0x
01290000 0x00000000 0x11ebffff 0x00000000 0x03000000 0x20090029 0x80000
//[2011-06-03 15:10:35]<----LS_ACC(0x0):0x23000000 0x00fffffe 0
x01980000 0x00000000 0x01a711ea 0x00000000 0x02000000
//[2011-06-03 15:10:35]---->LS_ACC:0x230000d6 0x00000000 0x0198
0000 0x51000000 0x11eb01a8 0x00000000 0x02000000
We can see in the log analysis that when the FC host port was linked up, the storage device immediately sent an FLOGI command to which the Emulex LP1150 HBA returned an ACC. Then, because the storage device is the master of the P2P, it had to send a PLOGI command to allocate NportID to the other side. However, we can see from the process that the FLOGI command was between the FLOGI command sent by the storage device and the ACC returned by the HBA. This led to a response frame issue on the Emulex LP1150 HBA, and the HBA recorded its address as 0. This resulted in a failure to set up a connection between the storage device and the application server.