sx60-100 QSG Us 090817

FibreCAT SX Series
Quick Start Guide
Edition August 2009 (Version 3.1, 2009-08-17)
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 fr Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks

Copyright Fujitsu Technology Solutions GmbH 2006 - 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
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1
Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2
Compatibility Check
1.3
Hardware Components and Hard Disk Drive LEDs . . . . . . . . . . . . . . . . . . 8
Overview of Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installing and Cabling FibreCAT Enclosures . . . . . . . . . . . . . . . . . . . . 13
Establishing a Connection to the FibreCAT SX . . . . . . . . . . . . . . . . . . . 17
4.1
Establishing a Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2
Using CLI Commands to Assign an IP Address . . . . . . . . . . . . . . . . . . 17
4.3
Using the FibreCAT SX Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Preparing and Connecting the FibreCAT SX and Servers . . . . . . . . . . . . . 19
5.1
Latest Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.2
Configuring the FC Ports on the FibreCAT SX . . . . . . . . . . . . . . . . . . . 19
5.3
Connecting the FibreCAT SX (FC) to Your Servers Directly . . . . . . . . . . . . 20
5.4
Connecting the FibreCAT SX (FC) to Your Servers Through a Switch (Example)
5.5
Installing MPIO (Windows and FC Only) . . . . . . . . . . . . . . . . . . . . . . . 22
5.6
Install Native MPIO Functionality Under Windows 2008 for FibreCAT SX
FibreCAT SX Series Quick Start Guide
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
21
. . . . 23
Contents
5.7
5.7.1
5.7.2
5.7.3
iSCSI Configurations . . . . . . . . . . . . . . . .
Editing Registry Timeout Values for iSCSI Initiator . .
iSCSI Single-Controller, Direct Attached Configuration
iSCSI Dual Controller, Switch Attached Configuration
5.8
Configuring the Microsoft iSCSI Software Initiator (iSCSI) . . . . . . . . . . . . . 29
5.9
5.9.1
5.9.2
5.9.3
5.9.4
5.9.5
FibreCAT SX100 Configurations . . . . . . . . . . . . . . . . . . . . . . . . .

Single-Controller, Direct Attached, One Single-Port Data Host . . . . . . . . . . .
Single-Controller, Direct Attached, Two Single-Port Data Hosts . . . . . . . . . .
High Availability, Dual-Controller, Direct Attached to One Dual-Port Data Host . . .
High-Availability, Dual-Controller, Direct Attached to Two Dual-Port Data Hosts . .
High-Performance, Dual-Controller, Direct Attached to Two Dual-Port Data Hosts
Non-Fault Tolerant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High Availability, Dual-Controller, Through One Switch to One Dual-Port Data Host
High-Availability, Dual-Controller Through Two Switches to Two or More Dual-Port
Data Hosts Standard Default Configuration for High-Availability . . . . . . . . .
High-Availability, Dual-Controller Through a Switch to Two or More Dual-Port
Data Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High-Availability, Dual-Controller Through a Switch to Two or More Dual-Port
Data Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9.6
5.9.7
5.9.8
5.9.9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
24
24
25
26
31
31
32
33
34
. . 35
. . 36
. . 37
. . 39
. . 40
Using vdisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.2
Manually Creating a Virtual Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.3
Assigning Local Spare Disks to a Virtual Disk
Mapping Volumes to Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.1
Managing the Host List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.2
Adding a Volume-to-host Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.3
Special Considerations for Cluster Configurations . . . . . . . . . . . . . . . . . 49
Using LUNs on Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.1
Using LUNs with Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.2
Troubleshooting LUNs
. . . . . . . . . . . . . . . . . . . 45
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Contents
Understanding, Configuring and Using snapshots . . . . . . . . . . . . . . . . . 53
9.1
Description and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.2
Creating a Snap Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
9.3
Enabling an Existing Volume for Snapshots . . . . . . . . . . . . . . . . . . . . 54
9.4
Defining Master Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9.5
Taking Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.6
Collecting Information About Snapshots . . . . . . . . . . . . . . . . . . . . . . 57
9.7
Mounting and Un-Mounting Snapshots . . . . . . . . . . . . . . . . . . . . . . . 57
9.8
Snap Pool Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10
Using Microsoft Storage Manager for SANs (VDS) . . . . . . . . . . . . . . . . . 61
11
Monitoring FibreCAT SX via ServerView
11.1
SNMP Settings
11.2
Discovering a FibreCAT SX in ServerView . . . . . . . . . . . . . . . . . . . . . 65
11.3
Finding Information on a FibreCAT SX in ServerView . . . . . . . . . . . . . . . 65
11.4
StorMan in Combination with ServerView . . . . . . . . . . . . . . . . . . . . . . 67
12
Managing Users with Access to the System . . . . . . . . . . . . . . . . . . . . 69
. . . . . . . . . . . . . . . . . . . . . . 63
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Related Documents and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
1 Preface
This guide describes how to install and initially configure the following array models:
FibreCAT SX60 Fibre Channel (FC) Controller Enclosure
FibreCAT SX80 iSCSI Controller Enclosure
FibreCAT SX Series SAS Expansion Enclosure
This guide does not apply to the FibreCAT SX40 model which is covered by separate
documents.
1.1 Notational Conventions

Typeface1
Meaning
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
V CAUTION
1
Important information and tips

Reference to hazards that can lead to personal injury, loss of data or
damage to equipment
The settings on your browser might differ from these settings.
Preface
1.2 Compatibility Check

Before you proceed with the FibreCAT SX installation, check the compatibility of the
FibreCAT SX with the server, operating system, Host Bus Adapters and desired features
such as MPIO. This can be done using MatrixEP, a Microsoft Windows program that can be
downloaded from
http://ts.fujitsu.com/matrixep
1.3 Hardware Components and Hard Disk Drive LEDs

In Figure 1 and Figure 2 you see an overview of the hardware components of the
FibreCAT SX with two controlers. The upper controller is controller A. The lower controller
is optional, identical to controller A, and called controller B.
Power switch
Host ports
CLI port
Ethernet port
Expansion port
Figure 1: FibreCAT SX 60 / SX80 / SX88 Rear
The figure above shows a FibreCAT SX60 / SX80 / SX88 model as example. These models
have two FC host ports and one SAS expansion port per controller.
The FibreCAT SX80 iSCSI is eqipped with two Ethernet host ports per controller instead of
the FC host ports.
Preface
Power switch
Host ports
CLI port
Ethernet port
Expansion ports
Figure 2: FibreCAT SX100 Rear
The figure above shows a FibreCAT SX100 model. It has four FC host ports and two SAS
expansion ports per controller.
Drive modules with LEDs

(numbered left to right
by row: 03, 47, 811)
Figure 3: Hard Disk Drives on the Front of an Controller Enclosure
On the front side of an controller or expansion enclosure, each hard disk drive has two
LEDs.
For a detailed overview of the hardware components and LEDs, please consult the
FibreCAT SX Series Operating Manual.
2 Overview of Installation Steps

i
Before installing your FibreCAT SX, make sure you read the supplied Safety manual
and the FibreCAT SX Release Notes at
http://ts.fujitsu.com/products/storage/disk/fibrecat_sx/index.html.
Also consult the installation poster before proceeding with the installation of your
FibreCAT SX.
The installation of your FibreCAT SX consists of the following steps.

