TruCluster 380578-B21 Manual

TruCluster Software Products
Hardware Configuration Technical Update for
Fibre Channel for TruCluster Software Products
Version 1.6
July 2000
Product Version: TruCluster Production Server Software
Version 1.6 and TruCluster Available
Server Software Version 1.6
Operating System and Version: Tru64 UNIX Version 4.0F (with NHD-2)
This technical update is an update to the Fibre Channel information
that is provided in the TruCluster™ Software Products Hardware
Configuration manual (Chapter 6). This update describes how to set
up and maintain the shared Fibre Channel mass storage devices in
a Compaq Tru64™ UNIX TruCluster configuration, including new
information on the use of the Fibre Channel arbitrated loop topology. It
also includes support for the use of the emx manager (emxmgr) utility,
which is part of New Hardware Delivery-2 (NHD-2) Tru64 UNIX Version
4.0F New Hardware Support. You may obtain NHD-2 from the following
URL: http://ftp.service.digital.com/public/unix/v4.0f
Compaq Computer Corporation
Houston, Texas

© 2000 Compaq Computer Corporation
COMPAQ and the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, AlphaServer,
StorageWorks, TruCluster, Tru64, and VMS are trademarks of Compaq Information Technologies Group,
L.P.
Microsoft and Windows are trademarks of Microsoft Corporation. UNIX and The Open Group are
trademarks of The Open Group. All other product names mentioned herein may be trademarks or
registered trademarks of their respective companies.
Confidential computer software. Valid license from Compaq required for possession, use, or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor’s standard commercial license.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information
in this publication is subject to change without notice and is provided "as is" without warranty of any
kind. The entire risk arising out of the use of this information remains with recipient. In no event shall
Compaq be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever
(including without limitation, damages for loss of business profits, business interruption or loss of business
information), even if Compaq has been advised of the possibility of such damages. The foregoing shall
apply regardless of the negligence or other fault of either party and regardless of whether such liability
sounds in contract, negligence, tort, or any other theory of legal liability, and notwithstanding any failure of
essential purpose of any limited remedy.
The limited warranties for Compaq products are exclusively set forth in the documentation accompanying
such products. Nothing herein should be construed as constituting a further or additional warranty.

Contents
About This Technical Update
1 Fibre Channel Overview
1.1 Basic Fibre Channel Terminology .................................. 1–1
1.2 Fibre Channel Topologies ............................................ 1–3
1.2.1 Point-to-Point Topology ......................................... 1–3
1.2.2 Fabric Topology ................................................... 1–4
1.2.3 Arbitrated Loop Topology ....................................... 1–5
1.3 Fibre Channel Topology Comparison .............................. 1–6
1.4 Example Fibre Channel Configurations Supported by the
TruCluster Software Products ...................................... 1–7
1.5 Zoning and Cascaded Switches ..................................... 1–12
1.5.1 Zoning .............................................................. 1–13
1.5.2 Cascaded Switches ............................................... 1–14
2 Fibre Channel Hardware, Requirements, and Restrictions
2.1 Fibre Channel Hardware Supported for Cluster Storage ...... 2–1
2.2 Fibre Channel Requirements and Restrictions .................. 2–1
3 Using the emx Manager (emxmgr) Utility
3.1 Using the emxmgr Utility to Display Fibre Channel Adapter
Information ............................................................ 3–1
3.1.1 Using the emxmgr Utility in an Arbitrated Loop Topology 3–4
3.2 Using the emxmgr Utility to Modify Worldwide
Name-to-Target ID Mapping ........................................ 3–5
3.2.1 Using the emxmgr Utility Interactively ...................... 3–5
3.2.2 Using the emxmgr Utility with a File to Modify Worldwide
Name-to-Target ID Mapping ................................... 3–7
4 Installing Fibre Channel Hardware and Configuring the emx Driver
4.1 Installing and Setting Up the Fibre Channel Switch ........... 4–1
4.1.1 Installing the Switch ............................................ 4–3
4.1.2 Managing the Fibre Channel Switches ....................... 4–3
Contents iii

