sx60-100 - Operating Manual PDF

FibreCAT SX Series
Operating Manual
Edition August 2009 (Version 3.1, 2009-08-24)

Comments… Suggestions… Corrections…
The User Documentation Department would like to know your
opinion on this manual. Your feedback helps us to optimize our
documentation to suit your individual needs.
Feel free to send us your comments by e-mail to:
manuals@ts.fujtsu.com
Certified documentation
according to DIN EN ISO 9001:2000
To ensure a consistently high quality standard and
user-friendliness, this documentation was created to
meet the regulations of a quality management system which
complies with the requirements of the standard
DIN EN ISO 9001:2000.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks

Copyright © Fujitsu Technology Solutions GmbH 2009.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
This manual is printed

on paper treated with
chlorine-free bleach.
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Management Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.1 FibreCAT SX Manager Web-Based Interface . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 FibreCAT SX Manager Command-Line Interface . . . . . . . . . . . . . . . . . . . . 8
1.3 Target Group of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 Structure of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.7 Installation and Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . 15
2 Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1 Notes on Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.2 Electrostatic-sensitive Component Label . . . . . . . . . . . . . . . . . . . . . . 19
2.3 CE Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4 RFI Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5 Notes on Mounting the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.6 Notes on Transportation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7 Environmental Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.8 Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.8.1 Physical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.8.1.1 Dimension and Weight Specifications . . . . . . . . . . . . . . . . . . . . . . . 22
2.8.1.2 Weight and Placement Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.8.1.3 Ventilation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.8.2 Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
FibreCAT SX Series Operating Manual

Contents
2.8.3 Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.8.3.1 Electrical Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.8.3.2 Site Wiring and Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . 25
2.8.3.3 Cabling Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.8.4 Management Host Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3 Hardware, Operating, and Indicator Components . . . . . . . . . . . . . . . . . . 27
3.1 Controller Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.1.1 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.2 Components and Indicators at the Front Side . . . . . . . . . . . . . . . . . . . . . 28
3.1.3 Ports and Switches at the Back Side . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1.4 Indicators at the Back Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2 Expansion Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.1 Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.2 Components and Indicators at the Front Side . . . . . . . . . . . . . . . . . . . . . 33
3.2.3 Ports and Switches at the Back Side . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.4 Indicators at the Back Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4 Connecting Hosts / Configurations . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.1 Connecting Remote Management Hosts . . . . . . . . . . . . . . . . . . . . . . . 37

4.2 Installing the SCSI Enclosures Services Driver . . . . . . . . . . . . . . . . . . . 37
4.3 Connecting Direct Attached iSCSI Configurations . . . . . . . . . . . . . . . . . 38
4.3.1 Single Controller FibreCAT SX80 iSCSI With One Host . . . . . . . . . . . . . . . . 38
4.4 Host Interface Speed for FibreCAT SX (FC) . . . . . . . . . . . . . . . . . . . . . 39
4.5 Connecting Direct Attached FC Configurations . . . . . . . . . . . . . . . . . . . 41
4.5.1 FibreCAT SX60 / SX80 / SX88 With One Dual Port Host . . . . . . . . . . . . . . . . 42
4.5.2 FibreCAT SX60 / SX80 / SX88 With Two Dual Port Hosts . . . . . . . . . . . . . . . 43
4.5.2.1 Controller Failover Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.5.2.2 Path Failover Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.5.3 FibreCAT SX60 / SX80 / SX88 With Two Dual Port Hosts for High Performance . . . . 46
4.5.4 FibreCAT SX100 With Four Dual-Port Hosts . . . . . . . . . . . . . . . . . . . . . . 47
4.6 Connecting Switch Attached iSCSI Configurations . . . . . . . . . . . . . . . . . 50
4.6.1 FibreCAT SX80 iSCSI With Two Dual Port Hosts and Two Switches . . . . . . . . . . 50

Contents
4.7 Connecting Switch Attached FC Configurations . . . . . . . . . . . . . . . . . . 52

4.7.1 FibreCAT SX60 / SX80 / SX88 With One Switch and One Dual Port Host . . . . . . . 52
4.7.2 FibreCAT SX60 / SX80 / SX88 With Two Switches and One Dual Port Host . . . . . 54
4.7.2.1 Configuration Rules for VMware ESX Server 3.0.0 and 3.0.1 . . . . . . . . . . . 55
4.7.3 FibreCAT SX60 / SX80 / SX88 With Two Switches and Two Dual Port Hosts . . . . . 56
4.7.4 FibreCAT SX100 With One Switch and Two Dual-Port Hosts . . . . . . . . . . . . . 58
4.8 Supported HBAs for Solaris (SPARC) . . . . . . . . . . . . . . . . . . . . . . . . 59
5 Installing Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.2 Unpacking an Enclosure and Verifying its Contents . . . . . . . . . . . . . . . . 62
5.3 Preparing the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.4 Installing an Enclosure in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.4.1 Rack-Mount Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.4.2 Rack Mounting Position Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.4.3 Mounting Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.5 Connecting Controller and Expansion Enclosures . . . . . . . . . . . . . . . . . 69
5.6 Connecting the AC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.7 Testing the Enclosure Connections . . . . . . . . . . . . . . . . . . . . . . . . . 72
6 Configuring a System for the First Time . . . . . . . . . . . . . . . . . . . . . . 73
6.1 Setting the IP Address Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . 73

6.2 FibreCAT SX Manager Web-Based Interface . . . . . . . . . . . . . . . . . . . . 76
6.2.1 Configuring Your Web Browser for the WBI . . . . . . . . . . . . . . . . . . . . . . 76
6.2.2 Logging In to WBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.2.3 Setting Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.3 Driver Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.4 Configuring Controller Enclosure Host Ports (FC) . . . . . . . . . . . . . . . . . 78
6.5 Configuring the Microsoft iSCSI Software Initiator (iSCSI) . . . . . . . . . . . . 78
6.6 Editing Registry Timeout Values for iSCSI Initiator . . . . . . . . . . . . . . . . 80
6.7 Install Native MPIO Functionality Under Windows 2008 for FibreCAT SX . . . . 81
6.8 Installing a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Contents
6.9 Creating Virtual Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.10 Volume Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.11 Testing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.12 Logging Out of the WBI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.13 Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7 Powering the System Off and On . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1 Powering Off the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.2 Powering On the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Glossary and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Related Documents and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

1 Introduction
This guide describes how to install, initially configure and operate FibreCAT® SX series
storage system, and applies to the following models:
● FibreCAT SX60 Fibre Channel (FC) Controller Enclosure
● FibreCAT SX80 iSCSI Controller Enclosure
● FibreCAT SX Serial Attached SCSI (SAS) Expansion Enclosure
This guide does not apply to the FibreCAT SX40 model which is covered by separate
documents.
If there are no differences between the five controller enclosure models, from now on they
together are referred to as FibreCAT SX controller enclosure.
1.1 Product Overview

FibreCAT SX storage systems are high-performance storage solutions that combine
outstanding performance with high reliability, availability, flexibility, and manageability.
FibreCAT SX storage systems are modular, rackmountable, and scalable from a single
controller enclosure configuration to a maximum configuration of eight expansion enclo-
sures behind one controller enclosure.
A controller enclosure can contain two RAID controller modules, which interact and provide
failover capability for the data path. The enclosures can use SAS (with SX80 / SX88 /SX100
only) or SATA disk drives and provides RAID functionality, caching, and disk storage.
The different characteristics of the FibreCAT SX models are itemized in “Technical Data” on
page 11.
The enclosures can be installed in Fujitsu PRIMECENTER racks or in standard 19-inch EIA
racks.
FibreCAT SX Series Operating Manual 7

Management Software Introduction
1.2 Management Software

The embedded management software FibreCAT SX Manager (FSM) includes the tools
outlined in the following topics:
● FibreCAT SX Manager’s Web Based Interface (WBI)
● FibreCAT SX Manager’s Command Line Interface (CLI)
1.2.1 FibreCAT SX Manager Web-Based Interface

The FSM web based interface (WBI) is the primary interface for configuring and managing
FibreCAT SX family arrays. A web server resides in each controller module. WBI enables
you to manage FibreCAT SX family arrays from a web browser that is properly configured
and that can access a controller module through an Ethernet connection.
The WBI also includes monitoring and diagnostic features that enable you to view and
collect information that enhances the reliability, availability, and serviceability (RAS) of
FibreCAT SX family arrays. You can configure the transmission of event notifications
(alerts), which can be sent to the screen or to email addresses, and Simple Network
Management Protocol (SNMP) traps, which can be sent to a host system. Events are
recorded in an event log, which you can view.
Information about using the WBI is in its online help and in the “FibreCAT SX Series Admin-
istrator’s Guide”.
To access the WBI for the first time, each FibreCAT SX controller module has a default IP
address (IP 10.0.0.1 and Subnet Mask 255.255.255.0). It can be used if the IP address
setting via CLI (see “Setting the IP Address Using the CLI” on page 73) can not be
performed, e. g. the appropriate serial cable is not on hand.
1.2.2 FibreCAT SX Manager Command-Line Interface

The FSM embedded command line interface (CLI) enables you to configure and manage
an array using individual commands or command scripts through an out-of-band RS-232 or
Ethernet connection.
NOTE
i As first time configuration of a FibreCAT SX controller enclosure the IP addresses
of its RAID controller(s) is/are to be set. This step can only be performed by using
the CLI through a RS-232 connection, which you will do in “Setting the IP Address
Using the CLI” on page 73.
All subsequent usage of the CLI can be performed with a terminal emulation
through an Ethernet connection.
Information about using the CLI is in the “FibreCAT SX Manager Command Line Interface
(CLI)” manual.
8 FibreCAT SX Series Operating Manual

Introduction Target Group of the Manual
1.3 Target Group of the Manual

The operating instructions are intended for the person responsible for installing the
hardware and correctly operating the system. The operating instructions contain all the
descriptions which are of importance for commissioning your FibreCAT SX storage system
in so far as they do not form part of the publication of your server system.
To understand the different expansion options it is necessary to have a knowledge of
hardware and data transmission, as well as basic knowledge of the operating system used.
1.4 Structure of the Manual

This manual consists of the following chapters:
● Important Notes
This chapter contains instructions on the safe operation of your storage system as well
as information about environmental protection and site requirements.
● Hardware, Operating, and Indicator Components
This chapter gives a detailed description of the main hardware components and the
position and meaning of the operating and indicator elements.
● Connecting Hosts / Configurations
This chapter shows some typical configurations.
● Installing Enclosures
This chapter describes the process of installing FibreCAT SX enclosures in a
PRIMECENTER rack or in a standard 19-inch EIA rack cabinet, cable a controller
enclosure to expansion enclosures, and describes how to connect the power cords and
how to test the connections.
● Connecting Hosts (FC)
This chapter describes the FibreCAT SX system cable connections to hosts for several
different configurations.
● Configuring a System for the First Time
This chapter describes how to use the CLI and the WBI of the FibreCAT SX Manager
to perform first-time configuration. The chapter also gives an overview about the
needed driver settings and describes how to perform basic storage configuration to
verify that your system is working.
● Powering the System Off and On
This chapter describes how to power off and power on the system when needed.

Notational Conventions Introduction
1.5 Notational Conventions

Italics Commands, options, file names and path names are written in italic letters
in continuous text.
fixed font Commands and options in syntax descriptions as well as system output
are written in a fixed font.
<variable> Angle brackets are used to enclose variables which are to be replaced by
actual values.
semi-bold Highlights text
“Quotation marks” References to documents and chapters or sections in this or other documents
I NOTE Important information and tips
V CAUTION Reference to hazards that can lead to personal injury, loss of data or
damage to equipment
Table 1: Typographic Conventions

Introduction Technical Data
1.6 Technical Data

