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 Fujitsu 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. Fifth Edition December 2010 The Contents and Structure of this Manual This document is composed of the following six chapters and an appendix. Chapter 1 Workflow This describes the workflow required to establish a connection between a server with Fujitsu 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 Installing the hddv Driver This describes how to install the hddv driver that is required when connecting the ETERNUS Disk storage systems and a Fujitsu driver equipped server in a single-path configuration. Chapter 4 Setting Up the Server This describes how to set up the server for different connection topologies. Chapter 5 Logical Unit Recognition This describes how to make the server recognize the ETERNUS Disk storage system LUNs (logical units). 3

4 Preface Chapter 6 Required Driver Parameters This describes how to set up the Fujitsu Fibre Channel card driver. An appendix contains the various management tables that are used in "Chapter 4 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. The company names, product names and service names mentioned in this document are registered trademarks or trademarks of their respective companies. 4

5 Preface 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. "Fibre Channel cable" refers to the cable that is used to connect the ETERNUS Disk storage systems and server over a Fibre Channel interface. "FC cable", "optical fibre cable", or "multi mode Fibre Channel cable" may be used instead, depending on the storage system. Italics are used to show variables such as values and characters that appear in command parameters and output examples. 5

6 Contents Chapter 1 Workflow...7 Chapter 2 Installing the Fibre Channel Card Driver...9 Chapter 3 Installing the hddv Driver...10 Chapter 4 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 (fjpfca.conf) Re-checking the Settings Chapter 5 Logical Unit Recognition Recognizing Logical Units with the sd Driver Logical Unit Recognition Getting the Server to Recognize the Logical Units Recognizing Logical Units with the hddv Driver Chapter 6 Required Driver Parameters Setting Up the Parameters fjpfca.conf Parameter Values /kernel/drv/fjpfca.conf Example Appendix A Various Management Table Templates...28 A.1 WWN Instance Management Table for the Server A.2 WWN Instance Management Table for Storage System A.3 Target Binding Table

7 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 Refer Install the driver. Download the proper driver from the Fujitsu web-site as required. - "Chapter 2 Installing the Fibre Channel Card Driver" (page 9) - Used for driver installation Product manual Management Table Creation (Various) Refer 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 4 Setting Up the Server" (page 11) - "Appendix A Various Management Table Templates" (page 28) Edit Configuration File Refer Set the driver parameters by editing the configuration file. - "Chapter 4 Setting Up the Server" (page 11) - "Chapter 6 Required Driver Parameters" (page 24) - Check the settings using the "grmpdautoconf" command ETERNUS Multipath Driver product manual 7

8 Chapter 1 Workflow > Logical Unit (LUN) Recognition Make the server recognize the ETERNUS Disk storage system logical units using the sd driver. Refer - "Chapter 5 Logical Unit Recognition" (page 20) 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". 8

9 Chapter 2 Installing the Fibre Channel Card Driver Install the Fibre Channel card driver according to the installation guide provided with the Fibre Channel card. 9

10 Chapter 3 Installing the hddv Driver Use the hddv driver if it is already installed and used. Do not use the hddv driver for new connections. 10

11 Chapter 4 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. Procedures are described below. Also refer to the FUJITSU PCI Fibre Channel manuals as necessary. For FC-AL connection Instance name data of the Fibre Channel card is necessary. Refer to the following to set. "4.1 Creating a WWN Instance Management Table for the Server" (page 12) "4.2 Creating a WWN Instance Management Table for Storage System" (page 14) "4.4 Setting the Configuration File (fjpfca.conf)" (page 16) "4.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. "4.1 Creating a WWN Instance Management Table for the Server" (page 12) "4.2 Creating a WWN Instance Management Table for Storage System" (page 14) "4.3 Creating a Target Binding Table" (page 15) "4.4 Setting the Configuration File (fjpfca.conf)" (page 16) "4.5 Re-checking the Settings" (page 17) 11