4.1.2.1 Using the Switch Front Panel ............................. 4–4
4.1.2.2 Setting the Ethernet IP Address and Subnet Mask
from the Front Panel ....................................... 4–4
4.1.2.3 Setting the DS-DSGGB-AA Ethernet IP Address and
Subnet Mask from a PC or Terminal ..................... 4–6
4.1.2.4 Logging In to the Switch with a Telnet Connection .... 4–7
4.1.2.5 Setting the Switch Name via Telnet Session ............ 4–8
4.2 Installing and Setting Up the SWXHB-07 Hub .................. 4–8
4.2.1 Installing the Hub ............................................... 4–9
4.2.2 Determining the Hub Status ................................... 4–9
4.3 Setting Up the HSG80 Array Controller for a Fibre Channel
Cluster .................................................................. 4–10
4.3.1 Setting Up the HSG80 Array Controller for Arbitrated
Loop ................................................................ 4–13
4.4 Obtaining the Worldwide Names of HSG80 Controllers ........ 4–15
4.5 Installing and Configuring the KGPSA PCI-to-Fibre Channel
Adapter Module ....................................................... 4–16
4.5.1 Obtaining the Worldwide Names of KGPSA Adapters ..... 4–16
4.5.2 Installing the KGPSA PCI-to-Fibre Channel Adapter
Module ............................................................. 4–17
4.5.3 Configuring the KGPSA-CA Adapter for Loop Mode ....... 4–17
4.5.4 Configuring the KGPSA Adapter .............................. 4–19
4.6 Configuring the emx Driver for Fibre Channel Operation ..... 4–19
4.6.1 Initial Worldwide Name-to-Target ID Mapping ............. 4–20
4.6.2 Synchronizing the Initial Assignment of Target IDs in a
Cluster ............................................................. 4–20
4.6.3 Remapping Target IDs After Adding or Replacing a Fibre
Channel Device ................................................... 4–22
4.7 Verifying the Fibre Channel Device Configuration .............. 4–25
4.8 Determining the Device Special File Name for a Disk .......... 4–25
5 Troubleshooting and Component Replacement Guidelines
5.1 Failure Behavior of Fibre Channel Components ................. 5–1
5.1.1 Fibre Channel (KGPSA) Adapter Failures ................... 5–1
5.1.2 Fibre Channel Switch Failures ................................ 5–2
5.1.3 Fibre Channel Hub Failures ................................... 5–3
5.1.4 HSG80 RAID Array Controller Failures ..................... 5–3
5.1.5 Disk Failures ..................................................... 5–4
5.2 Requirements and Limitations for Adding Storage ............. 5–4
5.3 Adding and Replacing Fibre Channel Devices ................... 5–5
5.3.1 Adding Disks to an Existing Configuration .................. 5–5
5.3.2 Adding or Moving Storage Units .............................. 5–6
iv Contents

5.3.3 Adding or Replacing a KGPSA Adapter ...................... 5–6
5.3.3.1 Replacing a KGPSA Adapter in a Cluster ............... 5–6
5.3.3.2 Adding a New Fibre Channel Bus to a Cluster ......... 5–8
5.3.4 Adding a Fibre Channel Switch or Hub to the Existing
Configuration ..................................................... 5–9
5.3.5 Adding an Additional RA8000/ESA12000 to an Existing
Cluster ............................................................. 5–9
5.4 Adding or Replacing a Cluster Member in a Fabric
Configuration .......................................................... 5–11
5.4.1 Adding a New Member System ................................ 5–11
5.4.2 Replacing a Cluster Member System ......................... 5–12
A emxmgr Reference Page
emxmgr(8) ......................................................... A–2
Index
Figures
1–1Point-to-Point Topology .............................................. 1–4
1–2Fabric Topology ........................................................ 1–5
1–3Arbitrated Loop Topology ............................................ 1–6
1–4Fibre Channel Single Switch Transparent Failover
Configuration ......................................................... 1–8
1–5Mirroring Storage Units with LSM in a Cluster ................. 1–9
1–6Single Switch Configuration with Full Complement ............ 1–10
1–7Arbitrated Loop Configuration with One Storage Array ....... 1–11
1–8Arbitrated Loop Maximum Configuration ........................ 1–12
1–9A Simple Zoned Configuration ...................................... 1–13
Tables
1–1Fibre Channel Fabric and Arbitrated Loop Comparison ....... 1–7
2–1Fibre Channel Hardware Supported for Cluster Storage ...... 2–1
2–2AlphaServer Systems Supported for Fibre Channel ............ 2–2
4–1Telnet Session Default User Names for Fibre Channel
Switches ................................................................ 4–7
Contents v

