ETERNUS Disk storage systems Server Connection Guide ...storage-system.fujitsu.com/global/manual/diskarray/pdf/p3am-2682... · -Check the settings using the "grmpdautoconf" command

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 Fujitsu 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.

Fifth EditionDecember 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 FujitsuFibre 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 ETERNUSDisk 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).

ETERNUS Disk storage systems Server Connection Guide for Oracle Solaris

3 Copyright 2010 FUJITSU LIMITED

3AM-2682-05ENZ0

Preface

P

� 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 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.� The company names, product names and service names mentioned in this document are

registered trademarks or trademarks of their respective companies.



3AM-2682-05ENZ0

Preface

P

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.

Copyright 2010 FUJITSU LIMITED



3AM-2682-05ENZ0



P3AM-2682-05ENZ0

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.............................................................114.1 Creating a WWN Instance Management Table for the Server ......................... 124.2 Creating a WWN Instance Management Table for Storage System ................ 144.3 Creating a Target Binding Table ...................................................................... 154.4 Setting the Configuration File (fjpfca.conf) ....................................................... 164.5 Re-checking the Settings ................................................................................. 17

Chapter 5 Logical Unit Recognition .......................................................205.1 Recognizing Logical Units with the sd Driver ................................................... 20

5.1.1 Logical Unit Recognition ............................................................................................................ 205.1.2 Getting the Server to Recognize the Logical Units .................................................................... 21

5.2 Recognizing Logical Units with the hddv Driver ............................................... 23

Chapter 6 Required Driver Parameters..................................................246.1 Setting Up the Parameters ............................................................................... 24

6.1.1 fjpfca.conf Parameter Values .................................................................................................... 246.1.2 /kernel/drv/fjpfca.conf Example ................................................................................................. 26

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

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 Fujitsu web-site as required.

Refer

- "Chapter 2 Installing the Fibre Channel Card Driver" (page 9)- Used for driver installation

� Product manual

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 4 Setting Up the Server" (page 11)- "Appendix A Various Management Table Templates" (page 28)

Edit Configuration FileSet the driver parameters by editing the configuration file.

Refer

- "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



3AM-2682-05ENZ0

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.

Refer

- "Chapter 5 Logical Unit Recognition" (page 20)



3AM-2682-05ENZ0

Chapter 2 Installing the Fibre Channel Card Driver

P

Install the Fibre Channel card driver according to the installation guide provided with the FibreChannel card.



3AM-2682-05ENZ0

Chapter 3 Installing the hddv Driver

P

Use the hddv driver if it is already installed and used. Do not use the hddv driver for new connec-tions.



3AM-2682-05ENZ0

Chapter 4 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.Procedures are described below. Also refer to the FUJITSU PCI Fibre Channel manuals as nec-essary.

■ 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 thoseinformation 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)



3AM-2682-05ENZ0

Chapter 4 Setting Up the Server > 4.1 Creating a WWN Instance Management Table for the Server

P

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 enterit into a copy of the "WWN instance management table for the server" (provided in "Appendix AVarious Management Table Templates" (page 28)).

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

WWN Instance Management Table for the Server

Procedure

1 Check the instance names."fjpfca + 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".

Physical slot name

WWN Instance name Physical path name

"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.

# grep "fjpfca" /etc/path_to_inst

"/pci@6,4000/fibre-channel@2" 1 "fjpfca""/pci@4,2000/fibre-channel@1" 0 "fjpfca"

Physical path name Instance number

Physical slot name WWN Instance name Physical path name/pci@4,2000/fibre-channel@1/pci@6,4000/fibre-channel@2

fjpfca0fjpfca1



3AM-2682-05ENZ0

Chapter 4 Setting Up the Server > 4.1 Creating a WWN Instance Management Table for the Server

P

3 Check the WWN for the Fibre Channel card.Execute the following command to check the WWN that corresponds to the Fibre Channelcard instance name.

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

4 Enter the results in the "WWN" column of the "WWN instance management table for the server".Example

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.)

