ETERNUS Disk storage systems Server Connection Guide ...storage-system.fujitsu.com/global/manual/diskarray/pdf/p3am-2712... · This describes how to set up the QLogic Fibre Channel

P

Preface

This document briefly explains the operations that need to be performed by the user in order toconnect an ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, orETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system to aserver running Solaris OS and using QLogic Fibre Channel cards via a Fibre Channel interface.

This document should be used in conjunction with any other applicable user manuals, such asthose for the ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, orETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system, server,OS used, Fibre Channel cards, drivers, etc.Note that this manual refers the following documents.

� Server Support Matrix� ETERNUS Disk storage systems Server Connection Guide (Fibre Channel)

for Oracle Solaris

Also, note that in this document the ETERNUS2000 models 100 and 200, ETERNUS4000 mod-els 300, 400, 500, and 600, and ETERNUS8000 models 700, 800, 900, 1100, 1200, 2100, and2200 Disk storage systems are collectively referred to as ETERNUS Disk storage systems.

Fourth EditionDecember 2010

The Contents and Structure of this Manual

This document is composed of the following five chapters and an appendix.

� Chapter 1 Workflow

This describes the workflow required to establish a connection between a server with QLogicFibre Channel cards and an ETERNUS Disk storage system.

� Chapter 2 Installing the Fibre Channel Card Driver

This describes how to install the Fibre Channel card driver.

� Chapter 3 Setting Up the Server

This describes how to set up the server for different connection topologies.

� Chapter 4 Logical Unit Recognition

This describes how to make the server recognize the ETERNUS Disk storage system LUNs(logical units).

� Chapter 5 Required Driver Parameters

This describes how to set up the QLogic Fibre Channel card driver.

ETERNUS Disk storage systems Server Connection Guide for Oracle Solaris

3 Copyright 2010 FUJITSU LIMITED

3AM-2712-04ENZ0

Preface

P

An appendix contains the various management tables that are used in "Chapter 3 Setting Up theServer".

Safe Use of this Product

■ Using this manual

This manual contains important information to ensure the safe use of this product. Be sure tothoroughly read and understand its contents before using the product. After reading, store thismanual in a safe place for future reference.FUJITSU has made every effort to ensure the safety of the users and other personnel, and toprevent property damage. When using this product, carefully follow the instructions described inthis manual.

Acknowledgments

� Oracle and Java are registered trademarks of Oracle and/or its affiliates.� All SPARC trademarks are used under license and are trademarks or registered trademarks

of SPARC International, Inc. in the United States and other countries.� QLogic is a trademark of QLogic Corp.� The company names, product names and service names mentioned in this document are

registered trademarks or trademarks of their respective companies.

Naming Conventions

■ Product names

� Oracle Solaris might be described as Solaris, Solaris Operating System, or Solaris OS.

■ Other names

� "Channel Adapter" (CA) refers to the Fibre Channel interface module used in the ETERNUS Disk storage systems to connect to the server.

� "Fibre Channel card" refers to the Fibre Channel interface module normally used by the server. A "Host Bus Adapter" (HBA) or "Channel Adapter" (CA) may be used instead, depending on the server.

� Italics are used to show variables such as values and characters that appear in command parameters and output examples.

Copyright 2010 FUJITSU LIMITED



3AM-2712-04ENZ0



P3AM-2712-04ENZ0

Contents

Chapter 1 Workflow ...................................................................................6

Chapter 2 Installing the Fibre Channel Card Driver................................8

Chapter 3 Setting Up the Server...............................................................93.1 Creating a WWN Instance Management Table for the Server ......................... 103.2 Creating a WWN Instance Management Table for Storage System ................ 143.3 Creating a Target Binding Table ...................................................................... 153.4 Setting the Configuration File ........................................................................... 173.5 Re-checking the Settings ................................................................................. 17

Chapter 4 Logical Unit Recognition .......................................................184.1 Recognizing Logical Units with the sd Driver ................................................... 18

4.1.1 Recognizing Logical Units ......................................................................................................... 184.1.2 Getting the Server to Recognize the Logical Units .................................................................... 19

Chapter 5 Required Driver Parameters..................................................205.1 Setting Up the Parameters ............................................................................... 20

5.1.1 qla2300.conf Parameter Values ................................................................................................ 205.1.2 /kernel/drv/qla2300.conf Example ............................................................................................. 23

Appendix A Various Management Table Templates ................................27A.1 WWN Instance Management Table for the Server ........................................... 27A.2 WWN Instance Management Table for Storage System .................................. 28A.3 Target Binding Table......................................................................................... 28

Chapter 1 Workflow

P

