Fujitsu ULTRA LVD SCSI Host Bus Adapter User manual

C120-E285-10ENZ2
FUJITSU ULTRA LVD SCSI Host Bus Adapter
Driver 3.0 User’s Guide
- for Oracle Solaris -

Preface
i
Preface
Purpose
This guide provides information about FUJITSU ULTRA LVD SCSI Host Bus Adapter Driver (fjulsa
driver).
Intended Readers
This guide is intended for following persons:
System administrators who use low voltage differential (LVD) SCSI devices with the
Ultra320 SCSI card (SE0X7SC1X, SE0X7SC2X) and SAS devices with the SAS card
(SE0X7SA1X).
Readers of the guide must have a general knowledge of Solaris system administration.
Organization
This manual is organized as follows:
Chapter1: Overview
This chapter contains specifications for Ultra320 SCSI/SAS card.
Chapter2: Configuration
This chapter explains how to set configuration information.
Chapter3: Troubleshooting
This chapter explains how to deal with problems.
Appendix A Messages
The appendix lists messages displayed by the driver.
Appendix B PCI slot number and device name
The appendix shows correspondence between PCI slot number and device name.
Scope The extent of procedures in this guide is to enable SCSI to recognize connected SCSI devices.
For instructions on formatting (writing a disk label and defining a partition) after
recognition of such a device, refer to the manuals supplied with the device and the standard
manual for Solaris.
Notation
The following notations are used in this manual:
"Oracle Solaris 10" is indicated as "Solaris 10."
"Oracle Solaris" is indicated as "Solaris OS."
The bold letter has described the actual command input.
#cd /cdrom/cdrom0/s0/Solaris10/Tools <Return>
Trademark Acknowledgements
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.

Preface
ii
FUJITSU LIMITED
October 2011
7th Edition: October 2011
Attention
●The contents of this manual shall not be disclosed in any way or reproduced in any media without the
express written permission of Fujitsu Limited.
●The contents of this manual may be revised without prior notice.
All Rights Reserved, Copyright (C) FUJITSU LIMITED 2007‑2011

Revision History
iii
Revision History
Edition Date Details
1 Feb 1, 2007 First Edition
2 Apr 9, 2007 Add 914572‑01 patch
3 Jun 13, 2007 Add 914572‑02 patch
4 May 16, 2008 Add 914572‑05 patch
5 Sep 2, 2008 Support SAS card(SE0X7SA1X)
Add 914572‑06 patch
6 Jan 8, 2010 Changed the Version 3.0
7 Oct 27, 2011 Support SPARC Enterprise Software DVD

Contents
viii
Contents
Chapter 1 Overview ···················································· 1
1.1 Function Overview···························································· 2
1.2 Hardware Support····························································· 3
1.2.1 Ultra320 SCSI card (SE0X7SC1X, SE0X7SC2X) ································ 3
1.2.2 SAS card (SE0X7SA1X) ····················································· 5
Chapter 2 Configuration ··············································· 6
2.1 Installing the Driver ························································ 7
2.2 Configuring the Driver Software ·············································· 8
2.2.1 disable‑u320 property setting ············································ 8
2.2.2 Property setting for each port ··········································· 8
2.2.3 max‑throttle property setting ············································ 8
2.3 Configuring I/O devices ····················································· 10
2.3.1 Collecting infomation about the devices to be connected ················· 10
2.3.2 Editing the sd.conf ····················································· 10
2.3.3 Editing the ses.conf (File Unit) ········································ 11
2.3.4 Reconfiguring the kernel ················································ 12
2.4 Network Install ····························································· 13
Chapter 3 Troubleshooting············································· 14
Appendix A Messages ···················································· 16
A.1 Warning messages ···························································· 17
A.2 PANIC messages ······························································ 27
A.3 Information messages ························································ 28
Appendix B PCI Slot Number and Device Name ····························· 31

