Server Support Matrix ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for Oracle Solaris

Transcription

1

2

3 Preface This document briefly explains the operations that need to be performed by the user in order to connect an ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, or ETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system to a server 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 as those for the ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, or ETERNUS8000 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 models 300, 400, 500, and 600, and ETERNUS8000 models 700, 800, 900, 1100, 1200, 2100, and 2200 Disk storage systems are collectively referred to as ETERNUS Disk storage systems. Fourth Edition December 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 QLogic Fibre 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. 3

4 Preface An appendix contains the various management tables that are used in "Chapter 3 Setting Up the Server". Safe Use of this Product Using this manual This manual contains important information to ensure the safe use of this product. Be sure to thoroughly read and understand its contents before using the product. After reading, store this manual in a safe place for future reference. FUJITSU has made every effort to ensure the safety of the users and other personnel, and to prevent property damage. When using this product, carefully follow the instructions described in this 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. 4

5 Contents Chapter 1 Workflow...6 Chapter 2 Installing the Fibre Channel Card Driver...8 Chapter 3 Setting Up the Server Creating a WWN Instance Management Table for the Server Creating a WWN Instance Management Table for Storage System Creating a Target Binding Table Setting the Configuration File Re-checking the Settings Chapter 4 Logical Unit Recognition Recognizing Logical Units with the sd Driver Recognizing Logical Units Getting the Server to Recognize the Logical Units Chapter 5 Required Driver Parameters Setting Up the Parameters qla2300.conf Parameter Values /kernel/drv/qla2300.conf Example Appendix A Various Management Table Templates...27 A.1 WWN Instance Management Table for the Server A.2 WWN Instance Management Table for Storage System A.3 Target Binding Table

6 Chapter 1 Workflow This manual is used when performing the setup procedure described in "Installing the Driver and Setting Up the Server" and "Logical Unit Recognition" of the "ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for Oracle Solaris". Workflow Fiber Channel Card Driver Installation Install the driver. Download the proper driver from the QLogic web-site as required. Refer - "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". Refer - "Chapter 3 Setting Up the Server" (page 9) - "Appendix A Various Management Table Templates" (page 27) Fiber Channel Card Driver Setup Set the driver parameters by editing the configuration file. Refer - "Chapter 3 Setting Up the Server" (page 9) - "Chapter 5 Required Driver Parameters" (page 20) 6

7 Chapter 1 Workflow > Logical Unit (LUN) Recognition Make the server recognize the ETERNUS Disk storage system logical units using the sd driver. Refer - "Chapter 4 Logical Unit Recognition" (page 18) After completing all the required procedures in this manual, proceed to "Setting the Multipaths" in "ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for Oracle Solaris". 7