FibreCAT
General Specifications
SX60 SX80 / SX88 SX100 SX80 iSCSI
Type 4 Gbit/s 1 Gbit/s
storage system storage system
Rack space 2U / enclosure
Number of hard disk drives max. 12 / enclosure
Supported operating systems Windows 2003 R2, Windows 2008
Red Hat 4.x and 5.x
SuSE SLES 9 and 10
VMware ESX VMware ESX VMware ESX
2.53 and 3.x 3.x 3.0, 3.0.1, 3.0.2
SPARC Solaris SPARC Solaris
--- ---
9 and 10 10
Number of power supplies 2 / enclosure
hot plug and with full redundancy
Controller cache memory
512 MByte 1 GByte
per RAID controller
FibreCAP per RAID controller 1
Number of
– FC ports with SFP transceiver
(Small Form-factor Pluggable)
2 4 2
– or RJ45 Ethernet ports
(for iSCSI
per RAID controller
Number of snapshots (default) 4
Number of snapshots (with license) 16 32 244 32
Max. number of expansion enclo-
1 4 8 4
sures per controller enclosure
Table 2: General Specifications

Technical Data Introduction
FibreCAT
Hard Disk Drives
Gross capacity1 500 GByte
SATA II 7200 rpm2 HDD 750 GByte
1 TByte
Gross capacity1
146 GByte
SAS1 15000 rpm2 HDD
— 300 GByte
(available for SX80 / SX88 /
450 GByte
SX 100 only)
Access time
11ms / 12ms (read / write)
with SATA II HDDs
Access time with SAS HDD — 4ms / 5ms (read / write
Total capacity including the max. 24 TByte 56 TByte 108 TByte 56 TByte
number of expansion enclosures (24 x 1 TByte) (56 x 1 TByte) (108 x 1 TByte) (56 x 1 TByte)
Table 3: Hard Disk Drives
1
mixing with SATA HDDs possible
Supported RAID Levels

RAID 0 Data Striping about several hard disk drives (HDDs)
RAID 1 Mirrored HDDs
RAID 10 Data mirroring, then Striping of the data over servers’ HDDs
RAID 3 Data Striping with dedicated parity HDD
RAID 5 Data Striping with distributed parity
RAID 50 RAID 5 arrays, Striped again over all drives
RAID 6 Data Striping with double parity
Table 4: Supported RAID Levels

Introduction Technical Data
Management
Diagnostics of non-data Signalling and monitoring via SES (SCSI enclosure services) protocol and
characteristics LEDs
Management interfaces RS232 (mini-DB9)
10/100 Ethernet (RJ45)
Supported protocol SNMP
Administration FibreCAT SX Manager (FSM) with web based interface (WBI)
and command line interface (CLI)
Table 5: Management
FibreCAT
Options
HDDs Hot plug HDDs (SATA and SAS, mixing possible)
RAID controller 2nd RAID controller
Max. number of expansion enclo-
1 4 8 4
sures per controller enclosure
Table 6: Options
Electrical Values per Enclosure (Maximum Values)

Power supply 2 hot-plug redundant modules with 1 fan integrated each
Apparent power 600 W (230 V AC, 50 Hz)
Max. electric current 2.61 A (230 V AC, 50 Hz)
Continuous load 535 W
Max. real ower 572 W (230 V AC, 50 Hz)
Power factor 0.953 (230 V AC, 50 Hz)
Peak load 650 W
Rated voltage 115 V – 240 V
Rated frequency 50 HZ – 60 Hz
Table 7: Electrical Values per Enclosure

Technical Data Introduction
Ambient Conditions (DIN EN 60721-3-X)

Operating temperature 5°C up to 40°C (IEC 721)
Non operating temperature -40°C to 70°C
Relative humidity 10% – 90% (non condensing)
Table 8: Ambient Conditions
Heat Dissipation per Enclosure

Max. heat dissipation 1926 kJ/j
Table 9: Heat Dissipation per Enclosure
Dimensions per Enclosure

Rack space (H x W x D)
H 3,45 Inch / 8,75 cm (2 U)
W 17,56 Inch / 44,60 cm
D 22,5 Inch / 57,15 cm
Weight max. 33.6 kg (dependent on configuration level)
Table 10: Dimensions per Enclosure
Compliance with Standards

Product safety UL listet, cUL, CE, CSA-C22.2, EN 60950-2000,
IEC 60950, GS, GOST, S-Mark
Approval GS, CSAUS/C, CB-certificate
Electromagnetic compatibility FCC Part 15 Class B, ICES-003, EN 300-386,
EN 55022 Class B, VCCI Class B, AS/NZS 3548 Class B,
BMSI Class B
Vibrations EN 61000-3, EN 61000-3-3
Immunity EN 300-386, EN 55024
CE certification EU Directive: 89/336/EWG (EMV);
EN61000-3-2;
EN 6100-3-3 73/23/EWG (Product security)
Environmental compliance RoHS compliant, WEEE compliant
Table 11: Compliance with Standards

Introduction Installation and Configuration Checklist
1.7 Installation and Configuration Checklist

Before you begin to install the system, make sure you have read the Safety manual.
The following table outlines the steps required to install and initially configure the system.
To ensure a successful installation, perform the tasks in the order in which they are
presented.
Step Task
1 Verify the site installation requirements (see page 22)
2 Install the enclosures (see page 61)
3 Cabling the enclosures (see page 69)
4 Connect the power cords (see page 72)
5 Test the enclosure connections (see page 72)
6 Connect the hosts (see page 69)
7 Configure a system for the first time (see page 73
Table 12: Installation and Configuration Checklist

2 Important Notes
2.1 Notes on Safety

In this section you will find information that you must note when using the storage system.
This device complies with the relevant safety standards for IT equipment.
I The following safety notes are also provided in the Safety manual. Also pay
attention to the notes in the operating manual of the connected system.
If you have any questions relating to setting up and operating your system in the
environment where you intend to use it, please contact your sales outlet or our customer
service team.
V CAUTION!
● The actions described in these instructions should only be performed by
technical specialists. Equipment repairs should only be performed by service
personnel. Any unauthorized openings and improper repairs could expose the
user to risks (electric shock, energy hazards, fire hazards) and could also
damage the equipment. Please note that any unauthorized openings of the
device will result in the invalidation of the warranty and exclusion from all liability.
● Transport the device in its original packaging or in other suitable packaging
which will protect it against shock or impact.
● Read the notes on environmental conditions in “Technical Data” on page 11
before setting up and operating the device.
● If the device is brought in from a cold environment, condensation may form both
inside and on the outside of the machine.
● Wait until the device has acclimatized to room temperature and is absolutely dry
before starting it up. Material damage may be caused to the device if this
requirement is not observed.
● Check that the rated voltage specified on the type label is the same as the local
line voltage.

Notes on Safety Important Notes
V CAUTION!
● The device must only be connected to a properly grounded wall outlet (the
device is fitted with a tested and approved power cable).
● Make sure that the power sockets on the device and the protective grounded
outlet of the building’s wiring system is freely accessible.
● Switching off the device does not cut off the supply of power. To do this you must
remove the power plugs.
● Before opening the unit, switch off the device and then pull out the power plugs.
● Route the cables in such a way that they do not form a potential hazard (make
sure no-one can trip over them) and that they cannot be damaged. When
connecting up a device, refer to the relevant notes in this manual.
● Never connect or disconnect data transmission lines during a storm (lightning
hazard).
● Systems which comprise a number of cabinets must use a separate fused
socket for each cabinet.
● The servers and the directly connected external storage subsystems should be
connected to the same power supply distributor. Otherwise you run the risk of
losing data if, for example, the central processing unit is still running but the
storage subsystem has failed during a power failure.
● Make sure that no objects (such as bracelets or paper clips) fall into or liquids
spill into the device (risk of electric shock or short circuit).
● In emergencies (e.g. damage to housings, power cords or controls or ingress of
liquids or foreign bodies), immediately power down the device, pull out the
power plugs and notify your service department.
● Note that proper operation of the system (in accordance with IEC 60950/DIN
EN 60950) is guaranteed only if slot covers are installed on all vacant slots
and/or dummies on all vacant bays and the housing cover is fitted (cooling, fire
protection, RFI suppression).

Important Notes Electrostatic-sensitive Component Label
2.2 Electrostatic-sensitive Component Label

Electrostatic-sensitive components may be identified by the following sticker:
You must follow the instructions below when handling modules containing electrostatic-
sensitive components
Ê Discharge static electricity from your body (for example by touching a grounded metal
object) before handling modules containing electrostatic-sensitive components.
Ê The equipment and tools you use must be free of static charge.
Ê Remove the power plug before installing or removing modules containing electrostatic-
sensitive components.
Ê Only hold modules containing electrostatic-sensitive components by their edges.
Ê Do not touch any of the pins or track conductors on a module containing
electrostatic-sensitive components.
Ê Use a grounding strap designed for the purpose, to connect you to the system unit as
you install the modules.
Ê Place all components on a static-safe base.
I An exhaustive description of the handling of modules containing electrostatic-
sensitive components can be found in the relevant European and international
standards (DIN EN 61340-5-1, ANSI/ESD S20.20).
2.3 CE Certificate
The shipped version of this device complies with the requirements of the EEC
directives 89/336/EEC “Electromagnetic compatibility” and 73/23/EEC “Low
voltage directive”. The device therefore qualifies for the CE certificate
(CE=Communauté Européenne).

RFI Suppression Important Notes
2.4 RFI Suppression

All other equipment which is connected to this product must also have radio noise
suppression in accordance with EC Guideline 89/336/EWG.
Products which meet this requirement are accompanied by a certificate to that effect issued
by the manufacturer and/or bear the CE mark. Products which do not meet this requirement
may be operated only with the special permission of the BZT (Bundesamt für Zulassungen
in der Telekommunikation).
I This is a “Class A“ equipment. This equipment may cause harmful interference in
residential areas. In this case, the user may be held liable for taking appropriate
measures and bearing the costs resulting from these measures.
2.5 Notes on Mounting the Rack

● For safety reasons, at least two people are required to install the rack-mounted model
because of its weight and size.
● When connecting and disconnecting cables, observe the notes in the operating manual
of your system and the comments in the “Important Notes” chapter in the technical
manual supplied with the rack.
● Ensure that the anti-tilt bracket is correctly mounted when you set up the rack.
● For safety reasons, no more than one unit may be withdrawn from the rack at any one
time during installation and maintenance work.
● If more than one unit is withdrawn from the rack at any one time, there is a danger that
the rack will tilt forward.
● The power supply to the rack must be installed by an authorized specialist (electrician).
2.6 Notes on Transportation

I Transport the storage subsystem in its original packaging or in other suitable
packaging which will protect it against shock or impact.
Do not unpack it until all transport maneuvers are completed.
If you need to lift or transport the storage system, ask someone to help you.

Important Notes Environmental Protection
2.7 Environmental Protection
Environmentally friendly product design and development

This product has been designed in accordance with standards for “environmentally friendly
product design and development”. This means that the designers have taken into account
important criteria such as durability, selection of materials, emissions, packaging, the ease
with which the product can be dismantled and the extent to which it can be recycled.
This saves resources and thus reduces the harm done to the environment.
Notes on packaging
Please do not throw away the packaging. We recommend that you do not throw away the
original packaging in case you need it later for transporting.
Notes on labeling plastic housing parts
Please avoid attaching your own labels to plastic housing parts wherever possible, since
this makes it difficult to recycle them.
Take-back, recycling and disposal
The device may not be disposed of with household rubbish. This appliance is
labelled in accordance with European Directive 2002/96/EC concerning used
electrical and electronic appliances (WEEE - waste electrical and electronic
equipment).
The guideline determines the framework for the return and recycling of used
appliances as applicable throughout the EU. To return your used device, please
use the return and collection systems available to you. You will find further infor-
mation on this at www.ts.fujitsu.com/recycling.
For details on returning and reuse of devices and consumables within Europe, refer to the
“Returning used devices” manual, or contact your Fujitsu branch office/subsidiary or our
recycling centre in Paderborn:
Fujitsu Technology Solutions GmbH
Recycling Center
D-33106 Paderborn
Tel. +49 5251 8180-10
Fax +49 5251 8180-15

Site Requirements Important Notes
2.8 Site Requirements

This chapter provides requirements and guidelines that you must address when preparing
your site for the installation.
CAUTION
! When selecting an installation site for the system, choose a location that avoids
excessive heat, direct sunlight, dust, or chemical exposure. These conditions
greatly reduce the system’s longevity, and might void your warranty.
2.8.1 Physical Requirements

This section provides dimension and weight specifications, weight and placement guide-
lines, and ventilation requirements.
2.8.1.1 Dimension and Weight Specifications
The floor space at the installation site must be strong enough to support the combined
weight of the rack, controller enclosures, expansion modules, and any additional
equipment. The site should provide sufficient space for installation, operation, and servicing
the enclosures, and also requires sufficient ventilation to allow a free flow of air to all enclo-
sures.
The following table lists enclosure dimensions and weight. Weights are based on an
enclosure having 12 drive modules, 2 controller or expansion modules, and 2 power and
cooling modules installed.
Specification Rackmount
Height 2U 8.76 cm
Width
● Chassis excluding mounting ears 44.6 cm
● Chassis including mounting ears 48.0 cm
Depth
● Chassis 55.37 cm
● To back of power and cooling module handle 57.12 cm
Weight, controller enclosure (12 drives)
● SAS drives 33.1 kg
● SATA drives 33.6 kg
Table 13: Dimension and Weight Specification Examples

Important Notes Site Requirements
Specification Rackmount
Weight, expansion enclosure (12 drives)
● SAS drives 30.8 kg
● SATA drives 31.3 kg
Table 13: Dimension and Weight Specification Examples
2.8.1.2 Weight and Placement Guidelines
As you prepare for installation, follow these guidelines:

● Ideally, use two people to lift an enclosure. However, one person can safely lift an
enclosure if its weight is reduced by removing the power and cooling modules and drive
modules.
● Do not place enclosures in a vertical position. Always install and operate the enclosures
in a horizontal orientation.
● When installing enclosures in a rack, make sure that any surfaces over which you might
move the rack can support the weight. To prevent accidents when moving equipment,
especially on sloped loading docks and up ramps to raised floors, ensure you have a
sufficient number of helpers. Remove obstacles such as cables and other objects from
the floor.
● To prevent the rack from tipping and to minimize personnel injury in the event of a
seismic occurrence, securely anchor the rack to a wall or other rigid structure that is
attached to both the floor and to the ceiling of the room.
2.8.1.3 Ventilation Requirements
As you prepare for installation, follow these requirements:

● Do not block or cover ventilation openings at the front and rear of an enclosure. Never
place an enclosure near a radiator or heating vent. Failure to follow these guidelines can
cause overheating and affect the reliability and warranty of the product.
● Leave a minimum of 15 cm at the front and back of an enclosure to ensure adequate
airflow for cooling. No cooling clearance is required on the sides, top, or bottom of enclo-
sures.
● Leave enough space in front and in back of an enclosure to allow access to enclosure
components for servicing. Removing a component requires a clearance of at least
137 cm in front of and behind the enclosure.

2.8.2 Environmental Requirements

The following table lists the environmental conditions in which the rackmounted controller
enclosure operates.
Specification Range
Altitude To 3 km, derate 2° C for every 1 km up to 3 km
Relative Humidity 10% to 90% RH, 27° C max. wet bulb, non-condensing
Temperature 5° C to 40° C, non-condensing
Shock 3.0 g, 11 ms, half-sine
Vibration 0.15 g (vertical); 0.10 g (horizontal), 5 to 500 Hz, swept-sine
Table 14: Environmental Requirements
2.8.3 Electrical Requirements

This section provides electrical guidelines and site wiring, power, and cabling requirements.
2.8.3.1 Electrical Guidelines
Each enclosure is shipped with two AC power cords that are appropriate for use in a typical
outlet in the destination country. Each power cord should connect one of the power and
cooling modules to an independent, external power source. To ensure power redundancy,
connect the two power cords to two separate circuits; for example, to one commercial circuit
and to one uninterruptable power source (UPS).
Safety status of I/O connections comply with Separated Extra Low Voltage (SELV) require-
ments.

Important Notes Site Requirements
As you prepare for installation, follow these guidelines:

● The enclosures work with single-phase power systems having an earth ground
connection. To reduce the risk of electric shock, do not plug an enclosure into any other
type of power system. Contact your facilities manager or a qualified electrician if you are
not sure what type of power is supplied to your building.
● Enclosures are shipped with a grounding-type (three-wire) power cord. To reduce the
risk of electric shock, always plug the cord into a grounded power outlet.
● Do not use household extension cords with the enclosures. Not all power cords have
the same current ratings. Household extension cords do not have overload protection
and are not meant for use with computer systems.
2.8.3.2 Site Wiring and Power Requirements
Each enclosure has two power and cooling modules for redundancy. If full redundancy is
required, use a separate power source for each module. The AC power supply unit in each
power and cooling module is auto-ranging and is automatically configured to an input
voltage range from 88–264 VAC with an input frequency of 47–63 Hz. The power and
cooling modules meet standard voltage requirements for both U.S. and international
operation. The power and cooling modules use standard industrial wiring with line-to-
neutral or line-to-line power connections.
● All AC mains and supply conductors to power distribution boxes for the rack-mounted
system must be enclosed in a metal conduit or raceway when specified by local,
national, or other applicable government codes and regulations.
● Ensure that the voltage and frequency of your power source match the voltage and
frequency inscribed on the equipment’s electrical rating label.
● To ensure redundancy, provide two separate power sources for the enclosures. These
power sources must be independent of each other, and each must be controlled by a
separate circuit breaker at the power distribution point.
● The system requires voltages within minimum fluctuation. The customer-supplied facil-
ities’ voltage must maintain a voltage with not more than ± 5 percent fluctuation. The
customer facilities must also provide suitable surge protection.
● Site wiring must include an earth ground connection to the AC power source. The
supply conductors and power distribution boxes (or equivalent metal enclosure) must
be grounded at both ends.

● Power circuits and associated circuit breakers must provide sufficient power and
overload protection. To prevent possible damage to the AC power distribution boxes and
other components in the rack, use an external, independent power source that is
isolated from large switching loads (such as air conditioning motors, elevator motors,
and factory loads).
2.8.3.3 Cabling Requirements

● Keep power and interface cables clear of foot traffic. Route cables in locations that
protect the cables from damage.
● Route interface cables away from motors and other sources of magnetic or radio
frequency interference.
● Stay within the cable length limitations.
2.8.4 Management Host Requirements

A local management host with at least one serial port connection is required for the initial
installation and configuration of a controller enclosure. After you configure one or both of
the controller modules with an Internet Protocol (IP) address, you then use a remote
management host on an Ethernet network to configure, manage, and monitor.
Note
i You must use Ethernet cable designated CAT-5 or higher to connect a controller
enclosure to an Ethernet network.

3 Hardware, Operating, and Indicator
Components
This chapter describes the main hardware components and the position and meaning of the
operating and indicator elements at the FibreCAT SX storage system enclosures.
3.1 Controller Enclosure

The FibreCAT SX60 / SX80 / SX88 / SX100 controller enclosure can be connected to Fibre
Channel host bus adapters or switches. The FibreCAT SX80 iSCSI controller enclosure can
be connected to Ethernet host bus adapters, hubs or switches.
3.1.1 Components
Enclosure Components Quantity

FC or ISCS RAID controller (I/O) 1 or 21
module
SAS or SATA drive module 2–12 per enclosure
AC power and cooling module 2 per enclosure
2- or 4-Gbps FC host port with SFP2 2 per controller module (SX60 / SX80 / S88 / SX80 iSCSI);
or 1 Gbps iSCSI host port 4 per controller module (SX100)
3-Gbps, 4-lane SAS expansion port 1 per controller module (SX60 / SX80 / S88 / SX80 iSCSI);
2 per controller module (SX100)
RJ-45 Ethernet port (RJ-45) 1 per controller module
CLI port (RS-232 micro-DB9) 1 per controller module
Table 15: Controller Enclosure Components
1
Air management system drive blanks or I/O blanks must fill empty slots to maintain optimum airflow through the
chassis.
2
The SFPs are part of the controller modules and must not be removed.

Controller Enclosure Hardware, Operating, and Indicator Components
3.1.2 Components and Indicators at the Front Side
Enclosure ID LED
Status LEDs (top to bottom):

Drive modules with LEDs - Unit Locator
(numbered left to right - Fault/Service Required
by row: 0–3, 4–7, 8–11) - FRU OK
- Temperature Fault
Figure 1: Components and Indicators on the Front of an Controller Enclosure
LED Color State Description

Enclosure ID Green On Shows the enclosure ID for an enclosure, which enables
you to correlate a physical enclosure with logical views
presented by management software. The enclosure ID for a
controller enclosure is zero (0); the enclosure ID for an
attached expansion enclosure is non-zero.
OK to Remove(drive Blue Off The drive module is not prepared for removal.
module) On The drive module has been removed from any active virtual
disk, spun down, and prepared for removal.
Power/Activity/Fault Green Off The drive module is not powered on.
(drive module)
On The drive module is operating normally.
Blink The drive module is active and processing I/O or is
performing a media scan.
Yellow Off No fault.
On The drive module has experienced a fault, has failed or is a
member of a critical vdisk.
Blink Physically identifies the drive module.
White Off Not active.
Unit Locator Blink Physically identifies the enclosure.
Yellow Off No fault.
Fault/Service Required On An enclosure-level fault has occurred. Service action is
required. The event has been acknowledged but the
problem still needs attention.
Table 16: Controller Enclosure LEDs (Front)

Hardware, Operating, and Indicator Components Controller Enclosure
LED Color State Description

Green On The enclosure is powered on with at least one power
FRU OK module operating normally.
Off Both power modules are off.
Green Off The enclosure temperature is normal.
Temperature Fault Yellow On The enclosure temperature is above threshold.
Table 16: Controller Enclosure LEDs (Front)
3.1.3 Ports and Switches at the Back Side

The following figure shows the ports (location: controller module) and the power switch
(location: power and cooling module) at the back of the FibreCAT SX60 / SX80 / SX88
controller enclosure equipped with two FC RAID controllers. The second (lower) controller
is optional.You will use the ports and the switch during the installation procedure.
Power switch
FC ports CLI port Ethernet management port Expansion port

Figure 2: FibreCAT SX60 / SX80 / SX88 Controller Enclosure Ports (FC) and Power Switch
(location: power and cooling module) at the back of the FibreCAT SX80 iSCSI controller
enclosure equipped with two iSCSI controllers. The second (lower) controller is optional.
You will use the ports and the switch during the installation procedure.

Power switch
Ethernet ports CLI port Ethernet management port Expansion port

Figure 3: FibreCAT SX80 iSCSI Controller Enclosure Ports (FC) and Power Switch
(location: power and cooling module) at the back of the FibreCAT SX100 controller
enclosure equipped with two FC RAID controllers. The second (lower) controller is
optional.You will use the ports and the switch during the installation procedure.
Power switch
FC ports CLI port Ethernet management port Expansion ports

Figure 4: FibreCAT SX100 Controller Enclosure Ports (FC) and Power Switch
Port/Switch Description
Power switch Toggle, where “|” is On and “O” is Off.
FC/Ethernet 4-Gbps FC or 1-Gbps iSCSI ports used to connect to data hosts. Each FC port
ports contains an SFP1 transceiver. Host port 0 and 1 connect to host channel 0 and 1,
respectively. The FibreCAT SX100 model has four host ports.
CLI port Micro-DB9 port used to connect the controller module to a local management host
using RS-232 communication for out-of-band configuration and management.
Table 17: Controller Enclosure Ports and Switches (Back)

Hardware, Operating, and Indicator Components Controller Enclosure
Ethernet 10/100BASE-T Ethernet port used for TCP/IP-based out-of-band management of
management the RAID controller. An internal Ethernet device provides standard 10 Mbit/second
port and 100 Mbit/second full-duplex connectivity.
Expansion port 3-Gbps, 4-lane (12 Gbps total) table-routed egress port used to connect SAS
expansion enclosures.
Table 17: Controller Enclosure Ports and Switches (Back)
1 The SFPs are part of the controller modules and must not be removed (SFP = Small Form-factor Pluggable).
3.1.4 Indicators at the Back Side

The following figure shows the LEDs at the back of the controller enclosure (FibreCAT SX60
/ SX80 / SX88 as example) equipped with two FC RAID controllers. The second (lower)
controller is optional. You will use the LEDs during the installation procedure.
AC Power Good
Host link status Cache status
DC Voltage/Fan Fault/
Host link speed Host activity Expansion port status
Service Required
Unit Locator FRU OK Ethernet activity

OK to Remove Fault/Service Required Ethernet link status
Figure 5: FibreCAT SX60 / SX80 / SX88 Controller Enclosure (FC) LEDs
LED (Location: Power Color State Description

and Cooling Module)
AC Power Good Green Off AC power is off or input voltage is below the minimum
threshold.
On AC power is on and input voltage is normal.
DC Voltage/Fan Fault/ Yellow Off DC output voltage is normal.
Service Required On DC output voltage is out of range or a fan is operating
below the minimum required RPM.
Table 18: Controller Enclosure LEDs (Back, Power and Cooling Module)

LED (Location: Color State Description

Controller Module)
Host link status (FC only) Green Off The port is empty or the link is down.
On The port link is up and connected.
Host link speed (FC only) Green Off The data transfer rate is 2 Gbps.
On The data transfer rate is 4 Gbps.
Unit Locator Blink Physically identifies the controller module.
Blue Off The controller module is not prepared for removal.
OK to Remove On The controller module can be removed.
Yellow On A fault has been detected or a service action is required.
Fault/ServiceRequired Blink Indicates a hardware-controlled power up or a cache
flush or restore error.
Green Off Controller module is not OK.
FRU OK On Controller module is operating normally.
Blink System is booting.
Cache status Green Off Cache is clean (contains no unwritten data).
On Cache is dirty (contains unwritten data) and operation is
normal.
Blink A Compact Flash flush or cache self-refresh is in
progress.
Host activity Green Off The host ports have no I/O activity.
Blink At least one host ports has I/O activity.
Ethernet link status Green Off The Ethernet port is not connected or the link is down.
On The Ethernet link is up.
Ethernet activity Green Off The Ethernet link has no I/O activity.
Blink The Ethernet link has I/O activity.
Expansion port status Green Off The port is empty or the link is down.
Table 19: Controller Enclosure LEDs (Back, Controller Module)

Hardware, Operating, and Indicator Components Expansion Enclosure
3.2 Expansion Enclosure

The FibreCAT SX expansion enclosure can be connected to a FibreCAT SX controller
enclosure to provide additional disk storage capacity.
3.2.1 Components.
Description Quantity
SAS expansion module 1 or 21
SAS or SATA drive module 2–12 per enclosure
AC power and cooling module 2 per enclosure
3-Gbps, 4-lane SAS In port 1 per expansion module
3-Gbps, 4-lane SAS Out port 1 per expansion module
Table 20: Expansion Enclosure Components
1
Air management system drive blanks or I/O blanks must fill empty slots to maintain
optimum airflow through the chassis.
3.2.2 Components and Indicators at the Front Side

The components and indicators at the front of an expansion enclosure are the same as at
a controller enclosure (see page 28).
3.2.3 Ports and Switches at the Back Side

The following figure shows the ports (location: expansion module) and the power switch
(location: power and cooling module) at the back of the expansion enclosure equipped with
two SAS expansion modules. The second (lower) module is optional.You will use the ports
and the switch during the installation procedure.

Expansion Enclosure Hardware, Operating, and Indicator Components
Power switch
SAS In port SAS Out port

Figure 6: Expansion Enclosure Ports and Power Switch
Power switch Toggle, where “|” is On and “O” is Off.
SAS In port 3-Gbps, 4-lane (12 Gbps total) subtractive ingress port used to connect to a
controller enclosure.
SAS Out port 3-Gbps, 4-lane (12 Gbps total) table-routed egress port used to connect to another
expansion enclosure.
Table 21: Expansion Enclosure Ports and Switches (Back)

Hardware, Operating, and Indicator Components Expansion Enclosure
3.2.4 Indicators at the Back Side

The following figure shows the LEDs at the back of the expansion enclosure equipped with
two SAS expansion modules. The second (lower) module is optional. You will use the LEDs
during the installation procedure.
AC Power Good
DC Voltage/Fan Fault/
Service Required SAS In port status SAS Out port status
Unit Locator FRU OK

OK to Remove Fault/Service Required
Figure 7: Expansion Enclosure LEDs
LED (Location: Power Color State Description

and Cooling Module)
AC Power Good Green Off AC power is off or input voltage is below the minimum
threshold.
On AC power is on and input voltage is normal.
DC Voltage/Fan Fault/ Yellow Off DC output voltage is normal.
Service Required On DC output voltage is out of range or a fan is operating
below the minimum required RPM.
Table 22: Expansion Enclosure LEDs (Back, Power and Cooling Module)

Expansion Module)
SAS In port status Green Off The port is empty or the link is down.
SAS Out port status Green Off The port is empty or the link is down.
Table 23: Expansion Enclosure LEDs (Back, Expansion Module)

Expansion Enclosure Hardware, Operating, and Indicator Components

Expansion Module)
Unit Locator Blink Physically identifies the expansion module.
Blue Off Not implemented.
OK to Remove
Yellow On A fault has been detected or a service action is required.
Fault/ServiceRequired Blink Indicates a hardware-controlled power up or a cache
flush or restore error.
Green Off Expansion module is not OK.
FRU OK On Expansion module is operating normally.
Blink System is booting.
Table 23: Expansion Enclosure LEDs (Back, Expansion Module)

4 Connecting Hosts / Configurations
This chapter describes the FibreCAT SX system cable connections for hosts and shows
typical configurations.
4.1 Connecting Remote Management Hosts

The management host directly manages systems out-of-band over a network. This section
describes how to connect the Ethernet cables and power cords to the management host.
1. Locate the Ethernet ports for controller A and controller B at the back of the controller
enclosure.
2. Connect an Ethernet cable to each Ethernet port.
3. Connect the other end of each Ethernet cable to a network that your management host
can access (preferably on the same subnet).
4.2 Installing the SCSI Enclosures Services Driver

NOTE
i This section applies to Microsoft Windows hosts only.
Installing the SCSI Enclosure Services (SES) driver prevents Microsoft Windows hosts from
displaying the Found New Hardware Wizard when the storage system is discovered.
1. In a web browser, go to
http://support.ts.fujitsu.com/com/support/downloads.html and download the SCSI
enclosure device driver for FibreCAT SX to a network location that the data host can
access.
2. Extract the package contents to a temporary folder on the host.
3. In that folder, double-click Setup.exe to install the driver.
4. Click Finish.
The driver is installed.

Connecting Direct Attached iSCSI Configurations Connecting Hosts / Configurations
4.3 Connecting Direct Attached iSCSI Configurations
4.3.1 Single Controller FibreCAT SX80 iSCSI With One Host

A single-controller configuration is supported but provides no redundancy in the event that
the controller fails. Each data host has one iSCSI port connected to the controller module.
If the controller fails, the host loses access to the volume LUNs.
Single-Controller, Direct Attach Connection to a Single Data Host shows the direct attach
configuration for a single data host
Figure 8: Single-Controller, Direct Attach Connection to a Single Data Host (iSCSI)
The FibreCAT SX80 iSCSI Storage Systems was designed as a fully redundant dual
controller storage array for iSCSI systems. The storage system alternately assigns virtual
disks between the two controllers to support automatic load balancing. It is currently
available as a non-redundant single controller storage system as an entry level option.
When the FibreCAT SX80 iSCSI Storage System has a single controller, every other virtual
disk created will be owned by the non-existent second controller, regardless of the
ownership specified when creating the virtual disk - any storage assigned to the missing
controller is treated as "failed-over" to the existing controller. This choice allows for trans-
parent upgrade to a dual controller system in the future. In order for the virtual disks
assigned to the non-existent controller to be visible, the host needs to establish logins to
both iSCSI targets. The IP addresses of the non-existent controller (target) need to be
configured in the storage system. The connected hosts then need to establish iSCSI
sessions (logins) to one or both targets to access the volumes on those virtual disks.

Connecting Hosts / Configurations Host Interface Speed for FibreCAT SX (FC)
For example, if you create 6 virtual disks, then the second, fourth and sixth virtual disks
would be owned by the non-existent second controller. To present volumes created on
these virtual disks to a host, you must assign IP addresses to the same ports on the non-
existent controller as ports that are used on the existing controller. The address assigned
to the port of the non-existent controller must be in the same network as the same port of
the existing controller. For example, if controller A has the following configuration:
Controller A
Port/Channel: 0 1
IP: 192.168.144.1 10.0.0.1
Netmask: 255.255.255.0 255.0.0.0
You should then set the IP address of the ports on the controller that is not installed to
reserve addresses in the same subnets so those hosts can see the volumes through the A
controller, as shown below:
Controller B (currently not installed)
Port/Channel: 0 1
IP: 192.168.144.18 10.0.0.22
Netmask: 255.255.255.0 255.0.0.0
Finally, include these addresses in the iSCSI initiator configuration the same as you would
the IP addresses of the existing controller.
If you follow this process, all of the volumes created on the FibreCAT SX80 iSCSI Storage
System will be visible through the existing controller host ports. When you are ready to
upgrade to a dual controller system, simply install the second controller with Ethernet
cables pre-attached and all the work will be done automatically by the storage system to
move those volumes to the new controller.
Configuration Rules
Fixed speed for all ports
4.4 Host Interface Speed for FibreCAT SX (FC)

NOTE
i The following restriction applies to FibreCAT SX60 / SX80 in direct attached config-
urations:
If your Host Interface Module (HIM) is Model 0 (or you have a mixed mode of HIM
0 and 1 in a dual controller FibreCAT controller enclosure), for FibreCAT SX60 /
SX80 in direct connect mode 2 Gbit FC speed is supported only.
If both HIMs in your controller enclosure are Model 1 (or you have only a single controller
FibreCAT SX and it is Model 1), in direct host connect mode up to 4 Gbit FC speed is
supported for FibreCAT SX60 / SX80.

Host Interface Speed for FibreCAT SX (FC) Connecting Hosts / Configurations
For FibreCAT SX88 / SX100, in direct host connect mode always up to 4 Gbit FC speed is
supported.
In switch attached mode, for FibreCAT SX60 / SX80 / SX88 / SX100 up to 4 Gbit FC speed
is supported always (no restriction with any HIM Model).
If you have a direct attached configuration with FibreCAT SX60 / SX80, you should find out
the HIM Model (0 or 1) of your controller(s) via FibreCAT SX Manager’s Web Based
Interface:
1. Open FibreCAT SX Manager’s Web Based Interface.
2. Login as monitor or manage user.
3. In MONITOR STATUS menu, click the link advanced settings (see screenshots below).
Here you can find out the HIM Model of your controller module(s):
Figure 9: Detecting the HIM Model With FibreCAT SX Manager’s WBI (Example With Two HIM Models 0)

Connecting Hosts / Configurations Connecting Direct Attached FC Configurations
Figure 10: Detecting the HIM Revision With FibreCAT SX Manager’s WBI (Example With Two HIM Models 1)
4.5 Connecting Direct Attached FC Configurations

This section explains how to connect data hosts to access the controller enclosure directly.
You will need fibre optic cables of the proper length to connect your data host to the storage
system.
The FibreCAT SX60 / SX80 / SX88 controller enclosure equipped with two controllers has
four FC connections, two per controller. The FibreCAT SX100 controller enclosure equipped
with two controllers has eight FC connections, four per controller. To maintain redundancy,
connect one data host to both Controller A and Controller B.
1. Locate the host ports at the back of the controller enclosure.
2. Connect a fiber optic cable to each host port on controller A and controller B.
V CAUTION!
Fiber optic cables are fragile. Do not bend, twist, fold, pinch, or step on the fiber
optic cables. Doing so can degrade performance or cause data loss.
3. Connect the other end of each fiber optic cable to the HBAs as shown in the following
figures.

Connecting Direct Attached FC Configurations Connecting Hosts / Configurations
4.5.1 FibreCAT SX60 / SX80 / SX88 With One Dual Port Host
The cabling examples show a high-availability controller and path failover configuration.
This configuration requires host port interconnect circuitry between controller modules to
be set to Interconnected as described in “Configuring Controller Enclosure Host Ports (FC)”
on page 78. For path failover this configuration requires a host-based multipathing software.
The controller enclosure is equipped with two FC RAID controllers and the host have two
FC HBAs each.
Port interconnects:
interconnected by FibreCAT SX Manager
Figure 11: Minimal Connection to a Single Data Host
Configuration Rules
Restrictions: not for VMware
FC-Topology: Arbitrated Loop (FC-AL)
FC Speed: max. 4Gbit/s
(note “Host Interface Speed for FibreCAT SX (FC)” on page 39)
Host Port Interconnect: Interconnected
Path-Failover Software: FTS DDM V5; native MPIO (DSM); FTS Multipath V 5,
native DM-MP (RedHat, SuSE)

4.5.2 FibreCAT SX60 / SX80 / SX88 With Two Dual Port Hosts
The following figure shows the preferred high-availability controller and path redundant
configuration. This configuration requires that host port interconnects are set to Intercon-
nected as described in “Configuring Controller Enclosure Host Ports (FC)” on page 78. This
configuration also requires host-based multipathing software. For failover behavior, see
“Configurations” on page 79.
A + B LUNs A + B LUNs
Figure 12: High-Availability, Dual-Controller, Direct Attached Connection to Dual Data Hosts for Windows and
Linux (no VMware support)
Configuration Rules
Restrictions: not for VMware
FC Speed: max. 4Gbit/s
(note “Host Interface Speed for FibreCAT SX (FC)” on page 39)
Host Port Interconnect: Interconnected
Path-Failover Software: FTS DDM V5; native MPIO (DSM); FTS Multipath V 5,
native DM-MP (RedHat, SuSE)

4.5.2.1 Controller Failover Scenario
A + B LUNs
A + B LUNs
FAILED
Figure 13: Direct Attached FibreCAT SX (Controller Failover Scenario)
In an active-active configuration, failover is the act of temporarily transferring ownership of

controller resources from a failed controller to a surviving controller. The resources include
virtual disks, cache data, host ID information, and LUNs and WWNs. In this scenario host
A and host B see all resources via controller A.

4.5.2.2 Path Failover Scenario
A + B LUNs
Figure 14: Direct Attached FibreCAT SX (Path Failover Scenario)
In scenario of path-failover, host A sees his B-LUNs via the host interconnect line. The filter
driver (multipath software) generates the B-LUN I/Os across the other HBA.

4.5.3 FibreCAT SX60 / SX80 / SX88 With Two Dual Port Hosts for High
Performance
The following figure shows a non-redundant path-failover configuration that can be used
when high performance is more important than high availability. This configuration requires
the host port interconnect circuitry to be be set to Straight-through, which it is by default.
A LUNs B LUNs
A LUNs B LUNs
Figure 15: High-Performance, Dual-Controller, Direct Attached Connection to Dual Data Hosts (no Solaris
Support)
Configuration Rules
Restrictions: not for Solaris and not for VMware
FC Speed: max. 4Gbit/s (note “Host Interface Speed for FibreCAT SX (FC)”
on page 39)
Host Port Interconnect: Straight-through
Path-Failover Software: FTS DDM V5; native MPIO (DSM); FTS Multipath V 5

4.5.4 FibreCAT SX100 With Four Dual-Port Hosts
2370, 2278 2070, 2178
2370, 2278 2070, 2178
2270, 2378 2078, 2170
2270, 2378 2078, 2170
Figure 16: Four Dual-Port Data Hosts with FibreCAT SX100

This figure shows the optimized connectivity for a high-availability, dual-controller, direct
attached connection to four dual-port data hosts. To ensure failover fault tolerance, each
dual port host must be connected to each controller. Connecting one host port to Port 0 or
Port 1 and the other to Port 2 or Port 3 on the other controller provides the most efficient
internal path balancing in each controller.
Configuration Rules
Usage Clustered servers, direct connect to storage, classroom applications, classroom file
server
Advantage
Benefits of fault tolerance of dual-controller and clustered servers
Example business
Educational facility; small tech business
Topology
Loop mode
HBA settings
fixed speed 2/4Gbit
Link time out 60 sec
node time out 60 sec
Queue depth (see release notes)
SW MPIO SW
Storage settings
host port interconnect: Interconnected
In this configuration, all hosts have redundant connections to volumes that are associated
with each of the controllers. If a controller fails, the hosts maintain access to all of the
volumes through the hosts ports on the surviving controller.

2370, 2278 2070, 2178
2370, 2278 2070, 2178
2270, 2378 2078, 2170
2170, 2078 2078, 2170
FAILED
Figure 17: Four Dual-Port Data Hosts with FibreCAT SX100 and Failed Controller

Connecting Switch Attached iSCSI Configurations Connecting Hosts / Configurations
4.6 Connecting Switch Attached iSCSI Configurations
4.6.1 FibreCAT SX80 iSCSI With Two Dual Port Hosts and Two Switches
The high-availability configuration requires two Gigabit Ethernet (GbE) switches, as shown
in the following figure. During active-active operation, both controllers' mapped volumes are
visible to both data hosts.
A & B volumes
A & B volumes
A volumes, A0 IP A volumes, A1 IP
B volumes, B0 IP B volumes, B1 IP
Figure 18: iSCSI Storage Presentation During Normal, Active-Active Operation

Connecting Hosts / Configurations Connecting Switch Attached iSCSI Configurations
A dual-controller FibreCAT SX80 iSCSI storage system uses port 0 of each controller as
one failover pair and port 1 of each controller as a second failover pair. If one controller fails,
all mapped volumes remain visible to all hosts. Dual IP-address technology is used in the
failed over state, and is largely transparent to the host system. However, for complete fault
tolerance, host-based path failover software is recommended.
Configuration Rules
Fixed speed for all ports
The following figure shows an example of storage presentation during failover of

controller B.
A & B volumes
A & B volumes
A & B volumes, A0 & B0 IPs A & B volumes, A1 & B1 IPs
Figure 19: iSCSI Storage Presentation During Failover

Connecting Switch Attached FC Configurations Connecting Hosts / Configurations
Single controller mode is supported in both direct attached and switch attached configu-
ration. In single controller mode the system is set to a failed over state to support a future
upgrade to dual controller system. When configuring a single controller system you will
need to assign ghost host IP configuration to the system. This will ensure that when an
additional controller is inserted no additional configuration is required.
NOTE
i Ensure that when configuring a single controller system you assign a host port IP
address to both the active controller and the host B controller.
4.7 Connecting Switch Attached FC Configurations

This section explains how to connect data hosts to access the controller enclosure through
one or more external FC switches.
You will need fiber optic cables of the proper length to connect your data host to the switch,
and the switch to the storage system.
4.7.1 FibreCAT SX60 / SX80 / SX88 With One Switch and One Dual Port Host
2. Connect a fiber optic cable to each host port on controller A and controller B.
V CAUTION!
3. Connect the other end of each cable to a switch port. Refer to Figure 20 for configu-
ration options.
4. Using fiber optic cables connect the switch to two FC HBA ports as shown in the
following figures.

Connecting Hosts / Configurations Connecting Switch Attached FC Configurations
The following figure shows a redundant connection through a single switch to a single data
host with two HBA ports. This configuration requires that host port interconnects are set to
Straight-through. It also requires host-based multipathing software.
Figure 20: Redundant Connection Through a Single Switch to a Single Data Host
NOTE
i The FC switch must be configured according to port zoning rules (only one initiator
and one target per zone) and with fixed speed and topology settings.

4.7.2 FibreCAT SX60 / SX80 / SX88 With Two Switches and One Dual Port
Host
2. For switch A: Connect fiber optic cables to host port 0 on controller A and host port 1
on controller B. Then connect the other ends of the cables to the switch.
3. For switch B: Connect fiber optic cables to host port 1 on controller A and host port 0
on controller B. Then connect the other ends of the cables to the switch.
V CAUTION!
4. Using fiber optic cables connect each of the two switches to FC HBAs on the host as
shown in the following figure.
This configuration requires host port interconnect circuitry between controller modules to
be set to Straight-through. The cabling examples show a controller and path high-availability
configuration. For path failover this configuration requires a host-based multipathing
software. The controller enclosure is equipped with two FC RAID controllers and the host
has two FC HBAs.
MMF <= 300 m A+B LUNs

MMF <= 300 m A+B LUNs
A B
A B
Figure 21: Redundant, High-Availability Connection Through Switches to Dual Data Hosts

NOTE
Configuration Rules
Restrictions: with Solaris not for FibreCAT SX60
FC Speed: 2 / 4 Gbit/s
Max. Member in Switch Zone: only 1 initiator and 1 target per zone
Path-Failover Software Linux: native DM-MP (RedHat, SuSE)
Path-Failover Software Windows: FTS DDM V5, native MPIO (DSM), FTS Multipath V 5
Path-Failover Software VMware: native MP
4.7.2.1 Configuration Rules for VMware ESX Server 3.0.0 and 3.0.1
Figure 20 above shows the configuration.

● Only switch configuration supported.
● Use port zoning and not WWN zoning on the switches.
● Adjust the port topology on the switch: F-Port for server, L-Port for storage.
● Adjust the link speed on the switch ports.
FibreCAT SX Configuration:
● Host Port Configuration Link Speed: 4 Gbit/s or 2 Gbit/s (depending on HBA)
● Internal Host Port Interconnect: Straight-through

4.7.3 FibreCAT SX60 / SX80 / SX88 With Two Switches and Two Dual Port
Hosts
For high availability, two data hosts can be connected through two switches to a dual-
controller storage system. The controller host port interconnects must be set to Straight-
thrrough and host-based multipathing software is not required.
Figure 22: Switch Attached Configuration with Two Switches and Two Hosts
NOTE

Configuration Rules
Restrictions: with Solaris not for FibreCAT SX60
Path-Failover Software Windows: FTS DDM V5, native MPIO (DSM), FTS Multipath V 5

4.7.4 FibreCAT SX100 With One Switch and Two Dual-Port Hosts
Figure 23: Two Dual-Port Data Hosts with FibreCAT SX100 and a Switch for High Availability
NOTE

Connecting Hosts / Configurations Supported HBAs for Solaris (SPARC)
Configuration Rules
Path-Failover Software Windows: FTS DDM V5, native MPIO (DSM), FTSC Multipath V 5
4.8 Supported HBAs for Solaris (SPARC)

For the latest released Host Bus Adapters, the latest released drivers and their settings,
please refer to http://www.ts.fujitsu.com/support/manuals.html. Select your
product (STORAGE / FibreCAT / FibreCAT SX ...). Here you can find the document
“Released Host Bus Adapters; Driver Settings and FW-Versions for FibreCAT SX ...”.

5 Installing Enclosures
This chapter describes the process of installing FibreCAT SX enclosures in a
PRIMECENTER rack or in a standard 19-inch EIA rack cabinet.
The installation procedures in this chapter require the following items:
● #2 Phillips screwdriver
● Standard screwdriver
● Allen wrench (provided; used with 6-mm screws and #12-24 x 3/8-inch sockethead
screws)
● Antistatic protection devices
V CAUTION!
Be careful if using a power tool; it could strip or damage connections.
V CAUTION!
Electrostatic discharge can damage sensitive components. be sure you are
properly grounded before touching a static-sensitive component or assembly.
5.1 Safety Precautions

For your protection, observe the following safety precautions when setting up your
equipment:
● Follow all cautions and instructions marked on the equipment.
● Ensure that the voltage and frequency of your power source match the voltage and
frequency inscribed on the equipment’s electrical rating label.
● Never push objects of any kind through openings in the equipment. Dangerous voltages
may be present. Conductive foreign objects could produce a short circuit that could
cause fire, electric shock, or damage to your equipment.
I Do not make mechanical or electrical modifications to the product. The vendor is
not responsible for the safety or regulatory compliance of a modified product.

Unpacking an Enclosure and Verifying its Contents Installing Enclosures
5.2 Unpacking an Enclosure and Verifying its Contents

This section provides a list of contents in an enclosure package.
V CAUTION!
Two people are needed to lift and move the enclosure. Use care to avoid injury. An
enclosure with all drives installed can weigh 33.6 kg. Do not lift the front of the
enclosure; this can cause damage to the drives.
1. Unpack the enclosure.
2. Check the contents of the enclosure and box for the items listed in the following table.
Item Quantity
Enclosure ordered1: 1
Controller enclosure
Expansion enclosure
SFP2 transceivers 1 per host port
7.5 m shielded CAT-5 Ethernet Crossover cable 1 with second controller module
(controller enclosure)
5 m serial cable, RS-232 micro-DB9 (controller 1 per controller module
enclosure)
0.5 m SAS-to-SAS cascading cable (expansion 1 per expansion module
enclosure)
2.5 m power cord 2 per enclosure
Rackmount kit 1 per enclosure
Safety manual 1
Purchased options. These options are ordered at the Various
time of purchase and are integrated into or added to the
array prior to delivery.
Table 24: Contents of an Enclosure Package
1 The enclosure includes 1 or 2 controller or expansion modules, as ordered.
2
The SFPs are part of the controller modules and must not be removed.

Installing Enclosures Preparing the Rack
5.3 Preparing the Rack

Before installing enclosures in a rack cabinet, ensure it is installed according to its instal-
lation instructions.
1. Stabilize the rack as described in its documentation.
Ensure the rack installation complies with local safety codes.
2. If the cabinet has casters, make sure the casters are locked to prevent the cabinet from
rolling.
3. Remove or open the top front panel.
4. Remove or open the vented back panel.
5.4 Installing an Enclosure in a Rack

The FibreCAT SX storage system enclosures are designed to be installed in a Fujitsu
PRIMECENTER rack or in a standard 4-post, 19-inch EIA rack, using 2 units (2U) of rack
space each.
5.4.1 Rack-Mount Kit

The rack-mount kit includes the following items:
● 1 sliding rail kit (see Figure 24)
– 2 ready for use sliding rails
– 10 M5 x 10 screws with centering washers
– 2 cage nuts
● 1 support bracket for use in Fujitsu’ PRIMECENTER racks
(see Figure 26)

Installing an Enclosure in a Rack Installing Enclosures
Left* sliding rail Right* sliding rail
Positioning tappets Screws and nuts Mounting outline for PRIMECENTER racks
Figure 24: Sliding Rail Kit (A3C40075969)
*: seen from the front of the rack

Installing Enclosures Installing an Enclosure in a Rack
5.4.2 Rack Mounting Position Overview

The following figure shows the rack mounting positions, screws, and cage nuts of two enclo-
sures one upon the other.
Rear Side of the Rack Front Side of the Rack

rear left** rear right** (with support bracket) front left** front right**
2. U*
2. U* 2. U* 2. U* 2. U*
1. U*
1. U* 1. U* 1. U* 1. U*
2. U*
2. U* 2. U* 2. U* 2. U*
1. U*
1. U* 1. U* 1. U* 1. U*
Legend
*: height units (U) counted starting from the bottom line of the device
**: "rear left" and "rear right": seen from the rear side of the rack
"front left" and "front right": seen from the front side of the rack
: M5 sqare caged nut
: M5 screw with centering washer (“mounting spring”)
Figure 25: Rack Post Mounting Positions of Two enclosures
5.4.3 Mounting Steps
1. If you use a Fujitsu PRIMECENTER rack you first have to moun

the support bracket in the appropriate height to the - seen from
the front of the rack - left rear rack post.
Figure 26: Support Bracket for Use in PRIMECENTER Racks

Figure 27: Mounting the Support Bracket
2. Place the right rail (support angle down) from the front into the rack, putting the
positioning tappet into the appropriate whole of the right rear rack post.
3. Compress the spring mounted rail to its length and screw on the front rail end to the right
front rack post as shown below.
Figure 28: Mounting the Right Sliding Rail (Front Side of the Rack)

Installing Enclosures Installing an Enclosure in a Rack
4. Then fasten the rail on the rear side as shown below.
Figure 29: Mounting the Right Sliding Rail (Rear Side of the Rack)
5. Mount the left rail in the same way:

– In PRIMECENTER racks, put the positioning tappet of the left rail into the appro-
priate whole of the support bracket which you have mounted on the left rear rack
post.
– Screw on the front rail end to the left front rack post.
– Screw on the rear rail end to support bracket as shown below.
Figure 30: Mounting the Left Sliding Rail (Rear Side of the Rack)
6. Mount two square cage nuts to the front rack posts (one to the right and one to the left
post) into the post holes between the rail screws each. See the figure below for the
position of a nut. The nuts must be set in from inside the rack and lock in place in the
square post holes.

Figure 31: Mounting Position of a Cage Nut Between the Rail Screws
7. Put the enclosure from the front of the rack on the support angles of the sliding rails and
push it into the rack to the back stop.
8. Screw on the enclosure to both cage nuts mounted to the front rack posts as shown
below for the right side of the enclosure.
Figure 32: Screwing on the Enclosure (Right Side Example)

Installing Enclosures Connecting Controller and Expansion Enclosures
5.5 Connecting Controller and Expansion Enclosures

Use the supplied SAS cables to connect a controller enclosure to up to four expansion
enclosures. Table 33 shows the recommended fault-tolerant cabling pattern. In an
enclosure, the upper module is designated A and the lower module is designated B.
Regardless of the number of enclosures, connect the controller B expansion port to the top
expansion B SAS In port.
Figure 33: Fault-Tolerant Cabling Connections Between Controller and Expansion Enclosures
(left example: FibreCAT SX60 / SX80 / SX88, right example: FibreCAT SX80 / SX88)

Connecting Controller and Expansion Enclosures Installing Enclosures
Fault-tolerant cabling is recommended because it enables the system to continue to

operate if any expansion enclosure fails. However, the system also supports non-fault-
tolerant cabling using the supplied SAS cables. Table 34 shows non-fault-tolerant cabling
between a controller and up to four expansion enclosures.
Figure 34: Non-Fault-Tolerant Cabling Connections Between Controller and Expansion Enclosures
(example: FibreCAT SX80 / SX88)

Installing Enclosures Connecting Controller and Expansion Enclosures
The FibreCAT SX100 model allows to connect a controller enclosure to up to eight

expansion enclosures in two chains of up to four enclosures each.
When connecting multiple expansion enclosures to a FibreCAT SX100, distribute
expansion enclosures as evenly as possible between expansion channels. For example, if
connecting four expansion enclosures to a single controller enclosure, attach two expansion
enclosures to channel 0 and two to channel 1.
In Out Enclosure
ID 8
In Out
In Out Enclosure
ID 7
In Out
In
Out Enclosure
ID 6
Out
In
In Out Enclosure
ID 5
In Out
In
Out Enclosure
ID 4
Out
In
In Out Enclosure
ID 3
In Out
Out
In Enclosure
ID 2
Out
In
In Out
Enclosure In Out Enclosure
ID 1 ID 1
In Out In Out
Controller A 0 1 Controller A 0 1
Enclosure
Enclosure
0 1 ID 0 0 1
ID 0
Controller B Controller B
SAS Expansion Channel: 0 1 SAS Expansion Channel: 0 1
Figure 35: Cabling Connections Between a FibreCAT SX100 Controller and 1 / 8 Expansion Enclosure(s)
NOTE
i Redundant cabling is not supported for FibreCAT SX100.

Connecting the AC Power Installing Enclosures
5.6 Connecting the AC Power

Use this procedure to connect AC power to enclosures.
1. Verify that both power switches are off for each enclosure in the rack.
2. Using the AC power cords, connect each power and cooling module in the enclosure to
a separate power source in the rack.
3. Connect the primary power cords from the rack to the external power source.
I Do not power on the system until you complete the procedures in this chapter. The
power-on sequence is described below in “Testing the Enclosure Connections” on
page 72.
5.7 Testing the Enclosure Connections

Power on any expansion enclosures before powering on the controller enclosure. This
ensures that the disks in the expansion enclosures have enough time to completely spin up
before being scanned by the RAID controllers in the controller enclosure. Depending on
your configuration, it can take several minutes for the system to power up.
Use this procedure to turn power on for all enclosures installed in a rack.
1. Press the power switches at the back of each expansion enclosure to the On position.
While enclosures power up, their LEDs turn on and off intermittently. After the LEDs
stop blinking, if no LEDs on the front and back of the enclosure are yellow, the power-
on sequence is complete and no faults have been detected.
2. Press the power switches at the back of the controller enclosure to the On position.
If the enclosure’s power-on sequence succeeded as described in Step 1, the system is
ready to use.

6 Configuring a System for the First Time
This chapter describes how to use the CLI and the WBI of the FibreCAT CS Manager to
perform first-time configuration. It also describes how to perform basic storage configu-
ration to verify that your system is working.
For information about additional configuration and management tasks, including changing
the manage user’s password, refer to the WBI’s online help or the “FibreCAT SX Series
Administrator’s Guide”.
6.1 Setting the IP Address Using the CLI

The FibreCAT SX Manager’s command line interface (CLI) embedded in each controller
module enables you to configure and manage the system using individual commands or
command scripts through an out-of-band RS-232 or Ethernet connection. For detailed infor-
mation about the CLI, see the “FibreCAT SX Series Command Line Interface (CLI)” manual.
I As first time configuration of a FibreCAT SX storage system controller enclosure the
IP addresses of its RAID controller(s) is/are to be set. This step can only be
performed by using the CLI through an RS-232 connection.
All subsequent usage of the CLI can be performed with a terminal emulation
through an Ethernet connection.
To set the IP address for each controller perform the following steps:
The FibreCAT SX Manager’s command line interface (CLI) embedded in each controller
module enables you to access the module using RS-232 communication and terminal
emulation software. Use this interface to set the IP address for each controller. For detailed
information about the CLI, see the “FibreCAT SX Series Command Line Interface (CLI)”
manual.
1. From your network administrator obtain an IP address, subnet mask, and gateway
address for each controller.
I Each controller must have a different IP address.
2. Use the provided micro-DB9 serial cable to connect controller A to a serial port on a
host computer.

Setting the IP Address Using the CLI Configuring a System for the First Time
Your package contents include a micro-DB9-to-DB9 serial cable. If necessary, use a

DB9-to-DB25 adapter (not included) for connecting the serial cable to a DB25 serial
port on the host computer.
If the host computer has not a serial port but an USB port, use a USB-to-DB9 converter
(not included).
You have to configure the host computer’s serial port and a terminal emulator’s display
and communications settings. If you use HyperTerminal (standard for serial COM ports
in Win2000 and WinXP1), you can perform these three types of settings together. In this
case:
● Start HyperTerminal:
Start -> All programs -> Accessories -> Communications -> HyperTerminal
● Choose an free serial COM port of the host computer.

● Use the information in the following table for the HyperTerminal settings you are
asked for:
Settings Values
Baud rate (bits/s) 115,200
Data Bits 8
Parity None
Stop bits 1
Flow control None
Table 25: Host Serial Port Communication Settings
● Continue with step 4

3. Start and configure a terminal emulator, using the following display settings and
communication settings:
Display settings Values
Terminal Emulation Mode VT-100 or ANSI (for color support)
Font Terminal (standard in HyperTerminal)
Translations (not in HyperTerminal) None
Columns 80 (standard in HyperTerminal)
Table 26: Terminal Emulator Display Settings
1
If HyperTerminal is not part of your Windows installation, install it from your Windows data medium:
Start > Control Panel > Add or remove programs > Add/Remove Windows Components > Accessories and Utilities > Details
> Communications > Details > HyperTerminal (check box) > OK

Configuring a System for the First Time Setting the IP Address Using the CLI
:
Communication settings Values
Baud Rate 115,200
Data Bits 8
Stop Bits 1
Parity None
Flow Control None
Connector COM1 (typically)
Table 27: Terminal Emulator Connection Settings
4. In the terminal emulator, connect to controller A.

5. At the prompt (#), type the following command to set the values you obtained in Step 1:
set network-parameters <ip-address> netmask <netmask> gateway <gateway>
controller a|b
where:
<address> is the IP address of the controller.
<netmask> is the subnet mask, in dotted-decimal format.
<gateway> is the IP address of a default router.
a|b specifies the controller whose network parameters you are setting. The upper
controller is a; the lower controller is b.
6. Type show network-parameters to verify the new IP addresses.
7. Type exit to exit the CLI.
8. Verify Ethernet connectivity by typing ping <ip-address> in the host’s computers
command prompt window.
9. Connect controller B to the host computer and connect to it with the terminal emulator.
10. Repeat Step 5–Step 8 to configure controller B.

FibreCAT SX Manager Web-Based Interface Configuring a System for the First Time
6.2 FibreCAT SX Manager Web-Based Interface

To access the WBI for the first time, each FibreCAT SX controller module has a default IP
address (IP 10.0.0.1 and Subnet Mask 255.255.255.0). It can be used if the IP address
setting via CLI (see “Setting the IP Address Using the CLI” on page 73) can not be
performed, e. g. the appropriate serial cable is not on hand.
6.2.1 Configuring Your Web Browser for the WBI

Before using the FibreCAT SX Manager web based interface (WBI), ensure that your web
browser is properly configured according to the following guidelines:
● Use one of the following browsers:
– Microsoft Internet Explorer 5.5 or later
– Mozilla Firefox 1.0.7 or later
– Sun Solaris Netscape V. 7.0 or later
– Opera 8.51 or later
– and others
● Because the WBI uses popup windows to indicate the progress of user-requested
tasks, disable any browser features or tools that block popup windows.
● To optimize performance, set your browser to never check for newer versions of stored
pages: that is, to use cached pages.
● To optimize display, use a color monitor and set its color quality to the highest level.
● For Internet Explorer, to ensure you can navigate beyond the WBI login page, set the
local-intranet security option to medium or medium-low.

Configuring a System for the First Time Driver Settings
6.2.2 Logging In to WBI

To log in to the WBI:
1. In a web browser, type the controller module’s IP address in the Address or Location field
and press Enter.
If the IP address has not been set via serial cable and CLI, use the default settings with
which each FibreCAT SX Storage System ships:
IP 10.0.0.1, Subnet Mask 255.255.255.0
If the login page does not display, verify that you have entered the correct IP address.
2. On the login page, type the default management user name manage and default
password !manage.
3. Click Log In.
The Status Summary page is displayed.
6.2.3 Setting Date and Time

To configure the system’s date and time:
1. Select Manage -> General Config -> Set Date/Time.
2. In the Set System Date panel, select the current month, day, and year.
3. In the Set System Time panel, enter time values using a 24-hour clock and select the
proper time zone.
4. Click Change Date/Time.
Messages in system logs will now have correct timestamps.
6.3 Driver Settings

For the latest released Host Bus Adapters, the latest released drivers and their settings,
please refer to http://www.ts.fujitsu.com/support/manuals.html. Select your product
(STORAGE / FibreCAT / FibreCAT S ...). Here you can find the document “Released Host
Bus Adapters; Driver Settings and FW-Versions for FibreCAT SX60 / SX80 / SX88 / SX100”.

Configuring Controller Enclosure Host Ports (FC) Configuring a System for the First Time
6.4 Configuring Controller Enclosure Host Ports (FC)

To configure controller enclosure host ports:
1. Select Manage -> General Config -> Host Port Configuration.
2. In the Controller Module Host Port Configuration panels, set the link speed values to the
speed of the connected host (HBA). The default link speed is 2 Gbps.
3. Click Update Host Port Configuration.
4. If your configuration requires that host port interconnects be set to Interconnected:
a) In the Advanced Options panel, click Change FC Port Interconnect Settings.
b) Select Interconnected.
c) Click Save and Continue.
The Host Port Configuration page is redisplayed.
6.5 Configuring the Microsoft iSCSI Software Initiator (iSCSI)

