IBM Total Storage ESS Introduction and Planning Guide

IBM TotalStorage Enterprise Storage Server
Introduction and Planning Guide
GC26-7444-06
GC26-7444-06
Note:
Before using this information and the product it supports, read the information in “Safety and environmental notices” on page
xi and “Notices” on page 137.
Seventh Edition (May 2004)

This edition replaces GC26-7444-05.
© Copyright International Business Machines Corporation 1999, 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Safety and environmental notices . . . . . . . . . . . . . . . . . xi

Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . xi
Environmental notices . . . . . . . . . . . . . . . . . . . . . . xi
Product recycling . . . . . . . . . . . . . . . . . . . . . . . xi
Disposing of products . . . . . . . . . . . . . . . . . . . . . . xi
About this guide . . . . . . . . . . . . . . . . . . . . . . . xiii

Who should use this guide . . . . . . . . . . . . . . . . . . . . xiii
Related information . . . . . . . . . . . . . . . . . . . . . . . xiii
ESS library . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Other IBM publications . . . . . . . . . . . . . . . . . . . . . xv
Ordering IBM publications . . . . . . . . . . . . . . . . . . . . xxi
Non-IBM publications . . . . . . . . . . . . . . . . . . . . . xxi
Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
How to send your comments . . . . . . . . . . . . . . . . . . . xxiii
Summary of Changes . . . . . . . . . . . . . . . . . . . . . xxv

Summary of Changes for GC26-7444-06 IBM TotalStorage Enterprise Storage
Server Introduction and Planning Guide . . . . . . . . . . . . . . xxv
New Information . . . . . . . . . . . . . . . . . . . . . . . xxv
New Information . . . . . . . . . . . . . . . . . . . . . . . xxv
New Information . . . . . . . . . . . . . . . . . . . . . . . xxvi
Changed Information . . . . . . . . . . . . . . . . . . . . . xxvi
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 1
Overview of the IBM TotalStorage Enterprise Storage Server . . . . . . . . 1
Host systems that the ESS supports . . . . . . . . . . . . . . . . 4
ESS interfaces . . . . . . . . . . . . . . . . . . . . . . . . 10
Summary of ESS components and functions . . . . . . . . . . . . . 19
ESS on demand features . . . . . . . . . . . . . . . . . . . . . 20
ESS data integrity, availability, and performance features . . . . . . . . . 21
Data-integrity functions and software for host systems . . . . . . . . . 21
RAID implementation . . . . . . . . . . . . . . . . . . . . . 22
DDM sparing . . . . . . . . . . . . . . . . . . . . . . . . 23
DDM predictive failure analysis . . . . . . . . . . . . . . . . . . 24
Redundant storage server with automatic failover . . . . . . . . . . . 24
Nonvolatile storage . . . . . . . . . . . . . . . . . . . . . . 24
Fast dual-write operation . . . . . . . . . . . . . . . . . . . . 24
Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Concurrent maintenance . . . . . . . . . . . . . . . . . . . . 25
Longitudinal redundancy check . . . . . . . . . . . . . . . . . . 25
Arrays across loops . . . . . . . . . . . . . . . . . . . . . . 25
Availability support for open-systems hosts . . . . . . . . . . . . . 25
Availability support for S/390 and zSeries hosts . . . . . . . . . . . . 27
Logical subsystems . . . . . . . . . . . . . . . . . . . . . . . 28
© Copyright IBM Corp. 1999, 2004 iii

Chapter 2. ESS advanced functions . . . . . . . . . . . . . . . . 31
ESS Copy Services advanced functions. . . . . . . . . . . . . . . . 31
Overview of ESS Copy Services . . . . . . . . . . . . . . . . . 31
Planning for ESS Copy Services . . . . . . . . . . . . . . . . . 33
FlashCopy . . . . . . . . . . . . . . . . . . . . . . . . . 37
Peer-to-Peer Remote Copy . . . . . . . . . . . . . . . . . . . 39
Advanced functions for S/390 and zSeries hosts . . . . . . . . . . . . 43
Extended Remote Copy . . . . . . . . . . . . . . . . . . . . 43
Concurrent Copy . . . . . . . . . . . . . . . . . . . . . . . 44
Parallel access volumes . . . . . . . . . . . . . . . . . . . . 44
Chapter 3. Planning the physical configuration . . . . . . . . . . . . 45

United States-government orders . . . . . . . . . . . . . . . . . . 45
Processor options for ESS Model 800 . . . . . . . . . . . . . . . . 45
Shipping options for ESS Model 800 . . . . . . . . . . . . . . . . . 46
Cache capacity . . . . . . . . . . . . . . . . . . . . . . . . . 46
Power features . . . . . . . . . . . . . . . . . . . . . . . . . 46
Power outlets . . . . . . . . . . . . . . . . . . . . . . . . 47
Uninterruptible power supply . . . . . . . . . . . . . . . . . . . 47
Power supply input voltage . . . . . . . . . . . . . . . . . . . 47
Power cables . . . . . . . . . . . . . . . . . . . . . . . . 48
Extension cords . . . . . . . . . . . . . . . . . . . . . . . 50
Remote support features . . . . . . . . . . . . . . . . . . . . . 51
Remote power control . . . . . . . . . . . . . . . . . . . . . 51
Attachment cables for the remote power control feature . . . . . . . . . 52
Remote support hardware for the ESS Master Console . . . . . . . . . 52
ESS Master Console additional attachment cables . . . . . . . . . . . 52
Power cables for remote support . . . . . . . . . . . . . . . . . 53
Disk capacity, enclosures, and configuration features and options . . . . . . 54
Flexible-capacity options . . . . . . . . . . . . . . . . . . . . 54
Disk eight-packs . . . . . . . . . . . . . . . . . . . . . . . 55
Standby CoD disk eight packs . . . . . . . . . . . . . . . . . . 56
Spare upgrades . . . . . . . . . . . . . . . . . . . . . . . 57
Disk eight-pack mounting kits . . . . . . . . . . . . . . . . . . 58
Expansion enclosure . . . . . . . . . . . . . . . . . . . . . . 59
Arrays across loops . . . . . . . . . . . . . . . . . . . . . . 59
| Reserve loops . . . . . . . . . . . . . . . . . . . . . . . . 59
Additional capacity and configuration information . . . . . . . . . . . 61
Host adapters . . . . . . . . . . . . . . . . . . . . . . . . . 66
SCSI host adapter . . . . . . . . . . . . . . . . . . . . . . 66
ESCON host adapters . . . . . . . . . . . . . . . . . . . . . 66
Fibre-channel (SCSI-FCP and FICON) host adapters . . . . . . . . . . 67
Host attachment cables . . . . . . . . . . . . . . . . . . . . . . 69
SCSI host attachment cables. . . . . . . . . . . . . . . . . . . 69
ESCON host attachment cables . . . . . . . . . . . . . . . . . 70
Fibre-channel host attachment cables . . . . . . . . . . . . . . . 71
Operator-panel language feature code . . . . . . . . . . . . . . . . 72
Logical configuration changes . . . . . . . . . . . . . . . . . . . 73
Optional one-year warranty . . . . . . . . . . . . . . . . . . . . 73
Advanced functions . . . . . . . . . . . . . . . . . . . . . . . 73
Advanced function feature codes for ESS Model 800 . . . . . . . . . . 74
| Advanced function feature codes for ESS Model 750 . . . . . . . . . . 75
Advanced function feature codes for ESS Models F20, F10, E20, and E10 77
Chapter 4. Installation planning . . . . . . . . . . . . . . . . . . 79

Equipment requirements . . . . . . . . . . . . . . . . . . . . . 79
iv ESS Introduction and Planning Guide

Equipment that IBM ships with the ESS for you . . . . . . . . . . . . 79
Equipment for authorized service personnel . . . . . . . . . . . . . 80
Equipment that you provide . . . . . . . . . . . . . . . . . . . 80
Engineering changes. . . . . . . . . . . . . . . . . . . . . . 81
Site planning. . . . . . . . . . . . . . . . . . . . . . . . . . 81
Cover removal for narrow doorways . . . . . . . . . . . . . . . . 83
Earthquake preparedness information for Models 750 and 800 . . . . . . 85
Cooling the ESS . . . . . . . . . . . . . . . . . . . . . . . 87
Fire-suppression system information . . . . . . . . . . . . . . . . 87
Service-clearance and floor-load requirements . . . . . . . . . . . . 87
Planning for installation of the ESS Master Console . . . . . . . . . . 89
Power requirements . . . . . . . . . . . . . . . . . . . . . . . 90
Input voltage requirements . . . . . . . . . . . . . . . . . . . 90
Power consumption and environmental information . . . . . . . . . . 90
Operating environment . . . . . . . . . . . . . . . . . . . . . . 91
With the power on . . . . . . . . . . . . . . . . . . . . . . . 91
With the power off . . . . . . . . . . . . . . . . . . . . . . . 92
In storage . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Energy savings . . . . . . . . . . . . . . . . . . . . . . . . . 92
Power connection requirements . . . . . . . . . . . . . . . . . . . 92
Power connectors . . . . . . . . . . . . . . . . . . . . . . . 92
Remote service connection . . . . . . . . . . . . . . . . . . . 94
Outlet power for the extension cord . . . . . . . . . . . . . . . . 94
Chapter 5. Planning ESS communications . . . . . . . . . . . . . . 95

Overview of communications . . . . . . . . . . . . . . . . . . . . 95
Guidelines for completing the Communication Resources work sheet . . . . . 96
Guidelines for completing the Communication Resources work sheet for the
ESS Master Console . . . . . . . . . . . . . . . . . . . . . 106
Converting from an ESSNet console to an ESS Master Console . . . . . . 110
Guidelines for completing the Communication Resources work sheets for ESS
Copy Services . . . . . . . . . . . . . . . . . . . . . . . . 110
Enable ESS Copy Services work sheet . . . . . . . . . . . . . . 112
Enable ESS Copy Services without DNS work sheet . . . . . . . . . 116
Chapter 6. Planning data migration . . . . . . . . . . . . . . . . 117

Migrating data for open-systems hosts . . . . . . . . . . . . . . . . 117
Reformatting existing disk drive modules . . . . . . . . . . . . . . 118
Fixed-byte sector format . . . . . . . . . . . . . . . . . . . . 118
Migrating data for S/390 and zSeries hosts . . . . . . . . . . . . . . 119
Planning data migration for MVS environments . . . . . . . . . . . . 119
Planning data migration for VM environments . . . . . . . . . . . . 119
Obtaining IBM data migration and other services . . . . . . . . . . . . 120
Appendix A. Communication Resources work sheet . . . . . . . . . 121
Appendix B. Communication Resources work sheet for the ESS Master

Console . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Appendix C. Communication Resources work sheets for ESS Copy

Services . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Enable ESS Copy Services work sheet . . . . . . . . . . . . . . . 127
Enable ESS Copy Services without DNS work sheet . . . . . . . . . . 129
| Appendix D. IBM 2105 Model 100 and 7133 Drawer Attachment . . . . . 131
| Model 100 requirements . . . . . . . . . . . . . . . . . . . . . 131
Contents v
| Reserve loops . . . . . . . . . . . . . . . . . . . . . . . . . 131
| 7133 drawer removal and installation . . . . . . . . . . . . . . . . 132
| 7133 Model 020 requirements . . . . . . . . . . . . . . . . . . . 132
| 7133 Model D40 requirements . . . . . . . . . . . . . . . . . . . 133
| Logical configuration planning . . . . . . . . . . . . . . . . . . . 133
Appendix E. Accessibility . . . . . . . . . . . . . . . . . . . . 135

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Navigating by keyboard . . . . . . . . . . . . . . . . . . . . . 135
Accessing the publications . . . . . . . . . . . . . . . . . . . . 135
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 138
Electronic emission notices . . . . . . . . . . . . . . . . . . . . 139
Federal Communications Commission (FCC) statement . . . . . . . . 139
Industry Canada compliance statement . . . . . . . . . . . . . . 139
European community compliance statement . . . . . . . . . . . . . 139
Japanese Voluntary Control Council for Interference (VCCI) class A
statement . . . . . . . . . . . . . . . . . . . . . . . . 141
Korean Ministry of Information and Communication (MIC) statement . . . . 141
Taiwan class A compliance statement . . . . . . . . . . . . . . . 141
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
vi ESS Introduction and Planning Guide

Figures
1. ESS Models E10, E20, F10, and F20 base enclosure; front and rear views . . . . . . . . . . 3
| 2. ESS Model 800 and 750 base enclosure: front and rear views . . . . . . . . . . . . . . 3
3. ESS expansion enclosure: front and rear views . . . . . . . . . . . . . . . . . . . . 4
4. ESS Master Console connections . . . . . . . . . . . . . . . . . . . . . . . . 12
5. Connecting to ESS Copy Services server domains . . . . . . . . . . . . . . . . . . 16
6. Multipath connections between a host server and ESS logical unit numbers (LUNs) . . . . . . 27
7. Cable cutout and door clearance for Models E10, F10, E20, F20, 750, and 800. Dimensions are
in centimeters (inches). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8. Cable cutout and door clearance for the expansion enclosure (Model 100). Dimensions are in
centimeters (inches). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9. Underside of an ESS with the location of the threaded holes . . . . . . . . . . . . . . . 86
10. ESS Copy Services server domain in a DNS configuration . . . . . . . . . . . . . . . 111
© Copyright IBM Corp. 1999, 2004 vii

viii ESS Introduction and Planning Guide
Tables
1. ESS feature comparison between hosts with different interfaces . . . . . . . . . . . . . . 8
2. Summary of ESS components and functions . . . . . . . . . . . . . . . . . . . . 19
3. Cache capacity for the ESS models . . . . . . . . . . . . . . . . . . . . . . . . 46
4. Input voltage feature codes for the U.S., Canada, AP, and LA . . . . . . . . . . . . . . 48
5. Input voltage feature codes for EMEA . . . . . . . . . . . . . . . . . . . . . . . 48
6. Remote power-control attachment cable group number and connector IDs. . . . . . . . . . 52
| 7. Flexible capacity options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
| 8. ESS feature codes, model support, and LIC requirements for disk eight packs . . . . . . . . 56
| 9. ESS feature codes and LIC requirements for Standby CoD disk eight-packs . . . . . . . . . 57
10. ESS feature codes and LIC requirements for spare upgrades . . . . . . . . . . . . . . 58
| 11. ESS feature codes for disk eight-pack mounting kits . . . . . . . . . . . . . . . . . . 58
12. ESS feature codes for expansion enclosures . . . . . . . . . . . . . . . . . . . . 59
13. Arrays across loops feature codes, requirements, and model support . . . . . . . . . . . 59
| 14. Reserve loops feature codes and model support . . . . . . . . . . . . . . . . . . . 60
| 15. Model 750 Disk Eight-Pack Configurations . . . . . . . . . . . . . . . . . . . . . 61
16. Disk eight-pack capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
17. SCSI host adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
| 18. ESCON host adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
19. Fibre channel host adapter characteristics . . . . . . . . . . . . . . . . . . . . . 67
| 20. Fibre channel host adapter model support and LIC requirement . . . . . . . . . . . . . 68
21. Fibre optic cables and distances . . . . . . . . . . . . . . . . . . . . . . . . . 68
22. SCSI host attachment cables . . . . . . . . . . . . . . . . . . . . . . . . . . 69
23. ESCON host attachment cables . . . . . . . . . . . . . . . . . . . . . . . . . 70
24. Fibre channel / FICON host attachment cables . . . . . . . . . . . . . . . . . . . . 71
| 25. Advanced function model support and LIC requirements . . . . . . . . . . . . . . . . 73
26. Feature codes for advanced functions on the Model 800 . . . . . . . . . . . . . . . . 74
27. Corequisite feature codes for Model 800 advanced functions. . . . . . . . . . . . . . . 75
| 28. Feature codes for advanced functions on the Model 750 . . . . . . . . . . . . . . . . 76
| 29. Corequisite feature codes for Model 750 advanced functions. . . . . . . . . . . . . . . 76
30. Feature codes for advanced functions on the Models F20, F10, E20, and E10 . . . . . . . . 77
| 31. ESS dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . 82
| 32. Cable cutout dimensions (maximum size) . . . . . . . . . . . . . . . . . . . . . . 83
| 33. Clearance and floor-loading requirements . . . . . . . . . . . . . . . . . . . . . . 87
34. ESS input voltages and frequencies . . . . . . . . . . . . . . . . . . . . . . . . 90
| 35. Power consumption and environmental information for the ESS . . . . . . . . . . . . . 91
36. Operating extremes with the power on . . . . . . . . . . . . . . . . . . . . . . . 91
37. Recommended operating points with the power on . . . . . . . . . . . . . . . . . . 92
38. Recommended operating ranges with the power on . . . . . . . . . . . . . . . . . . 92
39. Temperatures and humidity with the power off . . . . . . . . . . . . . . . . . . . . 92
40. ESS temperatures and humidity while in storage . . . . . . . . . . . . . . . . . . . 92
41. ESS power cable connectors . . . . . . . . . . . . . . . . . . . . . . . . . . 93
© Copyright IBM Corp. 1999, 2004 ix

x ESS Introduction and Planning Guide
Safety and environmental notices
This chapter contains information about:
v Safety notices that are used in this guide
v Environmental notices for this product
Safety notices
To find the translated text for a danger or caution notice:
1. Look for the identification number at the end of each danger notice or each
caution notice. In the following examples, the numbers 1000 and 1001 are the
identification numbers.
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 IBM TotalStorage Safety Notices,
GC26-7229.
Environmental notices
This section identifies the environmental guidelines that pertain to this product.
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 might contain batteries. Remove and discard these batteries, or recycle
them, according to local regulations.
© Copyright IBM Corp. 1999, 2004 xi

xii ESS Introduction and Planning Guide
About this guide
This publication introduces the IBM® TotalStorage® 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.
Related information
The tables in this section list and describe the following publications:
v The publications that make up the IBM® TotalStorage™ Enterprise Storage
Server™ (ESS) library
v Other IBM publications that relate to the ESS
v Non-IBM publications that relate to the ESS
See “Ordering IBM publications” on page xxi for information about how to order
publications in the IBM TotalStorage ESS publication library. See “How to send your
comments” on page xxiii for information about how to send comments about the
publications.
ESS library
The following customer publications make up the ESS library. Unless otherwise
noted, these publications are available in Adobe portable document format (PDF) on
a compact disc (CD) that comes with the ESS. If you need additional copies of this
CD, the order number is SK2T-8803. These publications are also available as PDF
files by clicking on the Documentation link on the following ESS Web site:
http://www-1.ibm.com/servers/storage/support/disk/2105.html
See “IBM publications center” on page xxi for information about ordering these and
other IBM publications.
Order
Title Description
Number
IBM® TotalStorage® This guide describes the commands that you can use from the ESS Copy SC26-7494
Enterprise Storage Services command-line interface (CLI) for managing your ESS (See Note.)
Server®: Command-Line configuration and Copy Services relationships. The CLI application
Interfaces User’s Guide provides a set of commands that you can use to write customized scripts
for a host system. The scripts initiate predefined tasks in an ESS Copy
Services server application. You can use the CLI commands to indirectly
control peer-to-peer remote copy and FlashCopy® configuration tasks
within an ESS Copy Services server group.
© Copyright IBM Corp. 1999, 2004 xiii

Order
Title Description
Number
IBM TotalStorage This guide provides guidelines and work sheets for planning the logical SC26-7477
Enterprise Storage configuration of an ESS that attaches to open-systems hosts. (See Note.)
Server: Configuration
Planner for
Open-Systems Hosts
IBM TotalStorage This guide provides guidelines and work sheets for planning the logical SC26-7476
Enterprise Storage configuration of an ESS that attaches to either the IBM S/390® and IBM (See Note.)
Server: Configuration ERserver zSeries host system.
Planner for S/390® and
IBM Eserver zSeries®
Hosts
IBM TotalStorage This guide provides guidelines for attaching the ESS to your host system SC26-7446
Enterprise Storage and for migrating to fibre-channel attachment from either a small computer (See Note.)
Server: Host Systems system interface or from the IBM SAN Data Gateway.
Attachment Guide
IBM TotalStorage This publication provides an overview of the ESS and highlights its unique SC26-7440
Enterprise Storage capabilities. It also describes Data Facility Storage Management (See Note.)
Server: DFSMS Subsystems (DFSMS) software support for the ESS, including support for
Software Support large volumes.
Reference
IBM TotalStorage This guide introduces the ESS product and lists the features you can GC26-7444
Enterprise Storage order. It also provides guidelines for planning the installation and
Server: Introduction and configuration of the ESS.
Planning Guide
IBM TotalStorage This booklet provides flow charts for using the TotalStorage Enterprise SC26-7354
Enterprise Storage Storage Server Specialist (ESS Specialist). The flow charts provide a
Server: Quick high-level view of the tasks that the IBM service support representative
Configuration Guide performs during initial logical configuration. You can also use the flow
charts for tasks that you might perform when you are modifying the logical
configuration.
IBM TotalStorage This publication describes the functions of the ESS and provides SC26-7298
Enterprise Storage reference information, such as channel commands, sense bytes, and error
Server: S/390 Command recovery procedures for IBM S/390 and zSeries hosts.
Reference
IBM TotalStorage Safety This publication provides translations of the danger notices and caution GC26-7229
Notices notices that IBM uses in ESS publications.
IBM TotalStorage This publication describes the functions of the ESS. It provides reference SC26-7297
Enterprise Storage information, such as channel commands, sense bytes, and error recovery
Server: SCSI Command procedures for UNIX®, IBM Application System/400® (AS/400®), and
Reference Eserver iSeries™ 400 hosts.
Subsystem Device This publication describes how to use the IBM Subsystem Device Driver SC26-7540
Driver User’s Guide for (SDD) on open-systems hosts to enhance performance and availability on
the IBM TotalStorage the ESS. SDD creates redundant paths for shared logical unit numbers.
Enterprise Storage SDD permits applications to run without interruption when path errors
Server and the IBM occur. It balances the workload across paths, and it transparently
TotalStorage SAN integrates with applications.
Volume Controller
IBM TotalStorage This guide provides instructions for setting up and operating the ESS and SC26-7445
Enterprise Storage for analyzing problems. (See Note.)
Server: User’s Guide
xiv ESS Introduction and Planning Guide

Order
Title Description
Number
IBM TotalStorage This guide provides instructions for using the two ESS Web interfaces, SC26-7448
Enterprise Storage ESS Specialist and ESS Copy Services. (See Note.)
Server: Web Interface
User’s Guide
The IBM TotalStorage This guide introduces the common interface model (CIM) concept and GC35-0485
Common Interface provides instructions for installing and configuring the CIM Agent. The CIM
Model Agent Installation Agent acts as an open-system standards interpreter, allowing other
and Configuration Guide CIM-compliant storage resource management applications (IBM and
non-IBM) to interoperate with each other.
IBM TotalStorage This publication provides reference information for the IBM TotalStorage GC35-0489
Enterprise Storage Enterprise Storage Server (ESS) application programming interface (API)
Server Application and provides instructions for installing the Common Information Model
Programming Interface Agent, which implements the ESS API.
Reference
Note: No hardcopy book is produced for this publication. However, a PDF file is available from the following Web
site:
http://www-1.ibm.com/servers/storage/support/disk//2105.html
Other IBM publications

Other IBM publications contain additional information that is related to the ESS. The
following list is divided into categories to help you find publications that are related
to specific topics. Some of the publications are listed under more than one category.
See “IBM publications center” on page xxi for information about ordering these and
other IBM publications.
Order
Title Description
Number
Data-copy services
z/OS DFSMS Advanced This publication helps you understand and use IBM Advanced Copy SC35-0428
Copy Services Services functions. It describes three dynamic copy functions and several
point-in-time copy functions. These functions provide backup and recovery
of data if a disaster occurs to your data center. The dynamic copy functions
are peer-to-peer remote copy, extended remote copy, and coupled
extended remote copy. Collectively, these functions are known as remote
copy. FlashCopy, ShapShot, and concurrent copy are the point-in-time copy
functions.
DFSMS/MVS V1: This publication provides guidelines for using remote copy functions with SC35-0169
Remote Copy Guide and S/390 and zSeries hosts.
Reference
IBM Enterprise Storage This publication, from the IBM International Technical Support Organization, SG24-5465
Server introduces the ESS and provides an understanding of its benefits. It also
describes in detail the architecture, hardware, and functions, including the
advanced copy functions, of the ESS.
Implementing Copy This publication, from the IBM International Technical Support Organization, SG24-5680
Services 0n S/390 tells you how to install, customize, and configure Copy Services on an ESS
that is attached to an S/390 or zSeries host system. Copy Services
functions include peer-to-peer remote copy, extended remote copy,
FlashCopy®, and concurrent copy. This publication describes the functions,
prerequisites, and corequisites and describes how to implement each
function into your environment.
About this guide xv

Order
Title Description
Number
IBM TotalStorage ESS This publication, from the IBM International Technical Support Organization, SG24-5757
Implementing Copy tells you how to install, customize, and configure ESS Copy Services on
Services in an Open UNIX, Windows NT®, Windows 2000, Sun Solaris, HP-UX, Tru64,
Environment OpenVMS, and iSeries host systems. The Copy Services functions that are
described include peer-to-peer remote copy and FlashCopy. This
publication describes the functions and shows you how to implement them
into your environment. It also shows you how to implement these functions
in a high-availability cluster multiprocessing environment.
Fibre channel
Fibre Channel This publication provides information about the fiber-channel I/O interface. SA24-7172
Connection (FICON) I/O This book is also available as a PDF file from the following Web site:
Interface: Physical Layer
www.ibm.com/servers/resourcelink/
Fibre-channel This publication tells you how to attach the IBM xSeries™ 430 and No order
Subsystem Installation NUMA-Q® host systems with fibre-channel adapters to the ESS. number
Guide
Contact your sales representative to obtain this publication.
Fibre Transport Services This publication provides information about fibre-optic and ESCON-trunking GA22-7234
(FTS): Physical and systems.
Configuration Planning
Guide
IBM SAN Fibre Channel This guide explains how to convert the IBM SAN Fibre Channel Managed SY27–7616
Managed Hub: 3534 Hub from a Fibre-Channel Arbitrated Loop (FC-AL) configuration to a
Service Guide fabric-capable switched environment.
IBM SAN Fibre Channel This guide provides an overview of the product and discusses available GC26-7391
Managed Hub: 3534 features and upgrades. It also tells you how to install the hub, how to
User’s Guide manage and monitor it using zoning, and how to manage it remotely. It also
tells you how to use the IBM 3534 SAN Fibre Channel Managed Hub
TotalStorage ESS Specialist.
IBM SAN Fibre Channel This guide describes how to install and maintain the IBM SAN Fibre SC26-7350
Switch: 2109 Model S08 Channel Switch 2109 Model S08.
Installation and Service
Guide
IBM SAN Fibre Channel This guide describes the IBM SAN Fibre Channel Switch and the IBM SC26-7349
Switch: 2109 Model S08 TotalStorage ESS Specialist. It provides information about the commands
User’s Guide and how to manage the switch with Telnet and the Simple Network
Management Protocol.
IBM SAN Fibre Channel This publication describes how to install and maintain the IBM SAN Fibre SC26-7352
Switch: 2109 Model S16 Channel Switch 2109 Model S16. It is intended for trained service
Installation and Service representatives and service providers.
Guide
IBM SAN Fibre Channel This guide introduces the IBM SAN Fibre Channel Switch 2109 Model S16 SC26-7351
Switch: 2109 Model S16 and tells you how to manage and monitor the switch using zoning and how
User’s Guide to manage the switch remotely.
Implementing Fibre This publication, from the IBM International Technical Support Organization, SG24-6113
Channel Attachment on helps you install, tailor, and configure fibre-channel attachment of
the ESS open-systems hosts to the ESS. It provides you with a broad
understanding of the procedures that are involved and describes the
prerequisites and requirements. It also shows you how to implement
fibre-channel attachment. This book also describes the steps required to
migrate to direct fibre-channel attachment from native SCSI adapters and
from fibre-channel attachment through the SAN Data Gateway.
Open-systems hosts
xvi ESS Introduction and Planning Guide

Order
Title Description
Number
ESA/390: ESCON I/O This publication provides a description of the physical and logical ESA/390 SA22-7202
Interface I/O interface and the protocols that govern information transfer over that
interface. It is intended for designers of programs and equipment
associated with the ESCON I/O interface and for service personnel who
maintain that equipment. However, anyone concerned with the functional
details of the ESCON I/O interface can find it useful.
ESS Solutions for Open This publication, from the IBM International Technical Support Organization, SG24-6119
Systems Storage: helps you install, tailor, and configure the ESS when you attach Compaq
Compaq AlphaServer, AlphaServer (running Tru64 UNIX), HP, and Sun hosts. This book does not
HP, and Sun cover Compaq AlphaServer that is running the OpenVMS operating
system. This book also focuses on the settings that are required to give
optimal performance and on the settings for device driver levels. This book
is for the experienced UNIX professional who has a broad understanding of
storage concepts.
Fibre-channel This publication tells you how to attach the IBM xSeries 430 and NUMA-Q No order
Subsystem Installation host systems with fibre-channel adapters to the ESS. number
Guide
Contact your sales representative to obtain this publication.
IBM TotalStorage ESS This publication, from the IBM International Technical Support Organization, SG24-5757
Implementing Copy tells you how to install, customize, and configure ESS Copy Services on
Services in an Open UNIX, Windows NT, or Windows 2000 host systems. The Copy Services
Environment functions that are described include peer-to-peer remote copy and
FlashCopy. This publication describes the functions and shows you how to
implement them into your environment. It also shows you how to
implement these functions in a high-availability cluster multiprocessing
environment.
the ESS open-systems hosts to the ESS. It gives you a broad understanding of the
procedures that are involved and describes the prerequisites and
requirements. It also shows you how to implement fibre-channel
attachment. This book also describes the steps that are required to migrate
to direct fibre-channel attachment from native SCSI adapters and from
fibre-channel attachment through the SAN Data Gateway.
S/390 and zSeries hosts
Device Support This publication describes the IBM Device Support Facilities (ICKDSF) GC35-0033
Facilities: User’s Guide product that are used with IBM direct access storage device (DASD)
and Reference subsystems. ICKDSF is a program that you can use to perform functions
that are needed for the installation, the use, and the maintenance of IBM
DASD. You can also use it to perform service functions, error detection,
and media maintenance.
z/OS Advanced Copy This publication helps you understand and use IBM Advanced Copy SC35-0428
Services Services functions. It describes three dynamic copy functions and several
point-in-time copy functions. These functions provide backup and recovery
of data if a disaster occurs to your data center. The dynamic copy functions
are peer-to-peer remote copy, extended remote copy, and coupled
extended remote copy. Collectively, these functions are known as remote
copy. FlashCopy, SnapShot, and concurrent copy are the point-in-time copy
functions.
DFSMS/MVS V1: This publication provides guidelines for using remote copy functions with SC35-0169
Remote Copy Guide and S/390 and zSeries hosts.
Reference
About this guide xvii

Order
Title Description
Number
ESA/390: ESCON I/O This publication provides a description of the physical and logical ESA/390 SA22-7202
Interface I/O interface and the protocols that govern information transfer over that
interface. It is intended for designers of programs and equipment
associated with the ESCON I/O interface and for service personnel who
maintain that equipment. However, anyone concerned with the functional
details of the ESCON I/O interface will find it useful.
Fibre Transport Services This publication provides information about fibre-optic and ESCON-trunking GA22-7234
(FTS): Physical and systems.
Configuration Planning
Guide
Implementing ESS Copy This publication, from the IBM International Technical Support Organization, SG24-5680
Services on S/390 tells you how to install, customize, and configure Copy Services on an ESS
that is attached to an S/390 or zSeries host system. Copy Services
functions include Peer-to-Peer Remote Copy, Extended Remote Copy,
FlashCopy, and Concurrent Copy. This publication describes the functions,
prerequisites, and corequisites and describes how to implement each
function into your environment.
ES/9000, ES/3090: This publication describes the Input/Output Configuration Program that GC38-0097
IOCP User Guide supports the Enterprise Systems Connection (ESCON) architecture. It
Volume A04 describes how to define, install, and configure the channels or channel
paths, control units, and I/O devices on the ES/9000 processors and the
IBM ES/3090 Processor Complex.
IOCP User’s Guide, IBM This publication describes the Input/Output Configuration Program that SB10-7029
Eserver zSeries 800 supports the zSeries 800 and 900 servers. This publication is available in
and 900 PDF format by accessing ResourceLink at the following Web site:
IOCP User’s Guide, IBM This publication describes the Input/Output Configuration Program that SB10-7037
Eserver zSeries supports the zSeries server. This publication is available in PDF format by
accessing ResourceLink at the following Web site:
S/390: Input/Output This publication describes the Input/Output Configuration Program that GC38-0401
Configuration Program supports ESCON architecture and the ESCON multiple image facility.
User’s Guide and
ESCON
Channel-to-Channel
Reference
IBM z/OS Hardware This guide provides conceptual and procedural information to help you use SC33-7988
Configuration Definition the z/OS Hardware Configuration Definition (HCD) application. It also
User’s Guide explains:
v How to migrate existing IOCP/MVSCP definitions
v How to use HCD to dynamically activate a new configuration
v How to resolve problems in conjunction with MVS/ESA HCD
OS/390: Hardware This guide provides detailed information about the input/output definition SC28-1848
Configuration Definition file and about how to configure parallel access volumes. This guide
User’s Guide discusses how to use Hardware Configuration Definition for both OS/390®
and z/OS V1R1.
OS/390 V2R10.0: MVS This publication lists OS/390 MVS™ system messages ABA to ASA. GC28-1784
System Messages
Volume 1 (ABA - ASA)
xviii ESS Introduction and Planning Guide

Order
Title Description
Number
Using IBM 3390 Direct This publication provides device-specific information for the various models GG26-4575
Access Storage in a VM of the 3390 and describes methods you can use to manage storage
Environment efficiently using the VM operating system. It provides guidance on
managing system performance, availability, and space through effective
use of the direct access storage subsystem.
Using IBM 3390 Direct This publication helps you use the 3390 in a VSE environment. It includes GC26-4576
Access Storage in a planning information for adding new 3390 units and instructions for
VSE Environment installing devices, migrating data, and performing ongoing storage
management activities.
Using IBM 3390 Direct This publication helps you use the 3390 in an MVS environment. It GC26-4574
Access Storage in an includes device-specific information for the various models of the 3390 and
MVS Environment illustrates techniques for more efficient storage management. It also offers
guidance on managing system performance, availability, and space
utilization through effective use of the direct access storage subsystem.
z/Architecture Principles This publication provides a detailed definition of the z/Architecture™. It is SA22-7832
of Operation written as a reference for use primarily by assembler language
programmers and describes each function at the level of detail needed to
prepare an assembler language program that relies on a particular
function. However, anyone concerned with the functional details of
z/Architecture will find this publication useful.
SAN
IBM OS/390 Hardware This guide explains how to use the Hardware Configuration Data SC28-1848
Configuration Definition application to perform the following tasks:
User’s Guide v Define new hardware configurations
v View and modify existing hardware configurations
v Activate configurations
v Query supported hardware
v Maintain input/output definition files (IODFs)
v Compare two IODFs or compare an IODF with an actual configuration
v Print reports of configurations
v Create graphical reports of a configuration
v Migrate existing configuration data
IBM SAN Fibre Channel This guide explains how to convert the IBM SAN Fibre Channel Managed SY27–7616
Managed Hub: 3534 Hub from a Fibre-Channel Arbitrated Loop (FC-AL) configuration to a
Service Guide fabric-capable switched environment.
IBM SAN Fibre Channel This guide provides an overview of the product and discussed the features GC26-7391
Managed Hub: 3534 and upgrades available. It also tells you how to install the hub, how to
User’s Guide manage and monitor it using zoning, and how to manage it remotely. It also
tells you how to use the IBM 3534 SAN Fibre Channel Managed Hub
TotalStorage ESS Specialist.
IBM SAN Fibre Channel This guide describes how to install and maintain the IBM SAN Fibre SC26-7350
Switch: 2109 Model S08 Channel Switch 2109 Model S08.
Installation and Service
Guide
IBM SAN Fibre Channel This guide describes the IBM SAN Fibre Channel Switch and the IBM SC26-7349
Switch: 2109 Model S08 TotalStorage ESS Specialist. It provides information about the commands
User’s Guide and how to manage the switch with Telnet and the Simple Network
Management Protocol (SNMP).
About this guide xix

Order
Title Description
Number
IBM SAN Fibre Channel This publication describes how to install and maintain the IBM SAN Fibre SC26-7352
Switch: 2109 Model S16 Channel Switch 2109 Model S16. It is intended for trained service
Installation and Service representatives and service providers.
Guide
IBM SAN Fibre Channel This guide introduces the IBM SAN Fibre Channel Switch 2109 Model S16 SC26-7351
Switch: 2109 Model S16 and tells you how to manage and monitor the switch using zoning and how
User’s Guide to manage the switch remotely.
the ESS open-systems hosts to the ESS. It provides you with a broad
understanding of the procedures that are involved and describes the
prerequisites and requirements. It also shows you how to implement
fibre-channel attachment. This book also describes the steps required to
migrate to direct fibre-channel attachment from native SCSI adapters and
from fibre-channel attachment through the SAN Data Gateway.
Seascape family
IBM Enterprise Storage This publication, from the IBM International Technical Support Organization, SG24-5465
Server introduces the ESS and provides an understanding of its benefits. It also
describes in detail the architecture, hardware, and functions, including the
advanced copy functions, of the ESS.
IBM Enterprise Storage This guide, from the IBM International Technical Support Organization, SG24-5656
Server Performance provides guidance on the best way to configure, monitor, and manage your
Monitoring and Tuning ESS to ensure optimum performance.
Guide
IBM Versatile Storage This publication introduces the IBM Versatile Storage Server™ and lists the GC26-7223
Server: Introduction and features you can order. It also provides planning information for both 2105
Planning Guide Models B09 and 100.
Implementing the IBM This publication, from the IBM International Technical Support Organization, SG24-5420
Enterprise Storage can help you install, tailor, and configure the ESS in your environment.
Server in Your
Environment
Storage management
Device Support This publication describes the IBM Device Support Facilities (ICKDSF) GC35-0033
Facilities: User’s Guide product used with IBM direct access storage device (DASD) subsystems.
and Reference ICKDSF is a program that you can use to perform functions that are
needed for the installation, the use, and the maintenance of IBM DASD.
You can also use it to perform service functions, error detection, and media
maintenance.
IBM TotalStorage This handbook, from the IBM International Technical Support Organization, SG24-5250
Solutions Handbook helps you understand what makes up enterprise storage management. The
concepts include the key technologies that you must know and the IBM
subsystems, software, and solutions that are available today. It also
provides guidelines for implementing various enterprise storage
administration tasks so that you can establish your own enterprise storage
management environment.
IBM TotalStorage Expert: This guide, from the IBM International Technical Support Organization, SG24-6102
Hands-On Usage Guide helps you install, tailor, configure, and use TotalStorage ESS Expert.
IBM TotalStorage Expert This guide helps you install the IBM TotalStorage Expert (formerly the IBM GC26-7436
Installation Guide StorWatch Expert) program. The IBM TotalStorage Expert provides asset,
capacity, and performance management information for disk and tape
storage systems.
xx ESS Introduction and Planning Guide

Order
Title Description
Number
Using IBM 3390 Direct This publication provides device-specific information for the various models GG26-4575
Access Storage in a VM of the 3390 and describes methods that you can use to manage storage
Environment efficiently using the VM operating system. It provides guidance for
managing system performance, availability, and space through effective
use of the direct access storage subsystem.
Using IBM 3390 Direct This publication helps you use the 3390 in a VSE environment. It includes GC26-4576
Access Storage in a planning information for adding new 3390 units and instructions for
VSE Environment installing devices, migrating data, and performing ongoing storage
management activities.
Using IBM 3390 Direct This publication helps you use the 3390 in an MVS environment. It GC26-4574
Access Storage in an includes device-specific information for the various models of the 3390 and
MVS Environment illustrates techniques for more efficient storage management. It also offers
guidance for managing system performance, availability, and space use
through effective use of the direct access storage subsystem.
Ordering IBM publications

This section tells you how to order copies of IBM publications and how to set up a
profile to receive notifications about new or changed publications.
IBM publications center

The publications center is a worldwide central repository for IBM product
publications and marketing material.
The IBM publications center offers customized search functions to help you find the
publications that you need. Some publications are available for you to view or
download free of charge. You can also order publications. The publications center
displays prices in your local currency. You can access the IBM publications center
through the following Web site:
www.ibm.com/shop/publications/order/
Publications notification system

The IBM publications center Web site offers you a notification system for IBM
publications. Register and you can create your own profile of publications that
interest you. The publications notification system sends you a daily e-mail that
contains information about new or revised publications that are based on your
profile.
If you want to subscribe, you can access the publications notification system from
the IBM publications center at the following Web site:
www.ibm.com/shop/publications/order/
Non-IBM publications
Other related publications are not available through IBM ordering systems. To order
them, contact the sales representative at the branch office in your locality.
Title Description
Quick Start Guide: An Example with Network File System This guide tells you how to configure the Veritas Cluster
(NFS) Server. See also the companion document, Veritas
Cluster Server User’s Guide.
About this guide xxi

Title Description
Veritas Cluster Server Installation Guide This guide tells you how to install the Veritas Cluster
Server. See also the companion document, Veritas
Cluster Server Release Notes.
Veritas Cluster Server Release Notes These release notes tell you how to install the Veritas
Cluster Server. See also the companion document,
Veritas Cluster Server Installation Guide.
Veritas Cluster Server User’s Guide This guide tells you how to configure the Veritas Cluster
Server. See also the companion document, Quick Start
Guide: An Example with Network File System (NFS).
Veritas Volume Manager Hardware Notes These hardware notes tell you how to implement multiple
paths dynamically.
Veritas Volume Manager Installation Guide This guide tells you how to install VxVM.
Veritas Volume Manager Storage Administrators Guide This guide tells you how to administer and configure the
disk volume groups.
Web sites
The following Web sites provide information about the ESS and other IBM storage
products.
Type of Storage Information Web Site

Concurrent Copy for S/390 and http://www.storage.ibm.com/software/sms/sdm/
zSeries host systems
Enterprise Storage Server (ESS) http://www.storage.ibm.com/disk/ess/index.html?/ess.htm
ESS Copy Services command-line http://www-1.ibm.com/servers/storage/support/software/cscli.html
interface (CLI)
ESS publications http://www-1.ibm.com/servers/storage/support/disk/2105.html
Click Documentation.
FlashCopy for S/390 and zSeries http://www.storage.ibm.com/software/sms/sdm/
host systems
Host system models, operating http://www-1.ibm.com/servers/storage/support/disk/2105.html
systems, and adapters that the ESS
supports Click Interoperability matrix.
IBM storage products http://www.storage.ibm.com/
IBM version of the Java (JRE) that is http://www-106.ibm.com/developerworks/java/jdk/
often required for IBM products
Multiple Device Manager (MDM) http://www.ibm.com/servers/storage/support/
Click Storage Virtualization.

NUMA-Q host systems http://publib.boulder.ibm.com/xseries/
PPRC for S/390 and zSeries host http://www.storage.ibm.com/software/sms/sdm/
systems
SAN fibre channel switches http://www.ibm.com/storage/fcswitch/
Storage Area Network Gateway and http://www-1.ibm.com/servers/storage/support/san/index.html?
Router
Subsystem Device Driver (SDD) http://www-1.ibm.com/servers/storage/support/software/sdd.html
TotalStorage Expert http://www-1.ibm.com/servers/storage/support/software/swexpert.html
xxii ESS Introduction and Planning Guide

Type of Storage Information Web Site
XRC for S/390 and zSeries host http://www.storage.ibm.com/software/sms/sdm/
systems
How to send your comments

Your feedback is important to help us provide the highest quality information. If you
have any comments about this book or any other ESS documentation, you can
submit them in one of the following ways:
v e-mail
Submit your comments electronically to the following e-mail address:
starpubs@us.ibm.com
Be sure to include the name and order number of the book and, if applicable, the
specific location of the text you are commenting on, such as a page number or
table number.
v Mail
Fill out the Readers’ Comments form (RCF) at the back of this book. Return it by
mail or give it to an IBM representative. If the RCF has been removed, you can
address your comments to:
International Business Machines Corporation
Information Development
Department 61C
9032 South Rita Road
TUCSON AZ 85775-4401
About this guide xxiii

xxiv ESS Introduction and Planning Guide
Summary of Changes
This document contains maintenance and editorial changes. Technical changes or
additions to the text and illustrations are indicated by a vertical line to the left of the
change. This summary of changes describes new functions that have been added
to this release.
Summary of Changes for GC26-7444-06 IBM TotalStorage Enterprise

Storage Server Introduction and Planning Guide
This document contains information previously presented in the IBM TotalStorage
Enterprise Storage Server Introduction and Planning Guide, GC26-7444-05.
The following section summarizes the changes to that information.
New Information
This edition includes the following new information:
v Asynchronous PPRC support
v PPRC primary as FlashCopy target support
v Asynchronous PPRC failover and failback enhancements
v Standby CoD and flexible capacity advanced options (FC 9510 and 9610)
v ESS Model 750 support

The following sections summarize the changes to that information.
New Information
v PPRC over fibre channel support
v Consistency group support
v ESS API support for Copy Services
v Arrays across loops support (feature code 9903)
v Turbo II processor support (feature code 3607)
v RPM intermix support within same disk capacity
v Spare upgrades (feature codes 2192, 2193, and 2194)

The following sections summarize the changes to that information.
© Copyright IBM Corp. 1999, 2004 xxv

New Information
v ESS CLI enhancements
v Copy Services server enhancements
v FlashCopy Version 2
v PPRC Version 2
v IBM Standby Capacity On Demand for ESS (Standby CoD)
v Support for Windows® Server 2003
v Model F10 and F20 support for 72.8-GB DDMs at 15 000 rpm
v Feature Codes 1850 - 1858, 8500 - 8515, 8599, 1860 - 1868, 8600 - 8615, and
8699
Changed Information
This edition includes the following changed information:
v The Step Ahead name has changed to IBM Standby Capacity On Demand for
ESS (Standby CoD).
xxvi ESS Introduction and Planning Guide

Chapter 1. Introduction
This chapter provides the following information:
v An overview of the IBM® TotalStorage™ Enterprise Storage Server™ (ESS)
v Descriptions of data integrity features and performance features
v A description of how the ESS is configured as logical subsystems
Overview of the IBM TotalStorage Enterprise Storage Server

The IBM TotalStorage Enterprise Storage Server (ESS) is a member of the
Seascape®® family of storage servers. The ESS concurrently supports diverse host
systems over diverse attachment protocols. You can allocate data storage among
the attached host systems with the ESS Specialist, a Web-based interface.
The ESS provides integrated caching and support for the attached disk drive
modules (DDMs). The DDMs are attached through a serial storage architecture
(SSA) interface. Disk storage on an ESS is available in modules that contain eight
DDMs. IBM calls these modules disk eight packs.
The ESS provides the following major features. See “ESS data integrity, availability,
and performance features” on page 21 for more details.
v Support of an intermix of types of RAID (redundant array of independent disks)
v Support of non-RAID disk groups
| Note: ESS Models 800 and 750 do not support non-RAID disk groups.
v Fast reduced instruction-set computer (RISC) processors
v A fault-tolerant system
v Fast disk drives with speeds of 10 000 and 15 000 revolutions per minute (rpm)
v Disk capacity that you can assign and reassign among attached host systems
v Instant copy solutions with FlashCopy®
v Disaster recovery solutions with Peer-to-Peer Remote Copy (PPRC)
The ESS models support the following features:

| v Model 750
| – Supports a two-way processor.
| – Supports 8 GB of cache.
| – Support for 72.8 GB and 145.6 GB 10 000 RPM drives that can be intermixed
| and configured as RAID 5, 10, or a both.
| – Supports up to eight disk eight-packs and up to 4.659 TB of physical capacity.
v Model 800:
– Supports either a standard processor or an optional turbo processor.
– Supports 8 GB of cache and an optional 16, 24, 32, or 64 GB of cache.
v Models F10 and F20:
– Support a standard processor.
Note: Models F10 and F20 are no longer available from the factory. Model
800 supersedes Model F20. This publication includes information about
Models F10 and F20 for those models that are currently in the field.
IBM will continue to support these models.
© Copyright IBM Corp. 1999, 2004 1

– Support 8 GB of cache and an optional 16, 24, or 32 GB of cache.
v Models E10 and E20:
– Support a two-way processor.
Note: Models E10 and E20 are no longer available from the factory. Model
800 supersedes Model E20. This publication includes information about
Models E10 and E20 for those models that are currently in the field.
IBM will continue to support these models.
– Support 6 GB of cache.
The ESS models support the following disk drive module (DDM) sizes and speeds:
v Models E10 and E20 support 18.2- and 36.4-GB DDMs at 10000 and 15000 rpm.
Note: The 9.1-GB DDMs are no longer available. IBM does support 9.1-GB
DDMs that are currently installed in an ESS. IBM also supports 9.1-GB
DDM conversion to larger capacity DDM. See “Disk eight-pack
conversion” on page 65 for more information.
v Models F10, F20, and 800 support 18.2-, 36.4-, and 72.8-GB DDMs at 10000
rpm and at 15000 rpm. In addition, the Model 800 supports 145.6-GB DDMs at
10000 rpm.
| v Model 750 supports 72.8 and 145.6-GB DDMs at 10000 rpm.
ESS Models F20 and 800, with an expansion enclosure, can provide the following
data storage capacity:
v With 18.2-GB homogeneous DDMs, the maximum capacity is 7.06 TB.
v With 145.6-GB homogeneous DDMs, the Model 800 supports a maximum
capacity of 55.9 TB.
| v Model 750 does not support an expansion enclosure.
Note: Storage capacity refers to physical data storage, which does not include the
overhead required for RAID parity and spare DDMs.
The large-capacity DDMs, in conjunction with DDM intermix support, provide an

almost unlimited number of configuration options for the ESS.
Figure 1 on page 3 shows an illustration of the base enclosure for ESS Models
E10, E20, F10, and F20. Figure 3 on page 4 shows an illustration of the expansion
enclosure. ESS Models E10 and F10 do not support an expansion enclosure. Both
the ESS base enclosure and the expansion enclosure have dual power cables and
redundant power. The redundant power system enables the ESS to continue normal
operations when one of the power cables is inactive. Redundancy also ensures
continuous data availability.
2 ESS Introduction and Planning Guide

Front view Rear view
Figure 1. ESS Models E10, E20, F10, and F20 base enclosure; front and rear views
| Figure 2 shows an illustration of the ESS Models 750 and 800 base enclosures.
The minimum configuration for all ESS models is 16 DDMs. ESS Models 750, E10
and F10 support a maximum of 64 DDMs. ESS Models E20, F20, and 800 support
a maximum of 384 DDMs, with 128 DDMs in the base enclosure and 256 DDMs in
the expansion enclosure.
Front View Rear View

|
| Figure 2. ESS Model 800 and 750 base enclosure: front and rear views
|
Chapter 1. Introduction 3
Front view Rear view
Figure 3. ESS expansion enclosure: front and rear views
Host systems that the ESS supports

The ESS provides diverse host system attachments so that you can consolidate
storage capacity and workloads for open-systems hosts, S/390 hosts, and ERserver
zSeries hosts. The ESS supports a maximum of 16 host adapters. You can
configure the ESS for any intermix of the following host adapter types and
protocols:
v Small computer system interface (SCSI) adapters
v Fibre-channel adapters, for support of fibre-channel protocol (FCP) and fibre
connection (FICON®) protocol
v Enterprise Systems Connection Architecture® (ESCON®) adapters
Note: Because their data-transfer protocols are very dissimilar, avoid running tape
and disk drives on the same host adapter. A configuration with tape and disk
on a single host adapter gives slow and unreliable performance. Backup
application servers, in particular, exhibit unpredictable results when they
have multiple simultaneous operations to disk and tape.
The following sections provide an overview about each of the following host-system
attachments:
v SCSI-attached host systems
v SCSI-FCP attached host systems
v ESCON-attached IBM S/390 host systems and zSeries host systems
v FICON-attached IBM S/390 host systems and zSeries host systems
v SGI (Silicon Graphics, Inc.) host systems
A comparison of ESS features by host-interface type follows the overview sections

on host-system attachment.

Features and functions are not necessarily available or supported on every ESS
model or in every environment. Refer to the ESS Interoperability Matrix Web site for
a list of interoperable environments and configurations, including minimum operating
system levels and ESS Licensed Internal Code (LIC) prerequisites:
http://www.ibm.com/storage/hardsoft/products/ess/supserver.htm
For detailed information and guidelines for attaching host systems to the ESS, see
the IBM TotalStorage Enterprise Storage Server: Host Systems Attachment Guide.
SCSI-attached open-systems hosts

An ESS attaches to open-systems hosts with two-port SCSI adapters. The SCSI
adapters are 2-byte wide, differential, fast-20. With SCSI adapters, the ESS
supports:
v A maximum of 32 SCSI ports (two ports per adapter)
v A maximum of 15 targets per SCSI adapter
v A maximum of 64 logical units per target, depending on the host-system type
v A maximum of 512 SCSI-FCP host login IDs or SCSI-3 Initiators per ESS
The ESS supports the following host systems for SCSI attachment:
v Hewlett-Packard AlphaServer with Tru64 UNIX® and OpenVMS operating
systems
v Data General with the DG/UX operating system
Data General host systems are not supported by the ESS Model 800.
v Hewlett-Packard with the HP-UX operating system
v IBM AS/400® and the IBM ERserver iSeries 400® (iSeries) with the IBM
Operating System/400® (OS/400®)
v IBM NUMA-Q and the IBM Eserver xSeries (xSeries) with the IBM ptx operating
system
v IBM RS/6000®, Eserver pSeries® (pSeries), and RS/6000 SP™ (Scalable
POWERparallel®) with the IBM AIX® operating system
v Intel-based servers with Microsoft® Windows NT operating system
v Intel-based servers with Microsoft Windows 2000 operating system
v Intel-based servers with Microsoft Windows Server 2003 operating system (both
32- and 64-bit)
v Intel-based servers with Novell NetWare operating system
v Sun with the Solaris operating system
SCSI-FCP attached host systems

| An ESS attaches to open-systems hosts with fibre-channel adapters. You can
| configure the fibre-channel adapters to operate with the SCSI-to-FCP (SCSI-FCP)
| protocol. Shortwave adapters are available on ESS Models E10 and E20.
| Longwave adapters and shortwave adapters are available on Models F10, F20,
| 750, and 800.
With fibre-channel adapters configured for SCSI-FCP protocol, the ESS supports:
v A maximum of 16 fibre-channel ports (one port per adapter)
v A maximum of 128 host login IDs per fibre-channel port
v A maximum of 512 SCSI-FCP host login IDs or SCSI-3 Initiators per ESS
v Logical unit number (LUN) and port masking by target
v Either fibre-channel arbitrated loop (FC-AL), fabric, or point-to-point topologies
The ESS supports the following host systems for fibre-channel attachment:
v Hewlett-Packard AlphaServer with Tru64 UNIX operating systems
v Hewlett-Packard AlphaServers with the OpenVMS operating system
v Hewlett-Packard with the HP/UX operating system
v Fujitsu PRIMEPOWER servers with Solaris Operating Environment operating
system
v IBM AS/400 and iSeries with the IBM OS/400 operating system
v IBM NUMA-Q and xSeries with the ptx operating system
v IBM RS/6000, pSeries, and RS/6000 SP with the IBM AIX operating system
| v IBM pSeries and iSeries with Linux operating system
| v IBM zSeries with United Linux operating system
| v Intel-based servers with the Linux operating system
v Intel-based servers with Microsoft Windows NT operating system
v Intel-based servers with Microsoft Windows 2000 operating system
| v Intel-based servers with VMware operating system
v Intel-based servers with the Microsoft Windows Server 2003 operating system
(both 32- and 64-bit)
v Intel-based servers with the Novell NetWare operating system
v Silicon Graphics (SGI) Origin servers with the IRIX operating system
v Sun with the Solaris operating system
| ESS supports fibre-channel protocol (FCP) and FICON protocol intermix on CNT
| (INRANGE), McDATA, and the IBM2109 Model M12. With intermix support, both
| FCP and FICON upper-level protocols are supported within the same director when
| these protocols are deployed independently by port.
| Implementation details and operational information for using intermix support are
| available at the following director Web sites:
| v CNT (INRANGE):
| http: //www.inrange.com/ibm
| v IBM 2109 M12:
| http: //www.ibm.com/storage/ibmsan/products/sanfabric.html
| v McDATA:
| http://www.mcdata.com/ibm
ESCON-attached host systems

The ESS attaches to S/390 host systems and zSeries host systems with two -port
ESCON adapters or FICON bridge channels. The FICON bridge card in ESCON
Director 9032 Model 5 enables a FICON bridge channel to connect to ESCON host
adapters in the ESS. The FICON bridge architecture supports up to 16 384 devices
per channel.

With ESCON adapters, the ESS supports:
v A maximum of 32 ESCON ports (two ports per adapter) per ESS
v A maximum of 64 logical paths per port
v A maximum of 2048 logical paths per ESS
v A maximum of 16 control-unit images per ESS
v A maximum of 256 logical paths per control-unit image
v Access to all 16 control-unit images and 2048 CKD devices over a single
ESCON port on the ESS
Note: Certain host channels might limit the number of devices per ESCON
channel to 1024. To fully access all 2048 devices, you might need to
transmit signals from four ESCON host channels simultaneously through a
switch to a single ESCON port. This would expose four control-unit
images to each host channel.
The ESS supports the following operating systems for IBM S/390, zSeries,
ES/9000®, and ES/3090™ host systems:
v Linux
v OS/390
v Transaction Processing Facility (TPF)
v Virtual Machine/Enterprise Storage Architecture (VM/ESA®)
v Virtual Storage Extended/Enterprise Storage Architecture (VSE/ESA™)
v z/OS®
v z/VM®
Default operation on the OS/390 and the z/OS operating systems uses a 30-second
missing-interrupt-handler (MIH) timeout for the ESS.
Consult your IBM storage specialist to obtain additional information.
For additional information about S/390 and zSeries support of ESS functions, see
IBM TotalStorage Enterprise Storage Server: DFSMS Software Support Reference.
FICON-attached host systems

| ESS Models F10, F20, and 800 can attach to S/390 and zSeries host systems with
| fibre-channel adapters that are configured to operate with the FICON upper-layer
| protocol. A maximum of 16 fibre-channel ports (one per adapter) can be installed.
| For the Model 750, a maximum of 6 fibre-channel ports can be installed. With
| fibre-channel adapters configured for FICON, the ESS supports the following
| configurations:
| v Either fabric or point-to-point topologies
| v A maximum of 127 channel-login IDs per fibre-channel port
| v A maximum of 16 FICON ports for ESS Models, F10, F20, and 800. For the
| Model 750, a maximum of 6 ports.
| v A maximum of 256 logical paths per FICON port
| v A maximum of 4096 logical paths per ESS (256 logical paths x 16 ports = 4096)
| Note: This support requires ESS models with an LIC level of 2.0.0 or later.
| Models with an LIC earlier than this level support a maximum of 128
| logical paths per control-unit image and a maximum of 2048 logical paths
| per ESS (16 control-unit images x 128 paths per control-unit image).
| v A maximum of 16 control-unit images per ESS
| v A maximum of 256 logical paths to each control-unit image
| v Access to all 16 control-unit images (4096 CKD devices) over each FICON port
The ESS supports the following operating systems for S/390 host systems and
zSeries host systems for FICON attachment:
v Linux
v OS/390
v Transaction processing facility (TPF)
v Virtual Machine/Enterprise Storage Architecture (VM/ESA)
v Virtual Storage Extended/Enterprise Storage Architecture (VSE/ESA)
v z/OS
v z/VM
Consult your IBM storage specialist to obtain additional information.
| ESS supports fibre-channel protocol (FCP) and FICON protocol intermix on CNT
| (INRANGE), McDATA, and the IBM2109 Model M12. With intermix support, both
| FCP and FICON upper-level protocols are supported within the same director when
| deployed independently by port.
| Implementation details and operational information for using intermix support are
| available at the director Web sites:
| v CNT (INRANGE):
| http: //www.inrange.com/ibm
| v IBM 2109 M12:
| http: //www.ibm.com/storage/ibmsan/products/sanfabric.html
| v McDATA:
| http://www.mcdata.com/ibm
Comparison of ESS features by host interface

This section compares ESS features between hosts with different interfaces. Table 1
lists the features in alphabetical order.
Table 1. ESS feature comparison between hosts with different interfaces
Feature Host Systems with SCSI or SCSI-FCP Host Systems with ESCON or FICON
Interfaces Interfaces
Attachment SCSI parallel attachment v ESCON attachment
v 1 - 15 targets per bus – 1 - 16 control-unit images
v 1 - 64 logical units per target – 1 - 64 logical paths per
control-unit image
SCSI-FCP (fibre-channel protocol)
attachment: v FICON attachment
v 128 fibre-channel host ports per ESS port – 1 - 16 control-unit images
v 512 fibre-channel host ports or SCSI – 1 - 128 logical paths per
parallel initiators per ESS control-unit image (See Note 1.)
Concurrent Copy No Yes

Control-unit emulation No v 3990 Model 3; 3990 Model 3 for
TPF; 3990 Model 6
v 2105 Model E10, F10, E20, F20,
and 800

Table 1. ESS feature comparison between hosts with different interfaces (continued)
Feature Host Systems with SCSI or SCSI-FCP Host Systems with ESCON or FICON
Interfaces Interfaces
Control-unit initiated No Yes
reconfiguration (CUIR)
Disk drive module (DDM) Fixed-block address (FBA) Count key data (CKD)
format
Extended Remote Copy No Yes
(XRC)
FlashCopy Yes Yes
Host adapters 1 - 16 v Ultra-SCSI, dual port (for attaching host v ESCON, dual port
systems with SCSI-2 or SCSI-3 adapters) v Fibre-channel, single port (for
v Fibre-channel, single port (for attaching attaching host systems with adapters
host systems with adapters configured for configured for FICON)
SCSI-FCP)
Host-system support v Hewlett-Packard AlphaServer v IBM ES/3090
v Data General v IBM ES/9000
v HP Servers (HP-UX) v IBM S/390
v Fujitsu PRIMEPOWER v IBM zSeries
v IBM AS/400 and iSeries
v IBM NUMA-Q and xSeries
v IBM RS/6000, pSeries, and RS/6000 SP
| v IBM zSeries (FCP and Linux only)
v Intel-based servers
v SGI
v Sun
IBM Subsystem Device Yes No
Driver
Multipath locking facility No Yes
(MPLF)
Multiple allegiance No Yes
Parallel access volumes No Yes
Peer-to-Peer Remote Copy Yes Yes
(PPRC)
PPRC-XD Yes Yes
XRC planned outage No Yes (See Note 2.)
Notes:
1. This support increases to a maximum of 256 logical paths per control-unit image over FICON channels. This
support requires an ESS LIC level of 1.6.0 or greater.
| 2. This function is not supported on the IBM ES/9000, the IBM ES/3090, or the Model 750.
ESS interfaces
This section describes the following interfaces:
v ESS connection security
v ESS Network (ESSNet)
v ESS Specialist
v ESS command-line interface
v ESS Copy Services
v ESS Expert, an optional software product
v ESS service interface
v ESS application programming interface
ESS connection security

You connect to the ESS administrative functions through the IBM TotalStorage
Enterprise Storage Server Master Console (ESS Master Console).
Access to the server functions associated with ESS Specialist and ESS Copy
Services requires user IDs and passwords. You control user access by assigning
levels of access, such as configure or view. The levels of access limit users to the
set of functions that they are authorized to perform.
IBM TotalStorage Enterprise Storage Server Network

The IBM TotalStorage Enterprise Storage Server Network (ESSNet) is a network
that is established between a set of ESSs and various support functions. You need
an ESSNet facility for each set of ESSs in a locality. A local ESSNet is the network
between the ESSNet facility and the ESSs. The local ESSNet supports installation
functions and configuration functions on the associated ESSs through the ESS
Specialist.
IBM installs the ESSNet facility when they install your ESS. The facility consists of
the dedicated ESS Master Console and the networking components.
Note: Feature code (FC) 2717, the ESS Master Console, replaces the remote
support facility, FC 2715. FC 2715 included the ESSNet console.
The ESS Master Console includes an application that provides links to the ESS
user interface. When you click on one of these links, it initiates the Web interface to
ESS Specialist and ESS Copy Services.
You can only use IBM-approved applications on the ESS Master Console. Software
support depends on the LIC level of the ESS.
The following service functions for local and remote service areas depend on
facilities that the local ESSNet networking components provide:
v Simple Network Management Protocol (SNMP) traps
v Electronic mail (e-mail)
v Pagers
v Call home

You can extend the local ESSNet into your Ethernet network and between local
ESSNets to create an expanded Copy Services server domain. The local ESSNet
can also enable other personal computers (PCs) in the network to interact with the
ESSs through either of the following:
v ESS Specialist
v ESS Copy Services
v SNMP protocols
Interface into the ESSNet facility is through the ESS Master Console, or through an
external Ethernet switch or hub that provides cable connections from the ESSNet to
the ESS. The ESS Master Console also requires a telephone connection for
operation of call home, remote service, and pager functions.
Note: You can attach your Ethernet LAN to the external hub. The hub speed is 10
or 100 megabits per second (Mbps), depending on your LAN. You provide
any hardware that is needed for this connection.
The ESS Master Console: The ESS Master Console uses a modem and a
16-port serial adapter that enables communication between your ESS and IBM. The
ESS Master Console offers the following remote support:
v Monitoring of hardware and microcode operations.
v Viewing console message files, formatted error files, log files, and trace files on
demand. This function is available to IBM service support representatives (SSRs)
and other support personnel.
v Activating microcode engineering changes (ECs) from the ESS Master Console.
v Reducing or eliminating long-distance telephone costs for call-home service.
(The ESS Master Console uses the IBM Global Network® to communicate with
the Field Support Center.)
v Improving data transmission rates and improved reliability for state saves and
traces.
v Loading code simultaneously to multiple ESSs.
v Allowing IBM or your service provider to copy an LIC package from a CD at the
ESS Master Console to any or all of your attached ESSs. IBM or your service
provider can then use the service panels on the ESS Master Console to activate
an LIC.
Because of the added benefits, you might want to convert your ESSNet console to
an ESS Master Console. Contact your IBM marketing office to request this free
service. For guidelines about the conversion, see “Converting from an ESSNet
console to an ESS Master Console” on page 110.
Figure 4 on page 12 shows the ESS Master Console connections and remote
support functions.
RS 232-S1
ESS
Cluster RS 232-S2
Ethernet Bay 1 RS 232-S3
15.3 m
(50 ft) CE MoST
ESS RS 232-S1
Cluster
Ethernet Bay 2 RS 232-S2
15.3 m RS 232-S3
(50 ft)
Customer-provided
analog phone line
16-port Ethernet switch
Customer-provided
15.3 m Ethernet cable Catcher
Modem systems
(50 ft) Ethernet
Customer firewall
Master (optional)
Call home To RETAIN or
Console distributed file
To customer network service
FTP trace data
MSA PCI
card
Serial 15.3 m (50 ft) null-modem cable Remote
port service
1.2 m 15.3 m (50 ft) null-modem cable
(4 ft)
Product
engineer
16-port serial adapter (MSA)
1.8 m (6 ft) modem cable
Figure 4. ESS Master Console connections
Methods of accessing the ESS Specialist and ESS Copy Services Web
interfaces: You access the ESS Specialist and ESS Copy Services Web
interfaces from the ESS Master Console. The ESS Master Console includes
browser software for this access.
You can access ESS Specialist from your workstation if you connect the ESS
Master Console into your intranet through one of the ports on the ESSNet switch. If
you use your own workstation, you need to provide the following:
v A workstation with at least 128 MB of memory
v A workstation with a Microsoft Windows operating system
v An additional network connection to the remote ESS through the ESSNet switch
for ESS Copy Services support
| IBM preloads the ESS Master Console with the Netscape Navigator browser. The
| ESS Web interfaces support the following Web browsers:
| v Netscape 4.05 with JDK 1.1 fixpack
| v Netscape 4.06 (no fixpack required)
| v Netscape 4.5x (no fixpack required)
| v Netscape 4.7x (no fixpack required)
| v Netscape 6.1 with Sun JVM 1.4.2+
| v MSIE 4.x with Microsoft Java™ virtual machine (JVM) 4.0 or 5.0
| v MSIE 5.x with Microsoft JVM 4.0 or 5.0
| v MSIE 6.x with Microsoft JVM 4.0 or Sun JVM 1.4.2+

| v Mozilla 1.5 with Sun JVM 1.4.2+
| Notes:
| 1. If your ESS is running with ESS LIC earlier than level 1.3.0 or SC01206, the
| performance of the ESS Web interfaces on IE 5.0 with JVM 5.0 is slower than
| with Netscape. Use Netscape as the browser or move to LIC level 1.3.0 or later.
| Check your ESSNet Console. NetVista™ PCs have been shipped as ESSNet
| Consoles with IE 5.0 and JVM 5.0 as the default browser.
| 2. IE 5.0 with JVM 4.0 is supported with all levels of ESS code. However, IBM
| does not recommend that you change JVM 5.x to JVM 4.0 on the ESSNet
| machine in order to improve performance. It is not trivial to change the JVM to a
| lower level.
| 3. The ESS Master Console running Linux does not support the IE browser.
| 4. There is one additional restriction using Microsoft Internet Explorer. There is a
| problem in some versions of MSIE with handling secure transactions (through
| the SSL) when the browser is in a different domain than the ESS. As a result,
| configuration change actions are not permitted in this situation and result in
| error message 1196 - ″Unencrypted update request″. There is no problem with
| configuration change actions when both browser and server are in the same
| domain. If experiencing 1196 errors, you can either try the operation again using
| a different browser (for example, Netscape), or you might have to do the
| operation from a client machine that resides in the same domain as the ESS.
| Note that the proxy settings in MSIE might affect the operation of MSIE in
| regard to the 1196 message. You might have to disable your proxy server
| settings in MSIE to avoid this restriction.
If you do not attach the ESS Master Console into your intranet, you can only
access the ESS interfaces from the ESS Master Console.
ESS Specialist
The ESS includes the ESS Specialist. The ESS Specialist is a Web-based interface
that enables you to configure the ESS.
IBM logically configures your ESS during installation by using the work sheets that
you completed from the IBM TotalStorage Enterprise Storage Server: Configuration
Planner for S/390 and IBM Eserver zSeries Hosts or IBM TotalStorage Enterprise
Storage Server: Configuration Planner for Open-Systems Hosts. IBM also
establishes communication with the ESS, using the Communication Resources work
sheet that you complete. See Chapter 5, “Planning ESS communications,” on page
95 for more information. After IBM installs the ESS, you can perform additional
configuration by using the ESS Specialist Web interface.
From the Web interface, you can perform the following tasks:
v Monitor error logs
v View and change the configuration, which includes the following subtasks:
– Add or delete SCSI-attached host systems and fibre-channel-attached host
systems
– Configure SCSI host ports and fibre-channel host ports on the ESS
– Define control-unit images for S/390 host systems and zSeries host systems
– Define fixed-block and count-key-data (CKD) disk groups
– Add fixed-block and CKD logical devices (volumes)
– Assign logical devices to be accessible to more than one host system
– Change logical-device 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 allocation of storage space to fixed-block and count key data (CKD) volumes
IBM updates the ESS Specialist through licensed internal code (LIC). See the IBM
TotalStorage Enterprise Storage Server: Web Interface User’s Guide for detailed
information about the ESS Specialist and instructions about how to use it.
ESS command-line interface

The ESS command-line interface (CLI) provides an alternate method to perform
ESS logical configuration and storage management functions. With the ESS CLI,
routine configuration and management tasks can be automated through their
incorporation into scripts and applications. The ESS CLI simplifies ESS
administration, thereby reducing the total cost of ownership. The ESS CLI supports
the following functions:
Asset management Obtains information about ESS volumes, I/O ports,
volume spaces, disk groups, and connected hosts
LUN masking Exposes or unexposes volumes to fibre
channel-based initiators and obtain volume access
information, including a list of volumes not exposed
to any initiator
Space management Queries available free space, creates new volumes
(including CKD volumes), creates volume space,
deletes volume space
Volume identification Assigns a user-specified label to a volume
Host connections Defines, undefines, and modifies host connections
and obtains host type information, including the
host port worldwide name
Audit log Obtains a log of configuration activity by userid
Parallel access volumes Lists, creates, and deletes parallel access volumes
(PAVs)
User account management Queries, creates, and deletes users
Remote services Queries, creates, and deletes remote services
Problems notification Queries and deletes active problems
Performance counters Queries open systems for performance
Copy services Queries functions to view tasks in the copy services
task repository, obtain PPRC path status, and
determine completion of the FlashCopy background
copy
Note: This function requires purchase of the

advanced functions for Copy Services.

You can invoke the ESS CLI from a workstation by issuing commands on a
command line. You can also invoke the CLI from a workstation disk-operating
system (DOS) prompt or a script that invokes a command-line command.
IBM supplies the script and instructions for installing the CLI on your host. The ESS
CLI is provided with the ESS at no additional charge. The ESS CLI client is
available for the AIX, HP-UX, Linux, Solaris, Windows 2000, and Windows Server
2003 operating system environments.
Because the ESS CLI is a Java-based application, you need Java to support CLI
installation. The level of Java support depends on the host type. See the following
Web site for information about the supported open-systems hosts and about the
level of Java that each host system requires:
http://ssddom02.storage.ibm.com/disk/ess/copyservices.html
For more information about the ESS CLI, see the IBM TotalStorage Enterprise
Storage Server: Command-Line Interfaces User’s Guide.
ESS Copy Services

ESS Copy Services operates over the ESSNet and involves a set of ESS storage
servers that are associated in a Copy Services server domain. Each Copy Services
server domain contains a primary and a backup ESS Copy Services server. Each of
the ESS Copy Services servers run on one of the ESS clusters within the Copy
Services server domain. ESS Copy Services provides the following types of
data-copy functions:
FlashCopy Makes a single point-in-time copy.
Peer-to-Peer Remote Copy Automatically copies changes that you make to a
source volume to the target volume until you
suspend or terminate the PPRC relationship.
| Copy Services enhancements: ESS Models F10, F20, 750, and 800 with LIC at
| level 2.3.0 or later support the following Copy Services enhancements:
| Domain expanded You can now define up to eight ESSs, 16 clusters.
| Command timed-out message
| A notification message is displayed when the CLI
| commands rsExecuteTask, rsQuery,
| rsQueryComplete, and rsPrimeServer do not
| complete after 15 minutes.
See the IBM TotalStorage Enterprise Storage Server: Web Interface User’s Guide
for additional information about these options.
The ESS Master Console supports communication between ESS Copy Services
servers and clients within an ESS Copy Services domain. The ESS Master Console
also supports communication between the ESS Copy Services servers and any
ESS Master Consoles or hosts that have an ESS Copy Services interface installed.
The ESS clusters that are part of an ESS Copy Services server domain use the
Transmission Control Protocol/Internet Protocol (TCP/IP) network to communicate.
You identify the TCP/IP addresses on the Communication Resources work sheets
(see “Enable ESS Copy Services work sheet” on page 127). You can configure two
ESS Copy Services servers to a domain. Each ESS Copy Services server domain
manages a maximum of eight ESSs, sixteen clusters, and a maximum of 4000
volumes. Figure 5 describes how ESS Copy Services server domains connect to
each other.
Figure 5. Connecting to ESS Copy Services server domains
See Chapter 2, “ESS advanced functions,” on page 31 for additional information

| about PPRC and FlashCopy.
| Multiple Device Manager (MDM)

| As a component of the IBM TotalStorage Productivity Center, Multiple Device
| Manager reduces the complexity of managing SAN storage devices by allowing
| administrators to configure, manage and monitor storage performance from a single
| console.
| Multiple Device Manager performs the following management tasks:

| v Configure multiple storage devices from a single console
| v Monitor and track the performance of SAN attached Storage Management
| Interface Specification (SMI-S) compliant storage devices
| v Manage advanced storage replication services Peer-to-Peer Remote Copy
| (PPRC) and FlashCopy
| You can consult the following Web site for more information on MDM:
| http://ssdweb01.storage.ibm.com/software/mdm/index.html
IBM TotalStorage Expert

The IBM TotalStorage Expert is an optional software product with a feature that you
can purchase to use with the ESS. The name of the feature is ESS Expert.

Notes:
1. The functions that the ESS Expert feature provides are also available for the
IBM TotalStorage Enterprise Tape Library (ETL). The name of that feature is
ETL Expert.
| 2. You must have LIC level 2.3.1 installed so that ESS Expert and MDM can
| manage the same ESS machines that are attached to the hosts on which the
| performance management applications are installed.
ESS Expert gathers performance, asset, and data capacity information from each
ESS that it finds on a network. It stores this information in a database, and
generates reports that are based on this information. ESS Expert displays these
reports to administrators who sign on to the Expert using a Web browser. You will
need to provide a LAN connection between ESS Expert and the ESS to enable
ESS Expert to gather the information from the ESS. See the following Web site for
additional planning and configuration information:
http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/swexpert
This Web site includes a PDF version of the IBM TotalStorage Expert Installation
Guide. See this publication for more detailed information about the ESS Expert and
for the ESS Expert installation instructions.
The ESS Expert Web interface provides the following storage-resource

management for the ESS:
v Asset management
ESS Expert collects and displays asset management data.
v Capacity management
ESS Expert collects and displays capacity management data.
v Performance management
ESS Expert collects and displays performance management data. For example:
– Number of input/output (I/O) requests
– Number of bytes transferred
– Read and write response time
– Cache usage statistics
v Volume data management
ESS Expert collects and displays volume data.
ESS Expert enables you to schedule the information collection. With this
information, you can make informed decisions about capacity planning and volume
placement. You can also isolate I/O performance bottlenecks.
ESS 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 solutions terminal (MoST) or an equivalent service interface.
The ESS service interface also provides remote service support with call-home
capability for directed maintenance by service personnel. You provide an analog
telephone line to enable this support.
The ESS provides the following service functions:
v Continuous self-monitoring initiates a call (call home) to service personnel if a
failure has occurred. Because service personnel who respond to the call know
about the failing component, they can reduce the repair time.
v Service personnel can access error and problem logs remotely. Service
personnel use the logs to analyze potential failures.
v Remote support can correct many types of problems on the ESS. When the ESS
reports a problem, service personnel can often correct the problem from a
remote location.
You enable or deny service personnel access to the ESS when you fill in the
Communication Resources work sheet. See Chapter 5, “Planning ESS
communications,” on page 95 for more information about the work sheet.
ESS application programming interface

| The ESS application programming interface (API) is a nonproprietary storage
| management client application that supports routine LUN management activities,
| such as LUN creation, mapping, and masking. It also supports Copy Services
| functions, specifically, FlashCopy, PPRC, and Asynchronous PPRC. It supports
| these activities through the use of the interface as defined by the Storage
| Networking Industry Association (SNIA) Storage Management Initiative Specification
| (SMIS).
The ESS API is implemented through the IBM TotalStorage Common Information
Model Agent (CIM Agent) for the ESS, a middleware application that provides a
CIM-compliant interface. The ESS API uses CIM technology to allow these storage
management applications to communicate with an ESS device. The CIM Agent is
available for the AIX, Linux, and Windows operating system environments.
ESS Models F10, F20, 750, and 800 support the following ESS API enhancements:
| Asynchronous Peer-to-Peer Remote Copy
| Asynchronous Peer-to-Peer Remote Copy (PPRC)
| provides a two-site extended distance remote copy
| solution. With Asynchronous PPRC, updates that
| you make to the primary ESS at the local site are
| asynchronously shadowed to the secondary ESS at
| the remote site. A consistent copy of the data is
| then automatically maintained on the secondary
| ESS using PPRC Extended Distance and
| FlashCopy.
| Additional FlashCopy options
| FlashCopy support provides the following additional
| withdraw options: commit and revert. Withdraw
| FlashCopy Commit is a feature that makes the
| FlashCopy relationship no longer revertible,
| commits the new relationship data, updates the
| FlashCopy bitmap, and resets source “Write
| Inhibited”. Withdraw FlashCopy Revert is a feature
| that reverts the relationship to the state that was
| saved by the last Establish Revertible FlashCopy
| command and resets source “Write Inhibited”.

| Note: You must issue Copy Services commands
| for an ESS Model F10 or F20 using an ESS
| Model 750 or 800 that is configured as the
| Copy Services server.
| Support for Microsoft Volume Shadow Copy Service
| The ESS API support for Microsoft Volume Shadow
| Copy Service enables users to quickly back up and
| restore large amounts of data on Windows Server
| 2003. Microsoft Volume Shadow Copy Service
| coordinates with a provider and the Enterprise
| Storage Server to create a consistent shadow copy
| of a volume or group of volumes at a point-in-time.
| This ensures consistency for writers that are aware
| of Volume Shadow Copy Service.
See the IBM TotalStorage Enterprise Storage Server Application Programming

Reference for additional information about these options.
For more information regarding the CIM Agent, refer to the IBM TotalStorage
Enterprise Storage Server Application Programming Interface Reference.
Summary of ESS components and functions

This section gives a summary of ESS components and functions. Table 2 lists the
components and functions in alphabetical order.
Table 2. Summary of ESS components and functions
Components and functions Description
Continuous availability, designed to virtually eliminate v Cluster-processor complex failover
single points of failure or repair (See Note 1.)
v Concurrent maintenance
DDMs (See Note 2.) v 16 - 384 in increments of 16 (two disk eight packs)
v Physical data storage capacity:
– With all 18.2-GB DDMs, the maximum capacity is
7.06 TB.
14.13 TB.
28.26 TB.
| – With all 145.6-GB DDMs, the Model 800 supports a
| maximum capacity of 55.9 TB
Dual-cluster configuration v Cache: 6 GB for Models E10 and E20; 8 GB for the
Model 750; 8 GB standard and optional 16, 24, or 32
GB for Models F10, F20, and 800,
| Note: Model 800 offer an additional cache option of 64
| GB.
| v NVS: 384 MB for Models E10, E20, F10, and F20; 2
| GB for Models 750 and 800
| Expansion enclosure Supported by Models E20, F20, and 800
Read and write functions v Read and write cache
v Fast-write NVS
v Maximum sequential bandwidth
Table 2. Summary of ESS components and functions (continued)
Components and functions Description
Service v Mobile solutions terminal (MoST) or equivalent
v Remote service
v Call home
v Simple Network Management Protocol (SNMP)
Spare DDMs (See Note 3.) v RAID 5
v RAID 10
v RAID reconstruction with a spare DDM
SSA device adapters Eight serial storage adapter loops (maximum)
User interface v Storage server Ethernet attachment
v ESS Master Console
v ESS Specialist Web interface
v ESS Copy Services Web interface
v ESS application programming interface
Notes:
1. For additional availability enhancement install the IBM ESS Subsystem Device Driver on your open-systems
hosts.
| 2. Models F10, F20, 750, and 800 support 72.8-GB DDMs.
3. The ESS provides enhanced availability with spare DDMs:
a. The ESS requires two spare DDMs per SSA loop with a RAID array.
b. For a RAID array with intermixed-capacity DDMs, the number of spares depends on the type of DDMs in
each loop. Each capacity size requires two spares. The ESS supports intermixed DDM sizes on ESS models
with ESS LIC level 1.5.0 or later.
ESS on demand features

| The IBM Standby Capacity On Demand for ESS (Standby CoD) program provides
| standby storage for the ESS and allows you to access the extra storage capacity
| whenever the need arises. This is particularly important if you experience rapid or
| unpredictable growth, or if you can benefit from having storage available when you
| need it.
| For a nominal charge, IBM can install two Standby CoD disk eight-packs in your
| Model 750 and up to six Standby CoD disk eight-packs in your Model 800 or F20.
| At any time, you can logically configure your Standby CoD for use. This process is
| not disruptive and does not require IBM assistance. Upon logical configuration, you
| are charged for the capacity.
Contact your IBM sales representative or Business Partner for additional information
regarding the Standby CoD program terms and conditions.
| In May 2004, the Standby CoD program for the Models 750 and 800 enhanced to
| allows you to purchase ESS advanced function licenses based upon your
| machine’s physical capacity excluding the Standby CoD capacity. An advanced
| function license upgrade purchase is only required when the Standby CoD capacity
| is configured and machine’s total physical capacity (including the newly configured
| Standby CoD) exceeds the advanced function license.

If you currently participate in the Standby CoD program, you may be required to
execute new agreements to utilize this latest enhancement.
Note: As of June 2003, the Step Ahead program was replaced by the Standby
CoD program. The Standby CoD program provides the following additional
flexibility options over the Step Ahead program:
v An ESS can have up to six Standby CoD disk eight-packs.
v Standby CoD disk eight-packs can be installed as a field upgrade.
If you currently participate in the Step Ahead program, you might be required
to execute new agreements to participate in the Standby CoD program.
ESS data integrity, availability, and performance features

This section provides information about data integrity, availability, and performance
features that are supported by the ESS. These are no-charge features. For
descriptions and planning information about optional advanced functions that you
can purchase for the ESS, see Chapter 2, “ESS advanced functions,” on page 31.
This section describes the following features:

v Data-integrity functions and software for host systems
v Redundant array of inexpensive disks (RAID) implementation
– RAID-5 implementation
– RAID-10 implementation
v DDM sparing
v DDM predictive failure analysis
v Redundant storage server with automatic failover
v Nonvolatile storage
v Fast dual write
v Cache
v Longitudinal redundancy check
v Arrays across loops
This section also describes features that are available only for:
v Open-systems hosts. See “Availability support for open-systems hosts” on page
25.
| – Data sharing for UNIX, Windows NT, Windows 2000, and Windows 2003
| operating systems
– IBM TotalStorage Enterprise Storage Server Subsystem Device Driver
v S/390 and zSeries hosts. See “Availability support for S/390 and zSeries hosts”
on page 27.
– Multiple allegiance
– Control-unit initiated reconfiguration
– Support of disk-volume consolidation
Data-integrity functions and software for host systems

The ESS also supports data-availability functions for some host systems with
high-availability cluster multiprocessing (HACMP™) and disk mirroring. HACMP
provides host interconnection. The software interconnects a set of hosts so that a
failure of one host is recovered by moving jobs to other hosts within the set. The
ESS supports HACMP on IBM RS/6000 and pSeries host systems. The ESS
supports software similar to HACMP for non-IBM host systems, such as Veritas
Cluster and Windows 2000 or Windows 2003 Datacenter Server.
The ESS supports TPF operating systems on S/390 and zSeries hosts. TPF
implements software mirroring and can store primary and duplicate copies of its
database on separate logical volumes. This capability improves performance and
availability by using both copies for I/O tasks. If one copy becomes unavailable, the
other copy ensures full database capability. The ESS also supports PPRC and
FlashCopy on TPF. See your IBM field office or consult your IBM storage or TPF
specialist for additional information about TPF.
For additional information about ESS support of data-integrity functions and

software for your host system, see your IBM field office.
RAID implementation
With RAID implementation the ESS offers fault-tolerant data storage. The ESS
supports RAID implementation on the ESS device adapters.
An ESS disk group consists of eight disk drives. The ESS supports groups of DDMs
in a RAID-5 array, a RAID-10 array, or a non-RAID implementation. For a
RAID-array implementation, a device adapter loop must have two spares.
Note: You cannot create RAID arrays that would exceed the capacity of the
installed LIC values (see “Advanced functions” on page 73).
| RAID 5 optimizes capacity. RAID 10 optimizes performance. ESS Models E10, E20,
| F10, and F20 support RAID-5 arrays and non-RAID disk groups. Models 750 and
| 800 support RAID-5 and RAID-10 arrays. (Models 750 and 800 does not support
| non-RAID disk groups.)
| ESS Models 750 and 800, possess the following RAID options and constraints:
| v You can select either RAID 5 or RAID 10 for a new disk group. You can also
| intermix RAID types on the same loop. The ESS determines if the available
| spares on that loop allow the choice that you make.
| v You can copy volumes from one type of RAID array to the other.
| v You can convert a disk group from one type of RAID to the other. However, doing
| so destroys the data on the array, so it is a good idea to back up the data first.
| You cannot convert a RAID array to the other type if the affected loop does not
| have the required two spares. See the IBM TotalStorage Enterprise Storage
| Server: Web Interface User’s Guide for more information about converting to a
| different RAID type.
| RAID-5 implementation
RAID 5 is a method of spreading volume data across multiple disk drives. The ESS
supports RAID-5 arrays on all models.
RAID 5 stripes data across a user-defined set of DDMs. Data protection is provided
by parity, which redundantly saves the data to the same DDMs. Implementation of
RAID-5 data striping increases performance by supporting concurrent accesses to
the multiple DDMs within each logical volume.
Because the ESS requires that a loop have two spare disk drives, the first two
RAID-5 disk groups must use the capacity of six DDMs for data, the capacity of one

DDM for parity, and one DDM as a spare. Subsequent disk groups on the same
loop can stripe data across the capacity of seven DDMs. Striping leaves the
remaining DDM capacity for parity and no spare DDM. See “DDM sparing” for more
information about ESS sparing.
RAID-10 implementation
RAID 10 provides high availability by combining features of RAID 0 and RAID 1.
RAID 0 optimizes performance by striping volume data across multiple disk drives
at a time. RAID 1 provides disk mirroring which duplicates data between two disk
drives. By combining the features of RAID 0 and RAID 1, RAID 10 provides a
second optimization for fault tolerance. Data is striped across half of the disk drives
in the RAID-10 array, and the other half of the array mirrors the first set of disk
drives. Access to data is preserved if one disk in each mirrored pair remains
available. RAID 10 is supported only on the ESS Model 800.
Because the ESS requires that a loop have two spare disk drives, the first RAID-10
disk group must consist of six DDMs and two spares. The data on three DDMs is
mirrored to the other three DDMs. This configuration satisfies the ESS requirement
for two-spares per loop. Subsequent disk groups on the same loop can have eight
DDMs, with the data on four DDMs mirrored to the other four DDMs.
With half of the DDMs in the group used for data and the other half for mirrored
data, RAID-10 arrays have less capacity than RAID-5 arrays.
Note: You cannot define 3380 and 3390 interleave volumes in a RAID-10 array.
You must perform a custom configuration for S/390 disk groups. See the IBM
TotalStorage Enterprise Storage Server: Web Interface User’s Guide for
more information about custom configuration.
Non-RAID implementation
The ESS supports non-RAID disk groups on Models E10, E20, F10, and F20. If you
configure a disk eight pack on the ESS as a non-RAID group, then each logical
volume resides on a single DDM and is not RAID protected.
DDM sparing
For extra protection, the ESS reserves spare disk drives. The sparing function of
the ESS is automatically initiated whenever a DDM failure is detected. If a DDM in
the array fails, the ESS reconstructs the data on the spare DDM by using redundant
information from the remaining DDMs in the array. The ESS maintains data access
during the sparing operation.
Each device (DDM) adapter provides two device loops. Because the device loops
are between adapter pairs, both Clusters 1 and 2 can access all DDMs on a loop. 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.
Because you have two spare disk drives per loop, the loop can have two DDM
failures and you can still access data if the failures are not on the same array. To
protect against loss of data, the ESS makes the data read-only on DDMs on a loop
that has no more spare DDMs available.
For an array with intermixed-capacity disk eight packs, you need two spares per
loop for each different capacity. For failed drives, the ESS initiates a spare drive of
the same size or larger, if the same size is not available.
Recommendation: When disk eight-packs of the same capacity but different rpm
are intermixed on a loop, ensure that the spare drives on that loop are the higher
rpm. This maintains performance in the event of a drive failure. See “Disk
eight-pack intermix options and considerations” on page 61 for more information.
DDM predictive failure analysis

The ESS and its DDMs provide state-of-the-art failure analysis techniques that
predict errors before they affect data availability.
The ESS periodically reads through all data on the DDMs to protect data integrity.
When the ESS detects media errors, it regenerates the data on RAID arrays. The
ESS might also use alternate tracks if that location on the media is bad.
Redundant storage server with automatic failover

The ESS includes a 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” and
“Fast dual-write operation” for additional information on cluster redundancy.
Nonvolatile storage
The ESS Models E10, E20, F10, and F20 have 192 MB per cluster of nonvolatile
storage (NVS) for a total of 384 MB of NVS per ESS.
| ESS Models 750 and 800 have a total NVS of 2 GB. Each pair of NVS cards has
| its own battery-power charger system that protects data during power failure.
In the event that a failure occurs in one cluster, write data is preserved in the NVS
of the other cluster. The data is preserved even if power is lost on the entire ESS,
because the NVS has battery backup for up to 72 hours.
Fast dual-write operation

For improved performance, the ESS implements a fast dual-write operation in which
the ESS signals the host that write operation is complete before the data is stored
on the disk. To protect the data integrity of this write operation, the ESS keeps two
copies of the data, one in the cache of the local cluster and one in the nonvolatile
storage (NVS) of the remote cluster.
Cache
In addition to providing cache for fast dual-write operations, the ESS also provides
the following cache features:
v Fast read from cache
The ESS provides fast-read access by using algorithms to store data in cache
that has the greatest probability of access by a read operation.
v Asynchronous write
The ESS provides fast-data write by completing an operation without accessing
DDMs.
v Least-recently-used (LRU) replacement

The ESS checks data at the top of the cache LRU list for updates in cache that
are not on the DDM. The ESS schedules data at the top of the nonvolatile
storage LRU list for destaging. The ESS can then allocate the data without a
delay during destaging.
v Cache scrubbing
| This facility on Models 750 and 800 cycles through cache and corrects any
| ECC-correctable bit errors, reducing the accumulation of bad bits beyond the
| ability of ECC to correct.
Note: If bit errors do occur beyond ECC capability to correct, data is not lost as
the ESS can go to the NVS copy.
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.
Longitudinal redundancy check

The ESS uses a longitudinal redundancy check (LRC) to locate errors. LRC
provides data-integrity protection on storage devices. It uses a bit column to create
and check parity across bytes of stored data. The LRC checks the data as it
progresses from the host to the ESS device adapter to the DDM.
LRC is also known as a logical redundancy check and a longitudinal parity check.
Arrays across loops

The arrays across loops feature allows you to take full advantage of ESS
subsystem bandwidth. With the arrays across loops feature enabled, a RAID array
is built across two SSA loops within a device adapter pair. Without the arrays
across loops feature enabled, a RAID array can only be built across one SSA loop.
Each SSA loop provides up to 160 MB per second nonarbitrated bandwidth for data
transfer. Providing access to two loops almost doubles the bandwidth capacity
available to a RAID rank.
z/OS logical volumes or open-systems LUNs are striped across the data volumes of
their associated RAID rank. The bandwidth that is available to multiple processes
that access a busy volume or LUN with high demand almost doubles with the
arrays across loops feature. This improves performance and reduces elapsed times
especially for sequential, batch, and file maintenance.
With the arrays across loops feature, you can consider using 146 GB hard disk
drives, even if you were previously unable to use those drives.
Availability support for open-systems hosts

This section describes availability support for open-systems hosts, which includes:
| v Data sharing for UNIX, Windows NT, Windows 2000, and Windows 2003
| operating systems
v The IBM Subsystem Device Driver (SDD)
Data sharing for UNIX, Windows NT, Windows 2000, and
Windows 2003 operating systems
You can use the ESS to share data among multiple UNIX-based homogeneous host
systems and host systems with Windows NT and Windows 2000 operating systems.
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 or pSeries 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 possible without
transferring files, creating second copies of data, or other methods that you may
have used previously.
The IBM TotalStorage Enterprise Storage Server Subsystem

Device Driver
The IBM TotalStorage Enterprise Storage Server Subsystem Device Driver (SDD)
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 6 on page 27 is an example of the type of configuration that the 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.

Host System
SCSI - FCP SCSI - FCP

adapter 0 adapter 1
ESS Port 0 Port 1
Cluster 1 Cluster 2
LUN 0 LUN 1 LUN 2 LUN 3
S009000Q
Figure 6. Multipath connections between a host server and ESS logical unit numbers (LUNs)
The 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 SDD 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.
For additional information about the Subsystem Device Driver, see the Subsystem
Device Driver User’s Guide for the IBM TotalStorage Enterprise Storage Server and
the IBM TotalStorage SAN Volume Controller and the following Web site:
http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/sdd
Availability support for S/390 and zSeries hosts

This section describes the following availability features and other S/390 functions
and zSeries functions:
v Multiple allegiance
v Control-unit initiated reconfiguration
v Support of disk-volume consolidation
Multiple allegiance
The multiple allegiance facility enables the ESS to accept concurrent I/O requests
for a CKD volume from multiple channel paths. This enables the ESS to process
requests from separate S/390 or zSeries hosts in parallel. Parallel processing of
requests improves throughput and performance. The multiple allegiance facility
does not require any user action.
Control-unit initiated reconfiguration

| For zSeries and S/390 environments, the ESS supports control-unit initiated
| reconfiguration (CUIR). CUIR automates channel path quiesce and resume actions
| to eliminate the requirement for manual actions during selected ESS service
| actions. CUIR is supported on Models F10 and F20 with ESS LIC level 1.5.0 or
| later and on Models 750 and 800.
Support of disk-volume consolidation

For zSeries and S/390 environments, the ESS supports a 3390-9 volume with
32 760 cylinders. The ESS also supports large volumes on Linux servers. The
larger volume can help relieve address constraints and improve disk resource
utilization by consolidating multiple disk volumes into a single address. This
consolidation also improves productivity for storage administrators.
| Note: The larger volume is supported on ESS Models F10 and F20 with ESS LIC
| level 1.5.0 or later and on Models 750 and 800.
Support of GDPS HiperSwap

The ESS supports the GDPS® HiperSwap function which rapidly swaps PPRC
volumes for continuous availability. GDPS (Geographically Dispersed Parallel
Sysplex®) is an S/390 or zSeries implementation that enables high data availability
across sites up to 40 km (25 mi) apart.
Logical subsystems
To facilitate configuration, the ESS partitions its 8096 possible logical devices into
groups of 256 devices. Each group is referred to as a logical subsystem (LSS). The
ESS supports a maximum of 16 fixed-block LSSs (4096 logical devices) and 16
CKD LSSs. The ESS maps a CKD LSS directly to S/390 or zSeries control-unit
image, thereby eliminating manual configuration.
Other functions, including some that are associated with fixed-block logical devices,
may have dependencies on LSS partitions. For example:
v The LSS partitions and their associated logical device numbers identify logical
devices that are specified for ESS Copy Services operations.
v To establish Peer-to-Peer Remote Copy (PPRC) pairs, a logical path must be
established between the associated LSS pair.
v FlashCopy pairs must reside within the same LSS.
Reducing the number of LSSs frees up some additional cache memory within the
ESS. If it is probable that you will never require the number of devices that are
allowed by the default (16 LSSs), consider reducing the maximum limit. IBM service
can reduce the number of possible LSSs to eight or zero for either CKD or
fixed-block LSSs. This limits the number of logical devices to 2048 or 0,
respectively.
Later, if you increase ESS capacity, you may also need to increase the number of
LSS that you have defined. This modification to increase the maximum is a

nonconcurrent action. If you might need capacity increases in the future, you should
leave the number of LSSs set to the maximum of 16.
Note: If you reduce the CKD LSS limit to zero for S/390 hosts or zSeries hosts, the
ESS does not process PPRC functions. The fixed-block LSS limit must be no
lower then eight to support PPRC functions for open-systems hosts.
Chapter 2. ESS advanced functions
This chapter provides information about the following optional advanced functions
that are supported on the ESS. See “Advanced functions” on page 73 for the
feature codes for ordering these functions.
v ESS Copy Services advanced functions
v Advanced functions that are supported only for S/390 hosts and zSeries hosts:
– Extended Remote Copy
– Concurrent Copy
Note: Concurrent Copy is not an optional feature. It is an ESS no-charge

feature.
– Parallel access volumes
ESS Copy Services advanced functions

This section describes the optional ESS Copy Services advanced functions. The
ESS supports these functions on open-systems hosts and on S/390 and zSeries
hosts. This section gives the following information:
v Overview of ESS Copy Services
v Planning for ESS Copy Services
v FlashCopy
v Peer-to-Peer Remote Copy (PPRC)
IBM Global Services (IGS) also offers planning and implementation services for
ESS copy services. For additional information, contact your IBM representative or
visit the following Web site:
http://www.ibm.com/services
Overview of ESS Copy Services

ESS Copy Services provides data-copy functions. The set of storage facilities that
an ESS Copy Services server manages is referred to as an ESS Copy Services
domain. An ESS Copy Services server is activated on a cluster within the ESS
Copy Services domain. Each ESS Copy Services domain has at least one pair of
ESS Copy Services servers that are associated with one another.
Copy Services servers in a domain are configured in dual-active or single-active

mode depending on the license internal code (LIC) of the ESS. The Copy Services
servers that are running pre-LIC 2.2.0 are operating in single-active mode. One
server is the primary and the other is the backup. The Copy Services servers that
are running LIC 2.2.0 or higher operate in dual-active mode. This means that both
servers are active at the same time. There is no concept of a primary or backup
Copy Services server. See the IBM TotalStorage Enterprise Storage Server: User’s
Guide for detailed information about the configuration of Copy Services servers.
With dual-active servers, either of the two ESS Copy Services servers can initiate
tasks or monitor status of the Copy Services that they control. Failure of one server
does not prevent the ongoing operation of the ESS Copy Services tasks.

For information about access and communication for ESS Copy Services, refer to
the following sections:
v Accessing ESS Copy Services, see “Methods of accessing the ESS Specialist
and ESS Copy Services Web interfaces” on page 12.
v Communicating with the ESS Copy Services, see “ESS Copy Services” on page
15.
You can define, run, and view the status of ESS Copy Services functions and tasks
in and between the server domains. For example, you can use ESS Copy Services
to perform the following tasks:
v Initiate a FlashCopy task for two volumes in one ESS cluster
v Establish PPRC relationships for volumes in two ESS clusters
v Run predefined PPRC and FlashCopy tasks
From the ESS Copy Services servers, you can define tasks to perform ESS Copy
Services functions between logical devices or logical subsystems within the ESS
Copy Services server domain. You can invoke these tasks from the following
interfaces:
v The ESS Copy Services Web interface
v The Copy Services command-line interface (CLI)
v An I/O interface through a Time Sharing Option (TSO) application programming
interface (API) on ESCON- and FICON-attached hosts
Web-based interface
The ESS Copy Services Web interface initiates and manages Peer-to-Peer Remote
Copy (PPRC) and FlashCopy functions for open-systems hosts and IBM S/390
hosts and zSeries hosts.
Use the ESS Copy Services Web interface to perform the following tasks:
v Define volumes as source or target volumes for PPRC or FlashCopy
v Manage tasks that you have defined
v View the ESS Copy Services event and ESS Copy Services timing logs
v Set password protection
You access the Web interface for ESS Copy Services from the ESS Master
Console. See the IBM TotalStorage Enterprise Storage Server: Web Interface
User’s Guide for detailed information about the ESS Copy Services interface and
instructions about how to use it.
Copy Services command-line interface

The Copy Services command-line interface (CLI) provides an alternate method to
perform Copy Services tasks. The Copy Services CLI is an API that you can invoke
from a workstation by issuing commands on a command line. You can use the CLI
to manage PPRC and FlashCopy functions for open-systems hosts. You can also
invoke the CLI from a workstation disk operating system (DOS) prompt or a script
that invokes a command-line command. If you have installed the CLI application on
an open-systems host and purchased the Advanced Copy Services functions, you
can perform the following Copy Services tasks:
v Write customized scripts by using CLI commands
v Run the CLI commands from a host system
v Invoke Copy Services tasks in an ESS Copy Services server

The CLI is a Java-based application. See IBM TotalStorage Enterprise Storage
Server: Command-Line Interfaces User’s Guide for installation procedures,
additional information, and Java requirements. IBM updates the ESS Copy Services
CLI through LIC updates.
I/O interface
You can invoke Extended Remote Copy (XRC), Concurrent Copy, PPRC, and
FlashCopy on IBM S/390 hosts and zSeries hosts with OS/390 command functions.
The OS/390 and z/OS operating systems provide APIs to run ESS Copy Services
commands over I/O interfaces. The I/O interface operations have no dependencies
on the state of the ESS Master Console or the ESS Copy Services facility.
You can use these APIs to write code that manages ESS Copy Services functions.
ESS Copy Services facilities supported by the APIs include:
v Concurrent Copy
v Peer-to-Peer Remote Copy (PPRC)
v FlashCopy
v Extended Remote Copy (XRC) with suspend and resume capability
For additional information, see z/OS DFSMS Advanced Copy Services.
Planning for ESS Copy Services

This section includes the following planning guidelines for ESS Copy Services:
v ESS Copy Services requirements
v Planning site configurations for disaster recovery
v Planning the ESS Copy Services tasks
ESS Copy Services requirements

Perform the following steps to ensure that your Copy Services facility meets all
requirements:
1. Determine the configuration of ESS Copy Services domains and update the
logical configuration of the appropriate storage facilities as follows:
a. Select the set of storage facilities to be within an ESS Copy Services
domain.
b. Select different clusters within the ESS Copy Services domain on which to
configure the Copy Services servers.
Attention: Copy Services servers are configured in dual-active or
single-active mode depending on the license internal code (LIC) of the ESS.
The Copy Services servers that are running pre-LIC 2.2.0 are operating in
single-active mode. One server is the primary and the other is the backup.
The Copy Services servers that are running LIC 2.2.0 or higher operate in
dual-active mode. This means that both servers are active at the same time.
There is no concept of a primary or backup Copy Services server. See the
IBM TotalStorage Enterprise Storage Server: User’s Guide for detailed
information about the configuration of Copy Services servers.
2. Define and save all required tasks when the ESS Copy Services domain is fully
operational.
3. If you modify the ESS Copy Services domain configuration, also modify existing
tasks or define additional tasks to support the changed scope of the
configuration.
4. Assign unique names to all tasks within an installation.
Chapter 2. ESS advanced functions 33

5. Determine the appropriate use of user IDs, passwords, and user access
authorities for the installation.
6. Determine the configuration of any firewalls within the network to achieve
desired levels of network security.
Note: See Chapter 5, “Planning ESS communications,” on page 95 for more

information about setting passwords and configuring firewalls for ESS
Copy Services.
Planning site configurations for disaster recovery

If a disaster at your production site causes you to lose connections to the server,
you can switch control to the ESS at your recovery site. The steps that you take
depend on how your Copy Services domain is configured. See the IBM
TotalStorage Enterprise Storage Server: User’s Guide for detailed information about
the configuration of Copy Services servers for a disaster recovery environment.
This section provides examples of site configurations for Copy Services and
explains why you might select a particular configuration for disaster recovery.
Example of a PPRC operational configuration: For this example, assume that

you have two sites, Site A and Site B. Each site has a set of ESSs that are
connected to the network. One of the ESS clusters at Site A has been configured
as an ESS Copy Services server. One of the clusters at Site B has been configured
as the alternate ESS Copy Services server. Host systems at both Site A and Site B
have installed the CLI for control of Copy Services. Copy Services keeps tasks
synchronized between the two servers.
Copy Services servers are configured in dual-active or single-active mode

depending on the license internal code (LIC) of the ESS. If your Copy Services
servers are running pre-LIC 2.2.0, the servers are configured in single-active mode,
where one server is defined as the primary and the other is the backup. If the Copy
Services servers are running LIC 2.2.0 or higher, then both servers are operating in
dual-active mode. This means that both servers are active at the same time. There
is no concept of a primary or backup Copy Services server.
If the Copy Services server at Site A is down, you can change the management of
all the ESS clusters to the Copy Services server at Site B. The Copy Services
server at Site B takes over the management of all the remaining ESSs.
A typical PPRC physical configuration might include the following:

v A single logical subsystem (primary) on one ESS is mirrored to a single logical
subsystem (secondary) on another ESS.
v All logical devices or a subset of the logical devices on the primary logical
subsystem are in PPRC pairs with the same logical devices on the secondary
logical subsystem.
The above configurations might apply to a business with its data located at one of
the following sites:
v All production applications and data located in a primary site
v All secondary data located at a disaster-recovery site
Example of a single storage server mirrored to a secondary server: Mirroring

all data that is associated with a server to a backup site reduces the operational
management complexity. This method includes determining what data (on a

file-by-file basis) the backup site requires to recover the application in the event of a
disaster because all data is replicated at the secondary site.
The environment for a mirrored configuration might be:

v All production applications and data are located in a primary site
v All secondary data is located in a secondary or disaster recovery site. For more
information about disaster recovery, see the IBM TotalStorage Enterprise Storage
Server: Web Interface User’s Guide.
Generally, the files that are associated with an application or application set are
dynamic in many environments. Consequently, you might choose to mirror all of the
application data. This configuration requires minimal application
storage-management analysis to guarantee optimal performance.
Example of Bidirectional mirroring: With bidirectional mirroring, one or more of

the devices are mirrored from ESS A to ESS B. The remaining devices are mirrored
from ESS B to ESS A.
This configuration distributes all I/O operations across two ESSs instead of directing
them to a single primary ESS.
Example of a combination configuration: You can combine any options to be

managed as a single logical subsystem to a secondary-site logical subsystem (or
bidirectional), such as:
v A volume list
v A logical volume group
This option depends on the amount of ESS storage that your operational
environment has.
In planning PPRC configurations, you should consider the following information:

v The PPRC configurations (source and target devices) must have the same track
format. Target volumes can be larger than the source volumes. For example, you
can do a FlashCopy from a 9-GB LUN to a 16-GB LUN for data expansion.
v Once the PPRC volumes are in full-duplex state, 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.
v 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 database 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.
v 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 run a task at the Copy Services server to end 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 perform a FlashCopy of the secondary

volume without ending the PPRC pair. The FlashCopy can be used to read the
secondary data at a particular point in time.
Recommendation:
v Ensure that the Copy Services servers are accessible from both the primary and
secondary sites.
v Ensure that the Copy Services servers are physically located on different sites for
disaster recovery purposes.
See the IBM TotalStorage Enterprise Storage Server: User’s Guide for detailed
information about the configuration of Copy Services servers.
Planning the ESS Copy Services tasks

Create tasks during ESS Copy Services configuration that both establish and end
relationships for paths, volumes, ESSs, and LSSs.
Consider the following information when you plan the tasks:

v A copy relationship is on a volume-by-volume basis.
v The target volume must be the same size or larger than the source volume.
Note: For Windows 2000, a dynamic LUN source and target must be the same
size.
v PPRC secondary volumes must be offline to all systems.
v Copy Services tasks are synchronized across servers depending on the mode
and the configuration of the servers. See the IBM TotalStorage Enterprise
Storage Server: Web Interface User’s Guide for more information about how task
changes made in one server are reflected in the other server.
Note: With dual-active servers, either of the two ESS Copy Services servers can
initiate tasks or monitor status of the Copy Services that they control.
Failure of one server does not prevent the ongoing operation of ESS Copy
Services tasks by the other server. Manual intervention is not required in a
dual-active server configuration. See the IBM TotalStorage Enterprise
Storage Server: User’s Guide for information about the configuration of
Copy Services servers.
Use the Tasks panel on the ESS Copy Services Web interface to manage your
tasks. You can perform the following tasks from the Tasks panel:
v Group tasks
v Ungroup tasks
v Modify a task
v Run a saved task
Note: You can only modify or copy tasks that you have named and saved. You
can also run these tasks at a later time. Name the tasks in a way that is
meaningful to you.
v Remove a saved task
v View error information about a failed task
v View information about a saved task
For more detailed information about creating tasks, see the IBM TotalStorage
Enterprise Storage Server: Web Interface User’s Guide.

FlashCopy
FlashCopy provides a nearly instantaneous copy of data to minimize the downtime
needed for data backup. FlashCopy creates a physical point-in-time copy of data
and makes it possible to immediately access both the source and target copies. By
creating an instant copy, FlashCopy enables applications to operate with only a
minimal interruption during FlashCopy use.
You can establish a FlashCopy relationship between CKD volumes or between

fixed-block volumes. This relationship exists from the time you initiate a FlashCopy
operation until one of the following actions takes place:
v The ESS copies all data from the source to the target
v You withdraw the FlashCopy relationship
For S/390 hosts and zSeries hosts, the FlashCopy feature provides instant
replication of a full CKD volume or data set.
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 the following purposes:
v Disaster recovery
v Business intelligence applications
v Test-environment usage
v Instant checkpoints
Note: For S/390 hosts and zSeries hosts, you can also use TSO to invoke these
functions.
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
synchronous backup.
FlashCopy Version 2
| ESS Models F10, F20, 750, and 800 with LIC at level 2.2.0 or later support all
| previous FlashCopy function, plus the following FlashCopy enhancements:
| Data Set FlashCopy Allows a volume to participate in multiple concurrent
| FlashCopy relationships at one time and allows a
| track to be relocated to a different address on the
| target volume.
| FlashCopy Inband over PPRC
| Allows you to establish and withdraw FlashCopy
| pairs at the remote site, without having a Copy
| Services Web interface connection to the remote
| site. Inband commands are issued to the primary
| volumes of PPRC pairs at a local ESS and are sent
| across PPRC paths (acting as a conduit) to a
| remote ESS to enable FlashCopy pairs to be
| established at the remote site.

| Incremental FlashCopy Allows you to create a new point-in-time data copy
| without copying an entire volume for each
| point-in-time copy. The initial FlashCopy operation
| with change recording enabled copies the data on
| the source volume to the target volume to keep the
| volumes in sync. The first incremental FlashCopy
| operation that is performed on the same volume
| pair with change recording enabled copies only the
| out-of-sync tracks to the target volume because
| change recording is maintained on the volume pair.
| Multiple Relationship FlashCopy
| Allows you to create backup copies from one
| source to multiple targets by simultaneously
| establishing multiple FlashCopy relationships.
| Elimination of LSS constraint
| Allows the FlashCopy source and target to reside
| within different logical subsystems (LSSs) within a
| given machine to set up or withdraw a FlashCopy
| relationship across volumes under the following
| conditions: 1) The selected source and target LSSs
| have the same number of volumes and the volumes
| are the same size and type, and 2) The LSSs are
| in the same ESS.
| Improvement in FlashCopy establish time
| Allows improved performance by reducing
| FlashCopy establish time which reduces application
| impact.
| Consistency group support Allows you to create a consistent point-in-time copy
| across multiple volumes with little host impact and
| no operator intervention. A FlashCopy consistency
| group is similar to a PPRC consistency group. It is
| a group of volumes participating in FlashCopy
| relationships in an LSS, across LSSs, or across
| Model 2105 ESSs that must be kept in a consistent
| state to ensure data integrity.
| PPRC primary as FlashCopy target: By using FlashCopy in combination with

| PPRC, you can take a point-in-time copy, and then make copy of that point-in-time
| copy at a remote site at the data set level. This function is only available on Models
| 750 and 800 and requires ESS LIC level 2.4.0 or later.

Peer-to-Peer Remote Copy
Peer-to-Peer Remote Copy (PPRC) is a hardware-based disaster recovery solution
that provides real-time mirroring of logical volumes within an ESS or to another
ESS. The PPRC feature copies a physical volume on one storage server to a target
volume on a second storage server.
PPRC over Fibre Channel

The ESS supports an intermixed configuration of ESCON and fibre-channel
adapters. This allows the sharing of fibre-channel link and fibre-channel port
resources among all Fibre Channel Protocol (FCP) operations. FCP is used to
transmit SCSI commands from one ESS to another. To use PPRC, you must have
ESCON or FCP adapter ports on both the primary and secondary ESS for the
peer-to-peer links.
While you can use both ESCON and FCP paths in the same ESS, a mix of ESCON
and FCP paths is not allowed between two logical subsystems (LSSs). The use of
FCP paths improves performance and requires fewer ports for transmission. Unlike
ESCON, FCP enables bi-directional PPRC, which allows data to be transferred from
one ESS to another, in both directions, and at the same time. In order to use a
fibre-channel adapter as a PPRC link, you must have a PPRC Version 2 license for
both the PPRC primary and secondary ESSs.
You can define from one to eight ESCON or FCP PPRC paths to the secondary
LSS and up to four secondary LSSs to each primary ESS. An ESCON or FCP port
that operates as a PPRC channel can support logical paths between many
control-unit images whether the port connects directly to another server or goes
through a switch.
To initiate a PPRC operation through the ESSNet for a logical device, both the
primary and secondary ESS must be attached to the same ESSNet. The ESSNet is
the ESS access facility that IBM installs when they install your ESS. ESSNet
consists of a switch (hub) and other networking components. See “IBM TotalStorage
Enterprise Storage Server Network” on page 10 for more information.
Synchronous PPRC
Synchronous PPRC protects write operations on both local and remote copies.
When PPRC receives a host update to the primary (local) volume, it completes the
corresponding update to the secondary volume. Synchronous PPRC completes this
corresponding update before giving final status for the update to the host. The ESS
performs Synchronous PPRC in phases:
v During the first phase, PPRC copies data from the primary to the secondary
volume, beginning with the first track and ending with the last track. PPRC uses
a bit map to determine which tracks it needs to copy.
v During the second phase, PPRC checks the bit map and copies any host
updates to the local volume that were received during the first phase. The
updates, and all subsequent updates that are received during the life of the
volume pair, are sent synchronously to the remote volume.
Synchronous PPRC copying supports a maximum distance of 103 km (64 mi).

Delays in response times for Synchronous PPRC are proportional to the distance
between the volumes. However, 100% of the primary data is available at the
secondary site when the copy operation ends.
To use Synchronous PPRC as a copy solution, you must receive prior approval
from IBM if the distance between primary and secondary ESS exceeds 103 km (64

mi). You can request approval by submitting a Request for Price Quotation (RPQ).
The RPQ should include the following information:
v Distance between sites
v Channel extension technology
v Type of telecommunication line
v Amount of network bandwidth
v ESS capacity
v General description of the workload
PPRC Extended Distance

PPRC Extended Distance (PPRC-XD) is included with the PPRC optional feature
on the ESS. The following environments that support PPRC also support PPRC-XD:
v The Web interface provided by the ESS Specialist
v The ESS command-line interface (CLI) in selected open-systems environments
v TSO commands in z/OS and OS/390 operating systems
PPRC-XD is a nonsynchronous long-distance copy option suitable for data

migration and periodic offsite backup. PPRC-XD can operate at distances well
beyond the 103 km (64 mi) supported with Synchronous PPRC transmissions, with
minimal impact on application performance. Only the capabilities of your network
and channel extension technologies limit distance.
Use different logical and physical paths for Synchronous PPRC copy pairs and
PPRC-XD copy pairs during normal PPRC operations. By keeping the logical and
physical paths separate, the synchronous write operation to a secondary ESS does
not adversely affect the I/O performance of the PPRC-XD pairs. This configuration
applies only to environments where the distance between primary and secondary
servers does not exceed 103 km (64 mi).
PPRC-XD copies data from the primary to the remote (secondary) volume. After
copying the data, PPRC-XD continuously cycles through the bit map, sending
updates over a continuous link to the remote copy volume.
This nonsynchronous operation does not maintain order or consistency of data. The
updates arrive at the remote volume some time after final status is given to each
host update. This nonsynchronous copy results in a fuzzy copy of the data on the
remote volume. However, by not waiting for a response before sending updates to
the remote volume, the response-time penalty of synchronous copy over extended
distances is avoided.
Initiate PPRC-XD from the Volumes panel in the ESS Copy Services Web interface
by selecting Establish PPRC Extended Distance copy pairs after you select the
source and target volumes.
To obtain a consistent copy, change the PPRC Extended Distance mode to

Synchronous PPRC mode. Temporarily suspend the PPRC pairs when they reach
full duplex mode (consistency). Perform a FlashCopy on the secondary ESS, and
then resume your operations using PPRC Extended Distance mode. This operation
provides a point-in-time consistent copy at the remote site for data migration,
backup, and transmission of database logs across virtually any distance.
PPRC-XD provides the following advantages over Synchronous PPRC copying:

v Minimal response-time delays for application hosts that are writing to a PPRC
primary device
v Copy distances that can be increased by thousands of kilometers with channel
extenders
v Data migration without the response-time penalty of synchronous copy
v No FlashCopy of the primary volume is required to eliminate the
synchronous-write penalty
PPRC-XD is supported with the use of ESCON directors, dense-wave division

multiplexer products, and channel extenders. Click Interoperability Matrix at the
following ESS web site to access a complete and current list of supported
environments, configurations, networks, and products:
http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/2105
When you use channel extender products with PPRC-XD, the channel extender
vendor determines the maximum distance supported between the primary and
secondary ESS. Contact the channel extender vendors for their distance capability,
line quality requirements, and wide-area network attachment capabilities.
PPRC failover and failback modes

For high-availability and clustered environments, PPRC failover and failback modes
reduce the time required to synchronize PPRC volumes after switching between
sites.
In a typical PPRC environment, processing will temporarily failover to the PPRC

secondary site upon an unplanned outage at the PPRC primary site. When the
primary site is capable of resuming production, processing will failback from the
PPRC secondary site to the primary site.
Without PPRC failover and failback support, synchronization of the PPRC volumes
during a failover process requires transmission of all data from the secondary site to
the primary site. The following descriptions show the advantages of using the PPRC
failover and failback modes during site switching:
PPRC Failback Mode When you use the PPRC failback mode during the
failback to the primary site, only changed data is
sent to the primary site to synchronize the volumes.
Sending only changed data reduces the time to
complete the failback process.
PPRC Failover Mode When you use the PPRC failover mode for failover
to the secondary site, the changes to the data are
recorded while volumes are processed at the
secondary site.
| These PPRC modes can be initiated with the IBM TotalStorage Enterprise Storage
| Server Specialist (ESS Specialist) and the Copy Services CLI. The PPRC failover
| and failback modes are supported on a Models 750, 800, F10, and F20 with LIC
| level 2.1.0 or later. See the IBM TotalStorage Enterprise Storage Server: Web
| Interface User’s Guide and the IBM TotalStorage Enterprise Storage Server:
| Command-Line Interfaces User’s Guide for more information about these modes
| and instructions about how to use them.
PPRC Version 2
| ESS Models F10, F20, 750, and 800 with LIC at level 2.2.0 or later support all
| previous PPRC functions, plus the following PPRC enhancement:

| Asynchronous Cascading PPRC
| Allows three-site long distance disaster recovery.
| This option provides extended business
| continuance.
| ESS Models 750 and 800 with LIC at level 2.3.0 or later supports all previous
| PPRC functions, plus the following PPRC enhancement:
| PPRC over Fibre Channel Protocol
| Improves the performance of PPRC by allowing
| PPRC paths to be established over fibre channel
| (FCP). With FCP, some of the limitations of ESCON
| (for example, distance and performance) are
| removed. FCP links provide higher bandwidth,
| transfer data at faster speeds than the fastest
| ESCON connections, and can connect at longer
| distances between the ESSs than is possible with
| ESCON.
| PPRC Version 2 enhancements

| ESS Models 750 and 800 with LIC at level 2.4.0 or later supports all previous
| PPRC functions, plus the following PPRC enhancements:
| Asynchronous PPRC: Asynchronous PPRC provides a two-site extended

| distance remote copy option for disaster recovery. With Asynchronous PPRC, the
| data that the host writes to the ESS at the local site is asynchronously shadowed to
| the ESS at the remote site. A consistent copy of the data is then automatically
| maintained on the ESS at the remote site.
| Asynchronous PPRC can operate at distances well beyond 103 km (64 mi) with
| minimal delays in response times. Separating volumes by larger distances provides
| greater protection against regional disasters. Only the capabilities of the network
| and channel extension technologies limit distance.
| Asynchronous PPRC uses a configuration of three volumes on two or more ESSs

| (up to eight in a domain). The primary volume is located on the ESS at the local
| site, and the secondary and tertiary volumes are located on the ESS at the remote
| site. The relationship between the volumes is as follows:
| v An extended distance PPRC pair is established between the primary and
| secondary volumes.
| v A FlashCopy relationship is established between the secondary volume and the
| tertiary volume, where the secondary volume is the source of the FlashCopy
| relationship and the tertiary volume is the FlashCopy target of the FlashCopy
| relationship. FlashCopy version 2 is required for this function.
| To ensure that a consistent copy of the data is created, the host writes to the
| primary volume at the local site. The extended distance pair then transfers the data
| from the primary volume to the secondary volume. The FlashCopy operation
| preserves the consistent copy in the tertiary volume at the remote site. To create
| the consistent copy, the data that was written after the beginning of an interval is
| held at the local site until FlashCopy creates a consistent copy of previously written
| data on the tertiary volume.

| Use of asynchronous PPRC does not guarantee against data loss. During a
| disaster, data can only be restored to the last known consistent increment that was
| created. This means that data that is written to the primary site that is waiting to be
| transferred to the secondary site is lost whenever the two ESSs can no longer
| communicate.
| Based on your application and your disaster recovery needs, you can customize
| your configuration. Asynchronous PPRC allows you to determine the maximum host
| response impact affecting the primary volume and the maximum time between
| consistency groups intervals. Increased time between consistency group intervals
| can result in increased data loss during a disaster.
| Besides the ability to create a consistent copy between two ESSs, asynchronous
| PPRC also allows you to create a consistent copy across multiple LSS boundaries
| and multiple ESS box boundaries. In addition, asynchronous PPRC can control the
| backup of CKD and open volumes at the same time within the same consistency
| group. Also, multiple consistency groups are supported among multiple ESS
| configurations.
| Asynchronous PPRC provides the following advantages over synchronous PPRC:

| v Minimal impact to host applications at the primary site, even when volumes are
| separated at distances larger then 103 km (64 mi) or during peak write activity.
| v Volumes that are separated by large distances, providing protection against
| regional disasters, such as weather-related disasters like hurricanes or
| earthquakes.
| v Link bandwidth use is improved between local and remote sites.
| PPRC failover and failback enhancement: For local and remote sites using
| asynchronous PPRC, enhancements to failover, failback, and FlashCopy commands
| provide a software recovery procedure that does not require full copies of volumes
| to restore the configuration to normal operation.
Advanced functions for S/390 and zSeries hosts

This section describes the following advanced functions for S/390 and zSeries host
systems:
v Extended Remote Copy
v Concurrent Copy
Note: Concurrent Copy support on the ESS is a no-charge feature.

v Parallel access volumes
For more detailed descriptions about the Extended Remote Copy (XRC) and
Concurrent Copy features and for procedures about how to use them, see z/OS
DFSMS Advanced Copy Services.
Extended Remote Copy

The ESS supports the XRC feature only on S/390 and zSeries hosts. XRC mirrors
data on the ESS to a remote location for disaster recovery. It protects 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.

With XRC, you can suspend or resume service during an outage. You do not have
to terminate your current data-copy session. You can suspend the session, then
restart it. Only data that has changed during the outage needs to be resynchronized
between the copies.
If you need to change the default setting for an outage, you can do so through the
ESS Copy Services Web interface. IBM service personnel must identify and set up
the ESS Copy Services servers before you use the ESS Copy Services Web
interface.
for the procedures for changing the XRC time-out from the ESS Copy Services
Web interface.
| Note: This feature is not supported on the Model 750.
Concurrent Copy
The ESS supports the Concurrent Copy feature on S/390 and zSeries 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 storage device. Data systems like the
IBM DB2®product can also initiate Concurrent Copy.
Parallel access volumes

The parallel access volume (PAV) facility enables an S/390 or z/Series host to issue
multiple concurrent I/O operations to the same CKD volume on an ESS. Multiple
concurrent I/O operations improve throughput and performance.
You can then dynamically reassign any configured alias address from one CKD
logical device to another CKD logical device. The 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 multiple alias addresses to the base address. The ESS runs I/O
operations to the alias address against the base address.
With PAV, a single S/390 or zSeries host can simultaneously process multiple I/O
operations to the same logical volume. This can reduce volume contention.
See the IBM TotalStorage Enterprise Storage Server: User’s Guide for more
information about using PAV.

Chapter 3. 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. This chapter includes
information about the following topics:
v United States-government orders
v Processor options for ESS Models 800
v Shipping options for ESS Models 800
v Cache capacity
v Power features
v Remote support features
v Physical configuration features and options
v Host adapters
v Host attachment cables
v Operator-panel language feature code
v Logical configuration changes
v Optional one-year warranty
v Advanced functions
United States-government orders

For United States-government orders, select feature code 0983. This feature code
ensures that IBM manufactures the ESS in the United States of America.
Processor options for ESS Model 800

ESS Model 800 supports a standard processor or an optional Turbo processor. IBM
offers feature conversion to allow you to upgrade from a standard processor to a
turbo processor or from a Turbo processor to a Turbo II processor. Use the
following feature codes to select the processor type for your ESS Model 800:
3604 Standard processor
3606 Turbo processor
Note: After February 2004, you can no longer order this feature
from the factory. Feature 3607, the Turbo II processor, has
replaced it.
3607 Turbo II processor

Shipping options for ESS Model 800
Because some sites have weight constraints for ESS delivery, IBM offers shipping
options for the ESS Model 800.
The following option reduces the weight of the ESS Model 800 by shipping selected
components separately. The IBM service support representative (SSR) assembles
the ESS components during ESS installation. This feature increases ESS
installation time and should only be ordered if required.
0970 This feature ensures that the maximum shipping weight of the ESS
base enclosure and expansion enclosure will not exceed 909 kg
(2000 lbs) each. Packaging adds 114 kg (250 lbs).
Cache capacity
Table 3 lists the cache capacity for the ESS models.
Table 3. Cache capacity for the ESS models
Feature Capacity LIC Level ESS Models
Code
N/A 6 GB (3 GB per cluster) 1.0.0 or later Models E10 and E20
4002 8 GB (4 GB per cluster) 1.2.0 or later Models F10 and F20
| 4012 8 GB (4 GB per cluster) 2.0.0 or later Model 800 and 750
4014 16 GB (8 GB per cluster) 2.0.0 or later Model 800
Power features
This section includes information about requirements and feature codes for:
v Power outlets
v Uninterruptible power supply
v Power supply input voltage
v Power cables
v Remote power-control logic card
v Extension cords

Power outlets
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
Use 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
(optional FC 2100 and FC 2110 for Model 800)
v Four regular-voltage power outlets for the ESS Master Console power cables:
– The ESS Master Console PC
– The ESS Master Console monitor
– The switch
– The remote support modem
v One power outlet for the service terminal
This outlet needs to be within 2 m (6 ft) of the ESS.
IBM cannot install the ESS if your site does not meet these power requirements.
Uninterruptible power supply

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

Use the input-voltage feature codes to specify the type of power supply that you
need for the ESS base enclosure and the optional expansion enclosure. These
input voltages are for the following geographical areas:
v The United States (U.S.)
v Canada
v Asia Pacific (AP)
v Latin America (LA)
v Europe, the Middle East, and Africa (EMEA)
Specify one of the following features on your initial order for an ESS:
9870 Nominal ac voltage, 200 - 240 V (phase to phase)
9871 Nominal ac voltage, 380 - 480 V (phase to phase)
Note: Feature 9871 is not compatible with power-cable features

9803, 9853, and 9855.
Chapter 3. Planning the physical configuration 47

Table 4 shows the input voltage feature codes and power cables for the U.S.,
Canada, AP, and LA.
Table 4. Input voltage feature codes for the U.S., Canada, AP, and LA
Power Requirement Input Voltage Power Cable Feature Code
Feature Code
Single-phase power, 200 - 9870 v 9801: 50 or 60 Hz, 50 A (U.S.,
240 V Canada, AP, LA)
v 9803: 50 or 60 Hz, 60 A (Japan)
v 9986: 50 or 60 Hz, 50 A (U.S. -
Chicago)
Three-phase power, 200 - 9870 v 9851: 50 or 60 Hz, 50 A (U.S.,
240 V (phase-to-phase) Canada, AP, LA)
v 9853: 50 or 60 Hz, 60 A (Japan,
U.S.)
v 9854: 50 or 60 Hz, 60 A (U.S.,
Canada, AP, LA)
v 9855: 50 or 60 Hz, 30 A (U.S.,
Canada, AP, LA)
v 9987: 50 or , 60 Hz, 50 A (U.S. -
Chicago)
v 9988: 50 or 60 Hz, 60 A (U.S. -
Chicago)
v 9989: 50 or 60 Hz, 30 A (U.S. -
Chicago)
Table 5 shows the input voltage feature codes and power cables for Europe, the
Middle East, and Africa (EMEA).
Table 5. Input voltage feature codes for EMEA
Power Requirement Input Voltage Power Cable Feature Code
Feature Code
Single-phase power, 200 - 9870 9802: 50 Hz, 50 A
240 V (phase-to-neutral)
240 V
Three-phase power, 200 - 240 9870 9852: 50 Hz, 50 A
V (phase-to-phase)
480 V
Three-phase power, 380 - 480 9871 9852: 50 Hz, 50 A
V (phase-to-phase)
Power cables
IBM provides two power cables with every new ESS and expansion enclosure. You
specify the power cable appropriate for your country or region from the feature
codes listed in this section. When you order an expansion enclosure, IBM includes
the correct power cables based on your selection from these feature codes.
Power-cable orders must also include the appropriate feature code for voltage as
indicated in “Power supply input voltage” on page 47.

Models E10 and F10 do not support the three-phase power features. Order the
following single-phase feature codes for Models E10 and F10:
9801 Single phase, 50 or 60 Hz, 50 A (U.S., Canada, Latin America
(LA), and Asia Pacific (AP)
9802 Single phase, 50 Hz, 50 A (EMEA)
9803 Single phase, 50 or 60 Hz, 60 A (Japan)
Note: Input voltage feature 9871 is not compatible with this power
cable.
9986 Single phase, 50 or 60 Hz, 50 A (Chicago)
| Models E20, F20, 750, and 800 do not support the single-phase power features.
| Order the following three-phase feature codes for Models E20, F20, 750, and 800:
9851 Three phase, 50 or 60 Hz, 50 A for the U.S., Canada, LA, and
AP
9852 Three phase, 50 Hz, 50 A for EMEA
9853 Three phase, 60 Hz, 60 A for Japan and U.S.
cable.
9854 Three phase, 50 or 60 Hz, 60 A for U.S., Canada, LA, and AP
AP
cable.
9987 Three phase, 50 or 60 Hz, 50 A for Chicago (U.S.)
Replacement power cords are also available as optional features. An ESS can only
have one power-cord feature, either the existing power cord (FC 9801 - 9989) or
the replacement power cord (FC 2601 - 2689).
Use the following feature codes to order replacement power cords for ESS Models
E10 and F10. Each feature supplies two power cords:
2601 Single phase, 50 or 60 Hz, 50 A (United States (U.S.), Canada,
Latin America (LA), and Asia Pacific (AP)
2602 Single phase, 50 Hz, 50 A (Europe, Middle East, Africa (EMEA))
2603 Single phase, 50 or 60 Hz, 60 A (Japan)
2686 Single phase, 50 or 60 Hz, 50 A (Chicago)
| Use the following feature codes to order replacement power cords for ESS Models
| E20, F20, 750, and 800. Each feature supplies two power cords:
AP
2652 Three phase, 50 Hz, 50 A for EMEA

2653 Three phase, 50 or 60 Hz, 60 A for Japan and U.S.
AP
AP
Extension cords
For Models E10, E20, F10, and F20, specify one of the following feature codes to
order the extension cord that you require at your site. (These cords are also known
as convenience cords.)
9401 Extension cord group C01
Brazil, U.S., Canada
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, Taiwan, Saudi Arabia, Surinam, Trinidad Tobago,
Venezuela
Peru, Thailand
Israel
Chile, Ethiopia, Italy, Libya, Somalia
Afghanistan, Algeria, Andorra, Angola, Austria, Belgium, Benin,
Bosnia Herzegovina, Bulgaria, Burundi, Cameroon, Central African
Republic, Chad, Congo Brazzaville, Croatia, Czech Republic, Egypt,
Finland, France, French Guiana, Germany, Greece, Guinea,
Hungary, Iceland, Indonesia, Iran, Ivory Coast, Jordan, Kenya,
Korea, Lebanon, Luxemburg, China (Macau Special Administration
Region [S.A.R.]), Malagasy, Mali, Martinique, Mauritania, Mauritius,
Monaco, Morocco, Mozambique, Netherlands, New Caledonia,
Niger, Norway, Poland, Portugal, Romania, Senegal, Slovakia,
Slovenia, Spain, Sudan, Sweden, Syria, Togo, Tunisia, Turkey,
Upper Volta, Russia, Vietnam, Yugoslavia, Zaire, Zimbabwe
Denmark

Argentina, Paraguay, Uruguay
Liechtenstein, Switzerland
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,
China (Hong Kong S.A.R.), India, Iraq, Ireland, Kuwait, Malawi,
Malaysia, Malta, Nepal, Nigeria, Oman, Polynesia, Qatar, Sierra
Leone, Singapore, Tanzania, United Arab Emirates, Uganda, United
Kingdom, Yemen, Zambia
Remote support features

This section includes the following feature codes for remote support:
v Remote power control
v Attachment cables for the remote power-control feature
v Remote support hardware for the ESS Master Console
Note: The remote support facility, FC 2715, which included the ESSNet console,
has been superseded by FC 2717, the ESS Master Console. See
“Converting from an ESSNet console to an ESS Master Console” on page
110 for information about converting an ESSNet console to an ESS
Master Console.
v ESS Master Console additional attachment
v Power cables for remote support by modem group
Remote power control

These optional features are for the logic card that supports remote power control
within the ESS:
1001 Remote power control for Models E10, E20, F10, and F20
| 1011 Remote power control for the Models 750 and 800

Attachment cables for the remote power control feature
You can order attachment cables for the remote power-control feature (see “Remote
power control” on page 51) in quantities from 1 - 8. Table 6 lists the cable group
numbers and the connector IDs.
Table 6. Remote power-control attachment cable group number and connector IDs
ESS Model Remote Power Cable Group Number of Connector ID
Control Feature Number Cables
Code
E10, E20, F10, 1001 1178 1-8 01, 03, 05, 07,
and F20 09, 11, 13, 15
| 750 and 800 1011 1178 1-8 01, 03, 05, 07,
09, 11, 13, 15
Remote support hardware for the ESS Master Console

This feature provides the hardware to support configuration, call home, and remote
support capabilities for the ESS. The facility consists of a dedicated ESS Master
Console (processor, modem, monitor, and keyboard) and networking components
(switch and Ethernet cables). Up to seven ESS machines are supported per ESS
Master Console. Order this feature for the first ESS installation at each location.
Also see “ESS Master Console additional attachment cables.”
2717 This feature provides:
v ESS Master Console
– Personal computer (PC)
– Monitor
– Keyboard
– Power cables (country or region specific)
v Multiport serial adapter (MSA)
v MSA connection cable 1.2 m (4 feet)
v Modem (country or region specific)
v Two RS-232 null modem cables, each 15.3 m (50 ft) in length
v ESS Master Console to modem RS-232 cable 1.8 m (6 feet)
v Ethernet switch
v Three Ethernet cables, each 15.3 m (50 ft) in length
v Product recovery CD for ESS Master Console, including the
Linux operating system
v CD with ESS Master Console LIC
For additional information about this feature, see “The ESS Master
Console” on page 11.
ESS Master Console additional attachment cables

You can connect up to six additional ESS machines to the ESS Master Console
with this feature. Each ESS is connected from an Ethernet port to the ESSNet
switch with an Ethernet cable. The ESSNet switch is connected to the ESS Master
Console by another Ethernet cable. The ESS serial port is connected to the
multiport serial adapter (MSA) on the ESS Master Console.

Order feature 2716 to attach additional ESS machines (up to six) to an ESS Master
Console (feature 2717) or the remote support facility (feature 2715). The additional
ESS machines to be attached with feature 2716 must be within 15.3 m (50 ft) of the
ESS Master Console or the remote support facility.
2716 ESS Master Console additional attachment cables
This feature includes two Ethernet cables, each 15.3 m (50 ft) in
length, and a pair of cables for attaching an ESS to the MSA on the
ESS Master Console.
If you order an ESS with feature 2716, another ESS with a Master Console (feature
2717 ) must be available within a distance of 15.3 m (50 ft). This distance constraint
does not apply to an ESS that is connected through the modem switch and hub
supplied by feature 2715.
Note: The remote support facility, feature 2715, which included the ESSNet
console, was superseded by feature 2717.
Power cables for remote support

Select the power cable for remote support for your modem group:
9301 Modem group M01
Brazil, Canada, Mexico, U.S.
Croatia, Czech Republic, Hungary, Jordan, Kazakhstan, Romania,
Russia, Slovakia, Ukraine
Germany
Israel
France, Italy, Portugal
Japan
Belgium, Netherlands
New Zealand
Denmark, Iceland, Norway, Poland, Sweden
Mozambique, Nigeria, South Africa
Cyprus, Great Britain (UK), Oman, United Arab Emirates (UAE)

Colombia, Costa Rica, Ecuador, Peru, Taiwan, Venezuela, Uruguay
Argentina, Chile, Egypt, Greece, India, Indonesia, Korea, Lebanon,
Philippines, Saudi Arabia, Spain, Thailand, Turkey
Austria
Switzerland
Finland
Australia
Peoples Republic of China, China (Hong Kong Special
Administration Region [S..A.R.]), Malaysia, Singapore
Disk capacity, enclosures, and configuration features and options

This section includes information about the following features and options:
v Flexible capacity options
v Disk eight-packs
v Standby Capacity on Demand (CoD) disk eight-packs
v Spare upgrades
v Disk eight-pack mounting kits
v Expansion enclosures
v Arrays across loops feature
v Reserve loops
v Additional capacity and configuration information:
– Disk eight-pack intermix options and considerations
– Capacity calculation guidelines
– Disk eight-pack installation sequence
– Spare creation
– Disk eight-pack feature conversions
Flexible-capacity options
Table 7 on page 55 lists the flexible capacity options that enable an ESS to support
the intermix of disk eight-pack features (FC 212x, 213x, 214x, and 215x).
| Specify the Standby Capacity on Demand (Standby CoD) flexible capacity option
| (FC 9500) for machines that are participating in the Standby CoD program. Specify
| the flexible capacity option (FC 9600) for all other machines. These features replace
| the standard hardware configuration features that were previously used on ESS
| Models E10, E20, F10, and F20.

| Table 7. Flexible capacity options
| Feature Description ESS Model ESS Models ESS Models LIC
| Code 750 and 800 F10 and F20 E10 and E20 Requirement
| 9500 Standby Yes Model F20 No LIC 1.5.0 or
| Capacity on only later
| Demand
| flexible-
| capacity
| option
| 9600 Flexible Yes Yes Yes LIC 1.5.0 or
| capacity later
| option
|
| Disk eight-packs
You order disk capacity for the ESS through disk eight-packs. A disk-eight pack
contains eight disk drives of the same capacity and rpm. Table 8 on page 56 lists
the feature codes, support, and LIC-level requirements for the disk eight packs.
The following rules apply when you order disk eight-packs:

| v New Model 750 machine orders require a minimum of two disk eight-packs.
| v New Model 800 machine orders require a minimum of four disk eight-packs.
| v You must order disk eight-packs in increments of two features of the same type.
| v For Model 800 machines with the arrays across loops feature (FC 9903) enabled,
| you must order disk eight-packs in increments of four features of the same type.
| See “Model 750 Limitations” on page 61 for capacity and disk-eight pack limitations.
See “Disk eight-pack intermix options and considerations” on page 61 for disk
eight-pack intermix options, limitations, and considerations.
Feature conversions are available to support the exchange of existing disk

eight-packs when you purchase new disk eight-packs. See “Disk eight-pack
conversion” on page 65 for information about feature conversions.

| Table 8. ESS feature codes, model support, and LIC requirements for disk eight packs
| Feature Description Disk ESS ESS ESS ESS LIC
| Code Speed Model Model Models Models Requirement
| 800 750 F10 and E10 and
| F20 E20
| 2122 18.2 GB disk 10 000 Yes No Yes Yes LIC 1.5.1.13
| eight pack rpm or later
| 2123 36.4 GB disk 10 000 Yes No Yes Yes LIC 1.5.1.13
| eight pack rpm or later
| (See
| note)
| 2124 72.8 GB disk 10 000 Yes Yes Yes No LIC 1.5.0 or
| eight pack rpm later
| 2125 145.6 GB 10 000 Yes Yes No No LIC 2.1.0 or
| disk eight rpm later
| pack
| 2142 18.2 GB disk 15 000 Yes No Yes Yes LIC 1.5.2 or
| 2143 36.4 GB disk 15 000 Yes No Yes Yes LIC 1.5.2 or
| 2144 72.8 GB disk 15 000 Yes No Yes No LIC 2.1.1 or
| Note: Prior to August 2000, IBM shipped FC 2123 with 7200 rpm drives.
|
Standby CoD disk eight packs

You can order the IBM Standby Capacity On Demand (Standby CoD) program for
ESS through Standby CoD disk eight-packs described in Table 9 on page 57. A
Standby CoD disk eight-pack contains eight disk drives of the same capacity and
rpm.
You must order Standby CoD disk eight-packs and activate them in increments of
two features of the same type. The Model 750 supports two Standby Cod disk
eight-pack features, while the Models F20 and 800 support up to six Standby CoD
disk eight-pack features. The following requirements apply:
v Four Standby CoD disk eight-packs require a minimum of eight disk eight-pack
features (FC 212x or 214x).
v Six Standby CoD disk eight-packs require a minimum of ten disk eight-pack
features (FC 212x or 214x).
When you activate Standby CoD capacity, you must order a feature conversion to
convert the Standby CoD disk eight-pack feature to the corresponding disk
eight-pack feature. You must order Standby CoD disk eight-pack feature
conversions in pairs of the same type.
If the Standby CoD capacity is not activated within one year, but you have ordered
additional disk eight-packs (FC 212x or 214x), you can remain in the Standby CoD
program by purchasing a one-year Standby CoD Annual Renewal (FC 216x or
217x). You can order the renewal multiple times if you order disk eight-packs within
each prior year.
| The Standby CoD program is available only for Models 750, 800 and F20. Standby
| CoD disk eight-packs are subject to the same intermix options and limitations as

| disk eight-packs. See “Disk eight-pack intermix options and considerations” on page
| 61 for more information on intermix options and limitations.
| Table 9. ESS feature codes and LIC requirements for Standby CoD disk eight-packs
| Feature Description Disk ESS ESS ESS LIC Feature
| Code Speed Model Model Model Requirement Conversion Annual Renewal
| 800 750 F20 Feature
| 2132 Standby CoD 10 000 Yes No Yes LIC 1.5.1.13 or 2122 2162
| 18.2 GB disk rpm later
| eight-pack
| 2133 Standby CoD 10 000 Yes No Yes LIC 1.5.1.13 or 2123 2163
| eight-pack
| 2134 Standby CoD 10 000 Yes Yes Yes LIC 1.5.0 or 2124 2164
| eight-pack
| 2135 Standby CoD 10 000 Yes Yes No LIC level 2.1.0 2125 2165
| 145.6 GB disk rpm or later
| eight-pack
| 2152 Standby CoD 15 000 Yes No Yes LIC 1.5.2 or 2142 2172
| eight-pack
| 2153 Standby CoD 15 000 Yes No Yes LIC 1.5.2 or 2143 2173
| eight-pack
| 2154 Standby CoD 15 000 Yes No Yes LIC level 2.1.1 2144 2174
| 72.8 GB disk rpm or later
| eight-pack
|
Spare upgrades
Table 10 on page 58 describes spare upgrades, which contain two 15 000 rpm disk
drives of the same capacity. They are used to replace lower rpm drives assigned to
the spare pool on an SSA loop.
Recommendation: Order spare upgrades when you want to install 15 000 rpm disk
eight-packs (FC 214x or 215x) on an SSA loop with logically configured eight-packs
of the same capacity but lower rpm (FC 212x or 213x). You must upgrade the
spares to 15 000 rpm to maintain the performance benefits of the 15 000 drive.
Attention: If you do not upgrade the spares when you create an intermix situation
on an SSA loop, you can experience performance degradation if a 15 000 rpm drive
fails. See “Disk eight-pack intermix options and considerations” on page 61 for more
information on intermix options and limitations.
Spare upgrades are available as a field install feature on Models 800 and F20 with
expansion enclosure (FC 2100 or 2110). For Model 800 machines with the arrays
across loops feature (FC 9903) enabled, you must order spare upgrades in
increments of two features of the same type.

Table 10. ESS feature codes and LIC requirements for spare upgrades
Feature Description ESS ESS LIC Prerequisites
Code Model Model Requirement
800 F20
2192 18.2 GB spare Yes Yes LIC 2.3.0 or FC 2122 or 2132 (18.2
upgrade, later GB, 10 000 rpm) and FC
(15 000 rpm) 2142 or 2152 (18.2 GB,
15 000 rpm)
(15 000 rpm) 2143 or 2153 (36.4 GB,
15 000 rpm)
(15 000 rpm) 2144 or 2154 (72.8 GB,
15 000 rpm)
Disk eight-pack mounting kits

A disk eight-pack mounting kit consists of sheet metal cages, power supplies, fans,
and cables. Order a disk eight-pack mounting kit for every eight disk eight-pack
features (FC 212x, 213x, 214x, 215x). Table 11 describes the ESS feature codes for
disk eight-pack mounting kits.
IBM automatically ships the appropriate quantity of disk eight-pack mounting kits
(FC 9101 or 9102) when you order disk eight-packs.
Note: The ESS ships with two disk eight-pack mounting kits in the base enclosure.
This is independent of the number of disk eight-packs that you order.
You can order additional mounting kits for preinstallation with the disk eight-pack
mounting kit preinstall feature (FC 2101 or 2102).
| Table 11. ESS feature codes for disk eight-pack mounting kits
| Feature Description Type ESS ESS ESS ESS
| Code Model Model Models Models
| 800 750 F10 and E10 and
| F20 E20
| 9101 Disk eight-pack No charge No No Yes Yes
| mounting kit specify
| 2101 Disk eight-pack Priced optional No No Yes Yes
| mounting kit
| (preinstall)
| 9102 Disk eight-pack No charge Yes Yes No No
| mounting kit specify
| 2102 Disk eight-pack Priced optional Yes No No No
| mounting kit
| (preinstall)
|

Expansion enclosure
Use the expansion enclosure for adding additional disk-eight packs into an ESS
configuration. It holds up to 32 additional disk eight-pack features and four disk
eight-pack mounting kits. The expansion enclosure is an optional, priced feature.
Table 12 describes the ESS feature codes for expansion enclosures.
The expansion enclosure is required when the total number of installed and ordered
disk eight-packs (FC 212x, 213x, 214x, and 215x) exceeds 16. It is not available on
Models 750, E10, and F10.
Table 12. ESS feature codes for expansion enclosures
Feature Description ESS Models ESS Model ESS Model
Code 800 F20 E20
2100 Expansion enclosure No Yes Yes
2110 Expansion enclosure Yes No No
Arrays across loops

You can use the arrays across loops feature to request a physical configuration in
which disk arrays are spread across both the loops of an SSA device adapter. An
arrays across loops configuration can provide improved performance in some
environments. See “Arrays across loops” on page 25 for information about a
specific environments’ performance with this feature.
Arrays across loops is a no charge, plant-install only feature. However, IBM

Technology Services (ITS) can either convert an existing machine to an arrays
across loops configuration or can reverse an existing configuration, converting it to
a nonarrays across loops configuration. However, both conversion processes are
disruptive and data is not preserved.
You must always order disk eight-packs in a quantity of four features of the same
type for machines with the arrays across loops feature. The arrays across loops
feature is not supported on machines with the Standby Capacity On Demand
program.
The disk eight-pack installation sequence for arrays across loops is different from
the sequence for a nonarrays across loops configuration. See “Disk eight-pack
installation sequence” on page 64 for information on the disk eight-pack installation
sequence for arrays across loops.
Table 13 provides arrays across loops feature codes, requirements, and support.
Table 13. Arrays across loops feature codes, requirements, and model support
Feature Code Description LIC Requirement ESS Support
9903 Arrays across loops LIC 2.3.0 or later Model 800
| Reserve loops
| This feature reserves two SSA loops for future attachment of the IBM 2105 Model
| 100 Expansion Enclosure with IBM 7133 Model 020 or Model D40 drawers, or both.
| When you specify this feature, the installation of disk eight-packs and construction
| of SSA loops creates reserved (empty) SSA loops that can then be used to cable
| 7133 drawers into the configuration. The reserve loop feature reserves two SSA

| loops, but you can order a maximum of two reserve loops features to reserve a
| total of four loops. With one reserve loop feature, you can attach up to six 7133
| drawers; with two reserve loop features, you can attach up to twelve 7133 drawers.
| See Appendix D, “IBM 2105 Model 100 and 7133 Drawer Attachment,” on page 131
| for additional information.
| With reserve loops, the resulting disk eight-pack and SSA loop configuration is
| different than for a machine without this feature. This configuration prevents the
| attachment of an ESS expansion enclosure (FC 2100), even if a 2105 Model 100
| has never actually been attached to the ESS. Therefore, this feature should only be
| specified if your intention is to attach 7133 drawers into the ESS configuration.
| This feature can only be installed at the plant. However, it can be field-installed or
| -removed at a cost by submitting a request for price quotation. Installation might
| require the deconfiguration of arrays on selected SSA loops.
| Table 14 provides reserve loops feature codes and support.

| Table 14. Reserve loops feature codes and model support
| Feature Code Description ESS Models ESS Models ESS Models E10
| 750 and 800 F10 and F20 and E20
| 9904 Reserve loops No Yes Yes
|
|

Additional capacity and configuration information
This section includes information about the following features, options, and
considerations:
v Model 750 limitations
v Disk eight-pack intermix options and considerations
v Capacity calculation guidelines
v Disk eight-pack installation sequence
v Spare creation
v Disk eight-pack feature conversions
| Model 750 Limitations

| The Model 750 supports up to eight Disk Eight-Packs (including Standby CoD) and
| up to 4.659 TB of physical capacity. Table 15 provides valid configuration options.
| Table 15. Model 750 Disk Eight-Pack Configurations
| 72.8 GB 72.8 GB 145.6 GB 145.6 Capacity Total GB
| Eight-Pack Capacity Eight-Pack Capacity
| Quantity Quantity
| 2 1164 0 0 1164
| 4 2329 0 0 2329
| 6 3494 0 0 3494
| 8 4659 0 0 4659
| 2 1164 2 2329 3494
| 4 2329 2 2329 4659
| 0 0 2 2329 2329
| 0 0 4 4659 4659
| Note: A gigabyte (GB) equals one billion bytes when referring to disk capacity.
|
| Disk eight-pack intermix options and considerations

All ESS models support the intermix of disk eight-pack features within a machine
and within an SSA loop, subject to the subsequent limitations.
For Models E10 and E20, this support requires a flexible capacity option feature
(FC 9600), ESS LIC level 1.5.0 or later, and is subject to the following limitation:
v 15 000 rpm disk eight-pack features (FC 214x) cannot be intermixed with lower
rpm disk eight-pack features (FC 212x) of the same capacity:
– FC 2142 (18.2 GB, 15 000 rpm) cannot be intermixed with FC 2122.
– FC 2143 (36.4 GB, 15 000 rpm) cannot be intermixed with FC 2123.

| For Models F10, F20, and 800, this support requires a flexible capacity option
| feature (FC 9500 or 9600), ESS LIC level 1.5.0 or later, and is subject to the
| following limitations:
| v On factory orders (new or refurbished machines), 15 000 rpm disk eight-pack
| features (FC 214x and 215x) cannot be intermixed with lower rpm disk eight-pack
| features (FC 212x and 213x) of the same capacity:
| – FC 2142 and 2152 (18.2 GB, 15 000 rpm) cannot be intermixed with FC 2122
| and 2132.
| and 2133.
| and 2134.
| v Intermixing of 15 000 rpm disk eight-pack features with lower rpm disk eight-pack
| features of the same capacity is available only as a field install. This support
| requires ESS LIC level 2.3.0, or later.
| Recommendation: Models F10, F20, and 800 support the intermix of 15 000 rpm
disk eight-pack features with lower rpm disk eight-pack features of the same
capacity. Order the appropriate 15 000 rpm spare upgrade (FC 219x) when you
order 15 000 rpm disk eight-packs if 15 000 rpm disk eight-packs will be installed on
an SSA loop with logically configured disk eight-packs of the same capacity but
lower rpm. The spare upgrade feature contains two 15 000 rpm disk drives of the
selected capacity and can replace the lower rpm drives that are assigned to the
spare pool on that SSA loop. You must upgrade the spares to 15 000 rpm to help
maintain the performance benefits of the 15 000 rpm drives.
Attention: If you fail to upgrade the spares when an intermix situation on an SSA
loop is first created, the machine is vulnerable to performance degradation in the
event of a 15 000 rpm drive failure. A 10 000 rpm drive replaces the 15 000 rpm
array after drive failure. The performance of the entire array can be degraded to
that of a 10 000 rpm array.
You can intermix rpm’s on an SSA loop only when there are more than two disk
eight-packs on the loop. Therefore, only Models F20 and 800 with an expansion
enclosure (FC 2100 for Model F20, and FC 2110 for Model 800) are subject to
intermix within an SSA loop. Even for those models with an expansion enclosure,
intermix within an SSA loop may not occur. It depends on the combination and
sequence that disk eight-pack features are ordered, installed, and logically
configured, even for models with an expansion enclosure. See “Disk eight-pack
installation sequence” on page 64 for more information.
Contact your disk marketing specialist to determine whether your configuration is

subject to rpm intermix within an SSA loop and to help you plan accordingly.
Capacity calculation guidelines

This section provides guidelines for calculating the effective capacity of your ESS.
See the IBM TotalStorage Enterprise Storage Server: Configuration Planner for
S/390 and IBM Eserver zSeries Hosts or the IBM TotalStorage Enterprise Storage
Server: Configuration Planner for Open-Systems Hosts for work sheets for detailed
planning of the ESS configuration.
| Physical capacity: To calculate the physical capacity of an ESS, multiply each

| disk eight-pack feature by its physical capacity and sum the values. Table 16 on
| page 64 describes the disk eight-pack physical capacity.

Effective capacity: To calculate the effective capacity of an ESS, first determine
the configuration of the arrays on the system. Then add the effective capacities of
each array to determine the total effective capacity. Table 16 on page 64 describes
the disk eight-pack effective capacity.
The effective capacity of an array is the capacity available to configure LUNs or

volumes on each array. Although LUNs and volumes lose some capacity to
overhead, you can closely approximate their effective capacities from the following
information about storage types:
v Effective fixed block LUN capacity is 100 percent based on the effective capacity
of arrays that are configured for a fixed-block track format.
v Effective 3390-volume capacity is 98.7 percent based on the effective capacity of
arrays that are configured for a 3390 track format.
v Effective 3380-volume capacity is 89.1 percent based on the effective capacity of
arrays that are configured for a 3380 track format.
The combination and sequence in which disk eight-pack features are ordered,
installed, and logically configured affects the effective capacity of the ESS. See
“Disk eight-pack installation sequence” on page 64 and “Spare creation” on page 65
for more information.

Table 16. Disk eight-pack capacity
Disk size (GB) Physical Effective capacity (GB) (See Notes 1 and 2.)
Capacity (GB)
Non-RAID RAID 10 arrays RAID 5 arrays (See Note 3.)
disk group
3 x 2 (See 4 x 2 (See 6 + P (See 7 + P (See
Note 4.) Note 5.) Note 6.) Note 7.)
18.2 145.6 17.50 52.50 70.00 105.20 122.74
36.4 291.2 35.04 105.12 140.16 210.45 245.53
72.8 582.4 70.13 210.39 280.52 420.92 491.08
145.6 1164.8 140.26 420.78 561.04 841.84 982.16
Notes:
1. A GB equals one billion bytes when referring to disk capacity.
2. Effective capacity represents the approximate portion of the disk eight pack that is available for creating logical
volumes. All available capacity might not be fully used due to the overhead on logical devices. Although this table
assumes that arrays map directly to disk eight packs, arrays are created using eight disk drives of the same type;
the disk drives are not necessarily contained within the same disk eight pack.
3. In RAID 5 configurations, the parity information uses the capacity of one disk, but is actually distributed across all
the disks within a given disk eight pack.
4. The array consists of three data drives that are mirrored to three copy drives. The remaining drives are used as
spares.
5. The array consists of four data drives that are mirrored to four copy drives.
6. The array consists of six data drives and one parity drive. The remaining drive is used as a spare.
7. The array consists of seven data drives and one parity drive.
Disk eight-pack installation sequence

A given set of disk eight-packs is installed in the sequence of highest capacity and
speed to lowest capacity and speed. As a result, 72.8 GB, 15 000 rpm drives are
installed before 72.8 GB, 10 000 rpm drives or 36.4 GB, 15 000 rpm drives, for
example. A set is a group of disk eight-pack features installed on a new machine
during the initial order, or a group of disk eight-pack features ordered on a capacity
upgrade.
Disk eight-packs are installed in pairs on SSA loops as follows:

v For nonarrays arrays across loops configurations, the disk eight-pack installation
rotates through the loops in the sequence 1A, 2A, 3A, 4A, 1B, 2B, 3B, 4B.
v For arrays across loops configurations (FC 9903), the disk eight-pack installation
rotates through the loops in the sequence 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B.
Disk eight-packs are installed in the disk eight-pack mounting kit as follows:
v For nonarrays arrays across loops configurations, disk eight-packs 1 through 8
are installed in the first disk eight-pack mounting kit, 9 through 16 in the second
disk eight-pack mounting kit, 17 through 24 in the third disk eight-pack mounting
kit, and so on.
v For arrays across loops configurations (FC 9903), disk eight-packs 1 through 16
are installed (evenly distributed) in the first and second disk eight-pack mounting
kits, 17 through 32 are installed (evenly distributed) in the third and fourth disk
eight-pack mounting kits, and 33 through 48 are installed (evenly distributed) in
the fifth and sixth disk eight-pack mounting kits.

Spare creation
The ESS establishes a unique spare pool with the following characteristics for each
drive capacity on an SSA loop that is logically configured into a RAID 5 or RAID 10
array:
v A spare pool must contain at least two drives.
v If an SSA loop contains both RAID 5 and RAID 10 arrays, the spare pool might
have three drives. The number of drives depends upon the sequence in which
the arrays are configured.
The ESS always creates the following spares when it configures the first array (of a
given drive capacity) on an SSA loop:
v If the ESS configures an array as RAID 5, it creates one spare (6 + P array).
v If the ESS configures an array as RAID 10, it creates two spares (3 x 2 array).
The ESS creates the following spares when it configures the second array (of the
same drive capacity) if the first array on the SSA loop was configured as RAID 5:
v If the ESS configures the first array as RAID 5, it creates one additional spare (6
+ P array) if the second array is also RAID 5.
v If the ESS configures the first array as RAID 10, it creates two additional spares
(3 x 2 array) if the second array is RAID 10.
Disk eight-pack conversion

IBM supports disk eight-pack feature conversions to exchange existing disk
eight-packs when you order new disk eight-packs with higher capacity or higher rpm
disk drives. These conversions are particularly useful for increasing storage
capacity at sites with space constraints that prohibit the addition of an expansion
enclosure. These conversions can also be used to install 15 000 rpm disk
eight-pack features into ESS machines that contain disk eight-pack features of the
same capacity but at 10 000 rpm.
The disk eight-pack feature conversion requires the removal of disk eight-packs
from the ESS. Removing logically configured disk eight-packs requires the deletion
of the logical configuration of all disk eight-packs on the SSA loop (not just of the
disk eight-packs to be removed). Data contained on the affected SSA loop is not
preserved during the deletion of the logical configuration. However, data on the
remaining SSA loops is not affected and can continue to be accessed.
IBM service personnel will remove the disk eight-packs. However, you are
responsible for the following tasks:
v Ensuring the machine has the prerequisite LIC level for the new eight-packs to
be installed
v Identifying the physical disk eight-packs to be removed by IBM service personnel
v Making a copy of the data contained on the affected SSA loops before deleting
the logical configuration
v Terminating existing PPRC pairs and PPRC paths before deleting the logical
configuration
v Deleting the logical configuration of disk eight-packs on the affected SSA loops
v Logically configuring the new disk eight-packs
v Restoring the data after the conversion is complete

IBM is not responsible for any data that is contained on the returned disk
eight-packs. As required by customer policies and practices, the customer is
responsible for erasing or invaliding data on disk eight-packs before IBM service
personnel removes them from the ESS.
Host adapters
This section includes the information and feature codes for the following host
adapters:
v SCSI host adapters
v ESCON host adapters
v Fibre Channel (SCSI-FCP and FICON) host adapters
The ESS supports an intermix of Fibre Channel, ESCON, and SCSI host adapters.
A minimum of two host adapters of the same type are required on the initial order,
and the total number of host adapter features cannot exceed 16.
For highest availability, it is recommended that adapters (of the same type) always
be added in pairs. Additionally, to maintain optimum performance, the host adapters
should be installed in a balanced manner between the two clusters within the ESS.
SCSI host adapter

Table 17 describes the SCSI host adapter that enables ESS attachment to SCSI
servers. The adapter has two ports (two 2-byte differential busses). Each port
supports default data transfer (narrow, slow) and wide, fast, and fast-20 data
transfer modes. This support results in data transfer rates of 5 MB/second, 10
MB/second, 20 MB/second, or 40 MB/second, respectively.
The ESS must be located at one end of the bus (as a terminator), and the total
cable length between the ESS and the other terminator can be no greater than 25
meters. The resulting configuration must meet any cable length limitations required
by any attached SCSI device.
Two cables are provided at no charge with each adapter. See “SCSI host
attachment cables” on page 69.
Table 17. SCSI host adapter
Host Adapter ESS Model ESS Models ESS Models ESS LIC
Feature Number Description 800 F10 and F20 E10 and E20 Requirement
3002 SCSI Host Adapter Yes Field install Field install 1.0.0 or later
only only
ESCON host adapters

The ESCON host adapters (Table 18 on page 67) enable ESS attachment to
ESCON channels on zSeries and S/390 servers or ESCON directors. ESCON host
adapters also serve as PPRC channels.
All adapters supports two ESCON links, with each link supporting up to 64 logical
paths. Each port utilizes a light emitting diode (LED) as the optical transceiver, and
supports use of 62.5 micron multimode fiber optic cable terminated with either an
ESCON Duplex connector or a small form factor MT-RJ connector.

Two cables are provided at no charge with each adapter. See “ESCON host
attachment cables” on page 70.
| Table 18. ESCON host adapter
| Host ESS ESS
| Adapter ESS ESS Models Models
| Feature Receptacle Model Model F10 and E10 and ESS LIC
| Number Description Type 800 750 F20 E20 Requirement
| 3011 Standard ESCON ESCON No No Withdrawn Field install 1.0.0 or later
| Host Adapter Duplex only
| 3012 Enhanced ESCON ESCON Withdrawn No Field install No 1.4.0 or later
| Host Adapter Duplex only
| 3013 64-bit ESCON Host MT-RJ Yes Yes No No 2.1.0 or later
| Adapter
|
Fibre-channel (SCSI-FCP and FICON) host adapters

The Fibre Channel host adapters enable ESS attachment to Fibre Channel
(SCSI-FCP) and FICON servers and SAN fabric components.
The adapters have one port and support either 1 Gb/second and 2 Gb/second, or
both, full duplex data transfer over longwave or shortwave fibre links. They support
the use of 9, 50, or 62.5 micron fiber optic cable terminated with either a standard
connector (SC) or Lucent connector (LC). See Table 21 on page 68 for distances
supported with the various cables. You are responsible for ensuring that link
distances are adhered to.
Supported protocols include SCSI-FCP ULP (Upper Layer Protocol) on

point-to-point, fabric, and arbitrated loop (private loop) topologies and the FICON
ULP on point-to-point and fabric topologies. SCSI-FCP and FICON are not
supported simultaneously on an adapter.
One cable is provided at no charge with each host adapter feature. See
“Fibre-channel host attachment cables” on page 71.
Table 19 lists the characteristics supported by each adapter. Table 20 on page 68

lists ESS model support and LIC requirements. Table 21 on page 68 lists fibre optic
cables and distances.
Table 19. Fibre channel host adapter characteristics
Host
Adapter
Feature Receptacle Supported
Number Description Protocols Type Link Speed Type Cables
3021 Fibre Channel / FICON SCSI-FCP and Longwave 1 Gb/second SC 9 micron
Host Adapter FICON (singlemode),
50 micron
(multimode),
62.5 micron
(multimode)
3022 Fibre Channel Host SCSI-FCP Shortwave 1 Gb/second SC 50 micron
Adapter (multimode),
62.5 micron
(multimode)

Table 19. Fibre channel host adapter characteristics (continued)
Host
Adapter
Feature Receptacle Supported
Number Description Protocols Type Link Speed Type Cables
3023 Fibre Channel / FICON SCSI-FCP and Shortwave 1 Gb/second SC 50 micron
Host Adapter FICON (multimode),
62.5 micron
(multimode)
3024 2 Gb Fibre Channel / SCSI-FCP and Longwave 2 Gb/second LC 9 micron
FICON Host Adapter FICON and 1 (singlemode)
Gb/second
3025 2 Gb Fibre Channel / SCSI-FCP and Shortwave 2 Gb/second LC 50 micron
FICON Host Adapter FICON and 1 (multimode),
Gb/second 62.5 micron
(multimode)
| Table 20. Fibre channel host adapter model support and LIC requirement
| ESS ESS
| Host Adapter Models Models
| Feature ESS Model ESS Model F10 and E10 and ESS LIC
| Number Description 800 750 F20 E20 Requirement
| 3021 Fibre Channel / FICON Host No No Field install No 1.4.0, or later
| Adapter only
| 3022 Fibre Channel Host Adapter No No Withdrawn Field install 1.2.0, or later
| only
| 3023 Fibre Channel / FICON Host No No Field install No 1.4.0, or later
| Adapter only
| 3024 2 Gb Fibre Channel / Yes Yes No No 2.0.0, or later
| FICON Host Adapter
| 3025 2 Gb Fibre Channel / Yes Yes No No 2.0.0, or later
| FICON Host Adapter
|
Table 21. Fibre optic cables and distances
Longwave - 1 Longwave - 2
Shortwave - 1 Shortwave - 2 Gb/second (See Gb/second (See
Gb/second (See Gb/second (See Notes 3, 4, and Notes 2, 3, and
Fibre optic cable Note 1) Notes 1 and 2) 5) 4)
9 micron, singlemode not applicable not applicable 10 km 10 km
50 micron, multimode 500 m 300 m 550 m not applicable
62.5 micron, multimode (200 MHz-km) 300 m 150 m 550 m not applicable
(See Note 5)
62.5 micron, multimode (160 MHz-km) 250 m 120 m 550 m N/A
(See Note 5)

Table 21. Fibre optic cables and distances (continued)
Longwave - 1 Longwave - 2
Shortwave - 1 Shortwave - 2 Gb/second (See Gb/second (See
Gb/second (See Gb/second (See Notes 3, 4, and Notes 2, 3, and
Fibre optic cable Note 1) Notes 1 and 2) 5) 4)
Notes:
1. A jumper cable is required when using shortwave with 50 or 62.5 micron multimode cables terminated with
ESCON Duplex connectors. The cable must have a male SC or LC connector on one end and an ESCON
Duplex receptacle on the other end.
2. Selected ESS adapters can operate at either 2 Gb/second or 1 Gb/second link speed. These adapters will
auto-negotiate with the attached unit to determine whether the link will operate at 1 or 2 Gb/second. Care should
be exercised when attaching new equipment that is capable of 2 Gb/second operation in place of old equipment
that was only capable of 1 Gb/second. The length of the link may be adequate for 1 Gb/second operation, but
inadequate for 2 Gb/second operation.
3. Support for FICON point-to-point distances of up to 20 km is available through Request for Price Quotation
(RPQ). Both ends of the link must support the increased distance.
4. Distances up to 100 km can be supported with appropriate SAN fabric components.
5. The use of multimode cables with longwave is primarily intended to enable use of existing ESCON cables for
FICON. This use reduces the distance capability provided by longwave and requires the use of mode
conditioning patch (MCP) cables. The MCP must terminate at one end with a 9 micron singlemode SC or LC
connector and at the opposite end with a 62.5 micron multimode ESCON Duplex receptacle.
Host attachment cables

This section includes the information and feature codes for the following cables:
v SCSI host attachment cables
v ESCON host attachment cables
v Fibre channel host attachment cables
Cables are provided at no additional charge with each ESS host adapter feature.
However, in some situations, the required lengths and installation of host
attachment cables will be unique to your configuration and facility specifications.
Additional cable options and product support services offered by IBM Global
Services’ Networking Services can provide assistance for these unique cabling and
installation requirements.
SCSI host attachment cables

A SCSI cable is required to attach the ESS to SCSI ports on servers. Two cables
are provided, at no additional charge, with each SCSI Host Adapter feature (#300x).
Cable options are shown below in Table 22. Two specify cable features (#97xx)
must be specified in conjunction with each host adapter feature number.
Additional and replacement cables can be ordered with the optional cable features
(#28xx).
Table 22. SCSI host attachment cables
Host Specify Optional
Adapter Cable Cable
Feature Feature Cable Feature
Number Number Cable Description Length Number
3002 9701 Ultra SCSI cable 10 meters 2801

Table 22. SCSI host attachment cables (continued)
Adapter Cable Cable
Number Number Cable Description Length Number
9702 Ultra SCSI 20 meters 2802
9703 SCSI-2 Fast and Wide 10 meters 2803
9704 SCSI-2 Fast and Wide 20 meters 2804
9705 SCSI-2 Fast and Wide (IBM iSeries and 10 meters 2805
AS/400)
9706 SCSI-2 Fast and Wide (IBM iSeries and 20 meters 2806
AS/400)
9707 SCSI-2 Fast and Wide (Sun PCI and 10 meters 2807
HP (dual) PCI)
9708 SCSI-2 Fast and Wide (Sun PCI and 20 meters 2808
HP (dual) PCI)
9709 SCSI-2 Fast and Wide (HP PCI) 10 meters 2809
9710 SCSI-2 Fast and Wide (HP PCI) 20 meters 2810
ESCON host attachment cables

An ESCON cable is required to attach the ESS to ESCON channels on zSeries and
S/390 servers or ESCON directors. Two cables are provided, at no additional
charge, with each ESCON host adapter feature (#301x).
Cable options are shown below in Table 23. One specify cable feature (#97xx) must
be specified in conjunction with each host adapter feature.
(#28xx).
Table 23. ESCON host attachment cables
Host Optional
Adapter Specify Cable Cable
Feature Feature Cable Cable Feature
Number Number Cable Description Rating Length Length
3011 9780 62.5 micron with ESCON Standard 31 2880
Duplex connectors meters
9781 62.5 micron with ESCON Plenum 31 2881
9770 62.5 micron with MT-RJ Standard 31 2870
and ESCON Duplex meters
connectors
9771 62.5 micron with MT-RJ Plenum 31 2871
connectors
3012 9780 62.5 micron with ESCON Standard 31 2880
9781 62.5 micron with ESCON Plenum 31 2881

Table 23. ESCON host attachment cables (continued)
Host Optional
Adapter Specify Cable Cable
Feature Feature Cable Cable Feature
Number Number Cable Description Rating Length Length
9770 62.5 micron with MT-RJ Standard 31 2870
connectors
9771 62.5 micron with MT-RJ Plenum 31 2871
connectors
3013 9790 62.5 micron cable with Standard 31 2890
MT-RJ connectors meters
9791 62.5 micron cable with Plenum 31 2891
MT-RJ connectors meters
9770 62.5 micron cable with Standard 31 2870
MT-RJ and ESCON meters
Duplex connectors
9771 62.5 micron cable with Plenum 31 2871
MT-RJ and ESCON meters
Duplex connectors
9775 62.5 micron cable with Standard 2 meters 2875
MT-RJ connector and
ESCON Duplex
receptacle (See note 1)
Note: Feature #9775 provides a conversion cable to enable the attachment of existing
ESCON cables with ESCON Duplex connectors to the host adapter feature #3013.
Fibre-channel host attachment cables

A fiber optic cable is required to attach the ESS to fibre channel and FICON ports
on servers and fabric components. One cable is provided, at no additional charge,
with each fibre channel and fibre channel/FICON host adapter feature (#302x).
Cable options are shown below in Table 24. One specify cable feature (#97xx) must
be specified in conjunction with each host adapter feature.
(#28xx).
Table 24. Fibre channel / FICON host attachment cables
Adapter Cable Cable
Number Number Cable Description (See Note 1.) Length Number
3021 9750 9 micron, singlemode with SC 31 meters 2850
connectors
9751 9 micron, singlemode with SC and LC 31 meters 2851
connectors
9760 50 micron, multimode with SC 31 meters 2860
connectors
9761 50 micron, multimode with SC and LC 31 meters 2861
connectors

Table 24. Fibre channel / FICON host attachment cables (continued)
Adapter Cable Cable
Number Number Cable Description (See Note 1.) Length Number
3022 9760 50 micron, multimode with SC 31 meters 2860
connectors
connectors
3023 9760 50 micron, multimode with SC 31 meters 2860
connectors
connectors
3024 9751 9 micron, singlemode with SC and LC 31 meters 2851
connectors
9752 9 micron, singlemode with LC 31 meters 2852
connectors
9753 9 micron, singlemode with LC connector 2 meters 2853
and SC receptacle (See Note 2.)
connectors
9762 50 micron, multimode with LC 31 meters 2862
connectors
9763 50 micron, multimode with LC connector 2 meters 2863
3025 9761 50 micron, multimode with SC and LC 31 meters 2861
connectors
9762 50 micron, multimode with LC 31 meters 2862
connectors
9763 50 micron, multimode with LC connector 2 meters 2863
Notes:
1. SC designates “standard connector” and LC designates “Lucent connector”.
2. Features #9753 and #9763 provide a conversion cable to enable the attachment of
existing cables with SC connectors to the host adapter features #3024 and #3025.
Operator-panel language feature code

The operator-panel language feature code determines the language for operator
panel labeling. If you do not specify a language, the default is English.
2924 English
2928 French
2929 German
2930 Japanese
2931 Spanish
2932 Italian
2935 Canadian French

2938 Brazilian Portuguese
2942 Belgian Dutch
2962 Chinese Traditional
2969 Korean
2980 UK English
Logical configuration changes

IBM performs the initial logical configuration during ESS installation. After IBM
installs the ESS, you can modify the logical configuration by using the ESS
Specialist Web interface. The Web interface includes help panels that assist you
with changing the logical configuration. Also see the IBM TotalStorage Enterprise
Storage Server: Web Interface User’s Guide for detailed information about the
interface and the logical configuration.
Note: You can contact IBM Service and request to have an IBM SSR modify the
configuration for a fee.
Optional one-year warranty

The ESS comes with a three-year warranty. IBM also offers an optional one-year
warranty. See your IBM field office for details.
Advanced functions
This section provides feature codes for the following optional ESS advanced
functions. See Chapter 2, “ESS advanced functions,” on page 31 for descriptions
and planning information about these functions:
v Parallel access volume (PAV) feature codes
v Extended Remote Copy (XRC) feature codes
v Peer-to-Peer Remote Copy (PPRC) and PPRC Version 2 feature codes
v FlashCopy and FlashCopy Version 2 feature codes
Table 25 lists the ESS model support, feature code ranges, and LIC requirements
for each advanced function.
| Table 25. Advanced function model support and LIC requirements
| ESS Advanced Model 800 Model 750 Models F10 and Models E10 and ESS LIC
| Functions Feature Codes Feature Codes F20 Feature E20 Feature Requirements
| Codes Codes
| PAV 80xx 80xx 180x 180x 1.0.0, or later
| XRC 81xx Not supported 181x 181x 1.1.0, or later
| PPRC 82xx 82xx 182x 182x 1.3.0, or later
| PPRC Version 2 85xx 85xx 185x Not supported 2.2.0, or later
| FlashCopy 83xx 83xx 183x 183x 1.3.0, or later
| FlashCopy 86xx 86xx 186x Not supported 2.2.0, or later
| Version 2
|
Advanced functions may have additional ESS LIC level requirements in selected
operating system environments. Refer to the ESS Interoperability Matrix Web site

for further information:
http://ssddom02.storage.ibm.com/techsup/webnav.nsf/support/2105
Advanced function feature codes for ESS Model 800

The following ESS advanced functions on the Model 800 are enabled and
authorized based upon the physical capacity of the ESS:
PAV and XRC Enablement and authorization must be equal to or
greater than the physical capacity within the ESS
that will be logically configured as Count Key Data
volumes for use with zSeries and S/390 servers.
PPRC and FlashCopy (including Version 2)
Enablement and authorization must be equal to or
greater than the total physical capacity of the ESS.
| Physical capacity is calculated by multiplying each disk eight-pack feature by its

| physical capacity (column 2 in Table 11 on page 56) and then adding the values.
| v For machines with feature number 9510 (Standby CoD Indicator), Standby CoD
| and Step Ahead disk eight-packs do not need to be included in the capacity
| calculation. Refer to “ESS on demand features” on page 20 for additional
| information.
| v For machines that do not have feature number 9510 (Standby CoD Indicator), all
| disk eight-packs, including Standby CoD and Step Ahead disk eight-packs, must
| be included in the capacity calculation.
The initial enablement of an ESS advanced function is a concurrent activity

(assuming the appropriate level of microcode is installed on the machine for the
given function). The removal of an ESS advanced function to deactivate the
function is a disruptive activity and requires a machine IML.
Table 26 lists the feature codes for advanced functions of the Model 800.
Table 26. Feature codes for advanced functions on the Model 800
Maximum Feature Codes
Physical
PAV XRC PPRC PPRC FlashCopy FlashCopy
Capacity
Version 2 Version 2
1 TB 8000 8100 8200 8500 8300 8600
2 TB 8001 8101 8201 8501 8301 8601
3 TB 8002 8102 8202 8502 8302 8602
4 TB 8003 8103 8203 8503 8303 8603
5 TB 8004 8104 8204 8504 8304 8604
6 TB 8005 8105 8205 8505 8305 8605
8 TB 8006 8106 8206 8506 8306 8606
10 TB 8007 8107 8207 8507 8307 8607
12 TB 8008 8108 8208 8508 8308 8608
16 TB 8009 8109 8209 8509 8209 8609
20 TB 8010 8110 8210 8510 8310 8610
25 TB 8011 8111 8211 8511 8311 8611
30 TB 8012 8112 8212 8512 8312 8612
40 TB 8013 8113 8213 8513 8313 8613

Table 26. Feature codes for advanced functions on the Model 800 (continued)
Physical
PAV XRC PPRC PPRC FlashCopy FlashCopy
Capacity
Version 2 Version 2
50 TB 8014 8114 8214 8514 8314 8614
60 TB 8015 8115 8215 8515 8315 8615
0 TB 8099 8199 8299 8599 8399 8699
(inactive)
Note: Model 800 requires 16 GB of cache to support XRC.
Advanced functions require the selection of ESS Model 800 feature numbers and
the order of the matching IBM 2240 ESS Function Authorization feature numbers:
v The ESS Model 800 feature number enables a given function on the ESS at a
given capacity level.
v The ESS Function Authorization feature number authorizes use of the given
advanced function at the given capacity level on the ESS machine for which it
was purchased.
The ESS Model 800 #8xxx feature numbers and the ESS Function Authorization
#8xxx feature numbers are corequisites and must always correspond to one
another.
Table 27 lists the corequisite feature codes for Model 800 advanced functions.
Table 27. Corequisite feature codes for Model 800 advanced functions
ESS Advanced Functions Model 800 Features ESS Function Authorization
Features
PAV 2105-800 feature 80xx 2240-PAV feature 80xx
XRC 2105-800 feature 81xx 2240-XRC feature 81xx
PPRC 2105-800 feature 82xx 2240-PRC feature 82xx
PPRC Version 2 2105-800 feature 85xx 2240-PRC feature 85xx
FlashCopy 2105-800 feature 83xx 2240-FLC feature 83xx
FlashCopy Version 2 2105-800 feature 86xx 2240-FLC feature 86xx
| Advanced function feature codes for ESS Model 750

| The following ESS advanced functions on the Model 750 are enabled and
| authorized based upon the physical capacity of the ESS:
| PAV Enablement and authorization must be equal to or
| greater than the physical capacity within the ESS
| that will be logically configured as count key data
| volumes for use with zSeries and S/390 servers.
| PPRC and FlashCopy (including Version 2)
| Enablement and authorization must be equal to or
| greater than the total physical capacity of the ESS.
| Physical capacity is calculated by multiplying each disk eight-pack feature by its

| physical capacity (column 2 in Table 11 on page 56) and then adding the values.

| v For machines with feature number 9510 (Standby CoD Indicator), Standby CoD
| and Step Ahead disk eight-packs do not need to be included in the capacity
| calculation. Refer to “ESS on demand features” on page 20 for additional
| information.
| v For machines that do not have feature number 9510 (Standby CoD Indicator), all
| disk eight-packs, including Standby CoD and Step Ahead disk eight-packs, must
| be included in the capacity calculation.
| Attention: The initial enablement of an ESS advanced function is a concurrent

| activity (assuming the appropriate level of microcode is installed on the machine for
| the given function). The removal of an ESS advanced function to deactivate the
| function is a disruptive activity and requires a machine IML.
| Table 28 lists the feature codes for advanced functions of the Model 750.
| Table 28. Feature codes for advanced functions on the Model 750
| Maximum Feature Codes
| Physical
| PAV PPRC PPRC FlashCopy FlashCopy
| Capacity
| Version 2 Version 2
| 1 TB 8000 8200 8500 8300 8600
| 2 TB 8001 8201 8501 8301 8601
| 3 TB 8002 8202 8502 8302 8602
| 4 TB 8003 8203 8503 8303 8603
| 5 TB 8004 8204 8504 8304 8604
| 0 TB 8099 8299 8599 8399 8699
| (inactive)
|
| Advanced functions require the selection of ESS Model 750 feature numbers and
| the order of the matching IBM 2240 ESS Function Authorization feature numbers:
| v The ESS Model 750 feature number enables a given function on the ESS at a
| given capacity level.
| v The ESS Function Authorization feature number authorizes use of the given
| advanced function at the given capacity level on the ESS machine for which it
| was purchased.
| The ESS Model 750 #8xxx feature numbers and the ESS Function Authorization
| #8xxx feature numbers are corequisites and must always correspond to one
| another.
| Table 29 lists the corequisite feature codes for Model 750 advanced functions.
| Table 29. Corequisite feature codes for Model 750 advanced functions
| ESS Advanced Functions Model 750 Features ESS Function Authorization
| Features
| PAV 2105-750 feature 80xx 2240-PAV feature 80xx
| PPRC 2105-750 feature 82xx 2240-PRC feature 82xx
| PPRC Version 2 2105-750 feature 85xx 2240-PRC feature 85xx
| FlashCopy 2105-750 feature 83xx 2240-FLC feature 83xx
| FlashCopy Version 2 2105-750 feature 86xx 2240-FLC feature 86xx
|

| Advanced function feature codes for ESS Models F20, F10, E20, and
E10
ESS advanced functions on the Models F20, F10, E20, and E10 are enabled based
upon the RAID-5 capacity of the ESS:
PAV and XRC The license purchased must be equal to or greater
than the RAID-5 capacity within the ESS that will be
logically configured as Count Key Data (CKD)
volumes for use with zSeries and S/390 servers.
PPRC and FlashCopy (including Version 2)
The license purchased must be equal to or greater
than the total RAID-5 capacity of the ESS.
Note: Version 2 does not support Models E20 and

E10.
| RAID-5 effective capacity is calculated by multiplying each disk eight-pack feature

| by its 6 + P array capacity (column 6 in Table 17 on page 66) and then adding the
| values. All disk eight-packs, including Standby CoD (except with FC 9510) and Step
| Ahead disk eight-packs, must be included in the capacity calculation.
The initial enablement of an ESS advanced function is a concurrent activity

(assuming the appropriate level of microcode is installed on the machine for the
given function). The removal of an ESS advanced function to deactivate the
function is a disruptive activity and requires a machine IML.
Table 30 lists the feature codes for advanced functions on the Models F20, F10,
E20, and E10.
Table 30. Feature codes for advanced functions on the Models F20, F10, E20, and E10
RAID-5
PAV XRC PPRC PPRC Version 2 FlashCopy FlashCopy
Effective
(See Note) Version 2 (See
Capacity
Note)
0.5 TB 1800 1810 1820 1850 1830 1860
1 TB 1801 1811 1821 1851 1831 1861
2 TB 1802 1812 1822 1852 1832 1862
4 TB 1803 1813 1823 1853 1833 1863
8 TB 1804 1814 1824 1854 1834 1864
12 TB 1805 1815 1825 1855 1835 1865
16 TB 1806 1816 1826 1856 1836 1866
20 TB 1807 1817 1827 1857 1837 1867
25 TB 1808 1818 1828 1858 1838 1868
Note: Version 2 feature codes are for Models F20 and F10 only. Version 2 does not support Models E20 and E10.

Chapter 4. Installation planning
This chapter provides the following information about planning the installation of
your ESS:
v Equipment requirements
v Site planning
v Power requirements
v Operating environment
v Energy savings
v Power connection requirements
Equipment requirements
This section lists the equipment that IBM ships with the IBM Enterprise Storage
Server that is for you or for authorized service personnel. It also lists equipment that
you need to provide at your ESS site.
Equipment that IBM ships with the ESS for you

Your equipment includes:
v Two ESS cover keys. If you open the ESS, 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 ESCON, SCSI, and fibre-channel host adapters and cables for the ESS. See
“Host adapters” on page 66.
v A CD for the host adapters.
v A CD that includes:
– Installation scripts for the 2105 (ESS) host attachment for AIX and HP-UX
– Software for the CLI
– Installation instructions for the IBM Subsystem Device Driver
– Software for the Subsystem Device Driver
v ESSNet facility equipment:
– ESS Master Console
Note: IBM installs the ESS Master Console when they install your ESS.
- Personal computer (PC)
- Monitor
- Keyboard
- Power cables (country or region specific)
- MSA connection cable
- PC Doctor IBM Diagnostics diskette
– Modem (country or region specific)
– Two RS-232 null modem cables, each 17 m (50 ft) in length
– ESS Master Console-to-modem RS-232 cable
– Ethernet hub

– Three Ethernet cables, each 17 m (50 ft) in length
– Product recovery CD for the ESS Master Console
– Two diskettes for the Linux operating system for the ESS Master Console
– A CD with the ESS Master Console LIC
v IBM Agreement for Licensed Internal Code
v Warranty forms:
– Important Warranty Information, Z125-4753
– Statement of Limited Warranty, GA22-1048
– Machine Specific Warranty Information, GA22-1050
v Customer documents CD, SK2T-8803
This CD includes a softcopy of the ESS customer publications. See “ESS library”
on page xiii for a list of the books.
Equipment for authorized service personnel

Additional items that are shipped with the ESS for use by authorized service
personnel, include:
v Licensed internal code (LIC) CD.
Note: IBM service enables or disables any LIC features on your ESS.
v The extension cord that connects the service terminal to a power outlet. See
“Extension cords” on page 50.
Note: An extension cord is not included for the Model 800.

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
1.44-MB drive has formatted.
v Service documents CD, SK2T-8800
This CD includes a softcopy of the ESS service guides, ESS parts catalog, and
the ESS customer publications.
v Hardcopies of the ESS service guides.
v Two CDs for the operating system.
v A CD for the operating system for program temporary fixes (PTFs).
v A CD for the operating system for service diagnostics.
Equipment that you provide

You also need the following equipment for installing and operating the ESS:
v An analog telephone line near the ESS to enable remote support.
v Power cable connectors. The ESS requires two power cables that are country
dependent and location dependent. You need the correct connectors as identified
in “Power connection requirements” on page 92 and “Power connectors” on page
92.

v The following components require a power outlet:
– ESS Master Console
– ESS Master Console monitor
– Hub
– Modem
v You also need a power outlet within 6 feet of the service console.
Outlets must be within 6 feet of the ESSNet or ESS Master Console. The ESSNet
or ESS MC must be within 50 feet of the ESS (all models). See “Power features” on
page 46 for details about power requirements for these components.
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 changes. You should install the mandatory changes as
directed by IBM.
Notes:
1. The CD 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 planning
Table 31 on page 82 gives the dimensions and weights of the ESS models.
IBM ships all ESS models on a pallet with a corrugated fiberboard (cardboard)
cover. The weight of this packaging is approximately 114 kg (250 lbs). The carrier is
responsible for delivering and unloading the ESS as close to its final destination as
possible.
To compensate for the weight of the ESS, the loading ramp at your site should not
exceed an angle of 10°.
Note: You can order a weight-reduced shipment of the ESS when a configured
ESS exceeds the weight capability of the elevators or the loading ramp at
your site. See “Shipping options for ESS Model 800” on page 46 for more
information.
CAUTION:
A fully configured unit in the packaging can weigh up to 1500 kg (3305 lbs).
Use of less than three persons to move it can result in injury.
Chapter 4. Installation planning 81

| Table 31. ESS dimensions and weights
| Unit Dimensions, Dimensions with Maximum Weight Maximum Weight
| Centimeters (Inches) Packaging, (Fully with Packaging
| (See Note 1.) Centimeters Configured)
| (Inches)
| ESS Model 800 (See Notes 1204 kg (2650 lbs) 1318 kg (2900 lbs)
|| 3 and 4.)
Height 179.6 (70.7) Height 200 (78)
| (See Note 2.) (See Note
| 2.)
| Width 138.3 (54.4)
| Width 157.3
| Depth 91 (35.8)
| (62.00)
| Depth 106.7
| (42.00)
| ESS Models E10 and F10 1000 kg (2200 lbs) 1114 kg (2450 lbs)
|| (See Note 3.)
Height 179.6 (70.7) Height 200 (78)
| 2.)
| Width 138.3 (54.4)
| Width 157.3
| Depth 91 (35.8)
| (62.00)
| Depth 106.7
| (42.00)
| ESS Model 750 1059 kg (2330 lbs) 1173 kg (2580 lbs)
| Height 179.6 (70.7) Height 200 (78)
| 2.)
| Width 138.3 (54.4)
| Width 157.3
| Depth 91 (35.8)
| (62.00)
| Depth 106.7
| (42.00)
| ESS Models E20 and F20 1204 kg (2650 lbs) 1318 kg (2900 lbs)
|| (See Note 4.)
Height 179.6 (70.7) Height 200 (78)
| 2.)
| Width 138.3 (54.4)
| Width 157.3
| Depth 91 (35.8)
| (62.00)
| Depth 106.7
| (42.00)
| ESS Models E20, F20, or 2545 kg (5600 lbs) (See Note 4.)
|| 800 with the ESS expansion
Height 179.6 (70.7) Height 207.5
| enclosure (See Note 3.)
(81.69)
| Width 293.8 (115.7)
| Width 312.8
|| Depth 91 (35.8)
(123.30)
| Depth 106.7
| (42.00)
| IBM Model 100 expansion 770 kg (1696 lbs) 884 kg (1946 lbs)
|| enclosure (See Note 5.)
Height 178.0 (70) Height 204.5 (80.5)
| Width 84 (33) Width 101.6 (40)
| Depth 130.5 (51) Depth 149.9 (59)

| Table 31. ESS dimensions and weights (continued)
| Unit Dimensions, Dimensions with Maximum Weight Maximum Weight
| Centimeters (Inches) Packaging, (Fully with Packaging
| (See Note 1.) Centimeters Configured)
| (Inches)
| 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 191.5 cm (75.3-in.).
| 3. Models E10, F10, 750, and 800 do not support the Model 100 expansion enclosure.
| 4. Models E20, F20, 800, and the expansion enclosure are shipped separately.
| 5. Install the expansion enclosure to the right (as you face its front) of the Model 800.
| 6. Install the Model 100 expansion enclosure to the right (as you face its front) of Models E20 and F20.
|
You can install the ESS on a non-raised floor. However, installing the ESS on a
raised floor provides increased air circulation for better cooling. With a raised floor,
you can also cut out tiles for cable entry at the front.
Center all openings and cutouts at the front of the enclosures. Table 32 provides the
dimensions for the cutouts. Figure 7 on page 84 and Figure 8 on page 85 provides
the cutout locations and the clearances that are required for the doors. The ESS
has recessed casters that do not require extra clearance.
| Table 32. Cable cutout dimensions (maximum size)
| Unit Floor Cutout Floor Cutout Key Reference
| Description Measurements
|| ESS Models E10, Input/output 10 x 30.4 cm (4 x 12 4 in Figure 7 on
|| F10, E20, F20, 750, (I/O) cutout in) page 84
| and 800 base
| enclosure
|| ESS Models E10, Power cable 7.6 x 24.1 cm (3 x 9.5 3 in Figure 7 on
|| F10, E20, F20, 750, cutout in) page 84
| and 800 base
| enclosure
|| Expansion enclosure Power cable Front: 15 x 15 cm (6 x 3 in Figure 8 on
|| cutout 6 in) page 85
| Rear: 15 x 15 cm (6 x
| 6 in)
|
Cover removal for narrow doorways

If the doorway is too narrow (see Figure 7 on page 84), have an IBM Customer
Engineer (CE) assist in removing the appropriate covers. Perform the following
steps to remove the front and rear covers:
1. Lift and remove the hinge pins from the top and bottom hinges of the covers.
2. Remove the cover.
3. Verify that the ESS model can fit through the doorway. If not, remove the
screws and hinges.

9.03
(3-9/16)
5
138.4 8.03
(54-1/2) (3-1/8)
129.5
(51)
114.3 2
(45)
68.9 71.1
(27-1/8) (28)
74.9 90.8
(29-1/2) (35-3/4)
4 4
3
19.9 30.4 24.1 30.4 19.9

(7-7/8) (12) (9-1/2) (12) (7-7/8)
56.5
(22-1/4)
83.4
86.3 (32-7/8)
(34)
1
S008303R
Legend:
1 is the front of the enclosure.
2 is the rear of the enclosure.
3 is the cutout for the power cables.
4 is the I/O cutout for the ESCON, fibre-channel, and SCSI cables (Models
E10, F10, E20, F20, 750, and 800 base enclosures only).
5 are the dimensions for the casters (Models E10, F10, E20, F20, 750, and
800 base enclosures and the Model 100 expansion enclosure).
Figure 7. Cable cutout and door clearance for Models E10, F10, E20, F20, 750, and 800.
Dimensions are in centimeters (inches).

2
76.6
(30-1/8)
2.5
(1) 30 15
(11-7/8) (6)
15 3
(6)
107
(42-1/8)
102
(40-1/8) 128.6
(50-5/8)
76.6
(30-1/8)
75
(29-1/2)
84 S009111
(33)
Legend:
1 is the front of the enclosure.
2 is the rear of the enclosure.
3 is the cutout for power cables.
Figure 8. Cable cutout and door clearance for the expansion enclosure (Model 100).
Dimensions are in centimeters (inches).
Earthquake preparedness information for Models 750 and 800

| The following information might be useful when you prepare your ESS Models 750
| and 800 to be earthquake safe:

| v Weight of Models 750 and 800: See Table 31 on page 82.
| v Dimensions of Models 750 and 800: See Table 31 on page 82.
| v Center of gravity: Based on rear side orientation, the center of gravity is
| estimated to be approximately 101.6 cm (40 in.) up from the floor.
| v Fundamental natural frequency: The measured vertical resonance frequency is
| 11.81 Hz, on top of a horizontal frame member adjacent to one of the ESS
| casters.
| v Dimensions between casters, with the casters rotated so the casters are as close
| together as possible:
| – Width (front or rear view) is 104 cm (41 in.), inside to inside of the caster
| wheels
| – Depth (left or right side view) is 46.4 cm (18.25 in.), inside to inside of the
| caster wheels
| v ESS caster locations and cable openings: See Figure 7 on page 84.
| v ESS frame: The ESS frame has four threaded holes on the underside (see
| Figure 9). IBM uses the holes to fasten the ESS to a pallet during shipment from
| the assembly factory to the installation site. You might use these holes to fasten
| the ESS to the floor for earthquake safety. However, IBM has not performed any
| earthquake testing that uses these holes to fasten an ESS to the floor. Before
| you use these holes for earthquake stability, contact a registered structural
| engineer or earthquake consultant to review such use.
1 2 1
1 1
S009584
Legend:
1 is a threaded hole.
2 is the front of the ESS.
Figure 9. Underside of an ESS with the location of the threaded holes

Cooling the ESS
The ESS provides the following air circulation for cooling:
v Fans in the lower part of the ESS take air in through the front covers and
exhaust the air through the rear covers.
v Fans in the upper part of the ESS, where the DDMs are located, take air in
through the front and rear covers. The fans exhaust the air through the top of the
ESS.
v Fans in the DDM section of the expansion enclosure also take air in through the
front and rear covers. The fans exhaust the air through the top of the ESS.
Install the ESS on a raised floor to provide increased air circulation for better
cooling. Installing perforated tiles can also assist in cooling the ESS and
maintaining the environmental conditions given in “Operating environment” on page
91.
v Install two fully perforated tiles in front of each ESS. An additional partially
perforated tile at the back might improve ESS cooling in some installations.
v Install one fully perforated tile in front of an expansion enclosure and one at the
back.
Fire-suppression system information

A fire suppression system for the ESS is the responsibility of the customer. Consult
your insurance underwriter, local fire marshall, or local building inspector about
selecting a fire-suppression system that provides the proper level of coverage and
protection.
IBM designs and manufactures equipment to internal and external standards that
require certain environments for reliable operation. Because IBM does not test any
equipment for compatibility with fire-suppression systems, IBM does not make
compatibility claims of any kind. IBM does not provide recommendations on
fire-suppression systems.
See “Operating environment” on page 91 for the environmental requirements for an

ESS.
Service-clearance and floor-load requirements

Table 33 shows the clearances that the ESS requires for service and the
requirements for floor-loading strength. This table also gives the side clearances
that are required for both sides of the installation.
| Table 33. Clearance and floor-loading requirements
| Configuration and Service Clearance (See Floor Loading, kg Dedicated Weight Distribution Areas
| Weight Note 3.) per m² (lbs per ft²) (See Notes 1, 2, 4, and 6.)
| (See Notes 1 and 4.)
| Front cm Rear cm Sides Front cm Rear cm
| (in.) (in.) cm (in.) (in.) (in.)
| (See Note
| 3.)
| Models E10 and F10, 86.4 (34) 114.5 (45) 610 (125) 0 (0) 35.6 (14) 35.6 (14)
| weight 1000 kg (2200
| 488 (100) 7.6 (3) 43.2 (17) 57.2 (22.5)
| lbs) (See Note 2.)
| 439 (90) 18.4 (7.25) 43.2 (17) 57.2 (22.5)
| 342 (70) 55.9 (22) 43.2 (17) 57.2 (22.5)

| Table 33. Clearance and floor-loading requirements (continued)
| Configuration and Service Clearance (See Floor Loading, kg Dedicated Weight Distribution Areas
| Weight Note 3.) per m² (lbs per ft²) (See Notes 1, 2, 4, and 6.)
| (See Notes 1 and 4.)
| Front cm Rear cm Sides Front cm Rear cm
| (in.) (in.) cm (in.) (in.) (in.)
| (See Note
| 3.)
| Models E20, F20, or 86.4 (34) 114.5 (45) 610 (125) 1.5 (.6) 43.2 (17) 57.2 (22.5)
| 800 maximum weight
| 488 (100) 22.9 (9) 43.2 (17) 57.2 (22.5)
| 1204 kg (2650 lbs)
| (See Note 2.) 439 (90) 36.8 (14.5) 43.2 (17) 57.2 (22.5)
| 342 (70) 76.2 (30) 48.3 (19.) 61 (24)
| Models E20, F20, 750, 86.4 (34) 114.5 (45) 610 (125) 0 (0) 38.1 (15) 57.2 (22.5)
| or 800 with expansion
|| enclosure, maximum 488 (100) 41.3 (16.25) 43.2 (17) 57.2 (22.5)
|| weight 2545 kg (5600 439 (90) 71.1 (28 ) 43.2 (17 ) 57.2 (22.5)
| lbs) (See Notes 2, 4,
| and 5.) 361 (74) 76.2 (30) 76.2 (30) 76.2 (30)
| Model 100, weight 770 114.5 (45) 81.3 (32) 610 (125) 0 (0) 55.9 (22) 31.8 (12.5)
| kg (1696 lbs) (See
| 488 (100) 10.2 (4) 57.2 (22.5) 40.6 (16)
| Notes 2, 4, 5, 6, 7, and
| 8.) 439 (90) 17.8 (7) 57.2 (22.5) 40.6 (16)
| 361 (74) 42.5 (16.75) 57.2 (22.5) 40.6 (16)
| Two Model 100s, 114.5 (45) 81.3 (32) 610 (125) 0 (0) 56.2 (22.5) 40 (16.0)
| combined weight 1542
| 488 (100) 17.8 (7) 57.2 (22.5) 40.6 (16)
| kg (3400 lbs) (See
| Notes 2, 6, 7, and 8.) 439 (90) 33.0 (13) 57.2 (22.5) 40.6 (16)
| 342 (70) 76.2 (30) 63.5 (25) 40.6 (16)
| Notes:
| 1. Install the ESS on a floor with a minimum of 342 kg per m² (70 lbs per ft²) strength.
| 2. Floor loads are calculated for maximum weight of the ESS.
| 3. Clearances on both sides are dedicated to the ESS. A clearance of 10.2 cm (4 in.) on each side of the ESS is
| required to open the covers to 90 degrees. Adjacent expansion enclosures must have their own floor-loading
| clearance.
| 4. If you install a Model E20, F20, or 800 with an expansion enclosure, the floor strength must be at least 361 kg
| per m² (74 lbs per ft²). At 342 kg per m² (70 lbs per ft²), the side clearance exceeds the 76.2-cm (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 28-cm (11-in.) spacers. Move the side cover from the ESS
| to the side of the expansion enclosure. Side clearances are for both sides of an expansion enclosure.
| 6. Place Model 100s to the right of Models E20 and F20. Determine the distance between the frames by the
| floor-loading requirements of each model. When you have two Model 100s, the frames are bolted together with a
| 4-cm (1.6-in.) spacer between them.
| 7. A Model 100 expansion enclosure can have a maximum of six drawers.
| 8. ESS Models 750 and 800 do not support the Model 100 expansion enclosure.
|

Planning for installation of the ESS Master Console
IBM installs the ESS Master Console (feature code 2717) when they install your
ESS.
IBM provides the power cables for the ESS Master Console. You provide:
v A location for the ESSNet hub that is within 15.3 m (50 ft) of the ESS
v A location for the ESS Master Console that is within 15.3 m (50 ft) of the hub
v A location for the ESS Master Console that is within 15.3 m (50 ft) of the ESS
v Three outlets that are within 1.8 m (6 ft) of the ESS Master Console (for the ESS
Master Console PC, monitor, and modem)
v One outlet that is within 1.8 m (6 ft) of the hub
Note: The length of the various cables that interconnect the components dictates
the distance of 15 m (50 ft) between components.
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 ESS Master Console are installed and in
operation.
If you order additional ESS machines with feature 2716, the additional machines
must be within 15.3 m (50 ft) of the ESS Master Console or the remote support
facility (feature 2715).
You are responsible for firewall protection for the ESSNet.
You also need to provide a table or a stand for the ESS Master Console at your
site.
The ESS Master Console is a personal computer (PC) and a monitor. The weight
and dimensions for the PC are:
PC weight 11 kg (25 lbs)
PC height 12.8 cm (5 in.)
PC width 44 cm (17.7 in.)
PC depth 44 cm (17.7 in.)
The approximate weight and dimensions for the monitor are:

Monitor weight 18 kg (38 lbs)
Monitor height 43.2 cm (17 in.)
Monitor width 40.6 cm (16 in.)
Monitor depth 43.2 cm (17 in.)
The monitor has a 7.5 cm (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 environmental information for the ESS.
Input voltage requirements

See Table 34 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 connectors” on page 92. Also see “Power
features” on page 46 for information about power features.
Note: The main front-end power supplies for the ESS come in two versions with
different voltage ratings. The minimum and maximum voltage ranges are
dependent on the power feature code that you ordered. You should use the
actual voltage range from the power ratings plate or from the rating of the
main front-end power supply on your ESS. For the 200 - 240 V supply, the
range is 180 - 256 V. For the 380 - 480 V supply, the range is 315 - 512 V.
Table 34. ESS input voltages and frequencies
Characteristic Value
Nominal input voltages 200, 208, 220, 240, 380, 400, 415,
or 480 RMS V ac
Minimum input voltage 180 RMS V ac
Maximum input voltage 512 RMS V ac
Steady-state input frequencies 50 ± 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 35 on page 91 gives power consumption and environmental information for
the ESS. Also see “Cooling the ESS” on page 87 for information about ESS air
circulation and exhaust.

| Table 35. Power consumption and environmental information for the ESS
| Measurement Units Models E10 or Models E20, Models E20,
| F10 F20, 750, or 800 F20, or 800 with
| an Expansion
| Enclosure
| Electric power kilovolt amperes 5.0 (See Note 6.4 (See Note 13.8 (See Note
| 1.) 2.) 2.)
| Thermal load British thermal 17 000 22 000 47 000
| units (BTU) per
| hour
| Capacity of cubic meters per 44.2 (1500) 51.8 (1800) 103.6 (3600)
| exhaust minute (cubic
| feet per minute
| [CFM])
| Single-phase milliamperes 17 17 17
| and three-phase
| leakage current
| Startup current amperes ≤ 100 ≤ 100 ≤ 100
| Startup current microseconds < 200 < 200 < 200
| duration
| Idle and bels 7.5 7.5 Not available
| operating-sound
| power
| Idle and decibels 59 59 Not available
| operating-sound
| pressure
| Notes:
| 1. This measurement is for a single-phase ESS with sixty-four 72-GB DDMs and
| fibre-channel adapters.
| 2. This measurement is for a three-phase ESS with one-hundred-twenty-eight 145-GB
| DDMs and fibre-channel adapters. With the expansion enclosure, the measurement is
| for two-hundred-fifty-six 145-GB DDMs.
|
Operating environment
The following sections list the environmental operating points and ranges for the
ESS. You need to maintain the conditions listed for all the ESS air intake areas
described in “Cooling the ESS” on page 87.
With the power on

Table 36 gives the operating extremes for an ESS with the power on.
Table 36. Operating extremes with the power on
Altitude 0 - 2133 m (7000 ft)
Dry bulb temperature 16 - 32°C (60 - 90°F)
Relative humidity 20 - 80%
Wet bulb temperature (maximum) 23°C (73°F)
Table 37 on page 92 gives the operating points that IBM recommends for an ESS
with the power on.

Table 37. Recommended operating points with the power on
Temperature 22°C (72°F)
Relative humidity 45%
Table 38 gives the operating ranges that IBM recommends for an ESS with the
power on.
Table 38. Recommended operating ranges with the power on
Temperature 20 - 25°C (68 - 77°F)
With the power off

Table 39 gives the temperatures and humidity for an ESS with the power off.
Table 39. Temperatures and humidity with the power off
Temperature 10 - 43°C (50 - 110°F)
In storage
Table 40 gives the temperatures and humidity for storing an ESS.
Table 40. ESS temperatures and humidity while in storage
Temperature 1 - 60°C (34 - 140°F)
Energy savings
The energy savings for all ESS models is:
0.001 W per MB for MB > 160, Category G.
Power consumption in energy savings mode is not applicable.
Power connection requirements

This section describes ESS power connector requirements and power outlet
requirements. See “Power cables” on page 48 for the power-cable feature codes.
See Table 4 on page 48 for the input voltage feature codes and power cables for
the United States (U.S.), Canada, Asia Pacific (AP), and Latin America (LA). See
Table 5 on page 48 for the input voltage feature codes and power cables for
Europe, the Middle East, and Africa.
Power connectors
Table 41 on page 93 shows the power cables, inline 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.
Table 41. ESS power cable connectors
Power Cable Feature Code Power Connector Description Inline Connector Receptacle
(See Notes 1 and 3.) (See Note 2.) (See Note 2.)
9801, 9986 (See Notes 4, Single phase, 50 or 60 Hz 50 9C53U0 (See Note 8.) 9R53U0W
10, and 12.) amperes (A)
9802 (See Notes 4, 5, 10, Single phase, 50 Hz No connector Hard wire
and 12.)
9803 (See Notes 4, 6, 10, Single phase, 50 or 60 Hz, 60 (A) Not used 360R6W
and 12.)
9851, 9987 (See Notes 9, Three phase, 50 or 60 Hz, 50 (A) 9C54U0 (See Note 8.) 9R54U0W
10, 11, and 13.)
9988, 9854 (See Notes 9, Three phase, 50 or 60 Hz, 60 (A) 7428-78 (See Note 7.) 7324-78
10, 11, and 13..)
9855, 9989 (See Note 9.) Three phase, 50 or 60 Hz, 30 (A) 430C9V04 (See Note 430R9V0 (See Note 14.)
14.)
9852 (See Notes 5, 9, 11, Three phase, 50 Hz No connector Hard wire
and 13.)
9853 (See Notes 6, 9, 11, Three phase, 50 or 60 Hz, 60 (A) Not used 460R9W
and 13.)
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 types and receptacle types are Russellstoll except types for Japan, which can use any manufacturer.
3. All power cables are 4.7 m (14 ft) long except Chicago, which is 2 m (6 ft) long.
| 4. This cable is not available on ESS Models E20, F20, 750, 800, or the expansion enclosure.
5. Power cables for Models E10, E20, F10, and F20 might have had a bulk wire gauge of 2.5 mm². The power
cable for this feature is now a bulk wire gauge of 10 mm².
6. Install the 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 inline connector must have the appropriate JPA adapter included in the assembly. This ensures
continuity between the connector housing and the metallic shielding of the liquid-tight conduit.
8. Attach these inline connectors to a liquid-tight, metallic-shielded conduit, using either adapter C75 for 1.89-cm
(3/4-in.) conduit or adapter C10 for 2.54-cm (1-in.) conduit.
9. This cable is not available on ESS Models E10 and F10.
10. Low-voltage, single-phase installations (200 - 240 V) require rated circuit breakers of 40 A. You should not
exceed the wire rating of the facility.
11. Low-voltage, three-phase installations (200 - 240 V) require rated circuit breakers of 30 A. You should not
12. High-voltage, single-phase installations (380 - 415 V) require rated circuit breakers of 20 A. You should not
13. High-voltage, three-phase installations (380 - 415 V) require rated circuit breakers of 20 A. You should not
14. Connector types and receptacle types are Hubbell for Japan.
| Amperage ratings of the power-cable connector for the expansion enclosure must
| match the ratings used in the ESS Model E20, F20, 750, or 800. For example, if
| your ESS model has a 60-A connector, your expansion enclosure should also have
| a 60-A connector.

Remote service connection
You need to connect each ESS to an ESS Master Console and a modem for
remote support. The modem connection allows service personnel to perform service
remotely. See “Remote support features” on page 51 for information on remote
support requirements.
Locate and provide power to the remote support modem connected to the ESS
Master Console. The serial cable from the ESS Master Console to the modem is 2
m (6 ft) long. You supply the cable to connect the modem to a telephone jack.
The modems that IBM offers are for worldwide use, and they meet all required
standards.
Remote service outlet power

You supply an appropriate receptacle for each modem. 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.
If your ESS has the remote power control feature, the Local/Remote switch settings
on the control panel affect the ability of the ESS to automatically power up if power
is lost to both power cords. See the IBM TotalStorage Enterprise Storage Server:
User’s Guide for additional information about ESS switch settings.
Remote service telephone lines

You need one or more analog telephone lines to support remote service. Determine
the number of telephone lines that you need by the number of ESSs that you are
installing. You also provide the telephone cable that connects the modem to the
telephone-line jack. An expander supports one telephone line.
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.
| Note: Because Models 750 and 800 must be within 2 m (6 ft) of the power outlet, it
| does not require an extension cord.
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.

Chapter 5. Planning ESS communications
This chapter provides the following information to help you plan communications for
your ESS:
v Overview of communications
v Guidelines for completing the Communication Resources work sheet
v Guidelines for completing the Communication Resources work sheet for the ESS
Master Console
v Guidelines for converting from an ESSNet console to an ESS Master Console
v Guidelines for completing the Communication Resources work sheets for ESS
Copy Services:
– Enable ESS Copy Services work sheet
– Enable ESS Copy Services without DNS work sheet
Overview of communications
During installation IBM establishes communication links:
v Between the ESS and your storage management personnel
v Between the ESS and service personnel
v Between the ESS and your host system
IBM installation personnel use the information from the work sheets to establish
these communication links.
After IBM has installed the ESS, you can change the communication settings from
the Web interface. See the IBM TotalStorage Enterprise Storage Server: Web
Interface User’s Guide for guidelines on using the ESS Specialist to change the
settings.
The ESS supports three levels of access:

Service access
On site access by service personnel who access the ESS through a
physical connection to the ESS serial port
Support access
Remote call-in access to the ESS through a modem
Product Engineering (PE) access
Scheduled remote call-in access to the ESS through a modem for PE
service
The Communication Resources work sheets enable you to define how the various
communication functions within the ESS should be configured. They also enable
you to authorize or deny access to your ESS by service personnel:
v Enable outgoing modem calls
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 enables IBM service personnel or your service provider to remotely
sign on to the ESS in response to the service call.
v Enable remote sign on

You control this remote access. IBM recommends that you enable this service by
checking Yes. Service personnel can sign on to the ESS with the call-back
password.
v Optional remote access password
This password adds further security to the support login ID. Set this password in
agreement between you and service personnel.
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

This section provides instructions for completing the Communication Resources
work sheet. You use this work sheet to enter communication information for the
ESS. If you are attaching the ESS to an ESS Master Console, you also need to fill
in the work sheet for the ESS Master Console configuration. See the guidelines on
page “Guidelines for completing the Communication Resources work sheet for the
ESS Master Console” on page 106.
Use the following guidelines to enter communication information for the ESS in the
work sheet (Appendix A, “Communication Resources work sheet,” on page 121):
1. Time zone configuration and date configuration
a. Daylight savings
Check Yes if this location goes on daylight savings time; check No if it
does not.
b. 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, in
hours, from Coordinated Universal time. Enter this number (including the
plus or minus sign) 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)
2. TCP/IP configuration
The following guidelines are for basic TCP/IP configuration. For advanced
TCP/IP configuration, see the AIX System Management Guide:
Communications and Networks, Version 4, 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 after the ESS and ESS Master Console are
installed and in operation.
a. Local cluster host name
Enter the host name that you are assigning to Cluster 1 for access over
the network. For example, Storage00.
Note: The host name that you define here is also the Web site address for
access to the ESS Specialist.
b. Local cluster Internet address
Enter the dotted decimal address that you are assigning to Cluster 1 of the
ESS. For example, 9.113.152.148.
c. Alternate cluster host name
Enter the host name that you are assigning to Cluster 2 for access over the
network. For example, Storage01.
d. Alternate cluster Internet address
Enter the dotted decimal address that you are assigning to Cluster 2 of the
ESS. For example, 9.113.152.14.
e. Network mask
Enter the dotted decimal network mask that you are applying to TCP/IP on
the ESS. For example, 255.255.254.0.
f. Network interface
Check one of the following network interfaces:
v en0 Standard Ethernet (default)
v et0 Institute of Electrical and Electronics Engineers (IEEE) 802.3
Ethernet
The difference between these two choices is the header format. On the
same local network, all stations must use the same header format.
g. Name server (DNS) Internet address
Enter the dotted decimal address of the name server that this ESS is to
access. For example, 9.113.42.250.
h. Name server domain name
Enter the domain name of the name server. For example, tucson.ibm.com.
i. Default gateway address
Enter a dotted decimal or symbolic name as the address of the default
gateway for this ESS. For example, 9.113.155.254 or sanjosegate.
j. Your cable type
Chapter 5. Planning ESS communications 97

Check the cable type that matches the cable for a standard Ethernet
interface or IEEE 802.3 Ethernet interface:
v N/A (default)
v bnc (thin cable)
v dix (thick cable)
v tp
3. ESSNet TCP/IP information
a. ESSNet workstation host name
Enter the host name that you are assigning to the ESSNet workstation for
access over the network. For example, essnetmc.
b. ESSNet workstation domain name
Enter the domain name that you are assigning to the ESSNet workstation.
For example, tucson.ibm.com.
c. ESSNet workstation Internet address
Enter the Internet address that you are assigning to the ESSNet
workstation for access over the network. For example, 254.254.253.0.
d. ESSNet workstation network mask
Enter the dotted decimal network mask that you are assigning to the
ESSNet workstation. For example, 255.255.254.0.
e. Name server (DNS) Internet address 1
Enter the dotted decimal address of the name server that this workstation
is to access. For example, 9.113.42.250.
f. Name server domain name 1
g. Name server (DNS) Internet address 2
Enter the dotted decimal address of the second name server that this
workstation is to access. For example, 9.113.42.252.
Note: The second name server Internet address and name server domain
name are optional. IBM recommends that you enter this information
when you configure a backup or secondary server for ESS Copy
Services.
h. Name server domain name 2
Enter the domain name of the second name server. For example,
tucson2.ibm.com.
gateway for this workstation. For example, 9.113.155.254.
j. Ethernet adapter mode (check one)
Check the mode that matches the mode of the external switch or router to
which you are connecting the Ethernet adapter:
v Half-duplex
v Full-duplex
4. Customer information
Enter information that you feel might be useful to IBM service personnel or
your service provider, such as:
a. Customer business company name or company name

IBM support uses this information; this information should be consistent for
all machines within an account.
b. Machine (ESS) location
Enter the location of the ESS (city, street address, and building).
c. Customer contact telephone number
This is the telephone number where service personnel can contact you.
d. Customer contact name
These are the names of individuals at your site that service personnel can
contact about ESS service matters.
e. Customer contact electronic mail (e-mail) address
IBM strongly recommends that you list at least one e-mail address. This
address will receive information when a PE or a service support person
connect to your machine.
f. Additional account information
IBM service personnel complete this information. This information is
intended to provide additional account or machine information to service
personnel who remotely sign on as a support or IBM PE user. The
information is unformatted with a maximum of 200 characters. An SSR,
support, or PE user can change the information in this field.
g. Customer phone number
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 must be for the individuals that you name for
contacts in step 4d.
h. Callback phone number (local modem)
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. Outside line prefix
This is the number that you use to access an outside line. Enter up to three
numbers in this field. Typical US prefixes would be “9,1”.
5. E-mail configuration
Attention: If you plan to connect your network to the ESSNet, IBM
recommends that you defer e-mail configuration by IBM during initial
installation. 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 - 9) to e-mail addresses and to the
call-home destination. Enter the total number of notifications (default is 1)
that 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. To enable a smart relay host, enter a host name or network address.

Note: You may enable smart relay host, or configure local e-mail, or do
neither. You cannot do both.
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 on your mail server.
Note: If the address you entered in step 5d does not receive e-mail,
configuring the smart relay host might correct the problem.
c. Configure or unconfigure local e-mail
v Configure
Check Configure if you have connected your ESS to a host-system
network that does not have a domain name server (DNS).
v Unconfigure (default)
Check Unconfigure if the host-system network does have a DNS.
d. Add e-mail destinations
The ESS sends error notifications and information to the destinations that
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, or none.
This specifies which notification the recipient receives.
6. SNMP configuration
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: PPRC status reporting for ESS Copy Services requires SNMP for
open-systems hosts.
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). Check
Read Only to allow read access to this information. Check None (default)
to disallow or deny read access to this information.
b. Allow generic traps
The ESS can generate generic SNMP traps. Check Yes to allow the ESS
to send these traps. Check No (default) to not allow the ESS to send these
traps.
c. Allow product-specific traps
The ESS can generate product-specific SNMP traps. Check Yes to allow
the ESS to send these traps. Check No (default) to not allow the ESS to
send these traps.

d. Maximum trap notifications per problem
Enter the total number of trap notifications that you want sent for each trap
condition. To ensure that traps are not lost, you might want to send each
trap notification more than once. The default is four notifications.
e. SNMP community name
| Enter the SNMP community name (up to 31 characters without spaces) 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 the host names or the dotted decimal addresses of the destinations
that are to receive SNMP traps. For example: host.com, or 9.113.152.254.
7. Pager information
This information is optional. The ESS can send problem record information
about the ESS to your pager through the call-home modem. Enter the
following information for each pager user:
a. Maximum pager problem presentation count, enter 1 - 9. Default is 4.
b. Pager user name
Enter your pager user name in alphanumeric characters. This must be a
unique name.
c. Modem telephone number
Enter the modem telephone number of the pager company. The pager
must use telocator alphanumeric protocol (TAP). 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.
d. Pager user PIN or ID number
This is the pager user’s PIN number or ID number that is required by the
pager company. It is usually not null.
e. Carrier pager user password
This is a security password. Check with your pager company; this can be
null.
f. Pager type
Check 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 your voice-telephone number
c is the cluster number (1 or 2)
ddd is the problem ID
Note: The information that the ESS can send to a numeric pager is limited.
g. Pager state
Check enable to enable, or disable to disable.

h. Number of repeats
This is the number of times that the ESS sends problem record information
(0 - 10). The ESS automatically sends information once.
8. Service information messages (SIMs) for S/390 and zSeries hosts
Select the number of times that the ESS sends a SIM to S/390 or zSeries
hosts for entry in the error-recording data set. You also select the severity of
SIMs that are to display a message on the host console. The ESS sends SIMs
to 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.
Severity levels are defined as follows:
Selection Severity reported
acute A major subsystem resource is disabled. Performance may be
severely degraded. System and application outages may have
occurred.
serious An unrecoverable error or a data check with loss of access to
data.
moderate Performance degradation is possible in a heavily loaded
environment. A primary subsystem resource is disabled.
Significant performance degradation is possible.
service No system or application performance degradation is expected
in any environment.
none None
Enter the severity levels for the SIMs and enter the number of times the ESS
should send a SIM:
a. Check the SIM-severity reporting level for DASD SIMs.
The choices are: Service, Moderate, Serious, Acute, or None. The default
is None.
b. Enter the maximum number of times that the ESS is to send a DASD SIM.
0 - 5 (the default is 5)
c. Enter the SIM-severity reporting level for media (data check) SIMs.
is Acute.
d. Enter the maximum number of times that the ESS is to send a media SIM.
e. Enter the SIM-severity reporting level for a storage server SIM.
is Acute.
f. Enter the maximum number of times that the ESS is to send the
storage-server SIM.
9. Problem presentation

Enter 0 - 5 for the maximum overall problem presentation count. The Default is
5. This is the maximum number of times that error detection messages will be
sent by e-mail, SNMP trap, pager, SIM, or call home.
10. Enable ESS Specialist
a. Check either Enable (default) or Disable. IBM service will enable or
disable the 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.
b. Check which cluster to update: Local, Alternate, or Both (default).
11. Modem configuration for the ESSNet
IBM service personnel complete this information. A list of the fields follows for
your information.
Note: Enter this information only for an ESSNet 1 console.

a. Name of modem set
Note: Enter DeskPorte Fast if you have a MultiTech MultiModem.

b. Dialer telephone system
Check tone or pulse.
c. Modem data rate
Check one of the following:
Fastest possible speed (default)
14400 16800 19200 21600
24000 26400 28800
Note: IBM recommends that you select Fastest possible speed.

d. Cancel the call if it does not connect within nn seconds
nn is a number of seconds from 30 - 180. The default is 45 seconds.
e. Number of consecutive retries for connection (default is 1 retry)
f. Name of the modem expander set
g. Modem expander port for the modem (IBM recommends port 16)
h. Modem expander port for Cluster 1
i. Modem expander port for Cluster 2
12. Call home and remote services
Complete all of this information except in the following fields. IBM service
personnel complete these fields:
v Remote telephone numbers (RETAIN®)
v Do not wait for dial tone before dialing
v Heartbeat and Machine-Reported Product Data (MRPD) record destination
v Support catcher telephone number
v Call home trace level
a. Enable incoming Remote Support
Check Yes to enable remote access to your ESS through a modem. Check
No (default) to disallow or deny access.
b. Enable outgoing call home
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 (default) to
disallow or deny these calls.

c. Enable outgoing 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 (default) to disable
e-mail.
d. Enable Paging
The ESS can send problem information to your pager if you have
connected the telephone to a modem and enabled outgoing pager calls
(see step 12b on page 103). Check Yes to enable pager messages. Check
No (default) to disable pager messages. See step 7 on page 101 for
details about pagers.
e. Remote telephone numbers (RETAIN)
| Note: Enter this information only if you are attaching the ESS to an
| ESSNet1 console.
| IBM service personnel complete this information. The telephone numbers
| must include the appropriate outside line prefix, if one is required. The
| outside line prefix is the number that you use to access an outside line.
| Typical US prefixes are 9 or 1. Area codes and country codes must be
| included when appropriate. Enter the remote telephone number (call home)
| for your area from the following list:
| v IBM U.S. 1-800-783-4525
| v Asia Pacific (inside Japan) 0120-36-2105
| v Asia Pacific (international) 81-44-244-4892
| v Europe, the Middle East, and Africa (EMEA), see the IBM Global
| Services Web site for the ESS RETAIN telehone numbers:
| w3.uk.ibm.com/esdpboeb/boedevd.htm
Note: You do not need a valid telephone number if you are installing an
ESS Master Console, but you must enter the proper protocol.
f. Do not wait for dial tone before dialing?
IBM service personnel complete this information. Check Yes only if the local
telephone system does not give a dial tone after it accesses the outside
line.
g. Heartbeat/MRPD record destination
IBM service personnel complete this information.
Note: You must set this entry to “Support and PE Catcher” if you are
installing an ESS Master Console.
v Check the Support and PE catcher box (the default setting) to send
heartbeat and MRPD records to the Support and PE catcher (a server).
If you check Support and PE catcher, you need to enter the Support and
PE catcher telephone number (see step 12h).
v Check the RETAIN (remote technical assistance information network)
box to send heartbeat and MRPD records to the RETAIN catcher (a
server). Check RETAIN only if it is not possible to send heartbeat and
MRPD records to the Support and PE catcher.
Be aware that if you check RETAIN, the ESS does not transmit MRPD
information because the record has a large amount of data.
h. Support Catcher Number (also known as PE catcher)

| IBM service personnel complete this information. This information is
| required for heartbeat/MRPD records. The telephone numbers must include
| the appropriate outside line prefix, if one is required. The outside line prefix
| is the number that you use to access an outside line. Typical US prefixes
| are 9 or 1. Area codes and country codes must be included when
| appropriate. The xx in the following list is for the international access code.
| Replace the xx with the code for your country.
| Note: You do not need a valid telephone number if you are installing an
| ESS Master Console.
| v North America (San Jose) is xx + 1-877-745-5932
| v EMEA (Mainz) is xx + 49 + 6131-998783
| v AP (inside Japan) is 0120-644-243
| v AP (International) is xx + 81 + 466-44-6442
| v LA (Sao Paulo) is xx + 55-11-3050-3990
Service personnel who do not know the telephone number should call the
next level of support for this information.
Service personnel use this number to send heartbeat call-home records
that are nonproblem related directly to the support catcher server. These
records might include physical information, information about machine
feature codes, or information about activation of Standby CoD storage.
i. Callback Phone Number (local modem)
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 Master Consoles can be connected to the same modem if

they are connected by a switch. Each ESS is connected to the
Master Console which controls the modem.
j. Customer Phone Number
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 that you name for
contacts in step 4d on page 99.
k. Remote-Support Primary 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.
l. Outside Line Prefix
numbers in this field. Typical US prefixes would be “9,1”.
m. Enable remote PE to login across a LAN
Check Yes to enable PE personnel to sign on to the ESS. The PE
personnel have service experience and development experience for this
product. Check No (default) to disallow this access.
n. Call home trace level
IBM service personnel enter this information after ESS installation.
13. Call-home heartbeat interval
Enter 0 - 15 days to set the length of time between call-home heartbeat calls
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 7 days.
Note: If you have Standby CoD storage, you must not set the call-home
interval to zero.
14. Fibre-channel LUN-access control
A switch on the ESS determines whether hosts have access to all LUNs over
fibre channels or whether access is restricted. Restricted access is based on
the worldwide ID (WWID) of the adapter port in the host system. Access also
depends on the logical configuration that is defined on the ESS for that host
port WWID. Restricted access is the normal way most environments are
configured.
Check one of the two switch settings:
v Check Restricted if you want to limit access to LUNs to those hosts that
you define in the ESS Specialist interface. Restricted is the default setting.
v Check Any if all hosts are to have access to all LUNs.
15. Change AS/400 LUN or iSeries serial number
This information is optional. Enter a three-digit number as a new serial number
base for an ESS. (Changing an ESS serial number also changes the current
LUN serial number, which uses the last three digits of an ESS serial number.)
Use this option when you attach a second ESS to an AS/400 or iSeries host
with the same three-character suffix as the first ESS. For example, the serial
number for ESS 1 is 13-14321 and the serial number for ESS 2 is 13-15321.
Because the LUN serial number is used for identification, the AS/400 does not
see the second LUN. Specifying a new serial-number base for the second ESS
prevents this problem. IBM service personnel enter the control-switch setting
for the new serial number base that you specify for this field.
Note: The probability of receiving two ESSs with the same last three serial
numbers is unlikely, but possible.
16. Allow CUIR (control-unit initiated reconfiguration) to automatically vary
paths off and on for S/390 and zSeries hosts
Check Enable to allow the ESS to initiate the reconfiguration for service.
Check Disable (default) to set the paths to the ESS cluster offline for service.
With CUIR enabled the ESS can request that an operating system verify that
one or more subsystem resources can be taken offline for service. The ESS
uses this process to automatically vary channel paths offline and online to
facilitate bay service or concurrent code installation.
Guidelines for completing the Communication Resources work sheet

for the ESS Master Console
Use the following guidelines when completing the work sheet that is shown in
Appendix B, “Communication Resources work sheet for the ESS Master Console,”
on page 125. Enter information in this work sheet only for the first ESS that you
attach to the ESS Master Console.
1. ESS Master Console Remote Service Settings
a. Enable remote services?
Check Yes (default) if you want to allow remote service to sign on (call in
and call out) to the ESS Master Console. If you check No, this disables IBM
service from accessing (calling) the ESS Master Console or the ESS for
remote service support. Call home is still enabled.

b. Use default password or optional password
Note: These passwords only authorize access to the ESS Master Console
and add another level of security to your system.
v Check Default password if you want to allow remote service to sign on
to use the default password. IBM sets the default password.
v Check Optional password if you want to assign a password (see Step
1c).
c. Set optional password
Enter the optional password for remote service to sign on. The password
can be any combination of 1 - 20 alphanumeric characters. Notify your next
level of support about the optional password.
d. Optional password expiration
Enter the length of time before the optional password expires. Enter either a
number of days (1 - 6), weeks (1, 2, or 4), or check Never.
e. Allow remote access authority update?
Check Yes to allow remote service to sign on to upgrade to a privileged
level of authority. This level of authority enables an IBM PE to analyze
problems within the ESS Master Console for setup and configuration. This
authority only applies to the ESS Master Console.
(Fill in the same information as in the fields with the same names in item 2 on
page 97 and item 3 on page 98 from “Guidelines for completing the
Communication Resources work sheet” on page 96.)
Enter the host name that you are assigning to the ESSNet workstation for
access over the network. For example, essnetmc.
Enter the domain name that you are assigning to the ESSNet workstation.
For example, tucson.ibm.com.
c. ESSNet workstation Internet address
Enter the dotted decimal network mask for the subnet for both the ESS and
the ESSnet workstation. The ESS and the Master Console are on the same
subnet and must be configured with the same subnet mask. For example,
255.255.254..
d. Network mask
Enter the dotted decimal network mask that you are applying to TCP/IP on
this machine (the ESS). For example, 255.255.254.0. (The ESS and the
Master Console are on the same subnet and both have to be configured
with the same subnet mask.)
Enter the dotted decimal address of the name server that this machine (the
ESS) is to access. For example, 9.113.42.250.
Enter the dotted decimal address of the second name server that this
machine (the ESS) is to access. For example, 9.113.42.252.

Note: The second name server Internet address and name server domain
name are optional. IBM recommends that you enter this information
when you configure a backup or secondary server for ESS Copy
Services.
Enter the domain name of the second name server. For example,
tucson2.ibm.com.
gateway for this machine (the ESS). For example, 9.113.155.254.
3. ESS Master Console call-home settings
Note: There is no configuration requirement at this time for “Disposition”.

a. Enable call home?
Check Yes to allow the ESS Master Console to call home.
Attention: If you check No, no ESS that is attached to the ESS Master
Console can call home, regardless of the ESS settings that you have
configured.
b. Check the call-home interface (check one)
v Check Modem if you want calls to go only over the modem.
v Check IBM Intranet if you want calls to go only over the IBM intranet.
Note: To select this option, you need to connect the Master Console to
the your LAN, and connect the your LAN to the IBM intranet.
v Check Autoselect if you want the communications program to
automatically select the fastest path.
4. Dumps and traces
Note: This information also applies to MRPD data.

a. Setup delivery method: same as call home or the IBM FTP data repository
server
v Check Use the same setup as call home if you want the ESS to use the
same interface selections as call home for dump and trace call-home
transmissions.
v Check Use the IBM FTP data repository server if you want to send
dumps and traces directly to an FTP proxy server.
Note: To select this option, you need to connect the Master Console to
the your LAN.
b. If you checked Use the IBM FTP data repository server, enter the
destination server information:
Note: Use the default values for most of the following entries. Contact your
PE organization for details.
1) Use passive transfers?
Check Yes if you need to use a passive transfer interface.
2) Destination server host name (default is testcase.boulder.ibm.com)
3) Destination server user ID (default is anonymous)

4) Destination server password (use the account default)
5) Destination server port (default is 21)
6) Destination server directory (default is /ssd/toibm/sharkdumps)
c. Enter your firewall properties
Check one of the following choices:
1) Use no firewall
2) Use passive FTP firewall
a) Firewall host name
b) Firewall port
3) Use relay FTP firewall
a) Firewall host name
b) Firewall user ID
c) Firewall password
d) Firewall command
e) Firewall port
5. Telephone settings
a. Dial
Check Tone if you have tone dial. Check Pulse if you have pulse dial.
b. Do not wait for dial tone?
Check Yes if you have a telephone system that does not give a dial tone
when you dial an outside line with a dial-out prefix.
c. Dial out prefixes
numbers in this field. Typical US prefixes would be 9 and 1.
d. Country or region
Enter the country or region for your AT&T Global Network Services
telephone number.
e. State or province
Enter the state or province (U.S. or Canadian) for your AT&T Global Network
Services telephone number.
f. Select location
When the CE configures the phone numbers, the CE uses the Master
Console to enter the location information that you enter in steps 5d and 5e.
When the CE enters this information, the Master Console displays a list of
phone numbers that receive Call Home records. The CE selects the
telephone number then clicks Import phone number.
6. Machine information
Defects and informational data associated with the ESS Master Console are
logged in RETAIN against one ESS that is attached to the ESS Master Console.
This ESS must be registered with RETAIN. If more than one ESS is attached
to the Master Console, select the ESS with the highest microcode level.
Enter the following information for that ESS:
a. Enter the machine type (for example, use 2105 for the ESS)
b. Enter the machine model (for example, F20)
c. Enter the machine serial number in upper case, with no dashes (for
example, 13FCA23).

Converting from an ESSNet console to an ESS Master Console
If you are converting from an ESSNet console to an ESS Master Console, contact
your IBM marketing office. When you obtain a miscellaneous equipment
specification (MES) for this service, IBM service personnel will perform the
conversion free of charge. The following guidelines are for the service personnel:
1. Get the IP address of the ESSNet console:
a. On the ESSNet console, double-click the ESSNet Toolkit icon on the
desktop.
b. Click the Install/Configure tab.
c. Click ESSNet Configuration.
d. Click the Primary ESSNet Console tab.
e. Record the following information from this window:
v Host name of the ESSNet console
v Console IP address of the ESSNet console
v Console subnet mask of the ESSNet console
2. Get the IP addresses of the attached ESSs:
a. From step 1e, click the Subsystem tab. For each attached ESS, record the
following information on this window:
v Host name of the ESS
v IP address of the ESS
v Subnet mask of the ESS
b. Close the ESSNet console Configuration Window.
c. Close the ESSNet console Toolkit.
In addition to gathering TCP/IP information to update call-home functions, perform

the following tasks:
v Increase the memory on your ESSNet console by adding 128 MB of memory.
Note: This is only necessary if the current amount of memory on the PC is less
than 128 MB.
v Install the ESS Master Console code. This code includes a Linux operating
system.
v Replace the modem expander with an MSA.
v Use an Ethernet hub with a speed of 100 Mbps. Ensure that the Ethernet cable
is compatible with the hub speed.
To complete the conversion, follow the instructions in the IBM miscellaneous

equipment specification (MES).
Guidelines for completing the Communication Resources work sheets

for ESS Copy Services
This section gives guidelines for completing the Communication Resources work
sheets (see Appendix C, “Communication Resources work sheets for ESS Copy
Services,” on page 127) for ESS Copy Services:
v Enable ESS Copy Services work sheet
v Enable ESS Copy Services without DNS work sheet

For ESS communication to work well, some type of name resolution has to be
running in your network. IBM recommends that you use a domain name server
(DNS) for name resolution. When DNS is not available, the IBM SSR can configure
each ESS to provide name resolution by using host tables.
DNS provides the following advantages:

v It resolves the names of the participating ESS clusters.
v It enables the open-systems hosts to run CLI for ESS Copy Services automation.
v It enables the ESS 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 10 shows an ESS Copy Services server domain in a DNS configuration.
Figure 10. ESS Copy Services server domain in a DNS configuration
Each ESS cluster needs to have an IP address assigned to it. Servers must be
defined for all of ESS clusters in the domain. If you are running a LIC level that is
below 2.2.0, you must have a service representative set up your server and client
IP addresses. If you have installed LIC level 2.2.0, you can set up your own server
and client IP addresses by using the Tools panel in the ESS Copy Services Web
interface. See the IBM TotalStorage Enterprise Storage Server: Web Interface
User’s Guide for more information about managing the IP addresses.
Note: Copy Services servers are configured in dual-active or single-active mode

depending on the LIC of the ESS. If your Copy Services servers are running
pre-LIC 2.2.0, the servers are configured in single-active mode, where one
server is defined as the primary and the other is the backup. If the Copy
Services servers are running LIC 2.2.0 or higher, then both servers are

operating in dual-active mode. This means that both servers are active at the
same time. There is no concept of a primary or backup Copy Services
server.
If you decide not to use a DNS in your configuration, provide your IBM SSR with
the following additional information. The SSR uses the Service interface to enter the
information in the ESS:
v The TCP/IP address and host name for each ESS cluster in the ESS Copy
Services server domain
v The TCP/IP address and host name for each host using the CLI
v The TCP/IP address and host name of the ESS Master Console
Enable ESS Copy Services work sheet

Use the following instructions to complete the Enable ESS Copy Services work
sheet (see Appendix C, “Communication Resources work sheets for ESS Copy
Services,” on page 127). See “Planning for ESS Copy Services” on page 33 for
additional information about Copy Services requirements and planning for site
configurations and Copy Services tasks.
Note: Copy and complete this work sheet for each ESS Copy Services server
domain that you define. You can define up to eight ESSs in a server domain.
In addition to completing this work sheet (Appendix C, “Communication

Resources work sheets for ESS Copy Services,” on page 127), if you have
not specified a DNS, fill out the “Enable ESS Copy Services without DNS
work sheet” on page 129 to collect the host names and IP addresses for all
of the open-systems hosts that use CLI. See “Enable ESS Copy Services
without DNS work sheet” on page 116 for the more information on how to fill
out this form.
1. Server domain
Identify the server domain that you are defining with this work sheet. Enter
unique alphanumeric characters to identify each server domain. IBM suggests
that you use three characters, for example, server domain 001, server domain
002, and so forth. There is no limit to the number of server domains that you
can identify.
You can configure up to eight ESSs within a ESS Copy Services server domain.
Each ESS Copy Services server domain manages up to 16 clusters and a
maximum of 2048 relationship-pairs (Flashcopy and PPRC pairs).
If you are running a LIC level that is below 2.2.0, provide this information to
your IBM SSR for each ESS Copy Services server domain that you want to
configure. If you have installed LIC level 2.2.0, you can set up your own server
domain by using the Tools panel in the ESS Copy Services Web interface.
2. Primary (or ServerA) Copy Services server IP address
Enter a dotted decimal or symbolic name as the address for this machine (the
ESS). For example, 9.113.152.148.
Note: If your Copy Services servers are running pre-LIC 2.2.0, the servers are
configured in single-active mode, where one server is defined as the
primary and the other is the backup. If the Copy Services servers are
running LIC 2.2.0 or higher, then both servers are operating in
dual-active mode. This means that both servers are active at the same
time. There is no concept of a primary or backup Copy Services server.
3. Backup (or ServerB) Copy Services server IP address

Enter a dotted decimal or symbolic name as the address for this machine (the
ESS). For example, 9.113.152.147.
4. Is a domain name server (DNS) configured on the ESS?
Check Yes or No.
If you checked No and you are using the CLI, you must additionally fill out the
“Enable ESS Copy Services without DNS work sheet” on page 116 for
information on the host names and IP addresses.
5. Copy Services commands for S/390 and zSeries volumes
Check Enable or Disable (disable is the default). ESS Copy Services supports
FlashCopy and PPRC for volumes on S/390 and zSeries hosts in addition to
volumes on open-systems hosts.
Note: It is not necessary to enable ESS Copy Services for volumes on S/390
or zSeries hosts if you are going to use TSO and IDCAMS.
6. ESS 1 machine serial number (primary server site)
Enter the serial number of this machine (an ESS). For example, 013-SJC15.
a. Cluster 1 host name
network. For example, Storage03.company.com.
Note: The host name that you define here is the Web site address for
access to ESS Copy Services.
b. Cluster 1 IP address
Enter the dotted decimal address that you are assigning to Cluster 1 of this
machine (an ESS). For example, 9.113.152.149.
c. Cluster 2 host name
d. Cluster 2 IP address
7. ESS 2 machine serial number (backup server site)
8. ESS 3 machine serial number (optional)

Enter the serial number of this machine For example, 013-SJC55.
the network. For example, Storage15.company.com.


Enable ESS Copy Services without DNS work sheet

If you have not specified a DNS, in addition to filling out the“Enable ESS Copy
Services work sheet” on page 127, complete the “Enable ESS Copy Services
without DNS work sheet” on page 129 to collect the host names and IP addresses
for all of the open-systems hosts that use CLI. Your SSR uses the service interface
to enter the information in the ESS.
Note: Copy this work sheet for additional hosts if you have more than four hosts
that are using CLI to communicate with a server domain.
1. Server domain
Identify the server domain that you are defining in this work sheet.
2. Command-line interface host 1
a. IP address
Enter the dotted decimal address that you are assigning to command-line
interface host 1. For example, 9.113.152.151.
b. Host name
Enter the host name that you are assigning to command-line interface host
1 for access over the network. For example, Storage04.company.com.
a. IP address
b. Host name
a. IP Address
b. Host name
a. IP Address
b. Host name

Chapter 6. Planning data migration
This chapter provides planning guidelines for migrating data to the ESS. It includes
the following information to help you plan for migrating data for the S/390, zSeries,
and open-systems hosts:
v Migrating data for open-systems hosts
v Migrating data for S/390 and zSeries hosts
v Obtaining IBM data migration and other services
See the IBM TotalStorage Enterprise Storage Server: User’s Guide for detailed
information about migrating data to the ESS.
You can use PPRC, PPRC-XD, and FlashCopy for backing up and migrating data.
for guidelines on using PPRC and PPRC-XD.
Migrating data for open-systems hosts

For UNIX, Windows, and OS/400 operating systems, you can use a variety of
methods for copying or moving data from one disk drive to another. These include,
but are not limited to:
v Volume management software
Volume management software provides specific tools for wholesale movement of
data.
AIX, Solaris, and HP-UX all have volume management software that directly
controls the disks and storage devices attached to the system. It provides the
system administrator with tools for configuring and managing disk drives, file
systems, paging, and to exchange spaces. The software also provides the
operating system interface to the data.
v Direct copy with cpio -p
The cpio command is a standard UNIX command for archiving and copying data.
The -p (pass) option allows the operating system to copy data between file
systems without the creation of an intermediate archive.
The cpio command reads a list of files to copy from its standard input. You
typically use it with the UNIX find command to copy complete directory
structures.
v AIX backup and restore commands
You commonly use these commands on AIX systems to archive and restore data.
However, they do not support a direct disk-to-disk copy. They require an
intermediate device such as a tape drive or spare disk drive to store the archive
that is created by the backup command.
v The dump and restore commands
These commands are similar in function to the AIX backup command and
restore command; you mostly find them on other forms of UNIX. They, too,
require an intermediate device.
v Other commands
Other UNIX commands provide archival functions, such as the tar command, that
you can use to transport data. Again, these commands require that you create an
intermediate archive, usually on a tape drive or spare disk drive.

Your system administrator should select the method that is the best compromise
between efficiency and least impact on the users of the system:
v Management software provides simple robust methods that you can generally
use during production without disturbing users.
v The AIX logical volume manager (LVM) provides methods that you can use at
any time without disrupting access to the data by users. You might notice a small
performance degradation, but this is better than having to shut down databases
or require users to log off the system.
v Methods that use backup and restore procedures will generally have the most
impact on the system usage. They require that databases and file systems be in
quiescent states to ensure a valid snapshot of the data.
Reformatting existing disk drive modules

To provide integrity-checking of data and to allow different operating systems to use
the ESS, IBM formats ESS disks to a 524-byte sector. The 524-byte sector replaces
the traditional 512-byte sector of fixed-block architecture disk drive modules
(DDMs). The 524-byte sector format requires that you reformat all disks that you
are migrating to the ESS. Because reformatting will erase any data that is already
contained on the drives, you must back up the data to some form of temporary
storage.
You can use the DDM for either direct migration of data or as temporary storage
while the existing drives are moved. If this is not possible, use a removable media
device such as a tape drive to temporarily store the data while you reformat the
drives.
The AIX LVM uses a fixed-byte sector of 512 bytes. When used in an ESS, the
format is a fixed-byte sector of 524 bytes. The data portion of the sector remains at
512 bytes. AS/400 and iSeries headers use eight additional bytes. A 2-byte
sequence number and a 2-byte longitudinal redundancy check (LRC) complete the
extra bytes. The ESS LIC uses the sequence number and LRC. The ESS does not
transfer them to the host system. For a description of the new format, see
“Fixed-byte sector format.”
Fixed-byte sector format

Most fixed-block disk architectures use a fixed-byte sector of 512 bytes. This
includes most UNIX systems, including AIX. When used in an ESS, the format of a
DDM has a fixed-byte sector of 524 bytes. The 524-byte sector format enables the
ESS to connect to a wide range of host systems and share data between them.
The 524-byte sector on the DDM is independent of the sector size exposed to the
host for a given device type emulation. Most LUNs for open-systems hosts are
exposed with a 512-byte sector.

The IBM AS/400 and iSeries host systems use eight bytes at the start of the sector.
UNIX host systems do not use these eight bytes when you attach them to the ESS.
The data portion of the sector remains at 512 bytes for all host systems. A 2-byte
sequence number and a 2-byte LRC increase the size of the sector to 524 bytes.
The sequence number is a modulo 64K value of the logical block address (LBA) of
this sector. It is an extra method of ensuring that you are accessing the correct
block.
The LRC, generated by the host adapter, is calculated on the 520 data bytes and
header bytes. The ESS uses the LRC as an error checking mechanism. The LRC
checks the data as it progresses from the host, through the ESS controller, into the
device adapter, to the array.
Migrating data for S/390 and zSeries hosts

This section includes information about planning data migration for S/390 and
zSeries host systems.
Planning data migration for MVS environments

The following guidelines and resources can help you plan data migration for MVS
environments:
1. Consider the major environments:
v System-managed storage (SMS)
The SMS environment greatly simplifies introduction of new DDMs in
comparison to non-SMS environments. If your environment is SMS, you can
use 3390 Installation and Migration for DFSMS to help you plan your
migration.
v Non-SMS
If your environment is non-SMS, you can coordinate a migration to SMS with
a migration to the new storage server. You can also consider SMS and
non-SMS migrations as separate projects.
2. Identify the most critical data and determine in advance some methods to verify
that the data has been moved correctly.
Planning data migration for VM environments

You can simplify data migration for a VM environment by using DFSMS/VM®®,
which is a no-charge feature of VM/ESA. This feature lets you manage and control
the use of VM disk space. It will also move minidisks from one media to another.
Use of DIRMAINT also provides tools that will manage the movement of CMS
minidisks from one media to another.
Chapter 6. Planning data migration 119

Obtaining IBM data migration and other services
IBM provides storage-related services for a fee, such as data migration services.
These services offer a reliable method of migrating your data to an ESS. These
services include:
v Project planning
v Data migration to larger capacity DDMs
v Consolidation of data from differing systems to one central location
v Consolidation of your data center
v Post-migration services
An IBM services specialist performs the service at your site by using an

IBM-supplied software tool installed on your systems. This tool mirrors source data
and target data and allows continued systems operation during the process. To
ensure a smooth migration, the tool only updates your files when there is minimal
impact to system operations. The tool provides minimal application disruption
without significantly impacting the performance of your system.
For information about data migration and storage services, call 1-800-IBM-4YOU.

Appendix A. Communication Resources work sheet
See “Guidelines for completing the Communication Resources work sheet” on page
96 for the instructions for completing this work sheet.
Note: Defaults are in bold-face type.
The customer must supply the information for items 1–4 unless defaults are to be used.
1. Time zone and date configuration
a. Do you go on daylight savings time? (check one) U Yes h No
b. Time zone
Enter a selection from the list in 1b on page 96.
2. TCP/IP configuration
a. Local cluster 1 host name (100 characters maximum)
b. Local cluster 1 Internet address (dotted decimal)
c. Alternate cluster 2host name (100 characters
maximum)
d. Alternate cluster 2 Internet address (dotted decimal)
e. Network mask (dotted decimal)
f. Network interface (check one) U en0 Standard Ethernet network interface
h et0 IEEE 802.3 Ethernet network interface
g. Name server (DNS) Internet address (dotted decimal)
h. Name server domain name (for example,
tucson.ibm.com)
i. Default gateway address (dotted decimal or
symbolic name)
j. Your cable type (check one) U N/A (default) h bnc (thin cable)
h dix (thick cable) h tp
Only complete item 3 if an ESSNet1 is being installed with the ESS. For installations with the Master
Console, see Appendix B, “Communication Resources work sheet for the ESS Master Console,” on page 125.
b. ESSNet workstation domain name (for example,
tucson.ibm.com)
c. ESSNet workstation Internet address (dotted decimal)
d. ESSNet workstation network mask (dotted decimal)
f. Name server domain name 1 (for example,
tucson.ibm.com)
h. Name server domain name 2 (for example,
tucson.ibm.com)
j. Ethernet adapter mode (check one) h half-duplex h full-duplex

4. Customer information
a. Customer business/company name a. _____________________________________

b. Machine (ESS) location b. _____________________________________
c. Customer contact telephone number c. _____________________________________
d. Customer contact name d. _____________________________________
e. Customer contact e-mail address e. _____________________________________
f. Additional account information f. _____________________________________
g. Customer phone number g. _____________________________________
h. Callback phone number (local modem) h. _____________________________________
i. Outside line prefix i. _____________________________________
Complete the optional items 5–7 only if the function is required.
5. E-mail configuration (optional)
a. Maximum error notification count per problem ________________(default is 1)
b. To enable smart relay host, enter a host name or _____________________
network address
c. Configure or unconfigure local e-mail h Configure h Unconfigure
d. Add e-mail destinations Enable for: (check one)
______________________________ 1. herrors h information h all h none
______________________________ 2. herrors h information h all h none
6. SNMP configuration (optional)
a. Allow MIB access? (check one) U None h Read Only
b. Allow generic traps? (check one) h Yes U No
c. Allow product-specific traps? (check one) h Yes U No
d. Maximum trap notifications per problem ___ (default is 4)
e. SNMP community name
f. SNMP SysContact (optional)
g. SNMP SysLocation (optional)
h. Add SNMP trap destinations ______________________________
______________________________
7. Pager information (optional)
a. Maximum pager problem presentation count (1 - 9) ___ (default is 4)
b. Pager user name _______________________________
c. Modem (TAP/XIO) telephone number ________________________________
d. Pager user PIN or ID number _______________________________
e. Carrier pager user password ________________________________
f. Pager type (check one) h Alphanumeric h Numeric
g. Pager state h Enabled h Disabled
h. Number of repeats (0 - 10) ________________________________
The IBM Service Representative uses the defaults indicated for items 8 – 16, unless you indicate otherwise.
Skip these items if the defaults are valid for your environment.
8. Service information messages (SIMs) for S/390
a. SIM severity reporting level for DASD SIMs a. Service h Serious h Moderate h Acute U
(check one) None h

b. Maximum number of times a DASD SIM is to be sent b. ___ (default is 5)
(0 - 5)
c. SIM severity reporting level for media SIMs c. Service h Serious h Moderate U Acute h
(check one) None h
d. Maximum number of times a media SIM is to be sent d. ___ (default is 3)
(0 - 5)
e. SIM severity reporting level for a storage server e. Service h Serious h Moderate U Acute h
SIM (check one) None h
f. Maximum number of times a storage server SIM is f. ___ (default is 1)
to be sent (0 - 5)
9. Problem presentation
Maximum overall problem presentation count ___ (default is 5)
(0 - 5)
10 Enable ESS Specialist
a. Enable or Disable ESS Specialist U Enable h Disable
b. Update ESS Specialist on which cluster? h Local cluster Alternate cluster U Both
11. Modem configuration
IBM service personnel fill in this section. Note: Enter this information only for an ESSNet 1 console.
a. Name of modem set: ________________________________
b. Dialer phone system (check one) h tone h pulse
c. Modem data rate (check one) U Fastest speed available
h14400 h16800 h 19200 h21600
h 24000 h26400 h28800
d. Cancel the call if it does not connect within: ________ seconds (default is 45)
e. Number of consecutive retries for connection ________ retries (default is 1)
f. Name of the expander set ________________________________
g. Modem expander port for the modem _____ ports 1 - 16 (default is 16)
h. Modem expander port for cluster 1 _____ ports 1 - 16
i. Modem expander port for cluster 2 _____ ports 1 - 16
12. Call home and remote services
a. Enable incoming remote support? (check one) h Yes U No
b. Enable outgoing call home? (check one) h Yes U No
c. Enable outgoing e-mail across LAN? (check one) h Yes U No
d. Enable paging? (check one) h Yes U No
e. Remote telephone numbers (RETAIN) 1. ________________________________
IBM service personnel fill in this information. 2. ________________________________
Note: Enter this information only if you are attaching the ESS
to an ESSNet1 console.
f. Do not wait for dial tone before dialing? (check one) h Yes
IBM service personnel fill in this information. h No
Appendix A. Communication Resources work sheet 123

g. Heartbeat/MRPD record destination (check one) U Support and PE catcher
IBM service personnel fill in this information. h Retain catcher
h. Support catcher number for heartbeat/MRPD records ________________________________
IBM service personnel fill in this information.
i. Callback phone number (local modem) See 4.h ________________________________
j. Customer phone number See4.g
Primary:_______________
Off shift:_____________
k. Remote-support primary password __________________________ (default is support)
l. Outside line prefix See 4.i________________________________
m. Enable remote PE login across a LAN? h Yes U No
n. Call-home trace level ________________________________
IBM service personnel enter this information after ESS
installation
13. Call-home heartbeat interval
Call-home heartbeat interval ______ (0 - 15 days, 7 is default)
14. Fibre-channel LUN access control
Switch setting (check one) U Restricted h Any
15. Change AS/400 LUN serial number
Enter the last three digits of the ESS serial number _________
16. Allow CUIR to automatically vary paths off and on for S/390 and zSeries hosts
Check one. U Enable h Disable

Appendix B. Communication Resources work sheet for the
ESS Master Console
Enter information in this work sheet only for the first ESS that you attach to an ESS
Master Console. See “Guidelines for completing the Communication Resources
work sheet for the ESS Master Console” on page 106 for detailed information about
this work sheet.
Note: Defaults are indicated in boldface type.
The customer must provide the information for item 2 if the ESS will be connected to a LAN. The customer
must provide the information for item 4c if FTP is used through a firewall. The IBM Service Representative
uses the defaults for the other items if other values are not specified. If the defaults are valid, you can skip
these items.
1. ESS Master Console remote service settings
a. Enable remote services? U Yes h No
b. Use default or optional password (check one) U default password h optional password
c. Set optional password ______________________________
d. Optional password expiration ___ days
___weeks
h Never
e. Allow remote access authority update? U Yes h No
The customer must provide the information for item 2 if the ESS will be connected to the LAN.
c. ESSNet workstation Internet address (dotted decimal)
d. Network mask (dotted decimal)
e. Name server (DNS) internet address 1 (dotted decimal)
g. Name server (DNS) Internet address 2 (dotted decimal)
i. Default gateway address (dotted decimal or
symbolic name)
3. ESS Master Console call-home settings The IBM Service Representative will complete this item.
a. Enable call home? U Yes h No
b. Check the call-home interface (check one) hModem
hIBM Intranet
hAutoselect
4. Dumps and traces The IBM Service Representative will complete this item.
a. Setup delivery method hUse the same setup as call home
hUse the IBM FTP data repository server

b. If you checked “Use the IBM FTP data repository
server” enter the destination server information:
1. Use passive transfers?

1. U Yes h No
2. Destination server host name
2. testcase.boulder.ibm.com
3. Destination server user ID
3. anonymous
4. Destination server password
4. shark
5. Destination server port
5. 21
6. Destination server directory
6. /ssd/toibm/sharkdumps
c. Enter your firewall properties (check one):
1. Use no firewall 1. h (If you check this box, skip steps 2 and 3.)
2. Use passive FTP firewall 2.
a. Firewall host name a. ______________
b. Firewall port b. ______________
3. Use relay FTP firewall 3.
a. Firewall host name a. ______________
b. Firewall user ID b. ______________
c. Firewall password c. ______________
d. Firewall command d. ______________
e. Firewall port e. ______________
5. Telephone settings
a. Dialing h Tone h Pulse
b. Do not wait for dial tone? h Yes h No
c. Dial out prefixes
d. Country or region
e. State or province
f. Select location (city)
6. Machine information
a. Machine type
b. Machine model
c. Machine serial number

Appendix C. Communication Resources work sheets for ESS
Copy Services
This appendix includes two work sheets for ESS Copy Services. You should
complete, copy, and make the work sheets available at both the primary server site
and the backup server site:
v Enable ESS Copy Services work sheet (see “Enable ESS Copy Services work
sheet”)
v Enable ESS Copy Services without DNS work sheet (see “Enable ESS Copy
Services without DNS work sheet” on page 129)
Enable ESS Copy Services work sheet

See page 110 for the instructions for completing this work sheet.
1. Server domain
2. Primary Copy Services server IP address
3. Backup Copy Services server IP address
4. Is a domain name server (DNS) configured on the
ESS? (check one) h Yes h No
Note: If you checked No and you are using the CLI,
additionally complete the “Enable ESS Copy
Services without DNS work sheet” on page 129 to
enter information about host names and IP
addresses.
5. Copy Services commands for S/390 or zSeries
volumes h Enable h Disable
6. ESS 1 machine serial number (primary server site)
a. Cluster 1 host name (100 characters maximum)
b. Cluster 1 IP address (dotted decimal)
c. Cluster 2 host name (100 characters maximum)
d. Cluster 2 IP address (dotted decimal)
7. ESS 2 machine serial number (backup server site)


Enable ESS Copy Services without DNS work sheet
If you do not have a domain name server configured on your ESS and you are
using the CLI, complete both the “Enable ESS Copy Services work sheet” on page
127 and the following “Enable ESS Copy Services without DNS work sheet.” See
“Enable ESS Copy Services without DNS work sheet” on page 116 for the
instructions for completing this work sheet.
1. Server domain
2. Command line interface host 1
a. IP address
b. host name
a. IP address
b. host name
a. IP address
b. host name
a. IP address
b. host name
Appendix C. Communication Resources work sheets for ESS Copy Services 129
|
| Appendix D. IBM 2105 Model 100 and 7133 Drawer Attachment
| The IBM 2105 Model 100 expansion enclosure allows you to attach IBM 7133
| Model 020 and D40 drawers into ESS configurations. The Model 100 expansion
| enclosure is supported on ESS Models E10, E20, F10, and F20. This support
| requires ESS LIC level 1.3.0, or later. If 7133 drawers of different capacity are
| attached to the same SSA loop, ESS LIC level 1.5.0, or later, is required. To attach
| a Model 100 to an ESS, you must purchase your Model 100 with selected features.
| See “Model 100 requirements” for details. Additionally, you must order the reserve
| loops feature (FC 9904) on your ESS. See “Reserve loops” on page 59 for
| additional information.
|
| Model 100 requirements
| The Model 100 can support up to six customer-supplied 7133 Model 020 or Model
| D40 drawers when they are attached to an ESS. Two Model 100 machines can be
| attached to an ESS. The second Model 100 can also support up to six
| customer-supplied 7133 Model 020 or D40 drawers, supporting a total of twelve
| drawers in the ESS configuration.
| You must order one of the following features with the Model 100 to enable
| attachment to the ESS. These features apply to new Model 100 orders only. The
| features ensure that your Model 100 is shipped with the appropriate hardware and
| cables to enable the installation of up to six 7133 drawers.
| v FC 1121 to attach the first new Model 100 expansion enclosure
| v FC 1122 to attach a second new Model 100 expansion enclosure
| You must also order the battery backup system (FC 1000) on your Model 100.
| The Model 100 installation must meet the floor-loading and service-clearance
| requirements as specified in “Service-clearance and floor-load requirements” on
| page 87.
| Notes:
| 1. The 2105 Model 100 is no longer available after November 7, 2003.
| 2. You cannot attach the Model 100 to an ESS model that already has an ESS
| expansion enclosure (FC 2100).
| 3. ESS Models 750 and 800 does not support the Model 100 expansion enclosure.
| 4. Some disk drives, such as the 72.8 GB disk drives or 15 000 rpm drives, are
| not supported by the Model 100 expansion enclosure. Contact your IBM field
| office for more information.
|
| Reserve loops
| Reserve loops (FC 9904) are required on your ESS to enable attachment of the
| Model 100. When you specify this feature, the installation of disk eight-packs and
| construction of SSA loops within the ESS creates reserved (empty) SSA loops that
| can then be used to cable 7133 drawers into the configuration.
| The reserve loops feature reserves two SSA loops. A maximum of two reserve
| loops features can be ordered to reserve a total of four loops.
| v With one reserve loop feature, loops 3B and 4B are reserved for the attachment
| of up to six 7133 drawers.

| v With two reserve loop features, loops 1B, 2B, 3B, and 4B are reserved for the
| attachment of up twelve 7133 drawers.
| See “Reserve loops” on page 59 for additional information.
|
| 7133 drawer removal and installation
| The 7133 drawer must be logically and physically removed from the previous
| subsystem. If you fail to properly remove arrays prior to attempting installation in an
| ESS, you receive an installation error when you attempt to format an existing array.
| Resolving the error adds extra hours to the drawer installation time.
| Before removing or relocating an existing 7133 drawer from its previously installed
| subsystem, complete the following tasks:
| v Make a copy of the data that is contained on the array before you delete the
| logical configuration.
| v Delete the logical configuration.
| After you meet the compatibility requirements that are listed in this section, an IBM
| service support representative installs and configures the 7133 drawers into the
| Model 100 attached to the ESS.
| IBM charges you for 7133 removals or relocations that are subsequent to
| installation of the Model 100 with FC 1121 or 1122. All parts that the service
| representative removes remain your property.
|
| 7133 Model 020 requirements
| Your 7133 Model 020 drawer must meet the following requirements before an
| service support representative can install it in a Model 100 that is attached to an
| ESS:
| v The drawer must contain 4.5 GB or 9.1 GB drives.
| v All drives in the drawer must be of the same capacity and rpm.
| v The drawer must be fully populated with 16 drives. If additional drives are
| required to fully populate the drawer, place an order against the serial number of
| the Model 020 drawer that requires the additional drives:
| – Use FC 3401 to purchase additional 4.5 GB drives.
| v The drawer cannot contain 48-V power supplies. If the drawer contains 48-V
| power supplies, you must order the following items:
| – Three 220-V power supplies (FC 3090™ on IBM 7132 Model REP)
| – Engineering Change F20795A for the power supply
| – Engineering Change F23443A for the power-supply package
| v Engineering Change 005 must be installed providing for SSA loop bypass cards.
| Engineering Change 005 can be verified by checking the bar code on the drawer
| mounting bracket for 1WCxxxxx. The code 1WC indicates that engineering
| change 005 is installed.
| v The drawer front cover must be removed.

|
| 7133 Model D40 requirements
| Your 7133 Model D40 drawer must meet the following requirements before a
| service support representative can install it in into a Model 100 that is attached to
| an ESS:
| v All drives in the drawer must be of the same capacity and rpm.
| v The drawer must be fully populated with 16 drives. If additional drives are
| required to fully populate the drawer, place an order against the serial number of
| the Model D40 drawer that requires the additional drives:
| v The drawer front cover must be removed.
|
| Logical configuration planning
| You cannot plan the logical configuration for an ESS with reserve loops and 7133
| attached drawers until IBM has installed and cabled the ESS. After installation, the
| ESS Specialist will show disk group locations on each SSA loop. At that time, you
| can plan the logical configuration.
| To plan your logical configuration, you must fill out custom configuration work
| sheets using a modified version of a Define Disk Groups work sheet that most
| closely matches the storage capacity being installed with the Model 100 expansion
| enclosures and 7133 drawers. The 7133 drawer will be configured as two disk
| groups. The disk groups can be either RAID 5 arrays or non-RAID disks. See IBM
| TotalStorage Enterprise Storage Server: Configuration Planner for Open-Systems
| Hosts or IBM TotalStorage Enterprise Storage Server: Configuration Planner for
| S/390 and IBM Eserver zSeries Hosts for more information about the configuration
| work sheets.
| Logical configuration of the 7133 drawers is only supported through the ESS
| Specialist.
Appendix D. IBM 2105 Model 100 and 7133 Drawer Attachment 133
Appendix E. Accessibility
Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully.
Features
These are the major accessibility features in the IBM TotalStorage Enterprise
Storage Server information:
1. You can use screen-reader software and a digital speech synthesizer to hear
what is displayed on the screen. IBM Home Page Reader version 3.0 has been
tested.
2. You can operate features using the keyboard instead of the mouse.
Navigating by keyboard
You can use keys or key combinations to perform operations and initiate menu
actions that can also be done through mouse actions. You can navigate the IBM
TotalStorage Enterprise Storage Server information from the keyboard by using the
shortcut keys for your browser or Home Page Reader. See your browser Help for a
list of shortcut keys that it supports. See the following Web site for a list of shortcut
keys supported by Home Page Reader:
http://www-306.ibm.com/able/solution_offerings/keyshort.html
Accessing the publications

You can find HTML versions of the IBM TotalStorage Enterprise Storage Server
information at the following Web site:
http://www.ehone.ibm.com/public/applications/publications/cgibin/pbi.cgi
You can access the information using IBM Home Page Reader 3.0.

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may be
used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you any
license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATIONS ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR
A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply to
you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this publication at any
time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for this
IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM
has not tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
Trademarks
The following terms are trademarks of International Business Machines Corporation
in the United States, other countries, or both:
AIX
AS/400
DB2
DFSMS/MVS
DFSMS/VM
e (logo)
Enterprise Storage Server
Enterprise Systems Architecture/390
ES/9000
ESCON
FICON
FlashCopy
IBM
MVS
MVS/ESA
Netfinity
NetVista
NUMA-Q
Operating System/400
OS/390
OS/400
RS/6000
S/390
Seascape
SP
System/360
System/370
System/390
TotalStorage
Versatile Storage Server
VM/ESA
VSE/ESA
xSeries

z/Architecture
z/OS
zSeries
z/VM
Microsoft, Windows, and Windows NT are registered trademarks of Microsoft

Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in
the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
Electronic emission notices

This section contains the electronic emission notices or statements for the United
States and other countries.
Federal Communications Commission (FCC) statement

This equipment has been tested and complies with the limits for a Class A digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide
reasonable protection against harmful interference when the equipment is operated
in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the
instruction manual, might cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful
interference, in which case the user will be required to correct the interference at
his own expense.
Properly shielded and grounded cables and connectors must be used to meet FCC
emission limits. IBM is not responsible for any radio or television interference
caused by using other than recommended cables and connectors, or by
unauthorized changes or modifications to this equipment. Unauthorized changes or
modifications could void the users authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) this device might not cause harmful interference, and
(2) this device must accept any interference received, including interference that
might cause undesired operation.
Industry Canada compliance statement

This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conform à la norme NMB-003 du

Canada.
European community compliance statement

This product is in conformity with the protection requirements of EC Council
Directive 89/336/EEC on the approximation of the laws of the Member States
relating to electromagnetic compatibility. IBM cannot accept responsibility for any
Notices 139
failure to satisfy the protection requirements resulting from a nonrecommended
modification of the product, including the fitting of non-IBM option cards.
Germany only
Zulassungsbescheinigung laut Gesetz ueber die elektromagnetische
Vertraeglichkeit von Geraeten (EMVG) vom 30. August 1995.
Dieses Geraet ist berechtigt, in Uebereinstimmung mit dem deutschen EMVG das
EG-Konformitaetszeichen - CE - zu fuehren.
Der Aussteller der Konformitaetserklaeung ist die IBM Deutschland.
Informationen in Hinsicht EMVG Paragraph 3 Abs. (2) 2:

Das Geraet erfuellt die Schutzanforderungen nach EN 50082-1 und
EN 55022 Klasse A.
EN 55022 Klasse A Geraete beduerfen folgender Hinweise:
Nach dem EMVG:

"Geraete duerfen an Orten, fuer die sie nicht ausreichend entstoert
sind, nur mit besonderer Genehmigung des Bundesministeriums
fuer Post und Telekommunikation oder des Bundesamtes fuer Post und
Telekommunikation
betrieben werden. Die Genehmigung wird erteilt, wenn keine
elektromagnetischen Stoerungen zu erwarten sind." (Auszug aus dem
EMVG, Paragraph 3, Abs.4)
Dieses Genehmigungsverfahren ist nach Paragraph 9 EMVG in Verbindung

mit der entsprechenden Kostenverordnung (Amtsblatt 14/93)
kostenpflichtig.
Nach der EN 55022:

"Dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funkstoerungen verursachen; in diesem Fall kann vom
Betreiber verlangt werden, angemessene Massnahmen durchzufuehren
und dafuer aufzukommen."
Anmerkung:
Um die Einhaltung des EMVG sicherzustellen, sind die Geraete wie in den
Handbuechern angegeben zu installieren und zu betreiben.

Japanese Voluntary Control Council for Interference (VCCI) class A
statement
Korean Ministry of Information and Communication (MIC) statement

Please note that this device has been certified for business use with regard to
electromagnetic interference. If you find this is not suitable for your use, you may
exchange it for one of residential use.
Taiwan class A compliance statement
VS07171L
Notices 141
Glossary
This glossary includes terms for the IBM Numerics
TotalStorage Enterprise Storage Server (ESS) and
other Seascape solution products. 750. A model of the Enterprise Storage Server
featuring a 2-way processor with limited physical
This glossary includes selected terms and storage capacity. This model can be updated to the
definitions from: model 800.
v The American National Standard Dictionary for 800. A model of the Enterprise Storage Server
Information Systems, ANSI X3.172–1990, featuring a standard processor or an optional Turbo
copyright 1990 by the American National processor. The Model 800 supports RAID 5, RAID 10,
Standards Institute (ANSI), 11 West 42nd and 15000 rpm drives. Model 800 supersedes Model
Street, New York, New York 10036. Definitions F20.
derived from this book have the symbol (A)
after the definition. 2105. The machine number for the IBM TotalStorage
Enterprise Storage Server (ESS). Models of the ESS
v The IBM Glossary of Computing Terms, which are expressed as the number 2105 followed by “Model
is available online at the following Web site: <xxx>”, such as 2105 Model 800. The 2105 Model 100
http://www.ibm.com/ibm/terminology/. Definitions is an ESS expansion enclosure that is typically referred
derived from this book have the symbol (GC) to simply as the Model 100. See also IBM TotalStorage
after the definition. Enterprise Storage Server and Model 100.
v The Information Technology Vocabulary 3390. The machine number of an IBM disk storage
developed by Subcommittee 1, Joint Technical system. The ESS, when interfaced to IBM S/390 or
Committee 1, of the International Organization zSeries hosts, is set up to appear as one or more 3390
for Standardization and the International devices, with a choice of 3390-2, 3390-3, or 3390-9
Electrotechnical Commission (ISO/IEC track formats.
JTC1/SC1). Definitions derived from this book
have the symbol (I) after the definition. 3990. The machine number of an IBM control unit.
Definitions taken from draft international 7133. The machine number of an IBM disk storage
standards, committee drafts, and working system. The Model D40 and 020 drawers of the 7133
papers that the ISO/IEC JTC1/SC1 is can be installed in the 2105-100 expansion enclosure of
developing have the symbol (T) after the the ESS.
definition, indicating that final agreement has
not been reached among the participating 8-pack. See disk eight pack.
National Bodies of SC1.
A
This glossary uses the following cross-reference
forms: access. (1) To obtain the use of a computer resource.
(2) In computer security, a specific type of interaction
See Refers the reader to one of two kinds of between a subject and an object that results in flow of
related information: information from one to the other.
v A term that is the expanded form of an
access-any mode. One of the two access modes that
abbreviation or acronym. This
can be set for the ESS during initial configuration. It
expanded form of the term contains the
enables all fibre-channel-attached host systems with no
full definition. defined access profile to access all logical volumes on
v A synonym or more preferred term the ESS. With a profile defined in ESS Specialist for a
particular host, that host has access only to volumes
See also that are assigned to the WWPN for that host. See also
Refers the reader to one or more related pseudo host and worldwide port name.
terms.
ACK. See request for acknowledgment and
Contrast with acknowledgment.
Refers the reader to a term that has an
opposite or substantively different active Copy Services server. The Copy Services
meaning. server that manages the Copy Services domain. Either
the primary or the backup Copy Services server can be

the active Copy Services server. The backup Copy and graphic characters. (A) Some organizations,
Services server is available to become the active Copy including IBM, have used the parity bit to expand the
Services server if the primary Copy Services server basic code set.
fails. See also Copy Services client and primary Copy
Services server. Contrast with backup Copy Services assigned storage. On an ESS, the space allocated to
server. a volume and assigned to a port.
agent. A program that automatically performs some asynchronous cascading PPRC. An optional feature
service without user intervention or on a regular of the Enterprise Storage Server (ESS) that uses a third
schedule. See also subagent. ESS to allow a secondary PPRC volume to become a
primary PPRC volume or a primary PPRC volume to
alert. A message or log that a storage facility become a secondary volume to another primary PPRC
generates as the result of error event collection and volume. See also synchronous PPRC and
analysis. An alert indicates that a service action is asynchronous PPRC.
required.
asynchronous PPRC. An optional feature of the
allegiance. In Enterprise Systems Architecture/390, a Enterprise Storage Server that provides a 2-site
relationship that is created between a device and one or extended distance remote copy. Data that is written by
more channel paths during the processing of certain the host to the ESS at the local site is automatically
conditions. See also implicit allegiance, contingent maintained at the remote site. See also synchronous
allegiance, and reserved allegiance. PPRC.
allocated storage. In an ESS, the space that is authorized program analysis report (APAR). A
allocated to volumes but not yet assigned. Contrast with request for correction of a defect in a current release of
assigned storage. an IBM-supplied program. (GC)
American National Standards Institute (ANSI). An availability. The degree to which a system or resource
organization of producers, consumers, and general is capable of performing its normal function. See data
interest groups that establishes the procedures by which availability.
accredited organizations create and maintain voluntary
industry standards in the United States. (A)
B
Anonymous. In ESS Specialist, the label on an icon
that represents all connections that are using backup Copy Services server. One of two Copy
fibre-channel adapters between the ESS and hosts and Services servers in a Copy Services domain. The other
that are not completely defined to the ESS. See also Copy Services server is the primary Copy Services
anonymous host, pseudo host, and access-any mode. server. The backup Copy Services server is available to
become the active Copy Services server if the primary
anonymous host. Synonym for pseudo host. Contrast Copy Services server fails. A Copy Services server is
with Anonymous and pseudo host. software that runs in one of the two clusters of an ESS
and manages data-copy operations for that Copy
ANSI. See American National Standards Institute. Services server group. See also Copy Services client
and primary Copy Services server. Contrast with active
APAR. See authorized program analysis report. (GC) Copy Services server.
arbitrated loop. A fibre-channel topology that enables bay. In the ESS, the physical space used for installing
the interconnection of a set of nodes. See also SCSI, ESCON, and fibre-channel host adapter cards.
point-to-point connection and switched fabric. The ESS has four bays, two in each cluster. See also
service boundary.
array. An ordered collection, or group, of physical
devices (disk drive modules) that is used to define bit. (1) Either of the digits 0 or 1 when used in the
logical volumes or devices. In the ESS, an array is a binary numeration system. (T) (2) The storage medium
group of disks that the user designates to be managed required to store a single binary digit. See also byte.
by the RAID technique. See also redundant array of
independent disks. block. (1) A string of data elements recorded or
transmitted as a unit. The elements may be characters,
ASCII. (American National Standard Code for words, or physical records. (T) (2) In the ESS, a group
Information Interchange) The standard code, using a of consecutive bytes used as the basic storage unit in
coded character set consisting of 7-bit coded characters fixed-block architecture (FBA). All blocks on the storage
(8 bits including parity check), that is used for device are the same size (fixed size). See also
information interchange among data processing fixed-block architecture and data record.
systems, data communication systems, and associated
equipment. The ASCII set consists of control characters

byte. (1) A group of eight adjacent binary digits that channel. In Enterprise Systems Architecture/390, the
represent one EBCDIC character. (2) The storage part of a channel subsystem that manages a single I/O
medium required to store eight bits. See also bit. interface between a channel subsystem and a set of
control units.
C channel command retry (CCR). In Enterprise
Systems Architecture/390, the protocol used between a
cache. A special-purpose buffer storage, smaller and channel and a control unit that enables the control unit
faster than main storage, used to hold a copy of to request that the channel reissue the current
instructions and data obtained from main storage and command.
likely to be needed next by the processor. (T)
channel command word (CCW). In Enterprise
cache fast write. In the ESS, a form of the fast-write Systems Architecture/390, a data structure that specifies
operation in which the storage server writes the data an I/O operation to the channel subsystem.
directly to cache, where it is available for later
destaging. channel path. In Enterprise Systems Architecture/390,
the interconnection between a channel and its
cache hit. An event that occurs when a read operation associated control units.
is sent to the cluster, and the requested data is found in
cache. The opposite of cache miss. channel subsystem. In Enterprise Systems
Architecture/390, the part of a host computer that
cache memory. Memory, typically volatile memory, manages I/O communication between the program and
that a storage server uses to improve access times to any attached control units.
instructions or data. The cache memory is typically
smaller and faster than the primary memory or storage channel-subsystem image. In Enterprise Systems
medium. In addition to residing in cache memory, the Architecture/390, the logical functions that a system
same data also resides on the storage devices in the requires to perform the function of a channel
storage facility. subsystem. With ESCON multiple image facility (EMIF),
one channel subsystem image exists in the channel
cache miss. An event that occurs when a read subsystem for each logical partition (LPAR). Each image
operation is sent to the cluster, but the data is not found appears to be an independent channel subsystem
in cache. The opposite of cache hit. program, but all images share a common set of
hardware facilities.
call home. A communication link established between
the ESS and a service provider. The ESS can use this CKD. See count key data.
link to place a call to IBM or to another service provider
when it requires service. With access to the machine, CLI. See command-line interface. See also Copy
service personnel can perform service tasks, such as Services command-line interface.
viewing error logs and problem logs or initiating trace
and dump retrievals. See also heartbeat and remote cluster. (1) In the ESS, a partition capable of
technical assistance information network. performing all ESS functions. With two clusters in the
ESS, any operational cluster can take over the
cascading. (1) Connecting network controllers to each processing of a failing cluster. (2) In the AIX operating
other in a succession of levels, to concentrate many system, a group of nodes within a complex.
more lines than a single level permits. (2) In
high-availability cluster multiprocessing (HACMP), cluster processor complex (CPC). In the ESS, the
cascading pertains to a cluster configuration in which unit within a cluster that provides the management
the cluster node with the highest priority for a particular function for the ESS. It consists of cluster processors,
resource acquires the resource if the primary node fails. cluster memory, and related logic.
The cluster node relinquishes the resource to the
primary node upon reintegration of the primary node command-line interface (CLI). An interface provided
into the cluster. by an operating system that defines a set of commands
and enables a user (or a script-like language) to issue
catcher. A server that service personnel use to collect these commands by typing text in response to the
and retain status data that an ESS sends to it. command prompt (for example, DOS commands or
UNIX shell commands). See also Copy Services
CCR. See channel command retry. command-line interface.
CCW. See channel command word. compact disc. An optically read disc, typically storing
approximately 660 MB. CD-ROM (compact disc
CD. See compact disc. read-only memory) refers to the read-only format used
to distribute ESS code and documentation.
CEC. See computer-electronic complex.
Glossary 145
compression. (1) The process of eliminating gaps, session. If there is only one ESS (the master ESS) in
empty fields, redundancies, and unnecessary data to the asynchronous PPRC session, no control path is
shorten the length of records or blocks. (2) Any required.
encoding that reduces the number of bits used to
represent a given message or record. (GC) control unit (CU). (1) A device that coordinates and
controls the operation of one or more input/output
computer-electronic complex (CEC). The set of devices, and synchronizes the operation of such
hardware facilities associated with a host computer. devices with the operation of the system as a whole. (2)
In Enterprise Systems Architecture/390, a storage
concurrent copy. A facility on a storage server that server with ESCON, FICON, or OEMI interfaces. The
enables a program to make a backup of a data set control unit adapts a native device interface to an I/O
while the logical volume remains available for interface that an ESA/390 host system supports. (3) In
subsequent processing. The data in the backup copy is the ESS, the portion of the ESS that supports the
frozen at the point in time that the server responds to attachment of emulated count key data devices over
the request. ESCON, FICON, or OEMI interfaces. See also cluster.
concurrent installation of licensed internal code. control-unit image. In Enterprise Systems
Process of installing licensed internal code on an ESS Architecture/390, a logical subsystem that is accessed
while applications continue to run. through an ESCON or FICON I/O interface. One or
more control-unit images exist in each control unit. Each
concurrent maintenance. Service that is performed image appears as an independent control unit, but all
on a unit while it is operational. control-unit images share a common set of hardware
facilities. The ESS can emulate 3990-3, TPF, 3990-6, or
concurrent media maintenance. Service performed
2105 control units.
on a disk drive module (DDM) without losing access to
the data. control-unit-initiated reconfiguration (CUIR). A
software mechanism that the ESS uses to request that
configure. In storage, to define the logical and
an operating system of a zSeries or S/390 host verify
physical configuration of the input/output (I/O)
that one or more subsystem resources can be taken
subsystem through the user interface that the storage
offline for service. The ESS can use this process to
facility provides for this function.
automatically vary channel paths offline and online to
consistency group. A group of volumes participating facilitate bay service or concurrent code installation.
in FlashCopy relationships in a logical subsystem, Depending on the operating system, support for this
across logical subsystems, or across Model 2105 process might be model dependent, might depend on
Enterprise Storage Servers that must be kept in a the IBM TotalStorage Enterprise Storage Server
consistent state to ensure data integrity. Subsystem Device Driver, or might not exist.
consistency group interval time. The value in Coordinated Universal Time (UTC). The international
seconds that indicates the length of time between the standard of time that is kept by atomic clocks around
formation of consistency groups. the world.
consistent copy. A copy of a data entity (a logical Copy Services CLI. See Copy Services command-line
volume, for example) that contains the contents of the interface.
entire data entity at a single instant in time.
Copy Services client. Software that runs on each
console. A user interface to a server, for example, the ESS cluster in the Copy Services server group and that
interface provided on a personal computer. See also performs the following functions:
IBM TotalStorage ESS Master Console. v Communicates configuration, status and connectivity
information to the Copy Services server
contingent allegiance. In Enterprise Systems
v Performs data-copy functions on behalf of the Copy
Architecture/390, a relationship that is created in a
Services server
control unit between a device and a channel when the
channel accepts unit-check status. The allegiance See also active Copy Services server, backup Copy
causes the control unit to guarantee access; the control Services server, and primary Copy Services server.
unit does not present the busy status to the device. The
allegiance enables the channel to retrieve sense data Copy Services command-line interface (Copy
that is associated with the unit-check status on the Services CLI). In the ESS, command-line interface
channel path associated with the allegiance. software provided with ESS Copy Services and used for
invoking Copy Services functions from host systems
control path. The route that is established from the attached to the ESS. See also command-line interface.
master ESS to the subordinate ESS when more than
one ESS participates in the asynchronous PPRC

Copy Services domain. A collection of (3380-track mode). See also count-key-data, interleave,
user-designated ESS clusters participating in Copy standard volume, and volume.
Services functions managed by a designated active
Copy Services server. See also Copy Services server, CUT. See Coordinated Universal Time.
dual-active server, and single-active server.
cyclic redundancy check (CRC). A redundancy
Copy Services server. An ESS cluster that the Copy check in which the check key is generated by a cyclic
Services administrator designates to perform the ESS algorithm. (T)
Copy Services functions. See also active Copy Services
server, backup Copy Services server, and primary Copy cylinder. A unit of storage on a CKD device with a
Services server. fixed number of tracks.
Copy Services server group. A collection of

user-designated ESS clusters participating in Copy
D
Services functions that a designated, active, Copy DA. See device adapter. See also SSA adapter.
Services server manages. A Copy Services server
group is also called a Copy Services domain. See also daisy chain. See serial connection.
active Copy Services server, backup Copy Services
server, and primary Copy Services server. DASD. See direct access storage device.
count field. The first field of a count key data (CKD) DASD fast write (DFW). A function of a storage server
record. This eight-byte field contains a four-byte track in which active write data is stored in nonvolatile cache,
address (CCHH). It defines the cylinder and head that thus avoiding exposure to data loss.
are associated with the track, and a one-byte record
number (R) that identifies the record on the track. It data availability. The degree to which data is
defines a one-byte key length that specifies the length available when needed, typically measured as a
of the record’s key field (0 means no key field). It percentage of time that the system would be capable of
defines a two-byte data length that specifies the length responding to any data request (for example, 99.999%
of the record’s data field (0 means no data field). Only available).
the end-of-file record has a data length of zero.
data compression. A technique or algorithm used to
count key data (CKD). In Enterprise Systems encode data such that the encoded result can be stored
Architecture/390, a data-record format employing in less space than the original data. The original data
self-defining record formats in which each record is can be recovered from the encoded result through a
represented by up to three fields: a count field reverse technique or reverse algorithm. See also
identifying the record and specifying its format, an compression.
optional key field that can be used to identify the data
area contents, and an optional data field that typically Data Facility Storage Management Subsystem
contains the user data. For CKD records on the ESS, (DFSMS). An operating environment that helps
the logical volume size is defined in terms of the device automate and centralize the management of storage. To
emulation mode (3390 or 3380 track format). The count manage storage, DFSMS provides the storage
field is always 8 bytes long and contains the lengths of administrator with control over data class, storage class,
the key and data fields, the key field has a length of 0 management class, storage group, and automatic class
to 255 bytes, and the data field has a length of 0 to 65 selection routine definitions.
535 or the maximum that will fit on the track. See also
data field. The optional third field of a count key data
data record.
(CKD) record. The count field specifies the length of the
CPC. See cluster processor complex. data field. The data field contains data that the program
writes.
CRC. See cyclic redundancy check.
data record. The basic unit of S/390 and zSeries
CU. See control unit. storage on an ESS, also known as a count-key-data
(CKD) record. Data records are stored on a track. The
CUIR. See control-unit initiated reconfiguration. records are sequentially numbered starting with 0. The
first record, R0, is typically called the track descriptor
custom volume. In the ESS, a volume in record and contains data that the operating system
count-key-data (CKD) format that is not a standard normally uses to manage the track. See also
volume, which means that it does not necessarily count-key-data and fixed-block architecture.
present the same number of cylinders and capacity to
its assigned logical control unit as provided by one of data set FlashCopy. An option of the Enterprise
the following standard S/390 volume types: 3390-2, Storage Server that allows a volume to participate in
3390-3, 3390-9, 3390-2 (3380-track mode), or 3390-3 multiple concurrent FlashCopy relationships at one time.
Glossary 147
data sharing. The ability of multiple host systems to DFSMS. See Data Facility Storage Management
concurrently utilize data that they store on one or more Subsystem.
storage devices. The storage facility enables configured
storage to be accessible to any, or all, attached host direct access storage device (DASD). (1) A mass
systems. To use this capability, the host program must storage medium on which a computer stores data. (2) A
be designed to support data that it is sharing. disk device.
DDM. See disk drive module. disk cage. A container for disk drives. Each disk cage
supports eight disk eight packs (64 disks).
DDM group. See disk eight pack.
disk drive. Standard term for a disk-based nonvolatile
dedicated storage. Storage within a storage facility storage medium. The ESS uses hard disk drives as the
that is configured such that a single host system has primary nonvolatile storage media to store host data.
exclusive access to the storage.
disk drive module (DDM). A field replaceable unit that
demote. To remove a logical data unit from cache consists of a single disk drive and its associated
memory. A storage server demotes a data unit to make packaging.
room for other logical data units in the cache or
because the logical data unit is not valid. The ESS must disk drive module group. See disk eight pack.
destage logical data units with active write units before
they can be demoted. disk eight pack. In the ESS, a group of eight disk
drive modules (DDMs) installed as a unit in a DDM bay.
destaging. Movement of data from an online or higher
priority to an offline or lower priority device. The ESS disk group. In the ESS, a collection of disk drives in
stages incoming data into cache and then destages it to the same SSA loop set up by the ESS to be available to
disk. be assigned as a RAID-formatted array. A disk group
can be formatted as count key data or fixed block, and
device. In Enterprise Systems Architecture/390, a disk as RAID or non-RAID, or it can be left unformatted. A
drive. disk group is a logical assemblage of eight disk drives.
Contrast with disk eight pack.
device adapter (DA). A physical component of the
ESS that provides communication between the clusters distributed file service (DFS). A service that provides
and the storage devices. The ESS has eight device data access over IP networks.
adapters that it deploys in pairs, one from each cluster.
DA pairing enables the ESS to access any disk drive DNS. See domain name system.
from either of two paths, providing fault tolerance and
domain. (1) That part of a computer network in which
enhanced availability.
the data processing resources are under common
device address. In Enterprise Systems control. (2) In TCP/IP, the naming system used in
Architecture/390, the field of an ESCON or FICON hierarchical networks. (3) A Copy Services server group,
device-level frame that selects a specific device on a in other words, the set of clusters the user designates to
control-unit image. be managed by a particular Copy Services server.
device ID. In the ESS, the unique two-digit domain name system (DNS). In TCP/IP, the server
hexadecimal number that identifies the logical device. program that supplies name-to-address translation by
mapping domain names to internet addresses. The
device interface card. A physical subunit of a storage address of a DNS server is the internet address of the
cluster that provides the communication with the server that hosts the DNS software for the network.
attached device drive modules.
dotted decimal notation. A convention used to
device number. In Enterprise Systems identify IP addresses. The notation consists of four 8-bit
Architecture/390, a four-hexadecimal-character identifier, numbers written in base 10. For example, 9.113.76.250
for example 13A0, that the systems administrator is an IP address that contains the octets 9, 113, 76, and
associates with a device to facilitate communication 250.
between the program and the host operator. The device
number is associated with a subchannel. drawer. A unit that contains multiple device drive
modules and provides power, cooling, and related
device sparing. A subsystem function that interconnection logic to make the device drive modules
automatically copies data from a failing device drive accessible to attached host systems.
module to a spare device drive module. The subsystem
maintains data access during the process. drive. (1) A peripheral device, especially one that has
addressed storage media. See also disk drive module.
DFS. See distributed file service. (2) The mechanism used to seek, read, and write
information on a storage medium.

duplex. (1) Regarding ESS Copy Services, the state A set of IBM products and services that provide a
of a volume pair after PPRC has completed the copy dynamically connected environment within an
operation and the volume pair is synchronized. (2) In enterprise.
general, pertaining to a communication mode in which
data can be sent and received at the same time. EPO. See emergency power off.
dynamic sparing. The ability of a storage server to ERDS. See error-recording data set.
move data from a failing disk drive module (DDM) to a
spare DDM while maintaining storage functions. ERP. See error recovery procedure.
error-recording data set (ERDS). On S/390 and

E zSeries hosts, a data set that records data-storage and
data-retrieval errors. A service information message
E10. The predecessor of the F10 model of the ESS. (SIM) provides the error information for the ERDS.
See also F10.
error recovery procedure (ERP). Procedures
E20. The predecessor of the F20 model of the ESS. designed to help isolate and, where possible, to recover
See also F20. from errors in equipment. The procedures are often
used in conjunction with programs that record
EBCDIC. See extended binary-coded decimal information on machine malfunctions.
interchange code.
ESA/390. See Enterprise Systems Architecture/390.
EC. See engineering change.
ESCD. See ESCON director.
ECKD. See extended count key data.
ESCON. See Enterprise System Connection.
eight pack. See disk eight pack.
ESCON channel. An S/390 or zSeries channel that
electrostatic discharge (ESD). An undesirable supports ESCON protocols.
discharge of static electricity that can damage
equipment and degrade electrical circuitry. ESCON director (ESCD). An I/O interface switch that
provides for the interconnection of multiple ESCON
emergency power off (EPO). A means of turning off interfaces in a distributed-star topology.
power during an emergency, usually a switch.
ESCON host systems. S/390 or zSeries hosts that
EMIF. See ESCON multiple image facility. attach to the ESS with an ESCON adapter. Such host
systems run on operating systems that include MVS,
enclosure. A unit that houses the components of a VSE, TPF, or versions of VM.
storage subsystem, such as a control unit, disk drives,
and power source. ESCON multiple image facility (EMIF). In Enterprise
Systems Architecture/390, a function that enables
end of file. A coded character recorded on a data LPARs to share an ESCON channel path by providing
medium to indicate the end of the medium. On a each LPAR with its own channel-subsystem image.
count-key-data direct access storage device, the
subsystem indicates the end of a file by including a EsconNet. In ESS Specialist, the label on a pseudo
record with a data length of zero. host icon that represents a host connection that uses
the ESCON protocol and that is not completely defined
engineering change (EC). An update to a machine, on the ESS. See also pseudo host and access-any
part, or program. mode.
Enterprise Storage Server. See IBM TotalStorage ESD. See electrostatic discharge.
Enterprise Storage Server.
eserver. See IBM Eserver.
Enterprise Systems Architecture/390 (ESA/390). An
IBM architecture for mainframe computers and ESS. See IBM TotalStorage Enterprise Storage Server.
peripherals. Processor systems that follow the ESA/390
architecture include the ES/9000® family. See also ESS Batch Configuration tool. A program that
z/Architecture. automatically configures an ESS. The configuration is
based on data that IBM service personnel enter into the
Enterprise Systems Connection (ESCON). (1) An program.
Enterprise Systems Architecture/390 and zSeries
computer peripheral interface. The I/O interface uses ESS Copy Services. In the ESS, a collection of
ESA/390 logical protocols over a serial interface that optional software features, with a Web-browser
configures attached units to a communication fabric. (2)
Glossary 149
interface, used for configuring, managing, and failover. In the ESS, pertaining to the process of
monitoring data-copy functions. transferring all control to a single cluster when the other
cluster in the ESS fails. See also cluster.
ESS Copy Services CLI. See Copy Services
Command-Line Interface. fast write. A write operation at cache speed that does
not require immediate transfer of data to a disk drive.
ESS Expert. See IBM TotalStorage Enterprise Storage The subsystem writes the data directly to cache, to
Server Expert. nonvolatile storage, or to both. The data is then
available for destaging. A fast-write operation reduces
ESS Master Console. See IBM TotalStorage ESS the time an application must wait for the I/O operation to
Master Console. complete.
ESSNet. See IBM TotalStorage Enterprise Storage FBA. See fixed-block architecture.
Server Network.
FC. See feature code. Note: FC is a common
ESS Specialist. See IBM TotalStorage Enterprise abbreviation for fibre channel in the industry, but the
Storage Server Specialist. ESS customer documentation library reserves FC for
feature code.
Expert. See IBM TotalStorage Enterprise Storage
Server Expert. FC-AL. See Fibre Channel-Arbitrated Loop.
extended binary-coded decimal interchange code FCP. See fibre-channel protocol.
(EBCDIC). An IBM-developed coding scheme used to
represent various alphabetic, numeric, and special FCS. See fibre-channel standard.
symbols with a coded character set of 256 eight-bit
codes. feature code (FC). A code that identifies a particular
orderable option and that is used by service personnel
extended count key data (ECKD). An extension of to process hardware and software orders. Individual
the count key data (CKD) architecture. optional features are each identified by a unique feature
code.
Extended Remote Copy (XRC). A function of a
storage server that assists a control program to fibre channel. A data-transmission architecture based
maintain a consistent copy of a logical volume on on the ANSI fibre-channel standard, which supports
another storage facility. All modifications of the primary full-duplex communication. The ESS supports data
logical volume by any attached host are presented in transmission over fiber-optic cable through its
order to a single host. The host then makes these fibre-channel adapters. See also fibre-channel protocol
modifications on the secondary logical volume. and fibre-channel standard.
extent. A continuous space on a disk that is occupied Fibre Channel-Arbitrated Loop (FC-AL). An
by or reserved for a particular data set, data space, or implementation of the fibre-channel standard that uses a
file. The unit of increment is a track. See also multiple ring topology for the communication fabric. Refer to
allegiance and parallel access volumes. American National Standards Institute (ANSI)
X3T11/93-275. In this topology, two or more
F fibre-channel end points are interconnected through a
looped interface. The ESS supports this topology.
F10. A model of the ESS featuring a single-phase
fibre-channel connection (FICON). A fibre-channel
power supply. It has fewer expansion capabilities than
communications protocol designed for IBM mainframe
the Model F20.
computers and peripherals.
F20. A model of the ESS featuring a three-phase
fibre-channel protocol (FCP). A protocol used in
power supply. It has more expansion capabilities than
fibre-channel communications with five layers that
the Model F10, including the ability to support a
define how fibre-channel ports interact through their
separate expansion enclosure.
physical links to communicate with other ports.
fabric. In fibre-channel technology, a routing structure,
fibre-channel standard (FCS). An ANSI standard for
such as a switch, receives addressed information and
a computer peripheral interface. The I/O interface
routes to the appropriate destination. A fabric can
defines a protocol for communication over a serial
consist of more than one switch. When multiple
interface that configures attached units to a
fibre-channel switches are interconnected, they are said
communication fabric. The protocol has two layers. The
to be cascaded.
IP layer defines basic interconnection protocols. The
failback. Pertaining to a cluster recovery from failover upper layer supports one or more logical protocols (for
following repair. See also failover. example, FCP for SCSI command protocols and

SBCON for ESA/390 command protocols). Refer to coordinate Withdraw FlashCopy actions only with
American National Standards Institute (ANSI) FlashCopy relationships that have matching sequence
X3.230-199x. See also fibre-channel protocol. numbers.
fibre-channel topology. An interconnection topology FRU. See field replaceable unit.

supported on fibre-channel adapters. See also
point-to-point connection, switched fabric, and arbitrated FTP. See File Transfer Protocol.
loop.
full duplex. See duplex.
FICON. See fibre-channel connection.
fuzzy copy. A function of the PPRC Extended
FiconNet. In ESS Specialist, the label on a pseudo Distance feature wherein modifications to the primary
host icon that represents a host connection that uses logical volume are performed on the secondary logical
the FICON protocol and that is not completely defined volume at a later time. The original order of update is
on the ESS. See also pseudo host and access-any not strictly maintained. See also PPRC Extended
mode. Distance.
field replaceable unit (FRU). An assembly that is

replaced in its entirety when any one of its components
G
fails. In some cases, a field replaceable unit might
GB. See gigabyte.
contain other field replaceable units. (GC)
GDPS. See Geographically Dispersed Parallel
FIFO. See first-in-first-out.
Sysplex.
File Transfer Protocol (FTP). In TCP/IP, an
Geographically Dispersed Parallel Sysplex (GDPS).
application protocol used to transfer files to and from
An S/390 multisite application- availability solution.
host computers. See also Transmission Control
Protocol/Internet Protocol. gigabyte (GB). A gigabyte of storage is 109 bytes. A
gigabyte of memory is 230 bytes.
firewall. A protection against unauthorized connection
to a computer or a data storage system. The protection group. In ESS documentation, a nickname for two
is usually in the form of software on a gateway server different kinds of groups, depending on the context. See
that grants access to users who meet authorization disk eight pack or Copy Services server group.
criteria.
first-in-first-out (FIFO). A queuing technique in which H

the next item to be retrieved is the item that has been in
the queue for the longest time. (A) HA. See host adapter.
fixed-block architecture (FBA). An architecture for HACMP. See High-Availability Cluster

logical devices that specifies the format of and access Multi-Processing.
mechanisms for the logical data units on the device.
The logical data unit is a block. All blocks on the device hard disk drive (HDD). (1) A storage medium within a
are the same size (fixed size). The subsystem can storage server used to maintain information that the
access them independently. storage server requires. (2) A mass storage medium for
computers that is typically available as a fixed disk
fixed-block device. An architecture for logical devices (such as the disks used in system units of personal
that specifies the format of the logical data units on the computers or in drives that are external to a personal
device. The logical data unit is a block. All blocks on the computer) or a removable cartridge.
device are the same size (fixed size); the subsystem
can access them independently. This is the required Hardware Configuration Data (HCD). An OS/390 and
format of the logical data units for host systems that z/OS application used to define the I/O configuration to
attach with a SCSI or fibre-channel interface. See also both the host operating system and the
fibre channel and small computer systems interface. cluster-processor complex within the channel
subsystem. The configuration program is available in
FlashCopy. An optional feature for the ESS that can three versions: stand-alone, VM/370, and MVS.
make an instant copy of data, that is, a point-in-time
copy of a volume. hardware service manager (HSM). An option on an
AS/400 or iSeries host that enables the user to display
FlashCopy sequence number. A 4-byte value passed and work with system hardware resources and to debug
as input on an Establish FlashCopy command that is input-output processors (IOP), input-output adapters
associated with the established FlashCopy relationship. (IOA), and devices.
Withdraw FlashCopy commands can use this number to
Glossary 151
HCD. See Hardware Configuration Data. In the ESS, the acronym HA is shared between home
address and host adapter. See also home address.
HDA. See head and disk assembly.
host name. The Internet address of a machine in the
HDD. See hard disk drive. network. In the ESS, the host name can be entered in
the host definition as the fully qualified domain name of
hdisk. An AIX term for storage space. the attached host system, such as
mycomputer.city.company.com, or as the subname of
head and disk assembly (HDA). The portion of an
the fully qualified domain name, for example,
HDD associated with the medium and the read/write
mycomputer. See also host system.
head.
host processor. A processor that controls all or part of
heartbeat. A status report sent at regular intervals
a user application network. In a network, the processing
from the ESS. The service provider uses this report to
unit in which the data communication access method
monitor the health of the call home process. See also
resides. See also host system.
call home, heartbeat call home record, and remote
technical assistance information network. host system. A computer, either of the mainframe
(S/390 or zSeries) or of the open-systems type, that is
heartbeat call home record. Machine operating and
connected to the ESS. S/390 or zSeries hosts are
service information sent to a service machine. These
connected to the ESS through ESCON or FICON
records might include such information as feature code
interfaces. Open-systems hosts are connected to the
information and product logical configuration
ESS by SCSI or fibre-channel interfaces.
information.
hot plug. Pertaining to the ability to add or remove a
hierarchical storage management. (1) A function in
hardware facility or resource to a unit while power is on.
storage management software, such as Tivoli Storage
Management or Data Facility Storage Management HSL. See high-speed link.
Subsystem/MVS (DFSMS/MVS), that automatically
manages free space based on the policy that the HSM. See hierarchical storage management or
storage administrator sets. (2) In AS/400 storage Hardware Service Manager.
management, an automatic method to manage and
distribute data between the different storage layers,
such as disk units and tape library devices. I
High-Availability Cluster Multi-Processing IBM Eserver. The IBM brand name for a series of
(HACMP). Software that provides host clustering, so server products that are optimized for e-commerce. The
that a failure of one host is recovered by moving jobs to products include the iSeries, pSeries, xSeries, and
other hosts within the cluster. zSeries.
high-speed link (HSL). A hardware connectivity IBM product engineering (PE). The third-level of IBM
architecture that links system processors to system service support. Product engineering is composed of
input/output buses and other system units. IBM engineers who have experience in supporting a
product or who are knowledgeable about the product.
home address (HA). A nine-byte field at the beginning
of a track that contains information that identifies the IBM TotalStorage. The brand name used to identify
physical track and its association with a cylinder. In the storage products from IBM, including the IBM
ESS, the acronym HA is shared between home address TotalStorage Enterprise Storage Server (ESS). See also
and host adapter. See also host adapter. IBM TotalStorage Enterprise Storage Server and IBM
TotalStorage Enterprise Storage Server Specialist.
hop. Interswitch connection. A hop count is the
number of connections that a particular block of data IBM TotalStorage Enterprise Storage Server (ESS).
traverses between source and destination. For example, A member of the Seascape product family of storage
data traveling from one hub over a wire to another hub servers and attached storage devices (disk drive
traverses one hop. modules). The ESS provides for high-performance,
fault-tolerant storage and management of enterprise
host. See host system. data, providing access through multiple concurrent
operating systems and communication protocols. High
host adapter (HA). A physical subunit of a storage performance is provided by multiple symmetrical
server that provides the ability to attach to one or more multiprocessors, integrated caching, RAID support for
host I/O interfaces. The Enterprise Storage Server has the disk drive modules, and disk access through a
four HA bays, two in each cluster. Each bay supports up high-speed serial storage architecture (SSA) interface.
to four host adapters.

IBM TotalStorage Enterprise Storage Server Expert initiator. A SCSI device that communicates with and
(ESS Expert). Formerly called IBM StorWatch controls one or more targets. An initiator is typically an
Enterprise Storage Server Expert, the software that I/O adapter on a host computer. A SCSI initiator is
gathers performance data from the ESS and presents it analogous to an S/390 channel. A SCSI logical unit is
through a Web browser. analogous to an S/390 device. Contrast with target.
IBM TotalStorage Enterprise Storage Server i-node. The internal structure in an AIX operating
Specialist (ESS Specialist). Software with a system that describes the individual files in the
Web-browser interface for configuring the ESS. operating system. It contains the code, type, location,
and owner of a file.
IBM TotalStorage Enterprise Storage Server Network
(ESSNet). A private network providing Web browser input/output (I/O). Pertaining to (a) input, output, or
access to the ESS. IBM installs the ESSNet software on both or (b) a device, process, or channel involved in
an IBM workstation called the IBM TotalStorage ESS data input, data output, or both.
Master Console, supplied with the first ESS delivery.
input/output configuration data set. A configuration
IBM TotalStorage ESS Master Console (ESS Master definition built by the I/O configuration program (IOCP)
Console). An IBM workstation (formerly named the and stored on disk files associated with the processor
ESSNet console) that IBM installs to provide the controller.
ESSNet facility when they install the ESS. It includes a
Web browser that provides links to the ESS user interleave. In the ESS, to automatically create two
interface, including ESS Specialist and ESS Copy striped partitions across the drives in a RAID-5 array,
Services. both of which use the count-key-data (CKD) record
format.
IBM Subsystem Device Driver (SDD). Software that
is designed to support the multipath configuration Internet Protocol (IP). In the Internet suite of
environments in the ESS. SDD resides in a host system protocols, a protocol without connections that routes
with the native disk device driver. data through a network or interconnecting networks and
acts as an intermediary between the higher protocol
ID. See identifier. layers and the physical network. The upper layer
supports one or more logical protocols (for example, a
inband FlashCopy. An option of the Enterprise SCSI-command protocol and an ESA/390 command
Storage Server that establishes and withdraws protocol). Refer to ANSI X3.230-199x. The IP acronym
FlashCopy pairs at the remote site without having a is the IP in TCP/IP. See also Transmission Control
Copy Services Web interface connection to the remote Protocol/Internet Protocol.
site.
invalidate. To remove a logical data unit from cache
incremental FlashCopy. An option of the Enterprise memory because it cannot support continued access to
Storage Server that creates a point-in-time data copy the logical data unit on the device. This removal might
without copying an entire volume for each point-in-time be the result of a failure within the storage server or a
copy. storage device that is associated with the device.
identifier (ID). A unique name or address that I/O. See input/output.
identifies things such as programs, devices, or systems.
I/O adapter (IOA). In the ESS, an input-output adapter
IML. See initial microcode load. on the PCI bus.
implicit allegiance. In Enterprise Systems IOCDS. See input/output configuration data set.
Architecture/390, a relationship that a control unit
creates between a device and a channel path when the IOCP. See I/O Configuration Program.
device accepts a read or write operation. The control
unit guarantees access to the channel program over the I/O Configuration Program (IOCP). A program that
set of channel paths that it associates with the defines to a system all the available I/O devices and
allegiance. channel paths.
initial microcode load (IML). The action of loading I/O device. An addressable read and write unit, such
microcode for a computer into that computer’s storage. as a disk drive device, magnetic tape device, or printer.
initial program load (IPL). The action of loading I/O interface. An interface that enables a host to
software into a computer, typically an operating system perform read and write operations with its associated
that controls the computer. peripheral devices.
I/O Priority Queueing. A facility in the Workload

Manager of OS/390 that enables the system
Glossary 153
administrator to set priorities for queueing I/Os from least recently used (LRU). (1) The algorithm used to
different system images. See also multiple allegiance identify and make available the cache space that
and parallel access volume. contains the least-recently used data. (2) A policy for a
caching algorithm that chooses to remove from cache
I/O processor (IOP). Controls input-output adapters the item that has the longest elapsed time since its last
and other devices. access.
I/O sequential response time. The time an I/O LED. See light-emitting diode.
request is queued in processor memory waiting for
previous I/Os to the same volume to complete. LIC. See licensed internal code.
IOSQ. See I/O sequential response time. licensed internal code (LIC). Microcode that IBM
does not sell as part of a machine, but licenses to the
IP. See Internet Protocol. customer. LIC is implemented in a part of storage that is
not addressable by user programs. Some IBM products
IPL. See initial program load. use it to implement functions as an alternate to
hard-wired circuitry.
iSeries. An IBM Eserver product that emphasizes
integration. It is the successor to the AS/400 family of LIFO. See last-in first-out.
servers.
light-emitting diode (LED). A semiconductor chip that
J gives off visible or infrared light when activated.
link address. On an ESCON or FICON interface, the

Java Virtual Machine (JVM). A software
portion of a source or destination address in a frame
implementation of a central processing unit (CPU) that
that ESCON or FICON uses to route a frame through
runs compiled Java code (applets and applications).
an ESCON or FICON director. ESCON or FICON
(GC)
associates the link address with a specific switch port
JVM. See Java Virtual Machine. that is on the ESCON or FICON director. Equivalently, it
associates the link address with the channel subsystem
or control unit link-level functions that are attached to
K the switch port.
KB. See kilobyte. link-level facility. The ESCON or FICON hardware

and logical functions of a control unit or channel
key field. The second (optional) field of a count key subsystem that allow communication over an ESCON or
data record. The key length is specified in the count FICON write interface and an ESCON or FICON read
field. The key length determines the field length. The interface.
program writes the data in the key field and use the key
field to identify or locate a given record. The subsystem local area network (LAN). A computer network
does not use the key field. located on a user’s premises within a limited geographic
area.
kilobyte (KB). (1) For processor storage, real, and
virtual storage, and channel volume, 210 or 1024 bytes. local e-mail. An e-mail configuration option for storage
(2) For disk storage capacity and communications servers that are connected to a host-system network
volume, 1000 bytes. that does not have a domain name system (DNS)
server.
Korn shell. Interactive command interpreter and a
command programming language. logical address. On an ESCON or FICON interface,
the portion of a source or destination address in a frame
KPOH. See thousands of power-on hours. used to select a specific channel-subsystem or
control-unit image.
L logical block address (LBA). The address assigned
by the ESS to a sector of a disk.
LAN. See local area network.
logical control unit (LCU). See control-unit image.
last-in first-out (LIFO). A queuing technique in which
the next item to be retrieved is the item most recently logical data unit. A unit of storage that is accessible
placed in the queue. (A) on a given device.
LBA. See logical block address. logical device. The facilities of a storage server (such
as the ESS) associated with the processing of I/O
LCU. See logical control unit. operations directed to a single host-accessible emulated

I/O device. The associated storage is referred to as a logical volume manager (LVM). A set of system
logical volume. The logical device is mapped to one or commands, library routines, and other tools that allow
more host-addressable units, such as a device on an the user to establish and control logical volume storage.
S/390 I/O interface or a logical unit on a SCSI I/O The LVM maps data between the logical view of storage
interface, such that the host initiating I/O operations to space and the physical disk drive module.
the I/O-addressable unit interacts with the storage on
the associated logical device. longitudinal redundancy check (LRC). (1) A method
of error checking during data transfer that involves
logical partition (LPAR). In Enterprise Systems checking parity on a row of binary digits that are
Architecture/390, a set of functions that create the members of a set that forms a matrix. Longitudinal
programming environment in which more than one redundancy check is also called a longitudinal parity
logical partition (LPAR) is established on a processor. check. (2) In the ESS, a mechanism that the ESS uses
An LPAR is conceptually similar to a virtual machine for locating errors. The LRC checks the data as it
environment except that the LPAR is a function of the progresses from the host, through the ESS controller,
processor. Also, the LPAR does not depend on an into the device adapter, and to the array.
operating system to create the virtual machine
environment. longwave laser adapter. A connector used between a
host and the ESS to support longwave fibre-channel
logical path. (1) The relationship between a channel communication.
image and a control-unit image that designates the
physical path to be used for device-level loop. The physical connection between a pair of
communications between these images. The logical device adapters in the ESS. See also device adapter.
path is established as part of the channel and
control-unit initialization procedures by the exchange of LPAR. See logical partition.
link-level frames. (2) In the ESS with the Peer-to-Peer
LRC. See longitudinal redundancy check.
Remote Copy (PPRC) feature, the relationship between
a source logical subsystem (LSS) and a target LSS that LRU. See least recently used.
is created over a physical path through the
interconnection fabric used for PPRC functions. An LSS LSS. See logical subsystem.
is a primary control unit, which performs the functions of
a channel image. LUN. See logical unit number.
logical subsystem (LSS). In the ESS, a topological LVM. See logical volume manager.
construct that consists of a group of up to 256 logical
devices. An ESS can have up to 16 CKD-formatted
logical subsystems (4096 CKD logical devices) and also
M
up to 16 fixed-block logical subsystems (4096
machine level control (MLC). A database that
fixed-block logical devices). The logical subsystem
contains the EC level and configuration of products in
facilitates configuration of the ESS and might have other
the field.
implications relative to the operation of certain functions.
There is a one-to-one mapping between a CKD logical machine reported product data (MRPD). Product
subsystem and an S/390 control-unit image. data gathered by a machine and sent to a destination
For S/390 or zSeries hosts, a logical subsystem such as an IBM support server or RETAIN. These
represents a logical control unit (LCU). Each control-unit records might include such information as feature code
image is associated with only one logical subsystem. information and product logical configuration
See also control-unit image. information.
logical unit. In open systems, a logical disk drive. mainframe. A computer, usually in a computer center,
with extensive capabilities and resources to which other
logical unit number (LUN). In the SCSI protocol, a computers may be connected so that they can share
unique number used on a SCSI bus to enable it to facilities. (T)
differentiate between a maximum of eight separate
devices, each of which is a logical unit. maintenance analysis procedure (MAP). A hardware
maintenance document that gives an IBM service
logical volume. The storage medium associated with representative a step-by-step procedure for tracing a
a logical disk drive. A logical volume typically resides on symptom to the cause of a failure.
one or more storage devices. The ESS administrator
defines this unit of storage. The logical volume, when Management Information Base (MIB). (1) A collection
residing on a RAID-formatted array, is spread over the of objects that can be accessed by means of a network
drives in the array. management protocol. (GC) (2) In the ESS, the MIB
record conforms to the Open Systems Interconnection
(OSI) standard defined by the International Organization
Glossary 155
for Standardization (ISO) for the exchange of Micro Channel architecture (MCA). The rules that
information. See also simple network management define how subsystems and adapters use the Micro
protocol. Channel bus in a computer. The architecture defines the
services that each subsystem can or must provide.
MAP. See maintenance analysis procedure.
Microsoft Internet Explorer (MSIE). Web browser
Master Console. See IBM TotalStorage ESS Master software manufactured by Microsoft.
Console.
migration. In the ESS, the replacement of a system or
master ESS. The ESS that controls the creation of subsystem with a different type of system or subsystem,
consistency groups in the asynchronous PPRC session. such as replacing a SCSI host adapter with a
The master ESS sends commands to subordinate fibre-channel host adapter. When used in the context of
ESSs. An ESS can be a master for only one data migration regarding the ESS, the transfer of data
asynchronous PPRC session. Contrast with subordinate from one storage facility to another, such as from a
ESS. 3390 to the ESS.
maximum consistency group drain time. The value MIH. See missing-interrupt handler.
in seconds that indicates the maximum time that writes
from the local site are delayed to the remote site while mirrored pair. Two units that contain the same data.
the current consistency group is being formed at the The system refers to them as one entity.
remote site. When this time is exceeded, the current
attempt to form a consistency group is ended and mirroring. In host systems, the process of writing the
another attempt is started. If this time is exceeded five same data to two disk units within the same auxiliary
times, this maximum time is ignored on the next attempt storage pool at the same time.
to form a consistency group. The default value is the
larger of four minutes or two times the consistency miscellaneous equipment specification (MES). IBM
group interval time if this value is set to zero. field-installed change to a machine.
maximum coordination time. The value in missing-interrupt handler (MIH). An MVS and
milliseconds that indicates the maximum time that is MVS/XA facility that tracks I/O interrupts. MIH informs
allowed for host I/O to be delayed during the the operator and creates a record whenever an
coordination of the primary volumes of an asynchronous expected interrupt fails to occur before a specified
PPRC session. The default is 50 milliseconds if this elapsed time is exceeded.
value is set to zero.
MLC. See machine level control.
MB. See megabyte.
mobile solutions terminal (MoST). The mobile
MCA. See Micro Channel architecture. terminal used by service personnel.
MDM. See Multiple Device Manager. mode conditioning patch cable. A cable that
converts a single-mode signal from a longwave adapter
mean time between failures (MTBF). (1) A projection into a light signal that is appropriate for multimode fibre.
of the time that an individual unit remains functional. Another mode conditioning patch cable is required at
The time is based on averaging the performance, or the terminating end of the multimode fibre to convert the
projected performance, of a population of statistically signal back to a single-mode signal for a longwave
independent units. The units operate under a set of adapter.
conditions or assumptions. (2) For a stated period in the
life of a functional unit, the mean value of the lengths of Model 100. A 2105 Model 100, often simply referred to
time between consecutive failures under stated as a Mod 100, is an expansion enclosure for the ESS.
conditions. (I) (A) See also 2105.
medium. For a storage facility, the disk surface on MoST. See mobile solutions terminal.
which data is stored.
MRPD. See machine reported product data.
megabyte (MB). (1) For processor storage, real and
MSA. See multiport serial adapter.
virtual storage, and channel volume, 220 or 1 048 576
bytes. (2) For disk storage capacity and MSIE. See Microsoft Internet Explorer.
communications volume, 1 000 000 bytes.
MTBF. See mean time between failures.
MES. See miscellaneous equipment specification.
multiple allegiance. An ESS hardware function that is
MIB. See management information base. independent of software support. This function enables
multiple system images to concurrently access the

same logical volume on the ESS as long as the system
images are accessing different extents. See also extent
O
and parallel access volumes.
octet. In Internet Protocol addressing, one of the four
Multiple Device Manager (MDM). A component of the parts of a 32-bit integer presented in dotted decimal
IBM TotalStorage Productivity Center that allows notation. See also dotted decimal notation.
administrators to configure, manage, and monitor the
OEMI. See original equipment manufacturer’s
performance of SAN storage devices from a single
information.
console.
open system. A system whose characteristics comply
multiple relationship FlashCopy. An option of the
with standards made available throughout the industry
Enterprise Storage Server that creates backup copies
and that therefore can be connected to other systems
from one source to multiple targets by simultaneously
complying with the same standards. Applied to the ESS,
establishing multiple FlashCopy relationships.
such systems are those hosts that connect to the ESS
multiple virtual storage (MVS). Implies MVS/390, through SCSI or FCP protocols. See also small
MVS/XA, MVS/ESA, and the MVS element of the computer system interface and fibre-channel protocol.
OS/390 operating system.
organizationally unique identifier (OUI). An
multiplex. The action of transmitting simultaneously. IEEE-standards number that identifies an organization
with a 24-bit globally unique assigned number
multiport serial adapter (MSA). An adapter on the referenced by various standards. OUI is used in the
ESS Master Console that has multiple ports to which family of 802 LAN standards, such as Ethernet and
ESSs can be attached. Token Ring.
multiprocessor. A computer that includes two or more original equipment manufacturer’s information
processors that have common access to a main (OEMI). A reference to an IBM guideline for a
storage. For the ESS, the multiprocessors operate in computer peripheral interface. The interface uses
parallel. ESA/390 logical protocols over an I/O interface that
configures attached units in a multidrop bus topology.
MVS. See multiple virtual storage.
OS/390. The IBM operating system that includes and
integrates functions that many IBM software products
N (including the MVS operating system) previously
provided for the IBM S/390 family of enterprise servers.
name server. A server that stores names of the
participating ESS clusters. OS/400. The IBM operating system that runs the IBM
AS/400 and iSeries Eserver families of servers.
Netfinity. IBM Intel-processor-based server;
predecessor to the IBM xSeries server. OUI. See organizationally unique identifier.
Netscape Navigator. Web browser software

manufactured by Netscape. P
network manager. A program or group of programs panel. The formatted display of information that
that is used to monitor, manage, and diagnose the appears on a display screen.
problems of a network. (GC)
parallel access volume (PAV). An advanced function
node. The unit that is connected in a fibre-channel of the ESS that enables OS/390 and z/OS systems to
network. An ESS is a node in a fibre-channel network. issue concurrent I/O requests against a count key data
logical volume by associating multiple devices of a
non-RAID. A disk drive set up independently of other single control-unit image with a single logical device. Up
disk drives and not set up as part of a disk eight pack to to eight device addresses can be assigned to a PAV.
store data using the redundant array of disks (RAID) The PAV function enables two or more concurrent write
data-striping methodology. operations to the same logical volume, as long as the
write operations are not to the same extents. See also
nonremovable medium. A recording medium that extent, I/O Priority Queueing, and multiple allegiance.
cannot be added to or removed from a storage device.
parity. A data checking scheme used in a computer
nonvolatile storage (NVS). In the ESS, memory that system to ensure the integrity of the data. The RAID
stores active write data to avoid data loss in the event implementation uses parity to re-create data if a disk
of a power loss. drive fails.
NVS. See nonvolatile storage.
Glossary 157
path group. In ESA/390 architecture, a set of channel power-on self test (POST). A diagnostic test that
paths that are defined to a control unit as being servers or computers run when they are turned on.
associated with a single logical partition (LPAR). The
channel paths are in a group state and are online to the PPRC. See Peer-to-Peer Remote Copy.
host. See also logical partition.
PPRC Extended Distance. An optional feature for the
path group identifier. In ESA/390 architecture, the ESS that maintains a fuzzy copy of a logical volume on
identifier that uniquely identifies a given logical partition the same ESS or on another ESS. In other words, all
(LPAR). The path group identifier is used in modifications that any attached host performs on the
communication between the LPAR program and a primary logical volume are also performed on the
device. The identifier associates the path group with secondary logical volume at a later point in time. The
one or more channel paths, thereby defining these original order of update is not strictly maintained. See
paths to the control unit as being associated with the also Peer-to-Peer Remote Copy (PPRC) and
same LPAR. See also logical partition. synchronous PPRC.
PAV. See parallel access volume. PPRC-XD. See PPRC Extended Distance.
PCI. See peripheral component interconnect. predictable write. A write operation that can cache
without knowledge of the existing format on the
PDU. See protocol data unit. medium. All write operations on FBA DASD devices are
predictable. On CKD DASD devices, a write operation is
PE. See IBM product engineering. predictable if it does a format write operation for the first
data record on the track.
Peer-to-Peer Remote Copy (PPRC). A function of a
storage server that constantly updates a secondary primary control unit. The ESS to which a PPRC
copy of a logical volume to match changes made to a primary device is physically attached.
primary logical volume. The primary and secondary
volumes can be on the same storage server or on primary Copy Services server. One of two Copy
separate storage servers. See also synchronous PPRC Services servers in a Copy Services server group. The
and PPRC Extended Distance. primary Copy Services server is the active Copy
Services server until it fails; it is then replaced by the
peripheral component interconnect (PCI). An backup Copy Services server. A Copy Services server is
architecture for a system bus and associated protocols software that runs in one of the two clusters of an ESS
that supports attachments of adapter cards to a system and performs data-copy operations within that group.
backplane. See active Copy Services server and backup Copy
Services server.
physical path. A single path through the I/O
interconnection fabric that attaches two units. For Copy primary device. One of the devices in a dual-copy or
Services, this is the path from a host adapter on one remote-copy volume pair. All channel commands to the
ESS (through cabling and switches) to a host adapter logical volume are directed to the primary device. The
on another ESS. data on the primary device is duplicated on the
secondary device. See also secondary device.
pinned data. Data that is held in cache until either an
error condition is corrected and it can be moved to disk product engineering. See IBM product engineering.
storage or until the data is discarded by a host
command. Pinned data conditions can only occur on an program. On a computer, a generic term for software
ESS Model 800 during fast-write or dual-copy functions. that controls the operation of the computer. Typically,
the program is a logical assemblage of software
point-to-point connection. A fibre-channel topology modules that perform multiple related tasks.
that enables the direct interconnection of ports. See
also arbitrated loop and switched fabric. program-controlled interruption. An interruption that
occurs when an I/O channel fetches a channel
port. In the ESS, a physical connection on a host command word with the program-controlled interruption
adapter to the cable that connects the ESS to hosts, flag on.
switches, or another ESS. The ESS uses SCSI and
ESCON host adapters that have two ports per adapter, program temporary fix (PTF). A temporary solution
and fibre-channel host adapters that have one port. See to, or bypass of, a problem diagnosed by IBM as the
also ESCON, fibre channel, host adapter, and small result of a defect in a current unaltered release of a
computer system interface. licensed program. (GC)
POST. See power-on self test. promote. To add a logical data unit to cache memory.

protected volume. In AS/400, a disk storage device reserves spare disk drives when it assigns arrays to a
that is protected from data loss by RAID techniques. An device adapter pair (DA pair). See also device adapter,
AS/400 host does not mirror a volume configured as a RAID 5, and redundant array of independent disks.
protected volume, while it does mirror all volumes
configured as unprotected volumes. The ESS, however, random access. A mode of accessing data on a
can be configured to indicate that an AS/400 volume is medium in a manner that requires the storage device to
protected or unprotected and give it RAID protection in access nonconsecutive storage locations on the
either case. medium.
protocol data unit (PDU). A unit of data specified in rank. See array.
the protocol of a given layer and consisting of protocol
control information for the layer and, possibly, user data redundant array of independent disks (RAID). A
for the layer. methodology of grouping disk drives for managing disk
storage to insulate data from a failing disk drive.
pSeries. The product name of an IBM Eserver
product that emphasizes performance. It is the remote technical assistance information network
successor to the RS/6000 family of servers. (RETAIN). The initial service tracking system for IBM
service support, which captures heartbeat and
pseudo host. A host connection that is not explicitly call-home records. See also support catcher and
defined to the ESS and that has access to at least one support catcher telephone number.
volume that is configured on the ESS. The FiconNet
pseudo host icon represents the FICON protocol. The REQ/ACK. See request for acknowledgment and
EsconNet pseudo host icon represents the ESCON acknowledgment.
protocol. The pseudo host icon labelled Anonymous
request for acknowledgment and acknowledgment
represents hosts connected through the FCP protocol.
(REQ/ACK). A cycle of communication between two
Anonymous host is a commonly used synonym for
data transport devices for the purpose of verifying the
pseudo host. The ESS adds a pseudo host icon only
connection, which starts with a request for
when the ESS is set to access-any mode. See also
acknowledgment from one of the devices and ends with
access-any mode.
an acknowledgment from the second device. The REQ
PTF. See program temporary fix. and ACK signals help to provide uniform timing to
support synchronous data transfer between an initiator
PV Links. Short for Physical Volume Links, an and a target. The objective of a synchronous data
alternate pathing solution from Hewlett-Packard that transfer method is to minimize the effect of device and
provides for multiple paths to a volume, as well as static cable delays.
load balancing.
reserved allegiance. In Enterprise Systems
Architecture/390, a relationship that is created in a
R control unit between a device and a channel path when
the device completes a Sense Reserve command. The
R0. See track-descriptor record. allegiance causes the control unit to guarantee access
(busy status is not presented) to the device. Access is
rack. See enclosure. over the set of channel paths that are associated with
the allegiance; access is for one or more channel
RAID. See redundant array of independent disks.
programs until the allegiance ends.
RAID is also commonly expanded to redundant array of
inexpensive disks. See also array. RETAIN. See remote technical assistance information
network.
RAID 5. A type of RAID that optimizes cost-effective
performance while emphasizing use of available
capacity through data striping. RAID 5 provides fault S
tolerance for up to two failed disk drives by distributing
parity across all the drives in the array plus one parity S/390. IBM enterprise servers based on Enterprise
disk drive. The ESS automatically reserves spare disk Systems Architecture/390 (ESA/390). S/390 is the
drives when it assigns arrays to a device adapter pair currently accepted shortened form of the original name
(DA pair). See also device adapter, RAID 10, and System/390.
redundant array of independent disks.
S/390 storage. (1) Storage arrays and logical volumes
RAID 10. A type of RAID that optimizes high that are defined in the ESS as connected to S/390
performance while maintaining fault tolerance for up to servers. This term is synonymous with count-key-data
two failed disk drives by by striping volume data across storage. (2) In ESS documentation, when noted, the
several disk drives and mirroring the first set of disk term can refer to both S/390 and zSeries storage. See
drives on an identical set. The ESS automatically also zSeries storage.
Glossary 159
SAID. See system adapter identification number. sequential access. A mode of accessing data on a
medium in a manner that requires the storage device to
SAM. See sequential access method. access consecutive storage locations on the medium.
SAN. See storage area network. sequential access method (SAM). An access method
for storing, deleting, or retrieving data in a continuous
SBCON. See Single-Byte Command Code Sets sequence based on the logical order of the records in
Connection. the file.
screen. The physical surface of a display device upon serial connection. A method of device interconnection
which information is shown to users. for determining interrupt priority by connecting the
interrupt sources serially.
SCSI. See small computer system interface.
serial storage architecture (SSA). An IBM standard
SCSI device. A disk drive connected to a host through
for a computer peripheral interface. The interface uses a
an I/O interface using the SCSI protocol. A SCSI device
SCSI logical protocol over a serial interface that
is either an initiator or a target. See also initiator and
configures attached targets and initiators in a ring
small computer system interface.
topology. See also SSA adapter.
SCSI-FCP. Synonym for fibre-channel protocol, a
server. (1) A host that provides certain services to
protocol used to transport data between an
other hosts that are referred to as clients. (2) A
open-systems host and a fibre-channel adapter on an
functional unit that provides services to one or more
ESS. See also fibre-channel protocol and small
clients over a network. (GC)
computer system interface.
service boundary. A category that identifies a group
SCSI host systems. Host systems that are attached
of components that are unavailable for use when one of
to the ESS with a SCSI interface. Such host systems
the components of the group is being serviced. Service
run on UNIX, OS/400, Windows NT, Windows 2000, or
boundaries are provided on the ESS, for example, in
Novell NetWare operating systems.
each host bay and in each cluster.
SCSI ID. A unique identifier assigned to a SCSI device
service information message (SIM). A message sent
that is used in protocols on the SCSI interface to
by a storage server to service personnel through an
identify or select the device. The number of data bits on
S/390 operating system.
the SCSI bus determines the number of available SCSI
IDs. A wide interface has 16 bits, with 16 possible IDs. service personnel. A generalization referring to
individuals or companies authorized to service the ESS.
SDD. See IBM Subsystem Device Driver.
The terms service provider, service representative, and
Seascape architecture. A storage system architecture IBM service support representative (SSR) refer to types
that IBM developed for open-systems servers and S/390 of service personnel. See also service support
and zSeries host systems. It provides storage solutions representative.
that integrate software, storage management, and
service processor. A dedicated processing unit used
technology for disk, tape, and optical storage.
to service a storage facility.
secondary control unit. The ESS to which a PPRC
service support representative (SSR). Individuals or
secondary device is physically attached.
a company authorized to service the ESS. This term
secondary device. One of the devices in a dual-copy also refers to a service provider, a service
or remote-copy volume pair that contains a duplicate of representative, or an IBM service support representative
the data on the primary device. Unlike the primary (SSR). An IBM SSR installs the ESS.
device, the secondary device might only accept a
session. A collection of volumes within a logical
limited subset of data. See also primary device.
subsystem that are managed together during the
self-timed interface (STI). An interface that has one creation of consistent copies of data. All volumes in a
or more conductors that transmit information serially session must transfer their data successfully to the
between two interconnected units without requiring any remote site before the increment can be called
clock signals to recover the data. The interface performs complete.
clock recovery independently on each serial data stream
shared storage. In an ESS, storage that is configured
and uses information in the data stream to determine
so that multiple hosts can concurrently access the
character boundaries and inter-conductor
storage. The storage has a uniform appearance to all
synchronization.
hosts. The host programs that access the storage must
have a common model for the information on a storage

device. The programs must be designed to handle the spatial reuse. A feature of serial storage architecture
effects of concurrent access. that enables a device adapter loop to support many
simultaneous read/write operations. See also serial
shortwave laser adapter. A connector used between storage architecture.
host and ESS to support shortwave fibre-channel
communication. Specialist. See IBM TotalStorage Enterprise Storage
Server Specialist.
SIM. See service information message.
SSA. See serial storage architecture.
Simple Network Management Protocol (SNMP). In
the Internet suite of protocols, a network management SSA adapter. A physical adapter based on serial
protocol that is used to monitor routers and attached storage architecture. SSA adapters connect disk drive
networks. SNMP is an application layer protocol. modules to ESS clusters. See also serial storage
Information on devices managed is defined and stored architecture.
in the application’s Management Information Base
(MIB). (GC) See also management information base. SSID. See subsystem identifier.
simplex volume. A volume that is not part of a SSR. See service support representative.
FlashCopy, XRC, or PPRC volume pair.
stacked status. In Enterprise Systems
Single-Byte Command Code Sets Connection Architecture/390, the condition when the control unit is
(SBCON). The ANSI standard for the ESCON or in a holding status for the channel, and the last time the
FICON I/O interface. control unit attempted to present the status, the channel
responded with the stack-status control.
small computer system interface (SCSI). A standard
hardware interface that enables a variety of peripheral stage operation. The operation of reading data from
devices to communicate with one another. (GC) the physical disk drive into the cache.
smart relay host. A mail relay or mail gateway that staging. To move data from an offline or low-priority
has the capability to correct e-mail addressing device back to an online or higher priority device,
problems. usually on demand of the system or on request of the
user.
SMIT. See System Management Interface Tool.
standard volume. In the ESS, a volume that emulates
SMP. See symmetrical multiprocessor. one of several S/390 volume types, including 3390-2,
3390-3, 3390-9, 3390-2 (3380-track mode), or 3390-3
SNMP. See Simple Network Management Protocol. (3380-track mode), by presenting the same number of
cylinders and capacity to the host as provided by the
SNMP agent. A server process that resides on a native S/390 volume type of the same name.
network node and is responsible for communicating with
managers regarding that node. The node is represented STI. See self-timed interface.
as a managed object, which has various fields or
variables that are defined in the appropriate MIB. storage area network. A network that connects a
company’s heterogeneous storage resources.
SNMP manager. A managing system that runs a
managing application or suite of applications. These storage complex. Multiple storage facilities.
applications depend on Management Information Base
(MIB) objects for information that resides on the storage device. A physical unit that provides a
managed system. Managers generate requests for this mechanism to store data on a given medium such that it
MIB information, and an SNMP agent on the managed can be subsequently retrieved. See also disk drive
system responds to these requests. A request can module.
either be the retrieval or modification of MIB information.
storage facility. (1) A physical unit that consists of a
software transparency. Criteria applied to a storage server integrated with one or more storage
processing environment that states that changes do not devices to provide storage capability to a host computer.
require modifications to the host software in order to (2) A storage server and its attached storage devices.
continue to provide an existing function.
storage server. A physical unit that manages attached
spare. A disk drive on the ESS that can replace a storage devices and provides an interface between
failed disk drive. A spare can be predesignated to allow them and a host computer by providing the function of
automatic dynamic sparing. Any data preexisting on a one or more logical subsystems. The storage server can
disk drive that is invoked as a spare is destroyed by the provide functions that the storage device does not
dynamic sparing copy process. provide. The storage server has one or more clusters.
Glossary 161
striping. A technique that distributes data in bit, byte, system adapter identification number (SAID). In the
multibyte, record, or block increments across multiple ESS, the unique identification number automatically
disk drives. assigned to each ESS host adapter for use by ESS
Copy Services.
subagent. An extension to an SNMP agent that
permits a user to dynamically add, or in some cases System Management Interface Tool (SMIT). An
replace, additional management variables in the local interface tool of the AIX operating system for installing,
MIB, thereby providing a means of extending the range maintaining, configuring, and diagnosing tasks.
of information that network managers can access. See
also agent. System Modification Program. A program used to
install software and software changes on MVS systems.
subchannel. A logical function of a channel subsystem
associated with the management of a single device.
T
subordinate ESS. The ESS that receives commands
from the master ESS and is specified when an TAP. See Telocator Alphanumeric Protocol.
asynchronous PPRC session is started. The
target. A SCSI device that acts as a subordinate to an
subordinate ESS forms consistency groups and
initiator and consists of a set of one or more logical
performs other asynchronous PPRC processing. A
units, each with an assigned logical unit number (LUN).
subordinate ESS can only be controlled by one ESS
The logical units on the target are typically I/O devices.
master. Contrast with master ESS.
A SCSI target is analogous to an S/390 control unit. A
Subsystem Device Driver. See IBM TotalStorage SCSI initiator is analogous to an S/390 channel. A SCSI
Enterprise Storage Server Subsystem Device Driver. logical unit is analogous to an S/390 device. See also
small computer system interface.
subsystem identifier (SSID). A number that uniquely
identifies a logical subsystem within a computer TB. See terabyte.
installation.
TCP/IP. See Transmission Control Protocol/Internet
support catcher telephone number. The telephone Protocol.
number that connects the support catcher server to the
Telocator Alphanumeric Protocol (TAP). An industry
ESS to receive a trace or dump package. See also
standard protocol for the input of paging requests.
support catcher and remote technical assistance
information network. terabyte (TB). (1) Nominally, 1 000 000 000 000
bytes, which is accurate when speaking of bandwidth
switched fabric. A fibre-channel topology in which
and disk storage capacity. (2) For ESS cache memory,
ports are interconnected through a switch. Fabric
processor storage, real and virtual storage, a terabyte
switches can also be interconnected to support
refers to 240 or 1 099 511 627 776 bytes.
numerous ports on a single network. See also arbitrated
loop and point-to-point connection. terminal emulator. In the ESS, a function of the ESS
Master Console that allows it to emulate a terminal.
symmetrical multiprocessor (SMP). An
implementation of a multiprocessor computer consisting thousands of power-on hours (KPOH). A unit of time
of several identical processors configured in a way that used to measure the mean time between failures
any subset of the set of processors is capable of (MTBF).
continuing the operation of the computer. The ESS
contains four processors set up in SMP mode. time sharing option (TSO). An operating system
option that provides interactive time sharing from remote
synchronous PPRC. A function of a storage server terminals.
that maintains a consistent copy of a logical volume on
the same storage server or on another storage server. TotalStorage. See IBM TotalStorage.
All modifications that any attached host performs on the
primary logical volume are also performed on the TPF. See transaction processing facility.
secondary logical volume. See also Peer-to-Peer
Remote Copy and PPRC Extended Distance. track. A unit of storage on a CKD device that can be
formatted to contain a number of data records. See also
synchronous write. A write operation whose home address, track-descriptor record, and data record.
completion is indicated after the data has been stored
on a storage device. track-descriptor record (R0). A special record on a
track that follows the home address. The control
System/390. See S/390. program uses it to maintain certain information about
the track. The record has a count field with a key length

of zero, a data length of 8, and a record number of 0. by definition. The data in an unprotected volume can be
This record is sometimes referred to as R0. mirrored. Also referred to as an unprotected device.
transaction processing facility (TPF). A upper-layer protocol. The layer of the Internet
high-availability, high-performance IBM operating Protocol (IP) that supports one or more logical protocols
system, designed to support real-time, (for example, a SCSI-command protocol and an
transaction-driven applications. The specialized ESA/390 command protocol). Refer to ANSI
architecture of TPF is intended to optimize system X3.230-199x.
efficiency, reliability, and responsiveness for data
communication and database processing. TPF provides UTC. See Coordinated Universal Time.
real-time inquiry and updates to a large, centralized
database, where message length is relatively short in utility device. The ESA/390 term for the device used
both directions, and response time is generally less than with the Extended Remote Copy facility to access
three seconds. Formerly known as the Airline Control information that describes the modifications performed
Program/Transaction Processing Facility (ACP/TPF). on the primary copy.
Transmission Control Protocol (TCP). A

communications protocol used in the Internet and in any
V
network that follows the Internet Engineering Task Force virtual machine facility. A virtual data processing
(IETF) standards for internetwork protocol. TCP machine that appears to the user to be for the exclusive
provides a reliable host-to-host protocol between hosts use of that user, but whose functions are accomplished
in packet-switched communications networks and in by sharing the resources of a shared data processing
interconnected systems of such networks. It uses the system. An alternate name for the VM/370 IBM
Internet Protocol (IP) as the underlying protocol. operating system.
Transmission Control Protocol/Internet Protocol vital product data (VPD). Information that uniquely
(TCP/IP). (1) A combination of data-transmission defines the system, hardware, software, and microcode
protocols that provide end-to-end connections between elements of a processing system.
applications over interconnected networks of different
types. (2) A suite of transport and application protocols VM. The root name of several IBM operating systems,
that run over the Internet Protocol. (GC) See also such as VM/XA, VM/ESA, VM/CMS, and z/VM. See
Internet Protocol and Transmission Control Protocol. also virtual machine facility.
transparency. See software transparency. volume. In Enterprise Systems Architecture/390, the
information recorded on a single unit of recording
TSO. See time sharing option. medium. Indirectly, it can refer to the unit of recording
medium itself. On a nonremovable-medium storage
turbo processor. In the ESS, a faster multiprocessor
device, the term can also indirectly refer to the storage
that has six processors with common access to the
device associated with the volume. When multiple
main storage.
volumes are stored on a single storage medium
transparently to the program, the volumes can be
U referred to as logical volumes.
UFS. UNIX filing system. volume label. In the ESS, a unique identifier that a
user assigns to a logical volume.
Ultra-SCSI. An enhanced small computer system
interface. VPD. See vital product data.
unconfigure. To delete the configuration. VSE/ESA. IBM operating system, the letters of which
represent virtual storage extended/enterprise systems
unit address. In Enterprise Systems Architecture/390, architecture.
the address associated with a device on a given control
unit. On ESCON or FICON interfaces, the unit address
is the same as the device address. On OEMI interfaces,
W
the unit address specifies a control unit and device pair
Web Copy Services. See ESS Copy Services.
on the interface.
worldwide node name (WWNN). A unique 64-bit
unprotected volume. An AS/400 term that indicates
identifier for a host that contains a fibre-channel port.
that the AS/400 host recognizes the volume as an
See also worldwide port name.
unprotected device, even though the storage resides on
a RAID-formatted array and is, therefore, fault tolerant worldwide port name (WWPN). A unique 64-bit
identifier associated with a fibre-channel adapter port. It
Glossary 163
is assigned in an implementation- and
protocol-independent manner.
write hit. A write operation in which the requested

data is in the cache.
write penalty. The performance impact of a classical

RAID-5 write operation.
WWPN. See worldwide port name.
X
XD. See PPRC Extended Distance.
XRC. See Extended Remote Copy.
xSeries. The product name of an IBM Eserver

product that emphasizes industry-standard server
scalability and self-managing server technologies. It is
the successor to the Netfinity family of servers.
Z
z/Architecture. An IBM architecture for mainframe
computers and peripherals. The IBM Eserver zSeries
family of servers uses the z/Architecture architecture. It
is the successor to the S/390 and 9672 family of
servers. See also Enterprise Systems Architecture/390.
z/OS. An operating system for the IBM Eserver

product line that supports 64-bit real storage.
zSeries. (1) An IBM Eserver family of servers that

emphasizes near-zero downtime. (2) IBM enterprise
servers based on z/Architecture.
zSeries storage. Storage arrays and logical volumes

that are defined in the ESS as connected to zSeries
servers. See also S/390 storage.

Index
Numerics artwork (continued)
ESS Copy Services server domain connections 16,
524-byte sector 118
111
7133 drawer
ESS Master Console connections 12
attaching to an ESS 131
expansion enclosure 4
Model 020 requirements 132
Model 750 base enclosure; front and rear views 3
Model 40 requirements 133
reserving loops for 131
Models E10, E20, F10, and F20 base enclosure;
reuse 131
front and rear views 3
Asynchronous Cascading PPRC 42
Asynchronous Peer-to-Peer Remote Copy (PPRC)
A description 42
access Failover/Failback 43
ESS Copy Services 12 attaching
ESS Specialist 12 7133 drawers 131
MIB 100 additional ESSs to the ESS Master Console 53
accessibility 135 authorization feature codes for advanced functions 75,
adapter 77
mode for Ethernet 98 availability
adapter mode for Ethernet 97 features 21
adapters, host open-systems hosts features 25
ESCON 66 S/390 and zSeries hosts 27
Fibre-channel 66 availability, performance, and data integrity features 21
SCSI 66
address
cluster 97
default gateway 97
B
bidirectional mirroring 35
e-mail 99
ESS Copy Services server 112
ESSNet workstation 98
Internet 97
C
internet protocol (IP) 110 cable
name server 97 connection to the ESSNet 11
advanced functions cutout locations 83
arrays across loops 25, 59 Ethernet 53
Copy Services 31 power 48
ESS Copy Services 31 power requirements 92
Extended Remote Copy 43 remote power-control attachment 52
feature codes 73 cables, host attachment
FlashCopy 37 ESCON 69
parallel access volumes 44 Fibre channel 69
Peer-to-Peer Remote Copy 39 SCSI 69
PPRC Failover and Failback Modes 41 cache
reserve loops 59 feature codes 46
S/390 and zSeries hosts 43 options 1
allegiance, multiple 28 performance features 24
allocated storage 14 call home 103, 105
altitude for an ESS 91 call-back
analog telephone line 80, 94 password 95
annual renewal for Standby CoD program 57 telephone number 105
Application Programming Interface (API) 18 calls, enable incoming 103
Arbo Crate 81 Canadian compliance statement 139
array, RAID 5 22 capacity
arrays across loops 25, 59 cache 46
artwork calculation 62
cable cutout and door clearance, Model 100 84 data storage 2
cable cutout and door clearance, Models E10, F10, disk eight-pack conversion 65
E20, F20, 750, and 800 83 effective 62

capacity (continued) configuration (continued)
floor loading 87 modem 103
Standby CoD options 56 pager 101
caution notice Peer-to-Peer Remote Copy (PPRC) 35
Enterprise Storage Server (ESS) weight 81 planning 45
changes SNMP 100
configuration 73 TCP/IP 97
engineering 81 time zone 96
channel director 6, 8 configuring with ESS Specialist 13
class A compliance statement, Taiwan 141 connecting
clearance to ESS Web Copy Services 16
door 83 to the ESS Master Console 12
service 87 connection
CLI (command-line interface) 15 extension cord 50
CLI (command-line interface) for Copy Services 33 modem 94
cluster remote support 94
host name 115 Web 10
Internet address 115 connectors
cluster host name 97 power cable 93
command-line interface (CLI) 15 power cord 80
command-line interface (CLI) for Copy Services 33 consistency group support with FlashCopy 38
common information model consumption, power 90
information 18 control-unit initiated reconfiguration (CUIR)
communication enable 106
ESS Copy Services 16 support by the ESS 28
overview 95 control, remote power 94
planning for 95 convenience cord. See extension cord. 94
resources work sheet conversion
ESS 121 disk eight-pack capacity 65
ESS Copy Services 127 ESSNet console to an ESS Master Console 110
ESS Copy Services without DNS 129 converting
Communication Resources work sheet disk eight-pack capacity 65
form for ESS Master Console 125 ESSNet console to an ESS Master Console 110
form for the ESS 121 converting your ESSNet console to an ESS Master
forms for ESS Copy Services 127 Console 11
guidelines for completing for ESS Copy cooling the ESS 87
Services 110 Copy Services
guidelines for completing for the ESS 96 access 12
guidelines for completing for the ESS Master command-line interface (CLI) 33
Console 106 communication 16
communications statement 139 description 15
community name, SNMP 101 disaster recovery considerations 116
comparison of ESS features by host interface 8 disaster recovery planning 34
compliance statement enable 112
Canadian 139 enable ESS Copy Services without DNS work
European community 139 sheet 129
German 140 enable ESS Copy Services work sheet 127
Industry Canada 139 enable without DNS 116
Japanese 141 enabling 113
Korean 141 guidelines for the Communication Resources work
radio frequency energy 139 sheet 110
Taiwan class A 141 I/O interface 33
components, ESS 19 interfaces 15
Concurrent Copy 44 overview 32
concurrent maintenance 25 planning the site configuration 34
configuration planning Web site 31
changes 13, 73 server address 112
date 96 server domain 16, 32
e-mail 99 task planning 36
features 54 user requirements 33
logical 13 Web-based interface 32

cord disk
convenience 50 eight pack
extension 50, 94 capacity calculation 62
country or region group capacity conversion 65
extension cords 50 feature intermix 62
modems 53 group 22
cover removal for narrow door 83 installation sequence 64
crate, Arbo 81 mounting kit 58
CUIR (control-unit initiated reconfiguration) sizes 55
enable 106 Standby CoD features 56
support by the ESS 28 failure 23
customer pager 101 flexible-capacity options 54
cutout locations 83 non-RAID group 23
predictive failure analysis 24
speed (rpm) 55
D volume consolidation 28
data disk capacity
integrity, availability, and performance features 21 features 54
migration disk drive module (DDM)
IBM service 120 524-byte sector 118
MVS environments 119 capacity conversion 65
open-systems hosts 117 eight pack group 22
planning 117 eight-pack mounting kit 58
S/390 and zSeries hosts 119 failure 23
VM environments 119 flexible-capacity options 54
rate for modem 103 installation sequence 64
sharing 26 non-RAID group 23
storage capacity predictive failure analysis 24
Model F10 and F20 DDM support 2 reformatting existing 118
transfer protocol for tape and disk drives 4 sizes 55
Data Set FlashCopy 37 spare 23
date configuration 96 spare upgrade 57
daylight savings time 96 speed (rpm) 55
DDM (disk drive module) drawer, 7133
524-byte sector 118 attaching to an ESS 131
capacity conversion 65 Model 020 requirements 132
eight pack group 22 Model 40 requirements 133
eight-pack mounting kit 58 reserving loops for 131
failure 23 reuse 131
flexible-capacity options 54
installation sequence 64
non-RAID group 23 E
predictive failure analysis 24 e-mail
reformatting existing 118 addresses 100
sizes 55 configuration 99
spare 23 destinations 100
speed (rpm) 55 earthquake preparedness 85
default gateway address eight pack, disk
ESS Master Console TCP/IP 108 capacity calculation 62
ESSNet TCP/IP 98 capacity conversion 65
TCP/IP 97 feature intermix 62
destinations, e-mail 100 installation sequence 64
device mounting kit 58
loop 23 sizes 55
dimensions of the Enterprise Storage Server (ESS) 81 Standby CoD features 56
director, channel 6, 8 electronic emission notices 139
disability 135 elimination of LSS constraint with FlashCopy 38
disaster recovery, planning for 116 enable
disaster recovery, planning site configurations 34 e-mail 104
ESS Copy Services work sheet 113
ESS Specialist 103
Index 167
enable (continued) equipment
incoming calls 103 requirements 79
local e-mail 100 supplied for authorized service personnel 80
modem outgoing calls 103 supplied for you 79
pager messages 104 that you provide 80
remote IBM Product Engineering sign on 105 ESCON (Enterprise Systems Connection Architecture)
smart relay host 100 host systems 6
Enable ESS Copy Services without DNS work sheet ESCON host adapter 66
form 129 ESS (Enterprise Storage Server)
guidelines for completing 116 advanced functions 31
Enable ESS Copy Services work sheet altitude 91
form 127 annual renewal for Standby CoD storage 57
guidelines for completing 112 API 18
enclosure, expansion 4 application programming interface 18
enclosures availability features 21
features 54 BTU per hour 91
energy savings 92 command-line interface (CLI) 15
engineering changes 81 common information model 18
Enterprise Storage Server (ESS) comparison of features by host interface 8
advanced functions 31 components 19
altitude 91 dimensions 81
annual renewal for Standby CoD storage 57 energy savings 92
API 18 ESS Specialist 14
application programming interface 18 exhaust capacity 91
availability features 21 Expert 16
BTU per hour 91 failover 24
command-line interface (CLI) 15 functions 19
common information model 18 host systems supported by 4
comparison of features by host interface 8 interfaces 10
components 19 introduction 1
dimensions 81 noise level 91
energy savings 92 overview 1
ESS Specialist 14 power requirements 90
exhaust capacity 91 redundant storage 24
Expert 16 service clearance requirements 87
failover 24 service interface 17
functions 19 shipping 81
host systems supported by 4 Standby CoD storage 57
interfaces 10 storage requirements 92
introduction 1 unloading 81
noise level 91 weight 81
overview 1 ESS API
power requirements 90 Microsoft Volume Shadow Copy Service 19
redundant storage 24 ESS Application Programming Interface (API) 18
service clearance requirements 87 ESS Copy Services
service interface 17 access 12
shipping 81 command-line interface (CLI) 33
Standby CoD storage 57 communication 16
storage requirements 92 Communication Resources work sheet 127
unloading 81 description 15
weight 81 disaster recovery considerations 116
Enterprise Storage Server Network (ESSNet) disaster recovery planning 34
description 10 enable 112
ESS Master Console site requirements 89 enable ESS Copy Services without DNS work
TCP/IP information 107 sheet 129
workstation configuration 98 enable ESS Copy Services work sheet 127
Enterprise Systems Connection Architecture (ESCON) enable without DNS 116
host systems 6 enabling 113
environment enhancements 15
information 91 guidelines for the Communication Resources work
operating 91 sheet 110

ESS Copy Services (continued) expansion enclosure
I/O interface 33 cooling 87
interfaces 15 feature codes 59
overview 32 Expert, ESS 16
planning the site configuration 34 Extended Remote Copy (XRC)
planning Web site 31 description 43
server address 112 using for outages 44
server domain 16, 32 extension cord
task planning 36 feature codes 50
user requirements 33 groups by country or region 50
Web-based interface 32 outlet power 94
ESS Master Console
additional attachments 52
applications 10 F
Communication Resources work sheet 125 Failover and Failback Modes with PPRC 41
configuration 106 failover protection 24, 26
configuration work sheet 125 fast dual write 24
connection to ESS administrative functions 10 FCC (Federal Communications Commission)
connections 12 statement 139
converting from an ESSNet console 110 feature codes
guidelines for completing the work sheet 106 7133 attachment 131
installation requirements 89 advanced functions 73
power cables for remote-support by modem annual renewal for Standby CoD program 57
group 53 authorization for advanced function capacity 75, 77
power outlets 47 cache 46
remote support 11 DDM mounting kit 58
remote support hardware 52 disk drive module (DDM) sizes 55
remote-support connection 94 disk eight-pack sizes 55
ESS Model 750 eight-pack mounting kit 58
base enclosure 3 ESS Master Console 52
cache 1 ESS Model 800
feature codes for advanced functions 77 cache 46
processor 1 expansion enclosure 59
ESS Model 800 processor options 45
base enclosure 3 remote power control 51
cache 1, 46 weight-reduced shipment 46
data storage capacity 2 expansion enclosure 59
disk eight-pack mounting kit 58 extension cords 50
expansion enclosure 59 flexible-capacity options 54
feature codes for advanced functions 75 for Model 750 77
processor 1 for Model 800 75
processor options 45 for Models F20, F10, E20, and E10 77
reduced shipping weight option 46 input voltage 47
remote power control 51 operator-panel language 72
ESS Specialist power cable 48
access 12 power cables for remote-support by modem
description 13 group 53
ESSNet (Enterprise Storage Server Network) remote power control 51
description 10 software 73
ESS Master Console site requirements 89 United States-government orders 45
TCP/IP information 107 Federal Communications Commission (FCC)
workstation configuration 98 statement 139
ESSNet console, converting to an ESS Master fibre connection (FICON)
Console 110 attached host systems 7
Ethernet fibre-channel
adapter mode 97, 98 host systems 5
cable for ESS Master Console 53 LUN access control 106
network 97 protocol intermix 6, 8
switch 11 Fibre-channel host adapter 67
European Community Compliance statement 139 fibre-channel protocol
expander, telephone 94 FICON 7
Index 169
fibre-channel protocol (continued) guidelines for completing work sheets (continued)
SCSI-FCP 5 Enable ESS Copy Services without DNS work
FICON (fibre connection) sheet 116
attached host systems 7
FICON host Adapter 67
figures H
cable cutout and door clearance, Model 100 84 HACMP (high-availability cluster multiprocessing) 21
cable cutout and door clearance, Models E10, F10, heartbeat interval for call home 105
E20, F20, 750, and 800 83 high-availability cluster multiprocessing (HACMP) 21
ESS Copy Services server domain connections 111 host adapter
ESS Master Console connections 12 ESCON 66
expansion enclosure 4 Fibre-channel 66
Model 750 base enclosure; front and rear views 3 SCSI 66
Model 800 base enclosure; front and rear views 3 host attachment cables
Models E10, E20, F10, and F20 base enclosure; ESCON 69
front and rear views 3 Fibre channel 69
fire suppression 87 SCSI 69
five-hundred twenty-four byte sector format 118 host systems
fixed-byte sector 118 ESCON attached 6
FlashCopy fibre channel 5
consistency group support 38 FICON attached 7
Data Set FlashCopy 37 S/390 and zSeries 6
description 37 SCSI 5
elimination of LSS constraint 38 SCSI-FCP attached 5
FlashCopy Inband over PPRC 37 supported by the ESS 4
improvement in FlashCopy establish time 38
Incremental FlashCopy 38
Multiple Relationship FlashCopy 38 I
FlashCopy Inband over PPRC 37 IBM Agreement for Licensed Internal Code 80
flexible-capacity options 54 IBM Subsystem Device Driver description 26
floor-loading capacity 87 illustrations
forms, communication cable cutout and door clearance, Model 100 84
ESS 121 cable cutout and door clearance, Models E10, F10,
ESS Copy Services 127 E20, F20, 750, and 800 83
ESS Master Console 125 ESS Copy Services server domain connections 16,
frequencies, power 90 111
functions 19 ESS Master Console connections 12
expansion enclosure 3
G Model 800 base enclosure; front and rear views 3
generic traps 100 Models E10, E20, F10, and F20 base enclosure;
German compliance statement 140 front and rear views 3
government orders, United States 45 improvement in FlashCopy establish time 38
graphics incoming calls, enable 103
cable cutout and door clearance, Model 100 84 Incremental FlashCopy 38
cable cutout and door clearance, Models E10, F10, Industry Canada compliance statement 139
E20, F20, 750, and 800 83 information message, service 102
ESS Copy Services server domain connections 16, information, common information model 18
111 input voltage
ESS Master Console connections 12 feature codes 47
expansion enclosure 4 requirements 90
Model 750 base enclosure; front and rear views 3 installation
Model 800 base enclosure; front and rear views 3 ESS Master Console 89
Models E10, E20, F10, and F20 base enclosure; planning 79
front and rear views 3 installing ESCON adapters for PPRC connectivity 39
guidelines for completing work sheets installing FCP adapters for PPRC connectivity 39
Communication-Resources work sheet for the installing the IBM Subsystem Device Driver on your
ESS 96 open-systems hosts 20
Communication-Resources work sheet for the ESS interface
Master Console 106 command line 14, 32
Enable ESS Copy Services 112 ESS Copy Services 15

interface (continued) LVM (logical volume manager) for data migration 118
ESS Expert 16
ESS Master Console 11
ESS Specialist 13 M
ESSNet 10 machine reported product data (MRPD) record
network 97 destination 104
security 10 maintenance, concurrent 25
service 17 management information base (MIB) access 100
Web 10, 12 Master Console
internet protocol (IP) address 110 additional attachments 52
introduction to the Enterprise Storage Server (ESS) 1 applications 10
IP (internet protocol) address 110 Communication Resources work sheet 125
configuration 106
configuration work sheet 125
J connection to ESS administrative functions 10
Japanese Voluntary Control Council for Interference connections 12
(VCCI) Class A statement 141 guidelines for completing the work sheet 106
installation requirements 89
power cables for remote-support by modem
K group 53
Korean Ministry of Information and Communication power outlets 47
(MIC) statement 141 remote support 11
remote support hardware 52
remote-support connection 94
L MDM 16
language for the operator panel 72 memory capacity 46
legal notices 137 messages, service information 102
LIC (licensed internal code) 80 MIB (management information base) access 100
for the ESS 73 Microsoft Volume Shadow Copy Service 19
licensed internal code (LIC) 80 migrating data, planning for 117
for the ESS 73 MIH (missing-interrupt handler) setting 7
Limited Warranty statement 80 mirroring, bidirectional 35
Linux operating system missing-interrupt handler (MIH) setting 7
CLI support 15 mobile solutions terminal (MoST) 17
diskettes for the ESS Master Console 80 model
ESS Master Console 52 7133
ESS Master Console microcode 110 Model 020 requirements 132
Intel-based servers 6 Model D40 requirements 133
S/390 7 ESS
loading capacity, floor 87 Model 750 cache 1
loading ramp at your site 81 Model 750 feature codes for advanced
local modem telephone number 105 functions 77
locations, cable cutout 83 Model 800 cache 1
logic card for remote power control 51 Model 800 DDM support 2
logical Model 800 feature codes for advanced
configuration 13 functions 75
configuration changes 73 Model 800 processor options 45
configuration planning 133 Model 800 shipping options 46
redundancy check (LRC) 25 Model E10 and E20 cache 2
subsystem (LSS) Model E10 and E20 DDM support 2
description 28 Model E10 and E20 shortwave adapter
unit number (LUN) support 5
change serial number 106 Model E20 superseded by Model 800 2
volume manager (LVM) for data migration 118 Model F10 and F20 cache 1
longitudinal redundancy check (LRC) 25 Model F10 and F20 DDM support 2
loop Model F10, F20, and 800 shortwave and
device 23, 131 longwave adapter support 5
reserved 131 Model F20 superseded by Model 800 2
LRC (longitudinal redundancy check) 25 Models E20 and 800 data storage capacity 2
LUN (logical unit number) Model 100 expansion enclosure 131
change serial number 106
Index 171
modem operating systems (continued)
configuration 103 SCSI-FCP attached 5
connection 94 supported by the ESS 5
data rate 103 z/OS and z/VM 7
enable outgoing calls 103 operator panel, language 72
groups by country or region 53 optional
remote-support connection 94 one-year warranty 73
telephone number 101 replacement power cords 49
MoST (mobile solutions terminal) 17 options
mounting kit, disk eight pack 58 cache 46
MRPD (machine reported product data) record ESS Model 800 processor 45
destination 104 Model 800 shipping 46
MSA (multiport-serial adapter) connection 52 Standby CoD disk eight packs 56
multiple allegiance 28 orders, United States-government 45
Multiple Device Manager 16 outage 44
Multiple Relationship FlashCopy 38 outgoing calls, enable 103
multiport-serial adapter (MSA) connection 52 outlet
MVS environments, planning data migration 119 customer requirements 81
power for the ESS 47
power for the ESS Master Console 47
N power for the extension cord 94
name server remote service power 94
domain name 97, 98, 107 overview
internet address 97, 98, 107 communication 95
name, SNMP community 101 Enterprise Storage Server 1
narrow door cover removal 83
network
Ethernet 97 P
interface 97 pager, customer information 101
mask 97, 107 parallel access volume (PAV)
non-RAID disk group 23 description 44
nonvolatile storage (NVS) using with the ESS 44
description 24 parity check, longitudinal. See longitudinal redundancy
fast write 19 check 25
for Models E10, E20, F10, F20, 750, and 800 19 password, call-back 105
notifications, trap 101 PAV (parallel access volume)
NVS (nonvolatile storage) description 44
description 24 using with the ESS 44
fast write 19 Peer-to-Peer Remote Copy (PPRC)
for Models E10, E20, F10, F20, 750, and 800 19 asynchronous 42
Asynchronous Cascading PPRC 42
benefits of using PPRC over fibre channel 42
O configuration 35
on demand features 20 description 39
one-year warranty, optional 73 example of an operating environment 34
open-systems hosts Extended Distance 40
fibre channel 5 Failover and Failback Modes 41
migrating data 117 planning the tasks 36
SCSI 5 PPRC over fibre channel 42
operating environment primary and secondary server requirements 39
example for Peer-to-Peer Remote Copy (PPRC) 34 requirements 39
while in storage 92 synchronous 39
with power on or off 91 perforated tiles 87
operating systems performance, availability, and data integrity features 21
ESCON attached 6 physical configuration
FICON attached 7 planning 45
Linux 110 pictures
Linux, OS/390, TPF, VM/ESA, and VSE/ESA 7 cable cutout and door clearance, Model 100 84
open-systems hosts 5 cable cutout and door clearance, Models E10, F10,
planning data migration for 117 E20, F20, 750, and 800 83
SCSI attached 5

pictures (continued) PPRC over fibre channel 42
ESS Copy Services server domain connections 16, predictive failure analysis, DDM 24
111 processor options 45
ESS Master Console connections 12 product-specific SNMP trap 100
expansion enclosure 4 protection, failover 24
Model 750 base enclosure; front and rear views 3 protocol
Model 800 base enclosure; front and rear views 3 attachment types 4
Models E10, E20, F10, and F20 base enclosure; data-transfer for tape and disk drives 4
front and rear views 3
planning
an outage 44 R
communication 95 radio frequency energy compliance statement 139
data migration RAID (redundant array of inexpensive disks)
for MVS environments 119 description 22
for open-systems hosts 117 RAID-5 implementation 22
for S/390 and zSeries hosts 119 redundant array of inexpensive disks (RAID)
for VM environments 119 description 22
to an ESS 117 RAID-5 implementation 22
ESS Copy Services tasks 36 redundant storage 24
ESS physical configuration 45 reformatting existing DDMs (disk drive modules) 118
for disaster recovery 34 relative humidity 91
installation of an ESS 79 remote
installation of an ESS Master Console 89 access authority 107
physical configuration 45 copy 39
power extended copy 43
cable power control 94
connectors 80, 93 power control logic card 51
feature codes 48 power-control attachment cable 52
remote support 52 service
requirements 92 call home 103
consumption 90 settings 106
feature codes for input voltage 47 sign on 105
for the extension cord 94 support
frequencies 90 connection 94
input voltage 90 ESS Master Console 11
outlets 81, 94 features 51
remote hardware for the ESS Master Console 52
control cable 52 power cables 52
control interfaces 94 telephone number 104
service support 94 removal
remote control covers for narrow door 83
ESS Model 800 51 renewal, Standby CoD program 57
Models E10, E20, F10, and F20 51 requirements
requirements for the ESS 47, 90 attaching a 7133 Model 020 132
single phase 49 attaching a 7133 Model D40 133
supply input requirements 48 attaching a Model 100 with 7133 drawers 131
three phase 49 equipment 79
uninterruptible 47 ESS Copy Services user 33
PPRC (Peer-to-Peer Remote Copy) ESS Master Console installation 89
asynchronous 42 ESS Master Console site 89
configuration 35 floor loading 87
description 39 input voltages 90
example of an operating environment 34 power cable connectors 93
Extended Distance 40 power frequencies 90
Failover and Failback Modes 41 service clearance 87
planning the tasks 36 site 81
primary and secondary server requirements 39 reserve loops 59
requirements 39 reserved loops 131
synchronous 39
using ESCON adapters 39
using FCP adapters 39
Index 173
S Standby Capacity on Demand program 57
Standby CoD Annual Renewal 57
S/390
Standby CoD program 20, 57
advanced functions 43
statement of compliance
availability features 27
Canada 139
Concurrent Copy support 44
European 139
control-unit initiated reconfiguration (CUIR) 28
Federal Communications Commission 139
data migration 119
Japan 141
disk-volume consolidation support 28
Korean Ministry of Information and Communication
host systems 6
(MIC) 141
multiple allegiance facility 28
Taiwan 141
operating systems 6
Statement of Limited Warranty 80
parallel access volume (PAV) 44
storage
Time Sharing Option (TSO) support 37
cache 46
TPF operating systems 22
environment 92
saving energy 92
on demand 57
SCSI (Small Computer System Interface)
Standby CoD 57
supported host systems 5
Standby CoD disk eight packs 56
SCSI host adapter 66
storing the Enterprise Storage Server (ESS) 92
SCSI-FCP
Subsystem Device Driver (SDD)
attached host systems 5
description 26
SCSI-FCP host adapter 67
subsystem, logical 28
SDD (Subsystem Device Driver)
support
description 26
ESS Master Console 11
sector, fixed byte 118
hardware for the ESS Master Console 52
security, Web connection 10
remote power control 51
server
support catcher telephone number 104
domain
Synchronous Peer-to-Peer Remote Copy (PPRC)
connections 111
description 39
definition 32
SysContact, SNMP 101
work sheet entries 112
SysLocation, SNMP 101
service
systems
clearance 87
S/390 and zSeries host 6
data migration 120
SCSI host 5
information message (SIM) 102
interface 17
personnel
equipment for 80
T
remote connection 94 Taiwan class A compliance statement 141
remote settings 106 TCP/IP configuration 97
seventy-one thirty-three drawer 131 telephone
sharing data 26 analog line 80, 94
shipping 46, 81 call-back number 105
side clearance for ESS models 88 expander 94
SIM (service information message) 102 remote number 104
Simple Network Management Protocol (SNMP) support catcher 104
configuration 100 temperature range 91
site tiles, perforated 87
requirements for the ESS 81 time zone configuration 96
switching with PPRC Failover and Failback trap
Modes 41 notifications 101
site for the ESS 87 SNMP 100
Small Computer System Interface (SCSI)
supported host systems 5
smart relay host 100 U
SNMP (Simple Network Management Protocol) uninterruptible power supply 47
configuration 100 United States-government orders 45
software, S/390 and zSeries 6 UNIX systems, data sharing 26
spare upgrades 57 unloading the Enterprise Storage Server (ESS) 81
Specialist, ESS using XRC for an outage 44
access 12
description 13

V
VM environments, planning data migration 119
voltage, feature codes 47
voltage, input 90
volume consolidation 28
W
warranty, limited 80
warranty, optional one year 73
Web browser
connection security 10
interface 12
Microsoft Internet Explorer (MSIE) 12
Netscape Navigator 12
weight caution 81
weight-reduced shipments of the ESS 46
who should use this guide xiii
Windows systems, data sharing 26
work sheet
Communication Resources for ESS Copy
Services 127
Communication Resources for the ESS 121
Communication Resources for the ESS Master
Console 125
ESS Copy Services with DNS 127
ESS Copy Services without DNS 129
Work sheet for ESS Copy Services configuration 112
workstation, ESSNet 89
X
XRC (Extended Remote Copy)
description 43
using for outages 44
Z
zSeries
advanced functions 43
availability features 27
Concurrent Copy support 44
control-unit initiated reconfiguration (CUIR) 28
data migration 119
disk-volume consolidation support 28
host systems 6
multiple allegiance facility 28
operating systems 6
parallel access volume (PAV) 44
SCSI-FCP support 9
Time Sharing Option (TSO) support 37
TPF operating systems 22
Index 175
Readers’ Comments — We’d Like to Hear from You
Publication No. GC26-7444-06
Overall, how satisfied are you with the information in this book?
Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Overall satisfaction h h h h h
How satisfied are you that the information in this book is:
Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h
Please tell us how we can improve this book:
Thank you for your responses. May we contact you? h Yes h No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.
Name Address
Company or Organization
Phone No.
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
GC26-7444-06 Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines Corporation

Information Development
Department 61C
9032 South Rita Road
Tucson, Arizona 85775-4401
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
GC26-7444-06 Along Line

Printed in USA
GC26-7444-06
Spine information:
IBM TotalStorage Enterprise

Storage Server ESS Introduction and Planning Guide

IBM Total Storage ESS Introduction and Planning Guide

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

IBM Total Storage ESS Introduction and Planning Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

IBM TotalStorage Enterprise Storage Server

Introduction and Planning Guide

Introduction and Planning Guide

Seventh Edition (May 2004)

Safety and environmental notices . . . . . . . . . . . . . . . . . xi

About this guide . . . . . . . . . . . . . . . . . . . . . . . xiii

Summary of Changes . . . . . . . . . . . . . . . . . . . . . xxv

© Copyright IBM Corp. 1999, 2004 iii

Chapter 3. Planning the physical configuration . . . . . . . . . . . . 45

Chapter 4. Installation planning . . . . . . . . . . . . . . . . . . 79

iv ESS Introduction and Planning Guide

Chapter 5. Planning ESS communications . . . . . . . . . . . . . . 95

Chapter 6. Planning data migration . . . . . . . . . . . . . . . . 117

Appendix A. Communication Resources work sheet . . . . . . . . . 121

Appendix B. Communication Resources work sheet for the ESS Master

Appendix C. Communication Resources work sheets for ESS Copy

Appendix E. Accessibility . . . . . . . . . . . . . . . . . . . . 135

vi ESS Introduction and Planning Guide

© Copyright IBM Corp. 1999, 2004 vii

© Copyright IBM Corp. 1999, 2004 ix

© Copyright IBM Corp. 1999, 2004 xi

Who should use this guide

© Copyright IBM Corp. 1999, 2004 xiii

xiv ESS Introduction and Planning Guide

Other IBM publications

About this guide xv

xvi ESS Introduction and Planning Guide

About this guide xvii

xviii ESS Introduction and Planning Guide

About this guide xix

xx ESS Introduction and Planning Guide

Ordering IBM publications

IBM publications center

Publications notification system

About this guide xxi

Type of Storage Information Web Site

Click Storage Virtualization.

xxii ESS Introduction and Planning Guide

How to send your comments

About this guide xxiii

Summary of Changes for GC26-7444-06 IBM TotalStorage Enterprise

The following section summarizes the changes to that information.

Summary of Changes for GC26-7444-05 IBM TotalStorage Enterprise

The following sections summarize the changes to that information.

Summary of Changes for GC26-7444-04 IBM TotalStorage Enterprise

The following sections summarize the changes to that information.

© Copyright IBM Corp. 1999, 2004 xxv

xxvi ESS Introduction and Planning Guide

Overview of the IBM TotalStorage Enterprise Storage Server

The ESS models support the following features:

© Copyright IBM Corp. 1999, 2004 1

The large-capacity DDMs, in conjunction with DDM intermix support, provide an

2 ESS Introduction and Planning Guide

Front View Rear View

Figure 3. ESS expansion enclosure: front and rear views

Host systems that the ESS supports

A comparison of ESS features by host-interface type follows the overview sections

4 ESS Introduction and Planning Guide

SCSI-attached open-systems hosts

SCSI-FCP attached host systems

ESCON-attached host systems

6 ESS Introduction and Planning Guide

Consult your IBM storage specialist to obtain additional information.