|
Topic |
|
Selections |
|
Select a Solaris task: Installing HBAs/drivers Select a HBA type: QLogic Select a switch type: Brocade |
Contents
· Installing
QLogic HBA(s) on a Solaris host
· Updating QLogic HBA firmware
for Solaris
· Downloading latest QLogic
driver for Solaris
· Installing a QLogic HBA
driver on Solaris host
· Editing the Solaris system
file
· Configuring a QLogic HBA
driver for Solaris failover support
· Adding persistent bindings
to Solaris QLogic kernel files
· Adding LUNs to Solaris
config file for QLogic HBA
· Making LUNs or Devices
available to Solaris
Install/Setup
QLogic HBA/Driver Environment on Solaris
Using various procedures,
this document for Solaris, featuring a QLogic HBA environment describes how to
install and setup host bus adapters and other aspects of a host environment
that deal with managing devices of a storage system. A series of procedures
take you from installing HBAs to installing and setting up HBA firmware and
driver software.
· Installing QLogic HBA(s) on a Solaris host |
||
|
|
Overview
This procedure
describes how to install HBAs on a Solaris host. This procedure is based on content from the following EMC manuals:
You can download these guides from EMC
Online Support (registration required): https://support.EMC.com |
|
|
1. |
Install Adapter in card slot With host system power removed, install
the HBA(s) by following the instructions included with your adapter. The
adapter installs into a single slot and has no user-configurable jumpers or
switches. Repeat the installation steps for each
host in which you are installing Fibre Channel HBAs. |
|
|
2. |
Apply power and boot Reapply power and allow the system to boot
normally. |
|
· Updating QLogic HBA firmware for Solaris |
|||||||||||||||||||||||||||||||||||||
|
|
Overview This procedure
describes how to update the QLogic HBA firmware on a Solaris host. \ This procedure is based on content from the following EMC manuals:
You can download these guides from EMC
Online Support (registration required): https://support.EMC.com Ensure that the
HBA firmware (FCode) is current on the adapter before proceeding with other host
setup tasks. |
|
|||||||||||||||||||||||||||||||||||
|
1. |
Verify Current Firmware To confirm and
obtain the latest version of the FCode, access the QLogic website: a.
From
the root of your system, create a directory from this list:
b. Use a web browser to access the QLogic
website at http://www.qlogic.com. c.
Click
Downloads at the left side of the screen. d.
Click
the EMC link under OEM Models. e.
On
the next page, select EMC SYMMETRIX,
CLARiiON, & CELERRA supported software. f.
Using
the table below, find the appropriate FCode (firmware) file for the HBA(s) in
your system and click the associated Download link to save the file.
|
|
|||||||||||||||||||||||||||||||||||
|
2. |
Untar the FCode file Go into the
appropriate HBA directory; then uncompress and untar the FCode file. |
|
|||||||||||||||||||||||||||||||||||
|
3. |
Record
all device paths Use the format utility to list all of your EMC storage array devices. Write down all storage array device paths
in your system. For example, type
format and press Enter. The output display
is similar to the following: Searching for
disks... done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN36G
cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cf72febf,0 1. c2t1d0
<EMC-SYMMETRIX-5669 cyl 2148 alt 2 hd 15 sec 64> /pci@8,700000/scsi@1/sd@1,0 2. c2t1d1
<EMC-SYMMETRIX-5669 cyl 2148 alt 2 hd 15 sec 64> /pci@8,700000/scsi@1/sd@1,1 3. c3t2d0
<EMC-SYMMETRIX-5669 cyl 2148 alt 2 hd 15 sec 64> /pci@8,700000/fibre-channel@2/sd@2,0 4. c3t2d1
<EMC-SYMMETRIX-5669 cyl 2148 alt 2 hd 15 sec 64> /pci@8,700000/fibre-channel@2/sd@2,1 5. c4t3d0
<EMC-SYMMETRIX-5669 cyl 2148 alt 2 hd 15 sec 64> /pci@8,600000/QLGC,qla@1/sd@3,0 6. c4t3d1
<EMC-SYMMETRIX-5669 cyl 2148 alt 2 hd 15 sec 64> /pci@8,600000/QLGC,qla@1/sd@3,1 ... The device path
of QLogic adapters in your system will be: /devices/pci@8,700000/scsi@1 /devices/pci@8,700000/fibre-channel@2 /devices/pci@8,600000/QLGC,qla@1 The device paths
containing the word scsi and fibre-channel belong to the HBA that has the x86
BIOS installed. The device path
containing word QLGC,qla belonging to the HBA that has the FCode installed. Caution: If
the system has an HBA containing the x86 BIOS, upgrading the HBA to FCode
will change the device path word "scsi" or
"fibre-channel" to "QLGC,qla," which means it will change
the adapter device path name. Therefore, on reboot of the system, Solaris
will: ·
Assign
a new device path for the HBA (affecting any mount points already created). ·
Create
a new driver instance number (affecting driver configuration file
parameters). To resolve these issues, please contact EMC local support for
assistance. Note: If
the x86 BIOS-to-FCode change is made on a new installation prior to creating
mount points and configuring the system, the previous caution does not apply,
since the mount points, driver persistent binding entries, etc., will be
created based on the new device paths. |
|
|||||||||||||||||||||||||||||||||||
|
4. |
Select
the utility The remainder of
this procedure depends on the method that will be used to update the
FCode. To update the
FCode for an HBA use one of the following utilities: ·
qla2x00flash Utility (Go to Step 5) ·
SANblade Control FX Utility (Go to Step 6) |
|
|||||||||||||||||||||||||||||||||||
|
5. |
Using the qla2x00flash Utility: Follow these
steps to use the qla2x00flash utility: a.
Download
the FCode for each HBA by entering the appropriate path on the command line. ·
For
the QLA2200F-EMC: ·
For
the QLA2202FS-E: ·
For
the QLA2342E-SP: ·
For the
QLA246xE-SP: ·
For
the QLE246xE-SP: b.
Repeat
step a for other adapters. c. Reboot the host with the reconfigure
option: d.
After
the system has rebooted, issue the format command to
verify that the device path name changed to QLGC,qla when the FCode was
installed. |
|
|||||||||||||||||||||||||||||||||||
|
6. |
Using the SANblade Control FX Utility: Follow these
steps to use the SANblade utility: a.
Open
the SANblade GUI: b.
Double-click
the host name pin located at the upper left of the GUI to display all QLogic
HBAs installed in the host. c.
Click
the adapter on which you want to update the FCode. d.
At
the Tab dialog, click Utilities. e.
Click
Select Input File and select
the appropriate file name:
f.
Click
Open. g.
Click
Update to update the FCode. h.
Repeat
steps c through h for any other HBA that needs the FCode updated. i.
On
the SANblade GUI main window’s File menu, select Exit to exit the GUI. j.
Reboot
the host with the reconfigure option: k.
Reboot
the host with the reconfigure option: |
|
|||||||||||||||||||||||||||||||||||
· Downloading latest QLogic driver for Solaris |
||
|
|
Overview
This procedure
describes how to grab the latest QLogic driver software from the QLogic
website. When installing
or upgrading drivers, be sure to use the latest versions specified by EMC.
Review the E-Lab Interoperability Navigator (ESM) for the latest information on approved HBAs and drivers. |
|
|
1. |
Download
the HBA driver To download the
latest HBA driver: a.
Create
a directory to which you will save the driver. For example: b.
Use a
web browser to access the QLogic website at http://www.qlogic.com. c.
Click
Downloads at the left side of the screen. d.
Click
the EMC link under OEM Models. e.
On
the next page, select EMC SYMMETRIX,
CLARiiON, & CELERRA supported software. f.
Select
the HBA model in the Product
column of the table. On the next table, find the supported driver and click
the associated Download link. g.
Extract
the downloaded file to the directory created earlier. |
|
· Installing a QLogic HBA driver on Solaris host |
||||||||||||
|
|
Overview
This procedure
describes how to install the QLogic driver on a Solaris host. Refer to the
release notes provided with the driver for information that might be unique
to new driver revisions. Note: The naming convention for the drivers,
associated files, and messages is QLA; however, the Solaris SPARC
driver supports standard QLogic PCI and SBus boards (QLAxxxx). |
|
||||||||||
|
1. |
Uncompress
the driver file Change to the /qlogic_driver directory you created earlier and
uncompress the driver file by entering the following applicable command:
|
|
||||||||||
|
2. |
Install the driver Install the
driver into the host by entering the following applicable command:
A list of
available packages appears. Select an HBA
driver and press Enter. |
|
||||||||||
|
3. |
Select the directory You are prompted
to select the directory into which the driver files will be installed. Press Enter at the next three prompts to
accept the defaults. |
|
||||||||||
|
4. |
Continue the installation The pkgadd program performs a series of checks, then posts a script warning and
asks whether to continue the installation. Type y at the prompt and press Enter to continue the driver installation. |
|
||||||||||
|
5. |
Complete the installation The pkgadd program will notify you when the driver installation is complete. If the driver is
version 4.13 or earlier, reboot the host. Note: There is no reboot required for driver
versions 4.15.03 and later. |
|
||||||||||
|
6. |
Verify the installation Verify that the QLogic
HBA’s FCode is installed. To do this,
view the QLogic device path name in the /var/adm/messages file or from the output of the format command: ·
If
the device path name contains QLGC, qla, the FCode is
already installed. For example: /ssm@0, 0/pci@19, 700000/pci@2/QLGC, qla@5 ·
If
the device path name contains fibre-channel or scsi, the FCode has not yet been
installed. If this is the case, update
the HBA FCode before continuing. For example: /ssm@0,
0/pci@19, 700000/pci@2/fibre-channel@5 |
|
||||||||||
· Editing the Solaris system file |
||
|
|
Overview This procedure describes
how to edit the /etc/system file. Refer to release notes provided with
the driver for information that might be unique to new driver revisions. |
|
|
1. |
Make entry for an I/O timeout and throttle Add a couple of lines
to set the I/O timeout and throttle. This setting prevents the host from
issuing warning messages when non-disruptive operations are performed on the
EMC storage system:
set
sd:sd_max_throttle = 20 |
|
|
2. |
Save the file Save the changes you made to the /etc/system file. |
|
· Configuring a QLogic HBA driver for Solaris failover support |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Overview
This procedure describes how configure the QLogic HBA driver for
failover support on a Solaris host. If using PowerPath or DMP failover software, verify that the installed
HBA drivers will support it. Refer to
the E-Lab Interoperability Navigator (ESM)
for more information. The configuration
file (qla2x00.conf) is created automatically while installing the driver. The file contains important information
about how the driver should behave. If necessary, edit the file as shown in
the following table. For descriptions
of the variables, refer to the EMC Fibre Channel with QLogic Host Bus
Adapters in the Solaris Environment manual, P/N 300-001-163 (available on http://www.qlogic.com). |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
1. |
Make
a copy of the kernel Before editing
the current qla2x00.conf file, use the following applicable
command to make a copy of it in case the file is lost or errors are made: cp /kernel/drv/qla2x00.conf
/kernel/drv/qla2x00.conf.bak Note: Using improper settings can cause erratic
behavior, such as greatly increased I/O delays.
Note A: In a hub
environment, the hard loop ID for each HBA must be unique. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
2. |
Save the changes to the file Save the changes you made to the qla2x00.conf file. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
· Creating switch zones |
||
|
|
Overview
For directions specific to Brocade switches, refer to the Brocade Fabric Manager Administrator’s Guide, which is located on Powerlink under the following location: Home > Support > Documentation/White
Paper Library > Hardware/Platforms Documentation > Connectrix Directors
and Switches > Maintenance/Administration Please refer to
the section Managing Zones, which
will provide the background information needed to configure and zone your
fabric. Note: There are multiple
versions of the user guide available. Be sure to reference the version
specific to your Fabric Manager version. |
|
|
3. |
Create switch zones Switch zones
define paths between the host HBAs and the Symmetrix array and can be created
using the switch management software
(refer to the switch documentation). Note: If you are using an HP-UX server with
QuickLoop zoning, then you must use port zoning. Refer to EMC Knowledgebase article emc66355
for more information. Definition - Zoning is the process by which a single
initiator is matched to a single storage array port (FA/SP) to be able to
pass info to storage array device. A Zone consists of 2 or more members, with
only 1 initiator (HBA) per zone A Zone is part of a zoneset . A Zoneset is a collection of zones in a
single fabric. A Zoneset
requires activation in order to be updated.
Important: EMC Recommends single initiator zoning. To reduce the chance of data
unavailability in the event that an HBA, switch, or FA Failure, the host should have at least one primary
path and one alternate path to each FA |
|
|
4. |
Determine zoning configuration Follow
these steps to determine your zoning configuration: a.
Determine
the FA WWN by entering the following command: b.
Determine
the HBA WWN by referencing the OS-specific commands from provisioning a host
section. c.
Determine
the number of paths needed. d.
Determine
the Active Zone name. |
|
|
5. |
Verify the HBA is logged in Solutions
Enabler offers a command line utility that will verify what is logged in to a
specific Symmetrix FA. Use the following command: symmask –sid SymmID
–dir 3c –p 0 list logins Where
SymmID is
the last four numbers of the Symmetrix serial number, 3c is the FA and 0 is
the port on the FA. It should
also be noted that HBAs in an HP-UX host only show as logged in while there
is active I/O. However, if an entry
exists in the login history table, it indicates that the HBA did log into the
FA at some point. After
verifying that the host is logged in, move on to configuring the host. |
|
Setup Solaris
QLogic kernel config files and add LUNs
The following procedures specific to QLogic HBAs describe how to add
persistent bindings and LUNs to the Solaris kernel config files.
· Adding persistent bindings to Solaris QLogic kernel files |
||
|
1. 1. |
Overview This procedure
explains how to configure one persistent binding per SP port on each HBA in
the QLogic qla2x00.conf file. |
|
|
1.
|
Find
the WWN In the /var/adm/messages file, locate
the keyword WWPN next to the driver instance. For example,
this messages file contains the following entries: qla2300-hbax-SCSI-target-id-0-fibre-channel-port
name=" 50060482c464abec"; qla2300-hbax-SCSI-target-id-0-fibre-channel-port-name="
50060482c464abec"; where x represents the
HBA driver instance. Note: It is possible that you might
find multiple instances of the driver.
If there are multiple
instances, determine which driver you are using before continuing. CAUTION: Verify that you are using the
WWPN of the FA and not the HBA. The
correct WWPN will begin with 5006048nnnnnnnnn. To collect the
FA WWN, execute the following SYMCLI command: symcfg –sid SymmID
list –fa all Subsitiute SymmID with the last four digits of the Symmetrix
Serial Number. |
|
|
2.
|
Create entries for each HBA Open the qla2x00.conf file for your driver and create an entry for each HBA and target
combination using the format: hbax-SCSI-target-id-y-fibre-channel-port-name="PPPP"; where x is the driver
instance number of the HBA, y is the device
address, and PPPP is the target
WWPN of the EMC storage array. The driver
instance can be obtained by looking at the message file, located at /var/adm/messages, search for qlc and you will
see a driver instance Number next to it. Save the changes
you made to the .conf file. |
|
|
3.
|
Reboot
the server Reboot the
server by entering the following command: reboot -- -r |
|
· Adding LUNs to Solaris config file for QLogic HBA |
||
|
1. |
Overview This procedure
adds LUNs to the Solaris QLogic Solaris config file. If you installed driver 4.15.03 or later,
there is no need to edit the sd.conf file and therefore, skip these steps. When editing the
file, follow these precautions: ·
Do not delete any original data from this file;
the Solaris operating system might not boot properly. · Do not insert
hidden format characters. The file is very sensitive to hidden format
characters, and a misplaced tab or other formatting character can make all
subsequent entries unreadable. · Enter all target
and LUN values in decimal format. |
|
|
1. |
Make a copy of the kernel Before editing the current /kernel/drv/sd.conf file, use the
following command to make a copy of it in case the file is lost or errors are
made: cp /kernel/drv/sd.conf /kernel/drv/sd.conf.bak |
|
|
2. |
Modify the config file Modify the config file (/kernel/drv/sd.conf): The default sd.conf file contains entries for LUN 0 only.
Therefore, you must edit the file to add entries for any LUNs with
numbers greater than 0 that you will bind in the storage systems connected to
the server. Devices accessed through Fibre Channel, using
the QLogic driver, are addressed behind a single target ID with up to 256
LUNs. Note: Make sure that only the target=x lun=0 line is specified for
any target ID that does not need LUN support.
This decreases the time needed to reboot the system. Edit sd.conf to list all targets and all LUNs that might be addressed. The Target ID needed to address a device is
determined by the Fibre Channel Arbitrated Loop Physical Address
(AL_PA). A Loop_ID of 00 (AL_PA of EF)
will have LUNs behind Target ID 0, Loop_ID 01 has LUNs on target ID1, and so
on. The following is an example of the
sd.conf file: name="sd"
class="scsi" target=0 lun=0; name="sd"
class="scsi" target=0 lun=1; . . . name="sd"
class="scsi" target=0 lun=255; name="sd"
class="scsi" target=1 lun=0; name="sd"
class="scsi" target=2 lun=0; . . . name="sd"
class="scsi" target=125 lun=0; |
|
|
3. |
After you add all of the LUNs that you think you
will need, save the file and reboot the operating system: reboot
-- -r Note: With a reboot, the host
recognizes the new driver and sets the driver variables. In an FC-SW
topology, the host also adds the new driver instances to its internal list of
drivers. |
|
|
4. |
Verify that Solaris recognizes the devices by
using the format command If Solaris does not recognize any devices,
verify the connection to the Storage array. |
|
· Making LUNs or Devices available to Solaris |
||
|
|
Overview This procedure describes how to make the devices or LUNs available or
visible to a Solaris host. It describes how to use the format command to label and partition
devices. Solaris disk names have the following form: cDtSdLsP where:
For example, if the HBA is 1, the target ID of the FA is 0, and the LUN
number is 2, you would format the disk by entering the following command: format c1t0d2 Note and Caution: If your host system cannot see the
devices, it may necessary to do a disk or device scan of the I/O bus with
this procedure. If you must, at an
appropriate low-peak time in your production environment, apply the necessary
operating system native commands, to perform a device scan (discover) to make
the devices visible to the host workstation. This might take a few minutes or
so to execute. Be sure you follow your operating system specific
administrators guide and/or known site procedures for this operation, as
scanning devices can cause pauses and crashes to other operational processes
running on this host. If you can and prefer, a reboot will also accomplish
the same thing (device discovery). The
following steps are provided only as a general or possible guide and not meant
to supersede your site preferences. |
|
|
6. |
Partition
and label devices: The version of the format command that ships with Solaris has an auto-configure
option that configures devices (disks) for you, as follows: a.
At the root prompt, enter the following command: b.
From the Format
menu, select Available Drive Types. c.
At the Specify
disk type prompt, enter 0 to
select the auto-configure option. d.
If you want to partition the disk, use the format command again. e.
If you have not labeled the disk, label it using the label command. |
|
|
7. |
Create
file systems on partitions: Use the newfs command to make file systems on all newly
created partitions. You must specify a character device name to indicate the
partition where you want to create the file system. For example, to
make a file system on partition 0 on the first disk (device), enter the
following command: newfs /dev/rdsk/c1t0d0s0 |
|
|
8. |
Mount the file systems: This procedure is
the same as for any device used with a Sun operating system. You must use the mount command to mount the
file systems that you have created on your storage system. Specify
the block device name of the partition where you created the file system and
the mount point directory. For example, to mount the file system partition 0 of the first disk
configured, at the mount point /temp, enter the
following command: mount /dev/dsk/c1t0d0s0 /temp |
|