After you have connected data hosts to the storage system and set IP properties for the
controller Ethernet management port and data host Ethernet ports, you can configure
settings in the Microsoft iSCSI Software Initiator, which you installed earlier on the data
hosts.
Configuring these settings on each data host includes:
● Setting IP addresses for each iSCSI host port (called a target portal) located on the
storage system.
● Logging on to iSCSI host ports on each controller module (called a target) from the data
host to initiate connectivity between the data host and the storage system.
1. Double-click the Microsoft iSCSI Software Initiator icon located on the desktop of the
host system.
2. In the Target Portals area of the Discovery tab, click Add.
3. Enter the IP address of an iSCSI host port on your storage system, leave the Port field
set at 3260, and click Add.
4. Repeat Step 2 and Step 3, adding IP addresses for the remaining iSCSI host ports on
the storage system.
IP addresses for storage system host ports (targets) are identified on the data host.

Configuring a System for the First Time Configuring the Microsoft iSCSI Software Initiator (iSCSI)
5. On the Targets tab, verify that two targets have been configured (.a and .b).
If two targets are not configured, one or more of the following issues may need to be
resolved:
● Data host IP addresses may not be set correctly.
● Controller enclosure host port addresses may not be set correctly on the data host.
● Cables between the controller enclosure and/or switches and/or data hosts may not
be connected correctly.
Correct the issue, return to the Targets tab and click Refresh.
6. If two targets are configured, select the first target (controller module) and click Log On.
7. On the Log On to Target dialog, set the following options:
a) For connectivity settings to persist across system reboots, check Automatically
Restore this Connection When the System Boots.
b) For fault-tolerant configurations, select Enable Multi-path.
c) Click Advanced to set connectivity settings as follows:
– At the Local Adapter field, select Microsoft iSCSI Initiator from the dropdown
menu.
– At the Source IP field, select the IP address for the local data Ethernet port that
is on the same subnet as the first target portal (iSCSI host port) to which you
want the host to connect.
– At the Target Portal field, select the IP address for the iSCSI host port on the
target (controller module) to which you are connecting.
– Repeat the log on procedure (Step i through Step iii) to initiate connectivity for
the second target portal on the selected target.
8. To allow LUN access through all available ports during failover, change default multip-
athing settings as follows:
a) On the Targets tab, select the target and click Details.
b) On the Devices tab of the Target Properties dialog, select the first device and click
Advanced.
c) On the MPIO tab of the Device Details dialog, select Round Robin from the Load
Balance Policy drop-down menu and click OK.
d) Repeat Step b and Step c for all devices listed.
9. Repeat tasks in Step 6, Step 7, and Step 8 for the second target.

