Sie sind auf Seite 1von 80

FUJITSU PCI Fibre Channel 4.

0 Update2 Guide
for Solaris (TM) Operating System -
Contents
Chapter 1 Overview .................................................................................................. 1
1.1 Function Overview ...................................................................................................................... 1
1.2 Hardware Support ....................................................................................................................... 2
1.3 Related Software......................................................................................................................... 7

Chapter 2 Configuration............................................................................................ 9
2.1 Installing the Driver ..................................................................................................................... 9
2.2 Configuring the driver software ................................................................................................... 9
2.3 Configuring Input-Output Devices ............................................................................................. 14
2.4 SCSI Target Driver Configuration.............................................................................................. 14

Chapter 3 Utility Commands................................................................................... 17


3.1 fc_info........................................................................................................................................ 17
3.2 chgfcctl ...................................................................................................................................... 21
3.3 alpa .......................................................................................................................................... 23
3.4 fc_adm....................................................................................................................................... 23
3.5 ns_show .................................................................................................................................... 25
3.6 chk_conf .................................................................................................................................... 26
3.7 clchgfc ....................................................................................................................................... 28
3.8 fc_config .................................................................................................................................... 32
3.9 fc_checkc .................................................................................................................................. 33
3.10 fc_hbaprp ................................................................................................................................ 36

Chapter 4 Troubleshooting ..................................................................................... 41

Appendix A Messages ............................................................................................ 45


A.1 fjpfca ......................................................................................................................................... 45
A.2 chgfcctl...................................................................................................................................... 55
A.3 chk_conf.................................................................................................................................... 57
A.4 clchgfc....................................................................................................................................... 59
A.5 fc_hbaprp .................................................................................................................................. 60
A.6 ns_show.................................................................................................................................... 63

Appendix B Conversion Table of Target IDs and AL_PAs..................................... 65

Appendix C How to examine instance name and installing slot ............................ 67

Appendix D Property list of fjpfca.conf file ............................................................. 69

Appendix E About the transmission route confirmation method when some


fibre channel cards are installed ................................................................. 73
E.1 Outline....................................................................................................................................... 73
E.2 Detail ....................................................................................................................................... 73
E.3 Validity confirmation of transmission route ............................................................................... 74

i
ii
Chapter 1 Overview
This chapter discusses the following:
· Functions of FUJITSU PCI Fibre Channel 4.0
· Specifications for the fibre channel card(GP7B8FC1U, PW008FC2U, PW008FC3U, SE0X7F11X, SE0X7F12X)
· Specifications for connectable input-output devices
· Related software

1.1 Function Overview


FUJITSU PCI Fibre Channel 4.0 is a SCSI Host Bus Adapter (HBA) driver that supports FCP (the Fibre Channel Protocol for
SCSI) as the SCSI protocol for the Fibre Channel. This software supports arbitrated loop(Private loop only) topology, connection
to F_Port/FL_Port of fabric. It does not support connection to N_Port of devices (point-to-point connections).

[Figure 1-1 Fibre Channel topologies supported by this software (1) - FC-AL]

1
[Figure 1-2 Fibre Channel topologies supported by this software (2) - Fabric]
This software complies with the following specifications:
· ANSI X3.230-1994, Fibre Channel - Physical and Signaling Interface (FC-PH)
· ANSI X3.297-1997, Fibre Channel - Physical and Signaling Interface-2(FC-PH-2)
· ANSI X3.272-1996, Fibre Channel - Arbitrated Loop(FC-AL)
· ANSI X3.269-1996, Fibre Channel Protocol for SCSI
· ANSI X3T11, Fibre Channel - Private Loop SCSI Direct Attach(FC-PLDA), Rev 2.1
· NCITS TR-20:1998, Fibre Channel - Fabric Loop Attachment(FC-FLA), Rev 2.7
· NCITS TR-xx:1999, Fibre Channel Tape, Rev 1.17
· NCITS.xxx:200x, Fibre Channel Protocol for SCSI, Second Version(FCP-2), Revision 05
· NCITS.xxx-200x, Fibre Channel - Framing and Signaling(FC-FS), Revision 1.50

1.2 Hardware Support


This section describes the hardware supported by this software.

1.2.1 Fibre Channel card(GP7B8FC1U or GP7B8FC1X)


This adapter is used by installing it in a PCI slot on the server. The adapter has one port for connection to FC_AL (Fibre Channel
Arbitrated Loop).

1.2.1.1 Specifications
Below are the specifications for the adapter:

2
[Table 1-1 Fibre Channel specifications]
Physical layer 100MB/sec, 1062.5 Mbit/sec
Multimode fibre(50 micrometer)
Shortwave laser(780 nanometer)
Medium interface
Non-OFC(Non-Open Fibre Control)
Duplex SC connector
Topology Arbitrated loop(Private loop), Fabric(F_port, FL_port)
Protocol FCP (Fibre Channel Protocol for SCSI)
Support class Class 3
[Table 1-2 PCI bus specifications]
Specification compliance PCI Local Bus Specification 2.1
Bus width 32bits or 64bits
Operating clock 33 MHz
Operating voltage 5V or 3.3V

1.2.1.2 Physical description


Figure 1-3 show the front of the Fibre Channel card. The various parts, together with their features, are as follows:
· Optical module
The optical module is connected to a Fibre Channel hub or Fabric or a disk array device with an optical fibre cable.
· SIG(Signal Detect)
This LED lights when optical signals from the connected device are detected at the receiving end of the optical module on
the adapter. SIG lights only if the optical fibre cable is connected. If the LED does not light even though the optical fibre
is connected and the device to which the other end of the cable is connected is in operational status, the optical fibre cable
may be broken, the optical module on the adapter may be faulty, or the optical module on the connected device may be
faulty.
· HB(Heart Beat)
This LED lights when the Fibre Channel control LSI chip on the adapter is operating. (Actually, the LED blinks so
quickly that it appears dimly lit.)
· LINK(Link) (*1)
This LED lights when Fibre Channel is in the communication-enabled state.
· CHK(Check) (*1)
This LED is not currently used.
*1: LED of LINK and CHK can be blinked by using the fc_adm command. Please refer to the "3.4 fc_adm command" for details.

[Figure 1-3 Front view of the Fibre Channel card]

1.2.1.3 Connectable input-output devices


Connection of the following devices to this software is assured:
Disk array devices.
· GP-DxxF2x disk array device (FC-AL)
· GP-DxCKFx, GP-DxRxFx disk array device (FC-AL, Fabric)
· PW-D500x1, PW-D5L1A1(FC-AL, Fabric)
· GR700 series devices (F6403xx) (FC-AL, Fabric *1)
· F649x disk array device (FC-AL, Fabric)
· GR720 device (GR72Axx, GR72Bxx) (FC-AL, Fabric)

3
· GR730 device (GR73Axx, GR73Bxx) (FC-AL, Fabric)
· GR740 device (FC-AL, Fabric)
· GR820 device (FC-AL, Fabric)
· GR840 device (FC-AL, Fabric)
· ETERNUS 2000/3000/4000/6000/8000 device(FC-AL, Fabric)
*1: When you use GR700 series (F6403xx) as a dump device, connection type must be set in Arbitrated loop (private loop). The
Fabric connection of GR700 series (F6403xx) cannot be set as the dump device.
Tape devices.
· LT300N (use Crossroads(TM) 4150 (Fibre Channel to SCSI Router))
· ETERNUS LT130/LT160

1.2.2 Fibre Channel card(PW008FC3U/PW008FC3X/PW008FC2U or PW008FC2X)


This adapter is used by installing it in a PCI slot on the server. The adapter has one port for connection to FC_AL (Fibre Channel
Arbitrated Loop).

1.2.2.1 Specifications
Below are the specifications for the adapter:
[Table 1-3 Fibre Channel specifications]
100MB/sec, 1062.5 Mbit/sec
Physical layer
200MB/sec, 2125 Mbit/sec, (maximum FC cable length 300m)
Multimode fibre(50 micrometer)

Medium Shortwave laser(780 nanometer)


interface Non-OFC(Non-Open Fibre Control)
Duplex LC connector
Topology Arbitrated loop(Private loop), Fabric(F_port, FL_port)
Protocol FCP (Fibre Channel Protocol for SCSI)
Support class Class 3
[Table 1-4 PCI bus specifications]
Specification compliance PCI Local Bus Specification 2.2
Bus width 32bits or 64bits
Operating clock 33 MHz or 66 MHz
Operating voltage 5V or 3.3V

1.2.2.2 Physical description


Figure 1-4 show the front of the Fibre Channel card. The various parts, together with their features, are as follows:
· Optical module
The optical module is connected to a Fibre Channel hub or Fabric or a disk array device with an optical fibre cable.
· SIG(Signal Detect)
This LED lights when optical signals from the connected device are detected at the receiving end of the optical module on
the adapter. SIG lights only if the optical fibre cable is connected. If the LED does not light even though the optical fibre
is connected and the device to which the other end of the cable is connected is in operational status, the optical fibre cable
may be broken, the optical module on the adapter may be faulty, or the optical module on the connected device may be
faulty.
· LINK(Link) (*1)
This LED lights when Fibre Channel is in the communication-enabled state.
· 2G
This LED lights when the Fibre Channel link speed is 2Gbps.
*1: LED of LINK can be blinked by using the fc_adm command. Please refer to the "3.4 fc_adm command" for details.

4
[Figure 1-4 Front view of the Fibre Channel card]

1.2.2.3 Connectable input-output devices


Connection of the following devices to this software is assured:
Disk array devices.
· GP-DxCKFx, GP-DxRxFx disk array device (FC-AL, Fabric)
· PW-D500x1, PW-D5L1A1(FC-AL, Fabric)
· GR700 series devices (F6403xx) (FC-AL, Fabric *1)
· F649x disk array device (FC-AL, Fabric)
· GR720 device (GR72Axx, GR72Bxx) (FC-AL, Fabric)
· GR730 device (GR73Axx, GR73Bxx) (FC-AL, Fabric)
· GR740 device (FC-AL, Fabric)
· GR820 device (FC-AL, Fabric)
· GR840 device (FC-AL, Fabric)
· ETERNUS 2000/3000/4000/6000/8000 device (FC-AL, Fabric)
*1: When you use GR700 series (F6403xx) as a dump device, connection type must be set in Arbitrated loop (private loop). The
Fabric connection of GR700 series (F6403xx) cannot be set as the dump device.
Tape devices.
· LT300N (use Crossroads(TM) 4150 (Fibre Channel to SCSI Router))
· ETERNUS LT130/LT160

1.2.3 Fibre Channel card(SE0X7F11X/SE0X7F12X)


This adapter is used by installing it in a PCI slot on the server. The adapter has one port for connection to FC_AL (Fibre Channel
Arbitrated Loop).

1.2.3.1 Specifications
Below are the specifications for the adapter:
[Table 1-5 Fibre Channel specifications]
100MB/sec, 1062.5 Mbit/sec
Physical layer 200MB/sec, 2125 Mbit/sec, (maximum FC cable length 300m)
400MB/sec,4250Mbit/sec, (maximum FC cable length 150m)
Multimode fibre(50 micrometer)

Medium Shortwave laser(780 nanometer)


interface Non-OFC(Non-Open Fibre Control)
Duplex LC connector
Topology Arbitrated loop(Private loop), Fabric(F_port, FL_port)
Protocol FCP (Fibre Channel Protocol for SCSI)
Support class Class 3

5
SE0X7F11X : 1 port
Number of port
SE0X7F12X : 2 port

[Table 1-6 PCI Express bus specifications]


Specification compliance PCI Express Specification 1.1a
Number of lane x4

1.2.3.2 Physical description


Figure 1-5 show the front of the Fibre Channel card. The various parts, together with their features, are as follows:
· Optical module
The optical module is connected to a Fibre Channel hub or Fabric or a disk array device with an optical fibre cable.
· SIG(Signal Detect)
This LED lights when optical signals from the connected device are detected at the receiving end of the optical module on
the adapter. SIG lights only if the optical fibre cable is connected. If the LED does not light even though the optical fibre
is connected and the device to which the other end of the cable is connected is in operational status, the optical fibre cable
may be broken, the optical module on the adapter may be faulty, or the optical module on the connected device may be
faulty.
· LINK(Link) (*1)
This LED lights or brinks when Fibre Channel is in the communication-enabled state.

When the transfer rate is 1Gbps, it blinks once every Green and two seconds.
When the transfer rate is 2Gbps, it blinks once Green and a second.
When the transfer rate is 4Gbps, it always lights Green.
However Execution time of -l option with fc_adm command blinks with Amber.
*1: LED of LINK can be blinked by using the fc_adm command. Please refer to the "3.4 fc_adm command" for details.

[Figure 1-5 Front view of the Fibre Channel card (SE0XF711X) ]

[Figure 1-6 Front view of the Fibre Channel card (SE0XF712X) ]

6
1.2.3.3 Connectable input-output devices
Connection of the following devices to this software is assured:
Disk array devices.
· ETERNUS 2000/3000/4000/6000/8000 (FC-AL, Fabric)
Tape devices.
· LT300N (use Crossroads(TM) 4150 (Fibre Channel to SCSI Router))
· ETERNUS LT130/LT160/LT270

1.3 Related Software


The following software is related to this software:
1. Hard disk driver (FJSVhddv)
2. Multipath disk control (FJSVmphd)
3. GR multipath driver(GRMPD)
4. ETERNUS Multipath driver (ETERNUS MPD)

The hard disk driver (FJSVhddv) can recognize such hardware error information as degradation specific to GP-DxxF2x,
GP-DxCKFx, GP-DxRxFx, PW-D500x1, PW-D5L1A1, GR700 series (F6403xx), GR720(GR72Axx, GR72Bxx),
GR730(GR73Axx, GR73Bxx), GR740, GR820 and GR840 products. This driver is upwardly compatible with the sd driver (the
standard SCSI disk driver for Solaris).
The multipath disk control software is used in combination with the hard disk driver to provide path switching if a path failure
such as a controller failure or a cable failure occurs when a disk array device with more than one controller is used.
Use of these two software programs enables a more reliable system to be constructed.
Notes:
The hot system replacement of device with the Fabric connection(*1) cannot be selected from the hot system replacement menu of
MPHD Viewer in the Multipath Disk Controller 1.x. In that case, use the clchgfc command included in this driver to select the hot
system replacement of the device. Refer to "3.7 clchgfc" for details.
*1: This actually indicates the connection type of the target device shown by the fcp-bind-target property of /kernel/drv/
fjpfca.conf file.

7
8
Chapter 2 Configuration
This chapter describes the tasks required to enable the SCSI target driver to recognize devices after installation of this software.
These tasks are explained in the following order:
· Installing the driver
· Configuring the driver software
· Configuring the input-output devices
· Configuring the SCSI target driver

2.1 Installing the Driver


To use the FUJITSU PCI Fibre Channel 3.0, install the driver package stored on the CD-ROM included with the adapter. For the
installation procedure, refer to the "Installation Guide - FUJITSU PCI Fibre Channel 4.0". FJSVpfca package includes the fjpfca
driver (SCSI HBA driver for the GP7B8FC1U/ GP7B8FC1X/ PW008FC2U/ PW008FC2X/ PW008FC3U/ PW008FC3X/
SE0X7F11X or SE0X7F12X).

2.2 Configuring the driver software


This section explains the required settings for the driver software.

2.2.1 Device identification by the fjpfca driver


Each Fibre Channel device has the following identifying information:
· WWN(World Wide Name)
64-bit identifier specific to each device. To be exact, each device has two WWNs, a Port name and a Node name. When
simply discussing the WWN related to this software, this manual refers to the Port name.
· Port ID
A 24-bit address used in Fibre Channel communication. This is used as a destination address or a source address. In an
arbitrated loop with no fabric device supported by this software, all of the high-order 16 bits of the port ID for each
device are 0. Although the port ID is temporarily determined when an arbitrated loop is established, there are methods of
preconfiguring a preferred port ID for most target devices.
· AL_PA
An address in the arbitrated loop. This is equal to the low-order 8 bits of the port ID. The AL_PA consists of 126
non-consecutive values from 0x01 to 0xEF. In addition to being the port ID, the AL_PA is also a temporary ID determined
when the arbitrated loop is established.
The driver in the Solaris operating system has the following identifying information.
· Driver Name
The driver software installed in the Solaris operating system has a unique driver name in each product. This driver name
is "fjpfca" .
· Instance Number
The installed adapter has the series of numbers (0,1,2, ...) in the controlled drivers. This number is called an instance
number.
· Instance Name
The instance name is an identifier that is described as a pair of the name of the driver name and the instance number.
This can be used to identify the adapter as a unique name. In this driver software, the Fibre Channel card has the instance
name such as fjpfca0, fjpfca1, fjpfca2, ... to be used by the driver in various setting. In Fabric connection, Each Fibre
Channel card is set by using this instance name.
The SCSI target driver for Solaris (the SCSI disk driver, etc.), on the other hand, identifies devices by target ID. Therefore, to use
Fibre Channel devices as SCSI devices, the target IDs must be associated with the equivalent Fibre Channel identifiers. In
Arbitrated loop and Fabric connection, the method is different.
· For Arbitrated loop
In the fjpfca driver, the target IDs are associated with the above three types of identifying information according to the
following rules:
1. For device recognition according to information in the device configuration of the SCSI target driver (such as sd.conf),
the driver retrieves the device whose AL_PA corresponds to the target ID specified by the SCSI target driver.
Correspondence of AL_PAs and target IDs are shown in Table 2-1.
2. Once the devices are recognized, input-output is executed with reference to the WWNs of the devices. In this way,
input-output with the wrong disk device can be prevented even though the AL_PA or port ID are changed during
operation.
[Table 2-1 Correspondence of Target IDs and AL_PAs(partial list)]
Target ID 0 1 2 ... 123 124 125
AL_PA 0xEF 0xE8 0xE4 ... 0x04 0x02 0x01