Step
Task
Chapter in this Quick

Start Guide
Unpack the FibreCAT SX base enclosure box, and check its contents. Also
unpack and check the FibreCAT SX expansion enclosures if you will be using
these.
Mount the FibreCAT SX base enclosure and optional expansion enclosures in a

rack.
Connect the optional FibreCAT SX expansion enclosures to the base enclosure. Installing and Cabling
FibreCAT Enclosures
on page 13
Switch on the optional expansion enclosures first, then switch on the FibreCAT
SX base enclosure. Switch on the host computer or computers last.
Establish a serial connection between your management workstation and the

FibreCAT SX, and set up the FibreCAT SX IP settings.
Connect the Ethernet port on the FibreCAT SX with your LAN, and open the Webbased Interface, called the FibreCAT SX Manager (FSM).
Using the FSM, apply patches to the FibreCAT SX.
8
9
Establishing a
Connection to the
FibreCAT SX on
page 17
Preparing and
Connecting the
Set the parameters for the FibreCAT SX interconnects.
FibreCAT SX and
Install, connect and configure the (FC or iSCSI) Host Bus Adapter or Adapters in Servers on page 19
your servers.
10
Using the FSM, set the FibreCAT SX port parameters.
11
Connect the FibreCAT SX controllers to your servers and/or

Fibre Channel or iSCSI switches.
12
If you will be using Windows Server: install and setup the SES driver and in case
of path redundancy configuration, install the MPIO DSM tool.
11
Overview of Installation Steps
Step
Task
Chapter in this Quick

Start Guide
13
Build virtual disks.
Using vdisks on
page 41
14
Build volumes.
Mapping Volumes to
Hosts on page 47
15
Assign volumes to servers.
Mapping Volumes to
Hosts on page 47 and
Using LUNs on Hosts
on page 51
12
3 Installing and Cabling FibreCAT Enclosures

Before you switch on the FibreCAT SX, you must connect any additional enclosures. The
three examples in this chapter show the principle of SAS cabling from a contoller enclosure
to the expansin enclosure(s). SAS cabling is the same with FC and iSCSI contoller models.
When you connect FibreCAT SX enclosures, you set up a connection from a "A SAS out"
port to a "A SAS in" port on the expansion enclosure. As shown below, "out" ports are
always on the right side whereas "in" ports are on the left side.
The FibreCAT SX60 can be expanded with one expansion enclosure:
Figure 4: Expanding a FibreCAT SX With One Enclosure
13
Installing and Cabling FibreCAT Enclosures
The FibreCAT SX80, SX88 and SX80 iSCSI support up to four expansion enclosures.
Figure 5: Expanding the FibreCAT SX80 or SX88 or SX80 iSCSI With Two Enclosures
When you install an expansion enclosure, you can plug and unplug cables while the system
is up or down.
As you can see in the illustrations, the connections can be set up in such a way that both
expansion enclosures are directly connected to the base enclosure. The advantage of this
approach is the fact that even after an expansion enclosure fails the other one is still accessible.
14
Figure 6: Expanding the FibreCAT SX80 or SX88 or SX80 iSCSI With Three Enclosures
15
The FibreCAT SX100 supports up to eight expansion enclosures. 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.
Redundant cabling is not supported for FibreCAT SX100.
In
Out
In
Out
In
Out
In
Out
In
Out
In
Out
In
Out
In
Out
Controller B
SAS Expansion Channel:
Enclosure
ID 0
Enclosure
ID 2
Out
In
Controller A
Enclosure
ID 3
Out
In
Out
Enclosure
ID 4
Out
In
In
Enclosure
ID 5
Out
In
Enclosure
ID 1
Enclosure
ID 6
Out
In
Out
Enclosure
ID 7
Out
In
In
Enclosure
ID 8
In
Out
In
Out
Enclosure
ID 1
Controller A
Controller B
SAS Expansion Channel:
Enclosure
ID 0
Figure 7: Expanding the FibreCAT SX100 With up to Eight Enclosures (non-redundant)
16
4 Establishing a Connection to the FibreCAT SX

4.1 Establishing a Serial Connection
The process for establishing a serial connection between the server that will be used for
managing the FibreCAT SX and the FibreCAT SX base enclosure is described in the
FibreCAT SX Series Operating Manual in the section "Setting the IP Address Using the
CLI" in the chapter "Configuring an Array for the First Time".
4.2 Using CLI Commands to Assign an IP Address

The FibreCAT SX uses 10.0.0.1 as its default IP address and 255.255.255.0 as its default
subnet mask. The process for using the serial connection to change this IP address and
subnet mask is described in the FibreCAT SX Series Operating Manual in the section
"Setting the IP Address Using the CLI" in the chapter "Configuring an Array for the First
Time".
4.3 Using the FibreCAT SX Manager

Until you change user names and password, anyone knowing the default user name
and password can access your FibreCAT SX. We strongly recommend that you first
change the default passwords.
Before using the FibreCAT SX Manager web based interface (FSM), 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
Because the FSM uses popup windows to indicate the progress of user-requested
tasks, disable any browser features or tools that block popup windows.
17
Establishing a Connection to the FibreCAT SX
To optimize performance, set your browser to never check for newer versions of stored
pages.
To optimize display, use a color monitor and set its color quality to the highest setting.
For Internet Explorer, to ensure you can navigate beyond the WBI login page, set the
local-intranet security option to medium or medium-low.
To log in to the FSM:

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 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.
To configure the array's date and time, you can connect your FibreCAT SX to an NTP server
or set date and time by yourself.
To set 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 array logs will now have correct timestamps.
18
5 Preparing and Connecting the FibreCAT SX

and Servers
5.1 Latest Product Information
The latest version of the manual is available at
http://ts.fujitsu.com/support/manuals.html
Latest firmware and drivers are available at

http://ts.fujitsu.com/support/downloads.html
For latest FibreCAT SX information browse to

http://ts.fujitsu.com/products/storage/disk/fibrecat_sx/index.html
The latest release information you will find in the MatrixEP:

http://de.ts.fujitsu.com/matrixep
5.2 Configuring the FC Ports on the FibreCAT SX

To configure the Fibre Channel ports on the FibreCAT SX, follow these steps.
In the FSM, click MANAGE.
Click GENERAL CONFIG.
Click host port configuration.
Set the appropriate link speed for all FC ports.
19
Preparing and Connecting the FibreCAT SX and Servers
5.3 Connecting the FibreCAT SX (FC) to Your Servers Directly

This section explains how to connect data hosts to access the FibreCAT SX controller
enclosure directly.
Before you connect data hosts directly to the array, check that fiber optic cables are
available to connect the array to the data host HBAs.
The following cabling examples show a high-availability and a high-performance

