Package Contents The following table describes the contents provided in the Mac OS FC HBA driver package. Filename Description QlogicHBA2xxx-.pkg Installer package binary readme.txt Text file version of this readme file release.txt Release notes revision.notes Revision history 2.

OS Support The Mac OS FC HBA driver is compatible with the following OS platforms:. Mac OS X Panther Version 10.3.8 and above (PPC). Mac OS X Tiger Version 10.4.10 and below (Intel and PPC) 3. Supported Features. Persistent Binding. FCAL - direct attach loop. Point-to-point.

Fabric support. Initiator mode only. Fault recovery on down loops 4. Installing and Loading the Driver This section provides procedures for installing and loading the driver. It includes the following sections:. 4.1 Installing from the Standard Package The installer utility installs the driver in the folder /System/Library/Extensions with root:wheel permission. This section provides the following subsections:.

4.1.1 Uncompress the Package To uncompress the driver installation package QLogicHBA2xxx-x.y.z.tgz:. Open Terminal Application located at /Applications/Utilities/Terminal. Run the following command to uncompress: # tar -xvzf QLogicHBA2xxx-x.y.z.tgz NOTEs:. If the driver installation package has a.tar extension, uncompress it by entering the following command: #tar -xvf QLogicHBA2xxx-x.y.z.tar.

Uncompressing the file generates a QLogicHBA2xxx-x.y.z.pkg installation package. When uncompressing the driver installation package using third-party utilities, it generates a QLogicHBA2xxx-x.y.z folder, which contains the installation package named QLogicHBA2xxx-x.y.z.pkg. 4.1.2 Install the Driver To install the driver:. Open the Finder Application. Go to the directory where the driver installation package ( QLogicHBA2xxx-x.y.z.pkg) is located. Double-click the package icon and wait for the user interface screen to appear.

Proceed through the interactive installation GUI interface. NOTE: If running the installer as a non-administrator account, when the installation interface prompts for the Administrator password, enter the administrator password to install the driver. Reboot the system for the newly installed driver to be loaded.

NOTEs:. To load the driver manually without rebooting the system, refer to (not recommended). By default the system records all the log messages to the /var/log/system.log file. 4.2 Loading the Driver Manually. Before loading the driver manually, follow.

Hp Hba Drivers

Manual loading/unloading requires Administrative privileges. This section provides the following subsections:. 4.2.1 Using kextload To load the driver manually using kextload:. Run the following command in the Terminal Application: # sudo kextload /System/Library/Extensions/QLogicHBA2xxx.kext.

Enter root password if prompted to continue loading. 4.2.2 Using kextunload To unload the driver using kextunload:.

Run the following command in the Terminal Application: # sudo kextunload -b com.qlogic.driver.QLogicHBA2xxx. Enter the root password if prompted to continue unloading. 4.3 Preventing Driver from Automatically Loading at Boot Time To prevent the driver from loading automatically at boot time:. Move the installed driver from /System/Library/Extensions to some other folder. For example, run the following command in the Terminal Application: # sudo mv /System/Library/Extensions/QLogicHBA2xxx.kext.

Enter root password if prompted. Driver Parameters This section describes the driver parameters. It includes the following sections:. 5.1 NVRAM Parameters The driver reads the NVRAM parameters at initialization time. You can change some of the NVRAM parameters dynamically using the SANsurfer FC HBA Manager or SANsurfer FC CLI application. 5.2 Configuring Driver Parameters from Info.plist You can change the default value of the driver parameters in the Info.plist file, which is located in the /System/Library/Extensions/QLogicHBA23xx.kext/Contents/ folder. The parameters use a simple format where is one of the parameter options shown in the following table.

Driver Parameters Parameter Option Description Default/Range osfailover This parameter enables/disables MAC OS failover support by driver is enable or disable. Default: True 0 - Disable failover 1 - Enable failover qlportdownretry This parameter defines how long to wait for a port that returns a PORT-DOWN status before returning I/O back to the OS. Default: 0 (use value specified in NVRAM) configRequired This parameter defines how to bind the devices. Default: 0 0=Present all the devices discovered to the OS 1=Present only the configured devices to the OS ql2xlogintimeout This parameter defines the Login timeout value in seconds during the initial login. Default: 20 seconds displayConfig This parameter defines whether to display the current configuration. Default: 1 1=Display the configuration 0=Don't display the configuration maxsrbs This parameter defines the maximum number of simultaneous commands that can be accepted by HBA driver from SCSI subsystem.

Default: 1024 extendederrorlogging This parameter defines whether to enable (1) or disable (0) writing the debug information to /var/log/system.log. Default: 0 (disable) 1=Enable writing the debug information 0=Disable writing the debug information qfullretrycount This parameter defines how many times HBA driver will retry the received command with TASKSETFULL status. Default: 24 qfullretrydelay This parameter defines the time period between 2 retries for a command when received back with TASKSETFULL status. Default: 4 secs qla2x00regtraceenable This parameter controls whether to display SCSI I/O statistics and driver debugging information in the IORegistery or not. Default: true true=Enable display in IORegistery false=Disable display in IORegistery qla2x00verbose This parameter defines whether to enable (true) or disable (false) writing the driver events information to the file /var/log/system.log during driver initialization time. Default: true true=Enable writing driver events false=Disable writing driver events qla2x00reinit This parameter defines whether to reinitialize the HBA hardware after the loop is down for more than 4 minutes.