Editing Registry Timeout Values for iSCSI Initiator Configuring a System for the First Time
10. On the Persistent Targets tab, verify that two entries appear for each controller (.a and
.b) for a total of four connections.
Configuring more than one session per controller port will use additional host interface
resources and may cause failover to function improperly.
If two persistent targets are not configured for each controller host port, complete the
following steps to remove and reconfigure targets:
a) Select each entry and click Remove.
b) Log off for each connection by selecting Targets > Details > Sessions > Log Off.
c) Verify that IP addresses were set correctly. If not, correct IP address settings.
d) Log on again for each target using the instructions in this section, starting at Step 2.
The data host can now communicate with the controllers through iSCSI Ethernet host
ports.
6.6 Editing Registry Timeout Values for iSCSI Initiator

V CAUTION!
Use caution when editing the Windows registry. Editing the wrong entry
or setting an incorrect value for a setting can introduce errors that cause the system
to malfunction. Create a registry back up before following instructions in this
section.
1. Locate and select the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\
{4D36E97B-E325-11CE-BFC1-08002BE10318}
Instances will be listed below the key using automatically generated (GUIDs).
Example: 0000,0001
2. Select and perform the following steps for each instance ID:
a) Check to see whether the DriverDesc parameter is set to Microsoft iSCSI Initiator.
If not, skip to the next interface ID.
b) If so, double-click to open the instance and then to open Parameters.
c) Edit the LinkDownTime key. The default value is 0x0f(15). Change this to
0x30(48).
3. Exit the Registry Editor.
4. Restart Windows for the new settings to take effect.