configuration. The controller enclosure is equipped with two FC RAID controllers
and the host have two FC HBAs each.
The FibreCAT SX controller enclosure equipped with two FC RAID controllers has four FC
connections, two per controller. To maintain redundancy, connect one data host to both
Controller A and Controller B.
For more detailed regarding the host port configuration, please use the FibreCAT
SX Series Operation Manual.
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.
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 figures
shown in the paragraph "Connecting Data Hosts Directly" in the FibreCAT SX Series
Operating Manual.
20
5.4 Connecting the FibreCAT SX (FC) to Your Servers Through a

Switch (Example)
This configuration (see Figure 8) requires host port interconnect circuitry between controller
modules to be set to Straight-through. The cabling example show a controller and path highavailability 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 have two FC HBAs.
MMF <= 300 m
A+B LUNs
MMF <= 300 m
A+B LUNs
Figure 8: Highly Available Configuration Connected Through Redundant Switches and HBAs
21
5.5 Installing MPIO (Windows and FC Only)

Setting up multiple connections between your server and your FibreCAT SX can help you
improve availability and performance. By default, though, Windows Server recognizes each
connection that it discovers as a separate device. You can implement multipathing, and thus
achieve:
fail-over across connections if a connection disappears
load balancing across connections
Multipathing can be done using different approaches:
Fujitsu MultiPath, available for Windows Server and Linux
Microsoft Multipath I/O (MPIO)
Fujitsu MultiPath is only supported on PRIMERGY servers. Its advantage over MPIO,
though, is greater ease of use through a graphical user interface. For installation and configuration instructions for MultiPath, consult the manual that came with your software, and
check for an updated manual on http://ts.fujitsu.com/support/downloads.html
Also, check out there for a (future) white paper about the use of MultiPath with the FibreCAT
SX.
MPIO is not a product, but a specification and a driver development kit. Vendors such as
Fujitsu use the driver development kit for developing a Device Specific Module (DSM) that
provides the MPIO functionality in Windows 2000 Server, Windows Server 2003 and
Windows Server 2003 R2.
To implement MPIO, follow these steps.
Download the MPIO driver for the FibreCAT SX from

http://ts.fujitsu.com/products/storage/disk/fibrecat_sx/index.html,
Set your product to FibreCAT SX.
Run setup.exe on every server running Windows Server that will connect to your
FibreCAT SX using multipathing. Accept the default settings.
Configure MPIO by running FibreCAT SX MPIO Configuration Settings, which is located in

All Programs, Fujitsu.
This configuration program uses a command line interface. Information about its syntax
can be found by entering help.
Identify the Fibre Channel Host Bus Adapters by entering devinfo. In most cases, you
will see that the FC Host Bus Adapters operate in RoundRobin mode.
In order to load balance traffic across all controllers, type devinfo all weighted.
Type exit to leave the DSMCLI.
In Windows Server Disk Management, your FibreCAT SX will now also show up as
FibreCAT SX Multipath Device.
22
All Fibre Channel ports on the FibreCAT SX must be in loop mode for failover to
happen properly.
5.6 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".
23
5.7 iSCSI Configurations

This section explains how to connect the controller enclosure to data hosts through either
in single controller direct connect mode or dual controller connected through Ethernet
switches. The controller enclosure has four host connections, two per controller.
5.7.1 Editing Registry Timeout Values for iSCSI Initiator
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.
24
5.7.2 iSCSI Single-Controller, Direct Attached Configuration

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.
Figure 9 shows the direct attached configuration for a single data host.
Figure 9: Single-Controller, Direct Attached Connection to a Single Data Host (iSCSI)
Single controller mode is only supported in direct attached configuration. 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.
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.
25
5.7.3 iSCSI Dual Controller, Switch Attached Configuration

Dual controller switch attached configuration is supported and has the highest redundancy
(Dual controller direct connections are not supported). To maintain redundancy, connect
each data host through the switch or switches to both controller A and controller B. Make
sure that link speed settings on switches match those on the controller host ports to which
they are connected. A speed mismatch prevents the host from accessing the storage
system. When using dual controller configuration it is recommended that a multi-pathing
software be used to ensure full controller and path redundancy (see the relevant multipathing documentation)
Figure 10 shows the preferred high-availability dual-controller connection through two
switches to two dual-port data hosts, in which each data host has two Ethernet ports with
each port connected to a different switch.
Figure 10: High-Availability Connection Through Two Switches to Two Dual-Port Data Hosts (iSCSI)
26
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 11: iSCSI Storage Presentation During Normal, Active-Active Operation
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.
The IP addresses of port A0 and B0 have to be in the same subnet. Likewise, the
IP addresses of port A1 and B1 have to be in the same subnet.
27
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 12: iSCSI Storage Presentation During Failover
28
5.8 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.
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.
29
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 multipathing 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.
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.
i
30
For more information, please refer to the "Microsoft iSCSI Software Initiator Version
2.X Users Guide".
5.9 FibreCAT SX100 Configurations

The following configuration examples demonstrate cabling best practices for the specified
connection. The standard default configuration for high-availability is shown in section
High-Availability, Dual-Controller Through Two Switches to Two or More Dual-Port Data
Hosts Standard Default Configuration for High-Availability on page 37.
5.9.1 Single-Controller, Direct Attached, One Single-Port Data Host
Usage: Benefits of 4-Gbit/sec speed and robust storage for video streaming/editing;
individual server systems
Advantage: Easy setup, low-cost
Example Business: Small business with a single server system, video production
Figure 13: Single-Controller, Direct Attached to One Single-Port Data Host
31
5.9.2 Single-Controller, Direct Attached, Two Single-Port Data Hosts
Usage: Individual users have direct access to a file server; users can store all CAD work
on robust storage
Advantage: Easy setup, low-cost
Example Business: Small business, architectural firm
Figure 14: Single-Controller, Direct Attached Connection to Two Single-Port Data Hosts
32
5.9.3 High Availability, Dual-Controller, Direct Attached to One Dual-Port

Data Host
In this configuration, the host has redundant connections to the volumes assigned to each
controller. If a controller were to fail, the host maintains access to all the volumes through
the host port on the surviving controller. This configuration requires that host port interconnects are set to Interconnected.
Usage: File server with fault tolerance
Advantage: Easy setup, low-cost, fault tolerance
Example Business: Small to medium business, legal firm
Port interconnects:
interconnected by FibreCAT SX Manager
A + B LUNs
A + B LUNs
Figure 15: High Availability, Dual-Controller, Direct Attached to One Dual-Port Data Host
33
5.9.4 High-Availability, Dual-Controller, Direct Attached to Two Dual-Port

Data Hosts
In this configuration, both hosts have redundant connections to volumes that are associated
with each of the controllers. If a controller were to fail, the hosts maintain access to all of the
volumes through the hosts ports on the surviving controller. This configuration requires that
host port interconnects are set to Interconnected.
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
Port interconnects:
interconnected by FibreCAT SX Manager
A& B LUNs
A& B LUNs
A& B LUNs
A& B LUNs
Figure 16: High-Availability, Dual-Controller, Direct Attached to Two Dual-Port Data Hosts
i
34
Default volume to host mapping only in cluster configurations. Otherwise volumes

have to be mapped explicitly.
5.9.5 High-Performance, Dual-Controller, Direct Attached to Two Dual-Port

