Qlogic Fibre Channel Hba Driver For Mac

Posted on 09.01.2020

Qlogic Fibre Channel Hba Driver For Mac Pro
Qlogic Fibre Channel Hba Driver For Mac Windows 10
Qlogic Fibre Channel Drivers

OS Support Products supported: QLA2XX, QLA23XX, QLA24XX, QLE23XX, QLE24XX. Driver currently supports:. MAC OS X Panther Version - 10.3.8, 10.3.9. MAC OS X Tiger Version - 10.4, 10.4.1, 10.4.2, 10.4.3, 10.4.4 2. Supported Features. Persistent Binding. FCAL - direct attach loop.

Point-to-point. Fabric support. Initiator mode only.

Fault recovery on down loop 3. Release History Driver support for 4 Gig HBAs has been added. For detailed history, refer to the release.txt file.

Installing the Driver. 4.1 Installing from the standard Package Installer utility will install the driver in the folder /System/Library/Extensions with root:wheel permission.

4.1.1 Uncompress the Package Uncompress the driver installation package QLogicHBA23xx-x.y.z.tgz as follows:. Open Terminal Application located at /Applications/Utilities/Terminal. Execute the following command to uncompress: # tar -xvzf QLogicHBA23xx-x.y.z.tgz NOTE: Uncompressing generates QLogicHBA23xx-x.y.z.pkg installation package. If the archive is uncompressed using third party utilities, a QLogicHBA23xx-x.y.z folder is generated which contains the installation package named QLogicHBA23xx-x.y.z.pkg. 4.1.2 Install the Driver.

Open the Finder Application. Go to the directory where the driver installation package QLogicHBA23xx-x.y.z.pkg is located.

Double-click on the package icon and wait for the user interface screen to appear. Proceed through the interactive installation GUI interface.

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. NOTE: To load the driver manually without rebooting the system, refer to (Not Recommended) By default all the log messages are logged to the /var/log/system.log file. 4.2 Load the Driver Manually using kextload Before loading the driver manually, please follow. Manual loading/unloading requires Administrative privileges. 4.2.1 Load the Driver Manually using kextload. Execute the following command in Terminal application to load the driver.

# sudo kextload /System/Library/Extensions/QLogicHBA23xx.kext. Enter root password if prompted to continue loading. 4.2.2 Unload the Driver using kextunload. Execute the following command in Terminal Application: # sudo kextunload -b com.qlogic.driver.QLogicHBA23xx.

Enter root password if prompted to continue unloading. 4.3 Unload the Driver Manually using kextunload. Move the installed driver from /System/Library/Extensions to some other folder. Execute the following command in Terminal application: # sudo mv /System/Library/Extensions/QLogicHBA23xx.kext. Enter root password if prompted.

Driver Parameters. 5.1 NVRAM Parameters The NVRAM parameters are read by the driver at initialization time. Some of the NVRAM parameters can be changed dynamically using SANsurfer HBA Manager or SANsurfer CLI application. 5.2 Configuring Driver Parameters from Info.plist The default value of the driver parameters can be changed from the Info.plist file located in: /System/Library/Extensions/QLogicHBA23xx.kext/Contents/ folder. The parameters are in simple format.

Where is one of the following option parameters: Usage:. osfailover - This parameter defines whether MAC OS failover support by driver is enable or disable. 0 to disable failover support.

1 to enable failover support. Default Value: 0. 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 Value: 0 (use value specified in NVRAM). configRequired - This parameter defines how to bind the devices. 0 - Present all the devices discovered to the OS.

1 - Present only the configured devices to the OS. Default Value: 0. Binding method - This parameter defines what type of target persistent binding method to use: 0 - bind by Portname 1 - bind by PortID.

Default Value: 0. ql2xlogintimeout - This parameter defines the Login timeout value in seconds during the initial login. Default Value: 20 seconds. displayConfig - This parameter defines whether to display the current configuration.

1 - display the configuration 0 - don't display the configuration Default Value: 1. maxsrbs - This parameter defines the maximum number of simultaneous commands that can be accepted by HBA driver from SCSI subsystem. Default Value: 256. extendederrorlogging - This parameter defines whether to enable (1) or disable (0) writing the debug information to /var/log/system.log. Default Value: 0 (disable). qfullretrycount - This parameter defines how many times HBA driver will retry the received command with TASKSETFULL status. Default Value: 24.

qfullretrydelay - This parameter defines the time period between 2 retries for a command when received back with TASKSETFULL status. Default Value: 4 secs. qla2x00regtraceenable - This parameter controls whether to display SCSI I/O statistics and driver debugging information in the IORegistery or not.

