Product guide
Table Of Contents
- Installing and Configuring the HBA and Driver
- Configuring a Boot Device on the EMC Storage Array

22
EMC Fibre Channel with QLogic Host Bus Adapters in the Solaris Environment
Installing and Configuring the HBA and Driver
a. In a hub environment, the hard loop ID for each HBA must be unique.
b.
qla2300.conf only.
Descriptions of
qla2x00.conf
variables
hba0-max-frame-length — Maximum Fibre Channel frame size
(512, 1024 or 2048 bytes).
hba0-execution-throttle — Maximum number of commands (1 to
65535) sent to the LUN by the FCode. Exceeding a device’s
capabilities causes unnecessary command retries, which impact
performance.
hba0-login-retry-count — Maximum number (0 to 255) of retries to
attempt when login into a device fails. Large values can cause long
delays during initialization.
hba0-enable-adapter-hard-loop-ID — Enables/disables the hard
loop ID and activates (if enabled) the setting for variable
hba0-adapter-hard-loop-ID. (See the next item.)
hba0-adapter-hard-loop-ID — Sets (if activated) the hard loop ID (in
the range 1 to 125) for the HBA during the Loop Initialization Process
(LIP). If
hba0-enable-adapter-hard-loop-ID and
hba0-adapter-hard-loop-ID are not set as shown in the table, the
LIP might fail and the host might not recognize the EMC storage
array. These variables become crucial in a hub environment, since no
device (storage array target or host bus adapter) can have the same
hard loop ID. The host HBA is conventionally assigned the highest
Hard Loop ID, starting from 125 and working down (124, 123, 122,
etc.). The EMC storage array is conventionally assigned a lowest
Hard Loop ID for each port, starting with 0 and working up (1, 2, 3,
etc.).
hba0-queue-full-retry-count 16 16 16
hba0-queue-full-retry-delay 2 2 2
hba0-security-protocols
b
00 0
hba0-FDMI-support 0 0 0
hba0-VDP-support
b
00 0
Table 4 Variables in /kernel/drv/qla2.x00.conf (continued)
Variable Default value
Recommended Setting
If No PowerPath or VERITAS
DMP
If PowerPath or
VERITAS DMP