Data Hosts Non-Fault Tolerant
This configuration shows a high-performance connection appropriate for high-bandwidth
applications that do not require failover or path redundancy. Each host has two single-port
FC HBAs or one dual-port FC HBA installed. For each host, one HBA port is connected to
each controller. The host port interconnect is set to Straight-Through. In this configuration,
each host only has access only to the volumes assigned to the controller to which the HBA
is connected.
CAUTION!
If a controller fails, the host loses access to volumes owned by that controller.
Usage: Benefits of 4-Gbit/sec speed and robust storage for video streaming/editing;
individual user systems
Advantage: Easy setup, low-cost, high performance
Example Business: Video production
Figure 17: High-Performance, Dual-Controller, Direct Attached Connection to Two Dual-Port Data Hosts NonFault Tolerant
35
5.9.6 High Availability, Dual-Controller, Through One Switch to One DualPort Data Host
This connection is for configurations in which there is a single switch. It requires that host
port interconnects are set to Straight-through.
Usage: Single switch
Advantage: Low-cost; enables growth of more servers, which provides more applications; enables expansion of user account storage space for files and video
Example Business: Internet Service Provider; Web commerce hosting company
Figure 18: High-Availability, Dual-Controller Connection Through One Switch to One Dual-Port Data Host
36
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.
5.9.7 High-Availability, Dual-Controller Through Two Switches to Two or

More Dual-Port Data Hosts Standard Default Configuration for HighAvailability
This connection represents the standard default configuration for high-availability. The host
port interconnects must be set to Straight-through.
Usage: Cluster servers for fault tolerance of OS and server; dual switches for fault
tolerance of switches; dual controllers for fault tolerance of storage (very high fault
tolerance and also high speed)
Advantage: Achieves higher uptime rate (99% uptime) by eliminating many points of
failure; enables more growth of additional cluster servers; enables more growth of data
storage; offers additional security through switches
Example Business: eCommerce company
37
Figure 19: High-Availability, Dual-Controller Connection Through Two Switches to Two or More Dual-Port Data
Hosts
38
5.9.8 High-Availability, Dual-Controller Through a Switch to Two or More

Dual-Port Data Hosts
Note that the switch is a potential SPOF.
Usage: Web server, multiple hosts handling web queues
Advantage: Low cost; multiple web servers; switch access to allow multiple hosts
Example Business: Mid-size Internet company (Web farm)
Figure 20: High-Availability, Dual-Controller Connection Through a Switch to Two or More Dual-Port Data Hosts
39
5.9.9 High-Availability, Dual-Controller Through a Switch to Two or More

Dual-Port Data Hosts
This configuration enables optimal connectivity for each dual port host because no FC
single path to each controller is shared between the two hosts.
Usage: High level of security; file server; web server; email server; SQL server
Advantage: Switch access allow multiple hosts; switch adds extra security with zoning
on storage ports, which allows volumes to be mapped to specific zones
Business: Government (City Chamber of Commerce)
Figure 21: High-Availability, Dual-Controller Connection Through a Switch to Two or More Dual-Port Data Hosts
i
40
6 Using vdisks
6.1 Glossary
A virtual disk ("vdisk") is a set of disks that form a RAID configuration, otherwise known as
an array.
The resilience of a vdisk can be improved by assigning one or more spare disks. The
FibreCAT SX offers a choice between two types of spare disks:
A local spare disk is dedicated to a specific RAID set and will only be used if a disk in
that RAID set fails
A global spare disk will be used to replace the first hard disk that fails in any RAID set.
The process for creating and modifying vdisks is described in Manually Creating a Virtual
Disk on page 43.
A volume is a certain amount of disk capacity on a vdisk, otherwise known as a LUN. To a
large extent, a volume behaves like a partition of a PC hard disk, so it can be formatted with
a file system such as NTFS if you use Microsoft Windows Server 2003. Also, you can assign
a drive letter to it, e.g. E:. However, unlike partitions on a hard disk that is located within a
server or directly attached to it, volumes in a FibreCAT SX can be mapped to multiple hosts,
which is a prerequisite for clustering.
The process for creating and modifying volumes is described in Mapping Volumes to
Hosts on page 47.
A host is a server that will be accessing one or more volumes on a FibreCAT SX. During or
after the creation of a volume, you can decide to what extent it will be mapped (or exposed)
to hosts. Only after a volume has been mapped to a host can it be used by that host. The
relationship between physical disks, virtual disks, volumes and partitions is illustrated in
Figure 22.
41
Using vdisks
Figure 22: Physical and virtual Disks, Volumes and Partitions
The process for creating and modifying volume-to-host mappings is described in Mapping
Volumes to Hosts on page 47.
42
Be very careful when mapping volumes to hosts, and only map hosts to volumes on
an as-needed basis. Superfluous volume-to-host mapping may lead to loss of data,
for instance when a Linux volume is mapped to a Windows host and the volume,
whose format isn't recognized by Windows, is formatted.
Using vdisks
Once a volume has been exposed to a host, it can be used by that host. The process for
using a volume on a host is described Using LUNs on Hosts on page 51
6.2 Manually Creating a Virtual Disk
The FibreCAT SX also allows automatic creation of vdisks. With manual creation
you can exercise more control over the parameters, so this manual only describes
manual creation.
Before you create a vdisk manually, you need to take the following decisions.
Decision
Can be changed later
The name of the virtual disk.
Yes
The RAID level.
No
The disks that you want to use for the vdisk. Yes, RAID sets can be expanded with the
exception of RAID 1 sets
Assign local spare disks to this vdisk.
Yes
Number of volumes on the vdisk
Yes
Size of the volumes on the vdisk
Can be expanded, cannot be reduced
Expose volume(s) to all hosts
Yes
Names of the volume(s)
Yes
Preferred controller for this vdisk
Yes
Follow these steps for creating a vdisk.
The vdisks and volumes on those vdisks can be used right away, even before the
initialization has completed.
Open the Web Management Interface as described in Using the FibreCAT SX

Manager on page 17.
Click Manage.
If not expanded yet, click on Virtual disk config.
Click Create a vdisk.
Under Virtual Disk Creation Method, choose Manual Virtual Disk Creation (Detail-based).
Choose a virtual disk name and the RAID level, then click Create New Virtual Disk. Under
Select Drives to Add to Virtual Disk, select the drives that you want to include in this vdisk.
43
Using vdisks
Click Calculate Virtual Disk Size in order to check the net capacity that this selection will
provide.
Decide whether or not to assign dedicated spare drives to this vdisk.
Click Continue.
Choose an initial number of volumes on this new vdisk.
Set Create Volume of Equal Size to No.
Set Expose Volumes to All Hosts to No.
Accept the default choice for Automatically assign LUNs.
Set your choice for Would you like to name your volumes to No.
44
Don't change the default block size. Doing so will degrade performance in most
cases. Only change the block size if you have explicit instructions.
Click Create Virtual Disk.
Set names for the volumes.
Click Add Volumes to start the creation of the vdisk and volumes.
Using vdisks
6.3 Assigning Local Spare Disks to a Virtual Disk

