SANsurfer FC CLI Application Notes Release Date: 07/30/2004 SANsurfer FC CLI Notes 1. For information on installation instructions and options make sure to review the SANsurfer FC CLI User's Guide. 2. On Windows, the ConfigRequired parameter in the registry dictates how devices would show up to the OS. If ConfigRequired=0, both persistently bound and new devices would show up as enabled. This includes devices that might have been previously unconfigured using the application. If ConfigRequired=1, only persistently bound devices would show up as configured. New devices or devices that were previously unconfigured using the application would show up as unconfigured. 3. On Linux, the "options qla2x00 ConfigRequired=1 ql2xxuseextopts=1" string is still in etc/modules.conf after deleting the Persistent Configuration. One must manually delete this entry if a configuration is not used anymore. 4. Under Linux, when running with standard (non failover) driver, the ConfigRequired=1 is ignored, which means the device will be automatically configured by the driver if no persistent binding entry is found. When running with failover driver, the ConfigRequired=1 means a device must have the matching config entry for the driver to configure it. 5. On Solaris, the qla_mp_config_required parameter in the registry dictates how devices would show up to the OS. The qla_mp_config_required 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 Manager. SANsurfer FC CLI sets the qla_mp_config_required flag to 1 by default. If qla_mp_config_required 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 qla_mp_config_required is set to 0, both persistently bound and new targets are reported to the OS. This is equivalent to 'persistent plus new'. SANsurfer FC CLI does not allow the user to change qla_mp_config_required from the application. If the user wants to change the value of this flag, the configuration file must be manually edited. SANsurfer FC CLI and SANsurfer HBA Manager honors this change and preserves the value of qla_mp_config_required when writing target configuration data in the configuration file. In other words, if the user sets qla_mp_config_required to 0, it will continue to be 0 until changed manually again. Note: SANsurfer FC CLI does not read in the value of the persistent-binding-configuration parameter from the configuration file. Support to read this parameter will be added in the next release. 6. For Linux SuSE SLES 8 ia64 machine, user needs to specify the install option flag "--nodeps" to bypass the dependency check before installing the rpm package. For example: rpm -iv <scli-x.xx.xx-xx.ia64.rpm --nodepsDownload Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.