Filter
Top Products
Solaris SFS Driver User Manual Page 162
Migrating from the Solaris lpfc Driver to the Solaris SFS
Driver
If the Emulex lpfc driver for Solaris is already installed, you can migrate to the Solaris SFS driver either
by customizing and running the unsupported sample scripts provided by Emulex, or by manually
performing a set of procedures.
Operational Differences Between lpfc and SFS
Device discovery operation is different between SFS and lpfc as follows:
• lpfc discovers all fabric target devices by default.
• The FCA driver discovers direct-attach and loop targets, but not fabric attached targets, by
default. Use cfgadm to indicate which fabric targets you want the driver to discover.
• Firmware download:
• Sun-branded HBAs: the SFS FCA driver includes the adapter firmware and overrides
any firmware version previously residing on the adapter. You cannot update the firmware
manually.
• Emulex SFS-supported HBAs: the Emulex-provided emlxadm tool provides a
download_fw command. Syntax and details are provided in the Emulex FCA Utilities
Reference Manual.
• Universal Boot download, including OpenBoot (FCode):
• Sun-branded 2-Gb HBAs: use Sun-provided luxadm.
• Sun-branded 4-Gb HBAs: use the Emulex-provided emlxadm tool, which provides a
download_fcode command (syntax and details are provided in the Emulex FCA Utili-
ties Reference Manual).
• Emulex SFS-supported 2-Gb HBAs: use either luxadm or emlxadm.
• Emulex SFS-supported 4-Gb HBAs: use emlxadm.
Sample Script File Details
Emulex provides unsupported sample scripts to help you migrate from the Solaris lpfc driver to the
Solaris SFS driver. These scripts are available on the SFS driver pages on the Emulex web site. You can
customize these scripts and run them to automate the migration process.
start_emlxs_migration.sh
The start_emlxs_migration.sh sample script performs the following tasks:
1. Verifies required packages are installed (3 packages - lpfc driver, leadville driver, and the
HBAnyware Utility).
2. Cleans up any device-dangling links by running the operating system utility: devfsadm -C.
3. Obtains and saves the following information for each HBA in the system:
• OS device name for the HBA (i.e. reflects PCI path).
• OS logical controller number for the HBA.
• Obtains a target number and wwn for all targets configured for each HBA and obtains the
number of Luns configured for each target.
4. Writes data to files.