9
For the complete correspondence of target IDs and AL_PAs, see "Appendix B Conversion Table of Target IDs and AL_PAs".
This software provides commands for both-way conversions between target ID and AL_PA. For details, see "3.3 alpa command."
· For Fabric
Because the number of the SCSI device which can be connected becomes huge at the Fabric connection; It is general to
define target ID in software on the server side. AL_PA (Or, target ID) need not be set on the target device.
For the fjpfca driver, it defines to the file of driver's environment definition to which target device which fibre channel
card accesses in which target ID. It uses WWN of the above-mentioned instance name, target ID, and the target device for
these definitions. Target ID can freely set for it is not to overlap by the definition in one instance name.
After the device defined in the environment definition file was able to be recognized, I/O is executed based on WWN of
each device as well as Arbitrated Loop.
Please refer to the paragraph of each explanation for a detailed set method of the Arbitrated Loop(FC-AL) connection and the
Fabric connection.
· Configuring FC-AL connections
· Configuring Fabric connections
· Other configurations
· Verifying the environment definition file

2.2.2 Configuring FC-AL connections


In FC-AL connection, an environment setting of the driver is not required. Otherwise the common setting that does not depend on
connecting topology might be necessary. Please refer to "2.2.4 Other configurations" for the detailed configuration of setting file if
necessary, then go to the next section "2.3 2.3 Configuring the Input-Output Devices."

2.2.3 Configuring Fabric connections


When the adapter is connected with the Fabric, an environment setting of the driver must be configured. The environment
definition file is in /kernel/drv/fjpfca.conf, the template of this definition file is installed with the driver installation. By default,
the file contains no information.
To define the environment setting file:
· Collecting the setting information (instance names, target WWNs, target IDs)
· Editing an environment definition file
· Verifying the definition file with the chk_conf command
In this example, the following connection model is applied.

1. Collecting the setting information


1. Instance Name
An environment setting is done in each adapter. The fjpfca driver is recognizing the adapter by the instance name,
which is a combination of the identification number (instance number: 0,1,2,...) allocated in an individual adapter
and the driver software name (fjpfca). This identifier uniquely designates the adapter names.