Configuring a System for the First Time Install Native MPIO Functionality Under Windows 2008 for
6.7 Install Native MPIO Functionality Under Windows 2008 for

FibreCAT SX
Run these two commands and the host will be rebooted with MPIO enabled for FibreCAT
SX systems. Note that the second command will reboot the host automatically.
servermanagercmd -install multipath-io
mpclaim -r -i -d "FSC FibreCAT_SX1"
Their must be exactly 5 spaces after "FSC".
6.8 Installing a License

Certain software features of this system have limits that can be extended by purchasing and
installing a license.
To install a license file on the system:
1. Select Manage -> General Config -> License Management -> Install A License.
2. Verify that the license file is valid as described in the on-screen text.
3. Ensure that the license file has been saved to a network location that the system can
access.
4. Click Browse and select the license file.
5. Click Load License File.
If the installation succeeds, the Licensed Features Installed panel shows license infor-
mation.
6.9 Creating Virtual Disks

Two or more disk drives can be logically combined to form a virtual disk. The combined
storage capacity can then be partitioned into volumes. The WBI provides both manual and
automatic methods for creating virtual disks, as described in its online help.
As an example, the following steps use the manual method to create two virtual disks with
the following characteristics:
● RAID 5, in which parity is distributed across all disk drives in the virtual disk
● Five disk drives per virtual disk