True - to enable display in IORegistery false - to disable display in IORegistery Default Value: true. qla2x00verbose - This parameter defines whether to enable (true) or disable (false) writing the driver events information to /var/log/system.log during driver initialization time. Default Value: true. qla2x00reinit - This parameter defines whether reinitialize the HBA hardware after loop is down for more than 4 minutes.

True - enable hba hardware re initialization false - disable initialization Default Value: true. qloginretrycount - This parameter defines how many time a fabric login should be retried in case of login failure. Default Value: 0 (use value specified in NVRAM). retrygnnft - This parameter defines how many time a getnodename command should be retried in case of failure.

Default Value: 10 Usage example:. Edit the Info.plist file with Administrative permission. Modify the parameter value in the file. Save the File. Update the system cache for Info.plist settings using following command in Terminal application: #sudo touch /System/Library/Extensions NOTE: OS keeps cache of the driver's Info.plist file.

It is required to update the OS cache when driver parameters are changed by the user. Change in the driver parameters would not reflect if above command is not executed after changing the Info.plist file.

Please reboot the system for changes to take affect. NOTE: Manual Loading/Unloading is not recommended. Please reboot the system for changes to take affect. If you decide to use the manual process, please make sure that the driver has completed initialization. SNIA API Library Package Current Driver Package doesn't contain SNIA API Library Package.

Qlogic Fibre Channel Hba Driver For Mac Pro

Limitations. Manually load/unload the driver using kextload/kextunload is not recommended. Manually unload the driver during Active I/O is never recommended. Cable pulls on the Tape devices during Active I/O phase are not supported. Additional Notes. 8.1 IORegistry Support Driver parameters and HBA related info can be viewed two ways in the system IORegistery.

Using IORegisteryExplorer application located in the /Developer/Applications/Utilities folder. or Type the following command in the Terminal Application: # ioreg -l 8.2 Failover Support MAC OS X has the failover support inbuild in the SAM family and its enabled by default.

MAC OS X Load Balancing and HBA side Failover are supported. At this time MAC OS X does not support Target Side Failover. 8.3 Persistent Binding The Persistent Binding information consists of adapter configuration entries along with target entries.

Persistent Binding can be specified in three ways. (1) Manually or via (2) SANsurfer HBA Manager or (3) SANsurfer CLI. QLogic recommends using SANsurfer HBA Manager or SANSurfer CLI for ease of 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 required by the driver. 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: #grep 'scsi-qla' /var/log/system.log /tmp/info.cfg Persistent binding configuration format is as follows: Device descriptions scsi-qla-adapter-port=; The parameter specifies the FC port name to be used for the adapter, where is the FC port name value in hexa-decimal format.

If this entry is not specified in the conf file, the default value is the adapter's port name as saved in the NVRAM. Example: scsi-qla0-adapter-port=21008d; 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, and 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 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 Target Specifies the path/device id (always 0 for non-failover) name of the device, and is the SCSI target ID to be assigned to the device and is the device unique id.

Scsi-qla-tgt-di-pid=; When Bind setting 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 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. Where Specifies the adapter instance number Specifies the SCSI ID of Target Specifies the path/device id msb lsb 000F The mask above makes the first four luns, 3, 2, 1, and 0 of a given Target disabled on that target/path. This mask specification is heavily type checked to be a sequence of 64 hex digits.

8.4 Configuration Data Configuration/persistent data is read from the configuration KEXT during driver loading time. Normally, configuration data is written via the SANsurfer Management Suite or the scli application.

NOTE: Approximately 300K of configuration space has been pre-allocated within the QLogicHBA23xxConfig KEXT for configuration/persistent data storage. 8.4.1 Compatibility with SMS (SANsurfer Management Suite) qlaopts utility works seamlessly with updated SMS applications.

The information is written to the appropriate QLogicHBA23xxConfig.conf file in /etc and then branded to the binary file of the corresponding configuration module ( QLogicHBA23xxConfig): /System/Library/Extensions/QLogicHBA23xxConfig.kext 9. Known Issues 9.1 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. 9.2 PCI Subsystem fails to detect 4Gb HBA (QLA24xx/QLE246x): PCI Subsystem fails to detect 4Gb HBA when it is flashed to multiboot image version 1.10(24xxmflash110.exe). It is recommended to only use multiboot image version 1.00 (24xxmflash100.exe). Contacting QLogic Please visit QLogic's website.

Unboxing wd elements portable hard drive and reformatting for mac. All other brand and product names are trademarks or registered trademarks of their respective owners.