To assign one or more local spare disks to a vdisk, follow these steps.
In the main menu of the FSM, choose Manage.
Click VIRTUAL DISK CONFIG.
Click Global Spares Menu.
By default, the Show global spares screen will be shown. Global spares are shown using
the color grey.
Click Add Global Spares.
In the box Select Drives to Add as Global Spares, select the disk or disks that you want to
use as global spares.
Click Add Global Spares.
When you change ownership of a virtual disk, the volume-to-host mappings for to
the virtual disk's volumes become invalid. After changing ownership, you must
reassign volumes to hosts before the volumes can be used. Assigning volumes to
hosts is covered in Mapping Volumes to Hosts on page 47.
45
7 Mapping Volumes to Hosts

You can manage which host computers have access to each volume. You do this by associating the volume with selected host computers' initiator ports, selected target ports on the
array, or both; and setting access privileges.
The host computer port can be an HBA (or part of a dual port HBA) on the host, or a port
on a switch that is configured to present the host computer. The HBA or switch is identified
by a port WWN (World Wide Name) or IQN (iSCSI Qualified Name).
Access privileges are read-write, read-only, and none (no access).
7.1 Managing the Host List

Instead of referring to a host's WWN or IQN, it is easier to give each host (or of the host has
multiple ports: each port on the host) a host name.
To assign a port nickname to a port, follow these steps.
In the main menu of the FSM, click Manage.
Click VOLUME MANAGEMENT.
Click volume mapping.
Click manage host lists.
In the box Global Host Port List, you see the WWN or IQN of each port that has been
found in the infrastructure to which you connected the FibreCAT SX. Enter a port
nickname, then click Edit Name.
Consider using descriptive names such as "Exch_BER_port_1" and

"Exch_BER_port_2" for the two ports in your Exchange mail server in Berlin, or
"SQL_node_1A" and "SQL_node_2A" for two of the ports in a SQL Server
cluster.
47
Mapping Volumes to Hosts
You will only see WWNs or IQNs if the FibreCAT SX has already been
connected and can actually see the ports. If for instance you have set up zones
on your switch and then assigned the FibreCAT SX to a specific zone, only the
ports in the same zone will be shown. If the WWNs/WWPNs or IQNs don't show
up automatically, they can be added manually as described in the next step.
If the port that you want to name does not appear in the Global Host Port List, you can
enter the port WWN and the port nickname in the box Add Port to Global Host Port List,
and then click Add New Port. The port will be added to the Global Host Port List.
7.2 Adding a Volume-to-host Mapping
In this section, "host" refers to port on a server or switch. If you want to access a
volume through multiple ports, e.g. for setting up MPIO, you must map the volume
to each port. This is illustrated in Figure 23.
Figure 23: LUN Mapping to Host Ports
48
Mapping Volumes to Hosts
Follow these steps to map a volume to a host or port.
Click volume mapping.
Click map hosts to volume.
In the box Select a virtual disk to view volume information, select the virtual disk where the
volume that you want to map to one or more hosts is located.
In the box Volume Menu for the selected vdisk, you can see which volume is about to be
mapped ("Selected X" is shown at the left of this volume). Change this selection by
clicking on volume that you want to map.
In the box Map Host or Default, enter the host WWN or IQN and/or host name, the LUN
and Port 0 Access and Port 1 Access. LUN or logical unit is a number assigned to a
logical unit (0-127).
You must set the same value to Port 0 Access and Port 1 Access.
Each host port on the server expects to see unique LUNs, so avoid duplicate LUNs.
Click Map Host or Default.
Host names other than Default are only shown if you set port nicknames. Setting
port nicknames makes it easier to identify ports on servers and switches. The
process for setting and changing port nicknames is described in section Managing
the Host List on page 47.
If you choose Default for Host WWN or Host Name, the volume will be visible to all
servers. This may jeopardize security and reliability. We therefore recommend that
you only expose a volume to the host or hosts that need access.
7.3 Special Considerations for Cluster Configurations

In a cluster configuration, the shared disks must be visible to all cluster nodes using the
same LUNs. No other special requirements exist. Consult the documentation of the
clustering software for vendor-specific considerations.
49
8 Using LUNs on Hosts

8.1 Using LUNs with Windows Server
Verify that your combination of Host Bus Adapter, operating system, server and
desired features is supported before you proceed.
To start using a volume on a Windows server, follow these steps.
On the Windows Server, start the tool for managing your Host Bus Adapter (for FC
configurations: HBAnywhere if you use an Emulex controller, SANsurfer if you use a
QLogic controller).
Run a discovery cycle after assigning or reassigning a volume to this server. In HBAnywhere, this is done by clicking View, then Start discovery cycle. You should now see the
LUN that you associated with the volume.
In some cases HBAnywhere does not show new LUNs after a discovery cycle.
Restarting HBAnywhere is then usually sufficient.
When the new LUN shows up, then use the Windows Device Manager for discovering the
new disk. To do so, follow these steps.
Click Start.
Click Administrative Tools.
Click Computer Management.
Expand System Tools.
Click Device Manager.
Expand Disk Drives.
For every FibreCAT SX volume that has been mapped to this server, you will now see
an entry FibreCAT_SX1 SCSI Disk Device. Right-click on each disk, and click Properties.
Open the tab General.
The Location field shows the LUN (you may have to scroll right to see the LUN).
51
Using LUNs on Hosts
If the LUN that you have exposed does not yet appear, right-click on Disk Drives, then
click Scan for hardware changes.
If the new LUN does not appear in the list, use the troubleshooting checklist that
you will find in Troubleshooting LUNs on page 52.
Within Computer Management, expand Storage.
Click Disk Management.
New LUNs will be shown as Disk [n], Unknown, [size], Not initialized.
Continue configuring and using the new disks as you would with any other newly added
disks, i.e. initialize, partition and format.
The word Volume is not related to the same word in the context of the
FibreCAT SX.
8.2 Troubleshooting LUNs

If the FibreCAT SX LUN is not visible on the server, check the following.
52
Check your host mapping settings. Did you use the correct WWN or host name for the
volume? Did you use a LUN that is not already being used on the server? Did you
choose the same value for Port 0 Access and Port 1 Access, i.e. read-only or
read+write?
Check your cabling as described in Installing and Cabling FibreCAT Enclosures on

page 13.
Check your settings in HBAnywhere or SANsurfer. For instance, the speed set in the
FibreCAT SX must be the same as the speed set for the port to which it is connected
on the switch or on the server. Read Configuring the FC Ports on the FibreCAT SX on
page 19 for details.
Check the software prerequisites as needed according to the latest FibreCAT SX information at
Consider restarting your server.
If you have replaced your HBA you have to modify the volume-mapping accordingly.
9 Understanding, Configuring and Using

snapshots
i
Before you start using snapshots, consider reading the white paper "Data
Protection with FibreCAT SX Snapshots", which you can download from
9.1 Description and Best Practices