This manual is used when performing the setup procedure described in "Installing the Driver andSetting Up the Server" and "Logical Unit Recognition" of the "ETERNUS Disk storage systemsServer Connection Guide (Fibre Channel) for Oracle Solaris".

Workflow

Fiber Channel Card Driver InstallationInstall the driver. Download the proper driver from the QLogic web-site as required.

- "Chapter 2 Installing the Fibre Channel Card Driver" (page 8)- Driver (downloaded from web-site)- Driver product manual- Used for driver installation

� "SANsurfer FC HBA CLI Application" (downloaded from web-site)

Management Table Creation (Various)Enter the necessary information in the "WWN Instance Management Table for the Server", "WWN Instance Management Table for Storage System", and "Target Binding Table".

- "Chapter 3 Setting Up the Server" (page 9)- "Appendix A Various Management Table Templates" (page 27)

Fiber Channel Card Driver SetupSet the driver parameters by editing the configuration file.

- "Chapter 3 Setting Up the Server" (page 9)- "Chapter 5 Required Driver Parameters" (page 20)

Refer

Refer

Refer



3AM-2712-04ENZ0

Chapter 1 Workflow >

P

After completing all the required procedures in this manual, proceed to "Setting the Multi-paths" in "ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) forOracle Solaris".

Logical Unit (LUN) RecognitionMake the server recognize the ETERNUS Disk storage system logical units using the sd driver.

- "Chapter 4 Logical Unit Recognition" (page 18)

Refer



3AM-2712-04ENZ0

Chapter 2 Installing the Fibre Channel Card Driver

P

Use the following procedure to install the Fibre Channel card driver.

Procedure

1 Download and install the appropriate driver from the QLogic web-site:http://www.qlogic.com (QLogic web-site)

Installation procedures should be available with the driver.

2 Download and install the "SANsurfer FC HBA CLI Application" from the QLogic web-site.

End of procedure



3AM-2712-04ENZ0

http://www.qlogic.com

Chapter 3 Setting Up the Server

P

The server setup will vary according to how the ETERNUS Disk storage systems and server areto be connected. Edit the server's configuration file to match the chosen topology. Configurationfiles may also differ depending on which Fibre Channel cards are to be used.

There are two possible connection topologies: FC-AL connection and Fabric connection.

■ For FC-AL connection

Instance name data of the Fibre Channel card is necessary. Refer to the following to set.

� "3.1 Creating a WWN Instance Management Table for the Server" (page 10)� "3.2 Creating a WWN Instance Management Table for Storage System" (page 14)� "3.4 Setting the Configuration File" (page 17)� "3.5 Re-checking the Settings" (page 17)

■ For Fabric connection

The Fibre Channel card Instance name, target WWN, and target ID information are necessary.Check each item and enter them in the list. Edit the configuration file according to thoseinformation and make settings.Refer to the following to set.

� "3.1 Creating a WWN Instance Management Table for the Server" (page 10)� "3.2 Creating a WWN Instance Management Table for Storage System" (page 14)� "3.3 Creating a Target Binding Table" (page 15)� "3.4 Setting the Configuration File" (page 17)� "3.5 Re-checking the Settings" (page 17)



3AM-2712-04ENZ0

Chapter 3 Setting Up the Server > 3.1 Creating a WWN Instance Management Table for the Server

P

3.1 Creating a WWN Instance Management Table for the Server

Determine the following information for each Fibre Channel card installed in the server and enterit into a copy of the "WWN instance management table for the server" (provided in "Appendix AVarious Management Table Templates" (page 27)).

� Physical slot name� WWN� Instance name� Physical path name

Procedure

1 Check the instance names."hba + instance number" is the format used to represent Fibre Channel card instancenames.

The instance No. that corresponds to the physical path in which the Fibre Channel card isinstalled is stored in the "/etc/path_to_inst" file at Fibre Channel card driver installation.Extract the necessary lines using the "grep" command.

Example

2 Enter the results in "Instance name" and "Physical path name" columns of the "WWN instance management table for the server".Example

"hba0" is the instance name of the "/pci@b,2000/QLGC,qla@2" pathFibre Channel card."hba1" is the instance name of the "/pci@b,2000/QLGC,qla@2,1"path Fibre Channel card.

Physical slot name WWN Instance name Physical path name

# grep "QLGC" /etc/path_to_inst

"/pci@b,2000/QLGC,qla@2 " 0 "qla2300""/pci@b,2000/QLGC,qla@2, 1" 1 "qla2300"

Physical path name Instance number


/pci@b,2000/QLGC,qla@2

/pci@b,2000/QLGC,qla@2,1

hba0

hba1



3AM-2712-04ENZ0