12 Chapter 4 Setting Up the Server > 4.1 Creating a WWN Instance Management Table for the Server 4.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 28)). Physical slot name WWN Instance name Physical path name WWN Instance Management Table for the Server Physical slot name WWN Instance name Physical path name Procedure 1 Check the instance names. "fjpfca + 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 "fjpfca" /etc/path_to_inst Example "/pci@6,4000/fibre-channel@2" 1 "fjpfca" "/pci@4,2000/fibre-channel@1" 0 "fjpfca" Physical path name Instance number "fjpfca1" is the instance name of the "/pci@6,4000/fibre-channel@2" path Fibre Channel card. "fjpfca0" is the instance name of the "/pci@4,2000/fibre-channel@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". Physical slot name WWN Instance name Physical path name fjpfca0 /pci@4,2000/fibre-channel@1 fjpfca1 /pci@6,4000/fibre-channel@2 12

13 Chapter 4 Setting Up the Server > 4.1 Creating a WWN Instance Management Table for the Server 3 Check the WWN for the Fibre Channel card. Execute the following command to check the WWN that corresponds to the Fibre Channel card instance name. # /usr/sbin/fjsvpfca/fc_info -a The instance name is displayed in the format "adapter=fjpfca#x" ("x" is instance number). The WWN corresponding to the instance name is displayed after "wwn=". Example adapter=fjpfca#0 wwn= e link_status=up port_id=0x11001 own_port=nl other_port=fl e_d_tov=2000ms r_a_tov=10000ms bb_credit=0x0 bb_frame_size=2112byte adapter=fjpfca#1 wwn= e24846f link_status=up port_id=0x21001 own_port=nl other_port=fl e_d_tov=2000ms r_a_tov=10000ms bb_credit=0x0 bb_frame_size=2112byte The WWN for Fibre Channel card instance name "fjpfca0" is " e248434" and WWN for "fjpfca1" is " e24846f". 4 Enter the results in the "WWN" column of the "WWN instance management table for the server". Example Physical slot name WWN Instance name Physical path name e fjpfca0 /pci@4,2000/fibre-channel@ e24846f fjpfca1 /pci@6,4000/fibre-channel@2 5 Check the physical slot positions that correspond to the instance names. 5-1 Execute the following command to check the physical slots where the Fibre Channel cards corresponding to each instance name are installed. (Execute this command for all Fibre Channel cards.) # /usr/sbin/fjsvpfca/fc_adm -l Instance_name For the "Instance_name", use the Fibre Channel card instance names identified in Step 1 (in this case, "fjpfca0" and "fjpfca1"). 5-2 Executing the command causes the LINK and CHK LEDs of the Fibre Channel card corresponding to the specified instance name to blink. Check the blinking LEDs. To exit this command, press [Ctrl]+[C]. Alternatively, wait three minutes to exit automatically. 13