About This Technical Update
The material in this technical update provides an update to the information
that is provided in Chapter 6 (Fibre Channel) of the Version 1.6 TruCluster
Software Products Hardware Configuration manual. It also updates the
previous version of this technical update dated 9 February 2000. This update
is required because of new support for Fibre Channel arbitrated loop.
This technical update is valid for Fibre Channel fabric and arbitrated loop
topologies with TruCluster™Software Products Version 1.6 and Tru64™
UNIX Version 4.0F with New Hardware Delivery-2 (NHD-2) (or later)
Tru64 UNIX Version 4.0F New Hardware Support (which includes the emx
manager (emxmgr) utility and support for the DS-KGPSA-CA Fibre Channel
host bus adapter).
Fibre Channel arbitrated loop support requires Tru64 UNIX/TruCluster
Software Products patch kit 4 (duv40fas0004-20000613.tar) in addition
to new hardware support NHD-2 (or later). You may obtain the patch kit
from http://www.support.compaq.com/patches/index.html.
The Version 1.6 TruCluster Software Products Hardware Configuration
manual provides a method of using the /sys/data/emx_data.c file and
a kernel rebuild to synchronize worldwide name-to-target ID mapping in a
fabric topology.
The procedures in this Technical Update use the new emx manager utility
(emxmgr). They provide an easier, more direct method to synchronize
worldwide name-to-target ID mapping. This is the preferred method.
Audience
If you plan to use Fibre Channel hardware in your TruCluster hardware
configuration, read this addendum to the TruCluster Software Products
Hardware Configuration manual.
Organization
This technical update contains five chapters and an appendix:
•Chapter 1: Fibre Channel Overview —Provides a basic overview of
Fibre Channel terminology and topologies, plus example Fibre Channel
cluster configurations.
About This Technical Update vii

•Chapter 2: Fibre Channel Hardware, Requirements, and Restrictions —
Provides information regarding the supported Fibre Channel hardware
and firmware, and the configuration requirements and restrictions.
•Chapter 3: Using the emx Manager (emxmgr) Utility —Provides
instruction on the use of the emxmgr utility.
•Chapter 4: Installing Fibre Channel Hardware and Configuring the
emx Driver —Provides information about installing the Fibre Channel
hardware needed for a TruCluster configuration that accesses storage
over the Fibre Channel.
•Chapter 5: Troubleshooting and Component Replacement Guidelines —
Covers the failure behavior of Fibre Channel components, and how to
add or replace Fibre Channel devices in a cluster configuration.
•Appendix A: emxmgr Reference Page —Describes the emxmgr utility,
including its syntax and options.
Purpose of this Document
This document outlines the setup, administrative, and maintenance
procedures to support the Compaq Tru64 UNIX TruCluster equipment,
including troubleshooting guidelines and instructions for recovery from
various outages that may involve the Fibre Channel subsystems. Outages
of other subsystems, such as network or parallel SCSI devices, are not
considered.
Related Documents
Consult the following documentation to assist you in Fibre Channel storage
configuration and administration:
•KGPSA-BC PCI-to-Optical Fibre Channel Host Bus Adapter User Guide
•64-Bit PCI-to-Fibre Channel Host Bus Adapter User Guide
•64-Bit PCI to Fibre Channel Host Bus Adapter Release Notes for Tru64
UNIX and OpenVMS
•Fibre Channel Storage Hub 7 Installation Guide
•Fibre Channel Storage Hub 7 Rack Mounting Kit Installation Card
•emx_data.c(4) reference page. You can access this documentation from:
http://www.unix.digital.com/faqs/publications/
base_doc/DOCUMENTATION/V40F_HTML/MAN/MAN4/0062____.HTM
•emx(7) reference page. You can access this documentation from:
http://www.unix.digital.com/faqs/publications/
base_doc/DOCUMENTATION/V40F_HTML/MAN/MAN7/0018____.HTM
viii About This Technical Update

_____________________ Note _____________________
There are four underscores ( _ ) after the number in each
of the two preceding URLs.
•emxmgr(8) reference page. The emxmgr reference page is included with
the New Hardware Delivery-2 (NHD-2) Tru64 UNIX Version 4.0F New
Hardware Support, but because no formal documentation is provided
with the NHD-2 release, the refererence page is included in Appendix A
of this update.
See the following Compaq StorageWorks documentation for switch and
HSG80 RAID array controller configuration information:
•Release Notes Compaq StorageWorks HSG80 Array Controller ACS
Version 8.4 for Compaq Tru64 UNIX
•HSG80 Array Controller ACS Version 8.4 Configuration and CLI
Reference Guide
•HSG80 Array Controller ACS Version 8.4 Maintenance and Service Guide
•Release Notes Compaq StorageWorks HSG80 Array Controller ACS
Version 8.5 for Compaq Tru64 UNIX
•HSG80 Array Controller ACS Version 8.5 CLI Reference Guide
•HSG80 Array Controller ACS Version 8.5 Configuration Guide
•Fibre Channel Storage Switch User’s Guide
•SAN Switch 8 Installation and Hardware Guide
•SAN Switch 16 Installation and Hardware Guide
•SAN Switch Fabric Operating System Management Guide
About This Technical Update ix