10
After the driver installation, the instance number corresponding to a physical path name of the mounting adapter
is stored in "device instance number file" in /etc/path_to_inst. To select where the fjpfca driver is listed in the file,
execute the following command.
# grep fjpfca /etc/path_to_inst
"/pci@6,4000/fibre-channel@2" 1 "fjpfca"
"/pci@4,2000/fibre-channel@1" 0 "fjpfca"
The selected part consists of the following format:
"physical name" instance number "driver name"
Where the instance name is a combination of the driver name and the instance number, the following format can
be shown:
The instance name of the adapter mounted at /pci@6,4000/fibre-channel@2 = fjpfca1
The instance name of the adapter mounted at /pci@4,2000/fibre-channel@1 = fjpfca0
Additionally, the method of confirming the instance name includes the following methods.
· Method to judge by message output when cable is pulled out and opened
· Method of blinking LED of adaptor of specified instance name by using fc_adm command
Please refer to "Appendix C How to examine instance name and installing slot " for details. There is a possibility
that the problem which has been described to "Appendix E About the transmission route confirmation method
when some fibre channel cards are installed" occurs when the correspondence of the instance name and the
installing slot is mistaken.
2. WWN (Port Name) of target devices
WWN (Port Name) of the controller in the connecting target device is checked. The device has the WWN that is
the device dependent identifier with 64bit length. With its varied checking method, refer to the manual of each
device to check the instance name.
3. Target ID
SCSI target ID of the connecting device is defined. In the Fabric connection, SCSI target ID is defined by the
software setting of the driver. Defining the SCSI target ID by the target device is not required.
Summary of the collected information is as follows:
instance target WWN (Port Name) of the
physical name
name ID(*1) target devices
0 50000e1000002501
/pci@4,2000/fibre-channel@1 fjpfca0
2 50000e1000003000
1 50000e1000002ab0
/pci@6,4000/fibre-channel@2 fjpfca1
3 50000e1000003c00
*1: It corresponds to target ID which described it in the device configuration of the SCSI target driver (such as
sd.conf).
2. Editing the environment definition file
1. Editing the fjpfca.conf file
Edit the /kernel/drv/fjpfca.conf file using with the text editor based on the collected information. The template
file of the fjpfca.conf is installed with the driver installation by the same name. Edit the file as follows at this
configuration:
alias =
"STORAGE_0A:0x50000e1000002501",
"STORAGE_1A:0x50000e1000002ab0",
"STORAGE_0B:0x50000e1000003000",
"STORAGE_1B:0x50000e1000003c00";
port =
"fjpfca0:nport:sp2",
"fjpfca1:nport";
fcp-bind-target =
"fjpfca0t0:STORAGE_0A",
"fjpfca0t2:0x50000e1000002ab0",
"fjpfca1t1:STORAGE_0B",
"fjpfca1t3:STORAGE_1B";
2. PROPERTY DESCRIPTION
- alias(optional)
Set the aliases for WWN(Port Name).
·SYNOPSIS:
alias = "alias name:WWN",....;
alias name:
You can use character strings which consists of alphabet (A-Z,a-z), figure (0-9), and sign ( _ , - , # ).
The alias name should be case sensitive. It sets it by 16 characters or less which start by the alphabet.
WWN:

11
WWN of controller for which alias name is defined. Specify the hexadecimal(eight bytes) by adding "0x"
in the head.
- port(required)
Define the connecting topology types. This should be defined for every instance.
·SYNOPSIS:
port = "instance name:connecting topology[:link speed]",....;
instance name:
Represent the adapter identifier which consists of the driver name (fjpfca0) and the instance number.
connecting topology:
In Fabric connections, fixed value as "nport." When the nport is not selected, the value is set
automatically. The common connecting topology is NL_port (loop connection). Using the 3.1 fc_info
command allows you to obtain the current connecting topology being used.
link speed:
Define the link speed. If you specify "sp1", the link speed is fixed to 1Gbps(1062.5Mbps). If you
specify "sp2", the link speed is fixed to 2Gbps(2125 Mbps). If you specify “sp4”, the link speed is
fixed 4Gbps(4250Mbps). If you don't specify this parameter, link speed will be automatically
negotiated with the peer port at the maximum link speed that both ports can communicate.
The automatic setting of the link speed is an easy way, but link speed might be change according to
status of a connected device and link up timing and not be a maximum rate which is supported by a
connected device. Therefore, especially for 4Gbps, link speed might not be a maximum and might be
changed with every link up. Specifying link speed to be a fixed value (sp2 or sp4) is recommended.
Each link speed has limitation of cable length.
z 4Gbps supports 150m or less cable.
z 2Gbps supports 300m or less cable.
Using the 3.1 fc_info command allows you to obtain the current link speed and the list of link speed
that the fibre channel card supports. The link speed property is only valid when you use the fibre
channel card (PW008FC3/ PW008FC2/ SE0X7F11X/ SE0X7F12X). The fibre channel card
(PW008FC3/PW008FC2) supports the speed of 1Gbps and 2Gbps. The fibre channel card
(SE0X7F11X/SE0X7F12X) supports the speed of 1Gbps, 2Gbps, and 4Gbps. The fibre channel card
(GP7B8FC1) is support the speed of 1Gbps.
You can define "sp2" parameter to GP7B8FC1, but the parameter will be ignored because it supports
1Gbps link speed only.
- fcp-bind-target(required)
bind the target ID and WWN.
·SYNOPSIS:
fcp-bind-target = "instance name + target ID:WWN", ... ;
or
fcp-bind-target = "instance name + target ID:alias name", ... ;
instance name + target ID:
Define the instance name and target ID consecutively. Target ID is defined by decimal number adding
"t", corresponding to the target property of /kernel/drv/sd.conf as seen in the following example.
WWN or alias name:
Specify WWN of the controller in the target device. This device is connected with the adapter shown
by the instance name. When "alias" is defined, you can use the alias name alternatively.
Blank lines and comment lines beginning with a hash character (#) are ignored.
Go to the next step "Other configurations."

2.2.4 Other configurations


1. Setting the number of maximum SCSI command (tag) issues
By some target devices to be connected, the number of SCSI commands (tag) that can be accepted at the same time is
certainly limited. In this adapter (GP7B8FC1U/GP7B8FC1X or PW008FC2U/PW008FC2X/PW008FC3U/PW008FC2X),
255 SCSI commands or less can be issued to the target device at the same time. With the target device that can be
accepted less than 255 SCSI commands, the adapter negotiates the device to set the possible number of the commands
and not to issue the commands more than that number. But some devices may inform the number of the SCSI commands
beyond the actual capability. In this case, the maximum number of the SCSI commands issued at the same time can be set
in the environment definition file for all or each controller of the target device.
Consult the specification of the devices for this setting before configuring the file.
To set the configuration:
2. Editing the fjfpfca.conf file
The /kernel/drv/fjpfca.conf file is edited. The template of this definition file is installed with the driver installation.
max-throttle =
"fjpfca0t0:128",
"fjpfca1t1:240";
max-throttle-all =40;
In this example, the following limitations are applied.
The number of the SCSI command (tag) is limited to 128 commands for the controller of target ID=0 connected with the

12
adapter of instance name = fjpfca0.
The number of the SCSI command (tag) is limited to 240 commands for the controller of target ID=0 connected with the
adapter of instance name = fjpfca1.
The number of the SCSI command (tag) is limited to 40 commands for all controllers of all targets. (but max-throttle is
priority)
3. PROPERTY DESCRIPTION
- max-throttle
Define the connecting topology type for each instance (adapter). No definition is required when the target devices
use the unrestricted configuration.

- SYNOPSIS:
max-throttle="instance name + target ID:number of the SCSI command (tag)", ... ;
instance name + target ID:
Define the instance name and the target ID consecutively. Target ID is defined by decimal number adding "t",
corresponding to the target property of /kernel/drv/sd.conf as seen in the following example.
Number of the SCSI command (tag):
Specify the maximum number of SCSI command from 1 to 255 by the decimal number. When the value is
specified outside the range, it is disregarded. In this case, the adapter negotiates the target device to set the value
of 255 (default), and then a least number is applied if the target device has an upper limit.
- max-throttle-all
Define the connecting topology type for all instances (adapters). No definition is required when the target devices
use the unrestricted configuration. But max-throttle is priority.
- SYNOPSIS:
max-throttle-all=number of the SCSI command (tag);
Number of the SCSI command (tag):
Specify the maximum number of SCSI command from 0 to 255 by the decimal number. When the value is
specified outside the range, it is disregarded.
Initial value of max-throttle-all is set to 30. If max-throttle-all property is not necessary, delete it.
- NOTE:
Do not set the total value of SCSI command (tag) of all adapters beyond an upper limit when one target device is
connected with two or more adapters.
- Blank lines and comment lines beginning with a hash character (#) are ignored.

4. Auto target bind function


It is necessary to bind WWN of the target device to target ID in fabric topology. There are following method of
target bindings.
- Method of setting to fcp-bind-target. (persistent binding)
- Method of recognizing target device that boot code of fibre channel card detects automatically in SAN Boot
(fcode-auto-bind).
- Method of making fjpfca driver recognize all target device connected with fabric automatically (fcp-auto-bind).

The priority of the bind function is as follows.

(high priority) fcp-bind-target property > fcode-auto-bind > fcp-auto-bind ..( low..priority)

fcode-auto-bind is the function that fjpfca driver obtains the target information which the fibre channel boot code
automatically recognized at boot execution time. Please refer to "SAN Boot environment construction guide" for
details of SAN Boot.
fcp-auto-bind is a function that detects all the target devices connected with the fabric. And fjpfca driver allocates
target _ ID in ascending order of WWN of the target device. When the fcp-auto-bind-function property of the
environment definition file is set to "1", the fcp-auto-bind function is effective.

Notes
A) The target device are recognized by the fjpfca driver in the fcp-auto-bind function cannot be execute
chgfcctl/clchgfc command.
B) The auto target bind function should be use temporary (i.e. Installing Operating System to external
storage device). The fjpfca driver doesn't register automatically detected target’s information in driver
definition file(/kernel/drv/fjpfca.conf). Therefore, target_ID might be change at every boot time
because of failure and fjpfca driver can’t access the target device. You should use persistent target
binding setting(fcp-bind-target property) usually instead of fcp-auto-bind.

Go to the next step "Verifying the environment definition file."

2.2.5 Verifying the environment definition file


Verify that the environment definition file is correctly set using with the 3.6 chk_conf command (file checker for the fjpfca.conf
file).

13
The following message is shown when the file is valid:
# /usr/sbin/FJSVpfca/chk_conf
/kernel/drv/fjpfca.conf seems to be correct.
The messages other than this example are output, the description error in the fjpfca.conf may be the case. Please review a state of
each device, a physical connection, and the description of the fjpfca.conf file. This command can be executed repetitively to check
the fjpfca.conf file.
Environment setting of the Fibre Channel driver is now completed.
~
Go to the next step "2.4 SCSI Target Driver Configuration"

2.3 Configuring Input-Output Devices


This section describes the required configuration for input-output devices.
In Fabric connection, it is not necessary to set AL_PA or SCSI target ID on the input-output device side. Go to the next step "2.4
SCSI Target Driver Configuration".

2.3.1 Configuring the devices


As described in the previous section, the fjpfca driver searches for a device with an AL_PA (equal to the low-order 8 bits of the
port ID) corresponding to a SCSI target ID during the process of device recognition. To enable a device to be correctly recognized,
therefore, the device must be configured to have a correct AL_PA corresponding to a SCSI target ID.
There are two types of devices:
· Devices configured with SCSI target IDs (the values in the top row of Table 2-1) ( ex. GR700 series devices (F6403xx),
F649x disk array device, GR720(GR72Axx, GR72Bxx), etc. )
· Devices configured with AL_PAs (or port IDs) ( ex. GP-DxxF2x, GP-DxCKFx, GP-DxRxFx, PW-D500x1, PW-D5L1A1
devices, etc. )
Carefully note the following:
· There must be no duplicate AL_PAs or SCSI target IDs in one Fibre Channel loop.
· To connect devices configured with AL_PAs and devices configured with SCSI target IDs to the same loop, be sure to
convert the configuration of all devices to AL_PAs or SCSI target IDs to make sure there is no duplication of
configuration between these devices.
For instructions on configuring devices, refer to the manual for each device.

2.4 SCSI Target Driver Configuration


This section describes the tasks required to enable the SCSI target driver to identify disk array devices. In the explanation here,
these tasks are discussed based on the assumption that the sd driver (SCSI disk driver) is used. If you are using the related hard
disk driver, please refer to the manual of related hard disk driver.
Please refer to the manual of each device for the definition of the control driver of other I/O devices such as tape drive.

2.4.1 Collecting information about the devices to be connected


First, collect the following information about the devices that will be connected:
· SCSI target ID for each device
In Fabric connection, the SCSI target ID is not associated with AL_PA, set AL_PA for devices are not required. The SCSI
target ID is defined in the environment setting file (fjpfca.conf). Refer to "2.2 Configuring the driver software" for
detailed instructions. For devices configured with AL_PAs (or port IDs), convert their AL_PAs to SCSI target IDs. It is
recommended to use 3.3 alpa command for the above conversion.
· Logical unit (LU: Logical Unit) number included with each device

2.4.2 Editing the sd.conf


The definition file for the sd driver is /kernel/drv/sd.conf. Add the collected information to this file. sd.conf contains several
default settings.
#
# Copyright (c) 1992, by Sun Microsystems, Inc.
#
#ident "@(#)sd.conf 1.8 93/05/03 SMI"

14
name="sd" class="scsi"
target=0 lun=0;
name="sd" class="scsi"
target=1 lun=0;
.
.
A definition begins with name="sd" and ends with a semicolon (;). target=X specifies a SCSI target ID. lun=X specifies a
logical unit number. A line starting with a number sign (#) is a comment line.
For example, if a disk array device is configured with SCSI target ID 0 and has three logical units from 0 to 2, edit sd.conf as
follows:
· Use target=0 lun=0 as is, since it is an applicable definition.
· Copy the two lines containing target=0 lun=0 twice. In the copied lines, change one lun=0 to lun=1 and the other to
lun=2.
#
# Copyright (c) 1992, by Sun Microsystems, Inc.
#
#ident "@(#)sd.conf 1.8 93/05/03 SMI"
name="sd" class="scsi"
target=0 lun=0;
name="sd" class="scsi"
target=0 lun=1;
name="sd" class="scsi"
target=0 lun=2;
name="sd" class="scsi"
target=1 lun=0;
..
The sd driver now has all the necessary definitions.

2.4.3 Reconfiguring the kernel


For the changes in sd.conf to take effect in the kernel, reboot the machine as follows:
# touch /reconfigure
# cd /
# /usr/sbin/shutdown -i6 -g0 -y
The sd driver can now recognize the Fibre Channel devices. Use the prtconf command to check the recognition results.
Next, write a disk label or define a partition with the formatting command as explained in the manual for each device.
NOTE
When you use GR700 as a target device, and if you define more LUs than 32 per a target in sd.conf file, and when you perform a
reconfiguration reboot, you might see a following message in /var/adm/messages file.
WARNING: /pci@XX,XXXX/fibre-channel@1 (fjpfcaX):
FC SCSI command invalid. file: fcp_main.c version: $Revision: XX.XX.XX $ line: XXXX

15
16
Chapter 3 Utility Commands
Fibre Channel provides the following utility commands:
· fc_info
· chgfcctl
· alpa
· fc_adm
· ns_show
· chk_conf
· clchgfc
· fc_config
· fc_checkc
· fc_hbaprp
This chapter describes these commands.

3.1 fc_info
NAME
fc_info - Provides information about Fibre Channel devices.
SYNOPSIS
/usr/sbin/FJSVpfca/fc_info -a | -p [adpname]
/usr/sbin/FJSVpfca/fc_info -c
/usr/sbin/FJSVpfca/fc_info -i adpname
DESCRIPTION
The fc_info command displays information about devices in the Fibre Channel environment.
OPTIONS
The options for this command are as follows:
· -a
Indicates World Wide Names of your node's adapters and the link status in the connected loop. If an adapter is directly
connected to a device, the link status between the adapter and the device is indicated. If an adapter is connected to a hub,
the link status between the adapter and the hub or fabric is provided. If an adapter is specified, only information about the
specified adapter is reported. When adpname is specified for an operand, only a piace of information on the specified
adapter is displayed.
link_status (linking status) shows the following states.
fail
Optical fibre cable is not connected.
offline
Link is offline state (different from the offline device)
initializing
Initialization is in progress.
up
Communication is enabled.
In this case, the port ID of your port will be displayed as a suffix.
own_port (port status of the adapter) displays the following states.
N
N_port (node port)
NL
NL_port (the node port where loop connection can be enabled)
other_port (link status of the destination port) displays the following states.
N
N_port (node port)
NL
NL_port(the node port where loop connection can be enabled)
F
F_port (fabric port)
FL
FL_port (the fabric port where loop connection can be enabled)
e_d_tov, r_a_tov, bb_credit, and frame_size (connection parameters of the Fibre Channel) display the following values
respectively.

17
e_d_tov
The value of E_D_TOV is displayed by unit ms.
r_a_tov
The value of R_A_TOV is displayed by unit ms.
bb_credit
The value of BB_Credit is displayed by hexadecimal.
frame_size
The size of the frame_size frame is displayed with byte. The size of the frame of GP7B8FC1U is 1024 bytes or less. The
size of the frame of PW008FC3U/PW008FC2U is 2048 bytes or less.
· -p
This option displays the port information on the device recognized by the driver. The port information displays the list of
Port ID, target ID, World Wide Name, connected adapter, connected state, and transmission service class. The Port ID
shows "-1" (invalidity) during disconnection. Specify the adapter to display the recognition device list of the specified
adapter. Besides, the recognition device list of all adapters is displayed when you do not specify the adapter. The output is
displayed in ascending order of the adapter instance number, and ascending order of World Wide Name of the connected
device.
The following states are indicated.
not_connected
No connection (connection disabled)
address_resolved
The address resolution was settled (connection disabled)
connected
Connection completion (connection opened)
The class (transmission service class) shows the following states.
class3
Class 3. GP7B8FC1U is fixed in class 3. Currently, PW008FC2U and PW008FC3U support only class 3.
class2
Class 2. In GP7B8FC1U, this state is not displayed because of class 2 unsupported. Currently, PW008FC2U and
PW008FC3U do not support class 2.
· -c
This option displays the Fibre Channel device definition on the system. The definition displays the list of the device name,
connected adapter name, target ID, logical unit number, and World Wide Name (device information). The device
information is displayed only when the driver is in "attach" state (if physical definition of the device is not done, this
information is not displayed).
· -i adpname
This option displays the PCI Configuration of the adapter, availability of the adapter, and availability of the adapter in
which the fjpfca.conf file with the predefined information is set.
<PCI infomation> (information on PCI Configuration) displays the following items.
- vender_id
Vender ID of the card. In PW008FC3/PW008FC2, this show the vendor ID of Fibre Channel controller chip, not
the vendor ID of the card.
- device_id
Device ID of the card. In PW008FC3/PW008FC2, this show the device ID of Fibre Channel controller chip, not
the device ID of the card.
- sub_vender
Subsystem vender ID of the card.
- sub_device
Subsystem device ID of the card.
- clock_freq
Current clock frequency of PCI
- bus_width
Current width of bus of PCI or the number of PCI Express Bus lane.
- rev_id
Revision number of the Fibre Channel controller chips
<NATIVE capability> availability of the adapter's Fibre Channel <native capability> and <USER defined
capability> availability of the adapter in which the range where the Fibre Channel <user defined capability> of
the adapter was predefined in the fjpfca.conf file display the following items.
- support_class
Transfer service class
- port
Available port type from the adapter
- connectivity
Available port type of the destination device
- link_speed
Transfer speed of the Fibre Channel
- max_frame_size
Maximum size of frame

18
- max_credit
Maximum size of "Credit"
OPERAND
The following operands can be specified for -p, -a (option switch "-i" is required).
adpname
Adapter driver name + Adapter instance number
(example: fjpfca0)
EXAMPLES
# fc_info -a
adapter=fjpfca#0 wwn=100000000e24804a link_status=up port_id=0x11401
own_port=N other_port=F e_d_tov=2000ms r_a_tov=10000ms
bb_credit=0x3 bb_frame_size=1024byte
adapter=fjpfca#1 wwn=100000000e2483a8 link_status=up port_id=0x1
own_port=NL other_port=NL e_d_tov=2000ms r_a_tov=2000ms

# fc_info -p
adapter=fjpfca#0 :
port_id=0x0000e8 tid=1 wwn=100000a0b80730e5 adapter=fjpfca#0 connected
class=class3
port_id=0x0000ef tid=0 wwn=50000e100000373c adapter=fjpfca#0 connected
class=class3
adapter=fjpfca#1 :
port_id=0x0000e4 tid=2 wwn=100000a0b807105f adapter=fjpfca#1 connected
class=class3
port_id=0x0000e2 tid=3 wwn=50000e1000002663 adapter=fjpfca#1 connected
class=class3

# fc_info -c
sd#32 adapter=fjpfca#0 tid=0x0 lun=0x7 wwn=50000e100000373c
"VENDOR-PRODUCT-REV"
sd#33 adapter=fjpfca#0 tid=0x1 lun=0x0 wwn=100000a0b80730e5
"VENDOR-PRODUCT-REV"

# fc_info -i fjpfca0
fjpfca#0
<PCI information>
vender_id=0x103c device_id=0x1028 sub_vender=0x10cf sub_device=0x105c
clock_freq=33MHz bus_width=32bit
rev_id=2.3
<NATIVE capability>
support_class=class3
port=N,NL connectivity=N,NL,F,FL
link_speed=1062.5Mbps
max_framesize=1024byte

19
max_credit=0x3
<USER defined capability>
support_class=class3
port=N connectivity=N,F
link_speed=1062.5Mbps
max_framesize=1024byte
max_credit=0x3

In the case of using fcp-auto-bind-function.


# fc_info –p
adapter=fjpfca#2 :
port_id=0x010400 tid=0 wwn=210000e000a8199e adapter=fjpfca#2 connected
class=class3 (auto-bind)

port_id=-1 tid=-1 wwn=21fd00051e35f334 adapter=fjpfca#2 not_connected


class=class3

In the case of using fibre channel card (SE0X7F11X/SE0X7F12X).


# fc_info –i
fjpfca#2
<pci information>
vender_id=0x15bc device_id=0x1203 sub_vender=0x10cf sub_device=0x13b6
clock_freq=2.5GHz bus_width=4-lane
rev_id=1.2
<native capability>
support_class=class3
port=N,NL connectivity=N,NL,F,FL
link_speed=4250Mbps
max_framesize=2048byte
max_credit=0x4
<user defined capability>
support_class=class3
port=N,NL connectivity=N,NL,F,FL
link_speed=4250Mbps
max_framesize=2048byte
max_credit=0x4

NOTE
1. In Fabric connections, following port_id=-1 (invalid device to unconnect) is displayed. The reason for this is to be
detected for a virtual device which processes the nameserver function etc. to Fabric. There is no problem.
# /usr/sbin/FJSVpfca/fc_info -p
adapter=fjpfca#1 :
port_id=-1 tid=-1 wwn=200000606910107f adapter=fjpfca#0 not connected
port_id=-1 tid=-1 wwn=20fd00606910107f adapter=fjpfca#0 not connected
2. In Fabric connections, after the system recognized target devices, if link down (between Fabric and the target device)
occurs, device connection status is not displayed correctly. In this case, newly issued I/O will make a transition into
"connected" status.
EXIT STATUS
The exit status is returned as follows:

20
0: Normal termination
Integer of 1 or more: Abnormal termination
REMARKS
About the connection state (not_connected/address_resolved/connected) of –p option
The connection state displayed will be in the following states.
Connection state State
not_connected In Arbitrated Loop topology :
Fibre Channel adapter cannot connect target device.
- Fibre Channel cable error
In Fabric topology :
Fibre Channel adapter cannot connect target device.
- Fibre Channel cable error.
- Fabric zone configuration setting error.
- The definition of fcp-bind-target of fjpfca.conf has an error.
In Fabric topology, upper layer (sd/st) has not access target
device after recovering from link error.
address_resolved In Arbitrated Loop topology :
- The Fibre Channel adapter has connected with target device,
and SCSI target ID of connected target equipment is not
defined as the configuration file of a target driver
(sd.conf/st.conf).
- Device without target function.
In Fabric topology :
- Device without target function.
Host Afinity setup of target device is wrong.
connected The Fibre Channel adapter communitcate with a target device.
In fabric topology, Fibre Channel adapter may communicate
target device, even if a definition of SCSI target ID as not
defined in sd.conf/st.conf

3.2 chgfcctl
NAME
chgfcctl - Instructs hot device replacement of a Fibre Channel device.
SYNOPSIS
/usr/sbin/FJSVpfca/chgfcctl -d diskpath [-p new_wwn]
/usr/sbin/FJSVpfca/chgfcctl -i adapname -o old_wwn [-n new_wwn]
DESCRIPTION
The chgfcctl command informs the driver a target device specified in diskpath or in pair of adapname and old_wwn has changed.
Since Fibre Channel devices are recognized on the basis of their World Wide Names, if you change the pair of target ID and World
Wide Name of a target device that has already been identified by the driver after booting of the system, you must use this
command to inform the driver the pair of the target ID and World Wide Name of the target device is no more valid. Please refer
following table to check if you need to run this command.
Necessity of running chgfcctl command for each Disk Array
Disk Array Replacing Part Need to run?
GP-DxxF2x Disk Arrays FC Interface board MUST
GP-DxCKFx, GP-DxRxFx Disk Arrays FC Interface board MUST
PW-D500x1, GP-D5L1A1 Disk Arrays - No necessary
GR700 Series(F6403XX) RAID controller board MUST
F649x Disk Arrays - No necessary
GR720/GR730/GR740/GR820/GR840 Disk Arrays - No necessary
ETERNUS 2000/3000/4000/6000/8000 Disk Arrays - No necessary

21
ETERNUS LT130/LT160 tape drive module MUST
Any target device specified in diskpath or in pair of adapname and old_wwn must be under the control of FJSVpfca. If any
other target device is specified, this command will terminate abnormally.
Executing this command rewrites the environment definition file (/kernel/drv/fjpfca.conf) of the driver at the same time. However,
if you change the environment setting file after starting up the system, statement in the definition file may conflicts with the
information loaded to the driver. In this case, the command displays the message of the failure in changing and redefine the
environment setting file manually is required.
To specify the command is to follow those method depends on the state where the hot device replacement of target devices is
defined in the fcp-bind-target property of the environment setting file or not.
The hot device replacement of the target is not defined (FC-AL without the definition):
· -d diskpath or -i adapname -o old_wwn
"-p" option is not required.
The hot device replacement of the target is defined (Fabric connections, and FC-AL connections with the definition):
· -d diskpath -p new_wwn
or -i adapname -o old_wwn -n new_wwn
WWN of the target device to be connected is specified with -p option (required).Specify the hexadecimal (eight bytes) by
adding "0x" in the head.
In FUJITSU PCI Fibre Channel 2.1 or later, "3.7 clchgfc command" is recommended instead of the chgfcctl command. The
clchgfc command can recognize the type of clustering system/non-clustering system. In the clustering system, the clchgfc
command issued to one node can automatically be processed the same command for all nodes.
EXAMPLE
The hot device replacement of the target is not defined (FC-AL without the definition):
# chgfcctl -d /dev/rdsk/c1t0d0s2 (Disk array example)
# chgfcctl -d /dev/rmt/0 (Tape drive example)

# chgfcctl -i fjpfca0 -o 0x50000e100002501


The hot device replacement of the target is defined (Fabric connections, and FC-AL connections with the definition):
# chgfcctl -d /dev/rdsk/c1t0d0s2 -p 0x50000e1000002501 (Disk array example)
# chgfcctl -d /dev/rmt/0 -p 0x50000e1000002501 (Tape drive example)
# chgfcctl -i fjpfca0 -o 0x50000e1000002501 -n 0x50000e1000002502
EXECUTION PROCEDURE
There is RAID controller's hot system replacement by MPHD Viewer since Multipath Disk Control 1.2. However, MPHD viewer
of the Multipass Disk Control 1.x does not correspond to the fabric connection function (Accurately, the target device is specified
by fcp-bind-target property in /kernel/drv/fjpfca.conf.) of this product. But MPHD viewer of the Multipath Disk Control 2.0 or
later supports the fabric connection function.
Please do the hot system replacement of RAID controller manually according to "Restart procedure of the passing breakdown" of
the Multipapth Disk Control Guide.
In "Restart procedure of the passing breakdown" of the Multipath Disk Control, there is an item of "Free device's address".
This is an operation to delete or change information on WWN(World Wide Port name) of RAID controller of the object which the
driver of GP7B8FC1U, PW008FC2U and PW008FC3U memorizes of the exchange, and does by the chgfcctl command.
Please execute the chgfcctl command as follows. When RAID controller's WWN is not changed by the part exchange, the
execution of this command can be omitted.
When you exchange the device not described in fcp-bind-target property
· Execute timing
Please execute this command after exchanging parts, and without connecting the fibre channel cable on the replaced
RAID controller side. If you connect the fibre channel cable before you run this command, some warning messages(1, 2,
or 3) might be displayed on the console. In this case, please pull out exchanged RAID controller's fibre channel cable and
rerun this command. Then insert fibre channel cable again.
Please execute this command for the clustered system by all nodes.
· Form of command
/usr/sbin/FJSVpfca/chgfcctl -d exchanged_device_name
or
/usr/sbin/FJSVpfca/chgfcctl -i adapter_name -o exchanged_device's_WWN
When you exchange the device described in fcp-bind-target property

22
· Execute timing
Please examine WWN of new parts after exchanging parts, and execute this command before the postprocessing of the
exchange of the Multipath Disk Control (iompadm restart processing or chgctl -c processing).
Please execute this command for the clustered system by all nodes with the definition of the exchanged RAID device.
· Form of command
/usr/sbin/FJSVpfca/chgfcctl -d exchanged_device_name -p new_device's_WWN
or
/usr/sbin/FJSVpfca/chgfcctl -i adapter_name -o exchanged_device's_WWN -p new_device's_WWN
NOTE
When the controller of GR700 is hot-replaced, the following message is displayed by executing this command. This implies that
the controller of GR700 has been blockaded at this point, and that the controller does not have any problem.
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't find target's WWN in Name server. wwn=%08x%08x.
iompadm restart command of the multipass disk controller is issued to reboot the contoroller after the above message, then the
following message is displayed when target device is recognized.
fjpfca%d: found target. target_id=0x%x port_id=0x%x wwn=%08x%08x
EXIT STATUS
The exit status is returned as follows:
0: Normal termination
1: Abnormal termination (parameter error)
2: Abnormal termination (resource error)
3: Abnormal termination (system call error)

3.3 alpa
NAME
alpa - Performs both-way conversion between target IDs and AL_PAs (port IDs)
SYNOPSIS
/usr/sbin/FJSVpfca/alpa [-t tid | -a alpa]
DESCRIPTION
alpa command is a tool that allows both-way conversion between target IDs required for defining devices in the SCSI target
driver and AL_PAs (Arbitrated Loop Physical Addresses), which are physical addresses in the Fibre Channel arbitrated loop.
If no options are specified, this command will display the conversion table of target IDs and AL_PAs.
· -t tid
Converts the target ID specified by tid to the corresponding AL_PA. To specify a target ID in tid, use octal, decimal, or
hexadecimal notation. If you use octal notation, prefix the target ID with 0. If you use hexadecimal notation, prefix the ID
with 0x or 0X. The corresponding AL_PA is given in hexadecimal. The range of values that can be specified in tid is
decimal 0 to 125.
· -a alpa
Converts the AL_PA specified by alpa to the corresponding target ID. To specify an AL_PA in alpa, use octal, decimal, or
hexadecimal notation. If you use octal notation, prefix the AL_PA with 0. If you use hexadecimal notation, prefix the
AL_PA with 0x or 0X. The corresponding target ID is given in decimal. The range of values that can be specified in alpa
is 0x1 to 0xEF in hexadecimal (note, however, that even a value in this range could cause an error, since AL_PAs are not
consecutive).
EXIT STATUS
0: Normal termination
1: Abnormal termination

3.4 fc_adm
NAME
fc_adm - Dislplays the control and state information of the adapter hardware.
SYNOPSIS

23
/usr/sbin/FJSVpfca/fc_adm { -l | -r | -x } adpname
/usr/sbin/FJSVpfca/fc_adm -z adpname level
DESCRIPTION
The fc_adm command displays the command issuance in which the adapter control directly and the internal state of the hardware
and the driver.
OPTIONS
The options for this command are as follows.
Specify adpname (instance name) to determine the adapter for the use of an operand in each option. The instance name is
specified by the adapter driver name + the adapter instance number (fjpfca0 for example). The instance name of all the mounted
adapters can be obtained by the 3.1 fc_info command with -a option (operand is not required).
· -l adpname
Two LED of LINK and CHK of the adapter specified with adpname is blinked at the same time (refer to "1.2.1.2 Physical
description(Figure 1-3)", "1.2.2.2 Physical description(Figure 1-4)" for a physical position of these LED). It is possible to
associate the instance name of the adapter with a physical position when environment setting of the Fabric connection is
set.
Blinking LED can be interrupted with Ctrl-c (c key is pushed while pushing the Ctrl key). Blinking is stopped (returning
in former state) in three minutes automatically when the Ctrl-c is not pressed, then the command terminates.
· -r adpname
Software reset is issued forcibly to the hardware of the adapter specified with adpname.
The root authority is necessary for executing this command. When you do not execute this command as root, the
command terminates abnormally.
· -x adpname
Internal register information on the adapter hardware is displayed. This optiondoes not influence the operation of the
adapter.
· -z adpname level
Driver's internal control information is displayed. The second operand (level) is specified to display the content. This
option does not influence the operation of the adapter.

level(In case of the decimal)


1:Displays the part of control information
2:Displays the control information
4:Displays the cue information
8:Displays the resource information
16:Displays the register trace information
32:Displays the cue trace information
64:Displays the kernel memory trace information (displays the blank because of no trace information is collected.)
128:Displays the port administrative information and the port information

EXAMPLES
# fc_adm -l fjpfca0
(displays the blank. LED of the specified adapter blinks. )
# (Return to the prompt in three minutes or when Ctrl-c is pressed.)

# fc_adm -r fjpfca0
WARNING: /pci@1f,2000/fibre-channel@1 (fjpfca0):
controller chip reseted(user operation)
(Messages such as "Link down" or "Link up" are displayed
while the target device is being connected.)
#

EXIT STATUS
The following termination status is returned.
0: Normal termination
Integer of 1 or more: Abnormal termination

24
3.5 ns_show
NAME
ns_show - Displays the information registered in name server.
SYNOPSIS
/usr/sbin/FJSVpfca/ns_show -n adpname
/usr/sbin/FJSVpfca/ns_show -c adpname
/usr/sbin/FJSVpfca/ns_show -l adpname domain_area_id
/usr/sbin/FJSVpfca/ns_show -t adpname -a alias
/usr/sbin/FJSVpfca/ns_show -t adpname -p port_name
/usr/sbin/FJSVpfca/ns_show -t adpname -i port_id
DESCRIPTION
The ns_show command can be used while the adapter is being connected with the Fibre Channel switch. This command displays
the information registered in the name server in the Fibre Channel switch.
OPTION
The options for this command are as follows.
Specify the adpname (instance name) to determine the adapter for the use of an operand in each option. The instance name is
specified by the adapter driver name + the adapter instance number (fjpfca0 for example). The instance name of all the mounted
adapters can be obtained by the 3.1 fc_info command with -a option (operand is not required).
· -n adpname
This option lists the port ID, the node name, the port name, and the alias name for all the target devices whose FC-4 type
is FCP(Fibrer Channel Protocol for SCSI) and that is registered in the name server which can be referred from the adapter
specified with adpname. The alias name is displayed only when the target is defined in /kernel/drv/fjpfca.conf as an alias
name.
FC-4 type shows kinds of protocol that the device supports, and the device whose FC-4 type is FCP is a SCSI device.
Normally, a SCSI device connected to Fabric registers its FC-4 type to name server by itself. But there are some devices
that doesn't register its FC-4 type to name server by itself. In such case, you can't see such devices by this option. If you
want to show such devices, you should use "ns_show -c adpname" instead.
· -c adpname
This option lists the port ID, the node name, the port name, the alias name and FC-4 types the device supports for all the
target devices registered in the name server which can be referred from the adapter specified with adpname. The alias
name is displayed only when the target is defined in /kernel/drv/fjpfca.conf as an alias name.
· -l adpname domain_area_id
The loop status of the domain_area_id connected with the adapter of the adpname is displayed. The domain_area_id is
an identification number of three bytes which consists of domain number + area number + port number. When the adapter
specified with adpname is connected to Fabric with N_port, a protocol error will be reported. It specifies domain_area_id
by the hexadecimal number (It adds "0x").
· -t adpname -a alias
-t adpname -p port_name
-t adpname -i port_id
This option displays the information of the target device registered in the name server which can be referred from the
adapter specified with adpname when either of alias, port_name or port_id is indicated as a registered name. It specifies
port_name and port_id by the hexadecimal number (It adds "0x").
EXAMPLES
# ns_show -n fjpfca0
fjpfca#0 :
port_id=011200 node_name=50000e1000002500 port_name=50000e1000002500 alias=STRAGE_A
port_id=011800 node_name=50000e1000002501 port_name=50000e1000002501
port_id=011c01 node_name=100000000e24ffec port_name=100000000e24ffec

# ns_show -c fjpfca0
fjpfca#0 :
port_id=011200 node_name=50000e1000002500 port_name=50000e1000002500

25
fc4_types=FCP(8)
port_id=011800 node_name=50000e1000002501 port_name=50000e1000002501
fc4_types=FCP(8)
port_id=011c01 node_name=100000000e24ffec port_name=100000000e24ffec
fc4_types=FCP(8)

# ns_show -l fjpfca0 0x021f01


fjpfca#0
failed_receiver : 00
compliance_level : 2 (FC-FLA B)
loop_state : 1 (online)
public_loop_devices : 01, 02
private_loop_devices : none
alpa_map : 00, 00

# ns_show -t fjpfca0 -a STRAGE_A


port_type : 0x02 (NL_Port)
port_id : 0218dc
port name : 50000e1000002500
sym_port_name_len : 28
sym_port_name : 'HITACHI DF400F 0000'
node name : 50000e1000002500
sym_node_name_len : 0
sym_node_name : none
init_proc_associator : ffffffffffffffff
ip_address(node) : none
class of service : Class 1, Class 2, Class 3
fc_4 types : SCSI-FCP(8)
ip_address(port) : none
fabric_port_name : 0000000000000000
hard_address : 000000
EXIT STATUS
The exit status is returned as follows:
0: Normal termination
Integer of 1 or more: Abnormal termination

3.6 chk_conf
NAME
chk_conf - File checker program for the fjpfca.conf file.
SYNOPSIS
/usr/sbin/FJSVpfca/chk_conf [-v] [-c conf_file]
DESCRIPTION
This command checks the content of the fjpfca.conf file. In default, /kernel/drv/fjpfca.conf file is checked. When the file is

26
specified with "-c" option, the specified file is checked. The following items can be checked by the chk_conf command.
1. General syntax verification of the fjpfca.conf file.
2. Detailed syntax verification of the following properties:
- alias
- port
- fcp-bind-target
- max-throttle
3. Related status in the fcp-bind-target and alias
4. Actual existence of the target device specified in fcp-bind-target
However, the properties except above-mentioned are not verified. For instance, verification of the misspelling and its property are
not executed. In this case, execute chk_conf -v after confirming the content with chk_conf to verify the loaded setting.
OPTIONS
· -c conf_file
Specify the conf file to be checked. When no file name is specified with this option, the /kernel/drv/fjpfca.conf file is
checked.
· -v
Verify the content of the fjpfca.conf file and display the setting information read from the fjpfca.conf file or the file
specified with the -c option. Misspelled property may not be checked by the chk_conf command, but using this option
allows you to confirm the setting recognized by the driver. The following contents are displayed.
*port definition*
instance
The instance name is displayed.
port
The port type and link speed are displayed.
status
Existence of the adaptor (instance) is displayed.
*target definition*
instance
Instance name
t-id
target ID
wwn
port name (World Wide Name) is displayed. (UNDEF indicates an undefined value)
When fcp-bind-target is undefined, "no binding" is indicated.
throt
The max-throttle value is displayed. (UNDEF indicates an undefined value)
alias
The alias name is displayed (UNDEF indicates an undefined value)
status
The detection status of the target device is displayed.
found: indicates the target device was detected.
none: indicates the target device cannot be detected.
EXAMPLES
# /usr/sbin/FJSVpfca/chk_conf -v
/kernel/drv/fjpfca.conf seems to be correct.
******************************
*port definition*
instance port status
------------------------------
fjpfca0 none loop
fjpfca2 foundnport,2Gbps
*target definition*
instance t-id wwn status throt alias
------------------------------------------------------------------------------
fjpfca0 0 0x50060e8000013121 detect UNDEF DF500_RK
fjpfca0 1 no binding none 240 UNDEF
NOTES

27
Notes on Fabric Connection
The type of target device which indicate the SCSI device is FCP (Fibre Channel Protocol for SCSI) might not be registered in the
name service of the Fabric occasionally. This phenomenon might not affect on the normal operation, but affects on the chk_conf
operation.
The driver cannot find the target device which does not register the type of FCP while the chk_conf checks existence of the target
device specified in fcp-bind-target because the driver recognizes only the device of the FCP type. The following message is
displayed even if the fjpfca.conf file is set correctly.
target '%s'(wwn=%s) seems to be absent on fjpfca#%d
or
target '%s' on fjpfca#%d seems to be unsupport SCSI-FCP(8) fc4_types
If you need to connect such a device, set the Device Probing function of SN200 (Fibre Channel switch) in "Enabled." The SN200
collects the information on the target device which does not register the type of FCP, and the device is registered in the SN200
name service.
When the error is displayed even if you set the fcp-bind-target correctly, and mistakes in the zone setting of Fabric and the
connection are not found, verify the Device Probing setting of SN200.
EXIT STATUS
The following termination status is returned.
0: Normal termination (no error)
1: Abnormal termination (with syntax error)
2: Abnormal termination (with semantic error)
3: Abnormal termination (with errors such as the system call error, etc.)

3.7 clchgfc
NAME
clchgfc - hot system replacement request on Fibre Channel device of the clustering system(FUJITSU Synfinity Cluster).
SYNOPSIS
/usr/sbin/FJSVpfca/clchgfc -c diskpath [-f log_file]
/usr/sbin/FJSVpfca/clchgfc -d diskpath [-p new_wwn] [-f log_file]
/usr/sbin/FJSVpfca/clchgfc -C old_wwn [-f log_file]
/usr/sbin/FJSVpfca/clchgfc -D old_wwn [-p new_wwn] [-f log_file]
DESCRIPTION
This command can be used to request the hot system replacement of Fibre Channel device of the clustering system. The command
offers the following two capabilities:
Verification function of existence of WWN definition (-c, -C option)
This option examines whether the target device specifying with the diskpath or with the old_wwn is defined in the
fcp-bind-target property of the environment setting file (/kernel/drv/fjpfca.conf). Verify the existence of the definition beforehand
because different command option is used on the basis of the presence of the WWN definition to perform the hot system
replacement.
old_wwn is specified by 8 bytes (16 figures) of hexadecimal number which attached "0x" to the head.
Scope of the search target is as follows.
· In non-clustering system:
- c/-C Both option : All the Fibre Channel cards (instances) existing in the node where the command was executed are
targeted.
· In clustering system:
-c option : All the Fibre Channel cards (instances) existing in the node of the clustering system are targeted. This
command must be executed on the one node selected.
-C option : All the Fibre Channel cards (instances) existing in the node where the command was executed are targeted.
NOTE) When you execute a command to library equipment without the standard special file of Solaris, please use -C
option and execute a command by All the nodes which need to execute a command.
hot system replacement function (-d, -D option)

28
This option notifies a replacement of the target device specified with the diskpath or with the old_wwn to the driver. The Fibre
Channel device is recognized based on World Wide Name (WWN) of the device. Therefore, when the device is replaced to change
WWN, change the target ID and WWN of the device recognized by the driver after starting the system. This means if device is
replaced but the WWN does not change (former WWN is succeeded), the hot system replacement need not be performed. Please
refer following table to check if you need to run this command.
old_wwn is specified by 8 bytes (16 figures) of hexadecimal number which attached "0x" to the head.
Necessity of running chgfcctl command for each Disk Array
Disk Array Replacing Part Need to run?
GP-DxxF2x Disk Arrays FC Interface board MUST
GP-DxCKFx, GP-DxRxFx Disk Arrays FC Interface board MUST
PW-D500x1, PW-D5L1A1 Disk Arrays - No necessary
GR700 Series(F6403XX) RAID controller board MUST
F649x Disk Arrays - No necessary
GR720/GR730/GR740/GR820/GR840 Disk Arrays - No necessary
ETERNUS 2000/3000/4000/6000/8000 Disk Arrays - No necessary
ETERNUS LT130/LT160 tape drive module MUST
The command with the -d option is executed to change the environment setting file (/kernel/drv/fjpfca.conf) of the driver at the
same time. However, if you change the environment setting file manually after starting up the system, statement in the definition
file may conflicts with the information loaded to the driver. In this case, the command displays the message of the failure in
changing, and redefine the environment setting file manually.
Scope of the target device to be replaced is as follows.
· In non-clustering system
-d/-D Both option : All the Fibre Channel cards (instances) which recognize the target device specifying with the
diskpath that exists in the node where the command was executed. Environment setting is
changed only to the node where the command was executed.
· In clustering system
-d option : All the Fibre Channel cards (instances) which recognize the target device specifying with the diskpath that
exists in the node of the clustering system. Environment setting is changed to all the node of the clustering
system. This command must be executed on the one node selected.

-D option : All the Fibre Channel cards (instances) which recognize the target device specifying with the diskpath that
exists in the node where the command was executed. Environment setting is changed only to the node
where the command was executed.
NOTE) When you execute a command to library equipment without the standard special file of Solaris, please use -D
option and execute a command by All the nodes which need to execute a command.
OPTIONS
· -c diskpath
· -C old_wwn
-c The scope of option serves as all the nodes of a cluster system.
-C The scope of option serves as a node which executed the command.
The target device specified with the diskpath should be the one controlled from FJSVpfca. This command terminates
abnormally when other target devices are specified. When the target device is defined in fcp-bind-target property of the
nodes within a scope , this option displays the defined WWN. Nothing is displayed when the property is not defined in
the nodes within a scope.
· -d diskpath [-p new_wwn]
· -D old_wwn [-p new_wwn]
-d option exchanges the target device recognized with all the Fibre Channel cards (instance) specified by diskpath which
exists in all the nodes of a cluster system.
-D option exchanges the target device recognized with all the Fibre Channel cards (instance) specified by old_wwn which
exists in the node which executed the command.
The way to specify the -p option is used differently whether the target device of the hot system replacement is being
defined in the fcp-bind-target property or not. Check with -c option beforehand to verify the target device to be exchanged
is defined in the fcp-bind-target property. In any case, it should be the one that the target device specified with the
diskpath is controlled from FJSVpfca. This command terminates abnormally when other target devices are specified.
hot system replacement of the target device without fcp-bind-target definition (FC-AL connection)
- -d diskpath / -D old_wwn
Specification of -p option is not required. The -p option is ignored even if it is specified in a correct format.
hot system replacement of target device with fcp-bind-target definition (Fabric connection or the defined FC-AL

29
connection)
- -d diskpath -p new_wwn / -D old_wwn –p new_wwn
WWN of the target device to be connected is specified with -p option. WWN is specified in hexadecimal of eight
bytes with the 0x prefix. This command terminates abnormally when -p option is not specified. Moreover, even if
the fcp-bind-target of the target device to be replanced is not defined but if the fcp-bind-target definition in other
nodes of the clustering system exists, -p option is required.
· [-f log_file]
Destination of error log is specified. If you omitted -f option, error log output to /var/opt/FJSVpfca/clchgfc.log.
EXAMPLES
This section explains how to request the hot system replacement using with the clchgfc command under the following
configuration.

1. Verify the presence of WWN definition in node A and C.


node_a# clchgfc -c /dev/rdsk/c2t1d0s2
50000e1000002500 ~<- CNT1 of present WWN (WWN was defined)
node_c# clchgfc -c /dev/rdsk/c5t1d0s2
* Nothing is displayed because CNT1 of the WWN in node C is not defined.
The existence of the WWN definition in node B is verified with the result of the node A processing.
2. The hot system replacement is performed to the node A and C.
node_a# clchgfc -d /dev/rdsk/c2t1d0s2 -p 0x50000e1000003000
node_c# clchgfc -d /dev/rdsk/c5t1d0s2
The command executed on node B is not required. When the command is executed on node A, the node B is
automatically processed with this command to complete the request of hot system replacement on PFCA (c4). However,
the hot system replacement must be performed on the node C individually because the node C is a non-clustering system.
EXECUTION PROCEDURE
When the hot system replacement function of MPHD Viewer in Multipath Disk Controller is used, this command need not be
performed manually.
However, the Multipath Disk Controller 1.x (see note 3) is used or the MPHD Viewer is not used, process this command manually
according to "Path Breakdown Restoration Procedure" of the Multipath Disk Controller Guide.

30
If the Multipath Disk Controller 1.x is used, perform the hot system replacement with the following procedures.
Example of the device replacement which is not described in fcp-bind-target
· Processing of Command
Please execute this command after exchanging parts, and without connecting the fibre channel cable on the replaced
RAID controller side. If you connect the fibre channel cable before you run this command, some warning messages(1, 2,
or 3) might be displayed on the console. In this case, please pull out exchanged RAID controller's fibre channel cable and
rerun this command. Then insert fibre channel cable again.
In the non-clustering system, execute the command on the all node. In the clustering system, the command issued to one
node can automatically be processed for all nodes.
· Synopsis
/usr/sbin/FJSVpfca/clchgfc -d raw_device_name
Example of the device replacement which is described in fcp-bind-target
· Processing of Command
After replacing the part, obtain the WWN of the new part (device) to execute the command before post process (iompadm
restart command, or chgctl -c command) of the Multipath Disk Control. In the non-clustering system, execute the
command on the node that has definition of the target device to be replaced. In the clustering system, the command issued
to one node can automatically be processed for all nodes.
· Synopsis
/usr/sbin/FJSVpfca/clchgfc -d raw_device_name -p new_device's_WWN
NOTE
1. When the controller of GR700 is hot-replaced, the following message is displayed by executing this command. This
implies that the controller of GR700 has been blockaded at this point, and that the controller does not have any problem.
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't find target's WWN in Name server. wwn=%08x%08x.
iompadm restart command of the multipass disk controller is issued to reboot the contoroller after the above message,
then the following message is displayed when target device is recognized.
fjpfca%d: found target. target_id=0x%x port_id=0x%x wwn=%08x%08x
2. The command of the hot system replacement request includes the chgfcctl command besides clchgfc. The clchgfc
command is best recommended for the hot system replacement request so that you remember to perform the request
though you can use the chgfcctl command.
3. In the Multipath Disk Controller 1.2 or later, MPHD Viewer has the hot system replacement function of RAID controller.
However, the MPHD Viewer of Multipath Disk Controller 1.x does not support the fabric connection function of this
product (that is, the target device is specified in the fcp-bind-target of /kernel/drv/fjpfca.conf), or the hot system
replacement function of the clustering system. Perform the command manually according to "Path Breakdown
Restoration Procedure" of the Multipath Disk Controller Guide for the hot system replacement of Fibre Channel device.
However, MPHD viewer of Multipath Disk Controller 2.0 or later supports the fabric connection function and the hot
system replacement function of the clustering system.
EXIT STATUS
The exit status is returned as follows:
End status of clchgfc -c, -C
0: Normal termination: Specified diskpath has no WWN definition (fcp-bind-target is not defined)
1: Normal termination: Specified diskpath has a WWN definition (fcp-bind-target is defined)
2: Abnormal termination (with parameter error)
3: Abnormal termination (with resource acquisition failure)
4: Abnormal termination (with system call error)
5: Abnormal termination (with hot system replacement failure in a part of nodes or all nodes)
End status of clchgfc -d, -D
0: Normal termination (with the hot system replacement completed in all nodes)
1: None
2: Abnormal termination (with parameter error)
3: Abnormal termination (with resource acquisition failure)
4: Abnormal termination (with system call error)
5: Abnormal termination (with hot system replacement failure in a part of nodes or all nodes)
File
· /var/opt/FJSVpfca/clchgfc.log

31
This is an error log file. The error log of all nodes in the clustering system where the clchgfc command was executed is
stored. When the log file exceeds 10Kbyte in size, the log is saved in clchgfc.log.0 (overwritten to the clchgfc.log.0 if the
file exists).

Related Topic
3.2 3.2 chgfcctl command

3.8 fc_config
NAME
fc_config - Hot target device addition command
SYNOPSIS
/usr/sbin/FJSVpfca/fc_config [-n] [-v]
/usr/sbin/FJSVpfca/fc_config -p adp_name
DESCRIPTION
This command can be used to request the hot target defice addtion to the driver. The command compares driver setup
file(/kernel/drv/fjpfca.conf) and operating parameter of driver. If there are some difference between them, this command will
update the operating parameter(driver property) of driver. You can modify parameters partially. Which part you can modify
depends on which property(parameter) you are modifying.
· fcp-bind-target property
You can add a new target binding, but you can't modify existing target binding. If you want to modify existing target
binding, you have to reboot the system. You can also use alias property when you add a new target binding.
· max-throttle property
You can modify the max-throttle of existing target device. In another word, you can modify the throttle of the device
which is displayed by the "fc_info-p" command.
· port property
You can modify the topology field, but you can't modify link speed. If you changed the port property, you have to pull-off
the optical fibre cable from the fibre channel card, and have to connect it again.
OPTIONS
· none
It checks the syntax of /kernel/drv/fjpfca.conf, extracts the difference between the file and operationg parameter, and then
update the operating parameter of the driver.
· -v
It checks the syntax of /kernel/drv/fjpfca.conf, extracts the difference between the file and operationg parameter, shows
the difference, and then update the operating parameter of the driver.
· -n
It checks the syntax of /kernel/drv/fjpfca.conf, extracts the difference between the file and operationg parameter, but it
does not modify the operating parameter of the driver.
· -p
Update the operating parameter of the driver concerned with the port property which is specified adp_name.
EXAMPLES
# fc_config -v
check new target definition
---------------------------------------------
New target binding find(fjpfca2t3, wwn=0x50060e8000013129).
check new max throttle setting
---------------------------------------------
fjpfca2t0:max throttle change 255 -> 90
check new port definition
---------------------------------------------
fjpfca2:change loop mode
NOTE
Syntax error messages are same with the messages of "chk_conf" command. Please see the message description of "chk_conf"
command.

32
When a fcp-bind-target property and a max-throttle property are simultaneously set up to a new target at the time of a new target
addition and you performed "fc_config -n", an error might be occur, Because the max-throttle information of new target does not
exist in the management infomation of driver. you will execute "fc_config" or "fc_config -v" as such case, An error is not occur.
EXIT STATUS
0: Normal termination
Integer of 1 or more: Abnormal termination.

3.9 fc_checkc
NAME
fc_checkc - display and check fibre channel environment
SYNOPSIS
/usr/sbin/FJSVpfca/fc_checkc
DESCRIPTION
The fc_checkc command displays the information/state of device (*) recognized as a target in the Fibre Channel environment.
(*) It becomes a device seen by the fc_info -p command.

The displayed content is as follows.


(1) Information of HBA (Host Bus Adaptor).
adapter_index
It is a number that the fc_checkc command allocated from 0 to the HBA. It is not an instance number of HBA.
hba_port_index.
It is a number that the fc_checkc command allocated from 0 to port in HBA. It is not an instance number of HBA. It becomes
"1" at port 1 of 2 port adaptor (SE0X7F12X).
0xXXXXXX
It is port_id of the instance of the HBA.
WWPN
It is port WWN corresponding to the instance of the HBA.
WWNN
It is node WWN corresponding to the instance of the HBA.
com.fujitsu.jp-PFCA-X
The HBAAPI vender unique library.
Model
It is a model name of the HBA.
NodeSymbolicName
It is a name that identifies the HOST node. It is shown not to be defined for the blank.
PortSymbolicName
It is a name that identifies the HOST port. It is shown not to be defined for the blank. Instance name (fjpfcaX) is displayed
for the fibre channel card (GP7B8FC1, PW008FC2, PW008FC3, SE0X7F11X, and SE0X7 F12X).
OSDeviceName
Device name (physical path name).
Link Status
It displays it when Link Status is not in the state of Link up.
HBA_PORTSTATE_OFFLINE(2): off-line
HBA_PORTSTATE_BYPASSED(4): Bypassed state

33
HBA_PORTSTATE_DIAGNOSTICS(5): In diagnostics mode
HBA_PORTSTATE_LINKDOWN(6): Link down state
HBA_PORTSTATE_ERROR(7): Port Error state
HBA_PORTSTATE_LOOPBACK(8): Loopback state
HBA_PORTSTATE_UNKNOWN(%d): unknown state
Link PortType
When it is not Fabric connection or port_id of HOST becomes 0x000000, it is displayed.
HBA_PORTTYPE_NPORT(5): N_port connection.
HBA_PORTTYPE_NLPORT(6): NL_port connection.
HBA_PORTTYPE_LPORT(20): FC-AL connection.
HBA_PORTTYPE_PTP(21): point to point connection.
HBA_PORTTYPE_XXX(%d): unknown state
NumberOfDiscoveredPort=0
When the target device is not connected, it is displayed.

The following message is displayed when there is a target device connected with Fabric different from Fabric with which HOST
port is connected.
Warning : Binding target devices connected to the other switches

(2) Information on Fabric


swXX
Name of fabric that fc_check command provided.
Fabric Name
Vendor name of Interconnect Element Name Vendor Name Fabric device for which FC-GS provides.
(3) Information on target device
swXX
the fabric name target device connect with.
0xXXXXXX device name
It is port_id of the target device.
If the fjpfca driver is not recognizing it, it becomes 0x000000. The device name displays information obtained by the SCSI
Inquiry command.
PortWWN
It is port WWN of the target device.
NodeWWN
It is node WWN of the target device.
PortSymbolicName
It is port symbolic name of the target device. It becomes blank when not obtaining it from the target device.
OSDeviceName
It is a name that shows SCSI Logical Unit.
(4) Information that shows FC-AL connection
Loop
It displays it at the FC-AL with HUB or FC-AL without HUB.
(5) Information that shows that there is target definition where real unit doesn't exist

34
???
This is defined in fcp-bind-target of environment definition file (/kernel/drv/fjpfca.conf), and when the target device cannot
be detected, it is displayed. and WWN of the target definition is displayed.
OPTIONS
· none
EXAMPLES
Example of Fabric topology

# fc_checkc
[adapter_index=0, hba_port_index=0]
0x010200 WWPN=0x1000000b5d65c060 WWNN=0x100000e000c50140 (*-1)
| com.fujitsu.jp-PFCA-0 Model=SE0X7F12X
| NodeSymbolicName=, PortSymbolicName=fjpfca2
| OSDeviceName=/devices/pci@2,600000/fibre-channel@0:devctl
|
sw01 --+-- Fabric Name=0x100000051e35f334 (*-2)
| | Vendor Name=Brocade Communications, Inc..34.0 v5.1.0a
||
| | sw01
| +-- 0x010e00 FUJITSU-E3000-0000 (*-3)
| | PortWWN=0x230000e000a819f1 NodeWWN=0x230000e000a819f1
| | PortSymbolicName=
| | OSDeviceName=/dev/rdsk/c7t0d0s2
[adapter_index=0, hba_port_index=1]
0x010100 WWPN=0x1000000b5d65c061 WWNN=0x100000e000c50140
| com.fujitsu.jp-PFCA-0 Model=SE0X7F12F
| NodeSymbolicName=, PortSymbolicName=fjpfca3
| OSDeviceName=/devices/pci@2,600000/fibre-channel@0,1:devctl
|
|
sw01 --+-- Fabric Name=0x100000051e35f334
| | Vendor Name=Brocade Communications, Inc..34.0 v5.1.0a
||
| | sw01
| +-- 0x010900 FUJITSU-E3000-0000
| | PortWWN=0x230000e000a8199e NodeWWN=0x230000e000a8199e
| | PortSymbolicName=
| | OSDeviceName=/dev/rdsk/c8t1d0s2

35
(*-1), (*-2), and (*-3)
adaptors 0(instance name = fjpfca2) are connected with Fabric sw01, are connected E3000 (wwn=0x230000e000a819f1) with the
same zone of sw01, and are recognized as the target device. (- -1 Model=SE0X7F12X is a fibre channel card name.)

Example of FC-AL topology.


# /opt/FJSVpfca/sbin/fc_checkc
[adapter_index=0, hba_port_index=0]
0x000001 WWPN=0x0b0000109ac0655d WWNN=0x1000000b5ddc00fa
| com.fujitsu.jp-PFCA-0 Model=SE0X7F12F
| NodeSymbolicName=, PortSymbolicName=fjpfca2
| OSDeviceName=/devices/pci@1,700000/fibre-channel@0:devctl
| Link PortType=HBA_PORTTYPE_LPORT(20)
|
|
Loop+--
||
||
| +-- 0x0000ef FUJITSU-E3000-0000
| | PortWWN=0x210000e000a8199e NodeWWN=0x210000e000a8199e
| | PortSymbolicName=
| | OSDeviceName=/dev/rdsk/c8t0d0s2

Example when there is target definition and target doesn't exist.


[adapter_index=1, hba_port_index=0]
0x031300 WWPN=0x1000000b5d65c060 WWNN=0x100000e000c50140
| com.fujitsu.jp-PFCA-1 Model=SE0X7F12F
| NodeSymbolicName=, PortSymbolicName=fjpfca1
| OSDeviceName=/devices/pci@2,600000/fibre-channel@0:devctl
|
|
sw03 --+-- Fabric Name=0x1000006069102543
| | Vendor Name=Brocade Communications, Inc..2.4 v2.6.0c
|
|
|******************************
|
? ? ?--+--
||
||
| +-- 0x000000
| | PortWWN=0x50000e100000373c NodeWWN=0x50000e100000373c
| | PortSymbolicName=
| | OSDeviceName=

NOTE
none
EXIT STATUS
0: Normal termination
Integer of 1 or more: Abnormal termination.

3.10 fc_hbaprp
NAME
fc_hbaprp - It variously sets to the fibre channel boot code.

36
SYNOPSIS
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -f tgt_id -P WWN
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -f tgt_id -I PORT_ID
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -d tgt_id
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -D [-y]
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -w boot-wait-time
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -l linkspeed
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -t topology
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -v
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -s savefile
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -r|-R filename
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -c conffile
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -C [-y]
/usr/sbin/FJSVpfca/fc_hbaprp -i adpname -b ENABLE|DISABLE
DESCRIPTION
This command sets to the boot code of the fibre channel card used for SAN Boot. Please refer to "SAN Boot environment
construction guide" for details concerning SAN Boot.

OPTIONS
It is possible to set it to the boot code of the fibre channel card as follows. It is necessary to specify instance name
(adpname) to specify the adaptor for i option. The instance name is specified by “adaptor driver name + adaptor instance
number”(fjpfca0). It can know the instance name of all of be mounted adaptors by a option (The operand is not specified)-
of the fc_info command.
-i adpname -f tgt_id -P WWN
-i adpname -f tgt_id -I PORT_ID
The target device (boot disk) is registered in the boot code of the fibre channel card used for SAN Boot. The target device
can be registered up to 10 entries or less. The target device is specified by combining "-f target_id + -P WWN" or "-f
target_id + -I port_id".

Tgt_id: Target_id of the target device.


WWN : World Wide Name of the target device.
PORT_ID: Port_id of the target device.

-i adpname -d tgt_id
Delete the setting of the target device registered with Target_ID (tgt_id).
Tgt_id: Target_id of the target device.

-i adpname -D [-y]
Delete All the settings of the target device registered in the boot code for SAN Boot.
-If -y is not added, the message to confirm the deletion of the setting is displayed.
-When y is added, the setting is unconditionally deleted.

-i adpname -w boot-wait-time
Set the boot delay time every second. The following one exists as a value that can be set.
0 : The boot delay time is not used.
180-86400: The boot delay time (For three minutes for ..~.. 24 hours) is specified.

-i adpname -l linkspeed
Set the link speed. The following one exists as a value that can be set.
1G|1g : It sets it to 1Gbps.
2G|2g : It sets it to 2Gbps.
4G|4g : It sets it to 4Gbps.
AUTO|Auto : It sets it to AUTO.

-i adpname -t topology
Set the topology. The following one exists as a value that can be set.
NPORT|Nport: Fabric topology. It is a setting done when connecting with the fibre channel switch.
AL|Al: FC-AL topology.
AUTO|Auto: It sets it automatically.

-i adpname -v
This command option display the setting. It is the display stripes as for the following information.

Item Value Description

37
Boot function DISABLE/ENABLE Specify boot feature.
Target_ID Ex) 0 Target_ID value.
Target WWN Ex)50000e1000002d51 WWN of bind target device.
Target DID Ex)010111 DID of bind target device.
topology AL/N_PORT/AUTO Fibre channel topology. AUTO means the automatic setting.
link-speed 1G/2G/4G/AUTO Fibre channel link speed. AUTO means the automatic setting.
boot wait time DISABLE or Set boot waiting time. The unit of the figure is a second.
number(digit) When boot at DISABLE setting. It doesn't wait this time.
interval time DISABLE This item is not used. Moreover, this value cannot be changed.
boot wait msg DISABLE This item is not used. Moreover, this value cannot be changed.