Snapshot services enable you to create and save snapshots of a volume, where each
snapshot preserves the volume's data state at the point in time when the snapshot was
created.
Snapshots can be taken of master volumes only. A master volume is a volume that has
been enabled for snapshots. You can either create a master volume directly (section
Defining Master Volumes on page 55) or convert a standard volume to a master volume
(section Enabling an Existing Volume for Snapshots on page 54).
Each master volume is associated with a single snap pool in which snapshot data is stored.
Multiple master volumes can share the same snap pool. A snap pool and all associated
master volumes must be owned by the same controller. The process for creating a snap
pool is described in section Creating a Snap Pool on page 54.
A snapshot is a virtual volume. While really a set of pointers to a portion of the snap pool,
a snapshot behaves like a volume in that it can be mapped to data hosts and the mapping
can be assigned a LUN and be made accessible as read-only or read/write, depending on
the intended purpose of the snapshot.
You can rollback (revert) the data in a master volume to the data that existed when a
specified snapshot was created. You can also specify whether to automatically re-map the
master volume if it is already mapped.
53
Understanding, Configuring and Using snapshots
9.2 Creating a Snap Pool

Snapshots are stored into a snap pool, a volume that is only used for this purpose. To create
a snap pool, follow these steps.
Click snapshot services.
Click create snap pool.
In the box Select a virtual disk to view volume information, click on the vdisk where you want
to store the snapshots for this controller. Your choice will be confirmed by means of a
blue box around the vdisk.
In the box Create Snap Pool, enter the Snap Pool Size and the Snap Pool Name. Next, click
Create Snap Pool. In the box Volume Menu for this vdisk, the snap pool will be shown in
blue.
Consider setting the size of the snap pool to 10% of the capacity of the volumes of
which snapshots will be taken. You can increase the size of the snapshot pool later,
but you cannot decrease it.
If you have a FibreCAT SX with two controllers, repeat this process for the other
controller. To do so, select a vdisk for which you set the other controller as the
preferred controller.
9.3 Enabling an Existing Volume for Snapshots
Before you can enable a volume for snapshots, you must create a snap pool for the
preferred controller of the vdisk where the volume is located. Please refer to section
Creating a Snap Pool on page 54 for the process of creating a snap pool.
To enable an existing volume for snapshots, follow these steps.
54
Click snapshot-enable volume.
In the box Select a virtual disk to view volume information, click on the vdisk where the
volume that you want to snapshot-enable is located.
clicking on volume that you want to snapshot-enable.
In the box Convert to Master Volume for the volume that you are about to snapshotenable, select the snap pool that you want to use. Next, click Convert to Master Volume.
A volume that is snapshot-enabled is shown in orange in the Volume Menu.
9.4 Defining Master Volumes

Instead of first creating a volume and then snapshot-enable it, you can combine these
actions by defining a master volume.
Before you can build a master volume, you must create a snap pool for the preferred
controller of the vdisk where the master volume will be located. Please refer to
section Creating a Snap Pool on page 54 for the process of creating a snap pool.
To define a master volume, follow these steps.
Click create master volume in the manage menu at the left side of the screen.
In the box Create Master Volume on Virtual Disk, select a snap pool, enter a volume size,
enter a volume name and enter a default LUN. Next, click Create Master Volume.
55
9.5 Taking Snapshots

To take a snapshot, follow these steps.
Click take snapshot.
volume of which you want to make a snapshot is located.
In the box Volume Menu for the selected vdisk, you can see for which volume you are
about to create a snapshot ("Selected X" is shown at the left of this volume). Change
this selection by clicking on the volume of which you want to take a snapshot.
You can only take a snapshot of a master volume, i.e. a volume that has been
snapshot-enabled. The type of such as volume is listed as Master volume in the
volume menu. Refer to section Enabling an Existing Volume for Snapshots on
page 54 for snapshot-enabling standard volumes (volumes that have not yet
been snapshot-enabled).
In the box Enable snapshot, enter a descriptive name of your snapshot, then click Take
snapshot. Your snapshot will be listed in the Volume menu.
Consider including the date and time that you take a snapshot. This will make it
easier to select the right snapshot when rolling back a volume.
As standard, the FibreCAT SX60 allows two snapshots per controller. The
FibreCAT SX80, SX88, SX 100 and SX80 iSCSI allow four snapshots per
controller. The ability to retain more snapshots can be obtained. The maximum
number of snapshots may change in future releases of the FibreCAT SX. Check
the FibreCAT SX Release Notes for the actual number.
Some applications like relational database management systems are often
used with multiple volumes, e.g. separate volumes for the database itself and
for the transaction log. If this is the case in your infrastructure, you should
synchronize the snapshot creation of all volumes. This can be done by using a
VSS-aware backup application. If you don't have such an application, this can
be done through the CLI by entering the following command:
create snapshots master-volumes [master-volumes] [snapshot names]
56
For example, if your application uses volumes Vdisk1V1 and Vdisk1V2, you
might enter the following command:
create snapshots master-volumes Vdisk1V1,Vdisk1V2 Snap1,Snap2
9.6 Collecting Information About Snapshots
This feature is very important because it is the only way to learn about the date and
time that a snapshot was taken.
To collect information about snapshots, follow these steps.
Click snapshot overview.
snapshot volume is located.
In the box Volume Menu for the selected vdisk, you can see for which volume you see
snapshot information ("Selected X" is shown at the left of this volume). Change this
selection by clicking on the snapshot volume.
In the box Volume status, you see all information related to this snapshot.
9.7 Mounting and Un-Mounting Snapshots
Visit
where you can download a white paper about integration between CA BrightStor
ARCserve and FibreCAT SX snapshots.
57
9.8 Snap Pool Policies

The total size of the snapshots cannot exceed the size of the snap pool. Your FibreCAT SX
allows you to determine what should happen if this is about to happen by means of three
snap-pool policies.
1. The first policy is the warning policy. This is the utilization (total size of the snapshots
divided by the snap pool size) at which you will receive a warning. You can set the utilization.
2. The second policy is the error policy. You can determine which action should be taken,
and at which utilization this should happen.
3. The third policy is the critical policy. You can determine which action should be taken if
the utilization reaches 99%.
The actions that can be taken are:
Action
Available for Available for

Warning Policy Error Policy
Available for
Critical Policy
Notify only
Delete oldest snapshots
Delete snapshots
Invalidate snapshots
Halt writes
Repeat this procedure for every snap pool unless you accept the default settings.
To set snap pool policies, follow these steps.
58
Click set snap-pool policy.
In the box Select a virtual disk to view volume information, click on the vdisk where the snap
pool for which you want to set the policy is located.
clicking on snap pool for which you want to set a policy.
In the box Change Policy Configuration, set the Warning Policy, i.e. the utilization of the
snap pool at which you want to be notified.
In the same box, set the Error Policy, i.e. the utilization of the snap pool at which an
automated action such as deletion of the oldest snapshot should happen. Also, set the
action.
In the same box, set the Critical Policy, i.e. the action that should be taken automatically
if the snap pool reaches 99% utilization.
Click Set Policy & Threshold.
59
10 Using Microsoft Storage Manager for SANs