14 Chapter 4 Setting Up the Server > 4.2 Creating a WWN Instance Management Table for Storage System 5-3 Enter the results in the "Physical slot name" column of the "WWN instance management table for the server". Example Physical slot name WWN Instance name Physical path name SERV1_SLOT0 SERV1_SLOT e e24846f fjpfca0 fjpfca1 /pci@4,2000/fibre-channel@1 /pci@6,4000/fibre-channel@2 End of procedure This completes the "WWN instance management table for the server". 4.2 Creating a WWN Instance Management Table for Storage System Create a "WWN instance management table for storage system" (provided in "Appendix A Various Management Table Templates" (page 28)) that summarizes information relating to CA in the ETERNUS Disk storage systems. Example: When there are two ports on the ETERNUS Disk storage systems Channel Adapter WWN Alias name T_ID CM0CA0Port0 CM1CA0Port e000cb e000cb0001 E4000_CM0CA0P0 16 E4000_CM1CA0P0 16 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) Alias name An arbitrarily chosen name for each CA that may be used when setting up the fjpfca driver This use of "alias name" differs from the "alias name" that is specified when setting Fibre Channel switch zoning. However, it is recommended to set both aliases to the same name. T_ID (SCSI target 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. 14

15 Chapter 4 Setting Up the Server > 4.3 Creating a Target Binding Table 4.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. Procedure 1 Reflect the information from the "WWN instance management table for storage system" in the "target binding table" (provided in "Appendix A Various Management Table Templates" (page 28)). Target Binding Table Server name: Server#0 Channel Adapter name SCSI T-ID Alias name (WWN) Instance name CM0CA0Port0 CM1CA0Port0 0 0 E4000_CM0CA0P0 E4000_CM1CA0P0 Name of target server Each "channel adapter name" and "T_ID" entered in "4.2 Creating a WWN Instance Management Table for Storage System" (page 14) The alias name entered in "4.2 Creating a WWN Instance Management Table for Storage System" (page 14) 2 Confirm the connection path(s) in the system. Example Server#0 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 Server#0 and CAs on the ETERNUS Disk storage systems are connected in the following paths. Server#0 SLOT0 CM0CA0 Server#0 SLOT1 CM1CA0 15

16 Chapter 4 Setting Up the Server > 4.4 Setting the Configuration File (fjpfca.conf) 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 storage system] 1. From the two tables, find the same combination of physical slot name and Channel Adapter as listed in the path route table. Physical slot name WWN Instance name SERV1_SLOT0 SERV1_SLOT e e24846f fjpfca0 fjpfca1 [target binding table] 2. Record the instance name in the same row as the physical slot name in the target binding table. Channel Adapter name SCSI T_ID Alias name (WWN) Instance name CM0CA0Port0 0 E4000_CM0CA0P0 fjpfca0 CM1CA0Port0 0 E4000_CM1CA0P0 fjpfca1 End of procedure This completes the target binding table. 4.4 Setting the Configuration File (fjpfca.conf) 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 6 Required Driver Parameters" (page 24). Check the "WWN instance management table for the server", "WWN instance management table for storage system", and "target binding table" for any omissions. 16

17 Chapter 4 Setting Up the Server > 4.5 Re-checking the Settings 4.5 Re-checking the Settings After setting is complete, check for incorrect settings in the configuration file. Procedure 1 Use the "chk_conf" command to check for errors. The settings in the configuration file can be checked for errors by entering the following command: #/usr/sbin/fjsvpfca/chk_conf -v If the settings are correct, the following message is displayed: /kernel/drv/fjpfca.conf seems to be correct Example /kernel/dfv/fjpfca.conf seems to be correct. ****************************** *port definition* instance status options fjpfca1 found nport fjpfca2 found nport *target definition* instance t-id wwn status throt alias fjpfca1 16 0x213100e000cb0001 detect UNDEF E4000_CM0CA0P0 fjpfca2 17 0x212100e000cb0001 detect UNDEF E4000_CM1CA0P0 If the settings are incorrect, different messages (incorrect setting examples 1 and 2) will be output. If the "/kernel/drv/fjpfca.conf seems to be correct" message does not appear, checking the configuration file settings, the status of each device, and the physical connections may find the problem. 17