-i adpname -s savefile
The content set to the boot code of the fibre channel card used for SAN Boot is preserved. The following set content is
preserved.
Item Value Description

Boot function DISABLE/ENABLE Specify boot feature.


Target_ID Ex) 0 Target_ID value.
Target WWN Ex)50000e1000002d51 WWN of bind target device.
Target DID Ex)010111 DID of bind target device.
topology AL/N_PORT/AUTO Fibre channel topology. AUTO means the automatic setting.
link-speed 1G/2G/4G/AUTO Fibre channel link speed. AUTO means the automatic setting.
boot wait time DISABLE or Set boot waiting time. The unit of the figure is a second.
number(digit) When boot at DISABLE setting. It doesn't wait this time.
interval time DISABLE This item is not used. Moreover, this value cannot be changed.
boot wait msg DISABLE This item is not used. Moreover, this value cannot be changed.
-i adpname -r|-R filename
Reflect the setting preserved by -s command option to the boot code.
-r : Reflect the setting without boot function content.
-R : Reflect the entire setting with boot function content.

-i adpname -c conffile
Reflect the content of driver configuration file.
/kernel/drv/fjpfca.conf or the file equal with it is specified for configuration file.

-i adpname -C [-y]
Delete An entire setting from the boot code without boot function. If -y is not added, the message to confirm the deletion of
the setting is displayed. When -y is added, the setting is unconditionally deleted.