(VDS)
i
As an alternative to the FibreCAT SX Manager you can use the Mircosoft Storage
Manager for SANs to configure the vdisks and volumes on your FibreCAT SX.
Required for this kind of configuration is the installation of the VDS provider and the
CAPI proxy.
One of the tools that use VDS is Microsoft Storage Manager for SANs, which is included in
Windows Server 2003 R2. Storage Manager for SANs allows the creation and modification
of virtual disks and volumes, and provides LUN mapping. Since it relies on VDS you don't
have to know the specifics of the FibreCAT SX in order to carry out these tasks.
To install Storage Manager, follow these steps.
Install the VDS Provider and CAPI Provider on the server that will be used for managing
the FibreCAT SX as needed according to the latest FibreCAT SX information at
Click Start.
Click Control Panel.
Click Add or Remove Programs.
Click Add/Remove Windows Components.
Click on Management and Monitoring Tools.
Click on Details.
Select Storage Manager for SANs.
Click OK.
Click Next.
To use Storage Manager for SANs, follow these steps.
Click Start.
Click Administrative Tools.
Click Storage Manager for SANs.
61
Using Microsoft Storage Manager for SANs (VDS)
Use Create LUN for creating a virtual disk with a volume (here called LUN) on the
FibreCAT SX.
Use Assign LUN to expose the volume (here called LUN) to one or more servers.
The other actions (Delete LUN, Extend LUN, Rename LUN and Unassign LUN) are selfexplanatory.
62
You can only create volumes (here called LUNs) on free disks in the FibreCAT SX.
For assigning local or global spare disks, using other RAID levels and other
advanced functions you must use the FSM (FibreCAT SX Manager) or the CLI.
11 Monitoring FibreCAT SX via ServerView

i
FibreCAT SX60 / SX80 / SX88 / SX100 is supported by ServerView 4.20.11 or later.

FibreCAT SX80 iSCSI is not integrated in ServerView.
11.1 SNMP Settings

To configure the FibreCAT SX SNMP settings, follow these steps.
Click EVENT NOTIFICATION.
Click SNMP configuration.
Enter the IP address of your ServerView management server in the field SNMP Trap
Host IP Address.
If you deploy multiple ServerView management servers, consider entering the IP

addresses of a second server in SNMP Trap Host IP Address 2 and of a third server in
SNMP Trap Host IP Address 3.
Set SNMP Traps Enable to Yes.
Click Change SNMP Traps Configuration.
By default, the FibreCAT SX uses the SNMP community Public as its read community and
Private as its write community. To change this, follow these steps.
Open the Command Line Interface and log in as described in Using CLI Commands to
Assign an IP Address on page 17.
Enter show snmp-parameters. The output is:

SNMP
---SNMP: enabled
SNMP Filter: Critical
SNMP Trap Host IP1: 10.0.0.3
SNMP read community: public
SNMP write community: private
63
In this example, the IP address of the ServerView management server was

changed to 10.0.0.3 as described earlier in this section, and filtering was set to
critical as described later on in this section.
To change the SNMP read community, enter the command

set snmp-parameters read-community [YourReadCommunity]
e. g.
snmp-parameters read-community ServerView
To change the SNMP write community, enter the command

set snmp-parameters write-community [YourWriteCommunity]
e.g.
snmp-parameters write-community ServerView
Check your new settings by typing show snmp-parameters.
Leave the Command Line Interface by entering the command exit.
Next, determine to what extent you want to monitor your FibreCAT SX with ServerView
using the following steps.
64
Click EVENT NOTIFICATION.
Click SNMP configuration.
Click notification summary.
Make sure that Notification Enabled in the column SNMP Traps is set to Enable.
Critical events are events that require operator intervention. We recommend that you
enable this setting.
Warning events are events that should be looked at. They may signal preventative
action to perform. We recommend that you enable this setting.
Informational events are events that are purely informational; no action required.
Consider enabling this setting initially and switch it off later if you feel that you no longer
need this level of monitoring and alerting.
Click Change Notification Settings.
Verify that the message Your change was successful is shown at the top of the screen.
11.2 Discovering a FibreCAT SX in ServerView

After you have configured the SNMP settings of your FibreCAT SX as described in
paragraph 10.1, you need to discover the FibreCAT SX in ServerView in order to start
monitoring.
To discover a FibreCAT SX in ServerView, follow these steps.
Open the ServerView server list by browsing to your ServerView Management Server,
e.g. by browsing from your PC to http://<yourserver>/serverview.
Right-click anywhere in the server browser or server list, and click Add new server.
Leave the type of device (underneath the Apply button) to Automatic.
In the tab Server Address, enter the IP address of your FibreCAT SX, then click Search.
ServerView should then find your FibreCAT SX.
Open the tab Network/SNMP, and set the SNMP community name.
Close the Browser screen.
11.3 Finding Information on a FibreCAT SX in ServerView

To find information on a FibreCAT SX in ServerView, follow these steps.
Open the ServerView S2 management console. If the FibreCAT SX was discovered by

ServerView, as discussed in Discovering a FibreCAT SX in ServerView on page 65,
the screen should look like Figure 24.
In the ServerList screen, you can click on the name of the FibreCAT SX, which is shown
as a hyperlink, to open the FibreCAT SX FSM.
If the FibreCAT SX raised an alarm, you can open the ServerView S2 Alarm Monitor,
which will display a screen similar to the one shown in Figure 25.
If you want to use other monitoring and alerting preferences than you set for your
(PRIMERGY) servers, click on monitoring and configure alarm settings.
65
Figure 24: FibreCAT SX in ServerView Server List
Figure 25: FibreCAT SX Integration with Alarm Service
66
11.4 StorMan in Combination with ServerView

The main scope of StorMan is the Virtualization and dynamic management of Storage.
For FibreCAT SX, StorMan provides extended monitoring capabilities, so ServerView can
display specific information. StorMan is a Fujitsu software middleware tool that provides
LUN provisioning and storage monitoring capabilities. The base technology of StorMan is
the standard SMI-S (Storage Management Initiative Specification), defined and supported
by the SNIA (Storage Networking Industry Association).
The SMI-S Provider for FibreCAT SX Storage is "embedded", it is delivered by default with
the storage array as part of the microcode and enabled by default. This support is available
as of version J110.
Figure 26: FibreCAT SX Integration with Storman
For more information about how to install StorMan please visit:

http://download.ts.fujitsu.com/Prim_SupportCD/start.html
67
12 Managing Users with Access to the System

Three users can be configured. Each user has a password, an access level, a user type,
and access to one or more array interfaces.
For access level, choose between:
Monitor: enables access to all functions on the Monitor menu.
Manage: enables access to all functions on the Monitor and Manage menus.
Only one Manage-level user and up to five Monitor-level users can be logged in
concurrently. SX Manager distinguishes users by their IP addresses. If you log in to
SX Manager using multiple browser instances on the same management host, SX
Manager considers all instances as a single user; actions you take in one instance
are reflected in the other instances on the same host. Do not log in more than once
from the same host.
For user type, choose between:
Standard: enables access to most functions.
Advanced: standard user rights plus access to infrequently used administrative