Volume Mappings Configuring a System for the First Time
● One spare disk drive dedicated to each virtual disk

● One volume per virtual disk, where the volume is not visible to data hosts
To create both virtual disks:
1. Select Manage -> Virtual Disk Config -> Create A Vdisk.
2. Select Manual Virtual Disk Creation (Detail-based).
3. Type a name for the virtual disks.
You can type up to 17 characters, including any printable ASCII characters except
quotation mark (“), comma, or backslash (\).
4. Select RAID 5 – Parity RAID, Parity Distributed.
5. Click Create New Virtual Disk.
6. In the Select Drives to Add to Virtual Disk panel, select the checkboxes of five drives.
7. For the dedicated spare drive option, select Yes and click Continue.
8. Select a drive to be the spare.
A dedicated spare (or vdisk spare) can replace a failed drive in this virtual disk only; it
cannot be used by other virtual disks.
9. Click Continue.
10. View but do not change the virtual disk and volume settings.
Notice that the virtual disk will have one volume, and by default that volume will not be
exposed to (accessible by) data hosts.
11. Click Create Virtual Disk.When processing is complete, a progress page is displayed.
12. Click the link to create another virtual disk.
13. Repeat Step 2–Step 11 to create a second virtual disk with a different name.
6.10 Volume Mappings

In the Map Hosts To Volume page you can add, change, or delete host access to the
selected volume.
Volume mapping changes take effect immediately. Make changes that limit access
! to volumes when the volumes are not in use. Be sure to unmount a mapped volume
from a host system before changing the mapping's LUN.
To manage host-to-volume mappings:
1. Select Manage -> Volume Management -> Volume Mapping -> Map Hosts To Volume.

Configuring a System for the First Time Testing the Configuration
For each virtual disk, the virtual disk panel shows a status icon; the name, RAID level,
size, number of disk drives, and number of volumes; and utility status, if any.
2. Select a virtual disk.
The selected virtual disk's volume names, sizes, default LUNs, and types are displayed.
3. Select a volume.
The Current Host-Volume Relationships panel shows which data-host ports have
access to the selected volume. For the selected volume you might see the following
mappings:
● All Hosts - Shows the settings used by all data-host ports to access the volume. This
entry is displayed only if no specific ports are mapped. If a specific port is mapped,
All Hosts changes to All Other Hosts.
● WWN value (FC) or IQN value (iSCSI) - Shows the settings used by a data-host port
to access the volume.
● All Other Hosts - Shows the access settings used by all data-host ports except by
specifically mapped ports. This entry is displayed only if specific ports are mapped.
If no specific port is mapped, All Other Hosts changes to All Hosts.
For each entry, the port identifier, the assigned LUN, and each controller host port's access
privilege are shown. The access privilege for a controller host port can be read-write, read-
only, or none (no access). A mapping cannot include both read-write and read-only access.
4. To add or change a mapping:
● In the Assign Host Access Privileges panel, select a host port identifier or All Other
Hosts.
● Specify a LUN and port-access settings.
● Click Map It.
When processing is complete, the page shows the new mapping.
6.11 Testing the Configuration

To determine that your system is ready for use, test the configuration as follows:
1. In the WBI, select Monitor -> Vdisk Status and view the configuration information for
each virtual disk.
The virtual disk status is Critical during initialization but you can perform I/O to the
volume.
2. From the data host:

Logging Out of the WBI Configuring a System for the First Time
a) Make the volume an operating system partition.

b) Verify that you can access the mapped volume and the volume size shown on the
data host matches the size shown in WBI.
c) Verify that you can write data to the volume.
If the above tests succeed, your system is ready for use. For information about
additional configuration and management tasks, including changing the manage user’s
password, refer to the WBI’s online help or the “FibreCAT SX Series Administrator’s
Guide”.
6.12 Logging Out of the WBI

If you do not log out of the FibreCAT SX Manager Web Based Interface when you have
finished using it, other manage users cannot log in to the same controller module, and your
IP address stays logged in for 30 minutes (the default auto-logout timeout setting).
To log out of the WBI:
1. Click Log Off at the bottom of the menu.
The Log Off page is displayed.
2. Click Log Off.
6.13 Next Steps

You have completed the installation and initial configuration tasks covered in this guide. For
information about further configuring your system and performing administrative tasks such
as upgrading software, refer to the “FibreCAT SX Series Administrator’s Guide” or the other
related documentation.

7 Powering the System Off and On
This chapter describes how to power off and power on the system when needed.
7.1 Powering Off the System

The system rarely needs to be powered off. You remove power only when you plan to physi-
cally move the system to another location.
Use this procedure when you need to power off the system.
1. Stop all I/O from hosts to the system.
2. Use WBI to shut down both controllers. Wait until WBI indicates that processing is
complete.
3. Press the power switches at the back of the controller enclosure to the Off position.
4. Press the power switches at the back of each expansion enclosure to the Off position.
7.2 Powering On the System

Power on any expansion enclosures before powering on the controller enclosure. This
ensures that the disks in the expansion enclosures have enough time to spin completely
before being scanned by the RAID controllers in the controller enclosure. Depending on
your configuration, it can take several minutes for the system to power up.
Use this procedure to turn power on for all enclosures installed in a rack.
1. Turn off both power switches on each enclosure that you want to connect to the rack’s
main power.
2. Connect the power cord for each power and cooling module to a separate power source
in the rack.
3. Connect the primary power cords from the rack to the external power source.

Powering On the System Powering the System Off and On
4. Press the power switches at the back of each expansion enclosure to the On position.
While enclosures power up, their LEDs turn on and off intermittently. After the LEDs
stop blinking, if no LEDs on the front and back of the enclosure are yellow, the power-
on sequence is complete and no faults have been detected.
5. Press the power switches at the back of the controller enclosure to the On position.
If the enclosure’s power-on sequence succeeded as described in Step 4, the system is
ready to use.

Glossary and Abbreviations
The glossary defines terms and acronyms used in FibreCAT SX storage system documen-
tation. Definitions obtained from the Storage Networking Industry Association (SNIA)
Dictionary are indicated with “(SNIA)” at the end. For the complete SNIA Dictionary, go to
www.snia.org/education/dictionary.
active-active
Synonym for dual active components or controllers. A pair of components, such
as the controllers in a failure tolerant storage subsystem that share a task or
class of tasks when both are functioning normally. When one of the components
fails, the other takes on the entire task. Dual active controllers are connected to
the same set of storage devices, improving both I/O performance and failure
tolerance compared to a single controller. (SNIA)
address
A data structure or logical convention used to identify a unique entity, such as a
particular process or network device.
AL_PA
See arbitrated loop physical address (AL_PA).
ANSI
American National Standards Institute
arbitrated loop physical address (AL_PA)

An 8-bit value used to identify a participating device in an Arbitrated Loop.
(SNIA)
API
Application Programming Interface
ARP
Address Resolution Protocol
array
See storage system.

block
A single sector on a disk. The smallest unit of data stored (written) to or
retrieved (read) from a disk.
broadcast write
Technology that provides simultaneous caching of write data to both RAID
controllers’ cache memory with positive direct memory access acknowl-
edgement (certified DMA).
cache
A high speed memory or storage device used to reduce the effective time
required to read data from or write data to a lower speed memory or device.
Read cache holds data in anticipation that it will be requested by a client. Write
cache holds data written by a client until it can be safely stored on more
permanent storage media such as disk or tape. (SNIA)
See also write-back cache, write-through cache.
capacitor pack
The controller module component that provides backup power to transfer
unwritten data from cache to Compact Flash memory in the event of a power
failure. Storing the data in Compact Flash provides unlimited backup time. The
unwritten data can be committed to the disk drives when power is restored.
CAPI
FibreCAT SX Configuration API.
channel
A physical path used for the transfer of data and control information between
storage devices and a RAID controller or a host; or, a SCSI bus in a controller
module.
chassis
An enclosure’s metal housing.
chunk size
The number of contiguous blocks in a stripe on a disk drive in a virtual disk. The
number can be adjusted to improve performance. Generally, larger chunks are
more effective for sequential reads. See block.
CLI
The command-line interface that system administrators can use to configure,
monitor, and manage FibreCAT SX storage systems. The CLI is accessible from
any management host that can access a controller module through an out-of-
band Ethernet or RS-232 connection.

controller
The control logic in a storage subsystem that performs command transfor-
mation and routing, aggregation (RAID, mirroring, striping, or other), high-level
error recovery, and performance optimization for multiple storage devices.
(SNIA)
A controller is also referred to as a RAID controller.
controller enclosure
An enclosure that contains disk drives and one or two controller modules.
See controller module.
controller module
A FRU that contains: a storage controller processor; a management controller
processor; out-of-band management interfaces; a LAN subsystem; cache
protected by a capacitor pack and Compact Flash memory; host, expansion,
and management ports; and midplane connectivity. If a controller enclosure
contains redundant controller modules, the upper one is designated A and the
lower one is designated B.
copy on write (COW)

A technique for maintaining a point in time copy of a collection of data by
copying only data that is modified after the instant of replicate initiation. The
original source data is used to satisfy read requests for both the source data
itself and for the unmodified portion of the point in time copy. (SNIA)
See also snap pool.
CPLD
Complex programmable logic device. A generic term for an integrated circuit
that can be programmed in a laboratory to perform complex functions.
CPU
Central processing unit. The CPU is where most calculations take place, and
the type of CPU in a controller module affects its performance capability. In
FibreCAT SX storage systems CPU is also referred to as the Storage Controller
processor or the RAID controller processor.
DAS
See direct attached storage (DAS).
data host
A host that reads/writes data to the storage system. A data host can be
connected directly to the system (direct attached storage, or DAS) or can be
connected to an external switch that supports multiple data hosts (storage area
network, or SAN).

data mirroring
Data written to one disk drive is simultaneously written to another disk drive. If
one disk fails, the other disk can be used to run the virtual disk and reconstruct
the failed disk. The primary advantage of disk mirroring is 100 percent data
redundancy: since the disk is mirrored, it does not matter if one of the disks fails;
both disks contain the same data at all times and either can act as the opera-
tional disk. The disadvantage of disk mirroring is that it is expensive because
each disk in the virtual disk is duplicated. RAID 1 and 10 use mirroring.
data striping
The storing of sequential blocks of incoming data on all the different disk drives
in a virtual disk. This method of writing data increases virtual disk throughput
because multiple disks are working simultaneously, retrieving and storing. RAID
0, 10, 3, 5 and 50 use striping.
DHCP
Dynamic Host Configuration Protocol
direct attached storage (DAS)