18 Chapter 4 Setting Up the Server > 4.5 Re-checking the Settings Incorrect setting example 1 Syntax error with the alias setting in the configuration file. #/usr/sbin/fjsvpfca/chk_conf -v "kernel/drv/fjpfca.conf",line 28: syntax error,before or at: "kernel/drv/fjpfca.conf",line 29: syntax error,before or at: "kernel/drv/fjpfca.conf",error:no such alias:e4000_cm0 "kernel/drv/fjpfca.conf",error:no such alias:e4000_cm1 there were some non fatal errors in fjpfca.conf. Still trying to check it. ****************************** *port definition* instance status options fjpfca1 found nport fjpfca2 found nport *target definition* instance t-id wwn status throt alias fjpfca1 16 0x213100e000cb0001 detect UNDEF E4000_CM0CA0P0 fjpfca2 17 no binding none UNDEF E4000_CM1CA0P0 Incorrect setting example 2 Cables are not connected correctly. /usr/sbin/fjsvpfca/chk_conf -v target fjpfca1t16 (alias=e4000_cm0) seems to be absent on fjpfca#1 target fjpfca2t17 (alias=e4000_cm1) seems to be absent on fjpfca#2 ****************************** *port definition* instance status options fjpfca1 found nport fjpfca2 found nport *target definition* instance t-id wwn status throt alias fjpfca1 16 0x213100e000cb0001 none UNDEF E4000_CM0CA0P0 fjpfca2 17 no binding none UNDEF E4000_CM1CA0P0 The following items can be confirmed by executing the "chk_conf" command: Syntax check of general configuration file Detailed syntax check relating to the following properties - alias - port - fcp-bind-target - Reference relationship between fcp-bind-target and alias - Whether or not the target device described in fcp-bindtarget actually exists 18

19 Chapter 4 Setting Up the Server > 4.5 Re-checking the Settings 2 Re-check target binding setting By using the "chk_conf" command, you can check any errors in the configuration file, and check the Fibre Channel cable physical connections. However, you cannot confirm whether or not target binding based upon the system configuration has been performed correctly using the "chk_conf" command. Re-check the following points before restarting the server. Is the target binding set according to the system configuration? Is the target binding table recorded according to the information in the WWN instance management table? Is "fjpfca.conf" setup according to the information of the target binding table? 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. End of procedure 19

20 Chapter 5 Logical Unit Recognition Logical units need to be recognized with the sd driver or hddv driver. Skip this chapter if using the ETERNUS Multipath Driver or GR Multipath Driver "grmpdautoconf" command. 5.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. Refer to "5.2 Recognizing Logical Units with the hddv Driver" (page 23) when using the hddv driver Logical Unit Recognition Add descriptions of the logical units to the sd driver configuration file (/kernel/drv/sd.conf) using a text editor, such as vi. Do not delete the lun=0 description for the system disk target ID. 20

21 Chapter 5 Logical Unit Recognition > 5.1 Recognizing Logical Units with the sd Driver Example # # Copyright (c) 1992, by Sun Microsystems, Inc. # #ident "@(#)sd.conf /01/11 SMI" name="sd" class="scsi" target=0 lun=0; name="sd" class="scsi" target=1 lun=0; name="sd" class="scsi" target=2 lun=0; : : name="sd" class="scsi" target=16 lun=0; name="sd" class="scsi" target=16 lun=1; name="sd" class="scsi" target=16 lun=2; For FC-AL connection Set the "target=" value the same as the Loop-ID set in the [Set CA Details] window of ETERNUSmgr. The ETERNUSmgr Loop-ID is natively set as a hexadecimal value, which must be converted to a decimal value for this setting. For Fabric connection Set the "target=" value the same as the target ID of the "fcp-bind-target" parameter set in the configuration file. Refer to "6.1 Setting Up the Parameters" (page 24) 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. # 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 assign labels and to confirm that the storage system and all logical units have been correctly recognized. # format 21