functions.
Diagnostic: advanced user rights plus access to troubleshooting functions for use by
service technicians.
For user interfaces, choose one or more of:
FSM: the web-based interface (FSM, also know as SX Manager)
CLI: the command-line interface
To set users, follow these steps.
In the FSM, click MANAGE.
Click GENERAL CONFIG.
Click user configuration.
To modify a user's configuration, select a user name from the dropdown list and click
Select Username to Modify. The Modify Selected User panel appears.
Change the user name, which can include 16 characters.
69
Managing Users with Access to the System
70
Change the password, which can include 16 characters.
Change the access level.
Enable or disable access to specific interfaces.
Click Update User. When processing is complete, the updated System User List panel
appears.
Figures
Figure 1: FibreCAT SX 60 / SX80 / SX88 Rear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Figure 2: FibreCAT SX100 Rear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 3: Hard Disk Drives on the Front of an Controller Enclosure . . . . . . . . . . . . . . . . . 9
Figure 4: Expanding a FibreCAT SX With One Enclosure. . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 5: Expanding the FibreCAT SX80 or SX88 or SX80 iSCSI
With Two Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 6: Expanding the FibreCAT SX80 or SX88 or SX80 iSCSI
With Three Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 7: Expanding the FibreCAT SX100 With up to Eight Enclosures
(non-redundant) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 8: Highly Available Configuration Connected Through Redundant
Switches and HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 9: Single-Controller, Direct Attached Connection to a Single Data Host (iSCSI) . 25
Figure 10: High-Availability Connection Through Two Switches to Two Dual-Port
Data Hosts (iSCSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 11: iSCSI Storage Presentation During Normal, Active-Active Operation . . . . . . 27
Figure 12: iSCSI Storage Presentation During Failover . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 13: Single-Controller, Direct Attached to One Single-Port Data Host. . . . . . . . . . 31
Figure 14: Single-Controller, Direct Attached Connection to Two Single-Port
Data Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 15: High Availability, Dual-Controller, Direct Attached to One Dual-Port
Data Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 16: High-Availability, Dual-Controller, Direct Attached to Two Dual-Port
Data Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
71
Figures
Figure 17: High-Performance, Dual-Controller, Direct Attached Connection

to Two Dual-Port Data Hosts Non-Fault Tolerant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 18: High-Availability, Dual-Controller Connection Through One Switch
to One Dual-Port Data Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 19: High-Availability, Dual-Controller Connection Through Two Switches
to Two or More Dual-Port Data Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 20: High-Availability, Dual-Controller Connection Through a Switch
Figure 21: High-Availability, Dual-Controller Connection Through a Switch
Figure 22: Physical and virtual Disks, Volumes and Partitions . . . . . . . . . . . . . . . . . . . . 42
Figure 23: LUN Mapping to Host Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 24: FibreCAT SX in ServerView Server List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 25: FibreCAT SX Integration with Alarm Service . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 26: FibreCAT SX Integration with Storman. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
72
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 (the manual in hand)

Overview and references for getting current information; short instructions for installation,
configuration, and administration.
The latest version of the manual is available at
http://ts.fujitsu.com/support/manuals.html
[3]
FibreCAT SX Series Operating Manual

Installing and configuring hardware.
Supported via http://ts.fujitsu.com/support/manuals.html
[4]
FibreCAT SX Series Best Practices Guide

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

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

Using the FibreCAT SX Managers (FSM) command-line interface (CLI) to configure and
manage a system.
73
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/
Pages/default.aspx
(for partners of Fujitsu Technology Solutions only; user name and password required)
[8]
Late-breaking information not included in the information set

[9]
MatrixEP
http://de.ts.fujitsu.com/matrixep
[10]
See also the user forum for the FibreCAT SX Series at

http://forum.ts.fujitsu.com/forum/viewforum.php?f=75
[11]
The Service Desk telephone numbers are listed at

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

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

sx60-100 QSG Us 090817

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

sx60-100 QSG Us 090817

Uploaded by

Copyright:

Available Formats

FibreCAT SX Series

Quick Start Guide

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

Comments Suggestions Corrections

Copyright and Trademarks

This manual is printed

Hardware Components and Hard Disk Drive LEDs . . . . . . . . . . . . . . . . . . 8

Overview of Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing and Cabling FibreCAT Enclosures . . . . . . . . . . . . . . . . . . . . 13

Establishing a Connection to the FibreCAT SX . . . . . . . . . . . . . . . . . . . 17

Establishing a Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Using CLI Commands to Assign an IP Address . . . . . . . . . . . . . . . . . . 17

Using the FibreCAT SX Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Preparing and Connecting the FibreCAT SX and Servers . . . . . . . . . . . . . 19

Latest Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring the FC Ports on the FibreCAT SX . . . . . . . . . . . . . . . . . . . 19

Connecting the FibreCAT SX (FC) to Your Servers Directly . . . . . . . . . . . . 20

Connecting the FibreCAT SX (FC) to Your Servers Through a Switch (Example)

Installing MPIO (Windows and FC Only) . . . . . . . . . . . . . . . . . . . . . . . 22

Install Native MPIO Functionality Under Windows 2008 for FibreCAT SX

FibreCAT SX Series Quick Start Guide

Configuring the Microsoft iSCSI Software Initiator (iSCSI) . . . . . . . . . . . . . 29

FibreCAT SX100 Configurations . . . . . . . . . . . . . . . . . . . . . . . . .

Manually Creating a Virtual Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Assigning Local Spare Disks to a Virtual Disk

Mapping Volumes to Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Managing the Host List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Adding a Volume-to-host Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Special Considerations for Cluster Configurations . . . . . . . . . . . . . . . . . 49

Using LUNs on Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Using LUNs with Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . 51

FibreCAT SX Series Quick Start Guide

Understanding, Configuring and Using snapshots . . . . . . . . . . . . . . . . . 53

Description and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Creating a Snap Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Enabling an Existing Volume for Snapshots . . . . . . . . . . . . . . . . . . . . 54

Defining Master Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Collecting Information About Snapshots . . . . . . . . . . . . . . . . . . . . . . 57

Mounting and Un-Mounting Snapshots . . . . . . . . . . . . . . . . . . . . . . . 57

Snap Pool Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Using Microsoft Storage Manager for SANs (VDS) . . . . . . . . . . . . . . . . . 61

Monitoring FibreCAT SX via ServerView

Discovering a FibreCAT SX in ServerView . . . . . . . . . . . . . . . . . . . . . 65

Finding Information on a FibreCAT SX in ServerView . . . . . . . . . . . . . . . 65

StorMan in Combination with ServerView . . . . . . . . . . . . . . . . . . . . . . 67

Managing Users with Access to the System . . . . . . . . . . . . . . . . . . . . 69

Related Documents and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

FibreCAT SX Series Quick Start Guide

FibreCAT SX60 Fibre Channel (FC) Controller Enclosure

FibreCAT SX80 Fibre Channel (FC) Controller Enclosure

FibreCAT SX88 Fibre Channel (FC) Controller Enclosure

FibreCAT SX100 Fibre Channel (FC) Controller Enclosure

FibreCAT SX80 iSCSI Controller Enclosure

FibreCAT SX Series SAS Expansion Enclosure

1.1 Notational Conventions

Commands and options in syntax descriptions as well as system output

Angle brackets are used to enclose variables which are to be replaced by

References to documents and chapters or sections in this or other documents

Important information and tips

The settings on your browser might differ from these settings.

FibreCAT SX Series Quick Start Guide

1.2 Compatibility Check

1.3 Hardware Components and Hard Disk Drive LEDs