OS Support The SANSurfer FC HBA Manager is available as OS-specific packages for Microsoft Windows, Red Hat Linux, Novell (SUSE) Linux, Sun Solaris, Apple Mac OS X, and Novell NetWare operating systems. Supported Features The SANSurfer FC HBA Manager provides a graphical user interface (GUI) that lets you easily install, configure, and deploy QLogic Fibre Channel HBAs. It also provides robust diagnostic and troubleshooting capabilities and useful statistical information to optimize SAN performance. Application Notes. For installation options and instructions, see the SANblade FC HBA Quick Start Guide, which you can download from. The default SANsurfer HBA Manager operation password is config. NOTE: Make sure to change this password after installation to ensure security.

To view the SANsurfer HBA Manager online web help, use one of the following browsers:. Internet Explorer (version 6.0 or greater).

Firefox (version 1.0 or greater). Safari (version 1.3 or greater). The SANsurfer HBA Manager application prevents the user from connecting to the same host more than once (to save system resources and address policy issues). This requires that all host IP addresses MUST resolve to a host name to allow the connection to complete.

If your system doesn't use DNS, you must edit the local host file on the system running the SANsurfer HBA Manager GUI and add the host name to IP mapping manually, as defined for your operating system: Windows:: winnt system32 drivers etc hosts Linux: /etc/hosts Macintosh: /etc/hosts Solaris: /etc/hosts NetWare (Windows System's NetWare client):: winnt system32 drivers etc hosts. In SANsurfer FC HBA Manager, the File Choosers don't always respond to a double-click traversal of the file system.

When this happens, select the directory and click the Open button to traverse the directory or open a specific file. Set the video resolution to a minimum of 800x600 with a color palette of at least 256 colors to run the SANsurfer HBA Manager GUI. Uninstalling the software does not remove some files and directories. You must manually delete these files. During SANsurfer FC HBA Manager installation, the system prompts you to select or deselect Enable Failover. When selected (default), failover tells the application how to create and validate the saved configurations. Selecting this option prevents the installation process from loading the platform-specific failover driver automatically.

Windows 2000 and Windows Server 2003 failover requires the driver registry parameters buschange=0 and FixupInquiry=1. You must add these parameters under the following registry keys: HKEYLOCALMACHINE SYSTEM CurrentControlSet Services ql2300 Parameters Device DriverParameters string value. A Windows installation uses the ConfigRequired driver registry parameter to dictate how devices are presented to the OS:. If ConfigRequired=0, both persistently bound and new devices show up as enabled. This includes devices that might have been previously unconfigured using the utility.

Qlogic Fibre Channel Hba Driver For Mac Windows 10

You can set this parameter in the Driver Setting of SANsurfer HBA Manager called: 'Present targets that are persistently bound plus any new target(s) found.' . If ConfigRequired=1, only persistently bound devices show up as configured. New devices or devices that were previously unconfigured using the utility show up as unconfigured. You can set this parameter in the Driver Setting of SANsurfer HBA Manager called: 'Present target that are persistently bound only.' NOTE: When using the new Windows driver (v8.2.0.10 and later), you must explicitly set the ConfigRequired parameter to 1 to prevent unconfigured entries from showing up to the OS.

The administrator account password must not be blank when changing the SANsurfer HBA Manager application password. This is a Windows Server 2003 security restriction. Running SANsurfer HBA Manager on an Itanium I system hinders the application performance due to a Java compatibility issue.

This issue is not seen with Itanium II systems. When updating the Windows driver using the SANsurfer HBA Manager, the driver parameters revert back to their default values:. Present targets that are persistently bound plus any new target(s) found. Bind By World Wide Port Name. When performing a driver update on unsigned Windows drivers, the system displays a confirmation dialog box:.

Qlogic Fibre Channel Drivers

If you are performing the driver update on the localhost and the GUI is connected to localhost (non-agent), the dialog box appears in front of the application (focus). If you are performing the driver update on the localhost and the GUI uses the host name or IP address to connect, the dialog box appears behind the GUI (no focus). To avoid this, you should perform a driver update on the local host, connected as localhost. Targets attached to QLA200 adapter ports have the failover configuration disabled (Windows only). If the targets are shared on other adapter ports (non-QLA200), but the same host, failover is disabled on all paths of the shared target. When connecting to a local host on Windows IA32 or Linux IA32, the system uses a DLL/shared library instead of the agent.

Because there is no communication between the localhost version and the agent, you must use only one or the other, but not both at the same time. When running SANsurfer HBA Manager and connecting to a remote RedHat Linux machine, you must modify the /etc/hosts files on the two machines to allow async notifications from the agent to the GUI to operate properly. To resolve this issue, create a new entry with the host IP address assigned to ethx. Modify the existing entry by moving the hostname from the locahost line to the newly created line. Example Initial: 127.0.0.1 localhost runner.domain.com Modified: 127.0.0.1 localhost 10.0.0.1 runner.domain.com.