For the "Instance_name", use the Fibre Channel card instance names identified in Step1 (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.

The WWN for Fibre Channel card instance name "fjpfca0" is"100000000e248434" and WWN fo r " f j p fca1" i s"100000000e24846f".

To exit this command, press [Ctrl]+[C]. Alternatively, wait threeminutes to exit automatically.

# /usr/sbin/FJSVpfca/fc_info -a

adapter=fjpfca#0 wwn=100000000e248434 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=2112byteadapter=fjpfca#1 wwn=100000000e24846f 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


fjpfca0fjpfca1

100000000e248434100000000e24846f

# /usr/sbin/FJSVpfca/fc_adm -l Instance_name



3AM-2682-05ENZ0

Chapter 4 Setting Up the Server > 4.2 Creating a WWN Instance Management Table for Storage System

P

5-3 Enter the results in the "Physical slot name" column of the "WWN instance management table for the server".Example

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 AVarious Management Table Templates" (page 28)) that summarizes information relating to CA inthe ETERNUS Disk storage systems.

Example: When there are two ports on the ETERNUS Disk storage systems

� Channel AdapterCA name in the ETERNUS Disk storage systems

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

� Alias nameAn arbitrarily chosen name for each CA that may be used when setting up the fjpfca driver

� T_ID (SCSI target ID)The 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 it mustbe defined as a Solaris OS SCSI driver setting. Values matched to the server environmentand connection state of the devices must be set beforehand.It is recommended to set the same target ID to CAs that configures a multipath.


fjpfca0fjpfca1

100000000e248434100000000e24846f

SERV1_SLOT0SERV1_SLOT1

This use of "alias name" differs from the "alias name" that is specifiedwhen setting Fibre Channel switch zoning. However, it is recommendedto set both aliases to the same name.

Channel Adapter WWN Alias name T_IDCM0CA0Port0CM1CA0Port0

202000e000cb0001203000e000cb0001

E4000_CM0CA0P0 1616E4000_CM1CA0P0



3AM-2682-05ENZ0

Chapter 4 Setting Up the Server > 4.3 Creating a Target Binding Table

P

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 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.

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

� 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

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

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

00

E4000_CM0CA0P0E4000_CM1CA0P0

Server name: Server#0

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



3AM-2682-05ENZ0

Chapter 4 Setting Up the Server > 4.4 Setting the Configuration File (fjpfca.conf)

P

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.

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 RequiredDriver Parameters" (page 24).

[WWN instance management table for storage system]

[target binding table]

SERV1_SLOT0

SERV1_SLOT1

100000000e248434

100000000e24846f

fjpfca0

fjpfca1

Physical slot name WWN Instance name

0

0

CM0CA0Port0

CM1CA0Port0

E4000_CM0CA0P0

E4000_CM1CA0P0

Channel Adapter name SCSI T_ID Alias name (WWN) Instance name

fjpfca0

fjpfca1

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.

Check the "WWN instance management table for the server", "WWNinstance management table for storage system", and "target binding table"for any omissions.



3AM-2682-05ENZ0

Chapter 4 Setting Up the Server > 4.5 Re-checking the Settings

P

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 followingcommand:

If the settings are correct, the following message is displayed:

� Example

If the settings are incorrect, different messages (incorrect setting examples 1 and 2) willbe 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 physicalconnections may find the problem.

#/usr/sbin/FJSVpfca/chk_conf -v

/kernel/drv/fjpfca.conf seems to be correct

/kernel/dfv/fjpfca.conf seems to be correct.

******************************

*port definition*

instance status options------------------------------fjpfca1 found nportfjpfca2 found nport

*target definition*

instance t-id wwn status throt alias------------------------------------------------------------------------------fjpfca1 16 0x213100e000cb0001 detect UNDEF E4000_CM0CA0P0fjpfca2 17 0x212100e000cb0001 detect UNDEF E4000_CM1CA0P0



3AM-2682-05ENZ0


P

� Incorrect setting example 1Syntax error with the alias setting in the configuration file.

� Incorrect setting example 2Cables are not connected correctly.

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-bind-

target actually exists

#/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_CM1there were some non fatal errors in fjpfca.conf. Still trying to check it.

******************************

*port definition*


*target definition*

instance t-id wwn status throt alias------------------------------------------------------------------------------fjpfca1 16 0x213100e000cb0001 detect UNDEF E4000_CM0CA0P0fjpfca2 17 no binding none UNDEF E4000_CM1CA0P0

/usr/sbin/FJSVpfca/chk_conf -vtarget ’fjpfca1t16’(alias=E4000_CM0) seems to be absent on fjpfca#1target ’fjpfca2t17’(alias=E4000_CM1) seems to be absent on fjpfca#2

******************************

*port definition*


*target definition*

instance t-id wwn status throt alias------------------------------------------------------------------------------fjpfca1 16 0x213100e000cb0001 none UNDEF E4000_CM0CA0P0fjpfca2 17 no binding none UNDEF E4000_CM1CA0P0



3AM-2682-05ENZ0


P

2 Re-check target binding settingBy using the "chk_conf" command, you can check any errors in the configuration file, andcheck the Fibre Channel cable physical connections. However, you cannot confirmwhether or not target binding based upon the system configuration has been performedcorrectly 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?

End of procedure

Check the target binding values before rebooting the server. If theserver boots with a setting error, it may recognize a different storagesystem from that set in the system configuration, without generatinga connection error.



3AM-2682-05ENZ0

Chapter 5 Logical Unit Recognition

P

Logical units need to be recognized with the sd driver or hddv driver.

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 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.

5.1.1 Logical Unit Recognition

Add descriptions of the logical units to the sd driver configuration file (/kernel/drv/sd.conf) using atext editor, such as vi.

Skip this chapter if using the ETERNUS Multipath Driver or GRMultipath Driver "grmpdautoconf" command.

Refer to "5.2 Recognizing Logical Units with the hddv Driver" (page 23)when using the hddv driver.

Do not delete the lun=0 description for the system disk target ID.



3AM-2682-05ENZ0

Chapter 5 Logical Unit Recognition > 5.1 Recognizing Logical Units with the sd Driver

P

Example

� For FC-AL connectionSet the "target=" value the same as the Loop-ID set in the [Set CA Details] window ofETERNUSmgr.

� For Fabric connectionSet the "target=" value the same as the target ID of the "fcp-bind-target" parameter set in theconfiguration file. Refer to "6.1 Setting Up the Parameters" (page 24).

5.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.

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.

The ETERNUSmgr Loop-ID is natively set as a hexadecimal value,which must be converted to a decimal value for this setting.

## Copyright (c) 1992, by Sun Microsystems, Inc.##ident "@(#)sd.conf 1.9 98/01/11 SMI"

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


name="sd" class="scsi" target=2 lun=0; : :name="sd" class="scsi" target=16 lun=0;



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

# format



3AM-2682-05ENZ0

Chapter 5 Logical Unit Recognition > 5.1 Recognizing Logical Units with the sd Driver

P

� 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.

� Example 2 EFI disk labelsEFI labels are automatically assigned to 1TB and larger disks. However, even if thedisk capacity is less than 1TB, EFI labels can still be assigned using the "format -e"command, as shown in the following example.

End of procedure

# formatSearching for disks...done

c4t16d0: configured with capacity of 7.98GBc4t16d1: configured with capacity of 7.98GBc5t16d0: configured with capacity of 7.98GBc5t16d1: configured with capacity of 7.98GB

AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6851ce,0 1. c4t16d0 <FUJITSU-E4000-0000 cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@1/sd@10,0 2. c4t16d1 <FUJITSU-E4000-0000 cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@1/sd@10,1 3. c5t16d0 <FUJITSU-E4000-0000 cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@2/sd@10,0 4. c5t16d1 <FUJITSU-E4000-0000 cyl 1022 alt 2 hd 64 sec 256> /pci@9,600000/lpfc@2/sd@10,1Specify disk (enter its number):

# format -eSearching for disks...done

c5t16d0: configured with capacity of 3555.50GB

AVAILABLE DISK SELECTIONS:0. c0t0d0 <FUJITSU-MAP3367NC-3701 cyl 12435 alt 2 hd 10 sec 574> /pci@83,4000/FJSV,ulsa@2,1/sd@0,01. c5t16d0 <FUJITSU-E4000-0000-3.47TB> /pci@80,4000/lpfc@3/sd@10,0Specify disk (enter its number): 1selecting c5t16d0[disk formatted]format> label[0] SMI Label[1] EFI LabelSpecify Label type[0]: 1Ready to label disk, continue? yesformat> quit



3AM-2682-05ENZ0

Chapter 5 Logical Unit Recognition > 5.2 Recognizing Logical Units with the hddv Driver

P

5.2 Recognizing Logical Units with the hddv Driver

Logical units may be recognized using the hddv driver. Refer to the driver product manual formore details.

When connecting with the server running on Solaris 10 OS in a sin-gle-path configuration, logical units do not need to be recognizedwith the hddv driver.



3AM-2682-05ENZ0

Chapter 6 Required Driver Parameters

P

6.1 Setting Up the Parameters

The parameters in the "/kernel/drv/fjpfca.conf" configuration file need to be edited as describedbelow.

Edit the configuration file according to the following parameter list.

6.1.1 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.

Original configuration file must be backed up before editing.

cp /kernel/drv/fjpfca.conf ./ fjpfca.conf.backup

ParameterValue

(for FC-AL connection)

Value (for Fabric

connection)Remarks

alias Set if required Set if requiredSet an alias name for the WWN.It is easier to edit the setting files if this alias name is set.

port Not required nport

Link speed may be set to a fixed value. (*1)Set the topology and link speed.port="<instance name>:<topology>:<linkspeed>"The following <topology> parameters may be used: nport:Fabric connection loop:FC-AL connectionThe following <link speed> parameters may be used: sp1 for 1GB links sp2 for 2GB links sp4 for 4GB links



3AM-2682-05ENZ0

Chapter 6 Required Driver Parameters > 6.1 Setting Up the Parameters

P

*1: It is recommended that the link speed be set to a fixed value, rather than the auto negotiation setting.

fcp-bind-target Not required See 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 <aliasname>.

max-throttle

For the ETERNUS2000: 40

For the ETERNUS4000 and ETERNUS8000: 255

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

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.

� 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.

ParameterValue

(for FC-AL connection)

Value (for Fabric

connection)Remarks

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

00

E4000_CM0CA0P0E4000_CM1CA0P0

fjpfca0fjpfca1

fcp-bind-target="fjpfca0t0:E4000_CM0CA0P0","fjpfca1t0:E4000_CM1CA0P0";



3AM-2682-05ENZ0


P

6.1.2 /kernel/drv/fjpfca.conf Example

� Description example for ETERNUS4000

## All Rights Reserved, Copyright (c) FUJITSU LIMITED 2000##ident "@(#)$Id: fjpfca.conf,v 1.3 2000/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:0x100000a0b8030001","TARGET_B:0x100000a0b8030002";##alias=# "TARGET_0A:0x100000a0b8030001",# "TARGET_1A:0x100000a0b8030002",# "TARGET_0B:0x100000a0b8030003",# "TARGET_1B:0x100000a0b8030004";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",# "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:0x100000a0b8030001","fjpfca1t0:TARGET_B";#

Not required for FC-AL connection.




3AM-2682-05ENZ0


P

##fcp-bind-target=# "fjpfca0t0:0x100000a0b8030001",# "fjpfca0t1:0x100000a0b8030003",# "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",# "fjpfca1t0:240",# "fjpfca1t1:128";max-throttle= "fjpfca0t0:255", "fjpfca1t0:255";


For both FC-AL and Fabric connections, add these settings.



3AM-2682-05ENZ0

Appendix A Various Management Table Templates

P

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 name WWN Controller number Instance name Physical path

name



3AM-2682-05ENZ0

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



3AM-2682-05ENZ0

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

Driver Settings for Fujitsu Fibre Channel Cards

P3AM-2682-05ENZ0

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-2682... · -Check the settings using the "grmpdautoconf" command