-i adpname -b ENABLE|DISABLE
Effective/ineffective of the boot feature is set to the boot code of the fibre channel card.
ENABLE: The boot feature is made effective.
DISABLE: The boot feature is ineffective.

EXAMPLES

38
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -f 0 -P 0x210000e0001014d9
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -f 1 -I 0x10c00
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -d 0
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -D
delete all bind registration ? [y(Y),n(N) ] y
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -w 180
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -l 4g
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -t nport
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -v
boot function : ENABLE
topology : N_Port
link-speed : 4G
boot wait time : 180 ( interval time : DISABLE , boot wait msg : DISABLE )
bind-target: Target_ID=0,WWPN=0x210000e0001014d9
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -s savefile
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -r savefile
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -c /kernel/drv/fjpfca.conf
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 –C –y
# /usr/sbin/FJSVpfca/fc_hbaprp -i fjpfca0 -b ENABLE

NOTE
none
EXIT STATUS
0: Normal termination
Integer of 1 or more: Abnormal termination.

39
40
Chapter 4 Troubleshooting
If a problem occurs, check the following.
------------------
Has the driver been installed?
If nothing is indicated by pkginfo -x FJSVpfca ( pkginfo -x FJSVpfcb for Solaris 10 sun4us machine class environment), the
driver has not been installed. Install the driver using the CD-ROM provided with the adapter.
------------------
Has the adapter been recognized by the system?
Can you find any 'pci10cf,105c'(GP7B8FC1),'pci10cf,1178'(PW008FC2),'pci10cf,12c3'(PW008FC3) string in the output from
"prtconf -pv | grep 10cf"? If you can't find it, the OBP(Open Boot PROM) does not recognize the adapter. Check the adapter
installation.
If you are using a machine made by Sun Microsystems(also includes OEM products), and if you find some 'pci105c,10cf' strings
in stead of 'pci10cf,105c', the OBP has a bug. To resolve this problem, there are two solutions.
[Updating the OBP]
Information about bugs of OBP and its fix are described in the following URL.
URL:
http://access1.sun.com/
Search Keyword
hardware/prom
Download an appropriate fix to your machine, and install it according to the direction in it.
[Avoiding the OBP bug without updating it]
You can avoid the bug of OBP by registering the driver to the system according to incorrect property generated by the OBP. After
installing the FJSVpfca package, perform following operations once by super user.
1. # rev_drv fjpfca
2. # add_drv -c scsi -i '"pci105c,10cf"' fjpfca
3. # reboot
If there seems to be no problem on adapter installation and the OBP, the adapter may be defective.
------------------
Is the SIG LED on the adapter on?
If the LED is off, the optical fibre cable may be defective, the connectors may be not properly attached, or the adapter may be
defective. For each of these cases, optical signals from the connected device cannot be seen.
------------------
Is the LINK LED on the adapter on?
If the LED is off, the Fibre Channel loop or between the adaptor and fabric has not been enabled for communication. Check the
connectors and the power to the hub or Fabric, change the connected port on the hub or Fabric, replace the optical fibre, turn the
disk array device power off and then on, or reinstall the driver.
This LED does not light because the adaptor does not enter the state that it is possible to communicate when the definition of the
driver is wrong. Please delete the port property, and test the connection by the automatic choice mode.
------------------
Is the SCSI target ID of the device displayed in /usr/sbin/FJSVpfca/fc_info -p?
If the desired device is not shown, its power may be off or its configuration (the AL_PA or SCSI target ID) may be wrong. Check
the state of the device and its configuration. The device configuration will not be valid until the power is turned off and then on
again. If the device is not correctly identified even though the configuration is correct, turn the device power off and on again.
In Fabric connection, Fabric definition leakage of target device, Set mistake of fjpfca.conf, difference between definition and
Actual connection, etc. is thought. The content of the connection and the environment definition file is confirmed again. Please
check the fjpfca.conf file by the chk_conf command.
If the SCSI target ID is indicated, but the port ID is reported as -1, the device cannot be currently identified. Check the state of the
device (power, the connection state of the optical fibre, etc.).