1
Fibre Channel Overview
Fibre Channel is designed to carry various command sets and their
associated architectures over the same physical interface. Fibre Channel is
primarily a transport medium; therefore, it is independent of the function
for which it is used.
The TruCluster Software Products use the Fibre Channel Protocol (FCP) for
SCSI-3 to use Fibre Channel as the physical interface.
Fibre Channel, with its serial transmission method, overcomes the
limitations of parallel SCSI by providing:
•Data rates of 100 MB/sec, 200 MB/sec, and 400 MB/sec
•Support for multiple protocols
•Better scalability
•Improved reliability, serviceability, and availability
Fibre Channel uses an extremely high transmit clock frequency to achieve
the high data rate. Using optical fibre transmission lines allows the
high-frequency information to be sent up to 70 km, which is the maximum
distance between transmitter and receiver. Copper transmission lines
may be used for shorter distances. (Tru64 UNIX does not support copper
transmission lines.)
______________________ Note _______________________
The TruCluster Software Products support 500 meters between
the KGPSA and the switch or hub, and 500 meters between the
switch or hub and the HSG80 array controller. See Figure 1–4 for
an example cluster configuration.
1.1 Basic Fibre Channel Terminology
This section describes the basic Fibre Channel terminology:
AL_PA The Arbitrated Loop Physical Address (AL_PA) is
used to address nodes on the Fibre Channel loop.
When a node is ready to transmit data, it transmits
Fibre Channel Overview 1–1

Fibre Channel primitive signals that include its
own identifying AL_PA.
Frame All data is transferred in a packet of information
called a frame. A frame is limited to 2112 bytes.
Information that consists of more than 2112 bytes
is divided into multiple frames.
Node The source and destination of a frame. A node
may be a computer system, redundant array of
independent disks (RAID) array controller, or a disk
device. Each node has a 64-bit unique node name
(worldwide name) that is built into the node when it
is manufactured.
N_Port Each node must have at least one Fibre Channel
port from which to send or receive data. This
node port is called an N_Port. Each port has a
64-bit unique port name (worldwide name) that is
built into the node when it is manufactured. An
N_Port is connected directly to another N_Port in a
point-to-point topology. An N_Port is connected to an
F_Port in a fabric topology.
NL_Port In an arbitrated loop topology, information is routed
around a loop. A node port that can operate on the
loop is called an NL_Port (node loop port). The
information is repeated by each NL_Port until it
reaches its destination. Each port has a 64-bit
unique port name (worldwide name) that is built
into the node when it is manufactured.
Fabric A switch, or multiple interconnected switches,
that route frames between the originator node
(transmitter) and destination node (receiver).
Fabrics do not originate nor are they the final
recipient of frames; they pass frames on to the
destination.
F_Port The ports within the fabric (fabric port). The port is
called an F_Port. Each F_Port has a 64-bit unique
port name (worldwide name) that is built into the
node when it is manufactured.
1–2Fibre Channel Overview

FL_Port A fabric port that contains the loop functionality is
called an FL_Port.
Link The physical connection between an N_Port and
another N_Port or between an N_Port and an
F_Port. A link consists of two fibres –one to
transmit information and one to receive information.
The transmit fibre on one node is the receive fibre on
the node at the other end of the link. A link may be
optical fibre, coaxial cable, or shielded twisted pair.
E_Port An expansion port on a switch that connects two
switches in the fabric.
1.2 Fibre Channel Topologies
Fibre Channel supports three different interconnect topologies:
•Point-to-point (Section 1.2.1)
•Fabric (Section 1.2.2)
•Arbitrated loop (Section 1.2.3)
______________________ Note _______________________
You can interconnect an arbitrated loop with fabric, creating
a hybrid configuration. The fabric must have ports with loop
functionality (FL_Ports) to attach an arbitrated loop to the fabric.
Tru64 UNIX does not support hybrid configurations and they are
not discussed in this document.
The following sections discuss these topologies.
1.2.1 Point-to-Point Topology
The point-to-point topology is the simplest of the Fibre Channel topologies.
In a point-to-point topology, one N_Port is connected to another N_Port by a
single link.
Frames require no routing; all frames transmitted by one N_Port are
received by the other N_Port, and in the same order in which they were sent.
Figure 1–1 shows an example of point-to-point topology.
Fibre Channel Overview 1–3