P

3 Check the WWN for the Fibre Channel card.

3-1 Execute the following command to check the WWN that corresponds to the Fibre Channel card instance name.

3-2 Follow the on-screen directions.

3-3 Enter "3" to select "3: Display HBA Information".The [HBA Information Menu] appears.

# scli

Searching for QLogic FC HBA(s) and attached device(s) ...

SANsurfer FC HBA CLI

v1.7.0 Build 12

Main Menu

1: Display System Information 2: Display HBA Settings 3: Display HBA Information 4: Display Device List 5: Display LUN List 6: Configure HBA Settings 7: Target Persistent Binding 8: Selective LUNs 9: Boot Device Settings 10: Driver Settings 11: HBA Utilities 12: Flash Beacon 13: Diagnostics 14: Statistics 15: Help 16: Quit


v1.7.0 Build 12

HBA Information Menu

1: Information 2: VPD

Note: 0 to return to Main Menu Enter Selection: 1



3AM-2712-04ENZ0


P

3-4 Enter "1" to select "1: Information".The [Information Menu] appears.


v1.7.0 Build 12

Information Menu

HBA Model QLA2462: 1: Port 1 (OS 0): WWPN: 21-00-00-E0-8B-91-D9-4F Online 2: Port 2 (OS 1): WWPN: 21-01-00-E0-8B-B1-D9-4F Online 3: All HBAs 4: Return to Previous Menu




3AM-2712-04ENZ0


P

3-5 Enter "3" to select "3: All HBAs".WWPN appears.

Host Name : v440a HBA Model : QLA2462 HBA Alias : Port : 1 Port Alias : Node Name : 20-00-00-E0-8B-91-D9-4F Port Name : 21-00-00-E0-8B-91-D9-4F Port ID : 00-00-01 Serial Number : RFC0630L34553 Driver Version : qla-5.03 FCode Version : 1.24 Firmware Version : 4.00.26 HBA Instance : 0 OS Instance : 0 HBA ID : 0-QLA2462 OptionROM BIOS Version : 1.24 OptionROM FCode Version : 1.24 OptionROM EFI Version : 1.08 OptionROM Firmware Version : 4.00.26 Actual Connection Mode : Loop Actual Data Rate : 2 Gbps PortType (Topology) : NLPort Total Number of Devices : 1 HBA Status : Online

Hit <RETURN> to continue: ------------------------------------------------------------------- Host Name : v440a HBA Model : QLA2462 HBA Alias : Port : 2 Port Alias : Node Name : 20-01-00-E0-8B-B1-D9-4F Port Name : 21-01-00-E0-8B-B1-D9-4F Port ID : 00-00-02 Serial Number : RFC0630L34553 Driver Version : qla-5.03 FCode Version : 1.24 Firmware Version : 4.00.26 HBA Instance : 1 OS Instance : 1 HBA ID : 1-QLA2462 OptionROM BIOS Version : 1.24 OptionROM FCode Version : 1.24 OptionROM EFI Version : 1.08 OptionROM Firmware Version : 4.00.26 Actual Connection Mode : Loop Actual Data Rate : 2 Gbps PortType (Topology) : NLPort Total Number of Devices : 1 HBA Status : Online

Hit <RETURN> to continue: -------------------------------------------------------------------


v1.7.0 Build 12

Information Menu

HBA Model QLA2462: 1: Port 1 (OS 0): WWPN: 21-00-00-E0-8B-91-D9-4F Online 2: Port 2 (OS 1): WWPN: 21-01-00-E0-8B-B1-D9-4F Online 3: All HBAs 4: Return to Previous Menu




3AM-2712-04ENZ0

Chapter 3 Setting Up the Server > 3.2 Creating a WWN Instance Management Table for Storage System

P

3-6 Enter "4" to select "4: Return to Previous Menu".The Main Menu reappears.

3-7 Enter "16" to quit.

4 Add the results in the "WWN instance management table for the server".Example

End of procedure

3.2 Creating a WWN Instance Management Table for Storage System

Create a "WWN instance management table for storage system" that summarizes informationrelating to CA in the ETERNUS Disk storage systems.When there are two ports on the ETERNUS Disk storage systems:

Check the following items and enter them in the WWN instance management table for storagesystem.

Main Menu

1: Display System Information 2: Display HBA Settings 3: Display HBA Information 4: Display Device List 5: Display LUN List 6: Configure HBA Settings 7: Target Persistent Binding 8: Selective LUNs 9: Boot Device Settings 10: Driver Settings 11: HBA Utilities 12: Flash Beacon 13: Diagnostics 14: Statistics 15: Help 16: Quit

Enter choice => 0#

