***************************************************************************** Solaris_Sparc_FC10_ReadMe.TXT ***************************************************************************** Installation Guide for the LSI Logic itmpt Solaris Sparc driver and utility package. This driver supports: o LSI Fibrechannel HBAs for the Solaris 10 Operating System This file contains these sections: Introduction for Solaris SPARC Driver Features Devices Supported Device Mapping Fibre Channel Persistent Binding Configuration Options Installing the Driver in Existing Systems Installing the Driver in an New System 1.0 Introduction for Solaris SPARC ................................ The LSI Logic driver, itmpt, allows the Solaris SPARC operating system to interface with the devices connected to the LSI Fibre Channel host adapters. The driver is optimized for low CPU overhead and high I/O throughput, making use of the LSI Logic Fusion-MPT architecture. The driver conforms to the Sun FCA driver standard. 1.1 Driver Features ................... The Solaris SPARC driver supports these features: o Fibre Channel protocol o PCI, PCI-X and PCIe bus protocols o LSI Logic MPT common software interface o Multiple host adapters o Multiple Logical Unit Numbers (LUNs) o Scatter-Gather o SCSI pass-through functionality o Disk array configurations with no LUN 0 o Disk array configurations with non-contiguous LUNs o Auto request sense o Multiprocessor environments. 1.2 LSI Logic Devices Supported ............................... The LSI Solaris SPARC driver supports all LSI Fibre Channel adapters. 1.3 Device Mapping .................. The itmptfc driver reads the /kernel/drv/ssd.conf file to determine configuration options. The driver automatically probes all Fibre Channel targets attached to the link, and no longer requires explicit device entries conf file to determine which devices to probe. Root Boot persistent target ID selection is configurable through the BIOS. 1.4 Fibre Channel Persistent Binding ..................................... The /kernel/drv/itmpt.conf configuration file may be optionally used to configure Fibre Channel persistent bindings. Note that the default behavior is to map targets by World Wide Name. It is important to use the "port" wwn for the device you want to map, rather than the "node" wwn, or only part of the wwn. The wwn displayed in the boot log or displayed by probe-scsi-all at the OBP (ok) prompt is the correct wwn to use (i.e. the port wwn). If the device was connected to the Fibre Channel bus via port A, the port wwn for that device would generally be: 2100002037102d0f If the device was connected to the Fibre Channel bus via port B, the port wwn for that device would generally be: 2200002037102d0f Many times the wwn printed on the physical device is only part of the full wwn. For example, for the wwn used in the preceeding example, the wwn listed on the disk case itself is: 002037102d0f Optionally, targets may be mapped by their Port ID. To map according to the Port ID, the firmware must be reconfigured. You can use the 'lsiutil' utility to make this change. Run the utility, choose the adapter to work on, then choose menu item number 13 (Change FC port settings). When asked the question: Assignment of Bus and Target IDs: enter a '1' to "sort by DID" rather than "sort by WWN". - To persistently map a Fibre Channel World Wide Name (wwn) to a target device, use this syntax: target-X-wwn="port wwn" For example: target-4-wwn="2200002037102d0f" will persistently map the wwn 2200002037102d0f to target 4 across all HBA ports. - To restrict the mapping to a single bus, use the syntax: hba-X-target-Y-wwn="port wwn" For example: hba-1-target-4-wwn="2200002037102d0f" will persistently map wwn 2200002037102d0f to target 4 on bus itmpt1 only - To persistently map a Fibre Channel Port ID to a given target, use the following syntax: target-X-did="port id" For example: target-4-did="0000ca" will persistently map the port id 0000ca to target 4 on all itmpt busses. 1.5 Configuration Options ......................... The /kernel/drv/itmpt.conf configuration file may be used to configure optional driver parameters. The itmptfc.conf file includes options for SCSI, SAS and Fibre Channel. The following parameters are specific to Fibre Channel: SYM_ADAPTER_FLAGS_ENABLE_ABORT_TASK When set, use Abort Task to abort timed-out I/Os, instead of using Bus Reset and/or Target Reset. SYM_ADAPTER_FLAGS_LOOP_ID_NAMING When set, use LoopIdNaming when possible for fibre channel targets. For targets on a private loop, the AL_PA is converted to a Loop ID, and that Loop ID is used as a target number. For targets not on a local loop, target numbers are assigned starting with 128. scsi-reset-delay This is the amount of time to delay after a bus reset and is reported in milliseconds. The default is 250ms. scsi-watchdog-tick This is how often the timeout handler is executed to walk the active I/O queue looking for I/O's that have timed out. The value is in seconds, default is 5. max-queue-depth This is the maximum number of active I/O's that can be sent to a target at a given time. The default is 32. The minimum settable value is 4 and the maximum is 256. coalesce-count This is the number of I/O's to hold off before interrupting the driver. The minimum count is 0 (turns off coalescing) and the maximum is 128 I/O's. If set to -1, the default value of the firmware is used. coalesce-time This is the time in microseconds to hold off before interrupting the driver. The minimum time is 0 (turns off coalescing) and the maximum settable time is 1000 microseconds. If set to -1, the default value of the firmware is used. 2.0 Installing the Driver in an Existing System ................................................ This section provides installation instructions for existing systems. NOTE: You must be logged on as root to perform the installation. The driver installation is performed using the standard Solaris 'pkgadd' utility. Starting with the itmptfc_install.tar.Z file: 1. Uncompress and un-tar the itmptfc_install.tar.Z file by typing the following commands to create a directory named install: uncompress itmptfc_install.tar.Z tar -xvf itmptfc_install.tar cd install 2. Start the installation by invoking the pkgadd command as: pkgadd -d . 3. Follow the prompts to perform the installation. 4. The itmptfc device driver is now installed. Reboot the machine to reconfigure the system and to recognize the new devices. NOTE: If you change the disk drive configuration of your machine, it may be necessary to issue the command: touch /reconfigure and then reboot the system in order for the system to detect and correctly install your new disks. 3.0 Root Boot Installation .......................... If you are using your LSI Logic adapter to root boot your SPARC Solaris system, you must install the Solaris operating system using a network install. This section describes a complete installation of Solaris to a client system using LSI Logic adapters for the system disk. The method described in this section allows you to install the LSI Logic itmptfc driver onto a network boot kit, making it available during the SPARC installation process. If you are simply installing an LSI Logic adapter as an additional storage adapter in an existing system, use the driver installation procedure described in the previous section. 3.1 Setting up a Boot/Install Server .................................... Refer to the "Preparing to Install Solaris Software Over the Network," section of the Solaris Advanced Installation Guide, available at http://docs.sun.com. The basic steps to set up a boot and install server are as follows: Step 1. Insert your Solaris distribution CD in your boot/install server's CD-ROM drive. Step 2. Change your directory to the Tools area on your distribution CD: cd /cdrom/cdrom0/Solaris_2.7/Tools Step 3. Use the setup_install_server script to copy the boot and installation files to your boot/install server: ./setup_install_server /export/home/install 3.2 Installing the itmptfc Driver on the Boot/Install Server .......................................................... After you have set up your network boot and install server, follow these steps to run the install.sh script with the -n parameter to copy the driver kit to the boot server's boot files: Step 1. Place the diskette in the floppy drive and execute the volcheck command to ensure the system sees the floppy. Step 2. Change the directory to the root of the floppy: cd /floppy/floppy0 Step 3. Execute the install.sh shell script to add the itmptfc driver to the boot installation area: ./install.sh -n /export/home/install/Solaris_2.x Notes: o For Solaris 2.8 boot files, the directory would be /export/home/install/Solaris_2.x. o The message "major number maximum based on server, not client" can safely be ignored. Running the install.sh script this way copies and installs the LSI Logic drivers into the Tools/Boot/ area of the boot files and allows LSI Logic adapters to be booted for installation using the bootserver. 3.3 Adding Clients to Your Boot/Install Server .............................................. For each machine that boots into the boot/install server, follow these steps to add a client entry on the boot/install server: Step 1. Change the directory to the boot/install kit: cd /export/home/install/Solaris_2.x/Tools Step 2. Use the add_install_client script to add the client machine ./add_install_client -i ipaddr -e ethernetid client_name platform_group Where: ipaddr is the tcp/ip address of the client ethernetid is the ethernet hardware (mac) address of the client client_name is the client's system name platform_group is the client's vendor defined hardware group Example: ./add_install_client -i 192.168.103.124 -e 00:08:26:02:25:34 sunsys sun4u Note: You can obtain the platform_group from a machine of the same type as the target client using the uname -m command. 3.4 Booting the Client Using the itmptfc Driver .............................................. Now you can begin the installation of the Solaris operating system to the client target machine using the boot and install server. On the client machine, boot the network install kit you created in the preceding steps as follows: ok boot net -v Note: It is important to choose "Manual Reboot" rather than "Auto Reboot" during the installation of Solaris on the target machine. If you choose "Auto Reboot", you will not have the opportunity to complete the installation of the LSI Logic drivers and your system will fail to boot. After the installation has completed and the system is waiting to be manually rebooted, proceed to a console window and run the following script: /sbin/itmptfcinst This copies and installs the drivers from the boot server to the newly created Solaris installation. After this script has been run, the LSI Logic device driver installation is complete and the system can be rebooted. Notes: The message "major number maximum based on server, not client" can safely be ignored. Your Sun machine will prompt you to allow power saving automatic shutdown. You must answer no to this question if you are using the LSI Logic adapter to support your boot disk. If you change the disk drive configuration of your machine, it may be necessary to issue the command: touch /reconfigure and then reboot the system in order for the system to detect and correctly install your new disks.Download 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.