Filter
Top Products
System Overview
Non-Windows Configuration Parameters
2-12 SN0054651-00 F
S
Step 6: Configure the Disks in the Operating System
After completing all hardware and configuration for FC subsystems, use the
appropriate operating system utilities to enable devices, assign drive letters or
logical names, and initialize file systems for each device or LUN on the system.
Step 7: Install the IP Communications Driver
As an option, you can install the IP communications driver. To use the NDIS driver
to enable IP traffic over FC, install that device driver and its configuration utility.
Non-Windows Configuration Parameters
This section lists specific configuration parameters for Linux, Macintosh, and
NetWare.
Linux Enhanced Driver Parameters
QLogic configuration parameters are stored in the modules.conf file in the
/etc subdirectory. For parameter values, see the readme.txt file for the
enhanced driver.
To maintain backward compatibility, if it cannot read the configuration from
persistent storage, the enhanced driver defaults to the previous operation of
configuring and enabling all devices found. Some OEMs indicate that this is an
unacceptable risk when adding a new host to a SAN system; they would rather
configure no devices instead of all devices. The parameter value is
ConfigRequired=1 (TRUE) in Linux.
Macintosh Basic Parameters
QLogic configuration parameters are stored in two files:
/etc/QLogicHBA23xx.conf
/System/Library/Extensions/QLogicHBA23xxConfig.kext/Contents/
QLogicHBA23xxConfig
This is a config module binary.
The qla_opts utility in the source code of Failover API can read the config file
and write to the config module.
NOTE:
If you are using the IOCTL module with the inbox driver or if you are using
sysfs/IOCTL module-based drivers in Red Hat 4.0, persistent
configuration is not saved. Additionally, persistent configuration is not saved
if you are using inbox drivers with SLES 10.0.