/pci@b,2000/QLGC,qla@2

/pci@b,2000/QLGC,qla@2,1

hba0

hba1


21-00-00-E0-8B-91-D9-4F

21-01-00-E0-8B-91-D9-4F

CM0CA0Port0

CM1CA0Port0

202000e000cb0001

203000e000cb0001

16

16

Channel Adapter WWN T_ID



3AM-2712-04ENZ0

Chapter 3 Setting Up the Server > 3.3 Creating a Target Binding Table

P

� Channel AdapterCA name in the ETERNUS Disk storage systems

� WWNThe WWN for each CA in the ETERNUS Disk storage system (check usingETERNUSmgr)

� T_IDThe SCSI target ID (decimal value) that is to be defined for each CA (check usingETERNUSmgr)In a Fabric topology, the SCSI target ID is irrelevant to the physical protocol, however itmust be defined as a Solaris OS SCSI driver setting. Values matched to the serverenvironment and connection state of the devices must be set beforehand.It is recommended to set the same target ID to CAs that configures a multipath.

3.3 Creating a Target Binding Table

This procedure is not necessary for FC-AL connection.Target binding logically binds the Fibre Channel card installed in the server, and the CA on theETERNUS Disk storage systems to be connected to the server.

Target binding binds the instance name of the Fibre Channel card, channel adapter name,WWN, and target ID.

Enter the required information for target binding in the "target binding table". Target bindingtables are created for each server to be connected.Enter the following information in the target binding table.

� Name of target server� Channel Adapter names and their SCSI target IDs

The "channel adapter names" and "target IDs" entered in the "WWN instancemanagementtable for storage system"

� RAID-WWNThe WWN entered in the "WWN instance management table for storage system"

Procedure

1 Enter the target information to be set for the server.Reflect the information from the "WWN instance management table for storage system" inthe "target binding table".

Example

CM0CA0Port0CM1CA0Port0

202000e000cb0001203000e000cb0001

1616

Channel Adapter WWN Instance nameT_ID



3AM-2712-04ENZ0

Chapter 3 Setting Up the Server > 3.3 Creating a Target Binding Table

P

2 Confirm the connection path(s) in the system.Example

Physical slots on Server#0 and CAs on the ETERNUS Disk storage systems areconnected in the following paths.

� Server#0 SLOT0 � CM0CA0� Server#0 SLOT1 � CM1CA0

3 Based on the connection path(s) confirmed in Step 2 and the information in the "WWN instance management table for the server", enter the instance names corresponding to the physical slot names on the server into the "target binding table".

End of procedure

This completes the target binding table.

Server#0

Slot0 Slot1

CA0 Port0

CM0

CA0 Port1

ETERNUS Disk storage system

Fibre Channel Switch A Fibre Channel Switch B

CM1

CA0 Port1 CA0 Port0

[WWN instance management table for the server]

[target binding table]

SERV1_SLOT0

SERV1_SLOT1

10000000c9366046

10000000c9365d9e

hba0

hba1

Physical slot name WWN Instance name

16

16

CM0CA0Port0

CM1CA0Port0

202000c000cb0001

203000c000cb0001

Channel Adapter name SCSI T_ID RAID-WWN Instance name

hba0

hba1

From the two tables, find the samecombination of physical slot nameand ChannelAdapter as listed inthe path route table.

1. Record the instancename in the samerow as the physicalslot name in thetarget binding table.

2.



3AM-2712-04ENZ0

Chapter 3 Setting Up the Server > 3.4 Setting the Configuration File

P

3.4 Setting the Configuration File

Edit the configuration file according to the "WWN instance management table for the server","WWN instance management table for storage system", and "target binding table".For how to set to the configuration file and the setting example, refer to "Chapter 5 RequiredDriver Parameters" (page 20).

3.5 Re-checking the Settings

After setting is complete, check for incorrect settings in the configuration file.

Check the WWN instance management table for the server, WWN instancemanagement table for storage system, and target binding table for anyomissions.

Check the target binding values before rebooting the server. If the serverboots with a setting error, it may recognize a different storage system fromthat set in the system configuration, without generating a connection error.



3AM-2712-04ENZ0

Chapter 4 Logical Unit Recognition

P

4.1 Recognizing Logical Units with the sd Driver

The sd driver needs to be set to allow the server to recognize the ETERNUS Disk storagesystems' logical units.First, confirm that the logical unit settings on the ETERNUS Disk storage systems are correct.Next, check that Fibre Channel card IDs are described in the sd driver's configuration file (/kernel/drv/sd.conf). Then reboot the server to get it to recognize the logical units.

4.1.1 Recognizing Logical Units