8 Chapter 2 Installing the Fibre Channel Card Driver Use the following procedure to install the Fibre Channel card driver. Procedure 1 Download and install the appropriate driver from the QLogic web-site: (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 8

9 Chapter 3 Setting Up the Server The server setup will vary according to how the ETERNUS Disk storage systems and server are to be connected. Edit the server's configuration file to match the chosen topology. Configuration files 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 those information 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) 9

10 Chapter 3 Setting Up the Server > 3.1 Creating a WWN Instance Management Table for the Server 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 enter it into a copy of the "WWN instance management table for the server" (provided in "Appendix A Various Management Table Templates" (page 27)). Physical slot name WWN Instance name Physical path name 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 instance names. The instance No. that corresponds to the physical path in which the Fibre Channel card is installed is stored in the "/etc/path_to_inst" file at Fibre Channel card driver installation. Extract the necessary lines using the "grep" command. grep "QLGC" /etc/path_to_inst Example "/pci@b,2000/qlgc,qla@2 " 0 "qla2300" "/pci@b,2000/qlgc,qla@2, 1" 1 "qla2300" Physical path name Instance number "hba0" is the instance name of the "/pci@b,2000/qlgc,qla@2" path Fibre Channel card. "hba1" is the instance name of the "/pci@b,2000/qlgc,qla@2,1" path Fibre Channel card. 2 Enter the results in "Instance name" and "Physical path name" columns of the "WWN instance management table for the server". Example Physical slot name WWN Instance name Physical path name hba0 hba1 /pci@b,2000/qlgc,qla@2 /pci@b,2000/qlgc,qla@2,1 10

11 Chapter 3 Setting Up the Server > 3.1 Creating a WWN Instance Management Table for the Server 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. scli 3-2 Follow the on-screen directions. 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 3-3 Enter "3" to select "3: Display HBA Information". The [HBA Information Menu] appears. SANsurfer FC HBA CLI v1.7.0 Build 12 HBA Information Menu 1: Information 2: VPD Note: 0 to return to Main Menu Enter Selection: 1 11

12 Chapter 3 Setting Up the Server > 3.1 Creating a WWN Instance Management Table for the Server 3-4 Enter "1" to select "1: Information". The [Information Menu] appears. SANsurfer FC HBA CLI v1.7.0 Build 12 Information Menu HBA Model QLA2462: 1: Port 1 (OS 0): WWPN: E0-8B-91-D9-4F Online 2: Port 2 (OS 1): WWPN: E0-8B-B1-D9-4F Online 3: All HBAs 4: Return to Previous Menu Note: 0 to return to Main Menu Enter Selection: 3 12

13 Chapter 3 Setting Up the Server > 3.1 Creating a WWN Instance Management Table for the Server 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 : E0-8B-91-D9-4F Port Name : E0-8B-91-D9-4F Port ID : Serial Number : RFC0630L34553 Driver Version : qla-5.03 FCode Version : 1.24 Firmware Version : 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 : 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 : E0-8B-B1-D9-4F Port Name : E0-8B-B1-D9-4F Port ID : Serial Number : RFC0630L34553 Driver Version : qla-5.03 FCode Version : 1.24 Firmware Version : 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 : Actual Connection Mode : Loop Actual Data Rate : 2 Gbps PortType (Topology) : NLPort Total Number of Devices : 1 HBA Status : Online Hit <RETURN> to continue: SANsurfer FC HBA CLI v1.7.0 Build 12 Information Menu HBA Model QLA2462: 1: Port 1 (OS 0): WWPN: E0-8B-91-D9-4F Online 2: Port 2 (OS 1): WWPN: E0-8B-B1-D9-4F Online 3: All HBAs 4: Return to Previous Menu Note: 0 to return to Main Menu Enter Selection: 4 13

14 Chapter 3 Setting Up the Server > 3.2 Creating a WWN Instance Management Table for Storage System 3-6 Enter "4" to select "4: Return to Previous Menu". The Main Menu reappears. 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 3-7 Enter "16" to quit. Enter choice => 0 4 Add the results in the "WWN instance management table for the server". Example Physical slot name WWN Instance name Physical path name E0-8B-91-D9-4F E0-8B-91-D9-4F hba0 hba1 /pci@b,2000/qlgc,qla@2 /pci@b,2000/qlgc,qla@2,1 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 information relating to CA in the ETERNUS Disk storage systems. When there are two ports on the ETERNUS Disk storage systems: Channel Adapter WWN T_ID CM0CA0Port0 CM1CA0Port e000cb e000cb Check the following items and enter them in the WWN instance management table for storage system. 14

15 Chapter 3 Setting Up the Server > 3.3 Creating a Target Binding Table Channel Adapter CA name in the ETERNUS Disk storage systems WWN The WWN for each CA in the ETERNUS Disk storage system (check using ETERNUSmgr) T_ID The SCSI target ID (decimal value) that is to be defined for each CA (check using ETERNUSmgr) In a Fabric topology, the SCSI target ID is irrelevant to the physical protocol, however it must be defined as a Solaris OS SCSI driver setting. Values matched to the server environment 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 the ETERNUS 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 binding tables 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 instance management table for storage system" RAID-WWN The 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" in the "target binding table". Example Channel Adapter WWN T_ID Instance name CM0CA0Port0 CM1CA0Port e000cb e000cb

16 Chapter 3 Setting Up the Server > 3.3 Creating a Target Binding Table 2 Confirm the connection path(s) in the system. Example Server0 Slot0 Slot1 Fibre Channel Switch A Fibre Channel Switch B CA0 Port0 CA0 Port1 CA0 Port0 CA0 Port1 CM0 ETERNUS Disk storage system CM1 Physical slots on Server0 and CAs on the ETERNUS Disk storage systems are connected in the following paths. Server0 SLOT0 CM0CA0 Server0 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". [WWN instance management table for the server] Physical slot name WWN Instance name 1. From the two 2. Record the instance tables, find the same name in the same SERV1_SLOT c hba0 combination of row as the physical physical slot name SERV1_SLOT c9365d9e hba1 slot name in the and Channel target binding table. Adapter as listed in the path route table. [target binding table] Channel Adapter name SCSI T_ID RAID-WWN Instance name CM0CA0Port c000cb0001 hba0 CM1CA0Port c000cb0001 hba1 This completes the target binding table. End of procedure 16

17 Chapter 3 Setting Up the Server > 3.4 Setting the Configuration File 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 Required Driver Parameters" (page 20). Check the WWN instance management table for the server, WWN instance management table for storage system, and target binding table for any omissions. 3.5 Re-checking the Settings After setting is complete, check for incorrect settings in the configuration file. Check the target binding values before rebooting the server. If the server boots with a setting error, it may recognize a different storage system from that set in the system configuration, without generating a connection error. 17

18 Chapter 4 Logical Unit Recognition 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 storage systems' 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 Recognizing Logical Units Make sure that the sd driver's configuration file (/kernel/drv/sd.conf) contains the following line using 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 /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 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" This line is required. target=7 lun=0; name="sd" parent="qla2300" target=2048; 18

19 Chapter 4 Logical Unit Recognition > 4.1 Recognizing Logical Units with the sd Driver 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" file and rebooting the server. touch /reconfigure /usr/sbin/shutdown -y -g0 -i6 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. format 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. format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /sbus@3,0/sunw,fas@3, /sd@0,0 1. c4t16d0 <FUJITSU-E cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/qlgc,qla@2/sd@0,0 2. c4t16d1 <FUJITSU-E cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/qlgc,qla@2/sd@0,1 3. c5t16d0 <FUJITSU-E cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/qlgc,qla@2,1/sd@0,0 4. c5t16d1 <FUJITSU-E cyl 260 alt 2 hd 64 sec 256> /pci@b,2000/qlgc,qla@2,1/sd@0,1 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 19

20 Chapter 5 Required Driver Parameters 5.1 Setting Up the Parameters The parameters in the "/kernel/drv/qla2300.conf" configuration file need to be edited as described below. The old configuration file should always be backed up before editing: Example cp /kernel/drv/qla2300.conf./qla2300.conf.backup Edit the configuration file according to the following parameter list 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 numbers to use in the "hbax" below. Parameter hbax-scsi-target-id- <X>-fibre-channel-portname="<Storage WWPN>"; Value (for FC-AL connection) Value (for Fabric connection) Initial value (default) Remarks (*1) (*1) N/A hbax-max-frame-length hbax-execution-throttle For the ETERNUS2000: 8 For the ETERNUS4000 and ETERNUS8000 : 20 For the ETERNUS2000: 8 For the ETERNUS4000 and ETERNUS8000 : Non-default value hbax-login-retry-count hbax-enable-adapterhard-loop-id for FC-AL connection 20

21 Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters Parameter hbax-adapter-hard-loop- ID For each FC-AL connection instance: assign in descending order, starting at 125 hbax-enable-lip-reset Value (for FC-AL connection) Value (for Fabric connection) Non-default value hbax-connection-options hbax-fc-tape Initial value (default) Remarks 0 for FC-AL connection 1 for Fabric connection Non-default value hbax-enable-lip-fulllogin hbax-enable-target-reset hbax-reset-delay hbax-port-down-retrycount hbax-port-down-retrydelay hbax-maximum-luns-pertarget 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-memoryread-byte-count hbax-link-down-error hbax-link-down-timeout hbax-persistent-bindingconfiguration hbax-persistent-bindingby-port-id hbax-fast-error-reporting hbax-extended-logging

22 Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters Parameter hbax-queue-full-retrycount hbax-queue-full-retrydelay Value (for FC-AL connection) Value (for Fabric connection) *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. Non-default value hbax-security-protocols hbax-fdmi-support hbax-vpd-support hbax-aif-support Channel Adapter name SCSI T-ID Alias name (WWN) Instance name CM0CA0Port0 CM1CA0Port e000cb e000cb0001 hba0 hba1 Initial value (default) Remarks Non-default value hba0-scsi-target-id-16-fibre-channel-port-name="202000e000cb0001"; hba1-scsi-target-id-16-fibre-channel-port-name="203000e000cb0001"; *2: "hbax-fc-data-rate" setting value Fibre Channel card transfer speed Fabric connection Fibre Channel switch transfer speed FC-AL connection CA transfer speed 8Gbps 4Gbps 2Gbps 8Gbps 4Gbps 8Gbps Gbps Gbps

23 Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters /kernel/drv/qla2300.conf Example The following example is for an ETERNUS8000 Fabric connection. Copyright (C) QLogic Corporation 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=" b5d6a0109"; hba1-scsi-target-id-16-fibre-channel-port-name=" b5d6a0109"; For example, to associate Add these settings following for both WWPN FC-AL with and target Fabric ID connections. 2 on adapter instance 1, the entry will be: hba1-scsi-target-id-2-fibre-channel-port-name=" ac9"; ******* 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. 23

24 Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters - 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 bytes hba0-max-frame-length=2048; Add these settings for both FC-AL and Fabric hba1-max-frame-length=2048; connections. Maximum number of commands queued on each logical unit. Range: hba0-execution-throttle=20; Add these settings for both FC-AL and Fabric hba1-execution-throttle=20; connections. Number of port login retry attempts. Range: hba0-login-retry-count=8; Add these settings for both FC-AL and Fabric hba1-login-retry-count=8; connections. 24

25 Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters Enable/disable the use adapter hard loop ID address on the fibre channel bus. 0 = disable, 1 = enabled hba0-enable-adapter-hard-loop-id=0; Use "1" for FC-AL connection. hba1-enable-adapter-hard-loop-id=0; Adapter hard loop ID address to use on the fibre channel bus. Range: hba0-adapter-hard-loop-id=0; Assign in descending order from 125 for each FC-AL hba1-adapter-hard-loop-id=0; connection instance. Enable/disable the use LIP reset for loop reset. 0 = disable, 1 = enabled hba0-enable-lip-reset=0; Add these settings for both FC-AL and Fabric connections. hba1-enable-lip-reset=0; Enable/disable the use LIP full login for loop reset. 0 = disable, 1 = enabled hba0-enable-lip-full-login=0; Add these settings for both FC-AL and Fabric hba1-enable-lip-full-login=0; connections. Enable/disable the use of target reset for loop reset. 0 = disable, 1 = enabled hba0-enable-target-reset=0; Add these settings for both FC-AL and Fabric hba1-enable-target-reset=0; connections. Amount of time to delay after a loop reset for starting any new I/O commands. Range: seconds hba0-reset-delay=5; Add these settings for both FC-AL and Fabric connections. hba1-reset-delay=5; Number of times to retry a port that is not responding. Range: hba0-port-down-retry-count=8; Add these settings for both FC-AL and Fabric hba1-port-down-retry-count=8; connections. Amount of time to delay between port down retries. Range: seconds hba0-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: hba0-maximum-luns-per-target=8; hba1-maximum-luns-per-target=8; Add these settings for both FC-AL and Fabric connections. Connection options. 0 = loop only 1 = point-to-point only 2 = loop preferred, otherwise point-to-point hba0-connection-options=1; hba1-connection-options=1; Use "0" for FC-AL connection. Enable FCP 2 Error Recovery support enable/disable. 0 = disable, 1 = enabled hba0-fc-tape=0; hba1-fc-tape=0; Add these settings for both FC-AL and Fabric connections. Fibre Channel Data Rate Option. 0 = 1 gigabit/second Set the link speed to match the target port speed for 1 = 2 gigabit/second both FC-AL and fabric connections. 2 = Auto-negotiate Use the following values: 3 = 4 gigabit/second 0 for 1Gbps (fixed) 4 = 8 gigabit/second 1 for 2Gbps (fixed) hba0-fc-data-rate=4; hba1-fc-data-rate=4; PCI latency timer. 2 for Auto (default) 3 for 4Gbps (fixed) 4 for 8Gbps (fixed) Range: 0x8-0xF8 -- must be a multiple of 8 hba0-pci-latency-timer=0x40; hba1-pci-latency-timer=0x40; Add these settings for both FC-AL and Fabric connections. 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: seconds hba0-link-down-timeout=60; hba1-link-down-timeout=60; Persistent binding only option. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. 25

26 Chapter 5 Required Driver Parameters > 5.1 Setting Up the Parameters 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 = enable hba0-persistent-binding-by-port-id=0; hba1-persistent-binding-by-port-id=0; Fast error reporting to Solaris, enabled/disabled. 0 = disabled, 1 = enable hba0-fast-error-reporting=0; hba1-fast-error-reporting=0; Extended logging level. Range: 0-255, 0 = disabled hba0-extended-logging=0; hba1-extended-logging=0; Number of times to retry a SCSI queue full error. Range: hba0-queue-full-retry-count=16; hba1-queue-full-retry-count=16; connections. Amount of time to delay after a SCSI queue full error before starting any new I/O commands. Range: seconds hba0-queue-full-retry-delay=2; hba1-queue-full-retry-delay=2; Enable DH-CHAP security protocols. 0 = disabled, 1 = enable hba0-security-protocols=0; hba1-security-protocols=0; FDMI support. 0 = disabled, 1 = enable hba0-fdmi-support=0; hba1-fdmi-support=0; Use target/lun VPD data for failover configuration support. 0 = disabled, 1 = enable hba0-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 default Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. Add these settings for both FC-AL and Fabric connections. hba0-aif-support=0; hba1-aif-support=0; Add these settings for both FC-AL and Fabric connections. WARNING: Beginning of Configuration Data stored by the QLogic Applications. Consult documentation before editing any data past this text. 26

27 Appendix A Various Management Table Templates 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 WWN name Instance name Physical path name 27

28 Appendix A Various Management Table Templates > A.2 WWN Instance Management Table for Storage System A.2 WWN Instance Management Table for Storage System WWN instance management table for storage system Channel Adapter WWN T_ID A.3 Target Binding Table Target binding table Server name: Channel Adapter name WWN T_ID Instance name 28

29 ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for Oracle Solaris Driver Settings for QLogic Fibre Channel Cards Date of issuance: December 2010 Issuance 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.

30