22 Chapter 5 Logical Unit Recognition > 5.1 Recognizing Logical Units with the sd Driver Example 1 VTOC disk labels - Target ID=16, lun=0 and 1 of ETERNUS4000 are connected to the physical path "/pci@9,600000/lpfc@1", 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@9,600000/lpfc@2", and c5t16d0 and c5t16d1 are assigned to each of these LUNs. # format Searching for disks...done c4t16d0: configured with capacity of 7.98GB c4t16d1: configured with capacity of 7.98GB c5t16d0: configured with capacity of 7.98GB c5t16d1: configured with capacity of 7.98GB AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN36G cyl alt 2 hd 27 sec 107> /pci@8,600000/sunw,qlc@2/fp@0,0/ssd@w cf6851ce,0 1. c4t16d0 <FUJITSU-E cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@1/sd@10,0 2. c4t16d1 <FUJITSU-E cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@1/sd@10,1 3. c5t16d0 <FUJITSU-E cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@2/sd@10,0 4. c5t16d1 <FUJITSU-E cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@2/sd@10,1 Specify disk (enter its number): Example 2 EFI disk labels EFI labels are automatically assigned to 1TB and larger disks. However, even if the disk capacity is less than 1TB, EFI labels can still be assigned using the "format -e" command, as shown in the following example. # format -e Searching for disks...done c5t16d0: configured with capacity of GB AVAILABLE DISK SELECTIONS: 0. c0t0d0 <FUJITSU-MAP3367NC-3701 cyl alt 2 hd 10 sec 574> /pci@83,4000/fjsv,ulsa@2,1/sd@0,0 1. c5t16d0 <FUJITSU-E TB> /pci@80,4000/lpfc@3/sd@10,0 Specify disk (enter its number): 1 selecting c5t16d0 [disk formatted] format> label [0] SMI Label [1] EFI Label Specify Label type[0]: 1 Ready to label disk, continue? yes format> quit End of procedure 22

23 Chapter 5 Logical Unit Recognition > 5.2 Recognizing Logical Units with the hddv Driver 5.2 Recognizing Logical Units with the hddv Driver Logical units may be recognized using the hddv driver. Refer to the driver product manual for more details. When connecting with the server running on Solaris 10 OS in a single-path configuration, logical units do not need to be recognized with the hddv driver. 23

24 Chapter 6 Required Driver Parameters 6.1 Setting Up the Parameters The parameters in the "/kernel/drv/fjpfca.conf" configuration file need to be edited as described below. Original configuration file must be backed up before editing. cp /kernel/drv/fjpfca.conf./ fjpfca.conf.backup Edit the configuration file according to the following parameter list fjpfca.conf Parameter Values These settings are common for all Solaris 10 OS, Solaris 9 OS, and Solaris 8 OS versions. Comment out any items that are not required by putting a "#" at the beginning of the line. Parameter Value (for FC-AL connection) Value (for Fabric connection) alias Set if required Set if required port Not required nport Remarks Set an alias name for the WWN. It is easier to edit the setting files if this alias name is set. Link speed may be set to a fixed value. (*1) Set the topology and link speed. port="<instance name>:<topology>:<link speed>" The following <topology> parameters may be used: nport:fabric connection loop:fc-al connection The following <link speed> parameters may be used: sp1 for 1GB links sp2 for 2GB links sp4 for 4GB links 24

25 Chapter 6 Required Driver Parameters > 6.1 Setting Up the Parameters Parameter fcp-bindtarget max-throttle Value (for FC-AL connection) Not required For the ETERNUS2000: 40 For the ETERNUS4000 and ETERNUS8000: 255 Value (for Fabric connection) See remarks For the ETERNUS2000: = 40 / (No. of Server-side Fibre Channel ports connected to each ETERNUS-side CA port) (Round the result down) Use the value of "8" if the actual result is lower. For the ETERNUS4000 and ETERNUS8000: 255 Remarks Binds the instance and the ETERNUS Disk storage systems' CA port together. fcp-bind-target="<instance name>t<scsi target ID>:<alias name>" * <WWN> can be used instead of the <alias name>. Set the maximum number of SCSI commands (tags) to be issued. max-throttle="instance name + Target ID:Setting value" Define the instance name and target ID in sequentialing. Specify this for all the ETERNUS Disk storage systems' access paths. The "max-throttle-all" property does not need to be set. *1: It is recommended that the link speed be set to a fixed value, rather than the auto negotiation setting. When multiple parameters are required for one item, delimit them with commas. Put a semicolon (;) at the end of the line to close the item. Perform these settings for all instances connected to the ETERNUS Disk storage systems. For the fcp-bind-target setting, see the target binding table. Channel Adapter name SCSI T-ID Alias name (WWN) Instance name CM0CA0Port0 CM1CA0Port0 0 0 E4000_CM0CA0P0 E4000_CM1CA0P0 fjpfca0 fjpfca1 fcp-bind-target="fjpfca0t0:e4000_cm0ca0p0","fjpfca1t0:e4000_cm1ca0p0"; 25