Make sure that the sd driver's configuration file (/kernel/drv/sd.conf) contains the following lineusing text editor such as vi:

name="sd" parent="qla2300" target=2048;Add this line if it does not present.

Example

## Copyright 2006 Sun Microsystems, Inc. All rights reserved.# Use is subject to license terms.##ident "@(#)sd.conf 1.10 06/02/08 SMI"

name="sd" class="scsi" class_prop="atapi" target=0 lun=0;

name="sd" class="scsi" class_prop="atapi" target=1 lun=0; name="sd" class="scsi" class_prop="atapi" target=2 lun=0; name="sd" class="scsi" class_prop="atapi" target=3 lun=0;

name="sd" class="scsi" target=4 lun=0; : : name="sd" class="scsi" target=15 lun=0;# # Enable Target 7 for the mpt SCSI/SAS/SATA driver. Target 7 has @# traditionally been reserved for legacy SCSI HBAs, but SAS controllers # supported by the mpt driver do not use target 7 for that purpose.# Enabling Target 7 allows the use of 8 disks on those controllers.# name="sd" parent="mpt" target=7 lun=0; name="sd" parent="qla2300" target=2048;

This line is required.



3AM-2712-04ENZ0

Chapter 4 Logical Unit Recognition > 4.1 Recognizing Logical Units with the sd Driver

P

4.1.2 Getting the Server to Recognize the Logical Units

The server now needs to use the new sd driver settings to recognize the logical units.

Procedure

1 Reconfigure and reboot the server to get it to recognize the listed logical units. Execute the following command.The ETERNUS Disk storage system can be reconfigured by creating the "/reconfigure" fileand rebooting the server.

2 After the server has booted up, log in as a superuser, and use the "format" command to confirm that the storage system and all the logical units have been correctly recognized.

Example� Target ID=16, lun=0 and 1 of ETERNUS4000 are connected to the physical path

"/pci@b,2000/QLGC,qla@2", and c4t16d0 and c4t16d1 are assigned to each of these LUNs.

� Target ID=16, lun=0 and 1 of ETERNUS4000 are connected to the physical path "/pci@b,2000/QLGC,qla@2,1", and c5t16d0 and c5t16d1 are assigned to each of these LUNs.

3 Check that "sd@xx,x" has been displayed following the physical path name. This message enables you to check that the logical units are recognized by the sd driver.

End of procedure

# touch /reconfigure# /usr/sbin/shutdown -y -g0 -i6

# format

# formatSearching for disks...done

AVAILABLE DISK SELECTIONS:0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /sbus@3,0/SUNW,fas@3,8800000/sd@0,01. c4t16d0 <FUJITSU-E4000-0000 cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/QLGC,qla@2/sd@0,02. c4t16d1 <FUJITSU-E4000-0000 cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/QLGC,qla@2/sd@0,13. c5t16d0 <FUJITSU-E4000-0000 cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/QLGC,qla@2,1/sd@0,04. c5t16d1 <FUJITSU-E4000-0000 cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/QLGC,qla@2,1/sd@0,1



3AM-2712-04ENZ0

Chapter 5 Required Driver Parameters

P

5.1 Setting Up the Parameters

The parameters in the "/kernel/drv/qla2300.conf" configuration file need to be edited asdescribed below.

Edit the configuration file according to the following parameter list.

5.1.1 qla2300.conf Parameter Values

� These settings are common for all Solaris 10 OS, Solaris 9 OS, and Solaris 8 OS versions.� Proper instance names should be specified in place of the item names.� Check the "WWN instance management table for the server" for the actual "X" instance num-

bers to use in the "hbaX" below.

The old configuration file should always be backed up before editing:

Example

cp /kernel/drv/qla2300.conf ./qla2300.conf.backup

ParameterValue

(for FC-AL connection)

Value (for Fabric

connection)

Initial value

(default)Remarks

hbaX-SCSI-target-id-<X>-fibre-channel-port-name="<Storage WWPN>";

(*1) (*1) N/A �

hbaX-max-frame-length 2048 2048 2048 �

hbaX-execution-throttle

For the ETERNUS2000: 8

For the ETERNUS4000 and ETERNUS8000 : 20

For the ETERNUS2000: 8

For the ETERNUS4000 and ETERNUS8000 : 20

16 Non-default value

hbaX-login-retry-count 8 8 8 �

hbaX-enable-adapter-hard-loop-ID 1 0 0 1 for FC-AL

connection



3AM-2712-04ENZ0

Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters

P

hbaX-adapter-hard-loop-ID 125 0 0

For each FC-AL connectioninstance: assign in descending order, startingat 125

hbaX-enable-LIP-reset 0 0 0 �

hbaX-enable-LIP-full-login 0 0 1 Non-default

value

hbaX-enable-target-reset 0 0 0 �

hbaX-reset-delay 5 5 5 �

hbaX-port-down-retry-count 8 8 8 �

hbaX-port-down-retry-delay 0 0 0 �

hbaX-maximum-luns-per-target 8 8 8 �

hbaX-connection-options 0 1 2

0 for FC-AL connection1 for Fabric connection

hbaX-fc-tape 0 0 1 Non-default value

hbaX-fc-data-rate 1, 3, or 4 0, 1, 3, or 4 2

(*2)The following values may be used:0 for 1Gbps (fixed)1 for 2Gbps (fixed)2 for Auto (default)3 for 4Gbps (fixed)4 for 8Gbps (fixed)

hbaX-pci-latency-timer 0x40 0x40 0x40 �

hbaX-pci-x-max-memory-read-byte-count 0 0 0 �

hbaX-link-down-error 1 1 1 �

hbaX-link-down-timeout 60 60 60 �

hbaX-persistent-binding-configuration 0 0 0 �

hbaX-persistent-binding-by-port-ID 0 0 0 �

hbaX-fast-error-reporting 0 0 0 �

hbaX-extended-logging 0 0 0 �

ParameterValue


Value (for Fabric

connection)

Initial value

(default)Remarks



3AM-2712-04ENZ0


P

*1: Set as follows:hbaX-SCSI-target-id-<X>-fibre-channel-port-name="<Storage WWPN>";Check the target binding table for the Storage WWPN setting.

*2: "hbaX-fc-data-rate" setting value

hbaX-queue-full-retry-count 16 16 0 Non-default

value

hbaX-queue-full-retry-delay 2 2 2 �

hbaX-security-protocols 0 0 0 �

hbaX-FDMI-support 0 0 0 �

hbaX-VPD-support 0 0 0 �

hbaX-AIF-support 0 0 1 Non-default value

Fibre Channel

card transfer speed

Fabric connectionFibre Channel switch transfer

speed

FC-AL connectionCA transfer speed

8Gbps 4Gbps 2Gbps 8Gbps 4Gbps

8Gbps 4 3 1 4 3

4Gbps 3 3 1 3 3

2Gbps 1 1 1 1 1

ParameterValue


Value (for Fabric

connection)

Initial value

(default)Remarks

Channel Adapter name SCSI T-ID Alias name (WWN) Instance name

CM0CA0Port0CM1CA0Port0

1616

202000e000cb0001203000e000cb0001

hba0hba1

hba0-SCSI-target-id-16-fibre-channel-port-name="202000e000cb0001";hba1-SCSI-target-id-16-fibre-channel-port-name="203000e000cb0001";



3AM-2712-04ENZ0


P

5.1.2 /kernel/drv/qla2300.conf Example

The following example is for an ETERNUS8000 Fabric connection.

# Copyright (C) QLogic Corporation 1996-2008. All rights reserved. # # File is setup as the default parameters for all adapters in the # system. # If a parameter needs to be changed for a particular adapter, # make a copy of the parameter. Then change the hba number # (decimal) in the parameter to match the adapter instance number # that is displayed during the boot process. Now alter the # parameter for the adapter. # # example: # Setting loop down timeout for adapter instance 3 and 4# respectively. # # Before: # hba0-link-down-timeout=60;# # After: # hba0-link-down-timeout=60;# hba3-link-down-timeout=120;# hba4-link-down-timeout=240;# # # =============================== # Target Persistent Name Binding # =============================== # # Note: This persistent binding section only applies if the string # "qla-mp-config-required" does NOT exist. This string refects# the fact that the GUI or CLI utilities have made alternate# persistent binding entries which override the manual persistent# binding entries documented in this section.# # The Persistent Name Binding support for target devices associates a # SCSI target ID to a specified device World Wide Port Name. In other # words, this entry changes the target ID of the specified device # to the number specified in the entry. # # To enable it, lines of the following format should be added # in the qla2300.conf file: # # hba<#>-SCSI-target-id-<#>-fibre-channel-port-name="<device WWPN>"; hba0-SCSI-target-id-16-fibre-channel-port-name="2150000b5d6a0109"; hba1-SCSI-target-id-16-fibre-channel-port-name="2151000b5d6a0109"; ## For example, to associate the following WWPN with target ID 2# on adapter instance 1, the entry will be:# # hba1-SCSI-target-id-2-fibre-channel-port-name="2100002037004ac9";## *******# IMPORTANT# *******## - Unlike other parameter entries in the qla2300.conf file, values# indicated in persistent name binding entries for instance 0 does# not apply to other instances when there are no entries for the# other instances.

