Digital PDFs

EK-HSG80-UG-B01

July 1998

576 pages

Original

4.8MB

Document:	HSG80 Array Controller ACS Version 8.2 User's Guide
Order Number:	EK-HSG80-UG
Revision:	B01
Pages:	576
Original Filename:

OCR Text

DIGITAL
HSG80 Array Controller ACS Version 8.2
EK-HSG80-UG. B01
Digital Equipment Corporation
Maynard, Massachusetts

User’s Guide

July 1998
While Digital Equipment Corporation believes the information included in this manual is correct as of the date of
publication, it is subject to change without notice. DIGITAL makes no representations that the interconnection of its
products in the manner described in this document will not infringe existing or future patent rights, nor do the
descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software
in accordance with the description. No responsibility is assumed for the use or reliability of firmware on equipment
not supplied by DIGITAL or its affiliated companies. Possession, use, or copying of the software or firmware
described in this documentation is authorized only pursuant to a valid written license from DIGITAL, an authorized
sublicensor, or the identified licensor.
Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are
licensed to the U.S. Government with DIGITAL’s standard commercial license and, when applicable, the rights in
DFAR 252.227 7015, “Technical Data—Commercial Items.”
© Digital Equipment Corporation, 1998.
Printed in U.S.A.
All rights reserved.
DIGITAL, DIGITAL UNIX, DECconnect, HSZ, StorageWorks, VMS, OpenVMS, and the DIGITAL logo are
trademarks of Digital Equipment Corporation.
UNIX is a registered trademark in the United States and other countries exclusively through X/Open Company Ltd.
Windows NT is a trademark of the Microsoft Corporation. Sun is a registered trademark of Sun Microsystems, Inc.
Hewlett-Packard and HP–UX are registered trademarks of the Hewlett-Packard Company. IBM and AIX are
registered trademarks of International Business Machines Corporation. All other trademarks and registered
trademarks are the property of their respective owners.
This equipment has been tested and found to comply 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 manuals, may 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. Restrictions apply to the use of
the local-connection port on this series of controllers; failure to observe these restrictions may result in harmful
interference. Always disconnect this port as soon as possible after completing the setup operation. Any changes or
modifications made to this equipment may void the user's authority to operate the equipment.
Warning!
This is a Class A product. In a domestic environment this product may cause radio interference in which case the
user may be required to take adequate measures.
Achtung!
Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen verantwortlich ist.
Avertissement!
Cet appareil est un appareil de Classe A. Dans un environnement résidentiel cet appareil peut provoquer des brouillages radioélectriques. Dans ce cas, il peut être demandé à l’ utilisateur de prendre les mesures appropriées.

iii

Preface
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Electrostatic Discharge Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Component Precaution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Maintenance Port Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx
Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Required Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxii
Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Chapter 1 General Description
The HSG80 Array Controller Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–2
Summary of HSG80 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–4
The HSG80 Array Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–7
Operator Control Panel
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–13
Maintenance Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14
Utilities and Exercisers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–14
Cache Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–18
Caching Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–20
Fault-Tolerance for Write-Back Caching . . . . . . . . . . . . . . . . . . . . . . . . . . .1–21
External Cache Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–28
Charging Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–29

Chapter 2 Configuring an HSG80 Array Controller
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–2
Configuration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–2
Configuring an HSG80 Array Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–3
Setting the PVA Module ID Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–6
Establishing a Local Connection to the Controller . . . . . . . . . . . . . . . . . . . . . . . .2–7
Selecting a Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–10
Using Transparent Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–10
Using Multiple-Bus Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–11
Enabling Mirrored Write-Back Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–12

Selecting a Cache Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Fault-Tolerance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Backing up Power with a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Connecting the Subsystem to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Connecting a Dual-Redundant Configuration to the Host . . . . . . . . . . . . . . 2–16

Chapter 3 Creating Storagesets
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Planning and Configuring Storagesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
Creating a Storageset and Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
Determining Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Choosing a Storageset Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Using Stripesets to Increase I/O Performance . . . . . . . . . . . . . . . . . . . . . . . . 3–8
Using Mirrorsets to Ensure Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Using RAIDsets to Increase Performance and Availability . . . . . . . . . . . . . 3–15
Using Striped Mirrorsets for Highest Performance and Availability . . . . . . 3–17
Cloning Data for Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–19
Backing Up Your Subsystem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–23
Saving Subsystem Configuration Information to a Single Disk . . . . . . . . . 3–23
Saving Subsystem Configuration Information to Multiple Disks . . . . . . . . 3–23
Saving Subsystem Configuration Information to a Storageset . . . . . . . . . . 3–24
Controller and Port Worldwide Names (Node IDs) . . . . . . . . . . . . . . . . . . . . . . 3–26
Restoring Worldwide Names (Node IDs) . . . . . . . . . . . . . . . . . . . . . . . . . . 3–26
Unit World Wide Names (LUN IDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–27
Assigning Unit Numbers for Host Access to Storagesets . . . . . . . . . . . . . . . . . . 3–28
Assigning Unit Offsets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–29
Assigning Access Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–30
Creating a Storageset Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
Device PTL Addressing Convention within the Controller . . . . . . . . . . . . . 3–33
Planning Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–37
Defining a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–37
Guidelines for Partitioning Storagesets and Disk Drives. . . . . . . . . . . . . . . 3–38
Choosing Switches for Storagesets and Devices. . . . . . . . . . . . . . . . . . . . . . . . . 3–39
Enabling Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–39
Changing Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–39
RAIDset Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–40

Replacement Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–40
Reconstruction Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–40
Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–41
Mirrorset Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–42
Replacement Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–42
Copy Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–42
Read Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–43
Device Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–44
Transportability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–44
Device Transfer Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–46
Initialize Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–47
Chunk Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–47
Save Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–50
Destroy/Nodestroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–52
Unit Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–54
Configuring Storagesets with CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . .3–55
Adding Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–55
Configuring a Stripeset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–55
Configuring a Mirrorset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–56
Configuring a RAIDset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–57
Configuring a Striped Mirrorset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–59
Configuring a Single-Disk Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–60
Partitioning a Storageset or Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–61
Adding a Disk Drive to the Spareset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–63
Removing a Disk Drive from the Spareset . . . . . . . . . . . . . . . . . . . . . . . . . .3–64
Enabling Autospare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–65
Deleting a Storageset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–65
Changing Switches for a Storageset or Device. . . . . . . . . . . . . . . . . . . . . . .3–66
Configuring with the Command Console LUN . . . . . . . . . . . . . . . . . . . . . . . . . .3–68
Enabling and Disabling the CCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–68
Finding the CCL Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–69
Multiple-Port and Multiple-Host Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–69
Troubleshooting with the CCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–70
Adding Storage Units: Where Is the CCL? . . . . . . . . . . . . . . . . . . . . . . . . .3–70
Moving Storagesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–71

Chapter 4 Troubleshooting
Maintenance Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Troubleshooting Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Significant Event Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Events that cause controller termination . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
Events that do not cause controller operation to terminate . . . . . . . . . . . . . 4–15
Fault Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Displaying Failure Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Translating Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
Controlling the Display of Significant Events and Failures. . . . . . . . . . . . . 4–20
Using VTDPY to Check for Communication Problems . . . . . . . . . . . . . . . . . . . 4–23
Checking Controller-to-Host Communications . . . . . . . . . . . . . . . . . . . . 4–24
Checking Controller-to-Device Communications . . . . . . . . . . . . . . . . . . . . 4–24
Checking Unit Status and I/O Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
Checking Fibre Channel Link Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
Checking for Disk-Drive Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
Finding a Disk Drive in the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
Testing the Read Capability of a Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . 4–36
Testing the Read and Write Capabilities of a Disk Drive . . . . . . . . . . . . . . 4–37
DILX Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Running the Controller’s Diagnostic Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–41

Chapter 5 Replacement Procedures
Replacing Modules in a Single Controller Configuration. . . . . . . . . . . . . . . . . . . 5–2
Replacing the Controller and Cache Module in a Single Controller
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Replacing the Controller in a Single Controller Configuration . . . . . . . . . . . 5–3
Replacing the Cache Module in a Single Controller Configuration . . . . . . . 5–6
Replacing Modules in a Dual-Redundant Controller Configuration. . . . . . . . . . . 5–8
Replacing a Controller and Cache Module in a Dual-Redundant Controller
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Replacing a Controller in a Dual-Redundant Controller Configuration . . . 5–15
Replacing a Cache Module in a Dual-Redundant Controller
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21

vii

Replacing the External Cache Battery Storage
Building Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–27
Replacing the External Cache Battery Storage Building Block
With Cabinet Powered On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–28
Replacing the External Cache Battery Storage Building Block
With Cabinet Powered Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–29
Replacing the GLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–32
Replacing a PVA Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–34
Replacing the PVA in the Master Enclosure (ID 0) . . . . . . . . . . . . . . . . . . .5–34
Replacing the PVA in the First Expansion (ID 2) or Second
Expansion Enclosure (ID 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–36
Replacing an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–39
Replacing DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–42
Removing DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–43
Installing DIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–44
Replacing a Fibre Cable or Hub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–45
Replacing a PCMCIA Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–46
Replacing a Failed Storageset Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–47
Removing a Failed RAIDset or Mirrorset Member . . . . . . . . . . . . . . . . . . .5–47
Installing the New Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–47
Shutting Down the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–48
Disabling and Enabling the External Cache Batteries . . . . . . . . . . . . . . . . .5–48
Restarting the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–50

Chapter 6 Upgrading the Subsystem
Upgrading Controller Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–2
Installing a New Program Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–2
Downloading New Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–3
Using CLCP to Install, Delete, and List Software Patches. . . . . . . . . . . . . . .6–6
Upgrading Firmware on a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–11
HSUTIL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–14
Upgrading to a Dual-Redundant Controller Configuration . . . . . . . . . . . . . . . . .6–16
Installing a New Controller, Cache Module, and ECB . . . . . . . . . . . . . . . . .6–16
Upgrading Cache Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6–20

viii

Appendix A System Profiles
Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–2
Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–3
Enclosure Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–4

Appendix B CLI Commands
CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2
Using the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2
Command Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3
Entering CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–3
Changing the CLI Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–5
ADD CONNECTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–7
ADD DISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–11
ADD MIRRORSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–15
ADD RAIDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–19
ADD SPARESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–23
ADD STRIPESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–25
ADD UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–27
CLEAR_ERRORS CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–35
CLEAR_ERRORS controller INVALID_CACHE . . . . . . . . . . . . . . . . . . . . . . B–37
CLEAR_ERRORS device-name UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . B–39
CLEAR_ERRORS unit-number LOST_DATA . . . . . . . . . . . . . . . . . . . . . . . . . B–41
CLEAR_ERRORS unit-number UNWRITEABLE_DATA . . . . . . . . . . . . . . . .B–43
CONFIGURATION RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–45
CONFIGURATION RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–47
CONFIGURATION SAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–49
CREATE_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–51
DELETE connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–55
DELETE container-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–57
DELETE FAILEDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–59
DELETE SPARESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–61
DELETE unit-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–63
DESTROY_PARTITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–65
DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–67

HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–69
INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–71
LOCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–77
MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–79
POWEROFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–83
REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–85
RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–89
RESTART controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–91
RETRY_ERRORS UNWRITEABLE_DATA . . . . . . . . . . . . . . . . . . . . . . . . . B–93
RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–95
SELFTEST controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–99
SET connection-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–101
SET controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–103
SET device-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–111
SET EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–113
SET FAILEDSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–117
SET FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–119
SET mirrorset-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–121
SET MULTIBUS_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–127
SET NOFAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–129
SET NOMULTIBUS_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–131
SET RAIDset-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–133
SET unit-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–137
SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–143
SHUTDOWN controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–149
UNMIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–151

Appendix C LED Codes
Operator Control Panel LED Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–2
Solid OCP Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–3
Flashing OCP Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–8

Appendix D Event Reporting: Templates and Codes
Passthrough Device Reset Event Sense Data Response. . . . . . . . . . . . . . . . . . . . D–2
Last Failure Event Sense Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . D–3
Multiple-Bus Failover Event Sense Data Response . . . . . . . . . . . . . . . . . . . D–5

Failover Event Sense Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–6
Nonvolatile Parameter Memory Component Event Sense
Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–8
Backup Battery Failure Event Sense Data Response . . . . . . . . . . . . . . . . . . .D–9
Subsystem Built-In Self Test Failure Event Sense Data Response . . . . . . .D–10
Memory System Failure Event Sense Data Response . . . . . . . . . . . . . . . . .D–12
Device Services Non-Transfer Error Event Sense Data Response . . . . . . .D–13
Disk Transfer Error Event Sense Data Response. . . . . . . . . . . . . . . . . . . . .D–14
Instance Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–16
Instance Code Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–16
Instance Codes and FMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–16
Last Failure Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–36
Last Failure Code Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–36
Last Failure Codes and FMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–36
Recommended Repair Action Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–77
Component Identifier Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–82
Event Threshold Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–84
ASC/ASCQ Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–85

Appendix E Controller Specifications
Physical and Electrical Specifications for the Controller . . . . . . . . . . . . . . . . . . . E–2
Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–3

Glossary
Index

Figures

The HSG80 Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–3
A Host and Its Storage Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–7
HSG80 Array Controller–Fibre Channel Copper Cabling. . . . . . . . . . . . . . . . . . .1–8
Optional Maintenance Port Cable for a Terminal Connection. . . . . . . . . . . . . . .1–10
HSG80 Array Controller–Fibre Channel Optical Cabling. . . . . . . . . . . . . . . . . .1–11
Location of Controllers and Cache Modules . . . . . . . . . . . . . . . . . . . . . . . . . . .1–13
HSG80 Controller Operator Control Panel (OCP). . . . . . . . . . . . . . . . . . . . . . . .1–14
Cache Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–19
ECB for Dual-Redundant Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–28
SCSI Target ID Numbers on the Controller Device Bus and PVA Settings
in an Extended Subsytem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–6
Terminal to Local-Connection Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . .2–7
“This Controller” and “Other Controller” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–9
Cabling for Single Configuration with Fibre Channel Copper Support . . . . . . .2–14
Cabling for Single Configuration with Fibre Channel Optical Support . . . . . . .2–15
Cabling for Dual-Redundant Configuration with Two Hubs using
Fibre Channel Copper Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–17
Cabling for Dual-Redundant Configuration with Two Hubs using
Fibre Channel Optical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–18
Cabling for Dual-Redundant Configuration with One Hub using
Fibre Channel Copper Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–20
Cabling for Dual-Redundant Configuration with One Hub using
Fibre Channel Optical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–21
Units Created from Storagesets, Partitions, and Drives . . . . . . . . . . . . . . . . . . . . .3–3
A Typical Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–6
Striping Lets Several Disk Drives Participate in Each I/O Request. . . . . . . . . . . .3–9
Distribute Members across Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–11
Mirrorsets Maintain Two Copies of the Same Data. . . . . . . . . . . . . . . . . . . . . . .3–12
First Mirrorset Members on Different Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–13

xii

Parity Ensures Availability; Striping Provides Good Performance. . . . . . . . . . . 3–15
Striping and Mirroring in the Same Storageset. . . . . . . . . . . . . . . . . . . . . . . . . . 3–17
CLONE Steps for Duplicating Unit Members . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20
Controller Port ID and Unit Numbers in Transparent Failover Mode . . . . . . . . 3–28
Controller Port ID Numbers and Unit Numbers in Mulitple Bus Failover
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–29
LUN Presentation Using Unit Offset on a Per-Host Basis . . . . . . . . . . . . . . . . . 3–30
Storageset Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–32
PTL Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–34
PTL Addressing in a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35
Locating Devices using PTLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
Partitioning a Single-Disk Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–37
Chunk Size Larger than the Request Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–48
Chunk Size Smaller than the Request Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–49
Moving a Storageset from one Subsystem to Another . . . . . . . . . . . . . . . . . . . . 3–71
Troubleshooting: Host Cannot Access Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
Xfer Rate Region of the Default Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
Regions on the Device Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–25
Unit Status on the Cache Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
Fibre Channel Host Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Single Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
Dual-Redundant Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Single-Battery ECB SSB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–27
Dual-battery ECB SBB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–27
Location of GLMs in Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–32
I/O Module Locations in a BA370 Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Cache-Module Memory Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Installing a DIMM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–44
Battery Disable Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–49
Location of Write-Protection Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
Upgrading Device Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
Pass-through Device Reset Event Sense Data Response Format . . . . . . . . . . . . .D–2
Template 01 - Last Failure Event Sense Data Response Format. . . . . . . . . . . . . .D–4
Template 04 - Multiple-Bus Failover Event Sense Data Response Format . . . . .D–5

xiii

Template 05 - Failover Event Sense Data Response Format . . . . . . . . . . . . . . . . D–7
Template 11 - Nonvolatile Parameter Memory Component Event Sense Data
Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–8
Template 12 - Backup Battery Failure Event Sense Data Response Format . . . . D–9
Template 13 - Subsystem Built-In Self Test Failure Event Sense Data
Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–11
Template 14 - Memory System Failure Event Sense Data Response Format . . D–12
Template 41 - Device Services Non-Transfer Error Event Sense Data
Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–13
Template 51 - Disk Transfer Error Event Sense Data Response Format . . . . . . D–15
Structure of an Instance Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–16
Instance Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–16
Structure of a Last Failure Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–36
Last Failure Code Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–36

Tables

Key to Figure 1–1 The HSG80 Subsystem . . . . . . . . . . . . . . . . . . .1–3
Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–4
Key to Figure 1–3 HSG80 Array Controller–Fibre Channel
Copper Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–9
Key to Figure 1–4: Optional Maintenance Port Cable for a
Terminal Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–10
Key to Figure 1–4 HSG80 Array Controller–Fibre Channel
Optical cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–11
Cache Module Memory Configurations . . . . . . . . . . . . . . . . . . . . . .1–18
Cache Policies and Cache Module Status . . . . . . . . . . . . . . . . . . . .1–22
Cache Policies Resulting and ECB Status . . . . . . . . . . . . . . . . . . . .1–24
ECB Capacity Based on Memory Size . . . . . . . . . . . . . . . . . . . . . . .1–29
Key to Figure 2–4 Cabling for Single Configuration (copper) . . . . .2–14
Key to Figure 2–5 Cabling for Single Configuration (optical) . . . . .2–15
Key to Figure 2–6 Cabling for Dual-Redundant Configuration
with Two Hubs (copper) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–17
Key to Figure 2–7 Cabling for Dual-Redundant Configuration
with Two Hubs (optical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–18
Key to Figure 2–8 Cabling for Dual-Redundant Configuration
with One Hub (copper) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–20
Key to Figure 2–9 Cabling for Dual-Redundant Configuration
with One Hub (optical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2–21
Controller Limitations for RAIDsets . . . . . . . . . . . . . . . . . . . . . . . . .3–3
A Comparison of Different Kinds of Storagesets . . . . . . . . . . . . . . . .3–8
Maximum Chunk Sizes for a RAIDset . . . . . . . . . . . . . . . . . . . . . .3–50
Unit Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–54
Troubleshooting Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–4
Event-Code Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–19
FMU SET Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4–20

xvi

VTDPY Key Sequences and Commands . . . . . . . . . . . . . . . . . . . . . 4–23
Device Map Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–25
Device Status Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
Device-Port Status Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
Unit Status Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
Fibre Channel Host Status Display- Known Hosts (Connections) . 4–32
Fibre Channel Host Status Display- Port Status . . . . . . . . . . . . . . . 4–33
Fibre Channel Host Status Display- Link Error Counters . . . . . . . 4–33
Tachyon First Digit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35
Tachyon Second Digit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35
DILX Control Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–37
Data Patterns for Phase 1: Write Test . . . . . . . . . . . . . . . . . . . . . . . 4–38
DILX Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Cache Module Memory Configurations. . . . . . . . . . . . . . . . . . . . . . 5–42
HSUTIL Messages and Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
Cache Module Memory Configurations. . . . . . . . . . . . . . . . . . . . . . 6–20
Recall and Edit Command Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4
ADD UNIT Switches for Storagesets . . . . . . . . . . . . . . . . . . . . . . . B–28
POWEROFF Switch Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–84
SET controller Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B–104
EMU Set Point Temperatures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–114
SET unit-number Switches for Existing Containers . . . . . . . . . . . B–138
Solid OCP Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–3
Flashing OCP Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–8
Instance Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–18
Controller Restart Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–37
Last Failure Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–38
Recommended Repair Action Codes . . . . . . . . . . . . . . . . . . . . . . .D–77
Component Identifier Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–82
Event Notification/Recovery Threshold Classifications . . . . . . . . .D–84
ASC and ASCQ Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–85
Controller Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–2
StorageWorks Environmental Specifications . . . . . . . . . . . . . . . . . . E–3

xvii

Preface

This book describes the features of the HSG80 array controller and configuration
procedures for the controller and storagesets running Array Controller Software
(ACS) Version 8.2G.
This book does not contain information about the operating environments to which
the controller may be connected, nor does it contain detailed information about
subsystem enclosures or their components. See the documentation that
accompanied these peripherals for information about them.

xviii

Precautions
Follow these precautions when carrying out the procedures in this
book.

Electrostatic Discharge Precautions
Static electricity collects on all nonconducting material, such as paper,
cloth, and plastic. An electrostatic discharge (ESD) can easily damage a
controller or other subsystem component even though you may not see
or feel the discharge. Follow these precautions whenever you’re
servicing a subsystem or one of its components:

n
n
n
n
n

Always use an ESD wrist strap when servicing the controller or
other components in the subsystem. Make sure that the strap
contacts bare skin, fits snugly, and that its grounding lead is
attached to a bus that is a verified earth ground.
Before touching any circuit board or component, always touch a
verifiable earth ground to discharge any static electricity that may
be present in your clothing.
Always keep circuit boards and components away from
nonconducting material.
Always keep clothing away from circuit boards and components.
Always use antistatic bags and grounding mats for storing circuit
boards or components during replacement procedures.
Always keep the ESD cover over the program card when the card is
in the controller. If you remove the card, put it in its original
carrying case. Never touch the contacts or twist or bend the card
while you’re handling it.
Never touch the connector pins of a cable when it is attached to a
component or host.

xix

Component Precaution
System components referenced in this manual comply to regulatory
standards documented herein. Use of other components in their place
may violate country standards, negate regulatory compliance, or
invalidate the warranty on your product.

Maintenance Port Precautions
The maintenance port generates, uses, and radiates radio-frequency
energy through cables that are connected to it. This energy may
interfere with radio and television reception. Do not leave a cable
connected to this port when you’re not communicating with the
controller.

Conventions
This book uses the following typographical conventions and special
notices to help you find what you’re looking for.

Typographical Conventions
Convention

Meaning

ALLCAPS BOLD

Command syntax that must be entered exactly as
shown, for example:
SET FAILOVER COPY=OTHER_CONTROLLER

ALLCAPS

Command discussed within text, for example:
“Use the SHOW SPARESET command to show
the contents of the spareset.”

Monospaced

Screen display.

Sans serif italic

Command variable or numeric value that you
supply, for example: SHOW RAIDset-name or
SET THIS_CONTROLLER ID= (n,n,n,n,)

italic

Reference to other books or publications, for
example: “See the HSG80 Array Controller ACS
V8.2 Release Notes for details.”

..
.

Indicates that a portion of an example or figure
has been omitted.

“this controller”

The controller serving your current CLI session
through a local or remote terminal.

“other controller” The controller in a dual-redundant pair that’s
connected to the controller serving your current
CLI session.

xxi

Special Notices
This book doesn’t contain detailed descriptions of standard safety
procedures. However, it does contain warnings for procedures that
could cause personal injury and cautions for procedures that could
damage the controller or its related components. Look for these
symbols when you’re carrying out the procedures in this book:
Warning A warning indicates the presence of a hazard that can cause
personal injury if you do not observe the precautions in the text.

Caution A caution indicates the presence of a hazard that might
damage hardware, corrupt software, or cause a loss of data.

Tip A tip provides alternative methods or procedures that may not be
immediately obvious. A tip may also alert customers that the
controller’s behavior being discussed is different from prior software or
hardware versions.

Note A note provides additional information that’s related to the
completion of an instruction or procedure.

xxii

Required Tools
You will need the following tools to service the controller, cache
module, external cache battery (ECB), the Power Verification and
Addressing (PVA) module, the Gigabit Link Module (GLM), and the
I/O module:

n
n
n
n
n

A flathead screwdriver for loosening and tightening the I/O module
retaining screws.
A small phillips screwdriver for loosening and tightening the GLM
access door screws.
An antistatic wrist strap.
An antistatic mat on which to place modules during servicing.
A Storage Building Block (SBB) Extractor for removing
StorageWorks building blocks. This tool is not required, but it will
enable you to perform more efficiently.

xxiii

Related Publications
The following table lists some of the documents that are related to the
use of the controller, cache module, and external cache battery.
Document Title
Fibre Channel Arbitrated Loop Hub
(DS-DHGGA-CA) User’s Guide

Part Number
EK–DHGGA–UG

KGPSA PCI-to-Fibre Channel Host Adapter EK–KGPSA–UG
DIGITAL StorageWorks Ultra SCSI RAID
Enclosure (BA370-Series) User’s Guide

EK–BA370–UG

The RAIDBOOK—A Source for RAID
Technology

RAID Advisory
Board

DIGITAL StorageWorks HSG80 Array
Controller ACS V8.2 Release Notes

AA–RDY8A–TE

xxiv

Revision History
This is a revised document. Previous documents include:
EK-HSG80-UG .A01

ACS Version 8.0

January 1998

1–1

CHAPTER

General Description

This chapter illustrates and describes in general terms your subsystem and its major
components: the HSG80 array controller, its cache module, and its external cache
battery. See the Fibre Channel Arbitrated Loop Hub User’s Guide and the KGPSA
PCI-to-Fibre Channel Host Adapter User Guide for information about the fibre
channel arbitrated loop hub and adapter that connect the subsystem to your host.

1–2

HSG80 User’s Guide

The HSG80 Array Controller Subsystem
Take a few moments to familiarize yourself with the major components
of the HSG80 Array Controller subsystem. Figure 1–1 shows the
components of a typical installation which includes:

n
n
n
n
n
n
n

One BA370 rack-mountable pedestal enclosure.
Two controllers, each supported by their own cache module.
Two external cache batteries (ECBs) in one Storage Building Block
(SBB), which provide backup power to the cache modules during a
primary power failure.
One environmental monitoring unit (EMU) that monitors the
subsystem’s environment, and alerts the controller of equipment
failures that could cause an abnormal environment.
One power verification and addressing (PVA) module that provides
a unique address to each enclosure in an extended subsystem.
Six I/O modules that integrate the SSB shelf with either an 8-bit
single-ended, 16-bit single-ended, or 16-bit differential SCSI bus.
Two cache modules, which support nonvolatile memory and
dynamic cache policies to protect the availability of its unwritten
(write-back) data.

General Description

1–3

Figure 1–1 The HSG80 Subsystem
12

1
11 4x

2
10
9

3 6x
8

7
6
5
4
CXO6453A

Table 1–1 Key to Figure 1–1 The HSG80 Subsystem
Item Description

Part No.

BA370 rack-mountable enclosure

DS–BA370–AA

Cooling fan

DS–BA35X–MK

I/O module

70–32876–01

AC input module

DS–BA35X–HE

PVA module

DS–BA35X–EC

Cache module B

70–33256–01

Cache module A

70–33256–01

HSG80 controller B

70–33259–01

HSG80 controller A

70–33259–01

EMU

70–32866–01

1–4

HSG80 User’s Guide

Table 1–1 Key to Figure 1–1 The HSG80 Subsystem (Continued)
Item Description

Part No.

180-watt power supply

DS–BA35X–HH

ECB, single
ECB, dual

DS–HS35X–BC
DS–HS35X–BD

Summary of HSG80 Features
Table 1–2 summarizes the features of the controller.
Table 1–2 Controller Features
Feature
Controller Failover
Topology

Supported

n
n
n
n
n
n

n
Supported Operating Systems
Host protocol
Host bus interconnect

n
n
n
n

Transparent Failover
Multiple Bus Failover
FC–AL
8 nodes per loop; maximum
4 initiators per loop
single and dual host
adapter(s)
2 controller subsystems;
maximum 4 controllers (2
dual-redundant
configurations)
128 LUNs in Transparent
and Multiple Bus Failover
Mode
WINNT/Intel
WINNT/Alpha
FC–AL
Copper
Optical: MultiMode 50
Micron
(Do not mix media types)
Gigabit link module (GLM)

General Description

1–5

Table 1–2 Controller Features (Continued)
Feature
Device protocol
Device bus interconnect

n
n
n

n
Number of SCSI device targets per n
Number of SCSI device ports
port
Maximum number of SCSI
devices
Disk Drives

RAID levels supported

Cache Capacity

n
n
n
n
n
n
n
n
n
n

Caching Features

Maximum number of RAID-5 and
RAID-1 storagesets
Maximum number of RAID-5
storagesets

n
n
n
n

Supported
SCSI–2
Limited SCSI–3
Ultra/Fast Wide Singleended
6
12
72
4 and 9 GB Ultra &
Fast Wide
18 GB Ultra
4 GB 10K Ultra
0
1
0+1
3/5
64 MB and 128 MB
(32 MB DIMMs only)
256 MB and 512 MB
(128 MB DIMMs only)
Mirrored Cache
Sequential Read Ahead
Graceful Power Down Policy

UPS support with “auto
cache flush”
30

1–6

HSG80 User’s Guide

Table 1–2 Controller Features (Continued)
Feature
Maximum number of RAID-5,
RAID-1, and RAID-0 storagesets
Maximum number of partitions
per storageset or individual disk
Maximum number of units
presented to each host
Maximum number of devices per
unit
Serial interconnect speed
Maximum device, storageset, or
unit size
Configuration Save

n
n
n
n
n
n

General Features

Supported

n
n
n
n
n

16 (8 on each of 2 ports) This
is a driver limitation.
48
1 GB/second
512 GB LUN capacity
Transfer configuration from
HSZ70 subsystem to HSG80
controller
Transfer configuration from
ACS V 8.0 to ACS V 8.2
Host Modes/Access
Privileges
Persistent Reserves
Program card updates
Device warm swap
Utilities to test disks

General Description

1–7

The HSG80 Array Controller
Your controller is the intelligent bridge between your host and the
devices in your subsystem. As Figure 1–2 illustrates, it bridges the gap
between the host and its storage subsystem.
Figure 1–2 A Host and Its Storage Subsystem

Storage
subsystem

Host

Hub

Controller
CXO6233B

The controller is an integral part of any storage subsystem because it
provides a host with high-performance and high-availability access to
storage devices.
The controller provides the ability to combine several ordinary disk
drives into a single, high-performance entity called a storageset.
Storagesets are implementations of RAID technology, which ensures
that every unpartitioned storageset, whether it uses two disk drives or
ten, looks like a single storage unit to the host. See Chapter 3,
“Creating Storagesets,” for more information about storagesets and
how to configure them.
From the host’s perspective, the controller is simply another device
connected to one of its I/O buses. Consequently, the host sends its I/O
requests to the controller just as it would to any Fibre Channel device.
From the subsystem’s perspective, the controller receives the I/O
requests and directs them to the devices in the subsystem. Because the

1–8

HSG80 User’s Guide

controller processes the I/O requests, the host isn’t burdened by the
processing that’s typically associated with reading and writing data to
multiple storage devices.
For the most recent list of supported devices and operating systems, see
the product-specific release notes that accompanied your controller’s
software. To determine which specific parts you need for your
configuration, see “Connecting the Subsystem to the Host,” page 2–14.
Figure 1–3 and Figure 1–4 detail the HSG80 Array Controller and its
fibre channel components. Figure 1–5 highlights the variant parts for an
optical configuration.
Figure 1–3 HSG80 Array Controller Fibre Channel Copper Cabling
2

3 2x
4

1 3x

5
6

8 2x

11
12 2x

To terminal
CXO6467A

General Description

Table 1–3 Key to Figure 1–3 HSG80 Array Controller–Fibre
Channel Copper Cabling
Item

Description

Part No.

Backplane connectors

Access Door

70–33287–01

GLM

30–49226–01

Program-card slot

—

Program-card ejection button

—

Program card

BG–R8Q3B–BA

ESD/PCMCIA card cover

74–52628–01

5-meter Fibre Channel copper cable
10-meter Fibre Channel copper cable

17–04718–06
17–04718–07

Maintenance Port Cable

17–04074–02

—

See Figure 1–4 for information
on an optional maintenance port
cable and its parts

Maintenance Port

—

Operator control panel (OCP)

—

Lever for removing, installing, and
retaining controller module.

—

1–9

1–10

HSG80 User’s Guide

Figure 1–4 Optional Maintenance Port Cable for a Terminal
Connection
1

2
3

5
CXO6485A

Table 1–4 Key to Figure 1–4: Optional Maintenance Port Cable for
a Terminal Connection
Item

Description

Part Number

BC16E-xx Cable Assembly

17–04074–01

Ferrite Bead

16–25105–14

RJ-11 Adapter

12–43346–01

RJ-11 Extension Cable

17–03511–01

PC Serial Port Adapter, 9 pin
D-sub to 25 pin SKT D-sub for a PC

12–45238–01

PC Serial Port Adapter, 9 pin D-sub to
25 pin D-sub for Sun operating system

12–45238–02

PC Serial Port Adapter, 9 pin D-sub to
25 pin D-sub, mod for an HP800
operating system

12–45238–03

General Description

1–11

Figure 1–5 HSG80 Array Controller–Fibre Channel Optical Cabling
1 2x

2 2x
CXO6494A

Table 1–5 Key to Figure 1–4 HSG80 Array Controller–Fibre
Channel Optical cabling
Item

Description

Part No.

GLM

30–50124–01

2 M Fibre Channel optical cable
5 M Fibre Channel optical cable
10 M Fibre Channel optical cable
20 M Fibre Channel optical cable
30 M Fibre Channel optical cable
50 M Fibre Channel optical cable

17–04820–03
17–04820–05
17–04820–06
17–04820–07
17–04820–08
17–04820–09

Caution If the Fibre Channel optical cable is not properly connected to
the controller, controller failure may result. In addition, if the cable is
not regularly maintained, its performance and lifespan will be affected.
Before proceeding, it is important to administer the precationary
measures detailed in the following sections.

Fibre Channel Optical Cable Precautions
Prior to connecting the Fibre Channel cable to the controller, look for
the white stripe on each side of the coupling. After the cable is seated
into the controller, be sure that the white stripes are hidden. Also, when
connecting the Fibre Channel cable to the controller, listen for a

1–12

HSG80 User’s Guide

distinctive “snap” sound. This will indicate that the cable is properly
inserted into the controller.

Fibre Channel Optical Cable Cleaning Instructions
It is essential to maintain clean cables to ensure optimum performance
and lifespan of the cable. Figure 1–6 illustrates the proper cleaning
procedures, as outlined in the following steps:
1. Open the prep cleaner using the lever on the side of the cable cartridge.
2. Rotate the end face of the ferrule 180 degrees.
3. Slide the ferrule end face along the opening to one side of the coupling.
4. Insert a lint-free polyester swab to dust out the cavity.
5. Remove the lint-free polyseter swab, and return the ferrule to its original
position.
6. Repeat 180 degree rotation in the opposite direction.
7. Slide the ferrule end face along the opening to the opposite side.
8. Insert the lint-free polyester swab to dust out the cavity.
9. Return to step 5, and repeat remaining procedures until all areas of the
cartridge are cleaned.
Note Be sure to clean both cartridges of the fibre channel coupling.
Figure 1–6 Fibre Channel Optical Cleaning Procedures

Small diameter
lint-free polyester
swab

Ferrule
CXO6503A

General Description

1–13

The HSG80 Array Controller components that you will use most often,
such as the maintenance port and the OCP, are conveniently located on
the controller’s front panel. The host port and program-card slot are
also located on the front panel, making it easy to update the controller’s
software or to connect the controller to a different host.
Each controller is supported by its own cache module. Figure 1–4
shows which cache module supports which controller in a dualredundant configuration in a BA370 rack-mountable enclosure.
Figure 1–7 Location of Controllers and Cache Modules
EMU

PVA
Controller A
Controller B

Cache module A

Cache module B
CXO6283A

Tip DIGITAL recommends that you use the slots for controller A and
cache module A for single configurations. Slot A responds to SCSI target
ID number 7 on device buses; slot B responds to SCSI target ID number
6 on the device buses.

Operator Control Panel
The operator control panel (OCP) contains a reset button and six port
LED buttons, as shown in Figure 1–5. The reset button flashes about
once per second to indicate that the controller is operating normally.
The port button LEDs correspond to the controller’s device ports and
remain off during normal operation. If an error occurs, the reset button
and LEDs will illuminate in a solid or flashing pattern to help you
diagnose the problem. See Appendix C, “LED Codes,” for further
explanation on these codes.

1–14

HSG80 User’s Guide

Figure 1–8 HSG80 Controller Operator Control Panel (OCP)
Reset button/
LED

Port button/
LED

CXO6216A

To identify the exact location of the OCP, refer to Figure 1–3.
Under normal circumstances, you will not need to remove the
controller from its enclosure. For this reason, the components that you
will use most often are conveniently located on the front panel. For
example, the maintenance port provides a convenient way to connect a
PC or terminal to your controller so that you can interact with it.
After you configure your controller, you should periodically check its
control panel. If an error occurs, one or more of the LEDs on the
control panel will flash in a pattern that will help you to diagnose the
problem. See Chapter 4, “Troubleshooting,” for details about
troubleshooting your controller.

Maintenance Port
You can access the controller through a PC or a local terminal via the
maintenance port, or through a remote terminal—sometimes called a
virtual terminal or host console—via the host. DIGITAL recommends
that you use a PC or a local terminal to carry out the troubleshooting
and servicing procedures in this manual. See “Establishing a Local
Connection to the Controller,” page 2–7, for more information on
connecting the controller with a maintenance port cable.

Utilities and Exercisers
The controller’s software includes the following utilities and exercisers
to assist in troubleshooting and maintaining the controller and the other
modules that support its operation:

General Description

1–15

Fault Management Utility
The Fault Management Utility (FMU) provides a limited interface to
the controller’s fault-management system. As a troubleshooting tool,
you can use FMU to display last-failure and memory-system-failure
entries, translate many of the code values contained in event messages,
and set the display characteristics of significant events and failures.
See “Fault Management Utility,” page 4–17, for more information
about using this utility.

Virtual Terminal Display
Use the virtual terminal display (VTDPY) utility to troubleshoot
communication between the controller and its host, communication
between the controller and the devices in the subsystem, and the state
and I/O activity of the logical units, devices, and device ports in the
subsystem.
See “Using VTDPY to Check for Communication Problems,” page
4–23, for more information about using this utility.

Disk Inline Exerciser
Use the disk inline exerciser (DILX) to investigate the data-transfer
capabilities of disk drives. DILX tests and verifies operation of the
controller and the SCSI–2 disk drives attached to it. DILX generates
intense read and write loads to the disk drive while monitoring the
drive’s performance and status. See “Checking for Disk-Drive
Problems,” page 4–37, for more information about this exerciser.

Configuration Utility
Use the configuration (CONFIG) utility to add one or more storage
devices to the subsystem. This utility checks the device ports for new
disk drives then adds them to the controller’s configuration and
automatically names them. See “Adding Several Disk Drives at a
Time,” page 3–55, for more information about using the CONFIG
utility.

1–16

HSG80 User’s Guide

HSUTIL
Use HSUTIL to upgrade the firmware on disk drives in the subsystem
and to format disk drives. See “Upgrading Firmware on a Device,”
page 6–11, for more information about this utility.

Code Load and Code Patch Utility
Use Code Load/Code Patch (CLCP) utility to upgrade the controller
software and the EMU software. You can also use it to patch the
controller software. When you install a new controller, you must have
the correct software version and patch number. See “Upgrading
Controller Software,” page 6–2, for more information about using this
utility.
Note Only DIGITAL field service personnel are authorized to upload
EMU microcode updates. Contact the Customer Service Center (CSC)
for directions in obtaining the appropriate EMU microcode and
installation guide.

Clone Utility
Use the Clone utility to duplicate the data on any unpartitioned singledisk unit, stripeset, or mirrorset. Back up the cloned data while the
actual storageset remains online. See “Cloning Data for Backup,” page
3–19, for more information about using the Clone utility.

Field Replacement Utility
Use the field replacement utility (FRUTIL) to replace a failed controller
(in a dual-redundant configuration) without shutting down the
subsystem.You can also use this menu-driven utility to replace cache
modules and external cache batteries. See Chapter 5, “Replacement
Procedures,” for a more detailed explanation of how to use FRUTIL.

General Description

1–17

Change Volume Serial Number Utility
Only DIGITIAL authorized service personnel may use this utility.
The Change Volume Serial Number (CHVSN) utility generates a new
volume serial number (called VSN) for the specified device and writes it
on the media. It is a way to eliminate duplicate volume serial numbers
and to rename duplicates with different volume serial numbers.

Device Statistics Utility
The Device Statistics (DSTAT) utility allows you to log I/O activity on
a controller over an extended period of time. Later, you can analyze that
log to determine where the bottlenecks are and how to tune the
controller for optimum performance.

1–18

HSG80 User’s Guide

Cache Module
Each controller requires a companion cache module as shown in Figure
1–9. Figure 1–7 on page 1–13 shows the location of a controller’s
companion cache module. The cache module, which can contain up to
512 MB of memory, increases the subsystem’s I/O performance by
providing read, read-ahead, write-through, and write-back caching.
The size of the memory contained in the cache module depends on the
configuration of the DIMMs, with the supported combinations shown
in Table 1–6. For placement of the DIMMs, see “Replacing DIMMs,”
page 5–42.
Table 1–6 Cache Module Memory Configurations
DIMMs

Quantity

Memory

32 MB

64 MB

32 MB

128 MB

256 MB

128 MB

512 MB

General Description

Figure 1–9 Cache Module
5

~
2
3 2x
CXO6161A

Item

Description

Part No.

Cache-memory power LED button

—

ECB Y cable for the BA370
Enclosure

17–04479–03

ECB Y cable for the Data Center
Cabinet

17–04479–04

Retaining lever

—

Backplane connector

—

64 MB cache upgrade

DS-HSDIM-AB

256 MB cache upgrade

DS-MSDIM-AC

1–19

1–20

HSG80 User’s Guide

Caching Techniques
The cache module supports the following caching techniques to
increase the subsystem’s read and write performance:

n
n
n
n

Read caching
Read-ahead caching
Write-through caching
Write-back caching

Read Caching
When the controller receives a read request from the host, it reads the
data from the disk drives, delivers it to the host, and stores the data in
its cache module. This process is called read caching.
Read caching can decrease the subsystem’s response time to many of
the host’s read requests. If the host requests some or all of the cached
data, the controller satisfies the request from its cache module rather
than from the disk drives. By default, read caching is enabled for all
storage units.
See SET unit number MAXIMUM_CACHED_TRANSFER in
Appendix B, “CLI Commands,” for more details.

Read-Ahead Caching
Read-ahead caching begins when the controller has already processed a
read request, and it receives a sequential read request from the host. If
the controller does not find the data in the cache memory, it reads the
data from the disks and sends it to the cache memory.
The controller then anticipates subsequent read requests and begins to
prefetch the next blocks of data from the disks as it sends the requested
read data to the host. This is a parallel action. The controller notifies the
host of the read completion, and subsequent sequential read requests
are satisfied from the cache memory. By default, read-ahead caching is
enabled for all disk units.

General Description

1–21

Write-Through Caching
When the controller receives a write request from the host, it stores the
data in its cache module, writes the data to the disk drives, then notifies
the host when the write operation is complete. This process is called
write-through caching because the data actually passes through—and is
stored in—the cache memory on its way to the disk drives.
If you enable read caching for a storage unit, write-through caching is
automatically enabled. Likewise, if you disable read caching, writethrough caching is automatically disabled.

Write-Back Caching
This caching technique improves the subsystem’s response time to
write requests by allowing the controller to declare the write operation
“complete” as soon as the data reaches its cache memory. The
controller performs the slower operation of writing the data to the disk
drives at a later time.
By default, write-back caching is enabled for all units. In either case,
the controller will not provide write-back caching to a unit unless the
cache memory is non-volatile, as described in the next section.

Fault-Tolerance for Write-Back Caching
The cache module supports nonvolatile memory and dynamic cache
policies to protect the availability of its unwritten (write-back) data:

Nonvolatile Memory
The controller can provide write-back caching for any storage unit as
long as the controller’s cache memory is nonvolatile. In other words, to
enable write-back caching, you must provide a backup power source to
the cache module to preserve the unwritten cache data in the event of a
power failure. If the cache memory were volatile—that is, if it didn’t
have a backup power supply—the unwritten cache data would be lost
during a power failure.
By default, the controller expects to use an ECB as the backup power
source for its cache module. See “External Cache Battery,” page 1–28,
for more information about the ECB. However, if your subsystem is
backed up by a UPS (uninterruptible power supply), you can tell the
controller to use the UPS as the backup power source with the SET

1–22

HSG80 User’s Guide

THIS CONTROLLER CACHE_UPS command. See Appendix B, “CLI
Commands,” for instructions on using this command.

Cache Policies Resulting from Cache Module Failures
If the controller detects a full or partial failure of its cache module or
ECB, it automatically reacts to preserve the unwritten data in its cache
module. Depending upon the severity of the failure, the controller
chooses an interim caching technique (also called the cache policy)
which it uses until you repair or replace the cache module or ECB.
Table 1-7 shows the cache policies resulting from a full or partial
failure of cache module A in a dual-redundant controller configuration.
The consequences shown in this table are the same for cache module B.
Table 1-7 Cache Policies and Cache Module Status
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

Good

Data loss: No

Cache policy: Both controllers
support write-back caching.

Failover: No

Data loss: Forced error and loss of
write-back data for which multibit
error occurred. Controller A
detects and reports the lost blocks.

Data loss: No. Controller A
recovers its lost write-back data
from the mirrored copy on cache B.

Multibit
cache
memory
failure

Good

Cache policy: Both controllers
support write-back caching.

Cache policy: Both controllers
support write-back caching.
Failover: No

Failover: No

General Description

1–23

Table 1-7 Cache Policies and Cache Module Status (Continued)
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

DIMM or
cache
memory
controller
chip
failure

Good

Data integrity: Write-back data
that was not written to media when
failure occurred was not
recovered.

Data integrity: Controller A
recovers all of its write-back data
from the mirrored copy on cache B.

Cache policy: Controller A
supports write-through caching
only; controller B supports writeback caching.
Failover: In transparent failover,
all units failover to controller B. In
multiple-bus failover with hostassist, only those units that use
write-back caching, such as
RAIDsets and mirrorsets, failover
to controller B. All units with lost
data become inoperative until you
clear them with the CLEAR
LOST_DATA command. Units
that didn’t lose data operate
normally on controller B.
In single controller configurations,
RAIDsets, mirrorsets, and all units
with lost data become inoperative.
Although you can clear the lost
data errors on some units,
RAIDsets and mirrorsets remain
inoperative until you repair or
replace the nonvolatile memory on
cache A.

1–24

HSG80 User’s Guide

Table 1-7 Cache Policies and Cache Module Status (Continued)
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

Cache
Board
Failure

Good

Same as for DIMM failure.

Data integrity: Controller A
recovers all of its write-back data
from the mirrored copy on cache B.
Cache policy: Both controllers
support write-through caching only.
Controller B cannot execute
mirrored writes because cache
module A cannot mirror
controller B’s unwritten data.
Failover: No

Table 1-8 shows the cache policies resulting from full or partial failure
of cache module A’s ECB in a dual-redundant configuration. Note that
when cache module A is at least 50% charged, the ECB is still operable
and charging. When it is less than 50% charged, the ECB is low but still
charging. The consequences shown in this table are reciprocal for a
failure of cache module B’s ECB.
Table 1-8 Cache Policies Resulting and ECB Status
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

At least
50%
charged

Data loss: No

Cache policy: Both controllers
continue to support write-back
caching.

Failover: No

General Description

Table 1-8 Cache Policies Resulting and ECB Status (Continued)
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

Less than
50%
charged

At least
50%
charged

Data loss: No

Cache policy: Controller A
supports write-through caching
only; controller B supports writeback caching.

Cache policy: Both controllers
continue to support write-back
caching.
Failover: No

Failover: In transparent failover,
all units failover to controller B.
In multiple-bus failover with hostassist, only those units that use
write-back caching, such as
RAIDsets and mirrorsets, failover
to controller B.
In single configurations, the
controller only provides writethrough caching to its units.

1–25

1–26

HSG80 User’s Guide

Table 1-8 Cache Policies Resulting and ECB Status (Continued)
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

Failed

At least
50%
charged

Data loss: No

Cache policy: Controller A
supports write-through caching
only; controller B supports writeback caching.

Cache policy: Both controllers
continue to support write-back
caching.
Failover: No

Failover: In transparent failover,
all units failover to controller B
and operate normally.
In multiple-bus failover with hostassist, only those units that use
write-back caching, such as
RAIDsets and mirrorsets, failover
to controller B.
In single configurations, the
controller only provides writethrough caching to its units.
Less than
50%
charged

Less
than
50%
charged

Data loss: No

Cache policy: Both controllers
support write-through caching
only.

Cache policy: Both controllers
support write-through caching only.
Failover: No

Failover: No

General Description

1–27

Table 1-8 Cache Policies Resulting and ECB Status (Continued)
Cache Module Status

Cache Policy

Cache A

Cache B

Unmirrored Cache

Mirrored Cache

Failed

Less
than
50%
charged

Data loss: No

Cache policy: Both controllers
support write-through caching
only.

Cache policy: Both controllers
support write-through caching only.
Failover: No

Failed

Data loss: No

Cache policy: Both controllers
support write-through caching
only.

Cache policy: Both controllers
support write-through caching only.

Failover: No. RAIDsets and
mirrorsets become inoperative.
Other units that use write-back
caching operate with writethrough caching only.

Failover: No. RAIDsets and
mirrorsets become inoperative.
Other units that use write-back
caching operate with write-through
caching only.

1–28

HSG80 User’s Guide

External Cache Battery
To preserve the write-back cache data in the event of a primary power
failure, a cache module must be connected to an external cache battery
(ECB) or a UPS.
DIGITAL supplies two versions of ECBs: a single-battery ECB for
single controller configurations, and a dual-battery ECB for dualredundant controller configurations, which is shown in Figure 1–10.
Figure 1–10ECB for Dual-Redundant Configurations

1
2

US
STAT
F
OF
UT

E
CH
CA ER
W
PO
E
CH
CA ER
W
PO

US
STAT
F
OF
UT

4
3

~
CXO5713A

Item

Description

Part No.

Dual battery ECB SBB (Storage
Building Block)

DS–HS35X–BD

Single battery ECB SBB

DS–HS35X–BC

Shut off button

—

Status LED

—

ECB Y cable for the BA370 Enclosure

17–04479–03

ECB Y cable for the Data Center
Cabinet

17–04479–04

Micro-D port for second battery

—

General Description

1–29

When the batteries are fully charged, an ECB can preserve 512 MB of
cache memory for 24 hours. However, the battery capacity depends
upon the size of memory contained in the cache module, as defined in
the Table 1–9.
Table 1–9 ECB Capacity Based on Memory Size
Size

DIMM Combinations

Capacity

64 MB

Two, 32 MB

96 hours

128 MB

Four, 32 MB

48 hours

256 MB

Two, 128 MB

48 hours

512 MB

Four, 128 MB

24 hours

Charging Diagnostics
Whenever you restart the controller, its diagnostic routines
automatically check the charge in the ECB’s batteries. If the batteries
are fully charged, the controller reports them as good and rechecks
them every 24 hours. If the batteries are charging, the controller
rechecks them every four minutes. Batteries are reported as being either
above or below 50 percent in capacity. Batteries below 50 percent in
capacity are referred to as being low.
This four-minute polling continues for up to 10 hours—the maximum
time it should take to recharge the batteries. If the batteries have not
been charged sufficiently after 10 hours, the controller declares them to
be failed.

Battery Hysteresis
When charging a battery, write-back caching will be allowed as long as
a previous down time has not drained more than 50 percent of a
battery’s capacity. When a battery is operating below 50 percent
capacity, the battery is considered to be low and write-back caching is
disabled.
Caution DIGITAL recommends that you replace the ECB every two
years to prevent battery failure.

1–30

HSG80 User’s Guide

Note If a UPS is used for backup power, the controller does not check
the battery. See Appendix B, “CLI Commands,” for information about
the CACHE_UPS and NOCACHE_UPS switches.

2–1

CHAPTER

Configuring an HSG80 Array Controller

This chapter explains how to configure an HSG80 Array Controller and the
modules that support its operation in a StorageWorks subsystem.

2–2

HSG80 User’s Guide

Introduction
Use the Getting Started Guide that came with your subsystem to
unpack and set up your subsystem prior to configuring your controller.
Unless you specifically requested a preconfigured subsystem, you will
have to configure your controller and its subsystem before you can use
them.
For the complete syntax and descriptions of the CLI commands used in
the configuration procedure, see Appendix B, “CLI Commands.”

Configuration Rules
Before you configure your controller, review these configuration rules
and ensure your planned configuration meets the requirements and
conditions.

n
n
n
n
n
n
n
n
n
n
n

Maximum 128 visible LUNs/200 assignable unit numbers
Maximum 512 GB LUN capacity
Maximum 72 physical devices
Maximum 20 RAID-5 storagesets
Maximum 30 RAID-5 and RAID-1 storagesets
Maximum 45 RAID-5, RAID-1, and RAID-0 storagesets
Maximum 8 partitions of a storageset or individual disk
Maximum 6 members per mirrorset
Maximum 14 members per RAID-5 storageset
Maximum 24 members per Stripeset
Maximum 48 physical devices per striped mirrorset

Configuring an HSG80 Array Controller

2–3

Configuring an HSG80 Array Controller
You can use this procedure to configure your controller in one of the
following ways:

n
n
n

Single controller
Dual controllers (in transparent failover mode)
Multiple-bus failover (host-assisted), dual-redundant controllers

References sited in the steps below will help you locate details about
the commands and concepts.
Use the following steps to configure an HSG80 array controller:
1. Use the power verification and addressing (PVA) module ID switch to
set the SCSI ID number for the BA370 rack-mountable enclosure.
See “Setting the PVA Module ID Switch,” page 2–6, for details about
PVA switch settings.
2. Remove the program card ESD cover, and insert the controller’s
program card. Replace the ESD cover.
3. Turn on the power to the pedestal enclosure.
4. Establish a local connection to the controller.
See “Establishing a Local Connection to the Controller,” page 2–7, for
details about creating a local connection.
5. Choose a configuration for the controller:
a.

If you are configuring dual- redundant controllers in
transparent failover mode, proceed to step 9.

If you are configuring dual-redundant controllers in multiplebus (sometimes called host-assisted) failover mode, skip to
step 10.

6. If the controller reports a node ID of all zeros (0000-0000-0000-0000)
set the subsystem worldwide name (node ID) to the worldwide name
that came with your subsystem. Use the steps in “Restoring Worldwide
Names (Node IDs),” page 3–26.
7. Set the port topology for each port.
SET THIS_CONTROLLER PORT_1_TOPOLOGY= “topology”
SET THIS_CONTROLLER PORT_2_TOPOLOGY=“ topology”

2–4

HSG80 User’s Guide

If this is a single configuration with a single hub, set PORT 2 off-line.
If this is a dual-redundant configuration, the “other controller” inherits
“this controller’s” port topology.
See Appendix B, “CLI Commands,” for more information about using
the SET THIS_CONTROLLER PORT_n_TOPOLOGY= command.
8. If you selected LOOP_HARD for the port topology, specify the
arbitrated loop physical address (ALPA) for the host ports.
SET THIS_CONTROLLER PORT_1_ALPA= “address”
SET THIS_CONTROLLER PORT_2_ALPA=“address”

If this is a dual-redundant configuration, the “other controller” inherits
“this controller’s” port ALPA addresses.
See Appendix B, “CLI Commands,” for more information about using
the SET OTHER_CONTROLLER PORT_n_ALPA= command.
9. Put “this controller” into transparent failover mode. Use the following
syntax:
SET FAILOVER COPY = THIS_CONTROLLER

The “other controller” inherits “this controller’s” configuration, then
restarts. Wait for it to return to normal operation before continuing.
See details about failover modes in “Selecting a Failover Mode,” page
2–10.
10. Put “this controller” in multiple-bus failover mode using the follwing
syntax:
SET MULTIBUS_FAILOVER COPY=THIS_CONTROLLER

The “other controller” inherits “this controller’s” configuration, then
restarts. Wait for it to return to normal operation before continuing.
See “Selecting a Failover Mode,” page 2–10, for details about failover
modes.
11. Optional: Change the CLI prompt. Type the following command:
SET THIS_CONTROLLER PROMPT = “new prompt”

Configuring an HSG80 Array Controller

2–5

If you’re configuring dual-redundant controllers, also change the CLI
prompt on the “other controller.” Use the following syntax:
SET OTHER_CONTROLLER PROMPT = “new prompt”

See Appendix B, “CLI Commands,” for more information about using
the SET OTHER_CONTROLLER PROMPT= command.
12. Optional: Indicate that your subsystem power is supported by a UPS.
Use the following syntax:
SET THIS_CONTROLLER CACHE_UPS

The “other controller” inherits “this controller’s” cache UPS setting.
See “Backing up Power with a UPS,” page 2–13, for more information.
13. Restart the controller, using the following syntax:
RESTART THIS_CONTROLLER

If this is a dual-redundant configuration, restart the “other controller”
using the following syntax:
RESTART OTHER_CONTROLLER

See the RESTART THIS_CONTROLLER command in Appendix B,
“CLI Commands,” for more information about using this command.
14. When the CLI prompt reappears, it will display details about the
controller you configured. Use the following syntax:
SHOW THIS_CONTROLLER FULL

See the SHOW THIS_CONTROLLER FULL command in Appendix
B, “CLI Commands,” for more information about using this command.
15. Connect the controller to the host.
See “Connecting the Subsystem to the Host,” page 2–14 for
information about how to complete the connection.
16. Plan and configure storagesets for your subsystem.
See Chapter 3, “Creating Storagesets,” for detailed information about
planning and configuring storagesets.
Note If you have problems during the configuration, use the SET
NOFAILOVER and CONFIGURATION RESTORE commands to reset
the system to the factory settings. You must reset the controller after
these commands are entered to employ the original settings.

2–6

HSG80 User’s Guide

Setting the PVA Module ID Switch
The Power, Verification, and Addressing (PVA) module provides
unique addresses to extended subsystems. Each BA370 rack-mountable
enclosure in an extended subsystem must have its own PVA ID. Use
PVA ID 0 for the enclosure that contains the array controllers. Use PVA
IDs 2 and 3 for the additional enclosures. Figure 2–1 illustrates the
PVA settings in an extended subsystem.
See the documentation that accompanied your enclosure for more
details about the PVA and its settings.
Figure 2–1 SCSI Target ID Numbers on the Controller Device Bus and PVA Settings in an
Extended Subsytem
First Expansion
Enclosure

Master
Enclosure

Second Expansion
Enclosure

SCSI Target ID = 11

SCSI Target ID = 3

SCSI Target ID = 15

SCSI Target ID = 10

SCSI Target ID = 2

SCSI Target ID = 14

SCSI Target ID = 9

SCSI Target ID = 1

SCSI Target ID = 13

SCSI Target ID = 8

SCSI Target ID = 0

SCSI Target ID = 12

EMU

EMU
PVA 0
Controller A
Controller B
Cache A
Cache B

EMU

PVA 2

PVA 3

OTE: SCSI target IDs 4 and 5 are reserved. IDs 6 and 7 are used by the controllers.
CXO5806B

Configuring an HSG80 Array Controller

2–7

Establishing a Local Connection to the Controller
You can communicate with a controller locally or remotely. Use a local
connection to configure the controller for the first time. Use a remote
connection to your host system for all subsequent configuration tasks.
See the Getting Started Guide that came with your platform kit for
details.
The maintenance port provides a convenient way to connect a PC or
terminal to the controller so that you can troubleshoot and configure it.
This port accepts a standard RS-232 jack from any EIA-423 compatible
terminal or a PC with a terminal-emulation program. The maintenance
port supports serial communications with default values of 9600 baud
using 8 data bits, 1 stop bit, and no parity.
Note The maintenance port cable shown in Figure 2–2 has a 9-pin
connector molded onto its end for a PC connection. If you need a
terminal connection, see Figure 1–4 on page 1–10 for information on
optional cabling.
Figure 2–2 Terminal to Local-Connection Port Connection

Maintenance
port cable

Maintenance
port

CXO6476A

2–8

HSG80 User’s Guide

Caution The local-connection port described in this book generates,
uses, and can radiate radio-frequency energy through cables that are
connected to it. This energy may interfere with radio and television
reception. Do not leave any cables connected to it when you are not
communicating with the controller.
Follow these steps to establish a local connection for setting the
controller’s initial configuration:
1. Turn off the PC or terminal, and connect it to the controller, as shown in
Figure 2–2.
a.

For a PC connection, plug one end of the maintenance port
cable into the terminal; plug the other end into the controller’s
maintenance port.

For a terminal connection, refer to Figure 1–4 on page 1–10 for
cabling information.

2. Turn on the PC or terminal.
3. Configure the terminal for 9600 baud, 8 data bits, 1 stop bit, and no
parity.
4. Press the Enter or Return key. A copyright notice and the CLI prompt
appear, indicating that you established a local connection with the
controller.
5. Optional: to increase the data transfer rate to 19200 baud:
a.

Set the controller to 19200 baud with one of the following
commands:
SET THIS_CONTROLLER TERMINAL SPEED=19200
SET OTHER_CONTROLLER TERMINAL SPEED=19200

Configure the PC or terminal for 19200 baud.

When you are entering CLI commands in a dual-redundant controller
configuration, remember that the conroller to which you’re connected is
“this controller” and the remaining controller is the “other controller”.
See Figure 2–3.

Configuring an HSG80 Array Controller

Figure 2–3 “This Controller” and “Other Controller”

Other controller
This controller

CXO6468B

2–9

2–10

HSG80 User’s Guide

Selecting a Failover Mode
When selecting a failover mode, use transparent failover if you want the
failover to occur without any intervention from the host, or employ
multiple-bus failover if you want the host to send commands to the
companion array controller.

Using Transparent Failover
Transparent failover is a dual-redundant controller configuration in
which two controllers are connected to the same host and device buses.
Use this configuration if you want to use two controllers to service the
entire group of storagesets, single-disk units, and other storage devices.
Because both controllers service the same storage units, either
controller can continue to service all of the units if its companion
controller fails.
Transparent failover occurs when a controller fails or a user presses the
reset button on one of the controllers. To configure controllers for
transparent failover, mount both controllers in the same BA370 pedestal
and follow the steps in “Configuring an HSG80 Array Controller,” page
2–3.
Keep the following tips in mind if you configure controllers for
transparent failover:

n
n

Set your controllers for transparent failover before configuring
devices. Once the devices, storagesets, and units are added to one
controller’s configuration, they are automatically added to the
other’s.
If you decide to configure your devices before setting the
controllers for transparent failover, make sure you know which
controller has the good configuration information before specifying
SET FAILOVER COPY=. See Appendix B, “CLI Commands,” for
details about the SET FAILOVER COPY= command.
Balance your assignment of devices. For example, in an18-device
subsystem, place 3 devices on each of the 6 ports, rather than
placing 6 devices on each of 3 ports.
The controller to which you copy configuration information restarts
after you enter the SET FAILOVER command.

Configuring an HSG80 Array Controller

2–11

Using Multiple-Bus Failover
Multiple-bus (or host-assisted) failover is a dual-redundant controller
configuration in which each array controller has its own connection to
the host. Thus, if one of the host connections to an array controller
fails, the host can cause units that became inaccessible to failover to the
remaining viable connection. Because both array controllers service the
same storage units, either array controller can continue to service all of
the units if the other array controller fails.
Keep the following points in mind when considering using multiple-bus
failover:

n
n
n
n

The host distributes the I/O load between the array controllers.
The host must have two Fibre Channel adapters as well as
operating-system software to support the multiple-bus failover,
dual-redundant controller configuration.
Mount both array controllers in the same BA370 rack-mountable
enclosure and follow the steps in “Configuring an HSG80 Array
Controller,” page 2–3.
Partitioning is not supported.

2–12

HSG80 User’s Guide

Enabling Mirrored Write-Back Cache
Before configuring dual-redundant controllers and enabling mirroring,
ensure the following conditions are met:

n
n
n
n
n

Both array controllers support the same size cache, 64 MB, 128
MB, 256MB, or 512 MB.
Diagnostics indicates that both caches are good.
Both caches have a battery present, if you have not enabled the
CACHE_UPS switch. A battery does not have to be present for
either cache if you enable the CACHE_UPS switch.
No unit errors are outstanding, for example, lost data or data that
cannot be written to devices.
Both array controllers are started and configured in failover mode.

For important considerations when adding or replacing DIMMs in a
mirrored cache configuration, see “Replacing DIMMs,” page 5–42.

Selecting a Cache Mode
Before selecting a cache mode you should understand the caching
techniques supported by the cache module.
The cache module supports read, read-ahead, write-through, and writeback caching techniques that you can enable separately for each storage
unit in a subsystem. For example, you can enable only read and writethrough caching for some units while enabling only write-back caching
for other units.
For details about these caching techniques, see“Caching Techniques,”
page 1–20.

Fault-Tolerance
The cache module supports the following features to protect the
availability of its unwritten (write-back) data:

n
n

Nonvolatile memory (required for write-back caching).
Dynamic caching techniques (automatic).

For details about these features, see “Fault-Tolerance for Write-Back
Caching,” page 1–21.

Configuring an HSG80 Array Controller

2–13

Backing up Power with a UPS
By default, the controller expects to use an external cache battery
(ECB) as backup power to the cache module. You can also opt to use an
uninterruptable power supply (UPS) to provide backup power in the
event of a primary power failure. See Appendix B, “CLI Commands,”
for details about the SET THIS_CONTROLLER CACHE_UPS
command. See Table 1-7 on page 1–22 and Table 1-8 on page 1–24 for
information about cache policies.

2–14

HSG80 User’s Guide

Connecting the Subsystem to the Host
This section describes how to connect your subsystem to a host. It also
includes instructions for connecting a single (nonredundant) controller
and dual-redundant controllers to the host.
Caution Do not attempt to configure dual-redundant controllers using
one hub with a loopback cable. This configuration will cause data
corruption and is not supported.

Connecting a Single Controller to the Host Using One Hub
There are two possible configurations for a single controller, one that
uses a single hub, and a second that uses two hubs. The second
configuration can be used if you have two hosts to which you’re
connecting to your controller.
Figure 2–4 Cabling for Single Configuration with Fibre Channel Copper Support

1
To host
2

3
CXO6115A

Table 2–1 Key to Figure 2–4 Cabling for Single Configuration
(copper)
Item

Description

Single Controller

9-Port Fibre Channel HUB

5-meter copper Fibre Channel cable or
10-meter copper Fibre Channel cable

Part No.
70-33259-xx
DS-DHGGA-CA
17-04718-06
17-04718-07

Configuring an HSG80 Array Controller

2–15

Use the following steps to connect a single, nonredundant controller to
the host using one hub:
1. Stop all I/O from the host to its devices on the bus to which you are
connecting the controller.
2. Connect the Fibre Channel cable from Port 1 on the controller to Port 1
of the hub.
For this configuration, set Port 2 off-line using the SET
THIS_CONTROLLER PORT_2_TOPOLOGY=OFFLINE command.
See Appendix B, “CLI Commands,” for details about the SET
command.
3. Follow the procedures in the Getting Started Guide for connecting the
Fibre Channel cable from the hub to your host system.
4. Route and tie the cables as desired.
Restart the I/O from the host. Some operating systems may require you
to restart the host to see the devices attached to the new controller.
Figure 2–5 Cabling for Single Configuration with Fibre Channel Optical Support
3

To host

2
CXO6495A

2–16

HSG80 User’s Guide

Table 2–2 Key to Figure 2–5 Cabling for Single Configuration
(optical)
Item

Description

Part No.

Single Controller

70–33259–xx

.5 M Fibre Channel Optic cable
1 M Fibre Channel Optic cable
2 M Fibre Channel Optic cable
3 M Fibre Channel Optic cable
5 M Fibre Channel Optic cable
10 M Fibre Channel Optic cable
20 M Fibre Channel Optic cable
30 M Fibre Channel Optic cable
50 M Fibre Channel Optic cable
100 M Fibre Channel Optic cable
200 M Fibre Channel Optic cable
400 M Fibre Channel Optic cable

17–04820–01
17–04820–02
17–04820–03
17–04820–04
17–04820–05
17–04820–06
17–04820–07
17–04820–08
17–04820–09
17–04820–10
17–04820–11
17–04820–12

12-Port Fibre Channel HUB

DHGGA-CA

Use the following steps to connect a single, nonredundant controller to
the host using one hub:
1. Stop all I/O from the host to its devices on the bus to which you are
connecting the controller.
2. Connect the Fibre Channel cable from Port 1 on the controller to Port 1
of the hub.
For this configuration, set Port 2 off-line using the SET
THIS_CONTROLLER PORT_2_TOPOLOGY=OFFLINE command.
See Appendix B, “CLI Commands,” for details about the SET
command.
3. Follow the procedures in the Getting Started Guide for connecting the
Fibre Channel cable from the hub to your host system.
4. Route and tie the cables as desired.
5. Restart the I/O from the host. Some operating systems may require you
to restart the host to see the devices attached to the new controller.

Configuring an HSG80 Array Controller

2–17

Connecting a Dual-Redundant Controller Configuration to the Host
There are two possible ways to connect dual-redundant controllers to
your host. The first method requires two hubs; the second method
requires one hub.

Using Two Hubs
Use the following steps and Figure 2–6 to connect your dual-redundant
controllers to the host using two hubs with copper support.
Figure 2–6 Cabling for Dual-Redundant Configuration with Two Hubs using Fibre Channel
Copper Support

1
To host

2
To host

CXO6167A

Table 2–3 Key to Figure 2–6 Cabling for Dual-Redundant
Configuration with Two Hubs (copper)
Item

Description

Dual Controller

9-port Fibre Channel HUB

5-meter host Fibre Channel cable
10-meter host Fibre Channel cable

Part No.
—
DS–DHGGA–CA
17–04718–06
17–04718–07

2–18

HSG80 User’s Guide

1. Stop all I/O from the host to its devices on the bus to which you are
connecting the controllers.
2. Connect the Fibre Channel cable from Port 1 on controller A to Port 9
on hub 1. Repeat this step to connect the second cable from Port 1 on
controller B to Port 8 on hub 1.
3. Connect another Fibre Channel cable from Port 2 on controller A to Port
1 on hub 2. Repeat this step to connect the final cable from Port 2 on
controller B to Port 2 on hub 2.
4. Connect each hub to their respective host according to the instructions
in the Getting Started manual.
5. Route and tie the cables as desired.
Restart the I/O from the host. Some operating systems may require you
to restart the host to see the devices attached to the new controller.

Configuring an HSG80 Array Controller

2–19

Use the following steps and Figure 2–7 to connect your dual-redundant
controllers to the host using two hubs with optical support:
Figure 2–7 Cabling for Dual-Redundant Configuration with Two Hubs using Fibre Channel
Optical Support
2

To host

2
3

To host
CXO6496A

2–20

HSG80 User’s Guide

Table 2–4 Key to Figure 2–7 Cabling for Dual-Redundant
Configuration with Two Hubs (optical)
Item

Description

Part No.

Dual Controller

—

12-Port Fibre Channel HUB

DHGGA-CA

17–04820–01
17–04820–02
17–04820–03
17–04820–04
17–04820–05
17–04820–06
17–04820–07
17–04820–08
17–04820–09
17–04820–10
17–04820–11
17–04820–12

1. Stop all I/O from the host to its devices on the bus to which you are
connecting the controllers.
2. Connect the Fibre Channel cable from Port 1 on controller A to Port 9
on hub 1. Repeat this step to connect the second cable from Port 1 on
controller B to Port 8 on hub 1.
3. Connect another Fibre Channel cable from Port 2 on controller A to Port
1 on hub 2. Repeat this step to connect the final cable from Port 2 on
controller B to Port 2 on hub 2.
4. Connect each hub to their respective host according to the instructions
in the Getting Started manual.
5. Route and tie the cables as desired.
6. Restart the I/O from the host. Some operating systems may require you
to restart the host to see the devices attached to the new controller.

Configuring an HSG80 Array Controller

2–21

Using One Hub
Use the following steps and Figure 2–8 to connect your dual-redundant
controllers to the host using one hub with copper support:
Figure 2–8 Cabling for Dual-Redundant Configuration with One
Hub using Fibre Channel Copper Support
1

2
To host
CXO6234A

Table 2–5 Key to Figure 2–8 Cabling for Dual-Redundant
Configuration with One Hub using Fibre Channel
Copper Support
Item

Description

Dual Controller

9-port Fibre Channel HUB

5-meter host Fibre Channel cable
10-meter host Fibre Channel cable

Part No.
—
DS-DHGGA-CA
17-04718-06
17-04718-07

2–22

HSG80 User’s Guide

3. Connect the Fibre Channel cable from Port 1 on controller A to Port 9
on hub 1. Repeat this step to connect the second cable from Port 1 on
controller B to Port 8 on hub 1.
4. Connect another Fibre Channel cable from Port 2 on controller A to Port
1 on hub 2. Repeat this step to connect the final cable from Port 2 on
controller B to Port 2 on hub 2.
5. Connect each hub to their respective host according to the instructions
supplied in the Getting Started manual.
6. Route and tie the cables as desired.
7. Restart the I/O from the host. Some operating systems may require you
to restart the host to see the devices attached to the new controller.
Use the following steps and Figure 2–9 to connect your dual-redundant
controllers to the host using one hub with copper support:
Figure 2–9 Cabling for Dual-Redundant Configuration with One Hub using Fibre Channel
Optical Support
1

To host
2

CXO6497A

Configuring an HSG80 Array Controller

2–23

Table 2–6 Key to Figure 2–9 Cabling for Dual-Redundant
Configuration with One Hub using Fibre Channel
Optical Support
Item

Description

Part No.

Dual Controller

—

12-Port Fibre Channel HUB

DHGGA-CA

17–04820–01
17–04820–02
17–04820–03
17–04820–04
17–04820–05
17–04820–06
17–04820–07
17–04820–08
17–04820–09
17–04820–10
17–04820–11
17–04820–12

1. Stop all I/O from the host to its devices on the bus to which you are
connecting the controllers.
2. For this configuration, set Port 2 off-line using the SET
THIS_CONTROLLER PORT_2_TOPOLOGY=OFFLINE command.
See Appendix B, “CLI Commands,” for details about the SET
command.
3. Connect the Fibre Channel cable from Port 1 on controller A to Port 9
on hub 1. Repeat this step to connect the second cable from Port 1 on
controller B to Port 8 on hub 1.
4. Connect another Fibre Channel cable from Port 2 on controller A to Port
1 on hub 2. Repeat this step to connect the final cable from Port 2 on
controller B to Port 2 on hub 2.
5. Connect each hub to their respective host according to the instructions
supplied in the Getting Started manual.
6. Route and tie the cables as desired.
7. Restart the I/O from the host. Some operating systems may require you
to restart the host to see the devices attached to the new controller.

3–1

CHAPTER

Creating Storagesets

This chapter provides information to help you create storagesets for your
subsystem. The procedure in this chapter takes you through the planning steps and
procedures for creating storagesets.

3–2

HSG80 User’s Guide

Introduction
Storagesets are implementations of RAID technology, also known as a
“Redundant Array of Independent Disks.” Every storageset shares one
important feature: each one looks like a single storage unit to the host,
regardless of the number of drives it uses.
You can create storage units by combining disk drives into storagesets,
such as stripesets, RAIDsets, and mirrorsets, or by presenting them to
the host as single-disk units, as shown in Figure 3–1.

n
n
n
n

Stripesets (RAID 0) combine disk drives in serial to increase
transfer or request rates.
Mirrorsets (RAID 1) combine disk drives in parallel to provide a
highly-reliable storage unit.
RAIDsets (RAID 3/5) combine disk drives in serial—as do
stripesets—but also store parity data to ensure high reliability.
Striped mirrorsets (RAID 0+1) combine mirrorsets in serial to
provide the highest throughput and availability of any storage unit.

Controllers can support the number of RAIDsets as listed in Table 3-1.
For a complete discussion of RAID, refer to The RAIDBOOK—A
Source Book for Disk Array Technology.

Creating Storagesets

Figure 3–1

Units Created from Storagesets, Partitions, and
Drives
Unit
Unit
Mirrorset

Unit
Stripeset

Partitioned
storageset
RAIDset

Unit

Striped
mirrorset

Disk drives

Unit

Partitioned
disk drive
Unit
CXO5368B

Table 3–1 Controller Limitations for RAIDsets
RAIDset Type

Limit

Total number of RAID5
Total number of RAID5 + RAID1
Total number of RAID5 + RAID1 + RAID0

20
30
45

3–3

3–4

HSG80 User’s Guide

Planning and Configuring Storagesets
Use this procedure to plan and configure the storagesets for your
subsystem. Use the references in each step to locate details about
specific commands and concepts.
1. Create a storageset and device profile. See “Creating a Storageset and
Device Profile,” page 3–5, for suggestions about creating a profile.
2. Determine your storage requirements. Use the questions in
“Determining Storage Requirements,” page 3–7, to help you.
3. Choose the type of storagesets you need to use in your subsystem. See
“Choosing a Storageset Type,” page 3–8, for a comparison and
description of each type of storageset.
4. Select names for your storagesets and units. See “Creating a Storageset
Map,” page 3–32, for details about selecting names.
5. Assign unit numbers to storagesets so the host can access the units.
See“Creating a Storageset Map,” page 3–32, for information about how
to assign units numbers to storagesets.
6. Create a storageset map to help you configure your subsystem. See
“Creating a Storageset Map,” page 3–32, for suggestions about creating
a storageset map.
7. If you are going to partition your storagesets, plan the partitions. See
“Planning Partitions,” page 3–37, for information about partitions and
how to plan for them.
8. Choose the switches that you will want to set for your storagesets and
devices. See“Choosing Switches for Storagesets and Devices,” page
3–39, for a description of the switches you can select for storagesets.
9. Configure the storagesets you have planned using one of these methods:

Use StorageWorks Command Console (SWCC), a Graphical User
Interface (GUI), to set up and manage RAID storage subsystems.
See the SWCC Getting Started guide for details about using SWCC
to configure your storagesets.
Use CLI commands. This method allows you flexibility in defining
and naming storagesets. See “Configuring Storagesets with CLI
Commands,” page 3–55, for information about configuring each
type of storageset using CLI commands.

Creating Storagesets

3–5

Creating a Storageset and Device Profile
Creating a profile for your storagesets and devices can help simplify the
configuration process. This chapter helps you to choose the storagesets
that best suit your needs and make informed decisions about the
switches that you can enable for each storageset or storage device that
you configure in your subsystem.
Familiarize yourself with the kinds of information contained in a
storageset profile, as shown in Figure 3–2.
Appendix A, “System Profiles,” contains blank profiles that you can
copy and use to record the details for your storagesets. Use the
information in this chapter to help you make decisions when creating
storageset profiles.

3–6

HSG80 User’s Guide

Figure 3–2

A Typical Storageset Profile
Type of storageset

_____ Mirrorset

__✔_ RAIDset

_____ Stripeset

_____ Striped Mirrorset

Storageset Name ... accept default values
Disk Drives............ DISK10300, DISK20300, DIS30300
Unit Number......... accept default
Partitions
Unit #

Unit #

RAIDset Switches
Reconstruction Policy

_✔ Normal (default)
___ Fast

Reduced Membership

_✔ No (default)
___ Yes, missing:

Replacement Policy

_✔ Best performance (default)
___ Best fit
___ None

Mirrorset Switches
Replacement Policy

Copy Policy

___ Best performance (default) ___ Normal (default)
___ Best fit
___ Fast
___ None

Read Source

___ Least busy (default)
___ Round robin
___ Disk drive:

Initialize Switches
Chunk size

✔ Automatic (default)
___ 64 blocks
___ 128 blocks
___ 256 blocks
___ Other:

Save Configuration

Metadata

✔ Destroy (default)
___ Retain

___ No (default)
_✔ Yes

Unit Switches
Read Cache

Read-Ahead Cache

Maximum Cache Transfer

✔ Yes (default)
___ No

✔ 32 blocks (default)
___ Other:

Write Cache

Write Protection

Availability

✔ No (default)
___ Yes

✔ Run (default)
___ NoRun

___ Yes (default)
✔ No

Creating Storagesets

3–7

Determining Storage Requirements
Start the planning process by determining your storage requirements.
Here are a few of the questions you should ask yourself:

n
n

What applications or user groups will access the subsystem? How
much capacity do they need?
What are the I/O requirements? If an application is data-transfer
intensive, what is the required transfer rate? If it is I/O-request
intensive, what is the required response time? What is the read/
write ratio for a typical request?
Are most I/O requests directed to a small percentage of the disk
drives? Do you want to keep it that way or balance the I/O load?
Do you store mission-critical data? Is availability the highest
priority, or would standard backup procedures suffice?

Use your responses to these questions along with Figure 3–2 to
determine the types of storagesets you should create to satisfy your
organization’s requirements.

3–8

HSG80 User’s Guide

Choosing a Storageset Type
Different applications may have different storage requirements, so you
will probably want to configure more than one kind of storageset in
your subsystem.
All of the storagesets described in this book implement RAID
(Redundant Array of Independent Disks) technology. Consequently,
they all share one important feature: each storageset, whether it
contains two disk drives or ten, looks like one large, virtual disk drive
to the host.
Table 3–2 compares different kinds of storagesets to help you
determine which ones satisfy your requirements.
Table 3–2 A Comparison of Different Kinds of Storagesets
Storageset

Relative
Availability

Request Rate
(Read/Write)
I/O per second

Transfer Rate
(Read/Write) MB
per second

Applications

Array of disk drives Equivalent to a
(JBOD)
single disk drive
Stripeset
Proportionate to
number of disk
(RAID 0)
drives; worse than
single disk drive
Mirrorset
Excellent

Identical to single
disk drive
Excellent if used
with large chunk
size

Identical to single
disk drive
Excellent if used
with small chunk
size

Good/Fair

System drives;
critical files

(RAID1)
RAIDset

Excellent

Excellent/Fair

Good/Poor

(RAID 3/5)
Striped Mirrorset

Excellent

Excellent if used
with large chunk
size

Excellent if used
with small chunk
size

High request rates,
read-intensive,
data lookup
Any critical
response-time
application

(RAID 0+1)

High performance
for non-critical
data

For a comprehensive discussion of RAID, refer to The RAIDBOOK—A
Source Book for Disk Array Technology.

Using Stripesets to Increase I/O Performance
Stripesets enhance I/O performance by spreading the data across
multiple disk drives. Each I/O request is broken into small segments

Creating Storagesets

3–9

called “chunks.” These chunks are then “striped” across the disk drives
in the storageset, thereby allowing several disk drives to participate in
one I/O request to handle several I/O requests simultaneously.
For example, in a three-member stripeset that contains disk drives
10000, 20000, and 30000, the first chunk of an I/O request is written to
10000, the second to 20000, the third to 30000, the fourth to 10000, and
so forth until all of the data has been written to the drives.
Figure 3–3

Striping Lets Several Disk Drives Participate in Each
I/O Request
6
1

5
2

Disk 10000

Chunk

Disk 20000

Disk 30000

6
CXO5507A

The relationship between the chunk size and the average request size
determines if striping maximizes the request rate or the data-transfer
rate. You can set the chunk size or let the controller set it automatically.
See “Chunk Size,” page 3–47, for information about setting the chunk
size.
A major benefit of striping is that it balances the I/O load across all of
the disk drives in the storageset. This can increase the subsystem’s
performance by eliminating the hot spots, or high localities of
reference, that occur when frequently-accessed data becomes
concentrated on a single disk drive.

3–10

HSG80 User’s Guide

Considerations for Planning a Stripeset
Keep the following points in mind as you plan your stripesets:

n
n

A controller can support up to 45 storagesets, consisting of
stripesets, mirrorsets and RAIDsets (refer to Table 3–1).
Reporting methods and size limitations prevent certain operating
systems from working with large stripesets. See the HSG80 Array
Controller ACS Version 8.2G Release Notes or the Getting Started
Guide that came with your platform kit for details about these
restrictions.
A storageset should only contain disk drives of the same capacity.
The controller limits the capacity of each member to the capacity of
the smallest member in the storageset when the storageset is
initialized (the base member size). Thus, if you combine 9 GB disk
drives with 4 GB disk drives in the same storageset, the 4 GB disk
drive will be the base member size, and you will waste 5 GB of
capacity on each 9 GB member.
If you need high performance and high availability, consider using a
RAIDset, striped mirrorset, or a host-based shadow of a stripeset.

Striping does not protect against data loss. In fact, because the
failure of one member is equivalent to the failure of the entire
stripeset, the likelihood of losing data is higher for a stripeset than
for a single disk drive.
For example, if the mean time between failures (MTBF) for a single
disk is one hour, then the MTBF for a stripeset that comprises N
such disks is l/N hours. As another example, if a single disk’s
MTBF is 150,000 hours (about 17 years), a stripeset comprising
four of these disks would only have an MTBF of slightly more than
four years.
For this reason, you should avoid using a stripeset to store critical
data. Stripesets are more suitable for storing data that can be
reproduced easily or whose loss does not prevent the system from
supporting its critical mission.

Evenly distribute the members across the device ports to balance
load and provide multiple paths as shown in the Figure 3–4.

Creating Storagesets

Figure 3–4
1

3–11

Distribute Members across Ports
Device ports
2 3 4 5

6
Backplane

4
0
3
0
0

3
0
2
0
0
2
0
1
0
0

1
0
0
0
0

6
CXO6235A

n
n

Stripesets contain between 2 and 24 members.
Stripesets are well-suited for the following applications:

n
n
n
n

Storing program image libraries or run-time libraries for rapid
loading
Storing large tables or other structures of read-only data for
rapid application access
Collecting data from external sources at very high data transfer
rates

Stripesets are not well-suited for the following applications:

A storage solution for data that cannot be easily reproduced or
for data that must be available for system operation

3–12

HSG80 User’s Guide

n
n

Applications that make requests for small amounts of
sequentially-located data
Applications that make synchronous random requests for small
amounts of data

By spreading the traffic evenly across the buses, you will ensure that no
bus handles the majority of data to the storageset.

Using Mirrorsets to Ensure Availability
Mirrorsets use redundancy to ensure availability, as illustrated in Figure
3–5. For each primary disk drive, there is at least one mirror disk drive.
Thus, if a primary disk drive fails, its mirror drive immediately provides
an exact copy of the data.
Figure 3–5

Mirrorsets Maintain Two Copies of the Same Data

Disk 10100

Disk 10000

Disk 20100

Disk 20000

Disk 30100

Disk 30000

Mirror drives contain
copy of data

CXO5511A

Considerations for Planning a Mirrorset
Keep these points in mind as you plan your mirrorsets:

n
n

A controller can support up to 30 storagesets, consisting of
mirrorsets and RAIDsets. Mirrorsets that are members of a stripeset
count against this limitation (refer to Table 3–1).
Data availability with a mirrorset is excellent but costly—you need
twice as many disk drives to satisfy a given capacity requirement. If
availability is your top priority, consider using redundant power
supplies and dual-redundant controllers.

Creating Storagesets

n
n
n
n

3–13

You can configure up to 30 mirrorsets per controller or pair of dualredundant controllers. Each mirrorset contains a minimum of one
and a maximum of six members.
A write-back cache module is required for mirrorsets, but writeback cache need not be enabled for the mirrorset to function
properly.
Both write-back cache modules must be the same size.
If you’re using more than one mirrorset in your subsystem, you
should put the first member of each mirrorset on different buses as
shown in Figure 3–6. (The first member of a mirrorset is the first
disk drive you add.)
When a controller receives a request to read data from a mirrorset, it
typically accesses the first member of the mirrorset. Read access
depends upon the read source switches, as described in “Read
Source,” page 3–43. If you have several mirrorsets in your
subsystem and their first members are on the same bus, that bus will
be forced to handle the majority of traffic to your mirrorsets. When
a controller receives a request to write data to a mirrorset, it
accesses and writes to all members.

Figure 3–6

First Mirrorset Members on Different Buses
First member
of Mirrorset 1

First member
of Mirrorset 2

CXO5506A

To avoid an I/O bottleneck on one bus, you can simply put the first
members on different buses. Additionally, you can set the readsource switch to Round Robin. See “Read Source,” page 3–43, for
more information about this switch.

Place mirrorsets and RAIDsets on different ports to minimize risk
in the event of a single port bus failure.

3–14

HSG80 User’s Guide

n
n

Mirrorset units are set to WRITEBACK_CACHE by default which
increases a unit’s performance.
A storageset should only contain disk drives of the same capacity.
The controller limits the capacity of each member to the capacity of
the smallest member in the storageset. Thus, if you combine 9 GB
disk drives with 4 GB disk drives in the same storageset, the 4 GB
disk drive will be the base member size, and you waste 5 GB of
capacity on each 9 GB member.
Evenly distribute the members across the device ports to balance
load and provide multiple paths as shown in Figure 3–4 on page
3–11.
Mirrorsets are well-suited for the following:

n
n
n
n

Any data for which reliability requirements are extremely high
Data to which high-performance access is required
Applications for which cost is a secondary issue

Mirrorsets are not well-suited for the following applications:

n
n

Write-intensive applications (JBODs are better for this type of
application, but mirrorsets are preferred over Raid5 RADsets.)
Applications for which cost is a primary issue

Creating Storagesets

3–15

Using RAIDsets to Increase Performance and Availability
RAIDsets are enhanced stripesets—they use striping to increase I/O
performance and distributed-parity data to ensure data availability.
Figure 3–7 illustrates the concept of RAIDsets and parity data.
Figure 3–7

Parity Ensures Availability; Striping Provides Good
Performance
I/O Request
Chunk 1
2

Disk 10000

Chunk 1

Disk 20000

Parity
for
3&4

Disk 30000

Parity
for
1&2

CXO5509A

Just as with stripesets, the I/O requests are broken into smaller
“chunks” and striped across the disk drives until the request is read or
written. But, in addition to the I/O data, chunks of parity data—derived
mathematically from the I/O data—are also striped across the disk
drives. This parity data enables the controller to reconstruct the I/O data
if a disk drive fails. Thus, it becomes possible to lose a disk drive
without losing access to the data it contained. (Data could be lost if a
second disk drive fails before the controller replaces the first failed disk
drive.)
For example, in a three-member RAIDset that contains disk drives
10000, 20000, and 30000, the first chunk of an I/O request is written to
10000, the second to 20000, then parity is calculated and written to
30000; the third chunk is written to 30000, the fourth to 10000, and so
on until all of the data is saved.

3–16

HSG80 User’s Guide

The relationship between the chunk size and the average request size
determines if striping maximizes the request rate or the data-transfer
rates. You can set the chunk size or let the controller set it
automatically. See “Chunk Size,” page 3–47, for information about
setting the chunk size.

Considerations for Planning a RAIDset
Keep these points in mind as you plan your RAIDsets:

n
n

n
n
n
n
n

n
n
n

A controller can support up to 20 storagesets, consisting of
RAIDsets (refer to Table 3–1).
Reporting methods and size limitations prevent certain operating
systems from working with large RAIDsets. See the HSG80 Array
Controller ACS Version 8.2G Release Notes or the Getting Started
Guide that came with your platform kit for details about these
restrictions.
A cache module is required for RAIDsets, but write-back cache
need not be enabled for the RAIDset to function properly.
Both cache modules must be the same size.
A RAIDset must include at least 3 disk drives, but no more than 14.
Evenly distribute the members across the device ports to balance
load and provide multiple paths as shown in Figure 3–4 on page
3–11.
A storageset should only contain disk drives of the same capacity.
The controller limits the capacity of each member to the capacity of
the smallest member in the storageset when the storageset is
initialzed (the base member size). Thus, if you combine 9 GB disk
drives with 4 GB disk drives in the same storageset, you will waste
5 GB of capacity on each 9 GB member.
RAIDset units are set to WRITEBACK_CACHE by default which
increases a unit’s performance.
RAIDsets and mirrorsets on different ports to minimize risk in the
event of a single port bus failure.
RAIDsets are particularly well-suited for the following:

n
n

Small to medium I/O requests
Applications requiring high availability

Creating Storagesets

n
n
n

3–17

High read request rates
Inquiry-type transaction processing

RAIDsets are not particularly well-suited for the following:

n
n
n
n
n

Write-intensive applications
Applications that require high data transfer capacity
High-speed data collection
Database applications in which fields are continually updated
Transaction processing

Using Striped Mirrorsets for Highest Performance and Availability
As illustrated in Figure 3–8, striped mirrorsets are simply stripesets
whose members are mirrorsets. Consequently, this kind of storageset
combines the performance of striping with the reliability of mirroring.
The result is a storageset with very high I/O performance and high data
availability.
Figure 3–8

Striping and Mirroring in the Same Storageset
Stripeset

Mirrorset1

Mirrorset2

Mirrorset3

Disk 10100

Disk 20100

Disk 30100

Disk 10000

Disk 20000

Disk 30000

C'
CXO5508A

The failure of a single disk drive has no effect on this storageset’s
ability to deliver data to the host and, under normal circumstances, it
has very little effect on performance. Because striped mirrorsets do not

3–18

HSG80 User’s Guide

require any more disk drives than mirrorsets, this storageset is an
excellent choice for data that warrants mirroring.

Considerations for Planning a Striped Mirrorset
Plan the mirrorset members, then plan the stripeset that will contain
them. Review the recommendations in “Considerations for Planning a
Stripeset,” page 3–10, and “Considerations for Planning a Mirrorset,”
page 3–12.
There are the following limitations for a striped mirrorset:

n
n
n

A maximum of 24 mirrorsets in a stripeset.
A maximum of 6 disks in each mirrorset.
A maximum of 48 disks in the entire striped mirrorset.

Creating Storagesets

3–19

Cloning Data for Backup
Use the CLONE utility to duplicate the data on any unpartitioned
single-disk unit, stripeset, mirrorset, or striped mirrorset in preparation
for backup. When the cloning operation is done, you can back up the
clones rather than the storageset or single-disk unit, which can continue
to service its I/O load. When you are cloning a mirrorset, CLONE does
not need to create a temporary mirrorset. Instead, it adds a temporary
member to the mirrorset and copies the data onto this new member.
The CLONE utility creates a temporary, two-member mirrorset for each
member in a single-disk unit or stripeset. Each temporary mirrorset
contains one disk drive from the unit you are cloning and one disk drive
onto which CLONE copies the data. During the copy operation, the unit
remains online and active so the clones contain the most up-to-date
data.
After the CLONE utility copies the data from the members to the
clones, it restores the unit to its original configuration and creates a
clone unit you can backup. The CLONE utility uses steps shown in
Figure 3–9 to duplicate each member of a unit.

3–20

HSG80 User’s Guide

Figure 3–9 CLONE Steps for Duplicating Unit Members
Unit
Unit
Temporary mirrorset
Disk10300

Disk10300

New member

Unit
Temporary mirrorset
Unit
Copy

Disk10300

New member

Clone Unit

Clone of Disk10300
CXO5510A

Use the following steps to clone a single-disk unit, stripeset, or
mirrorset:
1. Establish a connection to the controller that accesses the unit you want
to clone.
2. Start CLONE using the following command:
RUN CLONE

3. When prompted, enter the unit number of the unit you want to clone.
4. When prompted, enter a unit number for the clone unit that CLONE will
create.

Creating Storagesets

3–21

5. When prompted, indicate how you would like the clone unit to be
brought online: either automatically or only after your approval.
6. When prompted, enter the disk drives you want to use for the clone
units.
7. Back up the clone unit.

Example
This example shows the commands you would use to clone storage unit
D98. The clone command terminates after it creates storage unit D99, a
clone or copy of D98.
RUN CLONE
CLONE LOCAL PROGRAM INVOKED
UNITS AVAILABLE FOR CLONING:101
98
ENTER UNIT TO CLONE ? 98
CLONE WILL CREATE A NEW UNIT WHICH IS A COPY OF UNIT 98.
ENTER THE UNIT NUMBER WHICH YOU WANT ASSIGNED TO THE
NEW UNIT ? 99
THE NEW UNIT MAY BE ADDED USING ONE OF THE FOLLOWING
METHODS:
1. CLONE WILL PAUSE AFTER ALL MEMBERS HAVE BEEN COPIED. THE
USER MUST THEN PRESS RETURN TO CAUSE THE NEW UNIT TO BE
ADDED.
2. AFTER ALL MEMBERS HAVE BEEN COPIED, THE UNIT WILL BE ADDED
AUTOMATICALLY.
UNDER WHICH ABOVE METHOD SHOULD THE NEW UNIT BE
ADDED[]?1
DEVICES AVAILABLE FOR CLONE TARGETS:
DISK20200 (SIZE=832317)
DISK20300 (SIZE=832317)
DISK30100 (SIZE=832317)
USE AVAILABLE DEVICE DISK20200(SIZE=832317) FOR MEMBER
DISK10300(SIZE=832317) (Y,N) [Y] ? Y
MIRROR DISK10300 C_MA
SET C_MA NOPOLICY
SET C_MA MEMBERS=2
SET C_MA REPLACE=DISK220

3–22

HSG80 User’s Guide

DEVICES AVAILABLE FOR CLONE TARGETS:
DISK20300 (SIZE=832317)
DISK30100 (SIZE=832317)
USE AVAILABLE DEVICE DISK10400(SIZE=832317) FOR MEMBER
DISK10000(SIZE=832317) (Y,N) [Y] ? Y
MIRROR DISK10000 C_MB
SET C_MB NOPOLICY
SET C_MB MEMBERS=2
SET C_MB REPLACE=DISK10400
COPY IN PROGRESS FOR EACH NEW MEMBER. PLEASE BE PATIENT...
.
.
COPY FROM DISK10300 TO DISK10200 IS 100% COMPLETE
COPY FROM DISK10000 TO DISK10400 IS 100% COMPLETE

PRESS RETURN WHEN YOU WANT THE NEW UNIT TO BE CREATED
REDUCE DISK10200 DISK10400
UNMIRROR DISK10300
UNMIRROR DISK10000
ADD MIRRORSET C_MA

DISK10200

ADD MIRRORSET C_MB

DISK10400

ADD STRIPESET C_ST1 C_MA C_MB
INIT C_ST1

NODESTROY CHUNK=128

ADD UNIT D105 C_ST1
D105 HAS BEEN CREATED. IT IS A CLONE OF D104.
CLONE - NORMAL TERMINATION

Creating Storagesets

3–23

Backing Up Your Subsystem Configuration
Your controller stores information about your subsystem configuration
in its nonvolatile memory. This information could be lost if the
controller fails or when you replace a module in your subsystem.
See “Considerations for Saving the Configuration,” page 3–51, and
“Saving Configuration Information in Dual-Redundant
Configurations,” page 3–52, for more information.
You can avoid reconfiguring your subsystem manually by saving
configuration information on one or more of your subsystem disks
using the INITIALIZE SAVE_CONFIGURATION command. The
controller updates the configuration information saved to disk whenever
it changes. If the controller fails or you replace a module, you can
easily restore your subsystem configuration from this information on
the disks. Storing the configuration information uses a small amount of
space on each device.
You do not need to store the configuration on all devices in the
subsystem. You can use the INITIALIZE command without the
SAVE_CONFIGURATION option for any devices on which you do not
want to save the configuration.
You cannot use the SAVE_CONFIGURATION switch on
TRANSPORTABLE disks.

Saving Subsystem Configuration Information to a Single Disk
You can choose to save your subsystem configuration information on a
single disk.
Choose a disk on which to save the information by using the
SAVE_CONFIGURATION switch when you initialize the disk with the
INITIALIZE command. Use the following command:
INITIALIZE DISK nnn SAVE_CONFIGURATION

Saving Subsystem Configuration Information to Multiple Disks
You can save your subsystem configuration information to as many
individual disks as you would like, but you must initialize each using

3–24

HSG80 User’s Guide

the SAVE_CONFIGURATION switch. Use the following command for
each:
INITIALIZE DISK nnn SAVE_CONFIGURATION

Saving Subsystem Configuration Information to a Storageset
You can save your subsystem configuration information to a storageset.
The configuration information is duplicated on every disk that is a
member of the storageset. Use the following command:
INITIALIZE storageset-name SAVE_CONFIGURATION

Displaying the Status of the Save Configuration Feature
You can use the SHOW THIS_CONTROLLER FULL command to
find out if the save configuration feature is active and which devices
are being used to store the configuration. The display includes a line
that indicates status and how many devices have copies of the
configuration, as shown in the following example.
SHOW THIS_CONTROLLER FULL
Controller:
HSG80
(C) DEC ZG64100138 Firmware QBFB-0, Hardware CX02
Configured for dual-redundancy with ZG64100209
In dual-redundant configuration
Device Port SCSI address 7
Time: NOT SET
Host port:
SCSI target(s) (1, 3, 11)
Preferred target(s) (3, 11)
TRANSFER_RATE_REQUESTED = 20MHZ
Host Functionality Mode = A
Command Console LUN is target 1, lun 5
Cache:
64 megabyte write cache, version 4
Cache is GOOD
Battery is GOOD
No unflushed data in cache
CACHE_FLUSH_TIMER = DEFAULT (10 seconds)
NOCACHE_UPS
Mirrored Cache:
64 megabyte write cache, version 4
Cache is GOOD
Battery is GOOD
No unflushed data in cache
Extended information:
Terminal speed 19200 baud, eight bit, no parity, 1 stop bit
Operation control: 00000001 Security state code: 75524
Configuration backup enabled on 3 devices

Creating Storagesets

3–25

The following example shows sample devices with the
SAVE_CONFIGURATION switch enabled:
$ SHOW DEVICES FULL
Name

Type

Port Targ

Lun

Used by

-----------------------------------------------------------------------------DISK10000
disk
1
0
0
S2
DEC
Switches:

RZ28M

NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.00 MHZ negotiated)
Size: 4108970 blocks
Configuration being backed up on this container
DISK30300

disk
DEC

3
RZ28M

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.00 MHZ negotiated)
Size: 4108970 blocks
Configuration being backed up on this container

3–26

HSG80 User’s Guide

Controller and Port Worldwide Names (Node IDs)
A worldwide name (node ID) is a unique 64-bit number assigned to a
subsystem by the Institute of Electrical and Electronics Engineers
(IEEE) and set by DIGITAL manufacturing prior to shipping. The
worldwide name assigned to a subsystem never changes.
Each subsystem’s worldwide name ends in zero, for example
5000-1FE1-FF0C-EE00. The controller port ID numbers are derived
from the worldwide name. In a subsystem with two controllers (a dualredundant configuration) the port ID of Port 1 for both controllers is the
worldwide ID plus 1. In this example, both controllers’ Port 1 port ID
would be 5000-1FE1-FF0C-EE01. Similarly, both controllers would
have the same port ID for Port 2, 5000-1FE1-FF0C-EE02. The
controllers automatically assign their port IDs.
Use the CLI command SHOW THIS_CONTROLLER to display the
subsytem’s worldwide name. See Appendix B, “CLI Commands,” for
more information about the SHOW command and worldwide names.
The CLI uses the term node ID for worldwide names. When you enter
the SHOW command, the subsystem worldwide name (node ID)
displays as the REPORTED NODEID and will look like the following:
5000-1FE1-FF0C-EE00

Restoring Worldwide Names (Node IDs)
When you remove a controller to replace it in a dual-redundant
configuration, the remaining controller remembers the subsystem
worldwide name (node ID). When you install the replacement
controller, the remaining controller tells the new controller the
worldwide name; the replacement controller assumes the correct port
ID numbers.
If you have a single controller configuration, you must have a save
configuration disk if you want to be able to automatically restore the
worldwide name in the event of a failure. In this case the controller
could read the worldwide name from the save configuration disk.
If a situation occurs that requires you to restore the worldwide name,
you can restore it using the worldwide name and check sum printed on
the sticker on the frame into which your controller is inserted. See the
SET controller command in Appendix B, “CLI Commands,” for details
about setting the worldwide name (node ID).

Creating Storagesets

3–27

Unit World Wide Names (LUN IDs)
In addition, each unit has its own world wide name, or LUN ID. This is
a unique, 128-bit value that the controller assigns at the time of unit
initialization. It cannot be altered by the user but does change when the
unit is re-initialized. Use the SHOW command to list the LUN ID.
Caution Each subsystem has its own unique worldwide name (node
ID). This ID can be found on a sticker, which is located on top of the
frame that houses the controller(s), the EMU, the PVA, and cache
modules. If you attempt to set the subsystem worldwide name to a
name other than the one that came with the subsystem, the data on the
subsystem will not be accessible. Never set two subsystems to the same
worldwide name, or data corruption will occur.

3–28

HSG80 User’s Guide

Assigning Unit Numbers for Host Access to Storagesets
You will need to assign a unit number to each storageset, single disk
unit, or storage device that you want your host to know about in your
subsystem. The host uses these numbers to indicate the source or target
for every I/O request it sends to a controller.
Each unit number contains the following:

n
n

A letter that indicates the kind of devices in the storage unit. For
example, D for disk drives; P for passthrough devices (i.e. tape
drives, loaders, and libraries).
A number from 0-199.

Assigning Unit Numbers in Transparent Failover Mode
Each controller has two ports, Port 1 and Port 2, as shown in Figure
3–10. There is a set number of units that are accessible, depending on
the host operating system. This maximum is a limitation of the host.
In transparent failover mode, the range of assignable units is 0-99 on
Port 1, and 100-199 on Port 2, regardless of what unit offset is set on
the host. In other words, all hosts on Port 2 have a unit offset of 100.
Do not split partitioned storagesets across ports; they must be on the
same port.
See Appendix B, “CLI Commands,” for details about the ADD UNIT
command.
Figure 3–10 Controller Port ID and Unit Numbers in Transparent
Failover Mode
Controller A
Port 1 (Primary)

Port 2 (Standby)

Units 0-99

Units 100-199
Controller B

Port 1 (Standby)

Port 2 (Primary)

Units 0-99

Units 100-199
CXO6187A

Creating Storagesets

3–29

Assigning Unit Numbers in Multiple Bus Failover Mode
In multiple bus failover mode, the range of assignable units, which are
accessible from any port on the subsystem, is 0-199. Hosts obtain units
by reserving the unit for sole access. This is done on a first-available
basis. Figure 3–11 illustrates the controller port ID and unit numbers in
multiple bus failover mode.
Figure 3–11 Controller Port ID Numbers and Unit Numbers in
Mulitple Bus Failover Mode
Controller A
Port 1 (Primary)

Port 2 (Primary)

Units 0-199

Units 0-199
Controller B

Port 1 (Primary)

Port 2 (Primary)

Units 0-199

Units 0-199
CXO6454A

Assigning Unit Offsets
Unit offsets are used to define the first unit number that a host is able to
access on the controller. When assigning unit offsets, keep in mind that
the unit offset is settable on a per-host basis. Thus, one host can have a
unit offset of 0 and see units 0-99 as LUNs 0-99, and another host can
have a unit offset of 10 and see units 10-99 as LUNs 0-89 (controller
unit number 10 is seen at the host as LUN 0). This is useful for hosts
that have a limited LUN addressing range.
Figure 3–12 depicts the use of unit offsets on a per-host basis. Note that
controller units 0-99 are presented only on Port 1, and units 100-199
are presented only on Port 2. This implies that Port 1 hosts can have a
unit offset range of 0-99, and Port 2 hosts can have a unit offset range
of 100-199.

3–30

HSG80 User’s Guide

Figure 3–12 LUN Presentation Using Unit Offset on a Per-Host
Basis
Controller
Units

HOST 1
on Port 1
Dev Offset: 0

HOST 2
on Port 1
Dev Offset: 20

LUN 0

LUN 1

LUN 2

LUN 3

D20

LUN 20

LUN 0

D21

LUN 21

LUN 1

HOST 3
on Port 2
Dev Offset: 100

D100

LUN 0

D101

LUN 1

D102

LUN 2

D130

LUN 30

D131

LUN 31
CXO6455A

Assigning Access Paths
The HSG80 subsystem allows the user to specify unit access privileges
to limit host access. This feature is defined on a unit-by-unit basis.
You can enable host access to a unit by mapping the unit accessible
through the specified host paths. (A path is the logical connection
between the host and the controller.) The path is referenced by the
name attached to the logical connection. Once the unit is set for access
through a path, the access privilege is defined.
Paths may be automatically added to the system through the host fibre
channel login process or manually with the ADD command. See
Appendix B, “CLI Commands,” for more information about this
procedure.
Note Even when hosts are automatically entered, user intervention is
still recommended to set a meaningful connection name.

Creating Storagesets

3–31

By default, host access is set to ALL. If you wish to have the unit
access limited, you must first disable access to ALL, then set it to a
specified host access path.
You can define a unit’s access privileges with the ADD command.
These access privileges can be changed using the SET command. See
Appendix B, “CLI Commands,” for more information about these
commands.
Also, see Chapter 2, “Configuring an HSG80 Array Controller,”for
configuration rules and requirements that you should consider when
setting up and working in a multiple host environment.

3–32

HSG80 User’s Guide

Creating a Storageset Map
Configuring your subsystem will be easier if you know how the
storagesets correspond to the disk drives in your subsystem. You can
see this relationship by creating a storageset map like the one shown in
Figure 3–13. This storageset map is for a subsystem that contains two
RAIDsets, two mirrorsets, and three disk drives in the spareset. Each
enclosure also has redundant power supplies.
Figure 3–13 Storageset Map

To create a storageset map:
1. Copy the template from “Enclosure Template,” page A–4.

Creating Storagesets

3–33

2. Establish a local or remote connection to one of the controllers in your
subsystem.
3. Show the devices that are assigned to the controller. Use the following
command:
SHOW DEVICES

4. Locate each device assigned to the controller and record its location on
your copy of the cabinet template. Use the following command:
LOCATE device_name

The LOCATE command causes the device’s LED to flash continuously.
5. Turn off the LED, using the following command:
LOCATE CANCEL

The controller names each device based on its Port-Target-LUN (PTL)
location. See the next section for details about the controller’s PTL
addressing convention. Repeat step 2 through step 4 for each controller
or dual-redundant pair of controllers.
6. After you have mapped the devices to your cabinet template, create the
storageset map by circling each group of disk drives that you want to
combine into a storageset or put into the spareset. Label each group with
a storageset name, for example: RAID1 for a RAIDset; Mirr1 for a
mirrorset; and Stripe1 for a stripeset.

Device PTL Addressing Convention within the Controller
Your controller has six SCSI–2 device ports. Each device port connects
to an enclosure that supports 1 to 4 devices or “targets.” Every device
uses LUN 0.
The controller identifies the location of devices based on a Port-TargetLUN (PTL) numbering scheme. The controller uses the PTL address to
locate devices.

n
n

P—Designates the controller’s SCSI device port number (1 through
6).
T—Designates the target identification (ID) number of the device.
Valid target ID numbers for a single-controller configuration and
dual-redundant controller configuration are 0 through 15, excluding
ID numbers 4 through 7. ID numbers 4 and 5 are never used.
L—Designates the logical unit (LUN) of the device.

3–34

HSG80 User’s Guide

Note The controller operates with BA370 rack-mountable enclosures
that are assigned ID numbers 0, 2, and 3. These ID numbers are set
through the PVA module. Enclosure ID number 1, which houses
devices at targets 4 through 7, is not supported. Do not use device target
ID numbers 4 through 7 in a storage subsystem.
Place one space between the port number, target number, and the twodigit LUN number when entering the PTL address. An example of a
PTL address is shown below.
Figure 3–14 PTL Naming Convention

1 02 00
LUN 00 (leading zeros are not required)
Target 02 (leading zeros are not required)
Port 1
Figure 3–15 shows the addresses for each device in an extended
configuration. Use this figure along with “Configuration Rules,” page
2–2, to help you work with the devices in your configuration.
Caution Selecting SCSI–3 mode enables access to the Command
Console LUN (CCL) by all hosts. If the hosts access the CCL
simultaneously, unpredictable consequences can occur. In cases where
the CCL can be accessed through multiple paths and LUNs, system
administrators of each host must not attempt to access the CCL
simultaneously.

Target
numbers
1

10100

10200

10300

20000

20100

20200

20300

30000

30100

30200

30300

40000

40100

40200

40300

50000

50100

50200

50300

60000

60100

60200

60300

10900

11000

11100

20800

20900

21000

21100

30800

30900

31000

31100

40800

40900

41000

41100

50800

50900

51000

51100

60800

60900

61000

61100

PVA 2

8
EMU

11200

11300

11400

11500

21200

21300

21400

21500

31200

31300

31400

31500

41200

41300

41400

41500

51200

51300

51400

51500

61200

61300

61400

61500

PVA 3

EMU

CXO5851A

PTL location = Device port number = 3
Target number = 08
LUN = 00

10800

Device port numbers

0
PVA 0
EMU
Controller A
Controller B
Cache A
Cache B

10000

Figure 3–15 PTL Addressing in a Configuration
Creating Storagesets

3–35

3–36

HSG80 User’s Guide

In Figure 3–15, the controller addresses DISK30800 through device
port 3, target 08, LUN 00. This PTL location indicates the pathway the
controller uses to address a disk drive (device) in the subsystem. It also
indicates the device name.
The controller uses the PTL location to name each device that you add
to your subsystem with StorageWorks Command Console or the
CONFIG utility. (Factory-installed devices are added with the CONFIG
utility. Thus, their names derive from their PTL locations.) For
example, if the controller finds a disk in PTL 10200, it names it
DISK10200.
When your controller receives an I/O request, it identifies the storageset
unit number for the request, then correlates the unit number to the
storageset name. From the storageset name, the controller locates the
appropriate device for the I/O request. (For example, the RAIDset
“RAID1” might contain DISK10000, DISK20000, and DISK30000.)
The controller generates the read or write request to the appropriate
device using the PTL addressing convention. Figure 3–16 illustrates the
concept of PTL addressing.
Figure 3–16 Locating Devices using PTLs
D100

Host addressable
unit number

RAID1

Storageset
name

Controller
PTL addresses
Disk 10000

Disk 20000

Disk 30000
CXO6186A

Creating Storagesets

3–37

Planning Partitions
Use partitions to divide a storageset or disk drive into smaller pieces,
which can each be presented to the host as its own storage unit. Figure
3–17 shows the conceptual effects of partitioning a single-disk unit.
Figure 3–17 Partitioning a Single-Disk Unit
Partition 1
Partition 2
Partition 3

CXO-5316A-MC

You can create up to eight partitions per disk drive, RAIDset, mirrorset,
stripeset, or striped mirrorset. Each partition has its own unit number so
that the host can send I/O requests to the partition just as it would to
any unpartitioned storageset or device. Because partitions are
separately-addressable storage units, you can partition a single
storageset to service more than one user group or application.

Defining a Partition
Partitions are expressed as a percentage of the storageset or single disk
unit that contains them. For mirrorsets and single disk units, the
controller allocates the largest whole number of blocks that are equal to
or less than the percentage you specify. For RAIDsets and stripesets,
the controller allocates the largest whole number of stripes that are less
than or equal to the percentage you specify. For stripesets, the stripe
size = chunk size x number of members. For RAIDsets, the stripe size =
chunk size x (number of members-1).
An unpartitioned storage unit has more capacity than a partition that
uses the whole unit because each partition requires five blocks of
administrative metadata. Thus, a single disk unit that contains one
partition can store n-5 blocks of user or application data.
See “Partitioning a Storageset or Disk Drive,” page 3–61, for
information on manually partitioning a storageset or single-disk unit.

3–38

HSG80 User’s Guide

Guidelines for Partitioning Storagesets and Disk Drives
Keep these points in mind as you plan your partitions:

n
n

You can create up to eight partitions per storageset or disk drive.
All of the partitions on the same storageset or disk drive must be
addressed through the same controller port. This ensures a
transparent failover of devices should one of the dual-redundant
controllers fail.
Partitions cannot be combined into storagesets. For example, you
cannot divide a disk drive into three partitions, then combine those
partitions into a RAIDset.
Partitioned storagesets cannot function in multiple bus failover
dual-redundant configurations. Because they are not supported, you
must delete your partitions before configuring the controllers for
multiple bus failover.
Once you partition a container, you cannot unpartition it without
reinitializing the container.
Just as with storagesets, you do not have to assign unit numbers to
partitions until you are ready to use them.

Creating Storagesets

3–39

Choosing Switches for Storagesets and Devices
Depending upon the kind of storageset or device you are configuring,
you can enable the following options or “switches”:

n
n
n
n

RAIDset and mirrorset switches
Initialize switches
Unit switches
Device switches

Enabling Switches
If you use StorageWorks Command Console to configure the device or
storageset, you can set switches from the command console screens
during the configuration process. The Command Console automatically
applies them to the storageset or device. See Getting Started with
Command Console for information about using the Command Console.
If you use CLI commands to configure the storageset or device
manually, the procedures in “Configuring Storagesets with CLI
Commands,” page 3–55, indicate when and how to enable each switch.

Changing Switches
You can change the RAIDset, mirrorset, device, and unit switches at
any time. See “Changing Switches for a Storageset or Device,” page
3–66, for information about changing switches for a storageset or
device.
You cannot change the initialize switches without destroying the data
on the storageset or device. These switches are integral to the
formatting and can only be changed by re-initializing the storageset.
(Initializing a storageset is similar to formatting a disk drive; all of the
data is destroyed during this procedure.)

3–40

HSG80 User’s Guide

RAIDset Switches
You can enable the following switches to control how a RAIDset
behaves to ensure data availability:

n
n
n

Replacement policy
Reconstruction policy
Membership

Replacement Policy
Specify a replacement policy to determine how the controller replaces a
failed disk drive:

POLICY=BEST_PERFORMANCE (default) puts the failed disk
drive in the failedset then tries to find a replacement (from the
spareset) that is on a different device port than the remaining
operational disk drives. If more than one disk drive meets this
criterion, this switch selects the drive that also provides the best fit.
POLICY=BEST_FIT puts the failed disk drive in the failedset then
tries to find a replacement (from the spareset) that equals or exceeds
the base member size (smallest disk drive at the time the RAIDset
was initialized). If more than one disk drive meets this criterion,
this switch selects one that also provides the best performance.
NOPOLICY puts the failed disk drive in the failedset and does not
replace it. The storageset operates with less than the nominal
number of members until you specify a replacement policy or
manually replace the failed disk drive.

Reconstruction Policy
Specify the speed with which the controller reconstructs the data from
the remaining operational disk drives and writes it to a replacement
disk drive:

n
n

RECONSTRUCT=NORMAL (default) balances the overall
performance of the subsystem against the need for reconstructing
the replacement disk drive.
RECONSTRUCT=FAST gives more resources to reconstructing
the replacement disk drive, which may reduce the subsystem’s
overall performance during the reconstruction task.

Creating Storagesets

3–41

Membership
Indicate to the controller that the RAIDset you are adding is either
complete or reduced, which means it is missing one of its members:

n
n

NOREDUCED (default) indicates to the controller that all of the
disk drives are present for a RAIDset.
REDUCED lets you add a RAIDset that is missing one of its
members. For example, if you dropped or destroyed a disk drive
while moving a RAIDset, you could still add it to the subsystem by
using this switch.

3–42

HSG80 User’s Guide

Mirrorset Switches
You can enable the following switches to control how a mirrorset
behaves to ensure data availability:

n
n
n

Replacement policy
Copy speed
Read source

Replacement Policy
Specify a replacement policy to determine how the controller replaces a
failed disk drive:

POLICY=BEST_PERFORMANCE (default) puts the failed disk
drive in the failedset then tries to find a replacement (from the
spareset) that is on a different device port than the remaining
operational disk drives. If more than one disk drive meets this
criterion, this switch selects the drive that also provides the best fit.
POLICY=BEST_FIT puts the failed disk drive in the failedset then
tries to find a replacement (from the spareset) that most closely
matches the size of the remaining, operational disk drives. If more
than one disk drive meets this criterion, this switch selects the one
that also provides the best performance.
NOPOLICY puts the failed disk drive in the failedset and does not
replace it. The storageset operates with less than the nominal
number of members until you specify a replacement policy or
manually replace the failed disk drive.

Copy Speed
Specify a copy speed to determine the speed with which the controller
copies the data from an operational disk drive to a replacement disk
drive:

n
n

COPY=NORMAL (default) balances the overall performance of
the subsystem against the need for reconstructing the replacement
disk drive.
COPY=FAST allocates more resources to reconstructing the
replacement disk drive, which may reduce the subsystem’s overall
performance during the reconstruction task.

Creating Storagesets

3–43

Read Source
Specify the read source to determine how the controller reads data from
the members of a mirrorset:

READ_SOURCE=LEAST_BUSY (default) forces the controller to
read data from the “normal” or operational member that has the
least-busy work queue. If multiple disks have equally short queues,
the controller queries normal local disks for each read request as it
would when READ_SOURCE=ROUND_ROBIN is specified. If no
normal local disk exists, then the controller will query any remote
disks if available.
READ_SOURCE=ROUND_ROBIN forces the controller to read
data sequentially from all “normal” or operational members in a
mirrorset. For example, in a four-member mirrorset (A, B, C, and
D), the controller reads from A, then B, then C, then D, then A, then
B, and so forth. No preference is given to any member. If no normal
local disk exists, then the controller will query any remote disks if
available.
READ_SOURCE=DISKnnnnn forces the controller to always read
data from a particular “normal” or operational member. If the
specified member fails, the controller reads from the least busy
member.

3–44

HSG80 User’s Guide

Device Switches
When you add a disk drive or other storage device to your subsystem,
you can enable the following switches:

n
n

Transportability
Transfer rate

Transportability
Indicate whether a disk drive is transportable when you add it to your
subsystem:

NOTRANSPORTABLE disk drives (default) are marked with
StorageWorks-exclusive metadata. This metadata supports the
error-detection and recovery methods that the controller uses to
ensure data availability. Disk drives that contain this metadata
cannot be used in non-StorageWorks subsystems.
Consider these points when using the NOTRANSPORTABLE
switch:

When you bring non-transportable devices from another
subsystem to your controller subsystem, add the device to your
configuration using the ADD command. Do not initialize the
device, or you will reset and destroy any forced error
information contained on the device.
When you add units, the controller software verifies that the
disks or storagesets within the units contain metadata. To
determine whether a disk or storageset contains metadata, try
to create a unit from it. This causes the controller to check for
metadata. If no metadata is present, the controller displays a
message; initialize the disk or storageset before adding it.

TRANSPORTABLE disk drives can be used in non-StorageWorks
subsystems. Transportable disk drives can be used as single-disk
units in StorageWorks subsystems as well as disk drives in other
systems. They cannot be combined into storagesets in a
StorageWorks subsystem.

Creating Storagesets

3–45

TRANSPORTABLE is especially useful for moving a disk drive
from a workstation into your StorageWorks subsystem. When you
add a disk drive as transportable, you can configure it as a singledisk unit and access the data that was previously saved on it.
Transportable devices have these characteristics:

n
n
n
n

Can be interchanged with any SCSI interface that does not use
the device metadata, for example, a PC.
Cannot have write-back caching enabled.
Cannot be members of a shadowset, storageset, or spareset.
Do not support forced errors.

Consider these points when using the TRANSPORTABLE switch:

Before you move devices from the subsystem to a foreign
subsystem, delete the units and storagesets associated with the
device and set the device as transportable. Initialize the device
to remove any metadata.
When you bring foreign devices into the subsystem with
customer data follow this procedure:

Add the disk as a transportable device. Do not initialize it.

Copy the data the device contains to another nontransportable
unit.
Initialize the device again after resetting it as nontransportable.
Initializing it now places metadata on the device.

n
n

Storagesets cannot be made transportable. Specify
NOTRANSPORTABLE for all disks used in RAIDsets,
stripesets, and mirrorsets.
Do not keep a device set as transportable on a subsystem. The
unit attached to the device loses forced error support which is
mandatory for data integrity on the entire array.

3–46

HSG80 User’s Guide

Device Transfer Rate
Specify a transfer rate that the controller uses to communicate with the
device. Use one of these switches to limit the transfer rate to
accommodate long cables between the controller and a device, such as
a tape library. Use one of the following values:

n
n
n
n

TRANSFER_RATE_REQUESTED=20MHZ (default)
TRANSFER_RATE_REQUESTED=10MHZ
TRANSFER_RATE_REQUESTED=5MHZ
TRANSFER_RATE_REQUESTED=ASYNCHRONOUS

Creating Storagesets

3–47

Initialize Switches
You can enable the following kinds of switches to affect the format of a
disk drive or storageset:

n
n
n

Chunk size (for stripesets and RAIDsets only)
Save configuration
Destroy/Nodestroy

After you initialize the storageset or disk drive, you cannot change
these switches without reinitializing the storageset or disk drive.

Chunk Size
Specify a chunk size to control the stripesize used for RAIDsets and
stripesets:

n
n

CHUNKSIZE=DEFAULT lets the controller set the chunk size
based on the number of disk drives (d) in a stripeset or RAIDset. If
d < 9 then chunk size = 256. If d > 9 then chunk size = 128.
CHUNKSIZE=n lets you specify a chunk size in blocks. The
relationship between chunk size and request size determines
whether striping increases the request rate or the data-transfer rate.

See page B–72 for more information on Chunk Size.
Tip While a storageset may be initialized with a user-selected chunk
size, it is recommended that only the default value be used. The default
value is chosen to produce optimal performance for a wide variety of
loads. The use of a chunk size less than 128 blocks (64K) is strongly
discouraged. There are almost no customer loads for which small
chunk sizes are of value and, in almost all cases, selecting a small
chunk size will severely degrade the performance of the storageset and
the controller as a whole. Use of a small chunk size on any storageset
can result in severe degradation of overall system performance.

Increasing the Request Rate
A large chunk size (relative to the average request size) increases the
request rate by allowing multiple disk drives to respond to multiple
requests. If one disk drive contains all of the data for one request, then

3–48

HSG80 User’s Guide

the other disk drives in the storageset are available to handle other
requests. Thus, in principle, separate I/O requests can be handled in
parallel, thereby increasing the request rate. This concept is shown in
Figure 3–18.
Figure 3–18 Chunk Size Larger than the Request Size
Request A

Chunk size = 128k (256 blocks)

Request B

Request C

Request D

CXO-5135A-MC

Applications such as interactive transaction processing, office
automation, and file services for general timesharing tend to require
high I/O request rates.
Large chunk sizes also tend to increase the performance of random
reads and writes. It is recommended that you use a chunk size of 10 to
20 times the average request size, rounded up to the nearest multiple of
64. In general, a chunk size of 256 works well for UNIX® systems;
128 works well for OpenVMS™ systems.

Creating Storagesets

3–49

Increasing the Data Transfer Rate
A small chunk size relative to the average request size increases the
data transfer rate by allowing multiple disk drives to participate in one
I/O request. This concept is shown in Figure 3–19.
Figure 3–19 Chunk Size Smaller than the Request Size
Chunk size = 128k (256 blocks)

A1
Request A

A2
A3
A4

CXO-5172A-MC

Applications such as CAD, image processing, data collection and
reduction, and sequential file processing tend to require high datatransfer rates.

Increasing Sequential Write Performance
For stripesets (or striped mirrorsets), use a large chunk size relative to
the I/O size to increase the sequential write performance. A chunk size
of 256 generally works well.
Chunk size does not significantly affect sequential read performance.

3–50

HSG80 User’s Guide

Maximum Chunk Size for RAIDsets
Do not exceed the chunk sizes shown in Table 3–3 for a RAIDset. (The
maximum chunk size is derived by 2048/(d – 1) where d is the number
of disk drives in the RAIDset.)
Table 3–3

Maximum Chunk Sizes for a RAIDset

RAIDset Size

Max Chunk Size

3 members
4 members
5 members
6 members
7 members
8 members
9 members
10 members
11 members
12 members
13 members
14 members

1024 blocks
682 blocks
512 blocks
409 blocks
341 blocks
292 blocks
256 blocks
227 blocks
204 blocks
186 blocks
170 blocks
157 blocks

Save Configuration
Indicate whether to save the subsystem’s configuration on the storage
unit when you initialize it:

NOSAVE_CONFIGURATION (default) means that the controller
stores the subsystem’s configuration in its nonvolatile memory
only. Although this is generally secure, the configuration could be
jeopardized if the controller fails. For this reason, you should
initialize at least one of your storage units with the
SAVE_CONFIGURATION switch enabled.
SAVE_CONFIGURATION allows the controller to use 256K of
each device in a storage unit to save the subsystem’s configuration.
The controller saves the configuration every time you change it or
add a patch to your controller. If the controller should fail, you can
recover your latest configuration from the storage unit rather than
rebuild it from scratch.
The save configuration option saves the following information:

Creating Storagesets

3–51

All configuration information normally saved when you restart
your controller except, the controller serial number, product ID
number, vendor ID number, and any manufacturing fault
information.
Patch information

The save configuration option does not save the following
information:

n
n

Software or hardware upgrades
Inter-platform conversions

Considerations for Saving the Configuration

n
n

Use the SET FAILOVER COPY= command to restore
configuration information in a replacement controller. See “Saving
Configuration Information in Dual-Redundant Configurations,”
page 3–52 for details.
Do not remove and replace disk devices between the time you save
and restore your configuration. This is particularly important for
devices that you migrate from another system. The controller could
recover and use the wrong configuration information on your
subsystem.
Save your subsystem configuration as soon as possible after
removing and replacing any disk devices in your subsystem. This
ensures that the devices always contain the latest, valid information
for your system.
When you incorporate a spare into a storageset that you initialized
with the INITIALIZE SAVE_CONFIGURATION command, the
controller reserves space on the spare for configuration information.
The controller updates this information when the configuration
changes.
You cannot use a storageset that contains user data to save your
subsystem configuration unless you backup and restore the user
data.
If you previously configured storagesets with the
SAVE_CONFIGURATION option, you do not need to initialize
them again after you reconfigure your devices with a new
controller.

3–52

HSG80 User’s Guide

When you replace a controller, make sure the replacement
controller does not contain any configuration data. If the controller
is not new, use the CONFIGURATION RESET command to purge
any existing configuration. If you do not take this precaution, you
can lose configuration data if non-volatile memory changes.

Saving Configuration Information in Dual-Redundant
Configurations
If you decide to use SAVE_CONFIGURATION in a dual-redundant
configuration, keep these points in mind:

n
n

The controller-unique data for both controllers is saved.
Saved configuration data from a dual controller configuration can
be used to restore the configuration to a replacement controller.
However, if one controller in a dual configuration is replaced, use
the SET FAILOVER COPY= command to restore the
configuration.
When replacing both controllers, you can replace the first and
restart it alone by holding in port button 6 and simultaneously
pressing the reset button on the controller’s operator control panel.
(This controller picks up any previously saved configuration data
on disk and uses it to set up the subsystem configuration.) Replace
the second controller using the SET FAILOVER COPY= command
to copy the configuration information from the operating controller.
Both controllers update the saved data; each writes to only those
devices currently preferred to it. This prevents conflicting data
transfer.

More information on Save Configuration can be found in Appendix B,
page B–73.

Destroy/Nodestroy
Specify whether to destroy or retain the user data and metadata when
you initialize a disk drive that has been previously used in a mirrorset
or as a single-disk unit.
Note The DESTROY and NODESTROY switches are only valid for
striped mirrorsets and mirrorsets.

Creating Storagesets

n
n

3–53

DESTROY (default) overwrites the user data and forced-error
metadata on a disk drive when it is initialized.
NODESTROY preserves the user data and forced-error metadata
when a disk drive is initialized. Use NODESTROY to create a
single-disk unit from any disk drive that has been used as a member
of a mirrorset. See the REDUCED command in the Appendix B,
“CLI Commands,” for information on removing disk drives from a
mirrorset.
The NODESTROY switch is not valid for RAIDsets and singledisk configurations.

See Appendix B, page B–73, for more information on the Destroy/
Nodestroy switch.

3–54

HSG80 User’s Guide

Unit Switches
You can enable the Unit switches listed in Table 3–4 for the listed
storagesets and devices.
Unit Switches

Container Type

Switch
ENABLE_ACCESS_PATH
DISABLE_ACCESS_PATH
MAXIMUM_CACHED_
TRANSFER
IDENTIFIER
NOIDENTIFIER
PREFERRED_PATH
NOPREFERRED_PATH
READ_CACHE
NOREAD_CACHE
READAHEAD_CACHE
NOREADAHEAD_CACHE
WRITE_PROTECT
NOWRITE_PROTECT
WRITEBACK_CACHE
NOWRITEBACK_CACHE
RUN
NORUN

Table 3–4

RAIDset

✔

Stripeset

✔

Mirrorset

✔

NoTransportable
Disk

✔

Transportable Disk

✔

See “ADD UNIT,” page B–27 and “SET unit-number,” page B–137 in
Appendix B, “CLI Commands,” for a complete list and further
explanation of the unit switches.

Creating Storagesets

3–55

Configuring Storagesets with CLI Commands
One method of configuring storagesets is manual configuration. This
method allows you the most flexibility in defining and naming
storagesets. See Appendix B, “CLI Commands,” for complete
information about the CLI commands shown in this chapter.

Adding Disk Drives
The factory-installed devices in your StorageWorks subsystem have
already been added to the controller’s list of eligible devices. If you
want to add new devices to your subsystem, you must issue one of the
following CLI commands before you can use them in any kind of
storageset, single disk unit, or spareset:

Adding One Disk Drive at a Time
To add one new disk drive to your controller’s list of eligible devices,
enter the following command at the prompt:
ADD DISK DISK nnn ptl-location switch_value

Adding Several Disk Drives at a Time
To add several new disk drives to your controller’s list of eligible
devices, enter the following command at the prompt:
RUN CONFIG

Configuring a Stripeset
See “Using Striped Mirrorsets for Highest Performance and
Availability,” page 3–17, for information about creating a profile and
understanding the switches you can set for this kind of storage unit.
To configure a stripeset:
1. Create the stripeset by adding its name to the controller’s list of
storagesets and specifying the disk drives it contains. Use the following
command:
ADD STRIPESET stripeset-name DISK nnnnn DISK nnnnn

2. Initialize the stripeset. If you want to set any Initialize switches, you
must do so in this step. Use the following command:
INITIALIZE stripeset-name switch

3–56

HSG80 User’s Guide

3. Present the stripeset to the host by giving it a unit number the host can
recognize. Optionally, you can append Unit switch values. If you do not
specify switch values, the default values are applied.
ADD UNIT unit-number stripeset-name switch

4. Verify the stripeset configuration and switches. Use the following
command:
SHOW stripeset-name

5. Verify the unit configuration and switches. Use the following command:
SHOW unit-number

Example
The following example shows the commands you would use to create
Stripe1, a three-member stripeset:
ADD STRIPESET STRIPE1 DISK10000 DISK20000 DISK30000
INITIALIZE STRIPE1 CHUNKSIZE=128
ADD UNIT D100 STRIPE1 MAXIMUM_CACHED_TRANSFER=16
SHOW STRIPE1
SHOW D100

See Appendix B, “CLI Commands,”for more information on stripeset
switches and values.

Configuring a Mirrorset
See Chapter 3, “Creating Storagesets,” for information about creating a
profile and understanding the switches you can set for this kind of
storage unit.
To configure a mirrorset:
1. Create the mirrorset by adding its name to the controller’s list of
storagesets and specifying the disk drives it contains. Optionally, you
can append Mirrorset switch values. If you do not specify switch values,
the default values are applied.
Use the following command to create a mirrorset:
ADD MIRRORSET mirrorset-name DISK nnnnn DISK nnnnn switch

Creating Storagesets

3–57

2. Initialize the mirrorset. If you want to set any Initialize switches, you
must do so in this step. Use the following command:
INITIALIZE mirrorset-name switch

3. Present the mirrorset to the host by giving it a unit number the host can
recognize. Optionally, you can append Unit switch values. If you do not
specify switch values, the default values are applied. Use the following
command:
ADD UNIT unit-number mirrorset-name switch

4. Verify the mirrorset configuration and switches. Use the following
command:
SHOW mirrorset-name

5. Verify the unit configuration and switches. Use the following command:
SHOW unit-number

Example
The following example shows the commands you would use to create
Mirr1, a two-member stripeset:
ADD MIRRORSET MIRR1 DISK10000 DISK20000
INITIALIZE MIRR1
ADD UNIT D110 MIRR1
SHOW MIRR1
SHOW D110

Refer to Appendix B, “CLI Commands,” for more information on the
ADD_MIRRORSET, INITIALIZE, ADD_UNIT, and SHOW
commands for creating a mirrrorset.

Configuring a RAIDset
To configure a RAIDset:
1. Create the RAIDset by adding its name to the controller’s list of
storagesets and specifying the disk drives it contains. Optionally, you
can append RAIDset switch values. If you do not specify switch values,
the default values are applied.

3–58

HSG80 User’s Guide

Use the following command to create a RAIDset:
ADD RAIDSET RAIDset-name DISK nnnnn DISK nnnnn DISK nnnnn

switch
2. Initialize the RAIDset. Optional: If you want to set the Initialize
switches, you must do so in this step. Use the following command:
INITIALIZE RAIDset-name switch

Note It is recommended that you allow initial reconstruct to complete
before allowing I/O to the RAIDset. Not doing so may generate forced
errors at the host level. To determine whether initial reconstruct has
completed, enter SHOW S or SHOW RAIDSET FULL.
3. Present the RAIDset to the host by giving it a unit number the host can
recognize. Optionally, you can append Unit switch values. If you do not
specify switch values, the default values are applied.
Use the following command to present the RAIDset to the host:
ADD UNIT unit-number RAIDset-name switch

4. Verify the RAIDset configuration and switches. Use the following
command:
SHOW RAIDset-name

5. Verify the unit configuration and switches. Use the following command:
SHOW unit-number

Example
The following example shows the commands you would use to create
Raid1, a three-member RAIDset:
ADD RAIDSET RAID1 DISK10000 DISK20000 DISK30000
INITIALIZE RAID1
ADD UNIT D99 RAID1
SHOW RAID1
SHOW D99

Appendix B, “CLI Commands,” contains more information on valid
switches and values for configuraing a RAIDset.

Creating Storagesets

3–59

Configuring a Striped Mirrorset
See Chapter 3, “Creating Storagesets,” for information about creating a
profile and understanding the switches you can set for this kind of
storage unit.
To configure a striped mirrorset:
1. Create—but do not initialize—at least two mirrorsets.
2. Create a stripeset and specify the mirrorsets it contains. Use the
following command:
ADD STRIPESET mirrorset_1 mirrorset_2

3. Initialize the stripeset. If you want to set any Initialize switches, you
must do so in this step. Use the following command:
INITIALIZE stripeset-name switch

See page B–121 of Appendix B for a complete list of valid mirrorset
switches and values.
4. Present the stripeset to the host by giving it a unit number the host can
recognize. Optionally, you can append Unit switch values. If you do not
specify switch values, the default values are applied.
Use the following command to present the stripeset to the host:
ADD UNIT unit-number stripeset-name switch

5. Verify the striped mirrorset configuration and switches. Use the
following command:
SHOW stripeset-name

6. Verify the unit configuration and switches. Use the following command:
SHOW unit-number

3–60

HSG80 User’s Guide

Example
The following example shows the commands you would use to create
Stripe1, a three-member striped mirrorset that comprises Mirr1, Mirr2,
and Mirr3, each of which is a two-member mirrorset:
ADD MIRRORSET MIRR1 DISK10000 DISK20000
ADD MIRRORSET MIRR2 DISK30000 DISK40000
ADD MIRRORSET MIRR3 DISK50000 DISK60000
ADD STRIPESET STRIPE1 MIRR1 MIRR2 MIRR3
INITIALIZE STRIPE1 CHUNKSIZE=DEFAULT
ADD UNIT D101 STRIPE1
SHOW STRIPE1
SHOW D101

For more detailed information on configuring a striped mirrorset, refer
to Appendix B, “CLI Commands.”

Configuring a Single-Disk Unit
Follow these steps to use a single disk drive as a single-disk unit in your
subsystem:
1. Add the disk drive by following the steps in “Adding Disk Drives,” page
3–55. Optionally, you can append Device switch values. If you do not
specify switch values, the default values are applied.
2. Initialize the disk drive using the following command:
INITIALIZE DISK nnn switch

3. Present the disk drive to the host by giving it a unit number the host can
recognize. Optionally, you can append Unit switch values. If you do not
specify switch values, the default values are applied. Use the following
command:
ADD UNIT unit-number DISK nnn switch_value

Note If you make a disk transportable, you cannot specify
WRITEBACK_CACHE for that disk.
4. Verify the configuration using the following command:
SHOW DEVICES

Creating Storagesets

3–61

Example
The following example shows the commands you would use to
configure DISK10000 as a single-disk unit.
ADD DISK DISK10000 1 0 0
ADD UNIT D101 DISK10000
SHOW DEVICES

See Appendix B, “CLI Commands,” for further information on these
switches and values.

Partitioning a Storageset or Disk Drive
See “Planning Partitions,” page 3–37, for details about partitioning a
storage unit.
To partition a storageset or disk drive:
1. Add the storageset or disk drive to the controller’s list of storagesets and
specify the disk drives it contains. Use the following command:
ADD storageset-name DISK nnnnn DISK nnnnn

or
ADD DISK DISK nnnnn ptl-location

Do not split partitioned units across ports. They must be on a single
port. The subsystem assigns units 0-99 to Port 1; units 100-199 are
assigned to Port 2.
2. Initialize the storageset or disk drive. If you want to set any Initialize
switches, you must do so in this step. Use the following command:
INITIALIZE storageset-name switch

3. Create each partition in the storageset or disk drive by indicating the
partition’s size. Use the following command:
CREATE_PARTITION storageset-name SIZE= n

where n is the percentage of the disk drive or storageset that will be
assigned to the partition. Enter SIZE=LARGEST to let the controller
assign the largest free space available to the partition.
4. Verify the partitions, using the following command:
SHOW storageset-name

3–62

HSG80 User’s Guide

The partition number appears in the first column, followed by the size
and starting block of each partition.
5. Present each partition to the host by giving it a unit number the host can
recognize. (You can skip this step until you are ready to put the
partitions online.) Optionally, you can append Unit switch values. If you
do not specify switch values, the default values are applied.
Use the following command to present partitions to the host:
ADD UNIT unit-number storageset-name PARTITION= partition-number

switch
6. Verify the unit numbers for the partitions using the following command:
SHOW storageset-name

Example
The following example shows the commands you would use to create
Raid1, a three-member RAIDset, then partition it into four storage
units:
ADD RAIDSET RAID1 DISK10000 DISK20000 DISK30000
INITIALIZE RAID1
CREATE_PARTITION RAID1 SIZE=25
CREATE_PARTITION RAID1 SIZE=25
CREATE_PARTITION RAID1 SIZE=25
CREATE_PARTITION RAID1 SIZE=LARGEST
SHOW RAID1
Partition number

Size

Starting Block

1915 (0.98 MB)

Raid1

1915 (0.98 MB)

1920

Raid1

1915 (0.98 MB)

3840

Raid1

2371 (1.21 MB)

5760

Raid1

.
.
.

Used by

Creating Storagesets

3–63

ADD UNIT D1 RAID1 PARTITION=1
ADD UNIT D2 RAID1 PARTITION=2
ADD UNIT D3 RAID1 PARTITION=3
ADD UNIT D4 RAID1 PARTITION=4
SHOW RAID1
.
.
.
Partition number
1
2
3
4
.
.
.

Size
Starting Block
1915 (0.98 MB)
0
1915 (0.98 MB)
1920
1915 (0.98 MB)
3840
2371 (1.21 MB)
5760

Used by
D1
D2
D3
D4

Appendix B, “CLI Commands,” contains more information on
partitioning a storageset or disk drive.

Adding a Disk Drive to the Spareset
The spareset is a collection of hot spares that are available to the
controller should it need to replace a failed member of a RAIDset or
mirrorset.
Use the following steps to add a disk drive to the spareset:
Note This procedure assumes that the disks that you are adding to the
spareset have already been added to the controller’s list of eligible
devices.
1. Add the disk drive to the controller’s spareset list. Use the following
command:
ADD SPARESET DISK nnnnn

Repeat this step for each disk drive you want to add to the spareset:
2. Verify the contents of the spareset using the following command:
SHOW SPARESET

3–64

HSG80 User’s Guide

Example
The following example shows the commands you would use to add
DISK60000 and DISK60100 to the spareset.
ADD SPARESET DISK60000
ADD SPARESET DISK60100
SHOW SPARESET

Removing a Disk Drive from the Spareset
You cannot delete the spareset—it always exists whether or not it
contains disk drives. However, you can delete disks in the spareset if
you need to use them elsewhere in your StorageWorks subsystem.
To remove a disk drive from the spareset:
1. Show the contents of the spareset using the following command:
SHOW SPARESET

2. Delete the desired disk drive using the following command:
DELETE SPARESET DISK nnnnn

Verify the contents of the spareset using the following command:
SHOW SPARESET

Example
The following example shows the commands you would use to remove
DISK60000 from the spareset.
SHOW SPARESET

Name
SPARESET

Storageset
spareset

Uses
disk60000
disk60100

Used by

Uses
disk60100

Used by

DELETE SPARESET DISK60000
SHOW SPARESET

Name
SPARESET

Storageset
spareset

Creating Storagesets

3–65

Enabling Autospare
With AUTOSPARE enabled on the failedset, any new disk drive that is
inserted into the PTL location of a failed disk drive is automatically
initialized and placed into the spareset. If initialization fails, the disk
drive remains in the failedset until you manually delete it from the
failedset.
To enable autospare use the following command:
SET FAILEDSET AUTOSPARE

To disable autospare use the following command:
SET FAILEDSET NOAUTOSPARE

During initialization, AUTOSPARE checks to see if the new disk drive
contains metadata—the information that indicates it belongs to, or has
been used by, a known storageset. If the disk drive contains metadata,
initialization stops. (A new disk drive will not contain metadata but a
repaired or re-used disk drive might. To erase metadata from a disk
drive, add it to the controller’s list of devices, then set it to be
TRANSPORTABLE and initialize it.)

Deleting a Storageset
If the storageset you are deleting is partitioned, you must delete each
partitioned unit before you can delete the storageset. Use the following
steps to delete a storageset:
1. Show the configuration using the following command:
SHOW STORAGESETS

2. Delete the unit number shown in the “Used by” column. Use the
following command:
DELETE unit-number

3. Delete the name shown in the “Name” column. Use the following
command:
DELETE storageset-name

4. Verify the configuration using the following command:
SHOW STORAGESETS

3–66

HSG80 User’s Guide

Example
The following example shows the commands you would use to delete
Stripe1, a three-member stripeset that is comprised of DISK10000,
DISK20000, and DISK30000.
SHOW STORAGESETS

Name
STRIPE1

Storageset
stripeset

Uses
DISK10000
DISK20000
DISK30000

Used by
D100

DELETE D100
DELETE STRIPE1
SHOW STORAGESETS

Changing Switches for a Storageset or Device
You can optimize a storageset or device at any time by changing the
switches that are associated with it. See “Choosing Switches for
Storagesets and Devices,” page 3–39, for an explanation of the
switches. Remember to update the storageset’s profile when you change
its switches.

Displaying the Current Switches
To display the current switches for a storageset or single-disk unit, enter
the following command at a CLI prompt:
SHOW storageset-name or device-name FULL

Changing RAIDset and Mirrorset Switches
Use the SET storageset-name command to change the RAIDset and
Mirrorset switches associated with an existing storageset. For example,
the following command changes the replacement policy for RAIDset
Raid1 to BEST_FIT:
SET RAID1 POLICY=BEST_FIT

Creating Storagesets

3–67

Changing Device Switches
Use the SET command to change the device switches. For example, the
following command enables DISK10000 to be used in a nonStorageWorks environment:
SET DISK10000 TRANSPORTABLE

The TRANSPORTABLE switch cannot be changed for a disk if the
disk is part of an upper-level container. Additionally, the disk cannot be
configured as a unit if it is to be used as indicated in this example.

Changing Initialize Switches
The Initialize switches cannot be changed without destroying the data
on the storageset or device. These switches are integral to the
formatting and can only be changed by reinitializing the storageset.
Initializing a storageset is similar to formatting a disk drive; all data is
destroyed during this procedure.

Changing Unit Switches
Use the SET command to change Unit switches that are associated with
a unit. For example, the following command enables write protection
for unit D100:
SET D100 WRITE_PROTECT

3–68

HSG80 User’s Guide

Configuring with the Command Console LUN
The Command Console LUN (CCL) is a type of LUN that allows you
to communicate with the controller from the host using StorageWorks
Command Console (SWCC) or CLI commands instead of using the
maintenance port cable.
The most common tasks performed with the CCL include:

n
n
n
n
n

Configuring storage units
Preparing the subsystem for use
Checking a failed set
Checking performance with VTDPY
Troubleshooting with FMU

Note Do not use the CCL with HSUTIL, FRUTIL, or DILX. The host
and controller must communicate through the maintenance port cable
when using these utilities and exercisers. Also, do not use the CCL to
troubleshoot and maintain the controller. Instead, run the utilities and
exercisers with the local connection that uses the maintenance port
cable. See “Establishing a Local Connection to the Controller,” page
2–7.

Enabling and Disabling the CCL
If you have not configured any units and have not yet enabled the CCL,
you must first establish a local connection through the maintenance port
cable to provide a means of enabling CCL. See “Establishing a Local
Connection to the Controller,” page 2–9. Once the CCL is enabled, you
can communicate with the controller over the host port connection
instead of through the maintenance port connection.
If the the CCL is not automatically enabled on your controller, use the
following command:
SET THIS_CONTROLLER COMMAND_CONSOLE_LUN

Creating Storagesets

3–69

To turn it off, use the following command:
SET THIS_CONTROLLER NOCOMMAND_CONSOLE_LUN

Caution Disabling the CCL while SWCC is running may result in loss
of connection for the StorageWorks Command Console. Turn off
SWCC before issuing the command.

Finding the CCL Location
To see where each CCL is located, use the following commands:
SHOW THIS_CONTROLLER

or
SHOW OTHER_CONTROLLER

Look under host port to find the Command Console LUN location.
Because the CCL is not an actual device or unit, the SHOW UNITS
command will display only unit information and no CCL locations.

Multiple-Bus and Transparent Failover in SCSI-2 and SCSI-3 Modes
The way the host sees the CCL varies, depending on whether you’ve
enabled transparent or multiple-bus failover modes and whether you are
in SCSI-2 or SCSI-3 mode.

SCSI-2 Mode
Multiple-Bus Failover
If SET MULTIBUS_FAILOVER is enabled, all ports will be able to see
and access the CCL. In addition, the CCL appears to the host as a direct
access device.
Transparent Failover
If you are in SCSI-2 mode and have enabled the SET FAILOVER
command, only one CCL will be enabled.

3–70

HSG80 User’s Guide

SCSI-3 Mode
In SCSI-3 mode, a CCL will appear at LUN 0 of each unit offset.
Multiple-Bus Failover
If you are in multiple-bus failover mode, all ports will be able to see
and access the CCLs. As a result, all hosts will have access to each
CCL, and they will appear to the host as array controllers.
Transparent Failover
If you are in transparent failover mode, each CCL will be accessible
from the port that has the unit offset enabled. Ports with multiple unit
offsets assigned will have multiple CCLs, and they will appear to the
host as an array controller.
Caution Selecting SCSI-3 mode enables access to the CCL by all
hosts. If the hosts access the CCL simultaneously, unpredictable
consequences can occur. In cases where the CCL can be accessed
through multiple paths and LUNs, system administrators of each host
must not attempt to access the CCL simultaneously.

Adding Storage Units Using the CCL
To start configuring storage units, you must first assign unit offsets. See
“Assigning Unit Offsets,” page 3–29.

SCSI-2 Mode
As you add storage units and assign unit offsets over the CCL or above
its location, the CCL immediately and automatically moves into the
next available free space, which would be the lowest available LUN.
Note If you delete a unit at a setting below the CCL setting, the CCL
does not automatically move. Instead, it only moves to the lowest
deleted unit’s setting when you reboot the controller.

Creating Storagesets

3–71

SCSI-3 Mode
The CCL will appear at the default unit offset of each port. Because the
default unit offset is 0 for Port 1 and 100 for Port 2, the CCL will be at
LUN 0 on Port 1 and LUN 100 on Port 2.
Note Lun 100 on Port 2 appears as LUN 0 to its hosts.

3–72

HSG80 User’s Guide

Moving Storagesets
You can move a storageset from one subsystem to another without
destroying its data as shown in Figure 3–20. You also can follow the
steps in this section to move a storageset to a new location within the
same subsystem.
Caution Move only normal storagesets. Do not move storagesets that
are reconstructing or reduced, or data corruption will result.
You can use the procedure in this section to migrate wide devices from
an HSZ70 controller in a BA370 rack-mountable enclosure to an
HSG80 environment. However, if you have an HSZ40 or HSZ50
subsystem, you cannot migrate to an HSG80 in a BA370 rackmountable enclosure. Refer to the HSG80 Array Controller ACS
Version 8.2G Release Notes for drives that can be supported.
Figure 3–20 Moving a Storageset from one Subsystem to Another

CXO5595A

Caution Never initialize any container or this procedure will not
protect data.
Use the following procedure to move a storageset while maintaining the
data it contains:

Creating Storagesets

3–73

1. Show the details for the storageset you want to move. Use the following
command:
SHOW storageset-name

2. Label each member with its name and PTL location.
If you do not have a storageset map for your subsystem, you can enter
the LOCATE command for each member to find its PTL location. Use
the following command:
LOCATE disk-name

To cancel the locate command, enter the following:
LOCATE CANCEL

3. Delete the unit-number shown in the “Used by” column of the SHOW
storageset-name command. Use the following command:
DELETE unit-number

4. Delete the storageset shown in the “Name” column of the SHOW
storageset-name command. Use the following command:
DELETE storageset-name

5. Delete each disk drive—one at a time—that the storageset contained.
Use the following command:
DELETE disk-name
DELETE disk-name
DELETE disk-name

6. Remove the disk drives and move them to their new PTL locations.
7. Add again each disk drive to the controller’s list of valid devices. Use
the following command:
ADD DISK disk-name PTL-location
ADD DISK disk-name PTL-location
ADD DISK disk-name PTL-location

8. Recreate the storageset by adding its name to the controller’s list of
valid storagesets and specifying the disk drives it contains. (Although
you have to recreate the storageset from its original disks, you do not
have to add them in their original order.) Use the following command:
ADD storageset-name disk-name disk-name

3–74

HSG80 User’s Guide

9. Represent the storageset to the host by giving it a unit number the host
can recognize. You can use the original unit number or create a new one.
Use the following command:
ADD UNIT unit-number storageset-name

Example
The following example moves unit D100 to another cabinet. D100 is
the RAIDset RAID99 that is comprised of members DISK10000,
DISK20000, and DISK30000.
SHOW RAID99
Name
RAID99

Storageset
raidset

Uses
disk10000
disk20000
disk30000

DELETE D100
DELETE RAID99
DELETE DISK10000
DELETE DISK20000
DELETE DISK30000

(...move the disk drives to their new location...)
ADD DISK DISK20000 2 0 0
ADD DISK DISK30000 3 0 0
ADD DISK DISK40000 4 0 0
ADD RAIDSET RAID99 DISK20000 DISK30000 DISK40000
ADD UNIT D100 RAID99

Used by
D100

Creating Storagesets

3–75

Example
The following example moves the reduced RAIDset, R3, to another
cabinet. (R3 used to contain DISK20000, which failed before the
RAIDset was moved. R3 contained DISK10000, DISK30000, and
DISK40000 at the beginning of this example.)
DELETE D100
DELETE R3
DELETE DISK10000
DELETE DISK30000
DELETE DISK40000

(...move disk drives to their new location...)
ADD DISK DISK10000 1 0 0
ADD DISK DISK30000 3 0 0
ADD DISK DISK40000 4 0 0
ADD RAIDSET R3 DISK10000 DISK30000 DISK40000 REDUCED
ADD UNIT D100 R3

4–1

CHAPTER

Troubleshooting

This chapter provides guidelines for troubleshooting the controller, cache module,
and external cache battery (ECB). It also describes the utilities and exercisers that
you can use to aid in troubleshooting these components. See the appendixes for a
list of LEDs and event codes. See the documentation that accompanied the
enclosure for information on troubleshooting its hardware, such as the power
supplies, cooling fans, and environmental monitoring unit (EMU).

Maintenance Features
Use the following maintenance features to troubleshoot and service a controller:

n
n
n

“Operator Control Panel,” page 1–13
“Establishing a Local Connection to the Controller,” page 2–7
“Utilities and Exercisers,” page 1–14

4–2

HSG80 User’s Guide

Troubleshooting Checklist
The following checklist provides a general procedure for diagnosing the
controller and its supporting modules. If you follow this checklist,
you’ll be able to identify many of the problems that occur in a typical
installation. When you’ve identified the problem, use Table 4–1 to
confirm your diagnosis and fix the problem.
If your initial diagnosis points to several possible causes, use the tools
described later in this chapter to further refine your diagnosis. If the
problem can’t be diagnosed using the checklist and tools, call customer
service for additional support.
To troubleshoot the controller and its supporting modules:
1. Check the power to the cabinet and its components. Are the cords
properly connected? Is the power within specifications?
2. Check the component cables. Are the bus cables to the controllers
connected properly? Are the ECB cables properly connected?
3. Check the program cards to ensure they’re fully seated.
4. Check the operator control panel and devices for LED codes. See
Appendix C, “LED Codes,” to interpret the LED codes.
5. Connect a local terminal to the controller and check its configuration
with the following command:
SHOW THIS_CONTROLLER FULL

Ensure that the ACS version is correct and that pertinent patches have
been installed. Also, check the status of the cache module and its ECB.
In a dual redundant configuration, check the other controller with the
following command:
SHOW OTHER_CONTROLLER FULL

6. Using FMU, check for last failure or memory-system failure entries.
Show these codes and translate the last failure codes they contain.
“Significant Event Reporting,” page 4–14.
If the controller has failed to the extent that it cannot support a local
terminal for FMU, check the host’s error log for the instance or lastfailure codes. See Appendix D, “Event Reporting: Templates and
Codes,” to interpret the event codes.

Troubleshooting

4–3

7. Check the status of the devices with the following command:
SHOW DEVICES FULL

Look for errors such as “misconfigured device” or “No device at this
PTL.” If a device reports misconfigured or missing, check its status
with the following command:
SHOW device-name

8. Check the status of the storagesets with the following command:
SHOW STORAGESETS FULL

Ensure that all storagesets are normal (or normalizing if it’s a RAIDset
or mirrorset). Check again for misconfigured or missing devices.
9. Check the status of the units with the following command:
SHOW UNITS FULL

Ensure that all of the units are available or online. If the controller
reports that a unit is unavailable or offline, recheck the storageset it
belongs to with the following command:
SHOW storageset-name

If the controller reports that a unit has lost data or is unwriteable,
recheck the status of the devices that make up the storageset. If the
devices are OK, recheck the status of the cache module. If the unit
reports a media format error, recheck the status of the storageset and its
devices.

4–4

HSG80 User’s Guide

Troubleshooting Table
Use the troubleshooting checklist that begins on page 4–2 to find a
symptom, then use this table to verify and fix the problem.
Table 4–1

Troubleshooting Table

Symptom
Reset button not lit

Possible Cause

Investigation

Remedy

No power to subsystem. Check power to
Replace cord or AC
subsystem and power
input power module.
supplies on controller’s
shelf.
Ensure that all cooling
fans are installed. If one
or more fans are
missing or all are
inoperative for more
than eight minutes, the
EMU shuts down the
subsystem.

Turn off power switch
on AC input power
module. Replace
cooling fan. Restore
power to subsystem.

Verify that the standby Depress the alarm
power switch on the
control switch on the
PVA was not depressed EMU.
for more than five
seconds.
Failed controller.

If the foregoing check Replace controller.
fails to produce a
remedy, check for OCP
LED codes.

Reset button lit steadily;
other LEDs also lit.

Various

See “Operator Control
Panel LED Codes,”
page C–2.

Follow repair action.

Reset button blinking;
other LEDs also lit.

Device in error or FAIL SHOW device FULL
set on corresponding
device port with other
LEDs lit.

Follow repair action.

Troubleshooting

Table 4–1

4–5

Troubleshooting Table (Continued)

Symptom
Cannot set failover to
create dual-redundant
configuration.

Possible Cause
Incorrect command
syntax.

Investigation
See Appendix B, “CLI
Commands,” for the
SET FAILOVER
command.

Remedy
Use the correct
command syntax.

Different software
Check software
versions on controllers. versions on both
controllers.

Update one or both
controllers so that both
controllers are using the
same software version.

Incompatible hardware. Check hardware
versions.

Upgrade controllers so
that they’re using
compatible hardware.

Controller previously
set for failover.

Ensure that neither
Use the SET
controller is configured NOFAILOVER
for failover.
command on both
controllers, then reset
“this controller” for
failover.

Failed controller.

If the foregoing checks Follow repair action.
fail to produce a
remedy, check for OCP
LED codes.

Node ID is all zeros.

SHOW_THIS to see if
node ID is all zeros.

Set node ID using the
node ID (bar code) that
is located on the frame
in which the controller
sits. See SET THIS
CONTROLLER
NODE_ ID in
Appendix B, “CLI
Commands.” Also, be
sure that you are
copying in the right
direction. If you are
cabled to the new
controller, use SET
FAILOVER
COPY=OTHER. If
cabled to old controller,
use SET FAILOVER
COPY=THIS.

4–6

HSG80 User’s Guide

Table 4–1

Troubleshooting Table (Continued)

Symptom
Nonmirrored cache;
controller reports failed
DIMM in cache module
A or B.

Mirrored cache;
“this controller” reports
DIMM 1 or 2 failed in
cache module A or B.

Mirrored cache;
“this controller”reports
DIMM 3 or 4 failed in
cache module A or B.

Possible Cause

Investigation

Remedy

Improperly installed
DIMM.

Remove cache module Reseat DIMM (see
and ensure that DIMM Figure 5–8 on page
is fully seated in its slot. 5–44).
See Figure 1–7 on page
1–13 for location of
cache module and see
Figure 5–7 on page
5–42 for location of
DIMM.

Failed DIMM.

If the foregoing check Replace DIMM.
fails to produce a
remedy, check for OCP
LED codes.

Improperly installed
DIMM in “this
controller’s” cache
module (see Figure 1–7
on page 1–13 and
Figure 5–7 on page
5–42).

Remove cache module Reseat DIMM (see
and ensure that DIMMs Figure 5–8 on page
are installed properly.
5–44).
See “Replacing
DIMMs,” page 5–42.

Failed DIMM in “this
controller’s” cache
module.

If the foregoing check Replace DIMM in “this
fails to produce a
controller’s” cache
remedy, check for OCP module.
LED codes.

Improperly installed
DIMM in “other
controller’s” cache
module (see Figure 1–7
on page 1–13 and
Figure 5–7 on page
5–42).

Remove cache module Reseat DIMM (see
and ensure that DIMMs Figure 5–8 on page
are installed properly.
5–44).
See “Replacing
DIMMs,” page 5–42.

Failed DIMM in “other If the foregoing check Replace DIMM in
controller’s” cache
fails to produce a
“other controller’s”
module.
remedy, check for OCP cache module.
LED codes.
Mirrored cache;
Memory module was
controller reports battery installed before it was
not present.
connected to an ECB.

ECB cable not
connected to cache
module.

Connect ECB cable to
cache module, then
restart both controllers
by pushing their reset
buttons simultaneously.

Troubleshooting

Table 4–1

4–7

Troubleshooting Table (Continued)

Symptom

Possible Cause

Investigation

Remedy

Mirrored cache;
controller reports cache
or mirrored cache has
failed.

Primary data and its
mirrored copy data are
not identical.

SHOW
THIS_CONTROLLER
indicates that the cache
or mirrored cache has
failed.

Enter the SHUTDOWN
command on
controllers that report
the problem. (This
command flushes the
contents of cache to
synchronize its primary
and mirrored data.)
Restart the controllers
that you shut down.

Spontaneous FMU
message displays:
“Primary cache
declared failed - data
inconsistent with
mirror,” or “Mirrored
cache declared failed data inconsistent with
primary.”

4–8

HSG80 User’s Guide

Table 4–1

Troubleshooting Table (Continued)

Symptom
Invalid cache

Possible Cause

Investigation

Mirrored-cache mode
discrepancy. This may
occur after you’ve
installed a new
controller. Its existing
cache module is set for
mirrored caching, but
the new controller is set
for unmirrored caching.
(It may also occur if the
new controller is set for
mirrored caching but its
existing cache module
is not.)

SHOW THIS
CONTROLLER
indicates “invalid
cache.”

Cache module may
erroneously contain
unflushed write-back
data. This may occur
after you’ve installed a
new controller. Its
existing cache module
may indicate that it
contains unflushed
write-back data, but the
new controller expects
to find no data in the
existing cache module.
(This error may also
occur if you install a
new cache module for a
controller that expects
write-back data in the
cache.)

SHOW THIS
CONTROLLER
indicates “invalid
cache.”

Remedy

Connect a terminal to
the maintenance port on
the controller reporting
the error and clear the
error with the following
command—all on one
Spontaneous FMU
line:
message displays:
CLEAR_ERRORS
“Cache modules
inconsistent with mirror THIS_CONTROLLER
NODESTROY
mode.”
INVALID_CACHE.

No spontaneous FMU
message.

Connect a terminal to
the maintenance port on
the controller reporting
the error, and clear the
error with the following
command—all on one
line:
CLEAR_ERRORS
THIS_CONTROLLER
DESTROY
INVALID_CACHE.
See Appendix B, “CLI
Commands,” for more
information.

Troubleshooting

Table 4–1

4–9

Troubleshooting Table (Continued)

Symptom
Cannot add device

Cannot configure
storagesets

Possible Cause

Investigation

Remedy

Illegal device.

Replace device.
See product-specific
release notes that
accompanied the
software release for the
most recent list of
supported devices.

Device not properly
installed in shelf.

Check that SBB is fully Firmly press SBB into
seated.
slot.

Failed device.

Check for presence of
device LEDs.

Follow repair action in
the documentation
provided with the
enclosure or device.

Failed power supplies.

Check for presence of
power supply LEDs.

Follow repair action in
the documentation
provided with the
enclosure or power
supply.

Failed bus to device.

If the foregoing checks Replace enclosure or
shelf.
fail to produce a
remedy, check for OCP
LED codes.

Incorrect command
syntax.

See Appendix B, “CLI
Commands,” for the
ADD storageset
command.

Reconfigure storageset
with correct command
syntax.

Exceeded maximum
number of storagesets.

Use the SHOW
command to count the
number of storagesets
configured on the
controller.

Delete unused
storagesets.

Failed battery on ECB.
(An ECB or UPS is
required for RAIDsets
and mirrorsets.)

Use the SHOW
command to check the
ECB’s battery status.

Replace the ECB if
required.

4–10

HSG80 User’s Guide

Table 4–1

Troubleshooting Table (Continued)

Symptom

Possible Cause

Can’t assign unit number Incorrect command
to storageset.
syntax.
Incorrect SCSI target
ID numbers set for
controller that accesses
desired unit. (First
number of unit number
must be one of the SCSI
target ID numbers for
the controller.)

Investigation

Remedy

See the Appendix B,
“CLI Commands,” for
correct syntax.

Reassign the unit
number with the correct
syntax.

Use the SHOW
command to check the
controller’s SCSI target
ID numbers.

Reset the controller’s
SCSI target ID numbers
or assign a new unit
number as desired.

Unit is available but not
online

This is normal. Units
None
are “available” until the
host accesses them, at
which point their status
is changed to “online.”

None

Host cannot see device

Broken cables or a
missing, incorrect, or
defective terminator.

Check for broken
cables or a missing,
incorrect, or defective
terminator.

Replace broken
cablesor the missing,
incorrect, or defective
terminator.

Host cannot access unit

Host files or device
Check for the required
drivers not properly
device special files.
installed or configured.

Configure device
special files as
described in the getting
started manual that
accompanied your
software release.

Invalid Cache

See the description for
the invalid cache
symptom.

Unit(s) have lost data.

Issue the SHOW_UNIT CLEAR_ERRORS unit
command.
lost data.

For a more detailed description of how to troubleshoot this symptom, see
Figure 4–1.

Troubleshooting

Table 4–1

4–11

Troubleshooting Table (Continued)

Symptom

Possible Cause

Investigation

Remedy

Host’s log file or
maintenance terminal
indicates that a forced
error occurred when the
controller was
reconstructing a
RAIDset or mirrorset

Unrecoverable read
errors may have
occurred when
controller was
reconstructing the
storageset. Errors occur
if another member fails
while the controller is
reconstructing the
storageset.

Conduct a read scan of
the storageset using the
appropriate utility from
the host’s operating
system, such as the
“dd” utility for a
DIGITAL UNIX host.

Rebuild the storageset,
then restore its data
from a backup source.
While the controller is
reconstructing the
storageset, monitor the
host error log activity or
spontaneous event
reports on the
maintenance terminal
for any unrecoverable
errors. If unrecoverable
errors persist, note the
device on which they
occurred, and replace
the device before
proceeding.

Host requested data
from a normalizing
storageset that didn’t
contain the data.

Use the SHOW
storageset-name to see
if all of its members are
“normal.”

Wait for normalizing
members to become
normal, then resume
I/O to them.

4–12

HSG80 User’s Guide

Figure 4–1 Troubleshooting: Host Cannot Access Unit
Start

CLI: SHOW this
Controller
loop up?
Refer to Hub User's
Guide for information
on how to determine
this.
N

Port topology
offline
N

• Check cables
• Re-seat GLM
• Restart controller
• Restart host
• Go to Start

Host adapter
loop up?

• Set to Loop_soft/
Loop_hard
• Restart controller
• Restart host
• Go to Start

Go to
A

Check
host adapter
display
Y

Go to
B

This reading is
adapter-specific; see
adapter user's guide
for further details.

Host booted
before units
were online?
Y

• Restart host
• Go to Start
CXO6498A

Troubleshooting

4–13

Figure 4–1 Troubleshooting: Host Cannot Access Unit (continued)
A

Driver
loaded?

Event log errors
for adapters?

B
CLI: CLEAR_ERRORS INVALID_CACHE

Y
CLI: SHOW this

• Shutdown
• Re-seat GLM
• Re-seat adapter
• Check cables or
add loopback
• Go to Start

NOTE: If this happens
more than two times, there
may be PCI restrictions
on your adapter. Refer
to your adapter's readme
file for specifics.

Invalid cache?

• Clear condition
• Check units
• Restart host
• Go to Start

CLI: SHOW connections
Online?
Host mode?
Offset?

• Transparent: Units 0-99 on
port 1; units 0-99 on port 2
• Multiple bus: Units 0-199
on all ports

BAD

Units configured
correctly?

See Chapter 2,"Configuring
an HSG80 Array Controller."

CLI: SHOW unit-number
Online?
Access?
Lost data?

• Reconfigure
• Restart controller
• Restart host
• Go to Start
CXO6499A

4–14

HSG80 User’s Guide

Significant Event Reporting
The controller’s fault-management software reports information about
significant events that occur. These events are reported via the:

n
n
n

Maintenance terminal
Host error log
Operator control panel (OCP)

Some events cause controller operation to terminate; others allow the
controller to remain operable. Each of these two instances are detailed
in the following sections.

Events that cause controller termination
When an event causes the controller to terminate, there are three
possible ways in which it is reported:

n
n
n

Flashing OCP Pattern Display
Solid OCP Pattern Display
Last Failure

Flashing OCP Pattern Display Reporting
Certain events can cause an alternating display of the OCP LEDs.
These patterns are detailed in Appendix C, “LED Codes.”

Solid OCP Pattern Display Reporting
Some events cause a steady pattern to be displayed in the OCP LEDs,
as outlined in Appendix C, “LED Codes.”
In addition, information related to the solid OCP patterns may be
displayed on the maintenance terminal using %FLL formatting, as
detailed in the following examples:
%FLL--HSG> --13-JAN-1946 04:39:45 (time not set)-- OCP Code: 38
Controller operation terminated.
%FLL--HSG> --13-JAN-1946 04:32:26 (time not set)-- OCP Code: 26
Memory module is missing.

Troubleshooting

4–15

Last Failure Reporting
Last Failures are displayed on the maintenance terminal using %LFL
formatting. The example below details an occurrence of a Last Failure
report:
%LFL--HSG> --13-JAN-1946 04:39:45 (time not set)-- Last Failure Code: 20090010
Power On Time: 0.Years, 14.Days, 19.Hours, 58.Minutes, 42.Seconds
Controller Model: HSG80
Serial Number: AA12345678 Hardware Version: 0000(00)
Software Version: V080G(50)
Informational Report
Instance Code: 0102030A
Last Failure Code: 20090010 (No Last Failure Parameters)
Additional information is available in Last Failure Entry: 1.

In addition, Last Failures are reported to the host error log using
Template 01, following a reboot of the controller. See Figure D–2
“Template 01 - Last Failure Event Sense Data Response Format,” on
page D–4, for a more detailed explanation.

Events that do not cause controller operation to terminate
Events that do not cause controller operation to terminate are displayed
in one of two ways:

n
n

Spontaneous Event Log
CLI Event Reporting

4–16

HSG80 User’s Guide

Spontaneous Event Log
Spontaneous event logs are displayed on the maintenance terminal
using %EVL formatting, as illustrated in the following examples:
%EVL--HSG> --13-JAN-1946 04:32:47 (time not set)-- Instance Code: 0102030A (not
yet reported to host)
Template: 1.(01)
Power On Time: 0.Years, 14.Days, 19.Hours, 58.Minutes, 43.Seconds
Controller Model: HSG80
Serial Number: AA12345678 Hardware Version: 0000(00)
Software Version: V082G(50)
Informational Report
Instance Code: 0102030A
Last Failure Code: 011C0011
Last Failure Parameter[0.] 0000003F
%EVL--HSG> --13-JAN-1946 04:32:47 (time not set)-- Instance Code: 82042002 (not
yet reported to host)
Template: 19.(13)
Power On Time: 0.Years, 14.Days, 19.Hours, 58.Minutes, 43.Seconds
Controller Model: HSG80
Serial Number: AA12345678 Hardware Vesion: 0000(00)
Software Version: V082G(50)
Header type: 00 Header flags: 00
Test entity number: 0F Test number Demand/Failure: F8 Command: 01
Error Code: 0008 Return Code: 0005 Address of Error: A0000000
Expected Error Data: 44FCFCFC Actual Error Data: FFFF01BB
Extra Status(1): 00000000 Extra Status(2): 00000000 Extra Status(3): 00000000
Instance Code: 82042002
HSG>

Spontaneous event logs are reported to the host error log using SCSI
Sense Data Templates 01, 04, 05, 11, 12, 13, 14, 41, and 51. See
Appendix D, “Event Reporting: Templates and Codes,” for a more
detailed explanation.

CLI Event Reporting
CLI event reports are displayed on the maintenance terminal using
%CER formatting, as shown in the following example:
%CER--HSG> --13-JAN-1946 04:32:20 (time not set)-- Previous controlleroperation terminated with display of solid fault code, OCP Code: 3F
HSG>

Troubleshooting

4–17

Fault Management Utility
The Fault Management Utility (FMU) provides a limited interface to
the controller’s fault-management software. Use FMU to:

n
n

Display the last-failure and memory-system-failure entries that the
fault-management software stores in the controller’s non-volatile
memory.
Translate many of the code values contained in event messages. For
example, entries may contain code values that indicate the cause of
the event, the software component that reported the event, the repair
action, and so on.
Control the display characteristics of significant events and failures
that the fault-management system displays on the maintenance
terminal. See “Controlling the Display of Significant Events and
Failures,” page 4–20, for specific details on this feature.

Displaying Failure Entries
The controller stores the 16 most recent last-failure reports as entries in
its non-volatile memory. The occurrence of any failure event will
terminate operation of the controller on which it occurred.
Note Memory system failures are reported via the last failure
mechanism but can be displayed separately.
Use the following steps to display the last-failure entries:
1. Connect a local terminal to the controller.
2. Start FMU with the following command:
RUN FMU

3. Show one or more of the entries with the following command:
SHOW event_type entry# FULL

where:

n
n

event-type is LAST_FAILURE or
MEMORY_SYSTEM_FAILURE
entry# is ALL, MOST_RECENT, or 1 through 16

4–18

HSG80 User’s Guide

FULL displays additional information, such as the I960 stack and
hardware component register sets (for example, the memory
controller, FX, host port, and device ports, and so on).

4. Exit FMU with the following command:
EXIT

Example
The following example shows a last-failure entry. The Informational
Report—the lower half of the entry—contains the instance code,
reporting component, and so forth that you can translate with FMU to
learn more about the event.
Last Failure Entry: 4. Flags: 006FF300
Template: 1.(01) Description: Last Failure Event
Power On Time: 0. Years, 14. Days, 19. Hours, 51. Minutes, 31. Seconds
Controller Model: HSG80
Serial Number: AA12345678 Hardware Version: 0000(00)
Software Version: V082G(50)
Informational Report
Instance Code: 0102030A Description:
An unrecoverable software inconsistency was detected or an intentional
restart or shutdown of controller operation was requested.
Reporting Component: 1.(01) Description:
Executive Services
Reporting component’s event number: 2.(02)
Event Threshold: 10.(0A) Classification:
SOFT. An unexpected condition detected by a controller software component (e.g., protocol violations, host buffer access errors, internal
inconsistencies, uninterpreted device errors, etc.) or an intentional
restart or shutdown of controller operation is indicated.
Last Failure Code: 20090010 (No Last Failure Parameters)
Last Failure Code: 20090010 Description:
This controller requested this controller to shutdown.
Reporting Component: 32.(20) Description:
Command Line Interpreter
Reporting component’s event number: 9.(09)
Restart Type: 1.(01) Description: No restart

Translating Event Codes
Use the following steps to translate the event codes in the faultmanagement reports for spontaneous events and failures:
1. Connect a local terminal to the controller’s maintenance port.
2. Start FMU with the following command:
RUN FMU

Troubleshooting

4–19

3. Show one or more of the entries with the following command:
DESCRIBE code_type code#

where code_type is one of those listed in Table 4–2 and code# is the
alpha-numeric value displayed in the entry. The code types marked with
an asterisk (*) require multiple code numbers.
Table 4–2

Event-Code Types
Event-Code Type

ASC_ASCQ_CODE*
COMPONENT_CODE
CONTROLLER_UNIQUE_ASC_ASCQ_CODE*
DEVICE_TYPE_CODE
EVENT _THRESHOLD_CODE
INSTANCE_CODE
LAST_FAILURE_CODE
REPAIR_ACTION_CODE
RESTART_TYPE
SCSI_COMMAND_OPERATION_CODE*
SENSE_DATA_QUALIFIERS*
SENSE_KEY_CODE
TEMPLATE_CODE

Example
The following example shows the FMU translation of a last-failure
code.
FMU>DESCRIBE LAST_FAILURE_CODE 206C0020
Last Failure Code: 206C0020
Description: Controller was forced to restart in order for new controller code image to take effect.
Reporting Component: 32.(20)
Description: Command Line Interpreter
Reporting component’s event number: 108.(6C)
Restart Type: 2.(02)
Description: Automatic hardware restart

Instance Codes and Last-Failure Codes
Instance codes identify and accompany significant events that do not
cause the controller to terminate operation; last-failure codes identify
and accompany failure events that cause the controller to stop
operating. Last-failure codes are sent to the host only after the affected
controller is restarted successfully.

4–20

HSG80 User’s Guide

Controlling the Display of Significant Events and Failures
You can control how the fault-management software displays
significant events and failures with FMU’s SET command.
Table 4–3 describes various SET commands that you can enter while
running FMU. These commands remain in effect only as long as the
current FMU session remains active, unless you enter the
PERMANENT qualifier—the last entry in Table 4–3.
Table 4–3

FMU SET Commands
Command

SET EVENT_LOGGING
SET NOEVENT_LOGGING

Result
enable and disable the spontaneous display of significant events to
the local terminal; preceded by “%EVL.” By default, logging is
enabled (SET EVENT_LOGGING).
When logging is enabled, the controller spontaneously displays
information about the events on the local terminal. Spontaneous
event logging is suspended during the execution of CLI commands
and operation of utilities on a local terminal. Because these events
are spontaneous, logs are not stored by the controller.

SET LAST_FAILURE LOGGING
SET NOLAST_FAILURE LOGGING

enable and disable the spontaneous display of last failure events;
preceded by “%LFL.” By default, logging is enabled (SET
LAST_FAILURE LOGGING).
The controller spontaneously displays information relevant to the
sudden termination of controller operation.
In cases of automatic hardware reset (for example, power failure or
pressing the controller’s reset button), the fault LED log display is
inhibited because automatic resets do not allow sufficient time to
complete the log display.

SET log_type REPAIR_ACTION
SET log_type NOREPAIR_ACTION

enable and disable the inclusion of repair action information for
event logging or last-failure logging. By default, repair actions are
not displayed for these log types (SET log_type
NOREPAIR_ACTION). If the display of repair actions is enabled,
the controller displays any of the recommended repair actions
associated with the event.

SET log_type VERBOSE
SET log_type NOVERBOSE

enable and disable the automatic translation of event codes that are
contained in event logs or last-failure logs. By default, this
descriptive text is not displayed (SET log_type NOVERBOSE). See
Translating Event Codes on page 4–18 for instructions to translate
these codes manually.

Troubleshooting

Table 4–3

4–21

FMU SET Commands (Continued)
Command

Result

SET PROMPT
SET NOPROMPT

enable and disable the display of the CLI prompt string following
the log identifier “%EVL,” or “%LFL,” or “%FLL.” This command
is useful if the CLI prompt string is used to identify the controllers in
a dual-redundant configuration (see Appendix B, “CLI Commands,”
for instructions to set the CLI command string for a controller). If
enabled, the CLI prompt will be able to identify which controller
sent the log to the local terminal. By default, the prompt is set (SET
PROMPT).

SET TIMESTAMP
SET NOTIMESTAMP

enable and disable the display of the current date and time in the first
line of an event or last-failure log. By default, the timestamp is set
(SET TIMESTAMP)

SET FMU_REPAIR_ACTION
SET FMU_NOREPAIR_ACTION

enable and disable the inclusion of repair actions with SHOW
LAST_FAILURE and SHOW MEMORY_SYSTEM_FAILURE
commands. By default, the repair actions are not shown (SET FMU
NOREPAIR_ACTION). If repair actions are enabled, the command
outputs display all of the recommended repair actions associated
with the instance or last-failure codes used to describe an event.

SET FMU VERBOSE
SET FMU NOVERBOSE

enable and disable the inclusion of instance and last failure code
descriptive text with SHOW LAST_FAILURE and SHOW
MEMORY_SYSTEM_ FAILURE commands. By default, this
descriptive text is not displayed (SET FMU_NOVERBOSE). If the
descriptive text is enabled, it identifies the fields and their numeric
content that comprise an event or last-failure entry.

SET CLI_EVENT_REPORTING
SET NOCLI_EVENT_REPORTING

enable and disable the asynchronous errors reported at the CLI
prompt (for example, “swap signals disabled” or “shelf has a bad
power supply”). Preceded by “%CER.” By default, these errors are
reported (SET CLI_EVENT_REPORTING). These errors are
cleared with the CLEAR ERRORS_CLI command.

4–22

HSG80 User’s Guide

Table 4–3

FMU SET Commands (Continued)
Command

SET FAULT_LED_LOGGING
SET NOFAULT_LED_LOGGING

Result
enable and disable the solid fault LED event log display on the local
terminal. Preceded by “%FLL.” By default, logging is enabled (SET
FAULT_LED_LOGGING).
When enabled, and a solid fault pattern is displayed in the OCP
LEDs, the fault pattern and its meaning are displayed on the
maintenance terminal. For many of the patterns, additional
information is also displayed to aid in problem diagnosis.
In cases of automatic hardware reset (for example, power failure or
pressing the controller’s reset button), the fault LED log display is
inhibited because automatic resets do not allow sufficient time to
complete the log display.

SHOW PARAMETERS

displays the current settings associated with the SET command.

SET command PERMANENT

preserves the SET command across controller resets.

Troubleshooting

4–23

Using VTDPY to Check for Communication Problems
Use the virtual terminal display (VTDPY) utility to get information
about the following communications:

n
n
n

Communication between the controller and its hosts
Communication between the controller and the devices in the
subsystem
The state and I/O activity of the logical units, devices, and device
ports in the subsystem

Use the following steps to run VTDPY:
1. Connect a terminal to the controller. The terminal must support ANSI
control sequences.
2. Set the terminal to NOWRAP mode to prevent the top line of the display
from scrolling off of the screen.
3. Start VTDPY with the following command:
RUN VTDPY

Use the key sequences and commands liosted in Table 4–4 to control
VTDPY.
Table 4–4

VTDPY Key Sequences and Commands

Command

Action

Ctrl/C

Enables command mode; after entering Ctrl/C, enter
one of the following commands and press Return:
CLEAR
DISPLAY CACHE
DISPLAY DEFAULT
DISPLAY DEVICE
DISPLAY HOST
DISPLAY STATUS
HELP
INTERVAL seconds (to change update interval)

Ctrl/G

Updates screen

Ctrl/O

Pauses (and resumes) screen updates

Ctrl/R

Refreshes current screen display

Ctrl/Y

Exits VTDPY

4–24

HSG80 User’s Guide

You may abbreviate the commands to the minimum number of
characters necessary to identify the command. Enter a question mark
(?) after a partial command to see the values that can follow the
supplied command. For example, if you enter DISP ?, the utility will
list CACHE, DEFAULT, and so forth. (Separate “DISP” and “?” with a
space.) Upon successfully executing a command—other than HELP—
VTDPY exits command mode. Pressing Return without a command
also causes VTDPY to exit command mode.

Checking Controller-to-Host Communications
Use the display host VTDPY command to see how or if the controller
is communicating with the host (see Figure 4–2).
Figure 4–2 Xfer Rate Region of the Default Display
VTDPY> DISPLAY DEFAULT
S/N: ZG74100120 SW: R052G-0 HW: 00-00
35.8% Idle 98237 KB/S 1559 Rq/S

Pr Name
Stk/Max Typ
0 NULL
0/0
4 HP_MAIN 40/2
FNC

Sta CPU%
Rn
35.8
Rn
64.1

Target
111111
0123456789012345
P1 DDD hH
o2 DDD hH
r3 DDD hH
t4 DDD hH
5 DDD hH
6 DDD hH

Unit
D0000
D0001
D0002
D0003
D0004
D0005
D0006
D0007
D0100
D0101
D0102
D0103
D0104
D0105
D0106
D0107

ASWC
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a
o^a

KB/S
3288
3288
3288
3283
8800
8918
8795
8725
6254
6211
6227
6265
6216
6222
6227
6222

Rd%
100
100
100
100
100
100
100
100
100
100
100
100
100
100
100
100

Wr%
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Cm%
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

HT%
100
100
100
100
100
100
100
100
100
100
100
100
100
100
100
100

Checking Controller-to-Device Communications
Use the VTDPY display device to see how or if the controller is
communicating with the devices in the subsystem (see Figure 4–3).
This display contains three important regions:

n
n
n

Device map region (upper left)
Device status region (upper right)
Device-port status region (lower left)

Troubleshooting

4–25

Figure 4–3 Regions on the Device Display
VTDPY>DISPLAY DEVICE

67% I/D
Target
111111
0123456789012345
P1 hH PDD
o2 hH DDD
r3 ????hH
t4 hH DDD
5
P hH
6 DDD hH

Port
1
2
3
4
5
6

Rq/S
0
0
0
0
0
0

RdKB/S
0
0
0
0
0
0

PTL
P1120
D1130
D1140
D2120
D2130
D2150
?3020
?3030
?3040
?3050
D4090
D4100
D4110
P5030
D6010
D6020
D6030
WrKB/S
0
0
0
0
0
0

CR
0
0
0
0
0
0

ASWF
A^
A^
A^
A^
A^
a^
^F
^F
^F
^F
A^
A^
A^
A^
A^
A^
A^
BR
0
0
0
0
0
0

S/N: ZG64100176 SW: v7.0 HW: CX-02
99.9% Idle
0 KB/S
Up: 0 5:17.54
Rq/S
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

RdKB/S
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

WrKB/S
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Que
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Tg
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

CR
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

BR
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

TR
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

TR
0
0
0
0
0
0

Checking Device Type and Location
The device map region of the device display (upper left) shows all of
the devices that the controller recognizes through its device ports. Table
4–5 lists the heading and contents for each column of the device map
region.
Table 4–5 Device Map Columns
Column

Contents

Port

SCSI ports 1 through 6.

Target

SCSI targets 0 through 15. Single controllers occupy 7;
dual-redundant controllers occupy 6 and 7.
D = disk drive or CD-ROM drive
F = foreign device
H = this controller
h = other controller in dual-redundant configurations

4–26

HSG80 User’s Guide

Table 4–5 Device Map Columns (Continued)
Column

Contents
P = passthrough device
? = unknown device type
= no device at this port/target location

Checking Device Status and I/O Activity
The device status region of the device display (upper right) shows the
name and I/O characteristics for all of the devices that the controller
recognizes. Table 4–6 lists the heading and contents for each column of
the device status region.
Table 4–6 Device Status Columns
Column
PTL

Contents
Kind of device and its port-target-lun (PTL) location:
D = disk drive
P = passthrough device
? = unknown device type
= no device at this port/target location

Availability of the device:
A = available to this controller
a = available to other controller
U = unavailable, but configured on “this controller”
u = unavailable, but configured on “other controller”
= unknown availability state

Spindle state of the device:
^ = disk spinning at correct speed; tape loaded
> = disk spinning up
< = disk spinning down
v = disk not spinning

Troubleshooting

4–27

Table 4–6 Device Status Columns (Continued)
Column

Contents
= unknown spindle state

Write-protection state of the device. For disk drives, a W
in this column indicates that the device is hardware
write-protected. This column is blank for other kinds of
devices.

Fault state of the device. An F in this column indicates an
unrecoverable device fault. If this field is set, the device
fault LED should also be lit.

Rq/S

Average request rate for the device during the last update
interval. Requests can be up to 32K and generated by
host or cache activity.

RdKB/S

Average data transfer rate from the device (reads) during
the last update interval.

WrKB/S

Average data transfer rate to the device (writes) during
the last update interval.

Que

Maximum number of I/O requests waiting to be
transferred to the device during the last update interval.

Maximum number of requests queued to the device
during the last update interval. If the device doesn’t
support tagged queuing, the maximum value is 1.

Number of SCSI command resets that occurred since
VTDPY was started.

Number of SCSI bus resets that occurred since VTDPY
was started.

Number of SCSI target resets that occurred since
VTDPY was started.

4–28

HSG80 User’s Guide

Checking Device-Port Status and I/O Activity
The device-port status region of the device display (lower left) shows
the I/O characteristics for the controller’s device ports. Table 4–7 lists
the heading and contents for each column of the device-port status
region.
Table 4–7 Device-Port Status Columns
Column

Contents

Port

SCSI device ports 1 through 6.

Rq/S

Average request rate for the port during the last update
interval. Requests can be up to 32K and generated by
host or cache activity.

RdKB/S

Average data transfer rate from the devices on the port
(reads) during the last update interval.

WrKB/S

Average data transfer rate to the devices on the port
(writes) during the last update interval.

Number of SCSI command resets that occurred since
VTDPY was started.

Number of SCSI bus resets that occurred since
VTDPY was started.

Number of SCSI target resets that occurred since
VTDPY was started.

Troubleshooting

4–29

Checking Unit Status and I/O Activity
Use the cache display to see the status and I/O activity for the logical
units configured on the controller (see Figure 4–4). Table 4–8 lists the
heading and contents for each column of the device status region.
Figure 4–4 Unit Status on the Cache Display
VTDPY> DISPLAY CACHE

66% I/D
Unit
P0300
D0303
D0304
P0400
P0401
D0402

ASWC
o
o^ b

x^ b

S/N: ZG64100176 SW: v7.0 HW: CX-02
Hit 99.8% Idle
0 KB/S 0 Rq/S

KB/S
0
0
0
0
0
0

Rd%
0
0
0
0
0
0

Wr%
0
0
0
0
0
0

Cm%
0
0
0
0
0
0

HT%
0
0
0
0
0
0

PH%
0
0
0
0
0
0

Up: 0
MS%
0
0
0
0
0
0

5:16.42

Purge BlChd BlHit
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Table 4–8 Unit Status Columns
Column
Unit

Contents
Kind of unit (and its unit number):
D = disk drive or CD-ROM drive
P = passthrough device
? = unknown device type

Availability of the unit:
a = available to other controller
d = disabled for servicing, offline
e = mounted for exclusive access by a user
f = media format error
i = inoperative
m = maintenance mode for diagnostic purposes
o = online. Host may access this unit through “this
controller.”
r = rundown with the SET NORUN command
v = no volume mounted due to lack of media

4–30

HSG80 User’s Guide

Table 4–8 Unit Status Columns (Continued)
Column

Contents
x = online. Host may access this unit through “other
controller.”
= unknown availability

Spindle state of the device:
^ = disk spinning at correct speed; tape loaded
> = disk spinning up; tape loading
< = disk spinning down; tape unloading
v = disk not spinning; tape unloaded
= unknown spindle state

Write-protection state. For disk drives, a W in this
column indicates that the device is hardware writeprotected. This column is blank for units that comprise
other kinds of devices.

Caching state of the device:
a = read, write-back, and read-ahead caching enabled
b = read and write-back caching enabled
c = read and read-ahead caching enabled
p = read-ahead caching enabled
r = read caching only
= caching disabled

KB/S

Average amount of data transferred to and from the unit
during the last update interval in 1000-byte increments.

Rd%

Percentage of data transferred between the host and the
unit that were read from the unit.

Wr%

Percentage of data transferred between the host and the
unit that were written to the unit.

CM%

Percentage of data transferred between the host and the
unit that were compared. A compare operation can
accompany a read or a write operation, so this column is
not the sum of columns Rd% and Wr%.

Troubleshooting

4–31

Table 4–8 Unit Status Columns (Continued)
Column

Contents
x = online. Host may access this unit through “other
controller.”
= unknown availability

Write-protection state. For disk drives, a W in this
column indicates that the device is hardware writeprotected. This column is blank for units that comprise
other kinds of devices.

KB/S

Average amount of data transferred to and from the unit
during the last update interval in 1000-byte increments.

Rd%

Percentage of data transferred between the host and the
unit that were read from the unit.

Wr%

Percentage of data transferred between the host and the
unit that were written to the unit.

CM%

Percentage of data transferred between the host and the
unit that were compared. A compare operation can
accompany a read or a write operation, so this column is
not the sum of columns Rd% and Wr%.

4–32

HSG80 User’s Guide

Table 4–8 Unit Status Columns (Continued)
Column

Contents

HT%

Cache-hit percentage for data transferred between the
host and the unit.

PH%

Partial cache-hit percentage for data transferred between
the host and the unit.

MS%

Cache-miss percentage for data transferred between the
host and the unit.

Purge

Number of blocks purged from the cache during the last
update interval.

BlChd

Number of blocks added to the cache during the last
update interval.

BlHit

Number of blocks hit during the last update interval.

Checking Fibre Channel Link Errors
You can also use the display host VTDPY command to check for any
channel link errors (see Figure 4–5).
Note The following section outlines the VTDPY display for “this
controller” only. To see other connections, you must run VTDPY again
on the “other controller.”

Troubleshooting

4–33

Figure 4–5 Fibre Channel Host Status Display
FIBRE CHANNEL HOST STATUS DISPLAY
********* KNOWN HOSTS **********
## NAME
BB FrSz ID/ALPA P S
00 ASSIGN
0 2048
01
1F
01 !NEWCON47 0 2048
81
2N

******* PORT 1 *******
Topology
: LOOP
Current Status
: STNDBY
Current ID/ALPA
:
Tachyon Status
:
0
Queue Depth
:
0
Busy/QFull Rsp
:
0
LINK ERROR COUNTERS
Link Downs
:
30
Soft Inits
:
14
Hard Inits
:
0
Loss of Signals
:
0
Bad Rx Chars
:
243
Loss of Syncs
:
0
Link Fails
:
0
Received EOFa
:
0
Generated EOFa
:
0
Bad CRCs
:
0
Protocol Errors
:
0
Elastic Errors
:
0

******* PORT 2 *******
Topology
: LOOP
Current Status
: LOOP
Current ID/ALPA
:
e4
Tachyon Status
:
0
Queue Depth
:
24
Busy/QFull Rsp
:
0
LINK ERROR COUNTERS
Link Downs
:
5
Soft Inits
:
6
Hard Inits
:
0
Loss of Signals
:
0
Bad Rx Chars
: 207
Loss of Syncs
:
0
Link Fails
:
0
Received EOFa
:
0
Generated EOFa
:
0
Bad CRCs
:
0
Protocol Errors
:
0
Elastic Errors
:
1

Use the VTDPY>CLEAR command to clear the host display link error
counters.
Table outlines the “Known Hosts” portion of the Fibre Channel Host
Status Display that appears with the display host VTDPY command.
For a more detailed explanation on certain field labels and their
definitions, consult the FC-PH specification.
Table 4–9 Fibre Channel Host Status Display- Known Hosts
(Connections)
Field Label
##
NAME

Description
Internal ID
Refer to the SHOW connection command in
Appendix B.

Buffer-to-buffer credit

FrSz

Frame size

ID/ALPA

Host ID

Port number (1 or 2)

Status:
N = online
F = offline

4–34

HSG80 User’s Guide

The following tables detail the remaining portions of the Fibre Channel
Host Status Display. Table 4–10 includes the labels that report the
status of ports one and two, and Table 4–11 describes the Link Error
Counters.
Table 4–10 Fibre Channel Host Status Display- Port Status
Field Label

Description

Topology

LOOP
OFFLNE

Current Status

DOWN
LOOP
STNDBY

Current ID/ALPA

Controller ID

Tachyon Status

This denotes the current state of the Tachyon,
or Fibre Channel control chip. See “Tachyon
Status,” page 4–36, for more detail.

Queue Depth

Queue depth shows the instantaneous number
of commands at the controller port.

Busy/QFull RSP

This field represents the total number of QFull/
Busy responses sent by the port.

Table 4–11 Fibre Channel Host Status Display- Link Error
Counters
Field Label

Description

Link Downs

This field refers to the total number of link
down/up transitions.

Soft Inits

Soft initializations are the number of loop
initialization caused by this port.

Hard Inits

Hard initializations indicate the number of
Tachyon chip resets.

Loss of Signals

Loss of signals show the number of times the
Frame Manager detected a low-to-high
transition on the lnk_unuse signal.

Troubleshooting

4–35

Table 4–11 Fibre Channel Host Status Display- Link Error
Counters (Continued)
Field Label

Description

Bad Rx Chars

This field represents the number of times the
8B/10B decode detected an invalid 10-bit code.
FC-PH denotes this value as “Invalid
Transmission Word during frame reception.”
This field may be non-zero after initialization.
After initialization, the host should read this
value to determine the correct starting value for
this error count.

Loss of Syncs

Loss of Sync denotes the number of times the
loss of sync is greater than RT_TOV.

Link Fails

This field indicates the number of times the
Frame Manager detected a NOS or other
initialization protocol failure that caused a
transition to the Link Failure state.

Received EOFa

Received EOFa refers to the number of frames
containing an EOFa delimiter that Tachyon has
received.

Generated EOFa

This field reveals the number of problem
frames that Tachyon has received that caused
the Frame Manager to attach an EOFa
delimiter. Frames that Tachyon discarded due
to internal FIFO overflow are not included in
this or any other statistic.

Bad CRCs

Bad CRCs denotes the number of bad CRC
frames that Tachyon has received.

Protocol Errors

This field indicates the number of protocol
errors that the Frame Manager has detected.

Elastic Errors

Elastic errors reveal the timing difference
between the receive and transmit clocks and
usually indicate cable pulls.

4–36

HSG80 User’s Guide

Tachyon Status
The number that appears in the Tachyon Status field represents the
current state of the Tachyon, or Fibre Channel control chip. It consists
of a two-digit hex number, the first of which is explained in Figure
4–12. The second digit is outlined in Figure 4–13. Refer to the Tachyon
user’s manual for a more detailed explanation of the Tachyon
definitions.
Table 4–12 Tachyon First Digit
State

Definition

State

Definition

MONITORING

INITIALIZING

ARBITRATING

O_I INIT FINISH

ARBITRATION WON

O_I PROTOCOL

OPEN

O_I LIP RECEIVED

OPENED

HOST CONTROL

XMITTED CL0SE

LOOP FAIL

RECEIVED CLOSE

OLD PORT

TRANSFER

Table 4–13 Tachyon Second Digit
State

Definition

State

Definition

OFFLINE

LR2

OL1

LR3

OL2

LF1

OL3

LF2

LR1

ACTI VE

Troubleshooting

4–37

Checking for Disk-Drive Problems
Use the disk inline exerciser (DILX) to check the data-transfer
capability of disk drives. DILX generates intense read/write loads to the
disk drive while monitoring the drive’s performance and status. You
may run DILX on as many disk drives as you’d like, but because this
utility creates substantial I/O loads on the controller, DIGITAL
recommends that you stop host-based I/O during the test. You may also
use DILX to exercise the read capability of CD-ROM drives.

Finding a Disk Drive in the Subsystem
Use the following steps to find a disk drive or device in the subsystem:
1. Connect a terminal to the controller”s maintenance port.
2. Show the devices that are configured on the controller with the
following command:
SHOW DEVICES

3. Find the device in the enclosure with the following command:
LOCATE device-name

This command causes the device’s LED to blink continuously.
4. Enter the following command to turn off the LED:
LOCATE CANCEL

Testing the Read Capability of a Disk Drive
Use the following steps to test the read capability of a disk drive:
1. From a host console, dismount the logical unit that contains the disk
drive you want to test.
2. Connect a terminal to the maintenace port of the controller that accesses
the disk drive you want to test.
3. Run DILX with the following command:
RUN DILX

4. Decline the Auto-configure option so that you can specify the disk drive
to test.
5. Accept the default test settings and run the test in read-only mode.
6. Enter the unit number of the disk drive you want to test. For example, to
test D107, enter the number 107.

4–38

HSG80 User’s Guide

7. If you want to test more than one disk drive, enter the appropriate unit
numbers when prompted. Otherwise, enter “n” to start the test. Use the
control sequences listed in Table 4–14 to control DILX during the test.
Table 4–14 DILX Control Sequences
Command

Action

Ctrl/C

Terminates the test

Ctrl/G

Displays the performance summary for the current
test and continue testing

Ctrl/Y

Terminates the test and exits DILX

Testing the Read and Write Capabilities of a Disk Drive
Run a DILX Basic Function test to test the read and write capability of
a disk drive. During the Basic Function test, DILX runs the following
four tests. (DILX repeats the last three tests until the time that you
specify in step 6 on page 4–40 expires.)

n
n

Write test. Writes specific patterns of data to the disk drive (see
Table 4–15 on page 4–39.) DILX does not repeat this test.
Random I/O test. Simulates typical I/O activity by issuing read,
write, access, and erase commands to randomly-chosen logical
block numbers (LBNs). You can set the ratio of these commands as
well as the percentage of read and write data that are compared
throughout this test. This test takes six minutes.
Data-transfer test. Tests throughput by starting at an LBN and
transferring data to the next LBN that has not been written to. This
test takes two minutes.
Seek test. Stimulates head motion on the disk drive by issuing
single-sector erase and access commands. Each I/O uses a different
track on each subsequent transfer. You can set the ratio of access
and erase commands. This test takes two minutes.

Troubleshooting

4–39

Table 4–15 Data Patterns for Phase 1: Write Test
Pattern

Pattern in Hexadecimal Numbers

0000

8B8B

3333

3091

0001, 0003, 0007, 000F, 001F, 003F, 007F, 00FF, 01FF, 03FF, 07FF, 0FFF, 1FFF, 3FFF,
7FFF

FIE, FFFC, FFFC, FFFC, FFE0, FFE0, FFE0, FFE0, FE00, FC00, F800, F000, F000,
C000, 8000, 0000

0000, 0000, 0000, FFFF, FFFF, FFFF, 0000, 0000, FFFF, FFFF, 0000, FFFF, 0000, FFFF,
0000, FFFF

B6D9

5555, 5555, 5555, AAAA, AAAA, AAAA, 5555, 5555, AAAA, AAAA, 5555, AAAA,
5555, AAAA, 5555, AAAA, 5555

DB6C

2D2D, 2D2D, 2D2D, D2D2, D2D2, D2D2, 2D2D, 2D2D, D2D2, D2D2, 2D2D, D2D2,
2D2D, D2D2, 2D2D, D2D2

6DB6

0001, 0002, 0004, 0008, 0010, 0020, 0040, 0080, 0100, 0200, 0400, 0800, 1000, 2000,
4000, 8000

FIE, FFFD, FFFB, FFF7, FFEF, FFDF, FFBF, FF7F, FEFF, FDFF, FBFF, F7FF, EFFF,
BFFF, DFFF, 7FFF

DB6D, B6DB, 6DB6, DB6D, B6DB, 6DB6, DB6D, B6DB, 6DB6, DB6D, B6DB, 6DB6,
DB6D

3333, 3333, 3333, 1999, 9999, 9999, B6D9, B6D9, B6D9, B6D9, FFFF, FFFF, 0000,
0000, DB6C, DB6C

9999, 1999, 699C, E99C, 9921, 9921, 1921, 699C, 699C, 0747, 0747, 0747, 699C, E99C,
9999, 9999

FFFF

4–40

HSG80 User’s Guide

Use the following steps to test the read and write capabilities of a
specific disk drive:
1. From a host console, dismount the logical unit that contains the disk
drive you want to test.
2. Connect a terminal to the maintenance port of the controller that
accesses the disk drive you want to test.
3. Run DILX with the following command:
RUN DILX

4. Decline the auto-configure option so that you can specify the disk drive
to test.
Tip Use the auto-configure option if you want to test the read and
write capabilities of every disk drive in the subsystem.
5. Decline the default settings.
6. Enter the number of minutes you want the DILX Basic Function test to
run.
Note To ensure that DILX accesses the entire disk space, you should
enter 120 or more.
7. Enter the number of minutes between the display of performance
summaries.
8. Choose to include performance statistics in the summary.
9. Choose to display both hard and soft errors.
10. Choose to display the hex dump.
11. Accept the hard-error limit default.
12. Accept the soft-error limit default.
13. Accept the queue depth default.
14. Choose option 1 to run a Basic Function test.
15. Enable phase 1, the write test.
16. Accept the default percentage of requests that DILX issues as read
requests during phase 2, the random I/O test. DILX issues the balance as
write requests.

Troubleshooting

4–41

17. Choose ALL for the data patterns that DILX issues for write requests.
18. Perform the initial write pass.
19. Allow DILX to compare the read and write data.
20. Accept the default percentage of reads and writes that DILX compares.
21. Enter the unit number of the disk drive you want to test. For example, if
you want to test D107, enter the number 107.
22. If you want to test more than one disk drive, enter the appropriate unit
numbers when prompted, otherwise, enter “n” to start the test. Use the
command sequences shown in Table 4–14 to control the write test.

DILX Error Codes
Table 4–16 explains the error codes that DILX may display during and
after testing.
Table 4–16 DILX Error Codes
Error
Code

Explanation

Illegal Data Pattern Number found in data pattern
header. DILX read data from the disk and discovered
that the data did not conform to the pattern in which it
was previously written.

No write buffers correspond to data pattern. DILX read
a legal data pattern from the disk, but because no write
buffers correspond to the pattern, the data must be
considered corrupt.

Read data does not match write buffer. DILX compared
the read and write data and discovered that they didn’t
correspond.

4–42

HSG80 User’s Guide

Running the Controller’s Diagnostic Test
During start up, the controller automatically tests its device ports, host
port, cache module, and value-added functions. If you’re experiencing
intermittent problems with one of these components, you can run the
controller’s diagnostic test in a continuous loop, rather than restarting
the controller over and over again.
Use the following steps to run the controller’s diagnostic test:
1. Connect a terminal to the controller’s maintenance port.
2. Start the self test with one of the following commands:
SELFTEST THIS CONTROLLER
SELFTEST OTHER_CONTROLLER

Note The self test runs until it detects an error or until you press the
controller’s reset button.
If the self test detects an error, it saves information about the error and
produces an OCP LED code for a “daemon hard error.” Restart the
controller to write the error information to the host’s error log, then
check the log for a “built-in self-test failure” event report. This report
will contain an instance code, located at offset 32 through 35, that you
can use to determine the cause of the error. See “Translating Event
Codes,” page 4–18 for help on translating instance codes.

5–1

CHAPTER

Replacement Procedures

This chapter describes the procedures for replacing the controller, cache module,
external cache battery (ECB), gigabit link module (GLM), power verification and
addressing (PVA) module, I/O module, PCMCIA card, DIMMs, fibre cable or hub,
and a failed storageset member. Additionally, there are procedures for shutting
down and restarting the subsystem.
See the enclosure documentation for information about the power supplies, cooling
fans, cables, and environmental monitoring unit (EMU).

Electrostatic Discharge
Electrostatic discharge (ESD) is a common problem and may cause data loss,
system down time, and other problems. The most common source of static
electricity is the movement of people in contact with carpets and clothing. Low
humidity also increases the amount of static electricity. You must discharge all
static electricity prior to touching electronic equipment. Follow the precautions in
“Electrostatic Discharge Precautions” given in the Preface whenever you are
replacing any component.

5–2

HSG80 User’s Guide

Replacing Modules in a Single Controller Configuration
Follow the instructions in this section to replace modules in a single
controller configuration (see Figure 5–1). If you’re replacing modules
in a dual-redundant controller configuration, see “Replacing Modules
in a Dual-Redundant Controller Configuration,” page 5–8.
To upgrade a single controller configuration to a dual redundant
controller configuration, see “Upgrading to a Dual-Redundant
Controller Configuration,” page 6–16.
Figure 5–1 Single Controller Configuration

CXO6188A

The following sections cover procedures for replacing both the
controller and cache module, replacing the controller, and replacing the
cache module.
Caution You must shut down the subsystem before removing or
replacing any modules. If you remove the controller or any other
module without first shutting down the subsystem, data loss may occur.

Replacing the Controller and Cache Module in a Single Controller Configuration
If both the controller and cache module need to be replaced, follow the
steps in “Replacing the Controller in a Single Controller
Configuration,” page 5–3, and the steps in “Replacing the Cache
Module in a Single Controller Configuration,” page 5–6.

Replacement Procedures

5–3

Replacing the Controller in a Single Controller Configuration
Use the following steps in “Removing the Controller in a Single
Controller Configuration” and “Installing the Controller in a Single
Controller Configuration” to replace the controller.

Removing the Controller in a Single Controller
Configuration
Use the following steps to remove the controller:
1. From the host console, dismount the logical units in the subsystem. If
you are using a Windows NT platform, shut down the server.
2. If the controller is operating, connect a PC or terminal to the controller’s
maintenance port.
If the controller is not operating, go to step 5.
3. Run FMU to obtain the last failure codes, if desired.
Note If you initialized a container with the SAVE_
CONFIGURATION switch (see page B–73), you can save this
controller’s current device configuration using the CONFIGURATION
SAVE command (see page B–49). If CONFIGURATION SAVE is not
used, you will have to manually configure the new controller as
described in Chapter 2, “Configuring an HSG80 Array Controller.”

Caution The cache module may contain data if the controller crashed
and you weren’t able to shut it down with the SHUTDOWN
THIS_CONTROLLER command.
4. Shut down the controller with the following command:
SHUTDOWN THIS_CONTROLLER

When the controller shuts down, its reset button and the first three
LEDs are lit continuously.
Caution ESD can easily damage a controller. Wear a snug-fitting,
grounded ESD wrist strap.
5. Remove the program card’s ESD cover and program card. Save them for
the replacement controller.

5–4

HSG80 User’s Guide

6. Disconnect the hub cables from the controller.
Note One or two hub cables may be attached, depending on the
configuration.
7. If connected, disconnect the PC or terminal from the controller’s
maintenance port.
8. Disengage both retaining levers and remove the controller, then place
the controller into an antistatic bag or onto a grounded antistatic mat.

Installing the Controller in a Single Controller
Configuration
Use the following steps to install the controller:
Caution ESD can easily damage a controller. Wear a snug-fitting,
grounded ESD wrist strap.
Make sure you align the controller in the appropriate guide rails. If you
do not align the module correctly, damage to the backplane can occur.
1. Insert the new controller into its slot, and engage its retaining levers.
2. Connect the hub cables to the new controller.
Note One or two hub cables may be attached, depending on the
configuration.
3. Connect a PC or terminal to the controller’s maintenance port.
4. Hold the reset button while inserting the program card into the new
controller. Release the reset button and replace the ESD cover.
5. When the CLI prompt reappears, display details about the controller you
configured. Use the following command:
SHOW THIS_CONTROLLER FULL

See the SHOW THIS_CONTROLLER FULL on page B–145 for more
information about using this command.

Replacement Procedures

5–5

6. See “Configuring an HSG80 Array Controller,” page 2–3, to configure
the controller.
Note If the controller you’re installing was previously used in another
subsystem, it will need to be purged of the controller’s old
configuration (see “CONFIGURATION RESET,” page B–45).
7. To restore a configuration saved with the SAVE_CONFIGURATION
switch, hold button 6 while releasing the reset button.
8. Using CLCP, install any patches that you had installed on the previous
controller (see “Installing a Software Patch,” page 6–6).
9. Mount the logical units on the host. If you are using a Windows NT
platform, restart the server.
10. Set the subsystem date and time with the following command:
SET THIS_CONTROLLER TIME= dd-mmm-yyyy:hh:mm:ss

11. Disconnect the PC or terminal from the controller’s maintenance port.

5–6

HSG80 User’s Guide

Replacing the Cache Module in a Single Controller Configuration
Use the following steps in “Removing the Cache Module in a Single
Controller Configuration” and “Installing the Cache Module in a Single
Controller Configuration” to replace the cache module.

Removing the Cache Module in a Single Controller
Configuration
Use the following steps to remove the cache module:
1. From the host console, dismount the logical units in the subsystem. If
you are using a Windows NT platform, shut down the server.
2. If the controller is operating, connect a PC or terminal to the controller’s
maintenance port.
If the controller is not operating, go to step 5.
3. Run FMU to obtain the last failure codes, if desired.
4. Shut down the controller with the following command:
SHUTDOWN THIS_CONTROLLER

When the controller shuts down, its reset button and the first three LEDs
are lit continuously.
Caution ESD can easily damage a cache module. Wear a snug-fitting,
grounded ESD wrist strap.
5. Disable the ECB by pressing the battery disable switch until the status
light stops blinking—about five seconds.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before disconnecting the ECB cable from the cache module.
Failure to disable the ECB could result cache module damage.
6. Disconnect the ECB cable from the cache module.
7. Disengage both retaining levers, remove the cache module, and place
the cache module into an antistatic bag or onto a grounded antistatic
mat.

Replacement Procedures

5–7

Installing the Cache Module in a Single Controller
Configuration
Use the following steps to install the cache module:
Caution ESD can easily damage a cache module. Wear a snug-fitting,
grounded ESD wrist strap.
Make sure you align the cache module in the appropriate guide rails. If
you do not align the cache module correctly, damage to the backplane
can occur.
1. Insert the new cache module into its slot and engage its retaining levers.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before connecting the ECB cable to the cache module.
Failure to disable the ECB could result in ECB damage.
2. Connect the ECB cable to the new cache module.
3. If not already connected, connect a PC or terminal to the controller’s
maintenance port.
4. Mount the logical units on the host. If you are using a Windows NT
platform, restart the server.
5. Set the subsystem date and time with the following command:
SET THIS_CONTROLLER TIME= dd-mmm-yyyy:hh:mm:ss

6. Disconnect the PC or terminal from the controller’s maintenance port.

5–8

HSG80 User’s Guide

Replacing Modules in a Dual-Redundant Controller
Configuration
Follow the instructions in this section to replace modules in a dualredundant controller configuration (see Figure 5–2). If you’re replacing
modules in a single controller configuration, see “Replacing Modules in
a Single Controller Configuration,” page 5–2.
Figure 5–2 Dual-Redundant Controller Configuration

CXO6189A

The following sections cover procedures for replacing both the
controller and cache module, replacing the controller, and replacing the
cache module.
Note the following before starting the replacement procedures:

n
n

The new controller’s hardware must be compatible with the
functioning controller’s hardware. See the product-specific release
notes that accompanied the software release for information
regarding hardware compatibility.
The software versions and patch levels must be the same on both
controllers.
The new cache module must contain the same memory
configuration as the module it’s replacing.

Replacement Procedures

5–9

Replacing a Controller and Cache Module in a Dual-Redundant Controller
Configuration
Use the following steps in “Removing a Controller and Cache Module
in a Dual-Redundant Controller Configuration” and “Installing a
Controller and its Cache Module in a Dual-Redundant Controller
Configuration” to replace a controller and its cache module.

Removing a Controller and Cache Module in a DualRedundant Controller Configuration
Use the following steps to remove a controller and its cache module.
1. Connect a PC or terminal to the operational controller’s maintenance
port. The controller to which you’re connected is “this controller”; the
controller that you’re removing is the “other controller.”
2. Disable failover with the following command:
SET NOFAILOVER

3. Remove the ESD cover and program card from the “other controller.”
Save them for the replacement controller.
4. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

5. Enter N(o). FRUTIL displays the FRUTIL Main menu:
FRUTIL Main Menu:
1. Replace or remove a controller or cache module
2. Install a controller or cache module
3. Replace a PVA module
4. Replace an I/O module
5. Exit
Enter choice: 1, 2, 3, 4, or 5 ->

6. Enter option 1, Replace or remove a controller or cache module, from
the FRUTIL Main menu. FRUTIL displays the Replace or Remove
Options menu:
Replace or remove Options:
1. Other controller and cache module
2. Other controller module
3. Other cache module
4. Exit
Enter choice: 1, 2, 3, or 4 ->

5–10

HSG80 User’s Guide

7. Enter option 1, Other controller and cache module, from the Replace or
Remove Options menu. FRUTIL displays the following:
Slot Designations
(front view)
[

---

[

--------

EMU

---

Controller A

][

-------

]

[

--------

Controller B

-------

]

[

Cache Module A

][

---

PVA

---

Cache Module B

]

Remove both the slot A [or B] controller and cache module? Y/N

8. Enter Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Device Port 1 quiesced.
Device Port 2 quiesced.
Device Port 3 quiesced.
Device Port 4 quiesced.
Device Port 5 quiesced.
Device Port 6 quiesced.
All device ports quiesced.
Remove the slot A [or B] controller (the one without a
blinking green LED) within 4 minutes.

Caution The device ports must quiesce before removing the controller.
Failure to allow the ports to quiesce may result in data loss. Quiescing
may take several minutes.
ESD can easily damage a controller or a cache module. Wear a snugfitting, grounded ESD wrist strap.

Note A countdown timer allows a total of four minutes to remove the
controller and cache module. If you exceed four minutes, “this
controller” will exit FRUTIL and resume operations.
9. Remove the Hub cables from the “other controller.”
Note One or two hub cables may be attached, depending on the
configuration.

Replacement Procedures

5–11

10. Disengage both retaining levers and remove the “other controller,” then
place the controller into an antistatic bag or onto a grounded antistatic
mat.
Once the controller is removed, FRUTIL displays the following:
Remove the slot A [or B] cache module within x minutes, xx
seconds.

11. Disengage both retaining levers and partially remove the “other
controller’s” cache module—about half way.
12. Disable the ECB by pressing the battery disable switch until the status
light stops blinking—about five seconds.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before disconnecting the ECB cable from the cache module.
Failure to disable the ECB could result in cache module damage.
13. Disconnect the ECB cable from the “other controller’s” cache module,
remove the cache module, and place it onto a grounded antistatic mat or
into an antistatic bag.
Once the cache module is removed, FRUTIL displays the following:
Restarting all device ports. Please wait...
Device Port 1 restarted.
Device Port 2 restarted.
Device Port 3 restarted.
Device Port 4 restarted.
Device Port 5 restarted.
Device Port 6 restarted.
Do you have a replacement controller and cache module? Y/N

14. Enter N(o) if you don’t have a replacement controller and cache module;
disconnect the PC or terminal from the controller’s maintenance port.
Enter Y(es) if you have a replacement controller and cache module and
want to install it now. FRUTIL displays the following:
Insert both the slot A [or B] controller and cache module? Y/N

Note If you entered Y(es) go to step 6 on page 5–13.

5–12

HSG80 User’s Guide

Installing a Controller and its Cache Module in a DualRedundant Controller Configuration
Use the following steps to install a controller and its cache module.
1. Connect a PC or terminal to the operational controller. The controller to
which you’re connected is “this controller”; the controller whose cache
module you’re installing is the “other controller.”
2. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

3. Enter N(o). FRUTIL displays the FRUTIL Main menu:
FRUTIL Main Menu:
1. Replace or remove a controller or cache module
2. Install a controller or cache module
3. Replace a PVA module
4. Replace an I/O module
5. Exit
Enter choice: 1, 2, 3, 4, or 5 ->

4. Enter option 2, Install a controller or cache module, from the FRUTIL
Main menu. FRUTIL displays the Install Options menu:
Install Options:
1. Other controller and cache module
2. Other controller module
3. Other cache module
4. Exit
Enter choice: 1, 2, 3, or 4 ->

5. Enter option 1, Other controller and cache module, from the Install
Options menu. FRUTIL display the following:
Insert both the slot A [or B] controller and cache module? Y/N

Replacement Procedures

5–13

6. Enter Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Device Port 1 quiesced.
Device Port 2 quiesced.
Device Port 3 quiesced.
Device Port 4 quiesced.
Device Port 5 quiesced.
Device Port 6 quiesced.
All device ports quiesced.
.
.
.
Perform the following steps:
1. Turn off the battery for the new cache module by pressing
the battery’s shut off button for five seconds
2. Connect the battery to the new cache module.
3. Insert the new cache module in slot A [or B] within 4
minutes.

Note A countdown timer allows a total of four minutes to install the
cache module and controller. If you exceed four minutes, “this
controller” will exit FRUTIL and resume operations.

Caution ESD can easily damage a controller or a cache module. Wear
a snug-fitting, grounded ESD wrist strap.
7. Disable the ECB to which you’re connecting the new cache module by
pressing the battery disable switch until the status light stops blinking—
about five seconds.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before connecting the ECB cable to the cache module.
Failure to disable the ECB could result in ECB damage.
Make sure you align the cache module and controller in the appropriate
guide rails. If you do not align the modules correctly, damage to the
backplane can occur.
8. Connect the ECB cable to the new cache module.

5–14

HSG80 User’s Guide

9. Insert the new cache module into its slot and engage its retaining levers.
FRUTIL displays the following:
Insert the controller module, without its program card, in
slot A [or B] within x minutes, xx seconds.

10. Ensure that the program card is not in the replacement controller and
insert the new controller into its slot. Engage its retaining levers.
Note In mirrored mode, FRUTIL will initialize the mirrored portion of
the new cache module, check for old data on the cache module, and
then restart all device ports. After the device ports have been restarted,
FRUTIL will test the cache module and the ECB. After the test
completes, the device ports will quiesce and a mirror copy of the cache
module data will be created on the newly installed cache module.
FRUTIL displays the following:
The configuration has two controllers.
To restart the other controller:
1. Type ’restart other_controller’.
2. Press and hold the reset button while inserting the
program card on the slot A [or B] controller, then release
the reset button.
The controller will restart.
Field Replacement Utility terminated.

Note If the controller you’re installing was previously used in another
subsystem, it will need to be purged of the controller’s old
configuration (see “CONFIGURATION RESET,” page B–45).
11. Wait for FRUTIL to terminate, then connect the hub cables to the new
controller.
Note One or two hub cables may be attached, depending on the
configuration.
12. To allow the “other controller” to restart, enter the following command:
RESTART OTHER _CONTROLLER

Replacement Procedures

5–15

13. Hold the reset button while inserting the program card into the new
controller. Release the reset button and replace the ESD cover. The
controller will restart.
14. See “Configuring an HSG80 Array Controller,” page 2–3, to configure
the controller.
15. Enable failover, and re-establish the dual-redundant controller
configuration with the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the new controller.
16. Disconnect the PC or terminal from the controller’s maintenance port.

Replacing a Controller in a Dual-Redundant Controller Configuration
Use the following steps in “Removing a Controller in a DualRedundant Controller Configuration” and “Installing a Controller in a
Dual-Redundant Controller Configuration” to replace a controller.

Removing a Controller in a Dual-Redundant Controller
Configuration
Use the following steps to remove a controller:
1. Connect a PC or terminal to the operational controller’s maintenance
port. The controller to which you’re connected is “this controller”; the
controller that you’re removing is the “other controller.”
2. Disable failover and take the controllers out of their dual-redundant
configuration with the following command:
SET NOFAILOVER

3. Remove the program card’s ESD cover and program card. Save them for
the replacement controller.
4. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

5–16

HSG80 User’s Guide

7. Enter option 2, Other controller module, from the Replace or Remove
Options menu. FRUTIL displays the following:
Slot Designations
(front view)
[

---

[

--------

EMU

---

Controller A

][

-------

]

[

--------

Controller B

-------

]

[

Cache Module A

][

---

PVA

---

Cache Module B

]

Remove the slot A [or B] controller? Y/N

8. Type Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Replacement Procedures

5–17

Note A countdown timer allows a total of two minutes to remove the
controller. If you exceed two minutes, “this controller” will exit
FRUTIL and resume operations.
9. Remove the hub cables from the “other controller.”
Note One or two hub cables may be attached, depending on the
configuration.
10. Disengage both retaining levers, remove the “other controller,” and
place this controller into an antistatic bag or onto a grounded antistatic
mat.
Once the controller is removed, FRUTIL displays the following:
Restarting all device ports. Please wait...
Device Port 1 restarted.
Device Port 2 restarted.
Device Port 3 restarted.
Device Port 4 restarted.
Device Port 5 restarted.
Device Port 6 restarted.
Do you have a replacement controller? Y/N

11. Enter N(o) if you don’t have a replacement controller and disconnect the
PC or terminal from the controller’s maintenance port.
Enter Y(es) if you have a replacement controller and want to install it
now. FRUTIL displays the following:
Insert the slot A [or B] controller? Y/N

Note If you entered Y(es) go to step 6 on page 5–19.

5–18

HSG80 User’s Guide

Installing a Controller in a Dual-Redundant Controller
Configuration
Use the following steps to install a controller:
1. Connect a PC or terminal to the operational controller’s maintenance
port. The controller to which you’re connected is “this controller”; the
controller that you’re installing is the “other controller.”
2. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

5. Enter option 2, Other controller module, from the Install Options menu.
FRUTIL display the following:
Insert the slot A [or B] controller? Y/N

Replacement Procedures

5–19

6. Enter Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Device Port 1 quiesced.
Device Port 2 quiesced.
Device Port 3 quiesced.
Device Port 4 quiesced.
Device Port 5 quiesced.
Device Port 6 quiesced.
All device ports quiesced.
.
.
.
Insert the controller module, without its program card, in
slot A [or B] within x minutes, xx seconds.

Note A countdown timer allows a total of two minutes to install the
controller. If you exceed two minutes, “this controller” will exit
FRUTIL and resume operations.

Caution ESD can easily damage a controller. Wear a snug-fitting,
grounded ESD wrist strap.
Make sure you align the controller in the appropriate guide rails. If you
do not align the controller correctly, damage to the backplane can
occur.
7. Ensure that the program card is not in the new controller and insert the
new controller into its slot. Engage its retaining levers.
FRUTIL will display the following:
The configuration has two controllers.
To restart the other controller:
1. Type ’restart other_controller’.
2. Press and hold the reset button while inserting the
program card on the slot A [or B] controller, then release
the reset button.
The controller will restart.
Field Replacement Utility terminated.

5–20

HSG80 User’s Guide

Note If the controller you’re installing was previously used in another
subsystem, it will need to be purged of the controller’s old
configuration (see “CONFIGURATION RESET,” page B–45).
8. Wait for FRUTIL to terminate and connect the hub cables to the new
controller.
Note One or two hub cables may be attached, depending on the
configuration.
9. To allow the “other controller” to restart, type the following command:
RESTART OTHER _CONTROLLER

10. Hold the reset button while inserting the program card into the new
controller. Release the reset button and replace the ESD cover. The
controller will restart.
11. See “Configuring an HSG80 Array Controller,” page 2–3, to configure
the controller.
12. Enable failover, and re-establish the dual-redundant configuration with
the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the new controller.
13. Disconnect the PC or terminal from the controller’s maintenance port.

Replacement Procedures

5–21

Replacing a Cache Module in a Dual-Redundant Controller Configuration
Use the following steps in “Removing a Cache Module in a DualRedundant Controller Configuration” and “Installing a Cache Module
in a Dual-Redundant Controller Configuration” to replace a cache
module.
Note The new cache module must contain the same memory
configuration as the cache module it’s replacing.

Removing a Cache Module in a Dual-Redundant
Controller Configuration
Use the following steps to remove a cache module:
1. Connect a PC or terminal to the operational controller’s maintenance
port. The controller to which you’re connected is “this controller”; the
controller that you’re removing is the “other controller.”
2. Disable failover and take the controllers out of their dual-redundant
configuration with the following command:
SET NOFAILOVER

3. Remove the ESD cover and program card from the “other controller.”
Save them for reinstallation later.
4. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

5–22

HSG80 User’s Guide

7. Enter option 3, Other cache module, from the Replace or Remove
Options menu. FRUTIL displays the following:
Slot Designations
(front view)
[

---

EMU

---

[

--------

Controller A

][

-------

]

[

--------

Controller B

-------

]

[

Cache Module A

][

---

PVA

---

Cache Module B

]

Remove the slot A [or B] cache module? Y/N

8. Enter Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Device Port 1 quiesced.
Device Port 2 quiesced.
Device Port 3 quiesced.
Device Port 4 quiesced.
Device Port 5 quiesced.
Device Port 6 quiesced.
All device ports quiesced.
Remove the slot A [or B] cache module within 2 minutes. Then
disconnect the external battery from the cache module.

Caution The device ports must quiesce before removing the cache
module. Failure to allow the ports to quiesce may result in data loss.
Quiescing may take several minutes.
ESD can easily damage the cache module. Wear a snug-fitting,
grounded ESD wrist strap.

Replacement Procedures

5–23

Note A countdown timer allows a total of two minutes to remove the
cache module. If you exceed two minutes, “this controller” will exit
FRUTIL and resume operations.
9. Disengage both retaining levers and partially remove the “other
controller’s” cache module—about half way.
10. Disable the ECB by pressing the battery disable switch until the status
light stops blinking—about five seconds.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before disconnecting the ECB cable from the cache module.
Failure to disable the ECB could result in cache module damage.
11. Disconnect the ECB cable from the “other controller’s” cache module,
remove the cache module, and place it onto a grounded antistatic mat or
into an antistatic bag.
Once the cache module is removed, FRUTIL displays the following:
Restarting all device ports. Please wait...
Device Port 1 restarted.
Device Port 2 restarted.
Device Port 3 restarted.
Device Port 4 restarted.
Device Port 5 restarted.
Device Port 6 restarted.
Do you have a replacement cache module? Y/N

12. Enter N(o) if you don’t have a replacement cache module, and
disconnect the PC or terminal from the controller’s maintenance port.
Enter Y(es) if you have a replacement cache module and want to install
it now. FRUTIL displays the following:
Insert the slot A [or B] cache module? Y/N

Note If you entered Y(es) go to step 6 on page 5–25.

5–24

HSG80 User’s Guide

Installing a Cache Module in a Dual-Redundant
Controller Configuration
Use the following steps to install a cache module:
1. Connect a PC or terminal to the operational controller’s maintenance
port. The controller to which you’re connected is “this controller”; the
controller that you’re installing is the “other controller.”
2. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

5. Enter option 3, Other cache module, from the Install Options menu.
FRUTIL display the following:
Insert the slot A [or B] cache module? Y/N

Replacement Procedures

5–25

6. Enter Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Note A countdown timer allows a total of two minutes to install the
cache module. If you exceed two minutes, “this controller” will exit
FRUTIL and resume operations.

Caution ESD can easily damage a cache module. Wear a snug-fitting,
grounded ESD wrist strap.
Make sure you align the cache module in the appropriate guide rails. If
you do not align the cache module correctly, damage to the backplane
can occur.
7. Disable the ECB to which you’re connecting the new cache module by
pressing the battery disable switch until the status light stops blinking—
about five seconds.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before connecting the ECB cable to the cache module.
Failure to disable the ECB could result in ECB damage.
8. Connect the ECB cable to the new cache module.

5–26

HSG80 User’s Guide

9. Insert the new cache module into its slot and engage its retaining levers.
Note In mirrored mode, FRUTIL will initialize the mirrored portion of
the new cache module, check for old data on the cache module, and
then restart all device ports. After the device ports have been restarted,
FRUTIL will test the cache module and the ECB. After the test
completes, the device ports will quiesce and a mirror copy of the cache
module data will be created on the newly installed cache module.
FRUTIL displays the following:
The configuration has two controllers.
To restart the other controller:
1. Type ’restart other_controller’.
2. Press and hold the reset button while inserting the
program card on the slot A [or B] controller, then
release the reset button.
The controller will restart.
Field Replacement Utility terminated.

10. To allow the “other controller” to restart, type the following command:
RESTART OTHER _CONTROLLER

11. Hold the reset button while inserting the program card into the
controller. Release the reset button and replace the ESD cover. The
controller will restart.
12. Enable failover, and re-establish the dual-redundant configuration with
the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the “other controller.”
13. Disconnect the PC or terminal from the controller’s maintenance port.

Replacement Procedures

5–27

Replacing the External Cache Battery Storage
Building Block
The ECB SBB can be replaced with cabinet power on or off. A singlebattery ECB SBB is shown in Figure 5–3 and a dual-battery ECB SBB
is shown in Figure 5–4.
Figure 5–3 Single-Battery ECB SSB Configuration

1
SH

US
STAT
F
OF
UT

E
CH
CA ER
W
PO

~
CXO5715A

1
2
3

Battery disable switch
Status LED
ECB Y cable

Figure 5–4 Dual-battery ECB SBB Configuration

1
2

US
STAT
F
OF
UT

E
CH
CA
R
WE
PO
E
CH
CA
R
WE
PO

US
STAT
F
OF
UT

4
3

~
CXO5713A

1
2
3
4

Battery disable switch
Status LED
ECB Y cable
Faceplate and controls for second battery

5–28

HSG80 User’s Guide

Replacing the External Cache Battery Storage Building Block With Cabinet
Powered On
Use the following steps to replace the ECB SSB with the cabinet
powered on:
Note The procedure for a dual-redundant controller configuration
assumes that a single ECB SBB with a dual battery is installed and an
empty slot is available for the replacement ECB SBB. If an empty slot
is not available, place the new ECB SBB on the top of the enclosure.
After the old ECB SBB has been removed, carefully insert the new
ECB SBB into the empty slot.
1. Connect a PC or terminal to the controller with the ECB SBB that you
intend to replace. The controller to which you’re connected is “this
controller.”
2. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

3. Enter Y(es). FRUTIL displays the following:
If the batteries were replaced while the cabinet was powered
down, press return.
Otherwise follow this procedure:
WARNING: Ensure that at least one battery is connected to the
Y cable at all times during this procedure.
1. Connect the new battery to the unused end of the 'Y' cable
attached to cache A [or B].
2. Disconnect the old battery. Do not wait for the new
battery's status light to turn solid green.
3. Press return.

Caution The ECB cable has a 12-volt and a 5-volt pin. Improper
handling or misalignment when connecting or disconnecting could
cause these pins to contact ground, resulting in cache module damage.
4. Insert the new ECB SBB into the empty battery slot.
Note If an empty slot is not available, place the new ECB SBB on the
top of the enclosure.

Replacement Procedures

5–29

5. Connect the new battery to the unused end of the Y cable attached to
cache A [or B]
6. Disconnect the old battery. Do not wait for the new battery’s status light
to turn solid green.
7. Press return.
FRUTIL displays the following:
Updating this battery’s expiration date and deep discharge
history.
Field Replacement Utility terminated.

8. Disconnect the PC or terminal from the controller’s maintenance port.
9. If this is a dual-redundant controller configuration and you installed a
dual-battery ECB SBB and you want to connect the other cache module
to the new ECB SBB, connect the PC or terminal to the other
controller’s maintenance port. The controller to which you’re now
connected is “this controller.”
10. Repeat steps 2 through 8.
11. Remove the old ECB SBB.
Note If an empty slot was not available, and the new ECB SBB was
placed on the top of the enclosure, carefully insert it now into the empty
slot.

Replacing the External Cache Battery Storage Building Block With Cabinet
Powered Off
Use the following steps to replace the ECB SSB with the cabinet
powered off:
1. If the controller and cache module are not operating, go to step 4.
Otherwise, go to the next step.
2. Connect a PC or terminal to the controller’s maintenance port. The
controller to which you’re connected is “this controller.”
3. Shut down the controllers. In single-controller configurations, shut
down “this controller.” In dual-redundant controller configurations, shut
down the “other controller” first, then shut down “this controller” with
the following commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

5–30

HSG80 User’s Guide

When the controllers shut down, their reset buttons and their first three
LEDs are lit continuously. This may take several minutes, depending on
the amount of data that needs to be flushed from the cache modules.
4. Turn off the power to the subsystem.
5. Insert the new ECB SBB into its slot.
Caution The ECB cable has a 12-volt and a 5-volt pin. Improper
handling or misalignment when connecting or disconnecting could
cause these pins to contact ground, resulting in cache module damage.
6. Connect the open end of the ECB Y cable to the new ECB.
7. Restore power to the subsystem. The controller automatically restarts.
8. Disconnect the ECB cable from the old ECB.
9. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

10. Type Y(es). FRUTIL displays the following:
If the batteries were replaced while the cabinet was powered
down, press return.
Otherwise follow this procedure:
WARNING: Ensure that at least one battery is connected to the
Y cable at all times during this procedure.
1. Connect the new battery to the unused end of the 'Y' cable
attached to cache A [or B].
2. Disconnect the old battery. Do not wait for the new
battery's status light to turn solid green.
3. Press return.

11. Press return.
FRUTIL displays the following:
Updating this battery's expiration date and deep discharge
history.
Field Replacement Utility terminated.

12. Disconnect the PC or terminal from the controller’s maintenance port.

Replacement Procedures

5–31

13. In a dual-redundant controller configuration and if the ECB was
replaced for both cache modules, connect the PC or terminal to the other
controller’s maintenance port. The controller to which you’re now
connected is “this controller.”
14. Repeat steps 9 through 12.
15. Remove the old ECB SBB.

5–32

HSG80 User’s Guide

Replacing a GLM
Use the following steps in “Removing a GLM” and “Installing a GLM”
to replace a GLM in a controller. Figure 5–5 shows the location and
orientation of the GLMs.
Figure 5–5 Location of GLMs in Controller
Access door

Release
lever

Port 1
GLM

Locking
tab
Guide
holes

GLM
connector

Port 2
GLM

CXO6245A

Removing a GLM
Use the following steps to remove a GLM:
1. Remove the controller using either the steps in “Removing the
Controller in a Single Controller Configuration,” page 5–3, or
“Removing a Controller in a Dual-Redundant Controller
Configuration,” page 5–15.
2. Remove the screw that secures the access door on the top of the
controller.
3. Remove the access door, and set it aside.

Replacement Procedures

5–33

Caution ESD can easily damage a GLM. Wear a snug-fitting,
grounded ESD wrist strap.
4. Disengage the GLM’s locking tabs that protrude through the guide holes
on the controller.
5. Use your index finger and thumb to operate the release lever on the
exposed end of the GLM. Press the lower end of the release lever with
your index finger while pulling the raised end of the release lever up
with your thumb.
6. Remove the GLM.

Installing a GLM
Use the following steps to remove a GLM:
Note Before inserting the new GLM, note the holes in the board where
the GLM will reside.

Caution ESD can easily damage a GLM. Wear a snug-fitting,
grounded ESD wrist strap.
1. Insert the new GLM by first placing the cable connection end of the
GLM through the opening on the front of the controller.
2. Line up the locking tab on the bottom of the replacement GLM with the
holes in the board, and press firmly to seat the GLM.
3. Press the release lever firmly into place to secure the GLM.
4. Install the access door on the top of the controller and secure it with the
screw.
5. Install the controller using either the steps in “Installing the Controller
in a Single Controller Configuration,” page 5–4, or “Installing a
Controller in a Dual-Redundant Controller Configuration,” page 5–18.

5–34

HSG80 User’s Guide

Replacing a PVA Module
Use the following instructions in this section to replace a PVA module
in either (1) the master enclosure or (2) the first expansion or second
expansion enclosure.
Note This procedure is not applicable for the M1 shelf.
The HSG80 controller can support up to three enclosures: the master
enclosure, the first expansion enclosure, and the second expansion
enclosure.
A PVA can be replaced in either a single or a dual-redundant controller
configuration using this procedure.

Replacing the PVA in the Master Enclosure (ID 0)
Use the following steps to replace the PVA in the master enclosure:
1. Connect a PC or terminal to the controller’s maintenance port.
2. In a dual-redundant controller configuration, disable failover with the
following command:
SET NOFAILOVER

3. In a dual-redundant controller configuration, remove the program card’s
ESD cover and program card from the other controller. Save them for
reinstallation.
4. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

Replacement Procedures

5–35

6. Enter option 3, Replace a PVA module from the FRUTIL Main menu.
FRUTIL displays the PVA Replacement menu:
FRUTIL PVA Replacement Menu:
1. Master Enclosure (ID 0)
2. First Expansion Enclosure (ID 2)
3. Second Expansion Enclosure (ID 3)
4. Exit
Enter Choice: 1, 2, 3, or 4 ->

Note The HSG80 controller can support up to three enclosures. The
FRUTIL PVA Replacement Menu has options for three enclosures
regardless of how many enclosures are connected.
7. Enter option 1, Master Enclosure (ID 0), from the FRUTIL PVA
Replacement Menu. FRUTIL displays the following:
Do you have a replacement PVA module? Y/N

8. Enter Y(es) and press return. FRUTIL displays the following:
Ensure the replacement PVA’s address is set to zero.
Press return to quiesce device port activity.

9. Set the replacement PVA’s address to zero.
10. Press return and wait for FRUTIL to quiesce the device ports. This may
take several minutes. FRUTIL displays the following:
All device ports quiesced.
Replace the PVA in the master cabinet.

11. Remove the old PVA and install the new PVA. FRUTIL displays the
following:
Press return to resume device port activity.

12. Press return to resume device port activity (this may take several
minutes). When all port activity has restarted, FRUTIL displays the
following:
PVA replacement complete.

5–36

HSG80 User’s Guide

In a dual-redundant configuration, FRUTIL also displays:
The configuration has two controllers.
To restart the other controller:
1. Type ’restart other_controller’.
2. Press and hold the reset button while inserting the
program card on the slot A [or B] controller, then
release the reset button.
The controller will restart.
Field Replacement Utility terminated.

13. To allow the “other controller” to restart, type the following command:
RESTART OTHER _CONTROLLER

14. Hold the reset button while inserting the program card into the
controller. Release the reset button and replace the ESD cover. The
controller will restart.
15. Enable failover and re-establish the dual-redundant configuration with
the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the “other controller.”
16. Disconnect the PC or terminal from the controller’s maintenance port.

Replacing the PVA in the First Expansion (ID 2) or Second Expansion (ID 3)
Enclosure
Use the following steps to replace the PVA in the first expansion (ID 2)
or second expansion (ID 3) enclosure:
1. Connect a PC or terminal to the controller’s maintenance port.
2. In a dual-redundant controller configuration, disable failover with the
following command:
SET NOFAILOVER

3. In a dual-redundant controller configuration, remove the program card’s
ESD cover and program card from the “other controller.” Save them for
reinstallation.

Replacement Procedures

5–37

4. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

Note The HSG80 controller can support up to three enclosures. The
FRUTIL PVA Replacement menu has options for three enclosures
regardless of how many enclosures are connected.
7. Enter option 2, First Expansion Enclosure (ID 2), to replace the PVA in
the first expansion enclosure or option 3, Second Expansion Enclosure
(ID 3) to replace the PVA in the second expansion enclosure from the
FRUTIL PVA Replacement menu. FRUTIL displays the following:
Do you have a replacement PVA module? Y/N

8. Enter Y(es) and press return. FRUTIL displays the following:
Ensure the replacement PVA’s address is set to 2 [or 3].
Press return to quiesce device port activity.

9. Set the replacement PVA’s address to 2 for the first expansion enclosure
or to 3 for the second expansion enclosure.

5–38

HSG80 User’s Guide

10. Press return and wait for FRUTIL to quiesce the device ports. This may
take several minutes. FRUTIL displays the following:
All device ports quiesced.
Using the power switch, power down expansion cabinet #2 [or
#3] and replace the PVA.

11. Power down the appropriate expansion cabinet.
12. Remove the old PVA and install the new PVA.
13. Power on the appropriate expansion cabinet. FRUTIL displays the
following:
Press return to resume device port activity.

14. Press return to resume device port activity. This may take several
minutes. When all port activity has restarted, FRUTIL displays the
following:
PVA replacement complete.

In a dual-redundant configuration, FRUTIL also displays:
The configuration has two controllers.
To restart the other controller:
1. Type ’restart other_controller’.
2. Press and hold the reset button while inserting the
program card on the slot B controller, then release the
reset button.
The controller will restart.
Field Replacement Utility terminated.

15. To allow the “other controller” to restart, type the following command:
RESTART OTHER _CONTROLLER

16. Hold the reset button while inserting the program card into the new
controller. Release the reset button and replace the ESD cover. The
controller will restart.
17. Enable failover and re-establish the dual-redundant configuration with
the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the “other controller.”
18. Disconnect the PC or terminal from the controller’s maintenance port.

Replacement Procedures

5–39

Replacing an I/O Module
Figure 5–6 shows a rear view of the BA370 enclosure and the location
of the six I/O modules (also referred to as ports). Use the following
steps to replace an I/O module:
Note This procedure is not applicable for the M1 shelf.
An I/O module can be replaced in either a single-controller or a dualredundant controller configuration using this procedure.
Figure 5–6 I/O Module Locations in a BA370 Enclosure

Fan

Port 6

Port 4

Port 2

Port 5

Port 3

Port 1

Rear view
CXO6289A

Note The controller can function with one failed I/O module.
1. Connect a PC or terminal to the controller’s maintenance port.
2. In a dual-redundant controller configuration, disable failover with the
following command:
SET NOFAILOVER

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

5–40

HSG80 User’s Guide

Note The HSG80 controller can support up to three enclosures. The
I/O Module status can show the following states: Single Ended – OK,
Differential – OK, Termination only – OK, Missing or bad, Unknown
or bad, or N/A (cabinet is not present).
6. Enter option 4, Replace an I/O module, from the FRUTIL Main menu.
In the following example, cabinet 0, port 5 is missing or bad. FRUTIL
displays the following:
I/O Module Status:
Cabinet 0

Cabinet 2

Cabinet 3

-------------------

Port 1:

Single Ended - OK

N/A

Port 2:

Single Ended - OK

N/A

Port 3:

Single Ended - OK

N/A

Port 4:

Single Ended - OK

N/A

Port 5:

Missing or bad

N/A

Port 6:

Single Ended - OK

N/A

Is the replacement I/O module available? Y/N

7. Enter Y(es) and press return.
8. Wait for FRUTIL to quiesce the device ports. After the ports have been
quiesced (this may take several minutes), FRUTIL displays the
following:
All device ports quiesced.

Caution If you remove the incorrect module, the controller will crash.
9. Disconnect the cables (there may be one or two) from the appropriate
I/O module.
10. Remove the failed I/O module.

Replacement Procedures

5–41

11. Install a new I/O module.
12. Connect the cables (there may be one or two) to the I/O module.
13. Press return to resume device port activity. When all port activity has
restarted, FRUTIL displays the following:
I/O module replacement complete.

14. To allow the “other controller” to restart, type the following command:
RESTART OTHER _CONTROLLER

15. Hold the reset button while inserting the program card into the new
controller. Release the reset button and replace the ESD cover. The
controller will restart.
16. Enable failover and re-establish the dual-redundant configuration with
the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the “other controller.”
17. Disconnect the PC or terminal from the controller’s maintenance port.

5–42

HSG80 User’s Guide

Replacing DIMMs
Use the following steps in “Removing DIMMs” and “Installing
DIMMs” to replace DIMMs in a cache module. The cache module may
be configured as shown in Figure 5–7 and Table 5–1.
Figure 5–7 Cache-Module Memory Configurations

MC1-3
MC1-4

MC0-1
MC0-2

64MB configuration (2 x 32 MB)
256 MB configuration (2 x 128 MB)

MC1-3
MC1-4

128 MB configuration (4 x 32 MB)
512 MB configuration (4 x 128 MB)
CXO6288A

Table 5–1 Cache Module Memory Configurations
Memory

DIMMs

Quantity

Location

64 MB

32 MB

MC0-1 and MC1-3

128 MB

32 MB

MC0-1, MC0-2,
MC1-3, and MC1-4

256 MB

128 MB

MC0-1 and MC1-3

512 MB

128 MB

MC0-1, MC0-2,
MC1-3, and MC1-4

Note If a DIMM fails, note which DIMM you need to replace based on
the diagram that displays on the console.

Replacement Procedures

5–43

Caution ESD can easily damage a cache module or a DIMM. Wear a
snug-fitting, grounded ESD wrist strap.

Removing DIMMs
Use the following steps to remove a DIMM from a cache module:
1. Remove the cache module using the steps in either “Removing the
Cache Module in a Single Controller Configuration,” page 5–6, or
“Removing a Cache Module in a Dual-Redundant Controller
Configuration,” page 5–21.
2. Press down on the DIMM retaining levers at either end of the DIMM
you want to remove.
3. Grasp the DIMM and gently remove it from the DIMM slot.

5–44

HSG80 User’s Guide

Installing DIMMs
Use the following steps to install a DIMM in a cache module:
1. Insert the DIMM straight into the socket and ensure that the notches in
the DIMM align with the tabs in the socket (see Figure 5–8).
Figure 5–8 Installing a DIMM

Retaining
clip
(2x)

CXO6163A

2. Press the DIMM gently until it’s seated in the socket.
3. Double-check to ensure both ends of the DIMM are firmly seated in the
slot and both retaining clips engage the DIMM.
4. Install the cache module using the steps in either “Installing the Cache
Module in a Single Controller Configuration,” page 5–7, or “Installing a
Cache Module in a Dual-Redundant Controller Configuration,” page
5–24.

Replacement Procedures

5–45

Replacing a Fibre Cable or Hub
Use the following steps in “Remove a Fibre Cable or Hub” and “Install
a Fibre Cable or Hub” to replace a cable connected to either side of
your hub or to replace the hub itself.

Remove a Fibre Cable or Hub
Use the following steps to remove a cable connected to either side of
your hub or to remove the hub itself:
1. Shut down the host system.
2. Shut down the controllers. In single-controller configurations, shut
down “this controller.” In dual-redundant controller configurations, shut
down the “other controller” first, then shut down “this controller” with
the following commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

When the controllers shut down, their reset buttons and their first three
LEDs are lit continuously. This may take several minutes, depending on
the amount of data that needs to be flushed from the cache modules.
3. If you are replacing a cable, unplug the failed cable at each end. If you
are replacing a hub, unplug all of the cables connected to the hub.

Install a Fibre Cable or Hub
Use the following steps to install a cable connected to either side of
your hub or to install the hub itself:
1. If you are replacing a cable, plug the replacement cable into the ports
that the removed cable was plugged into.
If you are replacing a hub, plug all of the cables that were unplugged
from the removed hub into the replacement hub.
2. Push both reset buttons to restart the controllers.
The controllers automatically restart. Your subsystem is now ready for
operation.

5–46

HSG80 User’s Guide

Replacing a PCMCIA Card
Use the following steps to replace a PCMCIA (program) card:
Caution The new PCMCIA card must have the same software version
as the PCMCIA card being replaced. See “Installing a New Program
Card,” page 6–2, for more information.
1. From a host console, stop all host activity and dismount the logical units
in the subsystem.
2. Connect a maintenance PC or terminal to one of the controllers’
maintenance port in your subsystem.
3. Shut down the controllers. In single-controller configurations, shut
down “this controller.” In dual-redundant controller configurations, shut
down the “other controller” first, then shut down “this controller” with
the following commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

When the controllers shut down, their reset buttons and their first three
LEDs are lit continuously. This may take several minutes, depending on
the amount of data that needs to be flushed from the cache modules.
4. Remove the ESD program card cover on “this controller.”
5. Press and hold the reset button while ejecting the program card from
“this controller” by pressing the program-card eject button (see Figure
1–3 on page 1–8 for location).
6. Press and hold the reset button while inserting the new program card;
“this controller” automatically restarts. The controller is ready to handle
I/O when the CLI is responsive.
7. Replace the ESD program card cover on “this controller.”
The controller restarts. Your subsystem is now ready for operation.
8. In a dual-redundant controller configuration, repeat steps 4 through 7 for
the “other controller.”

Replacement Procedures

5–47

Replacing a Failed Storageset Member
If a disk drive fails in a RAIDset or mirrorset, the controller
automatically places it into the failedset. If the spareset contains a
replacement drive that satisfies the storageset’s replacement policy, the
controller automatically replaces the failed member with the
replacement drive. If the spareset is empty or doesn’t contain a
satisfactory drive, the controller simply “reduces” the storageset so that
it can operate without one of its members.
The storageset remains in this reduced state until the spareset contains a
satisfactory drive. When the controller senses a satisfactory drive in the
spareset, it automatically places the drive into the storageset and
restores the storageset to normal. Therefore, replacing a failed
storageset member means putting a satisfactory drive into the spareset.

Removing a Failed RAIDset or Mirrorset Member
Use the following steps to remove a failed RAIDset or mirrorset
member:
1. Connect a PC or terminal to the maintenance port of the controller that
accesses the reduced RAIDset or mirrorset.
2. Enable AUTOSPARE with the following command:
SET FAILEDSET AUTOSPARE

With AUTOSPARE enabled, any new disk drive that you insert into the
PTL location of a failed disk drive is automatically initialized and
placed into the spareset.
3. Remove the failed disk drive.

Installing the New Member
Use the following steps to install a new member:
1. Insert a new disk drive that satisfies the replacement policy of the
reduced storageset into the PTL location of the failed disk drive.
Note The controller automatically initializes the new disk drive and
places it into the spareset. As soon as it becomes a member of the
spareset, the controller automatically uses the new disk drive to restore
the reduced RAIDset or mirrorset. If initialization fails, the new disk
drive is placed into the failedset.

5–48

HSG80 User’s Guide

Shutting Down the Subsystem
Use the following steps to shut down a subsystem:
1. From a host console, stop all host activity and dismount the logical units
in the subsystem.
2. Connect a maintenance PC or terminal to the maintenance port of one of
the controllers in your subsystem.
3. Shut down the controllers. In single controller configurations, you only
need to shut down “this controller.” In dual-redundant controller
configurations, shut down the “other controller” first, then shut down
“this controller” with the following commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

When the controllers shut down, their reset buttons and their first three
LEDs are lit continuously. This may take several minutes, depending on
the amount of data that needs to be flushed from the cache modules.
4. Turn off the power to the subsystem.
Caution If you are shutting down the controller for longer than one
day, perform the steps in “Disabling and Enabling the External Cache
Batteries,” page 5–48, to prevent the write-back cache batteries from
discharging.

Disabling and Enabling the External Cache Batteries
Use the following steps to disable the ECBs:
Note The ECB SBB may contain one or two batteries, depending on
the configuration.
1. Press the battery-disable switch located on each battery within the ECB
SBB. The switch is the small button labeled SHUT OFF next to the
status LED (see Figure 5–9). Hold each switch in for approximately five
seconds. The ECB’s status LED will flash once and then shut off. Make
sure you perform this procedure on both ECB 1 and ECB 2, if
appropriate.

Replacement Procedures

5–49

Figure 5–9 Battery Disable Switch

ECB 1

ECB 2

Power
connector
Status
LED

Battery
disable
switch
CXO6164A

The batteries are no longer powering the cache module.
Note To return to normal operation, apply power to the storage
subsystem. The cache battery will be enabled when the subsystem is
powered on.

5–50

HSG80 User’s Guide

Restarting the Subsystem
Use the following steps to restart a subsystem:
1. Plug in the subsystem’s power cord, if it is not already plugged in.
2. Turn on the subsystem. The controllers automatically restart and the
ECBs automatically re-enable themselves to provide backup power to
the cache modules.

6–1

CHAPTER

Upgrading the Subsystem

This chapter provides instructions for upgrading the controller software, installing
software patches, upgrading firmware on a device, upgrading from a singlecontroller configuration to a dual-redundant controller configuration, and upgrading
cache memory.

Electrostatic Discharge
Electrostatic discharge (ESD) is a common problem and may cause data loss,
system down time, and other problems. The most common source of static
electricity is the movement of people in contact with carpets and clothing. Low
humidity also increases the amount of static electricity. You must discharge all
static electricity prior to touching electronic equipment. Follow the precautions in
the “Electrostatic Discharge Precautions” given in the Preface whenever you are
installing any component.

6–2

HSG80 User’s Guide

Upgrading Controller Software
You can upgrade the controller’s software two ways:

n
n

Install a new program card that contains the new software.
Download a new software image, and use the menu-driven Code
Load/Code Patch (CLCP) utility to write it onto the existing
program card. You may also use this utility to install, delete, and list
patches to the controller software.

Installing a New Program Card
Use the following steps to install a program card that contains the new
software. If you’re only upgrading the software in a single-controller
configuration, disregard references to the “other controller” and read
the plural controllers as the singular controller.
To upgrade the software by installing a new program card:
1. From the host console, dismount the storage units in the subsystem.
2. Connect a PC or terminal to one of the controllers’ maintenance port.
3. Shut down the controllers. In single-controller configurations, shut
down “this controller.” In dual-redundant controller configurations, shut
down the “other controller” first, then shut down “this controller” with
the following commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

When the controllers shut down, their reset buttons and their first three
LEDs are lit continuously. This may take several minutes, depending on
the amount of data that needs to be flushed from the cache modules.
Caution Do not change the subsystem’s configuration or replace any
of its modules until you’ve completed this procedure to upgrade the
controller software.
4. Remove the program card’s ESD cover on “this controller.”
5. Press and hold the reset button while ejecting the program card from
“this controller” by pressing the program card eject button (see Figure
1–3 on page 1-8).

Upgrading the Subsystem

6–3

6. Press and hold the reset button while inserting the new program card;
“this controller” automatically restarts. The controller is ready to ahndle
I/O when the CLI is responsive.
7. Replace the ESD program card cover on “this controller.”
8. In a dual-redundant controller configuration, repeat steps 4 through 7 for
teh “other controller.”
9. Mount the storage units on the host.

Downloading New Software
Use the CLCP to download new software to the program card while it’s
installed in the controller. Use the following steps to upgrade the
software with CLCP:
1. Obtain the new software image file from a customer service
representative.
Note The image file can also be loaded either by using StorageWorks
Command Console (SWCC) (see the SWCC documentation).
2. Load the image onto a PC or workstation using its file- or networktransfer capabilities.
3. From a host console, quiesce all port activity and dismount the storage
units in the subsystem.
Note Do not remove the program card.
4. Remove the ESD cover. If your program card is equipped with a writeprotection switch, disable write-protection by sliding the switch to the
left, as shown in Figure 6–1.
5. Connect a PC or terminal to the controller’s maintenance port.

6–4

HSG80 User’s Guide

Figure 6–1 Location of Write-Protection Switch

Write
protected
Write

CXO5873A

6. Start CLCP with the following command:
RUN CLCP

CLCP displays the following:
Select an option from the following list:
Code Load & Patch local program Main Menu
0: Exit
1: Enter Code LOAD local program
2: Enter Code PATCH local program
3: Enter EMU Code LOAD Utility
Enter option number

(0..3) [0] ?

7. Enter option 1, Enter Code LOAD local program, from the CLCP Main
menu to start the Code LOAD local program. CLCP displays the
following:
You have selected the Code Load Utility. This utility is used
to load a new software image into the program card currently
inserted in the controller.
Type ^Y or ^C (then RETURN) at any time to abort code load.
The code image may be loaded using SCSI Write Buffer commands
through the SCSI Host Port, or using KERMIT through the
maintenance terminal port.
0: Exit
1: Use the SCSI Host Port
2: Use the Maintenance Terminal Port
Enter option number (0..2) [0] ?

Note You can use either the SCSI host port (if your operating sysem
supports it) or the maintenance port. To use the SCSI host port, go to
step 8. To use the maintenance port, go to step 10.

Upgrading the Subsystem

6–5

8. Enter option 1, Use the SCSI Host Port, from the menu. CLCP displays
the following:
WARNING: proceeding with Controller Code Load will overwrite
the current Controller code image with a new image.
Do you want to continue (y/n) [n]: ?

9. Enter Y(es) and the download starts. When the download is complete,
CLCP writes the new image to the program card and restarts the
controller. This process takes one to three minutes. Go to step 15.
10. Enter option 2, Use the Maintenance Terminal Port, from the menu.
CLCP displays the following:
Perform the following steps before continuing:
* get new image file on serial line host computer
* configure KERMIT with the following parameters:
terminal speed 19200 baud, eight bit, no parity, 1 stop bit
It will take approximately 35 to 45 minutes to perform the
code load operation.
WARNING: proceeding with Controller Code Load will overwrite
the current Controller code image with a new image.
Do you want to continue (y/n) [n]: ?

11. Enter Y(es) and CLCP displays:
Start KERMIT now...

12. Connect the PC to the controller’s maintenance port (you’ll need the
PC-serial port adapter shown in Figure 1–3 on page 1–8).
13. Configure the KERMIT transfer protocol on the PC to 19200 baud,
eight bits, no parity, and one stop bit.
14. Use KERMIT to transfer the binary image from the PC to the controller.
When the download is complete, CLCP automatically writes the new
image to the program card and restarts the controller.
15. Verify that the controller is running the new software version with the
following command:
SHOW THIS CONTROLLER

16. If your program card is equipped with a write-protection switch, reenable write-protection by sliding the switch to the right.
17. Replace the program card’s ESD cover.
18. Repeat the procedure to upgrade the other controller in dual-redundant
subsystems.
19. Mount the storage units in the subsystem.

6–6

HSG80 User’s Guide

Using CLCP to Install, Delete, and List Software Patches
Use CLCP to manage software patches. These small programming
changes are placed into the controller’s non-volatile memory and
become active as soon you restart the controller. There is space for
about ten patches, depending upon the size of the patches you’re
installing.
Keep the following points in mind while installing or deleting patches:

n
n
n
n

Patches are associated with specific software versions. CLCP
verifies the patch against the currently installed version.
Patches are sequential: patch one must be entered before patch two,
and so on.
Deleting one patch also deletes all higher-numbered patches. For
example, if you delete patch two, you’ll automatically delete
patches three, four, and so on.
Controllers in a dual-redundant configuration must have the same
patches. You must install patches into each controller separately.

Installing a Software Patch
Use the following steps to install a software patch:
1. Obtain the patch file from a customer service representative or via the
Internet at: http://www.storage.digital.com/menusupport.htm.
2. Connect a PC or terminal to the controller’s maintenace port.
3. From the host console, quiesce all port activity.
4. Start CLCP with the following command:
RUN CLCP

(0..3) [0] ?

Upgrading the Subsystem

6–7

5. Enter option 2, Enter Code PATCH local program. CLCP displays the
following:
You have selected the Code Patch local program.
is used to manage software code patches.

This program

Select an option

from the following list:
Type ^Y or ^C (then RETURN) at any time to abort Code Patch.
Code Patch Main Menu
0: Exit
1: Enter a Patch
2: Delete Patches
3: List Patches
Enter option number (0..3) [0] ?

6. Enter option 1, Enter a Patch, to install a patch. CLCP displays the
following:
This is the Enter a Code Patch option.

The program prompts

you for the patch information, one line at time.

Be careful

to enter the information exactly as it appears on the patch
release. Patches may be installed for any version of software;
however, patches entered for software versions other than
XXXXX are not applied until the matching version of software
is installed.
To enter any patch, you must first install all patches with
lower patch numbers than the patch you are entering, beginning
with patch number 1, for a specific software version. If you
incorrectly enter the patch information, you are given the
option to review the patch one line at a time.
Type ^Y or ^C (then RETURN) at any time to abort Code Patch.
Do you wish to continue (y/n) [y] ?

7. Enter Y(es) and follow the on-screen prompts.
8. After the patch is installed, press the controller’s reset button to restart
the controller.

Deleting a Software Patch
Use the following steps to delete a software patch:
1. From a host console, quiesce all port activity.
2. Connect a PC or terminal to the controller’s maintenance port.

6–8

HSG80 User’s Guide

3. Start CLCP with the following command:
RUN CLCP

(0..3) [0] ?

4. Enter option 2, Enter Code PATCH local program. CLCP displays the
following:
You have selected the Code Patch local program.
is used to manage software code patches.

This program

Select an option

from the following list:
Type ^Y or ^C (then RETURN) at any time to abort Code Patch.
Code Patch Main Menu
0: Exit
1: Enter a Patch
2: Delete Patches
3: List Patches
Enter option number (0..3) [0] ?

5. Enter option 2, Delete Patches, to delete patches. CLCP displays the
following:
This is the Delete Patches option.

The program prompts you

for the software version and patch number you wish to delete.
If you select a patch for deletion that is required for
another patch, all dependent patches are also selected for
deletion. The program lists your deletion selections and asks
if you wish to continue.
Type ^Y or ^C (then RETURN) at any time to abort Code Patch.
The following patches are currently stored in the patch area:
Software Version - Patch number(s)
xxxx

xxxx

Currently, xx% of the patch area is free.
Software Version of patch to delete ?

Upgrading the Subsystem

6–9

6. Enter the software version of the patch to delete and press return. CLCP
displays the following:
Patch Number to delete ?

7. Enter the patch number to delete and press return. CLCP displays the
following:
The following patches have been selected for deletion:
Software Version - Patch #
xxxx

xxxx

Do you wish to continue (y/n) [n] ?

8. Enter Y(es) and the patches are deleted. CLCP displays the following:
Code Patch Main Menu
0: Exit
1: Enter a Patch
2: Delete Patches
3: List Patches
Enter option number (0..3) [0] ?

9. Enter option 0, Exit.
10. Press the controller’s reset button to restart the controller.

Listing Software Patches
Use the following steps to list software patches:
1. Connect a PC or terminal to the controller’s maintenance port.
2. Start CLCP with the following command:
RUN CLCP

(0..3) [0] ?

6–10

HSG80 User’s Guide

3. Enter option 2, Enter Code PATCH local program. CLCP displays the
following:
You have selected the Code Patch local program.
is used to manage software code patches.

This program

Select an option

from the following list:
Type ^Y or ^C (then RETURN) at any time to abort Code Patch.
Code Patch Main Menu
0: Exit
1: Enter a Patch
2: Delete Patches
3: List Patches
Enter option number (0..3) [0] ?

4. Enter option 3, List Patches, to list patches. CLCP displays the
following:
The following patches are currently stored in the patch area:
Software Version - Patch number(s)
xxxx

xxxx

Code Patch Main Menu
0: Exit
1: Enter a Patch
2: Delete Patches
3: List Patches
Enter option number (0..3) [0] ?

5. Enter option 0, Exit.

Upgrading the Subsystem

6–11

Upgrading Firmware on a Device
Use HSUTIL to upgrade a device with firmware located in contiguous
blocks at a specific LBN on a source disk drive configured as a unit on
the same controller. Upgrading firmware on a disk is a two-step process
as shown in Figure 6–2: first, copy the new firmware from your host to
a disk drive configured as a unit in your subsystem, then use HSUTIL
to load the firmware onto the devices in the subsystem.
Figure 6–2 Upgrading Device Firmware

Copy software
image from host

Use HSUTIL to
download software
image to devices

CXO5606A

Keep the following points in mind while using HSUTIL to upgrade
firmware on a device:

HSUTIL has been tested with the qualified devices listed in the
product-specific release notes that accompanied the software
release. You may attempt to install firmware on unsupported
devices—HSUTIL won’t prevent this—but if the upgrade fails, the
device may be rendered unusable and therefore require the
manufacturer’s attention.
If the power fails or the bus is reset while HSUTIL is installing the
new firmware, the device may become unusable. To minimize this
possibility, DIGITAL recommends that you secure a reliable power
source and suspend all I/O to the bus that services the device you’re
upgrading.

6–12

HSG80 User’s Guide

n
n

HSUTIL cannot install firmware on devices that have been
configured as single disk drive units or as members of a storageset,
spareset, or failedset. If you want to install firmware on a device
that has previously been configured as a single disk drive, delete the
unit number and storageset name associated with it.
During the installation, the source disk drive is not available for
other subsystem operations.
Some devices may not reflect the new firmware version number
when viewed from the “other” controller in a dual-redundant
configuration. If you experience this, enter the following CLI
command: CLEAR_ERRORS device-name UNKNOWN.
Do not issue any CLI commands that access or inspect devices that
are being formatted.

Use the following steps to upgrade firmware with HSUTIL:
1. Connect a PC or terminal to the maintenance port on the controller that
accesses the device you want to upgrade.
2. Configure a single-disk unit.
Note In the next steps, you’ll copy the firmware image to this unit,
then use HSUTIL to distribute it to the devices you’re upgrading. This
unit must be a newly initialized disk with no label or file structure to
ensure that the firmware image resides in contiguous blocks starting
from LBN 0 or another known LBN. Additionally, write-back caching
must be disabled (see “SET unit-number,” page B–137).
See “Configuring a Single-Disk Unit,” page 3–60, for instructions on
configuring a single-disk unit.
3. Copy the firmware image to the single-disk unit that you configured in
step 2. The firmware image must begin at a known LBN—usually 0—
and must be contiguous. See the documentation that accompanied your
host’s operating system for instructions on copying firmware images to
a disk drive.
Caution You must quiesce the host load before running HSUTIL or
damage to the storage device can occur.

Upgrading the Subsystem

6–13

4. Start HSUTIL with the following command:
RUN HSUTIL

HSUTIL displays the following:
HSUTIL Main Menu:
0. Exit
1. Disk Format
2. Disk Device Code Load
3. Tape Device Code Load
4. Disaster Tolerance Backend Controller Code Load
Enter function number: (0:4) [0]?

5. Enter option 2, Disk Device Code Load, from the HSUTIL menu.
6. Choose the single-disk unit as the source disk for the download.
7. Enter the starting LBN of the firmware image—usually LBN 0.
8. Enter the product ID of the device you want to upgrade. This ID
corresponds to the product information that’s reported in the Type
column when you issue the SHOW DISK FULL command.
HSUTIL lists all devices that correspond to the product ID you entered.
9. Enter the disk or tape name of the device you want to upgrade.
10. Confirm or enter the byte count of the firmware image.
11. Confirm the download.
12. Some disk firmware releases require that you reformat the disk after
upgrading its firmware. See the documentation that accompanied the
firmware to determine if you need to reformat the device.
13. When HSUTIL finishes downloading the firmware, it displays the new
firmware revision for the disk drive.

6–14

HSG80 User’s Guide

HSUTIL Messages
While you are formatting disk drives or installing new firmware,
HSUTIL may produce one or more of the messages in Table 6-1 (many
of the self-explanatory messages have been omitted).
Table 6–1 HSUTIL Messages and Inquiries
Message

Description

Insufficient resources

HSUTIL cannot find or perform the operation because
internal controller resources are not available.

Unable to change operation mode to
maintenance for unit

HSUTIL was unable to put the source single disk drive unit
into maintenance mode to enable formatting or code load.

Unit successfully allocated

HSUTIL has allocated the single disk drive unit for code load
operation. At this point, the unit and its associated device are
not available for other subsystem operations.

Unable to allocate unit

HSUTIL could not allocate the single disk drive unit. An
accompanying message explains the reason.

Unit is owned by another sysop

Device cannot be allocated because it is being used by
another subsystem function or local program.

Unit is in maintenance mode

Device cannot be formatted or code loaded because it is
being used by another subsystem function or local program.

Exclusive access is declared for unit

Another subsystem function has reserved the unit shown.

The other controller has exclusive
access declared for unit

The companion controller has locked out this controller from
accessing the unit shown.

The RUNSTOP_SWITCH is set to
RUN_DISABLED for unit

The RUN\NORUN unit indicator for the unit shown is set to
NORUN; the disk cannot spin up.

What BUFFER SIZE, (in BYTES),
does the drive require (2048, 4096,
8192) [8192]?

HSUTIL detects that an unsupported device has been
selected as the target device and the firmware image requires
multiple SCSI Write Buffer commands.You must specify the
number of bytes to be sent in each Write Buffer command.
The default buffer size is 8192 bytes. A firmware image of
256 K, for example, can be code loaded in 32 Write Buffer
commands, each transferring 8192 bytes.

What is the TOTAL SIZE of the code
image in BYTES [device default]?

HSUTIL detects that an unsupported device has been
selected as the target device. You must enter the total number
of bytes of data to be sent in the code load operation.

Upgrading the Subsystem

6–15

Table 6–1 HSUTIL Messages and Inquiries (Continued)
Message

Description

Does the target device support only the HSUTIL detects that an unsupported device has been
download microcode and save?
selected as the target device. You must specify whether the
device supports the SCSI Write Buffer command’s download
and save function.
Should the code be downloaded with a HSUTIL detects that an unsupported device has been selected
single write buffer command?
as the target device. You must indicate whether to download
the firmware image to the device in one or more contiguous
blocks, each corresponding to one SCSI Write Buffer
command.

6–16

HSG80 User’s Guide

Upgrading to a Dual-Redundant Controller Configuration
Use the following steps to upgrade a single-configuration subsystem to
a dual-redundant configuration subsystem. To replace failed
components, see Chapter 5, “Replacement Procedures,” for more
information. Before you complete this procedure, you’ll need the
following items:

n
n
n
n

Controller with the same software version and patch level that’s
installed on the subsystem’s current single controller
Cache module with the same memory configuration that’s installed
in the current cache module
ECB storage building block (SBB) for a dual-redundant
configuration
ECB cable

Installing a New Controller, Cache Module, and ECB
Use the following steps to install a new controller, cache module and
ECB:
1. Connect a PC or terminal to the controller’s maintenance port. The
controller to which you’re connected is “this controller”; the controller
that you’re installing is the “other controller.”
2. Start FRUTIL with the following command:
RUN FRUTIL

FRUTIL displays the following:
Do you intend to replace this controller’s cache battery? Y/N

Upgrading the Subsystem

6–17

5. Enter option 1, Other controller and cache module, from the Install
Options menu. FRUTIL display the following:
Insert the both the slot B controller and cache module? Y/N

6. Enter Y(es) and press return. FRUTIL displays the following:
Quiescing all device ports.

Please wait...

Device Port 1 quiesced.
Device Port 2 quiesced.
Device Port 3 quiesced.
Device Port 4 quiesced.
Device Port 5 quiesced.
Device Port 6 quiesced.
All device ports quiesced.
.
.
.
Perform the following steps:
1. Turn off the battery for the new cache module by pressing
the battery’s shut off button for five seconds.
2. Connect the battery to the new cache module.
3. Insert the new cache module in slot B within 4 minutes.

Note A countdown timer allows a total of four minutes to install the
controller and cache module. If you exceed four minutes, “this
controller” will exit FRUTIL and resume operations.

Caution ESD can easily damage a cache module or controller. Wear a
snug-fitting, grounded ESD wrist strap.
7. Insert the new ECB SBB into an empty slot.

6–18

HSG80 User’s Guide

8. Disable the ECB to which you’re connecting the new cache module by
pressing the battery disable switch until the status light stops blinking—
about five seconds.
Caution The ECB must be disabled—the status light is not lit or is not
blinking—before connecting the ECB cable to the cache module.
Failure to disable the ECB could result in the ECB being damaged.
Make sure you align the cache module and controller in the appropriate
guide rails. If you do not align the modules correctly, damage to the
backplane can occur.
9. Connect the ECB cable to the new cache module.
10. Insert the new cache module into its slot and engage its retaining levers.
FRUTIL displays the following:
Insert the controller module, without its program card, in
slot B within x minutes, xx seconds.

11. Ensure that the program card is not in the new controller and insert the
new controller into its slot. Engage its retaining levers.
Note In mirrored mode, FRUTIL will initialize the mirrored portion of
the new cache module, check for old data on the cache module, and
then restart all device ports. After the device ports have been restarted,
FRUTIL will test the cache module and the ECB. After the test
completes, the device ports will quiesce and a mirror copy of the cache
module data will be created on the newly installed cache module.
FRUTIL displays the following:
The configuration has two controllers.
To restart the other controller:
1. Type ’restart other_controller’.
2. Press and hold the reset button while inserting the
program card on the slot B controller, then release the
reset button.
The controller will restart.
Field Replacement Utility terminated.

Upgrading the Subsystem

6–19

Note If the controller you’re installing was previously used in another
subsystem, it will need to be purged of the controller’s old
configuration (see “CONFIGURATION RESET,” page B–45).
12. Wait for FRUTIL to terminate and connect the hub cables to the new
controller.
Note One or two hub cables may be attached, depending on the
configuration.
13. To allow the “other controller”to restart, type the following command:
RESTART OTHER _CONTROLLER

14. Hold the reset button while inserting the program card into the
controller. Release the reset button and replace the ESD cover. The
controller will restart.
15. See “Configuring an HSG80 Array Controller,” page 2–3, to configure
the controller.
16. Enable failover, and re-establish the dual-redundant controller
configuration with the following command:
SET FAILOVER COPY=THIS_CONTROLLER

This command copies the subsystem’s configuration from “this
controller” to the “other controller.”
17. Disconnect the PC or terminal from the controller’s maintenance port.

6–20

HSG80 User’s Guide

Upgrading Cache Memory
The cache module may be configured as shown in Figure 5–7 on page
5-42 and Table 6–2 on page 6–20.
Table 6–2 Cache Module Memory Configurations
Memory

DIMMs

Quantity

Location

64 MB

32 MB

MC0-1 and MC1-3

128 MB

32 MB

MC0-1, MC0-2,
MC1-3, and MC1-4

256 MB

128 MB

MC0-1 and MC1-3

512 MB

128 MB

MC0-1, MC0-2,
MC1-3, and MC1-4

In order to upgrade cache memory, the controller must be shut down.
Use the following steps to upgrade or add DIMMs:
1. From the host console, dismount the logical units in the subsystem. If
you are using a Windows NT platform, shut down the server.
2. If the controller is operating, connect a PC or terminal to the controller’s
maintenance port.
3. Shut down the controllers. In single controller configurations, shut down
“this controller.” In dual-redundant controller configurations, shut down
the “other controller” first, then shut down “this controller” with the
following commands:
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER

When the controllers shut down, their reset buttons and their first three
LEDs are lit continuously. This may take several minutes, depending on
the amount of data that needs to be flushed from the cache modules.
Caution ESD can easily damage a cache module or a DIMM. Wear a
snug-fitting, grounded ESD wrist strap.
4. Disable the ECB for the cache module in which you will be adding or
replacing DIMMS by pressing the battery disable switch until the status
light stops blinking—about five seconds.

Upgrading the Subsystem

6–21

Caution The ECB must be disabled—the status light is not lit or is not
blinking—before disconnecting the ECB cable from the cache module.
Failure to disable the ECB could result in cache module damage.
5. Disconnect the ECB cable from the cache module.
6. Disengage the two retaining levers, remove the cache module, and place
the cache module onto a grounded antistatic mat.
Note Allowed cache module memory configurations are shown in
Figure 5–7 on page 5-42 and described in Table 6–2 on page 6–20.
7. If you are adding DIMMs, insert the new DIMM straight into the socket
and ensure that the notches in the DIMM align with the tabs in the
socket (see Figure 5–8 on page 5-44).
8. If you are replacing DIMMs, press down on the DIMM retaining levers
at either end of the DIMM you want to remove.
9. Grasp the DIMM and gently remove it from the DIMM slot.
10. Insert the replacement DIMM straight into the socket and ensure that the
notches in the DIMM align with the tabs in the socket (see Figure 5–8
on page 5-44).
11. In a dual-redundant controller configuration, repeat steps 4 through 10,
as appropriate, for the other cache module.
Note In a dual-redundant controller configuration, both cache modules
must contain the same memory configuration.

Caution Make sure you align the cache module in the appropriate
guide rails. If you do not align the module correctly, damage to the
backplane can occur.
12. Insert the cache module into its slot and engage its retaining levers.
13. Connect the ECB cable to the cache module.
14. In a dual-redundant controller configuration, repeat steps 12 and 13, as
appropriate, for the other cache module.
15. Mount the logical units on the host. If you are using a Windows NT
platform, restart the server.

6–22

HSG80 User’s Guide

16. Set the subsystem date and time. In single controller configurations, set
“this controller.” In dual-redundant controller configurations, set “this
controller,” then set the “other controller” with the following command:
SET THIS_CONTROLLER TIME= dd-mmm-yyyy:hh:mm:ss
SET OTHER_CONTROLLER TIME= dd-mmm-yyyy:hh:mm:ss

17. Disconnect the PC or terminal from the controller’s maintenance port.

A–1

APPENDIX

System Profiles

This appendix contains device and storageset profiles you can use to create your
system profiles. It also contains an enclosure template you can use to help keep
track of the location of devices and storagesets in your shelves.

A–2

HSG80 User’s Guide

Device Profile
Type

___ Platter disk drive
___ Tape Drive

___ Optical disk drive
___ CD-ROM

Device Name ______________________________________________________________
Unit Number______________________________________________________________
Device Switches
Transportability

___ No (default)
___ Yes

Initialize Switches
Chunk size

Save Configuration

Metadata

___ Automatic (default)
___ 64 blocks
___ 128 blocks
___ 256 blocks
___ Other:

___ No (default)
___ Yes

___ Destroy (default)
___ Retain

Read Cache

Write Cache

Maximum Cache Transfer

___ Yes (default)
___ No

___ 32 blocks (default)
___ Other:

Availability

Write Protection

Read Ahead Cache

___ Run (default)
___ NoRun

___ No (default)
___ Yes

___ Yes (default)
___ No

Unit Switches

System Profiles

A–3

Storageset Profile
Type

___ RAIDset
___ Mirrorset

___ Stripeset
___ Striped Mirrorset

Storageset Name ___________________________________________________________
Disk Drives ________________________________________________________________
Unit Number ______________________________________________________________
Partitions
Unit #

Unit #

RAIDset Switches
Reconstruction Policy

Reduced Membership

Replacement Policy

___ Normal (default)
___ Fast

___ No (default)
___ Yes, missing:

___ Best performance (default)
___ Best fit
___ None

Replacement Policy

Copy Policy

Read Source

___ Best performance (default)
___ Best fit
___ None

___ Normal (default)
___ Fast

___ Least busy (default)
___ Round robin
___ Disk drive:

Chunk size

Save Configuration

Metadata

___ Automatic (default)
___ 64 blocks
___ 128 blocks
___ 256 blocks
___ Other:

___ No (default)
___ Yes

___ Destroy (default)
___ Retain

___ Yes (default)
___ No

Write Cache

Maximum Cache Transfer

___ Yes (default)
___ No

___ 32 blocks (default)
___ Other:

Availability

Write Protection

Read Ahead Cache

___ Run (default)
___ NoRun

___ No (default)
___ Yes

___ Yes (default)
___ No

Mirrorset Switches

Initialize Switches

Unit Switches
Read Cache

A–4

HSG80 User’s Guide

Enclosure Template
Power
Supply

Power
Supply

B–1

APPENDIX B

CLI Commands

This appendix contains the Command Line Interpreter (CLI)
commands you can use to interact with your controller. Each command
description contains the full syntax and examples of the use of the
command. The Overview provides a general description of the CLI and
how to use it.

B–2

HSG80 User’s Guide

CLI Overview
The Command Line Interpreter (CLI) is one of the user interfaces
through which you control your StorageWorks array controller in the
StorageWorks subsystem. The CLI commands allow you to manage the
subsystem by viewing and modifying the configuration of the controller
and the devices attached to them. You can also use the CLI to start
controller diagnostic and utility programs.
While the CLI provides the most detailed level of subsystem control, a
graphical user interface (GUI) is available for use with the CLI. The
GUI, StorageWorks Command Console (SWCC), replicates most of the
functions available within the CLI in graphic form and provides a userfriendly method of executing CLI commands.
CLI commands for configuring and viewing the controllers use the
relative terms “this controller” and “other controller.” See
“Typographical Conventions,” page xx, for an explanation of these
terms.

Using the CLI
You can access the CLI by connecting a maintenance terminal to the
port in the front bezel of the controller (local connection) or by using
HSZterm software (remote connection). See “Establishing a Local
Connection to the Controller,” page 2–7 for instructions explaining how
to connect a local terminal to the controller. After you have initially
configured the controller, making it visible to the host, you can perform
all other configuration tasks through a remote connection.
The section entitled “Maintenance Port Precautions,” page xix, explains
precautions you should observe when operating the CLI through a
maintenance port.

Command Overview
The CLI consists of six basic command types:

Controller Commands—Configure the controller’s SCSI ID
numbers, maintenance terminal characteristics, CLI prompt, and so
forth. Controller commands are also used to shut down and restart
the controller.

CLI Commands

n
n

n
n
n

B–3

Device Commands—Create and configure containers made from
physical devices attached to the controller.
Storageset Commands—Create and configure complex containers
made from groups of device containers. There are four basic types
of storagesets: stripesets, RAIDsets, striped-mirrorsets, and
mirrorsets. Storageset commands group device containers together
and allow them to be handled as single units.
Logical Unit Commands—Create and optimize access to logical
units made from any container type.
Failover Commands—Configure the controllers to operate in
transparent failover while also providing support for dualredundant configurations.
Diagnostic and Utility Commands—Perform general controller
support functions.

Getting Help
Help on using the CLI is at your fingertips. For an overview of the CLI
help system, enter help at the prompt. For help on a specific command
or to determine what switches are available with a command, enter as
much of the command as you know followed by a space and a question
mark. For example, to get information on the switches used with the
SET THIS_CONTROLLER command, enter:
SET THIS_CONTROLLER ?

See “HELP,” page B–69 for further information.

Entering CLI Commands
Use the following tips and techniques when entering CLI commands:

n
n
n

Commands are not case sensitive.
For most commands, you only need to enter enough of the
command to make the command unique. For example, SHO is the
same as entering SHOW.
The controller processes each command in sequence. You can
continue entering subsequent commands while the controller is
processing prior commands. A controller experiencing heavy data
I/O may respond slowly to CLI commands.

B–4

HSG80 User’s Guide

Specific keys or a combination of keys allow you to recall and edit the
last four commands. This feature can save time and help prevent
mistakes when you need to enter similar commands during the
configuration process. Table B–1 lists the keys used to recall and edit
commands.
Table B–1 Recall and Edit Command Keys
Key

Function

Up Arrow or Ctrl/B,
Down Arrow or Ctrl/N
Left arrow or Ctrl/D,
Right arrow or Ctrl/F
Ctrl/E
Ctrl/H or Backspace or
F12
Ctrl/J or Linefeed or
F13

Steps backward and forward through the
four most recent CLI commands.
Moves the cursor left or right in a command
line.
Moves the cursor to the end of the line.
Moves the cursor to the beginning of the
line.

Ctrl/U

Ctrl/A or F14

Ctrl/R

Deletes the word to the left of the cursor.
Deletes all characters on the same line as the
cursor.
Toggles between insert mode and overstrike
mode. The default setting is insert mode,
which allows you to insert characters at the
cursor location, moving the existing
characters to the right. Overstrike mode
replaces existing characters. The CLI returns
to insert mode at the beginning of each line.
Recalls the contents of the command line.
This is especially helpful if the system
issues a message that interrupts your typing.

Changing the CLI Prompt
You can change the CLI prompt that displays. Use the SET
THIS_CONTROLLER PROMPT= command. Enter a 1- to 16character string as the new prompt. For example, you could use the
prompt to indicate the array controller’s name, such as “HSG>.”

CLI Commands

B–5

Command Syntax
Commands to the controller must use the following command structure:
COMMAND parameter SWITCHES

Command. A word or phrase expressed as a verb that is used to
instruct the controller what to do. Every CLI command begins with
a command. Commands are represented in this manual in
capitalized form.
Parameter. When required in the command, one or more words or
phrases that supply necessary information to support the action of
the command. Not all CLI commands require parameters. The parts
of parameters that have to be entered as predefined text are in
uppercase italics and the variables are in lower-case italicized text.
Switches. An optional word or phrase that modifies the command.
Not all CLI commands require switches. Switches are represented
in this manual as capitalized, italicized text.

CLI Commands

B–7

ADD CONNECTIONS
Adds the specified host connection to the table of known connections.
This table is maintained in NVRAM. The maximum table length is 32
connections; if the table contains 32 entries, new connections cannot be
added unless some old ones are deleted.
There are two mechanisms for adding a new connection to the table, as
follows:

Physically connecting a host adapter to a controller port. During
loop initialization, the controller becomes aware of the connection
and adds it to the table. This physical discovery of connections
occurs at the point when a host adapter is plugged in to a controller
port and after a RESTART command. New connections discovered
through physical connection are assigned a default connection
name by the controller. The default connection name is of the form
!NEWCONnn.

Note Certain host conditions, such as a power cycle, that disturb the
state of the loop may cause a connection to reappear in the table. The
connection will be assigned a default connection name.

Adding a connection through the ADD CONNECTIONS
command.

Note ADD CONNECTIONS will add an entry to the table whether the
connection physically exists or not. The table can be completely filled
up with fictitious connections.

Syntax
ADD CONNECTIONS connection_name HOST_ID=n
ADAPTER_ID=n CONTROLLER=controller PORT=n

Parameters
connection_name
The name that will be assigned to the host connection. The connection
name can be any character string with one exception: it cannot be in the

B–8

HSG80 User’s Guide

form of a default connection name. The form of a default connection
name is !NEWCONnn.
Note The default connection name is assigned automatically by the
controller when the connection is physically made between a host
adapter and a controller port. Default connection names are assigned
only by the controller.
HOST_ID=nnnn-nnnn-nnnn-nnnn
Host_ID is the worldwide name of the host. It is a 16-character
hexadecimal number. The hyphens aren’t necessary, but are
recommended to avoid mistakes in entering the number.
ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
Adapter_ID is the worldwide name of the adapter. It is a 16-character
hexadecimal number. The hyphens aren’t necessary, but are
recommended to avoid mistakes in entering the number. Adapter_ID
maps to the fibre channel convention port name.
Note The worldwide name of the host and adapter are sometimes the
same. This is a characteristic of teh adapter.
CONTROLLER=THIS CONTROLLER
CONTROLLER=OTHER CONTROLLER
The controller parameter specifies whether the connection is to “this
controller” or “other controller.”
PORT=1
PORT=2
The port parameter specifies which port, 1 or 2, the connection is on.

CLI Commands

B–9

In transparent failover mode and normal mode, host connections on
controller port 1 have an offset of 0 and host connections on controller
port 2 have an offset of 100. These are the default offset values.
The relationship between LUN number, unit number, and offset is as
follows:

n
n
n

LUN number = unit number - offset.
Logical unit number or LUN number = the logical unit number
presented to the host connection.
Unit number = the number assigned to the unit in the ADD UNIT
command. This is the number by which the unit is known
internally to the controllers.

Note If the SET controller SCSI_VERSION=SCSI-3, the command
console LUN (CCL) is presented as LUN 0 to every connection,
superceding any unit assignments. See “ADD UNIT,” page B–27, for
more information.
OPERATING_SYSTEM=OS_name
Specifies the operating system of the host. The choices are:

n
n
n
n
n
n

DIGITAL_UNIX
IBM
SNI
SUN
VMS
WINNT

Examples
This will add to the table of known connections, an entry for a
connection named George with the indicated host and adapter
worldwide names, on port 2 of “this controller.”
CLI>ADD CONNECTIONS GEORGE HOST_ID=1000-0000-C920-1234
ADAPTER_ID=1000-0000-C920-5678 CONTROLLER=THIS PORT=2

B–10

HSG80 User’s Guide

See also
ADD UNIT
DELETE connections
SET connection-name

CLI Commands

B–11

ADD DISK
Names a disk drive and adds it to the controller’s configuration.
Note The controller supports a maximum of 72 storage devices, even
though more than 72 target IDs are available. Do not exceed the
maximum number of devices in the subsystem.

Syntax
ADD DISK container-name scsi-port-target-lun

Parameters
container-name
Assigns a name to the disk device. This is the name used with the ADD
UNIT command to create a single-disk unit.
The disk name must start with a letter (A through Z) and may consist of
a maximum of nine characters including letters A through Z, numbers 0
through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a disk drive DISKpttll, where pttll is the
disk’s Port-Target-LUN address. Although other naming conventions
are acceptable, this one presents the user with the type of disk drive and
its SCSI location.
scsi-port-target-lun
Indicates the SCSI device PTL address. Place one space between the
port number, target number, and the two-digit LUN number when
entering the PTL address. See the “Device PTL Addressing Convention
within the Controller,” page 3–33, for an explanation of the PTL
addressing naming format.
Note See the HSG80 Array Controller ACS Version 8.2 Release Notes
to determine whether the disk drive you are planning to use is
compatible with the controller.

B–12

HSG80 User’s Guide

Switches
NOTRANSPORTABLE (Default)
TRANSPORTABLE
Indicates whether a disk drive can be accessed exclusively by
StorageWorks controllers.
If the NOTRANSPORTABLE switch is specified, the controller makes
a small portion of the disk inaccessible to the host. This restricted space
is used to store information (metadata) that is used to improve data
reliability, error detection, and the ability to recover data. Because of
this metadata, only StorageWorks controllers can retrieve data from
non-transportable devices.
Transportable disk drives do not contain any metadata or restricted
areas. Therefore, transportable disks forfeit the advantage metadata
provides but can be moved to a non-StorageWorks environment with
their data intact. Disks that are to be used in storagesets cannot be set as
transportable.
If you specify the NOTRANSPORTABLE switch and there is no
metadata on the unit, the unit must be initialized. If you specify
TRANSPORTABLE for a disk that was originally initialized as a
NOTRANSPORTABLE, you should initialize the disk.
Note DIGITAL recommends you avoid using transportable disks
unless there is no other way to move the data.
TRANSFER_RATE_REQUESTED=ASYNCHRONOUS
TRANSFER_RATE_REQUESTED=20MHZ (Default)
TRANSFER_RATE_REQUESTED=10MHZ
TRANSFER_RATE_REQUESTED=5MHZ
Specifies the maximum data transfer rate at which the controller is to
communicate with the disk drive. The user might need to limit the
transfer rate to accommodate long cables between the controllers and
the device.

CLI Commands

B–13

Examples
To add DISK10000 at port 1, target 0, LUN 0, type:
ADD DISK DISK10000 1 0 0

To add DISK40200 as a transportable disk drive to port 4, target 2,
LUN 0, use:
ADD DISK DISK40200 4 2 0 TRANSPORTABLE

To add a disk drive named DISK30200 as non-transportable disk to port
3, target 2, LUN 0, and to set the data transfer rate to 10 MHz, enter the
following command on one line.
ADD DISK DISK30200 3 2 0 NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED=10MHZ

This example creates a host-addressable unit after the disk is added:
INITIALIZE DISK20000
ADD UNIT D199 DISK20000

See also
ADD MIRRORSET
ADD UNIT
DELETE container-name
LOCATE
SHOW DISKS
SHOW DEVICES
SET container-name

CLI Commands

B–15

ADD MIRRORSET
Names a mirrorset and adds it to the controller configuration.

Syntax
ADD MIRRORSET mirrorset-name disk-name1 [disk-nameN]

Parameters
mirrorset-name
Assigns a name to the mirrorset. This is the name used with the ADD
UNIT command to identify the mirrorset as a host-addressable unit.
The mirrorset name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a mirrorset MIRRn, where n is a
sequentially-assigned, unique identifier. Other naming conventions are
acceptable, but this naming convention presents both the type of
container and its unique identifier.
disk-name1 [disk-nameN]
Identifies the disk drives making up the mirrorset. A mirrorset may
contain one to six disk drives.

Switches
COPY=FAST
COPY=NORMAL (Default)
Sets the speed at which the controller copies data to a new member
from normal mirrorset members when data is being mirrored to the
storageset’s disk drives.
Specify COPY=FAST to allow the creation of mirrored data to take
precedence over other controller operations. When you specify
COPY=FAST, the controller uses more resources to create the mirrored
data, and copying takes less time. However, overall controller
performance is reduced during copying.

B–16

HSG80 User’s Guide

Specify COPY=NORMAL when operations performed by the
controller should take priority over the copy operation. If you specify
COPY=NORMAL, creating the mirrored data has a minimal impact on
performance.
POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
Sets the selection criteria the controller uses to choose a replacement
disk from the spareset when a mirrorset member fails.
Specify POLICY=BEST_FIT to choose a replacement disk drive from
the spareset that equals or exceeds the base member size (smallest disk
drive at the time the mirrorset was initialized). If there is more than one
disk drive in the spareset that meets the criteria, the controller selects a
disk drive with the best performance.
Specify POLICY=BEST_PERFORMANCE to choose a replacement
disk drive from the spareset with the best performance. The controller
attempts to select a disk on a different port than existing mirrorset
members. If there is more than one disk drive in the spareset matching
the best performance criteria, the controller selects a disk drive that
equals or exceeds the base member size.
Specify NOPOLICY to prevent the controller from automatically
replacing a failed disk device. The mirrorset operates in a reduced state
until a POLICY=BEST_FIT or POLICY=BEST_PERFORMANCE is
selected, or a member is manually placed in the mirrorset (see “SET
mirrorset-name,” page B–121).
READ_SOURCE=disk-name
READ_SOURCE=LEAST_BUSY (Default)
READ_SOURCE=ROUND_ROBIN
Selects the mirrorset member used by the controller to satisfy a read
request.
Specify the READ_SOURCE=disk-name of a specific member to
which you want the controller to direct all read requests. If the member
fails out of the mirrorset, the controller selects the first normal member
it finds to satisfy its read requests.

CLI Commands

B–17

Specify READ_SOURCE=LEAST_BUSY to direct read requests to
the mirrorset disk with the least amount of work in its queue. If
multiple members have equally short queues, the controller queries
normal disks for each read request as it would when READ_SOURCE=
ROUND_ROBIN is specified.
Specify READ_SOURCE=ROUND_ROBIN to sequentially direct read
requests to each mirrorset disk. The controller equally queries all
normal disks for each read request.

Examples
To add DISK10000, DISK20100, and DISK30200 as a mirrorset with
the name MIRR1, type:
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD MIRRORSET MIRR1 DISK10000 DISK20100 DISK30200

The following example shows how to create a host-addressable unit
after the mirrorset MIRR1 has been created:
INITIALIZE MIRR1
ADD UNIT D104 MIRR1

See also
ADD DISK
ADD UNIT
DELETE container-name
INITIALIZE
MIRROR
REDUCE
SHOW mirrorset-name
SHOW MIRRORSETS
SHOW STORAGESETS
UNMIRROR

CLI Commands

B–19

ADD RAIDSET
Names a RAIDset and adds the RAIDset to the controller’s
configuration. DIGITAL RAIDsets are often referred to as RAID level
3/5 storagesets because they use the best characteristics of RAID level
3 and RAID level 5. The number of members in the storageset is
determined by the number of containers specified by the containername parameter in the command. The data capacity of the RAIDset is
determined by the storage size of the smallest member.

Syntax
ADD RAIDSET RAIDset-name container-name1 container-name2
[container-nameN]

Parameters
RAIDset-name
Assigns a name to the RAIDset. This is the name used with the ADD
UNIT command to identify the RAIDset as a host-addressable unit.
The RAIDset name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It is common to name a RAIDset RAIDn, where n is a
sequentially-assigned, unique identifier. This naming convention
presents the user with the type of container and its unique identifier.
container-name1 container-name2 [container-nameN]
Identifies the disks making up the RAIDset. RAIDsets must include at
least 3 disk drives and no more than 14.

Switches
POLICY=BEST_FIT
POLICY=BEST_PERFORMANCE (Default)
NOPOLICY
Set the selection criteria the controller uses to choose a replacement
member from the spareset when a RAIDset member fails.

B–20

HSG80 User’s Guide

Specify POLICY=BEST_FIT to choose a replacement disk drive from
the spareset that equals or exceeds the base member size (smallest disk
drive at the time the RAIDset was initialized) of the remaining
members of the RAIDset. If more than one disk drive in the spareset is
the correct size, the controller selects a disk drive giving the best
performance.
Specify POLICY=BEST_PERFORMANCE to choose a replacement
disk drive from the spareset resulting in the best performance of the
RAIDset. The controller attempts to select a disk on a different port
than existing RAIDset members. If there is more than one disk drive in
the spareset matching the best performance criteria, the controller
selects the disk drive that equals or exceeds the base member size of the
RAIDset.
Specify NOPOLICY to prevent the controller from automatically
replacing a failed disk device. This RAIDset operates in a reduced state
until you select either POLICY=BEST_PERFORMANCE or
POLICY=BEST_FIT, or manually place a member in the RAIDset. See
“SET RAIDset-name,” page B–133, for more information regarding
this procedure.
RECONSTRUCT=FAST
RECONSTRUCT=NORMAL (Default)
Sets the speed at which the controller reconstructs data to a new
RAIDset disk that replaces the failed disk.
Specify FAST to allow the reconstruct process to take precedence over
other controller operations. When the RECONSTRUCT=FAST switch
is specified, the controller uses more resources to perform the
reconstruction. Reconstruction takes less time, but overall controller
performance is reduced during reconstruction.
Specify NORMAL to balance other controller operations with the
reconstruct operation. The controller uses relatively few resources to
perform the reconstruct process; therefore, there is little impact on
performance.

CLI Commands

B–21

REDUCED
NOREDUCED (Default)
Permits the addition of a RAIDset missing a member. Specify the
REDUCED switch when you add a reduced RAIDset (a RAIDset that
is missing a member).
Specify the NOREDUCED switch when all the disks making up the
RAIDset are present—for instance, when creating a new RAIDset.
Verify the RAIDset contains all but one of its disks before specifying
the REDUCED switch.

Examples
To create a RAIDset named RAID9 that contains disks DISK10000,
DISK20100, and DISK30200, use the following commands:
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID9 DISK10000 DISK20100 DISK30200

This example shows how to create a RAIDset named RAID8 that
contains disks DISK10000, DISK20100, and DISK30200 and uses the
BEST_FIT switch to indicate the replacement policy. Enter the ADD
RAIDSET command on one line.
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID8 DISK10000 DISK20100 DISK30200
POLICY=BEST_FIT

This example creates RAIDset RAID8 and then creates a hostaddressable unit.
INITIALIZE RAID8
ADD UNIT D70 RAID8

This example shows how you can create a three-member RAIDset from
the members of a reduced four-member RAIDset. Do not initialize the
RAIDset again.

B–22

HSG80 User’s Guide

Caution Data contained on the RAIDset will be erased if you
reinitialize the RAIDset.
ADD DISK DISK10300 1 3 0
ADD DISK DISK20400 2 4 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID6 DISK10300 DISK20400 DISK30200 REDUCED

See also
ADD UNIT
DELETE container-name
SET RAIDSET
SHOW RAIDSET
SHOW RAIDset-name
SHOW STORAGESETS
INITITALIZE

CLI Commands

B–23

ADD SPARESET
Adds a disk drive to the spareset.

Syntax
ADD SPARESET disk-name

Parameter
disk-name
Indicates the name of the disk drive being added to the spareset. Only
one disk drive can be added to the spareset with each ADD SPARESET
command.

Example
To add a disk drive named DISK20200 and DISK30300 to a spareset,
type:
ADD DISK DISK20200 2 2 0
ADD DISK DISK30300 3 3 0
ADD SPARESET DISK20200
ADD SPARESET DISK30300

See also
DELETE SPARESET
SET FAILEDSET
SHOW SPARESET
SHOW STORAGESETS

CLI Commands

B–25

ADD STRIPESET
Names a stripeset and adds it to the controller configuration. Stripesets
are sometimes referred to as RAID level 0 storagesets. The number of
members in the stripeset is determined by the number of containername parameters specified.

Syntax
ADD STRIPESET stripeset-name container-name1 container-name2
[container-nameN]

Parameters
stripeset-name
Assigns a name to the stripeset. This is the name used with the ADD
UNIT command to identify the stripeset as a host-addressable unit.
container-name1 container-name2 [container-nameN]
Identifies the members (disk drives or mirrorsets) making up the
stripeset. Stripeset can contain between 2 and 14 members.
The container name must start with a letter (A through Z) and may
consist of a maximum of nine characters including letters A through Z,
numbers 0 through 9, periods (.), dashes (-), or underscores (_).
Tip It’s common to name a stripeset STRIPEn, where n is a
sequentially-assigned, unique identifier. This naming convention
presents both the type of container and its unique identifier.

Note There is a 240 character limit for the command line. If you are
configuring a stripeset with multiple members (for example, more than
20) you will have to rename the members in order to execute the
command.

B–26

HSG80 User’s Guide

Examples
To create a stripeset named STRIPE1 with three disks: DISK10000,
DISK20100, and DISK30200, enter:
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD STRIPESET STRIPE1 DISK10000 DISK20100 DISK30200

To create a stripeset named STRIPE1 and then create a logical unit
from it, type:
INITIALIZE STRIPE1
ADD UNIT D103 STRIPE1

This example shows how to create a two-member striped mirrorset (a
stripeset whose members are mirrorsets), and how to create a logical
unit from it. Because you can initialize the stripeset, you do not need to
individually initialize the mirrorsets.
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD DISK DISK40300 4 3 0
ADD MIRRORSET MR1 DISK10000 DISK20100
ADD MIRRORSET MR2 DISK30200 DISK40300
ADD STRIPESET STRIPE1 MR1 MR2
INITIALIZE STRIPE1
ADD UNIT D104 STRIPE1

See also
ADD UNIT
ADD MIRRORSET
DELETE container-name
INITIALIZE
SHOW STORAGESET
SHOW STRIPESET
SHOW stripeset-name

CLI Commands

B–27

ADD UNIT
Creates a logical unit from a device, container, or partition. The
controller maps all requests from the host to the logical-unit number as
requests to the container specified in the ADD UNIT command.
If you add a newly-created storageset or disk to your subsystem, you
must initialize it before it can be added as a logical unit. If you are
adding a storageset or disk that has data on it that you want to maintain,
do not initialize it; it will be added as logical unit.

Syntax
ADD UNIT unit-number container-name

Parameters
unit-number
Assigns a number to the unit being created from a device, container, or
partition in the subsystem. The host uses this number to indicate the
source or target for every I/O request it sends to the controller. The
unit-number is a host-addressable LUN. The unit-number is assigned to
one of the host ports.
Unit numbers are 0-99 and are prefixed by one of the following:
D—assigns units to Port 1
D1—assigns units to Port 2
Adding unit D00 creates a logical unit and presents it as D00 to the host
on port 1. Adding unit D100 creates a logical unit and presents it as
D00 to the host on port 2. Units must be on a single port. Do not split
partitioned units across ports.
The LUN number a host connection assigns to a LUN is a function of
the UNIT_OFFSET qualifier in the ADD (or SET) connections
command: LUN number = unit number - offset
If no value is specified for the UNIT_OFFSET qualifier in the ADD (or
SET) CONNECTIONS command, then host connections on controller
port 1 have an offset of 0 and host connections on controller port 2 have
an offset of 100. These are the default offset values.

HSG80 User’s Guide

container-name
Specifies the name of the container (disk drive, device, storageset, or
partition) that is used to create the unit.
A maximum of 48 devices can make up one unit.

Switches
Table B–2 lists all switches for the ADD UNIT command and identifies
which switches may be used with each type of device or storageset.
Descriptions of each switch follow the table.

Container
Type

MAXIMUM_CACHED_
TRANSFER
PREFERRED_PATH
NOPREFERRED_PATH
READ_CACHE
NOREAD_CACHE
READAHEAD_CACHE
NOREADAHEAD_CACHE
WRITE_PROTECT
NOWRITE_PROTECT
WRITEBACK_CACHE
NOWRITEBACK_CACHE
RUN
NORUN

Table B–2 ADD UNIT Switches for Storagesets
Switch
ENABLE_ACCESS_PATH
DISABLE_ACCESS_PATH
PARTITION=partition-number

B–28

RAIDset

✔

Stripeset

✔

Mirrorset

✔

NoTransportable
Disk

✔

Transportable
Disk

✔

Note Regardless of the storageset type, you cannot specify RUN and
NORUN for partitioned units.
ENABLE_ACCESS_PATH=
DISABLE_ACCESS_PATH=
Specifies the access path. It can be a single specific host ID, multiple
host IDs, or all host IDs (ALL). If you have multiple hosts on the same

CLI Commands

B–29

bus, you can use this switch to restrict hosts from accessing certain
units. This switch limits visibility of specific units from certain hosts.
For example, if two hosts are on the same bus, you can restrict each
host to access only specific units.
If you enable another host ID(s), previously enabled host(s) are not
disabled. The new ID(s) are added. If you wish to enable only certain
ID(s), disable all access paths (DISABLE_ACCESS_PATH=ALL),
then enable the desired ID(s). The system will display the following
message:
Warning 1000: Access IDs in addition to the one(s) specified
are still enabled. If you wish to enable ONLY the id(s)
listed, disable all access paths (DISABLE_ACCESS_PATH=ALL),
then enable the ones previously listed.

Note To enable access by more than one host connection, list the
connection names separated by commas and enclosed in parenthesis.
Enabling access by more than one host connection can also be done by
sequential commands.
PARTITION=partition-number
Identifies the unit number for a partition on a container. The partitionnumber identifies the partition associated with the unit number being
added. Use the SHOW container-name command to find the partition
numbers used by a storageset or a single-disk unit.
Note Do not split partitioned units across ports. The subsystem assigns
units 0-99 to Port 1; units 100-199 are assigned to Port 2. Partitioned
units must be on a single port.
Transportable units cannot be partitioned.
MAXIMUM_CACHED_TRANSFER=32 (Default)
MAXIMUM_CACHED_TRANSFER=n
Sets the largest number of write blocks to be cached by the controller.
The controller will not cache any transfers over the specified size.
Accepted write block sizes are 1 through 1024.

B–30

HSG80 User’s Guide

The MAXIMUM_CACHED_TRANSFER switch affects both read and
write-back cache when set on a controller that has read and write-back
caching.
PREFERRED_PATH=OTHER_CONTROLLER
PREFERRED_PATH=THIS_CONTROLLER
NOPREFERRED_PATH (Default)
May be set only when dual-redundant controllers are operating in a
multiple bus failover configuration. In a multiple bus failover
configuration, the host determines which controller the units are
accessed through. The host’s unit-to-controller settings always take
precedence over the preferred path assigned to units with this switch.
The target ID numbers assigned with the SET controller
PORT_1_ALPA= (or PORT_2) command determines which target ID
number the controller uses to respond to the host.
Note If your controllers are configured to operate in transparentfailover mode, do not set the PREFERRED_PATH switch with the
ADD UNIT or SET unit-number command—otherwise, an error
message is displayed. The error message indicates the assignment of a
preferred controller path at the unit level is valid only when operating
in multiple bus failover mode.
When no preferred path is assigned, the unit is targeted through the
controller which detects the unit first after the controllers start.
Select PREFERRED_PATH=THIS_CONTROLLER to instruct “this
controller” to bring the units online.
Select PREFERRED_PATH=OTHER_CONTROLLER to instruct the
“other controller” to bring the units online.
See Chapter 2 for information regarding multiple bus failover.
Tip Subsystem performance is better if target ID numbers are
balanced across the dual-redundant pair.

CLI Commands

B–31

READ_CACHE (Default)
NOREAD_CACHE
Sets the controller’s cache read policy function. Read caching improves
performance in almost all situations. Therefore, it is recommended you
leave its default setting, READ_CACHE enabled. However, under
certain conditions, such as when performing a backup, read caching
may not be necessary since only a small amount of data is cached. In
such instances, it may be beneficial to disable the read cache function
and remove the processing overhead associated with caching data.
READAHEAD_CACHE (Default)
NOREADAHEAD_CACHE
Enables the controller to keep track of read I/Os. If the controller
detects sequential read I/Os from the host, it will then try to keep ahead
of the host by reading the next sequential blocks of data (those the host
has not yet requested) and put the data in cache. This process is
sometimes referred to as prefetch. The controller can detect multiple
sequential I/O requests across multiple units.
Read ahead caching improves host application performance since the
data will be read from the controller cache instead of disk. Read ahead
caching is the default for units.
If you are adding a unit that is not expected to get sequential I/O
requests, select NOREADAHEAD_CACHE for the unit.
RUN (Default)
NORUN
Controls the unit’s availability to the host.
Specify RUN to make a unit available to the host.
Specify NORUN to make a unit unavailable to the host and to cause
any data in cache to be flushed to one or more drives. NORUN spins
down all the disks used in the unit. The drives making up the unit spin
down after the data has been completely flushed.
Note Do not specify the RUN and NORUN switches for partitions.

B–32

HSG80 User’s Guide

WRITE_PROTECT (Default)
NOWRITE_PROTECT
Tells the controller whether data contained on the unit can be
overwritten.
Specify WRITE_PROTECT to prevent the host from writing data to the
unit. However, the controller may still write to a write-protected
RAIDset to complete a reconstruct operation and metadata, reconstruct
data, and copy data may still be written to RAIDsets and mirrorsets.
Specify NOWRITE_PROTECT to allow the host to write data to the
unit. This allows the controller to overwrite existing data.
NOWRITE_PROTECT is the default for transportable disks.
WRITEBACK_CACHE (Default)
NOWRITEBACK_CACHE
Enable or disable the write-back data caching function of the controller.
The controller’s write-back caching feature improves write
performance. WRITEBACK_CACHE is the default on transportable
disks.
Specify WRITEBACK_CACHE for all new RAIDsets, mirrorsets, and
units you want to take advantage of the controller’s write-back caching
feature.
Specify NOWRITEBACK_CACHE for units you want to receive data
directly from the host without being cached.
Caution Though there is built-in redundancy to protect data contained
in cache, allowing data to be written to write-back cache may result in
the loss of data if a catastrophic subsystem failure occurs.

Note The controller may take up to five minutes to flush data
contained within the write-back cache when you specify the
NOWRITEBACK_CACHE switch.

CLI Commands

B–33

Examples
This example shows how to create unit D102 from a single-disk drive
named DISK10000 and sets the host’s access to the unit through “this
controller.”
ADD DISK DISK10000 1 0 0
INITIALIZE DISK10000
ADD UNIT D102 DISK10000 PREFERRED_PATH=THIS_CONTROLLER

This example shows how to create unit D107 from a RAIDset named
RAID9 and instructs the unit to take advantage of the controller’s writeback caching feature.
ADD DISK DISK10100 1 1 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30100 3 1 0
ADD DISK DISK40100 4 1 0
ADD RAIDSET RAID9 DISK10100 DISK20100 DISK30100 DISK40100
INITIALIZE RAID9
ADD UNIT D107 RAID9 WRITEBACK_CACHE

See also
CREATE_PARTITION
DELETE unit-number
SET unit-number
SHOW UNITS

CLI Commands

B–35

CLEAR_ERRORS CLI
Stops the display of current or previous error messages at the CLI
prompt. This command does not clear the error conditions, it only stops
the display of errors at the CLI prompt.
After the cause of the error condition has been corrected, issue the
CLEAR_ERRORS CLI command to clear the error message.
Note There are three message types: info—general information;
warning—user may want to examine, but command will be executed;
and error—command will not execute.

Syntax
CLEAR_ERRORS CLI

Example
To clear the message “All NVPM components initialized to their
default settings” from the CLI prompt, type:
ALL NVPM COMPONENTS INITIALIZED TO THEIR DEFAULT SETTINGS
CLEAR_ERRORS CLI

See also
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLI Commands

B–37

CLEAR_ERRORS controller INVALID_CACHE
Clears an invalid cache error and allows the controller and cache to
resume operation. If the error is due to an incorrectly-mirrored
configuration, the controller indicates mirrored mode status after the
error is cleared.
Use this command for the following situations:

n
n

When the controller or cache modules have been replaced, resulting
in mismatched data between the controllers.
When the controller or cache module is replaced while data is still
in cache and not properly flushed with the SHUTDOWN or SET
NOFAILOVER COPY= commands.

Syntax
CLEAR_ERRORS controller INVALID_CACHE
Spell out INVALID_CACHE when using this command.

Parameters
controller
Identifies which controller is to receive the CLEAR_ERRORS
command. You must specify THIS_CONTROLLER or
OTHER_CONTROLLER.
data-retention-policy
DESTROY_UNFLUSHED_DATA
NODESTROY_UNFLUSHED_DATA (Default)
Instructs the controller on how to handle write-back cached data.
Specify NODESTROY_UNFLUSHED_DATA (default) to retain the cached
data and discard controller information.
Specify DESTROY_UNFLUSHED_DATA to retain the controller
information and discard the cached data.

B–38

HSG80 User’s Guide

Specify NODESTROY_UNFLUSHED_DATA in the following
situations:

n
n

If the controller module has been replaced
If the controller’s nonvolatile memory (NVMEM) has lost its
contents.

Specify DESTROY_UNFLUSHED_DATA in the following situations:

n
n

If the cache module has been replaced
Any other reason not listed above

Caution Specifying the DESTROY_UNFLUSHED_DATA switch
destroys data remaining in cache, which can result in data loss.

Examples
This example shows how to clear an invalid cache error on “this
controller” after you have replaced a controller module. Enter the
command on one line.
CLEAR_ERRORS THIS_CONTROLLER INVALID_CACHE
NODESTROY_UNFLUSHED_DATA

This example shows how to clear an invalid cache error on the “other
controller” after a cache module has been replaced. Enter this command
on the same line. Enter the command on one line.
CLEAR_ERRORS OTHER_CONTROLLER INVALID_CACHE
DESTROY_UNFLUSHED_DATA

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLI Commands

B–39

CLEAR_ERRORS device-name UNKNOWN
If a device failure causes the controller to label the device as unknown,
the controller does not check the device again to see if it has been
repaired or if the error condition has been corrected. You must enter
this command so the controller can recognize the device after the cause
of the error has been corrected.
Use this command to force the controller to recognize a failed device,
regardless of the controller’s prior evaluation of the device’s condition.

Syntax
CLEAR_ERRORS device-name UNKNOWN
Spell out UNKNOWN when using this command.

Parameters
device-name
Identifies the device with the unknown error.

Example
To force the controller to recognize a previously unknown device
named DISK30000, enter this command:
CLEAR_ERRORS DISK30000 UNKNOWN

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLI Commands

B–41

CLEAR_ERRORS unit-number LOST_DATA
Clears lost data errors on a unit; all partitions on the unit’s container are
affected.
The controller reports a lost data error on the unit when you remove a
write-back cache module or when the cache module contains unflushed
data, possibly due to an interruption in the primary power source with
no backup power present. The CLEAR_ERRORS LOST_DATA
command clears the lost data error but does not recover the lost data.
Note Clearing lost data errors or lost data block errors on a RAIDset
causes a reconstruction of all parity blocks. Clearing lost data errors or
lost data block errors on a mirrorset causes members to normalize.

Syntax
CLEAR_ERRORS unit-number LOST_DATA
Spell out LOST_DATA when using this command.
Caution This command may cause data loss.

Parameters
unit-number
Identifies the unit on which the lost data error is to be cleared. The unitnumber is the same name given to the unit when you added it to the
controller’s configuration.

Example
The following command will clear the lost data error on disk unit
number D103:
CLEAR_ERRORS D103 LOST_DATA

B–42

HSG80 User’s Guide

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS UNKNOWN
CLEAR_ERRORS UNWRITEABLE_DATA

CLI Commands

B–43

CLEAR_ERRORS unit-number UNWRITEABLE_DATA
Clears an unwriteable data error on a unit.
It affects all partitions on the same container.
If a storageset or disk drive fails before its data has been written to it, the
controller reports an unwriteable data error. The CLEAR_ERRORS
UNWRITEABLE_DATA command removes the data from the cache and
clears the unwriteable data error.
Caution This command causes data loss.

Syntax
CLEAR_ERRORS unit-number UNWRITEABLE_DATA
Spell out UNWRITEABLE_DATA when using this command.

Parameters
unit-number
Identifies the unit having the unwriteable data error. The unit-number is
the name given to the unit when it was created with the ADD UNIT
command.

Example
Use the following command to clear the unwriteable data error on disk
unit D103:
CLEAR_ERRORS D103 UNWRITEABLE_DATA

See also
CLEAR_ERRORS CLI
CLEAR_ERRORS INVALID_CACHE
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNKNOWN
RETRY_ERRORS UNWRITEABLE_DATA

CLI Commands

B–45

CONFIGURATION RESET
Erases the entire configuration on “this controller,” restores the
controller’s default configuration, and shuts down the controller.
Note If you plan to use this feature, SAVE_CONFIGURATION must
be set when you initialize the container. See “INITIALIZE,” page
B–71.
Specify the CONFIGURATION RESET command on “this controller”
in nofailover mode only. Enter this command to ensure all of the old
configuration information is removed when a controller is moved from
one subsystem to another.
This command disables communication between host and controller.
Enter new configuration information through the SET
THIS_CONTROLLER command or the CONFIGURATION
RESTORE command to make the controller operational.
You can also initiate the CONFIGURATION RESET command from
the controller’s operator control panel (OCP) by holding in port button
5 and pressing the reset button.

Syntax
CONFIGURATION RESET

See also
CONFIGURATION RESTORE
CONFIGURATION SAVE
INITIALIZE

CLI Commands

B–47

CONFIGURATION RESTORE
Copies a controller’s configuration from the disk configuration file into
the controller’s non-volatile memory. This command locates the most
recent configuration file created on disk and restores it. This command
causes a reboot and takes effect immediately.
Use this command for a single controller configuration only. Do not use
it for controllers in a dual-redundant configuration.
You can also initiate the CONFIGURATION RESTORE command
from the controller’s operator control panel (OCP) by holding in port
button 6 and pressing the reset button.
Note The controller must not have devices configured prior to issuing
this command. Use “CONFIGURATION RESET,” page B–45, instead.
f the controller you’re installing was previously used in another
subsystem, it will restart with the configuration that resides in its
nonvolatile memory. If this differs from the subsystem’s current
configuration, you can purge the controller’s old configuration with the
following command:
CONFIGURATION RESET

This will erase the entire configuration on the controller, restore the
controller’s default configuration, and shut down the controller. Press
its reset button to restart the controller after the controller has been
configured (see “Configuring an HSG80 Array Controller,” page 2–3).
Note The INITIALIZE container-name SAVE_CONFIGURATION
must be used to save the controller’s configuration to a disk (see
“SAVE_CONFIGURATION,” page B–73), in order to reset the
configuration (see “CONFIGURATION RESET,” page B–45) or to
restore the configuration (see “CONFIGURATION RESTORE,” page
B–47).

Syntax
CONFIGURATION RESTORE

B–48

HSG80 User’s Guide

See also
CONFIGURATION RESET
CONFIGURATION SAVE
INITIALIZE

CLI Commands

B–49

CONFIGURATION SAVE
Forces a current copy of configuration information in a controller’s
non-volatile memory into a configuration file on a disk. This allows the
user to determine when a copy of the configuration is saved. Use this
command to explicitly save a single controller’s configuration. The
command takes effect immediately. In a dual-redundant configuration,
issue this command to both controllers.
Use the INITIALIZE container-name SAVE_CONFIGURATION
command to set up the location of the configuration file on disk.

Syntax
CONFIGURATION SAVE

See also
CONFIGURATION RESET
CONFIGURATION RESTORE
INITIALIZE

CLI Commands

B–51

CREATE_PARTITION
Divides a non-transportable disk drive storageset into several,
separately-addressable storage units. The command marks a specified
percentage of a disk drive or storageset to be used as a separately
addressable unit. You can divide any nontransportable disk or
storageset into a maximum of eight partitions. Each partition can be
separately presented to the host. Partitions are not supported in multiple
bus failover mode. Initialize disks and storagesets before creating
partitions.
Note Partitioned units cannot function in multiple bus failover dualredundant configurations. Because they are not supported, you must
delete your partitions before configuring the controllers for multiple
bus failover.
After you partition a container, you must initialize it in order to destroy
the partitions.

Syntax
CREATE_PARTITION container-name SIZE=percent

Parameters
container-name
Identifies the disk or storageset to partition. This is the same name
given to the disk or storageset when it was created with the ADD
command (for example, ADD DISK, ADD STRIPESET, and so forth).
Any disk, stripeset, mirrorset, striped mirrorset, or RAIDset can be
partitioned. A transportable disk cannot be partitioned. You must
initialize the container before creating the first partition.
SIZE=percent
SIZE=LARGEST
Specifies the size of the partition to be created as a percentage of the
total container’s storageset size.
To create a partition, specify a percentage of the container’s total
capacity. The entire container is then divided into segments equal to the
percentage specified. For example, if SIZE=20, the container is divided
into five (1.0/0.2=5) equal segments. The resulting partition is slightly

B–52

HSG80 User’s Guide

smaller than the size specified because metadata also occupies some of
the partition’s allocated space.
Specify LARGEST in the following situations:

n
n

To have the controller create the largest partition possible from
unused space on the disk or storageset.
To create the last partition on a container. Because the remaining
space is not equal to an exact percentage value, specifying
LARGEST allows you to optimize use of the remaining space.

CAPACITY=
CYLINDERS=
HEADS=
SECTORS_PER_TRACK=
CAPACITY may be specified 1 to the maximum container size (in
blocks); CYLINDERS may be specified 1 to16,777,215; HEADS may
be specified 1 to 255; and SECTORS_PER_TRACK may be specified
1 to 255.
Note These are used to set the SCSI parameters reported to the host.
They should not be used unless there is a compatibility problem with
the existing defaults.
The geometry parameter switches for the INITIALIZE command are
ignored when you create partitions. The parameters supplied with the
CREATE_PARTITION command are used by the unit.

CLI Commands

B–53

Example
This example shows how to create a RAIDset named RAID9 and divide
it into four equal parts. It also creates host-addressable units for each
partition.
ADD DISK DISK10000 1 0 0
ADD DISK DISK20100 2 1 0
ADD DISK DISK30200 3 2 0
ADD RAIDSET RAID9 DISK10000 DISK20100 DISK30200
INITIALIZE RAID9
CREATE_PARTITION RAID9 SIZE=25
CREATE_PARTITION RAID9 SIZE=25
CREATE_PARTITION RAID9 SIZE=25
CREATE_PARTITOIN RAID9 SIZE=LARGEST
ADD UNIT D101 RAID9 PARTITION=1
ADD UNIT D102 RAID9 PARTITION=2
ADD UNIT D103 RAID9 PARTITION=3
ADD UNIT D104 RAID9 PARTITION=4

See also
ADD UNIT
DELETE unit-number
DESTROY PARTITION
SHOW

CLI Commands

B–55

DELETE connections
Deletes a host connection entry from the table of known connections.
This command deletes a specified connection from the table of known
connections maintained by the controller.
The table of known host connections is maintained in the controllers
NVRAM. Once a connection is added to the table, it stays there, even
if the physical connection between host adapter and controller port is
severed. The only way to remove a connection from the table is
through the DELETE connections command.
DELETE connections removes the connection from the table whether
or not the host adapter is still physically connected to a controlled port.
Note A connection that has access path explicity enabled on a unit
cannot be deleted. Access path is enabled through the ADD UNIT or
SET UNIT commands. If access path is generically enabled for all
connections (ENABLE_ACCESS_PATH= ALL), then any or all
connections can be deleted.

Syntax
DELETE connection name

Parameters
connection name
The name given to the host connection. The connection name is one of
the following:

n
n
n

The default name assigned to the host connection when it was
physically connected to the controller port. Default names are of
the form !NEWCONnn.
The name given through the RENAME command.
The name given through the ADD CONNECTIONS command.

B–56

HSG80 User’s Guide

Examples
Deletes the host connection Server1 from the table of known
connections (unless the access path to Server1 is specifically enabled
for one or more unit.)
CLI> DELETE SERVER1

See also
ADD CONNECTIONS
ADD UNIT
SET connection-name
SET unit-number

CLI Commands

B–57

DELETE container-name
Deletes a container belonging to the controller’s configuration. You
cannot delete a container in use by a higher-level container. For
example, you cannot delete a disk belonging to a RAIDset, or a
RAIDset belonging to a unit; you must first delete the higher-level
container or containers.
Note This command does not delete sparesets or failedsets. You cannot
delete spareset and failedset containers. See the DELETE FAILEDSET
and DELETE SPARESET commands for details.
When a storageset is deleted, the individual disks are free to be used by
another container. If you create the container again with the exact same
disk configuration, and none of the disks have been used for anything,
or initialized, then the container can be reassembled using its original
disks.

Syntax
DELETE container-name

Parameters
container-name
Identifies the container to be deleted. This is the name given to the
container when it was created using the ADD command (for example,
ADD DISK, ADD STRIPESET, and so forth).

Examples
To delete a disk drive named DISK10000, type:
DELETE DISK10000

To delete a stripeset named STRIPE1, enter:
DELETE STRIPE1

To delete a RAIDset named RAID9, use:
DELETE RAID9

B–58

HSG80 User’s Guide

See also
DELETE FAILEDSET
DELETE SPARESET
UNMIRROR

CLI Commands

B–59

DELETE FAILEDSET
Removes a disk drive from the failedset. The failedset contains disk
drives removed by the controller from RAIDsets and mirrorsets because
they failed or were manually removed using the SET command. Enter
the DELETE FAILEDSET command before physically removing failed
disks from the storage shelf for testing, repair, or replacement.
You should consider all disk drives in the failedset defective. Repair or
replace disks found in the failedset.

Syntax
DELETE FAILEDSET disk-name

Parameter
disk-name
Identifies the disk you want to delete from the failedset. Only one disk
at a time can be removed from a failedset.

Example
To delete DISK20200 from the failedset, use the following command:
DELETE FAILEDSET DISK20200

See also
DELETE container-name
DELETE SPARESET
SET FAILEDSET
SHOW FAILEDSET

CLI Commands

B–61

DELETE SPARESET
Removes a disk drive from the spareset.

Syntax
DELETE SPARESET disk-name

Parameter
disk-name
Identifies the disk drive being deleted from the spareset. Remove only
one disk at a time from a spareset.

Example
This command will remove DISK20300 from the spareset:
DELETE SPARESET DISK20300

See also
DELETE container-name
DELETE FAILEDSET
ADD SPARESET
SHOW SPARESET

CLI Commands

B–63

DELETE unit-number
Deletes a logical unit from the controller configuration. The host cannot
address deleted units. If the unit’s write-back caching feature is
enabled, the controller flushes the cached data to the unit’s devices
before deleting the unit.
Before using the DELETE unit-number command, clear any errors with
the CLEAR_ERRORS UNWRITEABLE_DATA or CLEAR_ERRORS
LOST_DATA commands.

Syntax
DELETE unit-number

Parameter
unit-number
Identifies the unit number to be deleted. The unit-number is the same
name given to the unit when it was created using the ADD UNIT
command.

Example
To delete disk unit number D103, enter:
DELETE D103

See also
ADD UNIT
CLEAR_ERRORS LOST_DATA
CLEAR_ERRORS UNWRITEABLE_DATA
DESTROY_PARTITION

CLI Commands

B–65

DESTROY_PARTITION
Marks the area reserved for a partition as available. The freed area is
then consolidated with any adjacent free areas.
Caution Data contained on a partition is lost when you enter the
DESTROY_PARTITION command.
You cannot destroy a partition that has been assigned a unit number.
First enter the DELETE unit-number command to delete the unit using
the partition.
After you partition a container, you must initialize it in order to destroy
the partitions.

Syntax
DESTROY_PARTITION container-name PARTITION=partitionnumber

Parameters
container-name
Identifies the disk or storageset containing the partition to be destroyed.
This is the name given to the container when it was created using the
ADD command (for example, ADD DISK, ADD STRIPESET, and so
forth).
partition-number
Identifies the partition to be destroyed. Use the SHOW container-name
command to identify the correct partition before carrying out the
DESTROY_PARTITION command.

Example
The following example shows how to delete the unit for partition 2 on
RAIDset RAID9 and destroy the partition:
DELETE D102
DESTROY_PARTITION RAID9 PARTITION=2

B–66

HSG80 User’s Guide

See also
ADD DISK
ADD STORAGESET
ADD STRIPESET
CREATE_PARTITION
DELETE unit-number
SHOW

CLI Commands

B–67

DIRECTORY
Lists the diagnostics and utilities available on “this controller.”

Syntax
DIRECTORY

Example
The example below shows how to display a directory listing:
DIRECTORY

HSUTIL

V82G

CHVSN

V82G

CLCP

V82G

CLONE

V82G

CONFIG

V82G

DILX

V82G

DIRECT

V82G

DSTAT

V82G

FRUTIL

V82G

FMU

V82G

VTDPY

V82G

Note CHVSN and DSTAT are not user utilities. They should be used
by DIGITAL authorized service personnel only.

See also
SHOW UNITS
SHOW unit-number

CLI Commands

B–143

SHOW
Displays information about controllers, storagesets, devices, partitions,
and units.
The SHOW command may not display some information for devices
accessed through the companion controller in a dual-redundant
configuration. When information regarding a device or parameter does
not appear, enter the same SHOW command from a terminal on the
other controller.

Syntax
SHOW connection
SHOW controller
SHOW device-name
SHOW device-type
SHOW EMU
SHOW storageset-name
SHOW storageset-type
SHOW unit-number
SHOW UNITS

Parameters
connection
Shows the following connection information: connection name,
operating system, controller, controller port, adapter ID address, online
or offline status, and unit offset.
controller
Specifies the controller to be displayed.
THIS_CONTROLLER
OTHER_CONTROLLER
device-name
Specifies the name of a particular device to be displayed. For example,
SHOW DISK20100 displays information about the device named
DISK20100.

B–144

HSG80 User’s Guide

device-type
Specifies the type of devices you want to be displayed. Valid choices
are:

n
n

DEVICES—Shows all devices attached to the controller
DISKS—Shows all disks attached to the controller

EMU
Displays information regarding the status of the environmental monitoring
unit (EMU).
storageset-name
Specifies the name of a particular storageset to be displayed. For
example, SHOW STRIPE1 displays information about the stripeset
named STRIPE1.
storageset-type
Specifies the type of storageset to be displayed. Valid types are:

n
n
n
n
n
n

FAILEDSET—Shows the failedset configured to the controller.
MIRRORSETS—Shows all mirrorsets configured to the controller.
RAIDSETS—Shows all RAIDsets configured to the controller.
SPARESET—Show the spareset configured to the controller.
STORAGESETS—Shows all storagesets configured with the
controller.
STRIPESETS—Shows all stripesets configured to the controller.

unit-number
Specifies the name of a particular unit to be displayed. For example,
SHOW D102 displays information about the unit named D102.
UNITS
Displays information for all units configured to the controller.
In addition to the unit name you defined for the unit, the information
includes the unique 128-bit subsystem unit ID. This ID consists of the
controller node ID plus a 64-bit unit ID generated by the subsystem.
You name the units, however, the subsystem identifies them internally
using this identifier.
A unit on controller 1234 5678 9ABC EF00 would have an ID like the
following:

CLI Commands

B–145

1234 5678 9ABC EF00 0001 0001 3056 00D2

Each single disk unit or storage device in your subsystem is assigned a
unique unit ID number. The controller constructs a unit ID number for
each device you add to the subsystem. The ID number consists of the
controller’s worldwide node ID and a unique, internally generated
serial stamp. You cannot set or change unit ID numbers.
Unit ID numbers stay with the unit when you move the unit from one
slot to another in the enclosure.

Switches
FULL
Displays additional information about each device, storageset, or
controller.

Examples
This example shows how to display a listing of disks:
SHOW DISKS
Name
Type
Port Targ Lun
Used by
----------------------------------------------------------DISK20300
DISK10100

disk
disk

100 D100
1 1 0

D101

This example shows a full listing of devices attached to the controller:
SHOW DEVICES FULL
Name

Type

Port Targ

Lun

Used by

-----------------------------------------------------------------------------DISK10300 disk
1
3 0
R0
Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8378028 blocks
DISK20100
disk

01 0

Switches:
NOTRANSPORTABLE
TRANSFER_RATE_REQUESTED = ASYNCHRONOUS (ASYNCHRONOUS negotiated)
Size: 8377528 blocks
Configuration being backed up on this container

B–146

HSG80 User’s Guide

This example shows how to display a complete listing of the mirrorset
named MIRR1:
SHOW MIRR1
Name

Storageset

Uses

Used by

-----------------------------------------------------------------------------MIRR1
mirrorset
DISK50300
S0
DISK60300
Switches:
POLICY (for replacement) = BEST_PERFORMANCE
COPY (priority) = NORMAL
READ_SOURCE = LEAST_BUSY
MEMBERSHIP = 2, 2 members present
State:
NORMAL
DISK60300 (member
DISK50300 (member

0) is NORMAL
1) is NORMAL

Size: 17769177 blocks

This example shows the full information for a controller:
SHOW THIS_CONTROLLER FULL
Controller:
HSG80 (C) DEC ZG74100120 Software R052G-0, Hardware 0000
NODE_ID = 5000-1FE1-FF00-00B0
ALLOCATION_CLASS = 0SCSI_VERSION = SCSI-2
Not configured for dual-redundancy
Device Port SCSI address 7
TIME: NOT SET
Host PORT_1:
Reported PORT_ID = 5000-1FE1-FF00-00B1
PORT_1_PROFILE = PLDA
PORT_1_TOPOLOGY = LOOP_SOFT (loop up)
PORT_1_AL_PA = 01 (negotiated)
Host PORT_2:
Reported PORT_ID = 5000-1FE1-FF00-00B2
PORT_2_PROFILE = PLDA
PORT_2_TOPOLOGY = LOOP_SOFT (loop up)
PORT_2_AL_PA = 02 (negotiated)
Cache:
256 megabyte write cache, version 0012
Cache is GOOD
No unflushed data in cache
CACHE_FLUSH_TIMER = DEFAULT (10 seconds)
NOCACHE_UPS
Mirrored Cache:
Not enabled
Battery:
MORE THAN 50% CHARGED
Standby capacity: Less than one hour
Time to full charge: 31 hours
Expires: 23-AUG-1957
WARNING: BATTERY AT END OF LIFE WITHIN ONE WEEK, REPLACE BATTERY SOON!

CLI Commands

B–147

Extended information:
Terminal speed 19200 baud, eight bit, no parity, 1 stop bit
Operation control: 00000001 Security state code: 33506
Configuration backup disabled
Other controller not responding - RESET signal NOT asserted - NINDY ON Temperature
within optimum limit.

This example shows how to display the current settings for the EMU:
SHOW EMU
EMU CABINET SETTINGS
SENSOR_1_SETPOINT
SENSOR_2_SETPOINT

35
35

DEGREES C
DEGREES C

SENSOR_3_SETPOINT
FANSPEED AUTOMATIC

DEGREES C

CLI Commands

B–149

SHUTDOWN controller
Flushes all user data from the specified controller’s write-back cache (if
present) and shuts down the controller. The controller does not
automatically restart. All units accessed through the failed controller
failover to the surviving controller.

Syntax
SHUTDOWN controller

Parameter
controller
Indicates which controller is to shut down. Specify
OTHER_CONTROLLER or THIS_CONTROLLER.

Switches
IGNORE_ERRORS
NOIGNORE_ERRORS (Default)
Controls the reaction of the controller based on the status of write-back
cache.
Caution The IGNORE_ERRORS switch causes the controller to keep
unflushed data in the write-back cache until it restarts and is able to
write the data to devices. Do not perform any hardware changes until
the controller flushes the cache.
Specify IGNORE_ERRORS to instruct the controller to shutdown even
if the data within write-back cache cannot be written to the devices.
Specify NOIGNORE_ERRORS to instruct the controller to stop
operation if the data within write-back cache cannot be written to the
devices.
IMMEDIATE_SHUTDOWN
NOIMMEDIATE_SHUTDOWN (Default)
Instructs the controller when to shutdown.

B–150

HSG80 User’s Guide

Caution The IMMEDIATE_SHUTDOWN switch causes the
controller to keep unflushed data in the write-back cache until it restarts
and is able to write the data to devices. Do not perform any hardware
changes until the controller flushes the cache.
Specify IMMEDIATE_SHUTDOWN to cause the controller to
shutdown immediately without checking for online devices or before
flushing data from the write-back cache to devices.
Specify NOIMMEDIATE_SHUTDOWN to cause the controller not to
shutdown without checking for online devices or before all data has
been flushed from the write-back cache to devices.

Examples
This example shows how to shut down “this controller:”
SHUTDOWN THIS_CONTROLLER

This example shows how to shut down the other controller, even if it
cannot write all of the write-back cached data to the units:
SHUTDOWN OTHER_CONTROLLER IGNORE_ERRORS

See also
RESTART controller
SELFTEST controller

CLI Commands

B–151

UNMIRROR
Converts a one-member mirrorset back to a non-mirrored disk drive and
deletes its mirrorset from the list of known mirrorsets. This command
can be used on mirrorsets already members of higher-level containers
(stripesets or units).
The UNMIRROR command is not valid for disk drives having a
capacity greater than the capacity of the existing mirrorset. If a
mirrorset is comprised of disk drives with different capacities, the
mirrorset capacity is limited to the size of the smallest member; larger
members contain unused capacity. If a member with unused capacity is
the last remaining member of a mirrorset, the UNMIRROR command
cannot be used to change the disk drive back to a single-disk unit. This
change would cause a change in the reported disk capacity, possibly
corrupting user data.

Syntax
UNMIRROR disk-name

Parameter
disk-name
Specifies the name of the normal mirrorset member to be removed from
a mirror storageset.

Example
This example shows how to convert DISK10300 back to a single
device:
UNMIRROR DISK10300

See also
ADD MIRRORSET
MIRROR
REDUCE
RUN CLONE
SET mirrorset-name

C–1

APPENDIX

LED Codes

This appendix shows and describes the LED codes that you may encounter while
servicing the controller, cache module, and external cache battery.

C–2

HSG80 User’s Guide

Operator Control Panel LED Codes
Use Table C–1 to interpret solid OCP patterns and Table C–2 to
identify flashing OCP patterns. Note that in the ERROR column of
Table C-1, there are two separate descriptions. The first denotes the
actual error message that appears on your terminal, and the second
provides a more detailed explanation of the designated error. Use this
legend for both tables:
■

= reset button on
❏ = reset button off
● = LED on
❍ = LED off
Note If the reset button is flashing and an LED is lit continuously,
either the devices on that LED’s bus don’t match the controller’s
configuration, or an error has occurred in one of the devices on that bus.
Also, a single LED that is lit indicates a failure of the drive on that port.

LED Codes

C–3

Solid OCP Patterns
Table C–1

Solid OCP Patterns

Pattern

OCP
Code

■● ● ● ●● ●

Error

Repair Action

DAEMON diagnostic failed hard
in non-fault tolerant mode

Verify that cache module is present. If
the error persists, replace controller.

DAEMON diagnostic detected
critical hardware component
failure; controller can no longer
operate
■● ● ● ●❍ ●

NVPM structure revision greater
than image’s

Replace program card with one that
contains the latest software version

NVPM structure revision number
is greater than the one that can be
handled by the software version
attempting to be executed
■● ● ● ●❍ ❍

NVPM write loop hang

Replace controller

Attempt to write data to NVPM
failed
■● ● ● ❍● ●

NVPM read loop hang

Replace controller

Attempt to read data from NVPM
failed
■● ● ● ❍● ❍

An unexpected NMI occurred
during Last Failure processing

Reset controller

Last Failure processing interrupted
by a Non-Maskable Interrupt
(NMI)
■● ● ● ❍❍●

NVPM configuration inconsistent
Device configuration within the
NVPM is inconsistent

Reset controller

C–4

HSG80 User’s Guide

Table C–1

Solid OCP Patterns (Continued)

Pattern

OCP
Code

Error

■● ● ● ❍❍❍

Controller operation terminated

Repair Action
Reset controller

Last Failure event required
termination of controller operation
(e.g. SHUT DOWN VIA CLI)
■● ● ❍● ● ●

Software-induced controller reset
expected

Replace controller

Software-induced reset failed
■● ● ❍● ● ❍

Hardware-induced controller reset
expected

Replace controller

Automatic hardware reset failed
■● ● ❍● ❍●

An unexpected bugcheck occurred
during Last Failure processing

Reset controller

Last Failure Processing interrupted
by another Last Failure event
■● ● ❍❍ ●●

NVPM structure revision too low
NVPM structure revision number
is less than the one that can be
handled by the software version
attempting to be executed

■● ● ❍❍ ●❍

Code load program card write
failure

Verify that the program card contains
the latest software version. If the error
persists, replace controller.

Replace card

Attempt to update program card
failed
■● ● ❍❍ ❍●

ILF$INIT unable to allocate
memory
Attempt to allocate memory by
ILF$INIT failed

Replace controller

LED Codes

Table C–1

C–5

Solid OCP Patterns (Continued)

Pattern

OCP
Code

■● ● ❍❍ ❍❍

Error

Repair Action

An unexpected bugcheck occurred
before subsystem initialization
completed

Reinsert controller. If that does not
correct the problem, reset the controller.
If the error persists, try resetting the
controller again, and replace it if no
change occurs.

An unexpected Last Failure
occurred during initialization
■● ❍ ●● ● ●

Memory module has illegal
DIMM configuration

Verify that DIMMs are installed as
shown in Figure 1-3 on page 1-7.

■● ❍ ●● ● ❍

Multiple cabinets have the same
SCSI ID

Reconfigure PVA ID to uniquelyidentify each cabinet in the subsystem.
The cabinet with the controllers must
be set to
PVA ID 0; additional cabinets must use
PVA IDs 2 and 3. If error continues
after PVA settings are unique, replace
each PVA module one at a time. Check
cabinet if problem remains.

More than one cabinet have the
same SCSI ID

■● ❍ ●● ❍●

All master cabinet SCSI buses are
not set to ID 0

Set PVA ID to 0 for the cabinet with the
controllers. If problem persists, try the
following repair actions:
1. Replace the PVA module
2. Replace the EMU
3. Remove all devices
4. Replace the cabinet

■● ❍ ●● ❍❍

Cabinet IO termination power out
of range

Ensure that all of the cabinet’s device
SCSI buses have an I/O module. If
problem persists, replace the failed I/O
module.

Faulty or missing IO module
causes cabinet IO termination
power to be out of range
■● ❍ ●❍ ●●

Jumpers not terminators found on
backplane
One or more SCSI bus terminators
are either missing from the
backplane or broken

Ensure that cabinet’s SCSI bus
terminators are installed and that there
are no jumpers. Replace the failed
terminator if the problem continues.

C–6

HSG80 User’s Guide

Table C–1

Solid OCP Patterns (Continued)

Pattern

OCP
Code

■● ❍ ●❍ ●❍

Error
All cabinet IO modules are not of
the same type
Cabinet I/O modules are a
combination of single-sided and
differential

■● ❍ ●❍ ❍●

EMU protocol version
incompatible
The microcode in the EMU and
the software in the controller are
not compatible

■● ❍ ●❍ ❍❍

An unexpected Machine Fault/
NMI occurred during Last Failure
processing

Repair Action
Ensure that the I/O modules in an
extended subsystem are either all
single-ended or all differential, not
both.

Upgrade either the EMU microcode or
the software (refer to the Release Notes
that accompanied the controller’s
software).

Reset the controller

A machine fault was detected
while a Non-Maskable Interrupt
was processing
■● ❍ ❍● ●●

Memory module has insufficient
usable memory

Replace indicated DIMM(s)
(this indication is only provided when
Fault LED logging is enabled).

■● ❍ ❍● ●❍

Indicated memory module is
missing

Insert memory module (cache board)

Controller is unable to detect a
particular memory module

LED Codes

Table C–1

C–7

Solid OCP Patterns (Continued)

Pattern

OCP
Code

■● ❍ ❍● ❍●

Error
Recursive Bugcheck detected
The same bugcheck has occurred
three times within ten minutes, and
controller operation has
terminated.

■❍❍ ❍❍❍❍

No program card detected or kill
asserted by other controller
Controller unable to read program
card

❏❍❍ ❍❍❍❍

Catastrophic controller or power
failure

Repair Action
Reset the controller. If this fault pattern
is displayed repeatedly, follow the
repair action(s) associated with the Last
Failure code that is repeatedly
terminating controller execution.
Ensure that program card is properly
seated while resetting the controller. If
the error persists, try the card with
another controller; or replace the card.
Otherwise, replace the controller that
reported the error.
Check power. If good, reset controller.
If problem persists, reseat controller
module and reset controller. If problem
is still evident, replace controller
module.

C–8

HSG80 User’s Guide

Flashing OCP Patterns
Table C–2

Flashing OCP Patterns
OCP
Code

Pattern

Error

Repair Action

■ ❍❍ ❍❍ ❍●

Program card EDC error

Replace program card

■ ❍❍ ❍● ❍❍

Timer zero on the processor is bad

Replace controller

■ ❍❍ ❍● ❍●

Timer one on the processor is bad

Replace controller

■ ❍❍ ❍● ● ❍

Processor Guarded Memory Unit
(GMU) is bad

Replace controller

■ ❍❍ ●❍ ● ●

Nonvolatile Journal Memory (JSRAM) First, verify correct upgrade (see
Release Notes). If error
structure is bad because of a memory
error or an incorrect upgrade procedure continues, replace controller

■ ❍❍ ●● ❍ ●

One or more bits in the diagnostic
registers did not match the expected
reset value

Press the reset button to restart
the controller. If this does not
correct the error, replace the
controller

■ ❍❍ ●● ● ❍

Memory error in the JSRAM

Replace controller

■ ❍❍ ●● ● ●

Wrong image found on program card

Replace program card or replace
controller if needed

■ ❍● ❍❍ ❍❍

Controller Module memory is bad

Replace controller

■ ❍● ❍❍ ● ❍

Controller Module memory addressing
is malfunctioning

Replace controller

■ ❍● ❍❍ ● ●

Controller Module memory parity is not Replace controller
working

■ ❍● ❍● ❍ ❍

Controller Module memory controller
timer has failed

Replace controller

■ ❍● ● ❍❍ ●

The Controller Module memory
controller interrupt handler has failed

Replace controller

■ ❍● ● ●● ❍

During the diagnostic memory test, the
Controller Module memory controller
caused an unexpected Non-Maskable
Interrupt (NMI)

Replace controller

■ ● ❍❍● ❍ ❍

The card’s code image changed when
the contents were copied to memory

Replace controller

LED Codes

Table C–2

Flashing OCP Patterns (Continued)

Pattern

OCP
Code

Error

Repair Action

■ ● ●❍ ❍❍ ❍

The JSRAM battery is bad

Replace controller

■ ● ●❍ ❍● ❍

First-half diagnostics of the Time of
Year Clock failed

Replace controller

■ ● ●❍ ❍● ●

Second-half diagnostics of the Time of
Year Clock failed

Replace controller

■ ● ●❍ ●❍ ●

The processor bus-to-device bus bridge Replace controller
chip is bad

■ ● ●● ❍● ●

There is an unnecessary interrupt
pending

Replace controller

■ ● ●● ● ❍❍

There was an unexpected fault during
initialization

Replace controller

■ ● ●● ● ❍●

There was an unexpected maskable
interrupt during initialization

Replace controller

■ ● ●● ● ●❍

There was an unexpected NMI during
initialization

Replace controller

■ ● ●● ● ●●

An invalid process ran during
initialization

Replace controller

C–9

D–1

APPENDIX

Event Reporting: Templates and Codes

This appendix describes the event codes that the fault-management software
generates for spontaneous events and last-failure events.
The HSG80 controller uses various codes to report different types of events, and
these codes are presented in template displays. Instance Codes are unique codes
that identify events, ASC and ASCQ codes explain the cause of the events, and Last
Failure codes describe unrecoverable conditions that may occur with the controller.

D–2

HSG80 User’s Guide

Passthrough Device Reset Event Sense Data Response
Events reported by passthrough devices during host/device operations
are conveyed directly to the host system without intervention or
interpretation by the HSG80controller, with the exception of device
sense data that is truncated to 160 bytes when it exceeds 160 bytes.
Events related to pass-through device recognition, initialization, and
SCSI bus communication events that result in a reset of a pass-through
device by the HSG80 controller are reported using standard SCSI Sense
Data, as shown in Figure D–1. For all other events, refer to the
templates to follow.

n
n

Figure D–1

off

bit
0

Pass-through Device Reset Event Sense Data
Response Format
7

Valid

1
2

Segment
FM

EOM

ILI

Sense Key

3-6

Rsvd
Information

Additional Sense Length

8-11

Instance Code

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

14
15
16

Error Code

Field Replaceable Unit Code
SKSV
Sense Key Specific

17
CXO-5093A-MC

Event Reporting: Templates and Codes

D–3

Last Failure Event Sense Data Response
Unrecoverable conditions detected by either software or hardware and
certain operator-initiated conditions result in the termination of HSG80
controller operation. In most cases, following such a termination, the
controller will attempt to restart (that is, reboot) with hardware
components and software data structures initialized to the states
necessary to perform normal operations (see Figure D–2).

n
n
n

Instance Codes (byte offset 32-35) are described in Table D–1,
“Instance Codes” on page D–18.
ASC and ASCQ codes (byte offsets 12 and 13) are described in
Table D–7, “ASC and ASCQ Codes” on page D–85.
Last Failure Codes (byte offset 104-107) are described in Table
D–3, “Last Failure Codes” on page D–38.

D–4

HSG80 User’s Guide

Figure D–2
off

bit
0

Template 01 - Last Failure Event Sense Data Response
Format
7

Unusd

1
2

Error Code
Unused
Sense Key

Unused

3-6

Unused

Additional Sense Length

8-11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–31

Reserved

32-35

Instance Code

Template

Template Flags

38–53

Reserved

54–69

Controller Board Serial Number

70–73

Controller Software Revision Level

74–75

Reserved

LUN Status

77–103

Reserved

104-107

Last Failure Code

108–111

Last Failure Parameter[0]

112–115

Last Failure Parameter[1]

116–119

Last Failure Parameter[2]

120–123

Last Failure Parameter[3]

124–127

Last Failure Parameter[4]

128–131

Last Failure Parameter[5]

132–135

Last Failure Parameter[6]

136–139

Last Failure Parameter[7]

140-159

Reserved
CXO6175A

Event Reporting: Templates and Codes

D–5

Multiple-Bus Failover Event Sense Data Response
The HSG80 SCSI Host Interconnect Services software component
reports Multiple Bus Failover events via the Multiple Bus Failover
Event Sense Data Response (see Figure D–3).

n
n

Figure D–3
off

bit
0

Template 04 - Multiple-Bus Failover Event Sense Data
Response Format
7

Unusd

1
2

Unused
Unused

Sense Key

3-6

Unused

Additional Sense Length

8-11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–26

Reserved

Failed Controller Target Number

28–31

Affected LUNs

32–35

Instance Code

Template

Template Flags

38–53

Other Controller Board Serial Number

54–69

Controller Board Serial Number

70–73

Controller Firmware Revision Level

74-75

Reserved
LUN Status

Error Code

77–103

Reserved

104-131

Affected LUNs Extension (TM0)

132-159

Reserved
CXO5314B

D–6

HSG80 User’s Guide

Failover Event Sense Data Response
The HSG80 controller Failover Control software component reports
errors and other conditions encountered during redundant controller
communications and failover operation via the Failover Event Sense
Data Response (see Figure D–4).

n
n
n

Event Reporting: Templates and Codes

Figure D–4
off

bit
0

Template 05 - Failover Event Sense Data Response
Format
7

Unusd

Error Code

1
2

D–7

Unused
Unused

Sense Key

3–6

Unused

Additional Sense Length

8–11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–31

Reserved

32–35

Instance Code

Template

Template Flags

38–53

Reserved

54–69

Controller Board Serial Number

70–73

Controller Software Revision Level

74–75

Reserved

LUN Status

77-103

Reserved

104–107

Last Failure Code

108–111

Last Failure Parameter[0]

112–115

Last Failure Parameter[1]

116–119

Last Failure Parameter[2]

120–123

Last Failure Parameter[3]

124–127

Last Failure Parameter[4]

128–131

Last Failure Parameter[5]

132–135

Last Failure Parameter[6]

136–139

Last Failure Parameter[7]

140–159

Reserved
CXO6177A

D–8

HSG80 User’s Guide

Nonvolatile Parameter Memory Component Event Sense Data Response
The HSG80 controller Executive software component reports errors
detected while accessing a Nonvolatile Parameter Memory Component
via the Nonvolatile Parameter Memory Component Event Sense Data
Response (see Figure D–5).

n
n

Figure D–5
off

bit
0

Template 11 - Nonvolatile Parameter Memory
Component Event Sense Data Response Format
7

Unusd

1
2

Error Code
Unused
Unused

Sense Key

3-6

Unused

Additional Sense Length

8-11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–31

Reserved

32-35

Instance Code

Template

Template Flags

38–53

Reserved

54–69

Controller Board Serial Number

70–73

Controller Software Revision Level

74–75

Reserved

LUN Status

77-103

Reserved

104–107

Memory Address

108–111

Byte Count

112–114

Number of Times Written

115

Undefined

116–159

Reserved
CXO6178A

Event Reporting: Templates and Codes

D–9

Backup Battery Failure Event Sense Data Response
The HSG80 controller Value Added Services software component
reports backup battery failure conditions for the various hardware
components that use a battery to maintain state during power failures
via the Backup Battery Failure Event Sense Data Response (see Figure
D–6).

n
n

Figure D–6
off

bit
0

Template 12 - Backup Battery Failure Event Sense
Data Response Format
7

Unusd

1
2

Error Code
Unused
Unused

Sense Key

3-6

Unused

Additional Sense Length

8-11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–31

Reserved

32-35

Instance Code

Template

Template Flags

38–53

Reserved

54–69

Controller Board Serial Number

70–73

Controller Software Revision Level

74-75

Reserved

LUN Status

77–103

Reserved

104–107

Memory Address

108–159

Reserved
CXO6179A

n
n

For more information on Instance Codes, see page D–16.
For a table of ASC and ASCQ codes, see page D–85.

D–10

HSG80 User’s Guide

Subsystem Built-In Self Test Failure Event Sense Data Response
The HSG80 controller Subsystem Built-In Self Tests software
component reports errors detected during test execution via the
Subsystem Built-In Self Test Failure Event Sense Data Response (see
Figure D–7).

n
n

Event Reporting: Templates and Codes

Figure D–7
off

D–11

Template 13 - Subsystem Built-In Self Test Failure
Event Sense Data Response Format
bit

Unusd

1
2

Error Code
Unused
Unused

Sense Key

3-6

Unused

Additional Sense Length

8-11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–31

Reserved

32-35

Instance Code

Template

Template Flags

38–53

Reserved

54–69

Controller Board Serial Number

70–73

Controller Software Revision Level

74–75

Reserved

LUN Status

77-103

Reserved

104–105

Undefined

106

Header Type

107

Header Flags

108

109

Test Number

110

Test Command

111

Test Flags

112–113

Error Code

114–115

Return Code

116–119

Address of Error

120–123

Expected Error Data

124–127

Actual Error Data

128–131

Extra Status 1

132–135

Extra Status 2

136–139

Extra Status 3

140-159

Reserved
CXO6180A

D–12

HSG80 User’s Guide

Memory System Failure Event Sense Data Response
The HSG80 controller Memory Controller Event Analyzer software
component and the Cache Manager, part of the Value Added software
component, report the occurrence of memory errors via the Memory
System Failure Event Sense Data Response (see Figure D–8).

n
n

Figure D–8 Template 14 - Memory System Failure Event Sense Data Response Format
off

bit
0

Unusd

1
2

Error Code

Unused
Unused

Sense Key

off

74-75

bit

4
3
Reserved

LUN Status

77-79

Reserved

3-6

Unused

80-83

Reserved or FXPAEC(TM1)
Reserved or FXCAEC(TM1)

Additional Sense Length

84-87

8-11

Unused

88-91

Reserved or FXPAEP(TM1)

Additional Sense Code (ASC)

92-95

Reserved or CHC (TM0) or FXCAEP(TM1)

Additional Sense Code Qualifier (ASCQ)

96-99

Reserved or CMC (TM0) or CFW(TM1)

Unused

100-103

Reserved or DSR2 (TM0) or RRR(TM1)

15-17

Unused

104-107

Memory Address

18-19

Reserved

108-111

Byte Count

20-23

Reserved or RDR2 (TM1)

112-115

DSR or PSR(TM1)

24-27

Reserved or RDEAR (TM1)

116-119

CSR or CSR(TM1)

28-31

Reserved

120-123

DCSR or EAR(TM1)

32–35

Instance Code

124-127

DER or EDR1(TM1)

Template

128-131

EAR or EDR0(TM1)

Template Flags

132-135

EDR or ICR TM1)

38-39

Reserved

136-139

ERR or IMR(TM1)

40-43

Reserved or FXPSCR (TM1)

140-143

RSR or DIO(TM1)

44-47

Reserved or FXCSR (TM1)

144-147

RDR0

48-51

Reserved or FXCCSR (TM1)

148-151

RDR1

52-53

Reserved

152-155

WDR0

54-69

Controller Board Serial Number

156-159

WDR1

70-73

Controller Software Revision Level

CXO6181A

Event Reporting: Templates and Codes

D–13

Device Services Non-Transfer Error Event Sense Data Response
The HSG80 controller Device Services software component reports
errors detected while performing non-transfer work related to disk
(including CD-ROM and optical memory) device operations via the
Device Services Non-Transfer Event Sense Data Response (see Figure
D–9).

n
n

Figure D–9
off

bit
0

Template 41 - Device Services Non-Transfer Error
Event Sense Data Response Format
7

Unusd

1
2

Error Code
Unused
Sense Key

Unused

3-6

Unused

Additional Sense Length

8-11

Unused

Additional Sense Code (ASC)

Additional Sense Code Qualifier (ASCQ)

Unused

15–17

Unused

18–31

Reserved

32-35

Instance Code

Template

Template Flags

38–53

Reserved

54–69

Controller Board Serial Number

70-73

Controller Software Revision Level

74-75

Reserved

LUN Status

77–103

Reserved

104

Associated Port

105

Associated Target

106

Associated Additional Sense Code

107

Associated Additional Sense Code Qualifier

108–159

Reserved
CXO6182A

D–14

HSG80 User’s Guide

Disk Transfer Error Event Sense Data Response
The HSG80 controller Device Services and Value Added Services
software components report errors detected while performing work
related to disk (including CD-ROM and optical memory) device
transfer operations via the Disk Transfer Error Event Sense Data
Response (see Figure D–10).

n
n

Event Reporting: Templates and Codes

D–15

Figure D–10 Template 51 - Disk Transfer Error Event Sense Data
Response Format
off

bit

0–17

18–19

Reserved

Total Number of Errors

Total Retry Count

22–25

ASC/ASCQ Stack

26–28

Device Locator

29–31

Reserved

32–35

Instance Code

Template

Template Flags

Reserved

Command Opcode

Sense Data Qualifier

41–50

Original CDB

Host ID

52–53

Reserved

54–69

Controller Board Serial Number

70–73

Controller Software Revision Level

74–75

Reserved

LUN Status

77–78

Reserved

79-82

Device Firmware Revision Level

83–98

Device Product ID

99–100

Reserved

101

Device Type

102–103
104

Error Code
Segment

EOM

ILI

Rsvd

Sense Key

Information

107–110
111

Additional Sense Length

112–115

Command Specific Information

116

Additional Sense Code (ASC)

117

Additional Sense Code Qualifier (ASCQ)
Field Replaceable Unit Code

118
119
120

Reserved
Valid

105
106

Standard Sense Data

SKSV
Sense Key Specific

121
122–159

Reserved
CXO6183B

D–16

HSG80 User’s Guide

Instance Codes
An Instance Code is a number that uniquely identifies an event being
reported.

Instance Code Structure
Figure D–11 shows the structure of an instance code. If you understand
its structure, you will be able to translate it, bypassing the fault
management utility (FMU).
Figure D–11 Structure of an Instance Code
omponent ID number

Repair action

01010302
Event #

Event threshold

Instance Codes and FMU
The format of an Instance Code as it appears in Sense Data Responses
is shown in Figure D–12.
Figure D–12 Instance Code Format
off

bit

(8)32

NR Threshold

(9)33

Repair Action

(10)34

Error Number

(11)35

Component ID
CXO6470A

Note The offset values enclosed in braces ({}) apply only to the
passthrough device reset event sense data response format (see Figure
D–1, “Pass-through Device Reset Event Sense Data Response Format”
on page D–2). The nonbraced offset values apply only to the logical
device event sense data response formats shown in the templates that
begin on page D–85.

Event Reporting: Templates and Codes

D–17

NR Threshold
Located at byte offset {8}32, the NR Threshold is the notification/
recovery threshold assigned to the event. This value is used during
Symptom-Directed Diagnosis procedures to determine when
notification/recovery action should be taken.

Repair Action
The Repair Action found at byte offset {9}33 indicates the
recommended repair action code assigned to the event. This value is
used during Symptom-Directed Diagnosis procedures to determine
what notification/recovery action should be taken when the NR
Threshold is reached. For more details about recommended repair
actions, see “Recommended Repair Action Codes,” page D–77.

Event Number
Located at byte offset {10}34, the Event Number, when combined with
the value contained in the Component ID field, uniquely-identifies the
reported event.

Component ID
A component ID is a number that uniquely-identifies the software
component that detected the event and is found at byte offset {11}35
(see “Component Identifier Codes,” page D–82).

D–18

HSG80 User’s Guide

Table D–1 contains the instance codes that can be issued by the
controller’s fault-management software.
Table D–1 Instance Codes
Instance
Description
Code
01010302 An unrecoverable hardware detected fault occurred.
0102030A
01032002

02020064

02032001

02042001

02052301

02072201

02082201
02090064

020B2201

020C2201

An unrecoverable software inconsistency was detected or an intentional
restart or shutdown of controller operation was requested.
Nonvolatile parameter memory component EDC check failed; content of
the component reset to default settings.
Disk Bad Block Replacement attempt completed for a write within the
user data area of the disk. Note that due to the way Bad Block
Replacement is performed on SCSI disk drives, information on the actual
replacement blocks is not available to the controller and is therefore not
included in the event report.
Journal SRAM backup battery failure; detected during system restart.
The Memory Address field contains the starting physical address of the
Journal SRAM.
Journal SRAM backup battery failure; detected during periodic check.
The Memory Address field contains the starting physical address of the
Journal SRAM.
A processor interrupt was generated by the CACHEA0 Memory
Controller with an indication that the CACHE backup battery has failed
or is low (needs charging). The Memory Address field contains the
starting physical address of the CACHEA0 memory.
The CACHEAO Memory Controller failed testing performed by the
Cache Diagnostics. The Memory Address field contains the starting
physical address of the CACHEA0 memory.
The CACHEA1 Memory Controller failed testing performed by the
Cache Diagnostics. The Memory Address field contains the starting
physical address of the CACHEA1 memory.
A data compare error was detected during the execution of a compare
modified READ or WRITE command.
Failed read test of a write-back metadata page residing in cache. Dirty
write-back cached data exists and cannot be flushed to media. The dirty
data is lost. The Memory Address field contains the starting physical
address of the CACHEA0 memory.
Cache Diagnostics have declared the cache bad during testing. The
Memory Address field contains the starting physical address of the
CACHEA0 memory.

Template
01
01
11

14
51

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The wrong write cache module is configured. The serial numbers do not
match. Either the existing or the expected cache contains dirty write020D2401 back cached data. Note that in this instance the Memory Address, Byte
Count, FX Chip Register, Memory Controller register, and Diagnostic
register fields are undefined.
The write cache module is missing. A cache is expected to be configured
and contains dirty write-back cached data. Note that in this instance the
020E2401
Memory Address, Byte Count, FX Chip Register, Memory Controller
register, and Diagnostic register fields are undefined.
The write cache modules are not configured properly for a dualredundant configuration. One of the cache modules is not the same size
02102401 to perform cache failover of dirty write-back cached data. Note that in
this instance the Memory Address, Byte Count, FX Chip Register,
Memory Controller register, and Diagnostic register fields are undefined.
Disk Bad Block Replacement attempt completed for a read within the
user data area of the disk. Note that due to the way Bad Block
02110064 Replacement is performed on SCSI disk drives, information on the
actual replacement blocks is not available to the controller and is
therefore not included in the event report.
Disk Bad Block Replacement attempt completed for a write of controller
metadata to a location outside the user data area of the disk. Note that
021A0064 due to the way Bad Block Replacement is performed on SCSI disk
drives, information on the actual replacement blocks is not available to
the controller and is therefore not included in the event report.
Disk Bad Block Replacement attempt completed for a read of controller
metadata from a location outside the user data area of the disk. Note that
021B0064 due to the way Bad Block Replacement is performed on SCSI disk
drives, information on the actual replacement blocks is not available to
the controller and is therefore not included in the event report.
Unable to lock the other controller’s cache in a write-cache failover
attempt. Either a latent error could not be cleared on the cache or the
021D0064 other controller did not release its cache. Note that in this instance the
Memory Address, Byte Count, FX Chip register, Memory Controller
register, and Diagnostic register fields are undefined.
The device specified in the Device Locator field has been added to the
021E0064 RAIDset associated with the logical unit.The RAIDset is now in
Reconstructing state.
The device specified in the Device Locator field has been added to the
02280064 Mirrorset associated with the logical unit. The new Mirrorset member is
now in Copying state.

D–19

Template

D–20

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The device specified in the Device Locator has transitioned from
022C0064
Copying or Normalizing state to Normal state.
The device specified in the Device Locator field has been converted to a
022E0064
Mirrorset associated with the logical unit.
The mirrored device specified in the Device Locator field has been
022F0064
converted to a single device associated with the logical unit.
The CACHEB0 Memory Controller, which resides on the other cache
module failed testing performed by the Cache Diagnostics. This is the
02383A01
mirrored cache Memory Controller. The Memory Address field contains
the starting physical address of the CACHEB0 memory.
Both the CACHEB0 Memory Controller and CACHEB1 Memory
Controller, which resides on the other cache module, failed testing
02392201 performed by the Cache Diagnostics. Data cannot be accessed in the
primary cache or the mirror cache. The Memory Address field contains
the starting physical address of the CACHEA0 memory.
Metadata residing in the controller and on the two cache modules
disagree as to the mirror node. Note that in this instance the Memory
023E2401
Address, Byte Count, FX Chip register, Memory Controller register, and
Diagnostic register fields are undefined.
The cache backup battery covering the mirror cache is insufficiently
023F2301 charged. The Memory Address field contains the starting physical
address of the CACHEB1 memory.
The cache backup battery covering the mirror cache has been declared
bad. Either it failed testing performed by the Cache Diagnostics during
02402301 system startup or it was low (insufficiently charged) for longer than the
expected duration. The Memory Address field contains the starting
physical address of the CACHEB1 memory.
Mirrored cache writes have been disabled. Either the primary or the
mirror cache has been declared bad or data invalid and will not be used.
02412401 Note that in this instance the Memory Address, Byte Count, FX Chip
register, Memory Controller register, and Diagnostic register fields are
undefined.
Cache failover attempt failed because the other cache was illegally
configured with DIMMs. Note that in this instance the Memory Address,
02422464
Byte Count, FX Chip register, Memory Controller register, and
Diagnostic register fields are undefined.

Template
51
51
51

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The write cache module which is the mirror for the primary cache is
unexpectedly not present (missing). A cache is expected to be
02492401 configured and it may contain dirty write cached data. Note that in this
instance, the Memory Address, Byte Count, FX Chip register, Memory
Controller register, and Diagnostic register fields are undefined.
Mirroring is enabled and the primary write cache module is expectedly
not present (missing). A cache is expected to be configured and it may
024A2401 contain dirty write cached data. Note that in this instance, the Memory
Address, Byte Count, FX Chip register, Memory Controller register, and
Diagnostic register fields are undefined.
Write-back caching has been disabled either due to a cache or batteryrelated problem. The exact nature of the problem is reported by other
024B2401 instance codes. Note that in this instance the Memory Address, Byte
Count, FX Chip register, Memory Controller register, and Diagnostic
register fields are undefined.
This cache module is populated with DIMMs incorrectly. Cache
metadata resident in the cache module indicates that unflushed write
cache data exists for a cache size different than what is found present.
024F2401
Note that in this instance the Memory Address, Byte Count, FX Chip
register, Memory Controller register, and Diagnostic register fields are
undefined.
This command failed because the target unit is not online to the
0251000A controller. The Information field of the Device Sense Data contains the
block number of the first block in error.
The last block of data returned contains a forced error. A forced error
occurs when a disk block is successfully reassigned, but the data in that
0252000A block is lost. Re-writing the disk block will clear the forced error
condition. The Information field of the Device Sense Data contains the
block number of the first block in error.
The data supplied from the host for a data compare operation differs
from the data on the disk in the specified block. The Information field of
0253000A
the Device Sense Data contains the block number of the first block in
error.
The command failed due to a host data transfer failure. The Information
0254000A field of the Device Sense Data contains the block number of the first
block in error.
The controller was unable to successfully transfer data to target unit. The
0255000A Information field of the Device Sense Data contains the block number of
the first block in error.

D–21

Template

D–22

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The write operation failed because the unit is Data Safety Write
0256000A Protected. The Information field of the Device Sense Data contains the
block number of the first block in error.
An attempt to reassign a bad disk block failed. The contents of the disk
0257000A block is lost. The Information field of the Device Sense Data contains
the block number of the first block in error.
This command was aborted prior to completion. The Information field
0258000A of the Device Sense Data contains the block number of the first block in
error.
The write operation failed because the unit is hardware write protected.
0259000A The Information field of the Device Sense Data contains the block
number of the first block in error.
The command failed because the unit became inoperative prior to
025A000A command completion. The Information field of the Device Sense Data
contains the block number of the first block in error.
The command failed because the unit became unknown to the controller
025B000A prior to command completion. The Information field of the Device
Sense Data contains the block number of the first block in error.
The command failed because of a unit media format error. The
025C000A Information field of the Device Sense Data contains the block number of
the first block in error.
The command failed for an unknown reason. The Information field of
025D000A the Device Sense Data contains the block number of the first block in
error
Memory diagnostics performed during controller initialization detected
an excessive number (512 pages or more) of memory errors detected on
the primary cache memory. Diagnostics have not declared the cache
failed, due to the isolated bad memory regions, but this is a warning to
025F2201
replace the cache as soon as possible in case of further degradation. The
software performed the necessary error recovery as appropriate. Note
that in this instance the Memory Address and Byte Count fields are
undefined.
Memory diagnostics performed during controller initialization detected
an excessive number (512 pages or more) of memory errors detected on
mirrored cache memory. Diagnostics has not declared the cache failed,
due to the isolated bad memory regions, but this is a warning to replace
02603A01
the cache as soon as possible in case of further degradation. The
software performed the necessary error recovery as appropriate. Note
that in this instance the Memory Address, Byte Count fields are
undefined.

Template
51

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
Memory diagnostics performed during controller initialization detected
02613801 that the DIMM in location 1 failed on the cache module. Note that in this
instance the Byte Count field in undefined.
Memory diagnostics performed during controller initialization detected
02623801 that the DIMM in location 2 failed on the cache module. Note that in this
instance the Byte Count field in undefined.
Memory diagnostics performed during controller initialization detected
02633801 that the DIMM in location 3 failed on the cache module. Note that in this
instance the Byte Count field in undefined.
Memory diagnostics performed during controller initialization detected
02643801 that the DIMM in location 4 failed on the cache module. Note that in this
instance the Byte Count field in undefined.
Memory diagnostics performed during controller initialization detected
that the DIMM in location 3 on the other controller’s cache module (on
02653C01
mirrored cache) failed. Mirroring has been disabled. Note that in this
instance the Byte Count field is undefined.
Memory diagnostics performed during controller initialization detected
that the DIMM in location 4 on the other controller’s cache module (on
02663C01
mirrored cache) failed. Mirroring has been disabled. Note that in this
instance the Byte Count field is undefined.
The device specified in the Device Locator field has been removed from
02675201 the RAIDset associated with the logical unit. The removed device is now
in the Failedset. The RAIDset is now in Reduced state.
The device specified in the Device Locator field failed to be added to the
0268530A RAIDset associated with the logical unit. The device will remain in the
Spareset.
The device specified in the Device Locator field failed to be added to the
02695401 RAIDset associated with the logical unit. The failed device has been
moved to the Failedset.
026A5001 The RAIDset associated with the logical unit has gone inoperative.
The RAIDset associated with the logical unit has transitioned from
026B0064
Normal state to Reconstructing state.
The RAIDset associated with the logical unit has transitioned from
026C0064
Reconstructing state to Normal state.
The device specified in the Device Locator field has been removed from
026D5201 the Mirrorset associated with the logical unit. The removed device is
now in the Failedset.

D–23

Template
14

51
51
51
51
51

D–24

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The device specified in the Device Locator field has been reduced from
the Mirrorset associated with the logical unit. The nominal number of
026E0001
members in the mirrorset has been decreased by one. The reduced device
is now available for use.
The device specified in the Device Locator field failed to be added to the
026F530A mirrorset associated with the logical unit. The device will remain in the
Spareset.
The device specified in the Device Locator field failed to be added to the
02705401 mirrorset associated with the logical unit. The failed device has been
moved to the Failedset.
The mirrorset associated with the logical unit has had its nominal
02710064 membership changed. The new nominal number of members for the
mirrorset is specified in the Device Sense Data Information field.
02725101 The Mirrorset associated with the logical unit has gone inoperative.
The device specified in the Device Locator field had a read error which
02730001
has been repaired with data from another mirrorset member.
The device specified in the Device Locator field had a read error.
02745A0A Attempts to repair the error with data from another mirrorset member
failed due to lack of alternate error-free data source.
The device specified in the Device Locator field had a read error.
Attempts to repair the error with data from another mirrorset member
02755601
failed due to a write error on the original device. The original device will
be removed from the mirrorset.
The mirrored cache is not being used because the data in the mirrored
cache is inconsistent with the data in the primary cache. The primary
cache contains valid data, so the controller is caching solely from the
primary cache. The mirrored cache is declared “failed”, but this is not
02773D01
due to a hardware fault, only inconsistent data. Mirrored writes have
been disabled until this condition is cleared. Note that in this instance the
Memory Address, Byte Count, FX Chip register, Memory Controller
register, and Diagnostic register fields are undefined.
The cache backup battery is not present. The Memory Address field
02782301
contains the starting physical address of the CACHEA0 memory.
The cache backup battery covering the mirror cache is not present. The
02792301 Memory Address field contains the starting physical address of the
CACHEB1 memory.

Template
51

51
51
51
51

12
12

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The CACHEB0 Memory Controller failed Cache Diagnostics testing
performed on the other cache during a cache failover attempt. The
027A2201
Memory Address field contains the starting physical address of the
CACHEB0 memory.
The CACHEB1 Memory Controller failed Cache Diagnostics testing
performed on the other cache during a cache failover attempt. The
027B2201
Memory Address field contains the starting physical address of the
CACHEB1 memory.
The CACHEB0 and CACHEB1 Memory Controllers failed Cache
Diagnostics testing performed on the other cache during a cache failover
027C2201
attempt. The Memory Address field contains the starting physical
address of the CACHEB0 memory.
The Mirrorset associated with the logical unit has gone inoperative due
027D5B01
to a disaster tolerance failsafe locked condition.
The command failed because the disaster tolerance mirrorset went
failsafe locked prior to command completion. The Information field of
027E5B01
the Device Sense Data contains the block number of the first block in
error.
The CACHE backup battery has been declared bad. The battery did not
become fully charged within the expected duration. The Memory
027F2301
Address field contains the starting physical address of the CACHEA0
memory.
The command failed because the disaster tolerance mirrorset is failsafe
02805B01 locked. The Information field of the Device Sense Data contains the
block number of the first block in error.
The command failed because the disaster tolerance mirrorset is failsafe
02815B01 locked. The Information field of the Device Sense Data contains the
block number of the first block in error.
The Mirrorset associated with the logical unit has just had a membership
02825C64 change such that disaster tolerance failsafe error mode can now be
enabled if desired.
The CACHE backup battery has exceeded the maximum number of deep
discharges. Battery capacity may be below specified values. The
02872301
Memory Address field contains the starting physical address of the
CACHEA0 memory.
The CACHE backup battery covering the mirror cache has exceeded the
maximum number of deep discharges. Battery capacity may be below
02882301
specified values. The Memory Address field contains the starting
physical address of the CACHEB1 memory.

D–25

Template
14

D–26

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The CACHE backup battery is near its end of life. The Memory Address
02892301
field contains the starting physical address of the CACHEA0 memory.
The CACHE backup battery covering the mirror cache is near its end of
028A2301 life. The Memory Address field contains the starting physical address of
the CACHEB1 memory.
No command control structures available for disk operation. Note that in
03010101 this instance the Associated Additional Sense Code and Associated
Additional Sense Code Qualifier fields are undefined.
SCSI interface chip command timeout during disk operation. Note that
03022002 in this instance the Associated Additional Sense Code and Associated
Additional Sense Code Qualifier fields are undefined.
Byte transfer timeout during disk operation. Note that in this instance the
03034002 Associated Additional Sense Code and Associated Additional Sense
Code Qualifier fields are undefined.
SCSI bus errors during disk operation. Note that in this instance the
03044402 Associated Additional Sense Code and Associated Additional Sense
Code Qualifier fields are undefined.
Device port SCSI chip reported gross error during disk operation. Note
03052002 that in this instance the Associated Additional Sense Code and
Associated Additional Sense Code Qualifier fields are undefined.
Non-SCSI bus parity error during disk operation. Note that in this
03062002 instance the Associated Additional Sense Code and Associated
Additional Sense Code Qualifier fields are undefined.
Source driver programming error encountered during disk operation.
03070101 Note that in this instance the Associated Additional Sense Code and
Associated Additional Sense Code Qualifier fields are undefined.
Miscellaneous SCSI Port Driver coding error detected during disk
operation. Note that in this instance the Associated Additional Sense
03080101
Code and Associated Additional Sense Code Qualifier fields are
undefined.
An unrecoverable disk drive error was encountered while performing
03094002
work related to disk unit operations.
A Drive failed because a Test Unit Ready command or a Read Capacity
030C4002
command failed.
030D000A Drive was failed by a Mode Select command received from the host.
030E4002 Drive failed due to a deferred error reported by drive.
030F4002 Unrecovered Read or Write error.
03104002 No response from one or more drives.

Template
12
12

51
51
51
51
51
51

Event Reporting: Templates and Codes

D–27

Table D–1 Instance Codes (Continued)
Instance
Description
Template
Code
Nonvolatile memory and drive metadata indicate conflicting drive
0311430A
51
configurations.
The Synchronous Transfer Value differs between drives in the same
0312430A
51
storageset.
03134002 Maximum number of errors for this data transfer operation exceeded.
51
03144002 Drive reported recovered error without transferring all data.
51
03154002 Data returned from drive is invalid.
51
03164002 Request Sense command to drive failed.
51
03170064 Illegal command for pass through mode.
51
03180064 Data transfer request error.
51
03194002 Premature completion of a drive command.
51
031A4002 Command timeout.
51
031B0101 Watchdog timer timeout.
51
031C4002 Disconnect timeout.
51
031D4002 Unexpected bus phase.
51
031E4002 Disconnect expected.
51
031F4002 ID Message not sent by drive.
51
03204002 Synchronous negotiation error.
51
03214002 The drive unexpectedly disconnected from the SCSI bus.
51
03224002 Unexpected message.
51
03234002 Unexpected Tag message.
51
03244002 Channel busy.
51
03254002 Message Reject received on a valid message.
51
0326450A The disk device reported Vendor Unique SCSI Sense Data.
51
A disk related error code was reported which was unknown to the Fault
Management firmware. Note that in this instance the Associated
03270101
41
Additional Sense Code and Associated Additional Sense Code Qualifier
fields are undefined.
0328450A The disk device reported standard SCSI Sense Data.
51
03324002 SCSI bus selection timeout.
Pass-through
03330002 Device power on reset.
Pass-through
03344002 Target assertion of REQ after WAIT DISCONNECT.
Pass-through
During device initialization a Test Unit Ready command or a Read
03354002
Pass-through
Capacity command to the device failed.
03364002 During device initialization the device reported a deferred error.
Pass-through

D–28

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Template
Code
During device initialization the maximum number of errors for a data
03374002
Pass-through
transfer operation was exceeded.
03384002 Request Sense command to the device failed.
Pass-through
03394002 Command timeout.
Pass-through
033A4002 Disconnect timeout.
Pass-through
033B4002 Unexpected bus phase.
Pass-through
033C4002 The device unexpectedly disconnected from the SCSI bus.
Pass-through
033D4002 Unexpected message.
Pass-through
033E4002 Message Reject received on a valid message.
Pass-through
No command control structures available for passthrough device
Pass-through
033F0101
operation.
03402002 Device port SCSI chip reported gross error.
Pass-through
03410101 Miscellaneous SCSI Port Driver coding error.
Pass-through
A passthrough device related internal error code was reported which is
03420101
Pass-through
not recognized by the Fault Management firmware.
During device initialization the device reported unexpected standard
Pass-through
03434002
SCSI Sense Data.
No command control structures available for operation to a device which
is unknown to the controller. Note that in this instance the Associated
03C80101
41
Additional Sense Code and Associated Additional Sense Code Qualifier
fields are undefined.
SCSI interface chip command timeout during operation to a device
which is unknown to the controller. Note that in this instance the
03C92002
41
Associated Additional Sense Code and Associated Additional Sense
Code Qualifier fields are undefined.
Byte transfer timeout during operation to a device which is unknown to
the controller. Note that in this instance the Associated Additional Sense
03CA4002
41
Code and Associated Additional Sense Code Qualifier fields are
undefined.
Miscellaneous SCSI Port Driver coding error detected during operation
to a device which is unknown to the controller. Note that in this instance
03CB0101
41
the Associated Additional Sense Code and Associated Additional Sense
Code Qualifier fields are undefined.
An error code was reported which was unknown to the Fault
Management software. Note that in this instance the Associated
03CC0101
41
Additional Sense Code and Associated Additional Sense Code Qualifier
fields are undefined.

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
Device port SCSI chip reported gross error during operation to a device
which is unknown to the controller. Note that in this instance the
03CD2002
Associated Additional Sense Code and Associated Additional Sense
Code Qualifier fields are undefined.
Non-SCSI bus parity error during operation to a device which is
unknown to the controller. Note that in this instance the Associated
03CE2002
Additional Sense Code and Associated Additional Sense Code Qualifier
fields are undefined.
Source driver programming error encountered during operation to a
device which is unknown to the controller. Note that in this instance the
03CF0101
Associated Additional Sense Code and Associated Additional Sense
Code Qualifier fields are undefined.
A failure occurred while attempting a SCSI Test Unit Ready or Read
Capacity command to a device. The device type is unknown to the
03D04002 controller. Note that in this instance the Associated Additional Sense
Code and Associated Additional Sense Code Qualifier fields are
undefined.
The identification of a device does not match the configuration
information. The actual device type is unknown to the controller. Note
03D14002
that in this instance the Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.
SCSI bus errors during device operation. The device type is unknown to
the controller. Note that in this instance the Associated Additional Sense
03D24402
Code and Associated Additional Sense Code Qualifier fields are
undefined.
During device initialization, the device reported the SCSI Sense Key NO
SENSE. This indicates that there is no specific sense key information to
be reported for the designated logical unit. This would be the case for a
03D3450A
successful command or a command that received CHECK CONDITION
or COMMAND TERMINATED status because one of the FM, EOM, or
ILI bits is set to one in the sense data flags field.
During device initialization, the device reported the SCSI Sense Key
03D4450A RECOVERED ERROR. This indicates the last command completed
successfully with some recovery action performed by the target.
During device initialization, the device reported the SCSI Sense Key
NOT READY. This indicates that the logical unit addressed cannot be
03D5450A
accessed. Operator intervention may be required to correct this
condition.

D–29

Template
41

D–30

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
During device initialization, the device reported the SCSI Sense Key
MEDIUM ERROR. This indicates that the command terminated with a
non-recovered error condition that was probably caused by a flaw in the
03D6450A medium or an error in the recorded data. This sense key may also be
returned if the target is unable to distinguish between a flaw in the
medium and a specific hardware failure (HARDWARE ERROR sense
key).
During device initialization, the device reported the SCSI Sense Key
HARDWARE ERROR. This indicates that the target detected a non03D7450A recoverable hardware failure (for example, controller failure, device
failure, parity error, etc.) while performing the command or during a self
test.
During device initialization, the device reported the SCSI Sense Key
ILLEGAL REQUEST. Indicates that there was an illegal parameter in
the command descriptor block or in the additional parameters supplied
as data for some commands (FORMAT UNIT, SEARCH DATA, etc.). If
03D8450A the target detects an invalid parameter in the command descriptor block,
then it shall terminate the command without altering the medium. If the
target detects an invalid parameter in the additional parameters supplied
as data, then the target may have already altered the medium. This sense
key may also indicate that an invalid IDENTIFY message was received.
During device initialization, the device reported the SCSI Sense Key
03D9450A UNIT ATTENTION. This indicates that the removable medium may
have been changed or the target has been reset.
During device initialization, the device reported the SCSI Sense Key
DATA PROTECT. This indicates that a command that reads or writes the
03DA450A
medium was attempted on a block that is protected from this operation.
The read or write operation is not performed.
During device initialization, the device reported the SCSI Sense Key
BLANK CHECK. This indicates that a write-once device encountered
03DB450A
blank medium or format-defined end-of-data indication while reading or
a write-once device encountered a non-blank medium while writing.
During device initialization, the device reported a SCSI Vendor Specific
03DC450A Sense Key. This sense key is available for reporting vendor specific
conditions.
During device initialization, the device reported the SCSI Sense Key
COPY ABORTED. This indicates a COPY, COMPARE, or COPY AND
03DD450A
VERIFY command was aborted due to an error condition on the source
device, the destination device, or both.

Template

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
During device initialization, the device reported the SCSI Sense Key
ABORTED COMMAND. This indicates the target aborted the
03DE450A
command. The initiator may be able to recover by trying the command
again.
During device initialization, the device reported the SCSI Sense Key
03DF450A EQUAL. This indicates a SEARCH DATA command has satisfied an
equal comparison.
During device initialization, the device reported the SCSI Sense Key
VOLUME OVERFLOW. This indicates a buffered peripheral device has
03E0450A reached the end-of-partition and data may remain in the buffer that has
not been written to the medium. A RECOVER BUFFERED DATA
command(s) may be issued to read the unwritten data from the buffer.
During device initialization, the device reported the SCSI Sense Key
03E1450A MISCOMPARE. This indicates the source data did not match the data
read from the medium.
During device initialization, the device reported a reserved SCSI Sense
03E2450A
Key.
The EMU has indicated that Termination Power is good on all ports.
Note that in this instance the Associated Target, Associated Additional
03E40F64
Sense Code, and Associated Additional Sense Code Qualifier fields are
undefined.
The EMU has detected bad Termination Power on the indicated port.
Note that in this instance the Associated Target, Associated Additional
03E58002
Sense Code, and Associated Additional Sense Code Qualifier fields are
undefined.
The EMU for the cabinet indicated by the Associated Port field has
become available. Note that the Associated Target, Associated
03EE0064
Additional Sense Code, and the Associated Additional Sense Code
Qualifier fields are undefined.
The EMU for the cabinet indicated by the Associated Port field has
become unavailable. Note that the Associated Target, Associated
03EF8301
Additional Sense Code, and the Associated Additional Sense Code
Qualifier fields are undefined.
The SWAP interrupt from the device port indicated by the Associated
Port field can not be cleared. All SWAP interrupts from all ports will be
disabled until corrective action is taken. When SWAP interrupts are
03F10502 disabled, both controller front panel button presses and removal/
insertion of devices are not detected by the controller. Note that in this
instance the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.

D–31

Template
41

41
41

D–32

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The SWAP interrupts have been cleared and re-enabled for all device
ports. Note that in this instance the Associated Port, Associated Target,
03F20064
Associated Additional Sense Code, and Associated Additional Sense
Code Qualifier fields are undefined.
An asynchronous SWAP interrupt was detected by the controller for the
device port indicated by the Associated Port field. Possible reasons for
this occurrence include:
n device insertion or removal
03F30064 n shelf power failure
n SWAP interrupts reenabled
Note that in this instance the Associated Target, Associated Additional
Sense Code, and Associated Additional Sense Code Qualifier fields are
undefined.
Device services had to reset the port to clear a bad condition. Note that
in this instance the Associated Target, Associated Additional Sense
03F40064
Code, and Associated Additional Sense Code Qualifier fields are
undefined.
The controller shelf is reporting a problem. This could mean one or both
of the following:
n If the shelf is using dual power supplies, one power supply has
failed.
03F60402
n One of the shelf cooling fans has failed.
Note that in this instance the Associated Target, Associated Additional
Sense Code, and Associated Additional Sense Code Qualifier fields are
undefined.
The shelf indicated by the Associated Port field is reporting a problem.
This could mean one or both of the following:
n If the shelf is using dual power supplies, one power supply has
failed.
03F70401
n One of the shelf cooling fans has failed.
Note that in this instance the Associated Target, Associated Additional
Sense Code, and Associated Additional Sense Code Qualifier fields are
undefined.
The EMU has detected one or more bad power supplies. Note that in this
03F80701 instance the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.
The EMU has detected one or more bad fans. Note that in this instance
03F90601 the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.

Template
41

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The EMU has detected an elevated temperature condition. Note that in
03FA0D01 this instance the Associated Target, Associated Additional Sense Code,
and Associated Additional Sense Code Qualifier fields are undefined.
The EMU has detected an external air sense fault. Note that in this
03FB0E01 instance the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.
The EMU-detected power supply fault is now fixed. Note that in this
03FC0F01 instance the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.
The EMU-detected bad-fan fault is now fixed. Note that in this instance
03FD0F01 the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.
The EMU-detected elevated temperature fault is now fixed. Note that in
03FE0F01 this instance the Associated Target, Associated Additional Sense Code,
and Associated Additional Sense Code Qualifier fields are undefined.
The EMU-detected external air sense fault is now fixed. Note that in this
03FF0F01 instance the Associated Target, Associated Additional Sense Code, and
Associated Additional Sense Code Qualifier fields are undefined.
Failover Control detected a receive packet sequence number mismatch.
The controllers are out of synchronization with each other and are
07030B0A
unable to communicate. Note that in this instance the Last Failure Code
and Last Failure Parameters fields are undefined.
Failover Control detected a transmit packet sequence number mismatch.
The controllers are out of synchronization with each other and are
07040B0A
unable to communicate. Note that in this instance the Last Failure Code
and Last Failure Parameters fields are undefined.
Failover Control received a Last Gasp message from the other controller.
07050064 The other controller is expected to restart itself within a given time
period. If it does not, it will be held reset with the “Kill” line.
Failover Control detected that both controllers are acting as SCSI ID 6.
Since ids are determined by hardware, it is unknown which controller is
07060C01
the real SCSI ID 6. Note that in this instance the Last Failure Code and
Last Failure Parameters fields are undefined.
Failover Control detected that both controllers are acting as SCSI ID 7.
Since ids are determined by hardware, it is unknown which controller is
07070C01
the real SCSI ID 7. Note that in this instance the Last Failure Code and
Last Failure Parameters fields are undefined.

D–33

Template
41

D–34

HSG80 User’s Guide

Table D–1 Instance Codes (Continued)
Instance
Description
Code
Failover Control was unable to send keepalive communication to the
other controller. It is assumed that the other controller is hung or not
07080B0A
started. Note that in this instance the Last Failure Code and Last Failure
Parameters fields are undefined.
Memory System Error Analysis is indicated in the information preserved
during a previous last failure but no error conditions are indicated in the
0C00370A
available Memory Controller registers. The Quadrant 0 Memory
Controller (CACHEA0) registers content is supplied.
The Quadrant 0 Memory Controller (CACHEA0) detected an Address
0C103E02
Parity error.
The Quadrant 1 Memory Controller (CACHEA1) detected an Address
0C113E02
Parity error.
The Quadrant 2 Memory Controller (CACHEB0) detected an Address
0C123E02
Parity error.
The Quadrant 3 Memory Controller (CACHEB1) detected an Address
0C133E02
Parity error.
The Quadrant 0 Memory Controller (CACHEA0) detected a Data Parity
0C203E02
error.
The Quadrant 1 Memory Controller (CACHEA1) detected a Data Parity
0C213E02
error.
The Quadrant 2 Memory Controller (CACHEB0) detected a Data Parity
0C223E02
error.
The Quadrant 3 Memory Controller (CACHEB1) detected a Data Parity
0C233E02
error.
The Quadrant 0 Memory Controller (CACHEA0) detected a Multibit ECC
0C303F02
error.
The Quadrant 1 Memory Controller (CACHEA1) detected a Multibit ECC
0C313F02
error.
The Quadrant 2 Memory Controller (CACHEB0) detected a Multibit ECC
0C323F02
error.
The Quadrant 3 Memory Controller (CACHEB1) detected a Multibit ECC
0C333F02
error.
The Quadrant 0 Memory Controller (CACHEA0) detected a Firewall
0C403E02
error.
The Quadrant 1 Memory Controller (CACHEA1) detected a Firewall
0C413E02
error.
The Quadrant 2 Memory Controller (CACHEB0) detected a Firewall
0C423E02
error.

Template
05

14
14
14
14
14
14
14
14
14
14
14
14
14
14
14

Event Reporting: Templates and Codes

Table D–1 Instance Codes (Continued)
Instance
Description
Code
The Quadrant 3 Memory Controller (CACHEB1) detected a Firewall
0C433E02
error.
Host Port Protocol component has detected that the other controller has
43010064 failed and that this controller has taken over the units specified in the
extended sense data.
Host Port Protocol component has detected that this controller has taken
43020064
over (failed back) the units specified in the extended sense data.
A spurious interrupt was detected during the execution of a Subsystem
82042002
Built-In Self Test.
An unrecoverable error was detected during execution of the HOST
82052002 PORT Subsystem Test. The system will not be able to communicate with
the host.
An unrecoverable error was detected during execution of the UART/
82062002 DUART Subsystem Test. This will cause the console to be unusable.
This will cause failover communications to fail.
An unrecoverable error was detected during execution of the FX
82072002
Subsystem Test.
An unrecoverable error was detected during execution of the PCI9060ES
820A2002
Test.
An unrecoverable error was detected during execution of the Device Port
Subsystem Built-In Self Test. One or more of the device ports on the
820B2002
controller module has failed; some/all of the attached storage is no
longer accessible via this controller.

D–35

Template
14
05
05
13
13

13
13
13

D–36

HSG80 User’s Guide

Last Failure Codes
A Last Failure Code is a number that uniquely-describes an
unrecoverable condition. It is found at byte offset 104 to 107 and will
only appear in Figure D–2, “Template 01 - Last Failure Event Sense
Data Response Format” on page D–4, and Figure D–4, “Template 05 Failover Event Sense Data Response Format” on page D–7.

Last Failure Code Structure
Figure D–13 shows the structure of a Last Failure Code. If you
understand its structure, you will be able to translate it, bypassing the
FMU.
Figure D–13 Structure of a Last Failure Code
Component ID number

Repair
action

Parameter Count

01000102
Error #

Restart Code and HW flag

Last Failure Codes and FMU
The format of an Last Failure Code is shown in Figure D–14.
Figure D–14 Last Failure Code Format
off

bit

104
105

7
HW

Restart Code

Parameter Code

Repair Action

106

Error Number

107

Component ID
CXO6469A

Note Do not confuse the Last Failure Code with the Instance Code (see
page D–16). They appear at different byte offsets and convey different
information.

Event Reporting: Templates and Codes

D–37

HW
This hardware/software flag is located at byte offset 104, bit 7. If this
flag is equal to 1, the unrecoverable condition is due to a hardwaredetected fault. If this flag is equal to 0, the unrecoverable condition is
due to an inconsistency with the software, or an intentional restart or
shutdown of the controller was requested.

Restart Code
Located at byte offset 104, bits 4-6, the Restart Code describes the
actions taken to restart the controller after the unrecoverable condition
was detected. Table D–2 gives a description of restart codes and their
descriptions.
Table D–2

Controller Restart Codes

Restart Code

Description

Full software restart

No restart

Automatic hardware restart

Parameter Count
The Parameter Count, located at byte offset 104, bits 0-3, indicates the
number of Last Failure Parameters containing supplemental
information supplied.

Repair Action
The Repair Action found at byte offset 105 indicates the recommended
repair action code assigned to the event. This value is used during
Symptom-Directed Diagnosis procedures to determine what
notification/recovery action should be taken. For more details, see
“Recommended Repair Action Codes,” page D–77.

Error Numbers
Located at byte offset 106, the Error Number, when combined with the
value contained in the Component ID field, uniquely-identifies the
condition detected.

D–38

HSG80 User’s Guide

Component IDs
A component ID uniquely identifies the software component that
detected the event and is found at byte offset {11}35 (see “Component
Identifier Codes,” page D–82).
Table D–3 contains the last failure codes that can be issued by the
controller’s fault-management software.
Table D–3

Last Failure Codes

Code

Description

01000100

Memory allocation failure during executive initialization.

01010100

An interrupt without any handler was triggered.

01020100

Entry on timer queue was not of type AQ or BQ.

01030100

Memory allocation for a facility lock failed.

01040100

Memory initialization called with invalid memory type.

01082004

01090105

010D0110

The core diagnostics reported a fault.
Last Failure Parameter[0] contains the error code value (same as blinking OCP
LEDs error code).
n Last Failure Parameter[1] contains the address of the fault.
n Last Failure Parameter[2] contains the actual data value.
n Last Failure Parameter[3] contains the expected data value.

n
n
n
n
n
n

An NMI occurred during EXEC$BUGCHECK processing.
Last Failure Parameter[0] contains the executive flags value.
Last Failure Parameter[1] contains the RIP from the NMI stack.
Last Failure Parameter[2] contains the read diagnostic register 0 value.
Last Failure Parameter[3] contains the FX Chip CSR value.
Last Failure Parameter[4] contains the SIP last failure code value

The System Information structure within the System Information Page has been reset to
default settings. The only known cause for this event is an I960 processor hang caused
by a reference to a memory region that is not implemented. When such a hang occurs,
controller modules equipped with inactivity watchdog timer circuitry will
spontaneously reboot after the watchdog timer expires (within seconds of the hang).
Controller modules not so equipped will just hang as indicated by the green LED on the
OCP remaining in a steady state.

Event Reporting: Templates and Codes

Table D–3

D–39

Last Failure Codes (Continued)

Code

Description

010E0110

All structures contained in the System Information Page (SIP) and the Last Failure
entries have been reset to their default settings. This is a normal occurrence for the first
boot following manufacture of the controller module and during the transition from one
software version to another if and only if the format of the SIP is different between the
two versions. If this event is reported at any other time, follow the recommended repair
action associated with this Last Failure code.

010F0110

All structures contained in the System Information Page and the Last Failure entries
have been reset to their default settings as the result of certain controller
manufacturing configuration activities. If this event is reported at any other time,
follow the recommended repair action associated with this Last Failure code.

01100100

Non-maskable interrupt entered but no Non-maskable interrupt pending. This is
typically caused by an indirect call to address 0.

01110106

A bugcheck occurred during EXEC$BUGCHECK processing.
n Last Failure Parameter [0] contains the executive flags value.
n Last Failure Parameter [1] contains the RIP from the bugcheck call stack.
n Last Failure Parameter [2] contains the first SIP last failure parameter value.
n Last Failure Parameter [3] contains the second SIP last failure parameter value.
n Last Failure Parameter [4] contains the SIP last failure code value.
n Last Failure Parameter [5] contains the EXEC$BUGCHECK call last failure code
value.

01150106

A bugcheck occurred before subsystem initialization completed.
n Last Failure Parameter [0] contains the executive flags value.
n Last Failure Parameter [1] contains the RIP from the bugcheck call stack.
n Last Failure Parameter [2] contains the first SIP last failure parameter value.
n Last Failure Parameter [3] contains the second SIP last failure parameter value.
n Last Failure Parameter [4] contains the SIP last failure code value.
n Last Failure Parameter [5] contains the EXEC$BUGCHECK call last failure code
value.

D–40

HSG80 User’s Guide

Table D–3
Code

Last Failure Codes (Continued)
Description

01160108

The I960 reported a machine fault (parity error).
n Last Failure Parameter [0] contains the RESERVED value.
n Last Failure Parameter [1] contains the access type value.
n Last Failure Parameter [2] contains the access address value.
n Last Failure Parameter [3] contains the number of faults value.
n Last Failure Parameter [4] contains the PC value.
n Last Failure Parameter [5] contains the AC value.
n Last Failure Parameter [6] contains the fault type and subtype values.
n Last Failure Parameter [7] contains the RIP value.

01170108

The I960 reported a machine fault (parity error) while an NMI was being processed.
n Last Failure Parameter [0] contains the RESERVED value.
n Last Failure Parameter [1] contains the access type value.
n Last Failure Parameter [2] contains the access address value.
n Last Failure Parameter [3] contains the number of faults value.
n Last Failure Parameter [4] contains the PC value.
n Last Failure Parameter [5] contains the AC value.
n Last Failure Parameter [6] contains the fault type and subtype values.
n Last Failure Parameter [7] contains the RIP value.

01180105

A machine fault (parity error) occurred during EXEC$BUGCHECK processing.
n Last Failure Parameter [0] contains the executive flags value.
n Last Failure Parameter [1] contains the RIP from the machine fault stack.
n Last Failure Parameter [2] contains the read diagnostic register 0 value.
n Last Failure Parameter [3] contains the FX Chip CSR value.
n Last Failure Parameter [4] contains the SIP last failure code value.

011B0108

The I960 reported a machine fault (nonparity error).
n Last Failure Parameter [0] contains the Fault Data (2) value.
n Last Failure Parameter [1] contains the Fault Data (1) value.
n Last Failure Parameter [2] contains the Fault Data (0) value.
n Last Failure Parameter [3] contains the Number of Faults value.
n Last Failure Parameter [4] contains the PC value.
n Last Failure Parameter [5] contains the AC value.
n Last Failure Parameter [6] contains the Fault Flags, Type and Subtype values.
n Last Failure Parameter [7] contains the RIP value (actual).

Event Reporting: Templates and Codes

Table D–3

D–41

Last Failure Codes (Continued)

Code

Description

011C0011

Controller execution terminated via display of solid fault code in OCP LEDs. Note
that upon receipt of this Last Failure in a last gasp message the other controller in a
dual controller configuration will inhibit assertion of the KILL line.
n Last Failure Parameter [0] contains the OCP LED solid fault code value.

018000A0

A powerfail interrupt occurred.

018600A0

A processor interrupt was generated with an indication that the other controller in a
dual controller configuration asserted the KILL line to disable this controller.

018700A0

A processor interrupt was generated with an indication that the (//) RESET button on
the controller module was depressed.

018800A0

A processor interrupt was generated with an indication that the program card was
removed.

018900A0

A processor interrupt was generated with an indication that the controller inactivity
watch dog timer expired.

018E2582

A NMI interrupt was generated with an indication that a memory system problem
occurred.
n Last Failure Parameter [0] contains the memory controller register address which
encountered the error.
n Last Failure Parameter [1] contains the memory controller’s Command Status
Register value.

018F2087

A NMI interrupt was generated with an indication that a controller system problem
occurred.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains PCI status. Bits 31::24 hold PCFX PSCR
status and bits 15::08 hold PLX PSCR status.
n Last Failure Parameter [3] contains the PCFX PDAL control/status register.
n Last Failure Parameter [4] contains the IBUS address of error register.
n Last Failure Parameter [5] contains the previous PDAL address of error register.
n Last Failure Parameter [6] contains the current PDAL address of error register.

01902080

The PCI bus on the controller will not allow a master to initiate a transfer. Unable to
provide further diagnosis of the problem.

D–42

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

01910084

A Cache Module was inserted or removed.
n Last Failure Parameter [0] contains the value of actual Cache Module A exists
state.
n Last Failure Parameter [1] contains the value of actual Cache Module B exists
state.
n Last Failure Parameter [2] contains the value of expected Cache Module A exists
state.
n Last Failure Parameter [3] contains the value of expected Cache Module B exists
state.

01920186

Unable to read the FX because a Device Port or a Host Port locked the PDAL bus.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of read diagnostic register 2.
n Last Failure Parameter [3] contains the value of write diagnostic register 0.
n Last Failure Parameter [4] contains the value of write diagnostic register 1.
n Last Failure Parameter [5] contains the IBUS address of error register.

01932588

An error has occurred on the CDAL.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of write diagnostic register 0.
n Last Failure Parameter [3] contains the value of write diagnostic register 1.
n Last Failure Parameter [4] contains the IBUS address of error register.
n Last Failure Parameter [5] contains the PCFX CDAL control / status register.
n Last Failure Parameter [6] contains the previous CDAL address of error register.
n Last Failure Parameter [7] contains the current CDAL address of error register.

01942088

An error has occurred on the PDAL.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of write diagnostic register 0.
n Last Failure Parameter [3] contains the value of write diagnostic register 1.
n Last Failure Parameter [4] contains the IBUS address of error register.
n Last Failure Parameter [5] contains the PCFX PDAL control / status register.
n Last Failure Parameter [6] contains the previous PDAL address of error register.
n Last Failure Parameter [7] contains the current PDAL address of error register.

Event Reporting: Templates and Codes

Table D–3

D–43

Last Failure Codes (Continued)

Code

Description

01950188

An error has occurred that caused the FX to be rest, when not permissible.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of write diagnostic register 0.
n Last Failure Parameter [3] contains the value of write diagnostic register 1.
n Last Failure Parameter [4] contains the IBUS address of error register.
n Last Failure Parameter [5] contains the PCFX PDAL control / status register.
n Last Failure Parameter [6] contains the PCFX CDAL control / status register.
n Last Failure Parameter [7] contains the current PDAL address of error register.

01960186

The Ibus is inaccessible.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of read diagnostic register 2.
n Last Failure Parameter [3] contains the value of write diagnostic register 0.
n Last Failure Parameter [4] contains the value of write diagnostic register 1.
n Last Failure Parameter [5] contains the IBUS address of error register.

01970188

Software indicates all NMI causes cleared, but some remain.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of read diagnostic register 2.
n Last Failure Parameter [3] contains the value of write diagnostic register 0.
n Last Failure Parameter [4] contains the value of write diagnostic register 1.
n Last Failure Parameter [5] contains the IBUS address of error register.
n Last Failure Parameter [6] contains the PCFX PDAL control / status register.
n Last Failure Parameter [7] contains the PCFX CDAL control / status register.

01982087

The Ibus encountered a parity error.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of read diagnostic register 2.
n Last Failure Parameter [3] contains the value of write diagnostic register 0.
n Last Failure Parameter [4] contains the value of write diagnostic register 1.
n Last Failure Parameter [5] contains the IBUS address of error register.
n Last Failure Parameter [6] contains the RIP.

D–44

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

01992088

An error was detected by the PLX.
n Last Failure Parameter [0] contains the value of read diagnostic register 0.
n Last Failure Parameter [1] contains the value of read diagnostic register 1.
n Last Failure Parameter [2] contains the value of write diagnostic register 0.
n Last Failure Parameter [3] contains the value of write diagnostic register 1.
n Last Failure Parameter [4] contains the IBUS address of error register.
n Last Failure Parameter [5] contains the PLX status register.
n Last Failure Parameter [6] contains the previous PDAL address of error register.
n Last Failure Parameter [7] contains the RIP.

02010100

Initialization code was unable to allocate enough memory to set up the send data
descriptors.

02040100

Unable to allocate memory necessary for data buffers.

02050100

Unable to allocate memory for the Free Buffer Array.

02080100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
populating the disk read DWD stack.

02090100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
populating the disk write DWD stack.

020C0100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
populating the miscellaneous DWD stack.

02100100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
creating the device services state table.

02170100

Unable to allocate memory for the Free Node Array.

021D0100

Unable to allocate memory for the Free Buffer Array.

021F0100

Unable to allocate memory for WARPs and RMDs.

02210100

Invalid parameters in CACHE$OFFER_META call.

02220100

No buffer found for CACHE$MARK_META_DIRTY call.

02270104

A callback from DS on a transfer request has returned a bad or illegal DWD status.
n Last Failure Parameter [0] contains the DWD Status.
n Last Failure Parameter [1] contains the DWD address.
n Last Failure Parameter [2] contains the PUB address.
n Last Failure Parameter [3] contains the Device Port.

Event Reporting: Templates and Codes

Table D–3

D–45

Last Failure Codes (Continued)

Code

Description

022C0100

A READ_LONG operation was requested for a Local Buffer Transfer. READ_LONG
is not supported for Local Buffer Transfers.

022D0100

A WRITE_LONG operation was requested for a Local Buffer Transfer.
WRTE_LONG is not supported for Local Buffer Transfers.

023A2084

A processor interrupt was generated by the controller’s XOR engine (FX), indicating
an unrecoverable error condition.
n Last Failure Parameter [0] contains the FX Control and Status Register (CSR).
n Last Failure Parameter [1] contains the FX DMA Indirect List Pointer register
(DILP).
n Last Failure Parameter [2] contains the FX DMA Page Address register
(DADDR).
n Last Failure Parameter [3] contains the FX DMA Command and control register
(DCMD).

02440100

The logical unit mapping type was detected invalid in va_set_disk_geometry()

02530102

An invalid status was returned from CACHE$LOOKUP_LOCK().
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

02560102

An invalid status was returned from CACHE$LOOKUP_LOCK().
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

02570102

An invalid status was returned from VA$XFER() during an operation.
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

025A0102

An invalid status was returned from CACHE$LOOKUP_LOCK().
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

02620102

An invalid status was returned from CACHE$LOOKUP_LOCK().
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

02690102

An invalid status was returned from CACHE$OFFER_WRITE_DATA().
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

D–46

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

027B0102

An invalid status was returned from VA$XFER() in a complex ACCESS operation.
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

027D0100

Unable to allocate memory for a Failover Control Block.

027E0100

Unable to allocate memory for a Failover Control Block.

027F0100

Unable to allocate memory for a Failover Control Block.

02800100

Unable to allocate memory for a Failover Control Block.

02840100

Unable to allocate memory for the XNode Array.

02860100

Unable to allocate memory for the Fault Management Event Information Packet used
by the Cache Manager in generating error logs to the host.

02880100

Invalid FOC Message in cmfoc_snd_cmd.

028A0100

Invalid return status from DIAG$CACHE_MEMORY_TEST.

028B0100

Invalid return status from DIAG$CACHE_MEMORY_TEST.

028C0100

Invalid error status given to cache_fail.

028E0100

Invalid DCA state detected in init_crashover.

02910100

Invalid metadata combination detected in build_raid_node.

02920100

Unable to handle that many bad dirty pages (exceeded MAX_BAD_DIRTY). Cache
memory is bad.

02930100

There was no free or freeable buffer to convert bad metadata or to borrow a buffer
during failover of bad dirty.

02940100

A free Device Correlation Array entry could not be found during write-back cache
failover.

02950100

Invalid DCA state detected in start_crashover.

02960100

Invalid DCA state detected in start_failover.

02970100

Invalid DCA state detected in init_failover.

02990100

A free RAID Correlation Array entry could not be found during write-back cache
failover.

Event Reporting: Templates and Codes

Table D–3

D–47

Last Failure Codes (Continued)

Code

Description

029A0100

Invalid cache buffer metadata detected while scanning the Buffer Metadata Array.
Found a page containing dirty data but the corresponding Device Correlation Array
entry does exist.

029D0100

Invalid metadata combination detected in build_bad_raid_node.

029F0100

The Cache Manager software has insufficient resources to handle a buffer request
pending.

02A00100

VA change state is trying to change device affinity and the cache has data for this
device.

02A10100

Pubs not one when transportable

02A20100

Pubs not one when transportable

02A30100

No available data buffers. If the cache module exists then this is true after testing the
whole cache. Otherwise there were no buffers allocated from BUFFER memory on the
controller module.

02A40100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
allocating VAXDs.

02A50100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
allocating DILPs.

02A60100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
allocating Change State Work Items.

02A70100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
allocating VA Request Items.

02A90100

Too many pending FOC$SEND requests by the Cache Manager. Code is not designed
to handle more than one FOC$SEND to be pending because there’s no reason to
expect more than one pending.

02AA0100

An invalid call was made to CACHE$DEALLOCATE_CLD. Either that device had
dirty data or it was bound to a RAIDset.

02AB0100

An invalid call was made to CACHE$DEALLOCATE_SLD. A RAIDset member
either had dirty data or write-back already turned on.

02AC0100

An invalid call was made to CACHE$DEALLOCATE_SLD. The RAIDset still has
data (strip nodes).

D–48

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

02AD0180

The FX detected a compare error for data that was identical. This error has always
previously occurred due to a hardware problem.

02AE0100

The mirrorset member count and individual member states are inconsistent.
Discovered during a mirrorset write or erase.

02AF0102

An invalid status was returned from VA$XFER() in a write operation.
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

02B00102

An invalid status was returned from VA$XFER () in an erase operation.
n Last Failure Parameter [0] contains the DD address.
n Last Failure Parameter [1] contains the invalid status.

02B10100

A mirrorset read operation was received and the round robin selection algorithm found
no normal members in the mirrorset. Internal inconsistency.

02B20102

An invalid status was returned from CACHE$LOCK_READ during a mirror copy
operation.
n Last Failure Parameter[0] contains the DD address.
n Last Failure Parameter[1] contains the invalid status.

02B30100

CACHE$CHANGE_MIRROR_MODE invoked illegally (cache bad, dirty data still
resident in the cache.)

02B90100

Invalid code loop count attempting to find the Cache ID Blocks.

02BD0100

A mirrorset metadata online operation found no normal members in the mirrorset.
Internal inconsistency.

02BE0100

No free pages in the other cache. In performing mirror cache failover, a bad page was
found, and an attempt was made to recover the data from the good copy (primary/
mirror), but no free good page was found on the other cache to copy the data to.

02BF0100

Report_error routine encountered an unexpected failure status returned from
DIAG$LOCK_AND_TEST_CACHE_B.

02C00100

Copy_buff_on_this routine expected the given page to be marked bad and it wasn’t.

02C10100

Copy_buff_on_other routine expected the given page to be marked bad and it wasn’t.

02C30100

CACHE$CREATE_MIRROR was invoked by C_SWAP under unexpected conditions
(e.g., other controller not dead, bad lock state).

02C60100

Mirroring transfer found CLD with writeback state OFF.

Event Reporting: Templates and Codes

Table D–3

D–49

Last Failure Codes (Continued)

Code

Description

02C70100

Bad BBR offsets for active shadowset, detected on write.

02C80100

Bad BBR offsets for active shadowset, detected on read.

02C90100

Illegal call made to CACHE$PURGE_META when the storageset was not quiesced.

02CA0100

Illegal call made to VA$RAID5_META_READ when another read (of metadata) is
already in progress on the same strip.

02CB0000

A restore of the configuration has been done. This cleans up and restarts with the new
configuration.

02CC0100

On an attempt, which is not allowed to fail, to allocate a cache node, no freeable cache
node was found.

02D00100

Not all alter_device requests from VA_SAVE_CONFIG completed within the timeout
interval.

02D30100

The controller has insufficient memory to allocate enough data structures used to
manage metadata operations.

02D60100

An invalid storage set type was specified for metadata initialization.

02D90100

Bad CLD pointer passed setwb routine.

02DA0100

A fatal logic error occurred while trying to restart a stalled data transfer stream.

02DB0100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
populating the disk read PCX DWD stack.

02DC0100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
populating the disk write PCX DWD stack.

02DD0101

The VA state change deadman timer expired, and at least one VSI was still interlocked.
n Last Failure Parameter [0] contains the nv_index.

02DE0100

An attempt to allocate memory for a null pub failed to get the memory.

02DF0101

License identified in Last Failure Parameter [0] was not forced valid.

02E00180

Mirror functionality is broken.

D–50

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

02E11016

While attempting to restore saved configuration information, data for two unrelated
controllers was found. The restore code is unable to determine which disk contains the
correct information. The Port/Target/LUN information for the two disks is contained
in the parameter list. Remove the disk containing the incorrect information, reboot the
controller, and issue the SET THIS_CONTROLLER INITIAL_CONFIGURATION
command. When the controller reboots, the proper configuration will be loaded.
n Last Failure Parameter [0] contains the first disk port.
n Last Failure Parameter [1] contains the first disk target.
n Last Failure Parameter [2] contains the first disk LUN.
n Last Failure Parameter [3] contains the second disk port.
n Last Failure Parameter [4] contains the second disk target.
n Last Failure Parameter [5] contains the second disk LUN.

02E20100

An attempt to allocate a va_cs_work item from the S_va_free_cs_work_queue failed.

02E30100

An attempt to allocate a free VAR failed.

02E40100

An attempt to allocate a free VAR failed.

O2E50100

An attempt to allocate a free VAR failed.

02E60100

An attempt to allocate a free VAR failed.

02E70100

An attempt to allocate a free VAR failed.

02E80100

An attempt to allocate a free VAR failed.

02E90100

An attempt to allocate a free VAR failed.

02EA0100

An attempt to allocate a free VAR failed.

02EB0100

An attempt to allocate a free metadata WARP failed.

02EC0101

An online request was received for a unit when both controllers had dirty data for the
unit. The crash is to allow the surviving controller to copy over all of the dirty data.
Last Failure Parameter [0] contains the nv_index of the unit.

02ED0100

On an attempt, which is not allowed to fail, to allocate a BDB, no freeable BDB was
found.

02EE0102

A CLD is already allocated when it should be free.
n Last Failure Parameter [0] contains the requesting entity.

Last Failure Parameter [1] contains the CLD index.

Event Reporting: Templates and Codes

Table D–3

Last Failure Codes (Continued)

Code
02EF0102

D–51

Description
A CLD is free when it should be allocated.
n Last Failure Parameter [0] contains the requesting entity.

Last Failure Parameter [1] contains the CLD index.

02F00100

The controller has insufficient free resources for the configuration restore process to
obtain a facility lock.

02F10102

The configuration restore process encountered an unexpected non-volatile parameter
store format. The process cannot restore from this version.
n Last Failure Parameter [0] contains the version found.

Last Failure Parameter [1] contains the expected version.

02F20100

The controller has insufficient free resources for the configuration restore process to
release a facility lock.

02F34083

A device read operation failed during the configuration restore operation. The
controller is crashed to prevent possible loss of saved configuration information on
other functioning devices.
n Last Failure Parameter [0] contains the disk port.

n
n

02F44083

Last failure Parameter [2] contains the disk LUN.

The calculated error detection code on the saved configuration information is bad. The
controller is crashed to prevent destruction of other copies of the saved configuration
information. Remove the device with the bad information and retry the operation.
n Last Failure Parameter [0] contains the disk port.

n
n
02F54083

Last Failure Parameter [1] contains the disk target.

Last Failure Parameter [1] contains the disk target.
Last Failure Parameter [2] contains the disk LUN.

The device saved configuration information selected for the restore process is from an
unsupported controller type. Remove the device with the unsupported information and
retry the operation.
n Last Failure Parameter [0] contains the disk port.
n Last Failure Parameter [1] contains the disk target.
n Last Failure Parameter [2] contains the disk LUN.

D–52

HSG80 User’s Guide

Table D–3
Code
02F60103

Last Failure Codes (Continued)
Description
An invalid modification to the no_interlock VSI flag was attempted.
n Last Failure Parameter [0] contains the nv_index of the config on which the
problem was found.
n Last Failure Parameter [1] contains modification flag.
n Last Failure Parameter [2] contains the current value of the no_interlock flag.
If the modification flag is 1, then an attempt was being made to set the no_interlock
flag, and the no_interlock flag was not clear at the time. If the modification flag is 0,
then an attempt was being made to clear the no_interlock flag, and the no_interlock
flag was not set (== 1) at the time.

02F70100

During boot testing, one or more device ports (SCSI) were found to be bad. Due to a
problem in the SYMBIOS 770 chip, the diagnostic may occasionally fail the port even
though the hardware is OKAY. A reboot should clear up the problem. If the port is
actually broken, logic to detect a loop that repeatedly causes the same bugcheck will
cause a halt.

02F80103

An attempt was made to bring a unit online when the cache manager says that a
member CLD was not in the appropriate state.
n Last Failure Parameter [0] contains the nv_index of the config on which the
problem was found.
n Last Failure Parameter [1] contains the map type of that config.
n Last Failure Parameter [2] contains the value from CACHE$CHECK_CID that
was not acceptable.

02F90100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
allocating structures for read ahead caching.

02FA0100

A read ahead caching data structure (RADD) is inconsistent.

02FB2084

Event Reporting: Templates and Codes

Table D–3

D–53

Last Failure Codes (Continued)

Code

Description

02FC0180

The FX detected a compare error for data that was identical. This error has always
previously occurred due to a hardware problem.

02FD0100

The controller has insufficient free memory to restore saved configuration information
from disk.

02FE0105

A field in the VSI was not cleared when an attempt was made to clear the interlock.
n Last Failure Parameter [0] contains the NV index of the VSI on which the
problem was found.
n Last Failure Parameter [1] contains the contents of the enable_change field of the
VSI, which should be zero.
n Last Failure Parameter [2] contains the contents of the desired_state field of the
VSI, which should be zero.
n Last Failure Parameter [3] contains the contents of the completion_routine field of
the VSI, which should be zero.
n Last Failure Parameter [4] contains the contents of the open_requests field of the
VSI, which should be zero.

03010100

Failed request for port-specific scripts memory allocation.

03020101

Invalid SCSI direct-access device opcode in misc command DWD.
n Last Failure Parameter [0] contains the SCSI command opcode.

03040101
03060101
03070101

Invalid SCSI CDROM device opcode in misc command DWD.
Last Failure Parameter [0] contains the SCSI command opcode.

Invalid SCSI device type in PUB.
Last Failure Parameter [0] contains the SCSI device type.

Invalid CDB Group Code detected during create of misc cmd DWD
Last Failure Parameter [0] contains the SCSI command opcode.

03080101

Invalid SCSI OPTICAL MEMORY device opcode in misc command DWD.
n Last Failure Parameter [0] contains the SCSI command opcode.

03090101

Failed request for allocation of pci miscellaneous block Last Failure Parameter [0]
contains the failed dwd command class.

030A0100

Error DWD not found in port in_proc_q.

D–54

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

030B0188

A dip error was detected when pcb_busy was set.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the new info NULL-SSTAT0-DSTAT-ISTAT.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

031E0100

Can’t find in_error dwd on in-process queue.

031F0100

Either DWD_ptr is null or bad value in dsps.

03280100

SCSI CDB contains an invalid group code for a transfer command.

03290100

The required Event Information Packet (EIP) or Device Work Descriptor (DWD) were
not supplied to the Device Services error logging code.

032B0100

A Device Work Descriptor (DWD) was supplied with a NULL Physical Unit Block
(PUB) pointer.

03320101

An invalid code was passed to the error recovery thread in the error_stat field of the
PCB.
n Last Failure Parameter[0] contains the PCB error_stat code.

Event Reporting: Templates and Codes

Table D–3

D–55

Last Failure Codes (Continued)

Code

Description

03330188

A parity error was detected by a device port while sending data out onto the SCSI bus.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

03350188

The TEA (bus fault) signal was asserted into a device port.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

D–56

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

03370108

A device port detected an illegal script instruction.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

03380188

A device port’s DSTAT register contains multiple asserted bits, or an invalidily
asserted bit, or both.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

Event Reporting: Templates and Codes

Table D–3

D–57

Last Failure Codes (Continued)

Code

Description

03390108

An unknown interrupt code was found in a device port’s DSPS register.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

033C0101

An invalid code was seen by the error recovery thread in the er_funct_step field of the
PCB.
n Last Failure Parameter [0] contains the PCB er_funct_step code.

033E0108

An attempt was made to restart a device port at the SDP DBD.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

D–58

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

033F0108

An EDC error was detected on a read of a soft-sectored device path not yet
implemented.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copy of the device port TEMP
register.
n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
n Last Failure Parameter [3] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [5] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [6] contains the PCB copies of the device port SSTAT2/
SSTAT1/SSTAT0/DSTAT registers.
n Last Failure Parameter [7] contains the PCB copies of the device port LCRC/
RESERVED/ISTAT/DFIFO registers.

03410101

Invalid SCSI device type in PUB.
n Last Failure Parameter [0] contains the PUB SCSI device type.

03450188

A Master Data Parity Error was detected by a port.
n Last Failure Parameter [0] contains the PCB port_ptr value.
n Last Failure Parameter [1] contains the PCB copies of the device port DCMD/
DBC registers.
n Last Failure Parameter [2] contains the PCB copy of the device port DNAD
register.
n Last Failure Parameter [3] contains the PCB copy of the device port DSP register.
n Last Failure Parameter [4] contains the PCB copy of the device port DSPS
register.
n Last Failure Parameter [5] contains the PCB copies of the device port DSTAT/
SSTAT0/SSTAT1/SSTAT2 registers.
n Last Failure Parameter [6] contains the PCB copies of the device port DFIFO/
ISTAT/SBCL/RESERVED registers.
n Last Failure Parameter [7] contains the PCB copies of the device port SIST0/
SIST1/SXFER/SCNTL3 registers.

03470100

Insufficient memory available for target block allocation.

03480100

Insufficient memory available for device port info block allocation.

03490100

Insufficient memory available for autoconfig buffer allocation.

Event Reporting: Templates and Codes

Table D–3

D–59

Last Failure Codes (Continued)

Code

Description

034A0100

Insufficient memory available for PUB allocation.

034B0100

Insufficient memory available for DS init buffer allocation.

034C0100

Insufficient memory available for static structure allocation.

034D0100

DS init DWDs exhausted.

034E2080

Diagnostics report all device ports are broken.

034F0100

Insufficient memory available for reselect target block allocation.

03500100

Insufficient memory available for command disk allocation.

03520100

A failure resulted when an attempt was made to allocate a DWD for use by DS CDI.

035A0100

Invalid SCSI message byte passed to DS.

035B0100

Insufficient DWD resources available for SCSI message passthrough.

03640100

Processing run_switch disabled for LOGDISK associated with the other controller.

03650100

Processing pub unblock for LOGDISK associated with the other controller.

03660100

No memory available to allocate pub to tell the other controller of reset to one if its
LUNs

03670100

No memory available to allocate pub to tell the other controller of a BDR to one if its
LUNs

036F0101

Either send_sdtr or send_wdtr flag set in a non-miscellaneous DWD.
n Last Failure Parameter [0] contains the invalid command class type.

03780181

In ds_get_resume_addr, the buffer address is non-longword aligned for FX access.
n Last Failure Parameter [0] contains the re-entry dbd address value.

03820100

Failed request for mapping table memory allocation.

03830100

Failed request pci 875 block memory allocation.

03850101

ds_alloc_mem called with invalid memory type Last Failure Parameter [0] contains
the invalid memory type.

03860100

ds_alloc_mem was unable to get requested memory allocated: NULL pointer returned.

038C0100

Insufficient memory available for completion dwd array allocation.

D–60

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

03980100

Failed to allocate expandable EMU static work structures.

03990100

Failed to allocate expandable EMU work entry.

039A0100

Failed to allocate expandable EMU FOC work entry.

039B0100

EMU request work queue corrupted.

039C0100

EMU response work queue corrupted.

039D0100

EMU work queue corrupted.

039E0100

EMU foc request work queue corrupted.

039F0100

EMU foc response work queue corrupted.

03A08093

A configuration or hardware error was reported by the EMU.
n Last Failure Parameter [0] contains the solid OCP pattern which identifies the
type of problem encountered.
n Last Failure Parameter [1] contains the cabinet ID reporting the problem.
n Last Failure Parameter [2] contains the SCSI Port number where the problem
exists (if port-specific).

03A28193

The EMU reported Terminator Power out of range.
n Last Failure Parameter [0] contains a bit mask indicating which SCSI Port
number(s) where the problem exists for cab 0. Bit 0 set indicates SCSI Port 1, Bit
1 set indicates SCSI port 2, etc.
n Last Failure Parameter [1] contains a bit mask indicating which SCSI Port
number(s) where the problem exists for cab 2.
n Last Failure Parameter [2] contains a bit mask indicating which SCSI Port
number(s) where the problem exists for cab 3.

04010101

The requester id component of the instance code passed to FM$REPORT_EVENT is
larger than the maximum allowed for this environment.
n Last Failure Parameter[0] contains the instance code value.

04020102

The requester’s error table index passed to FM$REPORT_EVENT is larger than the
maximum allowed for this requester.
n Last Failure Parameter[0] contains the instance code value.
n Last Failure Parameter[1] contains the requester error table index value.

Event Reporting: Templates and Codes

Table D–3

D–61

Last Failure Codes (Continued)

Code

Description

04030102

The USB index supplied in the Event Information Packet (EIP) is larger than the
maximum number of USBs.
n Last Failure Parameter[0] contains the instance code value.
n Last Failure Parameter[1] contains the USB index value.

04040103

The event log format found in V_fm_template_table is not supported by the Fault
Manager. The bad format was discovered while trying to fill in a supplied Event
Information Packet (EIP).
n Last Failure Parameter[0] contains the instance code value.
n Last Failure Parameter[1] contains the format code value.
n Last Failure Parameter[2] contains the requester error table index value.

04050100

The Fault Manager could not allocate memory for its Event Information Packet (EIP)
buffers.

040A0100

The caller of FM$CANCEL_SCSI_DE_NOTIFICATION passed an address of a
deferred error notification routine which doesn’t match the address of any routines for
which deferred error notification is enabled.

040E0100

FM$ENABLE_DE_NOTIFICATION was called to enable deferred error notification
but the specified routine was already enabled to receive deferred error notification.

040F0102

The Event Information Packet (EIP)->generic.mscp1.flgs field of the EIP passed to
FM$REPORT_EVENT contains an invalid flag.
n Last Failure Parameter[0] contains the instance code value.

Last Failure Parameter[1] contains the value supplied in the Event Information
Packet (EIP)->generic.mscp1.flgs field.

04100101

Unexpected template type found during fmu_display_errlog processing.
n Last Failure Parameter[0] contains the unexpected template value.

04110101

Unexpected instance code found during fmu_memerr_report processing.
n Last Failure Parameter[0] contains the unexpected instance code value.

04120101
04140103

CLIB$SDD_FAO call failed.
Last Failure Parameter[0] contains the failure status code value.

The template value found in the eip is not supported by the Fault Manager. The bad
template value was discovered while trying to build an esd.
n Last Failure Parameter [0] contains the instance code value.
n Last Failure Parameter [1] contains the template code value.
n Last Failure Parameter [2] contains the requester error table index value.

D–62

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

05010100

In recursive_nonconflict could not get enough memory for scanning the keyword
tables for configuration name conflicts.

06010100

The DUART was unable to allocate enough memory to establish a connection to the
CLI.

06020100

A port other than terminal port A was referred to by a set terminal characteristics
command. This is illegal.

06030100

A DUP question or default question message type was passed to the DUART driver,
but the pointer to the input area to receive the response to the question was NULL.

06040100

Attempted to detach unattached maintenance terminal.

06050100

Attempted output to unattached maintenance terminal.

06060100

Attempted input from output only maintenance terminal service.

06070100

The DUART was unable to allocate enough memory for its input buffers

06080000

Controller was forced to restart due to entry of a CNTRL-K character on the
maintenance terminal.

07010100

All available slots in the FOC notify table are filled.

07020100

FOC$CANCEL_NOTIFY() was called to disable notification for a rtn that did not
have notification enabled.

07030100

Unable to start the Failover Control Timer before main loop.

07040100

Unable to restart the Failover Control Timer.

07050100

Unable to allocate flush buffer.

07060100

Unable to allocate active receive fcb.

07070100

The other controller killed this, but could not assert the kill line because nindy on or in
debug. So it killed this now.

07080000

The other controller crashed, so this one must crash too.

07090100

A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when
allocating VA Request Items.

08010101

A remote state change was received from the FOC thread that NVFOC does not
recognize.
n Last Failure Parameter[0] contains the unrecognized state value.

Event Reporting: Templates and Codes

Table D–3
Code

D–63

Last Failure Codes (Continued)
Description

08020100

No memory could be allocated for a NVFOC information packet.

08030101

Work received on the S_nvfoc_bque did not have a NVFOC work id.
n Last Failure Parameter[0] contains the id type value that was received on the
NVFOC work queue.

08040101

Unknown work value received by the S_nvfoc_bque.
n Last Failure Parameter[0] contains the unknown work value.

08060100

A really write command was received when the NV memory was not locked.

08070100

A write to NV memory was received while not locked.

08080000

The other controller requested this controller to restart.

08090010

The other controller requested this controller to shutdown.

080A0000

The other controller requested this controller to selftest.

080B0100

Could not get enough memory to build a FCB to send to the remote routines on the
other controller.

080C0100

Could not get enough memory for FCBs to receive information from the other
controller.

080D0100

Could not get enough memory to build a FCB to reply to a request from the other
controller.

080E0101

An out-of-range receiver ID was received by the NVFOC communication utility
(master send to slave send ACK). Last Failure Parameter[0] contains the bad id value.

080F0101

An out-of-range receiver ID was received by the NVFOC communication utility
(received by master). Last Failure Parameter[0] contains the bad id value.

08100101

A call to NVFOC$TRANSACTION had a from field (id) that was out of range for the
NVFOC communication utility.
n Last Failure Parameter [0] contains the bad id value.

08110101

NVFOC tried to defer more than one FOC send. Last Failure Parameter[0] contains
the master ID of the connection that had the multiple delays.

08140100

Could not allocate memory to build a workblock to queue to the NVFOC thread.

08160100

A request to clear the remote configuration was received but the memory was not
locked.

D–64

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

08170100

A request to read the next configuration was received but the memory was not locked.

08180100

Could not get enough memory for FLS FCBs to receive information from the other
controller.

08190100

An unlock command was received when the NV memory was not locked.

081A0100

Unable to allocate memory for remote work.

081B0101

Bad remote work received on remote work queue.
n Last Failure Parameter[0] contains the id type value that was received on the
NVFOC remote work queue.

081C0101

Bad member management work received.
n Last Failure Parameter[0] contains the bad member management value that was
detected.

081D0000

In order to go into mirrored cache mode, the controllers must be restarted.

081E0000

In order to go into nonmirrored cache mode, the controllers must be restarted.

081F0000

An FLM$INSUFFICIENT_RESOURCES error was returned from a FLM lock or
unlock call.

08200000

Expected restart so the write_instance may recover from a configuration mismatch.

08210100

Unable to allocate memory to setup NVFOC lock/unlock notification routines.

09010100

Unable to acquire memory to initialize the FLM structures.

09640101

Work that was not FLM work was found on the FLM queue. Bad format is detected or
the formatted string overflows the output buffer.
n Last Failure Parameter [0] contains the work found.

09650101
09670101
09680101

Work that was not FLM work was found on the FLM queue.
Last Failure Parameter [0] contains the structure found.

Local FLM detected an invalid facility to act upon.
Last Failure Parameter [0] contains the faciltiy found.

Remote FLM detected an error and requested the local controller to restart.
n Last Failure Parameter [0] contains the reason for the request.

Event Reporting: Templates and Codes

Table D–3

Last Failure Codes (Continued)

Code

Description

09C80101

Remote FLM detected an invalid facility to act upon.
n Last Failure Parameter [0] contains the facility found.

09C90101

Remote FLM detected an invalid work type.
n Last Failure Parameter [0] contains the work type found.

09CA0101

Remote FLM detected an invalid work type.
Last Failure Parameter [0] contains the work type found.

09CB0012

Remote FLM detected that the other controller has a facility lock manager at an
incompatible revision level with this controller.
n Last Failure Parameter [0] contains the controller’s FLM revision.
n Last Failure Parameter [1] contains the other controller’s FLM revision.

0A020100

ILF$CACHE_READY unable to allocate necessary DWDs.

0A030100

ILF$CACHE_READY buffers_obtained > non-zero stack entry count.

0A040100

ILF$CACHE_READY DWD overrun.

0A050100

ILF$CACHE_READY DWD underrun.

0A060100

ILF$CACHE_READY found buffer marked for other controller.

0A070100

CACHE$FIND_LOG_BUFFERS returned continuation handle > 0.

0A080100

Not processing a bugcheck.

0A090100

No active DWD.

0A0A0100

Current entry pointer is not properly aligned.

0A0B0100

Next entry pointer is not properly aligned.

0A0C0100

Next entry was partially loaded.

0A0E0100

Active DWD is not a DISK WRITE DWD as expected.

0A0F0100

New active DWD is not a DISK WRITE DWD as expected.

0A100100

Data buffer pointer is not properly aligned.

0A120100

Data buffer pointer is not properly aligned.

0A130100

Data buffer pointer is not properly aligned.

D–65

D–66

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

0A140100

New entry pointer is not properly aligned.

0A150100

New entry record type is out of range.

0A190102

ilf_depopulate_DWD_to_cache first page guard check failed.
Last Failure Parameter [0] contains the DWD address value
Last Failure Parameter [1] contains the buffer address value.

n
n

0A1C0102

ILF$LOG_ENTRY page guard check failed.
n Last Failure Parameter [0] contains the DWD address value
n Last Failure Parameter [1] contains the buffer address value.

0A1D0102

ILF$LOG_ENTRY page guard check failed.
n Last Failure Parameter [0] contains the DWD address value
n Last Failure Parameter [1] contains the buffer address value.

0A1E0102

ILF$LOG_ENTRY page guard check failed.
n Last Failure Parameter [0] contains the DWD address value
n Last Failure Parameter [1] contains the buffer address value.

0A1F0100

ilf_rebind_cache_buffs_to_DWDs found duplicate buffer for current DWD.

0A200101

Unknown bugcheck code passed to ilf_cache_interface_crash.
n Last Failure Parameter [0] contains the unknown bugcheck code value.

0A210100

ilf_rebind_cache_buffs_to_DWDs found buffer type not IDX_ILF.

0A220100

ilf_rebind_cache_buffs_to_DWDs found buffer DBD index too big.

0A240100

ilf_check_handle_array_edc found ihiea EDC bad.

0A250100

ilf_get_next_handle found no free ihiea entry.

0A260100

ilf_remove_handle could not find specified handle.

0A270100

ilf_depopulate_DWD_to_cache could not find handle for first buffer.

0A280100

ilf_depopulate_DWD_to_cache buffer handle does not match current handle.

0A290100

ilf_rebind_cache_buffs_to_DWDs could not find handle for DWD being rebound.

0A2B0100

ILF$CACHE_READY cache manager did not return multiple of DWD DBDs worth
of buffers.

0A2C0100

ilf_rebind_cache_buffs_to_DWDs page guard check failed.

Event Reporting: Templates and Codes

Table D–3

D–67

Last Failure Codes (Continued)

Code

Description

0A2D0100

ilf_populate_DWD_from_cache buffer stack entry zero or not page aligned.

0A2E0100

ilf_populate_DWD_from_cache returned buffer type not IDX_ILF.

0A2F0100

ilf_rebind_cache_buffs_to_DWDs buffer stack entry not page aligned.

0A300100

ilf_depopulate_DWD_to_cache buffer stack entry zero or not page aligned.

0A310100

ilf_distribute_cache_DWDs active handle count not as expected.

0A320102

ILF$LOG_ENTRY, page guard check failed.
n Last Failure Parameter [0] contains the DWD address value.
n Last Failure Parameter [1] contains the buffer address value.

0A330100

ilf_ouput_error, message_keeper_array full.

0A340101

ilf_output_error, no memory for message display.
n Last Failure Parameter [0] contains the message address value.

0A350100

DWD failed validation.

0B010010

Due to an operator request, the controllers non-volatile configuration information has
been reset to its initial state.

0B020100

The controller has insufficient free memory to allocate a Configuration Manager work
item needed to perform the requested configuration reset.

0B030100

The controller has insufficient free memory to allocate a Configuration Manager work
item needed to perform the requested configuration restore.

0B040100

The controller has insufficient free memory to allocate a Configuration Manager
WWL work item needed to perform the requested World-Wide LUN ID change.

0B050100

More requests to WWL$NOTIFY have been made than can be supported.

0B060100

A call to WWL$UPDATE resulted in the need for another World-Wide LUN ID slot,
and no free slots were available.

0B070100

The controller has insufficient free memory to allocate a Configuration Manager DNN
work item needed to perform the requested Device Nickname change.

0B080100

More requests to DNN$NOTIFY have been made than can be supported.

0B090100

A call to DNN$UPDATE resulted in the need for another Device Nickname slot, and
no free slots were available.

D–68

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

0D000011

The EMU firmware returned a bad status when told to poweroff.
n Last Failure Parameter [0] contains the value of the bad status.

12000103

Two values found not equal.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains the first variable value.
n Last Failure Parameter [2] contains the second variable value.

12010103

Two values found equal.
Last Failure Parameter [0] contains the ASSUME instance address.
Last Failure Parameter [1] contains the first variable value.
Last Failure Parameter [2] contains the second variable value.

n
n
n

12020103

First value found bigger or equal.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains the first variable value.
n Last Failure Parameter [2] contains the second variable value.

12030103

First value found bigger.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains the first variable value.
n Last Failure Parameter [2] contains the second variable value.

12040103

First value found smaller or equal.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains the first variable value.
n Last Failure Parameter [2] contains the second variable value.

12050103

First value found smaller.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains the first variable value.
n Last Failure Parameter [2] contains the second variable value.

12060102

12070102

vsi_ptr->no_interlock not set.
Last Failure Parameter [0] contains the ASSUME instance address.
Last Failure Parameter [1] contains nv_index value.

n
n

vsi_ptr->allocated_this not set.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains nv_index value.

Event Reporting: Templates and Codes

Table D–3
Code

D–69

Last Failure Codes (Continued)
Description

12080102

vsi_ptr->cs_interlocked not set.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains nv_index value.

12090102

Unhandled switch case.
n Last Failure Parameter [0] contains the ASSUME instance address.
n Last Failure Parameter [1] contains nv_index value.

20010100

The action for work on the CLI queue should be CLI_CONNECT,
CLI_COMMAND_IN or CLI_PROMPT. If it isn’t one of these three, this bugcheck
will result.

20020100

The FAO returned a non-successful response. This will only happen if a bad format is
detected or the formatted string overflows the output buffer.

20030100

The type of work received on the CLI work queue wasn’t of type CLI.

20060100

A work item of an unknown type was placed on the CLI’s SCSI Virtual Terminal
thread’s work queue by the CLI.

20080000

This controller requested this controller to restart.

20090010

This controller requested this controller to shutdown.

200A0000

This controller requested this controller to selftest.

200B0100

Could not get enough memory for FCBs to receive information from the other
controller.

200D0101

After many calls to DS$PORT_BLOCKED, we never got a FALSE status back (which
signals that nothing is blocked).
n Last Failure Parameter[0] contains the port number (1 - n) that we were waiting on
to be unblocked.

200E0101

While traversing the structure of a unit, a config_info node was discovered with an
unrecognized structure type.
n Last Failure Parameter[0] contains the structure type number that was
unrecognized.

200F0101

A config_info node was discovered with an unrecognized structure type.
n Last Failure Parameter[0] contains the structure type number that was
unrecognized.

D–70

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

20100101

A config_node of type VA_MA_DEVICE had an unrecognized SCSI device type.
n Last Failure Parameter[0] contains the SCSI device type number that was
unrecognized.

20110100

An attempt to allocate memory so the CLI prompt messages could be deleted failed.

20120101

While traversing the structure of a unit, a config_info node was discovered with an
unrecognized structure type.
n Last Failure Parameter[0] contains the structure type number that was
unrecognized.

20130101

While traversing the structure of a unit, the device was of an unrecognized type.
n Last Failure Parameter[0] contains the SCSI device type that was unrecognized.

20160000

In order to go into mirrored cache mode, the controllers must be restarted.

20160100

Unable to allocate resources needed for the CLI local program.

20170000

In order to go into unmirrored cache mode, the controllers must be restarted.

20190010

A cache state of a unit remains WRITE_CACHE_UNWRITTEN_DATA. The unit is
not ONLINE, thus this state would only be valid for a very short period of time.

201A0100

An attempt to allocate memory so a CLI prompt message could be reformatted failed.

201B0100

Insufficient resources to get memory to lock CLI.

201C0100

Insufficient resources to get memory to unlock CLI.

201D0100

With “set failover copy=other”, the controller which is having the configuration copied
to will automatically be restarted via this bugcheck.

201E0101

CLI$ALLOCATE_STRUCT() was called by a process which it does not support
Last Failure Parameter [0] contains pscb address.

201F0101

CLI$DEALLOCATE_ALL_STRUCT() was called by a process which it does not
support.
n Last Failure Parameter [0] contains pscb address.

20200100

CLI$ALLOCATE_STRUCT() could not obtain memory for a new
nvfoc_rw_remote_nvmem structure.

20220020

This controller requested this subsystem to poweroff.

20230000

A restart of both controllers is required when exiting multibus failover.

Event Reporting: Templates and Codes

Table D–3

D–71

Last Failure Codes (Continued)

Code

Description

20240000

A restart of both controllers is required when entering multibus failover.

20260000

With “set failover copy=other”, the controller which is having the configuration copied
to will automatically be restarted via this bugcheck.

20640000

Nindy was turned on.

20650000

Nindy was turned off.

20692010

To enter dual-redundant mode, both controllers must be of the same type.

206A0000

Controller restart forced by DEBUG CRASH REBOOT command.

206B0010

Controller restart forced by DEBUG CRASH NOREBOOT command.

206C0020

Controller was forced to restart in order for new controller code image to take effect.

206D0000

Controller code load was not completed because the controller could not rundown all
units.

43000100

Encountered an unexpected structure type on hp_work_q.

43030100

Unable to allocate the necessary number of large Sense Data buckets in HPP_init().

43100100

Encountered a NULL completion routine pointer in a DD.

43130100

Could not allocate a large sense bucket.

43160100

A sense data bucket of unknown type (neither LARGE or SMALL) was passed to
deallocate_SDB().

43170100

Call to VA$ENABLE_NOTIFICATION() failed due to
INSUFFICIENT_RESOURCES.

43190100

Unable to allocate necessary memory in HPP_int().

431A0100

Unable to allocate necessary timer memory in HPP_int().

43210101

HPP detected unknown error indicated by HPT.
n Last Failure Parameter [0] contains the error value.

43220100

Unable to obtain Free CSR in HPP().

43230101

During processing to maintain consistency of the data for Persistent Reserve SCSI
commands, an internal inconsistency was detected.
n Last Failure Parameter [0] contains a code defining the precise nature of the
inconsistency.

D–72

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

44640100

Not enough abort requests in the system.

44650100

Exceeded the number of SEST abort retries.

44660100

Unable to allocate enough abort requests for Fibre Channel Host Port Transport
software layer.

44670100

Unable to allocate enough command HTBs for Fibre Channel Host Port Transport
software layer.

44680100

Unable to allocate enough FC HTBs for Fibre Channel Host Port Transport software
layer.

44690100

Unable to allocate enough work requests for Fibre Channel Host Port Transport
software layer.

446A0100

Unable to allocate enough HTBs for Fibre Channel Host Port Transport software layer.

446B0100

Unable to allocate enough TIS structures for Fibre Channel Host Port Transport
software layer.

446C0100

Unable to allocate enough MFSs for Fibre Channel Host Port Transport software layer.

446D0100

Unable to allocate enough Tachyon headers for Fibre Channel Host port Transport
software layer.

446E0100

Unable to allocate enough EDB structures for Fibre Channel Host Port Tansport
software layer.

446F0100

Unable to allocate enough LSFS structures for Fibre Channel Host Port Transport
software layer.

44700100

Unable to allocate enough TPS structures for Fibre Channel Host Port Transport
software layer.

44720101

An illegal status was returned to the FLOGI command error handler.
n Last Failure Parameter [0] contains error value.

44730101

An illegal completion message was returned by the Tachyon to I960.
Last Failure Parameter [0] contains the completion message type.

44740101

The Host Port Transport process handler received an illegal timer.
n Last Failure Parameter [0] contains the timer pointer. type.

44750100

The Host Port Transport work handler received an illegal work request.

Event Reporting: Templates and Codes

Table D–3

D–73

Last Failure Codes (Continued)

Code

Description

44760100

The Host Port Transport ran out of work requests.

44770102

An illegal script return value was received by the Host Port Transport init script
handler.
n Last Failure Parameter [0] contains the init function.
n Last Failure Parameter [1] contains return value.
The Host Port Transport ran out of work requests.

44780102

An illegal script return value was received by the Host Port Transport send script
handler.
n Last Failure Parameter [0] contains the send function.
n Last Failure Parameter [1] contains return value.
The Host Port Transport ran out of work requests.

44790102

An illegal script return value was received by the Host Port Transport response script
handler.
n Last Failure Parameter [0] contains the rsp function.
n Last Failure Parameter [1] contains return value.
The Host Port Transport ran out of work requests.

447A0102

An illegal script return value was received by the Host Port Transport error script
handler.
n Last Failure Parameter [0] contains the error function.
n Last Failure Parameter [1] contains return value.
The Host Port Transport ran out of work requests.

447B0100

The Host Port Transport response script handler received a response before a
command was sent.

447C0101

Unhandled command HTB status.
n Last Failure Parameter [0] contains the status value.
The Host Port Transport ran out of work requests.

447D0100

The Host Port Transport ran out of command HTBs.

447E0100

The Host Port Transport memory for LOGI parameters.

D–74

HSG80 User’s Guide

Table D–3
Code

Last Failure Codes (Continued)
Description

447F0100

The Host Port Transport memory for LOGI parameters.

44800101

An illegal status was returned to the name service command error handler.
n Last Failure Parameter [0] contains error value.

44810101

An illegal status was returned to the PLOGI command error handler.
n Last Failure Parameter [0] contains error value.

44820101

An illegal abort type was given to the Host Port Transport abort handler.
n Last Failure Parameter [0] contains abort type.

44830101

An illegal failover request was given to the Host Port Transport request handler.
n Last Failure Parameter [0] contains failover request.

44840101

An illegal failover response was given to the Host Port Transport failover response
handler.
n Last Failure Parameter [0] contains failover response.

44850100

The Host Port Transport failover control had a bad send count.

44860100

Unable to allocate enough ESD structures for Fibre Channel Host Port Transport
software layer.

44870101

An illegal abort type was given to the Host Port Transport abort handler.
n Last Failure Parameter [0] contains abort type.

44892091

Host Port Hardware diagnostic field at system initialization.
n Last Failure Parameter [0] contains failed port number.

64000100

Insufficient buffer memory to allocate data structures needed to propagate SCSI Mode
Select changes to other controller.

64010100

During an initialization of LUN specific mode pages, an unexpected device type was
encountered.

64020100

A DD is already in use by a RCV DIAG command - cannot get two RCV_DIAGs
without sending the data for the first.

80010100

An HTB was not available to issue an I/O when it should have been.

80030100

DILX tried to release a facility that wasn’t reserved by DILX.

80040100

DILX tried to change the unit state from MAINTENANCE_MODE to NORMAL but
was rejected because of insufficient resources.

Event Reporting: Templates and Codes

Table D–3

D–75

Last Failure Codes (Continued)

Code

Description

80050100

DILX tried to change the usb unit state from MAINTENANCE_MODE to NORMAL
but DILX never received notification of a successful state change.

80060100

DILX tried to switch the unit state from MAINTENANCE_MODE to NORMAL but
was not successful.

80070100

DILX aborted all cmds via va$d_abort() but the HTBS haven’t been returned.

80090100

DILX received an end msg which corresponds to an op code not supported by DILX.

800A0100

DILX was not able to restart his timer.

800B0100

DILX tried to issue an I/O for an opcode not supported.

800C0100

DILX tried to issue a oneshot I/O for an opcode not supported.

800D0100

A DILX device control block contains an unsupported unit_state.

800F0100

A DILX cmd completed with a sense key that DILX does not support.

80100100

DILX could not compare buffers because no memory was available from
EXEC$ALLOCATE_MEM_ZEROED.

80110100

While DILX was deallocating his deferred error buffers, at least one could not be
found.

80120100

DILX expected an Event Information Packet (EIP) to be on the receive EIP queue but
no EIPs were there.

80130100

DILX was asked to fill a data buffer with an unsupported data pattern.

80140100

DILX could not process an unsupported answer in dx$reuse_params().

80150100

A deferred error was received with an unsupported template.

83020100

An unsupported message type or terminal request was received by the CONFIG virtual
terminal code from the CLI.

83030100

Not all alter_device requests from the CONFIG utility completed within the timeout
interval.

83050100

An unsupported message type or terminal request was received by the CFMENU
utility code from the CLI.

83060100

Not all alter_device requests from the CFMENU utility completed within the timeout
interval.

D–76

HSG80 User’s Guide

Table D–3

Last Failure Codes (Continued)

Code

Description

84010100

An unsupported message type or terminal request was received by the CLONE virtual
terminal code from the CLI.

85010100

HSUTIL tried to release a facility that wasn’t reserved by HSUTIL.

85020100

HSUTIL tried to change the unit state from MAINTENANCE_MODE to NORMAL
but was rejected because of insufficient resources.

85030100

HSUTIL tried to change the usb unit state from MAINTENANCE_MODE to
NORMAL but HSUTIL never received notification of a successful state change.

85040100

HSUTIL tried to switch the unit state from MAINTENANCE_MODE to NORMAL
but was not successful.

86000020

Controller was forced to restart in order for new code load or patch to take effect.

86010010

The controller code load function is about to update the program card. This requires
controller activity to cease. This code is used to inform the other controller this
controller will stop responding to inter-controller communications during card update.
An automatic restart of the controller at the end of the program card update will cause
normal controller activity to resume.

86020011

The EMU firmware returned a bad status when told to prepare for a code load. Last
Failure Parameter [0] contains the value of the bad status.

8A040080

New cache module failed diagnostics. The controller has been reset to clear the error.

8A050080

Could not initialize new cache module. The controller has been reset to clear the error.

8B000186

An single bit error was found by software scrubbing.
n Last Failure Parameter [0] contains the address of the first single bit ecc error
found.
n Last Failure Parameter [1] contains the count of single bit ecc errors found in the
same region below this address.
n Last Failure Parameter [2] contains the lower 32-bits of the actual data read at the
Parameter [0] address.
n Last Failure Parameter [3] contains the higher 32-bits of the actual data read at the
Parameter [0] address.
n Last Failure Parameter [4] contains the lower 32-bits of the expected data at the
Parameter [0] address.
n Last Failure Parameter [5] contains the higher 32-bits of the expected data at the
Parameter [0] address.

Event Reporting: Templates and Codes

D–77

Recommended Repair Action Codes
Recommended Repair Action Codes are embedded in Instance and Last
Failure codes. Refer to “Instance Codes,” page D–16, and “Last Failure
Codes,” page D–36, for a more detailed description of the relationship
between these codes.
Table D–4 contains the repair action codes assigned to each significant
event in the system.
Table D–4

Recommended Repair Action Codes

Code

Description

No action necessary.

An unrecoverable hardware detected fault occurred or an unrecoverable software
inconsistency was detected. Proceed with controller support avenues.

Follow the recommended repair action contained as indicated in the Last Failure Code.

Two possible problem sources are indicated:
In the case of a shelf with dual power supplies, one of the power supplies has failed.
Follow repair action 07 for the power supply with the Power LED out.
n One of the shelf blowers has failed. Follow repair action 06.

Four possible problem sources are indicated:
Total power supply failure on a shelf. Follow repair action 09.
A device inserted into a shelf that has a broken internal SBB connector. Follow repair
action 0A.
n A standalone device is connected to the controller with an incorrect cable. Follow
repair action 08.
n A controller hardware failure. Follow repair action 20.

n
n

Determine which blower has failed and replace it.

Replace power supply.

Replace the cable. Refer to the specific device documentation.

Determine power failure cause.

Determine which SBB has a failed connector and replace it.

D–78

HSG80 User’s Guide

Table D–4

Recommended Repair Action Codes (Continued)

Code
0B

Description
The other controller in a dual-redundant configuration has been reset with the “Kill” line
by the controller that reported the event.
To restart the “Killed” controller enter the CLI command RESTART OTHER on the
“Surviving” controller and then depress the (//) RESET button on the “Killed” controller.
If the other controller is repeatedly being “Killed” for the same or a similar reason, follow
repair action 20.

Both controllers in a dual-redundant configuration are attempting to use the same SCSI
ID (either 6 or 7 as indicated in the event report).
Note that the other controller of the dual-redundant pair has been reset with the “Kill” line
by the controller that reported the event. Two possible problem sources are indicated:
n A controller hardware failure.
n A controller backplane failure.
First, follow repair action 20 for the “Killed” controller. If the problem persists follow
repair action 20 for the “Surviving” controller. If the problem still persists replace the
controller backplane.

The Environmental Monitor Unit has detected an elevated temperature condition. Check
the shelf and its components for the cause of the fault.

The Environmental Monitor Unit has detected an external air-sense fault. Check
components outside of the shelf for the cause of the fault.

An environmental fault previously detected by the Environmental Monitor Unit is now
fixed. This event report is notification that the repair was successful.

Restore on-disk configuration information to original state.

Replace the controller module.

Replace the indicated cache module or the appropriate memory DIMMs on the indicated
cache module.

Replace the indicated write cache battery. CAUTION: BATTERY REPLACEMENT
MAY CAUSE INJURY.

Event Reporting: Templates and Codes

Table D–4

D–79

Recommended Repair Action Codes (Continued)

Code

Description

Check for the following invalid write cache configurations:
n If the wrong write cache module is installed, replace with the matching module or
clear the invalid cache error via the CLI. Refer to Appendix B, “CLI Commands” for
more information.
n If the write cache module is missing, reseat cache if it is actually present, or add the
missing cache module, or clear the invalid cache error via the CLI. Refer to
Appendix B, “CLI Commands” for more details.
n If in a dual-redundant configuration and one of the write cache modules is missing,
match write cache boards with both controllers.

An unrecoverable Memory System failure occurred. Upon restart the controller will
generate one or more Memory System Failure Event Sense Data Responses; follow the
repair action(s) contained therein.

The Memory System Failure translator could not determine the failure cause. Follow
repair action 01.

Replace the indicated cache memory DIMM.

Check that the cache memory DIMMs are properly configured.

This error applies to this controller’s mirrored cache. Since the mirrored cache is
physically located on the other controller’s cache module, replace the other controller’s
cache module, or the appropriate memory DIMMs on the other controller’s cache
module.

This error applies to this controller’s mirrored cache. Since the mirrored cache is
physically located on the other controller’s cache module, replace the indicated cache
memory DIMM on the other controller’s cache module.

Either the primary cache or the mirrored cache has inconsistent data. Check for the
following conditions to determine appropriate means to restore mirrored copies.
n If the mirrored cache is reported as inconsistent and a previous FRU Utility
warmswap of the mirrored cache module was unsuccessful, retry the procedure via
the FRU Utility, by removing the module and re-inserting the same or a new module.
n Otherwise, enter the CLI command SHUTDOWN THIS to clear the inconsistency
upon reboot.

Replace the indicated cache module.

No action necessary, cache diagnostics will determine whether the indicated cache
module is faulty.

D–80

HSG80 User’s Guide

Table D–4
Code

Recommended Repair Action Codes (Continued)
Description

If the Sense Data FRU field is non-zero, follow repair action 41. Otherwise, replace the
appropriate FRU associated with the device’s SCSI interface or the entire device.

Consult the device’s maintenance manual for guidance on replacing the indicated device
FRU.

Update the configuration data to correct the problem.

Replace the SCSI cable for the failing SCSI bus. If the problem persists, replace the
controller backplane, drive backplane, or controller module.

Interpreting the device supplied Sense Data is beyond the scope of the controller’s
firmware. See the device’s service manual to determine the appropriate repair action, if
any.

The RAIDset is inoperative for one or more of the following reasons:
n More than one member malfunctioned. Perform repair action 55.
n More than one member is missing. Perform repair action 58.
n Before reconstruction of a previously replaced member completes another member
becomes missing or malfunctions. Perform repair action 59.
n The members have been moved around and the consistency checks show mismatched
members. Perform repair action 58.

The mirrorset is inoperative for one or more of the following reasons:
n The last NORMAL member has malfunctioned. Perform repair actions 55 and 59.
n The last NORMAL member is missing. Perform repair action 58.
n The members have been moved around and the consistency checks show mismatched
members. Perform repair action 58.

The indicated Storageset member was removed for one of the following reasons:
n The member malfunctioned. Perform repair action 56.
n By operator command. Perform repair action 57.

The STORAGESET may be in a state that prevents the adding of a replacement member,
check the state of the STORAGESET and its associated UNIT and resolve the problems
found before adding the replacement member.

The device may be in a state that prevents adding it as a replacement member or may not
be large enough for the STORAGESET. Use another device for the ADD action and
perform repair action 57 for the device that failed to be added.

Perform the repair actions indicated in any and all event reports found for the devices that
are members of the STORAGESET.

Event Reporting: Templates and Codes

Table D–4

D–81

Recommended Repair Action Codes (Continued)

Code

Description

Perform the repair actions indicated in any and all event reports found for the member
device that was removed from the STORAGESET. Then perform repair action 57.

Delete the device from the FAILEDSET and redeploy, perhaps by adding it to the
SPARESET so it will be available to be used to replace another failing device.

Install the physical devices that are members of the STORAGESET in the proper Port,
Target, and LUN locations.

Delete the STORAGESET, recreate it with the appropriate ADD, INITIALIZE, and ADD
UNIT commands and reload its contents from backup storage.

Restore the MIRRORSET data from backup storage.

The mirrorset is inoperative due to a disaster tolerance failsafe locked condition, as a
result of the loss of all local or remote NORMAL/NORMALIZING members while
ERROR_MODE=FAILSAFE was enabled. To clear the failsafe locked condition, enter
the CLI command SET unit-number ERROR_MODE=NORMAL.

The mirrorset has at least one local NORMAL/NORMALIZING member and one remote
NORMAL/NORMALIZING member. Failsafe error mode can now be enabled by
entering the CLI command SET unit-number ERROR_MODE=FAILSAFE.

An EMU fault has occurred.

The EMU reported terminator power out of range. Replace the indicated I/O module(s).

An EMU (Environmental Monitoring Unit) has become unavailable.
n This EMU Unit (and associated cabinet) may have been removed from the
subsystem; no action is required.
n The cabinet has lost power; restore power to the cabinet.
n The EM- to-EMU communications bus cable has been disconnected or broken;
replace or reconnect the cable to reestablish communications.
n The specified EMU is broken; replace the EMU module.
n The EMU in cabinet 0 is broken; replace the EMU module.

D–82

HSG80 User’s Guide

Component Identifier Codes
Component Identifier Codes are embedded in Instance and Last Failure
codes. Refer to “Instance Codes,” page D–16, and “Last Failure
Codes,” page D–36, for a more detailed description of the relationship
between these codes.
Table D–5 lists the component identifier codes.
Table D–5

Component Identifier Codes

Code

Description

Executive Services

Value Added Services

Device Services

Fault Manager

Common Library Routines

Dual Universal Asynchronous Receiver/Transmitter Services

Failover Control

Nonvolatile Parameter Memory Failover Control

Facility Lock Manager

Integrated Logging Facility

Configuration Manager Process

Memory Controller Event Analyzer

Poweroff Process

Value Added Services (extended)

Command Line Interpreter

Host Port Protocol Layer

Host Port Transport Layer

SCSI Host Value Added Services

Disk Inline Exercise (DILX)

Event Reporting: Templates and Codes

Table D–5

Component Identifier Codes (Continued)

Code

Description

Subsystem Built-In Self Tests (BIST)

Device Configuration Utilities (CONFIG)

Clone Unit Utility (CLONE)

Format and Device Code Load Utility (HSUTIL)

Code Load/Code Patch Utility (CLCP)

Field Replacement Utility (FRUTIL)

Periodic Diagnostics (PDIAG)

D–83

D–84

HSG80 User’s Guide

Event Threshold Codes
Table D–6 lists the classifications for event notification and recovery
threshold values.
Table D–6

Event Notification/Recovery Threshold Classifications

Threshold
Value

Classification

Description

IMMEDIATE

Failure or potential failure of a component critical to proper
controller operation is indicated; immediate attention is required.

HARD

Failure of a component that affects controller performance or
precludes access to a device connected to the controller is
indicated.

SOFT

An unexpected condition detected by a controller firmware
component (e.g., protocol violations, host buffer access errors,
internal inconsistencies, uninterpreted device errors, etc.) or an
intentional restart or shutdown of controller operation is indicated.

INFORMATIONAL

An event having little or no effect on proper controller or device
operation is indicated.

Event Reporting: Templates and Codes

D–85

ASC/ASCQ Codes
Table D–7 lists HSG80-specific SCSI ASC and ASCQ codes. These
codes are Template-specific and appear at byte offsets 12 and 13.
Note Additional codes that are common to all SCSI devices can be
found in the SCSI specification.
Table D–7

ASC and ASCQ Codes

ASC Code

ASCQ Code

Description

Logical unit is disaster tolerant failsafe locked (inoperative).

Test Unit Ready or Read Capacity Command failed

Drive failed by a Host Mode Select command.

Drive failed due to a deferred error reported by drive.

Unrecovered Read/Write error.

No response from one or more drives.

NV memory and drive metadata indicate conflicting drive configurations.

Synchronous Transfer Value differences between drives.

Forced error on Read

No Command control structures available.

Command failed - SCSI ID verification failed.

Data returned from drive is invalid.

Request Sense command to drive failed.

Illegal command for pass through mode.

Data transfer request error.

Premature completion of a drive command.

Drive returned vendor unique sense data.

Last failure event report.

Nonvolatile parameter memory component event report.

D–86

HSG80 User’s Guide

Table D–7

ASC and ASCQ Codes (Continued)

ASC Code

ASCQ Code

Description

Backup battery failure event report.

Subsystem built-in self test failure event report.

Memory system failure event report.

Failover event report.

RAID membership event report.

Multiple Bus failover event.

Multiple Bus failback event.

Disaster Tolerance failsafe error mode can now be enabled.

Shelf OK is not properly asserted.

Unable to clear SWAP interrupt. Interrupt disabled.

Swap interrupt re-enabled.

Asynchronous SWAP detected.

Controller shelf OK is not properly asserted.

EMU fault: Power Supplies not OK.

EMU fault: Fans not OK.

EMU fault: Temperature not OK.

EMU fault: External Air Sense not OK.

Power supply fault is now fixed.

Fans fault is now fixed.

Temperature fault is now fixed.

External Air Sense fault is now fixed.

EMU and cabinet now available.

EMU and cabinet now unavailable.

Command timeout.

Watchdog timer timeout.

Event Reporting: Templates and Codes

Table D–7

ASC and ASCQ Codes (Continued)

ASC Code

ASCQ Code

Description

Disconnect timeout.

Chip command timeout.

Byte transfer timeout.

Bus errors.

Unexpected bus phase.

Disconnect expected.

ID Message not sent.

Synchronous negotiation error.

Unexpected disconnect.

Unexpected message.

Unexpected Tag message.

Channel busy.

Device initialization failure. Device sense data available.

Miscellaneous SCSI driver error.

Device services had to reset the bus.

Drive SCSI chip reported gross error.

Non-SCSI bus parity error.

Message Reject received on a valid message.

Source driver programming error.

Fault Manager detected an unknown error code.

Maximum number of errors for this I/O exceeded.

Drive reported recovered error without transferring all data.

D–87

E–1

APPENDIX

Controller Specifications

This appendix contains physical, electrical, and environmental specifications for the
HSG80 array controller.

E–2

HSG80 User’s Guide

Physical and Electrical Specifications for the Controller
Table E–1 lists the physical and electrical specifications for the
controller and cache modules.
Table E–1

Controller Specifications

Hardware

Length

Width

Power

Current
at +5 V

HSG80 Array Controller
module

12.5 inches

8.75 inches

23.27 W

6.04 A

Write-back Cache, 512 MB 12.5 inches
(Battery charging)

7.75 inches

2.48 W
8.72 W

Current at +12
V

Cache idle, no
battery 230 mA
Cache running
diagnostics, no
battery 400 mA
Cache idle, fully
discharged
battery 710 mA

Voltage measurements in Table E–1 are nominal measurements (at +5
and +12 B). This table does not included tolerances.

Controller Specifications

E–3

Environmental Specifications
The HSG80 array controller is intended for installation in a Class A
computer room environment.
The environmental specifications listed in Table E–2 are the same as for
other DIGITAL storage devices.
Table E–2

StorageWorks Environmental Specifications

Condition

Optimum Operating Environment

Temperature

+18° to +24°C (+65° to +75°F)

Temperature rate of change

11°C (20°F per hour)

Relative humidity

40% to 60% (noncondensing) with a step change of 10% or less
(noncondensing)

Altitude

From sea level to 2400 m (8000 ft)

Air quality

Maximum particle count 0.5 micron or larger, not to exceed 500,000
particles per cubic foot of air

Inlet air volume

0.026 cubic m per second (50 cubic ft per minute)

Condition

Maximum Operating Environment (Range)

Temperature

+10° to +40°C (+50° to +104°F)
Derate 1.8°C for each 1000 m (1.0°F for each 1000 ft) of altitude
Maximum temperature gradient 11°C/hour (20°F/hour) ±2°C/hour
(4°F/hour)

Relative humidity

10% to 90% (noncondensing)
Maximum wet bulb temperature: 28°C (82°F)
Minimum dew point: 2°C (36°F)

Condition

Maximum Nonoperating Environment (Range)

Temperature

-40° to +66°C (-40° to +151°F)
(During transportation and associated short-term storage)

Relative Humidity

8% to 95% in original shipping container (noncondensing);
otherwise, 50% (noncondensing)

Altitude

From -300 m (-1000 ft) to +3600 m (+12,000 ft) Mean Sea Level
(MSL)

G–1

Glossary

This glossary defines terms pertaining to the HSG80 Fibre Channel
array controller. It is not a comprehensive glossary of computer terms.
8B/10B

A type of byte encoding and decoding to reduce errors in data
transmission patented by the IBM Corporation. This process of
encoding and decoding data for transmission has been adopted by
ANSI.

adapter

A device that converts the protocol and hardware interface of one bus
type into another without changing the function of the bus.

ACS

See array controller software.

AL_PA

See arbitrated loop physical address.

alias address

An AL_PA value recognized by an Arbitrated Loop port in addition to
its assigned AL_PA.

ANSI

Pronounced “ann-see.” Acronym for the American National Standards
Institute. An organization who develops standards used voluntarily by
many manufacturers within the USA. ANSI is not a government
agency.

arbitrate

A process of selecting one L_Port from a collection of several ports that
request use of the arbitrated loop concurrently.

arbitrated loop

A loop type of topology where two or more ports can be
interconnected, but only two ports at a time can communicate.

arbitrated loop physical
address

Abbreviated AL_PA. A one-byte value used to identify a port in an
Arbitrated Loop topology. The AL_PA value corresponds to bits 7:0 of
the 24-bit Native Address Indentifier.

array controller

See controller.

G–2

HSG80 User’s Guide

array controller software

Abbreviated ACS. Software contained on a removable ROM program
card that provides the operating system for the array controller.

asynchronous

Pertaining to events that are scheduled as the result of a signal asking
for the event; pertaining to that which is without any specified time
relation. See also synchronous.

autospare

A controller feature that automatically replaces a failed disk drive. To
aid the controller in automatically replacing failed disk drives, you can
enable the AUTOSPARE switch for the failedset causing physically
replaced disk drives to be automatically placed into the spareset. Also
called “autonewspare.”

bad block

A data block that contains a physical defect.

bad block replacement

Abbreviated BBR. A replacement routine that substitutes defect-free
disk blocks for those found to have defects. This process takes place in
the controller, transparent to the host.

backplane

The electronic printed circuit board into which you plug subsystem
devices—for example, the SBB or power supply.

BBR

See bad block replacement.

BIST

See built-in self-test.

bit

A single binary digit having a value of either 0 or 1. A bit is the
smallest unit of data a computer can process.

block

Also called a sector. The smallest collection of consecutive bytes
addressable on a disk drive. In integrated storage elements, a block
contains 512 bytes of data, error codes, flags, and the block’s address
header.

bootstrapping

A method used to bring a system or device into a defined state by
means of its own action. For example, a machine routine whose first
few instructions are enough to bring the rest of the routine into the
computer from an input device.

built-in self-test

A diagnostic test performed by the array controller software on the
controller’s policy processor.

Glossary

G–3

byte

A binary character string made up of 8 bits operated on as a unit.

cache memory

A portion of memory used to accelerate read and write operations.

CCITT

Acronym for Consultive Committee International Telephone and
Telegraph. An international association that sets worldwide
communication standards, recently renamed International
Telecommunications Union (ITU).

CDU

Cable distribution unit. The power entry device for StorageWorks
cabinets. The CDU provides the connections necessary to distribute
power to the cabinet shelves and fans.

channel

An interface which allows high speed transfer of large amounts of data.
Another term for a SCSI bus. See also SCSI.

chunk

A block of data written by the host.

chunk size

The number of data blocks, assigned by a system administrator, written
to the primary RAIDset or stripeset member before the remaining data
blocks are written to the next RAIDset or stripeset member.

CLCP

An abbreviation for code-load code-patch utility.

CLI

See command line interpreter.

coax

See coaxial cable.

coaxial cable

A two-conductor wire in which one conductor completely wraps the
other with the two separated by insulation.

cold swap

A method of device replacement that requires the entire subsystem to
be turned off before the device can be replaced. See also hot swap and
warm swap.

command line
interpreter

The configuration interface to operate the controller software.

configuration file

A file that contains a representation of a storage subsystem’s
configuration.

G–4

HSG80 User’s Guide

container

1) Any entity that is capable of storing data, whether it is a physical
device or a group of physical devices. (2) A virtual, internal controller
structure representing either a single disk or a group of disk drives
linked as a storageset. Stripesets and mirrorsets are examples of
storageset containers the controller uses to create units.

controller

A hardware device that, with proprietary software, facilitates
communications between a host and one or more devices organized in
an array. HS family controllers are examples of array controllers.

copying

A state in which data to be copied to the mirrorset is inconsistent with
other members of the mirrorset. See also normalizing.

copying member

Any member that joins the mirrorset after the mirrorset is created is
regarded as a copying member. Once all the data from the normal
member (or members) is copied to a normalizing or copying member,
the copying member then becomes a normal member. See also
normalizing member.

CSR

An acronym for control and status register.

DAEMON

Pronounced “demon.” A program usually associated with a UNIX
systems that performs a utility (housekeeping or maintenance) function
without being requested or even known of by the user. A daemon is a
diagnostic and execution monitor.

data center cabinet

A generic reference to large DIGITAL subsystem cabinets, such as the
SW600-series and 800-series cabinets in which StorageWorks
components can be mounted.

data striping

The process of segmenting logically sequential data, such as a single
file, so that segments can be written to multiple physical devices
(usually disk drives) in a round-robin fashion. This technique is useful
if the processor is capable of reading or writing data faster than a single
disk can supply or accept the data. While data is being transferred from
the first disk, the second disk can locate the next segment.

device

See node and peripheral device.

differential I/O module

A 16-bit I/O module with SCSI bus converter circuitry for extending a
differential SCSI bus. See also I/O module.

Glossary

G–5

differential SCSI bus

A bus in which a signal’s level is determined by the potential difference
between two wires. A differential bus is more robust and less subject to
electrical noise than is a single-ended bus.

DIMM

Dual inline Memory Module.

dirty data

The write-back cached data that has not been written to storage media,
even though the host operation processing the data has completed.

DMA

Direct Memory Access.

DOC

DWZZA-On-a-Chip. An NCR53C120 SCSI bus extender chip used to
connect a SCSI bus in an expansion cabinet to the corresponding SCSI
bus in another cabinet.

driver

A hardware device or a program that controls or regulates another
device. For example, a device driver is a driver developed for a specific
device that allows a computer to operate with the device, such as a
printer or a disk drive.

dual-redundant
configuration

A controller configuration consisting of two active controllers operating
as a single controller. If one controller fails, the other controller
assumes control of the failing controller’s devices.

dual-simplex

A communications protocol that allows simultaneous transmission in
both directions in a link, usually with no flow control.

DUART

Dual universal asynchronous receiver and transmitter. An integrated
circuit containing two serial, asynchronous transceiver circuits.

ECB

External cache battery. The unit that supplies backup power to the
cache module in the event the primary power source fails or is
interrupted.

ECC

Error checking and correction.

EDC

Error detection code.

EIA

The abbreviation for Electronic Industries Association. EIA is a
standards organization specializing in the electrical and functional
characteristics of interface equipment. Same as Electronic Industries
Association.

G–6

HSG80 User’s Guide

EMU

Environmental monitoring unit. A unit that provides increased
protection against catastrophic failures. Some subsystem enclosures
include an EMU which works with the controller to detect conditions
such as failed power supplies, failed blowers, elevated temperatures,
and external air sense faults. The EMU also controls certain cabinet
hardware including DOC chips, alarms, and fan speeds.

ESD

Electrostatic discharge. The discharge of potentially harmful static
electrical voltage as a result of improper grounding.

extended subsystem

A subsystem in which two cabinets are connected to the primary
cabinet.

external cache battery

See ECB.

F_Port

A port in a fabric where an N_Port or NL_Port may attach.

fabric

A group of interconnections between ports that includes a fabric element.

failedset

A group of failed mirrorset or RAIDset devices automatically created
by the controller.

failover

The process that takes place when one controller in a dual-redundant
configuration assumes the workload of a failed companion controller.
Failover continues until the failed controller is repaired or replaced.

FC–AL

The Fibre Channel Arbitrated Loop standard.

FC–ATM

ATM AAL5 over Fibre Channel

FC–FG

Fibre Channel Fabric Generic Requirements

FG–FP

Fibre Channel Framing Protocol (HIPPI on FC)

FC-GS-1

Fibre Channel Generic Services-1

FC–GS-2

Fibre Channel Generic Services-2

FC–IG

Fibre Channel Implementation Guide

FC–LE

Fibre Channel Link Encapsulation (ISO 8802.2)

Glossary

G–7

FC–PH

The Fibre Channel Physical and Signaling standard.

FC–SB

Fibre Channel Single Byte Command Code Set

FC–SW

Fibre Channel Switched Topology and Switch Controls

FCC

Federal Communications Commission. The federal agency responsible
for establishing standards and approving electronic devices within the
United States.

FCC Class A

This certification label appears on electronic devices that can only be
used in a commercial environment within the United States.

FCC Class B

This certification label appears on electronic devices that can be used in
either a home or a commercial environment within the United States.

FCP

The mapping of SCSI-3 operations to Fibre Channel.

FDDI

Fiber Distributed Data Interface. An ANSI standard for 100 megabaud
transmission over fiber optic cable.

FD SCSI

The fast, narrow, differential SCSI bus with an 8-bit data transfer rate of
10 MB/s. See also FWD SCSI and SCSI.

fiber

A fiber or optical strand. Spelled fibre in Fibre Channel.

fiber optic cable

A transmission medium designed to transmit digital signals in the form
of pulses of light. Fiber optic cable is noted for its properties of
electrical isolation and resistance to electrostatic contamination.

FL_Port

A port in a fabric where N_Port or an NL_Port may be connected.

flush

The act of writing dirty data from cache to a storage media.

FMU

Fault management utility.

forced errors

A data bit indicating a corresponding logical data block contains
unrecoverable data.

frame

An invisible unit used to transfer information in Fibre Channel.

G–8

HSG80 User’s Guide

FRU

Field replaceable unit. A hardware component that can be replaced at
the customer’s location by DIGITAL service personnel or qualified
customer service personnel.

full duplex (n)

A communications system in which there is a capability for 2-way
transmission and acceptance between two sites at the same time.

full duplex (adj)

Pertaining to a communications method in which data can be
transmitted and received at the same time.

FWD SCSI

A fast, wide, differential SCSI bus with a maximum 16-bit data transfer
rate of 20 MB/s. See also SCSI and FD SCSI.

GLM

Gigabit link module

giga

A prefix indicating a billion (109) units, as in gigabaud or gigabyte.

gigabaud

An encoded bit transmission rate of one billion (109) bits per second.

gigabyte

A value normally associated with a disk drives storage capacity,
meaning a billion (109) bytes. The decimal value 1024 is usually used
for one thousand.

half-duplex (adj)

Pertaining to a communications system in which data can be either
transmitted or received but only in one direction at one time.

hard address

The AL_PA which an NL_Port attempts to acquire during loop
initialization.

HIPPI–FC

Fibre Channel over HIPPI

host

The primary or controlling computer to which a storage subsystem is
attached.

host adapter

A device that connects a host system to a SCSI bus. The host adapter
usually performs the lowest layers of the SCSI protocol. This function
may be logically and physically integrated into the host system.

host compatibility mode

A setting used by the controller to provide optimal controller
performance with specific operating systems. This improves the
controller’s performance and compatibility with the specified operating
system. The supported modes are A, Normal (including DIGITAL

Glossary

G–9

UNIX®, OpenVMS, Sun®, and Hewlett-Packard® HP–UX); B, IBM
AIX®; C, Proprietary; and D, Microsoft Windows NTTM Server.
hot disks

A disk containing multiple hot spots. Hot disks occur when the
workload is poorly distributed across storage devices which prevents
optimum subsystem performance. See also hot spots.

hot spots

A portion of a disk drive frequently accessed by the host. Because the
data being accessed is concentrated in one area, rather than spread
across an array of disks providing parallel access, I/O performance is
significantly reduced. See also hot disks.

hot swap

A method of device replacement that allows normal I/O activity on a
device’s bus to remain active during device removal and insertion. The
device being removed or inserted is the only device that cannot perform
operations during this process. See also cold swap and warm swap.

IBR

Initial Boot Record.

ILF

Illegal function.

INIT

Initialize input and output.

initiator

A SCSI device that requests an I/O process to be performed by another
SCSI device, namely, the SCSI target. The controller is the initiator on
the device bus. The host is the initiator on the host bus.

instance code

A four-byte value displayed in most text error messages and issued by
the controller when a subsystem error occurs. The instance code
indicates when during software processing the error was detected.

interface

A set of protocols used between components, such as cables,
connectors, and signal levels.

I/O

Refers to input and output functions.

I/O driver

The set of code in the kernel that handles the physical I/O to a device.
This is implemented as a fork process. Same as driver.

I/O interface

See interface.

G–10

HSG80 User’s Guide

I/O module

A 16-bit SBB shelf device that integrates the SBB shelf with either an
8-bit single ended, 16-bit single-ended, or 16-bit differential SCSI bus.

I/O operation

The process of requesting a transfer of data from a peripheral device to
memory (or visa versa), the actual transfer of the data, and the
processing and overlaying activity to make both of those happen.

IPI

Intelligent Peripheral Interface. An ANSI standard for controlling
peripheral devices by a host computer.

IPI-3 Disk

Intelligent Peripheral Interface Level 3 for Disk

IPI-3 Tape

Intelligent Peripheral Interface Level 3 for Tape

JBOD

Just a bunch of disks. A term used to describe a group of single-device
logical units.

kernel

The most privileged processor access mode.

LBN

Logical Block Number.

L_port

A node or fabric port capable of performing arbitrated loop functions
and protocols. NL_Ports and FL_Ports are loop-capable ports.

LED

Light Emitting Diode.

link

A connection between two Fibre Channel ports consisting of a transmit
fibre and a receive fibre.

logical block number

See LBN.

local connection

A connection to the subsystem using either its serial maintenance port
or the host’s SCSI bus. A local connection enables you to connect to
one subsystem controller within the physical range of the serial or host
SCSI cable.

local terminal

A terminal plugged into the EIA-423 maintenance port located on the
front bezel of the controller. See also maintenance terminal.

logical bus

A single-ended bus connected to a differential bus by a SCSI bus signal
converter.

Glossary

G–11

logical unit

A physical or virtual device addressable through a target ID number.
LUNs use their target’s bus connection to communicate on the SCSI
bus.

logical unit number

A value that identifies a specific logical unit belonging to a SCSI target
ID number. A number associated with a physical device unit during a
task’s I/O operations. Each task in the system must establish its own
correspondence between logical unit numbers and physical devices.

logon

Also called login. A procedure whereby a participant, either a person or
network connection, is identified as being an authorized network
participant.

loop

See arbitrated loop.

loop_ID

A seven-bit value numbered contiguously from zero to 126-decimal and
represent the 127 legal AL_PA values on a loop (not all of the 256 hex
values are allowed as AL_PA values per FC-AL.

loop tenancy

The period of time between the following events: when a port wins
loop arbitration and when the port returns to a monitoring state.

L_Port

A node or fabric port capable of performing Arbitrated Loop functions
and protocols. NL_Ports and FL_Ports are loop-capable ports.

LRU

Least recently used. A cache term used to describe the block
replacement policy for read cache.

Mbps

Approximately one million (106) bits per second—that is, megabits per
second.

MBps

Approximately one million (106) bytes per second—that is, megabytes
per second.

maintenance terminal

An EIA-423-compatible terminal used with the controller. This
terminal is used to identify the controller, enable host paths, enter
configuration information, and check the controller’s status. The
maintenance terminal is not required for normal operations.
See also local terminal.

member

A container that is a storage element in a RAID array.

G–12

HSG80 User’s Guide

metadata

The data written to a disk for the purposes of controller administration.
Metadata improves error detection and media defect management for
the disk drive. It is also used to support storageset configuration and
partitioning. Nontransportable disks also contain metadata to indicate
they are uniquely configured for StorageWorks environments. Metadata
can be thought of as “data about data.”

mirroring

The act of creating an exact copy or image of data.

mirrorset

See RAID level 1.

MIST

Module Integrity Self-Test.

N_port

A port attached to a node for use with point-to-point topology or fabric
topology.

NL_port

A port attached to a node for use in all three topologies.

network

A data communication, a configuration in which two or more terminals
or devices are connected to enable information transfer.

node

In data communications, the point at which one or more functional
units connect transmission lines.

Non-L_Port

A Node of Fabric port that is not capable of performing the Arbitrated
Loop functions and protocols. N_Ports and F_Ports loop-capable ports.

non-participating mode

A mode within an L_Port that inhibits the port from participating in
loop activities. L_Ports in this mode continue to retransmit received
transmission words but are not permitted to arbitrate or originate
frames. An L_Port in non-participating mode may or may not have an
AL_PA. See also participating mode.

nominal membership

The desired number of mirrorset members when the mirrorset is fully
populated with active devices. If a member is removed from a
mirrorset, the actual number of members may fall below the “nominal”
membership.

node

In data communications, the point at which one or more functional
units connect transmission lines. In fibre channel, a device that has at
least one N_Port or NL_Port.

Glossary

G–13

nonredundant controller
configuration

(1) A single controller configuration. (2) A controller configuration that
does not include a second controller.

normal member

A mirrorset member that, block-for-block, contains the same data as
other normal members within the mirrorset. Read requests from the
host are always satisfied by normal members.

normalizing

Normalizing is a state in which, block-for-block, data written by the
host to a mirrorset member is consistent with the data on other normal
and normalizing members. The normalizing state exists only after a
mirrorset is initialized. Therefore, no customer data is on the mirrorset.

normalizing member

A mirrorset member whose contents is the same as all other normal and
normalizing members for data that has been written since the mirrorset
was created or lost cache data was cleared. A normalizing member is
created by a normal member when either all of the normal members fail
or all of the normal members are removed from the mirrorset. See also
copying member.

NVM

Non-Volatile Memory. A type of memory where the contents survive
power loss. Also sometimes referred to as NVMEM.

OCP

Operator control panel. The control or indicator panel associated with a
device. The OCP is usually mounted on the device and is accessible to
the operator.

other controller

The controller in a dual-redundant pair that is connected to the
controller serving your current CLI session. See also this controller.

outbound fiber

One fiber in a link that carries information away from a port.

parallel data
transmission

A data communication technique in which more than one code element
(for example, bit) of each byte is sent or received simultaneously.

parity

parity bit

A binary digit added to a group of bits that checks to see if errors exist
in the transmission.

G–14

HSG80 User’s Guide

parity check

A method of detecting errors when data is sent over a communications
line. With even parity, the number of ones in a set of binary data should
be even. With odd parity, the number of ones should be odd.

participating mode

A mode within an L_Port that allows the port to participate in loop
activities. A port must have a valid AL_PA to be in participating mode.

PCM

Polycenter Console Manager.

PCMCIA

Personal Computer Memory Card Industry Association. An
international association formed to promote a common standard for PC
card-based peripherals to be plugged into notebook computers. The
card commonly known as a PCMCIA card is about the size of a credit
card.

parity

A method of checking if binary numbers or characters are correct by
counting the ONE bits. In odd parity, the total number of ONE bits
must be odd; in even parity, the total number of ONE bits must be even.
Parity information can be used to correct corrupted data. RAIDsets use
parity to improve the availability of data.

parity bit

A binary digit added to a group of bits that checks to see if there are
errors in the transmission.

parity RAID

See RAIDset.

partition

A logical division of a container, represented to the host as a logical
unit.

peripheral device

Any unit, distinct from the CPU and physical memory, that can provide
the system with input or accept any output from it. Terminals, printers,
tape drives, and disks are peripheral devices.

point-to-point
connection

A network configuration in which a connection is established between
two, and only two, terminal installations. The connection may include
switching facilities.

Glossary

port

G–15

(1) In general terms, a logical channel in a communications system. (2)
The hardware and software used to connect a host controller to a
communications bus, such as a SCSI bus or serial bus.
Regarding the controller, the port is (1) the logical route for data in and
out of a controller that can contain one or more channels, all of which
contain the same type of data. (2) The hardware and software that
connects a controller to a SCSI device.

port_name

A 64-bit unique identifier assigned to each Fibre Channel port. The
Port_Name is communicated during the logon and port discovery
process.

preferred address

The AL_PA which an NL_Port attempts to acquire first during
initialization.

primary cabinet

The primary cabinet is the subsystem enclosure that contains the
controllers, cache modules, external cache batteries, and the PVA
module.

private NL_Port

An NL_Port which does not attempt login with the fabric and only
communicates with NL_Ports on the same loop.

public NL_Port

An NL_Port that attempts login with the fabric and can observe the
rules of either public or private loop behavior. A public NL_Port may
communicate with both private and public NL_Ports.

program card

The PCMCIA card containing the controller’s operating software.

protocol

The conventions or rules for the format and timing of messages sent
and received.

PTL

Port-Target-LUN. The controller’s method of locating a device on the
controller’s device bus.

PVA module

Power Verification and Addressing module.

quiesce

The act of rendering bus activity inactive or dormant. For example,
“quiesce the SCSI bus operations during a device warm-swap.”

G–16

HSG80 User’s Guide

RAID

Redundant Array of Independent Disks. Represents multiple levels of
storage access developed to improve performance or availability or
both.

RAID level 0

A RAID storageset that stripes data across an array of disk drives. A
single logical disk spans multiple physical disks, allowing parallel data
processing for increased I/O performance. While the performance
characteristics of RAID level 0 is excellent, this RAID level is the only
one that does not provide redundancy. Raid level 0 storagesets are
sometimes referred to as stripesets.

RAID level 0+1

A RAID storageset that stripes data across an array of disks (RAID
level 0) and mirrors the striped data (RAID level 1) to provide high I/O
performance and high availability. This RAID level is alternatively
called a striped mirrorset. Raid level 0+1 storagesets are sometimes
referred to as striped mirrorsets.

RAID level 1

A RAID storageset of two or more physical disks that maintains a
complete and independent copy of the entire virtual disk’s data. This
type of storageset has the advantage of being highly reliable and
extremely tolerant of device failure. Raid level 1 storagesets are
sometimes referred to as mirrorsets.

RAID level 3

A RAID storageset that transfers data parallel across the array’s disk
drives a byte at a time, causing individual blocks of data to be spread
over several disks serving as one enormous virtual disk. A separate
redundant check disk for the entire array stores parity on a dedicated
disk drive within the storageset. See also RAID level 5.

RAID Level 5

A RAID storageset that, unlike RAID level 3, stores the parity
information across all of the disk drives within the storageset. See also
RAID level 3.

RAID level 3/5

A DIGITAL-developed RAID storageset that stripes data and parity
across three or more members in a disk array. A RAIDset combines the
best characteristics of RAID level 3 and RAID level 5. A RAIDset is
the best choice for most applications with small to medium I/O
requests, unless the application is write intensive. A RAIDset is
sometimes called parity RAID. Raid level 3/5 storagesets are
sometimes referred to as RAIDsets.

RAIDset

See RAID level 3/5.

Glossary

G–17

RAM

Random access memory.

read ahead caching

A caching technique for improving performance of synchronous
sequential reads by prefetching data from disk.

read caching

A cache management method used to decrease the subsystem’s
response time to a read request by allowing the controller to satisfy the
request from the cache memory rather than from the disk drives.

reconstruction

The process of regenerating the contents of a failed member’s data. The
reconstruct process writes the data to a spareset disk and then
incorporates the spareset disk into the mirrorset, striped mirrorset, or
RAIDset from which the failed member came. See also regeneration.

reduced

Indicates that a mirrorset or RAIDset is missing one member because
the member has failed or has been physically removed.

redundancy

The provision of multiple interchangeable components to perform a
single function in order to cope with failures and errors. A RAIDset is
considered to be redundant when user data is recorded directly to one
member and all of the other members include associated parity
information.

regeneration

(1) The process of calculating missing data from redundant data. (2)
The process of recreating a portion of the data from a failing or failed
drive using the data and parity information from the other members
within the storageset. The regeneration of an entire RAIDset member is
called reconstruction. See also reconstruction.

request rate

The rate at which requests are arriving at a servicing entity.

RFI

Radio frequency interference. The disturbance of a signal by an
unwanted radio signal or frequency.

replacement policy

The policy specified by a switch with the SET FAILEDSET command
indicating whether a failed disk from a mirrorset or RAIDset is to be
automatically replaced with a disk from the spareset. The two switch
choices are AUTOSPARE and NOAUTOSPARE.

SBB

StorageWorks building block. (1) A modular carrier plus the interface
required to mount the carrier into a standard StorageWorks shelf. (2)
any device conforming to shelf mechanical and electrical standards

G–18

HSG80 User’s Guide

installed in a 3.5-inch or 5.25-inch carrier, whether it is a storage device
or power supply.
SCSI

Small computer system interface. (1) An ANSI interface standard
defining the physical and electrical parameters of a parallel I/O bus
used to connect initiators to devices. (2) a processor-independent
standard protocol for system-level interfacing between a computer and
intelligent devices including hard drives, floppy disks, CD-ROMs,
printers, scanners, and others.

SCSI-A cable

A 50-conductor (25 twisted-pair) cable generally used for single-ended,
SCSI-bus connections.

SCSI bus signal
converter

Sometimes referred to as an adapter. (1) A device used to interface
between the subsystem and a peripheral device unable to be mounted
directly into the SBB shelf of the subsystem. (2) a device used to
connect a differential SCSI bus to a single-ended SCSI bus. (3) A
device used to extend the length of a differential or single-ended SCSI
bus. See also I/O module.

SCSI device

(1) A host computer adapter, a peripheral controller, or an intelligent
peripheral that can be attached to the SCSI bus. (2) Any physical unit
that can communicate on a SCSI bus.

SCSI device ID number

A bit-significant representation of the SCSI address referring to one of
the signal lines, numbered 0 through 7 for an 8-bit bus, or 0 through 15
for a 16-bit bus. See also target ID number.

SCSI ID number

The representation of the SCSI address that refers to one of the signal
lines numbered 0 through 15.

SCSI-P cable

A 68-conductor (34 twisted-pair) cable generally used for differential
bus connections.

SCSI port

(1) Software: The channel controlling communications to and from a
specific SCSI bus in the system. (2) Hardware: The name of the logical
socket at the back of the system unit to which a SCSI device is
connected.

serial transmission

A method transmission in which each bit of information is sent
sequentially on a single channel rather than simultaneously as in
parallel transmission.

Glossary

G–19

service rate

The rate at which an entity is able to service requests For example, the
rate at which an Arbitrated Loop is able to service arbitrated requests.

signal converter

See SCSI bus signal converter.

SIMM

Single Inline Memory Module.

single ended I/O module

A 16-bit I/O module. See also I/O module.

single-ended SCSI bus

An electrical connection where one wire carries the signal and another
wire or shield is connected to electrical ground. Each signal’s logic
level is determined by the voltage of a single wire in relation to ground.
This is in contrast to a differential connection where the second wire
carries an inverted signal.

spareset

A collection of disk drives made ready by the controller to replace
failed members of a storageset.

storage array

An integrated set of storage devices.

storage array subsystem

See storage subsystem.

storageset

(1) A group of devices configured with RAID techniques to operate as
a single container. (2) Any collection of containers, such as stripesets,
mirrorsets, striped mirrorsets, and RAIDsets.

storage subsystem

The controllers, storage devices, shelves, cables, and power supplies
used to form a mass storage subsystem.

storage unit

The general term that refers to storagesets, single-disk units, and all
other storage devices that are installed in your subsystem and accessed
by the host. A storage unit can be any entity that is capable of storing
data, whether it is a physical device or a group of physical devices.

StorageWorks

A family of DIGITAL modular data storage products that allow
customers to design and configure their own storage subsystems.
Components include power, packaging, cabling, devices, controllers,
and software. Customers can integrate devices and array controllers in
StorageWorks enclosures to form storage subsystems.

G–20

HSG80 User’s Guide

StorageWorks systems include integrated SBBs and array controllers to
form storage subsystems. System-level enclosures to house the shelves
and standard mounting devices for SBBs are also included.
stripe

The data divided into blocks and written across two or more member
disks in an array.

striped mirrorset

See RAID level 0+1.

stripeset

See RAID level 0.

stripe size

The stripe capacity as determined by n–1 times the chunksize, where n
is the number of RAIDset members.

striping

The technique used to divide data into segments, also called chunks.
The segments are striped, or distributed, across members of the
stripeset. This technique helps to distribute hot spots across the array of
physical devices to prevent hot spots and hot disks.
Each stripeset member receives an equal share of the I/O request load,
improving performance.

surviving controller

The controller in a dual-redundant configuration pair that serves its
companion’s devices when the companion controller fails.

switch

A method that controls the flow of functions and operations in
software.

synchronous

Pertaining to a method of data transmission which allows each event to
operate in relation to a timing signal. See also asynchronous.

tape

A storage device supporting sequential access to variable sized data
records.

target

(1) A SCSI device that performs an operation requested by an initiator.
(2) Designates the target identification (ID) number of the device.

this controller

The controller that is serving your current CLI session through a local
or remote terminal. See also other controller.

Glossary

G–21

topology

An interconnection scheme that allows multiple Fibre Channel ports to
communicate with each other. For example, point-to-point, Arbitrated
Loop, and switched fabric are all Fibre Channel topologies.

transfer data rate

The speed at which data may be exchanged with the central processor,
expressed in thousands of bytes per second.

ULP

Upper Layer Protocol.

ULP process

A function executing within a Fibre Channel node which conforms to
the Upper Layer Protocol (ULP) requirements when interacting with
other ULP processes.

Ultra-SCSI bus

A wide, Fast-20 SCSI bus.

unit

A container made accessible to a host. A unit may be created from a
single disk drive or tape drive. A unit may also be created from a more
complex container such as a RAIDset. The controller supports a
maximum of eight units on each target. See also target and target ID
number.

unwritten cached data

Sometimes called unflushed data. See dirty data.

UPS

Uninterruptible power supply. A battery-powered power supply
guaranteed to provide power to an electrical device in the event of an
unexpected interruption to the primary power supply. Uninterruptible
power supplies are usually rated by the amount of voltage supplied and
the length of time the voltage is supplied.

VHDCI

Very high-density-cable interface. A 68-pin interface. Required for
Ultra-SCSI connections.

virtual terminal

A software path from an operator terminal on the host to the controller’s
CLI interface, sometimes called a host console. The path can be
established via the host port on the controller (using HSZterm) or via
the maintenance port through an intermediary host.

VTDPY

An abbreviation for Virtual Terminal Display Utility.

G–22

HSG80 User’s Guide

warm swap

A device replacement method that allows the complete system remains
online during device removal or insertion. The system bus may be
halted, or quiesced, for a brief period of time during the warm-swap
procedure.

Worldwide name

A unique 64-bit number assigned to a subsystem by the Institute of
Electrical and Electronics Engineers (IEEE) and set by DIGITAL
manufacturing prior to shipping. This name is referred to as the node
ID within the CLI.

write-back caching

A cache management method used to decrease the subsystem’s
response time to write requests by allowing the controller to declare the
write operation “complete” as soon as the data reaches its cache
memory. The controller performs the slower operation of writing the
data to the disk drives at a later time.

write-through caching

A cache management method used to decrease the subsystem’s
response time to a read. This method allows the controller to satisfy the
request from the cache memory rather than from the disk drives.

write hole

The period of time in a RAID level 1 or RAID level 5 write operation
when an opportunity emerges for undetectable RAIDset data
corruption. Write holes occur under conditions such as power outages,
where the writing of multiple members can be abruptly interrupted. A
battery backed-up cache design eliminates the write hole because data
is preserved in cache and unsuccessful write operations can be retried.

write-through cache

A cache management technique for retaining host write requests in read
cache. When the host requests a write operation, the controller writes
data directly to the storage device. This technique allows the controller
to complete some read requests from the cache, greatly improving the
response time to retrieve data. The operation is complete only after the
data to be written is received by the target storage device.
This cache management method may update, invalidate, or delete data
from the cache memory accordingly, to ensure that the cache contains
the most current data.

I–1

Index

A
AC input module
part number, 1–3
Access door
part number, 1–9
ADD DISK, B–11
NOTRANSPORTABLE, B–12
TRANSFER_RATE_REQUESTED, B–12
TRANSPORTABLE, B–12
ADD DISK container-name scsi-port-target-lun,
B–11
ADD MIRRORSET, B–15
COPY, B–15
POLICY, B–16
READ_SOURCE, B–16
ADD RAIDSET, B–19
NOPOLICY, B–19
NOREDUCED, B–21
POLICY, B–19
RECONSTRUCT, B–20
REDUCED, B–21
ADD RAIDSET RAIDset-name containernameN, B–19
ADD SPARESET, B–23
ADD SPARESET disk-name, B–23
ADD STRIPESET, B–25
ADD STRIPESET stripeset-name containernameN, B–25
ADD UNIT, B–27
DISABLE_ACCESS_PATH, B–28
ENABLE_ACCESS_PATH, B–28
MAXIMUM_CACHED_TRANSFER, B–29
NOPREFERRED_PATH, B–30
NOREAD_CACHE, B–31

NOREADAHEAD_CACHE, B–31
NORUN, B–31
NOWRITE_PROTECT, B–32
NOWRITEBACK_CACHE, B–32
PARTITION, B–29
PREFERRED_PATH, B–30
READ_CACHE, B–31
READAHEAD_CACHE, B–31
RUN, B–31
WRITE_PROTECT, B–32
WRITEBACK_CACHE, B–32
ADD UNIT unit-number container-name, B–27
Adding
DIMMs, 6–20
disks, B–11
mirrorsets, B–15
RAIDsets, B–19
sparesets, B–23
stripesets, B–25
units, B–27
Adding cache memory, 6–20
Adding DIMMs, 6–20
Adding disk drives
as eligible devices, 3–55
to spareset using CLI, 3–63
Addresses
providing with the PVA module, 2–6
Addressing PTL convention, 3–33
ALLOCATION_CLASS
SET controller, B–105

I–2

HSG80 User’s Guide

Array Controller. See Controller
Array of disk drives, 3–8
ASC/ASCQ codes, D–85
ASC_ASCQ codes, 4–18
AUTOSPARE, 3–65
SET FAILEDSET, B–117
Autospare
failedset, 3–65
Availability, 3–15

B
BA370 enclosure
ECB Y cable, 1–19
BA370 rack-mountable enclosure
ECB Y cable, 1–28
part number, 1–3
Backing up data, 3–19
Backing up data with the Clone utility, 1–16
Backplane
location, 1–13
Backup power source
enabling write-back caching, 1–21
Battery hysteresis, 1–29
BATTERY_OFF
POWEROFF, B–83
BATTERY_ON
POWEROFF, B–83
BC16E-xx cable assembly
part number, 1–10
Bus
device bus interconnect, 1–5
distribute members across, 3–14, 3–16
distributing first mirrorset members, 3–13
distributing members across, 3–10

C
Cable assembly
terminal connection, 1–10
Cables
ECB Y cable part numbers, 1–28
BA370 enclosure, 1–19
data center cabinet, 1–19

fibre channel
copper, 2–14
optical, 2–15
maintenance port cable part number for a PC,
1–9
maintenance port cable part number for a
terminal, 1–10
Cabling
copper
single configuration, 2–14 to 2–15
Cache module
256-MB cache upgrade part number, 1–19
64-MB cache upgrade part number, 1–19
caching techniques, 1–20
companion cache module, 1–18
controller and cache module location, 1–13
DIMMs supported, 1–5, 1–18
general description, 1–18
illustration of parts, 1–19
installing
dual-redundant controller configuration,
5–24
single-controller configuration, 5–7
location, 1–13
memory configurations, 1–18
memory sizes supported, 1–5
part number, 1–3
read caching, 1–20
relationship to controller, 1–13
removing
dual-redundant controller configuration,
5–21
single-controller configuration, 5–6
replacing
dual-redundant controller configuration,
5–21
single-controller configuration, 5–6
replacing cache modules with FRUTIL, 1–16
write-back caching, 1–21
write-through caching, 1–21
Cache policies
fault-tolerance for write-back caching, 1–22

Index

Cache, setting flush timer, B–105
CACHE_FLUSH_TIMER
SET controller, B–105
CACHE_UPS
SET controller, B–105
Caching techniques, 1–5
general description, 1–20
read caching, 1–20
read-ahead caching, 1–20
write-back caching, 1–21
write-through caching, 1–21
CAPACITY
CREATE_PARTITION, B–52
INITIALIZE, B–72
Caution, defined, xxi
Change volume serial number utility. See CHVSN
utility
Changing switches
devices, 3–39
initialize, 3–67
storagesets, 3–39
unit, 3–67
Charging diagnostics
battery hysteresis, 1–29
general description, 1–29
Checking fibre channel link errors, 4–32
Chunk size, 3–47
choosing for RAIDsets and stripesets, 3–47
controlling stripesize, 3–47
maximum for RAIDsets, 3–50
using to increase data transfer rate, 3–49
using to increase request rate, 3–47
using to increase write performance, 3–49
CHUNKSIZE, 3–47
INITIALIZE, B–72
Chunksize, setting storageset size, B–72
CHVSN utility
general description, 1–17
CHVSN, running, B–95
CLCP
downloading new software, 6–3

I–3

patches
installing, 6–6
CLCP utility
general description, 1–16
CLCP, running, B–95
Cleaning instructions
fibre channel optical cable, 1–12
CLEAR_ERRORS CLI, B–35
CLEAR_ERRORS controller
INVALID_CACHE, B–37
data-retention-policy, B–37
DESTROY_UNFLUSHED_DATA, B–37
NODESTROY_UNFLUSHED_DATA, B–37
CLEAR_ERRORS device-name UNKNOWN,
B–39
CLEAR_ERRORS unit-number LOST_DATA,
B–41
CLI
definition, B–2
overview, B–2
CLI commands
abbreviating commands, B–3
ADD DISK, B–11
ADD MIRRORSET, B–15
ADD RAIDSET, B–19
ADD SPARESET, B–23
ADD STRIPESET, B–25
ADD UNIT, B–27
CLEAR_ERRORS CLI, B–35
CLEAR_ERRORS controller
INVALID_CACHE, B–37
CLEAR_ERRORS device-name UNKNOWN,
B–39
CLEAR_ERRORS unit-number LOST_DATA,
B–41
CLEAR_ERRORS unit-number
UNWRITEABLE_DATA, B–43
CONFIGURATION RESET, B–45
CONFIGURATION RESTORE, B–47
CONFIGURATION SAVE, B–49
CREATE_PARTITION, B–51
customizing the prompt, B–108

I–4

HSG80 User’s Guide

DELETE connections, B–55
DELETE container-name, B–57
DELETE FAILEDSET, B–59
DELETE SPARESET, B–61
DELETE unit-number, B–63
DESTROY_PARTITION, B–65
DIRECTORY, B–67
editing keys, B–4
getting help, B–3
HELP, B–69
INITIALIZE, B–71
LOCATE, B–77
MIRROR, B–79
overview, B–2
POWEROFF, B–83
REDUCE, B–85
RENAME, B–89
RETRY_ERRORS unit-number
UNWRITEABLE_DATA, B–93
rules for entering, B–3
RUN, B–95
SELFTEST controller, B–99
SET controller, B–103
SET device-name, B–111
SET EMU, B–113
SET FAILEDSET, B–117
SET FAILOVER, B–119
SET mirrorset-name, B–121
SET MULTIBUS_FAILOVER, B–127
SET NOFAILOVER, B–129
SET NOMULTIBUS_FAILOVER, B–131
SET RAIDset-name, B–133
SET unit-number, B–137
shortcuts, B–4
SHOW, B–143
SHUTDOWN controller, B–149
syntax, B–5
UNMIRROR, B–151
CLI event reporting
no controller termination, 4–16
CLONE
procedure, 3–20

utility, 3–19
Clone utility
general description, 1–16
CLONE, running, B–95
Cloning data, 3–19
Code load and code patch utility. See CLCP utility
Codes
ASC/ASCQ, D–85
ASC_ASCQ, 4–18
component identifier codes, D–82
device_type, 4–18
event codes, 4–18
event threshold codes, D–84
instance, 4–18, D–18 to D–35
last_failure, 4–18
last-failure, D–38 to D–76
repair action, D–77 to D–81
repair_action, 4–18
structure of events and last-failures, 4–19
translating, 4–18
types of, 4–18
Command line interpreter. See CLI
COMMAND_CONSOLE_LUN
SET controller, B–106
Communicating with a controller
from a local terminal, 2–8
Comparison of storagesets, 3–8
Component codes, 4–18
Component identifier codes, D–82
Components. See Controller
CONFIG utility
general description, 1–15
CONFIG, running, B–95
Configuration
map of devices in subsystem, 4–25
modifying controller configurations, B–2
resetting, B–45
restoring, B–47, B–73
saving, B–49
upgrading to dual-redundant controller, 6–16

Index

CONFIGURATION RESET, B–45
CONFIGURATION RESTORE, B–47
Configuration rules
devices, 2–2
LUN capacity, 2–2
mirrorsets, 2–2
partitions per storageset, 2–2
RAID-5 and RAID-1 storagesets, 2–2
RAID-5 storagesets, 2–2
RAID-5, RAID-1, and RAID-0 storagesets, 2–2
requirements, 2–2
striped mirrorsets, 2–2
stripesets, 2–2
See also Summary of controller features
CONFIGURATION SAVE, B–49
Configuration utility. See CONFIG utility
Configuring
controller, 2–3, 2–10
dual-redundant controller configurations, 2–10
dual-redundant controller configurations with
mirrored cache, 2–12
mirrorsets, 3–56
multiple-bus failover, 2–11
RAIDsets, 3–57
single-disk unit, 3–60
striped mirrorsets, 3–59
stripesets, 3–55
Configuring using CLI
mirrorsets, 3–56
RAIDsets, 3–57
storagesets, 3–55
striped mirrorsets, 3–59
stripesets, 3–55
Configuring with CLI
single-disk units, 3–60
Connecting
dual controllers to the host
using one hub, 2–21
using two hubs, 2–17
dual-redundant controllers to host, one hub,
2–21, 2–23

I–5

dual-redundant controllers to host, two hubs,
2–18, 2–20
dual-redundant controllers to the host, 2–17
local connection to the controller, 2–7
PC connection to the controller, 2–7
single controller to the host using one hub, 2–14
terminal connection to the controller, 2–7
Container
initializing, B–71
Containers
naming a unit, B–28
Controller
“this” and “other” defined, xx
addressing, 3–33
backplane, 1–13
checking communication with devices, 4–24
checking communication with host, 4–24
checking transfer rate with host, 4–24
communicating from a local terminal, 2–8
configuring, 2–3, 2–10
connecting dual-redundant to host, one hub,
2–21, 2–23
connecting dual-redundant to host, two hubs,
2–18, 2–20
controller and cache module location, 1–13
displaying information, B–143
dual-redundant controller configuration, 2–10,
2–17, 2–21
dual-redundant controller configurations with
mirrored cache, 2–12
ECB diagnostics, 1–29
fault LEDs, 1–13
fibre channel copper cabling
illustration of parts, 1–8
part numbers of parts used in configuring,
1–9
parts used in configuring, 1–9
fibre channel optical cabling
illustration of parts, 1–11
part numbers of parts used in configuring,
1–11
parts used in configuring, 1–11

I–6

HSG80 User’s Guide

general description, 1–3
host ports, 1–13
installing
dual-redundant controller configuration,
5–18
single-controller configuration, 5–4
local connection, 2–7
location, 1–13
maintenance features, 4–1
maintenance port, 1–13
multiple-bus failover configuration, 2–11
multiple-bus failover mode, 2–11
node IDs, 3–26
OCP, 1–13
patching controller software with the CLCP
utility, 1–16
program card, 1–13
relationship to cache module, 1–13
release lever, 1–13
removing
dual-redundant controller configuration,
5–15
single-controller configuration, 5–3
replacing
dual-redundant controller configuration,
5–15
single-controller configuration, 5–3
replacing a failed controller with FRUTIL, 1–16
reset button on the OCP, 1–14
self-test, 4–42
showing, B–143
shutting down, 5–48, B–149
single-controller configuration, 2–14
summary of features, 1–4
testing with DILX, 1–15
transparent failover mode, 2–10
troubleshooting with FMU, 1–15
upgrading controller software with the CLCP
utility, 1–16
upgrading software, 6–2
worldwide names, 3–26
fault-management. See FMU

Controller and its cache module
installing
dual-redundant controller configuration,
5–12
removing
dual-redundant controller configuration,
5–9
replacing
dual-redundant controller configuration,
5–9
single-controller configuration, 5–2
Controller termination
events, 4–14
flashing OCP, 4–14
last failure reporting, 4–15
solid OCP, 4–14
Controller, cache module, and ECB
upgrade installation, 6–16
Conventions
typographical, xx
warnings, cautions, tips, notes, xx
Cooling fan
part number, 1–3
Copper support
cabling, 2–14
COPY
ADD MIRRORSET, B–15
mirrorset switches, 3–42
SET mirrorset-name, B–121
CREATE_PARTITION, B–51
CAPACITY, B–52
CYLINDERS, B–52
HEADS, B–52
SECTORS_PER_TRACK, B–52
SIZE, B–51
CREATE_PARTITION container-name
SIZE=percent, B–51
Creating
disks, B–11
mirrorsets, B–15
partitions, 3–61
RAIDsets, B–19

Index

single-disk units, B–33
sparesets, B–23
storageset and device profiles, 3–5
stripesets, B–25
units, B–27
CYLINDERS
CREATE_PARTITION, B–52
INITIALIZE, B–72

D
DAEMON tests, 4–42
Data
backing up with the Clone utility, 1–16
duplicating with the Clone utility, 1–16
Data center cabinet
ECB Y cable, 1–19, 1–28
Data patterns for DILX write test, 4–39
Data transfer rate, 3–49
Data-retention-policy
CLEAR_ERRORS controller
INVALID_CACHE, B–37
DELETE connections, B–55
DELETE container-name, B–57
DELETE FAILEDSET, B–59
DELETE FAILEDSET disk-name, B–59
DELETE SPARESET, B–61
DELETE SPARESET disk-name, B–61
DELETE unit-number, B–63
Deleting
devices, B–57
mirrorsets, B–57
patches, 6–6 to 6–7
RAIDsets, B–57
software patches, 6–6 to 6–7
storagesets, 3–65, B–57
stripesets, B–57
units, B–63
Describing event codes, 4–18
DESTROY, 3–52
INITIALIZE, B–73

I–7

DESTROY_PARTITION, B–65
DESTROY_PARTITION container-name
PARTITION=partition-number, B–65
DESTROY_UNFLUSHABLE_DATA
SET, B–129
SET NOMULTIBUS_FAILOVER, B–131
DESTROY_UNFLUSHED_DATA
CLEAR_ERRORS controller
INVALID_CACHE, B–37
Device bus interconnect, 1–5
Device ports
checking status, 4–28
LEDs, 1–13
number supported, 1–5
Device profile, A–2, C–9
Device protocol, 1–5
Device statistics utility. See DSTAT utility
Device switches, 3–39, 3–44
changing switches, 3–39
device transfer rate, 3–46
enabling switches, 3–39
NOTRANSPORTABLE, 3–44
TRANSFER_RATE_REQUESTED, 3–46
transportability, 3–44
TRANSPORTABLE, 3–44
Device targets. See Devices
Device transfer rate, 3–46
Device_type codes, 4–18
Devices
adding with the CONFIG utility, 1–15
changing switches, 3–66 to 3–67
checking communication with controller, 4–24
checking I/O, 4–26
checking port status, 4–28
checking status, 4–26
creating a profile, 3–5
exercising, 4–37
finding, 4–37
generating a new volume serial number with the
CHVSN utility, 1–17
largest supported, 1–6, 2–2
locating, B–77

I–8

HSG80 User’s Guide

mapping in subsystem, 4–25
maximum number in striped mirrorsets, 1–6,
2–2
maximum number supported, 1–5, 2–2
number per port, 1–5
renaming the volume serial number with the
CHVSN utility, 1–17
replacing, 5–47
setting data transfer rate, B–12, B–111
SHOW device-type, B–144
showing, B–143
testing read and write capability, 4–38
testing read capability, 4–37
transfer rate, 3–46
upgrading firmware, 6–11
Diagnostics
ECB charging, 1–29
listing of, B–67
running, B–95
DILX, 4–37
general description, 1–15
DILX, running, B–95
DIMMs
cache module memory configurations, 1–18
installing, 5–44
dual-redundant controller configuration,
5–44
single-configuration controller, 5–44
removing, 5–43
dual-redundant controller configuration,
5–43
single-configuration controller, 5–43
replacing, 5–42
replacing in a dual-redundant controller
configuration, 5–42
replacing in a single-configuration controller,
5–42
supported, 1–5
DIRECT, running, B–96
DIRECTORY, B–67
DISABLE_ACCESS
SET unit-number, B–138

DISABLE_ACCESS_PATH
ADD UNIT, B–28
Disabling
autospare, 3–65
Disabling the ECBs
shutting down the subsystem, 5–48
Disk drive. See devices
Disk drives
adding, 3–55
adding to configuration, B–11
adding to spareset using CLI, 3–63
adding with the CONFIG utility, 1–15
array, 3–8
corresponding storagesets, 3–32
deleting, B–57
displaying information, B–143
dividing, 3–37
formatting with HSUTIL, 1–16
generating a new volume serial number with the
CHVSN utility, 1–17
generating read and write loads with DILX,
1–15
initializing, B–71
investigating data transfer with DILX, 1–15
largest device supported, 1–6, 2–2
making transportable, B–111
mirroring, B–79
monitoring performance with DILX, 1–15
partitioning, 3–61
partitions supported, 2–2
removing from a mirrorset, B–85
removing from sparesets using CLI, 3–64
removing from the failedset, B–59
removing from the spareset, B–61
renaming, B–89
renaming the volume serial number with the
CHVSN utility, 1–17
setting device data transfer rate, B–12
showing, B–143 to B–144
transfer rate, B–12
upgrading the firmware with HSUTIL, 1–16

Index

Disk inline exerciser
general description, 1–15
DISKS
SHOW device-type, B–144
Display. See VTDPY
Displaying
current FMU settings, 4–22
event codes, 4–18
last-failure codes, 4–17
memory-system failures, 4–17
switches, 3–66
Distributing
first member of multiple mirrorsets, 3–13
members across ports, 3–14, 3–16
members of storageset, 3–10
Dividing storagesets, 3–37
Documentation, related, xxiii
Downloading
software, 6–3
DSTAT, running, B–96
Dual-battery ECB
part number, 1–4, 1–28
Dual-redundant controller configuration
connecting to host, one hub, 2–21, 2–23
connecting to host, two hubs, 2–18, 2–20
connecting to the host, 2–17
using one hub, 2–21
using two hubs, 2–17
disabling, B–129, B–131
ECB, 1–28
enabling, B–119
installing
cache module, 5–24
controller, 5–18
controller and its cache module, 5–12
DIMMs, 5–44
GLM, 5–33
multiple-bus failover mode, 2–11

I–9

removing
cache module, 5–21
controller, 5–15
controller and its cache module, 5–9
DIMMs, 5–43
GLM, 5–32
replacing
cache module, 5–21
controller, 5–15
controller and its cache module, 5–9
DIMMs, 5–42
ECB, 5–27
ECB with cabinet powered off, 5–29
ECB with cabinet powered on, 5–28
I/O module, 5–39
PCMCIA card, 5–46
PVA module in the first expansion enclosure, 5–36
PVA module in the master enclosure, 5–34
PVA module in the second expansion enclosure, 5–36
replacing modules, 5–8
transparent failover mode, 2–10
upgrading from single controller, 6–16
when to use, 2–10

E
ECB
as a default backup source, 1–21
battery hysteresis, 1–29
diagnostics, 1–29
disabling
shutting down the subsystem, 5–48
dual-battery ECB part number, 1–4, 1–28
dual-redundant controller configuration
replacing with cabinet powered off, 5–29
replacing with cabinet powered on, 5–28
enabling
shutting down the subsystem, 5–48
general description, 1–28
maintenance period, 1–28
replacing, 5–27

I–10

HSG80 User’s Guide

replacing ECBs with FRUTIL, 1–16
replacing in a dual-redundant controller
configuration, 5–27
replacing in a single-configuration controller,
5–27
replacing with cabinet powered off, 5–29
replacing with cabinet powered on, 5–28
single-battery ECB part number, 1–4, 1–28
single-controller configuration
replacing with cabinet powered off, 5–29
replacing with cabinet powered on, 5–28
ECB Y cable
BA370 enclosure
part numbers, 1–19
data center cabinet
part numbers, 1–19
part numbers, 1–28
Electrostatic discharge precautions, xviii, 5–1,
6–1
EMU
part number, 1–3
setting, B–113
ENABLE_ACCESS
SET unit-number, B–138
ENABLE_ACCESS_PATH
ADD UNIT, B–28
Enabling
AUTOSPARE, 3–65
Enabling switches
devices, 3–39
storagesets, 3–39
Enabling the ECBs
shutting down the subsystem, 5–48
Enclosure template, A–4
Enclosures
addressing with the PVA module, 2–6
PVA ID, 2–6
Erasing metadata, 3–53
Error messages
clearing from CLI, B–35
clearing unwriteable data errors, B–43

ESD card cover
part number, 1–9
Event codes
list, D–84
structure, 4–19
translating, 4–18
types, 4–18
Event threshold codes, 4–18
Events
controller termination, 4–14
flashing OCP, 4–14
last failure reporting, 4–15
solid OCP, 4–14
no controller termination, 4–15
CLI event reporting, 4–16
spontaneous event log, 4–16
Examples
adding disk drives to a spareset, 3–64
cloning a storage unit, 3–21
configuring a mirrorset, 3–57
configuring a RAIDset, 3–58
configuring a single-disk unit, 3–61
configuring a striped mirrorset, 3–60
configuring a stripeset, 3–56
deleting storagesets, 3–66
partitioning a storageset, 3–62
removing disk drives from a spareset, 3–64
Exercisers
DILX, 1–15
See also Utilities and exercisers
Exercising drives and units, 4–37
External cache battery. See ECB

F
Failedset
autospare, 3–65
deleting members, B–59
Failover
disabling, B–129, B–131
general description, 2–10
multiple-bus, 2–11
transparent, 2–10

Index

FANSPEED
SET EMU, B–114
Fault LEDs, 1–13
Fault management utility. See FMU
Fault remedy table, 4–4
Fault-tolerance for write-back caching
general description, 1–21
nonvolatile memory, 1–21
Ferrite bead
part number, 1–10
Fibre cable
installing, 5–45
installing in a dual-redundant controller
configuration, 5–45
installing in a single-configuration controller,
5–45
removing, 5–45
removing in a dual-redundant controller
configuration, 5–45
removing in a single-configuration controller,
5–45
replacing, 5–45
replacing in a dual-redundant controller
configuration, 5–45
replacing in a single-configuration controller,
5–45
Fibre channel
cables
copper, 2–14
optical, 2–15
link error, 4–32
Fibre channel copper cable
10-meter
part number, 1–9
5-meter
part number, 1–9
Fibre channel host status display, 4–33
Fibre channel optical cable
10-meter
part number, 1–11
20-meter
part number, 1–11

I–11

2-meter
part number, 1–11
30-meter
part number, 1–11
50-meter
part number, 1–11
5-meter
part number, 1–11
cleaning instructions, 1–12
Fibre channel optical cable precautions, 1–11
Field Replacement utility. See FRUTIL
Finding
devices, 4–37
Finding devices and storagesets, B–77
Firmware
upgrading with HSUTIL, 6–11
Flashing OCP
events
controller termination, 4–14
FMU
displaying current display settings, 4–22
enabling event logging, 4–20
enabling repair-action logging, 4–20
enabling timestamp, 4–21
enabling verbose logging, 4–20
general description, 1–15, 4–17
interpreting last-failures, 4–17
interpreting memory-system failures, 4–17
logging last-failure codes, 4–20
setting display for, 4–20
translating event codes, 4–18
FMU, running, B–96
Formatting
disk drives with HSUTIL, 1–16
FRUTIL
general description, 1–16
FRUTIL, running, B–96
FULL
SHOW, B–145

I–12

HSG80 User’s Guide

G
GLM
copper
part number, 1–9
installing, 5–33
installing in a dual-redundant controller
configuration, 5–33
installing in a single-configuration controller,
5–33
optical
part number, 1–11
removing, 5–32
removing in a dual-redundant controller
configuration, 5–32
removing in a single-configuration controller,
5–32
replacing, 5–32
replacing in a dual-redundant controller
configuration, 5–32
replacing in a single-configuration controller,
5–32

H
HEADS
CREATE_PARTITION, B–52
INITIALIZE, B–72
HELP, B–69
History, revision of this manual, xxiv
Host
checking transfer rate to controller, 4–24
how it works with the controller and subsystem,
1–7 to 1–8
protocol supported, 1–4
Host bus interconnect, 1–4
Host port
checking status, 4–24
Host ports
location, 1–13
Host-assisted failover. See Failover, Multiple-bus
failover
HP800 operating system connection
9-pin adapter part number, 1–10

HSG80 Array Controller Subsystem. See Storage
subsystem
HSG80 Array Controller. See Controller
HSUTIL
general description, 1–16
messages, 6–14
upgrading device firmware, 6–11
HSUTIL, running, B–96
HSZterm. See remote connection
Hub
cabling for single configuration
copper, 2–14
optical, 2–15
installing, 5–45
installing in a dual-redundant controller
configuration, 5–45
installing in a single-configuration controller,
5–45
removing, 5–45
removing in a dual-redundant controller
configuration, 5–45
removing in a single-configuration controller,
5–45
replacing, 5–45
replacing in a dual-redundant controller
configuration, 5–45
replacing in a single-configuration controller,
5–45
Hubs
cabling for dual-redundant controller
configuration, 2–17, 2–21
Hysteresis. See Battery hysteresis

I
I/O
checking to devices, 4–26
checking to host, 4–24
checking to units, 4–29
investigating I/O activity of units with VTDPY,
1–15
logging I/O activity with DSTAT, 1–17
request routing, 3–36

Index

I/O module
part number, 1–3
replacing, 5–39
replacing in a dual-redundant controller
configuration, 5–39
replacing in a single-configuration controller,
5–39
IDENTIFIER
SET controller, B–106
SET unit-number, B–139
IGNORE_ERRORS
RESTART controller, B–91
SELFTEST controller, B–99
SHUTDOWN controller, B–149
IMMEDIATE_SHUTDOWN
RESTART controller, B–91
SELFTEST controller, B–99
SHUTDOWN controller, B–149
INITIALIZE, B–71
CAPACITY, B–72
changing, 3–67
CHUNKSIZE, B–72
CYLINDERS, B–72
DESTROY, B–73
HEADS, B–72
NODESTROY, B–73
NOSAVE_CONFIGURATION, B–73
SAVE_CONFIGURATION, B–73
saving user data, B–73
SECTORS_PER_TRACK, B–72
INITIALIZE container-name, B–71
Initialize switches, 3–47
chunk size, 3–47
CHUNKSIZE, 3–47
DESTROY, 3–52
destroy/nodestroy, 3–52
NODESTROY, 3–52
save configuration, 3–50
SAVE_CONFIGURATION, 3–50

I–13

Installing
cache module
dual-redundant controller configuration,
5–24
single-controller configuration, 5–7
controller
dual-redundant controller configuration,
5–18
single-controller configuration, 5–4
controller and its cache module
dual-redundant controller configuration,
5–12
controller, cache module, and ECB, 6–16
DIMMs, 5–44
dual-redundant controller configuration,
5–44
single-controller configuration, 5–44
dual-redundant controller configuration
cache module, 5–24
controller, 5–18
controller and its cache module, 5–12
DIMMs, 5–44
fibre cable, 5–45
GLM, 5–33
hub, 5–45
fibre cable, 5–45
dual-redundant controller configuration,
5–45
single-controller configuration, 5–45
GLM, 5–33
hub, 5–45
dual-redundant controller configuration,
5–45
single-controller configuration, 5–45
mirrorset member, 5–47
patches, 6–6
PCMCIA card, new, 6–2
RAIDset member, 5–47

I–14

HSG80 User’s Guide

single-controller configuration
cache module, 5–7
controller, 5–4
DIMMs, 5–44
fibre cable, 5–45
GLM, 5–33
hub, 5–45
software patches, 6–6
Instance codes, D–18 to D–35
structure, 4–19
translating, 4–18
Interpreting event codes, 4–19

J
JBOD, 3–8

L
Largest device supported, 1–6, 2–2
Last failure codes
list, D–38 to D–76
Last failure reporting
events
controller termination, 4–15
Last-failure codes
displaying, 4–17
logging, 4–20
structure, 4–19
translating, 4–18
LED codes
flashing patterns, C–8
solid patterns, C–3
LEDs, 1–13
Link errors
fibre channel, 4–32
Listing
patches, 6–6, 6–9
software patches, 6–6, 6–9
Listing diagnostics and utilities, B–67
Local connection
connecting to the controller, 2–7
illustration of terminal to maintenance port, 2–7

Local terminal
connecting through the maintenance port, 1–14
Local terminal port. See Maintenance port
LOCATE, B–77
ALL, B–77
CANCEL, B–77
container-name, B–78
DISKS, B–77
parameter, B–77
PTL (SCSI-location), B–77
unit-number, B–78
UNITS, B–78
Locating
devices, 4–37
Locking the program card, 6–4
Logging
enabling in FMU, 4–20
enabling verbose logging, 4–20
timestamping, 4–21
Lost data error, clearing, B–41
LUN, 2–2

M
Maintenance features, 4–1
Maintenance port
establishing a local connection to the controller,
2–7
general description, 1–14
location, 1–13
precautions, xix
terminal or PC connection, 2–7
See also Maintenance port cable, Terminal
connection
Maintenance port cable
establishing a local connection to the array
controller, 2–7
part number, 1–9
PC or terminal connection illustration, 1–10
terminal connection part number, 1–10
See also Maintenance port, Terminal connection

Index

Map of devices in subsystem, 4–25
Mapping storagesets, 3–32
Maximum LUN capacity, 2–2
MAXIMUM_CACHED_TRANSFER
ADD UNIT, B–29
SET unit-number, B–139
Mean time between failures, 3–10
Member
replacing, 5–47
Members
distributing first member of mirrorset, 3–13
distributing on bus, 3–13 to 3–14, 3–16
MEMBERSHIP
SET mirrorset-name, B–121
Membership
RAIDset switches, 3–41
Memory-system failures, 4–17
Metadata
erasing, 3–65
retaining, 3–65
MIRROR, B–79
COPY, B–79
POLICY, B–80
MIRROR disk-name mirrorset-name, B–79
Mirrored write-back cache
enabling, 2–12
MIRRORED_CACHE
SET controller, B–106
Mirrorset member
installing, 5–47
removing, 5–47
Mirrorset switches, 3–42
COPY, 3–42
POLICY, 3–42
READ_SOURCE, 3–43
Mirrorsets
actual number of members, B–85
adding to configuration, B–15
changing switches, 3–66
choosing a replacement member, B–19
configuring using CLI, 3–56
converting back to a single device, B–151

I–15

creating from a single disk, B–79
deleting, B–57
description, 3–2, 3–12
displaying information, B–143
duplicating data with the Clone utility, 1–16
initializing, B–71
manually removing a member, B–122
maximum number of members, 2–2
planning, 3–12
removing a member, B–85
renaming, B–89
setting a replacement policy, B–19
showing, B–143
temporary from CLONE, 3–19
unmirroring, B–151
Moving storagesets, 3–72
MTBF. See Mean time between failures
Multiple-bus failover configuration
when to use, 2–11
Multiple-bus failover mode
general description, 2–11

N
NO_OVERRIDE_BAD_FLUSH
POWEROFF, B–83
NOAUTOSPARE
SET FAILEDSET, B–117
NOCACHE_UPS
SET controller, B–105
NOCOMMAND_CONSOLE_LUN
SET controller, B–106
Node IDs, 3–26
NODE_ID
SET controller, B–107
NODESTROY, 3–52
INITIALIZE, B–73
NODESTROY_UNFLUSHABLE_DATA
SET NOMULTIBUS_FAILOVER, B–131
NODESTROY_UNFLUSHED_DATA
CLEAR_ERRORS controller
INVALID_CACHE, B–37

I–16

HSG80 User’s Guide

NOIDENTIFIER
SET controller, B–106
SET unit-number, B–139
NOIGNORE_ERRORS
RESTART controller, B–91
SELFTEST controller, B–99
SHUTDOWN controller, B–149
NOIMMEDIATE_SHUTDOWN
RESTART controller, B–91
SELFTEST controller, B–99
SHUTDOWN controller, B–149
NOMIRRORED_CACHE
SET controller, B–106
Nonvolatile memory
fault-tolerance for write-back caching, 1–21
NOPOLICY
ADD RAIDSET, B–19
NOPREFERRED_PATH
ADD UNIT, B–30
SET unit-number, B–139
NOREAD_CACHE
ADD UNIT, B–31
SET unit-number, B–140
NOREADAHEAD_CACHE
ADD UNIT, B–31
SET unit-number, B–140
NOREDUCED
ADD RAIDSET, B–21
NORUN
ADD UNIT, B–31
SET unit-number, B–140
NOSAVE_CONFIGURATION, 3–50
INITIALIZE, B–73
Note, defined, xxi
NOTERMINAL_PARITY
SET controller, B–108
NOTRANSPORTABLE, 3–44
ADD DISK, B–12
SET device-name, B–111
NOWRITE_PROTECT
ADD UNIT, B–32
SET unit-number, B–141

NOWRITEBACK_CACHE
ADD UNIT, B–32
SET unit-number, B–141

O
OCP
fault LEDs, 1–13
general description, 1–13
location, 1–13
reset button, 1–13
Operator control panel. See OCP
Optical support
cabling, 2–15
Options
for devices, 3–44
for RAIDsets, 3–40
for storage units, 3–54
initialize, 3–47
Other controller
explained, B–2
OVERRIDE_BAD_FLUSH
POWEROFF, B–83
Overwriting data, 3–52

P
Part numbers
256-MB cache upgrade, 1–19
64-MB cache upgrade, 1–19
AC input module, 1–3
access door, 1–9
BA370 rack-mountable enclosure, 1–3
BC16E-xx cable assembly, 1–10
cache module, 1–3
cooling fan, 1–3
dual-battery ECB, 1–4, 1–28
ECB, 1–4, 1–28
ECB Y cable, 1–28
BA370 enclosure, 1–19
data center cabinet, 1–19
EMU, 1–3
ESD card cover, 1–9
ferrite bead, 1–10

Index

fibre channel copper cable
10-meter, 1–9
5-meter, 1–9
fibre channel copper cabling
parts used in configuring the controller, 1–9
fibre channel optical cable
10-meter, 1–11
20-meter, 1–11
2-meter, 1–11
30-meter, 1–11
50-meter, 1–11
5-meter, 1–11
fibre channel optical cabling
parts used in configuring the controller,
1–11
GLM
copper, 1–9
optical, 1–11
HSG80 subsystem, 1–3
I/O module, 1–3
maintenance port cable, 1–9
maintenance port cable for a terminal
connection, 1–10
PC serial port adapter, 1–10
power supply, 1–4
program card, 1–9
PVA module, 1–3
RJ-11 adapter, 1–10
RJ-11 extension cable, 1–10
single-battery ECB, 1–4, 1–28
PARTITION
ADD UNIT, B–29
Partitioning
disk drives, 3–61
storagesets using CLI, 3–61
Partitions
creating, B–51
defining, 3–37
deleting unit, B–63
displaying size, B–143
guidelines, 3–38
maximum supported, 1–6, 2–2

I–17

planning, 3–37
setting size, B–51
showing, B–143
Patches
deleting, 6–7
installing, 6–6
listing, 6–9
listing, installing, deleting, 6–6
PC connection
9-pin adapter part number, 1–10
optional maintenance port cable, 1–10
part number for the optional maintenance port
cable, 1–10
See also optional maintenance port cable
PC serial port adapter
part number, 1–10
PCMCIA card
installing a new card, 6–2
replacing, 5–46
dual-redundant controller configuration,
5–46
single-configuration controller, 5–46
Performance, 3–15
Planning
mirrorsets, 3–12
overview, 3–5
partitions, 3–37
RAIDsets, 3–16
storagesets, 3–8
striped mirrorsets, 3–18
stripesets, 3–10
POLICY, 3–42
ADD MIRRORSET, B–16
ADD RAIDSET, B–19
MIRROR, B–80
RAIDset switches, 3–40
SET mirrorset-name, B–123
SET RAIDset-name, B–133
PORT_1_ALPA
SET controller, B–107
PORT_1_TOPOLOGY
SET controller, B–108

I–18

HSG80 User’s Guide

PORT_2_ALPA
SET controller, B–107
PORT_2_TOPOLOGY
SET controller, B–108
Ports
See also Device ports, Host ports
Power source
enabling write-back caching, 1–21
Power supply
part number, 1–4
Power, verification, and addressing module. See
PVA module
POWEROFF, B–83
BATERY_ON, B–83
BATTERY_OFF, B–83
NO_OVERRIDE_BAD_FLUSH, B–83
OVERRIDE_BAD_FLUSH, B–83
SECONDS, B–83
Precautions
electrostatic discharge, xviii
fibre channel optical cable, 1–11
maintenance port, xix
PREFERRED_PATH
ADD UNIT, B–30
PREFERRRED_PATH
SET unit-number, B–139
Problem solving, 4–2
Profiles
creating, 3–5
description, 3–5
device, A–2, C–9
storageset, A–3
Program card
ESD cover, 1–9
location, 1–13
part number, 1–9
write-protection switch, 6–4
PROMPT
SET controller, B–108
Protocol
device, 1–5
host, 1–4

PTL
addressing convention, 3–33
Publications, related, xxiii
PVA ID, 2–6
PVA module
part number, 1–3
replacing, 5–34
first expansion enclosure, 5–36
master enclosure, 5–34
second expansion enclosure, 5–36
replacing in a dual-redundant controller
configuration, 5–34
first expansion enclosure, 5–36
master enclosure, 5–34
second expansion enclosure, 5–36
replacing in a single-configuration controller,
5–34
first expansion enclosure, 5–36
master enclosure, 5–34
second expansion enclosure, 5–36
setting the switch, 2–6

R
RAID levels supported, 1–5
RAID-5 and RAID-1 storagesets
maximum number, 1–5, 2–2
RAID-5 storagesets
maximum number, 1–5, 2–2
maximum number of members, 2–2
RAID-5, RAID-1, and RAID-0 storagesets
maximum number, 1–6, 2–2
RAIDset
specifying chunksize, B–72
RAIDset member
installing, 5–47
removing, 5–47
RAIDset switches, 3–40
membership, 3–41
NOREDUCED, 3–41
POLICY, 3–40
RECONSTRUCT, 3–40
reconstruction policy, 3–40

Index

REDUCED, 3–41
replacement policy, 3–40
RAIDsets
adding to configuration, B–19
adding while missing a member, B–21
changing characteristics, B–133
changing switches, 3–66
choosing chunk size, 3–47
configuring using CLI, 3–57
deleting, B–57
description, 3–2, 3–15
displaying information, B–143
initializing, B–71
maximum chunk size, 3–50
maximum membership, 3–16
planning, 3–16
removing a member, B–134
renaming, B–89
replacing a member, B–135
showing, B–143
specifying replacement policy, B–133
switches, 3–40
Rate of transfer, checking to host, 4–24
Read caching
enabled for all storage units, 1–20
general description, 1–20
Read capability, testing, 4–37
READ_CACHE
ADD UNIT, B–31
SET unit-number, B–140
READ_SOURCE
ADD MIRRORSET, B–16
mirrorset switches, 3–43
SET mirrorset-name, B–124
Read-ahead caching, 1–20
enabled for all disk units, 1–20
READAHEAD_CACHE
ADD UNIT, B–31
SET unit-number, B–140
RECONSTRUCT
ADD RAIDSET, B–20
RAIDset switches, 3–40

I–19

SET RAIDset-name, B–134
REDUCE, B–85
REDUCE disk-nameN, B–86
REDUCED
ADD RAIDSET, B–21
Reduced storageset, 5–47
Related publications, xxiii
Relationship
controller to cache module, 1–13
Release lever
location, 1–13
Remedies, 4–4
REMOVE
SET mirrorset-name, B–122
SET RAIDset-name, B–134
Removing
cache module
dual-redundant controller configuration,
5–21
single-controller configuration, 5–6
controller
dual-redundant controller configuration,
5–15
single-controller configuration, 5–3
controller and its cache module
dual-redundant controller configuration,
5–9
DIMMs, 5–43
dual-redundant controller configuration,
5–43
single-controller configuration, 5–43
disk drives from sparesets, 3–64
dual-redundant controller configuration
cache module, 5–21
controller, 5–15
controller and its cache module, 5–9
DIMMs, 5–43
fibre cable, 5–45
GLM, 5–32
hub, 5–45
failed mirrorset member, 5–47
failed RAIDset member, 5–47

I–20

HSG80 User’s Guide

fibre cable, 5–45
dual-redundant controller configuration,
5–45
single-controller configuration, 5–45
GLM, 5–32
hub, 5–45
dual-redundant controller configuration,
5–45
single-controller configuration, 5–45
single-controller configuration
cache module, 5–6
controller, 5–3
DIMMs, 5–43
fibre cable, 5–45
GLM, 5–32
hub, 5–45
Removing a mirrorset member, B–85
RENAME, B–89
RENAME old-container-name new-containername, B–89
Renaming, B–89
Repair action codes
list, D–77 to D–81
Repair-action codes
logging, 4–20
translating, 4–18
REPLACE
SET mirrorset-name, B–123
Replacement policy
mirrorsets, 3–42
REPLACESET RAIDset-name, B–135
Replacing
cache module
dual-redundant controller configuration,
5–21
single-controller configuration, 5–6
controller
dual-redundant controller configuration,
5–15
single-controller configuration, 5–3

controller and its cache module
dual-redundant controller configuration,
5–9
single-controller configuration, 5–2
DIMMs, 5–42
dual-redundant controller configuration,
5–42
single-controller configuration, 5–42
dual-redundant controller configuration, 5–8
cache module, 5–21
controller, 5–15
controller and its cache module, 5–9
DIMMs, 5–42
ECB, 5–27
ECB with cabinet powered off, 5–29
ECB with cabinet powered on, 5–28
fibre cable, 5–45
GLM, 5–32
hub, 5–45
I/O module, 5–39
PCMCIA card, 5–46
PVA module, 5–34
PVA module, first expansion enclosure,
5–36
PVA module, master enclosure, 5–34
PVA module, second expansion enclosure,
5–36
ECB, 5–27 to 5–28
ECB with cabinet powered off, 5–29
ECB with cabinet powered on, 5–28
fibre cable, 5–45
dual-redundant controller configuration,
5–45
single-controller configuration, 5–45
GLM, 5–32
hub, 5–45
dual-redundant controller configuration,
5–45
single-controller configuration, 5–45
I/O module, 5–39

Index

modules
dual-redundant controller configuration,
5–8
modules in a single-controller configuration,
5–2
PCMCIA card, 5–46
PVA module, 5–34
first expansion enclosure, 5–36
master enclosure, 5–34
second expansion enclosure, 5–36
single-controller configuration, 5–2
cache module, 5–6
controller, 5–3
DIMMs, 5–42
ECB, 5–27
ECB with cabinet powered off, 5–29
ECB with cabinet powered on, 5–28
fibre cable, 5–45
GLM, 5–32
hub, 5–45
I/O module, 5–39
PCMCIA card, 5–46
PVA module, 5–34
PVA module, first expansion enclosure,
5–36
PVA module, master enclosure, 5–34
PVA module, second expansion enclosure,
5–36
storageset member, 5–47
Request rate, 3–47
Required tools, xxii
Resetting configuration, B–45
RESTART controller
IGNORE_ERRORS, B–91
IMMEDIATE_SHUTDOWN, B–91
NOIGNORE_ERRORS, B–91
NOIMMEDIATE_SHUTDOWN, B–91

Restart_type codes, 4–18
Restarting the subsystem, 5–50
Restoring configuration, B–47
RETRY_ERRORS unit-number
UNWRITEABLE_DATA, B–93
Revision history, xxiv
RJ-11 adapter
part number, 1–10
RJ-11 extension cable
part number, 1–10
RUN, B–95
ADD UNIT, B–31
CHVSN, B–95
CLCP, B–95
CLONE, B–95
CONFIG, B–95
DILX, B–95
DIRECT, B–96
DSTAT, B–96
FMU, B–96
FRUTIL, B–96
HSUTIL, B–96
SET unit-number, B–140
VTDPY, B–96
RUN program name, B–95
Running
controller self-test, 4–42
DAEMON tests, 4–42
DILX, 4–37
FMU, 4–17
VTDPY, 4–23

S
Save configuration, 3–50
SAVE_CONFIGURATION, 3–50
INITIALIZE, B–73
Saving configurations, B–49
dual-redundant configurations, 3–52

I–21

I–22

HSG80 User’s Guide

SCSI command operations, 4–18
SCSI device ports. See Device ports
SCSI device targets. See Devices
SCSI target ID numbers. See Target ID numbers
SCSI_VERSION
SET controller, B–108
SECONDS
POWEROFF, B–83
SECTORS_PER_TRACK
CREATE_PARTITION, B–52
INITIALIZE, B–72
Self-test, 4–42
SELFTEST controller, B–99
IGNORE_ERRORS, B–99
IMMEDIATE_SHUTDOWN, B–99
NOIGNORE_ERRORS, B–99
NOIMMEDIATE_SHUTDOWN, B–99
SENSOR_N_SETPOINT
SET EMU, B–113
Serial interconnect speed, 1–6
SET controller, B–103
ALLOCATION_CLASS, B–105
CACHE_FLUSH_TIMER, B–105
CACHE_UPS, B–105
COMMAND_CONSOLE_LUN, B–106
IDENTIFIER, B–106
MIRRORED_CACHE, B–106
NOCACHE_UPS, B–105
NOCOMMAND_CONSOLE_LUN, B–106
NODE_ID, B–107
NOIDENTIFIER, B–106
NOMIRRORED_CACHE, B–106
NOTERMINAL_PARITY, B–108
PORT_1_ALPA, B–107
PORT_1_TOPOLOGY, B–108
PORT_2_ALPA, B–107
PORT_2_TOPOLOGY, B–108
PROMPT, B–108
SCSI_VERSION, B–108
TERMINAL_PARITY, B–108
TERMINAL_SPEED, B–109
TIME, B–109

SET device-name, B–111
NOTRANSPORTABLE, B–111
TRANSFER_RATE_REQUESTED, B–111
TRANSPORTABLE, B–111
SET EMU, B–113
FANSPEED, B–114
SENSOR_N_SETPOINT, B–113
SET FAILEDSET, B–117
AUTOSPARE, B–117
NOAUTOSPARE, B–117
SET FAILOVER, B–119
SET FAILOVER COPY=controller, B–119
SET mirrorset-name, B–121
COPY, B–121
MEMBERSHIP, B–121
POLICY, B–123
READ_SOURCE, B–124
REMOVE, B–122
REPLACE, B–123
SET MULTIBUS_FAILOVER, B–127
SET NOFAILOVER, B–129
DESTROY_UNFLUSHABLE_DATA, B–129
NODESTROY_UNFLUSHABLE_DATA,
B–129
SET NOMULTIBUS_FAILOVER, B–131
DESTROY_UNFLUSHABLE_DATA, B–131
NODESTROY_UNFLUSHABLE_DATA,
B–131
SET RAIDset-name, B–133
POLICY, B–133
RECONSTRUCT, B–134
REMOVE, B–134
REPLACE, B–135
SET unit-number, B–137
DISABLE_ACCESS, B–138
ENABLE_ACCESS, B–138
IDENTIFIER, B–139
MAXIMUM_CACHED_TRANSFER, B–139
NOIDENTIFIER, B–139
NOPREFERRED_PATH, B–139
NOREAD_CACHE, B–140
NOREADAHEAD_CACHE, B–140

Index

NORUN, B–140
NOWRITE_PROTECT, B–141
NOWRITEBACK_CACHE, B–141
PREFERRED_PATH, B–139
READ_CACHE, B–140
READAHEAD_CACHE, B–140
RUN, B–140
WRITE_PROTECT, B–141
WRITEBACK_CACHE, B–141
Setting
cache flush timer, B–105
CLI prompt, B–108
control of metadata, B–73
controller behavior at restart, B–91
controller behavior at shutdown, B–149
controller behavior selftest, B–99
controller cache flush timer, B–105
controller cache UPS policy, B–105
controller configuration handling, B–73
controller error handling at self-test, B–91, B–99
controller error handling at shutdown, B–149
data retention policy, B–37
device data transfer rate, B–12, B–111
display characteristics for FMU, 4–20
failedset autospare feature, B–117
fan speed, B–114
full display, B–145
mirrorset copy data, B–79
mirrorset copy speed, B–15, B–79, B–121
mirrorset member read source, B–16, B–124
mirrorset read source, B–16, B–124
mirrorset spareset replacement policy, B–16,
B–80, B–123
nofailover cached data policy, B–129
number of blocks cached by controller, B–29,
B–139
number of mirrorset members, B–121
number of unit partitions, B–29
partition size, B–37, B–51
RAIDset member reconstruct policy, B–20,
B–134

I–23

RAIDset member replacement policy, B–16,
B–19, B–124
read cache for units, B–31, B–140
storageset chunksize, B–72
subsystem temperature sensor setpoint, B–113
terminal parity, B–108
terminal speed, B–109
time, B–109
transportability of devices, B–111
transportability of disks, B–12, B–111
unit availability to the host, B–31, B–140
write protect for units, B–32, B–141
write-back cache for units, B–32, B–141
SHOW, B–143
FULL, B–145
SHOW controller, B–143
SHOW device-name, B–143
SHOW device-type, B–144
DEVICES, B–144
DISKS, B–144
SHOW EMU, B–144
SHOW storageset-name, B–144
SHOW storageset-type, B–144
FAILEDSET, B–144
MIRRORSETS, B–144
RAIDSETS, B–144
SPARESETS, B–144
STORAGESETS, B–144
STRIPESETS, B–144
SHOW unit-number, B–144
SHOW UNITS, B–144
SHUTDOWN controller, B–149
IGNORE_ERRORS, B–149
IMMEDIATE_SHUTDOWN, B–149
NOIGNORE_ERRORS, B–149
NOIMMEDIATE_SHUTDOWN, B–149
Shutting down the subsystem, 5–48
disabling the ECBs, 5–48
enabling the ECBs, 5–48
Significant event reporting, 4–14
Single-battery ECB
part number, 1–4, 1–28

I–24

HSG80 User’s Guide

Single-controller configuration
connecting to the host using one hub, 2–14
ECB, 1–28
installing
cache module, 5–7
controller, 5–4
DIMMs, 5–44
GLM, 5–33
removing
cache module, 5–6
controller, 5–3
DIMMs, 5–43
GLM, 5–32
replacing
cache module, 5–6
controller, 5–3
controller and its cache module, 5–2
DIMMs, 5–42
ECB, 5–27
ECB with cabinet powered off, 5–29
ECB with cabinet powered on, 5–28
GLM, 5–32
I/O module, 5–39
PCMCIA card, 5–46
PVA module, 5–34
PVA module in the first expansion enclosure, 5–36
PVA module in the master enclosure, 5–34
PVA module in the second expansion enclosure, 5–36
replacing modules, 5–2
upgrading to dual-redundant controller
configuration, 6–16
Single-disk units
backing up, 3–19
configuring with CLI, 3–60
displaying switches, 3–66
SIZE
CREATE_PARTITION, B–51
Software
patches, 6–6
upgrading, 6–2

Software patches
deleting, 6–7
installing, 6–6
listing, 6–9
listing, installing, deleting, 6–6
Solid OCP
events
controller termination, 4–14
Sparesets
adding disk drives using CLI, 3–63
adding to configuration, B–23
AUTOSPARE, 3–65
removing a disk drive, B–61
removing disk drives using CLI, 3–64
Speed. See transfer rate
Spontaneous event log
no controller termination, 4–16
Starting the subsystem, 5–50
Status
device ports, 4–28
devices, 4–26
host port, 4–24
units, 4–29
Storage requirements, determining, 3–7
Storage subsystem
typical installation, 1–2
Storageset map, 3–32
Storageset member
replacing, 5–47
Storageset profile, 3–5, A–3
Storageset switches, 3–39
changing switches, 3–39
enabling switches, 3–39
Storagesets
adding devices with the CONFIG utility, 1–15
attributes, 3–8
backing up, 3–19
backing up data with the Clone utility, 1–16
changing switches, 3–66
comparison, 3–8
configuring using CLI, 3–55
creating a profile, 3–5

Index

creating map, 3–32
deleting, 3–65
displaying information, B–143
displaying switches, 3–66
dividing, 3–37
duplicating data with the Clone utility, 1–16
formatting disk drives with HSUTIL, 1–16
generating a new volume serial number with the
CHVSN utility, 1–17
how they work with the host, 1–7
initializing, B–71
largest device supported, 1–6, 2–2
locating, B–77
maximum number of partitions supported, 2–2
mirrorsets, 3–2, 3–12
moving, 3–72
partitioning using CLI, 3–61
planning, 3–8
RAIDsets, 3–2
renaming, B–89
renaming the volume serial number with the
CHVSN utility, 1–17
showing, B–143
striped mirrorsets, 3–2
stripesets, 3–2, 3–8
upgrading the firmware in disk drives with
HSUTIL, 1–16
See also Configuration rules
StorageWorks array controller, B–2
Striped mirrorsets
configuring using CLI, 3–59
description, 3–2, 3–17
maximum number of physical devices, 1–6, 2–2
planning, 3–18
Stripesets
adding to configuration, B–25
configuring using CLI, 3–55
deleting, B–57
description, 3–2, 3–8
displaying information, B–143
initializing, B–71
maximum number of members, 2–2

I–25

mirroring, B–79
planning, 3–10
renaming, B–89
showing, B–143
specifying chunksize, B–72
Structure of event codes, 4–19
Subsystem
addressing with the PVA module, 2–6
connecting a single controller to the host using
one hub, 2–14
connecting dual-redundant controllers to the
host, 2–17
connecting the subsystem to the host, 2–14
illustration of SCSI target ID numbers and PVA
settings, 2–6
restarting, 5–50
saving configuration, 3–50
shutting down, 5–48
upgrading, 6–1
Sun operating system connection
9-pin adapter part number, 1–10
Switches
changing for devices, 3–66 to 3–67
changing for storagesets, 3–66
changing initialize, 3–67
changing mirrorset, 3–66
changing RAIDset, 3–66
changing unit, 3–67
displaying current, 3–66
NOTRANSPORTABLE, 3–44
overview, 3–39
RAIDset, 3–40
TRANSFER_RATE_REQUESTED, 3–46
TRANSPORTABLE, 3–44
Symptoms, 4–4

T
Target ID numbers
illustration of SCSI target ID numbers and PVA
settings, 2–6

I–26

HSG80 User’s Guide

Targets. See Devices
Template, enclosure, A–4
Templates, D–85
Terminal
setting parity, B–108
setting speed, B–109
Terminal connection
optional maintenance port cable, 1–10, 2–7
part number for the optional maintenance port,
1–10
See also Maintenance port, Maintenance port
cable
Terminal display. See VTDPY
Terminal. See Maintenance port
TERMINAL_PARITY
SET controller, B–108
TERMINAL_SPEED
SET controller, B–109
Testing controllers, B–99
Testing read capability, 4–37
This controller
explained, B–2
removing from dual-redundant controller
configuration, B–129, B–131
starting diagnostic or utility programs, B–95
This controller, defined, xx
TIME
SET controller, B–109
Timestamp for logging, 4–21
Tip, defined, xxi
Tools, xxii
Topology
supported, 1–4
Transfer rate
checking to devices, 4–24
checking to host, 4–24
how chunk size affects, 3–47
setting device, B–12, B–111
switch, 3–46
TRANSFER_RATE_REQUESTED, 3–46
ADD DISK, B–12

SET device-name, B–111
Translating event codes, 4–18
Transparent failover mode
general description, 2–10
Transportability, 3–44
TRANSPORTABLE, 3–44
ADD DISK, B–12
SET device-name, B–111
Troubleshooting
backing up data with the Clone utility, 1–16
checklist, 4–2
CLCP utility, 1–16
communication between controller and devices
with VTDPY, 1–15
communication between the controller and hosts
with VTDPY, 1–15
DILX, 1–15
FMU, 1–15
generating a new volume serial number with the
CHVSN utility, 1–17
generating read and write loads with DILX,
1–15
investigating data transfer with DILX, 1–15
investigating I/O activity of units with VTDPY,
1–15
logging I/O activity with DSTAT, 1–17
monitoring performance with DILX, 1–15
patching controller software with the CLCP
utility, 1–16
renaming the volume serial number with the
CHVSN utility, 1–17
replacing a failed controller with FRUTIL, 1–16
replacing cache modules with FRUTIL, 1–16
replacing ECBs with FRUTIL, 1–16
table, 4–4
testing the controller and disk drives with DILX,
1–15
upgrading controller software with the CLCP
utility, 1–16
upgrading EMU software with the CLCP utility,
1–16
VTDPY, 1–15

Index

See also Config utility
See also HSUTIL
Troubleshooting and maintaining the controller
utilities and exercisers, 1–14
Turning off the subsystem, 5–48
Turning on the subsystem, 5–50
Typographical conventions, xx

U
Unit switches
changing, 3–67
overview, 3–54
Units
adding to configuration, B–27
changing characteristics, B–137
checking I/O, 4–29
checking status, 4–29
clearing lost data error, B–41
deleting from the configuration, B–63
displaying configured units, B–144
displaying information, B–143
exercising, 4–37
largest unit supported, 1–6, 2–2
mirroring, B–79
naming with ADD command, B–28
showing, B–143
UNMIRROR, B–151
UNMIRROR disk-name, B–151
Unpartitioned mirrorsets
duplicating data with the Clone utility, 1–16
Unwriteable data error, retrying, B–93
Upgrading
cache memory, 6–20
controller software, 6–2
controller software with the CLCP utility, 1–16
device firmware, 6–11
DIMMs, 6–20
downloading new software, 6–3
EMU software with the CLCP utility, 1–16
installing
controller, cache module, and ECB, 6–16
installing a new program card, 6–2

I–27

single controller to dual-redundant controller,
6–16
using CLCP, 6–6
deleting patches, 6–7
deleting software patches, 6–7
installing patches, 6–6
installing software patches, 6–6
listing patches, 6–9
listing software patches, 6–9
Utilities
CHVSN, B–95
CLCP, B–95
CLONE, B–95
CONFIG, B–95
DILX, B–95
DIRECT, B–96
DSTAT, B–96
FMU, B–96
FRUTIL, B–96
HSUTIL, B–96
listing of, B–67
running, B–95
VTDPY, B–96
Utilities and exercisers
CHVSN utility, 1–17
CLCP utility, 1–16
Clone utility, 1–16
CONFIG utility, 1–15
DILX, 1–15
DSTAT, 1–17
FMU, 1–15
FRUTIL, 1–16
HSUTIL, 1–16
VTDPY, 1–15

V
Verbose logging, 4–20
Virtual terminal display, 1–15
Virtual terminal display. See VTDPY
Volume serial number
generating a new one with the CHVSN utility,
1–17

I–28

HSG80 User’s Guide

renaming with the CHVSN utility, 1–17
VTDPY
checking communication with host, 4–24
commands, 4–23
general description, 1–15, 4–23
running, 4–23
VTDPY, running, B–96

W
Warning, defined, xxi
Worldwide names, 3–26
Write capability, test for devices, 4–38
Write performance, 3–49
Write protection for program card, 6–4
WRITE_PROTECT
ADD UNIT, B–32
SET unit-number, B–141
Write-back caching
enabled for all disk units, 1–21
fault-tolerance, 1–21
general description, 1–21
setting the flush timer, B–105
WRITEBACK_CACHE
ADD UNIT, B–32
SET unit-number, B–141
Write-through caching
enabling and disabling, 1–21
general description, 1–21