IBM Enterprise Storage Server 2105 E10, Enterprise Storage Server 2105 E20, Enterprise Storage Server 2105 F10, Enterprise Storage Server 2105 F20 Introduction And Planning Manual
Introduction and Planning Guide
2105 Models E10, E20, F10, and F20
IBM
GC26-7294-05
IBM Enterprise Storage Server
™
Introduction and Planning Guide
2105 Models E10, E20, F10, and F20
IBM
GC26-7294-05
Note!
Before using this information and the product it supports, read the information in “Notices” on page 95.
Sixth Edition (December 2000)
This edition replaces GC26–7294–04.
|
Publications are not stocked at the address given below. If you want additional IBM publications, ask your IBM
representative or write to the IBM branch office serving your locality.
A form for your comments is provided at the back of this document. If the form has been removed, you may address
comments to:
International Business Machines Corporation
RCF Processing Department
G26/050
5600 Cottle Road
San Jose, CA 95193-0001
U.S.A.
FAX: 1-800-426-6209
You can also send your comments electronically to:
starpubs@us.ibm.com
For additional information on IBM storage products, visit the Web site at:http://www.ibm.com/storage
To find the translated text for a danger or caution notice:
1. Look for the identification number at the end of each danger or caution notice.
In the following examples, look for the numbers 1000 and 1001.
DANGER
A danger notice indicates the presence of a hazard that has the
potential of causing death or serious personal injury.
1000
CAUTION:
A caution notice indicates the presence of a hazard that has the potential
of causing moderate or minor personal injury.
1001
2. Find the number that matches in the
GC26-7229.
IBM Storage Solution Safety Notices
book,
Product recycling
This unit contains recyclable materials. Recycle these materials at your local
recycling sites. Recycle the materials according to local regulations. In some areas,
IBM provides a product take-back program that ensures proper handling of the
product. Contact your IBM representative for more information.
Disposing of products
This unit may contain batteries. Remove and discard these batteries, or recycle
them, according to local regulations.
This publication introduces the IBM®Enterprise Storage Server™(ESS) and lists
the features you can order. It also gives guidelines for the following tasks:
v Planning for installation
v Planning communications
v Planning data migration
Who should use this guide
This publication is for storage administrators, system programmers, and
performance and capacity analysts.
Frequently used terms
The following terms appear in this publication to describe the IBM Enterprise
Storage Server (ESS) and its configuration. Also see the “Glossary” on page 107 for
additional terms and definitions.
TermDefinition
arrayAn arrangement of related disk drive modules
(DDMs) that you have assigned to a group. Also
referred to as a rank. For the ESS, an array is a
group of up to eight DDMs.
clusterA partition of a storage server that is capable of
performing all functions of a storage server. When a
cluster fails in a multiple-cluster storage server, the
cluster that remains in the configuration takes over
the processes of that cluster.
®
controller imageA System/390
you access with an ESCON
more controller images exist in each controller.
Each image appears to be an independent
controller, but all images share a common set of
hardware facilities. The ESS can emulate 3990-3,
3990-6, or 3990-3 TPF controller images.
count key data (CKD)A System/390 term for a logical device that
specifies the format of the logical data units on the
device. The logical data unit is a track that contains
one or more records, consisting of a count field, a
key field (optional), and a data field (optional).
device adapterA physical component of a storage controller that
attaches to one or more interfaces. It enables
communication between the interfaces and the
associated storage devices.
destageThe process of writing modified storage from cache
to the disk drive module (DDM).
term for a logical subsystem that
®
I/O interface. One or
disk drive module (DDM)The primary, nonvolatile storage medium that you
use for any host data that is stored within a storage
server. The number and type of storage devices
within a storage server may vary.
Enterprise Systems Connection architecture (ESCON)
1. An ESA/390 computer-peripheral interface. The
I/O interface uses ESA/390 logical protocols
over a serial interface.
2. A set of IBM products and services that provide
a dynamically connected environment within an
enterprise.
ESCONSee
Enterprise Systems Connection architecture
.
ESCON channelA channel that has an ESCON channel-to-controller
I/O interface that uses optical cables as a
transmission medium.
ESCON host systemsSystem/390 hosts that you attach to the ESS with
an ESCON adapter. Such host systems run on
Multiple Virtual Storage (MVS), virtual machine
(VM), VSE, or TPF operating systems.
fabricIn fibre-channel technology, a routing structure,
such as a switch, receives addressed information
and routes to the appropriate destination. A fabric
can consist of more than one switch. When multiple
fibre-channel switches are interconnected, they are
cascaded
.
fibre-channelFibre-channel is an architecture that supports
full-duplex communication over a serial interface
that configures attached units to a communication
fabric.
The ESS supports fibre-channel communications for
open system hosts through its fibre-channel
adapters.
fixed-block (FB) devicesAn architecture for logical devices that specifies the
format of the logical data units on the device. The
logical data unit is a block. All blocks on the device
are the same size (fixed size); the subsystem can
access them independently. This is the required
format of the logical data units for host systems that
you attach with a small computer system interface
(SCSI) or fibre-channel interface.
gigabyte (GB)When referring to hard-disk-drive capacity, GB
host adapterA physical component in a storage server that
IBM Enterprise Storage Server (ESS)
xivESS Introduction and Planning
means 1 000 000 000 bytes; total user-accessible
capacity may vary depending on operating
environment.
enables the server to attach to one or more host
I/O interfaces.
™
A member of the Seascape
product family of
storage servers and attached storage devices (disk
drive modules). The ESS provides integrated
caching and RAID support for the disk drive
modules (DDMs). The DDMs are attached through
a serial storage architecture (SSA) interface.
logical deviceA pointer to a logical volume on a storage server.
The pointer enables a host system to access the
logical volume. For the ESS, the logical device
represents a logical volume.
logical subsystem (LSS)The LSS is a logical “container” for RAID-5 arrays,
disk groups, and the volumes that are located on
those arrays or disk groups. One SSA Adapter
accesses an LSS primarily. One or more logical
subsystems can exist on the ESS. In general, the
ESS associates a given set of devices with only
one logical subsystem.
For System/390 hosts, a logical subsystem
represents a controller.
logical unitThe Small Computer System Interface (SCSI) term
for a logical disk drive.
logical unit number (LUN)LUN is a SCSI term for the field in an identifying
message that is used to select a logical unit on a
given target.
logical volumeThe storage medium associated with a logical disk
drive. A logical volume typically resides on one or
more storage devices. For the ESS, you define this
unit of storage; the logical volume resides on a
RAID-5 array, and is spread over6+Por7+P
drives, where P is parity. A logical volume can also
reside on a non-RAID array on one storage device.
For CKD, you can define the logical volume size by
the device emulation mode (3390 or 3380 track
format). For UNIX
Microsoft Windows 2000
fixed-block format, the size is 0.5 GB to 224 GB.
For AS/400
®
, Microsoft®Windows NT®, and
®
operating systems in the
®
operating systems in the fixed-block
format, the size is 4.19, 8.59, 17.55, or 36 GB.
®
Note: The AIX
operating system views a logical
volume as a logical disk or a hard disk
(hdisk).
SCSISee
small computer system interface
.
SCSI host systemsIdentifies host systems that you attach to the ESS
with a SCSI interface. Such host systems run on
UNIX, OS/400, Windows NT, Windows 2000, or
Novell NetWare operating systems.
SCSI IDA unique identifier (ID) assigned to a SCSI device
that is used in protocols on the SCSI interface to
identify or select the device. The number of data
bits on the SCSI bus determines the number of
available SCSI IDs. A wide interface has 16 bits,
with 16 possible IDs. A SCSI device is either an
initiator or a target.
service personnelIndividuals or a company that you have authorized
to service your ESS. This term also refers to a
About this guidexv
service provider, a service representative, or an
IBM service support representative (SSR). An IBM
SSR installs your ESS.
Small Computer System Interface
An American National Standards Institute (ANSI)
standard for a logical interface to computer
peripherals and for a computer-peripheral interface.
The interface uses a SCSI logical protocol.
stagingTo move data from an offline or low-priority device
to an online or higher priority device is called
staging.
storage serverA unit that manages attached storage devices and
provides access to the storage or storage-related
functions for one or more attached hosts.
terabyte (TB)When referring to hard-disk-drive capacity, TB
means 1 000 000 000 000 bytes; total
user-accessible capacity may vary depending on
operating environment.
volumeRefers to a
Publications
This section describes the ESS library and publications for related products. It also
gives ordering information for these publications.
The ESS product library
The ESS is an IBM Seascape architecture-based product. See the following
publications for more information on the ESS:
v
IBM Enterprise Storage Server Introduction and Planning Guide
This guide introduces the product and lists the features you can order. It also
provides guidelines on planning for the installation and configuration of the ESS.
IBM Enterprise Storage Server User’s Guide
v
|
|
This guide provides instructions for setting up and operating the ESS and for
analyzing problems.
IBM Enterprise Storage Server Host Systems Attachment Guide
v
This book provides guidelines for attaching the ESS to your host system and for
migrating from SCSI to fibre-channel attachment.
v
IBM Enterprise Storage Server SCSI Command Reference
This book describes the functions of the ESS. It provides reference information
for UNIX and Application System/400
commands, sense bytes, and error recovery procedures.
v
IBM Enterprise Storage Server System/390 Command Reference
This book describes the functions of the ESS and provides reference information
for System/390 hosts, such as channel commands, sense bytes, and error
recovery procedures.
IBM Storage Solutions Safety Notices
v
This book provides translations of the danger notices and caution notices that
IBM uses in ESS publications.
IBM Enterprise Storage Server Web Interface User’s Guide
v
logical
®
(AS/400®) hosts, such as channel
, GC26-7229
volume.
, GC26-7294
, SC26-7295
, SC26-7296
, SC26-7297
, SC26-7298
, SC26-7346
xviESS Introduction and Planning
This book provides instructions for using the IBM StorWatch™Enterprise Storage
Server Web interfaces, ESS Specialist and ESS Web Copy Services.
IBM Enterprise Storage Server Configuration Planner
v
This book provides work sheets for planning the logical configuration of the ESS.
This book is not available in hardcopy. This book is only available on the
following Web site:
IBM Enterprise Storage Server Quick Configuration Guide
v
This booklet provides flow charts for using the StorWatch Enterprise Storage
Server Specialist. The flow charts provide a high-level view of the tasks the IBM
service support representative performs during initial logical configuration. You
can also use the flow charts for tasks that you might perform during modification
of the logical configuration.
The hardcopy of this booklet is a 9-inch × 4-inch fanfold.
|
|
|
|
|
|
|
IBM Enterprise Storage Server Service Guide
v
This service guide is for the service support representatives who are trained to
install and repair the IBM 2105 Models E10/E20 and F10/F20. This service guide
is broken into three volumes that contain the following chapters:
– Volume 1: Information, Start, and Isolation
– Volume 2: Repair, Install, and Configure
– Volume 3: Locations, Service Terminal, Codes, Power
, SY27–7605
, SC26-7353
, SC26-7354
Ordering publications
|
All of the publications that are listed in “The ESS product library” on page xvi are
available on a compact disc that comes with the ESS, unless otherwise noted. You
can also order a hardcopy of each publication. For publications on compact disc,
order
All the customer documents listed above are available on the following ESS Web
site:
Related publications
The following related publications are also available:
v
DFSMS/MVS®Version 1 Release 5 Software Support for the IBM Enterprise
Storage Server
This book describes the changes you need to make to operating systems for
System/390 hosts to support the ESS functions.
v
IBM Storage Area Network Data Gateway Installation and User’s Guide, 2108
Model G07
This book introduces the IBM Storage Area Network (SAN) Data Gateway and
provides the procedures for installing and using it.
v
IBM Subsystem Device Driver
This book describes how to use the IBM Subsystem Device Driver on
open-systems hosts to enhance performance and availability on the ESS. The
Subsystem Device Driver creates redundant paths for shared logical unit
numbers. The Subsystem Device Driver permits applications to run without
interruption when path errors occur. It balances the workload across paths, and it
transparently integrates with applications.
This publication is not available in hardcopy. However, it is available on the
compact disc that is delivered with your ESS. You can also view and copy this
publication from the Web site:
This book provides detailed information about Copy Services functions such as
Peer-to-Peer Remote Copy (PPRC), Extended Remote Copy (XRC), and
FlashCopy.
|
|
|
|
|
|
|
|
OS/390 MVS System Messages Volume 1 (ABA - ASA)
v
This publication helps you understand and use IBM Advanced Copy Services
functions on an IBM System/390. It describes two dynamic-copy functions and
several point-in-time copy functions. These functions provide backup and
recovery of data should a disaster occur to your data center. The dynamic-copy
functions are Peer-to-Peer Remote Copy and Extended Remote Copy, and are
known collectively as remote copy. FlashCopy, SNAPSHOT
Copy are the point-in-time copy functions.
v
IBM Enterprise Storage Server
, SG24-5465
, SG24-5465
®
, and Concurrent
This book, from the IBM International Technical Support Organization, introduces
the IBM Enterprise Storage Server (ESS) and provides an understanding of its
benefits. It also describes in detail the architecture, hardware and functions of the
ESS.
Implementing the IBM Enterprise Storage Server
v
, SG24-5420
This book, from the IBM International Technical Support Organization, can help
you install, tailor, and configure the IBM Enterprise Storage Server (ESS) in your
environment.
IBM Enterprise Storage Server Performance Monitoring and Management
v
,
SG24-5656.
This book, from the IBM International Technical Support Organization, provides
guidance on the best way to configure, monitor, and manage your Enterprise
Storage Server (ESS) to ensure optimum performance.
v
IBM System/360™and System/370™I/O Interface Channel to Control Unit
Original Equipment Manufactures’ Information
, GA22-6974
This publication provides a description of the interface between System/360,
System/370, and System/390 channels and controllers that are designed to
operate with this interface. This publication covers the parallel I/O interface. It
does not cover the interface between the controller and the I/O device, nor does
it cover the ESCON-I/O interface for the System/390.
This publication is for designers of programs and equipment that are associated
with parallel I/O interfaces and for service personnel that maintain the equipment.
Anyone concerned with the functional details of this interface will also find it
useful.
Fibre Transport Services (FTS) Direct Attach, Physical and Configuration
v
Planning
, GA22-7234
This publication provides information about fibre-optic and ESCON-trunking
systems.
v
DFSMS/MVS Version 1 Remote Copy Guide and Reference
, SC35-0169
This publication provides guidelines for using remote copy functions with
System/390 hosts.
Implementing ESS Copy Services on S/390
v
, SG24-6480
This publication tells you how to install, customize and configure Copy Services
on IBM Enterprise Storage Server on a S/390 host system. Copy Services
xviiiESS Introduction and Planning
Web sites
functions include, Peer-to-Peer Remote Copy, Extended Remote Copy,
FlashCopy, and Concurrent Copy. This publication describes the functions,
pre-requisites and co-requisites. The publication also describes how to implement
each of the functions into your environment.
Implementing ESS Copy Services on UNIX and Windows NT
v
This publications tells you how to install, customize, and configure Copy Services
on an IBM Enterprise Storage Server on the UNIX and Windows NT host system.
Copy Services functions include, Peer-to-Peer Remote Copy, FlashCopy,
Extended Remote Copy, and Concurrent Copy. Extended Remote Copy and
Concurrent Copy are not available for UNIX and Windows NT host systems.
They are only available on System/390. This publication describes the functions,
pre-requisites and co-requisites. The publications also shows you how to
implement each of the functions into your environment. This publications also
shows how to implement these solutions in an HACMP cluster.
NUMA-Q ESS Integration Release Notes
v
This publication contains information about special procedures and limitations
involved in running ESS with Copy Services on a NUMA-Q host system. It is not
available through IBM ordering systems. Contact your IBM NUMA-Q sales
representative to obtain this document
For general information about IBM storage servers, see the following Web site:
v www.storage.ibm.com/hardsoft/products/ess/ess.htm
, Part Number 1003-80094-01
, SG24-5757
To view and print the IBM Enterprise Storage Server publications, see the following
Web site:
v www.storage.ibm.com/hardsoft/products/ess/refinfo.htm
To get current information about the host system models, operating systems, and
adapters that the ESS supports, see the following Web site:
v www.storage.ibm.com/hardsoft/products/ess/supserver.htm
For information about the IBM Subsystem Device Driver, see the following Web site:
To attach a SAN or host system that uses an industry-standard, fibre-channel
arbitrated loop (FC-AL) through the IBM 2108 SAN Data Gateway Model G07, see
the following Web site:
For information about the latest updates to Copy Services components XRC,
PPRC, SnapShot, Concurrent Copy, and FlashCopy for S/390, see the following
Web site:
www.storage.ibm.com/software/sms/sdm/sdmtech.htm
About this guidexix
xxESS Introduction and Planning
Summary of Changes
Revision bars in the left margin indicate technical changes to this publication. Minor
|
|
|
|
|
|
|
|
|
|
editorial changes are not marked. This edition includes the following major changes:
v Support for the new IBM System/390 eserver zSeries 900 (z900 server)
v Feature codes for a SCSI cable with an additional interposer
v Feature codes for step-ahead storage planning
v Modification to the ESS weight information
v Additional information about the environment for storing an ESS
v Modifications to the information about planning for ESS Copy Services
v New fields for the Communication Resources work sheet:
– Support Catcher Telephone Number
– Enable ESS Copy Services commands for IBM System/390 volumes
v A new work sheet for Network Communications for ESS Copy Services
This book provides an overview of the IBM Enterprise Storage Server (ESS) and
lists the features that you can order. It also provides guidelines for these tasks:
v Installation planning
v Communications planning
v Data migration planning
For guidelines and work sheets for logical configuration, see the
This section provides an overview of the IBM Enterprise Storage Server (ESS) and
describes its interfaces and components.
The ESS is a member of the Seascape family of storage servers. The ESS
provides integrated caching and support for redundant arrays of independent disks
(RAID) for the disk drive modules (DDMs). The DDMs are attached through a serial
storage architecture (SSA) interface.
The ESS uses peripheral component interconnect (PCI) architecture that is
designed to provide high availability and to avoid single points of failure.
|
|
|
The ESS Models E10 and E20 provide 6 GB of cache. The ESS Models F10 and
F20 provide 8 GB of cache; an optional 16 GB of cache; and faster PCI
architecture.
The ESS provides the following features:
v RAID 5 or non-RAID disk groups
v Fast SSA drives
v Fast reduced instruction-set computer (RISC) processors
v A fault-tolerant system
v Sharing of storage between open-systems hosts
®
v OS/390
v Instant copy solutions
v Disaster recovery solutions
parallel input/output (I/O) interface
IBM Enterprise
on the product Web site:
Models E20 and F20, with expansion enclosures, can provide up to 11 terabytes
(TB) of storage capacity, with a choice of 9.1, 18.2, or 36.4 GB DDMs. When IBM
refers to DDM capacity, TB means 1 000 000 000 000 bytes. For processor
storage, real and virtual, a TB equals 2⁴⁰ or 1 099 511 627 766 bytes. Total
user-accessible capacity may vary depending on the operating environment.
See Figure 1 on page 2 and Figure 2 on page 2 for illustrations of the ESS models
and the expansion enclosure. ESS Models E10 and F10 do not support an
expansion enclosure.
Figure 1. Models E10, E20, F10, and F20; front and rear views
Rear view
Each ESS expansion enclosure has dual power cables and redundant power. The
redundant power system allows both the storage controller and DDMs to continue
normal operation when one of the power cables is inactive. Redundancy also
ensures continuous data availability.
Figure 2. Expansion enclosure, front and rear views
ESS Models E10 and F10 support a maximum of 64 DDMs. The minimum
configuration for a Model E10 or F10 base enclosure is 16 DDMs. ESS Models E20
and F20 support a maximum of 128 DDMs. With the expansion enclosure, Models
E20 and F20 support a maximum of 384 DDMs.
Host systems supported by the ESS
The ESS provides heterogeneous data storage that you can share between
workloads for open-systems hosts. The following sections contain information about:
v Open-systems hosts with small computer system interface (SCSI) adapters
2ESS Introduction and Planning
Front view
Rear view
v Open-systems hosts with fibre-channel adapters
Note: Because of possible interactions between host bus adapters in switched
configurations, IBM recommends that you establish zones that contain a
single port attached to a host bus adapter with the desired number of ports
attached to ESS. You can establish the zones by using either the hard (by
port) or soft (by WWN) zoning method. You can configure ports that are
attached to the ESS in more than one zone, which allows multiple host bus
adapters to share access to the ESS fibre-channel ports. Shared access to
an ESS fibre-channel port might be from host platforms that use a
combination of supported host bus adapter types and operating systems.
SCSI host systems
Each SCSI adapter has two ports. With SCSI adapters you can connect up to 128
host systems when you serially interconnect them. The ESS supports the following
host systems for SCSI attachment:
v Hewlett Packard with the HP-UX operating system
®
v IBM RISC System/6000
system
v IBM AS/400 with the IBM Operating System/400 (OS/400) Version 3 or Version 4
v Personal computer servers with Microsoft Windows NT 4.0 operating systems
v Personal computer servers with Microsoft Windows 2000 operating systems
v Sun with the Solaris operating system
v Data General with the DG UX operating system
v Personal computer servers with Novell Netware
and RISC System/6000 SP with the IBM AIX operating
See the following ESS Web site for details about types, models, adapters, and the
operating systems that the ESS supports for SCSI-attached host systems:
Each ESS fibre-channel adapter has one port. With fibre-channel adapters you can
connect up to 127 host systems. See “Fibre-channel connection” on page 10 for
information on the fibre-channel protocols that the ESS supports. The ESS supports
the following host systems for fibre-channel attachment:
v IBM RISC System/6000 and RISC System/6000 SP with the IBM AIX operating
system
v Personal computer servers with Microsoft Windows NT 4.0 operating systems
v Personal computer servers with Windows 2000 operating systems
v IBM NUMA-Q with DYNIX/ptx
|
|
|
v Hewlett Packard with the HP-UX operating system
v Personal computer servers with Novell NetWare
v Sun with the Solaris operating system
See the following ESS Web site for details about types, models, adapters, and the
operating systems that the ESS supports for fibre-channel attached host systems:
With ESCON adapters, the ESS supports up to 32 connections for System/390 host
systems, each with up to 64 logical paths. IBM attaches an ESS to a System/390
server for fibre-channel connection (FICON
9032 Model 005 ESCON Director.
The ESS supports the following operating systems:
v OS/390
v Multiple Virtual Storage/Enterprise Storage Architecture (MVS/ESA
v Virtual Machine/Enterprise Storage Architecture (VM/ESA®)
v Virtual Storage Extended/Enterprise Storage Architecture (VSE/ESA™)
v Transaction Processing Facility (TPF)
The ESS also supports the following operating systems for the new IBM eserver
zSeries 900 (z900 server):
v z/OS Version 1 Release 1
v OS/390 Version 2 Release 6 or higher
v VM
– z/VM Version 3 Release 1
– VM/ESA Version 2 Release 2
– VM/ESA Version 2 Release 3
– VM/ESA Version 2 Release 4
v VSE/ESA Version 2 Release 3 and higher
v Transaction Processing Facility (TPF) Version 4 Release 1
™
) through the bridge card on the IBM
™
)
|
|
|
Web interfaces
|
|
|
See the preventive service planning (PSP) bucket for operating system support and
planning information that includes APARs and programming temporary fixes (PTFs).
For additional information about the changes you need to make to System/390
hosts to support ESS functions, see
Support for the IBM Enterprise Storage Server
DFSMS/MVS Version 1 Release 5 Software
.
For information about the latest updates to Copy Services components XRC,
PPRC, SnapShot, Concurrent Copy, and FlashCopy for S/390, see the following
Web site:
www.storage.ibm.com/software/sms/sdm/sdmtech.htm
This section describes the Web security, the ESSNet, and the Web interfaces for
ESS. The Web interfaces include:
v StorWatch Enterprise Storage Server Specialist (ESS Specialist)
v StorWatch Enterprise Storage Server Web Copy Services (ESS Web Copy
Services) that supports Web Interfaces to manager peer-to-peer remote copy or
FlashCopy.
v StorWatch Expert, an optional software product
See your IBM Field office for information about how to order StorWatch Expert. See
IBM Enterprise Storage Server Web Interface User’s Guide
the
which provides
detailed descriptions of the ESS Specialist and the ESS Web Copy Services
interfaces and how to use them.
4ESS Introduction and Planning
Web connection security
You connect to the ESS through the ESSNet.
All data that is sent between the ESS and the Web browser through the ESSNet is
encrypted to avoid unauthorized modification of configuration commands.
Passwords and authorization levels protect access to the interface.
You control user access by assigning levels of access and passwords.
IBM Enterprise Storage Server Network
The IBM Enterprise Storage Server Network (ESSNet) is a private network resident
on an IBM workstation. It is a required feature. IBM installs the ESSNet when they
install your IBM Enterprise Storage Server. The ESSNet hardware includes:
v The IBM workstation (a PC) and monitor
v An external Ethernet hub that provides cable connections from the ESSNet to the
IBM Enterprise Storage Server. The hub speed is 10 megabits per second
(Mbps) or 10/100 megabits per second, depending on your system.
Note: You can attach your Ethernet LAN to the external hub. You provide any
hardware that is needed for this connection.
v A modem and a modem expander that allow your ESS to communicate between
you and IBM
Note: The feature code for Remote Service Support includes the modem and
modem expander.
The ESSNet includes the following software on the workstation:
v Windows NT 4.0 operating system
v Browser software (Microsoft Internet Explorer and Netscape Navigator) that
allows access to the ESS Specialist
v The ESSNet application for installation and configuration. The ESSNet
workstations includes an HTML page that provides links to all ESS connected to
the ESSNet for Specialist access.
The ESSNet provides the following features:
v Support for multiple ESSs. A hub with 16 ports will support 7 ESSs.
v Connectivity between your ESS and the ESS Specialist Web interface. The
ESSNet provides browser software at the appropriate level for this connection.
v Improvements in Web performance compared to previous Web browser
connections.
v Faster network connectivity and elimination of network setup problems when
using previous Web connections.
v Ethernet connectivity through an Ethernet hub to the ESSNet.
v An independent platform that facilitates installation and configuration of the ESS.
v Software for maintenance and configuration.
IBM installs the ESSNet when they install your first IBM Enterprise Storage Server.
Accessing ESS Specialist and ESS Web Copy Services
|
|
|
|
You access the IBM StorWatch Enterprise Storage Server Specialist (ESS
Specialist) from the ESSNet. The ESSNet includes browser software for this
access. You access ESS Web Copy Services from the ESS Specialist Navigation
frame.
Chapter 1. Introduction5
|
|
|
|
|
|
|
You can access ESS Specialist from your own workstation if you connect the
ESSNet into your intranet by using one of the ports on the ESSNet hub. If you use
your own workstation IBM recommends at least 128MB of memory in the
workstation. You can access the ESS Specialist by using a browser that is fully
enabled for Java(TM) 1.1.x. The ESS Specialist supports the following browsers:
v Netscape Navigator Version 4.04 or greater, which supports Windows NT and
Windows 95.
|
|
|
|
|
|
|
|
Note: Version 4.04 requires Java 1.1 fixpack; later versions such as 4.5 may not
require this fixpack.For better web performance, IBM recommends using
Netscape Navigator Version 4.5.1 or greater.
v Microsoft Internet Explorer (MSIE) Version 4.0 or greater, which supports
Windows NT and Windows 95.
Note: Version 4.0 requires Service Pack 1.
The ESSNet PC is pre-loaded with current release levels of Microsoft Internet
Explorer and Netscape Navigator.
If you do not choose to attach ESSNet into your intranet, you can only access ESS
Specialist from a browser on the ESSNet workstation.
You must provide another network connection to the remote ESS through ESSNet
hubs for Copy Services support.
IBM updates ESS Specialist and ESS Copy Services through engineering changes
(ECs).
ESS Specialist
The ESS includes the ESS Specialist. The ESS Specialist is a Web-based interface
that allows you to configure the ESS.
From the Web interface, you can perform the following tasks:
v Monitor error logs
v View and change the configuration:
– Add or delete SCSI and fibre-channel host systems
– Configure SCSI host ports and fibre-channel host ports on the ESS
– Define controller images for System/390
– Define fixed-block (FB) and count-key-data (CKD) disk groups
– Add FB and CKD volumes
– Assign volumes to be accessible to more than one host system
– Change volume assignments
v Change and view communication resource settings, such as electronic mail
(e-mail) addresses and telephone numbers
v Authorize user access
With the ESS Specialist, you can view the following information:
v The external connection between a host system and an ESS port
v The internal connection of SCSI ports and fibre-channel ports to cluster 1 or
cluster 2
v The allocation of storage space to FB and CKD volumes
IBM updates the ESS Specialist through licensed internal code (LIC) updates.
6ESS Introduction and Planning
ESS Copy Services
ESS Copy Services collects information from your IBM storage servers onto a
single Copy Services server. The ESS supports Copy Services through both a
Web-based interface and a command-line interface.
This section describes the two interfaces for ESS Copy Services, shows an
example of the connections between two Copy Services server groups, and gives
you an overview of the functions you can perform using the ESS Web Copy
Services panels.
Web-based interface:
The ESS Web Copy Services interface initiates and
manages Peer-to-Peer Remote Copy (PPRC) and FlashCopy functions for open
systems and IBM System/390 hosts.
You access ESS Web Copy Services from the ESS Specialist Navigation frame.
Command-line interface:
If you choose to install the command-line interface
(CLI) application on your host system, you can write customized scripts using CLI
commands. You can execute the CLI commands from a host system. You can use
the CLI commands to invoke Copy Services tasks in an ESS Web Copy Services
server.
The command-line functions (TSO or API) on IBM System/390 hosts initiate and
manage Extended Remote Copy (XRC), Concurrent Copy, FlashCopy and PPRC.
An API has been developed which uses the TSO command line function. For more
information, see
OS/390 DFSMSdfp Advanced Services
.
The CLI on the open-systems hosts initiates and manages PPRC and FlashCopy
on ESS.
IBM Enterprise Storage Server Host Systems Attachment Guide
See
for information
about using the Copy Services command-line interface from your open systems
hosts to invoke Copy Services functions. See the web site at
http://www.ibm.com/storage/hardsoft/products/ess/refinfo.htm
for information on which open systems host platforms are supported for CLI. The
command-line interface (CLI) is updated when a new LIC is provided.
Copy Services server groups:
between two ESS Web Copy Services server groups. A Copy Services server group
is a collection of ESS clusters that participate in Copy Services functions that
include the volumes within the clusters.
Figure 3 on page 8 shows the connections
Chapter 1. Introduction7
Site 1 Primary Site
ESS 1
P
Backup
C
F
/
I
S
C
S
Server Group 1
ESCON
Site 2 Recovery Site
ESS 4
Primary
S
C
S
I
/
F
C
P
H
O
S
T
P
CLI
C
F
ESSnet
/
I
S
C
S
ESS 2
Backup
Server Group 2
ESCON
ESS 5
Primary
ESSnet
HUBHUB
CLI
S
C
S
I
/
F
C
P
CS000005
Figure 3. Connecting to ESS Web Copy Services server groups
Copy Services panels:
Use the ESS Web Copy Services panels to view and
define:
v Volumes
The volumes panel allows you to view volumes and define them as source or
target volumes for PPRC or FlashCopy.
v Storage Server
The Storage Server panel allows you to work with logical servers as complete
entities. You can build tasks to place all the volumes of a logical server within a
peer-to-peer relationship with all the volumes of another logical server.
You can also build a task to remove similar groups of volumes from an existing
peer-to-peer relationship.
You can determine the function of Consistency Groups and freeze and create
commands.
v Paths
The Paths panel displays the current status of paths between an ESS and the
other ESSs or switches to which it is connected. The paths panel also shows
ESCON connected hosts and channel extenders.
You can use the paths panel to add or remove copy services paths or to create
consistency group relationships for the LSS pairs.
v Tasks
The Tasks panel allows you to manage tasks you have defined. You can run,
remove, save, group, or ungroup tasks. The host system command line interface
function uses these predefined tasks.
v Configuration
The Configuration panel allows the customer to view the copy services event and
timing logs, set password protection, refresh the panels and mail logs to a
specified userid.
H
O
S
T
8ESS Introduction and Planning
ESS Expert
The IBM StorWatch Enterprise Storage Server Expert (ESS Expert) is an optional
software feature of the IBM StorWatch Expert. The StorWatch Expert can be
purchased to use with the ESS. The StorWatch Expert Web interface provides
storage-resource management for the IBM storage servers.
v Asset management
StorWatch Expert collects and displays asset management data on all of your
ESSs.
v Capacity management
StorWatch Expert collects and displays capacity management data on all of your
ESSs.
v Performance management
StorWatch Expert collects and displays performance management data on all of
your ESSs. For example:
– Number of I/O requests
– Number of bytes transferred
– Read and write response time
– Cache usage statistics
The IBM StorWatch Expert allows you to schedule the information collection. With
this information, you can make informed decisions about volume placement and
capacity planning as well as isolate I/O performance bottlenecks.
Service interface
The ESS provides service interface ports for external connection of a service
terminal.
IBM or your service provider can perform service on the ESS by using an IBM
mobile service terminal (MoST) or equivalent.
Remote services support
The ESS service interface also provides remote service support with call-home
capability for directed maintenance for service personnel.
You provide an analog telephone line to enable this support. The service interface
provides an RS232 connection through a modem switch and modem to the analog
telephone line.
You need to order a modem and modem switch. The first ESS you order requires
this equipment. The modem and modem switch support up to seven ESSs. The
cable length from the ESS to the modem switch should be a maximum of 15 m (50
ft.).
The ESS provides the following service functions:
v Continuous self-monitoring initiates a call (call home) to service personnel if a
v Error and problem logs are available that service personnel can access remotely
v Remote support allows the ESS to correct many types of problems. When the
failure has occurred. Because service personnel who respond to the call know
about the failing component, the service personnel can reduce the repair time.
to analyze potential failures.
ESS reports a problem, service personnel can often correct the problem from a
remote location.
Chapter 1. Introduction9
Configuration
IBM logically configures your ESS during installation using the work sheets that you
completed from the
installs the ESS, you can perform additional configuration by using the ESS Web
interfaces. You can also change the remote service functions.
Fibre-channel connection
The ESS provides fibre-channel connection to open-systems hosts that it supports.
Fibre-channel interconnection architecture provides a variety of communication
protocols on the ESS. The units that are interconnected are referred to as
Each node has one or more ports.
An ESS is a node in a fibre-channel network. Each port on an ESS fibre-channel
host adapter is a fibre-channel port. A host is also a node in a fibre-channel
network. Each port attaches to a serial-transmission medium that provides duplex
communication with the node at the other end of the medium.
With fibre-channel technology, the distance between an ESS and attached host
systems increases from the 25 m (75 ft) maximum imposed by SCSI connections
up to 500 m (1500 ft). The ESS can be up to 11 km (6.8 mi) from your host when
you connect to it with an IBM SAN fibre-channel switch. The ESS can also be the
same distance from your host when you connect to it with an IBM fibre-channel
storage hub.
IBM Enterprise Storage Server Configuration Planner
. After IBM
nodes
.
ESS architecture supports three basic interconnection topologies:
v Point-to-point
v Switched fabric
v Arbitrated loop
Point-to-point topology
The point-to-point topology, also known as direct connect, allows you to
interconnect ports directly. Figure 4 shows an illustration of a point-to-point topology.
1
Legend
«1¬ is the host system.
«2¬ is the ESS.
Figure 4. Point-to-point topology
2
S008944L
Switched fabric topology
The switched fabric topology provides the underlying structure that allows you to
interconnect multiple nodes. You can use a fabric that provides the necessary
switching functions to support communication between multiple nodes. You can
implement a fabric by using available vendor products that the ESS supports. For a
list of these vendor products, see the ESS Web site at:
v www.storage.ibm.com/hardsoft/products/ess/supserver.htm
10ESS Introduction and Planning
The ESS supports the switched-fabric topology with point-to-point protocol. The
ESS fibre-channel adapter should be configured to operate in point-to-point mode
when you connect it to point-to-point topologies or fabric topologies. See Figure 5.
2
1
3
3
3
2
1
S008945N
Legend
«1¬ is the host system.
«2¬ is the ESS.
«3¬ is a switch.
Figure 5. Switched fabric topology
Arbitrated loop
Fibre-channel arbitrated loop (FC-AL) is a ring topology that allows you to
interconnect a set of nodes. The maximum number of ports you can have for a
fibre-channel arbitrated loop is 127. See Figure 6 on page 12.
The ESS supports FC-AL as a private loop. It does not support the fabric-switching
functions in FC-AL.
Chapter 1. Introduction11
1
1
Legend
«1¬ is the host system.
«2¬ is the ESS.
Figure 6. Arbitrated loop topology
Introducing the IBM Subsystem Device Driver
The IBM Subsystem Device Driver resides in the host server with the native disk
device driver for the ESS. It uses redundant connections between the host server
and disk storage in an ESS to provide enhanced performance and data availability.
Figure 7 on page 13 is an example of the type of configuration that IBM Subsystem
Device Driver supports. These connections comprise many different components
through which data flows during input and output processes. Redundancy and the
ability to switch between these components provides many different paths for the
data to travel. In the event of failure in one input-output path, it automatically
switches to another input-output path. This automatic switching in the event of
failure is called
failover
.
2
2
S008943N
12ESS Introduction and Planning
Host Server
SCSI / FCP
adapter 0
ESS
Figure 7. Multipath connections between a host server and ESS LUNs
Port 0
Cluster 1Cluster 2
LUN 0LUN 1LUN 2LUN 3
SCSI / FCP
adapter 1
Port 1
S009000Q
The IBM Subsystem Device Driver provides the following functions:
v Enhanced data availability
v Automatic path failover and recovery to an alternate path
v Dynamic load balancing of multiple paths
v Path selection policies for the AIX operating system
v Concurrent download of licensed internal code
In most cases, host servers are configured with multiple host adapters with SCSI or
fibre-channel connections to an ESS that, in turn, provides internal component
redundancy. With dual clusters and multiple host interface adapters, the ESS
provides more flexibility in the number of input-output (I/O) paths that are available.
When there is a failure, the IBM Subsystem Device Driver reroutes I/O operations
from the failed path to the remaining paths. This function eliminates the following
connections as single points of failure: a bus adapter on the host server, an external
SCSI cable, a fiber-connection cable, or a host interface adapter on the ESS.
In addition, multipath load balancing of data flow prevents a single path from
becoming overloaded with I/O operations.
Dead
The IBM Subsystem Device Driver path recovery algorithms now test
paths
that are not manually offline every 30 minutes.
Concurrent download of licensed internal code
is the capability to download and
install licensed internal code on an ESS while applications continue to run. During
the time when new licensed internal code is being installed in an ESS, the upper
interface adapters inside the ESS may not respond to host I/O requests for
approximately 30 seconds. The IBM Subsystem Device Drivers makes this
transparent to the host through its path selection and retry algorithms.
Chapter 1. Introduction13
Note: For updated and additional information not included in this publication, see
the README file on the IBM Subsystem Device Driver compact disk
recordable (CDR) or visit the Subsystem Device Driver Web site at:
IBM Enterprise Storage Server availability features
This section describes the following enhanced data availability features that the
ESS offers for hosts with UNIX, OS/400, Windows NT, and Windows 2000
operating systems and for System/390 hosts:
v Redundant array of independent disks (RAID)
v Predictive failure analysis
v Failover protection
v Sparing
v Fibre-channel support (on supported host systems)
v Storage area network (SAN) support
v Cache
v Nonvolatile storage
v Concurrent maintenance
v FlashCopy (not supported for OS/400)
v Peer-to-Peer Remote Copy (not supported for OS/400)
v IBM Subsystem Device Driver
This section also describes data availability features that are available
v Open host systems. See “UNIX, Windows NT, and Windows 2000 availability
features” on page 18.
v System/390 hosts. See “System/390 availability features” on page 19.
Enhanced data availability for some host systems is also available with the following
software. The software automatically uses a secondary path (from a secondary
server) if a failure occurs.
v HACMP, for mirroring, for RS/6000 host systems
v Similar software for other non-IBM host systems
v System/390 hosts running TPF can use routines that ensure volume redundancy
Redundant array of independent disks implementation
The IBM Enterprise Storage Server protects all storage with redundant arrays of
independent disks (RAID). An array is an ordered collection of physical devices
(disk drives) that are used to define logical volumes or devices.
The ESS attaches disk drive modules (DDMs) in RAID-5 configurations. The
implementation of RAID-5 configurations distributes (stripes) parity across all DDMs
in the array. The ESS requires two spare DDMs per loop. With two spares, a loop
can have two DDM failures and still allow you to access data.
Implementation of RAID-5 data striping supports independent accesses to the
DDMs. The dual-loop device interface card provides the RAID-5 protection on the
ESS.
only
for:
All DDMs on a single loop must be of the same capacity.
14ESS Introduction and Planning
In the event of a DDM failure, the ESS can regenerate data from the other DDMs in
the array.
Non-RAID disk group support
The ESS supports non-RAID arrays also. If you format the DDMs as a non-RAID
group, then the array is a single DDM.
Predictive failure analysis
The DDMs in the ESS provide state-of-the-art failure analysis techniques that
predict errors
The DDM, which is continuously performing predictive failure analysis of device
failure conditions, notifies the IBM Enterprise Storage Server of impending hardware
failures.
before
Failover protection
The ESS includes the failover protection feature.
If one of the clusters fails, the ESS temporarily transfers all ports over to the
remaining cluster so that data access can continue. See “Nonvolatile storage” on
page 16 for additional information on cluster redundancy.
Sparing
The sparing function of the ESS is automatically called whenever a DDM failure is
detected. The ESS maintains data access during the sparing operation.
1
they affect data availability.
Note: The first two arrays on a loop include a spare.
When the ESS detects a DDM failure in a loop, it automatically uses a spare DDM
to replace the failing DDM. The ESS reconstructs the data on the spare DDM by
using redundant information from the remaining DDMs in the array.
If a DDM fails, a loop reconfigures itself into two loops. Once service personnel
have replaced the DDM, the loop automatically resumes normal operation as a
single loop. Neither the host system nor the operator needs to take any action.
Fibre-channel support
The ESS provides fibre-channel connection when your IBM SSR installs a
Fibre-channel adapter card (short wave) in the ESS. See “Fibre-channel
connection” on page 10 for a description of fibre-channel topologies that are
supported by the ESS.
For more information on host adapters and operating system attachments that the
ESS supports on the fibre-channel adapter see the ESS Web site:
IBM also provides fibre-channel connection through the IBM 2108 SAN Data
Gateway, Model G07. You can get the details on fibre-capable server models,
adapters, and operating systems on the Web at:
http://www.ibm.com/storage/SANGateway
1. Disk storage on an ESS is available in a package of eight DDMs, which IBM calls an 8-pack.
Chapter 1. Introduction
15
Cache
The ESS provides fibre-channel connectivity to System/390 host systems with the
IBM 9032 Model 005 ESCON director. The 9032 FICON-bridge option provides
connection and switching among FICON channels and ESCON controllers.
The ESS provides the following cache features that improve performance:
v 8-GB standard cache and 16-GB optional cache for Models F10 and F20
v 6-GB standard cache for Models E10 and E20
v Fast read from cache
The ESS improves performance by using algorithms to store data in cache tracks
that have the greatest probability of access by a read operation.
v Asynchronous write
The ESS provides improved write performance by completing an operation
without accessing DDMs.
v Least-recently-used (LRU) replacement
The ESS checks tracks at the top of the cache LRU list for updates in cache that
are not on the DDM. The ESS schedules tracks at the top of the nonvolatile
storage LRU list for destaging. The ESS can then allocate the tracks without a
delay during destaging.
v Internal error recovery
The ESS performs error recovery on DDM-to-cache operations.
Nonvolatile storage
The ESS provides 384 MB of nonvolatile storage (NVS) with all models. Cluster 1
and cluster 2 each have 192 MB of NVS, which enables them to store a second
copy of write data. This ensures data integrity in the event of a power failure.
The NVS for cluster 1 is located in cluster 2; cluster 2 NVS is stored in cluster 1.
Should a cluster fail, the remaining cluster can access the data from the failed
cluster. Battery backup power protects NVS in each cluster.
Concurrent maintenance
The ESS supports concurrent maintenance. Service personnel can replace a failed
component, such as a disk drive module (DDM), without shutting down the entire
system. Your host system continues to access data while service personnel replace
the component in the ESS.
FlashCopy
The FlashCopy feature provides an instant or point-in-time copy of a logical volume.
FlashCopy makes it possible for you to access both the source copies and the
target copies. This enables applications that use either the source copy or target
copy to operate almost without interruption. The source and target volume must
both be within the same logical subsystem.
The ESS supports FlashCopy on System/390 hosts and open system hosts (SCSI
or fibre channel). FlashCopy is not supported on AS/400 host systems. You can
initiate and use FlashCopy from the ESS Web Copy Services interface. See the
IBM Enterprise Storage Server Web Interface User’s Guide
for more information.
If a volume is reserved by host application software it cannot be used as a target
volume for FlashCopy.
16ESS Introduction and Planning
You can also use the command line interface to initiate Copy Services commands
from your open host system. See the
Attachment Guide
for more information on the command-line interface.
IBM Enterprise Storage Server Host Systems
A FlashCopy relationship is between CKD volumes or FB LUNs. This relationship
exists from the time you initiate a FlashCopy operation:
v Until the ESS copies all data from the source to the target, or
v Until you withdraw the FlashCopy relationship
For System/390 hosts, the FlashCopy feature provides instant replication of a full
CKD volume.
After a FlashCopy operation, track images on the source volumes and the target
volumes are independently available for data read and write operations. You can
use FlashCopy to create copies for:
v Disaster recovery
v Business intelligence applications
v Use in a test environment
v Instant checkpoints
Note: For System/390 hosts you can use TSO to invoke these functions for MVS
While your critical applications continue using the source volume, you can define
and initiate a FlashCopy from the ESS Specialist Web interface. Once you have
defined and initiated the target volume, it is available to you for tasks such as
asynchronous backup.
™
.
See “FlashCopy and PPRC restrictions for open system hosts” on page 18 for
additional information about FlashCopy.
Peer-to-Peer Remote Copy
The Peer-to-Peer Remote Copy (PPRC) feature allows synchronous copying of a
physical volume (the source) on one storage server to another volume (the target)
on a second storage server. PPRC ensures write operations on both local and
remote copies. The ESS supports PPRC on System/390 hosts and open system
hosts (SCSI or fibre channel). PPRC is not supported on AS/400 host systems.
Note: A PPRC target cannot be accessed until the PPRC relationship is ended,
that is the target volume is no longer part of a PPRC pair.
If a volume is reserved by host application software it cannot be used as a
secondary volume for PPRC.
You need to connect the ESSNet to both the primary and recovery sites through
your LAN to initiate PPRC operations for SCSI and fibre-channel attached hosts.
v The primary storage server (application site) establishes the paths and links to a
secondary storage server (recovery site). The primary storage server also
manages the synchronous copying of the volume from the primary site to the
secondary site. The remote secondary server can be up to 103 km from the
primary server.
v From the primary host, the I/O operation to the secondary storage server is
transparent.
Chapter 1. Introduction17
The PPRC feature requires that you install ESCON adapters on the ESS. The
ESCON adapter provides the link between a primary and a secondary server. More
than one ESCON link increases the reliability and availability of the PPRC feature.
You can use the ESS Web Copy Services interface to:
v Initiate and terminate the functions
v Suspend a copy operation
v Query the status of volumes
v Perform predefined tasks
Also, with PPRC, a recovery host has the ability to recover control of the secondary
volume.
For System/390 hosts you can use TSO to invoke these functions for MVS. For the
procedures for using TSO for PPRC functions, see
Guide and Reference
For open system hosts you can use the ESS Web Copy Services command-line
interface to invoke these functions. For more information on the command-line
interface see the
See “FlashCopy and PPRC restrictions for open system hosts” for additional
information about PPRC.
.
IBM Enterprise Storage Server Host Systems Attachment Guide
DFSMS/MVS V1 Remote Copy
.
FlashCopy and PPRC restrictions for open system hosts
When you copy a source volume to a target volume with FlashCopy or PPRC, and
you require concurrent read/write access of both volumes, the source and target
volumes should be on different host systems. A copy operation with the source and
target volume on the same host system creates a target volume with the same
identification as the source volume. The host system sees two identical volumes.
When the copy process creates the same identification for the target volume as for
the source volume the user cannot distinguish one from the other, so the user may
not be able to access the original data.
Note: For some operating systems, such as Novell NetWare, the user is unable to
access either the source or target volume. Although both data sets are intact,
they are invisible to the user.
The target volume and the source volume can be on the same host system for a
PPRC or FlashCopy operation only under the following conditions:
v For AIX: when the host system is using a Logical Volume Manager (LVM) with
recreatevg command support
v For AIX, SUN, and HP: when the host system is not using an LVM
v For any host system: when the host system can distinguish between a source
and a target volume that have the same identification
UNIX, Windows NT, and Windows 2000 availability features
This section describes UNIX, Windows NT, and Windows 2000 availability features,
which include:
v Data sharing
v IBM Subsystem Device Driver
18ESS Introduction and Planning
Data sharing
You can use the ESS to share data among multiple UNIX-based homogeneous host
systems and host systems with Windows NT and Windows 2000. Use the correct
application code or database manager to regulate concurrent read or write access.
For example:
v You could assign an 8-GB disk partition (logical volume) to multiple separate
UNIX-based host systems.
If host systems are using software that can regulate access to data, then one
host system could write data while a second host system initiates a query.
v Two IBM RS/6000 host systems with the Oracle Parallel Edition could also share
a single copy of data.
Oracle also runs with other UNIX operating systems.
Application software or database manager software is responsible for the integrity of
the database. This includes access management and access locking. The ESS
provides the physical access to the data. Sharing of data is now possible without
transferring files, creating second copies of data, or other methods that you may
have used previously.
IBM Subsystem Device Driver
You can install the IBM Subsystem Device Driver in your open host system to
improve data availability and performance. The IBM Subsystem Device Driver uses
redundant connections between the host server and disk storage in an ESS. These
connections comprise many different components through which data flows during
input and output processes.
Redundancy and the ability to switch between these components provides many
different paths on which the data travels. See
Version 1 Release 1
for more information.
System/390 availability features
This section describes the following availability features and other System/390
functions:
v Extended remote copy
v Using Extended Remote Copy for outages
v Concurrent Copy
v Multiple allegiance
v Parallel Access Volumes
For more detailed descriptions of extended remote copy and concurrent copy and
procedures about how to use them, see
Extended Remote Copy
The ESS supports the Extended Remote Copy (XRC) feature on System/390 hosts.
XRC mirrors data on the ESS to a remote location for disaster recovery. It ensures
data consistency across all volumes that you have defined for mirroring. The
volumes can reside on several different ESSs. XRC can mirror the volumes over
several thousand kilometers from the primary site to the recovery site.
IBM Subsystem Device Driver,
IBM Advanced Copy Services
.
Using Extended Remote Copy for outages
With ESS XRC you can suspend or resume service during an outage. You do not
have to terminate your current data-copy session. You can suspend it and restart it.
Chapter 1. Introduction19
Only data that has changed during the outage needs to be resynchronized between
the copies, a simple operation that greatly reduces resynchronization time.
Note: The ESS supports this function on System/390 MVS operating systems only.
If you need to change the default setting for an outage, you can do so through the
ESS Copy Services Web interface. The Copy Services servers must be identified
and set up by IBM service personnel prior to your using the ESS Copy Services
Web interface.
See the
procedures for changing the XRC time-out from the ESS Copy Services Web
interface.
IBM Enterprise Storage Server Web Interface User’s Guide
for the
Concurrent Copy
The ESS supports the Concurrent Copy feature on System/390 hosts. Concurrent
Copy, like FlashCopy, creates point-in-time copies of volumes. However, Concurrent
Copy can also copy data sets from a source volume. It can copy the data to tape,
an optical library or to another DASD device. Data systems like the IBM DB2
product, can also initiate Concurrent Copy.
®
Multiple allegiance
The Multiple Allegiance feature allows the ESS to accept an input/output (I/O)
request from each channel path group for a unit address. The request can be
concurrent with other I/O requests. The ESS queues requests and then initiates
them. This allows you to have multiple access to a shared volume (logical device)
without affecting performance.
Using the Multiple Allegiance feature can improve ESS throughput and
performance.
Parallel Access Volume
The Parallel Access Volume (PAV) feature allows you to access a CKD volume on
an ESS in parallel. With PAV, you assign a base address to a CKD logical device.
You can use any of the 256 available addresses as the base device address. You
then configure alias addresses for the CKD logical device.
You can then dynamically reassign any configured alias address from one CKD
logical device to another CKD logical device. Address types are:
v Base address
The base address is the unique unit address of a volume. The ESS associates
storage space with this address.
v Alias address
You can assign several alias addresses to the base address. The ESS runs I/O
operations to the alias address against the base address.
With PAV, a single System/390 can simultaneously process multiple I/O
operations to the same logical volume. This can reduce volume contention.
See the
PAV.
IBM Enterprise Storage Server User’s Guide
Descriptions and comparisons of the IBM Enterprise Storage Server
models
This section describes the ESS models and features.
20ESS Introduction and Planning
for more information on using
Power differences between models
Table 1 shows the power differences between the ESS models.
Table 1. Power differences between ESS models
AttributeModels E10 and F10Models E20 and F20
Dual power cordsYesYes
PowerSingle phase (50/60 A)Three phase (50/60 A)
DDM support16 - 6416 - 128
Features
Table 2 compares the ESS features that are available for hosts that have small
computer system interface (SCSI) interfaces with hosts that have Enterprise
Systems Connection (ESCON) interfaces.
Table 2. IBM Enterprise Storage Server feature comparison
FeatureHost Systems with SCSI or
Fibre-Channel Interfaces
AttachmentParallel attachment, SCSI
v 1 - 15 targets per bus
v 1 - 64 logical units per target
128 fibre-channel attached hosts per
fibre port (see “Fibre-channel host
adapters” on page 30 for information
on loop topology)
Host systems supported
Control unit emulationNo
Host adapters,2-16(See Note 1.)
Software device drivers
v IBM AS/400
v IBM RS/6000 and RS/6000 SP
v HP 9000
v Sun
v Compaq AlphaServer
v Data General
v IBM Netfinity and Intel-based PCs
v IBM NUMA-Q
v Ultra-SCSI, dual port (for attaching
host systems with SCSI-2 or
SCSI-3 adapters)
v Fibre channel, single port (for
attaching host systems with
fibre-channel adapters)
v AS/400 hosts
– 9337 Models 580, 590
v UNIX , Window NT and Windows
2000 hosts
– Models E10, E20, F10, and F20
Host Systems with ESCON
Interfaces
ESCON attachment
v 1 - 16 controller images
v 1 - 256 devices per control unit
image
v IBM ES/9000
v IBM 3090
v IBM S/390 Models 7060, 9672, and
2003
v 3990 Model 3, Model 3 transaction
processing facility (TPF), and
Model 6
vModels E10, F10, E20, and F20
ESCON
MVS, VM, VSE, TPF
Chapter 1. Introduction21
Table 2. IBM Enterprise Storage Server feature comparison (continued)
FeatureHost Systems with SCSI or
Fibre-Channel Interfaces
Disk drive module (DDM) formatFixed block address (FBA)Count key data (CKD)
Peer-to-Peer remote copy (PPRC)
(See Notes 2 and 3.)
Concurrent CopyNoYes
Extended Remote Copy (XRC)NoYes
XRC planned outageNoYes (MVS operating systems)
FlashCopy (See Note 3.)YesYes
IBM Subsystem Device Driver (see
1. See the ESS web site at
www.ibm.com/storage/hardsoft/products/ess/refinfo.htm
for details about host-system adapters supported with the ESS. See the following web site for details
2. This feature requires that you install an ESCON adapter on both the primary ESS and the secondary ESS.
3. The ESS does not support PPRC or FlashCopy on the AS/400.
YesYes
YesNo
Host Systems with ESCON
Interfaces
Table 3 lists the physical features for the ESS.
Table 3. IBM Enterprise Storage Server physical features
FeatureDescription
Continuous availability, designed to virtually eliminate
single points of failure or repair (See Note 1.)
Dual-cluster configuration
SSA device adaptersEight serial storage adapter loops (maximum)
Spare DDM (See Note 2.)
Read/write functions
v Cluster-processor complex failover
v Device adapter failover
v Concurrent maintenance
v Failover/failback
v Eight cluster processors
v Cache: 6 GB for Models E10 and E20, 8 GB standard
and optional 16 GB for Models F10 and F20
v NVS: 384 MB
v RAID 5 (6+P+S, 7+P)
v RAID reconstruction with spare DDM
v Read/write cache
v Fast-write NVS in storage server
v Maximum sequential bandwidth
– 180 MB/second read
– 140 MB/second write
22ESS Introduction and Planning
Table 3. IBM Enterprise Storage Server physical features (continued)
FeatureDescription
Service
Customer interface
DDMs (See Note 2.)
Support of 8-packs
Expansion enclosureSupported by Models E20 and F20
Notes:
1. The ESS requires two spares per SSA loop with RAID. For enhanced availability, IBM recommends that you
install the IBM Subsystem Device Driver on your open host system.
2. DDM configuration:
a. DDMs are either all 9.1 GB, all 18.2 GB, or all 36.4 GB.
b. DDM capacity assumes a RAID-5 configuration.
v Mobile solutions terminal or equivalent
v Remote service
v Call home
v Concurrent maintenance
v Simple Network Management Protocol (SNMP)
v Storage server Ethernet attachment (10Base-T)
v Customer workstation
v Web interface
v 16 - 384 in increments of 8 (8-pack)
v Capacity
– 105 GB to 2.8 TB (9.1 GB DDMs)
– 210 GB to 5.6 TB (18.2 GB DDMs)
– 420 GB to 11.2 TB (36.4 GB DDMs)
v 36.4 GB (40 MBps)
v 18.2 GB (40 MBps)
v9.1 GB (40 MBps)
Logical subsystems
IBM configures the ESS as logical containers that are known as logical subsystems
(LSSs). The limit is 16 LSSs each for count-key-data (CKD) and fixed block (FB)
format.
Note: If you reduce the CKD LSS limit to zero, then no Peer-to-peer copy functions
IBM advises that you consider reducing the maximum LSSs limit (to eight or zero) if
you do not intend to create more than eight LSSs. Also reduce the maximum LSS
limit if you plan to create only CKD or FB data on your ESS. Reducing the
maximum LSS limit reduces the cache space that the ESS uses to maintain the
LSS structures (performance tuning).
Note: If you increase or decrease the LSS at a future date, you will need to
will execute. CKD LSS limit must be no lower then eight to support
peer-to-peer copy functions for Open only machines.
reinitialize the ESS in order for the change to take effect.
Chapter 1. Introduction23
24ESS Introduction and Planning
Chapter 2. Planning the physical configuration
This chapter lists the feature codes for the required and optional features for the
ESS, and gives planning information for the features. Use the feature codes to
order the following software components and hardware components:
v United States-government orders
v Power
v Adapter cards
v Memory capacity
|
United States-government orders
v Physical configuration feature codes and options
v Connection hardware
v Language for the operator panel
v Requirements for attaching 7133 drawers
v ESS Network (ESSNet) installation requirements
v Physical configuration changes
v Licensed internal code and optional software
See “Physical configuration options” on page 32 for a list of the physical
configuration options you may select.
Power features
Power outlets
For United States-government orders, select feature code 0983. This feature code
ensures that IBM manufactures the ESS in the United States of America.
This section includes information on requirements and feature codes for:
v Power outlets
v Power supply input voltage
v Power cables
v Remote power-control logic card
v Remote support (modem and modem switch)
v Extension cords
You need to supply the following power outlets for the ESS installation:
v High-voltage outlets:
– Two power outlets for the two ESS power cables
IBM recommends separate power sources for these outlets. This maximizes
availability by eliminating a single point of failure.
– Two power outlets for the two power cables for the expansion enclosure
v Regular-voltage outlets:
– Three power outlets for the ESSNet power cables (one for the workstation,
one for the display, and one for the hub). IBM provides the power cables for
the ESSNet
– One power outlet for the service terminal
This outlet needs to be within2m(6ft.) of the ESS.
– Two power outlets for remote support (one for the modem and one for the
switch)
IBM cannot install the ESS if your site does not meet these power requirements.
Uninterruptible power system
If you have an uninterruptible power supply (UPS) that prevents power interruptions,
have IBM connect the UPS to each ESS enclosure. Connect the UPS to the ESS
enclosures through mainline power cable 1. The ESS maintains the charge of the
main batteries through this mainline power cable.
Power supply input voltage
You need to specify one of the following feature codes for input voltage when you
order your ESS:
The following feature codes determine the type of power cable you receive with the
ESS Models. The ESS requires two power cables. The expansion enclosure also
requires two power cables. When you order an expansion enclosure, IBM includes
the correct power cables. IBM also provides the power cables for the ESSNet.
For Models E10 and F10, order the following feature codes:
9801Single Phase, 50, 60 Hz, 50 A (United States (U.S.), Canada,
9802Single Phase, 50 Hz, 50 A (Europe, Middle East, Africa (EMEA))
9803Single Phase, 50, 60 Hz, 60 A (Japan)
9986Single Phase, 50, 60 Hz, 50 A (Chicago)
For Models E20 and F20, order the following feature codes:
9851Three phase, 50, 60 Hz, 50 A for the U.S., Canada, LA, and AP
9852Three phase, 50 Hz for EMEA
9853Three phase, 60 Hz, 60 A for Japan and U.S.
9854Three phase, 50, 60 Hz, 60 A for U.S., Canada, LA, and AP
9987Three phase, 50, 60 Hz, 50 A for Chicago (U.S.)
9988Three phase, 50, 60 Hz, 60 A for Chicago (U.S.)
Remote support features
This section includes feature codes for remote support. This includes:
v Remote power control
v Remote support function
v Remote support function attachment
Latin America (LA), and Asia Pacific (AP)
Remote power control
This optional feature is for the logic card that supports remote power control within
the ESS:
26ESS Introduction and Planning
1001Remote power control
Remote support switch
Each ESS requires a modem for remote service access. When you attach the
remote-support switch to a modem, you can interconnect up to seven ESSs. For
remote support, you must order either feature code 2715 or feature code 2716:
2715Remote-support function
This feature provides:
v Remote-support switch and cables
v Modem
v ESSNet workstation (a personal computer)
v Monitor
v Three Ethernet cables, each 17 m (50 ft.) in length
v Ethernet Hub
v Power cables for the PC, hub, and monitor
v Hypertext Markup Language (HTML) file for the ESSNet
2716Remote-support function - additional attachment
This feature provides a pair of cables for attaching an ESS to the
remote-support switch. This feature also includes two ESSNet
Ethernet cables, each 17 m (50 ft.) in length.
See “Power cables for the remote-support switch by modem
country” for information about power cables.
Power cables for the remote-support switch by modem country
Select the power cable for the remote-support switch for your modem
country-group:
Cyprus, Great Britain (UK), Oman, United Arab Emirates (UAE)
9312Modem country-group M12
Colombia, Costa Rica, Ecuador, Peru, Republic of China,
Venezuela, Uruguay
9313Modem country-group M13
Argentina, Chile, Egypt, Greece, India, Indonesia, Korea, Lebanon,
Philippines, Saudi Arabia, Spain, Thailand, Turkey
9314Modem country-group M14
Austria
9315Modem country-group M15
Switzerland
9316Modem country-group M16
Extension cords
Finland
9317Modem country-group M17
Australia
9318Modem country-group M18
Peoples Republic of China, Hong Kong, Malaysia, Singapore
Each ESS requires an extension cord for use by service personnel. (These cords
are also known as convenience cords.) Specify one of the following feature codes
to order the type of extension cord you require at your site:
9401Extension cord country-group C01
Brazil, U.S., Canada
9402Extension cord country-group C02
Aruba, Bahamas, Barbados, Bermuda, Bolivia, Cayman Islands,
Columbia, Costa Rica, Curacao, Dominican Republic, El Salvador,
Ecuador, Guatemala, Guyana, Haiti, Honduras, Jamaica, Japan,
Liberia, Mexico, Netherlands Antilles, Nicaragua, Panama,
Philippines, Peoples Republic of China, Saudi Arabia, Surinam,
Trinidad Tobago, Venezuela
This section includes the feature codes and information for:
v Small computer system interface (SCSI) host adapters
v Fibre-channel host adapters and attachment
v Enterprise Systems Connection (ESCON) host adapters
v Device adapters
Also see the ESS Web site for details about the host system adapters that the ESS
supports:
Australia, Peoples Republic of China, New Zealand, Papua New
Guinea, Western Samoa
Bangladesh, Burma, Pakistan, South Africa, Sri Lanka
Antigua, Bahrain, Brunei, Channel Islands, Cyprus, Fiji, Ghana,
Hong Kong, India, Iraq, Ireland, Kuwait, Malawi, Malaysia, Malta,
Nepal, Nigeria, Oman, Polynesia, Qatar, Sierra Leone, Singapore,
Tanzania, United Arab Emirates, Uganda, United Kingdom, Yemen,
Zambia
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
The ESS has four host adapter bays. Each bay supports up to four host adapters.
Each ESS supports 32 SCSI ports, 16 fibre-channel ports, or 32 ESCON channel
ports or any combination of SCSI, fibre-channel, and ESCON connections. The
ESS supports up to a total of 32 physical ports (16 host system adapters).
Chapter 2. Planning the physical configuration29
SCSI host adapters
The ESS provides an ultra-SCSI interface with SCSI-3 protocol for attachment to
host systems with UNIX, Windows NT, Windows 2000, and the OS/400 operating
systems. The interface also supports SCSI-2 protocol.
The ESS supports up to 32 ports; two per SCSI host adapter. Each port supports
an ultra-SCSI or SCSI-2 fast and wide differential-connection to the host system. A
SCSI-2 fast and wide differential connection is a subset of ultra-SCSI.
3002SCSI host adapter (optional1-16)
Order host cables separately (see “Connection hardware” on page 37).
Fibre-channel host adapters
The ESS supports the point-to-point topology, the switched fabric topology and the
fibre channel arbitrated loop topology, private loop profile. When using the loop
topology, the ESS has no restrictions on the number of hosts or devices that you
can attach on a loop, other than the architectural limit of 127. However, the loop
goes through a loop initialization process (LIP) whenever you add or remove a host
or device from the loop. LIP disrupts any I/O operations currently in progress. For
this reason, IBM recommends that you only have a single host and a single ESS on
any loop (point-to-point loop).
To have IBM install short-wave fibre-channel adapters on your ESS, order FC 3022
(IBM P/N 54G3384). This feature code includes a 31 m (93 ft), 50 µM short-wave
optics cable. These fibre-channel adapters incorporate short-wave laser
transmitters. You can order and have IBM install a maximum of 16 fibre-channel
adapters on the ESS. Each adapter has a single host port. See your IBM field office
about longer cables or 62.5 µM cable.
3022Fibre-Channel Short Wave host adapter (optional 2-16)
ESCON host-adapters
Each ESCON host adapter provides two ESCON channel interfaces for attachment
to up to 32 channels. Each ESCON channel supports 64 logical paths, for a total of
2048 paths.
3011ESCON host adapter (optional 2, 4, 6, 8, 10, 12, 14, and 16)
Order host cables separately (see “Connection hardware” on page 37).
Device adapters
The standard configuration for the ESS includes eight device (DDM) adapters.
Each device adapter provides two device loops (4 interfaces) that operate at up to
160 MB per second, depending on the DDM type that you attach. Each loop
supports up to 48 DDMs.
Because the device loops are between adapter pairs, both clusters 1 and 2 can
access all DDMs on a loop. See “Failover protection” on page 15 for the
advantages to this configuration.
Complimentary 31m, 50 micron host cable included.
30ESS Introduction and Planning
Reserved loops
IBM supports reuse of 7133 Models 020 and D40 drawers in a 2105 Model 100
expansion enclosure in an IBM Enterprise Storage Server configuration. Support
includes 7133 drawers in new 2105 Model 100 expansion enclosures. This support
provides investment protection for up to 12 of your existing IBM 7133 serial disk
drawers.
IBM service personnel add the Model 100 to the loops you reserved with feature
code 9904. FC 9904 reserves two loops; the limit is four reserved loops. A loop
refers to the wiring that is needed to address the storage. Figure 8 shows reserved
loops.
DA
Pair 1
DA
Pair 2
DA
Pair 3
DA
Pair 4
Figure 8. Reserved loops
|
|
See “Feature codes and requirements for attaching 7133 drawers” on page 36 for
the needed requirements in order to attach Model 100 expansion racks.
Memory capacity features
The ESS Models E10 and E20 have the following memory capacity:
v Standard 6 GB of cache, 3 per cluster
v 384 MB (192 MB per cluster) of nonvolatile storage (NVS)
Loop A
8-Pack
Loop B
8-Pack
Loop A
8-Pack
Loop B
8-Pack
Loop A
8-Pack
Loop A
8-Pack
Loop A
8-Pack
Loop B
8-Pack
Loop A
8-Pack
Loop B
8-Pack
Loop A
8-Pack
Loop A
8-Pack
Loop A
8-Pack
Loop B Reserved by FC9904
Loop A
8-Pack
Loop B Reserved by FC9904
Loop A
8-Pack
Loop A
8-Pack
DA
Pair 1
DA
Pair 2
DA
Pair 3
DA
Pair 4
S008708
The ESS Models F10 and F20 have the following memory capacity:
|
|
|
|
v Standard 8 GB of cache, 4 per cluster with FC 4002. IBM delivers FC 4002 on
the ESS unless you specify the following option:
– 16 GB of cache, FC 4004
v 384 MB (192 MB per cluster) of nonvolatile storage (NVS)
Physical configuration features and options
This section includes the feature codes for:
v DDM cages and 8-packs
v physical configuration options
v Storage on demand
Chapter 2. Planning the physical configuration31
DDM cages and 8 packs
The Models E10 and F10 support one DDM cage. Models E20 and F20 support two
DDM cages.
Each DDM cage supports eight 8-packs (64 DDMs), four in the front, and four in the
rear. IBM will ship the appropriate number of cages, based on the number of
8-packs you order.
The feature numbers for ordering 8-packs in different DDM sizes for the ESS cages
are:
IBM includes device cables for the 8-packs that IBM installs in the factory. You must
order device cables for the 8-packs that you have service personnel install in the
field.
Expansion enclosures
The expansion enclosures (feature code 2100) support one, two, three, or four
DDM cages.
Each DDM cage supports eight 8-packs (64 DDMs), four in the front, and four in the
rear.
Note: The Model E10 does not support the expansion enclosure.
Populating the IBM Enterprise Storage Server
You can build the maximum configuration for an ESS with the expansion
enclosures.
If you order the expansion enclosure from the factory, IBM populates the expansion
enclosure with 8-packs in the following order:
You can order the following physical configurations for your ESS:
v Ultra-high-performance configuration with arrays that include only 9.1-GB DDMs
v High-performance configuration with arrays that include only 18.2-GB DDMs
v Capacity configurations with arrays that include only 36.4-GB DDMs
Standard configuration provides:
v 6 GB of cache for Models E10 and E20
32ESS Introduction and Planning
v 8 GB of cache for Models F10 and F20. Also see “Cache” on page 16 for an
optional cache increase.
v 384 MB of nonvolatile storage (NVS)
v Eight SSA device adapter cards
v DDMs assigned to optimum serial loops
v Storage that is allocated as RAID or non-RAID
Note: AS/400 storage must be RAID.
v System/390 and zSeries storage defined as either 3380 or 3390 track format
v Emulated LUNs defined for the UNIX, OS/400, Windows NT, and Windows 2000
operating systems
Ultra-high-performance configurations
You can order the ultra-high-performance configuration in two capacities for Models
E10, E20, F10, and F20. This configuration supports only arrays with 9.1-GB
DDMs.
Table 4. Ultra-high-performance configuration
Feature CodeCapacityDescriptionModels
9601420 GB8 eight-packsE10, F10, E20, and F20
9602840 GB16 eight-packsE20 and F20
High-performance configurations
The high-performance configurations in Table 5 support only arrays with 18.2-GB
DDMs.
Table 5. High-performance configurations
Feature CodeCapacityDescriptionModels
9621420 GB4 eight-packsE10, F10, E20, and F20
9622630 GB6 eight-packsE10, F10, E20, and F20
9623840 GB8 eight-packsE10, F10, E20, and F20
96301050 GB10 eight-packsE20 and F20
96241260 GB12 eight-packsE20 and F20
96311470 GB14 eight-packsE20 and F20
96251680 GB16 eight-packsE20 and F20
96322170 GB20 eight-packs, and
The capacity configuration supports only arrays with 36.4-GB DDMs.
Table 6. Capacity configurations
Feature CodeCapacityDescriptionModels
9646840 GB4 eight-packsE10, F10, E20, and F20
96471260 GB6 eight-packsE10, F10, E20, and F20
96411680 GB8 eight-packsE10, F10, E20, and F20
96502100 GB10 eight-packsE20 and F20
96422520 GB12 eight-packsE20 and F20
96512940 GB14 eight-packsE20 and F20
96433360 GB16 eight-packsE20 and F20
96524340 GB20 eight-packs, and
expansion enclosure
96485320 GB24 eight-packs, and
expansion enclosure
96536300 GB28 eight-packs, and
expansion enclosure
96447280 GB32 eight-packs, and
expansion enclosure
96548260 GB36 eight-packs, and
expansion enclosure
96499240 GB40 eight-packs, and
expansion enclosure
965510 220 GB44 eight-packs, and
expansion enclosure
964511 200 GB48 eight-packs, and
expansion enclosure
E20 and F20
E20 and F20
E20 and F20
E20 and F20
E20 and F20
E20 and F20
E20 and F20
E20 and F20
ESS storage on demand
|
|
|
|
|
|
|
|
|
|
|
IBM offers a storage–on-demand feature called step-ahead storage. With the
step-ahead feature you can purchase an ESS Model F20 with extra storage (18.2
or 36.4 GB drives) and use the extra storage when you need it.
This option is particularly useful when you have dynamic or unpredictable growth, or
if you just want the assurance that the storage will be there when you need it. You
may activate the stand-by capacity without interruption to your work. IBM requires
payment for the on-demand capacity upon your activation of the storage.
To get storage on-demand you must:
v Place a new order of an ESS Model F20. The order includes ESS standard
configuration plus step ahead feature codes.
34ESS Introduction and Planning
|
|
|
|
|
|
|
Note: You are billed for the standard configuration that you ordered plus a
carrying fee for the step-ahead storage.
v Sign a contract with IBM wherein you agree to purchase the step-ahead storage
when you configure it for use. The purchase must be no later than one year after
you activate the storage.
v Enable the ESS call-home function, and leave it enabled to allow IBM to monitor
your activation of the step-ahead storage.
v The Call Home heartbeat interval must not be set to 0.
Feature codes for step-ahead storage
Use the following feature codes to order the ESS Model F20 with step ahead
storage. The step-ahead carrying fee is included in the price of these step-ahead
configuration features:
FC 2132
Eight pack with 18.2 GB DDM
FC 2133
Eight pack with 36.4 GBDDM
Table 7. High-performance Configurations with 18.2 GB DDMs
Capacity
Increments
(GB)
420210630No9521(4) 2122, (2)
630210840No9522(6) 2122, (2)
8402101050No9523(8) 2122, (2)
10502101260No9530(10) 2122, (2)
12602101470No9524(12) 2122, (2)
14702101680No9531(14) 2122, (2)
16804902170Yes9525(16) 2122, (4)
21704902660Yes9532(20) 2122, (4)
26604903150Yes9526(24) 2122, (4)
31504903640Yes9533(28) 2122, (4)
36404904130Yes9527(32) 2122, (4)
41304904620Yes9534(36) 2122, (4)
46204905110Yes9528(40) 2122, (4)
51104905600Yes9535(44) 2122, (4)
Step ahead
Capacity
Increments
(GB)
Total
Capacity
(GB)
Expansion
Enclosure
(FC 2100)
Feature
Code
Number of
Eight Pack
Feature
Codes
2132
2132
2132
2132
2132
2132
2132
2132
2132
2132
2132
2132
2132
2132
Chapter 2. Planning the physical configuration35
Table 8. Capacity Configurations with 36.4 GB DDMs
Capacity
Increments
(GB)
8404201260No9546(4) 2123, (2)
12604201680No9547(6) 2123, (2)
16804202100No9541(8) 2123, (2)
21004202520No9550(10) 2123, (2)
25204202940No9542(12) 2123, (2)
29404203360No9551(14) 2123, (2)
33609804340Yes9543(16) 2123, (4)
43409805320Yes9552(20) 2123, (4)
53209806300Yes9548(24) 2123, (4)
63009807280Yes9553(28) 2123, (4)
72809808260Yes9544(32) 2123, (4)
82609809240Yes9554(36) 2123, (4)
924098010,220Yes9549(40) 2123, (4)
10,22098011,200Yes9555(44) 2123, (4)
Step ahead
Capacity
Increments
(GB)
Total
Capacity
(GB)
Expansion
Enclosure
(FC 2100)
Feature
Code
Number of
Eight Pack
Feature
Codes
2133
2133
2133
2133
2133
2132
2133
2133
2133
2133
2133
2133
2133
2133
Feature codes and requirements for attaching 7133 drawers
For protection of your assets, IBM supports attachment of your existing 7133
drawers to an ESS in a new 2105 Model 100 expansion enclosure. Use:
v FC 1121 to attach the first new Model 100 expansion enclosure
v FC 1122 to attach a second new Model 100 expansion enclosure, as a follow-on
to FC 1121
These feature codes have the following requirements:
v The LIC in the ESS to which you are attaching the 2105 model 100 expansion
enclosure must support attachment of 7133 drawers.
v The 2105 Model 100 installation must meet the floor loading and service
clearance requirements as specified in “Service clearance and floor-loading
requirements for the ESS” on page 55.
36ESS Introduction and Planning
v You must fill out custom configuration work sheets, using a modified version of a
Define Disk Groups work sheet that closely matches the storage capacity being
installed with the Model 100 expansion enclosures and 7133 drawers. The 7133
drawer will be configured as 2 disk groups. The disk groups can be either RAID
5 arrays or non RAID disks. Logical configuration of the 7133 drawers is only
supported via ESS Specialist. See the
Configuration Planner
v You cannot attach the Model 100 to an ESS model that already has an ESS
expansion enclosure (FC 2100).
v You reserved the necessary device loops in the ESS with FC 9904
With two FC 9904 (four reserve loops), you can attach up to a maximum of
twelve 7133 Model 020 or Model D40 drawers. With one FC 9904 (two reserve
loops), you can attach up to the maximum of six 7133 Model 020 or Model D40
drawers.
v The 7133 drawers can only be installed in a new Model 100 (FC 1121 and FC
1122). The drawers must meet the following requirements:
– When attached to an ESS, up to six 7133 drawers can be installed in a Model
100 rack. A maximum of two Model 100s can be attached to an ESS.
– Only 7133 Model 020 and 7133 Model D40 drawers can be attached to the
ESS.
– You cannot attach drawers that have less than 16 DDMs to the ESS. All the
DDMs must be the same capacity. The ESS cannot support mixed DDMs on
the same loop.
|
|
– Any 7133 drawers you install must meet the 7133 drawer compatibility
requirements above.
– You need to migrate or remove all data on 7133 drawers and disband the
ranks/arrays before installing the 7133 drawers in the model 100.
.
IBM Enterprise Storage Server
See “Appendix C. Adding and Removing Drawers and Racks” on page 91 for more
information on attaching 7133 drawers and racks to the ESS.
Connection hardware
This section includes the feature codes for:
v SCSI host cables
v Fibre-channel cables
v ESCON host cables
v Remote power-control attachment cables
SCSI host cables
You need to order cables for each host adapter. Each host adapter provides two
host connections (ports). Each host connection has a terminator; the connection to
the ESS must be at the end of the SCSI bus.
For each SCSI host adapter (FC 3002), order two SCSI host cables:
9701Ultra-SCSI cable (10 m for UNIX and Windows NT)
9702Ultra-SCSI cable (20 m for UNIX and Windows NT)
9703SCSI-2 fast and wide cable (10 m for IBM RS/6000 MCA adapter)
9704SCSI-2 fast and wide cable (20 m for IBM RS/6000 MCA adapter)
9705SCSI-2 fast and wide cable (10 m for IBM AS/400)
Chapter 2. Planning the physical configuration37
9706SCSI-2 fast and wide cable (20 m for IBM AS/400)
9707SCSI-2 fast and wide cable (10 m for Sun and Hewlett Packard PCI
9708SCSI-2 fast and wide cable (20 m for Sun and Hewlett Packard PCI
9709SCSI-2 fast and wide cable (10 m for Hewlett Packard PCI single
9710SCSI-2 fast and wide cable (20 m for Hewlett Packard PCI single
All cables support a 2-byte-wide bus with differential drivers. If you require a cable
length that is not listed above, see your IBM field office.
Fibre-channel cables
For fibre-channel cable, order FC 3022 (IBM P/N 54G3384) which includes a
fibre-channel short wave adapter card and a 31 m (93 ft), 50 µM short-wave optics
cable. See your IBM field office if additional cables, longer cables, or 62.5 µM
cables are required.
ESCON host cables
Each ESCON host adapter provides two host connections. Order two ESCON
cables for each adapter for System/390 hosts. You can have your IBM field office
order the cable using the OMCABLE transaction in Advanced Administrative
Systems (AAS).
dual port)
dual port)
port)
ports)
Each feature code 3011 gives you one host adapter card. Each adapter card
requires two ESCON attachment cables: either the standard riser-rated cable, cable
group number 3797, or the plenum-rated cable, cable group number 8486. The
following table gives the connector IDs to order for the cables.
Table 9. ESCON cable connectors
Number of ESCON Host
Adapter Feature Code 3011s to
Order
The operator-panel language feature determines the language for operator panel
labeling. If you do not specify a language, the default is English.
2924English
2928French
2929German
2930Japanese
2931Spanish
2932Italian
2935Canadian French
2938Brazilian Portuguese
Number of CablesConnector ID
11, 13, 15
2942Belgian Dutch
2962Chinese Traditional (ROC)
Chapter 2. Planning the physical configuration39
2969Korean
2980UK English
Configuration changes
After IBM performs the initial logical configuration during ESS installation, use the
ESS Specialist Web interface to reconfigure or deconfigure the logical configuration.
IBM can only perform capacity upgrades that are within the same DDM size.
Optional one-year warranty
The ESS comes with a three-year warranty. IBM also offers a one-year warranty.
See your IBM field office for details.
Licensed internal code and optional software
The ESS includes licensed internal code (LIC) for the following features:
v Multiple allegiance
v I/O priority queues
v Concurrent copy
This section describes the following optional features for the ESS:
v Parallel Access Volumes
|
v ESS Copy Services
IBM service personnel enable these features for you. Order the feature code for the
capacity that is equal to or greater than the capacity of your ESS.
Parallel Access Volumes (PAV)
Order the PAV capacity that you need for your System/390 and zSeries hosts by
using the following feature codes:
1800Up to 0.5 terabyte (TB)
1801Up to 1 TB
1802Up to 2 TB
1803Up to 4 TB
1804Up to 8 TB
1805Larger than 8 TB
OS/390 operating systems that support PAV include: V1R3, V2R4, V2R6, V2R7
(with program temporary fixes); and DFSMS/MVS
ESS Copy Services
This section lists the following information:
v Feature codes for FlashCopy
v Feature codes for extended remote copy (XRC)
v Feature codes for peer-to-peer remote copy (PPRC)
|
|
v Guidelines for enabling and using ESS Copy Services
v Planning ESS Web Copy Services configuration
™
1.3.0, 1.4.0, and 1.5.0.
40ESS Introduction and Planning
See the
information on the ESS command line interface (CLI) for open system hosts. You
can use the command-line interface from your host system to invoke PPRC and
FlashCopy.
See “FlashCopy and PPRC restrictions for open system hosts” on page 18 for
additional information about PPRC and FlashCopy.
IBM Enterprise Storage Server Host Systems Attachment Guide
for
Feature codes for FlashCopy
Order the capacity you need for your System/390 hosts, SCSI, and fibre-channel
attached host systems by using the following feature codes:
1830Up to 0.5 TB
1831Up to 1 TB
1832Up to 2 TB
1833Up to 4 TB
1834Up to 8 TB
1835Larger than 8 TB
Feature codes for Extended Remote Copy (XRC)
Order the Extended Remote Copy feature for the total capacity you need using the
following feature codes:
1810Up to 0.5 TB
1811Up to 1 TB
1812Up to 2 TB
1813Up to 4 TB
1814Up to 8 TB
1815Larger than 8 TB
Feature codes for peer-to-peer remote copy
Order the capacity you need for your System/390 hosts, fibre-channel, and SCSI
attached host systems for
feature codes:
1820Up to 0.5 TB
1821Up to 1 TB
1822Up to 2 TB
1823Up to 4 TB
1824Up to 8 TB
1825Larger than 8 TB
both
the primary and secondary ESS. Use the following
Guidelines for enabling and using ESS Web Copy Services
This section gives an overview of ESS Copy Services followed by the guidelines for
enabling and using ESS Web Copy Services.
OS/390
You can access and control ESS Copy Services functions from OS/390 host
systems with OS/390 DFSMS. Alternatively, you can access and control ESS Copy
Services functions for OS/390 host systems using the ESS StorWatch Web Copy
Chapter 2. Planning the physical configuration41
Services function. The default setting for ESS is disable ESS Web Copy service
Interface for S/390 hosts. If you are interested in using the Web Copy service
Interface, you must identify the information in “Appendix B. Communication
Resources (ESS Web Copy Services) work sheet” on page 89.
Note: You can invoke Extended Remote Copy (XRC), Concurrent Copy, PPRC,
and FlashCopy for IBM System/390 hosts with the IBM/System390 command
functions.
Open Systems
ESS Web Copy Services is a Java-based client server application. The application
consists of one primary server component, an optional backup server component,
and one or more client components. The backup server refers to a server that can
be started as a primary server in the event that the first primary server fails.
The implementation of these application components in a collection of ESS clusters
forms an ESS Web Copy Services server group. This implementation allows users
to define, execute and view the status of Copy Services functions and tasks in, and
between the server group clusters. For example, the ESS Web Copy Services
application allows a user to:
v Initiate a FlashCopy task for two volumes in one ESS cluster
v Establish PPRC relationships for volumes in two ESS clusters
v Execute predefined PPRC and FlashCopy tasks
Each ESS cluster within a server group runs the ESS Web Copy Services client
component. The user designates one of the ESS clusters in a server group to also
run the primary server component, and optionally designates another ESS cluster to
run the backup server component. If the server group consists of ESS clusters
installed at different locations, then the primary and backup servers should be
assigned to ESS clusters that are remote from each other.
The ESS clusters that are part of a Copy Services (CS) server group use the
TCP/IP network to communicate. You can configure two ESS Copy Services
servers to a group. Each ESS Copy Services server group manages four clusters
and a maximum of 2048 volumes. You have identified the assignment of the TCP/IP
addresses within the Communication work sheet given to the CE during ESS
installation. You enter this information on the Copy Services work sheet. See
“Chapter 4. Planning for communication” on page 65 for the procedures for filling in
this work sheet. (In order for this communication to work well, some type of name
resolution has to be running in the users network.) IBM recommends using a
domain name server (DNS) for name resolution. DNS resolves the names of the
participating ESS clusters and enables ESS Web Copy Services to operate
correctly. This includes allowing the open system hosts to run CLI for Copy Services
automation. When DNS is not available, the IBM SSR can configure each ESS to
provide name resolution.
Users access the ESS Web Copy Services interface from the ESS Specialist
Introduction panel using an ESSNet console or a Web browser at a local
workstation. Access to the ESS Web Copy Services from a browser window
normally connects to the primary server, which has the overall view and control of
the server group Copy Services configuration. The backup server provides similar
view and control for handling when the primary server is unavailable. A user can
access the backup server if the primary server is unavailable. A user must manually
reset the Web Copy Services Function to connect to the backup server when the
primary server is unavailable as in Disaster Recovery actions.
42ESS Introduction and Planning
ESS Copy Services also includes a command-line interface (CLI). The CLI is a
Java-based application package that you may optionally install on your open system
host. The CLI application provides a set of commands that allow a user to write
customized scripts for a host system that will initiate predefined tasks in an ESS
Copy Services server application. You use the set of CLI commands to indirectly
control ESS PPRC and FlashCopy tasks within an ESS Copy Services server
group. The CLI is available for the following operating systems:
v AIX
v Solaris
v HP-UX
v Windows NT 4.0
v Windows 2000
See the following ESS Web site for details about supported operating system
levels.
www.storage.ibm.com/hardsoft/products/ess/supserver.htm
Before using either the ESS Web Copy Services interface or the Open host
command-line interface, you or IBM must perform the following tasks:
1. Purchase ESS Copy Services features (FlashCopy, PPRC, or XRC).
2. If the ESS machine has already been installed, then the ESS needs to be
upgraded to the 2105 LIC code that support Copy Services.
3. IBM installs and configures the ESS. The requirements include:
a. Connect the ESS to the ESSNET Network. Install DNS (recommended)
b. Install and activate the Copy Services LIC features.
Note: LIC features for F10/F20 is capacity limited. You can use the capacity
for Flash Copy and PPRC that you purchase. LIC features should be
installed before you configure the machine.
c. For PPRC, install ESS ESCON host adapters. If you specify the ESCON
feature code with your initial order for an ESS, IBM will install the ESCON
host adapters. After initial installation, you must order an MES to have IBM
install the adapters.
Note: ESS ESCON host adapters are required for PPRC because
communication in a peer-to-peer relationship is through the ESCON
channels.
d. For each ESS cluster in a Copy Services Server Group, decide if ESS Copy
Services commands should be enabled for S/390 volumes. Enter the
information in “Appendix A. Communication Resources work sheet” on
page 85.
Note: This information should be filled out for the SSR prior to the
installation of the ESS.
e. Configure the ESS clusters for the use of ESS Web Copy Services. For
each ESS in a Copy Services Server Group, enter the IP addresses of the
ESS clusters that you have identified as the primary and backup servers in
“Appendix B. Communication Resources (ESS Web Copy Services) work
sheet” on page 89.
Chapter 2. Planning the physical configuration43
f. Configure a domain name server (DNS) for ESS Copy Services. Enter the
information in “Appendix A. Communication Resources work sheet” on
page 85.
g. Logically configure the ESS, allocate storage, and create logical unit
numbers (LUNs).
h. Attach the ESSs to your host systems; this enables you to identify, create,
and copy volumes.
i. If the HOSTS are already installed, make sure that you are at the correct
levels of HOST Install, SDD, and CLI.
Note: There may be additional level requirements between CLI and the ESS
License Internal Code. When the SSR updates the ESS with new
microcode, there may be a CLI code update.
j. Install the command line interface (CLI) on your open system hosts. You can
use the command-line interface from your host system to invoke PPRC and
FlashCopy. CLI must have Java 1.1.8 support on the Open Host system. See
IBM Enterprise Storage Server Host Systems Attachment Guide
the
information about CLI.
4. Run cfgmgr or operating system environment, to have the host system
recognize the ESS volumes.
5. Run rsTestConnection to ensure that web Copy Services is running.
6. Run rsPrimeServer on your open host system.
This script notifies the ESS Copy Services server of the mapping of your host
system disks to ESS volume serial numbers. This task allows you to view the
Host system assigned volume with the Web Copy Services interface, from the
Volume panel.
for more
Notes:
a. You must first authorize users before they can initiate this script from your
host system. CLI commands provide security level protection. See the
Enterprise Storage Server Host Systems Attachment Guide
.
IBM
b. This script must be run whenever there are changes to the volumes
accessed on a specific host.
c. rsPrimeServer with -d option should be run when you remove a host from
attachment to the ESS machine to remove the mapping from Web Copy
Services Interface.
7. Run rsList2105s to get host disk to ESS volume association that can be used
in defining Copy Services tasks.
8. The PPRC device-physical configurations (source and target devices) must be
the same track format. Target volumes may be larger than the source volumes.
For example, you can do a FlashCopy froma9GBLUNtoa16GBLUNfor
data expansion.
See the
IBM Enterprise Storage Server Web Interface User’s Guide
for the
procedures on using PPRC and information about how to:
v Define disks to the primary host
v Access the secondary disks
v Control volume groups
v Perform disaster recovery
v Migrate data between storage servers
44ESS Introduction and Planning
See “Planning ESS Copy Services configuration” for examples of site configurations
for PPRC.
Planning ESS Copy Services configuration
This section provides examples of site configurations for Copy Services, and
explains why you might select a particular configuration.
Example of a PPRC operational environment
For this example, assume that you have two sites, Site A and Site B. Each Site has
a set of ESSs connected to the network. One of the ESS clusters at Site A has
been configured as the ESS Web Copy Services primary server. One of the clusters
at Site B has been configured as the ESS Web Copy Services backup server. Host
systems at both Site A and Site B have installed the CLI for control of ESS Copy
Services. ESS Copy Services code keeps data synchronized between the primary
and the backup server.
|
|
|
|
If for some reason, the Copy Services primary server is down, you can change the
management of all the ESS clusters to the backup Copy Services server. The
secondary Copy Services server then takes over the management of all the
remaining ESSs.
A typical PPRC physical configuration might include:
v A single logical storage server that is shadowed to a single secondary logical
subsystem
v All devices or a subset of devices in PPRC pairs
This applies to a user who might have:
v All production applications and data located in a primary site
v All secondary data located at a disaster-recovery site
Shadowing all data that is associated with a server to a backup site reduces the
operational management complexity. This includes determining what data (on a
file-by-file basis) the backup site requires to recover the application in the event of a
disaster since all data is replicated at the secondary site.
A single storage server mirrored to a secondary server
IBM recommends mirroring all logical subsystems at the primary site to an identical
logical subsystem at the secondary site. This includes:
v All production applications and data located in a primary site
v All secondary data located in a secondary or disaster recovery site. For more
information on disaster recovery, see the
Interface User’s Guide
.
IBM Enterprise Storage Server Web
Generally, the files associated with an application or application set are dynamic in
many environments. Consequently, you may choose to mirror all of the application
data. This configuration requires minimal application storage-management analysis
to guarantee optimal performance.
Bi-directional mirroring
With bi-directional mirroring, half of the devices are mirrored from ESS A to ESS B.
The remaining half are mirrored from ESS B to ESS A.
This configuration distributes all inputs/outputs (I/O) across two ESSs instead of
directing them to a single primary ESS.
Chapter 2. Planning the physical configuration45
A combination configuration
You can combine any options to be managed as a single logical subsystem to a
secondary-site logical subsystem (or bi-directional), such as:
v A volume list
v A logical volume group
This option depends on the amount of ESS storage your operational environment
has.
Any combination you select must meet these requirements:
v The PPRC configurations (source and target devices) must be the same track
format. Target volumes may be larger than the source volumes. For example,
you can do a FlashCopy froma9GBLUNtoa16GBLUNfordata expansion.
v PPRC source volumes and target volumes are mirror images of each other from
a host point of view. That is, all of the data that you can access from the primary
host is exactly the same across the source and target PPRC volume.
Note: The volumes must be in full duplex mode.
v Additional requirements for fibre-channel, SCSI-attached host systems (open
systems), and System/390 hosts:
– Because data on both the primary and secondary PPRC devices is identical,
the volume identifications are the same for both the source and the target
volumes. Typically operating systems for open systems hosts, and their
related file and related data base systems cannot easily manage LUNs with
identical device identification.
IBM recommends that, for operational simplicity, you attach and address the
PPRC primary devices from the primary production server. IBM recommends
that you also attach and address the PPRC secondary devices from the
secondary production server or the recovery server.
– The ESS protects open system PPRC secondary volumes from host access.
This protection ensures data integrity and data consistency between the
PPRC primary and secondary volumes.
|
|
|
|
|
|
|
|
|
|
|
Consequently, you must execute a task at the ESS Copy Services server to
terminate the PPRC pair before you can use the backup volumes. This action
recovers or returns the PPRC secondary device to simplex mode, allowing
host system access to secondary volumes. Another option is to do a
FlashCopy of the secondary volume without terminating the PPRC pair. The
FlashCopy can be used to read the secondary data at a particular point in
time.
v IBM also recommends the following:
– The Copy Services primary server be accessible from both the primary and
secondary sites.
– The primary and backup copy services servers should be physically located
on different sites for disaster recovery purposes.
|
|
IBM recommends that you configure ESS Copy Services primary/backup servers to
run on cluster 1.
IBM Subsystem Device Driver
The IBM Subsystem Device Driver feature supports multiple or redundant data
paths for shared LUNs. Multi-pathing reduces the potential for a single point of
failure on an ESS.
46ESS Introduction and Planning
See
IBM Subsystem Device Driver
for information about using this ESS option. This
book describes how to install and use the IBM Subsystem Device Driver on SCSI
and fibre-channel attached host systems to enhance availability for the ESS.
Chapter 2. Planning the physical configuration47
48ESS Introduction and Planning
Chapter 3. Installation planning
This chapter includes information for installation planning:
v Host system support
v Software requirements
v Equipment requirements
v Site requirements
Equipment requirements
Your shipment of the IBM Enterprise Storage Server includes:
|
|
|
|
v Two ESS cover keys. If you open the ESS, please be aware of IBM safety
concerns. The tag to the keys has the following caution notice:
CAUTION:
This machine is certified to be serviced by trained personnel only.
|
|
1062
v Licensed internal code (LIC) compact disc.
Note: IBM service enables or disables any LIC features on your ESS.
v Host interface cards for the ESS. See “Adapter features” on page 29 and
“Connection hardware” on page 37. Enterprise Systems Connection (ESCON),
small computer system interface (SCSI), and fibre-channel host adapters and
cables for the ESS.
v Compact disc for the host adapters.
v Compact disc that includes installation scripts for the 2105 (ESS) host
attachment for AIX and HP-UX , and installation instructions for the IBM
Subsystem Device Driver.
v Modems, modem switches, cables, and power cables for remote support. See
“Remote support switch” on page 27.
v The IBM workstation, cables, and power cables for ESSNet.
v The extension cord that the service provider uses to connect the service terminal
to a power outlet. See “Extension cords” on page 28.
v Compact disc for the IBM Subsystem Device Driver.
v Customer documents compact disc, SK2T-8770
This compact disc includes a softcopy of the ESS customer publications. See
“The ESS product library” on page xvi for a list of the books.
Additional items that are shipped with the ESS for use by authorized service
personnel, include:
v State-save diskettes
One set of blank diskettes that are used for extracting state-save information
during service.
Note: The ESS diskette drive only reads diskettes with 1.44-MB format that a
v Service documents compact disc, SK2T-8771
This compact disc includes softcopies of the ESS service guides, ESS parts
catalog, and the ESS customer publications.
v Hardcopies of the service guide.
v Two compact discs for the operating system.
v Compact disc for the operating system for program temporary fixes (PTFs).
v Compact disc for the operating system for service diagnostics.
You also need the following equipment for installing and operating the ESS:
v An analog telephone line near the ESS to enable remote support. The service
v Power cable connectors. The ESS requires two power cables that are country
|
|
|
v Power outlets that are compatible with the extension cords listed in “Extension
Engineering changes
IBM might periodically release engineering changes (ECs) to the materials in the
ship group to correct problems or provide additional support. IBM might ship ECs as
either mandatory or optional field bills. You should install the mandatory field bills as
directed by IBM.
interface provides an RS232 connection, through a modem switch, to the analog
telephone line.
dependent and location dependent. You need the correct connectors as identified
in “Power cable and power connector requirements” on page 60 and “Power
cable connectors” on page 61.
cords” on page 28. Outlets must be within3m(9ft)oftheESS. See “Power
features” on page 25 for details on power requirements.
Notes:
1. The compact disc label indicates the EC level of the LIC.
2. The ESS stores three EC levels of LIC code for the ESS and for any DDMs that
IBM has installed on the ESS. The ESS stores a new EC level prior to
activating it as the current level.
Site requirements for the ESS
See Table 11 on page 51 for the physical characteristics of the IBM Enterprise
Storage Server.
IBM ships all models in an Arbo Crate. The Arbo Crate weighs 228 kg (504 lbs).
The local carrier is responsible for delivering the ESS as close to its final location
as possible. The carrier is also responsible for unloading the ESS and removing the
crate and returning it to IBM.
To compensate for the weight of the ESS models, IBM recommends that the
loading dock ramp at your site does not exceed an angle of 12°.
CAUTION:
A fully configured unit in the crate can weigh up to 1500 kilograms (3305
pounds). Use of less than three persons to move it can result in injury.
1060.
Table 11 on page 51 gives the dimensions and weights of the ESS models.
50ESS Introduction and Planning
|
|
||||||
|
|
|
|
|
|
|
|||
||
||
|
|
|
|
|
|
|
|
|
||
||
|
|
||
||
|
|
|
|
|
|||
||
||
|
|
|
|
|
|
|
|
|
||
||
|
|
||
||
|
|
|
|
|||
|
||
||
|
|
|
|
|
|
||
||
|
|
|
|
||
||
|
|
|
|
|
|
||
||
|
|
|
|
||
||
|
|
|
|
||
||
|
|
|
|
|
|
Table 11. ESS dimensions and weights
ModelDimensions, Meters
(Inches) (See Note 1.)
E10 or F10
E20 or F20
Model E20 or
F20 with the
expansion
enclosure
(See Notes 3
and 5.)
Model 100
(See Note 6)
Height1.796
(70.7)
(See
Note
2.)
Width1.383
(54.4)
Depth0.91
(35.8)
Height1.796
(70.7)
(See
Note
2.)
Width1.383
(54.4)
Depth0.91
(35.8)
Height1.796
(70.7)
Width2.938
(115.7)
Depth0.91
(35.8)
Height1.780
(70)
WidthWidth
0.840
(33)
DepthDepth
1.305
(51)
Dimensions with Arbo
Crate, Meters (Inches)
Height2.075
(81.69)
(See
Note
2.)
Width1.573
(62.00)
Depth1.067
(42.00)
Height2.075
(81.69)
(See
Note
2.)
Width1.573
(62.00)
Depth1.067
(42.00)
Height2.075
(81.69)
Width3.128
(123.30)
Depth1.067
(42.00)
Height2.045
(80.5)
WidthWidth
1.016
(40)
DepthDepth
1.499
(59)
Maximum
Weight
(Fully
Configured)
1000 kg
(2200 lbs)
1204 kg
(2650 lbs)
2545 kg
(5600 lbs)
770 kg
(1696 lbs)
Maximum
Weight with
Arbo Crate
1228 kg
(2704 lbs)
1432 kg
(3154 lbs)
(See Note
4.)
928 kg
(2046 lbs)
Chapter 3. Installation planning51
Table 11. ESS dimensions and weights (continued)
ModelDimensions, Meters
(Inches) (See Note 1.)
Notes:
1. These dimensions include casters and covers. (The casters are recessed and do not
require extra clearance.)
2. These dimensions exclude the top cover. With the top cover, the height is 1.915 m (75.3
in.).
3. Models E10 and F10 do not support the expansion enclosure.
4. Models E20 and F20 and the expansion enclosure are shipped in separate crates. With
the Arbo Crate, the expansion enclosure weighs 1500 kg (3305 lbs).
5. Install the expansion enclosure to the right (as you face its front) of Models E20 and
F20.
6. Install the Model 100 to the right (as you face its front) of Models E10/E20 and E10/F20.
Dimensions with Arbo
Crate, Meters (Inches)
Maximum
Weight
(Fully
Configured)
Maximum
Weight with
Arbo Crate
IBM recommends that you install the ESS on a raised floor. When you install the
ESS, you can cut out tiles for cable entry at the front. IBM recommends that you
place two fully perforated tiles in front of the ESS for cooling.
Center all openings and cutouts at the front of the enclosures. See Table 12 for the
dimensions for the cutouts. See Figure 9 on page 53 for the cutout locations, and
the clearances that are required for the doors. The ESS has recessed casters that
do not require extra clearance.
Table 12. Cable cutout dimensions (maximum size)
ModelFloor Cutouts, Meters (Inches)
E10, F10, E20, and F200.10 x 0.91 (4 x 36)
Expansion enclosure0.10 x 0.25 (4 x 10)
100Front: 0.15 x 0.15 (6 x 6)
Rear: 0.15 x 0.15 (6 x 6)
52ESS Introduction and Planning
138.4
(54-1/2)
129.5
(51)
114.3
(45)
74.9
(29-1/2)
86.3
(34)
68.9
(27-1/8)
56.5
(22-1/4)
19.9
(7-7/8)
7.6
(3)
4
22.8
(9)
1
2
3
24.1
(9-1/2)
22.8
(9)
71.1
(28)
90.8
(35-3/4)
4
19.9
7.6
(7-7/8)
(3)
83.4
(32-7/8)
Figure 9. Cable cutout and door clearance for Models E10, F10, E20, and F20
The reference keys in Figure 9 identify the following locations:
«1¬ is the front of the enclosure.
«2¬ is the rear of the enclosure.
«3¬ is the cutout for the power cables. Expansion enclosure only.
«4¬ is the cutout for the Enterprise Systems Connection (ESCON), fibre channel,
small computer system interface (SCSI) cables, and power cables. (Models E10,
F10, E20, F20)
Dimensions shown are centimeters (inches).
S008303R
Chapter 3. Installation planning53
The dimensions and cutouts for the expansion enclosure are the same as for
Models E10, F10, E20, and F20. However, the expansion enclosure does not
require «4¬, the cutout for the ESCON, fibre channel, or SCSI cables.
2
76.6
2.5
(1)
(30-1/8)
30
(11-7/8)
15
(6)
102
(40-1/8)
15
(6)
3
107
(42-1/8)
128.6
(50-5/8)
3
76.6
(30-1/8)
1
75
(29-1/2)
Figure 10. Cable cutout and door clearance for Model 100
The reference keys in Figure 10 identify the following locations:
«1¬ is the front of the enclosure.
«2¬ is the rear of the enclosure.
«3¬ is the cutout for power cables
Dimensions shown are centimeters (inches).
54ESS Introduction and Planning
84
(33)
S009111
Service clearance and floor-loading requirements for the ESS
Table 13 shows the clearances that the ESS requires for service and for the
floor-loading requirements.
Table 13. Clearance and floor-loading requirements
Configuration and
Weight
2105 Model E10
and F10, Weight
998 kg (2200 lbs)
Note 2
2105 Model E20
and F20, Weight
1202 kg (2650 lbs)
Note 2
2105 Model E20
and F20 with
Expansion
Enclosure, Weight
2540 kg (5600 lbs)
Note 2, 4, 5
Service ClearanceFloor
Loading,
lbs/ft²
(See
FrontRearSidesFrontRear
864mm (34
in.)
864 mm
(34 in.)
864 mm
(34 in.)
1145 mm
(45 in.)
1145 mm
(45 in.)
1145 mm
(45 in.)
Notes 1
and 3.)
610
kg/m²
(125
lb/ft²)
488
kg/m²
(100
lb/ft²)
439
kg/m² (90
lb/ft²)
361
kg/m² (70
lb/ft²)
610
kg/m²
(125
lb/ft²)
488
kg/m²
(100
lb/ft²)
439
kg/m² (90
lb/ft²)
342
kg/m²(70
lb/ft²)
610
kg/m²
(125
lb/ft²)
488
kg/m²
(100
lb/ft²)
439
kg/m² (90
lb/ft²)
342
kg/m² (70
lb/ft²)
Dedicated Weight Distribution
Areas mm (in.) (See Notes 3, 4,
6, and 7.)
0mm(0
in.)
76 mm (3
in.)
184 mm
(7.25 in.)
559 mm
(22 in.)
15 mm
(.6 in.)
229 mm
(9 in.)
368 mm
(14.5 in.)
762 mm
(30 in.)
0mm(0
in.)
413 mm
(16.25
in.)
711 mm
(28 in.)
762 mm
(30 in.)
356 mm
(14 in.)
432 mm
(17 in.)
432 mm
(17 in.)
432 mm
(17 in.)
432 mm
(17 in.)
432 mm
(17 in.)
432 mm
(17 in.)
483 mm
(19 in.)
381 mm
(15 in.)
432 mm
(17 in.)
432 mm
(17 in.)
762 mm
(30 in.)
356 mm
(14 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
610 mm
(24 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
762 mm
(30 in.)
Chapter 3. Installation planning55
Table 13. Clearance and floor-loading requirements (continued)
Configuration and
Weight
2105 Model 100,
Weight 771 kg
(1700 lbs) Note 2,
6, 8.
2105 Model 100s,
Weight 1542 kg
(3400 lbs) Note 2,
7, 8
Service ClearanceFloor
Loading,
lbs/ft²
(See
FrontRearSidesFrontRear
1145 mm
(45 in.)
1145 mm
(45 in.)
813 mm
(32in.)
813 mm
(32in.)
Notes 1
and 3.)
610
kg/m²
(125
lb/ft²)
488
kg/m²
(100
lb/ft²)
439
kg/m² (90
lb/ft²)
342
kg/m²(70
lb/ft²)
610
kg/m²
(125
lb/ft²)
488
kg/m²
(100
lb/ft²)
439
kg/m² (90
lb/ft²)
342
kg/m² (70
lb/ft²)
Dedicated Weight Distribution
Areas mm (in.) (See Notes 3, 4,
0mm(0
in.)
102 mm
(4 in.)
178 mm
(7 in.)
425 mm
(16.75
in.)
0mm(0
in.)
178 mm
(7 in.)
330 mm
(13 in.)
762 mm
(30 in.)
6, and 7.)
318 mm
(12.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
419 mm
(16.25
in.)
572 mm
(22.5 in.)
572 mm
(22.5 in.)
635 mm
(25 in.)
559 mm
(22 in.)
406 mm
(16 in.)
406 mm
(16 in.)
406 mm
(16 in.)
419 mm
(16.25
in.)
406 mm
(16 in.)
406 mm
(16 in.)
406 mm
(16 in.)
56ESS Introduction and Planning
Table 13. Clearance and floor-loading requirements (continued)
Configuration and
Weight
Notes:
1. IBM recommends that you install the ESS on a floor with a minimum of 342 kg/m² (70
lbs/ft²) strength.
2. Floor loads are calculated for maximum weight of the storage server.
3. Side clearances are for both sides of an ESS expansion enclosure. Clearances on
both sides are dedicated to the ESS. Adjacent expansion enclosures must have their
own floor-loading clearance.
|
|
|
|
|
|
|
|
|
|
|
|
4. If you install a Model E20 or F20 with an expansion enclosure, the floor strength must
be 440 kg/m² (90 lbs/ft²). At 342 kg/m² (70 lbs/ft²), the side clearance exceeds the
762-mm (30-in.) maximum allowed. Consult a structural engineer if you are unsure
about the correct placement and clearances of these machines for floor-loading
distribution.
5. Multiple expansion enclosures are bolted together with 280-mm (11-in.) spacers. Move
the side cover from the Model E20 or F20 to the side of the expansion enclosure.
6. The Model 100 is recommended to be placed to the right side of the E20 and F20.
Distance between the frames is dictated by the floor loading of each machine.
7. When having two Model 100s, the Model 100 frames are bolted together with a 40 mm
(1.6 in) spacer between them, and physically positioned to the right of the Model E20
or F20.
8. There can be a maximum of six drawers in a Model 100.
9. A clearance of 102 mm (4 in.) on each side of the ESS is required to open the covers
to 90 degrees.
10. If you place an ESS Model E10, E20, F10, or F20 next to each other, a clearance of
102 mm (4 in.) is required between the sides of the models. This clearance allows you
to open the doors.
Service ClearanceFloor
Loading,
lbs/ft²
(See
FrontRearSidesFrontRear
Notes 1
and 3.)
Dedicated Weight Distribution
Areas mm (in.) (See Notes 3, 4,
6, and 7.)
When you attach the IBM 2105 Model 100 expansion enclosure to the ESS, follow
the floor loading requirements in Table 13 on page 55. This table also gives the side
clearances that are required for both sides of the installation. For more information
on the IBM 2105 Model 100, please see the
Model B09
, which can be accessed at the following web site:
IBM installs the IBM Enterprise Storage Server Network (ESSNet) when they install
your ESS.
IBM provides the power cables for the ESSNet. You provide:
v A location for the ESSNet hub that is within 15 m (50 ft) of the ESS.
v A location for the ESSNet console (workstation and monitor) that is within 15 m
(50 ft) of the hub.
v Three outlets (for the workstation, monitor, and hub).
Introduction and Planning Guide 2105
Chapter 3. Installation planning57
If you are attaching your network to the ESSNet hub, you also need to provide an
Ethernet cable and TCP/IP information to IBM. IBM will connect your LAN cable to
the ESSNet hub after the ESS and the ESSNet are installed and in operation.
You are responsible for firewall protection for the ESSNet.
You also need to provide a table or a stand for the ESSNet workstation at your site.
The workstation is a personal computer (PC) and a monitor. The weight and
dimensions for the PC are:
PC weight11 kg (25 lbs)
PC height128 mm (5 in.)
PC width440 mm (17.7 in.)
PC depth440 mm (17.7 in.)
The approximate weight and dimensions for the monitor are:
Monitor weight18 kg (38 lbs)
Monitor height432 mm (17 in.)
Monitor width406 mm (16 in.)
Monitor depth432 mm (17 in.)
The monitor has a 75 mm (15 in.) screen. The combined weight of the monitor and
the PC does not exceed 30 kg (65 lbs).
Power requirements
This section provides power and cooling requirements and environmental
information for the ESS.
Input voltages and frequencies
See Table 14 for the input voltages and frequencies that the ESS supports. The
values apply to both primary power cables on any expansion enclosure or any
model. Inputs are either single phase or balanced three phase depending on the
connector type as described in “Power cable connectors” on page 61. Also see
“Power features” on page 25 for information about power features.
or 480 RMS V ac
Minimum input voltage180 RMS V ac
Maximum input voltage512 RMS V ac
Steady-state input frequencies50 ± 0.5 or 60 ± 0.5 Hz
PLD input frequencies (<10 seconds)50 ± 2.0 or 60 ± 2.0 Hz
Power consumption and environmental information
Table 15 on page 59 gives power consumption and environmental information on
the ESS.
58ESS Introduction and Planning
Table 15. Power consumption and environmental information for the ESS
MeasurementUnitsModels E10 or
F10
Electric powerkVA3.5512
Thermal loadBTU/hour11 00016 00040 000
Capacity of
exhaust (See
Note.)
Single-phase
and three-phase
leakage current
Startup currentAmps≤ 100≤ 100≤ 100
Startup current
duration
Idle and
operating-sound
power (LwAd)
Idle and
operating-sound
pressure (LpA)
Note: The ESS takes air in through the front cover and exhausts air from the rear and top.
Cubic meters per
min (cubic ft per
min)
Milliamps171717
microseconds< 200< 200< 200
bels7.57.5Not applicable
decibels5959Not applicable
44.2 (1500)51.8 (1800)102.7 (3600)
Models E20 or
F20
Models E20 or
F20 with
Expansion
Enclosure
Cooling requirements
For cooling, install two fully perforated tiles in front of each ESS. Also install one
fully perforated tile in front of an expansion enclosure and one fully perforated tile at
the back of an expansion enclosure.
Operating environment
The following sections list the environmental operating points and ranges that IBM
recommends for the ESS.
Power on environment
Table 16 gives the operating extremes for an ESS with the power on.
Table 17 gives the operating points that IBM recommends for an ESS with the
power on.
Table 17. Recommended operating points with the power on
Temperature (See Attention)22°C (72°F)
Relative humidity (See Attention)45%
Chapter 3. Installation planning59
Table 17. Recommended operating points with the power on (continued)
Attention:
If you deviate substantially in either direction from these recommended operating points for extended, consecutive
hours, you expose the ESS to malfunction from extreme causes.
Table 18 gives the operating ranges that IBM recommends for an ESS with the
power on.
Table 18. Recommended operating ranges with the power on
Power consumption in energy savings mode is not applicable.
Power cable and power connector requirements
This section describes ESS power cable requirements and power connector
requirements. See “Power cables” on page 26 for the power-cable feature codes.
60ESS Introduction and Planning
Power cable connectors
Table 21 on page 62 shows the power cables, in-line connectors, and receptacles.
Select the feature code that is appropriate for your site. Phase rotation on
three-phase power-cable connectors is counterclockwise as you look at the plug.
Phase rotation is clockwise as you look at the face of the power receptacle.
Chapter 3. Installation planning61
Table 21. ESS power cable connectors
Power cable
Feature Code
9801, 99861-phase, 50/60 Hz 50 A (See
98021-phase, 50 Hz (See Notes 4
98031-phase, 50/60 Hz, 60 A (See
9851, 99873-phase, 50/60 Hz, 50 A (See
9988, 98543-phase, 50/60 Hz, 60 A (See
98523-phase, 50 Hz, (See Notes 5
98533-phase, 50/60 Hz, 60 A (See
Notes:
1. All power cables are rated at 600 V ac except power cables for Japan, which are 250
V ac. Single-phase power cables have 2 poles and 3 wires. Three-phase power cables
have 3 poles and 4 wires.
2. Connector and receptacle types indicated are Russell Stoll except types for Japan,
which can use any manufacturer.
3. All power cables are 4.7 m (14 ft) long except Chicago, which is2m(6ft)long.
4. Not available on the Model E20 or F20 or the expansion enclosure.
5. Not available on the Model E10 or F10.
6. Install IEC309 receptacle in a metal-backed box with the green wire ground-connected
to the grounding lug within the box. Ensure continuity between the box and the metallic
shielding of the liquid-tight conduit.
7. The 7428-78 in-line connector must have the appropriate JPA adapter included in the
assembly to ensure continuity between the connector housing and the metallic
shielding of the liquid-tight conduit.
8. IBM recommends that you attach these in-line connectors to a liquid-tight,
metallic-shielded conduit, using adapter C75 for 1.89 cm (3/4-in.) conduit, or using C10
for 2.54 cm (1-in.) conduit.
9. These receptacles require back box 3711A.
10. For low-voltage, single phase installations (200 V to 240 V), IBM recommends a
minimum rated circuit breaker of 40 amperes, and not to exceed the wire rating of the
facility.
11. For low-voltage, three phase installation (200 V to 240 V), IBM recommends a
minimum rated circuit breaker of 25 amperes, and not to exceed the wire rating of the
facility.
12. For high-voltage, single phase installations (380 V to 415 V), IBM recommends a
minimum rated circuit breaker of 20 amperes, and not to exceed the wire rating of the
facility.
13. For high-voltage, three phase installations (380 V to 415 V), IBM recommends a
minimum rated circuit breaker of 15 amperes, and not to exceed the wire rating of the
facility.
Power cable Description (See
Notes 1 and 3.)
Notes 4 and 10.)
and 10.)
Note 4.)
Notes 5 and 10.)
Notes 5 and 10.)
and 11.)
Note 5.)
In-line Connector
(See Note 2.)
9C53U0 (See Note
8.)
No connectorHard wire (See
Not used360R6W (See
9C54U0 (See Note
8.)
7428-78 (See Note
7.)
No connectorHard wire (See
Not used460R9W (See
Receptacle (See
Note 2.)
9R53U0W (See
Note 9, 10, and
12.)
note 10 and 12.)
Note 6, 10, and
12.)
9R54U0W (See
Note 9, 11, and
13.)
7324-78 (See note
11 and 13.)
note 11 and 13.)
Note 6, 11, and
13.)
62ESS Introduction and Planning
Outlet power for the extension cord
Each ESS model E10, F10, E20, or F20 includes a 4.7-m (14-ft), multiple-outlet
extension cord. Service personnel use the outlets within the ESS to power service
tools.
You must supply an appropriate receptacle for the extension cord at your site for
each ESS model. The ESS supports various power cable plugs to accommodate
your site. The outlet circuit should support at least 1200 W.
Remote service connection
You need to connect each ESS to a modem and a remote support switch. With the
remote support switch, you can attach up to seven ESSs. The modem connection
and the switch connection allow service personnel to perform service remotely. See
“Remote support features” on page 26 for information on remote support feature
codes.
Locate and provide power to the remote support switch and modem externally from
the ESS. The cable from the ESS to the remote support switch is 16 m (50 ft) long.
The cable from the remote support switch to the modem is 3.33 m (10 ft) long. You
supply the cable to connect the modem to a telephone jack.
Select the appropriate power cables for the modem and for the remote support
switch. Make your selection based on the feature code for the remote
support-switch power cable.
The modems that IBM offers are for worldwide use, and they meet all required
standards.
Connect the remote support switch to the serial port of each cluster in the ESS.
Remote service outlet power
You supply an appropriate receptacle for each modem and each remote support
switch. The ESS supports various power cable plugs to accommodate different
geographies. The country code determines which plug IBM supplies with the
product.
Remote power control
The ESS supports up to eight S/360 remote power-control interfaces to allow
remote power control.
Remote service telephone lines
You need one or more analog telephone lines to support remote service. Determine
the number of telephone lines you need by the number of ESSs you are installing.
You also provide the telephone cable that connects the modem to the
telephone-line jack. An expander supports one telephone line.
Chapter 3. Installation planning63
64ESS Introduction and Planning
Chapter 4. Planning for communication
This chapter provides guidelines for completing the Communication Resources work
sheet (see “Guidelines for completing the Communication Resources work sheet”)
and the ESS Copy Services work sheet (see “Communications for ESS Web Copy
Services” on page 73).
Communication overview
During installation IBM establishes communication links between the ESS and your
storage management personnel, and between the ESS and service personnel.
IBM installation personnel use the information from the work sheet to establish
communications between your host system and the ESS.
After IBM has installed the ESS, you can change the communication settings from
the Web interface. See the
Guide
Specialist to change the settings.
The Communication Resources work sheet allows you to define how the various
communications functions within the ESS should be configured. It also lets you
authorize or deny access to your ESS by service personnel. The following
communications functions are available:
v Enable outgoing modem calls
v Enable remote login
v Optional remote access password
for guidelines on using the IBM StorWatch Enterprise Storage Server
You control this remote service. IBM recommends that you enable this service by
checking Yes. When you enable outgoing-modem calls, the ESS places the
call-back password in the header of each call home record. The call-back
password allows your service provider to login to the ESS in response to the
service call.
You control this remote access. IBM recommends that you enable this service by
checking Yes. Service personnel can login to the ESS with the call-back
password.
This password adds further security to the support login ID. This password
should be set in agreement between you and IBM service personnel.
IBM Enterprise Storage Server Web Interface User’s
With access to the ESS, service personnel can perform service tasks, such as
viewing error logs and problem logs and initiating trace or dump retrievals.
Guidelines for completing the Communication Resources work sheet
Use the following guidelines when completing the work sheet that is shown in
“Appendix A. Communication Resources work sheet” on page 85:
1. Time zone configuration and date configuration
a. Time zone
Fill in the time zone that applies to this machine. Select one of the following
items. The number in parentheses shows the time adjustment from
Coordinated Universal (CUT) time, in hours. Enter this number (with the plus
or minus) in the field:
v Coordinated Universal
v United Kingdom (0)
v Azores; Cape Verde (-1)
v Falkland Islands (-2)
v Greenland; East Brazil (-3)
v Central Brazil (-4)
v Eastern U.S.; Columbia (-5)
v Central U.S.; Honduras (-6)
v Mountain U.S. (-7)
v Pacific U.S.; Yukon (-8)
v Alaska (-9)
v Hawaii; Aleutians (-10)
v Bering Straits (-11)
v New Zealand (+12)
v Solomon Islands (+11)
v Eastern Australia (+10)
v Japan (+9)
v Korea (+9)
v Western Australia (+8)
v Taiwan (+8)
v Thailand (+7)
v Tashkent; Central Asia (+6)
v Pakistan (+5)
v Gorki; Central Asia; Oman (+4)
v Turkey (+3)
v Saudi Arabia (+3)
v Finland (+2)
v South Africa (+2)
v Norway; France (+1)
b. Daylight savings
Check Yes if this location goes on daylight savings time; check No if it does
not.
2. TCP/IP configuration
The following guidelines are for basic TCP/IP configuration. For advanced
TCP/IP configuration, see the
and Networks, Version 4
AIX System Management Guide: Communications
, SC23-2526. Work with the IBM service personnel at
your ESS site to set up advanced TCP/IP configuration on the ESS.
If you want to attach your LAN to the ESSNet hub, you need to provide the
following TCP/IP information to IBM. IBM will connect your LAN cable to the
ESSNet hub and enter the TCP/IP information.
Note: IBM will attach your LAN
a. Network interface
Select one of the following network interfaces:
The difference between these two choices is the header format. On the
same local network, all stations must use the same header format.
b. Cluster 1 hostname
Enter the hostname that you are assigning to cluster 1 for access over the
network. For example, Storage00.
66ESS Introduction and Planning
after
the ESS and ESSNet are installed and in
operation.
en0 Standard Ethernet
et0 Institute of Electrical and Electronics Engineers (IEEE) 802.3
Ethernet
Note: The hostname you define here is also the Web site address for
access to ESS Specialist in cluster 1 or cluster 2.
The ESS has two independent clusters (cluster 1 and cluster 2). The
clusters provide management functions for the ESS. The clusters also
manage the interfaces to host devices and to external local area networks
(LANs). Each cluster manages approximately half of the attached storage.
c. Cluster 1 Internet address
Enter the dotted decimal address you are assigning to cluster 1 of this
machine. For example, 9.113.152.148.
d. Cluster 2 hostname
Enter the hostname that you are assigning to cluster 2 for access over the
network. For example, Storage01.
e. Cluster 2 Internet address
Enter the dotted decimal address you are assigning to cluster 2 of this
machine. For example, 9.113.152.149 .
f. ESSNet workstation hostname
Enter the hostname that you are assigning to ESSNet for access over the
network. For example, ESSNet1.
g. ESSNet workstation Internet address
Enter the Internet address that you are assigning to ESSNet for access over
the network. For example, 555.555.555.0.
h. Network mask
Enter the dotted decimal network mask that you are applying to TCP/IP on
this machine. For example, 255.255.255.0.
i. Nameserver Internet address
Enter the dotted decimal address of the nameserver that this machine is to
access. For example, 9.113.42.250.
j. Nameserver domain name
Enter the domain name of the nameserver. For example, tucson.ibm.com.
k. Default gateway address
Enter a dotted decimal or symbolic name as the address of the default
gateway for this machine. For example, 9.113.155.254 or sanjosegate.
l. Ethernet adapter mode
Select half-duplex mode for the Ethernet adapter. The mode must match the
mode of the external switch or router to which you are connecting the
adapter.
3. Customer information
Enter information that you feel might be useful to your service provider, such as:
a. Business name or company name
IBM support uses this information; this information should be consistent for
all machines within an account.
b. Location
Enter the location of the ESS (city, street address, and building).
c. Telephone number
This is the telephone number where service personnel can contact you.
d. Name of contacts
Chapter 4. Planning for communication67
These are the names of individuals at your site that service personnel can
contact about ESS service matters.
e. Electronic mail (e-mail) address
Note: IBM strongly recommends that you list at least one e-mail address.
This address will receive information when product engineers or
service support personnel connect to your machine.
4. Enable ESS Specialist
Check either Yes or No. IBM service will enable or disable ESS Specialist
during installation of your ESS. ESS Specialist is the Web interface that you
and IBM use to configure the ESS. When you enable ESS Specialist, you can
use it to change the configuration.
5. Call home and remote services
|
|
|
Complete all of this information except the Remote telephone numbers field
and the Support catcher telephone number field. IBM service personnel or
your service provider completes these fields.
a. Enable the incoming calls
The ESS can accept the incoming calls. Check Yes to enable these calls.
Check No to disallow or deny these calls.
b. Enable outgoing modem calls
The ESS can place a call to IBM service or to your service provider when it
requires service. Check Yes to enable these calls. Check No to disallow or
deny these calls.
c. Call home heartbeat interval
Enter0-15days to set the length of time between heartbeat call homes
from the ESS clusters to IBM. IBM uses this record to monitor the health of
the call home process for each cluster. If you enter 0, the ESS does not
send a call home heartbeat. The default interval is 5 days.
d. Enable e-mail across the LAN
The ESS can send e-mail to your LAN when it requires service. It sends
e-mail through the ESSNet if you have attached your LAN to the ESSNet
external hub. Check Yes to enable e-mail. Check No to disable e-mail.
e. Enable pager messages
The ESS can send problem information to your pager if you have attached
your LAN to the ESSNet external hub. Check Yes to enable pager
messages. Check No to disable pager messages. See step 9 on page 71
for details about pagers.
f. Remote telephone numbers
IBM service personnel or your service provider completes this information.
The telephone numbers should include area codes and country codes,
when appropriate.
|
|
|
|
|
g. Support catcher telephone number
IBM service personnel or your service provider completes this information.
The telephone numbers should include area codes and country codes,
when appropriate. The SSR personnel who do not know this number
should call the next level of support for this information.
Service personnel use this telephone number to send heartbeat call home
records that are non-problem related, directly to the support catcher server
rather than to the catcher server for remote technical-assistance
68ESS Introduction and Planning
information network (RETAIN). These records might include such
information as a trace, dump package, and the activation of Step Ahead
Storage usage.
h. Call-back (local modem) telephone number
Enter the external telephone number of the line to the modem that is
connected to this machine. Include all area codes and all country codes,
when appropriate.
Note: Multiple ESSs can share a telephone modem if you install a modem
switch.
i. Customer-contact telephone numbers
Enter the primary and off-shift telephone numbers that service personnel
can use to contact someone at your ESS site to discuss service matters.
Include all area codes. An off-shift number could be the backup number.
These telephone numbers should be for the individuals you name for
contacts in step 3 on page 67.
j. Call-back password
Enter 1 to 8 characters for the password. This is a mandatory entry. The
ESS sends this public password with each call-home record. IBM suggests
that you set support as the password.
k. Outside line prefix
This is the number you dial to access an outside line. Enter up to three
numbers in this field.
l. Enable remote IBM PE login across a LAN
Check Yes to enable IBM product engineering (PE) personnel to login to
the ESS. The PE personnel have service experience and development
experience for this product. Check No to disallow this access.
6. Modem configuration
IBM service personnel or your service provider completes this information. A list
of the fields follows for your information.
a. Name of modem set
Note: DeskPorte Fast should be entered if a MultiTech MultiModem was
shipped
b. Dialer telephone system
Select tone or pulse.
c. Modem data rate
Select one of the following:
Fastest possible speed
14400168001920021600
240002640028800
Note: IBM recommends that you select Fastest possible speed.
d. Cancel the call if it does not connect within 30 - 180 seconds. IBM
recommends 45 seconds.
e. Number of consecutive retries for connection
f. Name of the expander set
g. Expander port for the modem
h. Expander port for cluster 1
Chapter 4. Planning for communication69
i. Expander port for cluster 2
7. E-mail configurationAttention: If you plan to connect your network to the ESSNet, IBM
recommends that you defer having IBM configure e-mail during initial
installation and configuration. You can configure e-mail by using ESS Specialist
after you connect your network to the ESSNet.
a. Maximum error notification count per problem
The ESS sends error notifications (0 to 9) to e-mail addresses and call
home. Enter the total number of notifications you want sent to each
recipient for each problem. A number greater than 1 increases
opportunities for delivery.
Note: If you enter a value of 0, the ESS does not send an error
notification.
b. Add e-mail destinations
The ESS sends error notifications and information to the destinations you
enter here if you have attached your LAN to the ESSNet external hub.
Note: IBM strongly recommends that you list at least one e-mail address.
This address will receive information when product engineers or
service support personnel connect to your machine.
v Enter the full e-mail address for each destination, for example,
maria@host.com.
v For each recipient, check one box: Errors, information, all,ornone.
This specifies which notification the recipient receives.
c. Enable smart relay host
Note: You cannot enable smart relay host if you have enabled local e-mail
as the two configurations are mutually exclusive.
Select Yes to enable a smart relay host when you have met either of the
following conditions:
v Your e-mail is sent from a UNIX-based system on which you have
specified a mail relay or mail gateway
v You have installed a message transfer agent (MTA) on your mail server
If you selected Yes (one of the above conditions applies), enter a host
name or network address.
If the above conditions do not apply, select No.
Note: If the address you entered in step 7b does not receive e-mail,
configuring the smart relay host may correct the problem.
d. Enable local e-mail
Note: You cannot enable local e-mail if you have enabled smart relay host
as the two configurations are mutually exclusive.
Select Yes when:
v You have connected your ESS to a host-system network that does not
have a domain name server (DNS)
8. SNMP configuration
70ESS Introduction and Planning
|
|
The ESS generates Simple Network Management Protocol (SNMP) traps and
supports a read-only management information base (MIB) to allow monitoring by
your network.
Note: SNMP is required for PPRC status reporting for ESS Copy Services for
Open Systems.
Attention: If you plan to connect your network to the ESSNet, IBM
recommends that you defer having IBM configure SNMP during initial
installation and configuration. You can configure SNMP by using ESS Specialist
after you connect your network to the ESSNet.
a. Allow MIB access
The ESS provides access to a management information base (MIB). To
allow read access to this information, check Read Only. To disallow or deny
read access to this information, check None.
b. Allow generic traps
The ESS can generate generic SNMP traps. To allow the ESS to send these
traps, check Yes; to not allow it to send these traps, check No.
c. Allow product-specific traps
The ESS can generate product-specific SNMP traps. To allow it to send
these traps, check Yes. To not allow it to send these traps, check No.
d. Maximum trap notifications per problem
Enter the total number of trap notifications you want sent for each trap
condition. To ensure that traps are not lost, you may want to send each trap
notification more than once.
e. SNMP community name
Enter the SNMP community name (up to 31 characters) to use for
authenticating requests. If you do not enter a name, this entry defaults to
public access.
f. SNMP SysContact
This is an optional entry. If you like, enter the name of the person
responsible for your machine who your service provider should contact.
g. SNMP SysLocation
This is an optional entry. If you like, enter the location of the machine.
h. Add SNMP trap destinations
Enter host names or dotted decimal addresses of the destinations that are
to receive SNMP traps. For example: host.com, or 9.113.152.254.
9. Customer pager information
This information is optional. The ESS can send problem record information to
your pager through the call-home modem. Enter the following information:
a. Pager user name
Enter your pager user name in alphanumeric characters. This must be a
unique name.
b. Modem telephone number
Enter the modem telephone number of the pager company. The pager must
use TAP/IPO protocol. If the pager company recommends a slow speed or
non-error correcting protocol, add an uppercase “z” (Z) to the end of the
telephone number.
c. Pager PIN or ID number
Chapter 4. Planning for communication71
This is the pager PIN number or ID number required by the pager company.
It is usually not null.
d. Carrier password
This is a security password. Check with your pager company; this may be
null.
e. Pager type
Select alphanumeric or numeric.
The numeric pager test message is: 01234-56789
The normal pager message is: 111-aaaaaa-222-bbbbbbb-333-c-444-ddd,
where:
aaaaaa is the numeric characters from the product-serial number
bbbbbbb is the customer voice-telephone number
c is the cluster number (1 or 2)
ddd is the Problem ID
Note: The information the ESS can send to a numeric pager is limited.
f. Pager state
Check Yes to enable, or No to disable.
g. Number of repeats
This is the number of times the ESS sends problem record information (0 -
10). The ESS sends information once automatically.
10. Service information messages (SIMs) for S/390
The ESS sends SIMs to System/390 host consoles for the following three
types of SIMs:
v Direct access storage device (DASD) SIM
This SIM tracks disk drive module (DDM) failures and problems.
v Media SIM
This SIM tracks data check problems on the media.
v Storage facility SIM
This SIM tracks control unit, power control, and other hardware problems.
You select the number of times that the ESS sends a SIM to your console. The
ESScansendaSIM1-9times, or not at all (0). You also select the severity
level of the SIMs. The ESS does not send any SIMs that are below the
severity level that you select. Severity levels are:
1 acuteAn irrecoverable error with possible loss of data. This severity
2 seriousAn irrecoverable error or a data check with loss of access to
3 moderateA system path or paths are not operational, and performance
4 serviceA recoverable error, equipment checks, or data checks. You
Enter the severity levels for the SIMs and enter the number of times the ESS
should send a SIM:
a. Enter the SIM-severity reporting level for DASD SIMs.
72ESS Introduction and Planning
level only applies to DASD SIMs.
data.
may be degraded. This severity level does not apply to media
SIMs.
can defer repair.
1to4
b. Enter the number of times the ESS is to send a DASD SIM.
0to9
c. Enter the SIM-severity reporting level for media (data check) SIMs.
2or4
d. Enter the number of times the ESS is to send a media SIM.
0to9
e. Enter the SIM-severity reporting level for a storage server SIM.
2, 3, or 4
f. Enter the number of times the ESS is to send the storage-server SIM.
0to9
11. Fibre-channel LUN-access control
A switch on the ESS determines whether hosts have access to all LUNs over
fibre channel, or whether access is restricted.
a. Switch setting:
Check Restricted if you want to limit access to LUNs to hosts that you
define in the ESS Specialist interface. Restricted is the default setting.
Check Permit All if all hosts are to have access to all LUNs.
Communications for ESS Web Copy Services
This section gives guidelines for filling out the Copy Services work sheet.
The ESS clusters that are part of a Copy Services Server Group use the TCP/IP
network to communicate. Each ESS cluster needs to have an IP address assigned
to it. You enter this information on the Communication Resources (Copy Services)
work sheet.
IBM recommends that you use a Domain Name Server (DNS) for name resolution.
DNS provides the following advantages:
v It resolves the names of the participating ESS clusters
v It allows the Copy Services code to communicate with remote sites
v A domain name provides a unique, stable address for communication; the dotted
decimal address can be changed
Figure 11 on page 74 shows ESS Copy Services server group in a DNS
configuration.
Chapter 4. Planning for communication73
Site 1 Primary Site
ESS 1
P
Backup
C
F
/
I
S
C
S
Server Group 1
ESCON
Site 2 Recovery Site
ESS 4
Primary
S
C
S
I
/
F
C
P
H
O
S
T
P
CLI
C
F
ESSnet
/
I
S
C
ESS 2
S
Backup
Server Group 2
ESCON
ESS 5
Primary
ESSnet
HUBHUB
CLI
P
C
S
I
/
F
C
CS000005
H
O
S
T
S
Figure 11. ESS Web Copy Services configuration with DNS
If you decide not to use a DNS in your configuration, you need to provide your IBM
SSR with information in addition to the information in the Communication Resources
(Copy Services) work sheet. The SSR uses the ESS Service interface to update the
host table with this information:
v The TCP/IP address and host name for each ESS cluster in the copy services
server group.
v The TCP/IP address and hostname for each host using the CLI.
v The TCP/IP address and hostname of the ESSNet Workstation.
Use the following instructions when completing the Communication Resources (ESS
Web Copy Services) work sheet in “Appendix B. Communication Resources (ESS
Web Copy Services) work sheet” on page 89. Refer to the “Guidelines for enabling
and using ESS Web Copy Services” on page 41 for additional information:
Attention:This work sheet must be copied and provided for each ESS Web copy
services server group defined
1. Server Group : Identify the server group (_) that is being defined by this work
sheet.
2. Primary Copy Services Server IP Address. For example, 9.113.152.148.
3. Backup Copy Services Server IP Address. For example, 9.113.152.147.
4. Is a Domain Name Server (DNS) configured on ESS.
Note: If you do not have a DNS specified and you are using the CLI, collect the
5. Enable ESS Web Copy Services commands for System/390 volumes
74ESS Introduction and Planning
hostnames and IP addresses for all of the Open System servers that are
using the CLI.
Select Enable or Disable. (Disable is the default) ESS Copy Services supports
FlashCopy and PPRC for System/390 volumes in addition to volumes on open
system hosts.
Note: It is not necessary to enable ESS Web Copy Services if you are going to
use TSO and IDCAMS
6. ESS Machine Serial Number for Primary Server Site.
Enter the serial number of this machine. For example, 013-FCA15.
You can configure two ESS within a Copy Services Server group. Each ESS
Copy Services server group manages four clusters and a maximum of 2048
volumes. Provide this information to your IBM SSR for each Copy Services
server group that you want to configure.
Note: A Copy Services server group is a collection of ESS clusters that
participate in Copy Services functions that include the volumes within the
clusters.
a. Cluster 1 Hostname
Enter the hostname that you are assigning to cluster 1 for access over the
network. For example, Storage03.company.com.
Note: The hostname you define here is the Web site address for access to
ESS Copy Services.
b. Cluster 1 IP Address
Enter the dotted decimal address you are assigning to cluster 1 of this
machine. For example, 9.113.152.149.
c. Cluster 2 Hostname
Enter the hostname that you are assigning to cluster 2 for access over the
network. For example, Storage04.company.com.
d. Cluster 2 IP Address
Enter the dotted decimal address you are assigning to cluster 2 of this
machine. For example, 9.113.152.151 .
7. ESS Machine Serial Number for Backup Server Site.
Enter the serial number of this machine. For example, 013-FCA15.
a. Cluster 1 Hostname
Enter the hostname that you are assigning to cluster 1 for access over the
network. For example, Storage03.company.com.
b. Cluster 1 IP Address
c. Cluster 2 Hostname
Enter the hostname that you are assigning to cluster 2 for access over the
network. For example, Storage04.company.com.
d. Cluster 2 IP Address
Use the following instructions when completing the work sheet that is shown in
Table 24 on page 89:
Note: The hostname you define here is the Web site address for access to
ESS Copy Services.
Enter the dotted decimal address you are assigning to cluster 1 of this
machine. For example, 9.113.152.149.
Enter the dotted decimal address you are assigning to cluster 2 of this
machine. For example, 9.113.152.151 .
Chapter 4. Planning for communication75
1. Server Group : Identify the server group (_) that is being defined by this work
sheet.
2. Command Line Interface Host 1 IP Address
Enter the dotted decimal address you are assigning to Command Line Interface
Host 1. For example, 9.113.152.151 .
Command Line Interface Host 1 Hostname
Enter the hostname that you are assigning to Command Line Interface 1 for
access over the network. For example, Storage04.company.com.
3. Command Line Interface Host 2 IP Address
Enter the dotted decimal address you are assigning to Command Line Interface
Host 1. For example, 9.113.152.153 .
Command Line Interface Host 2 Hostname
Enter the hostname that you are assigning to Command Line Interface 2 for
access over the network. For example, Storage01.company.com.
4. Command Line Interface Host 3 IP Address
Enter the dotted decimal address you are assigning to Command Line Interface
Host 1. For example, 9.113.152.154 .
Command Line Interface Host 3 Hostname
Enter the hostname that you are assigning to Command Line Interface 3 for
access over the network. For example, Storage02.company.com.
5. Command Line Interface Host 4 IP Address
Enter the dotted decimal address you are assigning to Command Line Interface
Host 1. For example, 9.113.152.155 .
Command Line Interface Host 4 Hostname
Enter the hostname that you are assigning to Command Line Interface 4 for
access over the network. For example, Storage03.company.com.
6. ESSNet workstation Internet address
Enter the Internet address that you are assigning to ESSNet for access over the
network. For example, 555.555.555.0.ESSNet workstation hostname
Enter the hostname that you are assigning to ESSNet for access over the
network. For example, ESSNet1.
Disaster Recovery Considerations for Copy Services
If a disaster or emergency situation at your primary production site causes you to
lose connections to the Copy Services primary server, you must manually switch
control to your recovery site. ESS Web Copy Services code copies tasks
synchronously between the primary and backup servers, but there are some steps
you should consider in planning for disaster recovery, and in implementing
procedures following a disaster.
Preparing for a disaster
Planning for a disaster requires some additional steps for PPRC. First, decide
where to place your primary and backup ESS Web Copy Services servers. There
are two options:
1. Primary Copy Services server is at your recovery site
Choosing this configuration can gain you some efficiency in terms of recovering
from a disaster. Because the primary server is at the recovery site, you do not
have to perform manual recovery steps to switch to a different Web Copy
76ESS Introduction and Planning
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.