Figure 1–1: Point-to-Point Topology
N_Port N_Port
Transmit
Receive
Node 1 Node 2
Transmit
Receive
ZK-1534U-AI
1.2.2 Fabric Topology
The fabric topology provides more connectivity than point-to-point topology.
The fabric topology allows up to 224 ports to be connected.
The fabric examines the destination address in the frame header and routes
the frame to the destination node.
A fabric may consist of a single switch, or several interconnected
switches. Each switch contains two or more fabric ports (F_Port) that are
interconnected by the fabric switching function, which routes the frame from
one F_Port to another F_Port within the fabric. Communication between
two switches is routed between two expansion ports (E_Port).
When an N_Port is connected to a fabric F_Port, the fabric is responsible for
the assignment of the Fibre Channel address to the N_Port that is attached
to the fabric. The fabric is also responsible for selecting the route that the
frame will take, within the fabric, to be delivered to the destination.
When the fabric consists of multiple switches, the fabric may determine an
alternate route to ensure that a frame gets delivered to its destination.
Figure 1–2 shows an example of fabric topology.
1–4Fibre Channel Overview

Figure 1–2: Fabric Topology
N_Port
Node 1
Node 2
Transmit
Receive
Transmit
Receive
Transmit
Receive
Transmit
Receive
Transmit
Receive
Transmit
Receive
Transmit
Receive
Transmit
Receive
F_Port
Fabric
Node 3
Node 4
F_Port
F_PortF_Port N_Port
N_Port
N_Port
ZK-1536U-AI
1.2.3 Arbitrated Loop Topology
In an arbitrated loop topology, frames are routed around a loop that is set
up by the links between the nodes. The hub maintains loop continuity by
bypassing a node when the node or its cabling fails, when the node is powered
down, or when the node is removed for maintenance. The hub is transparent
to the protocol. It does not consume any Fibre Channel arbitrated loop
addresses so it is not addressable by a Fibre Channel arbitrated loop port.
The nodes arbitrate to gain control (become master) of the loop. After a
node becomes master, the nodes select (by way of setting bits in a bitmask)
their own Arbitrated Loop Physical Address (AL_PA). The AL_PA is used
to address nodes on the loop. The AL_PA is dynamic and can change each
time the loop is initialized, a node is added or removed, or at any other time
that an event causes the membership of the loop to change. When a node is
ready to transmit data, it transmits Fibre Channel primitive signals that
include its own identifying AL_PA.
In the arbitrated loop topology, a node port is called an NL_Port (node loop
port), and a fabric port is called an FL_Port (fabric loop port).
Figure 1–3 shows an example of an arbitrated loop topology.
Fibre Channel Overview 1–5

Figure 1–3: Arbitrated Loop Topology
NL_Port NL_Port
Node 1
Node 2
NL_Port NL_Port
Transmit
Receive
Transmit
Receive Transmit
Receive
Transmit
Receive
Node 3
Node 4
Hub
ZK-1535U-AI
1.3 Fibre Channel Topology Comparison
This section compares and contrasts the fabric and arbitrated loop topologies
and describes why you might choose to use them.
When compared with the fabric (switched) topology, arbitrated loop is
a lower cost, if lower performance, alternative. Arbitrated loop reduces
Fibre Channel cost by substituting a lower-cost, often nonintelligent and
unmanaged hub, for a more expensive switch. The hub operates by collapsing
the physical loop into a logical star. The cables, associated connectors, and
allowable cable lengths are similar to those of a fabric. Arbitrated loop
supports a theoretical limit of 127 nodes in a loop. Arbitrated loop nodes are
self-configuring and do not require Fibre Channel address switches.
Arbitrated loop provides reduced cost at the expense of bandwidth; all
nodes in a loop share the bandwidth (100 MB/sec per loop), and bandwidth
degrades slightly as nodes and cables are added. Nodes on the loop see
all traffic on the loop, including traffic between other nodes. The hub can
include port-bypass functions that manage movement of nodes on and off the
loop. For example, if the port bypass logic detects a problem, the hub can
remove that node from the loop without intervention. Data availability is
then preserved by preventing the down time associated with node failures,
cable disconnections, and network reconfigurations. Traffic caused by node
insertion and removal, errors, and so forth, can cause temporary disruption
on the loop.
1–6Fibre Channel Overview

