Page 1
FUJITSU Storage
ETERNUS DX, ETERNUS AF
Configuration Guide -Server Connection-
(Fibre Channel) for Oracle Solaris
Driver Settings for Fujitsu Fibre Channel Cards
P3AM-3712-15ENZ0
Page 2
This page is intentionally left blank.
Page 3
This manual briefly explains the operations that need to be performed by the user in order to connect an
ETERNUS DX/AF to a server running Solaris OS and using Fujitsu Fibre Channel cards via a Fibre Channel interface.
This manual is used when performing the setup procedure described in "Installing Drivers and Setting Up the
Server" and "Recognizing the Logical Units" of the "Configuration Guide -Server Connection- (Fibre Channel)
for Oracle Solaris".
This manual should be used in conjunction with any other applicable user manuals, such as those for the
ETERNUS DX/AF, server, OS, Fibre Channel cards, and drivers.
Refer to "Configuration Guide -Server Connection- Notations" for the notations used in this manual such as
product trademarks and product names. For storage systems that are supported by the OS, refer to the Server
Support Matrix of the ETERNUS DX/AF.
The Contents and Structure of this Manual
Preface
15th Edition
April 2017
This manual is composed of the following six chapters and an appendix.
"Chapter 1 Workflow" (page 5)
•
This chapter describes the workflow required to establish a connection between a server with Fujitsu Fibre
Channel cards and an ETERNUS DX/AF.
"Chapter 2 Installing the Fibre Channel Card Driver" (page 7)
•
This chapter describes how to install the Fibre Channel card driver.
"Chapter 3 Installing the hddv Driver" (page 8)
•
This chapter describes how to install the hddv driver that is required when connecting the ETERNUS DX/AF
storage systems and a Fujitsu driver equipped server in a single-path configuration.
"Chapter 4 Setting Up the Server" (page 9)
•
This chapter describes how to set up the server for different connection topologies.
"Chapter 5 Setting Up the Server to Recognize the Logical Units" (page 18)
•
This chapter describes how to make the server recognize the LUNs of the ETERNUS DX/AF.
"Chapter 6 Required Driver Parameters" (page 22)
•
This chapter 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".
3
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 4
Table of Contents
Chapter 1 Workflow 5
Chapter 2 Installing the Fibre Channel Card Driver 7
Chapter 3 Installing the hddv Driver 8
Chapter 4 Setting Up the Server 9
4.1 Creating a WWN Instance Management Table for the Server.......................................................... 9
4.2 Creating a WWN Instance Management Table for Storage System ............................................... 12
4.3 Creating a Target Binding Table ................................................................................................... 13
4.4 Setting the Configuration File (fjpfca.conf) .................................................................................. 14
4.5 Re-checking the Settings.............................................................................................................. 14
Chapter 5 Setting Up the Server to Recognize the Logical Units 18
5.1 Recognizing Logical Units with the sd Driver................................................................................ 18
5.1.1 Logical Unit Recognition.....................................................................................................................................18
5.1.2 Getting the Server to Recognize the Logical Units...............................................................................................19
5.2 Recognizing Logical Units with the hddv Driver............................................................................ 21
Chapter 6 Required Driver Parameters 22
6.1 Setting Up the Parameters ........................................................................................................... 22
6.1.1 "fjpfca.conf" Parameter Values............................................................................................................................22
6.1.2 "/kernel/drv/fjpfca.conf" Example........................................................................................................................24
Appendix A Various Management Table Templates 25
A.1 WWN Instance Management Table for the Server ........................................................................ 25
A.2 WWN Instance Management Table for Storage System ................................................................ 25
A.3 Target Binding Table.................................................................................................................... 26
4
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 5
Chapter 1
Workflow
This chapter describes the driver settings required to establish a connection between a server with Fujitsu
Fibre Channel cards and an ETERNUS DX/AF.
Workflow
Installing the Fibre Channel Card Driver
Install the driver. Download the proper driver from the Fujitsu web-site as required.
"Chapter 2 Installing the Fibre Channel Card Driver" (page 7)
•
Used for driver installation
•
Documentation provided with the product
-
Creating Various Management Tables
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 9)
•
"Appendix A Various Management Table Templates" (page 25)
•
Editing the Configuration File
Set the driver parameters by editing the configuration file.
"Chapter 4 Setting Up the Server" (page 9)
•
"Chapter 6 Required Driver Parameters" (page 22)
•
Check the settings using the "grmpdautoconf" command
•
ETERNUS Multipath Driver product manual
-
5
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 6
Chapter 1 Workflow
Setting Up the Server to Recognize the Logical Units (LUNs)
Make the server recognize the ETERNUS DX/AF logical units using the sd driver.
"Chapter 5 Setting Up the Server to Recognize the Logical Units" (page 18)
•
After completing all the required procedures in this manual, proceed to "Setting the Multipaths" in
"Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris".
6
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 7
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.
7
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 8
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.
8
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 9
Chapter 4
● For direct connection
Setting Up the Server
The server setup will vary according to how the ETERNUS DX/AF 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: direct connection and switch connection. Procedures are described below. Also refer to the FUJITSU PCI Fibre Channel manuals as necessary.
Instance name data of the Fibre Channel card is necessary. Refer to the following sections to set.
"4.1 Creating a WWN Instance Management Table for the Server" (page 9)
•
"4.2 Creating a WWN Instance Management Table for Storage System" (page 12)
•
"4.4 Setting the Configuration File (fjpfca.conf)" (page 14)
•
"4.5 Re-checking the Settings" (page 14)
•
● For switch connection
The Fibre Channel card Instance name, target WWN, and target ID information are necessary. Check each
item and enter them in the table. Edit the configuration file according to those information and make settings.
Refer to the following sections to set.
"4.1 Creating a WWN Instance Management Table for the Server" (page 9)
•
"4.2 Creating a WWN Instance Management Table for Storage System" (page 12)
•
"4.3 Creating a Target Binding Table" (page 13)
•
"4.4 Setting the Configuration File (fjpfca.conf)" (page 14)
•
"4.5 Re-checking the Settings" (page 14)
•
4.1 Creating a WWN Instance Management Table for the Server
Create a "WWN instance management table for the server" with information regarding the Fibre Channel
card.
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 25)).
Physical slot name
•
WWN
•
Instance name
•
Physical path name
•
9
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 10
Physical slot name
WWN
Instance name
Physical path name
/pci@4,2000/fibre-channel@1
/pci@6,4000/fibre-channel@2
fjpfca0
fjpfca1
Chapter 4
4.1 Creating a WWN Instance Management Table for the Server
Setting Up the Server
Table 4.1 WWN Instance Management Table for the Server
Physical slot name WWN Instance name Physical path name
1
Check the instance names.
"fjpfca + instance number" is the format used to represent Fibre Channel card instance names.
The instance number that corresponds to the physical path in which the Fibre Channel card is installed
is stored in the "/etc/path_to_inst" file at the 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"
(1) (2)
(1) indicates the physical path name and (2) indicates the 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 manage-
ment table for the server".
3 Check the WWN of each 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
"adapter=fjpfca#x" ("x" is instance number) is the format used to represent Fibre Channel card instant
names. The WWN corresponding to the instance name is displayed after "wwn=".
10
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 11
Physical slot name
WWN
Instance name
Physical path name
/pci@4,2000/fibre-channel@1
/pci@6,4000/fibre-channel@2
fjpfca0
fjpfca1
100000000e248434
100000000e24846f
Chapter 4
4.1 Creating a WWN Instance Management Table for the Server
Setting Up the Server
Example:
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=2112byte
adapter=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
The WWN for Fibre Channel card instance name "fjpfca0" is "100000000e248434" and WWN for
"fjpfca1" is "100000000e24846f".
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.
(1) Execute the following command to check the physical slots where the Fibre Channel cards corre-
sponding 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").
(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.
11
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 12
Physical slot name
WWN
Instance name
Physical path name
/pci@4,2000/fibre-channel@1
/pci@6,4000/fibre-channel@2
fjpfca0
fjpfca1
100000000e248434
100000000e24846f
SERV1_SLOT0
SERV1_SLOT1
Channel Adapter
WWN
Alias name
T_ID
CM0CA0Port0
CM1CA0Port0
202000e000cb0001
203000e000cb0001
DX400_CM0CA0P0
16
16
DX400_CM1CA0P0
Chapter 4
4.2 Creating a WWN Instance Management Table for Storage System
Setting Up the Server
(3) Enter the results in the "Physical slot name" column of the "WWN instance management table for
the server".
Example:
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 Manage-
ment Table Templates" (page 25)) that summarizes information relating to CA in the ETERNUS DX/AF stor-
age systems.
(Example) When there are two ports on the ETERNUS DX/AF storage systems:
Channel Adapter
•
CA name in the ETERNUS DX/AF storage systems
WWN
•
The WWN for each CA in the ETERNUS DX/AF (check using ETERNUSmgr or ETERNUS Web GUI)
Alias name
•
An arbitrarily-chosen alias 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 or ETERNUS
Web GUI)
For switch connections, 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.
12
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 13
Channel Adapter name
SCSI T-ID
Alias name (WWN)
Instance name
CM0CA0Port0
CM1CA0Port0
0
0
DX400_CM0CA0P0
DX400_CM1CA0P0
Server name: Server#0
Server#0
Slot0
Slot1
CA0 Port0
CM0
CA0 Port1
ETERNUS DX/AF
Fibre Channel Switch A Fibre Channel Switch B
CM1
CA0 Port1 CA0 Port0
Chapter 4
4.3 Creating a Target Binding Table
Setting Up the Server
4.3 Creating a Target Binding Table
This procedure is not necessary for direct connections.
Target binding logically binds the Fibre Channel card installed in the server, and the CA on the ETERNUS
DX/AF 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.
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 25)).
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 12)
• The alias name entered in "4.2 Creating a WWN Instance Management Table for Storage System"
(page 12)
2 Confirm the connection path(s) in the system.
Example:
Physical slots on Server#0 and CAs on the ETERNUS DX/AF storage systems are connected in the following paths.
• Server#0 SLOT0 - CM0CA0
• Server#0 SLOT1 - CM1CA0
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
13
P3AM-3712-15ENZ0
Page 14
[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
DX400_CM0CA0P0
DX400_CM1CA0P0
Channel Adapter name SCSI T_ID Alias name (WWN)
Instance name
fjpfca0
fjpfca1
From the two tables,
find the same
combination of
physical slot name
and Channel
Adapter as listed in
the path route table.
1.
Record the instance
name in the same
row as the physical
slot name in the
target binding table.
2.
Chapter 4
4.4 Setting the Configuration File (fjpfca.conf)
Setting Up the Server
3 Based on the connection path(s) confirmed in Step 2 and the information in the "WWN instance man-
agement table for the server", enter the instance names corresponding to the physical slot names on
the server into the "target binding table".
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 Parame-
ters" (page 22).
Check the "WWN instance management table for the server", "WWN instance management table for storage system", and "target binding table" for any omissions.
4.5 Re-checking the Settings
After setting is complete, check for incorrect settings in the configuration file.
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
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
14
P3AM-3712-15ENZ0
Page 15
Chapter 4
4.5 Re-checking the Settings
Setting Up the Server
If the settings are correct, the following message is displayed:
/kernel/drv/fjpfca.conf seems to be correct
• Example:
/kernel/drv/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 DX400_CM0CA0P0
fjpfca2 17 0x212100e000cb0001 detect UNDEF DX400_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.
• 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:DX400_CM0
"kernel/drv/fjpfca.conf",error:no such alias:DX400_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 DX400_CM0CA0P0
fjpfca2 17 no binding none UNDEF DX400_CM1CA0P0
15
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 16
Chapter 4
4.5 Re-checking the Settings
Setting Up the Server
• Incorrect setting example 2
Cables are not connected correctly.
#/usr/sbin/FJSVpfca/chk_conf -v
target 'fjpfca1t16'(alias=DX400_CM0) seems to be absent on fjpfca#1
target 'fjpfca2t17'(alias=DX400_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 DX400_CM0CA0P0
fjpfca2 17 no binding none UNDEF DX400_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-bind-target actually exists
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" set up according to the information of the target binding table?
16
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 17
Chapter 4 Setting Up the Server
4.5 Re-checking the Settings
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
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 18
Chapter 5
Setting Up the Server to Recognize the Logical
Units
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
Make the server recognize the ETERNUS DX/AF logical units using the sd driver.
First, confirm that the logical unit settings on the ETERNUS DX/AF storage systems are correct. Next, add the
descriptions of the logical units in the sd driver's configuration file (sd.conf) to register the units.
Then reboot the server to get it to recognize the logical units.
Refer to "5.2 Recognizing Logical Units with the hddv Driver" (page 21) when using the hddv driver.
5.1.1 Logical Unit Recognition
Add descriptions of the logical units to the sd driver configuration file (sd.conf) using a text editor, such as vi.
Solaris 11 OS
•
If the "/etc/driver/drv/sd.conf” file does not exist, copy the "/kernel/drv/sd.conf" file to the "/etc/driver/drv"
directory and add the line to the newly copied "sd.conf" file.
If the "/etc/driver/drv/sd.conf” file exists, do not copy over the file but instead add the line to the existing
"sd.conf" file.
Solaris 10 OS
•
Add the line to the "/kernel/drv/sd.conf" file.
Do not delete the lun=0 description for the system disk target ID.
18
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 19
Chapter 5
5.1 Recognizing Logical Units with the sd Driver
Setting Up the Server to Recognize the Logical Units
Example:
#
# 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=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 direct connection
•
Set the "target=" value the same as the Loop-ID set in the [Set CA Parameters] window of ETERNUS Web
GUI or ETERNUSmgr.
The ETERNUS Web GUI or ETERNUSmgr Loop-ID is natively set as a hexadecimal value, which must be
converted to a decimal value for this setting.
For switch 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 22).
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.
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
19
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 20
Chapter 5
5.1 Recognizing Logical Units with the sd Driver
Setting Up the Server to Recognize the Logical Units
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
• Example 1: VTOC disk labels
- Target ID=16, lun=0 and 1 of ETERNUS DX400/DX400 S2 series 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 ETERNUS DX400/DX400 S2 series 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 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6851ce,0
1. c4t16d0 <FUJITSU-ETERNUS_DX400 cyl 1022 alt 2 hd 64 sec 256>
/pci@9,600000/lpfc@1/sd@10,0
2. c4t16d1 <FUJITSU-ETERNUS_DX400 cyl 1022 alt 2 hd 64 sec 256>
/pci@9,600000/lpfc@1/sd@10,1
3. c5t16d0 <FUJITSU-ETERNUS_DX400 cyl 1022 alt 2 hd 64 sec 256>
/pci@9,600000/lpfc@2/sd@10,0
4. c5t16d1 <FUJITSU-ETERNUS_DX400 cyl 1022 alt 2 hd 64 sec 256>
/pci@9,600000/lpfc@2/sd@10,1
Specify disk (enter its number):
20
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 21
Chapter 5
5.2 Recognizing Logical Units with the hddv Driver
Setting Up the Server to Recognize the Logical Units
• 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 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,0
1. c5t16d0 <FUJITSU-ETERNUS_DX400-3.47TB>
/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
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.
21
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 22
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.
Example:
cp /kernel/drv/fjpfca.conf ./ fjpfca.conf.backup
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.
•
Parameter
alias Set if required Set if required Set an alias name for the WWN.
port Not required nport Link speed may be set to a fixed value. (*1)
fcp-bindtarget
Setting value (for
direct connection)
Not required See remarks Binds the instance and the ETERNUS DX/AF storage systems' CA
Setting value
(for switch connec-
tion)
Remarks
It is easier to edit the setting files if this alias name is set.
Set the topology and link speed.
port="<Instance name>:<Topology>:<Link speed>"
The following <topology> parameters may be used:
nport: Switch connection
loop: Direct connection
The following <link speed> parameters may be used:
sp1 for 1Gbit/s links
sp2 for 2Gbit/s links
sp4 for 4Gbit/s links
port together.
fcp-bind-target="<Instance name>t<SCSI target ID>:<alias name>"
(<WWN> can be used instead of the <alias name>.)
22
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 23
Channel Adapter name
SCSI T-ID
Alias name (WWN)
Instance name
CM0CA0Port0
CM1CA0Port0
0
0
DX400_CM0CA0P0
DX400_CM1CA0P0
fjpfca0
fjpfca1
fcp-bind-target="fjpfca0t0:DX400_CM0CA0P0","fjpfca1t0:DX400_CM1CA0P0";
Chapter 6
6.1 Setting Up the Parameters
Required Driver Parameters
Setting value
(for switch connec-
tion)
Arbitrary (*2) (Up to
512 for each FC port
of the ETERNUS
DX/AF)
Remarks
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 sequentializing.
Specify this for all the ETERNUS DX/AF storage systems' access
paths.
The "max-throttle-all" property does not need to be set.
Parameter
max-throttle
Setting value (for
direct connection)
Arbitrary (*2)
(Up to 512 for each
FC port of the ETERNUS DX/AF)
*1: It is recommended that the link speed be set to a fixed value, rather than the auto negotiation setting.
*2: Recommended value = 512 ¸ (number of Fibre Channel ports that are connected to a single CA port) ¸
number of LUNs
(Round the result down)
Use the value of "8" if the actual result is lower.
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 DX/AF storage systems. For the fcp-
•
bind-target setting, see the target binding table.
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
23
P3AM-3712-15ENZ0
Page 24
#
# 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= "DX400_CM0CA0P0:0x202000e000cb0001",
"DX400_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";
#
#
#fcp-bind-target=
# "fjpfca0t0:0x100000a0b8030001",
# "fjpfca0t1:0x100000a0b8030003",
# "fjpfca1t0:TARGET_1A",
# "fjpfca1t1:TARGET_1B";
fcp-bind-target= "fjpfca0t0:DX400_CM0CA0P0",
"fjpfca1t0:DX400_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 direct connections, set this parameter if required.
For both direct connections and switch connections, add this setting.
For direct connections, this setting is not required.
For direct connections, this setting is not required.
Chapter 6 Required Driver Parameters
6.1 Setting Up the Parameters
6.1.2 "/kernel/drv/fjpfca.conf" Example
Description example for ETERNUS DX400/DX400 S2 series
•
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
24
P3AM-3712-15ENZ0
Page 25
Appendix A
Various Management Table Templates
The following various management tables are required in "Chapter 4 Setting Up the Server" (page 9).
Use them as required.
A.1 WWN Instance Management Table for the Server
WWN instance management table for the server
Physical slot name WWN Controller number Instance name Physical path name
A.2 WWN Instance Management Table for Storage System
WWN instance management table for storage system
Channel Adapter WWN T_ID
25
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 26
Appendix A Various Management Table Templates
A.3 Target Binding Table
A.3 Target Binding Table
Target binding table
Server name:
Channel Adapter name SCSI T_ID RAID-WWN Instance name Controller number
26
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
Copyright 2017 FUJITSU LIMITED
P3AM-3712-15ENZ0
Page 27
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection-
(Fibre Channel) for Oracle Solaris
Driver Settings for Fujitsu Fibre Channel Cards
P3AM-3712-15ENZ0
Date of issuance: April 2017
Issuance responsibility: FUJITSU LIMITED
The content of this manual is subject to change without notice.
•
This manual was prepared with the utmost attention to detail. However, Fujitsu shall assume no responsibility for any
•
operational problems as the result of errors, omissions, or the use of information 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.
The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission from
•
Fujitsu.
Page 28
Loading...