Chapter 1 Overview
1
Chapter 1 Overview
This chapter covers the following:
Functions of Fujitsu ULTRA LVD SCSI Host Bus Adapter Driver 3.0
Specification for the SCSI card supported by Fujitsu ULTRA LVD SCSI Host Bus Adapter
Driver 3.0
Specification for the SAS card supported by Fujitsu ULTRA LVD SCSI Host Bus Adapter
Driver 3.0

Chapter 1 Overview
2
1.1 Function Overview
Fujitsu ULTRA LVD SCSI Host Bus Adapter Driver 3.0 is a SCSI/SAS host bus adapter (HBA)
driver
[Figure 1‑1 Form of SCSI connection]
[Figure 1‑2 Form of SAS connection]

Chapter 1 Overview
3
1.2 Hardware Support
This section describes hardware supported by this software.
1.2.1 Ultra320 SCSI card (SE0X7SC1X, SE0X7SC2X)
To use this adapter, it must be installed in a PCI‑X/PCI‑Express slot in a server. The
adapter has two VHDCI ports for connections to LVD devices.
1.2.1.1 Specifications
Specifications for the adapter are given below.
[Table 11 Ultra320 SCSI specifications]
Interface port Ultra 320 SCSI
SCSI bus width 8 bits or 16 bits
Electrical interface Low voltage differential
Connector type VHDCI 68‑pin
Transfer rate Async mode: Maximum 7MB/s(per SCSI port)
Sync mode: Maximum: 320 MB/s (per SCSI
port)
Maximum Cable Length 12m
Number of SCSI devices Up to 14 (per SCSI port)
Multi‑Initiator Support
Number of Initiator Maximum:2(per SCSI port)
[Table 12 PCI‑X bus specifications]
Specification compliance PCI‑X 1.0
Bus width 64 bit
Operating clock 133 MHz
Card form Low profile, MD2
Bracket form Standard Bracket
[Table 13 PCI Express specification]
Specification compliance PCI Express
Line speed 2.5Gbps
Number of lane x4
Card form Low profile, MD2
Bracket form Standard Bracket
1.2.1.2 Physical description
Figure 13 and Figure 14 show the top of the Ultra320 SCSI cards. The different parts
together with their features are described below.