Default: true true=Enable HBA hardware re-initialization false=disable initialization qloginretrycount This parameter defines the number of fabric logins that should be retried in case of a login failure. Default: 0 (use value specified in NVRAM) retrygnnft This parameter defines the number of getnodename commands should be retried in case of failure.

Default: 10 Example The OS keeps a cache of the driver's Info.plist file. To change driver parameters using the Info.plist file:.

Edit the Info.plist file with Administrative permission. Modify the parameter values in the file. Save the Info.plist file. Update the system cache with Info.plist settings using following command in Terminal Application: #sudo touch /System/Library/Extensions. Reboot the system for changes to take effect. NOTE: Manually loading or unloading is not recommended.

Reboot the system to make any changes take effect. If you decide to use the manual process, make sure that the driver has completed initialization. SNIA API Library Package The current driver package does not contain the SNIA API Library Package. Limitations. Manually loading and unloading the driver using kextload/kextunload is not recommended.

Manually unloading the driver during an active I/O is never recommended. Pulling cables on the tape devices during an active I/O phase is not supported. Additional Notes The section provides the following additional information:. 8.1 IORegistry Support You can view driver parameters and HBA-related information using either of the following methods in the system IORegistry:. Using IORegisteryExplorer application located in the /Developer/Applications/Utilities folder.

Typing the following command in the Terminal Application: # ioreg -l 8.2 Failover Support Mac OS X has the failover support in the SAM family; it is enabled by default. It supports Mac OS X Load Balancing and HBA-side failover. At this time, the Mac OS X does not support target side failover. Mac OS failover support is prone to workloop dead lock which sometimes causes I/Os to hang when HBAs are in multi-pathing configuration. 8.3 Persistent Binding The persistent binding information consists of adapter configuration entries along with target entries. You can specify persistent binding using any of the following methods:.

Manually. Using the SANsurfer HBA Manager.

Using the SANsurfer CLI QLogic recommends using SANsurfer HBA Manager or SANsurfer CLI since those applications are easier to use. The driver displays the current configuration in /var/log/system.log file, when the displayConfig option is set to 1. The configuration information is in the format the driver requires. The best way to extract configuration messages is to use the grep command and direct the output to a file. You need to remove the Mac OS timestamp at the beginning of each message and combine them together on single line. For example: #grep 'scsi-qla' /var/log/system.log /tmp/info.cfg Persistent binding configuration uses the format described below. Scsi-qla-adapter-port=; The parameter specifies the adapter's FC port name where is the FC port name value in hexadecimal format.

If this entry is not specified in the conf file, it uses the default value for the port name, saved in the NVRAM. For example: scsi-qla0-adapter-port=21008d; The host adapter instance 0 has a portname of 21008d. Scsi-qla -tgt- -di- -node=; This parameter associates the specified with the SCSI target ID value specified by and a device ID value specified by, where type is the FC node name of the device, is the SCSI target ID to be assigned to the device, and is the device unique ID. Where Specifies the adapter instance number Specifies the SCSI ID of the target Specifies the path/device ID scsi-qla -tgt- -di- -port=; This parameter associates the specified with the SCSI target ID value specified by and a device ID value specified by, where type is the FC port where Specifies the adapter instance number Specifies the SCSI ID of the target Specifies the path/device ID (always 0 for non-failover) The name of the device, is the SCSI target ID to be assigned to the device, and is the device unique ID. Scsi-qla -tgt- -di- -pid=; When Bind is set to Bind By Port ID in Info.plist settings, this parameter associates the port ID specified by with target ID specified. Where Specifies the adapter instance number Specifies the SCSI ID of the target Specifies the path/device ID Specifies the port ID. Scsi-qla -tgt- -di- -disabled=; This parameter associates the specified with the SCSI target ID value specified by and a device ID value specified.

Linux Hba Driver

Where Specifies the adapter instance number Specifies the SCSI ID of the target Specifies the path/device ID msb lsb 000F The mask above disables the first four LUNs, 3, 2, 1, and 0 of a given target on that target/path. This mask specification is heavily type checked to be a sequence of 64 hexadecimal digits. 8.4 Configuration Data Configuration/persistent data is read from the configuration KEXT during driver loading time. Normally, the SANsurfer FC HBA Manager or the scli application writes the configuration data.

NOTE: Approximately 300K of configuration space has been pre-allocated within the QLogicHBA2xxxConfig KEXT for configuration/persistent data storage. The qlaopts utility works seamlessly with updated SANsurfer FC HBA Manager applications. It writes the information to the appropriate QLogicHBA2xxxConfig.conf file in /etc and then brands it to the binary file of the corresponding configuration module ( QLogicHBA2xxxConfig): /System/Library/Extensions/QLogicHBA2xxxConfig.kext 9. Known Issues Known Issues Workaround Target Device not Reported during the Name Server Query – Prior to QLogic Fibre Channel SanBox2 Switch Firmware, version 5.0.0.20.00, moving a target from one port to another port of a switch results in the target device not being reported to the driver during Name Server query for the list of devices. None PCI Subsystem fails to detect 4Gb HBA when it is flashed to multi-boot image version 1.10 (24xxmflash110.exe). Use multi-boot image version 1.00 (24xxmflash100.exe) 10.

Contacting Support Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: Web: North America Contact Information Email: Phone: (952) 932-4040 Support contact information for other regions of the world is available at the QLogic website: © Copyright 2007. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation.

All other brand and product names are trademarks or registered trademarks of their respective owners.