41
------------------
Is the vendor code of a target device displayed in /usr/sbin/FJSVpfca/fc_info -c?
If neither the intended SCSI target ID nor the logical unit number is displayed, the device configuration in the SCSI target driver
(such as sd.conf) is wrong or the device definitions have not taken effect in the kernel. See "2.4 SCSI Target Driver
Configuration."
If the intended target ID and logical unit are indicated but no vendor ID for the disk array device (character string identifying the
product) follows them on the line, a logical unit is not defined for the device. Refer to the manual for the device to create a logical
unit.
------------------
If the hot system replacement in the clustering system has failed:
Follow the steps explained below for how to deal with an abnormal termination in the hot system replacement request (clchgfc)
command of the clustering system.
Error Type Examples of Error Messages Workaround
clchgfc: input parameter is
illegal.
clchgfc: specified disk does not
exist.
clchgfc: specified disk is not
fibre-channel device.
clchgfc: to send exchange port
command is failed.
clchgfc: input wwn format is
illegal: %s
usage: clchgfc -c raw_device [-f
log_file]
usage: clchgfc -d raw_device [-p
WWN] [-f log_file]
clchgfc: ERROR: You must be
"root" for clchgfc to execute
properly.
clchgfc: failed. You should
specify new target's WWN for
Parameter Error bind target. Verify parameter to execute the command again.
Please retry again. "clchgfc -d
raw_device -p new_wwn"
chgfcctl: specified instance does
not exist
chgfcctl: failed. You should
specify new target's WWN for
bind target.
Please retry again. "chgfcctl -d
raw_device -p new_wwn" or
"chgfcctl -i fjpfcaX -o old_wwn
-n new_wwn"
chgfcctl: failed. You must not
specify new target's WWN for
un-bind target.
Please retry again. "chgfcctl -d
raw_device" or
"chgfcctl -i fjpfcaX -o old_wwn"
chgfcctl: %s, no such binding in
/kernel/drv/fjpfca.conf.
clchgfc: specified disk is used by
other process.
clchgfc: can't get user memory Error occurs in the node where the command is executed, execute the
Temporary area. command again after a while.
memory chgfcctl: specified disk is used Error occurs in the other node, perform the hot system replacement
shortage, etc. by other process request in the node where the error is generated individually using with
chgfcctl: can't get user memory chgfcctl.
area.

42
When it does not reboot the system after the work of an initial
introduction of the clustered system, the daemon for the clchgfc
command is not active. It starts the daemon with all nodes where
Abnormality of timeout error is occured as follows by the super user. Please execute
clchgfc: timeout error. clchgfc command again.
other node
# ps -ef | grep /usr/lib/FJSVpfca/clexecd
# (confirms the clexecd is not active)
# /usr/lib/FJSVpfca/clexecd & <RETURN>
When the clustering state can be restored, execute the command again
Abnormality of after restoration.
clchgfc: cluster is abnormal state.
clustering status When the restoration is impossible, perform the hot system replacement
request in all nodes individually using with chgfcctl.
chgfcctl: there were some non
fatal errors in fjpfca.conf. Still
trying to modify it.
chgfcctl: there were some fatal
errrors in fjpfca.conf. Replacing
WWN is aborted.
chgfcctl: broken target
binding: %s
Rewriting The environment setting file of the node where error occurred must be
chgfcctl: can't open
failure of corrected manually according to the current state because hot system
temporally: %s
fjpfca.conf replacement has already ended.
chgfcctl: modification failed: %s
"%s", line %d: syntax error,
before or at: %s
"%s", error: no such alias: %s
"%s", error: duplicate target
definition: %s
"%s", error: duplicate alias
definition: %s

43
44
Appendix A Messages
A.1 fjpfca
A.1.1 Information
Dislay format of the "Infomation" is slightly different between Solaris 2.6 and Solaris 7/Solaris 8/Solaris9. Followings are the
format of Solaris 2.6. In Solaris 7,Solaris 8, Solaris 9 and Solaris 10 the head part of the message; "fjpfca%d:" is displayed as
"/pci@%x,%x/fibre-channel@%x (fjpfca%d):", and after that, newline code is displayed, and then the remaining part is displayed.
------------------
fjpfca%d: INFO :AL link up. alpa=0x%x.
The link status has changed to the up state. No action is required.
------------------
fjpfca%d: INFO :AL link down.
The link status has changed to the down state. If the link-up state is not established in about ten seconds, check the optical fibre
connections, the operating state of the connected device, and the operating state of the hub.
------------------
fjpfca%d: found target. target_id=0x%x port_id=0x%x wwn=%08x%08x
fjpfca%d detected a device with target_id=0x%x port_id=0x%x wwn(port_name)=%08x%08x.
------------------
fjpfca%d: Remote node link_status change is detected. target_id=0x%x. [alias=%s.]
fjpfca%d detected changes which the device of target_id=0x%x port_id=0x%x alias=%s linked. Please check the linking state of
the target device.
------------------
fjpfca%d: the alpa(0x%x) corresponding to the target_id(0x%x) was already used by the target defined in fjpfca.conf.
alpa=0x%x corresponding to target_id=0x%x has already been defined as other targets in the fjpfca.conf file. The target device of
alpa=0x%x existing in the loop cannot be used.
------------------
fjpfca%d: found target's WWN in Name server. wwn=%08x%08x. [alias=%s.]
fjpfca%d detected the device of target_id=0x%x wwn (port_name) = %08x%08x alias=%x. No action is apparently required.
------------------
fjpfca%d: INFO : NPORT link up (connected fabric. id=0x%x.)
The link status has changed to the up state. Connected with fabric. No action is required.
------------------
fjpfca%d: INFO : NPORT link up (connected point-to-point. id=0x%d.)
The link status has changed to the up state. Connected point-to-point with the N_port device. This driver is not supporting the
point-to-point connection with the N_port device. Please review setting of target devie and the driver.
------------------
fjpfca%d: the target whose alpa is 0xdc cannot be used.
Because target_id(0x%d) corresponding to alpa(0x%x) has already
been used as other target's id in fjpfca.conf file.
the target whose alpa is 0xdc cannot be used. Because target_id(0x%d) corresponding to alpa(0x%x) has already been used as
other target's id in fjpfca.conf file. Please add the definition of this target in another target ID when you use this target.
------------------
fjpfca%d: the target connected with point-to-point cannot be used.
Because target_id(0x0) is bound to another target in fjpfca.conf file.
the target connected with point-to-point cannot be used. Because target_id(0x0) is bound to another target in fjpfca.conf

45
file.Please review the environment definition file(/kernel/drv/fjpfca.conf).
------------------
INFO: Unexpected Frame received at data XX phase
An unexpected frame was received. There is a possibility of temporary error of transmission line or target device error. It is not
necessary about the action when thought that the incidence is few and temporary error of the transmission line.
When this messages displayed frequently, other WARNING messages are output. Please observe the action law. The action of this
message is unnecessary.
------------------
fjpfca%d: INFO : Timeout occured. fcph_exp=0x%x.fcph_exp->status = 0x%x. x_id = 0x%x
fjpfca%d: INFO : sest:%x %x %x %x, %x %x %x %x, %x %x %x %x, %x %x %x %x.
The internal information is displayed when the timeout is occured. The action of thie messages is unnecessary.
------------------
fjpfca%d: INFO : LIP(%x, ALPS) received.
The LIP (Loop Initialization Primitive) was received from the device which port-id is ALPS. The action of this message is
unnecessary.
-------------------
fjpfca%d: INFO : fjpfca%dt%d is disabled
The failover timer passed after disable access path. Please confirm the connection of the optical fibre, the state of the hub, and the
state etc. of the attachment unit.
-------------------
fjpfca%d: INFO : fjpfca%dt%d is enabled
The access path of the attachment device is recovered, and possible I/O. No action is apparently required.
-------------------
fjpfca%d: INFO : the target whose alpa is 0x%x cannot be used.\n\tBecause target_id(0x%x) corresponding to
alpa(0x%x) has already\n\tbeen used as auto-bind-target's id.
The target with this alpa(0x%x) cannot be used. Target_id=0x%d to the alpa=0x%x has already been in other target devices by the
auto target bind function. There is a possibility that the environment is changed from the initial environment. Please review the
environment and fibre channel connection.
---------------------
fjpfca%d: INFO : FUJITSU PCI Fibre Channel FCode Version : %s, boot_function=%s;
The version of the boot code. If boot_function is effective, "ENALBE" is displayed . No action is apparently required.
---------------------
fjpfca%d: INFO : Credit error. fm_stat=0x%x
Receiving buffers run short by the flow control.
when this message is displayed just before a link-up message, No action is apparently required.
If the link-up state is not established in about 30 seconds, check the optical fibre connections, the operating state of the connected
device, and the operating state of the hub.

A.1.2 Warning
WARNING: fjpfca: DDI_ATTACH ddi_device_acc_attr_t alloc failed. instance#%d.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: fjpfca: Cmd != DDI_ATTACH. instance#%d.
An unsupported initialization command was issued. The driver does not support power management.
------------------
WARNING: fjpfca: Device in slave-only slot, unused. instance#%d.
The adapter is installed in the slot without DMA capability. This adapter operates using DMA. Change the installation location.

46
------------------
WARNING: fjpfca: High-Level interrupt not supported. instance#%d.
The interrupt level of the adapter is too high. Contact customer support.
------------------
WARNING: fjpfca: Internal control area alloc failed. instance#%d.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Can't alloc DMA handle
The acquisition of resources necessary for driver initialization failed. There are not enough DMA resources. This problem can be
prevented by changing the location of the adapter.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Can't alloc cmd area
The acquisition of resources necessary for driver initialization failed. Memory for storing control data cannot be allocated.
Installed memory may be insufficient. If the amount of memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Can't bind cmd area
The acquisition of resources necessary for driver initialization failed. There are not enough DMA resources. This problem can be
prevented by changing the location of the adapter.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Internal trace Initialize failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
TRANS que construct failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
INTR que construct failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
RSRC que construct failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
CALLBACK que construct failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)

47
Register mapping failed.
The acquisition of resources necessary for driver initialization failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Control index allocate failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Can't add intr.
The interrupt cannot be registered with the kernel. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Can't schedule timer.
The acquisition of resources necessary for initialization failed. Activation of the timer failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI Config Register mapping failed.
The acquisition of resources necessary for initialization failed. The mapping of the PCI configuration space failed. Contact
customer support.
------------------

WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)


Adapter not installed
No adapter is installed. Make sure an adapter is installed.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Adapter not supported ( different Vendor ID ). Vendor-ID = 0x%x.
An unsupported adapter is installed. The vendor ID is not that of a supported adapter. Check the installed adapter.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Adapter not supported ( different Device ID ). Device-ID = 0x%x.
An unsupported adapter is installed. The device ID is not that of asupported adapter. Check the installed adapter.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Adapter not supported ( different SVID ). Device-ID = 0x%x.
An unsupported adapter is installed. The subvendor ID is not that of a supported adapter. Check the installed adapter.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Adapter doesn't have WWN.
There is no WWN (port name) in the adapter. A hardware failure is likely. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Link Failure : Cable Problem?
The optical signals from the connected device cannot be detected or synchronized. Check the optical fibre connections and the
hub connections.
The adapter may have a fault. If this message is displayed even though connections are good, contact customer support.
------------------

48
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Link Failure : Elastic store error.
A link error (elastic store error) occurred. A buffer overrun or underrun occurred because the difference between the clocks on the
receiving and transmitting ends is too great. This error could be the result of a link disturbance. If this message is continuously
displayed, the adapter or connected device may have a fault. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : TX_FAULT signal asserted.
A adapter hardware error was detected. The optical module on the adapter caused the error. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : Transmit Parity error.
A DMA parity error was detected within the adapter control LSI chip. An adapter failure is likely. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : PCI DMA error.
A DMA parity error was detected in the adapter control LSI chip. An adapter failure is likely. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : PCI parity error.
The adapter detected a parity error on the PCI bus. The adapter or PCI bus may have failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Signaled system error.
A system error occurred on the PCI bus. The adapter or PCI bus may have failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Received Master abort.
An error occurred on the PCI bus. When operating as the target, the adapter received an abort request from the master. The adapter
or PCI bus may have failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Received Target abort.
An error occurred on the PCI bus. When operating as the bus master, the adapter received an abort request from the target. The
adapter or PCI bus may have failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Signaled Target abort.
An error occurred on the PCI bus. When operating as the target, the adapter issued an abort request to the bus master. The adapter
or PCI bus may have failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Data parity error.
An error occurred on the PCI bus. When the adapter was operating as the master, a parity error occurred. The adapter or PCI bus
may have failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : Unknown hard error. Intr = 0x%x. CFGSTAT = 0x%x.
Abnormal operation of the control LSI chip was detected in the adapter. Contact customer support.

49
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : Freezing time out.
A time-out error occurred during halt processing of the control LSI chip in the adapter. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't allocate System resource. file: %s version: %s line: %d
There are not enough system resources. Installed memory may be insufficient. If the amount of memory does not seem to be the
problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Unable to attach. file: %s version: %s line: %d
Attach of the fjpfca%d driver failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
%s. file: %s version: %s line: %d
The kernel (DDI, SCSA) function in %s failed. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
%s target_id=0x%x lun=0x%x invalid target device configuration.
file: %s version: %s line: %d
The target definitions in %s(target-driver-name) target_id=0x%x lun=0x%x are invalid. Check the definition files of the target
driver (such as /kernel/drv/target-driver-name.conf).
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
target port_id changed. wwn=%08x%08x
old port_id=0x%x new port_id=0x%x
The port ID of a device with wwn(port_name)=%08x08x was changed from old port_id=0x%x to new port_id=0x%x. If there is
no other warning message which insists the device configuration problem, no action is required since I/O is executed on the basis
of WWNs. If you see another warning message which insists the device configuration problem, obey the instruction of the
warning message.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
found new target port. target_id=0x%x port_id=0x%x
old wwn=%08x%08x, new wwn=%08x%08x
A new device with target_id=0x%x port_id=0x%x was detected. Information about the device with target_id=0x%x was changed
from old wwn(port_name)=%08x%08x to new wwn(port_name)=%08x%08x. This message is displayed only if a device change
instruction is the result of the chgfcctl command.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
duplicate target_id. target_id=0x%x
wwn=%08x%08x(reserve target_id) and wwn=%08x%08x
More than one device has the same target_id. Currently, the device with the reserve target_id is using target_id=0x%x. None of
other devices with the same target_id can be used. To make a hot device replacement, execute the chgfccgl command.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Process Login parameter error. target_id=0x%x port_id=0x%x
wwn=%08x%08x parm=%08x %08x %08x %08x
The device with target_id=0x%x port_id=0x%x wwn(port_name)=%08x%08x cannot be used because of a process login
parameter error. Turn power to the device off and then on again. If the device does not recover from the error, contact customer
support.
------------------

50
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
port_id does not match hard address. wwn=%08x%08x
port_id=0x%x hard_address=0x%x(target_id=0x%x)
The preset address of the device is different with the address it is really using. The preset address of the device is displayed as
"hard_address=0x%x(target_id=0x%x)". The current address it is really using is displayed as "port_id=0x%x". This device can't
be available. Verify preset addresses of all devices in the loop. If you modify the preset address of the device, be sure to turn
power of the device off and on, and to do 2.4.3 the reconfiguration boot. If the preset adresses seems to be correnct, contact
customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
some other device have same hard address with wwn=%08x%08x
port_id=0x%x hard_address=0x%x(target_id=0x%x)
More than one devices has the same preset address. Its preset address is displayed as "hard_address=0x%x(target_id=0x%x)". All
devices which have the same preset address can't be available. Verify preset addresses of all devices in the loop. If you modify the
preset address of the device, be sure to turn power of the device off and on, and to do 2.4.3 the reconfiguration boot. If the preset
adresses seems to be correnct, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
reserved target_id does not match hard address. wwn=%08x%08x
reserved target_id=0x%x port_id=0x%x hard address=0x%x(target_id=0x%x)
The preset address of the device has been changed while it is online. The last preset address is displayed as "resreved
target_id=0x%x". The new preset address is displayed as "hard_address=0x%x(target_id=0x%x)". If the new preset address
makes no confilict with preset addresses of other devices in the loop, the device will be available until the O.S. shutdown. If the
new preset address makes a conflict with the other device in the loop, both of the devices can't be available. Verify preset
addresses of all devices in the loop. If you modify the preset address of the device, be sure to turn power of the device off and on,
and to do 2.4.3 the reconfiguration boot. If the preset adresses seems to be correnct, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d), %s(+0x%x) register read error.
An error occured while reading register.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d), offline.
Adapter fatal error occured or PCI bus is closed due to some hardware error. This adapter can not be used anymore.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't find target's WWN in Name server. wwn=%08x%08x. [alias=%s.]
The device of wwn (port_name) = %08x%08x alias=%s defined by environment definition file (/kernel/drv/fjpfca.conf) was not
able to be detected by fjpfca%d. Please recheck the state of environment definition file, connection between adaptor and fibre
channel switch, connection between target device and fibre channel switch, or zoning setting of fibre channel switch. If this
message is displayed though the mistake is not found in the checking, please contact technical support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't regist port infomation in Name server.
Port information on fjpfca%d was not able to be registered in the name server of the fibre channel switch. Please contact technical
support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
target_id is redefined in fjpfca.conf. target_id=0x%x.
In fcp-bind-target property of environment definition file (/kernel/drv/fjpfca.conf), target ID (target_id=%x) is defined more than
once in the instance of fjpfca%d. In one instance (fjpfca%d), same target ID cannot be defined more than once. Correction of
environment definition file is required.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
WWN is redefined in fjpfca.conf. wwn=%08x%08x.