With Linux 7.x and Advanced Server 2.1, a new secure portmapper has been included. Add the statement portmap:ALL to the /etc/hosts.allow file to enable remote communication to work properly between GUIs and agents. Before you can change the current SANsurfer HBA Manager password, you must shadow the password option installed on your Linux machine. For example on a Linux 7.2 platform, follow these steps to create the /etc/shadow file:. Install shadow-utils rpm package from /RedHat/RPMS/shadow-utils-20000902-4.i386.rpm. Go to /etc and type the pwconv command to convert the passwords to shadow password format. The Linux system displays the message Warning: Cannot convert string 'x' to type VirtualBinding when running either the GUI or the uninstall; this is a Java issue where the specified key mapping are already defined by the window manager.

You can ignore these warnings since they do not affect the operation of the application. The string options qla2x00 ConfigRequired=1 ql2xuseextopts=1, resides in the /etc/modules file, even after you delete the Persistent Configuration. To completely delete any and all persistent data, you must manually edit this file. When using the non-failover version of the Linux driver, disable failover by launching the Fibre Channel Port Configuration window and de-selecting the Enable Failover Configuration (host) selection under the File menu.

To run the IA32 SANsurfer FC HBA Manager installer under Linux x8664 (EM64T), you must install the IA32 X11 libs. These libs are included in the xorg-x11-libs-.EL rpm. If the libs are missing, the system displays the following exception: java.lang.UnsatisfiedLinkError: /tmp/install.dir.4191/Linux/resource/jre/lib/ i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory. Why doesn't my hard drive show the correct size under LUN information? The system uses two different measurement formats: decimal (GB), which is used by Windows and binary (GiB), which is used by Linux.

Both Linux and Windows provide the 'correct' number. Binary numbers are based on a power of 2. Decimal numbers are based on a power of 10. 2^10 is 1,024 the closest Decimal number is 10^3 or 1,000 2^20 is 1,048,576 The closest Decimal number is 10^6 or 1,000,000 2^30 is 1,073,741,824 The closest Decimal number is 10^9 or 1,000,000,000. On Solaris, the qlampconfigrequired parameter in the registry dictates how devices would show up to the OS.

The qlampconfigrequired flag in the QLogic configuration file ( qla2x00.conf) controls persistent binding of targets. The default configuration file that comes with the QLogic driver does not have an entry for this flag.

An entry for this flag appears in the configuration file only when target configuration data is saved using SANsurfer HBA Manager. SANsurfer HBA Manager sets the qlampconfigrequired flag to 1 by default. If qlampconfigrequired is set to 1, only target devices that are persistently bound in the configuration file are reported to the OS. Any new or unconfigured targets are not reported to the OS by the driver. In other words, the default behavior for this flag is persistent targets only. If qlampconfigrequired is set to 0, both persistently bound and new targets are reported to the OS. This is equivalent to persistent plus new.

NOTE: SANsurfer HBA Manager does not read in the value of the persistent-binding-configuration parameter from the configuration file. On Solaris, you must stop the qlremote agent before using the Hot Swap feature on QLogic FC adapters. Please refer to the hardware manual for detailed instructions.

During normal operation of the SANsurfer FC HBA Manager applications on Solaris, a stale semephore left behind causes all applications to fail on load. To resolve the issue, you must manually remove these two files: /var/tmp/.SEMD /var/tmp/.SEML. Operating the SANsurfer HBA Manager on NetWare 5.x/6.x servers requires the IPX/SPX network protocol.

After completing installation of the Novell NetWare agent, you must start the SANsurfer HBA Manager agent using one of these methods:. Reboot the NetWare server on which you installed the agent. On the console of the NetWare server where the agent resides, type the following command: RPCSTART LOAD QLREMOTE.NLM NOTE: This assumes you have already loaded the QLogic Novell NetWare HAM driver. To run SANsurfer on NetWare, modify the FILES and BUFFERS defined in the boot drive's CONFIG.SYS file to the following settings: FILES = 100 BUFFERS = 50. When uninstalling the SANsurfer HBA Manager from a NetWare server, the server's prompt displays the following message: Cannot stat sys:etc/rpcnet.cfg. NOTE: You can ignore this message since it does not affect the NetWare server's operation.

Mac OS X has a bug that affects SANsurfer installer on OS X 10.3.9 systems with the QuickTime 7.0.4 upgrade. This appears to only affects systems running 10.3.9, and not 10.4. The current workaround is to revert to QuickTime 7.0.1, through a reinstaller available from Apple on the Support/Downloads page.

After updating to Mac OS X 10.3.9, SANsurfer does not install and start. SANsurfer is a Java application and is affected by this Java issue. Review article: 4. 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 2006.

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