Under Advanced Adapter Settings
2) Change Max Throttle to 20
3) Change Max Luns to 128
When exiting Fast!Util, save all changes and reboot.
III. QLA2100F SOLARIS X86 DRIVER ISSUES
The only known driver issue is related to a hub configuration. In a hubless or
hub
configuration the qla2100 driver 2.20 is designed to have an option of holding
I/O
indefinitely in the case the link is broken to the Symmetrix or the Symmetrix FA
goes offline.
In the Hub environment, the only exception to this is if one port of the
symmetrix is
offline and then another port on a hub configuration link is broken. This will
send a
Loop initialization primitive sequence around the loop which the driver
interprets
as the Symmetrix being back online which will initiate the qla2100 driver to
start
executing and returning all holding commands.
1. HOST DRIVER CONFIGURATION VARIABLES
The following variables are found in the file /kernel/drv/qla2100.conf. The
proper setting for driver configuration is crucial to Symmetrix and host
integration.
Each HBA has its own settings for each of the 17 variables in the
/kernel/drv/qla2100.conf file. (For example, if there are three QLA2100F
HBAs installed, a variable must be created for each HBA.)
Example In the example below, a separate variable line is dedicated to
each HBA (hba0, hba1, and hba2).
# Adapter hard loop ID enable.
# 0 = disable, 1 = enabled
hba0-enable-adapter-hard-loop-ID=1;
hba1-enable-adapter-hard-loop-ID=1;
hba2-enable-adapter-hard-loop-ID=1;
# Adapter hard loop ID.
# Range: 0 - 126
hba0-adapter-hard-loop-ID=125;
hba1-adapter-hard-loop-ID=125;
hba2-adapter-hard-loop-ID=125;
Note: Using the same hard loop ID for all HBAs is a valid configuration only in
a hubless loop connection.
Each HBA variable line in the qla2100.conf file corresponds to the instance
number of the HBA in the /var/adm/messages file. In the above example, hba0
of hba0-enable-adapter-hard-loop-ID=1 corresponds to instance #0 in the
/var/adm/messages file.
Komentáře k této Příručce