51
In fcp-bind-target property of environment definition file (/kernel/drv/fjpfca.conf), WWN (wwn=%08x%08x) is defined more
than once in the instance of fjpfca%d. In one instance (fjpfca%d), same WWN cannot be defined more than once. Correction of
environment definition file is required.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
controller chip resetting.(detect internal error)
Since the abnormal operation of control LSI in the adaptor was detected, the recovary processing has been performed. Please
contact technical support if this message is frequently displayed.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
controller chip reset.(user operation)
The control LSI in the adapter was initialized by user operation (fc_adm -r). No action is apparently required.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't find configured target(wwn=%08x%08x [alias=%s]) on fjpfca%d.
The target (wwn=%08x%08x [alias=%s]) defined in the fcp-bind-target property of the environment definition file
(/kernel/drv/fjpfca.conf) were not found in the loop status. Modify the entries in the environment definition file.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't %s ( %s ) and recover is failed( %s ).
Driver Initialize process failed. Installed memory may be insufficient. If the amount of memory does not seem to be the problem,
contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Can't add software intr.
The interrupt cannot be registered with the kernel. Contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Internal trace initialize failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Register mapping failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
Control index allocate failed.
The acquisition of resources required for driver initialization failed. Installed memory may be insufficient. If the amount of
memory does not seem to be the problem, contact customer support.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
scsi command timeout (fjpfca0). ex = 0x%x cdb = %x %x %x %x. file: fcp_main.c version: $Revision: %d.%d
I/O command timeout error is occured. It might be happen because of 1)temporary transmission line's error,2)target device
hardware error, and , 3)miss setting of target device side.Please contact technical support if this message is frequently displayed.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
received short frame(XXXXXXX). file: fcp_main.c version: $Revision: %d.%d.%d.%d $ line: %d
The frame lost due to an error of fibre channel transmission line was detected. A temporary error might occur stochastically in the

52
specification, data frame be damaged due to an error, and frame lost is happen. Please contact technical support if this message is
frequently displayed.
------------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
received invalid interface unit. file: fcp_main.c version: $Revision: %d.%d.%d.%d $ line: %d
An illegal frame on the fibre channel protocol was received.It happens because of target device error, please confirm the state of
target device.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
target definition was ignored.
invalid alias format: %s
The mistake was found in the alias definition of/kernel/drv/fjpfca.conf, and the target specified for fcp-bind-target was not able to
be specified. Processing is continued disregarding an illegal definition. Please review the alias definition of/kenrel/drv/fjpfca.conf.
-------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
target definition was ignored.
invalid WWN format: %s
The mistake was found in the fcp-bind-target definition in configuration file (/kernel/drv/fjpfca.conf), and the target specified for
fcp-bind-target was not able to be specified. Processing is continued disregarding an illegal definition. Please review the alias
definition of /kenrel/drv/fjpfca.conf.
-------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
target definition at %s was ignored.
The mistake was found in the fcp-bind-target definition in configuration file (/kernel/drv/fjpfca.conf), and the target was not able
to be specified. Processing is continued disregarding an illegal definition. Please review the fcp-bind-target definition of
/kenrel/drv/fjpfca.conf.
-------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
auto-bind-target definition(target_id=0x%x) is ignored\n\tdue to target_id is reserved by fcp-bind-target.
Information on the target device used for SAN Boot was not able to be succeeded to the fjpfca driver. It causes because the
fcp-bind-target definition and the correspondence of configuration file (/kenrel/drv/fjpfca.conf) are not taken. Please review the
setting of the configuration file.
-------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
auto-bind-target definition(wwn=0x%08x%08x) is ignored\n\tdue to wwn is reserved by fcp-bind-target.
Information on the target device used for SAN Boot was not able to be succeeded to the fjpfca driver. It causes because the
fcp-bind-target definition and the correspondence of configuration file (/kenrel/drv/fjpfca.conf) are not taken. Please review the
setting of the configuration file.
-------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca%d):
auto-bind-target definition at %s was ignored.
It failed in the boot code of the fibre channel card used for SAN Boot and the fjpfca driver failed in taking set auto bind target
information. The adapter may have failed. Contact customer support
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Unsupported Request Error.
The adaptor detected the Unsupported Request Error error on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.

53
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Malformed TLP.
The adaptor detected the Malformed TLP error on PCI bus. The adapter or PCI bus may have failed. Contact customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Unexpected Completion.
The adaptor detected the Unexpected Completion error on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Completion Timeout.
The adaptor detected the Completion Timeout error on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Poisoned TLP.
The adaptor detected the Poisoned TLP error on PCI bus. The adapter or PCI bus may have failed. Contact customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Data Link Protocol Error.
The adaptor detected the Data Link Protocol Error error on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Split Completion Timeout.
The adaptor detected the Split Completion Timeout error on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Unexpected Split Completion.
The adaptor detected the Unexpected Split Completion error on PCI bus. The adapter or PCI bus may have failed. Contact
customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Parity Error on Outbound Data.
The adaptor detected the Parity Error on Outbound Data on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Split Completion Excessive Byte.
The adaptor detected the Split Completion Excessive Byte error on PCI bus. The adapter or PCI bus may have failed. Contact
customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)