Although more expensive, the fabric topology provides both increased
connectivity and higher performance; switches provide a full-duplex 100
(200) MB/sec point-to-point connection to the fabric. Switches also provide
improved performance and scaling because nodes on the fabric see only
data destined for themselves, and individual nodes are isolated from
reconfiguration and error recovery of other nodes within the fabric. Switches
can provide management information about the overall structure of the
Fibre Channel fabric, which may not be the case for an arbitrated loop hub.
Table 1–1 shows a comparison between the fabric and arbitrated loop
topologies.
Table 1–1: Fibre Channel Fabric and Arbitrated Loop Comparison
When to Use Arbitrated Loop When to Use Fabric
In clusters of up to two members In clusters of more than two members
In applications where low total solution
cost and simplicity are key requirements In multinode cluster configurations when possible temporary traffic disruption due
to reconfiguration or repair is a concern
In applications where the shared
bandwidth of an arbitrated loop
configuration is not a limiting factor
In high bandwidth applications where
a shared arbitrated loop topology
is not adequate
In configurations where expansion and
scaling are not anticipated In cluster configurations where expansion is anticipated and requires
performance scaling
1.4 Example Fibre Channel Configurations Supported by
the TruCluster Software Products
This section provides diagrams of some of the configurations that Tru64
UNIX and TruCluster Software Products Version 1.6 support.
Fibre Channel Overview 1–7

Figure 1–4 shows a typical Fibre Channel cluster configuration using
transparent failover mode.
Figure 1–4: Fibre Channel Single Switch Transparent Failover
Configuration
ZK-1531U-AI
KGPSA
Member
System
1
Memory
Channel KGPSA
Memory
Channel
Memory
Channel
Interface
Member
System
2
Fibre Channel Switch
HSG 80
Controller A
HSG 80
Controller B
RA8000/ESA12000
Port 1 Port 2
Port 1 Port 2
In transparent failover, units D00 through D99 are accessed through port 1
of both controllers. Units D100 through D199 are accessed through port 2 of
both HSG80 controllers (with the limit of a total of 128 storage units).
You cannot achieve no-single-point-of-failure (NSPOF) with the configuration
shown in Figure 1–4 because the switch represents a single-point-of-failure.
You can, however, add the hardware for a second bus (another KGPSA,
switch, and RA8000/ESA12000 with associated cabling) and use the Logical
Storage Manager (LSM) to mirror across the buses to achieve a NSPOF
cluster.
1–8Fibre Channel Overview

Figure 1–5 shows a transparent failover configuration set up to use LSM to
mirror storage units on one RAID array controller to the other controller.
Figure 1–5: Mirroring Storage Units with LSM in a Cluster
KGPSA
Member
System
2
KGPSA
KGPSA
Member
System
1
KGPSA
ZK-1533U-AI
Memory
Channel Memory Channel
Memory
Channel
Interface
Fibre Channel Switch Fibre Channel Switch
HSG 80
Controller A
HSG 80
Controller B
RA8000/ESA12000
Port 1 Port 2
Port 1 Port 2
HSG 80
Controller A
HSG 80
Controller B
RA8000/ESA12000
Port 1 Port 2
Port 1 Port 2
Fibre Channel Overview 1–9

Figure 1–6 shows a cluster with a full complement of eight targets on one
Fibre Channel switch. Each member system represents one target, and each
dual-redundant HSG80 port pair represents one target.
Figure 1–6: Single Switch Configuration with Full Complement
ZK-1532U-AI
KGPSA
Member
System
1
Memory
Channel KGPSA
Memory
Channel
Memory
Channel
Interface
Member
System
2
Fibre Channel Switch
HSG 80
Controller A
HSG 80
Controller B
RA8000/ESA12000
Port 1
Port 1
Port 2
Port 2
HSG 80
Controller A
HSG 80
Controller B
RA8000/ESA12000
Port 1
Port 1
Port 2
Port 2
HSG 80
Controller A
HSG 80
Controller B
RA8000/ESA12000
Port 1
Port 1
Port 2
Port 2
1–10 Fibre Channel Overview