A dedicated storage device that connects directly to one or more servers.
(SNIA)
disk mirroring
See data mirroring.
DMA
Direct Memory Access
drive module
A FRU consisting of a disk drive and drive sled.
dynamic spare
An available disk drive that is used to replace a failed drive in a virtual disk, if
the Dynamic Spares feature is enabled and no vdisk spares or global spares are
designated.
EC
See Expander Controller (EC).
ECC
Error correcting code.
EIA
Enterprise Information Architecture

EMP
See enclosure management processor (EMP).
enclosure
A physical storage device that contains disk drives. If the enclosure contains
integrated RAID controllers it is known as a controller enclosure; otherwise it is
an expansion enclosure.
enclosure management processor (EMP)

A device in the enclosure from which the system can inquire about the
enclosure’s environmental conditions such as temperature, power supply and
fan status, and the presence or absence of disk drives.
Expander Controller (EC)

The processor (located in the SAS expander in each controller module and
expansion module) that is primarily responsible for enclosure management and
SES.
expansion enclosure
An enclosure that contains disk drives and one or two expansion modules.
Expansion enclosures can be attached to a controller enclosure to provide
additional storage capacity. See expansion module.
expansion module
A FRU that contains: host, expansion, and management ports; an Enclosure
Management Processor; and midplane connectivity. If a system contains
redundant expansion modules, the upper one is designated A and the lower one
is designated B.
expansion enclosure
An enclosure that contains disk drives and one or two expansion modules. See
expansion module.
fabric
A Fibre Channel switch or two or more Fibre Channel switches interconnected
in such a way that data can be physically transmitted between any two N_Ports
on any of the switches. (SNIA)
fabric port (F_Port)

An F_Port that can support an attached arbitrated loop. An FL_Port on a loop
has the AL_PA hex '00' and is the gateway to the fabric for NL_Ports on a loop.

fabric switch
A Fabric switch functions as a routing engine that actively directs data transfer
from source to destination and arbitrates every connection. Bandwidth per node
via a Fabric switch remains constant when more nodes are added, and a node
on a switch port uses a data path of up to 100 MByte/sec to send or receive
data.
fabric-loop port (FL_Port)

An F_Port can support an attached arbitrated loop. An FL_Port on a loop has
the AL_PA hex'00', giving the fabric highest priority access to the loop. An
FL_Port is the gateway to the fabric for NL_Ports on a loop.
failback
See recovery.
failover
In an active-active configuration, failover is the act of temporarily transferring
ownership of controller resources from a failed controller to a surviving
controller. The resources include virtual disks, cache data, host ID information,
and LUNs and WWNs. See also recovery.
fault tolerance
The capacity to cope with internal hardware problems without interrupting the
system’s data availability, often by using backup systems brought online when
a failure is detected. Many systems provide fault tolerance by using RAID archi-
tecture to give protection against loss of data when a single disk drive fails.
Using RAID 1, 3, 5, 10, or 50 techniques, the RAID controller can reconstruct
data from a failed disk drive and write it to a spare or replacement disk drive.
fault-tolerant virtual disk

A virtual disk that provides protection of data in the event of a single disk drive
failure by employing RAID 1, 10, 3, 5, or 50.
FC
See Fibre Channel (FC).
FC-AL
See Fibre Channel-Arbitrated Loop (FC-AL).
Fibre Channel (FC)

A set of standards for a serial I/O bus capable of transferring data between two
ports at up to 100 MByte/sec, with standards proposals to go to higher speeds.
Fibre Channel supports point-to-point*, arbitrated loop, and switched topol-

ogies. Fibre Channel was completely developed through industry cooperation,

unlike SCSI, which was developed by a vendor and submitted for standard-
ization after the fact. (SNIA)
*: FC point-to-point Topology was not tested by Fujitsu and it is not recom-
mended to use point-to-point topology. FibreCAT SX100 point-to-point
configurations are not supported.
Fibre Channel-Arbitrated Loop (FC-AL)

A form of Fibre Channel network in which up to 126 nodes are connected in a
loop topology, with each node's L_Port transmitter connecting to the L_Port
receiver of the node to its logical right. Nodes connected to a Fibre Channel
Arbitrated Loop arbitrate for the single transmission that can occur on the loop
at any instant using a Fibre Channel Arbitrated Loop protocol that is different
from Fibre Channel switched and point-to-point* protocols. An arbitrated loop
may be private (no fabric connection) or public (attached to a fabric by an
FL_Port). (SNIA)
field-replaceable unit (FRU)

An assembly component that is designed to be replaced on site, without the
system having to be returned to the manufacturer for repair.
FRU
See field-replaceable unit (FRU).
FSM
FibreCAT SX Manager comprising both a WBI and a CLI.
GByte (GB)
Gigabyte. Equivalent to 1000 Kbyte for data storage and statistics, or 1024
Kbyte for memory.
global spare
A spare disk drive that is available to all virtual disks in a system.
HBA
See host bus adapter (HBA).
HIM
Host interface module.

host bus adapter (HBA)

An I/O adapter that connects a host I/O bus to a computer’s memory system.
(SNIA)
host port
A host-interface port on a controller module or an expansion module.
host port interconnect

A dual-controller Fibre Channel enclosure includes host port interconnect
circuitry which can be used to connect the host ports on the upper controller
module to those on the lower controller module. When enabled (set to Intercon-
nected), the port interconnect gives each host access to all the volumes
assigned to both controllers and makes it possible to create a redundant config-
uration without using an external FC switch. The port interconnect should only
be enabled when the system is used in direct attached configurations. When
using a switch attached configuration, the port interconnect must be disabled
(set to Straight-through).
hot swap
The ability to remove and replace a FRU while the system is powered on and
operational.
in-band management
Transmission of a protocol other than the primary data protocol over the same
medium as the primary data protocol. Management protocols are a common
example of in-band transmission. (SNIA)
independent cache performance mode (ICPM)

An operating mode in which a pair of controllers can process host I/Os and
share disk channels but cannot fail over and assume responsibilities of a failed
controller, because no mirroring of write-back cache occurs.
initialization
The process of writing a specific pattern to all data blocks on all disk drives in a
virtual disk. This process overwrites and destroys existing data on the disk
drives and the virtual disk. Initialization is required to make the entire virtual disk
consistent at the onset. Initialization ensures that virtual-disk verifications
performed in the future are executed correctly.
I/O
Input/output.
I/O module (IOM)

See controller module and expansion module.

IP
Internet Protocol
IQN
iSCSI Qualified Name.
Format: iqn.yyyy-mm.{reversed domain name}
(e.g. iqn.2001-04.com.acme:storage.tape.sys1.xyz)
IQN addresses are the most common format. They are qualified by a date
(yyyy-mm) because domain names can expire or be acquired by another entity.
iSCSI
Internet SCSI
JBOD
Just a Bunch of Disks. An expansion enclosure that is directly attached to a
host.
KByte (KB)
Kilobyte. Equivalent to 1000 bytes for data storage and statistics, or 1024 bytes
for memory.
LAN
See local area network (LAN).
leftover drive
A disk drive that contains metadata but is no longer part of a virtual disk.
local area network (LAN)

Local Area Network. A communications infrastructure designed to use
dedicated wiring over a limited distance (typically a diameter of less than five
kilometers) to connect to a large number of intercommunicating nodes. (SNIA)
logical unit number (LUN)

The SCSI identifier of a logical unit with a target. (SNIA)
For example, a LUN identifies the mapping between a volume (logical unit) and
a host port (target).
loop address
Indicates the unique ID of a node in FC loop topology. A loop address is
sometimes referred to as a Loop ID.
loop port (L_Port)

A “Loop” port is capable of performing arbitrated loop functions and protocols.
NL_Ports and FL_Ports are examples of loop-capable ports. (SNIA)

loop topology
See Fibre Channel-Arbitrated Loop (FC-AL).
LUN
See logical unit number (LUN).
management controller (MC)

The processor (located in a controller module) that is primarily responsible for
human-computer interface and computer-computer interface functions, and
interacts with the storage controller.
management host
A workstation with a direct or local connection to the system and that is used to
manage the system.
management information base (MIB)

A database of managed objects accessed by network management protocols.
An SNMP MIB is a set of parameters that an SNMP management station can
query or set in the SNMP agent of a network device (for example, a router).
master volume
A volume that is enabled for snapshots. A master volume must be owned by the
same controller as the associated snap pool.
MByte
Megabyte (MB).
MC
See management controller (MC).
metadata
Data in the first sectors of a disk drive that the system uses to identify virtual
disk members.
MIB
See management information base (MIB).
Network Time Protocol (NTP)

A protocol that enables the storage system’s time and date to be obtained from
a network-attached server, keeping multiple hosts and storage devices
synchronized.

node port (N_Port)

A port on a computer, disk drive, or other device through which the device does
its FC communication.
node-loop port (NL_Port)

An N_Port that can operate on FC-AL topology.
node WWN
See world wide node name (WWNN).
Non-RAID
The RAID level option that can be used for a virtual disk having a single disk
drive and that does not need the data redundancy or performance benefits of
RAID. The capacity of a non-RAID virtual disk equals the capacity of its disk
drive. For fault tolerance, use RAID 0 or above.
NTP
See Network Time Protocol (NTP).
out-of-band management
Method of accessing and managing a system using the RS-232 or Ethernet
connection.
ownership
In an active-active configuration, one controller has ownership of the following
resources: virtual disks and vdisk spares. When a controller fails, the other
controller assumes temporary ownership of its resources.
PHY
Hardware component that converts between digital and analog in the signal
path between the storage controller, expander controller, disk drives, and SAS
ports.
PID
Primary controller identifier number.

point-to-point
Point-to-point* is an alternative to FC-AL topology and is required in some fabric
switch configurations. The controller enclosure supports point-to-point connec-
tions only to fabric ports (F_Ports). Loop topology is appropriate for most fabric
switches, as it provides more flexibility when considering fault-tolerant designs.
port bypass circuit (PBC)

See host port interconnect.
port interconnect
See host port interconnect.
port WWN
See world wide port name (WWPN).
power and cooling module

A FRU that includes an AC power supply and two cooling fans. An enclosure
has two power and cooling modules for failure tolerance and can operate with
only one module.
priority
Priority enables controllers to serve other I/O requests while running jobs
(utilities) such as rebuilding virtual disks. Priority ranges from low, which uses
the controller’s minimum resources, to high, which uses the controller’s
maximum resources.
RAID
Redundant Array of Independent Disks, a family of techniques for managing
multiple disks to deliver desirable cost, data availability, and performance
characteristics to host environments. (SNIA)
RAID controller
See controller.
RAS
Reliability, availability, and serviceability. These headings refer to a variety of
features and initiatives all designed to maximize equipment uptime and mean
time between failures, minimize downtime and the length of time necessary to
repair failures, and eliminate or decrease single points of failure in favor of
redundancy.

rebuild
The regeneration and writing onto one or more replacement disks of all of the
user data and check data from a failed disk in a virtual disk with RAID level 1,
10, 3, 5, and 50. A rebuild can occur while applications are accessing data on
the system’s virtual disks.
recovery
In an active-active configuration, recovery (also known as failback) is the act of
returning ownership of controller resources from a surviving controller to a
previously failed (but now active) controller. The resources include virtual disks,
cache data, host ID information, and LUNs and WWNs.
remote scripting CLI client

A command-line interface (CLI) that enables you to manage the system from a
remote management host. The client communicates with the management
software through a secure out-of-band interface, HTTPS, and provides the
same control and monitoring capability as the browser interface. The client must
be installed on a host that has network access to the system.
rollback
The process of resetting a volume's data to become identical to a snapshot
taken of that volume.
SAN
See Storage Area Network (SAN).
SAS
Serial Attached SCSI
SATA
Serial Advanced Technology Attachment
SC
See storage controller (SC).
SCSI
Small Computer System Interface. A collection of ANSI standards and
proposed standards which define I/O buses primarily intended for connecting
storage subsystems or devices to hosts through host bus adapters. (SNIA)

SCSI Enclosure Services (SES)

An ANSI X3T10 standard for management of environmental factors such as
temperature, power, voltage, etc. (SNIA)
In FibreCAT SX storage systems, SES data is managed by enclosure
management processors (EMPs).
SFP
Small form-factor pluggable connector, used in FC controller module host ports.
With FibreCAT SX storage systems, the SFPs belong to the controller modules
and are not FRUs.
SID
Secondary controller identifier number.
SMART
Self-Monitoring Analysis and Reporting Technology. The industry-standard
reliability prediction indicator for both the IDE/ATA and SCSI hard disk drives.
Hard disk drives with SMART offer early warning of some hard disk failures so
critical data can be protected.
SMI-S
Storage Management Interface Specification
SMTP
Simple Mail Transfer Protocol. A protocol for sending email messages between
servers and from mail clients to mail servers. The messages can then be
retrieved with an email client using either POP or IMAP.
snap pool
A volume that is configured to store snapshot data.
snapshot
A fully usable copy of a defined collection of data that contains an image of the
data as it appeared at the point in time at which the copy was initiated. (SNIA)
SNIA
Storage Networking Industry Association. A not profit trade association of
producers and consumers of storage networking products, whose goal is to
further storage networking technology and applications.

SNMP
Simple Network Management Protocol. An IETF protocol for monitoring and
managing systems and devices in a network. The data being monitored and
managed is defined by a MIB. The functions supported by the protocol are the
request and retrieval of data, the setting or writing of data, and traps that signal
the occurrence of events. (SNIA)
spare
See dynamic spare, global spare, vdisk spare.
standard volume
A volume that is not enabled for snapshots.
standby
See spare.
state
The current operational status of a disk drive, a virtual disk, or controller. A
controller module stores the states of drives, virtual disks, and the controller in
its nonvolatile memory. This information is retained across power interruptions.
Storage Area Network (SAN)

A storage system consisting of storage elements, storage devices, computer
systems, and/or appliances, plus all control software, communicating over a
network. (SNIA)
storage controller (SC)

The processor (located in a controller module) that is primarily responsible for
RAID controller functions. The storage controller is also referred to as the RAID
controller.
storage system
One or more enclosures, referred to in a logical (as opposed to physical) sense.
strip size
See chunk size.
stripe size
The number of data disks in a virtual disk multiplied by the chunk size.
sub-vdisk, subvirtual disk

One of multiple RAID 1 virtual disks across which data is striped to form a RAID
10 virtual disk; or one of multiple RAID 5 virtual disks across which data is
striped to form a RAID 50 virtual disk.