54
PCI bus Error : Parity Error Register TLP.
The adaptor detected the Parity Error Register TLP on PCI bus. The adapter or PCI bus may have failed. Contact customer
support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
PCI bus Error : Parity Error Split TLP.
The adaptor detected the Parity Error Split TLP on PCI bus. The adapter or PCI bus may have failed. Contact customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : Outbound Parity Error.
The adaptor detected the outbound parity error. The adapter may have failed. Contact customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
Hard Error : Inbound Parity Error.
The adaptor detected the InBound Parity Error. The adapter may have failed. Contact customer support.
----------------
WARNING: /pci@%x,%x/fibre-channel@%x (fjpfca#)
SFP Module Problem?
The SFP module (optical module) may not be connected to Fibre Channe card. Please check the connection state of a SFP module.
Please contact a support representative, when this message is displayed, although there is no problem in connection of a SFP
module.

A.2 chgfcctl
------------------
chgfcctl: input parameter is illegal.
An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
chgfcctl: specified disk does not exist.
An invalid device was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
chgfcctl: specified disk is not fibre-channel device.
The specified device is not a device which fjpfca controls. Check that the parameter entry is defined correctly and execute the
command again.
------------------
chgfcctl: specified disk is used by other process.
The hot device replacement of the specified device cannot be done while other process has been processed. Execute this command
again later.
------------------
chgfcctl: can't get user memory area.
Insufficient working memory for the command was reported. Execute this command again later.
------------------
chgfcctl: to send exchange port command is failed.
The hot device replacement instruction of the controller failed in the fjpfca driver. If the device defined in the fcp-bind-target
without specifying "-p WWN" or the device not defined in the fcp-bind-target with specifying "-p WWN", this error message is
reported. Check that the parameter entry is defined correctly and execute the command again.
------------------

55
chgfcctl: input wwn format is illegal: %s
An invalid WWN (World Wide Name) was specified. Check that the parameter entry is defined correctly and execute the
command again.
------------------
usage: chgfcctl -d raw_device [-p NEW_TARGET_WWN]
chgfcctl -i instance_name -o OLD_TARGET_WWN [-n NEW_TRAGET_WWN]
An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
chgfcctl: there were some non fatal errors in fjpfca.conf. Still trying to modify it.
Minor error in the /kernel/drv/fjpfca.conf file was detected while processing the command but the operation is continued. Check
that the /kernel/drv/fjpfca.conffile is defined correctly after the processing.
------------------
chgfcctl: there were some fatal errrors in fjpfca.conf. Replacing WWN is aborted.
Fatal error in the /kernel/drv/fjpfca.conf file was detected while processing the command and the operation cannot be continued.
Check that the /kernel/drv/fjpfca.conf is defined correctly and execute the command again.
------------------
chgfcctl: broken target binding: %s
The indicated definition (fcp-bind-target) of the target was invalid. Check the definition entry and correct it.
------------------
chgfcctl: can't open temporally: %s
Temporary file for edit cannot be created. Delete the unnecessary files in /tmp directory and execute the command again later.
------------------
chgfcctl: modification failed: %s
Updating the file was failed. Follow the action indicated in the other message, or contact your authorized support personnel.
------------------
"%s", line %d: syntax error, before or at: %s
Grammatical error was found in the character string around the line indicated.
------------------
"%s", error: no such alias: %s
Such an alias definition does not exist.
------------------
"%s", error: duplicate target definition: %s
Target definition in the fcp-bind-target was overlapped.
------------------
"%s", error: duplicate alias definition: %s
An alias definition was overlapped.
------------------
chgfcctl: specified instance does not exist.
Instance specified with -i option does not exist.
------------------
chgfcctl: failed. You should specify new target's WWN for bind target.
Please retry again. "chgfcctl -d raw_device -p new_wwn" or
chgfcctl -i fjpfcaX -o old_wwn -n new_wwn"
The command was issued without a new WWN for the target device defined in the fcp-bind-target property of
/kernel/drv/fjpfca.conf file. Execute the command with a new WWN.

56
------------------
chgfcctl: failed. You must not specify new target's WWN for un-bind target.
Please retry again. "chgfcctl -d raw_device" or
chgfcctl -i fjpfcaX -o old_wwn"
The command was issued with a new WWN for the target which is not defined in the fcp-bind-target property of
/kernel/drv/fjpfca.conf file. The specification of new WWN is not required.
------------------
chgfcctl: %s, no such binding in /kernel/drv/fjpfca.conf.
The specified device does not exist in the fcp-bind-target definition. Correct /kernel/drv/fjpfca.conf manually though hot system
replacement has already ended.

A.3 chk_conf
------------------
"%s", line %d: syntax error, unexpected EOF.
Grammatical error was detected. The end of the file is reached unexpectedly.
------------------
"%s", line %d: syntax error, before or at: %s
Grammatical error was found in the character string around the line indicated.
------------------
"%s", error: no such alias: %s
Such an alias definition does not exist.
------------------
"%s", error: duplicate target definition: %s
Target definition in the fcp-bind-target was overlapped.
------------------
"%s", error: duplicate alias definition: %s
An alias definition was overlapped.
------------------
Name server lookup( %s ) failed on fjpfca#%d
An inquiry from the Fibre Channel to the name server was failed. In the environment without the Fabric devices, disregard this
error message. In the environment with the Fabric devices, it is likely that the error in the connection with the Fabric device, or
that the Fabric device does not work.
------------------
target '%s'(wwn=%s) seems to be absent on fjpfca#%d
The specified target was not found in the definition of the adapter. Check that the entry is defined correctly, or that the device is
connected properly.
In Fabric connecting, if this error is displayed though it does not find the mistake in the definition, the connection, and setting the
zone, confirm the Device Probing function of SN200 is set in "Effective". If it is set "Invalidity", try to set in "Effective", and
execute chk_conf command again. Please refer to "3.6 Note of chk_conf" for details.
------------------
target '%s' on fjpfca#%d seems to be unsupport SCSI-FCP(8) fc4_types
The specified target didn't supported service of FCP. Check that the device is connected properly. If this error is displayed though
it does not find the mistake in the definition, the connection, and setting the zone of fabric, confirm the Device Probing function
of SN200 is set in "Effective". If it is set "Invalidity", try to set in "Effective", and execute chk_conf command again. Please refer
to "3.6 Note of 3.6 chk_conf" for details.
------------------
%s seems to be correct.

57
The check ended successfully. No error was found.
------------------
usage: chk_conf [-c config_file] [-v]
An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
there were some non fatal errors in fjpfca.conf. Still trying to check it.
Minor error in the /kernel/drv/fjpfca.conf file was detected while processing the command but the operation is continued. Check
that the /kernel/drv/fjpfca.conffile is defined correctly after the processing.
------------------
there were some fatal errrors in fjpfca.conf. Config file check is aborted.
Fatal error in the /kernel/drv/fjpfca.conf file was detected while processing the command and the operation cannot be continued.
Check that the /kernel/drv/fjpfca.conf is defined correctly and execute the command again.
------------------
"%s", error: duplicate port definition: %s
A port definition was overlapped.
------------------
"%s", error: duplicate throttle definition: %s
A max-throttle definition was overlapped.
------------------
"%s", error: more than one fcp-bind-target properties exist
A fcp-bind-target definition was overlapped.
------------------
"%s", error: more than one alias properties exist
An alias definition was overlapped.
------------------
"%s", error: more than one port properties exist
A port definition was overlapped.
------------------
"%s", error: more than one max-throttle properties exist
A max-throttle definition was overlapped.
------------------
error: one WWN binds more than one target's at same instance: %s
The WWN indicated in %s is defined as a different target_id in the same instance. Verify the syntax of fcp-bind-target.
------------------
error: throttle value is out of range.(1 - 255): %d
The value of max-throttle indicated in %d is exceeded. Input the value of max-throttle within the range from 1 to 255.
----------------
error: The number of characters of alias is over 16 characters.: %s
16 characters to be able to set %s to the alias name are exceeded. Please set the alias name by 16 characters or less.
----------------
error: duplicate failover_function definition
A failover_function definition was overlapped.
----------------

58
error: duplicate fcp_recover_timer definition
A fcp_recover_timer definition was overlapped.
----------------
error: duplicate fcp_recover_interval definition
A fcp_recover_interval sentence was overlapped.
----------------
error: duplicate max-throttle-all definition
A max-throttle-all definition was overlapped.
----------------
error: failover_function is out of range.(0 or 1): %d
The value of failover_function in %d is exceeded. Input the value of 0 or 1 to the failover_function value.
----------------
error: fcp_recover_timer is out of range.(0 - 86400): %d
The value of fcp_recover_timer in %d is exceeded. Input the value of fcp_recover_timer within the range from 0 to 86400.
----------------
error: fcp_recover_interval is out of range.(0 - 10): %d
The value of fcp_recover_interval in %d is exceeded. Input the value of fcp_recover_interval within the range from 0 to 10.
----------------
error: max-throttle-all is out of range.(1 - 255): %d
The value of max-throttle-all in %d is exceeded. Input the value of max-throttle-all within the range from 1 to 255.

A.4 clchgfc
The clchgfc displays the error message of all nodes where the error occurs by the following formats.
clchgfc: detected the following error.
[node1_name] instance1_name:
instance1_name: error message of instance1 in node1
[node2_name] instance1_name:
instance1_name: error message of instance1 in node2
See [node_name1]:%s for details.
Clchgfc executes the chgfcctl command internally. Therefore, please refer to "A.2 A.2 chgfcctl" for the one which starts by
"chgfcctl:" among error messages of each node.
Moreover, refer to "If the hot system replacement in the clustering system has failed" in "Chapter 4 Troubleshooting" for how to
deal with the cause when error occurs.
------------------
clchgfc: input parameter is illegal.
An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
clchgfc: specified disk does not exist.
An invalid device was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
clchgfc: specified disk is not fibre-channel device.
The specified device is not a device which fjpfca controls. Check that the parameter entry is defined correctly and execute the
command again.
------------------
clchgfc: specified disk is used by other process.
The hot device replacement of the specified device cannot be done while other process has been processed. Execute this command

59
again later.
------------------
clchgfc: can't get user memory area.
Insufficient working memory for the command was reported. Execute this command again later.
------------------
clchgfc: to send exchange port command is failed.
The hot device replacement instruction of the controller failed in the fjpfca driver. If the device defined in the fcp-bind-target
without specifying "-p WWN" or the device not defined in the fcp-bind-target with specifying "-p WWN", this error message is
reported. Check that the parameter entry is defined correctly and execute the command again.
------------------
clchgfc: input wwn format is illegal: %s
An invalid WWN (World Wide Name) was specified. Check that the parameter entry is defined correctly and execute the
command again.
------------------
usage: clchgfc -c raw_device [-f log_file]
usage: clchgfc -d raw_device [-p WWN] [-f log_file]
usage: clchgfc -C raw_device [-f log_file]
usage: clchgfc -D raw_device [-p WWN] [-f log_file]
An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
clchgfc: timeout error.
There is no response from other nodes. It is thought the daemon for clchgfc command(/usr/lib/FJSVpfca/clexecd) in the node
where the error occured is not active. Please execute the clchgfc command again after starting the daemon. Details refer to the
paragraph of "Abnormality of other node" of "If the hot system replacement in the clustering system has failed" in "Chapter 4
Troubleshooting"
------------------
clchgfc: ERROR: You must be "root" for clchgfc to execute properly.
The clchgfc command was executed by permissions other than superuser. Execute the command again after becoming a superuser.
------------------
clchgfc: failed. You should specify new target's WWN for bind target.
Please retry again. "clchgfc -d raw_device -p new_wwn"
The command was issued without a new WWN for the target device defined in the fcp-bind-target property of
/kernel/drv/fjpfca.conf file. Execute the command with a new WWN.
------------------
clchgfc: cluster is abnormal state.
Abnormality is found in the state of clustering. Verify the clustering environment.
------------------
cluster configuration management (ClDispatchEvent) abnormal end (-29:306)
Communication of clustering event service failed. Verify the clustering environment. This message appears when initiliaze
clustering environment( execute by reset.sh or clinitrest in SafeCluster), In this case, system boot is required.
------------------
specified WWN is defined with other diskpath
Spcified WWN is defined as other diskpath's WWN. Execute command with a new WWN.

A.5 fc_hbaprp
---------------

60
Usage: fc_hbaprp -i adpname -f target_id -P WWN
Usage: fc_hbaprp -i adpname -f target_id -I PORT_ID
Usage: fc_hbaprp -i adpname -w boot_wait_time [-W interval msg]
Usage: fc_hbaprp -i adpname -t topology
Usage: fc_hbaprp -i adpname -l linkspeed
Usage: fc_hbaprp -i adpname -d target_id
Usage: fc_hbaprp -i adpname -D [-y]
Usage: fc_hbaprp -i adpname -s savefile
Usage: fc_hbaprp -i adpname -r|-R filename
Usage: fc_hbaprp -i adpname -c conffile
Usage: fc_hbaprp -i adpname -v
Usage: fc_hbaprp -i adpname -b ENABLE|DISABLE
Usage: The mistake is found in fc_hbaprp -i adpname -C -y argument.

An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
error: no such alias: %s
Such an alias definition does not exist.
------------------
error: duplicate target definition: %s
Target definition in the fcp-bind-target was overlapped.
------------------
error: duplicate alias definition: %s
An alias definition was overlapped.
------------------
error: duplicate port definition: %s
A port definition was overlapped.
------------------
error: duplicate throttle definition: %s
A max-throttle definition was overlapped.
------------------
error: more than one fcp-bind-target properties exist
A fcp-bind-target definition was overlapped.
------------------
error: more than one alias properties exist
An alias definition was overlapped.
------------------
error: more than one port properties exist
A port definition was overlapped.
------------------
error: more than one max-throttle properties exist
A max-throttle definition was overlapped.
------------------

61
error: one WWN binds more than one target's at same instance: %s
The WWN indicated in %s is defined as a different target_id in the same instance. Verify the syntax of fcp-bind-target.
------------------
error: throttle value is out of range.(1 - 255): %d
The value of max-throttle indicated in %d is exceeded. Input the value of max-throttle within the range from 1 to 255.
----------------
error: The number of characters of alias is over 16 characters.: %s
16 characters to be able to set %s to the alias name are exceeded. Please set the alias name by 16 characters or less.
----------------
error: duplicate boot_wait definition: fjpfca%d
A boot-wait definition was overlapped.
----------------
error: more than one boot_wait properties exist
A boot_wait definition was overlapped.
----------------
error: boot_wait value is out of range.(time:0/180 - 86400, interval:1 - 60, msg:0 or 1)
The value of boot_wait time is exceeded. Input the value of max-throttle within the range from 180 to 86400.
or
The value of boot interval is exceeded. Input the value of boot interval within the range from 1 to 60.
or
The value of boot msg is out of range. Input the value of 0 or 1.
----------------
error: duplicate linkspeed definition
A linkspeed definition was overlapped.
----------------
error: duplicate topology definition
A topology definition was overlapped.
----------------
error: duplicate boot-wait-time definition
A boot-wait-time definition was overlapped.
----------------
error: duplicate boot-wait-interval definition
A boot-wait-interval definition was overlapped.
----------------
error: duplicate boot-wait-msg definition
A boot-wait-msg definition was overlapped.
----------------
error: bind count is out of range.(bind count<=10)
The number of bind-target definition count(bind count) was defined 10 or more. Please reduce the bind-target definition count less
than 10.
----------------
error: boot-wait-time value is out of range. (0/180 - 86400): %d
The value of boot-wait-time indicated in %d is exceeded. Input the value of boot-wait-time within the range from 0 or 180 to

62
86400.
----------------
error: boot-wait-interval value is out of range. (1 - 60): %d
The value of boot-wait-interval indicated in %d is exceeded. Input the value of boot-wait-inerval within the range from 1 to 60.
----------------
error: WWN binds more than one target: 0x%08x%08x
A WWW bind definitions was overlapped. Please review the setting.
----------------
error: DID binds more than one target: 0x%x
A DID bind definitions was overlapped. Please review the setting.
----------------
error: duplicate Target_ID definition: %d
A Target_ID definitions was overlapped. Please review the setting.
----------------
error: duplicate boot_function definition
A boot_function definition was overlapped. Please review the setting.
----------------
fc_hbaprp: WWN binds more than one target
The specified target (WWN) has already been in another target_id. Please confirm the definition that has been registered.
----------------
fc_hbaprp: DID binds more than one target
The specified target (DID) has already been in another target_id. Please confirm the definition that has been registered.
----------------
fc_hbaprp: bind count is out of range.(bind count<=10)
The number of target bind definitions has already reached the maximum number that can be registered.
----------------
fc_hbaprp: There is invalid parameter in %s
In configuration file “Link-speed”, ”topology”, ” boot-wait-time”, ” boot-wait-inteval”, ” boot-wait-msg”, ”bind-target”, and
“boot-function” are defined more than one. Please confirm configuration file.
----------------
error: bind count is out of range.(bind count<=10)
The number of target bind definitions has already reached the maximum number that can be registered.
----------------
fc_hbaprp: There is no valid parameter in %s.
There was no effective definition in %s file. Please confirm that input file was made by fc_hbaprp -s option?

A.6 ns_show
---------------
Usage: ns_show -n|-c adpname
Usage: ns_show -l adpname domain_area_id
Usage: ns_show -t adpname -a alias
Usage: ns_show -t adpname -p port_name

63
Usage: ns_show -t adpname -i port_id

An invalid parameter was specified. Check that the parameter entry is defined correctly and execute the command again.
------------------
ns_show: %s: A query to Fabric controller(LSTS) failed on fjpfca#%d
An inquiry from the Fibre Channel to the name server was failed. In the environment without the Fabric devices, disregard this
error message. In the environment with the Fabric devices, it is likely that the error in the connection with the Fabric device, or
that the Fabric device does not work.
------------------
ns_show: %s: Name server lookup(XXX_XX) failed on fjpfca#%d
An inquiry from the Fibre Channel to the name server was failed. In the environment without the Fabric devices, disregard this
error message. In the environment with the Fabric devices, it is likely that the error in the connection with the Fabric device, or
that the Fabric device does not work.

64
Appendix B Conversion Table of Target IDs and
AL_PAs
Target ID AL_PA Target ID AL_PA Target ID AL_PA Target ID AL_PA
0 EF 32 B2 64 72 96 3A
1 E8 33 B1 65 71 97 39
2 E4 34 AE 66 6E 98 36
3 E2 35 AD 67 6D 99 35
4 E1 36 AC 68 6C 100 34
5 E0 37 AB 69 6B 101 33
6 DC 38 AA 70 6A 102 32
7 DA 39 A9 71 69 103 31
8 D9 40 A7 72 67 104 2E
9 D6 41 A6 73 66 105 2D
10 D5 42 A5 74 65 106 2C
11 D4 43 A3 75 63 107 2B
12 D3 44 9F 76 5C 108 2A
13 D2 45 9E 77 5A 109 29
14 D1 46 9D 78 59 110 27
15 CE 47 9B 79 56 111 26
16 CD 48 98 80 55 112 25
17 CC 49 97 81 54 113 23
18 CB 50 90 82 53 114 1F
19 CA 51 8F 83 52 115 1E
20 C9 52 88 84 51 116 1D
21 C7 53 84 85 4E 117 1B
22 C6 54 82 86 4D 118 18
23 C5 55 81 87 4C 119 17
24 C3 56 80 88 4B 120 10
25 BC 57 7C 89 4A 121 0F
26 BA 58 7A 90 49 122 08
27 B9 59 79 91 47 123 04
28 B6 60 76 92 46 124 02
29 B5 61 75 93 45 125 01
30 B4 62 74 94 43
31 B3 63 73 95 3C

65
66
Appendix C How to examine instance name and i
nstalling slot
When the following means can be executed, the instance name and the installing slot of adapter can be confirmed even by these
methods. The instance number corresponds to one port on the fibre channel card. For 2 port 4Gbps fibre channel
card(SE0X7F12X), this command can confirm the port position corresponding to the instance name.
1. Method to confirm by cable operation
To identify the instance name of the adaptor, see the message displayed on the console screen when one of the following
connectors is plugged or unplugged from the switch.
- Loop back connector (appended to the fibre channel card)
- Optical cable connector connected with a fibre channel switch
The following messages are output to the console screen respectively by pulling out or inserting the optical cable
or loop back connector.
- In disconnecting
WARNING: /pci@1d,2000/fibre-channel@1 (fjpfca0):
Link Failure : Cable Problem?
- In connecting
fjpfca0: INFO : NPORT link up (connected fabric. id=0x11000)
*If the reverse connector cannot be linked up, please identify the instance name of the adaptor from the message
when disconnecting the cable.
fjpfcaX (X is 0,1,2,...), included in the above messages, is the instance name of the adaptor. This instance name never
changes even if another adaptor is added or deleted, and the driver is updated (or reinstallation, etc.). The instance name
must be checked for all the adaptor mounted on the main device by following the above instruction.
2. Method of using fc_adm command
LED of the adaptor specified by the instance name can be blinked by using the fc_adm command. Please refer to 3.4
fc_adm for details. In 2 port 4Gbps fibre channel card the link LED of the port corresponding to the instance can be
blinked. Please refer to fc_adm command for details.

67
68
Appendix D Property list of fjpfca.conf file
The property list of the environment definition file is shown.

Parameter Toporogy
properties default
which can be HUB Explanation Definition example
(*1) value Fabric
set NL_port

It starts from
The alias can be
the alphabet,
specified for the
and alphabet alias=
fcp-bind-target
(A-Z,a-z), optional "TARGET_A:0x100000000e
Unnecessar property by defining
alias None figure (0-9), a24001",
y(*2) the alias of WWN of
and sign ( _ , "TARGET_B:0x100000000ea
the other party
- , # ). 16 24002";
device instead of
characters or
WWN.
less.

Unnecessar
Required The port type on the
y for
for adaptor is fixed to
topology
topology the set
(*2)
point.(Default is
distinguished
automatically. )Whe
n Fabric is
connected with the
adaptor, "nport" is
specified. When
HUB is connected
with the adaptor,
setting this property
is unnecessary. It is
also possible to
specify "loop". The
nport, link speed property
is only valid when
loop, you use the Fibre port=
Automatic Channel card
port sp1, "fjpfca0:nport:ps2",
distinction (PW008FC2/PW008 "fjpfca1:loop";
sp2, FC3/SE0X7F11X/S
Required for link
sp4 E0X7F12X).
speed.(*3)
If you specify
(It sets it responding to
"sp1", the link speed
the environment)
is fixed to 1Gbps.
If you specify
"sp2", the link speed
is fixed to 2Gbps.
If you specify
“sp4”,the link speed
is fixed to 4Gbps.
It becomes an
automatic
distinction at the
time port type , the
link speed unsetting.

fcp-bind-t WWN or alias Unnecessa Adapter and WWN fcp-bind-target=


None required of the target binds to "fjpfca0t0:0x260000000ea60
arget name ry(*2)
target ID at the 001",

69
Fabric connection. "fjpfca0t1:TARGET_A";
They sets and are
unnecessary for
FC-AL.
255(The When it is necessary
value is to suppress the
compared number of SCSI
Decimal
and the commands (tag)
number of max-throttle=
max-throt small of Please refer to the accepted to the
value within "fjpfca0t0:128",
tle the material of the target. connected target
the range from "fjpfca0t1:240";
notificatio device at the same
1 to 255
n of the time to 255 or less,
other this property is set.
party. ) Each target is set.

When it is necessary
to suppress the
number of SCSI
commands (tag)
accepted by target
device at the same
time to 255 or less,
Decimal set this property.
number of
max-throt Please refer to the max-throttle-all=40;
30 value within When the value is
tle-all material of the target.
the range from set to 0 (initial
1 to 255 value), the limitation
does not work.
When this property
and max-throttle are
set at the same time,
this property is
ignored.

When 1 is set, the


function that the
fjpfca driver
recognizes the target
device connected
with the adaptor
fcp-auto- automatically is
bind-func None 0,1 - made effective. fcp-auto-bind-function=1;
tion
When 0 is set or
undefined, the
automatic
recognition function
of the target device
is ineffective.

failover_f The target blockage


unction function to refuse
None 0,1 - failover_function=1;
the I/O demand
issued to the

70
target concerned
device by a sd driver
when becoming
inaccessible for a
long time to the
target device
because of fatal
error.
When 1 is set,
failover function
mode is enable.
When 0 is set,
failover function
mode is disable
*1: Each property is specifiable only by one. Please refer to the definition example.
*2: It is also possible to set this parameter.
*3: The automatic setting of the link speed is an easy valuing of connectability. Therefore, it is likely not to become a maximum
speed that transfer rate expects according to the connection. Please set the highest speed in consideration of the environment.

71
72
Appendix E About the transmission route confirma
tion method when some fibre channel cards are in
stalled
E.1 Outline
When the alternate path to the I/O device is made by using two fibre channel cards (GP7B8FC1, PW008FC2 or PW008FC3), the
method of confirming the transmission route between each fibre channel card and the I/O device is described.
In this appendix, the following compositions are required.
· Fibre channel card: FUJITSU PCI Fibre Channel GP7B8FC1/PW008FC2/PW008FC3/SE0X7F11X/SE0X7F12X
· Fibre Channel switch: ETERNUS SN200 series
· Connected topology: Fabric connection (switch composition)

E.1.1 Necessity of confirmation


The following problems might occur when the cable which is connected with the physical position is mistake or fibre channel
card's OS instance name is invalid.
The fibre channel switches transmit zoning information in the cascade connection,
· The reliability of the system decreases.
All I/O connections are downed due to the cascade connection failed or the breakdown of either one fibre channel switch.
· Data transfer performance deterioration
You should not use cascade connection as I/O data transmission. If you use it as I/O transmission, transfer performance
deterioration or communication error might be occur.

E.1.2 Point to be checked


The transmission route of the I/O device adaptor is confirmed in following 1.-3.
1. Driver instance name - Confirmation of mounting position
2. The switch's port at the connection destination of each fibre channel instance is confirmed.
3. Target device bindings and the route of each instance are confirmed.
In result, if you find some mistakes in cable connection or binding target setting, please refine it.
As for the confirm method, explains it in E.2.

E.2 Detail
The I/O device is defined by the driver instance name and the combination of Target device side adaptor's WWN.
At this time, there is a possibility to be connected by a route different from connected route assumed like the example shown in
Figure 1 when the correspondence of the driver instance name is mistaken.

73
In this example, the systems designer was assuming Figure 1(a).but actually result in Figure 1(b). The transmission route between
adaptors 0 and fjpfca0 passes the cascade connection between fibre channel switches.

E.3 Validity confirmation of transmission route


It explains the method of confirming connected route by using host's fibre channel driver's utility command.
The following information is gathered on the host.
1. Collection of host fibre channel card's port ID per driver instance (fc_info -a)
2. Collection of I/O device port ID (fc_info -p)
The validity of connected route is judged as a result because of the following idea.
1. Port ID does the following composition.
ex: In case of Port ID=0x011102
01 11 02
domain number area number port number

74
2. When SN200 series is used, the domain number becomes a peculiar number to each connected switch.

Therefore, the communication route can be understood by comparing the domain numbers of Port ID of each instance of the fibre
channel driver and the I/O device side adaptor.
same domain ID connect with same switch No problem
connect with different switch
different domain ID No Good
->using cascade connection

E.3.1 Collection and comparison of Port ID


It explains here as an example of the system to which the connection is actually done by mistake.
1. Collection of port ID of fibre channel driver's instance
The "su"command is executed and it becomes a super user authority. Next, the "fc_info -a" command is executed.
# /usr/sbin/FJSVpfca/fc_info -a
adapter=fjpfca#0wwn=100000000e2446a6 link_status=up port_id=0x21400
own_port=N other_port=F e_d_tov=2000ms r_a_tov=4000ms
bb_credit=0x10 bb_frame_size=2048byte
adapter=fjpfca#1wwn=100000000e2446a4 link_status=up port_id=0x11400
own_port=N other_port=F e_d_tov=2000ms r_a_tov=4000ms
bb_credit=0x10 bb_frame_size=2048byte
Port ID of each driver instance is output like above. It is shown that 0x is a hexadecimal number display. At this time, 0 is
supplemented to the head when five digits since 0x. In this example, 0 is supplemented respectively (021400, 011400)
and two head digits are assumed to be a reading domain number. The domain number of fjpfca0 is 0x02 and the domain
number of fjpfca1 is 0x01.
2. Port ID collection of I/O device side adaptor
The fc_info -p command is executed.
# /usr/sbin/FJSVpfca/fc_info -p
adapter=fjpfca#0 :
port_id=0x012100 tid=16 wwn=210000e000a80093 adapter=fjpfca#0 connected class=class3
adapter=fjpfca#1 :
port_id=0x021200 tid=16 wwn=230000e000a80093 adapter=fjpfca#1 connected class=class3#
From the command output result, the domain number of the I/O device adaptor becomes 0x01 at the destination of fjpfca0.
And the domain number of I/O device adaptor becomes 0x02 at the destination of fjpfca1.
3. Comparison of domain numbers
The validity of connected route is judged from the result of 1 and 2.
fjpfca0 - Route of I/O device confirmation.
the domain number of the domain number of I/O
Is domain number same?
driver instance device adaptor
Incorrect -> some trouble in driver setting or
02 01
connected route

75
fjpfca1 - Route of I/O device confirmation
domain number of driver domain number of I/O device
Is domain number same?
instance adaptor
Incorrect -> some trouble in driver setting or
01 02
connected route

When there is a problem in connected route, please edit the driver setting or correct the cable connection.

E.3.2 Validity confirmation method used by fc_checkc command.


The fc_checkc command displays connected composition between HOST and the fibre channel switch target device. The model
name, WWN, port_id, fjpfcaX and connected target device information can be confirmed from the command output result.

Figure 4 and Figure 5 is shown as example of the incorrect connection.

Fig 4. Example of incorrect connection.

76
Fig 5: Example of fc_checkc command result.

The validity of the connection is judged from the result of fc_checkc.


Instance name of Fabric name of the HBA Fabric name of the target device Match the fabric name?
HBA connect with. connect with.
fjpfca0 sw02 sw03 Unmatched (No Good)
fjpfca2 sw03 sw02 Unmatched (No Good)

If there is a problem in the connection between HBA and target device, please modify the driver configuration file or please
review cabling.

77