Chapter 1 Overview
4
Port A is a LVD SCSI VHDCI connector. FJSV,(e)ulsa@#indicates that it is a SCSI bus.
Port B is a LVD SCSI VHDCI connector. FJSV,(e)ulsa@#,1indicates that it is a SCSI bus.
(#is a variable representing the PCI slot location of this card.)
[Figure 13 Top view of the Ultra320 SCSI card (SE0X7SC1X)]
[Figure 14 Top view of the Ultra320 SCSI card (SE0X7SC2X)]

Chapter 1 Overview
5
1.2.2 SAS card (SE0X7SA1X)
To use this adapter, it must be installed in a PCI Express slot in a server. The adapter
has one SAS x4 port for connections to SAS devices.
1.2.2.1 Specifications
Specifications for the adapter are given below.
[Table 14 SAS specifications]
Interface port Serial Attached SCSI
Transfer rate Max 3.0 Gbps x 4
Medium Interface Specification compliance：SAS‑1.1 (3Gbps)
Connector：SAS x4 connector
Maximum Cable Length Max 6 m
[Table 15 PCI Express specification]
Specification compliance PCI Express
Line speed 2.5Gbps
Number of lane x4
Card form Low profile, MD2
Bracket form Standard Bracket
1.2.2.2 Physical description
Figure 15 show the top of the SAS cards. The different parts together with their features
are described below.
[Figure 15 Top view of the SAS card (SE0X7SA1X)]

Chapter 2 Configuration
6
Chapter 2 Configuration
This chapter explains, the tasks required after installation of this software, so that
SCSI/SAS target driver can recognize devices. Explanations of tasks are given in the
following sequence:
Installing the driver
Configuring the driver software
Configuring I/O devices

Chapter 2 Configuration
7
2.1 Installing the Driver
To use FUJITSU ULTRA LVD SCSI Host Bus Adapter Driver 3.0, install the package stored on
the SPARC Enterprise Software DVD. For the installation procedure, refer to the
Installation Guide –FUJITSU ULTRA LVD SCSI Host Bus Adapter Driver 3.0.

Chapter 2 Configuration
8
2.2 Configuring the Driver Software
The section describes the settings required for the driver software.
2.2.1 disable‑u320 property setting
The disable‑u320 property setting must be configured as shown below in the fjulsa driver
definition file. Adding the following line to the /platform/{sun4v￨SUNW,SPARC‑Enterprise}
/kernel/drv/fjulsa.conf file makes the disable‑u320 property effective:
disable‑u320=0x1:
2.2.2 Property setting for each port
When the properties in the fjulsa driver definition file (/platform/{sun4v￨
SUNW,SPARC‑Enterprise}/kernel/drv/fjulsa.conf) are set according to explanations in
Section 2.2.1, the property setting are applied to each port of all Ultra320 SCSI/SAS cards
mounted in the server.
To make the properties valid only for a specific port of a specific SCSI/SAS card, define
the properties as follows:
name=drivername
parent=/pci@##,####
unit‑address=#
The name of the adapter driver corresponding to the SCSI/SAS card is defined in drivername
of the name property. Specify fjulsa for the Ultra320 SCSI/SAS card.
The parent node of the SCSI/SAS card as named in a device name is defined in /pci@##,####
of the parent property. For example, if a device name shows that the SCSI/SAS card port
is /pci@1d,4000/FJSV,(e)ulsa@3, specify /pci@1d,4000.
The device number of the SCSI/SAS card in the device name is specified for # of the
unit‑address property. For example, if a device name shows that the SCSI/SAS card port
is /pci@1d,4000/FJSV(e)ulsa@3, specify 3 immediately following
FJSV,(e)ulsa@.
In the following example, the disable‑u320 is set to 0x1 for the port of an Ultra320 SCSI/SAS
card indicated as /pci@1d,4000/FJSV,(e)ulsa@3in a device name:
name=fjulsa
parent=/pci@1d,4000
unit‑address=3
disable‑u320=0x1;
2.2.3 max‑throttle property setting
Some device such as disk drives can accept requests for multiple data transfers at the
same time. However, when the number of data transfer requests accepted by such a device
reaches the maximum number for the device, its queue becomes full, and the SCSI/SAS HBA
driver is notified of this status so that no more requests are sent from the driver.
Therefore, processing for data transfer requests is temporarily interrupted occasionally,
and data transfer efficiency decreases as a result.
The max‑throttle property of the fjulsa driver has been prepared as a means of preventing
this problem. By setting the max‑throttle property to a value below the maximum number
of data transfer requests that a device can handle concurrently, the number of data transfer
requests issued at the same time to the device is limited and a queue‑full state can be

Chapter 2 Configuration
9
prevented.
Adding the following line to the /platform/{sun4v￨SUNW,SPARC‑Enterprise}/kernel/drv/
fjulsa.conf file makes the max‑throttle property effective:
max‑throttle=##;
(##: Number of data transfer requests that can be issued at the same time)
Moreover, the target#‑max‑throttle property (# is SCSI ID) can be set to limit the number
of data transfer request issued to a device with a specific SCSI ID.
Adding the following line to the /platform/{sun4v￨SUNW,SPARC‑Enterprise}/kernel/drv
/fjulsa.conf file makes the target#‑max‑throttle property effective:
target#‑max‑throttle=##;
(#:SCSI ID, ##: Number of data transfer requests which can be issued at the same time)
In the following example, the number of data transfer requests that can be issued at the
same time to a device with SCSI ID=1 is limited to 128:
target1‑max‑throttle=128;
For information on the maximum number of data transfer requests that a device can handle
concurrently, refer to the manual of the device.
For the changes in fjulsa.conf to take effect in the kernel, reboot the machine as follows
2.3.4 Reconfiguring the kernel.

Chapter 2 Configuration
10
2.3 Configuring I/O devices
This section describes the tasks required to enable the SCSI/SAS target driver to identify
disk devices. In the explanation here, these tasks are discussed based on the assumption
that the sd driver (SCSI disk driver) is used.
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.3.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
Logical unit (LU: Logical Unit) number included with each device
WWID of HBA (SAS)
Information on the device with which the server for the installation is connected by
executing "probe‑scsi‑all" on OBP can be confirmed.
{0} ok probe‑scsi‑all
/pci@7,700000/FJSV,eulsa@0
MPT Version : 01.05 , Firmware Version : 01.24.00.00
SAS World Wide ID(HBA:Port0) is 0x500605b0 003cf854
Target 0x1c
Unit 0x0 Disk FUJITSU E2000 0000 2097152 Blocks, 1073 MB
Unit 0x1 Disk FUJITSU E2000 0000 2097152 Blocks, 1073 MB
:
2.3.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
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

Chapter 2 Configuration
11
(#) is a comment line.
For example, if a disk 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.3.3 Editing the ses.conf (File Unit)
The definition file for the ses driver is /kernel/drv/ses.conf add the collected
information to this file. ses.conf contains several default settings.
A definition begins with name=ses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 the File Unit is configured with SES Controller target ID 32 and has one
logical unit 0, edit ses.conf as follows:
#
# Copyright 2003 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#
#ident "@(#)ses.conf 1.11 03/10/23 SMI"
#
name="ses" class="scsi" target=0 lun=0;
name="ses" class="scsi" target=1 lun=0;
name="ses" class="scsi" target=2 lun=0;
…

Chapter 2 Configuration
12
name="ses" class="scsi" target=32 lun=0;
2.3.4 Reconfiguring the kernel
For the changes in sd.conf to take effect in the kernel, reboot the machine as follows:
# touch /reconfigure
# /usr/sbin/shutdown –i6 –g0 ‑y
The sd driver can now recognize the SCSI devices. Use the format 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.

Chapter 2 Configuration
13
2.4 Network Install
When you install the driver in the server connected to this SCSI/SAS card with an
installation server. Please refer to the following manual when the target machine of the
network installation is SPARC Enterprise.
・Install Server Build Guide I/O device driver (SPARC Enterprise)

Chapter 3 Troubleshooting
14
Chapter 3 Troubleshooting
Check the following if a problem occurs.

Chapter 3 Troubleshooting
15
■ Has the driver been installed?
Enter pkginfo –x FJSV,(e)ulsa and if nothing is displayed, the driver has not been installed.
Install the driver from the SPARC Enterprise Software DVD. For Ultra320 SCSI/SAS on a 32‑bit
kernel, install the FJSV,(e)ulsa package, and for a 64‑bit kernel, install the FJSV,(e)ulsa
packages; otherwise, the fjulsa driver does not operate property.
■ Does the SCSI device have a valid operating status and correct configuration?
If you cannot see the name of the device that you want to use, it may be off, its SCSI
ID or logical unit number may be wrong, the device configuration in the SCSI/SAS target
driver (such as in sd.conf) may be wrong, or device definitions are not yet valid in the
kernel. Check the status of the device, its configuration, and the SCSI/SAS target driver
configuration. Changes in a device configuration do not become valid until the device is
turned off and then on again. If a device is not correctly identified even though its
configuration is correct, turn the device off and then on again.
■ Does the SCSI bus have duplicate SCSI IDs?
If the Initiator ID and SCSI ID for a device are the same on a SCSI bus, correct SCSI bus
operation is not possible.
In this event, check the Initiator ID and SCSI ID of the device. Methods of identifying
the current Initiator ID are shown below.
Checking the OBP configuration
ok> printenv scsi‑initiator‑id
scsi‑initiator‑id= 7
ok>
Checking the /var/adm/messages file
1. Search for initiator SCSI ID now in the /var/adm/messages file.
2. If you find the following messages, the Initiator ID was changed from 7 to 6:
unix: /pci@##,####/FJSV,(e)ulsa@# (fjulsa#): (*1)
initiator SCSI ID now 6
*1:# is decimal number or hexadecimal number.
3. If you cannot find messages similar to the above messages, the Initiator ID is
7, which is the default Initiator ID.
If different IDs are found with the methods, the result of checking the messages file takes
priority.
The software and hardware requirements describe below must be met for use of this software.