system
See array.
TByte (TB)
Terabyte. Equivalent to 1000 Gbyte for data storage and statistics, or 1024
Gbyte for memory.
TCP/IP
Transmission ControlProtocol/Internet Protocol
topology
The logical layout of the components of a computer system or network and their
interconnections. Topology deals with questions of what components are
directly connected to other components from the standpoint of being able to
communicate. It does not deal with questions of physical location of compo-
nents or interconnecting cables. (SNIA)
trap
A type of SNMP message used to signal that an event has occurred. (SNIA)
UT
Universal Time. A modern time system related to the conventional Greenwich
Mean Time (GMT) used for time zones.
UPS
Uninterruptable Power Supply
vdisk
Abbreviation for virtual disk.
vdisk spare
A disk drive that is marked as a spare to support automatic data rebuilding after
a disk drive associated with a virtual disk fails. For a vdisk spare to take the
place of another disk drive, it must be at least equal in size to the failed disk drive
and all of the virtual disks dependent on the failed disk drive must be
redundant—RAID 1, 10, 3, 5, or 50.
VDS
Virtual Disk Service. An API that enables virtual disks and volumes to be
managed by third-party applications.

verify
A process that checks the integrity of the redundant data on fault-tolerant virtual
disks. For RAID 3, 5, and 50, the verify process recalculates the parity of data
stripes in each of the virtual disk’s RAID stripe sets and compares it with the
stored parity. If a discrepancy is found, an error is reported and the new correct
parity is substituted for the stored parity. For RAID 1 and 10, the verify process
checks for mirror mismatches. If an inconsistency is encountered, data is copied
from the master disk drive to the slave disk drive. If a bad block is encountered
when the parity is regenerated, the data is copied from the other disk drive,
master or slave, to the reporting disk drive reallocating the bad block.
virtual disk
For FibreCAT SX storage systems, a set of disk drives that share a RAID level
and disk type, and across which host data is spread for redundancy or perfor-
mance.
volume
A logical subdivision of a virtual disk. Multiple LUNs can be assigned to the
same volume, one for each host port given access to the volume.
See also standard volume.
volume mapping
The process by which volume permissions (read only, read/write, or none) and
LUNs are assigned to a host port.
WBI
See web based interface (WBI).
web based interface (WBI)

The web based interface that system administrators can use to configure,
monitor, and manage controller enclosures and attached expansion enclosures.
The WBI is accessible from any management host that can access an array
through an out-of-band Ethernet connection.
world wide name (WWN)

A unique 64-bit number assigned by a recognized naming authority (often via
block assignment to a manufacturer) that identifies a node process or node port.
(SNIA)
For FibreCAT SX storage systems derive WWNs from the serial numbers of
controller modules and expansion modules.
world wide node name (WWNN)

A globally unique 64-bit identifier assigned to each Fibre Channel node
process. (SNIA)

world wide port name (WWPN)

A globally unique 64-bit identifier assigned to each Fibre Channel port. (SNIA)
write policy
A cache-writing strategy used to control write operations. The write policy
options are CIFS write-back and write-through cache.
write-back cache
A caching technique in which the completion of a write request is signaled as
soon as the data is in cache, and actual writing to non-volatile media occurs at
a later time. Write-back cache includes an inherent risk that an application will
take some action predicated on the write completion signal, and a system failure
before the data is written to non-volatile media will cause media contents to be
inconsistent with that subsequent action. For this reason, good write-back
cache implementations include mechanisms to preserve cache contents across
system failures (including power failures) and to flush the cache at system
restart time. (SNIA)
This is how FibreCAT SX storage systems operate.
See also write-through cache.
write-through cache
A caching technique in which the completion of a write request is not signaled
until data is safely stored on non-volatile media. Write performance with a write-
through cache is approximately that of a non-cached system, but if the data
written is also held in cache, subsequent read performance may be dramatically
improved. (SNIA)
FibreCAT SX storage systems use write-through cache when write-back cache
is disabled or when cache backup power is not working.
See also write-back cache.

Figures
Figure 1: Components and Indicators on the Front of an Controller Enclosure. . . . . . . . 28
Figure 2: FibreCAT SX60 / SX80 / SX88 Controller Enclosure Ports (FC)

and Power Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 3: FibreCAT SX80 iSCSI Controller Enclosure Ports (FC) and Power Switch . . . 30
Figure 4: FibreCAT SX100 Controller Enclosure Ports (FC) and Power Switch . . . . . . . 30
Figure 5: FibreCAT SX60 / SX80 / SX88 Controller Enclosure (FC) LEDs . . . . . . . . . . . 31
Figure 6: Expansion Enclosure Ports and Power Switch . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 7: Expansion Enclosure LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 8: Single-Controller, Direct Attach Connection to a Single Data Host (iSCSI) . . . 38
Figure 9: Detecting the HIM Model With FibreCAT SX Manager’s WBI

(Example With Two HIM Models 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 10: Detecting the HIM Revision With FibreCAT SX Manager’s WBI
(Example With Two HIM Models 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 11: Minimal Connection to a Single Data Host . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 12: High-Availability, Dual-Controller, Direct Attached Connection

to Dual Data Hosts for Windows and Linux (no VMware support). . . . . . . . . . . . . . . . . . 43
Figure 13: Direct Attached FibreCAT SX (Controller Failover Scenario) . . . . . . . . . . . . . 44
Figure 14: Direct Attached FibreCAT SX (Path Failover Scenario) . . . . . . . . . . . . . . . . . 45
Figure 15: High-Performance, Dual-Controller, Direct Attached Connection

to Dual Data Hosts (no Solaris Support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 16: Four Dual-Port Data Hosts with FibreCAT SX100 . . . . . . . . . . . . . . . . . . . . . 47
Figure 17: Four Dual-Port Data Hosts with FibreCAT SX100 and Failed Controller . . . . 49
Figure 18: iSCSI Storage Presentation During Normal, Active-Active Operation . . . . . . 50
Figure 19: iSCSI Storage Presentation During Failover . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figures
Figure 20: Redundant Connection Through a Single Switch to a Single Data Host . . . . 53
Figure 21: Redundant, High-Availability Connection Through Switches

to Dual Data Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 22: Switch Attached Configuration with Two Switches and Two Hosts. . . . . . . . . 56
Figure 23: Two Dual-Port Data Hosts with FibreCAT SX100 and a Switch
for High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 24: Sliding Rail Kit (A3C40075969) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figure 25: Rack Post Mounting Positions of Two enclosures. . . . . . . . . . . . . . . . . . . . . . 65
Figure 26: Support Bracket for Use in PRIMECENTER Racks . . . . . . . . . . . . . . . . . . . . 65
Figure 27: Mounting the Support Bracket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Figure 28: Mounting the Right Sliding Rail (Front Side of the Rack) . . . . . . . . . . . . . . . . 66
Figure 29: Mounting the Right Sliding Rail (Rear Side of the Rack) . . . . . . . . . . . . . . . . 67
Figure 30: Mounting the Left Sliding Rail (Rear Side of the Rack) . . . . . . . . . . . . . . . . . 67
Figure 31: Mounting Position of a Cage Nut Between the Rail Screws . . . . . . . . . . . . . . 68
Figure 32: Screwing on the Enclosure (Right Side Example) . . . . . . . . . . . . . . . . . . . . . 68
Figure 33: Fault-Tolerant Cabling Connections Between Controller and Expansion

Enclosures (left example: FibreCAT SX60 / SX80 / SX88,
right example: FibreCAT SX80 / SX88) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 34: Non-Fault-Tolerant Cabling Connections Between Controller and Expansion

Enclosures (example: FibreCAT SX80 / SX88) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 35: Cabling Connections Between a FibreCAT SX100 Controller

and 1 / 8 Expansion Enclosure(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Tables
Table 1: Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 2: General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 3: Hard Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 4: Supported RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 5: Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 6: Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 7: Electrical Values per Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 8: Ambient Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 9: Heat Dissipation per Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 10: Dimensions per Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 11: Compliance with Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 12: Installation and Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 13: Dimension and Weight Specification Examples . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 14: Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Table 15: Controller Enclosure Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 16: Controller Enclosure LEDs (Front) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 17: Controller Enclosure Ports and Switches (Back) . . . . . . . . . . . . . . . . . . . . . . . 30
Table 18: Controller Enclosure LEDs (Back, Power and Cooling Module). . . . . . . . . . . . 31
Table 19: Controller Enclosure LEDs (Back, Controller Module) . . . . . . . . . . . . . . . . . . . 32
Table 20: Expansion Enclosure Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 21: Expansion Enclosure Ports and Switches (Back) . . . . . . . . . . . . . . . . . . . . . . 34

Table 22: Expansion Enclosure LEDs (Back, Power and Cooling Module) . . . . . . . . . . . 35

Tables
Table 23: Expansion Enclosure LEDs (Back, Expansion Module) . . . . . . . . . . . . . . . . . . 35
Table 24: Contents of an Enclosure Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Table 25: Host Serial Port Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 26: Terminal Emulator Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 27: Terminal Emulator Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Related Documents and Links
[1] Safety manual
Basic safety information including the handling of racks and rack mount enclosures.
Supported with the hardware as printed manual.
[2] FibreCAT SX Series Quick Start Guide

Overview and references for getting current information; short instructions for installation,
configuration, and administration.
Supported via http://www.ts.fujitsu.com/support/manuals.html
[3] FibreCAT SX Series Operating Manual (the manual in hand)

Installing and configuring hardware.
The latest version of the manual
is available at http://www.ts.fujitsu.com/support/manuals.html
[4] FibreCAT SX Series Best Practices Guide

Recommendations for maximizing reliability, accessibility, and serviceability.
[5] FibreCAT SX Series Administrator’s Guide

Using the FibreCAT SX Manager’s (FSM) web based interface WBI to configure and
manage a system.
[6] FibreCAT SX Manager Command Line Interface (CLI)

Using the FibreCAT SX Manager’s (FSM) command-line interface (CLI) to configure and
manage a system.

Related Documents and Links
[7] FibreCAT SX Series Service Manual

Troubleshooting and servicing a system.
Supported via
https://partners.ts.fujitsu.com/com/service/storage/online/fibrecat_sxxx/
fibrecat%20sx60/service_documents/
(for partners of Fujitsu only; user name and password required)
[8] Late-breaking information not included in the information set

http://www.ts.fujitsu.com/products/storage/disk/fibrecat_sx/index.html
[9] MatrixEP
http://ts.fujitsu.com/matrixep
(for partners of Fujitsu only; user name and password required)
[10] See also the user forum for the FibreCAT SX Series at
http://forum.ts.fujitsu.com/forum/viewforum.php?f=75
[11] The Servicedesk telephone numbers are listed at

http://ts.fujitsu.com/support/servicedesk.html
[12] Latest firmware is available at

http://ts.fujitsu.com/support/downloads.html

Index
A E
adhesive labels on plastic casing parts 21 electrical guidelines 24
altitude range, operating 24 enclosure
array cabling configurations 69
first-time configuration 73 power off 85
test configuration 83 power up 85
test connections 72
C environmental protection 21
cable routing guidelines 26 environmental requirements 24
clearance requirements expansion enclosure
service 23 connect to controller enclosure 69
ventilation 23
CLI F
see command-line interface frequency requirement, input 25
command-line interface
description 8 H
set controller IP address 73 HIM
configuration charts 37 restriction 39
console requirement 26 Host Interface Module
controller enclosure restriction 39
configure host ports 78 humidity range, operating 24
connect to data hosts 41, 52
connect to remote management hosts 37 I
Initiator (iSCSI) 78
D installation safety precautions 61
date IP address
using WBI to set 77 default 8, 76, 77
date and time, set controller 77 set controller via CLI 73
dimensions, enclosure 22 iSCSI initiator timeout value 80
disposal of equipment 21 iSCSI Software Initiator 78
Driver Settings 77
M
management host requirements 26
Model of HIM 39

Index
mpclaim 81 T
MPIO 81 temperature range, operating 24
time
N using WBI to set 77
Native MPIO 81 timeout value for iSCSI initiator 80
notation conventions 10
V
P ventilation requirements 23
packing 21 vibration range, operating 24
physical requirements 22 virtual disks and volumes
placement guidelines 23 create 81
plastic casing parts, adhesive labels 21 view status 83
power cord guidelines 24 voltage requirement, input 25
power requirements, site 25
power, connect AC 72 W
WBI
R logging in 77
radio suppression 20 See web-based interface
recycling, equipment 21 setting date and time 77
restriction system requirements 76
direct connect mode 39 web browser configuration 76
FibreCAT SX60 / SX80 39 web-based interface
returning, equipment 21 configure 76
create virtual disks 81
S description 8, 76
safety instructions 17 log out 84
safety precautions 61 set date and time 77
servermanagercmd 81 test array configuration 83
shock range, operating 24 weight guidelines 23
site planning weight, enclosure 22
console requirement 26 Windows 2008 81
electrical requirements 24 wiring requirements, site 25
environmental 24
environmental requirements 24
management host requirements 26
physical requirements 22
software, system requirements 76
storage system
environmental requirements 24
power off 85
power on 85
structure of the manual 9
system requirements
WBI 76

sx60-100 - Operating Manual PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

sx60-100 - Operating Manual PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

FibreCAT SX Series

Edition August 2009 (Version 3.1, 2009-08-24)

Copyright and Trademarks

This manual is printed

1.1 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 Notes on Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

FibreCAT SX Series Operating Manual

2.8.3 Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3 Hardware, Operating, and Indicator Components . . . . . . . . . . . . . . . . . . 27

3.1 Controller Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 Connecting Hosts / Configurations . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1 Connecting Remote Management Hosts . . . . . . . . . . . . . . . . . . . . . . . 37

FibreCAT SX Series Operating Manual

4.7 Connecting Switch Attached FC Configurations . . . . . . . . . . . . . . . . . . 52

5.1 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6 Configuring a System for the First Time . . . . . . . . . . . . . . . . . . . . . . 73

6.1 Setting the IP Address Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . 73

FibreCAT SX Series Operating Manual

6.9 Creating Virtual Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

7 Powering the System Off and On . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.1 Powering Off the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Glossary and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Related Documents and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

FibreCAT SX Series Operating Manual

1.1 Product Overview

FibreCAT SX Series Operating Manual 7

1.2 Management Software

1.2.1 FibreCAT SX Manager Web-Based Interface

1.2.2 FibreCAT SX Manager Command-Line Interface

8 FibreCAT SX Series Operating Manual

1.3 Target Group of the Manual

1.4 Structure of the Manual

FibreCAT SX Series Operating Manual 9

1.5 Notational Conventions

10 FibreCAT SX Series Operating Manual

1.6 Technical Data

FibreCAT SX Series Operating Manual 11

Supported RAID Levels

12 FibreCAT SX Series Operating Manual

Electrical Values per Enclosure (Maximum Values)

FibreCAT SX Series Operating Manual 13

Ambient Conditions (DIN EN 60721-3-X)

Heat Dissipation per Enclosure

Dimensions per Enclosure

Compliance with Standards

14 FibreCAT SX Series Operating Manual

1.7 Installation and Configuration Checklist

FibreCAT SX Series Operating Manual 15

2.1 Notes on Safety

FibreCAT SX Series Operating Manual 17

18 FibreCAT SX Series Operating Manual

2.2 Electrostatic-sensitive Component Label

FibreCAT SX Series Operating Manual 19

2.4 RFI Suppression

2.5 Notes on Mounting the Rack

2.6 Notes on Transportation

20 FibreCAT SX Series Operating Manual

2.7 Environmental Protection

Environmentally friendly product design and development

Notes on labeling plastic housing parts

Take-back, recycling and disposal

FibreCAT SX Series Operating Manual 21

2.8 Site Requirements