26 Chapter 6 Required Driver Parameters > 6.1 Setting Up the Parameters /kernel/drv/fjpfca.conf Example Description example for ETERNUS4000 # # All Rights Reserved, Copyright (c) FUJITSU LIMITED 2000 # #ident "@(#)$Id: fjpfca.conf,v /05/30 13:59:43 ueno Exp $ FUJITSU" # The fjpfca driver support connection to NL_port(FC-AL) and # F_Port/FL_Port(fabric). # It is necessary to define "port" property in order to communicate # with the fabric or N_port target. In addition, it is necessary # to define "fcp-bind-target" property in order to communicate # with the fabric. These need not be defined for FC-AL. # Other properties like "alias" and "max-throttle" are optional. # Alias name definition # You can create an alias definition for a specific WWN # with "alias" property. # SYNOPSIS: # alias="alias-name:wwn",...; # EXAMPLE: # alias="target_a:0x100000a0b ","target_b:0x100000a0b "; # #alias= # "TARGET_0A:0x100000a0b ", # "TARGET_1A:0x100000a0b ", Not required for FC-AL connection. # "TARGET_0B:0x100000a0b ", # "TARGET_1B:0x100000a0b "; alias= "E4000_CM0CA0P0:0x202000e000cb0001", "E4000_CM1CA0P0:0x203000e000cb0001"; # Port type definition # The port type definition sets the port mode for a specific instance. # If the "port" property is not defined, the fjpfca driver # will determine the port mode automatically during the initialization. # SYNOPSIS: # port="instance-name:[nport loop]",...; # EXAMPLE: # port="fjpfca0:nport","fjpfca1:loop"; # #port= # "fjpfca0:nport", # "fjpfca1:nport", # "fjpfca2:nport", Not required for FC-AL connection. # "fjpfca3:nport"; port= "fjpfca0:nport:sp4", "fjpfca1:nport:sp4"; # Target binding definition # fcp-bind-target binds a specific instance to a target ID. # You can use defined alias in "alias" property for the WWN. # SYNOPSIS: # fcp-bind-target="[target-name:[wwn alias-name]]",...; # EXAMPLE: # fcp-bind-target= "fjpfca0t0:0x100000a0b ","fjpfca1t0:target_b"; # 26

27 Chapter 6 Required Driver Parameters > 6.1 Setting Up the Parameters # #fcp-bind-target= # "fjpfca0t0:0x100000a0b ", # "fjpfca0t1:0x100000a0b ", Not required for FC-AL connection. # "fjpfca1t0:target_1a", # "fjpfca1t1:target_1b"; fcp-bind-target= "fjpfca0t0:e4000_cm0ca0p0", "fjpfca1t0:e4000_cm1ca0p0"; # Number of maximum commands per target definition # The driver uses the value specified by the max-throttle property # as a number a target of commands which can be issued simultaneously. # SYNOPSIS: # max-throttle="[target-name:number]",...; # EXAMPLE: # max-throttle="fjpfca0t0:240","fjpfca1t0:240"; # #max-throttle= # "fjpfca0t0:240", # "fjpfca0t1:128", For both FC-AL and Fabric connections, add these settings. # "fjpfca1t0:240", # "fjpfca1t1:128"; max-throttle= "fjpfca0t0:255", "fjpfca1t0:255"; 27

28 Appendix A Various Management Table Templates The following various management tables are required in "Chapter 4 Setting Up the Server" (page 11). Use them as required. A.1 WWN Instance Management Table for the Server WWN instance management table for the server Physical slot WWN Controller number Instance name name Physical path name 28

29 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 SCSI T_ID RAID-WWN Instance name Controller number 29

30 ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for Oracle Solaris Driver Settings for Fujitsu 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.

31