Add these settings for both FC-AL and Fabric connections.



3AM-2712-04ENZ0


P

# - Persistent Name Binding entries are optional entries in the# qla2300.conf file. These entries do not dictate which devices# are scanned by the driver, and do not perform any device masking,# unless the "Persistent Binding Only Option" is set. Absence of# this entry for any given device name or SCSI ID does not direct# the driver to perform any type of device masking, unless the# "Persistent Binding Only Option" is set.## - For target devices, if no Persistent Name Binding entries are# specified, the default SCSI target IDs assigned will be the loop# ID of the devices, if failover is disabled else will start at 0.# Please refer to the FAQ section for which default SCSI target IDs# are assigned to fabric devices.## ***********************# CAUTION CAUTION CAUTION# ***********************## When the Persistent Name Binding entries are used in combination# with the device entries in the /kernel/drv/sd.conf or# /kernel/drv/st.conf file, it is possible to purposely mask off# certain devices of all adapter instances from the operating system,# by purposely commenting out/deleting entries in the sd.conf/st.conf# file for those SCSI target IDs/LUNs bound to all adapter instances.# However, when the devices are shared among multiple adapters,# doing so requires extreme caution, and it is strongly recommended# that all target devices be bound with all adapter instances so that# the devices will show up in a predeterminable way. A shared device# which is bound on one adapter instance but unbound on another# adapter instance may show up at a SCSI target ID which is# unexpected by the user for the unbound adapter instance, which may# lead to possible data corruption on the device if the user# unknowingly writes to the unexpected device.## The QLogic Solaris SCSI HBA driver does not filter out the OS# scanning of SCSI devices, except when the "Persistent Binding# Only Option" is set. The target IDs/LUNs scanned by the OS are# based on the entries specified in the sd.conf and st.conf files.# When the HBA driver first initializes during the system boot# process, it assigns a target ID internally to all of the devices it# detected. During the OS device scan, the driver ignores the ’class’# value indicated in the sd.conf/st.conf file and processes the IOs# addressed to a device whose target ID/LUN matches that of a device# previously detected by the driver.## Solaris x86 properties.flow_control="duplx";queue="qfifo";disk="scdk";tape="sctp";## Solaris force attach all possible driver instances during system# startup property.#ddi-forceattach=1;

# Maximum fibre channel frame size.# Range: 512, 1024 or 2048 byteshba0-max-frame-length=2048;hba1-max-frame-length=2048;

# Maximum number of commands queued on each logical unit.# Range: 1 - 65535hba0-execution-throttle=20;hba1-execution-throttle=20;

# Number of port login retry attempts.# Range: 0 - 255hba0-login-retry-count=8;hba1-login-retry-count=8;






3AM-2712-04ENZ0


P

# Enable/disable the use adapter hard loop ID address on the fibre# channel bus.# 0 = disable, 1 = enabledhba0-enable-adapter-hard-loop-ID=0;hba1-enable-adapter-hard-loop-ID=0;

# Adapter hard loop ID address to use on the fibre channel bus.# Range: 0 - 125hba0-adapter-hard-loop-ID=0;hba1-adapter-hard-loop-ID=0;# Enable/disable the use LIP reset for loop reset.# 0 = disable, 1 = enabledhba0-enable-LIP-reset=0;hba1-enable-LIP-reset=0;# Enable/disable the use LIP full login for loop reset.# 0 = disable, 1 = enabledhba0-enable-LIP-full-login=0;hba1-enable-LIP-full-login=0;# Enable/disable the use of target reset for loop reset.# 0 = disable, 1 = enabledhba0-enable-target-reset=0;hba1-enable-target-reset=0;# Amount of time to delay after a loop reset for starting any new# I/O commands.# Range: 0 - 255 secondshba0-reset-delay=5;hba1-reset-delay=5;# Number of times to retry a port that is not responding.# Range: 0 - 255hba0-port-down-retry-count=8;hba1-port-down-retry-count=8;# Amount of time to delay between port down retries.# Range: 0 - 255 secondshba0-port-down-retry-delay=0;hba1-port-down-retry-delay=0;# Maximum number of LUNs to scan for, if a device does not# support SCSI Report LUNs command.# Range: 1 - 256hba0-maximum-luns-per-target=8;hba1-maximum-luns-per-target=8;# Connection options.# 0 = loop only# 1 = point-to-point only# 2 = loop preferred, otherwise point-to-pointhba0-connection-options=1;hba1-connection-options=1;# Enable FCP 2 Error Recovery support enable/disable.# 0 = disable, 1 = enabledhba0-fc-tape=0;hba1-fc-tape=0;# Fibre Channel Data Rate Option.# 0 = 1 gigabit/second# 1 = 2 gigabit/second# 2 = Auto-negotiate# 3 = 4 gigabit/second# 4 = 8 gigabit/secondhba0-fc-data-rate=4;hba1-fc-data-rate=4;# PCI latency timer.# Range: 0x8 - 0xF8 -- must be a multiple of 8hba0-pci-latency-timer=0x40;hba1-pci-latency-timer=0x40;# During link down conditions enable/disable the reporting of # errors. # 0 = disabled, 1 = enable hba0-link-down-error=1; hba1-link-down-error=1; # Amount of time to wait for loop to come up after it has gone down # before reporting I/O errors. # Range: 0 - 240 secondshba0-link-down-timeout=60; hba1-link-down-timeout=60;# Persistent binding only option.


Assign in descending order from 125 for each FC-ALconnection instance.

Use "1" for FC-AL connection.







Use "0" for FC-AL connection.


Set the link speed to match the target port speed forboth FC-AL and fabric connections.Use the following values:0 for 1Gbps (fixed)1 for 2Gbps (fixed)2 for Auto (default)3 for 4Gbps (fixed)4 for 8Gbps (fixed)






3AM-2712-04ENZ0


P

# 0 = Reports to OS discovery of binded and non-binded devices# 1 = Reports to OS discovery of persistent binded devices only# Note: This entry is ignored when qla-mpconfig parameter is found.hba0-persistent-binding-configuration=0;hba1-persistent-binding-configuration=0;# Persistent binding by port ID.# 0 = disabled, 1 = enablehba0-persistent-binding-by-port-ID=0;hba1-persistent-binding-by-port-ID=0;# Fast error reporting to Solaris, enabled/disabled.# 0 = disabled, 1 = enablehba0-fast-error-reporting=0;hba1-fast-error-reporting=0;# Extended logging level.# Range: 0 - 255, 0 = disabledhba0-extended-logging=0;hba1-extended-logging=0;# Number of times to retry a SCSI queue full error.# Range: 0 - 255hba0-queue-full-retry-count=16;hba1-queue-full-retry-count=16;# Amount of time to delay after a SCSI queue full error before# starting any new I/O commands.# Range: 0 - 255 secondshba0-queue-full-retry-delay=2;hba1-queue-full-retry-delay=2;# Enable DH-CHAP security protocols.# 0 = disabled, 1 = enablehba0-security-protocols=0;hba1-security-protocols=0;# FDMI support.# 0 = disabled, 1 = enablehba0-FDMI-support=0;hba1-FDMI-support=0;# Use target/lun VPD data for failover configuration support.# 0 = disabled, 1 = enablehba0-VPD-support=0;hba1-VPD-support=0;# Advance Interrupt Framework (AIF) support.# 0 = disable AIF # 1 = disable MSI-X # 2 = disable MSI # 3 = disable MSI and MSI-X # 4 = system defaulthba0-AIF-support=0;hba1-AIF-support=0;###################################################################### WARNING: Beginning of Configuration Data stored by the QLogic ## Applications. Consult documentation before editing ## any data past this text. ######################################################################













3AM-2712-04ENZ0

Appendix A Various Management Table Templates

P

The following various management tables are required in "Chapter 3 Setting Up the Server"(page 9).Use them as required.

A.1 WWN Instance Management Table for the Server

WWN instance management table for the server

Physical slot name WWN Instance name Physical path

name



3AM-2712-04ENZ0

Appendix A Various Management Table Templates > A.2 WWN Instance Management Table for Storage System

P

A.2 WWN Instance Management Table for Storage System

A.3 Target Binding Table

WWN instance management table for storage system

Channel Adapter WWN T_ID

Target binding table

Server name:

Channel Adapter name WWN T_ID Instance name



3AM-2712-04ENZ0

ETERNUS Disk storage systemsServer Connection Guide (Fibre Channel) for Oracle Solaris

Driver Settings for QLogic Fibre Channel Cards

P3AM-2712-04ENZ0

Date of issuance: December 2010Issuance responsibility: FUJITSU LIMITED

� The contents of this manual are liable to being updated without notice.� While the contents of this manual are the product of all due care and diligence, no

responsibility can be accepted for operational problems arising from any errors or missing information, or other use of the information contained in this manual.

� Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual.

� Contents of this manual are not to be reproduced without permission from Fujitsu.

Documents

ETERNUS Disk storage systems Server Connection Guide ...storage-system.fujitsu.com/global/manual/diskarray/pdf/p3am-2712... · This describes how to set up the QLogic Fibre Channel