Df7150all - df700 Maintenance Manual Rev1 05-05 PDF

DF700 Hitachi Proprietary K6603122-
FE-95DF744-00
DF700
Disk Array Subsystem
Maintenance Manual
REV.1
Read this manual carefully and keep it.
y Before starting operation, read the safety instructions carefully and fully understand them.
y After reading this manual, keep it at hand for your reference.
Copyright 2005, Hitachi, Ltd.

GENE 0000-01
Preface
This manual explains the operation introduction, installation, maintenance, and WEB
of the DF700 disk array subsystem for service personnel to make them understand the
DF700.
This manual contains information on maintenance works of the DF700 series disk array
subsystem such as subsystem outline, structure, installation, and actions against
failures.
When performing a maintenance work, read this manual carefully, and fully
understand the theory of operation, operation procedure, and instructions before
starting the work.
This manual was carefully prepared and reviewed for completeness and correctness.
However, please feel free to contact us concerning any question, mistake, omission,
or any other issues about this manual.

GENE 0010-01
Cautionary Notes
On This Manual
y Hitachi, Ltd. owns the copyrights of the DF700 Maintenance Manual. No part of this manual
may be reused or reproduced without permission of Hitachi, Ltd.
y Hitachi, Ltd. is not liable for any troubles or accidents which are caused by operation not
written in this manual.
y The DF700 Maintenance Manual may be revised without prior notice.
y The subsystem is a class 1 laser system which emits no hazardous laser beam.
Be sure to operate it according to this manual. Do not perform any operations other than
those written in this manual. Otherwise, unexpected failures or accidents may be caused.
The subsystem is a class 1 laser system which emits no hazardous laser beam.
The subsystem complies with FDA radiation performance standards 21CFR subchapter J.
General Cautionary Notes

y It is feared that user data is lost unless the power is turned off correctly following the
specified procedure.
y The Disk Drives are precise components. Never apply them any shock nor vibration.
y When replacing the batteries, turn off the AC Power Unit Switch of the subsystem, charge the
batteries for six hours or longer, and then return the subsystem to the customer.
y In order to protect parts from the electrostatic discharge, every worker must put a wrist band
on his/her wrist before starting installation or maintenance work and start the work after
connecting the grounding clip to a metallic portion of the frame. (The wrist band must be put
on when connecting the LAN or RS232C cable.)
y Do the work with the wrist band put on. Do not put off the wrist band till the work is finished.
y When handling a part, hold it in the way that fingertips of the hand putting the wrist band on
touch a metallic portion of the part.
(The above is necessary in order to discharge the charged static electricity and prevent a
charge caused by handling.)
y Be sure to keep the wrist band close to the subsystem.
y Be sure to touch the subsystem with the wrist band put on. If you touch the subsystem
without putting on the wrist band, the static electricity charged on your body flows to the
subsystem in an instant because no resistance exists between your body and the subsystem
causing a subsystem trouble.
The part to be unpacked and

replaced for maintenance Support a part by touching its metal
part (metal plate) with your fingers
The clip side of wrist strap:

Connect this to the metal part
on the frame of subsystem (rear
A wrist strap (Be sure to wear this before face)
starting maintenance.)

GENE 0020-01
Trademarks
HP is a company name of Hewlett Packard Company, in the U.S.A.

IBM, AIX is a registered trademark of International Business Machines Corp. in the U.S.A.
IRIX is a product name of Sillicon Graphics, Inc. in the U.S.A.
Java and all the brands and logos concerning Java are trade marks or registered
trademarks of Sun Microsystems, Inc. in the United States of America and other countries.
Solaris is a product name of Sun Microsystems, Inc. in the U.S.A.
Sun is a registered trademark of Sun Microsystems, Inc. in the U.S.A.
Windows is a registered trademark of Microsoft Corp, Inc. in the U.S.A. and other
countries.
Other company names and trade names described in this manual are trademarks or
registered trademarks of each respective company.

GENE 0030-01
Note
EMI Regulation
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
instruction manual, may cause harmful interference in which case the user will be
required to correct the interference at his own expense. Testing was done with
shielded cables. Therefore, in order to comply with the FCC regulations, you must
use shielded cables with you installation.
EMI Regulation Labels Affixed on the Subsystem.

"This equipment complies with the This Class A digital apparatus complies
requirements in part 15 of FCC Rules with Canadian ICES-003.
for a Class A computing device and
Part.Vol.122.No.20 of Canada Gazette Cet appareil numerique de la classe A
for a Class A digital apparatus. est conform a la norme NMB-003 du Canada.
Operation of this equipment in a
residential area may cause
unacceptable interference to radio
and TV reception requiring the
operator to take whatever steps are
necessary to correct the interference."
The EMI test was done in the following configuration.

If a trouble occurs in another configuration, a user may be requested to take
appropriate preventive measures.
y DF700-RKM/RKS+H1J
y DF700-RKM/RKS+RKAJ+H2J
y DF700-RKM/RKS+RKAJ(2)+RKAJAT+U7

GENE 0040-01
Model Name Conversion

Throughout this document, product model name is written as DF700. When you want to use
this document for the HT-4064 series, please conversion the model name DF700 with
HT-4064.
Table 1 Conversion Table for Model Name and Other Model Name
The model name which is used The model name
Type
in this document replace to DF700
DF700- HT-4064- Rackmount model (DF700-RKM)
Rackmount model (DF700-RKAJ)
Rackmount model (DF700-RKAJAT)
Rackmount model (DF700-RKS)
Floor model (RKM + H1J)

Floor model (RKS+ H1J)
Floor model (RKM + RKAJ + H2J)
Floor model (RKS + RKAJ + H2J)
DF-F700- HT-F4064- Optional component

Accessory component

GENE 0050-01
Manual Composition
This Maintenance Manual is composed of 13 volumes, that is, Maintenance Manuals- for
Theory, for Maintenance, for Installation, Microprogram, System Parameter,
Addition/Subtraction/ Relocation, ACE, Troubleshooting, Messages, Replacement, Parts
Catalog, and for WEB.
Each volume and chapter has table of contents to help readers to find just the page they
want.
Besides, glossary a contained in each appendix.
For the composition of the each volume, refer to the following.
Maintenance Manual - for Safety Summary :

This Safety Summary volume describes the cautionary notes to handle the maintenance
work safely.
1 About the symbols ....................................................................................................................... SAFE 0020
2 General Safety Guidelines ........................................................................................................... SAFE 0020
3 Hazard Warning Statements ....................................................................................................... SAFE 0070
4 Warning Labels Affixed on the Subsystem .................................................................................. SAFE 0170
Maintenance Manual - for Theory :

This Theory volume describes the cautionary/prohibited notes in the maintenance work,
the outline of the subsystem, and the configuration, etc.
Chapter 1. Warranty and Service ............................................................................................. THEO 01-0000
Chapter 2. Outline of Subsystem ............................................................................................. THEO 02-0000
Chapter 3. Major Specifications of the Subsystem ................................................................... THEO 03-0000
Chapter 4. Theory of Operation ................................................................................................ THEO 04-0000
Chapter 5. Outline of P.P ......................................................................................................... THEO 05-0000
Maintenance Manual - for Installation :

This Installation volume describes the setting of the subsystem and the installation of
the parts, etc.
Chapter 1. Before Starting Installation Work .............................................................................. INST 01-0000
Chapter 2. Installing Floor Model ............................................................................................... INST 02-0000
Chapter 3. Installing Rackmount Model ..................................................................................... INST 03-0000
Maintenance Manual - for Microprogram :

This Microprogram volume describes the new and update installation of the
microprogram.
Chapter 1. Installation of Microprogram ................................................................................. MICRO 01-0000
Chapter 2. Procedure for Recovery from a Failure ................................................................. MICRO 02-0000

GENE 0060-01
Chapter 3. Procedure for Isolating Cause of Disk Drive Failure when

Install partially complete Message Is Output........................ MICRO 03-0000

GENE 0060-01
Maintenance Manual - for System Parameter :

This System Parameter volume describes the setting of the system parameter of the
subsystem, etc.
Chapter 1. Setting (Storage Navigator Modular) .................................................................... SYSPR 01-0000
Chapter 2. Setting Host Group ............................................................................................... SYSPR 02-0000
Chapter 3. Setting the RAID/LU/Spare Disk ........................................................................... SYSPR 03-0000
Chapter 4. Setting Configuration Information ......................................................................... SYSPR 04-0000
Chapter 5. Setting Host Connection Parameters .................................................................... SYSPR 05-0000
Chapter 6. Setting an Extra-cost Optional Feature ................................................................ SYSPR 06-0000
Chapter 7. System Parameter Setting List ............................................................................. SYSPR 07-0000
Maintenance Manual - for Addition/Subtraction/Relocation :

This Addition/Subtraction/Relocation volume describes the addition, subtraction and
relocation related to the setting of the subsystem.
Chapter 1. Adding Optional Components ....................................................................................ADD 01-0000
Chapter 2. Subtracting Optional Components .............................................................................ADD 02-0000
Chapter 3. Relocation/Removal Work .........................................................................................ADD 03-0000
Maintenance Manual - for Troubleshooting :

This Troubleshooting volume describes the trouble analysis of the subsystem, etc.
Chapter 1. Flowchart for troubleshooting ................................................................................... TRBL 01-0000
Chapter 2. Before Maintenance Work ....................................................................................... TRBL 02-0000
Chapter 3. Before Starting WEB Connection ............................................................................ TRBL 03-0000
Chapter 4. Trouble Analysis by WEB connection ...................................................................... TRBL 04-0000
Chapter 5. Procedure for Investigating Disk Array Subsystem Regarding
Fibre Channel Failure ..................... TRBL 05-0000
Chapter 6. Details of Recovery Methods ................................................................................... TRBL 06-0000
Chapter 7. Collecting Error Information ..................................................................................... TRBL 07-0000
Chapter 8. Trouble Analysis by LED Indication ......................................................................... TRBL 08-0000
Chapter 9. Data Collection when a Failure Occurs in Program Product (P.P.) ......................... TRBL 09-0000
Chapter 10. Trouble Analysis by Failure Monitoring Function...................................................... TRBL 10-0000

GENE 0070-01
Maintenance Manual - for Messages:

This Message volume describes the content of the message which occurs at the time of
the subsystem failure.
Chapter 1. Before Starting Trouble Analysis .............................................................................. MSG 01-0000
Chapter 2. CUDG Detected Messages ...................................................................................... MSG 02-0000
Chapter 3. Failure Messages ..................................................................................................... MSG 03-0000
Chapter 4. Progress Message .................................................................................................... MSG 04-0000
Chapter 5. Flash Detected Messages ........................................................................................ MSG 05-0000
Chapter 6. Warning Messages ................................................................................................... MSG 06-0000
Chapter 7. Web Error Messages ................................................................................................ MSG 07-0000
Chapter 8. Storage Navigator Modular Error Messages ............................................................ MSG 08-0000
Chapter 9. Failure Analysis by Sense Data ................................................................................ MSG 09-0000
Chapter 10. ACE Tool Error Message........................................................................................... MSG 10-0000
Maintenance Manual - for Replacement :

This Parts Replacement volume describes the replacement work of each part and the
periodic maintenance, etc.
Chapter 1. Before Starting Maintenance Work ............................................................................ REP 01-0000
Chapter 2. Parts Replacement .................................................................................................... REP 02-0000
Chapter 3. Periodic Maintenance ................................................................................................ REP 03-0000
Chapter 4. Maintenance Tools .................................................................................................... REP 04-0000
Chapter 5. Recycling ................................................................................................................... REP 05-0000
Maintenance Manual - for Parts Catalog :

This Parts Catalog volume describes each part installed in the subsystem.
Chapter 1. Parts Catalog ........................................................................................................ PARTS 01-0000
Maintenance Manual - for WEB :

This WEB volume describes the operating procedure for WEB.
Chapter 1. Before Using Web .................................................................................................... WEB 01-0000
Chapter 2. The Normal Mode Operation Procedure .................................................................. WEB 02-0000
Chapter 3. The Maintenance Mode Operation Procedure ......................................................... WEB 03-0000

GENE 0080-01
Contents
Preface ............................................................................................... GENE 0010
Cautionary Notes ................................................................................... GENE 0020
Note................................................................................................... GENE 0050
Model Name Conversion .......................................................................... GENE 0060
Manual Composition ............................................................................... GENE 0070
[Safety Summary]
SAFETY SUMMARY .............................................................................. SAFE 0000
[Theory]
Chapter 1. Warranty and Service .......................................................... THEO 01-0000
1.1 Warranty .......................................................................... THEO 01-0000
1.2 Service ............................................................................. THEO 01-0010
Chapter 2. Outline of Subsystem .......................................................... THEO 02-0000

2.1 What is RAID ...................................................................... THEO 02-0000
2.1.1 Application of RAID technology .......................................... THEO 02-0010
2.1.2 RAID levels .................................................................. THEO 02-0020
2.2 Outline of the Subsystem ....................................................... THEO 02-0040
2.2.1 Outline of functions ....................................................... THEO 02-0040
2.2.2 Differences between the DF700 and DF600............................ THEO 02-0070
2.3 Subsystem Structure............................................................. THEO 02-0090
2.3.1 External appearances ..................................................... THEO 02-0110
2.3.2 Configuration of floor model ............................................. THEO 02-0160
2.3.3 System configuration of the rackmount model........................ THEO 02-0170
2.3.4 Configuration of rackmount model with U7 rack frame ............. THEO 02-0200
2.4 Configuration of Internal Power Supply System............................. THEO 02-0210
2.5 Configuration of Internal Data System ....................................... THEO 02-0250
2.6 Configuration of Built-in Software ............................................ THEO 02-0300
2.6.1 Block diagram of built-in software configuration..................... THEO 02-0300
2.6.2 Storages for parameters .................................................. THEO 02-0330

GENE 0090-01
Chapter 3. Major Specifications of the Subsystem ..................................... THEO 03-0000

3.1 Basic Specifications of the Subsystem ........................................ THEO 03-0020
Chapter 4. Theory of Operation ........................................................... THEO 04-0000

4.1 Power On/Off Sequence ........................................................ THEO 04-0000
4.1.1 IMPL sequence .............................................................. THEO 04-0000
4.1.2 Disk Drive powering on sequence........................................ THEO 04-0020
4.1.3 Sequential shutdown ...................................................... THEO 04-0050
4.2 Data Format ...................................................................... THEO 04-0060
4.3 Read/Write Operation .......................................................... THEO 04-0070
4.3.1 Command execution ....................................................... THEO 04-0070
4.3.2 Dual system configuration ................................................ THEO 04-0080
4.4 Cache Memory Control .......................................................... THEO 04-0090
4.4.1 Purpose of Cache memory ................................................ THEO 04-0090
4.4.2 Cache memory configuration............................................. THEO 04-0100
4.4.3 Cache memory structure.................................................. THEO 04-0110
4.4.4 Basic operation of cache control ........................................ THEO 04-0130
4.4.5 Destaging operation ....................................................... THEO 04-0140
4.4.6 Staging operation (Writing to the Cache memory) ................... THEO 04-0150
4.5 Optional Functions................................................................ THEO 04-0160
4.6 Operation Against Disk Failure Occurs ....................................... THEO 04-0190
4.7 Setting RAID Group .............................................................. THEO 04-0260
Chapter 5. Outline of P.P. ................................................................... THEO 05-0000

5.1 P.P.s Required for Maintenance ............................................... THEO 05-0000

GENE 0100-01
[Installation]
Chapter 1 Before Starting Installation Work.............................................. INST 01-0000
1.1 Before Starting Installation Work............................................... INST 01-0000
1.2 Fibre Channel Interface.......................................................... INST 01-0020
1.2.1 Restrictions on Using the Fibre Channel Interface..................... INST 01-0020
1.2.2 Mini-HUB...................................................................... INST 01-0020
1.2.3 Connection Specifications of RKS......................................... INST 01-0030
1.2.4 Fibre Channel Configuration of RKS ...................................... INST 01-0030
1.2.5 Attention of Host Directly Connection for RKS ......................... INST 01-0030
1.3 Model Name........................................................................ INST 01-0040
1.3.1 Components and indispensable parts .................................... INST 01-0040
1.3.2 Optional parts ............................................................... INST 01-0060
1.3.3 Accessory parts .............................................................. INST 01-0070
1.4 Installation Configuration of the Subsystem.................................. INST 01-0080
1.5 How to Open/Close Door or Attach/Remove
Front Bezel/Rear Cover of the Subsystem ........... INST 01-0100
1.5.1 How to attach/remove Front Bezel of Floor Model.................... INST 01-0100
1.5.2 How to attach/remove Rear Cover of Floor Model .................... INST 01-0120
1.5.3 How to attach/remove Front Bezel
of the Rackmount Model ............... INST 01-0130
1.5.4 How to open/close the Rear Door of U7 rack frame .................. INST 01-0150
1.6 Device ID Setting and ENC Cable Connection................................. INST 01-0160
1.6.1 Example of device ID and ENC cable connection ...................... INST 01-0160
1.6.2 Checking methods of device ID and ENC cable connection
when mounting the newly introduced rack .... INST 01-0180
1.6.3 Procedure for making the configuration diagram
when adding the disk unit(s) ............ INST 01-0250
1.7 Power On/Off Procedure ........................................................ INST 01-0290
1.7.1 Subsystem power on ........................................................ INST 01-0290
1.7.2 Subsystem power off ....................................................... INST 01-0310
1.8 Setting the Power Control Mode (Local/Remote Mode) .................... INST 01-0320
Chapter 2. Installing Floor Model ........................................................... INST 02-0000
2.1 Procedures for Installing Floor Model.......................................... INST 02-0000
2.2 Unpacking the Subsystem........................................................ INST 02-0020
2.3 Installing Floor Stand Kit......................................................... INST 02-0050
2.3.1 Installing Floor Stand Kit................................................... INST 02-0050
2.3.2 Procedure for installing Floor Stand Kit ................................. INST 02-0060
2.4 Installing the Subsystem ......................................................... INST 02-0140
2.4.1 Subsystem floor-space and service clearance .......................... INST 02-0140
2.4.2 Installing the subsystem ................................................... INST 02-0150

GENE 0110-01
2.5 Installing Components............................................................ INST 02-0170

2.6 Connecting Cables ................................................................ INST 02-0300
2.6.1 Connecting Fibre Channel interface cables............................. INST 02-0300
2.6.2 Connecting ENC cables ..................................................... INST 02-0320
2.6.3 Connecting power cables .................................................. INST 02-0340
2.7 Installing Skirt ..................................................................... INST 02-0350
Chapter 3. Installing Rackmount Model.................................................... INST 03-0000

3.1 Procedures for Installing Rackmount Model .................................. INST 03-0000
3.2 Unpacking and Installing Rack Frame.......................................... INST 03-0020
3.2.1 U7 Rack Frame (Unpacking/Installing
and Installation areas/maintenance areas) ................ INST 03-0020
3.2.2 HP Rack Frame (Unpacking/Installing
3.2.3 Sun StorEdge Rack Frame (Unpacking/Installing
3.2.4 RS6000 Rack Frame (Unpacking/Installing
3.3 Unpacking the Subsystems....................................................... INST 03-0310
3.4 Installing the Rackmount Model ................................................ INST 03-0330
3.4.1 Work Procedure before Installing the Rack Mounting ................. INST 03-0330
3.4.2 Removing Components ..................................................... INST 03-0330
3.4.3 Mounting on Rack Frame ................................................... INST 03-0400
3.4.4 Mounting lifter on rack frame............................................. INST 03-0410
3.4.5 Mounting subsystem on rack frame ...................................... INST 03-0430
3.4.6 Securing the subsystem .................................................... INST 03-0450
3.4.7 Installing Components ...................................................... INST 03-0490
3.4.8 Connecting Cables .......................................................... INST 03-0610
3.4.9 Connecting the Fibre Channel interface cable .......................... INST 03-0640
3.4.10 Connecting the ENC cables ............................................... INST 03-0670
3.4.11 Connecting the power cables............................................. INST 03-0710
3.4.12 Connecting the power cables (Rack frame PDB) ...................... INST 03-0730
3.4.13 Attaching Decoration Panels.............................................. INST 03-0740
3.4.14 Closing Door or Attaching Front Bezel .................................. INST 03-0750

GENE 0120-01
[Microprogram]
Chapter 1. Installation of Microprogram ................................................ MICRO 01-0000
1.1 Materials necessary for installation........................................... MICRO 01-0000
1.2 Outline of procedure for installation ......................................... MICRO 01-0010
1.3 Preparation for installation of microprogram ............................... MICRO 01-0020
1.3.1 Hierarchy of Microprogram Storage Directories...................... MICRO 01-0090
1.4 Procedure for installation ...................................................... MICRO 01-0100
1.5 Checking the start and the termination of the
ENC/SENC firmware automatic download................ MICRO 01-0220
Chapter 2. Procedure for Recovery from a Failure ................................... MICRO 02-0000

2.1 Procedure for recovery from a failure during installation ................ MICRO 02-0000

Install partially completeMessage Is Output ...... MICRO 03-0000
3.1 Procedure for Checking whether system copy operation occurred ...... MICRO 03-0010
3.2 Procedure for checking the status of system copy complete............. MICRO 03-0020
[System Parameter]
Chapter 1. Setting (Storage Navigator Modular) ....................................... SYSPR 01-0000
1.1 Procedure for connecting
Storage Navigator Modular with the subsystem......................SYSPR 01-0010
Chapter 2. Setting Host Group ............................................................ SYSPR 02-0000

2.1 Before setting host group.......................................................SYSPR 02-0000
2.2 Setting of option .................................................................SYSPR 02-0010
2.3 Setting LU mapping ..............................................................SYSPR 02-0100
Chapter 3. Setting the RAID/LU/Spare Disk ............................................. SYSPR 03-0000

3.1 Preparation of RAID/LU setting................................................SYSPR 03-0030
3.2 RAID group setting ...............................................................SYSPR 03-0050
3.3 Setting of LU ......................................................................SYSPR 03-0140
3.4 Setting of Spare Disk ............................................................SYSPR 03-0350
3.5 Checking the status of Disk Drive .............................................SYSPR 03-0400
Chapter 4. Setting Configuration Information.......................................... SYSPR 04-0000

4.1 Before setting configuration information ....................................SYSPR 04-0000
4.2 Setting the subsystem configuration information ..........................SYSPR 04-0020

GENE 0130-01
Chapter 5. Setting Host Connection Parameters ...................................... SYSPR 05-0000

5.1 Simple setting for Connecting to the Host Computer ......................SYSPR 05-0000
5.2 Simple setting for Connecting to the Host Computer ......................SYSPR 05-0040
5.3 When using the subsystem in LU blockade Mode ...........................SYSPR 05-0050
Chapter 6. Setting an Extra-cost Optional Feature ................................... SYSPR 06-0000
Chapter 7. System Parameter Setting List .............................................. SYSPR 07-0000
[Addition/Subtraction/Relocation]
Chapter 1. Adding Optional Components ..................................................ADD 01-0000
1.1 Before Starting Addition of Optional Components............................ ADD 01-0000
1.2 Procedures for Adding Optional Components ................................. ADD 01-0010
1.2.1 Unpacking ..................................................................... ADD 01-0090
1.3 Mounting RKAJ/RKAJAT on Rack Frame ........................................ ADD 01-0100
1.3.1 Work immediately after abnormal termination ......................... ADD 01-0110
1.4 Adding Optional Components .................................................... ADD 01-0130
1.4.1 Subsystems optional components for addition .......................... ADD 01-0130
1.4.2 Adding a Control Unit ....................................................... ADD 01-0140
1.4.3 Adding a Disk Drive .......................................................... ADD 01-0190
1.4.4 Adding a Cache Unit ......................................................... ADD 01-0410
1.5 Adding Other Optional Devices .................................................. ADD 01-0450
1.5.1 Other optional additional devices ......................................... ADD 01-0450
1.5.2 Mounting a PDB (UPDU7) .................................................... ADD 01-0460
1.6 Adding the RKAJ to the Rack Frame ............................................ ADD 01-0490
1.6.1 Procedure for adding the RKAJ to the subsystem
of rackmount model with U7 rack frame.................... ADD 01-0490
1.6.2 Connecting multiple RKAJs ................................................ ADD 01-0550
1.6.3 Recognition and connection of the added RKAJ........................ ADD 01-0590
1.6.4 Verifying the addition ...................................................... ADD 01-0670
1.6.5 Install the rest of the Disk Drives ......................................... ADD 01-0740
1.7 Adding the RKAJ/RKAJAT to the Rack Frame ................................. ADD 01-0750
1.7.1 Procedure for adding the RKAJ/RKAJAT to the subsystem
of rackmount model with U7 rack frame.................... ADD 01-0750
1.7.2 Connecting multiple RKAJs/RKAJATs .................................... ADD 01-0800
1.7.3 Recognition and connection of the added RKAJ/RKAJAT ............. ADD 01-0880
1.7.4 Verifying the addition ...................................................... ADD 01-0980
1.7.5 Install the rest of the Disk Drives ......................................... ADD 01-1070

GENE 0140-01
Chapter 2. Subtracting Optional Components ............................................ADD 02-0000

2.1 Before Starting Subtraction of Optional Components........................ ADD 02-0000
2.1.1 Preparatory works for subtraction ........................................ ADD 02-0010
2.2 Procedures for Subtracting Optional Components............................ ADD 02-0090
2.3 Subtracting RKAJ/RKAJAT on Rack Frame ..................................... ADD 02-0120
2.4 Subtracting Optional Components............................................... ADD 02-0140
2.4.1 Subsystems optional components for subtraction ...................... ADD 02-0140
2.4.2 Subtracting a Control Unit.................................................. ADD 02-0160
2.4.3 Subtracting a Disk Drive..................................................... ADD 02-0200
2.4.4 Subtracting a Cache Unit ................................................... ADD 02-0280
2.5 Subtracting Other Optional Devices............................................. ADD 02-0320
2.5.1 Other Optional subtraction devices ....................................... ADD 02-0320
2.5.2 Subtracting a PDB (UPDU7) ................................................. ADD 02-0330
Chapter 3. Relocation/Removal Work.......................................................ADD 03-0000

3.1 Before Starting Relocation/Removal Work .................................... ADD 03-0000
3.2 Procedure for Relocating or Removing Floor Model .......................... ADD 03-0020
3.2.1 Disconnecting power cable ................................................. ADD 03-0040
3.2.2 Disconnecting interface cables ............................................ ADD 03-0050
3.3 Procedure for Relocating or Removing Rackmount Model................... ADD 03-0060
3.3.1 Disconnecting the power cables ........................................... ADD 03-0090
3.3.2 Disconnecting the power Cable
(for supplying power to Rack frame) ............................ ADD 03-0100
3.3.3 Disconnecting interface cables ............................................ ADD 03-0110

GENE 0150-01
[Troubleshooting]
Chapter 1. Flowchart for troubleshooting ............................................... TRBL 01-0000
Chapter 2. Before Maintenance Work .................................................... TRBL 02-0000

2.1 Precautions ........................................................................TRBL 02-0000
2.2 Confirming and setting RTC (Real Time Clock)...............................TRBL 02-0010
2.3 Indications and their Functions .................................................TRBL 02-0040
Chapter 3. Before Starting WEB Connection ............................................ TRBL 03-0000

3.1 Procedure to WEB connection ..................................................TRBL 03-0000
3.2 When the WEB has already been connected..................................TRBL 03-0050
3.3 Note on WEB connecting.........................................................TRBL 03-0060
Chapter 4. Trouble Analysis by WEB Connection ....................................... TRBL 04-0000

4.1 Confirm state of unit .............................................................TRBL 04-0010
4.2 Confirm state of each part ......................................................TRBL 04-0040
4.3 Confirm log messages ............................................................TRBL 04-0100
4.4 TrueCopy remote replication path confirm state............................TRBL 04-0170
4.5 The Priority Error Messages when W0100x CTL alarm is displayed ....TRBL 04-0180
Chapter 5. Procedure for Investigating Disk Array Subsystem

Regarding Fibre Channel Failure ............. TRBL 05-0000
Chapter 6. Details of Recovery Methods ................................................. TRBL 06-0000

6.1 Error recovery methods ..........................................................TRBL 06-0000
6.1.1 System down ................................................................TRBL 06-0020
6.1.2 The subsystem does not become ready : Case 1(Loading failure)..TRBL 06-0050
6.1.3 The failure occurred immediately after being ready
(Forced parity correction).............TRBL 06-0060
6.1.4 The power cannot be turned off : Case 1
(The number of PIN data is too large)...TRBL 06-0420
6.1.5 The power cannot be turned off : Case 2 (Hardware failure).......TRBL 06-0450
6.1.6 The power cannot be turned off : Case 3 (Control Unit failure) ...TRBL 06-0470
6.1.7 The power cannot be turned off : Case 4 (Cache memory failure) TRBL 06-0490
6.1.8 Data recovery does not terminate normally : Case 1 (Read error).TRBL 06-0510
6.1.9 Data recovery does not terminate normally : Case 2
(Disk Drive failure) ..........TRBL 06-0520
6.1.10 Data recovery does not terminate normally : Case 3
(Spare Disk Drive failure) ..TRBL 06-0540
6.1.11 A failure occurred during operation : Case 1 (PIN over) .............TRBL 06-0550
6.1.12 A failure occurred during operation : Case 2 (LA/LRC error) .......TRBL 06-0570
6.1.13 A failure occurred during operation : Case 3 (LU blockade) ........TRBL 06-0590
6.1.14 A failure occurred during operation : Case 4 (Loop failure) ........TRBL 06-0600

GENE 0160-01
6.1.15 A failure occurred during operation : Case 5 (Incomplete writing) TRBL 06-1110
6.1.16 A failure in Copy-on-write SnapShot occurs. ..........................TRBL 06-1120
6.2 Initialization procedure for configuration information .....................TRBL 06-1130
6.3 Procedure for Recovery from Path Blockade
when the TrueCopy remote replication Function Is Used ...TRBL 06-1170
Chapter 7. Collecting Error Information.................................................. TRBL 07-0000

7.1 Time to collect failure information ............................................TRBL 07-0010
7.2 Judge collection of failure information .......................................TRBL 07-0020
7.3 Collecting simple trace ..........................................................TRBL 07-0040
7.4 Collecting CTL Alarm Trace .....................................................TRBL 07-0080
7.5 Collecting Memory Dump ........................................................TRBL 07-0130
7.6 Storing simple trace information in the USB memory.......................TRBL 07-0230
Chapter 8. Trouble Analysis by LED Indication ......................................... TRBL 08-0000

8.1 Trouble Analysis by LED Indication of Front Bezel...........................TRBL 08-0000
8.2 Trouble Analysis by LED Indication of Each Part .............................TRBL 08-0150
Chapter 9. Data Collection when a Failure Occurs in Program Product (P.P.) ... TRBL 09-0000
9.1 Locating Failed Part ...............................................................TRBL 09-0000
9.1.1 When a failure occurs in the DF700 main body ........................TRBL 09-0020
9.1.2 When a failure occurs in a host system server .........................TRBL 09-0020
9.1.3 When a failure occurs in a server for monitoring and setting .......TRBL 09-0030
9.2 List of Data to Be Collected when a P.P. Failure Occurs ....................TRBL 09-0040
Chapter 10. Trouble Analysis by Failure Monitoring Function....................... TRBL 10-0000

10.1 Trouble Analysis by SNMP Agent Support Function .........................TRBL 10-0000
10.1.1 Maintenance with TRAP Codes..........................................TRBL 10-0000
10.1.2 Maintenance with MIB (df Regression) Values ........................TRBL 10-0050
10.2 Trouble Analysis by Storage Navigator Modular .............................TRBL 10-0080
10.2.1 Maintenance with the Storage Navigator Modular (GUI version) ..TRBL 10-0080
10.2.2 Storage Navigator Modular Maintenance Function ..................TRBL 10-0130
10.2.3 Displaying Statistical Information ......................................TRBL 10-0150
10.2.4 Displaying Logical Unit Failure Data Information ....................TRBL 10-0250
10.2.5 Setting Pre-fetch Information ..........................................TRBL 10-0270
10.2.6 Setting a Threshold for Preventive Maintenance ....................TRBL 10-0300
10.2.7 Drive Maintenance ........................................................TRBL 10-0330
10.2.8 Setting a Mode for Reporting to the Host Using an SSB.............TRBL 10-0360
10.2.9 Setting SATA Drive Options..............................................TRBL 10-0390

GENE 0170-01
10.2.10 Setting SATA Drive Restore Options....................................TRBL 10-0420

10.2.11 Replacing the Online ENC/SENC Firmware............................TRBL 10-0450
10.2.12 Drive Performance Delay Diagnostic Function .......................TRBL 10-0480
[Message]
Chapter 1. Before Starting Trouble Analysis ..............................................MSG 01-0000
1.1 Failed parts of the internal Fibre Channel......................................MSG 01-0010
Chapter 2. CUDG Detected Messages........................................................MSG 02-0000
Chapter 3. Failure Messages ..................................................................MSG 03-0000
Chapter 4. Progress Message..................................................................MSG 04-0000
Chapter 5. Flash Detected Messages ........................................................MSG 05-0000
Chapter 6. Warning Messages.................................................................MSG 06-0000
Chapter 7. Web Error Messages ..............................................................MSG 07-0000

7.1 Web error messages (Uploading Function)......................................MSG 07-0000
7.2 Web error messages (Simple Trace) .............................................MSG 07-0060
7.3 Web error messages (Web Control Management)..............................MSG 07-0070
Chapter 8. Storage Navigator Modular Error Messages ..................................MSG 08-0000
Chapter 9. Failure Analysis by Sense Data .................................................MSG 09-0000

9.1 Details of sense code...............................................................MSG 09-0000
9.2 List of detail codes of sense code (05/9FFF)...................................MSG 09-0190
Chapter 10. ACE Tool Error Message ........................................................MSG 10-0000
[Replacement]
Chapter 1. Before Starting Maintenance Work............................................ REP 01-0000
1.1 Before Starting Maintenance Work............................................... REP 01-0000
1.1.1 Cautionary Notes ............................................................. REP 01-0000
1.1.2 Checking cache memory in the back-up state........................... REP 01-0030
1.1.3 Procedure for making sure of model name
and drive firmware of Disk Drive ......................... REP 01-0100
Chapter 2. Parts Replacement................................................................ REP 02-0000

2.1 Locations of Replacement Components ......................................... REP 02-0000
2.1.1 Part Locations of Rackmount Model...................................... REP 02-0020
2.1.2 Part Locations of Floor Model ............................................. REP 02-0030

GENE 0180-01
2.2 Replacement of Components ..................................................... REP 02-0050

2.2.1 Replacing Disk Drive ........................................................ REP 02-0050
2.2.2 Replacing Backup Battery Unit............................................ REP 02-0240
2.2.3 Replacing Fan Assembly .................................................... REP 02-0300
2.2.4 Replacing Power Unit ....................................................... REP 02-0340
2.2.5 Replacing Control Unit ..................................................... REP 02-0390
2.2.6 Replacing Cache Unit ....................................................... REP 02-0540
2.2.7 Replacing Interface Board ................................................. REP 02-0660
2.2.8 Replacing Host Connector ................................................. REP 02-0770
2.2.9 Replacing ENC Unit/SENC Unit ............................................ REP 02-0830
2.2.10 Replacing ENC cable ........................................................ REP 02-0910
2.2.11 Replacing Basic Chassis of Rack Mount Style............................ REP 02-0950
2.2.12 Replacing Additional Chassis of Rack Mount Style ..................... REP 02-0990
2.2.13 Replacing Remote Adapter................................................. REP 02-1030
Chapter 3. Periodic Maintenance ............................................................ REP 03-0000

3.1 Periodic Maintenance Items....................................................... REP 03-0000
3.2 Inspecting and Cleaning Floor Model ............................................ REP 03-0010
3.2.1 Inspecting fans ............................................................... REP 03-0020
3.2.2 Cleaning the subsystem ..................................................... REP 03-0030
3.3 Inspecting and Cleaning Rackmount Model with U7 Rack Frame............ REP 03-0040
3.3.1 Inspecting fans ............................................................... REP 03-0040
3.3.2 Cleaning the subsystem ..................................................... REP 03-0060
3.4 Replacing Periodical Replacement Parts........................................ REP 03-0070
3.4.1 Replacing Battery unit ...................................................... REP 03-0070
Chapter 4. Maintenance Tools................................................................ REP 04-0000

4.1 Maintenance Tools for Hardware................................................. REP 04-0000
4.2 Maintenance Tools for Software.................................................. REP 04-0010
Chapter 5. Recycling ........................................................................... REP 05-0000
[Parts Catalog]
Chapter 1. Parts Catalog .................................................................... PARTS 01-0000
1.1 How to Use this Parts Catalog ................................................. PARTS 01-0000
1.2 System of Parts Catalog ........................................................ PARTS 01-0010
1.3 Parts Catalog ..................................................................... PARTS 01-0020

GENE 0190-01
[WEB]
Chapter 1 Before Using Web ................................................................. WEB 01-0000
1.1 The Operating Environment.......................................................WEB 01-0000
1.2 Notices on (restriction of) the support browser ...............................WEB 01-0010
1.3 The Characteristic of the Network Function ...................................WEB 01-0030
1.4 Support Browser List ...............................................................WEB 01-0050
Chapter 2 The Normal Mode Operation Procedure ..................................... WEB 02-0000

2.1 Transferring to the Normal Mode ................................................WEB 02-0000
2.2 Screen Outline.......................................................................WEB 02-0010
2.3 Main Screen of the Normal Mode .................................................WEB 02-0030
2.4 Display of Exchangeable Parts Status (Parts Information) ...................WEB 02-0070
2.5 Information Message ...............................................................WEB 02-0120
2.6 Collecting Simple Trace ...........................................................WEB 02-0130
2.7 Collecting CTL Alarm Trace .......................................................WEB 02-0150
2.8 Setting of the Buzzer Volume.....................................................WEB 02-0170
2.9 Host Command Trace Download..................................................WEB 02-0180
Chapter 3 The Maintenance Mode Operation Procedure .............................. WEB 03-0000

3.1 Transferring to the Maintenance Mode..........................................WEB 03-0000
3.1.1 WEB Operation in the Maintenance Mode during the
Cache Memory Access Failure .............................WEB 03-0040
3.2 Reference/Setting of the System Parameter and Initialize ..................WEB 03-0050
3.2.1 Subsystem .....................................................................WEB 03-0060
3.2.2 Host Interface ................................................................WEB 03-0120
3.2.3 Network........................................................................WEB 03-0170
3.2.4 Name ...........................................................................WEB 03-0220
3.2.5 ALL .............................................................................WEB 03-0260
3.3 Setup..................................................................................WEB 03-0280
3.3.1 Microprogram .................................................................WEB 03-0280
3.4 Reference ............................................................................WEB 03-0310
3.4.1 Information Message.........................................................WEB 03-0310
3.5 Trace/Dump .........................................................................WEB 03-0320
3.5.1 Collecting Simple Trace.....................................................WEB 03-0320
3.5.2 Collecting CTL Alarm Trace ................................................WEB 03-0340
3.5.3 Collecting Full Dump ........................................................WEB 03-0370
3.5.4 Collecting Full Dump(Full Dump(SnapShot)) .............................WEB 03-0400
3.6 Other..................................................................................WEB 03-0430
3.7 Return Method to the Normal Mode .............................................WEB 03-0440
GENE 0200-01
[REV]
Revision Control .................................................................................... REV 0000

GENE 0210-01
.
Safety Summary

SAFE 0000-01
This page is for editorial purpose only.

SAFE 0010-01
SAFETY SUMMARY
The hazard warnings which appear on the warning labels on the machine or in the manual have
one of the following alert headings consisting of a safety alert symbol and a signal word,
DANGER, WARNING, or CAUTION.
1. About the symbols
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible injury or
death.
DANGER : Indicates an imminently hazardous situation which, if not avoided, will result in death or
serious injury.
WARNING : Indicates a potentially hazardous situation which, if not avoided, could result in death or
serious injury.
CAUTION : Indicates a potentially hazardous situation which, if not avoided, may result in minor or
moderate injury.
CAUTION : Indicates a potentially hazardous situation which, if not avoided, may result in property
damage.
2. General Safety Guidelines
Read the following safety guidelines carefully and follow them when you conduct maintenance
of the machine.
Before starting maintenance

Maintenance of the machine must be done only by trained and qualified engineers.
Read and follow the safety guidelines and procedures in this manuals.
In this manual and on the machine, hazard warnings are provided to aid you in preventing or
reducing the risk of death, personal injury, or product damage. Understand and follow
these hazard warnings fully.
When warning labels become dirty or start peeling off, replace them.
Keep in mind that the hazard warnings in this manual or on the machine cannot cover every
possible case, as it is impossible to predict and evaluate all circumstances beforehand. Be
alert and use your common sense.
This disk array is a class 1 laser system which emits no hazardous laser beam.
Be sure to operate it according to this manual. Do not perform any operations other than
those written in this manual. Otherwise, unexpected failures or accidents may be caused.

SAFE 0020-01
SAFETY SUMMARY (Continued)
During work
For each procedure, follow the given method and sequence of steps.
Use the spare, consumables, and materials for maintenance which are specified in the
manual; otherwise, personal injury or damage of the machine, as well as deterioration of
the products quality, may result.
Use the special tools and instruments specified for the work in the manual or commercially
available tools and instruments which fit the purpose.
Use measurement instruments and powered tools which are properly calibrated or
periodically inspected.
Keep the maintenance area neat and tidy.
Always put away parts, materials, or tool when not in use.
Wear an eye protector where liquid may splash or anything may fly about.
When lifting anything heavy, lift it using your legs with your back kept erect, to prevent
injury to your back or spine.
When lifting anything, for the weight of which CAUTION is indicated, use a proper lifting
tool or have somebody help you.
Keep a soldering iron and its stand away from you to prevent accidental contact and burns.
When using sharp objects or cutting tools, make sure that no part of your body lies in the
path of the blade, or point.
Before finishing your work, check if the subsystem is returned to its original state.
(Make sure that all parts removed during maintenance have been in stalled back in their
original positions in the machine. Make sure that no tool or foreign material left in the
machine.)

SAFE 0030-01
Prevention of electric shocks
Before starting work, make sure that, unless otherwise specifically instructed, there is no
potential electric hazard in the maintenance area such as insufficient grounding or a wet
floor.
Before starting work, note where the emergency power-off switches are located and make
sure you know how to operate them.
Unless otherwise specifically instructed, cut off all power sources to the machine before
staring maintenance. Just switching off the machine power supplies is usually not enough.
When power is fed from a wall or floor outlet, unplug the power supply cord, or turn off the
switch on the power distribution panel or board.
When the power supply has a lockout device(*1), lock it up after the powering off and keep
the key.
Attach a notice on the panel or board prohibiting the use of the switch.
If the machine power has been already turned off, make sure yourself that these conditions
are satisfied.
*1
The following is a portion of 29 CFR 1910.147 The control of hazardous energy
(lockout/tagout), in the OSHA (Occupational Safety & Health Administration U.S
Department of Labor USA) Regurations.
Lockout device. A device that utilizes a positive means such as a lock, either key or
combination type, to hold an energy isolating device in a safe position and prevent the
energizing of a machine or equipment. Included are blank flanges and bolted slip
blinds.
Energy isolating device. A mechanical device that physically prevents the transmission
or release of energy, including but not limited to the following: A manually operated
electrical circuit breaker; a disconnect switch, a manually operated switch by which the
conductors of a circuit can be disconnected from all ungrounded supply conductors, and,
in addition, no pole can be operated independently; a line valve; a block; and any
similar device used to block or isolate energy. Push buttons, selector switches and
other control circuit type devices are not energy isolating devices.
Do not touch any uninsured conductor or surface, where so instructed, which remains
charged for a limited time after the external power supply to the machine is disconnected.
When working on a machine which has a grounding terminal, make sure that the terminals
properly connected to the facilitys ground.
When working close to a hazardously energized part, do not work alone; work with another
person who can immediately turn off the power in an emergency.

SAFE 0040-01
Do not wear any metallic item such as a wrist watch with a metallic surface, or metallic
accessories.
If you wear eyeglasses with a metallic frame, take care not to let the frame touch an
uninsured surface.
Make sure that your hands and arms are dry.
Unless otherwise specifically instructed, use only one hand when it is necessary to work
near an exposed live electric circuit.
This prevents the completion of the circuit through both hands even if you accidentally
touch the circuit.
Do not use a dental mirror near an exposed live electric circuit.
The mirror surface is conductive and can become hazardous even if it is made of plastic.
Unless otherwise specifically instructed, do not supply power to any subassembly such as a
power supply unit or a motor while it is removed from the machine.
Preventing being caught by rotating or moving parts
Tuck in your tie, scarf, shirt, or any other loose clothing so that it will not be caught by a
rotating or moving part.
Tie up long hair.
Unless otherwise specifically instructed, do not supply power to any device with rotating or
moving parts which are not properly covered.
When instructed to supply power to any device with rotating or moving parts whose covers
have been removed, work with another person who can immediately turn off the power in
an emergency.
Procedure in an emergency
For electric shock
Do not panic. Do not become another victim through contact with the injured person.
First, shut off the electric current passing through the victim.
Use the emergency power-off switch, if there is one, or otherwise, a normal power-off
switch. If this cannot be done, push the victim away from the source of the electric
current by using a nonconductor object such as a dry wooden stick.
Then, call an ambulance.
If the victim is unconscious, artificial respiration may be necessary.
A proper method for performing artificial respiration or resuscitation should be learned
beforehand.
If the victims heart is not beating, cardiac resuscitation should be performed by a trained
and qualified person.

SAFE 0050-01
For outbreak of fire
First shut off all the power from the machine using the emergency power-off switch.
If the fire continues burning after the power is shut off, take suitable actions including the
use of a fire extinguisher or a call for the fire department.

SAFE 0060-01
3. Hazard Warning Statements
The following are the hazard warning statements contained in this manual.
3.1 DANGER statements
y Do not disassemble the case, do not modify it, or do not peel off the label. There are high
voltage parts inside: If you attempt any of these actions, you may get an electrical shock or
burn.
(REP 05-0000)
y Do not disassemble the battery; this may cause short circuits inside or outside of the
battery. If the components are exposed to the air, the battery may cause overheat, burst
or ignite. Disassembling the battery may expose you to its alkaline solution, which can be
dangerous.
(REP 05-0000)
y Do not cut the output cable. Do not modify the connector. If you attempt any of these
actions, you may get an electrical shock or burn. A short-circuit may cause abnormal
chemical reactions inside the battery which leads to overheating, bursting or ignition.
(REP 05-0000)
y Follow the instructions when you recharge the battery pack. If you recharge it in a way
different from specified here, it may cause the following problems: The battery may
become charged excessively; excessive current may be produced; or the battery cannot be
recharged. As a result, the battery may leak, become overheated, burst, or ignite.
(REP 05-0000)
y Do not use excessive force when you connect the battery pack to the charger or other
devices. If you cannot connect it easily, check the positive and negative are correct for the
connector. If you connect the battery in reverse, it will be charged incorrectly and
abnormal chemical reactions may occur inside. As a result, the battery may become
overheated, burst or ignite.
(REP 05-0000)
y Do not connect the battery to a power receptacle. If you apply an excessive amount of
voltage to the battery, it may produce excessive current making the battery overheat, burst
or ignite.
(REP 05-0000)

SAFE 0070-01
y Do not use or leave the battery where the temperature can become high, such as, near a
fire or a heating element. High temperatures may damage the batterys separator, which
may cause short circuit, making it overheat, burst or ignite.
(REP 05-0000)
y Do not incinerate the battery pack or heat it. If you do so, the insulator may melt, the
safety fuse/
mechanism may be damaged, or the electrolyte may gush out. As a result, the battery may
become burst, explode or ignite.
(REP 05-0010)
y Do not connect the negative terminal to the positive with metal wire. Do not carry or store
the battery with other metal parts. This may cause a short circuit or produce excessive
current which can cause the battery to leak, overheat, burst or ignite.
(REP 05-0010)
y Do not let the battery become wet by soaking it in the water or seawater. If the battery
gets wet, a short circuit may occur and an excessive amount of current may be produced
causing abnormal chemical reactions inside. As a result, the battery may become
(REP 05-0010)
y Do not nail the battery, hit it with a hammer, or stamp on it. The battery may be broken or
dented and a short circuit may occur inside. As a result, the battery may become
(REP 05-0010)
y Do not solder directly to the battery. If you do so, heat will melt the insulator and damage
the safety fuse/mechanism. As a result, the battery may leak or may become overheated,
burst or ignite.
(REP 05-0010)
y Do not recharge the battery where there is a high temperature, such as near a fire.
This may cause abnormal chemical reactions inside the battery and it may become
overheated, burst or ignite. High temperatures may also cause deterioration of
performance/life of the battery.
(REP 05-0010)

SAFE 0080-01
3.2 WARNING statements
y If the Subsystem falls when the elevator of the lifter is at a high position, a personal injury
will be caused.
Perform the positioning, fastening, or other handlings very carefully.
(INST 03-0430)
y Do not place the battery pack in the microwave oven or under high pressure. Either of
these actions will rapidly heat the battery or break its seals: As a result, the battery may
become overheated, burst or ignite.
(REP 05-0020)
y If you find anything strange or unusual with the battery when you use/carry/store it, remove
the battery from the device and stop using it. For example, strange smells, strange colors,
or deformation are a sign you must stop using the battery.
(REP 05-0020)
y If it takes longer than the specified time to complete recharging, stop recharging the
battery: Otherwise, the battery may become overheated, burst or ignite.
(REP 05-0020)
y If the battery leaks and gets into your eyes, immediately flush your eyes with clean water
(tap water) and do not rub your eye. Then visit the doctor immediately. If you do not
seek any treatment for your eyes, problems may occur later. Because the battery uses
highly concentrated alkaline as electrolyte, it may burn or you may lose your sight if it
contacts your skin or eyes. If the batterys liquid contacts your skin or eyes, you must flush
them with plenty of clean water and visit the doctor at once.
(REP 05-0020)
3.3 CAUTION statements
y Attach or remove the Front Bezel carefully following the procedure. Otherwise, you may
hurt your fingers by pinching them.
(INST 01-0100, INST 01-0130, REP 03-0060)
y Attach or remove the Rear Cover carefully following the procedure. Otherwise, you may
hurt your fingers by pinching them.
(INST 01-0120)
y Do not lean against the rear cover. The cover comes off, and it causes the injury.
(INST 01-0120)

SAFE 0090-01
y Open or close the door carefully following the procedure. Otherwise, you may hurt you
fingers by pinching them.
(INST 01-0150)
y The unpacking should be done by two or more personnel to prevent turning over of the
subsystem or being caught under the subsystem.
(INST 02-0020, INST 03-0310)
y Perform the work with enough care because the Floor (RKM+H1H/RKS+ H1J) Model, Floor
(RKM/RKS+RKAJ+H2J) Model, and Floor Model are heavy; their masses are about 80 kg and
125 kg respectively.
(INST 02-0020)
y When moving the subsystem, remove the skirts and raise the leveling bolts. Otherwise, an
accident such as a falling may be caused because of contact with the floor or catching of a
part.
(INST 02-0020)
y When moving the subsystem across a difference in floor level, etc., use a gangway, which
forms a slope with an inclination angle of less than eight degrees.
(INST 02-0020)
y Masses of RKM is approximately 58 kg , and RKS is approximately 56 kg.

When raising each of them, take measures to prevent it from slipping because the slipping
may cause a personnel injury owing to a pinching.
(INST 02-0060)
y When raising the subsystem, it is dangerous to do it by using the handles. Be sure to raise
the subsystem by holding its front and rear portions made of sheet metal.
(INST 02-0060, INST 02-0100)
y Masses of RKM is approximately 58 kg , RKS is approximately 56 kg, and RKAJ/RKAJAT 40 kg

is approximately.
When raising each of them, take measures to prevent it from slipping because the slipping
may cause a personnel injury owing to a pinching.
(INST 02-0100)
y Do not block the vent holes. Or else, temperature rise inside the subsystem may cause a
failure or even a fire.
(INST 02-0140)

SAFE 0100-01
y Work carefully because the mass of the single RKM is about 58 kg, RKS is about 56 kg, RKAJ /
RKAJAT is about 40 kg.
(INST 03-0310, INST 03-0420, INST 03-0430)
y Make sure that there is no scratch or flaw on a power cable. It can cause an electric shock
or even a fire.
(INST 02-0340, INST 03-0710, INST 03-0730)
(ADD 01-0480, ADD 03-0040, ADD 03-0090)
y Do not put your hands at both ends of the skirt when installing the front skirt. The fingers
and the like are pinched between the side skirts, and it causes the injury.
(INST 02-0350)
y Rack mounting and lifter operation should only be conducted by a person who has been
trained and qualified since the subsystem could turn over or a worker could be caught under
the subsystem.
(INST 03-0420, INST 03-0430)
y Be sure to perform the operation with two or more workers.
(INST 03-0420, INST 03-0430)
(REP 02-0950, REP 02-0990)
y Operate the valve slowly when opening it. If it is opened quickly, the elevator of the lifter
descends rapidly and may cause personal injury.
(INST 03-0430)
y Do not move the lifter away from the rack frame nor lower the elevator until the red line on
the label affixed on the subsystem enters the rack frame across the end of it. Otherwise,
falling of the subsystem may be caused.
(INST 03-0440)
y The cable of PDB is a fixed type. Do not loosen the installation part. If it is loosened, the
connected part is damaged, and it causes an electric shock or fire.
(INST 03-0730)
y Do not disassemble or remodel parts for maintenance. Otherwise, a failure or a serious
accident may be caused. Be sure to replace parts in units of formally defined maintenance
part.
(REP 01-0000)
y When replacing the power supply, do it in haste after preparing a replacement power supply
and arranging cables, etc. so that they do not disturb the replacement.
(REP 01-0000)

SAFE 0110-01
y A closed type nickel-hydrogen battery can cause an electric shock or explosion if it is

handled wrongly. Observe the following requirements for handling.
y Do not disassemble or remake the battery.
y Do not deform the battery.
y Do not connect plus and minus poles with a metallic article such as a wire.
y Do not reverse the connections of plus and minus poles.
y Do not peel off the covering tube.
y Do not connect the battery directly to the outlet.
y Do not connect the battery to anything other than this subsystem for
charging/discharging.
y Do not leave the battery in a hot place. Store it in a dark and cool place.
y Do not discard a used battery at the site where it was removed for replacement.
(REP 02-0240)
y Since each fan is rotating with high-speed, be careful not to be caught by it.
(REP 02-0300, REP 03-0020, REP 03-0040)
y Be sure to keep the front bezel and rear panel clean. Or else, the ventilation is deteriorated so
that the temperature inside the subsystem may rise causing a failure or even a fire.
(REP 03-0030, REP 03-0060)
y Be careful not to move the subsystem during cleaning.
(REP 03-0030, REP 03-0060)
y If a battery is handled wrongly, it is feared that an explosion is caused.
(REP 03-0070)
y Do not disassemble the battery, or a burn or electric shock may be caused.
(REP 03-0070)

SAFE 0120-01

y Touching heat sinks or ICs may cause getting burned. Be sure to handle with care.
(ADD 01-0140, ADD 01-0410, ADD 01-0420, ADD 02-0160, ADD 02-0280, ADD 02-0290)
(REP 02-0390, REP 02-0420, REP 02-0460, REP 02-0500, REP 02-0520, REP 02-0540,
REP 02-0560, REP 02-0610, REP 02-0640, REP 02-0660, REP 02-0680, REP 02-0720,
REP 02-0750)
y When doing a hot replacement of a part, do not wear metallic accessories or a watch so as to
avoid an electric shock. Be careful not to touch any of live parts with a screwdriver, etc.
(REP 01-0000)
y If you touch a live part, it is feared that you receive an electric shock.
(REP 03-0030, REP 03-0060)

SAFE 0130-01
y To prevent part failures caused by static electrical charge built up on your own body, be
sure to wear a wrist strap connected to the chassis before starting (before removing bezel)
and do not take it off until you finish.
Please be sure to keep a wrist strap near the subsystem.
(INST 01-0000, INST 01-0100, INST 01-0130, INST 02-0200, INST 02-0250, INST 02-0270,
INST 03-0330, INST 03-0490)
(ADD 01-0140, ADD 01-0210, ADD 01-0410, ADD 02-0160, ADD 02-0210, ADD 02-0280,
ADD 03-0000)
REP 02-0830, REP 02-0910, REP 02-0950, REP 02-0990)
y Be sure to wear a wrist strap connected to the chassis whenever you unpack parts from a
case. Otherwise, the static electrical charge on your body may damage the parts.
(INST 01-0000, INST 02-0200, INST 02-0250, INST 02-0270, INST 03-0330, INST 03-0490)
(ADD 01-0140, ADD 01-0210, ADD 01-0410, ADD 02-0160, ADD 02-0210, ADD 02-0280,
ADD 03-0000)
REP 02-0830)
y When you install are Disk Drive, Control Unit and ENC Unit/SENC Unit, support its metal part
with your hand that has the wrist strap. You can discharge static electricity by touching the
metal plate.
(INST 01-0000, INST 03-0330, INST 03-0490)
(ADD 03-0000)
(REP 01-0010)
y Since front bezels of the RKM/RKS and the RKAJ are different with each other in their size.
(INST 01-0100)
y Since front bezels of the RKM/RKS and the RKAJ/RKAJAT are different with each other in
their size.
(INST 01-0130)

SAFE 0140-01
y When you install is Control Unit, support its metal part with your hand that has the wrist
strap. You can discharge static electricity by touching the metal plate.
(INST 02-0200)
(ADD 01-0140, ADD 01-0410, ADD 02-0160, ADD 02-0280)
(REP 02-0390, REP 02-0540, REP 02-0660)
y When you install an ENC Unit, support its metal part with your hand that has the wrist strap.
By so doing, you can discharge the static electricity from your body may change the parts.
(INST 02-0250)
y Disk Drives are precision components. Be careful not to expose drives to hard shock.
(INST 02-0270)
(ADD 01-0210, ADD 02-0210)
(REP 02-0070)
y When you install a Disk Drive, support its metal part with your hand that has the wrist strap.
You can discharge static electricity by touching the metal plate.
(INST 02-0270)
(ADD 01-0210)
(REP 02-0070)
y Take full care to connect cables correctly.

(INST 02-0300, INST 03-0610)
y Press the rail against the rack frame as much as possible to secure the rail to the rack
frame. If there is a gap between the rail and the rack frame, the rail may interfere with the
equipment.
(INST 03-0200, INST 03-0250, INST 03-0300)
y If the ENC cables are removed without ensuring intervals of 20 seconds or more, it is feared
that the system goes down.
(ADD 01-0120, ADD 01-0730, ADD 01-1060)
y The system may go down if the AC Input Power Switch is turned off with the instructed ENC
cable connected.
(ADD 01-0120, ADD 01-0730, ADD 01-1060)
y When you remove a Disk Drive, support its metal part with your hand that has the wrist
strap. You can discharge static electricity by touching the metal plate.
(ADD 02-0210)

SAFE 0150-01
y For the system Disk Drives (Disk Drive #0 to #4 of RKM\RKS) regardless of the data Disk
Drives, the Spare Drives and the Disk Drives which do not configure the RAID group, do not
remove the Disk Drives #0 and #1 at the same time with the subsystem power turned on.
There is a possibility of downing the subsystem if removing them.
(REP 02-0070)
y Do not remove these two at the same time for RKM/RKS on which only two Disk Drives are
mounted (Disk Drive #0 and #1).
(REP 02-0070)
y The replacement of the component is restricted in time. This operation requires referring
to the manual. If the subsystem is left with this component removed for more than 10
minutes, it will stop by detecting the thermal alarm.
(REP 02-0300, REP 02-0340)
y When the CALM LED on the Control Unit is on while the ALM LED of the Fan Assembly is on,
be sure to solve the trouble of the Control Unit first.
(REP 02-0300)
y When a trouble of the Power Unit is detected due to a trouble of the Fan Assembly, the
Power Unit does not need to be replaced. When a trouble of the Power Unit is detected
during replacement of the Fan Assembly, pull out and then insert the Power Unit.
(REP 02-0340)
y When replacing the Fan Assembly, do it in haste after preparing a replacement Fan Assembly
and arranging cables, etc. so that they do not disturb the replacement.
(REP 02-0300)
y When replacing the Power Unit, do it in haste after preparing a replacement Power Unit and
arranging cables, etc. so that they do not disturb the replacement.
(REP 02-0340)
y When you install an ENC Unit/SENC Unit, support its metal part with your hand that has the
wrist strap. By so doing, you can discharge the static electricity from your body may
change the parts.
(REP 02-0830)
y When a device is kept with power-off for more than three months, the battery may be
excessively discharged, and it may cause an unrecoverable damage. In such a storing
condition, either charge the battery at least once every three months for more than six (6)
hours, or switch off the battery. Even though the battery is switched off, to prevent
damages from natural discharge, the battery must be charged once every six months for
more than six (6) hours.
(REP 03-0070)

SAFE 0160-01
4. Warning Labels Affixed on the Subsystem
4.1 Floor (RKM+H1J) Model/Floor (RKS+H1J) Model

SAFE 0170-01
3.2 Floor (RKM+RKAJ+H2J) Model/Floor (RKS+RKAJ+H2J) Model

SAFE 0180-01
3.3 Rackmount model (RKM)

SAFE 0190-01
3.4 Rackmount model (RKS)

SAFE 0200-01
3.5 Rackmount model (RKAJ)

SAFE 0210-01
3.6 Rackmount model (RKAJAT)

SAFE 0220-01
3.7 Rackmount model with U7 rack frame

SAFE 0230-01
FE-95DF745-00
Theory
Chapter 1. Warranty and Service................................................................................... THEO 01-0000
Chapter 2. Outline of Subsystem ................................................................................... THEO 02-0000
Chapter 3. Major Specifications of the Subsystem......................................................... THEO 03-0000
Chapter 4. Theory of Operation ..................................................................................... THEO 04-0000
Chapter 5. Outline of P.P ............................................................................................... THEO 05-0000

THEO 00-0000-01

THEO 00-0010-01
Chapter 1.
This page is intentionally left blank.

THEO 01-0000-01
This page is intentionally left blank.

THEO 01-0010-01
Chapter 2. Outline of Subsystem

This chapter explained about the outline of the subsystem which composes a disk array system.
In this chapter, it mechanical and power supplying system structures of each model are
explained separately.
2.1 What is RAID

To put RAID to practical use, some techniques such as striping, mirroring, and parity disk are
used.
Striping
It means to store data spreading it on several Disk Drives. Since a datum is written on several
Disk Drives, time required to access each Disk Drive is shortened and thus, time required for
reading or writing is shortened.
Mirroring
It means to copy all the contents of one Disk Drive to one or more Disk Drives at the same time
in order to enhance reliability.
Parity disk
It is a data writing method used when configure RAID with three or more Disk Drives.
Parity of data in the corresponding positions of two or more Disk Drives is generated and stored
on another Disk Drive.

THEO 02-0000-01
2.1.1 Application of RAID technology

When one I/O processing spans multiple Disk Drives (when the stripe size is too small) during
transaction processing in RAID 5, the performance cannot be exhibited sufficiently.
Therefore, the stripe size of this subsystem is fixed at 64 k bytes only.
Lump writing of data on the Disk Drive and pre-reading of old data are performed by use of the
cache memory so as prevent occurrence of write penalty as far as possible.
y Write penalty
In the RAID 5 configuration, 3 to 16 Disk Drives compose one parity group (2D+1P to 15D+1P).
Since parity data is generated from 2 to 15 data disks in the group, when partial writing of one
stripe in the group occurs in the transaction processing, it is necessary to generate the
corresponding parity data in the group once again. For RAID 5, since parity data is calculated
by the following calculation formula, data before update, parity before update and data
after update are necessary to create the parity.
RAID 5:
[New parity] = ([Data before update] EOR [Data after update]) EOR [Parity before update]

THEO 02-0010-01
2.1.2 RAID levels

It is necessary to understand the characteristics of each RAID level to make the environment
most suitable for the system you want to construct.
The RKM and RKAJ or RKS and RKAJ subsystem supports RAID 0 (2D to 16D), RAID 1, RAID 5 (2D+1P
to 15D+1P), RAID 1+0 (2D+2D to 8D+8D). But, the subsystem configured by the RKM, RKS and
RKAJAT do not support RAID 0.
Table 2.1.1 Outline of RAID Levels
Level Configuration Characteristics
RAID 0 Outline RAID 0 stripes data across Disk Drives (five Disk Drives in the DF700) to
Data block
attain higher throughput.
A B C D E F G H I J
Controller
Advantages Because Disk Drives having redundant data is not needed, Disk Drives
A B C D E can be used efficiently.
F G H I J
: : : : :
: : : : : Disadvantage Data is lost in any failure of the Disk Drive.
: : : : :
Data disk
RAID 1 Data block Outline RAID 1 provides data redundancy by copying all the contents of two Disk
A B C D E F G H I J Drive to another (mirroring).
Read/write performance is a little better than the individual Disk Drive.
Controller
Advantages Data is not lost even if a failure occurs in any Disk Drive.
A A Performance is not lowered even when a Disk Drive fails.
B B
: :
: : Disadvantage RAID 1 is expensive because it requires twice the Disk capacity.
J J
Data disk Mirror disk
RAID 5 Data block Outline RAID 5 consists of three or more Disk Drives.
It uses one of them as a parity disk and writes divided data on the other
A B C D E F G H I J Disk Drives. Recovery from a failure of a data is possible by utilizing the
parity data.
Controller
Since the parity data is stored on all the Disk Drives, a bottleneck of the
parity disk does not occur.
A B C D (A--D)P
E F G (E-H)P H Advantages When reading data, RAID 5 stripes data across Disk Drives in the same
way as that in RAID 0 to attain higher throughput.
: : : : :
: : : : : Disadvantage When writing data, since parity data is required to be updated,
performance of writing small random data is lowered although there is no
: : : : :
Data disk + Parity disk problem regarding writing of continuous data. The performance is also
:Parity lowered when a Disk Drive fails.
*1 : Only the RAID levels supported by DF700 are explained.

THEO 02-0020-01
Level Configuration Characteristics

RAID Outline RAID 1+0 provides data redundancy like RAID 1 by copying all the
1+0 Data block contents of two Disk Drive to another. Different from RAID 1, data
striping is performed over two to eight (RKS is seven) sets of two Disk
A B C D E F G H I J
Drives.
Controller
Advantages Data is not lost even if any Disk Drive fails.
A A B B Besides, since RAID 1+0 stripes data, it can make the performance of
C C D D dealing with small size random accesses higher comparing with RAID 1.
E E F F Performance is not lowered even when a Disk Drive fails.
G G H H Disadvantage RAID 1+0 is expensive because it requires twice the disk capacity.
I I J J
Data Mirror Data Mirror
disk disk disk disk

THEO 02-0030-01
2.2 Outline of the Subsystem

2.2.1 Outline of functions
DF700 subsystem has two models: floor model and rackmount model.
There are four types of the floor model : one is a combination of the RKM and the floor
standing kit (hereafter referred to as Floor (RKM+H1J) Model) and one is a combination of the
RKM, the RKAJ, and the floor standing kit (hereafter, referred to as Floor (RKM+RKAJ+H2J)
Model) and one is a combination of the RKS and the floor standing kit (hereafter referred to as
Floor (RKS+H1J) Model) and one is a combination of the RKS, the RKAJ, and the floor standing
kit (hereafter, referred to as Floor (RKS+RKAJ+H2J) Model).
The rackmount model is a subsystem which is used in the form of a combination of the DF700-
RKM/ DF700-RKS (hereafter, referred to as RKM/RKS.) and the DF700-RKAJ/DF700-RKAJAT
(hereafter, referred to as RKAJ/RKAJAT).(1)
For an external power supplying, RKM, RKS, RKAJ, and RKAJAT are supplied from AC power
supply.
Features of the subsystem are explained below.
y Each of the RKM, Floor (RKM+H1J) Model, RKS, and Floor (RKS+H1J) Model is a subsystem that
has up to 15 disk drives installed and controls the disk drives as components of RAID with
controllers.
y Each of the Floor (RKM+RKAJ+H2J) Model, and Floor (RKS+RKAJ+H2J) Model is a subsystem
that has up to 30 Disk Drives installed and controls the disk drives as components of RAID
with controllers.
y The RKM, RKS mounts up to fifteen Disk Drives and controls them as RAID by a controller.
y The RKAJ/RKAJAT mounts up to fifteen Disk Drives and can be used being connected with the
RKM (2).
y The subsystem uses either Fibre Channel (Non-OFC) as an interface with a host computer.
y The RKM, RKS, RKAJ and RKAJAT are models to be mounted on a 19-type rack frame,
however, them can also be used as floor model when combined with the optional kit.
y Up to the 14 RKAJs/RKAJATs can be connected to the one RKM by the exclusive cables and a
system(1) with a set of the 225 Disk Drives controlled by the controller of the RKM can be
constructed. When the SATA Disk Drives are connected, a system(1) with a set of the 15 FC
Disk Drives and the 210 SATA Disk Drives can be constructed.
y Up to the 6 RKAJs/RKAJATs can be connected to the one RKS by the exclusive cables and a
system(1) with a set of the 105 Disk Drives controlled by the controller of the RKS can be
constructed. When the SATA Disk Drives are connected, a system(1) with a set of the 15 FC
Disk Drives and the 90 SATA Disk Drives can be constructed.
y A special rack frame (DF-F700-U7) is provided, which can mount a various combination of the
RKM/RKS(s) (4 U units high) and RKAJ/RKAJAT (3 U units high) up to a height of 38 U units.
y The DF700 adopts the fibre channel interface that enables data to be transferred from/to a
host at a rate of up to 400 M bytes/s (in the case of the RKM) or up to 200 M bytes/s (in the
case of the RKS).
1 : The two or more RKMs/RKSs cannot be connected to the one system.

THEO 02-0040-01
y The Fibre Channel interface provides 2 ports per Control Unit.

y The Fibre Channel interface board for the RKS has two connection ports expanded from the
one port by means of the Mini-HUB.
(1) Scalability
y Various systems that meet the wide range of needs can be constructed from the single
RKM/RKS with up to 15 Disk Drives to a system in which the number of Disk Drives can be
increased up to 225 (15 FC Disk Drives and 210 SATA Disk Drives, in the case where the SATA
Disk Drives are connected) when up to 14 RKAJs/RKAJATs are connected to the RKM.(1)
y By using the rack frame (U7) exclusive to DF700, you can construct a system conforming to
your demand.
y Spare Disk(s), up to fifteen of which can be set up, can be mounted in any location(s).
You can use the system effectively by mounting each Spare Disk in a Disk Drive slot left
unused as a result of a system construction.
y From the host computer, the subsystem can be used not only as a single large scale Disk Drive
but also as 2,048 logical disks (LUs) at the maximum (RKS: 512 logical disks (LUs) at the
maximum).
y The subsystem enables you to construct a system which can connect up to 126 Fibre Channel
devices by using the Fibre Channel interface and connecting the HUB and switch (hereafter,
referred to as SW.).
(2) Multi-RAID configuration
y Four RAID levels, that is, RAID 0, RAID 1, RAID 5, and RAID 1+0 can be set up. (When the RKAJAT
connected: RAID 1, RAID 5, and RAID 1+0 can be set up)
y Because RAID 1, RAID 5, and RAID 1+0 are provided with redundancy by virtue of mirror disk(s)
and parity disk(s), they do not lose data even when a failure occurs in one of Disk Drives, and
moreover, data can be read/written from/onto them as if there existed no failure.
y With RAID 1+0 of DF700, you can construct a flexible system conforming to your demands from a
system configured with 4 data disks (2D+2D) to that with 16 data disks (8D+8D).
y With RAID 5 of DF700, you can construct a flexible system conforming to your demands from a
system configured with 3 data disks (2D+1P) to that with 16 data disks (15D+1P).
(3) High-speed data transfer

y The subsystem can read and write data at a high-speed by activating Disk Drives in parallel.
y With the Fibre Channel connection, the subsystem can transfer data between the host
computer and the subsystem at a maximum speed of 400 M bytes/s (RKS is 200 M bytes/s).
Enough throughput can be got when connecting devices and making a multiple access.
y By using a non-volatile large-capacity cache memory (RKM is 1,024 M bytes to 2,048 M bytes
/CTL, RKS is 1,024 M bytes/CTL), speed-up of command execution at the time of read/write
hit was achieved.
1 : The two or more RKMs/RKSs cannot be connected to the one system.

THEO 02-0050-01
(4) Large capacity

A maximum of 225 subsystems can be connected. The subsystems provide a maximum of
66.9 T bytes disk capacity at RAID 0.
Further, when the RKAJAT is connected, the maximum disk capacity of 80.9 T bytes is
realized (in the case of RAID 5).
(5) High data availability

y With the redundant RAID configuration (RAID 1,RAID 5, or RAID 1+0), the subsystem can
continuously read or write data without shutting down the subsystem by using the parity
and/or mirror disks even when a Disk Drive failed.
(6) High data reliability

y The Controller of the DF700 adds the original 8-byte data assurance codes to data from a host
computer by automatically generating them, writes them in the Disk Drive together with the
data, and checks them when reading the data, and thus the data reliability is improved.
y On the data bus in the controller, the automatic generation of the data assurance codes and
the check are executed to enhance data reliability in data distribution/concentration control
which is peculiar to the disk array.
(7) Diagnostic and maintenance functions

y Diagnosis and maintenance of the subsystem can be done on a screen of a PC connected to
the subsystem via a LAN.
y Status of the subsystem can be checked and a faulty part can be identified by the Storage
Navigator Modular.
y Diagnosis of the subsystem can be done from a distant place by using the remote
maintenance function (SNMP).
(8) Maintenance
y Adding Disk Drive and maintenance can be performed without powering off the system.
y All the subject components for maintenance can be replaced without powering off the
subsystem. (Excluding the Basic Chassis of Rack Mount Style and Additional Chassis of Rack
Mount Style.)

THEO 02-0060-01
2.2.2 Differences between the DF700 and DF600

Differences between the subsystem and DF600 are explained below.
y Capability of installing up to 15 Disk Drives in the basic frame

The RK/RKS of the DF600 can install up to 14 Disk Drives, whereas the both RKM and RKS of
the DF700 can install up to 15 Disk Drives.
y Capability of connecting the additional frame to the RKS

The additional frame cannot be connected to the RKS of the DF600, whereas up to 6
additional frames (RKAJs/RKAJATs) can be connected to the RKS of the DF700.
y Adoption of the Mini-HUB for the RKSs port

The number of ports in the RKS of the DF600 is one/CTL, whereas in the RKS of the DF700, it
is two connection ports/CTL by virtue of the use of the Mini-HUB.
The number of usable connection ports out of the two connection ports is fixed according to
the topology of the Fibre Channel connected.
The Fabric Topology is used in the case of a connection such as that via the SAN Switch. It
makes it possible to use one of the two Fibre ports (0A-0 and 1A-0) only.
The FC-AL Topology is used in the case of a connection such as the direct connection and
that via the SAN Managed Hub. It makes it possible to use both of the two connection ports.
y Adoption of high-speed RISC processor

The microprocessor for the RKM of the DF700, it was changed from POWER PC 7455 (677
MHz) for the RKM of the DF600 to POWER PC 7447A (1.0 GHz) that is faster and has higher
performance. The microprocessor for the RKS of the DF700 is POWER PC 7447A (500 MHz).
y With the Fibre Channel connection, the subsystem can transfer data between the host
computer and the subsystem at a maximum speed of 400 M bytes/s (RKS is 200 M bytes/s).
Enough throughput can be got when connecting devices and making a multiple access.
y Duplicated power supply

In the DF700 like the DF600, the power supply which integrates functions of the IN BOX and
the Power Unit is duplicated as a standard configuration.
y Adoption of Fibre Channel Disk Drive

The Disk Drives with the Fibre Channel interface are adopted in the same way as the DF600.
The maximum number of Disk Drives that can be connected to the RKM of the DF700 is 225,
which is equivalent to that for the RK of the DF600, that is, 224. This enables users to
construct various RAID configurations. The maximum number of Disk Drives that can be
connected to the RKS is 14 for the DF600, whereas it is 105 for the DF700; it also makes it
possible to construct various RAID configurations.

THEO 02-0070-01
y Adoption of SATA Disk Drive (DF700-RKAJAT model only)

The Disk Drives with the SATA interface are adopted for the RKS/RKM of the DF700 in the
same way as the RK of the DF600.
The maximum number of SATA Disk Drives that can be connected to the RKM of the DF700 is
210, which is equivalent to that for the RK of the DF600, that is, 209. This enables users to
construct various RAID configurations. The Disk Drives cannot be connected to the RKS of
the DF600, whereas the RKS of the DF700 can connect up to 90 Disk Drives. This also
enables users to construct various RAID configurations.

THEO 02-0080-01
2.3 Subsystem Structure

For a single unit of Rackmount model, there are RKM/RKS/RKAJ/RKAJAT.
Floor model (RKAJAT is not supported) or Rackmount model are configured by combining single
units.
RKM/RKS/RKAJ/RKAJAT has a Power Unit power-supplied from AC power supply.
(1) RKM, RKS, RKAJ, RKAJAT, Floor (RKM+H1J/RKS+H1J) Model, Floor (RKM+RKAJ+H2J/
RKS+RKAJ+H2J) Model
The subsystem can be composed of a combination of the RKM/RKS (s) and RKAJ (s).
There are four types of the floor model : one is a combination of the RKM and the floor
standing kit (hereafter referred to as Floor (RKM+H1J) Model) and one is a combination of the
RKM, the RKAJ, and the floor standing kit (hereafter, referred to as Floor (RKM+RKAJ+H2J)
Model) and the other is a combination of the RKS and the floor standing kit (hereafter referred
to as Floor (RKS+H1J) Model) and one is combination of the RKS, the RKAJ, and the floor
standing kit (hereafter, referred to as Floor (RKS+RKAJ+H2J) Model).
As for the rackmount model (RKM, RKS), a system with one RKM and up to 10 RKAJ/RKAJATs
(with 165 Disk Drives at the maximum) can be configured when using the U7 rack frame (DF-
F700-U7).
The system in the DF700 can be configured with up to 14 RKAJ/RKAJATs for a total of 225 Disk
Drives at a maximum of 2 U7 rack frames.
Racks heights are measured in meters, EIA units, and U. 1EIA unit equals 1U, which equals
44.45 mm.

THEO 02-0090-01
(a) RKM, RKS, RKAJ, RKAJAT, Floor (RKM+H1J/RKS+HIJ) Model, Floor

(RKM+RKAJ+H2J/RKS+RKAJ+H2J) Model
Floor (RKS+H1J) Model Floor (RKS+RKAJ+H2J) Model

(1 RKS) (1 RKS and 1 RKAJ)
RKS
(4 U/EIA unit)
Floor model
Floor (RKM+H1J) Model Floor (RKM+RKAJ+H2J) Model

(1 RKM) (1 RKM and 1 RKAJ)
RKM
(4 U/EIA unit)
RKAJ
(3 U/EIA unit)
U7 rack model
Any combination can be mounted as long as it
requires a height less than 38 U (EIA Standard.38 EIA
units).
y However, be sure to mount at least the 1 RKM/RKS.
RKAJAT Rackmount model with U7 rack frame Rackmount model with U7 rack frame
(3 U/EIA unit) Minimum configuration (1 RKM/RKS) Maximum configuration
(1 RKM and 10 RKAJ/RKAJATs)
Rackmount model (1 RKS and 6 RKAJ/RKAJATs)
Figure 2.3.1 Subsystem Configuration

THEO 02-0100-01
2.3.1 External appearances

(1) Appearances of Floor (RKM+H1J/ RKM+RKAJ+H2J/ RKS+H1J/ RKS+RKAJ+H2J) Model, RKM, RKS
and RKAJ
(a) Floor (RKM+H1J) Model, Floor (RKM+RKAJ+H2J) Model, Floor (RKS+H1J) Model, Floor
(RKS+RKAJ+H2J) Model
RKM(RKS) RKAJ
RKM(RKS)
540 mm 540 mm
737 mm
260 mm 737 mm
309 mm
(a) Floor (RKM+H1J/RKS+H1J) Model (b) Floor (RKM+RKAJ+H2J/RKS+RKAJ+H2J) Model
Figure 2.3.2 Appearances of the Floor Models

THEO 02-0110-01
Floor (RKM+RKAJ+H2J) Model Control Unit

Front bezel (Option)
Fan Assembly
Backup Battery Unit Power Unit

(Battery) (RKAJ)
Control Unit
Disk Drive
ENC Unit
Power Unit
(RKM)
Fan Assembly
Floor (RKM+H1J) Model
RKAJ (Front view) RKM (Front view) RKM (Rear view) RKAJ (Rear view)
Floor (RKS+RKAJ+H2J) Model Control Unit

Front bezel (Option)
Fan Assembly
Power Unit
(RKAJ)
Control Unit
Disk Drive
Backup Battery Unit

(Battery)
ENC Unit
Power Unit
(RKS)
Fan Assembly
Floor (RKS+H1J) Model
RKAJ (Front view) RKS (Front view) RKS (Rear view) RKAJ (Rear view)
Figure 2.3.3 Major Components of the Floor Model

THEO 02-0120-01
(b) Rackmount model (RKM, RKS, RKAJ)
RKM(RKS)
174 mm RKAJ
483 mm 650 mm
129 mm
483 mm 650 mm
483 mm
Figure 2.3.4 Appearances of the RKM, RKS and RKAJ
Disk Drive ENC Unit

Front bezel
RKAJ (Front view) Power Unit (RKAJ) RKAJ (Rear view)
Control Unit (Option)

Disk Drive Front bezel Fan Assembly Control Unit Fan Assembly
Backup Battery Unit Power Unit (RKM)

RKM (Front view) RKM (Rear view)
Control Unit (Option)

Disk Drive Front bezel Fan Assembly Control Unit Fan Assembly
Backup Battery Unit Power Unit (RKS)

RKS (Front view) RKS (Rear view)
Figure 2.3.5 Major Components of the RKM, RKS and RKAJ

THEO 02-0130-01
(c) Rackmount model with U7 rack frame
1,880 mm
RKAJ(*1)
RKM(*1)
610 mm 813 mm
*1 : This figure shows an example of a subsystem with the one RKM and eleven RKAJs.
Figure 2.3.6 Appearances of the Rackmount Model with U7 Rack Frame

THEO 02-0140-01
(d) Rackmount model (RKAJAT)
RKAJAT
129 mm
483 mm 650 mm
Figure 2.3.7 Appearances of the RKAJAT
Disk Drive Front bezel SENC Unit
Power Unit (RKAJAT)

RKAJAT (Front view) RKAJAT (Rear view)
Figure 2.3.8 Major Components of the RKAJAT

THEO 02-0150-01
2.3.2 Configuration of floor model

(1) Floor (RKM+H1J/RKS+H1J) Model
This model is produced by the combination of the RKM/RKS and Floor Setting Kit (DF-F700-
H1J).
Floor (RKM+H1J) Model/Floor (RKS+H1J) Model
RKM/RKS
Power Unit
Power Unit
AC 100/200 V AC 100/200 V
(Single phase) (Single phase)
Figure 2.3.9 System Configuration of Floor (RKM+H1J/RKS+H1J) Model
(2) Floor (RKM+RKAJ+H2J/RKS+RKAJ+H2J) Model

This model is produced by the combination of the RKM/RKS, RKAJ, and Floor Setting Kit (DF-
F700-H2J).
Floor (RKM+RKAJ+H2J/RKS+RKAJ+H2J) Model
RKM/RKS RKAJ
Power Power
Unit Unit
(RKAJ)
Power Power
Unit Unit
(RKAJ)
AC 100/200 V AC 100/200 V

THEO 02-0160-01
Figure 2.3.10 System Configuration of Floor (RKM+RKAJ+H2J/RKS+RKAJ+H2J) Model

THEO 02-0160-01
2.3.3 System configuration of the rackmount model

(1) Configuration of RKM, RKS, RKAJ and RKAJAT
Configuration block diagram of the RKM, RKS, RKAJ and RKAJAT is shown below. Each of the
RKM, RKS, RKAJ and RKAJAT can mount fifteen Disk Drives. (The RKM has a Control Unit which
can control up to 225 Disk Drives configured as RAID.
The Disk Drives can be assigned to data disk(s), parity disk(s) (mirror disk(s)) depending on the
RAID level.
Up to fifteen Spare Disks can be mounted in any locations within the configuration assured.
Figure 2.3.12, Figure 2.3.13 and Figure 2.3.14 shows configuration block diagrams of the RKM,
RKS, RKAJ and RKAJAT respectively.
Configuration of RKS : Basic component and

Host computer indispensable optional part
: Option (additional) part
Interface Interface Interface Interface
Control Unit #0 Control Unit #1(*2)

Cache Unit Cache Unit
LAN (*1) (*1) LAN
Fan Assembly Fan Assembly

#0 #1
Backup Battery Backup Battery
Unit #0 Unit #1(*4)
0
Panel Power Unit Power Unit
1
ASSY (RKM) #0 (RKM) #1
2
Status
panel 14
Disk Drives(*3) To RKAJ/RKAJAT AC 100/200 V AC 100/200 V

*1 : Cache Unit :
DF-F700-C1GJ
*2 : Control Unit (for extension) :
RKMDF-F700-F1JM (Fibre Channel interface, 2port)
RKSDF-F700-F1JS (Fibre Channel interface, 1port)
*3 : Disk Drive :
DF-F700-AGF72, DF-F700-AGF146, DF-F700-AGF300
*4 : This Backup Battery Unit is not installed in RKS.
Figure 2.3.11 System Configuration Block Diagrams of the RKM and RKS

THEO 02-0170-01
Disk Drives(*1) : Basic component and

indispensable optional part
From RKM/RKS (*2) /RKAJ : Option (additional) part
ENC Unit ENC Unit Power Unit (RKAJ) AC 100/200 V

#0 0 #1 #0 (Single phase)
Status 1 AC 100/200 V
Power Unit (RKAJ)
panel (Single phase)
2 #1
14
To RKAJ/RKAJAT
*1 : Disk Drive :
DF-F700-AGF72, DF-F700-AGF146, DF-F700-AGF300
*2 : When connecting RKAJ, a dual controller configuration is required for the RKM/RKS.
Figure 2.3.12 System Configuration Block Diagrams of the RKAJ

THEO 02-0180-01
: Basic component and

From RKM/RKS/RKAJ/RKAJAT indispensable optional part
: Option (additional) part
Disk Drives(*1)
SENC Unit #0 SENC Unit #1 Power Unit (RKAJAT) #0 AC 100/200 V
Path CTL
(Single phase)
0
Power Unit (RKAJAT) #1 AC 100/200 V
Status
Path CTL (Single phase)
panel FC-SATA 1
FC-SATA
conversion Path CTL
conversion
Path CTL
Path CTL
Path CTL
Path CTL
14
To RKAJ/RKAJAT
*1 : Disk Drive :
DF-F700-ATE250R, DF-F700-ATE400R
Figure 2.3.13 System Configuration Block Diagrams of the RKAJAT

THEO 02-0190-01
2.3.4 Configuration of rackmount model with U7 rack frame

(1) Configuration of rackmount model with U7 rack frame
The DF-F700-U7 is an exclusive rack frame for mounting up to a height of 38 U (EIA Standard).
(1 RKM and 10 RKAJs)
It consists of a rack frame main body and PDBs to be used to supply AC power to power supply
units of the mounted RKM(s), RKS(s) and RKAJ(s). The four PDBs are installed to allow the
power system to be duplicated.
Up to the eleven RKAJs can be mounted through an addition of the UPDU7 (optional).
UPDU7 (PDB)
(option)
AC 200 V
AC 200 V
U7 rack frame
PDB RKAJ
RKAJ
RKAJ
RKAJ
RKAJ
RKAJ
RKAJ
AC 200 V AC 200 V AC 200 V RKAJ AC 200 V
RKAJ
AC 200 V AC 200 V AC 200 V AC 200 V
RKAJ
RKM RKM
Maximum configuration
Minimum configuration
(A case where eleven RKAJs are installed is shown)
Figure 2.3.14 System Configuration of Rackmount Model with U7 Rack Frame

THEO 02-0200-01
2.4 Configuration of Internal Power Supply System

For a single unit of Rackmount model, there are RKM/RKS/RKAJ/RKAJAT Floor model (RKAJAT
is not supported) or Rackmount model are configured by combining single units.
RKM/RKS/RKAJ/RKAJAT has a Power Unit power-supplied from AC.
(1) Internal power supply system configuration (RKM/RKS/RKAJ/RKAJAT)

Figure 2.4.1, Figure 2.4.2, and Figure 2.4.3 shows the connection diagrams of the internal
power supply system of the RKM, RKS, RKAJ, and RKAJAT respectively.
Input power to the RKM, RKAJ and RKS is supplied from the Power Unit.
Even if the main switch is off, each voltage (BS) is supplied. To turn off each voltage (BS), the
AC Power unit switch of the Power Unit needs to be turned off (1).
Two Power Units are installed as the standard to duplicate the power supply system.
Accordingly, the subsystem can continue its operation even when a failure occurs in one of the
Power Unit or power cables.
Further, part replacement can be done while the subsystem is operating.
1 : In the situation where the main switch is turned off, do not leave the components removed from the subsystem for
a long time. The power supply alarm can be given because of an abnormal alarm.

THEO 02-0210-01
+5V
STATUS
Power Unit #0
To external +12V(BS) PANEL
+12V(BS)
AC
+3.3V(BS)
AC100240V Control Unit #0

+12V
(Single phase)
DC-DC +3.3V(BS)
+3.3V(BS) Interface Board

+5V
DC-DC +3.3V
+12V(BS)
Power Unit #1
Reg. +1.5V
To external +12V(BS)
AC Reg. +1.8V
Reg. +1.8V
AC100240V Reg. +2.5V

+12V
(Single phase)
+3.3V
DC-DC +1.1V
+5V DC-DC +2.5V
Reg. +5V
DC-DC +2.5V
Backup Battery Unit #0 +12V(BS)
DC-DC +1.5V
DC-DC +1.8V
Backup Battery Unit #1(*1) +12V(BS) +1.8V
Reg. +3.3V
Fan Assembly #0 Control Unit #1

DC-DC +3.3V(BS)
+3.3V(BS)
+3.3V(BS) Interface Board
DC-DC +3.3V
+12V(BS)
Fan Assembly #0
Reg. +1.5V
+3.3V(BS) Reg. +1.8V
Reg. +1.8V
FC Disk Drive #0 Reg. +2.5V
+3.3V
DC-DC +1.1V
FC Disk Drive #1 DC-DC +2.5V
Reg. +5V
DC-DC +2.5V
DC-DC +1.5V
DC-DC +1.8V
+1.8V
FC Disk Drive #14 Reg. +3.3V
Figure 2.4.1 Connection diagram of Power Supply System (RKM/RKS)

THEO 02-0220-01
Power Unit #0
To external STATUS
AC +12V
+5V
AC100240V
(Single phase) ENC #0
+12V
+5V DC-DC +3.3V
DC-DC +2.5V
Power Unit #1
+5V
To external
AC +12V
ENC #1
AC100240V +12V
(Single phase)
DC-DC +3.3V
DC-DC +2.5V
+5V
+5V
ID_SW
Reg. +3.3V
FC Disk Drive #0
FC Disk Drive #1
FC Disk Drive #14
Figure 2.4.2 Connection diagram of Power Supply System (RKAJ)

THEO 02-0230-01
STATUS 1
+5V
Power Unit #0
To exeternal STATUS 2
AC +12V
+5V
AC100240V
(Single phase) SENC #0
+12V
+5V DC-DC +1.8V
+5V
Power Unit #1
Reg. +3.3V
To external
AC +12V
Reg. +2.5V
AC100240V
(Single phase) SENC #1
+12V
+5V DC-DC +1.8V
+5V
Reg. +3.3V
Reg. +2.5V
ID_SW
Reg. +3.3V
SATA Disk Drive #0
Reg. +3.3V
SATA Disk Drive #1
SATA Disk Drive #14
Figure 2.4.3 Connection diagram of Power Supply System (RKAJAT)

THEO 02-0240-01
2.5 Configuration of Internal Data System

Figure 2.5.1, Figure 2.5.2 and Figure 2.5.3 shows the connection block diagram of the internal
data system of the RKM, RKS and RKAJ respectively.
Figure 2.5.4 and Figure 2.5.5 shows the connection block diagram of the internal data system
of the RKM/RKS+RKAJ/RKAJAT respectively.
(1) Host interface

The RKM, RKS and RKAJ subsystem utilize the PCI bus for its host interface, and Control Unit
implements a Fibre Channel interface as a standard.
In the Fibre Channel configuration, one Control Unit can have up to two ports. With the dual
Controller configuration, the subsystem can have up to four Fibre Channel ports.
(The controller of the RKS can have two ports or up to four ports in the case of the dual
controller system by virtue of the Mini-HUB.)
(2) Cache memory backup

The Cache Unit is backed up by the battery. Therefore, data in the Cache Unit is maintained
even when a sudden power failure or a power supply unit failure occurs.
(3) Spare Disks

When a spare Disk Drive is set in a group of Disk Drives, even if a failure occurs in the Disk
Drive, the same operation as before can be performed through reconstruction of data to the
Spare Disk Drive. Up to 15 Spare Disk Drives can be set.

THEO 02-0250-01
Host computer
RKM
Interface #0A Interface #0B Interface #1A Interface #1B
PCI bus
Cache memory Cache memory

LSI LSI
Control Unit #0 Control Unit #1

#0 (option)
#1
Disk Drive group

(Disk Drive #0-#14)
#14
RKAJ
RKAJAT
To RKAJ/RKAJAT
Figure 2.5.1 Internal Data Connection of the RKM

THEO 02-0260-01
Host computer
0A-0 0A-1 1A-0 1A-1 RKS
Mini-HUB Mini-HUB
Interface #0A Interface #1A

PCI bus

LSI LSI

#0 (option)
#1
Disk Drive group

(Disk Drive #0-#14)
#14
RKAJ
RKAJAT
To RKAJ/RKAJAT
Figure 2.5.2 Internal Data Connection of the RKS
From RKM/RKS/RKAJ
ENC Unit #0 ENC Unit

#1 RKAJ
#0
#1
Disk Drive group

(Disk Drive #0-#14)
#14
RKAJ
To RKAJ
Figure 2.5.3 Internal Data Connection of the RKAJ

THEO 02-0270-01
Host computer
RKM
Interface #0A Interface #0B Interface #1A Interface #1B
PCI bus

LSI LSI

#0
#1
Disk Drive group

(Disk Drive #0-#14)
#14
SENC Unit #0 SENC Unit #1 SENC Unit #0 SENC Unit #1

Path CTL Path CTL
The first one of the FC-SATA FC-SATA FC-SATA FC-SATA The second of the
0 0
RKAJATs conversion conversion conversion conversion RKAJATs
connected to the Path CTL connected to the
Path CTL
RKM RKM
Unit ID #21 Unit ID #32
1 1
Path CTL Path CTL
2 2
Path CTL Path CTL
14 14
RKAJAT RKAJAT
Disk Drives Disk Drives
The third of the ENC Unit ENC Unit

#0 #0 #1
RKAJs connected
to the RKM
Unit ID #03 #1
#2
#14
RKAJ
Disk Drives
To RKAJ/RKAJAT
*1 : A case, where the RKAJAT, RKAJAT, RKAJ, and so forth are connected to the RKM in this order, is shown.
Figure 2.5.4 Internal Data Connection of the RKM+RKAJ/RKAJAT

THEO 02-0280-01
Host computer
0A-0 0A-1 1A-0 1A-1
RKS
Mini-HUB Mini-HUB
Interface #0A Interface #1A

PCI bus

LSI LSI

#0
#1
Disk Drive group

(Disk Drive #0-#14)
#14
SENC Unit #0 SENC Unit #1 SENC Unit #0 SENC Unit #1

Path CTL Path CTL
The first one of the FC-SATA FC-SATA FC-SATA FC-SATA The second of the
0 0
RKAJATs conversion conversion conversion conversion RKAJATs
connected to the connected to the
Path CTL Path CTL
RKS RKS
Unit ID #21 Unit ID #32
1 1
Path CTL Path CTL
2 2
Path CTL Path CTL
14 14
RKAJAT RKAJAT
Disk Drives Disk Drives
The third of the ENC Unit ENC Unit

#0 #0 #1
RKAJs connected
to the RKS
Unit ID #03 #1
#2
#14
RKAJ
Disk Drives
*1 : A case, where the RKAJAT, RKAJAT, RKAJ, and so forth are connected to the RKS in this order, is shown.
In the case of the RKS, up to 6 RKAJs/RKAJTs can be connected.
Figure 2.5.5 Internal Data Connection of the RKS+RKAJ/RKAJAT

THEO 02-0290-01
2.6 Configuration of Built-in Software

2.6.1 Block diagram of built-in software configuration
The built-in software configuration is shown in Figure 2.6.1.
For the shaded portions in the figure, detailed explanations are given on the succeeding pages.
Control Unit
Fibre Channel chip set
RAM Flash memory
Microprogram Configuration Fixed part program System parameters

(1) information (2-1) (5-1)
(5-2)
Flashprogram
(2-2)
SNMP
informations (*1)
(5-3)
ENC SENC
ENC firmware SENC firmware

(3-1) (3-2)
Disk Drive
Disk
Firmware
(4)
*1 : The SNMP information can be used when the SNMP function is validated by the P-002D-J200.
Figure 2.6.1 Software Structure

THEO 02-0300-01
(1) Microprograms
These are programs that control.
Their version numbers are controlled in the format of 07xxx/xx.
There are types of microprograms shown below corresponding to as many usages.
No. Type of usage Version Supplying media

1 Fibre Channel 07xxx/xx (:Optional) One CD
/xx in the version number may not be added or may be controlled by the other method.
(2) Flashprograms
These are programs to start up the subsystem after powering on.
(2-1) Fixed part program
No. Name Type
1 Fixed part program F (:Optional)
(2-2) Flashprogram
No. Name Type
1 Flashprogram (Fibre Channel) (*1) 07xxx/xx (:Optional)
*1 : This program and the microprogram are controlled unitarily.
(3) ENC/SENC firmware

The version of the firmware can be see using Storage Navigator Modular or through the Web.
(3-1) ENC firmware
This firmware controls the RKAJ.
(3-2) SENC firmware
This firmware makes a change from the S-ATA to the FC.
This firmware controls the RKAJAT.
(4) Disk firmware

You can also refer to even a version of firmware which the disk has independently. (You can
do it by means of an simplicity trace.)
(5) Parameter Information

The parameters are classified into the following three types for operating the subsystem.
(5-1) System parameters
Parameters necessary for the subsystem start-up process from the turning on of the main
switch to the coming on of the READY LED (green) are called system parameters.
For the details of it, refer to the for System Parameter Chapter 1. Setting (Storage
Navigator Modular) (SYSPR 01-0000).
The system parameters are stores in the flash memory.
Back up of the system parameter is automatically performed to the drive in the changing
opportunity.

THEO 02-0310-01
(5-2) Configuration information

This is a piece of information on the configuration, such as the RAID configuration and LU
capacity, for the subsystem to record user data.
The configuration information exists on the Disk Drives when the subsystem main switch is
turned off, and is spread onto the RAM at the time when the main switch is turned on.
When it is changed, that on the Disk Drives are also changed.
(5-3) SNMP information
The SNMP information is a parameter for making the SNMP agent support function work
effectively.
When the SNMP information makes the SNMP agent support function effective, it edits the
template on the SNMP EVA FD and registers the template with the subsystem.
To update the information, edit the SNMP information on the SNMP EVA FD and register it
with the subsystem.
For the details of it, refer to the SNMP Agent Support Function Users Guide.

THEO 02-0320-01
2.6.2 Storages for parameters

The storages in which the parameters on the controller are stored are shown in Table 2.6.1.
Table 2.6.1 Storages for Parameter

No. Parameter Storage Description
1 Fixed part program Flash memory The parameters are stored in the flash memory.
Flashprogram No provision of storage against a power shut off is required for the
System parameters parameters because the flash memory can retain information even if
a power is shut off.
The parameters can be backed up to the following to provide against
a trouble.
Fixed part program................. Cannot be backed up.
Flash program ........................ Automatically backed up to the
system area.
System parameters................ Automatically backed up to the
system area.
2 Microprogram System area Generally, information in a RAM is erased when the main switch is
Configuration information turned off. Therefore, the subsystem also stores the parameters
SNMP information used on the RAM on the Disk Drive.
(An area is reserved in the Disk Drive to store them. The area is
called system area.)

THEO 02-0330-01
.
Chapter 3. Major Specifications of the Subsystem

Basic specifications of the subsystem and the optional devices which compose a disk array
system are shown below.
(1) Floor model

(a) Floor (RKM+H1J) Model/Floor (RKM+RKAJ+H2J) Model
Remote adapter Host computer
Floor (RKM+H1J) Model Fibre Channel Fibre Channel Fibre Channel

(1 RKM + H1J) HUB HBA
UPS
Fibre Channel Fibre Channel Fibre Channel

Floor (RKM+RKAJ+H2J) Model
(1 RKM + 1 RKAJ + H2J) HUB HBA
UPS
: Optional part
: Accessory
Figure 3.1 System Outline of Floor Model (RKM+H1J/RKM+RKAJ+H2J)
(b) Floor (RKS+H1J) Model/Floor (RKS+RKAJ+H2J)
Floor (RKS+H1J) Model Fibre Channel Fibre Channel Fibre Channel

(1 RKS + H1J) HUB HBA
UPS
Fibre Channel Fibre Channel Fibre Channel

Floor (RKS+RKAJ+H2J) Model
(1 RKS + 1 RKAJ + H2J) HUB HBA
UPS
: Optional part
: Accessory
Figure 3.2 System Outline of Floor Model (RKS+H1J/RKS+RKAJ+H2J)

THEO 03-0000-01
(2) Rackmount model
(a) Rackmount model (RKM/RKAJ/RKAJAT)

+ U7 rack frame
19-type rack frame
RKM
(DF700-RKM) + Fibre Channel Fibre Channel Fibre Channel
Rail kit HUB HBA
RKAJ Decoration panel
(DF700-RKAJ) UPS
: Optional part
RKAJAT : Accessory
(DF700-RKAJAT)
Rackmount model
Figure 3.3 System Outline of Rackmount Model (RKM/RKAJ/RKAJAT)
(b) Rackmount model (RKS/RKAJ/RKAJAT)

+ U7 rack frame
19-type rack frame
RKS
(DF700-RKS) + Fibre Channel Fibre Channel Fibre Channel
Rail kit HUB HBA
RKAJ Decoration panel
(DF700-RKAJ) UPS
: Optional part
RKAJAT : Accessory
(DF700-RKAJAT)
Rackmount model
Figure 3.4 System Outline of Rackmount Model (RKS/RKAJ/RKAJAT)

THEO 03-0010-01
3.1 Basic Specifications of the Subsystem

(1) Floor (RKM+H1J) Model/Floor (RKM+RKAJ+H2J) Model
Table 3.1.1 Basic Specifications

Model Floor model
Item Floor (RKM+H1J) Model Floor (RKM+RKAJ+H2J) Model
Confi- Configuration 1 RKM 1 RKM
guration + +
H1J Floor setting kit (Optional) 1 RKAJ
+
H2J Floor setting kit (Optional)
Subsystem appearance
Disk Drive Disk Drive size 101.6146.125.4

used (WDH) (mm)
Data capacity(*1) 71.3/143.3/287.6
(G byte)
Rotational speed 10,000
(min-1)
Maximum mountable 15 30
quantity (unit)
Host Host interface 4 G bps Fibre Channel Optical (Non-OFC)
interface Data transfer speed 400 M bytes/s (Fibre Channel)
(i.e. maximum speed for
transfer to host)
Number of Single Fibre Channel : 2
ports controller
Dual Fibre Channel : 4
controller
Transferred block size 512
(bytes)
RAID RAID level(*3) 0/1/5/1+0
specifi- RAID RAID 0 2D to 15D 2D to 16D
cations(*2) configuration RAID 1 1D+1D
(unit of RAID 5 2D+1P to 14D+1P 2D+1P to 15D+1P
addition) RAID 1+0 2D+2D to 7D+7D 2D+2D to 8D+8D
*1 : These values of storage capacity are calculated as 1 G bytes = 1,00,000,000 bytes.
This definition is different from that (1 k bytes = 1,024 bytes) shown on PCs you are using.
*2 : D : Data disk
P : Parity disk
*3 : Although the subsystem with a configuration of RAID 5, RAID 1, or RAID 1+0 provides data reliability enhanced by
means of redundancy, a possibility remains that user data is lost owing to an unexpected failure of a host
computer or hardware/software of the subsystem itself.
Therefore, users are requested to back up all data for restoration in case where the original data is lost.

THEO 03-0020-01
Model Floor model

Internal Control CPU POWER PC 7447A (1.0 G Hz)
logic Control memory Flash memory : 2 M bytes
specifi- L2 Cache memory : 512 k bytes
cations SRAM : 64 M bytes
Data assurance method Data bus : Through-parity
Cache memory : ECC (1 bit for correction, 2 bits for detection)
Disk Drive : Data assurance code
Physical Start-up time (min) Standard : 3(*1)
Specifi- Chassis size (260737540) (309737540)
cations (WDH) (mm)
Mass(*2) (kg) 80 approx. 125 approx.
Acoustic noise(*3) 56 approx. 59 approx
(dB)
EIA Standard for unit
(U) (*4)
Input power Input voltage AC 100/200 (100 to 120/200 to 240)
specifi- (V)
cations Frequency 50/60 1
(Hz)
Number of phases, cabling Single-phase with protective grounding
Steady-state current(*5)(*6) 4.22/2.12 4.22+2.62/2.12+1.32
AC 100 to 120 / 200 to 240
(A)
*1 : The start-up time may be longer than three minutes depending on the configuration.
*2 : Value of maximum configuration (in the case where all the mountable Disk Drives and Control Unit are
mounted).
*3 : A noise emitted at the time of start is not included.
*4 : Racks height are measured in meters, EIA units, and U. 1EIA unit equals 1U, which equals 44.45 mm.
*5 : For the both systems, plan the facilities for supplying power to the subsystem according to the specifications for
the single power supply because when a failure occurs, only the one power supply operates.
*6 : The current value in the operation by a single power supply unit is same as that in the operation by both power
supply units.

THEO 03-0030-01
Model Floor model

Input power Breaking current (A) 16.0
specifi- Required Steady state 840 or less 1,360 or less
cations power (VA)
Starting 840 or less 1,400 or less
state(*1)
(VA)
Heat value (normal) 3,025 or less 4,900 or less
(kJ/h)
Cache Capacity 1,024 to 2,048
specifi- (M bytes/CTL)
cations Control method Read LRU/Write after
Battery backup Provided
Backup duration(*2) 24
(h) (When cache of 2,048 M bytes/CTL)
Mainte- Parts to which hot yControl Unit yControl Unit
nance replacement is yDisk Drive yDisk Drive
specifi- applicable(*3) yPower Unit (RKM) yPower Unit (RKM)
cations/ yCache Unit yPower Unit (RKAJ)
anti-fault yFan Assembly yCache Unit
specifi- yBackup Battery Unit(*4) yFan Assembly
cations yBackup Battery Unit(*4)
yENC Unit
*1 : Power requirement in the case of the maximum configuration is shown. When planning facilities such as the
uninterrupted power supply (UPS), specify the power factor as 100% for calculation. Value at 100 V/200 V is
shown.
(Example : 300 W=300 VA)
The actual required power may exceed the value shown in the table when the tolerance is included.
*2 : y The backup time of the data on the Cache memory is indicated (in the case of the battery full charge).
y In the battery that exceeds the periodic replacement cycle, the backup time may become remarkably short.
y Non-volatility of data in the cache memory is ensured against power trouble such as a sudden power failure.
It transfers data in the Cache memory to Disk Drives by turning off the power normally, and prevents the
battery charge from being wasted.
y When the subsystem enters the Cache Backup mode, a warning (lighting of the orange LED) informing of a
voltage drop of the battery may be issued when the subsystem is started. It shows that the remaining
capacity of the battery is not sufficient, and in this state, the subsystem operates disabling the Write Cache
function automatically.
When the battery is charged, the warning indication disappears, and the subsystem continues the operation
enabling the Write Cache function. The warning indication disappears within six hours at the latest. Even
when the warning is being indicated, normal functional operation is assured although the operation is
performed in the Write-Through mode and the R/W performance is lowered because the Write Cache function
is disabled.
y Since battery is subject to effect of environmental temperature, avoid using a battery in unnecessarily
continuous operation at high temperature.
y If the subsystem is not energized for more than three months, the over discharging of the battery occurs and it
may cause the battery an unrecoverable damage. In this case, the battery must be energized more than 6
hours at least once three months, or store the subsystem with the switch of the battery turned off. Even
when the switch is turned off, the battery discharges naturally. Even in this case, however, charge the
battery once per six months for longer than 6 hours because spontaneous discharge is done.
y To minimize the deterioration of battery, use and keep a battery at the lowest temperature possible.
*3 : Only the trained service personnel can perform a hot replacement.
*4 : The battery in the Backup Battery unit is a part to be recycled.

THEO 03-0040-01
Model Floor model

Mainte- Microprogram installation Flash memory/Disk Drive
nance method (resident)
specifi- SVP (built-in exclusive yFailure information logging/Power control
cations/ tool) function yControlling microprogram patching
anti-fault yDisk Drive controlling microprogram down loading
specifi- yConfiguration information change
cations yDisk Drive recovery initiating process
(This process is automatically executed when Disk Drive is replaced.)
Spare Disk Up to 15 of mounted Disk Drive s can be set to Spare Disks
Collection of trace and Download the trace and dump through LAN on the maintenance PC.
dump
Display function yStatus LEDs (POWER, READY, WARNING, and ALARM)
yLED of maintenance part
Insulation Insulation withstand AC 1,500 V AC 1,500 V
perform- voltage (10 mA, 1 min) (100 mA, 1 min)
ance Insulation resistance DC 500 V, 10 M or more

THEO 03-0050-01
(2) Floor (RKS+H1J) Model/Floor (RKS+H2J) Model

Model Floor model
Item Floor (RKS+H1J) Model Floor (RKS+RKAJ+H2J) Model
Confi- Configuration 1 RKS 1 RKS
guration + +
H1J Floor setting kit (Optional) 1 RKAJ
+
H2J Floor setting kit (Optional)

used (WDH) (mm)
Data capacity(*1) 71.3/143.3/287.6
(G byte)
Rotational speed 10,000
(min-1)
quantity (unit)
Host Host interface 2 G bps Fibre Channel Optical (Non-OFC)
interface Data transfer speed 200 M bytes/s (Fibre Channel)
(i.e. maximum speed for
transfer to host)
Number of Single Fibre Channel : 2 (In the case of Mini-HUB use)
ports controller
Dual Fibre Channel : 4 (In the case of Mini-HUB use)
controller
(bytes)
RAID RAID level(*3) 0/1/5/1+0
specifi- RAID RAID 0 2D to 15D 2D to 16D
cations(*2) configuration RAID 1 1D+1D
(unit of RAID 5 2D+1P to 14D+1P 2D+1P to 15D+1P
addition) RAID 1+0 2D+2D to 7D+7D 2D+2D to 8D+8D
*2 : D : Data disk
P : Parity disk
*3 : Although the subsystem with a configuration of RAID 5, RAID 1, or RAID 1+0 provides data reliability enhanced by
means of redundancy, a possibility remains that user data is lost owing to an unexpected failure of a host

THEO 03-0060-01
Model Floor model

Internal Control CPU POWER PC7447A (500 M Hz)
logic Control memory Flash memory : 2 M bytes
specifi- L2 Cache memory : 512 k bytes
cations SRAM : 64 M bytes
Data assurance method Data bus : Through-parity
Cache memory : ECC (1 bit for correction, 2 bits for detection)
Disk Drive : Data assurance code
Specifi- Chassis size (260737540) (309737540)
cations (WDH) (mm)
Mass(*2) 80 approx. 125 approx.
(kg)
Acoustic noise(*3) 56 approx. 59 approx
(dB)
EIA Standard for unit
(U) (*4, *5)
Input power Input voltage AC 100/200 (100 to 120/200 to 240)
specifi- (V)
cations Frequency (Hz) 50/60 1
Number of phases, cabling Single-phase with protective grounding
Steady-state current(*6)(*7) 4.02/2.02 4.02+2.62/2.02+1.32
AC 100 to 120/200 to 240
(A)
Breaking current (A) 16.0
Required Steady state 800 or less 1,320 or less
power (VA)
Starting 800 or less 1,360 or less
state(*8)
(VA)
Heat value (normal) 2,880 or less 4,755 or less
(kJ/h)
mounted).
*4 : Can be mounted on the Hitachi special rack frame (U7). For the mounting, special rails for the rack frame and
decoration panel(s) are required separately depending on the number of the mounted subsystem(s).
*6 : For the both systems, plan the facilities for supplying power to the subsystem according to the specifications for
the single power supply because when a failure occurs, only the one power supply operates.
*7 : The current value in the operation by a single power supply unit is same as that in the operation by both power
supply units.
shown. (Example : 300 W=300 VA) The actual required power may exceed the value shown in the table when
the tolerance is included.

THEO 03-0070-01
Model Floor model

Cache Capacity 1,024
cations Control method Read LRU/Write after
Battery backup Provided
Backup duration(*1) 24
(h) (When cache of 1,024 M bytes/CTL)
Mainte- Parts to which hot yControl Unit yControl Unit
nance replacement is yDisk Drive yDisk Drive
specifi- applicable(*2) yPower Unit (RKS) yPower Unit (RKS)
cations/ yCache Unit yCache Unit
anti-fault yFan Assembly yFan Assembly
specifi- yBackup Battery Unit(*3) yBackup Battery Unit(*3)
cations Microprogram installation Flash memory/Disk Drive
method (resident)
SVP (built-in exclusive yFailure information logging/Power control
tool) function yControlling microprogram patching
yDisk Drive controlling microprogram down loading
yConfiguration information change
yDisk Drive recovery initiating process
Collection of trace and Download the trace and dump through LAN on the maintenance PC.
dump
Display function yStatus LEDs (POWER, READY, WARNING, and ALARM)
yLED of maintenance part
is disabled.

THEO 03-0080-01
(3) Rackmount (RKM+RKAJ/RKAJAT) Model

Model Rackmount model
RKM + RKAJ/RKAJAT + 19-type rack frame
RKM RKAJ RKAJAT With U7 rack frame
Item One rack Two racks

Confi- Configuration 1 RKM 1 RKAJ 1 RKAJAT 1 RKM+RKAJ/ 1 RKM+RKAJ/
guration RKAJAT (10units)(*1) RKAJAT (14units)
(Maximum configuration) (Maximum configuration)
+ +
U7 rack frame U7 rack frame
(Optional) (Optional)

used (WDH) (mm)
Data capacity (*2) 71.3/143.3/287.6 245.7/393.4 71.3/143.3/245.7/287.6/393.4
(G byte)
Rotational speed 10,000 7,200 RKAJ: 10,000
(min-1) RKAJAT: 7,200
Maximum mountable 15 165 225
quantity (*3) (unit)
Host Host interface 4 G bps Fibre 4 G bps Fibre Channel Optical (Non-OFC)
interface Channel Optical
(Non-OFC)
Data transfer speed 400 M bytes/s 400 M bytes/s (Fibre Channel)
(i.e. maximum speed for (Fibre Channel)
transfer to host)
Number of Single Fibre Channel : 2 Fibre Channel : 2
ports controller
Dual Fibre Channel : 4 Fibre Channel : 4
controller
/Optional
(bytes)
*1 : When nine or more RKAJ/RKAJATs are mounted on U7 rack, optional PDU/PDB is necessary.

THEO 03-0090-01


RAID RAID level (*1) 0/1/5/1+0 1/5/1+0 Mount RKAJ only: 0/1/5/1+0
specifi- Mount RKAJAT: 1/5/1+0
cations(*2) RAID RAID 0 2D to 15D 2D to 16D Mount RKAJ only: 2D to 16D
configuration Mount RKAJAT: Not support
(unit of RAID 1 1D+1D
addition) RAID 5 2D+1P to 14D+1P 2D+1P to 15D+1P(*3) 2D+1P to 15D+1P
RAID 1+0 2D+2D to 7D+7D 2D+2D to 8D+8D
Internal Control CPU It is the same as POWER PC 7447A (1.0 G Hz)
logic Control memory With U7 rack y Flash memory : 2 M bytes
specifi- frame y L2 Cache memory : 512 k bytes
cations y SRAM : 64 M bytes
Data assurance method y Data bus : Through-parity
y Cache memory :ECC
(1 bit for correction, 2 bits for detection)
y Disk Drive : Data assurance code
Specifi- Chassis size (483650174) (483650129) (6108131,880) (610813)2(1,880)
cations (WDH) (mm)
Mass(*5) (kg) 58 approx. 40 approx. 40 approx. 690 approx. 1,050 approx.
Acoustic noise(*6) 57 approx. 60 approx 65 66
(dB) approx. approx.
EIA Standard for unit 4 3 Max. 38 Max. 38
(U) (*7)
Input power Input voltage AC 100/200 (100 to 120/200 to 240) AC 200 (200 to 240)
specifi- (V)
(Hz)
Number of phases, Single-phase with protective grounding
cabling
Steady-state current(*8) 4.22/2.12 2.62/1.32 2.42/1.22 -/20.0(One PDB) -/20.0(One PDB)
AC 100/200 (A)
*1 : Although the subsystem with a configuration of RAID 5, RAID 1, or RAID 1+0 provides data reliability enhanced
by means of redundancy, a possibility remains that user data is lost owing to an unexpected failure of a host
*2 : D : Data disk
P : Parity disk
*3 : It is recommended to use the RAID configuration within 6D+1P.
mounted).
*8 : The current value in the operation by a single power supply unit is same as that in the operation by both
power supply units.

THEO 03-0100-01


Input power Breaking current (A) 16.0 15.0 20.0
specifi- Required Steady state 840 or less 520 or less 480 or less 6,040 or less 8,120 or less
cations power (VA) (RKM+RKAJ (10units))/ (RKM+RKAJ (14units))/
5,640 or less 7,560 or less
(RKM+RKAJAT (10units)) (RKM+RKAJAT (14units))
Starting 840 or less 560 or less 480 or less 6,440 or less 8,680 or less
state (*1) (RKM+RKAJ (10units))/ (RKM+RKAJ (14units))/
(VA) 5,640 or less 7,560 or less
Heat value (normal) 3,025 or less 1,875 or less 1,730 or less 21,745 or less 29,235 or less
(kJ/h) (RKM+RKAJ (10units))/ (RKM+RKAJ (14units))/
20,305 or less 27,220 or less
Cache Capacity 1,024 to 2,048 1,024 to 2,048
cations Control method Read LRU/ Read LRU/Write after
Write after
Battery backup Provided Provided
Backup duration(*2) 24 24
(h) (When cache of (When cache of 2,048 M bytes/CTL)
2,048 M bytes/CTL)
Mainte- Parts to which hot yControl Unit yDisk Drive yControl Unit
yDisk Drive
nance replacement is applicable yDisk Drive yPower Unit yDisk Drive
yPower Unit
specifi- (*3) yPower Unit (RKM) (RKAJ) yPower Unit (RKM/RKAJ/RKAJAT)
(RKAJAT)
cations/ yCache Unit yENC Unit yCache Unit
ySENC Unit
specifi- yBackup Battery yBackup Battery Unit(*4)
cations Unit(*4) yENC Unit
ySENC Unit
yPDB
shown.
enabling the Write Cache function. The warning indication disappears within six hours at the latest. Even when
the warning is being indicated, normal functional operation is assured although the operation is performed in the
Write-Through mode and the R/W performance is lowered because the Write Cache function is disabled.

THEO 03-0110-01


Mainte- Microprogram installation It is the same as Flash memory/Disk Drive
nance method With U7 rack frame (resident)
specifi- SVP (built-in exclusive y Failure information logging/Power control
cations/ tool) function y Controlling microprogram patching
anti-fault y Disk Drive controlling microprogram down loading
specifi- y Configuration information change
cations y Disk Drive recovery initiating process
Collection of trace and It is the same as Download the trace and dump through LAN on the
dump With U7 rack frame maintenance PC.
Display function y Status LEDs (POWER, READY, WARNING, and ALARM)
y LED of maintenance part

THEO 03-0120-01
(4) Rackmount (RKS+RKAJ/RKAJAT) Model

RKS + RKAJ/RKAJAT + 19-type rack frame
RKS RKAJ RKAJAT With U7 rack frame
Item One rack

Confi- Configuration 1 RKS 1 RKAJ 1 RKAJAT 1 RKS
guration +
RKAJ/RKAJAT (6 units)(*1)
(Maximum configuration)
+
U7 rack frame (Optional)

used (WDH) (mm)
Data capacity (*2) 71.3/143.3/287.6 245.7/393.4 71.3/143.3/245.7/287.6/393.4
(G byte)
Rotational speed 10,000 7,200 RKAJ: 10,000
(min-1) RKAJAT: 7,200
quantity (*3) (unit)
Host Host interface 2 G bps Fibre 2 G bps Fibre Channel Optical (Non-OFC)
interface Channel Optical
(Non-OFC)
Data transfer speed 200 M bytes/s 200 M bytes/s (Fibre Channel)
(i.e. maximum speed for (Fibre Channel)
transfer to host)
Number of Single Fibre Channel : 1 Fibre Channel : 2 (In the case of Mini-HUB use)
ports controller (In the case of Mini-
HUB use: 2)
Dual Fibre Channel : 2 Fibre Channel : 4 (In the case of Mini-HUB use)
controller (In the case of Mini-
/Optional HUB use: 4)
(bytes)
*1 : Up to the nine RKAJ/RKAJATs can be mounted through an addition of the PDU/PDB (optional).

THEO 03-0130-01

RKS + RKAJ/RKAJAT + 19-type rack frame
Item One rack

RAID RAID level (*1) 0/1/5/1+0 1/5/1+0 Mount RKAJ only: 0/1/5/1+0
specifi- Mount RKAJAT: 1/5/1+0
cations(*2) RAID - RAID 0 2D to 15D 2D to 16D Mount RKAJ only: 2D to 16D
configuration Mount RKAJAT: Not support
(unit of RAID 1 1D+1D
addition) RAID 5 2D+1P to 14D+1P 2D+1P to 15D+1P(*3) 2D+1P to 15D+1P
RAID 1+0 2D+2D to 7D+7D 2D+2D to 8D+8D
Internal Control CPU It is the same as POWER PC 7447A (500 M Hz)
logic Control memory With U7 rack y Flash memory : 2 M bytes
specifi- frame y L2 Cache memory : 512 k bytes
cations y SRAM : 64 M bytes
Data assurance method y Data bus : Through-parity
y Cache memory :ECC
(1 bit for correction, 2 bits for detection)
y Disk Drive : Data assurance code
Specifi- Chassis size (483650174) (483650129) (6108131,880)
cations (WDH) (mm)
Mass(*5) (kg) 56 approx. 40 approx. 40 approx. 500 approx.
Acoustic noise(*6) 57 approx. 60 approx 63 approx.
(dB)
EIA Standard for unit 4 3 Max. 38
(U) (*7)
Input power Input voltage AC 100/200 (100 to 120/200 to 240) AC 200 (200 to 240)
specifi- (V)
(Hz)
Number of phases, Single-phase with protective grounding
cabling
Steady-state current(*8) 4.02/2.02 2.62/1.32 2.42/1.22 -/20.0(One PDB)
AC 100/200 (A)
*1 : Although the subsystem with a configuration of RAID 5, RAID 1, or RAID 1+0 provides data reliability enhanced
by means of redundancy, a possibility remains that user data is lost owing to an unexpected failure of a host
*2 : D : Data disk
P : Parity disk
*3 : It is recommended to use the RAID configuration within 6D+1P.
mounted).
*8 : The current value in the operation by a single power supply unit is same as that in the operation by both
power supply units.

THEO 03-0140-01

Item One rack

Input power Breaking current (A) 16.0 15.0 20.0
specifi- Required Steady state 800 or less 520 or less 480 or less 3,920 or less (RKS+RKAJ (6units))/
cations power (VA) 3,680 or less (RKS+RKAJAT (6units))
Starting 800 or less 560 or less 480 or less 4,160 or less (RKS+RKAJ (6units))/
state (*1) 3,680 or less (RKS+RKAJAT (6units))
(VA)
Heat value (normal) 2,880 or less 1,875 or less 1,730 or less 14,115 or less (RKS+RKAJ (6units))/
(kJ/h) 13,250 or less (RKS+RKAJAT (6units))
Cache Capacity 1,024 1,024
cations Control method Read LRU/ Read LRU/Write after
Write after
Battery backup Provided Provided
Backup duration(*2) 24 24
(h) (When cache of (When cache of 1,024 M bytes/CTL)
1,024 M bytes/CTL)
Mainte- Parts to which hot yControl Unit yDisk Drive yControl Unit
yDisk Drive
nance replacement is applicable yDisk Drive yPower Unit yDisk Drive
yPower Unit
specifi- (*3) yPower Unit (RKS) (RKAJ) (RKAJAT) yPower Unit (RKS/RKAJ/RKAJAT)
cations/ yCache Unit yENC Unit ySENC UnityCache Unit
specifi- yBackup Battery yBackup Battery Unit(*4)
cations Unit(*4) yENC Unit
ySENC Unit
yPDB
shown.
is disabled.

THEO 03-0150-01

Item One rack

Mainte- Microprogram installation It is the same as Flash memory/Disk Drive
nance method With U7 rack frame (resident)
specifi- SVP (built-in exclusive y Failure information logging/Power control
cations/ tool) function y Controlling microprogram patching
anti-fault y Disk Drive controlling microprogram down loading
specifi- y Configuration information change
cations y Disk Drive recovery initiating process
Collection of trace and It is the same as Download the trace and dump through LAN on the
dump With U7 rack frame maintenance PC.
Display function y Status LEDs (POWER, READY, WARNING, and ALARM)
y LED of maintenance part

THEO 03-0160-01

THEO 03-0170-01
Chapter 4. Theory of Operation

This chapter explains the flow and format of data. It also explains the data processing.
4.1 Power On/Off Sequence

4.1.1 IMPL sequence
The procedure for processing the IMPL executed when the subsystem is started is explained
below. The IMPL sequence is broadly divided into four processes and they are executed
sequentially.
(1) Boot loader

After the boot loader is booted from the flash memory, it executes the minimum CUDG and
hardware initialization. Then, it loads the local memory loader from the flash memory to the
local memory and transfers the control to the local memory loader.
(2) Local memory loader
The local memory loader performs the CUDG and hardware initialization which are necessary
for loading the OS load module. It loads the OS load module in the local memory after the
spin-up of all Disk Drives of the RKM (RKS), RKAJ, and RKAJAT is completed. And then, the
local memory loader passes the control to the OS.
(3) OS
The OS initializes the table on the local memory for the communication between the tasks
using the root task of the OS and generates the DF initialization task.
(4) DF initialization task
After making the initial setting of the hardware and the DF table, DF initialization task
generates DF task. The load of the CUDG and the takeover information is executed in the DF
task, and then the loop diagnosis on the Disk Drive side and the load of pinned data are
performed.

THEO 04-0000-01
Turning on the main switch
Boot loader
y Booting from flash memory
y CUDG
y Hardware initialization
y Loading of the local memory loader to the local memory
Local memory loader

y CUDG
y Hardware initialization
y The spin-up of all Disk Drives in the RKM (RKS), RKAJ, and RKAJAT.
y Microprogram loading
OS
y Table initialization
y DF initialization task generation
DF initialization task
y Initialization of table and D-CTL
y DF task generation
CUDG
Take-over information loading
Loop diagnosis on the Disk Drive side
PIN data loading
Scan
Figure 4.1.1 IMPL Sequence

THEO 04-0010-01
4.1.2 Disk Drive powering on sequence

If all the Disk Drive motors are rotated at the same time an overcorrect may be caused.
To avoid it, the drives are started in the following sequence.
(1) Disk Drive Starting Sequence (RKM/RKS/RKAJ/RKAJAT)
Start
Starting the Disk Drives #0 to #4 of the RKM/RKS

Starting the Disk Drives #0 to #3 of the RKAJ/RKAJAT
RKM/RKS
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Number of connectable Disk
Drives is 165 at the 1st additional
maximum. (When 10 RKAJ/RKAJAT
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
additional RKAJ/RKAJATs
are mounted on a U7 rack.)
In the RKS, number of
connectable Disk Drives is
105 at the maximum. (When 9th additional
RKAJ/RKAJAT
6 additional RKAJ/RKAJATs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
10th additional About
RKAJ/RKAJAT
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 30 seconds
14th additional
RKAJ/RKAJAT
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
In the configuration with 2 racks, up to 225 Ascertaining completion of the spin-ups of the
Disk Drives (14 additional RKAJ/RKAJATs) Disk Drives #0 to #4 in the RKM/RKS.
can be connected.
When the second rack has been connected, Ascertaining completion of the spin-ups of the
start the RKAJ/RKAJATs mounted on the Disk Drives #0 to #3 in the RKAJ/RKAJATs.
second rack in the same procedure as the first
rack.
A To THEO-04-0030
Figure 4.1.2(1/3) Disk Drive Starting Sequence (RKM/RKS/RKAJ/RKAJAT)

THEO 04-0020-01
From THEO 04-0020 A

Starting the Disk Drives #4 to #9 of the RKAJ/RKAJATs
RKM/RKS
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
RKAJ/RKAJAT
10th additional About
RKAJ/RKAJAT
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
30 seconds
14th additional
RKAJ/RKAJAT
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
In the configuration with 2 racks, up to 225 Ascertaining completion of the spin-ups of

Disk Drives (14 additional RKAJ/RKAJATs) the Disk Drives #5 to #9 in the RKM/RKS.
can be connected.
When the second rack has been connected, Ascertaining completion of the spin-ups of
start the RKAJ/RKAJATs mounted on the the Disk Drives #4 to #9 in the
second rack in the same procedure as the first RKAJ/RKAJATs.
rack.
B To THEO-04-0040

THEO 04-0030-01
From THEO 04-0030 B

Starting the Disk Drives #10 to #14of the RKAJ/RKAJATs
RKM/RKS
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
RKAJ/RKAJAT
10th additional
About
RKAJ/RKAJAT 30 seconds
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
14th additional
RKAJ/RKAJAT
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
In the configuration with 2 racks, up to 225

Disk Drives (14 additional RKAJ/RKAJATs) Ascertaining completion of the spin-ups of
can be connected. the remaining Disk Drives.
When the second rack has been connected,
start the RKAJ/RKAJATs mounted on the
second rack in the same procedure as the first
rack.
Completed of spin-ups process

THEO 04-0040-01
4.1.3 Sequential shutdown

When the subsystem is instructed to shut it down because of the host computer powering off
(remote control) or the main switch turning off (local control), it watches completion of
processes being executed and not executed yet for all the logical devices.
After ascertaining completion of all of them, it executes the destaging.
When doing the above, if a track failed to be destaged (pinned data) occurs, it stores the Pin
information in the system area on the system disk.
Then, after the take-over information is stored in the system area of the system disk and the
power supplying from the Backup Battery Unit is shut off, the subsystem is notified of the
permission for powering off.
The AC Power Unit Switch of the subsystem becomes able to be turned off after receiving the
permission.
Detection of powering off instruction.
Start of destaging
y Dirty data
y Pinned data
y Take-over information
Spin-down of the Disk Drive
Shut off of the power supply from the Backup

Battery unit.
Turning off of the AC Power Unit Switch is

enabled.
Figure 4.1.3 Flow Chart of Sequential Shutdown

THEO 04-0050-01
4.2 Data Format

Figure 4.2.1 shows the data format.
To the sub-block, the check code the address assurance code (LA), write sequence (WR_SEQ),
reserve (RSV) and data assurance code (LRC), is added.
The physical format on the physical disk is that recorded in the data field in units of 520 bytes.
Cache memory data
Data Check Data Check

code code
8
512 bytes
bytes
SUB BLOCK SUB BLOCK (520 bytes)

(520 bytes)
Disk Drive data
LA WR_SEQ RSV LRC LA WR_SEQ RSV LRC

Data ECC Data ECC
4 bytes 1 bytes 1 bytes 2 bytes 4 bytes 1 bytes 1 bytes 2 bytes
00 00
Figure 4.2.1 Data Format

THEO 04-0060-01
4.3 Read/Write Operation

4.3.1 Command execution
In the subsystem, all R/W commands are executed via the Cache memory.
y When read data is in the Cache memory, the data in the Cache memory is transferred to the
host computer (Read hit operation).
y Only when read data is not in the cache memory, the data is transferred to the host
computer directly from the Disk Drive (Read miss operation). The data is left in the Cache
memory then, the read hit operation can be performed at the time of the next reading.
y To improve the responding performance of write operation, the write-after operation, in
which a operation completion is reported to the host computer when a data writing into the
Cache memory is completed, is performed. After that, the Controller generates the parity
and writes the data on the Disk Drive asynchronously.
y Data in the Cache memory is backed up by batteries. Thus, a data loss caused by a power
failure, etc. can be prevented.
Data flows are shown in Figure 4.3.1.
Operation Flow of data

Read hit
Host compputer READ Cache memory
Disk Drive
Completion report
Read error
Host compputer Cache memory
READ
Disk Drive
Completion report
Write
Host compputer WRITE Cache memory
Completion report
Old data/
Disk Drive
Old parity
New data/
New parity
: Flow of data
: Flow of Command
Figure 4.3.1 Flow of Data

THEO 04-0070-01
4.3.2 Dual system configuration

(1) Feature of dual system
(a) The flexible system can be configured by virtue of the two Control Units installed.
This allows the system configuration, which fits the host computer operation, to be provided.
For details, refer to Item (2), Dual system configuration.
(b) Data is duplicated and written on the Cache memories on the two Control Units respectively.
The duplication makes it possible to continue the operation and assure user data even when a
Controller failure occurs.
(2) Dual system configuration
The Dual Active mode makes the two controllers operate in parallel.
In this system configuration, it allocates the controlled LU to each Control Unit. For the
method of accessing to the LU, which is not controlled, from the Control Unit, there are two
ways, reallocating to the Control Unit in charge of the LU and requesting to the Control Unit
in charge of the LU, and it is determined by the access frequency of each Control Unit.
In the Dual system configuration, it executes the processing by requesting it to the Control Unit
in charge of the LU when accessing to the LU, which is not controlled, from the Control Unit.
If no access is made from the controller that controls the LU within one minute, however, re-
assignment of the LU to the controller is made.
Incidentally, when one of the dual controller attempts to access an LU that is out of its control,
the performance will be lowered because it accomplished the access by making a request to
another controller that controls the LU for the access.
Host computer #0 Host computer #1
LU0 In the normal state

In the abnormal state
(A switching operation on the host
LU1
computer side is necessary.)
Figure 4.3.2 System Configuration

THEO 04-0080-01
4.4 Cache Memory Control

4.4.1 Purpose of Cache memory
(1) Mitigation of the write penalty (overheads for generating the parity which is unique to RAID)
that accompanies the write-after operation
Received write data is nonvolatile with batteries in order to prevent the data loss due a power
failure that might occur before it is written to the HDD. Further, with the duplexed
configuration of Controllers, write data are written into both Controller Cache memories, so
that the write data is kept even in a case of a controller failure.
(2) Speed-up of sequential reading operation by means of pre-fetch

The reading performance is enhanced as follows. The subsystem studies the received
commands and when it perceives that it is receiving read commands to read data from
continuous addresses, it executes the pre-fetch operation to read the next read data from a
Disk Drive before receiving the next read command. Thus the subsystem makes it possible to
read from the cache memory when it receives the read command from a host.
(3) Faster sequential read operation

Performance of the sequential read operation is improved through impounding some amount of
write data in the Cache memory at the sequential access and destaging it out to an HDD at
once.
(4) Achieving the cache read hit at executing a highly local job by the LRU algorithm
Further, a one-hundred percent cache hit rate can be realized by virtue of the Cache Residency
Manager function (see Section 4.5 Optional Functions (THEO 04-0160).).

THEO 04-0090-01
4.4.2 Cache memory configuration

The cache memory consists of the following components.
y Subsystem management area
y Directory part
y Data part
The cache memory configuration corresponding to each subsystem configuration is shown
below.
a. For the single controller configuration
Subsystem management area
Directory part
User area
Data part
b. For the dual controller configuration (in the Dual Active mode)
Directory part Directory part

Duplex writing
Data part Data part
Directory part Directory part

Duplex writing
Data part Data part
Active controller Active controller

THEO 04-0100-01
4.4.3 Cache memory structure

(1) Cache memory structure
The Cache memory consists of a directory section for controlling data and a data section for
storing user data.
(2) Data part

Data stored in the Cache memory is controlled in the state in which it is divided into segments
with fixed length 16 k bytes. However, when the High Performance Partitioning function is
used, the length of a segment can be changed to from 4 k bytes to 64 k bytes.
The minimum unit of data is sub-block (logical block of 512 bytes). When the segment length
is 16 k bytes, one segment is 32 sub-blocks. Data storage is done in units of sub-block.
When a command to write data of one logical block (512 bytes) is received, for example, a
segment is secured and the received write data is stored in one of the sub-blocks in the
segment. The data area is also used as a work area while of the parity generation.
Data Data Data
Cache memory
Segment xxxxx Segment Segment Segment
xxxxxxxxxx
1 segment = 32 sub-blocks
Sub-block 1 sub-block = 1 logical block
Figure 4.4.1 Data Structure in Cache Memory

THEO 04-0110-01
(3) Directory part

The directory consists of a hash table for deciding hit or miss and SGCBs for controlling the
segments. The SGCB has a one-to-one correspondence with the segment and has a pointer to
the segment concerned and information regarding the status of the segment concerned.
The hash table stores the segment management information addresses.
When the segment management information is NULL, an error is occurs.
Data Directory
LUN
Hash LBA
Segment SGCB Hash table
function
SGCB NULL
SGCB address
One-to-one SGCB address
correspondence

Synonyms are
allowed
NULL
NULL
16 k bytes
SGCB address
Figure 4.4.2 Control Structure in Cache Memory

THEO 04-0120-01
4.4.4 Basic operation of cache control

The following dynamic optimizing operation is performed in the cache control.
(1) Dynamic optimization of read/write cache area assignment

The read and write cache areas are not fixed but dynamically assigned according to an I/O
instruction from a host.
Cache data part
Write cache
Dynamic area
change Write
Reception of a Reception of a date
lot of read Read lot of write
commands data commands
Read cache (Note)
area
Work area for
parity
generation
To be used To be used
completely as a read completely as a write
cache cache
NOTE : No wider write cache data area than the threshold value is assigned in order to
secure the area for parity generation.
(2) Dynamic optimization of destaging algorithm

The optimum destaging algorithm is selected automatically according to a writing pattern given
by a host computer. (Refer to Subsection 4.4.5 Destaging operation (THEO 04-0140).)
(3) Dynamic optimization of staging algorithm
The optimum staging algorithm is selected automatically through a study of a read command
issued by a host computer. (Refer to Subsection 4.4.6 Staging operation (Writing to the Cache
memory) (THEO 04-0150).)

THEO 04-0130-01
4.4.5 Destaging operation

Write data transferred from a host computer is stored in the cache memory and written to a
Disk Drive asynchronously. This operation to write data to a Disk Drive asynchronously is
called destaging operation.
In the destaging operation, random and sequential accesses are discriminated and written to a
Disk Drive in a way optimum for each of them.
(1) Destaging of random data

Data is destaged in units of LBA. Old data and its parity to be destaged are staged from a disk.
A new parity is generated from new data, the old data, and the old parity and then the new
data and new parity are destaged in units of LBA.
Cache memory
Disk Drive
Old data/old parity
New data/new parity
Figure 4.4.3 Destaging of Random Data
(2) Destaging of sequential data

Data is destaged in units of stripe. A new parity is generated from write data, and then new
data and the new parity are destaged in units of stripe.
Cache memory
Disk Drive
New data/new parity
Figure 4.4.4 Destaging of Sequential Data

THEO 04-0140-01
4.4.6 Staging operation (Writing to the Cache memory)

(1) Random reading
The LRU (Least Recently Used) method is used for assigning the Cache memory to improve the
hit rate.
(2) Sequential reading

According to the learning of received commands, in case of a command to read back data from
consecutive addresses is received, a pre-fetch read data from the next area of the HDD is
performed prior to the following read command. When the following read command is
received, the data is read back from the Cache memory, so that the read performance is
improved.

THEO 04-0150-01
4.5 Optional Functions

(1) ShadowImage in-system replication
This subsystem provides the ShadowImage in-system replication function as an optional
function.
To use the ShadowImage in-system replication, the P-002D-J311 is required separately.
The ShadowImage in-system replication controls LU copying done within one and the same
subsystem. It can create a copy (secondary volume) of an LU within one and the same
subsystem keeping the redundancy that the source LU (primary volume) has.
(For the details, refer to the manual supplied with the P-002D-J311.)
(2) TrueCopy remote replication

The subsystem provides the TrueCopy remote replication as an optional function. To use the
TrueCopy remote replication, the P-002D-J312 is required separately.
The TrueCopy remote replication supports the mode, in which data of disk subsystems
connected via the Fibre Channel interface are equalized, by always synchronizing their data.
Besides, the function makes the copying speed higher by transferring differential data only.
(3) Copy-on-write SnapShot

This subsystem provides the Copy-on-write SnapShot as an optional function.
To use the Copy-on-write SnapShot, the P-002D-J310 is required separately.
Copy-on-write SnapShot is a function to internally retain a logical duplication of the primary
volume data at the time of the command instruction.
Copy-on-write SnapShot can create up to 14 duplication volumes per primary volume and
manage data in two or more generations within the disk subsystem.
(4) Data Retention Utility

This subsystem provides the Data Retention Utility as an optional function.
To use the Data Retention Utility, the P-002D-J309 is required separately.
Data Retention Utility is an option for protecting a logical unit (LU) against an illegal access
from a host computer by setting an access attribute to LU.
(5) LUN Manager

The subsystem provides the LUN Manager as an optional function.
To use the LUN Manager, the P-002D-J308 is required separately.
The LUN Manager enables the subsystem to make a suitable response to each connected host
even within the same port by grouping the connected hosts within a port and setting the logical
unit mapping and the Host Connection mode for each host group.

THEO 04-0160-01
(6) Cache Residency Manager

This subsystem provides the Cache Residency Manager as an optional function.
To use the Cache Residency Manager, the P-002D-J305 is required separately.
The Cache Residency Manager to make the data of the specified LU resident in the Cache
memory installed in the Control Unit, and to execute all the accesses from the server related
to the LU concerned by cache hit without generating any access of the Disk Drive.
(7) SNMP Agent Support Function

This subsystem provides the SNMP Agent Support Function as an optional function.
To use the SNMP Agent Support Function, the P-002D-J303 is required separately.
The SNMP Agent Support Function reports occurrences of failure to the workstation for
monitoring the network via the SNMP (Simple Network Management Protocol) of the open
platform. It reports conditions of command operation (such as a number of command
receptions and number of cache hits) of the disk array subsystem.
It enables you to refer to the conditions of command operation depending on a type of access
from a host and you can utilize it as information for tuning subsystem performance.
(8) LUN Expansion

This subsystem provides the LUN Expansion as an optional feature.
To use the LUN Expansion, the P-002D-J304 is required separately.
The LUN Expansion is that to expand a size of an LU (volume) accessed by a host computer by
combining LUs (volumes) internally.
(For the details, refer to the manual supplied with the P-002D-J304).
(9) Password Protection

The subsystem provides the Password Protection as an optional function.
To use the Password Protection, the P-002D-J302 is required separately.
The Password Protection prevents any DF700 from being concurrently accessed by users by
limiting users of Storage Navigator Modular to be permitted to access the DF700. It can
suspend the information provided from the DF700 to the user who has no access authority, and
avoid the case that two or more users update the configuration information at the same time.
(10) Performance Monitor

This subsystem provides the Performance Monitor as an optional function.
To use the Performance Monitor, the P-002D-J306 is required separately. Performance
Monitor acquires information on performance of the subsystem and utilization rates of
resources. Further, the information acquired is displayed with line graphs in the Monitor.

THEO 04-0170-01
(11) Cache Partition Manager

The subsystem provides the Cache Partition Manager as an optional function. To use the
Cache Partition Manager, the P-002D-J307 is required separately.
Cache Partition Manager is a function to tune the cache memory and has the following
functions. (For the details, refer to the manual supplied with the P-002D-J307.)
y A function to partition the cache memory and to make each LUs domain exclusive
y A function to change the segment size for each partition
y A function to make data of a specific LU reside in the cache memory in order to make all
access by a host computer to the LU result in cache hits preventing the access from
being made to Disk Drives.

THEO 04-0180-01
4.6 Operation Against Disk Failure Occurs

(1) I/O operation against Disk Drive failure
In the subsystem with the RAID1, RAID5, or RAID1+0 configuration, even when a failure occurs
in one Disk Drive and data cannot be read from it, the target data can be recovered by means
of using data on the other normal Disk Drives.
In the case of RAID1 and RAID1+0, data on the mirror Disk Drive is used, and in the case of
RAID5, data on the other Disk Drive on the same stripe is used. By means of these measures,
even when a Disk Drive failure occurs, reading/writing can be done as before.
Figure 4.6.2 shows the outline of the data reading operation performed when a Disk Drive
failure occurs.

THEO 04-0190-01
Data B reading request

(a) Data B read request
B B
B B
A B C D P A B
A B
E F G P H C C D
D
I J P E F
E F
Disk Drive 1 Disk Drive 2 Disk Drive 3 Disk Drive 4 Disk Drive 5 Disk Drive 1 Disk Drive 2 Disk Drive 3 Disk Drive 4
RAID 5 (in the case 4D+1P) RAID 1+0 (in the case 2D+2D)
B
A, B, C xxx ; data
P ; parity data
A, B, Cxxx ; mirror data
B
A A
B B
Disk Drive 1 Disk Drive 2
RAID 1
Figure 4.6.1 Data Reading Operation When Disk Drive is Normal

THEO 04-0200-01
(b) When a Disk Drive failure occurs
B B
A C D P B
A B C D P A A B B
E F G P H C C D D
I J P E E F F
Disk Drive 1 Disk Drive 2 Disk Drive 3 Disk Drive 4 Disk Drive 5 Disk Drive 1 Disk Drive 2 Disk Drive 3 Disk Drive 4
RAID 5 (in the case of 4D+1P) RAID 1+0 (in the case of 2D+2D)
B
A, B, C xxx ; data
P ; parity data
B
A A
B B
Disk Drive 1 Disk Drive 2
RAID 1
Figure 4.6.2 Data Reading Operation When a Disk Drive Failure Occurs

THEO 04-0210-01
(2) Data assurance when a disk failure occurs

The subsystem can have a Spare Disk (s) optionally. Data on a Disk Drive which is blocked
owing to its failure or a Disk Drive in which a number of error occurrence has exceeded the
specified value is automatically reconstructed on the Spare Disk.
This operation is performed in the background without making the host computer conscious of
it, so that I/O request can be accepted continuously. When the failed Disk Drive is replaced,
the data saved on the Spare Disk is copied to the new Disk Drive.
(a) Dynamic sparing
Errors which occur during ordinary reading/writing operation are controlled for each Disk
Drive. When a number of error occurrences of a Disk Drive exceeds the specified value, data
on the Disk Drive is automatically copied onto the Spare Disk because it is determined that
there exists a risk that a failure (an uncorrectable error) will occur in the Disk Drive. This
function is called a dynamic sparing function.
Disk Drive in which a number of error occurrences has

I/O is acceptable. exceeded the specified value. A, B, Cxxxxx ; data
P ; parity data
Controller
A B C D P C
Disk Drive Disk Drive Disk Drive Disk Drive Disk Drive Spare Disk
Figure 4.6.3 Dynamic Sparing

THEO 04-0220-01
(b) Correction copy

In the subsystem with the RAID 5 configuration, when a failure occurs in a Disk Drive and data
reading/writing from on it cannot be done, the data on the failed Disk Drive is restored using
those on the other data Disk Drives and the parity Disk Drive, and then copied onto the Spare
Disk. In the subsystem with the RAID 1 or RAID 1+0 configuration, when the same situation
as above occurs, data on the mirror Disk Drive is copied onto the Spare Disk. In the RAID 0
configuration, the correction copy cannot be done.
I/O is acceptable
A, B, C xxx ; data
P ; parity data
Controller
A B C D P C
RAID 5 (in the case of 4D+1P)
I/O is acceptable I/O is acceptable
Controller Controller
A A A A A B B B
Disk Drive Disk Drive Spare Disk Disk Drive Disk Drive Disk Drive Disk Drive Spare Disk
RAID 1 RAID 1+0 (in the case of 2D+2D)
Figure 4.6.4 Correction Copy

THEO 04-0230-01
(3) Operation after replacing failed Disk Drive

Operation mode of the Spare Disk can be selected from the two shown below.
Fixed : When the failed drive is replaced, data that was saved in the Spare Disk is copied back
to the new Disk Drive (see Figure 4.6.5).
Variable : Even when the failed Disk Drive is replaced, data that was saved in the Spare Disk is
not copied to the new Disk Drive. The new Disk Drive becomes a new Spare Disk.
Therefore, the copy back-less operation is performed (see Figure 4.6.6).
When a failed Disk Drive is replaced after its data is reconstructed in a Spare Disk by means of
the dynamic sparing or correction copy, this operation restores the storage of the data as it
was before by copying data in the Spare Disk to the replacement Disk Drive.
I/O is acceptable A failed disk drive is replaced A, B, C xxx ; data

P ; parity data
Controller
A B C D P C
Figure 4.6.5 Copy Back
I/O is acceptable The dynamic sparing or correction copy A, B, C xxx ; data

P ; parity data
Controller
A B C D P C
A failed disk drive is replaced

I/O is acceptable
Controller
A B D P C
Disk Drive Disk Drive Spare Disk Disk Drive Disk Drive Disk Drive
Figure 4.6.6 CopyBack Less

THEO 04-0240-01
(4) Method for selecting a Spare Disk

When data is restored to a Spare Drive in the case where two or more Spare Drives are
installed, the Spare Drive is selected according to priorities of the following items.
Priority item Description Degree of priority

Drive type It is judged whether the drive that requires restoration is FC or S-ATA and only a High
drive of the same type is used.
Drive disk speed A drive of the same model as a drive to be restored is used preferentially.
Drive capacity A spare disk with the same capacity as a RAID group to be restored is used Low
preferentially. When a drive with the same capacity does not exist, a drive with the
most approximate and larger capacity is selected preferentially.

THEO 04-0250-01
4.7 Setting RAID Group

You can set the RAID group and RAID level shown below by using the setting function.
(1) RAID level

The range of the RAID levels supported by the DF700 is shown in the table below.
Table 4.7.1 Range of Supported RAID Levels

Supported range
No. RAID level RKM/RKS + Remarks
RKM + RKAJ RKS + RKAJ
RKAJ/RKAJAT
1 RAID 0 2D to 16D 2D to 14D Not supported The stripe size is fixed
2 RAID 1 1D+1D 1D+1D 1D+1D to only 64 k bytes.
3 RAID 5 2D+1P to 15D+1P 2D+1P to 15D+1P 2D+1P to 15D+1P
4 RAID 1+0 2D+2D to 8D+8D 2D+2D to 8D+8D 2D+2D to 8D+8D
(2) Assignment of Disk Drives

Disk drives for a RAID group
When assigning Disk Drives to a RAID group, it is possible to select the Disk Drive to be assigned
optionally.
In the case where the automatic assignment is used, Disk Drives within an extent of a RAID
width (number of Disk Drives in a parity group) RAID depth (number of parity groups) are
assigned in an ascending order of the Disk Drive address number starting from the Specified
Disk Drive and in order of device number.
(2-1) Assignment of optional Disk Drives
Frame #2
(RKAJ/RKAJAT) #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
ROW #2
Frame #1
(RKAJ/RKAJAT) #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
ROW #1
Frame #0
(RKM/RKS) #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
ROW #0
A RAID group can be formed using optional Disk Drives (shown in gray).

THEO 04-0260-01
(2-2) Automatic assignment
Frame #2
(RKAJ/RKAJAT) #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
ROW #2
Frame #1
(RKAJ/RKAJAT) #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
ROW #1
Frame #0
(RKM/RKS) #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
ROW #0
When the automatic assignment is used, Disk Drives are selected in

order of Disk Drive address starting from the specified one.

THEO 04-0270-01
(3) User data area

All the Disk Drives allocated to a RAID group are managed as those having the same capacity
because of the full mapping.
The size of the user data in one Disk Drive is the specified Disk Drive capacity from which the
system area capacity is subtracted and rounded with 0x0800.
Expression:
User data size = ((LAST LBA + 1) - Data portion beginning LBA) & 0xFFFFF800
When the capacity of the Disk Drives installed within the range where the RAID group is
allocated is smaller than the specified Disk Drive capacity, the RAID group cannot be defined.
146 G bytes 300 G bytes 146 G bytes 300 G bytes
Syatem area
User data area
Capacity of the Disk Drive

(LAST LBA) allocated to the
RAID group
Unused area
Figure 4.7.1 User Data Area

THEO 04-0280-01
(4) Image of RAID group definition for each RAID level (RKM/RKS + RKAJ/RKAJAT)
(a) RAID 0 (when connected RKAJAT, RAID 0 is not supported)

In the case of 2D
RG1 RG2
parity group
SP
SP Spare Disk
RG0 RG1
SP
RG0 : Number of the Disk Drive in the parity group = 2

Number of parity groups = 3
In the case of 7D
RG1
parity group
SP SP SP
SP Spare Disk
RG0


THEO 04-0290-01
In the case of 2D to16D

RG4 parity group
SP
SP Spare Disk
RG2 RG3
SP
RG1
SP
RG0
RG0 : 3D Number of the Disk Drive in the parity group =3

RG2 : 16D Number of the Disk Drive in the parity group = 16

THEO 04-0300-01
(b) RAID 1
RG1 RG2 parity group
D D D D SP SP SP D D D D SP SP
SP Spare Disk
RG0
D D D D D D D D D D D D D D


THEO 04-0310-01
(c) RAID 5
In the case of 2D + 1P
RG1 parity group
SP
SP Spare Disk
RG0
SP SP

In the case of 4D + 1P
RG1
parity group
SP SP SP SP SP
SP Spare Disk
RG0


THEO 04-0320-01
In the case of 2D + 1P to 15D + 1P

RG4 parity group
SP
SP Spare Disk
RG3
RG1 RG2
SP SP
RG0
RG0 : 2D + 1P Number of the Disk Drive in the parity group =3

RG1:13D + 1P Number of the Disk Drive in the parity group = 14
Number of parity groups =1
RG2: 5D + 1P Number of the Disk Drive in the parity group =6

THEO 04-0330-01
(d) RAID 1+0

In the case of 2D + 2D
RG1 parity group
D D D D D D D D D D D D D SP SP
SP Spare Disk
RG0
D D D D D D D D D D D D D D D

In the case of 4D + 4D
RG1 parity group
D D D D D D D D D D SP SP SP
D D SP Spare Disk
RG0
D D D D D D D D SP SP SP D D D D

In the case of 2D + 2D to 8D + 8D
RG3 parity group
D D D D D D D D D D SP SP SP SP SP
SP Spare Disk
RG1 RG2
RG0
RG0 : 3D + 3D Number of the Disk Drive in the parity group = 6


THEO 04-0340-01
(e) In the case where RAID levels coexist

RG4(RAID 5) parity group
SP
SP Spare Disk
RG3(RAID 1+0)
D D D D D D SP
RG1(RAID 5) RG2(RAID 0)
SP
RG0(RAID 1)
D D D D D D D D SP SP
RG0 (RAID 1) :1D+1D Number of the Disk Drive in the parity group = 2
RG1 (RAID 5) : 14D + 1P
Number of the Disk Drive in the parity group = 15
RG2 (RAID 0) : 5D
RG3 (RAID 1+0) : 3D + 3D
RG4 (RAID 5) : 11D + 1P

THEO 04-0350-01
Chapter 5. Outline of P.P.

5.1 P.P.s Required for Maintenance
P.P.s included in DF700 required for maintenance are divided mainly into three categories
depending on the related part.
Server for host
d Software based on the

hostSoftware
Fibre
DF700 Server for monitoring

LAN
c Software embedded in e Software for monitoring and
microprogram setting
Figure 5.1.1 P.Ps required for maintenance and its related parts
c Software embedded in microprogram:

Is software embedded in microprogram in DF700. This software will be enabled by
unlocking.
d Software based on the host:

Is software performed and installed on server for host connected to the DF700 with Fibre
Channel interface.
e Monitoring, setting software:

Is software performed and installed on the monitoring server / PC connected to the DF700
with a LAN.
The P.Ps required for maintenance are shown in Table 5.1.1.

THEO 05-0000-01
Table.5.1.1 The P.Ps Required for Maintenance

Related part
Object for
No. Program product Type Basic Host The title of manual
maintenance Monitoring
Microprogram computer
1 Storage Navigator Modular P-002D-J301 e { { y Storage Navigator Modular (for
GUI) Users Guide
2 ShadowImage in-system P-002D-J311 c,d { { y ShadowImage in-system
replication replication Users Guide
(include RAID Manager) y Command Control Interface (CCI)
User and Reference Guide
3 TrueCopy remote P-002D-J312 c,d { { y TrueCopy remote replication
replication Users Guide
4 Copy-on-write SnapShot P-002D-J310 c,d { { y Copy-on-write SnapShot Users
(include RAID Manager) Guide
y Command Control Interface (CCI)
5 Data Retention Utility P-002D-J309 c,d { { y Data Retention Utility Users
6 LUN Manager P-002D-J308 c { y LUN Manager Users Guide
7 Cache Residency P-002D-J305 c { y Cache Residency Manager
Manager Users Guide
8 SNMP Agent Support P-002D-J303 c { y SNMP Agent Support Function
Function Users Guide
9 LUN Expansion P-002D-J304 c { y LUN Expansion Function Users
Guide
10 Password Protection P-002D-J302 c { y Password Protection Users
Guide
11 Performance Monitor P-002D-J306 c { y Performance Monitor Users
Guide
12 Cache Partition Manager P-002D-J307 c { y Cache Partition Manager Users
Guide

THEO 05-0010-01
FE-95DF746-00
Installation
Chapter 1. Before Starting Installation Work.................................................................... INST 01-0000
Chapter 2. Installing Floor Model ..................................................................................... INST 02-0000
Chapter 3. Installing Rackmount Model ........................................................................... INST 03-0000

INST 00-0000-01

INST 00-0010-01
Chapter 1. Before Starting Installation Work

1.1 Before Starting Installation Work
Take notice of the following when performing a installation work for the subsystem. Read
and understand them well before performing the installation.
(1) Note on installing and removing parts

Generally, each part is equipped with high-precision components. Remove and install the part
gently so as not to give it any shock.
CAUTION
y To prevent part failures caused by static electrical charge built up on your own
body, be sure to wear a wrist strap connected to the chassis before starting
(before removing bezel) and do not take it off until you finish.
y Be sure to wear a wrist strap connected to the chassis whenever you unpack
parts from a case. Otherwise, the static electrical charge on your body may
damage the parts.
y When you install are Disk Drive, Control Unit and ENC Unit/SENC Unit, support
its metal part with your hand that has the wrist strap. You can discharge static
electricity by touching the metal plate.
Be sure to wear the wristband, connect its lead wire to the subsystem enclosure before starting
the work, and do not remove them until the work is completed.
When installing a Disk Drive, Control Unit and ENC Unit/SENC Unit, hold it with your hand
wearing the wristband having fingers contact metallic portions on the sides of the part.
Support a Disk Drive by touching its metal ENC Unit (RKAJ)/

part (metal plate) with your fingers SENC Unit (RKAJAT)
Disk Drive

Connect this to the metal part on A wristband (Be sure to wear this before
the frame of subsystem (rear starting maintenance.)
face)

INST 01-0000-01
(2) Note on cable routing

(a) Handling of cables on the floor
Protect cables which cannot be accommodated by the subsystem and thus laid on the floor
or cables which cross a passage with cable protecting, etc.
Do not make inter-device cables apart from the floor but lay them on the floor.
(b) Handling of under-floor cables when the subsystem is installed on the free access floor.
Give excess lengths to cables routed under the floor so that they can easily be laid on the
slab. Do not make them to be hung dangling.
(c) How to route cables
Give adequate margin of length to cables to withstand earthquakes, etc.
Route cables giving them excess lengths lest they should disturb replacement of part to be
done for maintenance.
Make power cable and power cable apart each other. When they have to be positioned
close each other, do not make them run in parallel but make them cross each other.
When using cable protecting duct, be careful not to damage or break cables by catching
them.
(d) Be sure to insert or pull out a cable connector holding it with your hand. If you pull a cable,
a trouble may be caused.
(e) When bending the FC I/F cable and RC (ENC) cable to connect it, give it a bend with a long
radius (not less than 30 mm) so as not to apply the cable and the connector excessive
stresses.
(3) Note on restarting

When restarting the subsystem, turn on the main switch after waiting more than one minute
after the main switch is turned off (after the POWER LED goes out).
(4) Note on completing a maintenance work

Close all the external covers when a maintenance work is completed.
It is required to make all the external covers closed to operate the subsystem properly.
(Be sure to close all the external covers during operation because it is indispensable to
maintain the performance of the subsystem including prevention of adverse effects caused by
radio frequency energy.)
(5) Note on moving the Floor Model

The allowable maximum inclination angle at the end of the slope for the Floor Model is eight
degrees.
When moving the Floor Model through a slope steeper than the above or across a level
difference of the floor, use a gangway, etc. to make the slope easier.
Floor model
Slope easier
8degrees

INST 01-0010-01
1.2 Fibre Channel Interface

1.2.1 Restrictions on Using the Fibre Channel Interface
When using a 2G bps Fibre Channel Interface board as 1G bps mode, the GBIC used in the
target connection (HUB/Sw) has the following restrictions. Otherwise, a Linkup malfunction
may occur.
Restrictions:
(1) Vixel CD Laser is not supported. However, Vixel GBIC (VCSEL) is supported.
CD Laser or VCSEL is identified by first digit of the serial number.
[CD Laser] : 3****, 4****
[VCSEL] : 7**** or later
(2) Point to Point topology with 1G bps Qlogic X6729A or X6730A is not supported.
(3) Point to Point with Sun default 1G bps Fibre Channel Host Bus Adapter Board (Qlogic OEM
product (X6929A/X6730A) which were mentioned (2)) is not supported.
1.2.2 Mini-HUB
The host interface of RKS has Mini-HUB in the Control Unit, and enhances one port to two host
connectors.
Port A Port B
Port A
Port
Mini-HUB
Mini-HUB
Host Connector
Port A-0 Port B-0
Port A-0 Port A-1
FC Connector of RKM FC Connector of RKS

INST 01-0020-01
1.2.3 Connection Specifications of RKS

The host connector that can be used is different from the topology setting of RKS and the
connection method. The following table shows available host connector of each topology
setting and connection method.
Table 1.2.1 Available Host Connector of each topology setting and connection method
Direct Connection of
SANRISE UPS (*1)
No. Topology of RKS Transfer speed of RKS Direct Connection of Host Switch Connection
Direct Connection of
SANRISE 9900V
1 Loop Auto Host Connector#0 Not Support Host Connector#0
2 1Gbps/2Gbps Host Connector#0 and #1
3 Point-to-Point Auto/1Gbps/2Gbps Not Support Host Connector#0 Not Support
*1 SANRISE USP:It is the abbreviation of SANRISE Universal Storage Platform, and a high-ranking model of
the SANRISE series.
When connecting directly to the host, the Loop topology is set to port.
y Connect it to the host connector 0 side, when transfer speed of RKS is Auto (do not connect
it to the host connector 1 side).
y Both host connector 0 and 1 is available, when transfer speed of RKS is 1Gbps or 2Gbps.
y Port that set the Point-to-Point topology cannot be connected directly to the host, SANRISE
USP or SANRISE 9900V.
When connecting it to Switch, the Point-to-Point topology is set to port.
y Connect it to the host connector 0 side (do not connect it to the host connector 1 side).
y Port that set the Loop topology cannot be connected to Switch.
When connecting directly to SANRISE USP or SANRISE 9900V, the Loop topology is set to port.
y Connect it to the host connector 0 side (do not connect it to the host connector 1 side).
y Port that set the Point-to-Point topology cannot be connected to SANRISE USP or SANRISE
9900V.
1.2.4 Fibre Channel Configuration of RKS

The following Fibre Channel information is set to the port not to the host connector.
- Port Address
- Topology
- Transfer Rate
- Adding Host Group
- Host Group Options
- LU Mapping Information
1.2.5 Attention of Host Directly Connection for RKS

Read the following guideline, when connecting both host connectors to the host directly with
the Loop topology.
- Exclusive Access of LU
Each host connector of RKS cannot be set LU mapping. It is necessary to set the access path
between hosts and LUs according to the assignment of the LUs to the hosts using LUN Manager.
- Transfer Speed of Host
Transfer speed of RKS is set to the port. It is necessary to set the same transfer speed both
host connectors.

INST 01-0030-01
1.3 Model Name

1.3.1 Components and indispensable parts
Table 1.3.1 Components and indispensable parts (SANRISE AMS500 (Adaptable Modular Storage))
No. Name Model Components

1 RKM DF700-RKM Frame (1), Control unit (1), Panel (1), Backup battery unit (2), Fan
assembly (2), AC cable J2H (2), Power unit (RKM) (2)
2 RKAJ DF700-RKAJ Frame (1), AC cable J2H (2), Power unit (RKAJ) (2), ENC unit (2),
Connection cable for basic subsystem or added subsystem (4)
3 RKAJAT DF700-RKAJAT Frame (1), AC cable J2H (2), Power unit (RKAJAT) (2), SENC unit (2),
ENC cable (2), connection cable for basic subsystem or added
subsystem (2)
4 Floor (RKM+H1J) Model DF700-RKM+ RKM (1), Floor setting kit H1J (1), Control unit (1), Panel (1), Power unit
DF-F700-H1J (RKM) (2), Backup battery unit (2), Fan assembly (2), AC cable J1H (2)
5 Floor (RKM+RKAJ+H2J) DF700-RKM+ RKM (1), RKAJ (1), Floor setting kit H2J (1), Control unit (1), Panel (1),
Model DF700-RKAJ+ Power unit (RKM) (2), Power unit (RKAJ) (2), Backup battery unit (2),
DF-F700-H2J Fan assembly (2), ENC unit (2), Connection cable for basic subsystem
(4), AC cable J1H (4)
6 Cache memory DF-F700-C1GJ Cache memory of 1,024 M bytes
7 Interface Board DF-F700-DJ4G2 4Gbps Fibre Channel Interface (including Host Connector (2))
8 Disk Drive(*1) DF-F700-AGF72 3.5-type Disk drive (71.3 G bytes) installed in a canister.
(Disk rotational speed: 10,000 min-1)
DF-F700-AGF146 3.5-type Disk drive (143.3 G bytes) installed in a canister.
DF-F700-ATE250R 3.5-type Disk drive (245.7 G bytes) installed in a canister.
*1 : This values of storage capacity are calculated as 1 G bytes = 1,000,000,000 bytes.

INST 01-0040-01
Table 1.3.2 Components and indispensable parts (SANRISE AMS200 (Adaptable Modular Storage))
No. Name Model Components

1 RKS DF700-RKS Frame (1), Control unit (including 2 G bytes Host Connector (2)) (1),
Panel (1), Backup battery unit (1), Fan assembly (2), AC cable J2H (2),
Power unit (RKS) (2)
2 RKAJ DF700-RKAJ Frame (1), AC cable J2H (2), Power unit (RKAJ) (2), ENC unit (2),
Connection cable for basic subsystem or added subsystem (4)
3 RKAJAT DF700-RKAJAT Frame (1), AC cable J2H (2), Power unit (RKAJAT) (2), SENC unit (2),
ENC cable (2), connection cable for basic subsystem or added
subsystem (2)
4 Floor (RKS+H1J) Model DF700-RKS+ RKS (1), Floor setting kit H1J (1), Control unit (including 2 G bytes Host
DF-F700-H1J Connector (2)) (1), Panel (1), Power unit (RKS) (2), Backup battery unit
(1), Fan assembly (2), AC cable J1H (2)
5 Floor (RKS+RKAJ+H2J) DF700-RKS+ RKS (1), RKAJ (1), Floor setting kit H2J (1), Control unit (including 2 G
Model DF700-RKAJ+ bytes Host Connector (2)) (1), Panel (1), Power unit (RKM) (2), Power
DF-F700-H2J unit (RKAJ) (2), Backup battery unit (1), Fan assembly (2), ENC unit (2),
connection cable for basic subsystem (4), AC cable J1H (4)
6 Cache memory DF-F700-C1GJ Cache memory of 1,024 M bytes
7 Disk Drive(*1) DF-F700-AGF72 3.5-type Disk drive (71.3 G bytes) installed in a canister.
*1 : This values of storage capacity are calculated as 1 G bytes = 1,000,000,000 bytes.

INST 01-0050-01
1.3.2 Optional parts

Table 1.3.3 Optional Parts
No. Classification Model Name Specification
1 Spare Disk Drive - Disk Drive Name : Refer to the column of the Disk Drive.
2 Controller DF-F700-F1JM Controller (RKM) Array Control Unit for duplication, Software P.P.
- Cache Unit Name : Refer to the column of the Cache Unit.
DF-F700-F1JS Controller (RKS) Array Control Unit for duplication, Software P.P.
(Fibre I/F (2) is standard installation.)
Cache memory of 1,024 M bytes (1),
- Cache Unit Name : Refer to the column of the Cache Unit.
3 Floor setting kit DF-F700-H1J Floor setting kit for RKM/RKS Floor setting kit
DF-F700-H2J Floor setting kit for Floor setting kit (for RKM+RKAJ or RKS+RKAJ )
RKM+RKAJ/ RKS+RKAJ
4 Disk Drive for addition - Disk Drive Name : Refer to the column of the Disk Drive.
(RKM/RKS/RKAJ/ RKAJAT)
5 Interface Board for addition DF-F700-DJ4G2 Interface Board Name : Refer to the column of the Interface
(RKM) Board.
6 Rack frame DF-F700-U7 Rack frame Rack frame
7 PDB DF-F700-UPDU7 PDB Power distribution box for U7 rack.
PDB (2), Bracket (4), Cable clamp (2)
8 Remote adapter DF-F700-VR4A Remote adapter Adapter for PS interlock control
(Main unit) (Power cables for 100V and 200V each are
standard equipment)
DF-F700-VR4H Remote adapter Hub for remote adapter
(Hub) (Power cables for 100V and 200V each are
standard equipment)

INST 01-0060-01
1.3.3 Accessory parts

Table 1.3.4 Accessory Parts
No. Classification Model Name Specification
1 Power cable(*1) DF-F700-J1H Power cable 2.5 m, 2-pole power cable with grounding terminal
(AC 125 V, 13 A or 15 A)
DF-F700-J2H Power cable 2.5 m, 2-pole power cable with grounding terminal
(AC 250 V, 13 A or 15 A)
DF-F700-J2H5 Power cable 5.0 m, 2-pole power cable with grounding terminal
(AC 200 V, 13 A or 15 A)
DF-F700-J2H10 Power cable 10.0 m, 2-pole power cable with grounding terminal
(AC 200 V, 13 A or 15 A)
2 Fibre channel DF-F700-KB5M SC-LC Fibre I/F Cable SC-LC Fibre I/F cable for Optical (5 m)
interface cable DF-F700-KB10M SC-LC Fibre I/F Cable SC-LC Fibre I/F cable for Optical (10 m)
DF-F700-KB20M SC-LC Fibre I/F Cable SC-LC Fibre I/F cable for Optical (20 m)
DF-F700-KB50M SC-LC Fibre I/F Cable SC-LC Fibre I/F cable for Optical (50 m)
DF-F700-KB1HM SC-LC Fibre I/F Cable SC-LC Fibre I/F cable for Optical (100 m)
DF-F700-KC5M LC-LC Fibre I/F Cable LC-LC Fibre I/F cable for Optical (5 m)
DF-F700-KC1HM LC-LC Fibre I/F Cable LC-LC Fibre I/F cable for Optical (100 m)
3 Remote adapter DF-F700-VRC2 Remote adapter cable For control of Remote adapter, 2 m
cable DF-F700-VRC5 Remote adapter cable For control of Remote adapter, 5 m
DF-F700-VRC10 Remote adapter cable For control of Remote adapter, 10 m
4 Tray for remote adapter DF-F700-HVR4 Tray for remote adapter Rail kit for mounting the Remote adapter on the U7
rack frame.
5 FC cable assembly for DF-F700-K5B FC cable assembly FC cable 5 m (2)
2 G bps
6 Decoration panel DF-F700-U71D Decoration panel Panel to cover vacant space (1 EIA) of the U7 rack
frame.

INST 01-0070-01
1.4 Installation Configuration of the Subsystem

There are two models of the DF700, floor model and rack-mount model, which are classified
according to their installation forms. The former includes combinations of the RKM/RKS,
RKAJ, and the Floor Standing Kit and a combination of the RKM/RKS and the Floor Standing Kit
and the latter includes combinations of the RKM/RKS and RKAJ mounted on the 19-inch rack
frame.
There are three types of the floor model: an RKM alone, an RKM/RKS added with an RKAJ, and
an RKS alone.
The rackmount model uses the special U7 rack frame and it can connect up to 10 RKAJ (up to
180 Disk Drives) to an RKM. A subsystem with the two U7 rack frames containing up to 14
RKAJs (up to 225 Disk Drives) can be configured. It can connect up to 6 RKAJ (up to 105 Disk
Drives) to an RKS.
A mixed configuration, in which up to the 14 RKAJ(s)/RKAJAT(s) in total (up to the 225 Disk
Drives) are connected to the one RKM, can be formed.
A mixed configuration, in which up to the 6 RKAJ(s)/RKAJAT(s) in total (up to the 60 Disk
Drives) are connected to the one RKS, can be formed.
Floor model
RKM
(4 U (EIA unit))
RKM+H1J RKM/RKS+RKAJ+H2J RKS+H1J

(one RKM) (one RKM/RKS + one RKAJ) (one RKS)
RKAJ
(4 U (EIA unit))
RKS
(3 U (EIA unit))
Any combination can be mounted as long as it
Rackmount model requires a height less than 38 EIA units.
y However, be sure to mount at least the one
RKM.
y RKS is mounted on each rack frame individually.
y An RKM can be connected to 14 RKAJs at the
maximum.
y An RKS can be connected to 6 RKAJs at the
maximum.
U7 rack model Minimum configuration Maximum configuration

(one RKM/RKS) (one RKM and ten RKAJs)
Figure 1.4.1 Subsystem Configuration (RKM/RKS+RKAJ)

INST 01-0080-01
RKM
(4 U (EIA unit))
U7 rack model
RKS
(4 U (EIA unit))
Any combination can be mounted as long as

RKAJ it requires a height less than 38 EIA units.
(3 U (EIA unit)) y An RKM can be connected to 14
RKAJs/RKAJATs at the maximum.
y An RKS can be connected to 6
RKAJs/RKAJATs at the maximum.
RKAJAT Minimum configuration Maximum configuration

(3 U (EIA unit)) (one RKM/RKM) (one RKM and 14 RKAJs/RKAJATs)
Rackmount model
Figure 1.4.2.1 Subsystem Configuration (RKM+RKAJ/RKAJAT)

INST 01-0090-01
1.5 How to Open/Close Door or Attach/Remove Front Bezel/Rear Cover of the Subsystem
1.5.1 How to attach/remove Front Bezel of Floor Model
CAUTION
Attach or remove the Front Bezel carefully following the procedure. Otherwise,
you may hurt your fingers by pinching them.
CAUTION
y Since front bezels of the RKM/RKS and the RKAJ are different with each other in
their size.
A key is necessary to attach or remove the Front Bezel.
(1) Procedure for removal

(a) Insert the key into the keyhole on the Front Bezel and release the Lock of the Front Bezel.
(b) Pull the Front Bezel toward you holding its sides to disengage it from the ball catches.
(c) Disengage the two hooks of the Front Bezel from the slots on the subsystem main body by
shifting the bezel to the left and remove the bezel.
(2) Procedure for attachment

(a) Hold the side of front bezel with your both hands.
(b) Engage two hooks of the Front Bezel with the slots on the right side of the subsystem main
body.
(c) After making the hooks of the front bezel engaged, press the bezel against the main body
until it is stopped.
(d) Fix the front bezel by turning the key.

INST 01-0100-01
Ball catches
The state in which the slit of the

keyhole is aligned with the mark.
To lock
(The key can be inserted or pulled Key
out in this state.)
To unlock
Hook
Front bezel
Keyhole
The floor (RKM+RKAJ+H2J) model is shown as an example.
Figure 1.5.1 Procedure for Attaching/Removing Front Bezel
NOTE : y When inserting and turning the key, have it inserted completely. If it is
turned when it is inserted half way, a damage of it may be caused.
Locking Pull the key off aligning its groove with the
Key positioning mark on the lock. (The key can
be inserted or pulled off in this state.)
The key cannot be pulled off when its

groove is not aligned with the positioning
Unlocking mark on the lock.
y When removing the key after locking up the Front Bezel, pull it off aligning its
groove with the positioning mark on the lock.
When the key is pulled off in the state where its groove is not aligned with the
positioning mark on the lock, a damage of the lock may be caused.

INST 01-0110-01
1.5.2 How to attach/remove Rear Cover of Floor Model
CAUTION
y Attach or remove the Rear Cover carefully following the procedure. Otherwise,
y Do not lean against the rear cover. The cover comes off, and it causes the
injury.

(a) Hold the rear cover with your both hands.
(b) When you disengage the rear cover from a ball catch by pulling the upper part of it toward
you, you can remove the rear cover.
NOTE : When installing Rear Cover, be careful not to catch cables.
(a) Hold the rear cover with your both hands.

(b) Hang the hook under the rear cover.
(c) Fasten the rear cover by pressing it against the ball catch at the upper part of the subsystem
main body.
Ball catches Ball catches
Rear cover
Rear cover
Hook
Hanging
Hook Hanging
(a) Floor (RKM+H1J) Model / Floor (RKS+H1J) Model (b) Floor (RKM+RKAJ+H2J) Model
Figure 1.5.2 Procedure for Attaching/Removing Rear Cover

INST 01-0120-01
1.5.3 How to attach/remove Front Bezel of the Rackmount Model
CAUTION
Attach or remove the Front Bezel carefully following the procedure. Otherwise,
CAUTION
y Since front bezels of the RKM/RKS and the RKAJ/RKAJAT are different with each
other in their size.
A key is necessary to attach or remove the Front Bezel.

(a) Insert the key into the keyhole on the Front Bezel and release the Lock of the Front Bezel.
(b) Pull the front bezel toward you holding its sides to disengage it from the ball catches.
(c) Disengage the two hooks of the front bezel from the slots on the subsystem main body by
shifting the bezel to the right and remove the bezel.

(a) Hold the side of Front Bezel with your both hands.
(b) Engage two hooks of the front bezel with the slots on the right side of the subsystem main
body.
(c) After making the hooks of the front bezel engaged, press the bezel against the main body
until it is stopped.
(d) Fix the front bezel by turning the key.

INST 01-0130-01
The RKM/RKS is shown as an example.

Front Bezel
Ball catches

Key Hook
To lock
Keyhole The state in which the slit of the keyhole is

aligned with the mark.
To unlock (The key can be inserted or pulled out in this
state.)
Figure 1.5.3 Procedure for Attaching/Removing Front Bezel
NOTE : y When inserting and turning the key, have it inserted completely. If it is
turned when it is inserted half way, a damage of it may be caused.
Locking Pull the key off aligning its groove with the
Key positioning mark on the lock. (The key can
be inserted or pulled off in this state.)
The key cannot be pulled off when its

groove is not aligned with the positioning
Unlocking mark on the lock.
y When removing the key after locking up the Front Bezel, pull it off aligning its
groove with the positioning mark on the lock.
y When the key is pulled off in the state where its groove is not aligned with the
positioning mark on the lock, a damage of the lock may be caused.

INST 01-0140-01
1.5.4 How to open/close the Rear Door of U7 rack frame
CAUTION
Open or close the door carefully following the procedure.
Otherwise, you may hurt you fingers by pinching them.
For the procedure for removing and installing the Font Bezel, refer to 1.5 How to
Open/Close Door or Attach/Remove Front Bezel/Rear Cover of the Subsystem (INST 01-0100).
(1) Fit an Allen wrench in the key socket on the rear door, turn the Allen wrench in the direction
shown by the arrow (), and open the rear door slowly leaving the wrench as it is.
(2) To close the rear door, fit the Allen wrench in the key socket on the door, turn the wrench in
the direction shown by the arrow (), press the door against the main body leaving the
wrench as it is, and then turn the wrench in the direction shown by the arrow (>) to
return it to its original state.
(3) Make sure that the rear door is latched and cannot be opened.
Latch
U7 rack frame
Front bezel
Allen wrench
To close
To open
Rear door
The case where one RKM/RKS and ten RKAJs are mounted
is shown as an example.
Figure 1.5.4 Procedure for Opening/Closing Rear Door

INST 01-0150-01
1.6 Device ID Setting and ENC Cable Connection

Set the specified device ID and connect the ENC cable by executing the ACE tool of Storage
Navigator Modular. When an error message is displayed during operation of the ACE Tool,
take recovery actions referring to Message Chapter 10. ACE Tool Error Message (MSG 10-
0000).
1.6.1 Example of device ID and ENC cable connection

(1) For RKM+RKAJ
RKAJ (9)
Unit ID:10
Device ID:0A
RKAJ (8)
Unit ID:9
Device ID:09
RKAJ (7)
Unit ID:8
Device ID:08
RKAJ (6)
Unit ID:7
Device ID:07
RKAJ (5)
Unit ID:6
Device ID:06
RKAJ (4)
Unit ID:5
Device ID:05
RKAJ (3)
Unit ID:4
Device ID:04
RKAJ (2)
Unit ID:3 RKAJ (13)
Device ID:03 Unit ID:14
Device ID:0E
RKAJ (1)
Unit ID:2 RKAJ (12)
Device ID:0D
RKAJ (0)
Unit ID:1 RKAJ (11)
Device ID:0C
RKM RKAJ (10)

Unit ID:0 Unit ID:11
Device ID:00 Device ID:0B
Figure 1.6.1 Example of RKM+RKAJ ENC cable connection (The figure shows an example in which the
maximum configuration is installed in the U7 rack frame.)
Unit ID Device ID Unit ID Device ID Unit ID Device ID Unit ID Device ID

1st #0 #00 5th #4 #04 9th #8 #08 13th #12 #0C
2nd #1 #01 6th #5 #05 10th #9 #09 14th #13 #0D
3rd #2 #02 7th #6 #06 11th #10 #0A 15th #14 #0E

INST 01-0160-01
4th #3 #03 8th #7 #07 12th #11 #0B

INST 01-0160-01
(2) For RKM+RKAJ+RKAJAT
RKAJAT (8)
Unit ID:10
Device ID:2A
RKAJAT (7)
Unit ID:9
Device ID:39
RKAJAT (6)
Unit ID:8
Device ID:28
RKAJAT (5)
Unit ID:7
Device ID:37
RKAJAT (4)
Unit ID:6
Device ID:26
RKAJAT (3)
Unit ID:5
Device ID:35
RKAJAT (2)
Unit ID:4
Device ID:24
RKAJAT (1)
Unit ID:3 RKAJ (1)
Device ID:0E
RKAJAT (0)
Unit ID:2 RKAJAT (11)
Device ID:3D
RKAJ (0)
Unit ID:1 RKAJAT (10)
Device ID:2C
RKM RKAJAT (9)

Unit ID:0 Unit ID:11
Device ID:00 Device ID:3B
Figure 1.6.2 Example of RKM+RKAJ+RKAJAT ENC cable connection (The figure shows an example in
which the maximum configuration is installed in the U7 rack frame.)
Unit ID Device ID Unit ID Device ID Unit ID Device ID Unit ID Device ID

1st #0 #00 5th #4 #24 9th #8 #28 13th #12 #2C
2nd #1 #01 6th #5 #35 10th #9 #39 14th #13 #3D
3rd #2 #22 7th #6 #26 11th #10 #2A 15th #14 #0E
4th #3 #33 8th #7 #37 12th #11 #3B

INST 01-0170-01
1.6.2 Checking methods of device ID and ENC cable connection when mounting the newly
introduced rack
(1) Start Storage Navigator Modular and select [Tool] and [ACE Tool] in this order in the main
window. The ACE Tool is started and a window for selecting a subsystem is displayed.
(2) Select the subsystem, and click the [OK] button.
NOTE : When selecting a subsystemin (1), this dialog is not displayed.

INST 01-0180-01
(3) Set the subsystem to be configured in the frame part of the Physical.
Click the [Edit] button in the Physical part.
(a) (c)
(b) (d)
(e)
(g)
(f)
(h) (i) (j) (k) (l) (m)
(a) [Logical] : The device ID can be checked per Path.

(b) [Edit in Logical] button : The chassis frame in Logical can be edited manually. If [Create] button is selected
after the setting, the subsystem and the device ID are displayed in the Logical part
and the Physical part.
(c) [Physical] : The device ID can be checked per Rack.
(d) [Edit in Physical] button : The chassis frame in Physical can be edited manually. If [Create] button is selected
after the setting, the subsystem and the device ID are displayed in the Logical part
and the Physical part.
(e) [Single, Dual in Physical] button : It selects the installation configuration of the Control Unit.
(f) [Max number of disk units] button : The maximum number of chassis frames per Rack can be specified.
(g) [Cable figure] button : The ENC cable connection figure is displayed.
(h) [Load] button : The configuration figure can be read.
( i ) [Save] button : The configuration figure can be stored in files.
( j ) [Base] button : The chassis frame type and the device ID are displayed automatically in the Logical part and
the Physical part.
(k) [Clear] button : The subsystem and the device ID, which have been set, are cleared.
( l ) [Create] button : The name and ID number of the subsystem are displayed in the Logical part and Physical
part.
(m) [End] button : It returns to the device model selection window.
(4) Click the [OK] button.

INST 01-0190-01
(5) If the chassis frame section the Physical part is clicked, the Unit Select window is displayed.
Select RKAJ (Fibre), RKAJAT (SATA) or Empty and input the configuration.
Check that the actual rack mounting position and the Physical part are the same.
Physical part
Frame type selection window
(6) Click the [Create] button.

INST 01-0200-01
(7) The device ID# is output in the Logical part and the Physical part window.
(8) Click the [Cable figure] button.
(9) The ENC cable connection diagram is displayed.

Refer to the ENC cable connection figure, and perform the ENC cable connection.

INST 01-0210-01
(a) When Path 0 is selected, the Path 0 is highlighted and the disk units connected to its lines are
displayed in white.
When the each [Path] button is clicked, the displayed lines connected to the path are
highlighted, disk units connected to the lines are displayed in white, and disk units not
connected to the lines are displayed in gray.
To cancel the highlighting, click the [Standard] button.
The explanations of the buttons are shown below.

(viii) (ix) (x)(xi) (xii)(xiii)
(i) (ii) (iii) (iv)(v) (iii) (vi)(vii)

[Explanation of each button]
[Standard] button : It returns the window line to the initial status (the highlighting is
cancelled).
[Path0] button : The line connected to Path0 is highlighted.
[Path1] button : The line connected to Path1 is highlighted.
[Path2] button : The line connected to Path2 is highlighted (it is not displayed in the
700M (RKM)).
[Path3] button : The line connected to Path3 is highlighted (it is not displayed in the
700M (RKM)).
[Path0/2] button : The lines connected to Path0 and Path2 are highlighted (Path2 does
not exist in the 700M (RKM)).
[Path1/3] button : The lines connected to Path1 and Path3 are highlighted (Path3 does
not exist in the 700M (RKM)).
[Loop0] button : The line connected to Loop0 is highlighted.
[Loop1] button : The line connected to Loop1 is highlighted.

INST 01-0220-01
[Explanation of the window display]

(i ) The number of ENC cables of Path0 is displayed.
(ii) The number of ENC cables of Path1 is displayed.
(iii) The color of the binders attached to both ends of the ENC cable is displayed.
(iv) The number of ENC cables of Path0 is displayed.
(v) The number of ENC cables (long ENC cables) between the racks of Path0 is displayed.
(vi) The number of ENC cables of Path1 is displayed.
(vii) The number of ENC cables (long ENC cables) between the racks of Path1 is displayed.
(viii) The number of ENC cables of Loop0 is displayed.
(ix) The number of ENC cables of Loop1 is displayed.
(x) The number of the cables of the Path 0 connected to the selected disk unit or that of
the Path 0 connected to the additional disk unit is displayed.
(xi) The number of the inter-rack cables (long ENC cables) of the Path 0 connected to the
selected disk unit or that of the Path 0 connected to the additional disk unit is displayed.
(xii) The number of the cables of the Path 1 connected to the selected disk unit or that of
the Path 1 connected to the additional disk unit is displayed.
(xiii) The number of the inter-rack cables (long ENC cables) of the Path 1 connected to the
selected disk unit or that of the Path 1 connected to the additional disk unit is displayed.
(b) When [RKAJ(Fibre) #03] is selected, the [RKAJ(Fibre) #03] disk unit is displayed in orange and
disk units connected to the [RKAJ(Fibre) #03] disk unit are displayed in white.
Besides, the displayed ENC cables connected to the [RKAJ(Fibre) #03] disk unit are
highlighted.
To cancel the selection of the disk unit, click the [Standard] button.

INST 01-0230-01
(c) When [RKAJ(Fibre) #03] is selected and [RKAJAT(SATA) #27] is clicked while the control [Ctrl]
key is pressed, the chassis frame connected to the [RKAJ(Fibre) #03 and RKAJAT(SATA) #27]
chassis frame is displayed in white. Also, the connecting ENC cable from the [RKAJ(Fibre)
#03 and RKAJAT(SATA) #27] chassis frame is highlighted.
Any of the following methods is able to cancel the selection of two or more chassis frames.
c Click the selected chassis frame again while the control [Ctrl] key is pressed.
d Click the [Standard] button.
e Click another chassis frame while the control [Ctrl] key is not pressed.
(10) Click the [End] button in the ENC cable connection figure.
It returns to the Configuration window.
(11) Click the [End] button.

INST 01-0240-01
1.6.3 Procedure for making the configuration diagram when adding the disk unit(s)
When adding the disk unit(s) to the subsystem already installed, you can display the
configuration of the existing subsystem using the following procedure in addition to the
procedure explained above. The procedure is to get the configuration information with the
configuration copying function of Storage Navigator Modular and to have the file read.
c Set up the specified device ID and connect the ENC cable by executing the ACE tool.
d If error messages are displayed during the operation, refer to Message Chapter 10. ACE
Tool Error Message (MSG 10-0000) and perform the recovery method.
(1) Start the Storage Navigator Modular and set the Active Mode in the Maintenance Mode.
For the procedure for changing to the Maintenance mode, refer to System Parameter 1.1
(3)(b) Changing the Maintenance Mode (SYSPR 01-0050).
(2) Click an icon of the disk array subsystem you want to set in the main window.
There are three ways of the setting as shown below.
y Selecting [File] [Open]
y Double-clicking an icon of the disk array subsystem you want to set
y Clicking [ : Open]

INST 01-0250-01
(3) Select [Tools] [Configuration Settings] in the unit window or click [ : Configuration
Settings] in the tool bar.
(4) Click the [Constitute] tab.

Get the configuration information by selecting [Parts Information].
(5) Select [Tool] and [ACE Tool] in this order in the main window.
The ACE tool starts up and the Array Unit Type window is displayed.

INST 01-0260-01
(6) Select the subsystem, and click the [File input] button.
(7) Have the file that has been got in Step (4) read.
(8) Enter the number of the disk units in each of the Rack boxes according to the actual state in
which the disk units are installed. When the rack is not specified, the entries are made in
regular order starting from Rack 1.

INST 01-0270-01
(10) The device ID numbers are displayed in the Logical part and Physical part.
The post-addition configuration can be derived from the diagrams above.

For the creation procedure, refer to 1.6.2 (3) Set the subsystem to be configured in the
frame part of the Physical. (INST 01-0190) and add the chassis frame to be added by the
connection tool and perform the specified device ID and ENC cable connection.

INST 01-0280-01
1.7 Power On/Off Procedure

The Disk Drive may emit mechanical sound, click-clack, when the Disk Drive is started (spun
up) immediately after the subsystem powering on and when the Disk Drive is powered off
(spun down). However, since it does not mean a problem as long as the WARNING or ALARM
LED of the basic subsystem is off, please use the subsystem as it is.
1.7.1 Subsystem power on

(1) In the case of Floor model, make sure that the AC Power Unit Switch of the Power Unit is
turned off.
In the case of Rackmount model, make sure that the circuit breaker is turned off.
(2) Make sure that the main switch is turned off.
(3) All turn on the battery switch of the Backup Battery Unit on the front of the subsystem.
(4) In the case of Rackmount model, turn on the circuit breaker of the PDB.
(5) Turn on the AC Power Unit Switch of the Power Unit. (1)
(6) Turn on the main switch.
(7) Make sure that the RDY LED (green) comes on about four minutes later normally.
However, when it is blinking at high speed, it blinks up to 30/50 minutes because the
ENC/SENC firmware is being downloaded.
If the ALARM LED (red) or WARN LED (orange) comes on, refer to Troubleshooting 8.1 Trouble
Analysis by LED Indication of Front Bezel (TRBL 08-0000).
NOTE : The EALM LED (red) on the Control Unit (on the rear side of the subsystem) may
come on after powering on the subsystem. However, it is not a problem if the
EALM LED (red) goes out until the RDY LED (green) comes on.
Battery switch Main switch AC Power Unit Switch
PWR LED
(Green)
RDY LED
(Green)
WARN LED
(Orange)
Backup Battery Unit(*1)
WARN LED
(Orange)
ALARM LED
(Red)
Power Unit Power Unit
(RKM) (RKAJ)
RKAJ (Front) RKM/RKS (Front) RKM/RKS (Rear) RKAJ (Rear)

*1 : There is only one Backup Battery Unit to be installed in the RKS and install it in the lower side of the subsystem.
Figure 1.7.1 Location of Switches for Power On (Floor model)
1 : When Disk Drives are not installed on the additional Disk Drive, shut off the power to the Power Unit (RKAJ).

INST 01-0290-01
PDB
ALARM LED WARN LED RDY LED PWR LED
(Red) (Orange) (Green) (Green)
Power Unit
(RKAJ/RKAJAT)
Backup Battery Unit(*1)
Backup Battery switch Main switch AC Power Unit Switch Power Unit (RKM)
Circuit breaker (CB1)
*1 : There is only one Backup Battery Unit to be installed in the RKS and install it in the left side of the subsystem.
Figure 1.7.2 Locations of Switches for Power On (Rackmount model)

INST 01-0300-01
1.7.2 Subsystem power off
Note : Do not perform the planned shutdown (powering off) while the READY LED
(green) is blinking at high speed (for the maximum of 30 to 50 minutes).
(1) Turn off the main switch.

(1)
(2) Make sure that the PWR LED (green) on the front of the subsystem is off.
(3) All turn off the AC Power Unit Switch of the Power Unit.
(4) Turn off the battery switch of the Backup Battery Unit.
(5) All turn off the circuit breaker of the PDB.
1 : The PWR LED (green) of the RKA does not go out when the main switch is turned off in the Maintenance mode,
however, this is not a problem.

INST 01-0310-01
1.8 Setting the Power Control Mode (Local/Remote Mode)

Set the mode of the power control. When the Remote mode is selected, the remote control
to control turning on/off of the subsystem power by a host computer is enabled.
(1) Procedure for setting the Remote/Local mode

The remote adapter is not needed when the UPS with the interlocking function is used.
(a) Setting the Local mode
When setting the Local mode
Turn off the power.

(Refer to 1.7.2 Subsystem power off
(INST 01-0310).)
Set the rotary switch (the rotary switch 0

in the Table 1.8.1 Power Control Mode
Settings and Corresponding Operation
Modes (INST 01-0330))
to the LOCAL position.
Turn on the power.

(Refer to 1.7.1 Subsystem power on
(INST 01-0290).)
(b) Setting the Remote mode
When setting the Remote mode
Turn off the power.

(Refer to 1.7.2 Subsystem power off
(INST 01-0310).)
Set the rotary switch (the rotary switch 2

in the Table 1.8.1 Power Control Mode
Settings and Corresponding Operation
Modes (INST 01-0330)) to the Fibre
Channel REMOTE position.
Turn on the power.

(Refer to 1.7.1 Subsystem power on
(INST 01-0290).)

INST 01-0320-01
(2) Setting the Rotary switch (The rotary switch is on the side of the main switch.)
Set the mode of power control.
Either Local mode or Remote mode is set by the Rotary switch. Local/Remote mode settings
and corresponding operation modes are shown in Table 1.8.1.
Table 1.8.1 Power Control Mode Settings and Corresponding Operation Modes
Rotary switch Operation mode name Operation mode
0 LOCAL Local mode (Before shipment)
1
2 Fibre Channel Remote Remote mode by means of the HOST AC (using a remote adapter)
3
4 UPS Interlock mode 1 Interlock mode 1 with an UPS exclusive for the subsystem
To set the mode, connect AC#0 and AC#1 to the UPS and an external and an
external AC power supply or the PDB of the U7 rack frame respectively.
5 UPS Interlock mode 2 Interlocking mode 2 with an UPS exclusive for the subsystem
To set the mode connect AC#0 and AC#1 to the one UPS.(*1)
6 UPS Interlock mode 3 Interlocking mode 3 with an UPS exclusive for the subsystem
To set the mode, connect each of AC#0 and AC#1 to the different UPSs.
7
8
9
: Do not make this setting when the UPS is not connected.
*1 : The duplication of the power supply system becomes unable to be done.
Rotary switch
Here shown is an instance that it is

set to Local-mode. Rotary switch
(a) Floor Model (b) Rackmount Model
Figure 1.8.1 Location of Rotary Switch for Setting Power Control Mode

INST 01-0330-01
.
Chapter 2. Installing Floor Model

2.1 Procedures for Installing Floor Model
(1) Procedures for installing floor model
Before installing and moving subsystem, confirm the following work.
(Subsystem carrying in)
Work-1 Unpacking See 2.2 Unpacking the Subsystem (INST 02-0020)
Work-2 Installing the subsystem See 2.4 Installing the Subsystem (INST 02-0140)
Work-3 Installing components See 2.5 Installing Components (INST 02-0170)
Work-4 Connecting cables See 2.6 Connecting Cables (INST 02-0300)
Work-5 Subsystem power on See 1.7.1 Subsystem power on (INST 01-0290)

See System Parameter 1.1 Procedure for connecting
Work-6 Connection of a service PC and the subsystem Storage Navigator Modular with the subsystem (SYSPR
01-0010)
Work-7 Newly Installing Microprogram (1) See Microprogram Chapter 1. Installation of
Microprogram (MICRO 01-0000)
Work-8 Installing ENC/SENC Firmware See DF700 Disk Array Subsystem Procedure for Offline
ENC/SENC Firmware Download
Work-9 Subsystem setting made
by the operation of the service PC See System Parameter Chapter 2. Setting Host Group
(1) Setting of system parameters (SYSPR 02-0000) to System Parameter Chapter 6.
(2) Setting of host group Setting an Extra-cost Optional Feature (SYSPR 06-
(3) Setting of RAID, LU, and Spare Disk 0000)
(4) Setting of configuration
(5) Setting of the subsystem when using it in the special
mode
(6) Setting of onerous options
A To INST 02-0010
1 : Normally, microprograms are installed when the subsystem is shipped from the factory.

INST 02-0000-01
A For INST 02-0000
Work-10 Subsystem powering off See 1.7.2 Subsystem power off (INST 01-0310)
Work-11 Check by means of subsystem restart See 1.7.1 Subsystem power on (INST 01-0290)
Work-12 Setting the Power Control Mode

See 1.8 Setting the Power Control Mode
(Local/Remote Mode)
(Local/Remote Mode) (INST 01-0320)
Work-14 Connection interface cable See 2.6.1 Connecting Fibre Channel interface cables
(INST 02-0300)
Work-15 How to Attach/Remove Front Bezel or Rear Cover See 1.5 How to Open/Close Door or Attach/Remove
Front Bezel/Rear Cover of the Subsystem
(INST 01-0100)
Work-16 Installing skirt See 2.7 Installing Skirt (INST 02-0350)
Work-17 Installing host computer See manual of each host computer.
(2) Tool for installation work

Names and usages of tools to be used for installation are shown below.
Table 2.1.1 Tool for Installation Work

Division Tool name Specification Usage
Tool Phillips screwdriver No.1 For Local/Remote Mode Setting Switch (rotary switch)
Phillips screwdriver No.2 For general works
Slotted screwdriver No.1 For Device ID Setting Switch
Allen wrench No.3 For installing the floor standing kits (H1J and H2J)
Tool of other LAN cross cable Category 5 For connecting a service PC and the subsystem
PC for maintenance Pentium For maintenance
(Pentium (Pentium II (233 MHz or more) is recommended),
Memory 40 Mbytes or more (64 Mbytes or more is recommended)

INST 02-0010-01
2.2 Unpacking the Subsystem
CAUTION
y The unpacking should be done by two or more personnel to prevent turning over
of the subsystem or being caught under the subsystem.
y Perform the work with enough care because the Floor (RKM+H1H/RKS+ H1J)
Model, Floor (RKM/RKS+RKAJ+H2J) Model, and Floor Model are heavy; their
masses are about 80 kg and 125 kg respectively.
y When moving the subsystem, remove the skirts and raise the leveling bolts.
Otherwise, an accident such as a falling may be caused because of contact with
the floor or catching of a part.
y When moving the subsystem across a difference in floor level, etc., use a
gangway, which forms a slope with an inclination angle of less than eight
degrees.
(1) Unpacking
The procedure for unpacking the subsystem is shown below.
(a) Loosen the polyester bands.
(b) Remove the outer package and packing materials.
(c) Take the subsystem out of the polyethylene bag.
(d) Remove bands, etc. applied to the subsystem.
Polyester bands
Crepe tape
Corrugated cardboard box
Figure 2.2.1 Packed Subsystem

INST 02-0020-01
Accessory box
Subsystem
Crepe tape
Shipping label
Polyethylene bag
Crepe tape
Figure 2.2.2 Packed Subsystem after Removing Other Package
(2) Inspecting the subsystem visually

Check the exterior of the subsystem visually for distortion or damage owing to the transport.
(a) Floor (RKM+H1J) Model (b) Floor (RKM/RKS+RKAJ+H2J) Mode

Figure 2.2.3 External Appearances of Floor Model Subsystem

INST 02-0030-01
(3) Checking contents of package

(a) Check if the contents of the package (their model names, product serial numbers, and
quantities) agree with those in the packing list shipped with the subsystem.
(b) The key for the front bezel(1) supplied with the subsystem must be kept by service personnel
in order to prevent users from maintaining the subsystem.
The key for Front Bezel is used to mount and dismount Front Bezel.
Subsystem serial
number Markings Subsystem serial
number Markings
(a) Floor (RKM+H1J) Model (b) Floor (RKM/RKS+RKAJ+H2J) Model
Figure 2.2.4 Locations of Subsystem Serial Number Markings
1 : Two keys for Front Bezel are attached to Floor Model (RKM+H1J/RKS+H1J)
Four keys for Front Bezel are attached to Floor Model (RKM/RKS+RKAJ+H2J).

INST 02-0040-01
2.3 Installing Floor Stand Kit

2.3.1 Installing Floor Stand Kit
NOTE : Be sure to remove the Disk Drives before installing the subsystem on the Floor
stand kit. Do not installing floor stand kit the subsystem with the Disk Drives
installed.
When the subsystem to be installed has already been made as the floor model, this work is not
necessary. When the kit has already been installed, go to 2.4 Installing the Subsystem
(INST 02-0140).
When remaking the subsystem into the floor model, perform the work explained in 2.3.2
Procedure for installing Floor Stand Kit (INST 02-0060).
It is required to install the floor standing kit, which is an optional component (see Table
2.3.1), to the RKM/RKS or a combination of the RKM and RKAJ to produce the floor model.
Table 2.3.1 Composition of Floor Stand Kit

Kit type No. Part No. Part name Quantity Remarks
Floor stand kit H1J 1 2106507-A CART 1
2 3266239-A Top cover 1
3 3266232-A Option bezel (Front cover) 1
4 1507088-1 Side cover (R) 1 For right side
5 1507087-1 Side cover (L) 1 For left side
6 3183095-408 Washer and socket bolt (M48) 17
7 3266240-A Front Skirt (H1J) 1
8 2106469-A Side Skirt (R) 1 For right side
9 2106469-B Side Skirt (L) 1 For left side
10 3266231-A Option tray (Frame UPS) 1
11 5518619-1 Bracket (UPS) 1
12 Power cable 2 J1H
13 3266241-A Rear cover 1 H1J only
14 3266191-A Clamp (H1J) 1 H1J only
15 SB306 Bind screw (M36.3) 4
16 3274577-1 Label (Handle) 1
Floor stand kit H2J 1 2106502-A CART 1
2 3266235-A Top cover 1
3 3266232-A Option bezel (Front cover) 1
4 150787-1 Side cover (R) 1 For right side
5 1507087-1 Side cover (L) 1 For left side
6 3183095-408 Washer and socket bolt (M48) 24
7 3266233-A Front Skirt (H2J) 1
8 2106462-A Side Skirt (R) 1 For right side
9 2106462-B Side Skirt (L) 1 For left side
10 3266231-A Option tray (Frame UPS) 1
11 5518619-1 Bracket (UPS) 1
12 Power cable 4 J1H
13 3266234-A Rear cover 1 H2J only
14 3266192-A Clamp (H2J) 1 H2J only
15 3259043-445 EMI gasket 2 Against radio-frequency radiation
16 SB306 Bind screw (M36.3) 4
17 3274577-1 Label (Handle) 1
18 5409042-2 Repeat binder 2

INST 02-0050-01
2.3.2 Procedure for installing Floor Stand Kit

(1) Floor (RKM+H1J) Model/Floor (RKS+H1J) Model
(a) Installing the CART
CAUTION
y Masses of RKM is approximately 58 kg , and RKS is approximately 56 kg.
When raising each of them, take measures to prevent it from slipping because
the slipping may cause a personnel injury owing to a pinching.
(i ) Lock the cart to the floor.

Turn the leveling bolts in the direction shown by the arrow so that each clearance
between the caster and the floor becomes about 2.5 mm.
(ii) Fix the left side handle with the label (handle).
(iii) Raise the RKM/RKS making its top facing left, and place it on the Cart.
CAUTION
When raising the subsystem, it is dangerous to do it by using the handles. Be
sure to raise the subsystem by holding its front and rear portions made of sheet
metal.
(iv) Fasten front and rear sides of the RKM/RKS to the cart each with four washer and socket
bolts.

INST 02-0060-01
Label (Handle)
Washer and
socket bolt
Frame
Washer and
socket bolt Top
Handle
CART
Caster
Approx. 2.5 mm
Leveling bolts Floor
(four each)
When the leveling bolt is turned in the arrow direction, it
goes down. (Approx.1.25 mm/turn)
Figure 2.3.2 Installing CART

INST 02-0070-01
(b) Installing the side covers

(i ) Slide the side cover (L) in the direction shown by the arrow and fit its hook and center
claw to the side panel of the frame.
(ii) Insert the three claws at the bottom of the side cover (L) into the three slots on the cart
and then make the side cover (L) stand upright.
(iii) Press the front end of the side cover (L) against the subsystem main body so that there is
no gap between them.
(iv) Fasten top of the side cover (L) to the frame with two washer and socket boltsc.
(v) Insert the three claws at the bottom of the side cover (R) into the three slots on the cart
and then make the side cover (R) stand upright.
(vi) Press the front end of the side cover (R) against the subsystem main body so that there is
(vii) Fasten top of the side cover (L) to the frame with two washer and socket boltsc.
Slide
Washer and socket Hook Washer and socket

bolts c bolts c
Frame
Side cover (L)

Side cover (R)
Craw
Craw
CART
Slot for receiving the claw
Figure 2.3.4 Installing Side Covers

INST 02-0080-01
(c) Installing the top cover

(i ) Place the top cover on the RKM/RKS main body.
(ii) Fasten its front and rear sides with four and one washer and socket bolts respectively.
(iii) Fasten the bracket to the upper rear side of the Option tray with two binding screws
(M36).
Top cover
Washer and
socket bolts
Washer and
socket bolts
CART
Figure 2.3.5 Installing Top Covers

INST 02-0090-01
(2) Floor (RKM/RKS+RKAJ+H2J) Model

(a) Installing the CART
CAUTION
y Masses of RKM is approximately 58 kg , RKS is approximately 56 kg, and RKAJ
40 kg is approximately.
When raising each of them, take measures to prevent it from slipping because
the slipping may cause a personnel injury owing to a pinching.
(i ) Lock the cart to the floor.

Turn the leveling bolts in the direction shown by the arrow so that each clearance
(ii) Stick the EMI gasket on the front side surface of the RKM/RKS.
(iii) Fix the left side handle of RKM/RKS with the label (handle).
CAUTION
When raising the subsystem, it is dangerous to do it by using the handles. Be
sure to raise the subsystem by holding its front and rear portions made of sheet
metal.
(iv) Raise the RKM/RKAJ making its top facing left, and place it on the cart.
(v) Fasten front and rear sides of the subsystem to the CART each with four washer and socket
bolts.
When installing the RKM/RKAJ on the cart, install the RKM first, and then install the RKAJ.

INST 02-0100-01
RKAJ
Washer and socket bolt

Top
EMI gasket
Label (Handle)
Top
Handle
RKM/RKS
Washer and
CART Handle
socket bolt
EMI gasket
Caster
Leveling bolts
(four each) Approx. 2.5 mm
Floor
When the leveling bolt is turned in the arrow direction, it

goes down. (Approx.1.25 mm/turn)
Figure 2.3.6 Installing CART

INST 02-0110-01
(b) Installing the side covers

(i ) Slide the side cover (L) in the direction shown by the arrow and fit its hook and center
claw to the side panel of the RKAJ.
(ii) Insert the three claws at the bottom of the side cover (L) into the three slots on the cart
and then make the side cover (L) stand upright.
(iii) Press the front end of the side cover (L) against the subsystem main body so that there is
(iv) Fasten top of the side cover (L) to the RKAJ (RK, in the case of the H1H) with two washer
and socket boltsc.
(v) Insert the three claws at the bottom of the side cover (R) into the three slots on the cart
and then make the side cover (R) stand upright.
(vi) Press the front end of the side cover (R) against the subsystem main body so that there is
(vii) Fasten top of the side cover (L) to the RKAJ with two washer and socket boltsc.
Slide
Hook
Washer and socket
Washer and socket bolts c
bolts c
Side cover (L)
Side cover (R)
Craw
Craw
CART
Slot for receiving the claw
Figure 2.3.8 Installing Side Covers

INST 02-0120-01
(c) Installing the top cover

(i ) Place the top cover on the RKM/RKAJ main body.
(ii) Fasten its front and rear sides with six and two washer and socket bolts respectively.
Top cover
Washer and
socket bolts
Washer and
socket bolts
CART
Figure 2.3.9 Installing Top Covers

INST 02-0130-01
2.4 Installing the Subsystem

2.4.1 Subsystem floor-space and service clearance
CAUTION
Do not block the vent holes. Or else, temperature rise inside the subsystem may
cause a failure or even a fire.
Install the subsystem so that the air intakes and the air exhaust remain clear.
Figure 2.4.1 shows floor space and service clearance of the floor model
unit : mm
255.78 305.9
18 219.8 18 18 269.9 18
420 420
75 75
30 30
75 75
622.5 622.5 562.5

562.5 472.5
472.5
75 75
30 30
300 300
18 18 18 18
59.7 59.7 59.2 59.2
136.4 187.5
(a) Floor (RKM+H1J) Model (b) Floor (RKM/RKS+RKAJ+H2J) Model

Symbols
: Outline of the floor model : Front side of the floor model
: Maintenance area boundary : Leveling bolt
: Installation area boundary : Caster
Figure 2.4.1 Floor space and service clearance of Floor Models

INST 02-0140-01
2.4.2 Installing the subsystem

(1) Adjusting leveling bolts
(a) Be sure to remove the skirt when moving the subsystem.
Pull Front-skirt toward you and remove it. Then pull side-skirts toward you and remove
them.
(b) Move the subsystem to the place where it is to be installed. When moving it, turn the
leveling bolts to make the casters contact the floor.
(c) Adjust the leveling bolts so that the tilts of the subsystem to the front or rear, and left or
right become 02 mm.
(d) Turn the leveling bolts in the direction shown by the arrow so that each clearance between
the caster and the floor becomes about 2.5 mm.
Duracon catches
Slide
Side skirt (L)
Hook
Side skirt (R)

Front skirt
Figure 2.4.2 Removing Skirt

INST 02-0150-01
0 2 mm
0 2 mm
Leveling bolt(four each)
Caster
Approx. 2.5 mm
Floor
When the leveling bolt is turned in the

arrow direction, it goes down.
(Approx.1.25 mm/turn)
Figure 2.4.3 Adjusting Leveling Bolts

INST 02-0160-01
2.5 Installing Components

Install the components in the subsystem. When installing them, take care not to apply them
any shock.
When some of the components have already been installed, check if they are firmly installed.
If not, fasten them tightly.
The figures in this section are drawn for the procedure of Floor model (RKM/RKS+RKAJ+H2J).
The procedure of other Floor models is similar to the case shown in the figures here.
When the front bezel is attached, remove it before installing a component. (See 1.5 How to
Open/Close Door or Attach/Remove Front Bezel/Rear Cover of the Subsystem (INST 01-
0100).)
Table 2.5.1 Components Required for the Floor (RKM+H1J/RKS+H1J)

No. Component name Model Quantity Remarks
1 Backup Battery Unit 1(*1)
2 Fan Assembly 2
3 Control Unit DF-F700-F1JM 1 or 2(*2) for RKM
DF-F700-F1JS 1 or 2(*2) for RKS
4 Cache Unit DF-F700-C1GJ 1 or 2 The Cache Units with a model name selected from
those shown on the left are installed.
5 Interface Board (for RKM) DF-F700-DJ4G2 1
6 Power Unit 2
7 Disk Drive DF-F700-AGF72 2 to 15(*1) The Disk Drives with a model name selected from those
DF-F700-AGF146 shown on the left are installed.
DF-F700-AGF300
*1 : There is only one Backup Battery Unit to be installed in the RKS and install it in the lower side of the
subsystem.
*2 : When no component is installed, a dummy part is installed instead.
Table 2.5.2 Components Required for the (RKM/RKS+RKAJ+H2J)

No. Component name Model Quantity Remarks
2 Fan Assembly 2
4 Cache Unit DF-F700-C1GJ 1 or 2 The Cache Unit with a model name selected from those
shown on the left are installed.
5 Interface Board (for RKM) DF-F700-DJ4G2 2
6 Power Unit 2 for RKM/RKS
7 Power Unit 2 for RKAJ
8 ENC Unit 2
9 Disk Drive DF-F700-AGF72 2 to 30(*1) The Disk Drives with a model name selected from those
DF-F700-AGF146 shown on the left are installed.
DF-F700-AGF300
*1 : There is only one Backup Battery Unit to be installed in the RKS and install it in the lower side of the
subsystem.

INST 02-0170-01
(1) Installing the Backup Battery Unit

(a) Make sure that the battery switch on the Battery Unit is turned off.
(b) Insert the Backup Battery Unit into the specified position in the subsystem.
NOTE : There is only one Backup Battery Unit to be installed in the RKS and install it in
the lower side of the subsystem.
Battery switch
Latch Backup Battery Unit
Figure 2.5.1 Installing Backup Battery Unit (RKS)
Battery switch
Backup Battery Unit

Latch
Figure 2.5.1.1 Installing Backup Battery Unit (RKM)

INST 02-0180-01
(2) Installing the Fan Assembly

This installing work is only applied to RKM/RKS.
The two same Fan Assemblies are installed facing each other in the state in which each of them
faces upper and lower. When installing them, make each of them face reverse direction
correctly.
(a) Insert the Fan Assembly in the specified position in the subsystem, raise it by fitting the hook
of the lever to the cutout of the subsystem, and tighten it with the fixing screw.
cutout
Fixing screw
Fan Assembly #0
ALM LED
Lever
Fan Assembly #1
ALM LED
Figure 2.5.2 Installing Fan Assembly

INST 02-0190-01
(3) Installing the Control Unit, Cache Unit, and Interface Board
CAUTION
To prevent part failures caused by static electrical charge built up on your own
Be sure to wear a wrist strap connected to the chassis whenever you unpack
damage the parts.
When you install is Control Unit, support its metal part with your hand that has
the wrist strap. You can discharge static electricity by touching the metal plate.
When replacing the additional chassis, a failure may be caused by the electric shock since the
Control Unit is precision instrument. Before starting the operation, make sure to wear a wrist
strap to protect Control Unit against the electric shock.
NOTE : Before unpacking and replacing maintenance components, be sure to wear a

wrist strap and connect to ground the grounding clip in the opposite end of the
wrist strap to the chassis frame (metal part).
When you insert a Control Unit into the subsystem, support the Control Unit as
touching its metal part with fingers of your hand that wears a wrist strap.

Connect this to the metal part on the frame
of subsystem (rear face)
A wristband (Be sure to wear this before

Support a Control Unit by touching

its metal part (metal plate) with your
fingers
Control Unit

INST 02-0200-01
<Working Procedure>
(a) In the case of RKS
Interface Board does not install.
(i) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the
direction shown by the arrow (), and remove it.
(ii) Install the Cache memory after removing the dust cover from the Cache slot of the Control
Unit.
NOTE : For the dual Control Unit, install the Cache Unit of the same capacity in the
Control Unit #0 and #1.
Be careful not to insert Cache Units at the reversed direction.
(iii) Make sure that the Cache Unit is firmly installed.

(iv) Slide the cover in the opposite direction of which it was removed, attach it, and tighten
the fixing screw for the cover at the back of the cover.
(v) Insert it into the position in the Control Unit #0 with the both right and left levers of the
Control Unit pushed down, raise the levers with the hooks fitting to the cutouts of the
subsystem, and tighten the fixing screw for the lever.
In the case of dual Control Unit, Insert it into the position in the Control Unit #1 too.
NOTE : The installation direction is different in the Control Unit # 0 and # 1. Install the
Control Unit #0 with the cover to the right and #1 with the cover to the left.
Cover
Cache Unit Fixing screw
Control Unit #0
Fixing screw

Removal :
Slot lever Press open the slot lever to outside
and pull out the cache memory by
cutout
holding the both end by hand.
Cut Installation :
Fit the projection and the cut and
Projections push it into the slot by holding the
Socket inside the slot both end by hand.
Figure 2.5.3 Installing Control Unit

INST 02-0210-01
(b) In the case of RKM

(ii) Place the Interface Board on the Control Unit fitting it to the positioning pin and fasten it
by tightening the five mounting screws. Insert the connectors surely.
(iii) Make sure that the Interface Board is firmly installed.
(iv) Install the Cache memory after removing the dust cover from the Cache slot of the Control
Unit.
Be careful not to insert the Cache Units in the reverse orientation.
Insert the Cache Units in the cache slots in regular order starting from the slot
#0.
Insert the dust cover in the Cache slot in which the Cache memory is not
installed.
(v) Make sure that the Cache Unit is firmly installed.

(vi) Slide the cover in the opposite direction of which it was removed, attach it, and tighten
(vii) Insert it into the position in the Control Unit #0 with the both right and left levers of the
Control Unit #0 with the cover to the right and #1 with the cover to the left.

INST 02-0220-01
Cover
Positioning hole
Cache Unit Fixing screw
Interface Board
Control Unit #0
Positioning pin
Lever
Fixing screw
Control Unit #1
Control Unit #0
Removal :
Slot lever Press open the slot lever to outside
cutout and pull out the cache memory by
holding the both end by hand.
: Fixing Screw for Interface Board Socket Installation :
(five screws) Cut Fit the projection and the cut and
slot #1 slot #0 inside the slot both end by hand.

INST 02-0230-01
(4) Installing Power Unit

(a) Power Unit of RKM/RKS/RKAJ
Since the Power Units of the RKM/RKS and RKAJ are different from each other, install each of
them in the specified location taking care not to install the wrong one.
(i ) Make sure that the AC Power Unit Switch is turned off.
(ii) Shift the latch (fixing screw) of the Power Unit (RKM/RKS) to the Release position, insert it
slowly into the sheet metal slit part at the right of the power Unit, and then push it to the
end.
(iii) Shift the latch (fixing screw) of the Power Unit (RKAJ) to the Release position, insert it
slowly into the sheet metal slit part at the right of the power Unit, and then push it to the
end.
(RKM/RKS) (RKAJ)
Power Unit #0 (RKAJ)

Power Unit #0
(RKAM/RKS)
AC power unit switch
Power Unit #1 (RKM/RKS)

Latch
Power Unit #1 (RKJ)
Latch
Figure 2.5.4 Installing Power Unit

INST 02-0240-01
(5) Installing the ENC Unit

This installation work is only applied to Floor model (RKM/RKS+RKAJ+H2J).
CAUTION
damage the parts.
When you install an ENC Unit, support its metal part with your hand that has the
wrist strap. By so doing, you can discharge the static electricity from your body
may change the parts.
The ENC Unit is a precision machine that may have troubles because of electrostatic
discharge. Be sure to put on the wristband before starting work in order to protect ENC Units
from electrostatic discharge.

When you insert an ENC Unit into the subsystem, support the ENC Unit as
Support an ENC Unit by touching its

metal part (metal plate) with your fingers
ENC Unit

Connect this to the metal part on the frame
A wristband (Be sure to wear this before of subsystem (rear face)

INST 02-0250-01
(a) Insert the ENC Unit into the specified location in the subsystem with its lever being raised,
then return the lever in the direction shown by the arrow ().
ENC Unit#0
ENC Unit#1
Figure 2.5.5 Installing ENC Unit

INST 02-0260-01
(6) Installing the Disk Drive
CAUTION
damage the parts.
Disk Drives are precision components. Be careful not to expose drives to hard
shock.
When you install a Disk Drive, support its metal part with your hand that has the
wrist strap. You can discharge static electricity by touching the metal plate.
The Disk Drive is a precision machine that may have troubles because of electrostatic
discharge. Be sure to put on the wristband before starting work in order to protect Disk Drives
from electrostatic discharge.

wrist strap to the chassis frame (metal part). When you insert a Disk Drive into
the subsystem, support the Disk Drive as touching its metal part with fingers of
your hand that wears a wrist strap.
Disk Drive
Support a Disk Drive

by touching its metal part (metal plate)
with your fingers
Connect this to the metalpart on the frame of
subsystem (rear face)
A wrist strap
(Be sure to wear this before starting maintenance.)

INST 02-0270-01
(a) Pull the parts out of the Disk Drives safekeeping of component.
Be sure to install the removed Disk Drive to the original bay.
(b) Insert the Disk Drive into the position (address) where it was by holding it with the handle.
(i) Fit the Disk Drive in the guide rail of the RKAJAT and slide it in the direction shown by the
arrow.
(ii) Push it in until it reaches the position where a hook of the handle can be entered into the
rectangular hole at the lower part of a frame on the front side of the disk array unit.
(iii) Raise the stopper, which has been titled toward you, and then have the lock on by
pressing the stopper.
NOTE : If the handle is raised in the state in which its hook cannot be entered into the
rectangular hole, the Disk Drive cannot be installed correctly because it runs
into the frame of the disk array unit.
(c) Pull the handle lightly to make sure that the Disk Drive cannot be pulled out.
(d) Attach the dummy (Disk Drive) to the each Disk Drive slot in which no Disk Drive is installed.
#5 The Disk Drive numbers of

Disk Drive #4 RKM/RKS/RKAJ are assigned
sequentially from No.0 starting at
#3
the bottom and ending at #14.
#2
#1
#0
Handle
The Disk Drive numbers
Indication panel
Figure 2.5.6 Installing Disk Drive

INST 02-0280-01
(7) Setting Unit number

The device ID number of the RKM/RKS/RKAJ has been set to #0. Set the Device ID number of
the RKAJ to be connected to #1.
Position of switch for

Device ID setting (RKAJ)
This figure shows an example in

which the Device ID is set as #1.
Figure 2.5.7 Position of Switch for Device ID Setting
(7) Setting the subsystem identification switch

Set only the RKAJ.
When the basic subsystem to be connected is the RKM, set it in the M side, and when it is the
RKS, set it in the S side.
The figure is a setting example

when the basic subsystem is the
RKM.
Subsystem identification switch (RKAJ)
Figure 2.5.8 Position of the subsystem identification switch

INST 02-0290-01
2.6 Connecting Cables
CAUTION
Take full care to connect cables correctly.
Because operation of the subsystem is affected by the cable routing, follow the 1.1 (2) Note
on cable routing (INST 01-0010).
The figures in this chapter are drawn for the procedure of Floor model (RKM/RKS+RKAJ+H2J).
The cable connection procedure of other Floor model is similar to the case shown in the
figures here.
Remove Rear-cover if installed.
2.6.1 Connecting Fibre Channel interface cables

Two types of cable are provided as the Fibre cables(1) to be used so that they fit to connector
shapes of the RKM/RKS and host computer (or HUB/SW) to be connected.
Table 2.6.1 shows correspondences between the connector shapes and cable types.
Choose the applicable cables from the table correctly.
Table 2.6.1 Types Cables to be Connected

Host computer side
Control Unit side (for RKM/RKS side) Types Cables to be Connected
(HUB/SW)
Parts name of connected Connector Connector form Cable connector
Model Model
cable plug form shape
Control Unit DF-F700-F1JM LC SC LC-SC cable DF-F700-KBM(*1)
DF-F700-F1JS(RKS) LC LC-LC cable DF-F700-KCM(*1)
Interface Board DF-F700-DJ4G2 LC SC LC-SC cable DF-F700-KBM(*1)
LC LC-LC cable DF-F700-KCM(*1)
*1 : "x" denotes a valuable (1 to 5) that shows a cable length.
1 : When the multiple Interface Boards are used, make sure of the port corresponding to the host computer to be
connected.

INST 02-0300-01
Connect the Fibre Channel interface cables after making sure of the ports to be connected
the label.
Route the Fibre Channel interface cable to the Clamp (Fibre).
NOTE : When bending the Fibre Channel interface cable to connect it, give it a bend
with a long radius (not less than 30 mm) so as not to apply the cable and the
connector excessive stresses.
RKS is limited depending on topologies to be set for port and connection
methods. (See 1.2.2 Mini-HUB (INST 01-0020).)
Port 1B-0
Tx
Fibre Channel
Interface cable
Rx
Control Unit #1 (Port 1B-0)
Port 1A-0 Control Unit #1 (Port 1A-0)
Control Unit #0 (Port 0A-0)
Control Unit #0 (Port 0B-0)

Clamp (Fibre)
(a) RKM
Port 1A-1
Tx
Fibre Channel
Interface cable
Rx
Port 1A-0 Control Unit #1 (Port 1A-0)

Clamp (Fibre)
(b) RKS
Figure 2.6.1 Port Layout of Fibre Channel

INST 02-0310-01
2.6.2 Connecting ENC cables

In the case of the Floor (RKM/RKS+RKAJ+H2J) model with both of the RKM/RKAJ, it is required
to connect the Control Unit (RKM/RKS) and the ENC Unit (RKAJ) with the ENC cables (1). (The
ENC cables are supplied with the RKAJ.)
NOTE : y When bending the ENC cable to connect it, give it a bend with a long radius
(not less than 30 mm) so as not to apply the cable and the connector
excessive stresses .
y Connect the two (Loop#0 and Loop#1) systems of each of the Control Unit and
the ENC Unit with the ENC cables.
Parts of the Loop#0 and Loop #1 systems are discriminated from each other by
means of color markings in milk white and yellow respectively.
When connecting the left and right sets of the Control Unit and ENC Unit with
the ENC cables, be sure to connect each of the cables to the sets of adjacent
connectors of the same kind, that is, the PATH#0 (marked in milk white) and
the PATH#1 (marked in yellow) of the ENC Unit and the Control Unit.
(1) Remove the rubber cap on the Control Unit.

(2) Connect the ENC cable to the Control Unit.
(a) To the PATH#0 (marked in milky white on the RKM side), connect the ENC cable marked in
milky white.
(b) To the PATH#1 (marked in yellow on the RKM side), connect the ENC cable marked in yellow.
(3) Connect the ENC cable to the ENC Unit.
(a) To the PATH#0 (on the ENC Unit) side and marked in milk white), connect the ENC cable
(marked in milk white) led from the PATH#0 (on the Control Unit) side and marked in milk
white).
(b) To the PATH#1 (on the ENC Unit side and marked in yellow), connect the ENC cable (marked
in yellow) led from the PATH#1 (on the Control Unit) side and marked in yellow).
(4) After connecting the ENC cable, roll up the excess part of the cable in a circle, tighten it
lightly with the repeat binder, and put it inside the subsystem.
1 : Keep the ENC cables carefully to provide for the case where they are needed.

INST 02-0320-01
Control Unit #1 PATH #1 (yellow)

Control Unit #0 PATH #0 (milk white)
ENC Unit #0
PATH #0 (milk white)
Loop #1
PATH #1 (yellow)
Loop #0
PATH #0 (milk white) PATH #0 (milk white)
PATH #1 (yellow)
Rubber cap
ENC Unit #1
PATH #1 (yellow)
Repeat binder
ENC cable
ENC cable(milk white)
ENC cable(yellow)
Figure 2.6.2 ENC Cable Connection

INST 02-0330-01
2.6.3 Connecting power cables

(1) Connecting the power cables of Power Unit
CAUTION
Make sure that there is no scratch or flaw on a power cable. It can cause an
electric shock or even a fire.
NOTE : y Connect the power cable to the two systems, Power Unit #0 and Power Unit
#1.
y Although the subsystem has a dual power-system, each Power Unit is required
to have capacity for the whole subsystem to cope with one power-system
failure. Accordingly the facility power source for each Power Unit is also
required to have capacity for the whole subsystem.
(a) Make sure that all the Power Unit AC Power Unit switches are turned off.
(b) Connect the connectors (Power Unit side) of the power cables (white, yellow) to the
receptacle of the Power Unit.
(c) Connect the power cable to the power outlet.
Power cable
Figure 2.6.3 Power Cable Connection

INST 02-0340-01
2.7 Installing Skirt
CAUTION
Do not put your hands at both ends of the skirt when installing the front skirt. The
fingers and the like are pinched between the side skirts, and it causes the injury.
(1) Floor (RKM+H1J/RKS+H1J) Model

(a) Install the side skirt (L) by inserting its hooks into rectangular holes on the cart and by sliding it.
(b) Install the side skirt (R) by inserting its hooks into rectangular holes on the cart and by sliding it.
(c) After both side skirts was installed, fit the duracon catch of the front skirt.
Slide
Side skirt (L)

Hook
Side skirt (R)

Front skirt
Duracon catches
Figure 2.7.1 Installing Skirt

INST 02-0350-01
(2) Floor (RKM+RKAJ+H2J/RKS+RKAJ+H2J) model

(a) Install the side skirt (L) by inserting its hooks into rectangular holes on the cart and by sliding it.
(b) Install the side skirt (R) by inserting its hooks into rectangular holes on the cart and by sliding it.
(c) After both side skirts was installed, fit the duracon catch of the front skirt.
Slide
Side skirt (L)
Hook
Side skirt (R)
Front skirt
Duracon catches
Figure 2.7.2 Installing Skirt

INST 02-0360-01

INST 02-0370-01
Chapter 3. Installing Rackmount Model

3.1 Procedures for Installing Rackmount Model
(1) Procedures for installation
In the case of a new introduction or moving, perform the installation after making sure of the
following necessary works.
Work-1 Unpacking rack frame See 3.2 Unpacking and Installing Rack Frame (INST
03-0020)
Work-2 Unpacking the rackmount model See 3.3 Unpacking the Subsystems (INST 03-0310)
Work-3 Removing Components See 3.4.2 Removing Components (INST 03-0330)
Work-4 Mounting on rack frame See 3.4.3 Mounting on Rack Frame (INST 03-0400)
Work-5 Installing Components See 3.4.7 Installing Components (INST 03-0490)
Work-6 Connecting cables See 3.4.8 Connecting Cables (INST 03-0610)
Work-7 Attaching the decoration panel See 3.4.13 Attaching Decoration Panels
(INST 03-0740)
Work-8 Subsystem power on See 1.7.1 Subsystem power on (INST 01-0290)
Work-9 See System Parameter 1.1 Procedure for connecting

Connection of a service PC and the subsystem Storage Navigator Modular with the subsystem
(SYSPR 01-0010)
Work-10 Newly installing microprogram (1) See Microprogram Chapter 1. Installation of
Microprogram (MICRO 01-0000)
Work-11 Installing ENC/SENC Firmware See DF700 Disk Array Subsystem Procedure for
Offline ENC/SENC Firmware Download
See System Parameter Chapter 2. Setting Host Group
by the operation of the service PC
(SYSPR 02-0000) to System Parameter Chapter 6.
(1) Setting of system parameters Setting an Extra-cost Optional Feature (SYSPR 06-
(2) Setting of host group 0000)
(3) Setting of RAID, LU, and Spare Disk
(4) Setting of configuration information
mode
(6) Setting of onerous options
A To INST 03-0010
1 : Normally, microprograms are installed when the subsystem is shipped from the factory.

INST 03-0000-01
A From INST 03-0000
Work-14 Check by means of subsystem restart See 1.7.1 Subsystem power on (INST 01-0290)

See 1.8 Setting the Power Control Mode (Local/Remote
(Local/Remote Mode)
Mode) (INST 01-0320)
Work-17 Connecting Interface cable See 3.4.9 Connecting the Fibre Channel interface
cable (INST 03-0640)
Work-18 Closing doors, etc. See 3.4.14 Closing Door or Attaching Front Bezel
(INST 03-0750)
(2) Tools required

The following tools are required for the installation.
Table 3.1.1 Tools Required

Division Tool name Specification Usage
Tool Phillips screwdriver No.1 For Local/Remote Mode Setting Switch (rotary switch)
Phillips screwdriver No.2 Installation of skirts and securing the subsystem.
Slotted screwdriver No.1 For Device ID Setting Switch
Allen wrench No.3 Securing of cable cramps
Allen wrench No.4 Securing of rail and connection of power cable.
Allen wrench No.6 Opening/closing of doors; removal of stabilizers
Spanner No.22 Adjustment of leveling bolts
Tool of other LAN cross cable Category 5 For connecting a service PC and the subsystem
PC for maintenance Pentium For maintenance
(Pentium (Pentium II (233 MHz or more) is recommended),

INST 03-0010-01
3.2 Unpacking and Installing Rack Frame

3.2.1 U7 Rack Frame (Unpacking/Installing and Installation areas/maintenance areas)
NOTE : When installing the rack rails in the rack frame that has already been in use,
perform the installation works in Step 3.2.1 (11) Installing the rails (INST 03-
0100) and the following steps.
The exterior of the packed rack frame is shown in the Figure 3.2.1 Packed Status of the U7
Rack Frame (INST 03-0030).
Table 3.2.1 show optional parts required to install one subsystem.
As many kits as the subsystems to be mounted are required.
Table 3.2.1 Parts Required for Installation of DF-F600-URHT7

No. Product name Parts No. Quantity Comment Remarks
1 Rail 3272150-1 1 For right hand side
2 Rail 3272150-2 1 For left hand side
3 Stopper 5528571-1 2 For securing the subsystems
4 Cage nut (M5) 5528564-1 12(*1) For securing the rail, subsystems
5 Cage nut (M6) 5528564-3 3(*2) Not used
6 Fastener 5510146-1 14(*1) For securing the rail, subsystems
7 Bind screw (M48) SB408N 8(*1) For securing the stopper
8 Bind screw (M510) SB510N 6(*1) For securing the subsystems
9 Hexagon socket bolt 3261899-520 10(*1) For securing the rail
(M520)
10 Hexagon socket bolt BS612N 3(*1) For securing the subsystems
(M612)
11 LL washer (M4) 5513553-433 6(*1) For securing the stopper
12 LL washer (M5) 5513553-513 10(*1) For securing the rail
13 Washer 5513554-6 3(*2) Not used
14 Lock washer 5513569-6 3(*2) Not used
15 Wire rope 5490846-1 2(*2) Not used
16 Repeat binder (Cable) 5409042-3 3(*2) Used to fix a slackened part of overlong cable
17 Cleat (Cable) 5409055-1 4(*1) For securing the cable
18 Clamp (Fibre) 5511447-1 2 For securing the cable
19 Binder (Flat) 5409039-1 6 For securing the cable
20 Power cable 3272181-E 2 Power cable (900 mm)
*1 : 2 spares are included.
*2 : 1 spare is included.

INST 03-0020-01
(1) Unpacking
(a) Remove the external packaging and packing materials.
(b) Take the rack frame out of the polyethylene bag.
(c) Check all items provided with the U7 rack frame against the table below.
Table 3.2.2 Parts Required for Installation of DF-F600-U7(*1)

No. Product name Parts No. Quantity Comment
1 U7 rack frame 1
2 SKIRT (S) 3256549-A 1 For right hand side
3 SKIRT (S) 3256549-B 1 For left hand side
4 SKIRT (F) 3256547-A 1
5 SKIRT (R) 3256548-A 1
6 Bind screw (M48) SB408 10 For securing the holder and skirt
7 Holder (R) 5507132-1 2 For right hand side
8 Holder (L) 5507132-2 2 For left hand side
9 AC power cable 4
*1 : Exclusive rack frame for mounting an subsystem(s).
Tri-wall cap
Tape
Polyethylene bag
Tri-wall
Tape
Figure 3.2.1 Packed Status of the U7 Rack Frame

INST 03-0030-01
(2) Inspecting the subsystem visually

Check the exterior of the subsystem visually for distortion or damage owing to the transport.
U7 Rack frame
Stabilizer
Figure 3.2.2 Exterior Rack Frame

Check if the contents of the package (their model names, product serial numbers, and

INST 03-0040-01
(4) Installation and maintenance areas

Figure 3.2.3 shows installation and maintenance areas for the DF-F600-U7 rack frame.
Unit : mm
910
1,000
150 610 150
60 135
808 688 538
60 135
42.5 525 42.5
90 430 90
1,000
Symbols
: Outline of the rack frame : Front side of the rack frame
: Maintenance area boundary : Leveling bolt
: Swinging door : Caster
Figure 3.2.3 Installation and Maintenance Areas of Rack Frame

INST 03-0050-01
(5) Move the unpacked subsystem to the site where it is to be installed.

When moving the subsystem, attach the stabilizers to prevent it from falling.
(6) Removing stabilizers

(a) Remove the allen bolt (M840) with an Allen wrench.
(b) Remove the stabilizers from subsystem.
Keep the removed allen bolt (M840) and stabilizers. (They will be necessary when the rack
frame is moved again later.)
Allen bolt (M840)
Stabilizer
Allen bolt (M840)
Figure 3.2.4 Removing the Stabilizers

INST 03-0060-01
(7) Settling the rack frame

Settle the rack frame in the installation site by adjusting the leveling bolts.
(a) Turn the each leveling bolt in the direction shown by the arrow so that the clearance
(b) Adjust the leveling volts so that the tilts of the subsystem to the front or rear and left or
right become 0 2 mm.
left side and right front and rear
0 2 mm 0 2 mm When the leveling bolt is turned in the

arrow direction, it goes down.
(Approx.2.5 mm/turn)
Leveling bolts
(four each)
Approx. 2.5 mm
Floor Caster
Figure 3.2.5 Adjusting Leveling Bolts

INST 03-0070-01
(8) Installing the skirts

Make the bottom of the skirt contact the floor to prevent a trouble caused by an electrostatic
discharge.
(a) Fasten the skirt bracket and skirt (F) with the binding screws.
(b) Fasten the holder to the lower part on the side with binding screws.
(c) Install the skirt (S)'s on the left and right sides of the subsystem.
To install the skirt (S), engage it with the holders of the frame by sliding it in the direction
from rear to front.
(d) Fasten the skirt (S) with the binding screws.
(e) For wiring on the floor, pull out the plug of PDB before installing the skirt (R).
(f) For wiring on the floor, loosen two screws (M38) of the skirt (R), adjust the sliding section
and pass the cable.
(g) Install the skirt (R) by fitting its claws into the rectangular holes on the skirt (S).
Decoration panel (1U)
Binding screw
(M48 Black)
Skirt (F)
Binding screw
Skirt (S) (M48 Black)
(for right side)
Binding screw (M48)

Skirt bracket
Skirt (R) Binding screw (M48) Holder

Screw (M38) Binding screw (M48)
Binding screw (M48)
Binding screw (M48)
Skirt (S)
Sliding section (for left side)
Binding screw (M48) Screw (M38)

Rectangular
Figure 3.2.6 Installing Skirts and Removing Decoration Panel(s)
(9) Removing the decoration panels (1 U)

When the decorative panels have been attached, it is necessary to remove the one(s) attached
to the location(s) where the subsystem(s) is to be mounted.
(a) Pull the decorative panel toward you.
(b) The decorative panel will be come off.
INST 03-0080-01
(10) Removing the protection paper

(a) Open the rear door.
(Refer to 1.5.4 How to open/close the Rear Door of U7 rack frame (INST 01-0150).)
(b) Remove the protection paper which covers the Rear door.
Rear door
Frame
Protection paper
Figure 3.2.6.1 Removing the protection paper

INST 03-0090-01
(11) Installing the rails

If the rails have already been installed, this installation is not required.
For the components list, see Table 3.1.1 Tools Required (INST 03-0010).
EIA units and intervals of mounting holes of 19-inch rack frame conforming to EIA standard
y A unit (U) space conforming to EIA standard is 19 inches wide and 44.5mm high as shown in
the figure below.
y The boundary of the unit falls on the middle of the interval of 12.7mm.
y When the unit space is shifted by 0.5 units, the unit boundary is shifted from the normal
position by 22.2mm.
For the U7 rack frame
Wide intervals: Repeat of 44.45mm (31.75mm + 12.7mm)
Maximum number of mountable unit spaces: 38
12.7mm Unit boundary
15.875mm
31.75mm 1U = 44.45 mm
1 unit (EIA)
15.875mm
12.7mm Unit boundary
Some types of rack frame do not have this hole.

Rack frame with the holes (HP, etc.): Universal interval
Rack frame without the holes (U7): Wide interval
Figure 3.2.7 Attachment Hole Size of Rack

INST 03-0100-01
The addresses are given as 1, 2, 3, and so on counted from the bottom of the rack frame. In
the case of the U7 rack frame, you must count the holes to know the address because no
number is marked on the rack frame.
The following figure illustrates the whole layout of addresses of installation positions in the U7
rack frame.
There are 38 addresses, that is, the 1U to 38U counted in the vertical direction starting from
the lower boundary of the 1U (the lowest unit).
Addresses of installation The height from the bottom

positions boundary of number 1U
Unit boundary 1689.10 mm

38U
37U
Unit boundary 36U 1600.20 mm
33U
32U
31U
30U
29U
28U
27U
26U
25U
24U
23U
22U
21U
20U
19U
18U
17U
16U
15U
Area of 4 EIA units(*1) 14U
13U
12U
11U
6U
4U
2U
1U
Unit boundary
(Starting point of
height direction)
*1 : The grayed are shows a layout of an area for installing the subsystem at the 11U
Figure 3.2.8 Whole Layout of Installation Position Addresses

INST 03-0110-01
(a) Slide the stopper in the direction shown by the arrow and temporarily fix it to the Rail (R)
using the binding screws and LL washers c (M4 (at two places.)).
For the installation position address, see Figure 3.2.8.
(b) On the right side of the installation location in the rack frame, align the round holes of the
Rail (R) with those of the rack frame and insert the fasteners (at four places in total in front
and rear.).
(c) Fasten the Rail (R) to the rack frame using the hexagon socket bolts and LL washers d (M5
(at two places each on the front and rear sides.)).
(d) Install the Rail (L) to the rack frame in the same way.
Binding screw (M48) Rack frame Rack frame

LL washer c (M4) (Rear side) (Front side)
Stopper
Fastener
LL washer d (M5)
Hexagon socket bolt
(M520)
Rail (R)
LL washer d (M5)
Hexagon socket bolt
(M520)
Rack frame
Unit boundary
Hexagon socket bolt 1 unit
(M520) Position of 14U
(EIA(*1))
4 unit (EIA) LL washer (M5)
Floor Model Unit boundary
mounting area Fastener 1 unit
(RKM/RKS) Position of 13U
(EIA(*1))
Unit boundary
3 unit (EIA) 1 unit
Floor Model (EIA(*1)) Position of 12U
mounting area Unit boundary
(RKAJ/RKAJAT)
1 unit Position of 11U
(EIA(*1))
Unit boundary
Rail
When you shift the rail a little upward from the position where the bottom edge of
the rail is aligned with the lower boundary line of the installation position address
(boundary of a unit), the 2nd and 4th (counted from the lowest one) round holes on
the rail are exactly aligned with the holes on the rack frame.
*1 : One EIA unit is approximately 44. 45 mm.
Figure 3.2.9 Installation of Rails to the Rack frame and Installation Positions

INST 03-0120-01
(12) Installing fasteners on the front side of the rack frame

Install the fasteners on the front side of the rack frame in order to fasten the subsystems to be
mounted on the rack frame.
(a) Fit the two fasteners to each of the right and left beams on the front side of the rack frame
referring to Figures 3.2.10 and 3.2.11.
Install the mounting fasteners at the 2nd and 5th (counted upward from the unit boundary on
the rack frame at the same height as the bottom of the rail) round holes.
Unit boundary
Unit boundary
Unit boundary
Unit boundary
Unit boundary
Fastener
Rail (R)
Figure 3.2.10 Installing Fasteners on the Front Side of the Rack Frame

INST 03-0130-01
Part of the subsystem to be

fastened
Installation position of the

fastener for fastening on the
rack frame
Rail
Frame (beam) to which the rail is to Frame (beam) to which the fasteners for
be installed fastening to be installed
Figure 3.2.11 Installation Positions of Fasteners and Relation with Rails

INST 03-0140-01
3.2.2 HP Rack Frame (Unpacking/Installing and Installation areas/maintenance areas)

The DF700 can be mounted on the HP rack frame by installing the rack rails for Hitachi
common rack frame (DF-F700-UR7) which are accessory parts.
Installation procedure for the case where the HP rack frame with the rack rails HP rack frame
(HP model name: J1501A) are used is shown below.
The exterior of the packed rack frame is shown in the Figure 3.2.22.
Table 3.2.3 show optional parts required to install one subsystem.
As many kits as the subsystems to be mounted are required.
Table 3.2.3 Parts Required for Installation of DF-F700-UR7 (Rev.B or C)

1 Front rail 3272207-1 1 For left hand side
2 Front rail 3272207-2 1 For right hand side
3 Rear rail 3272208-1 2 For left/right commonness
5 Spacer 5528619-1 2 Not used
6 Bind screw (M510) SB510N 18 For securing the subsystems
7 Bind screw (M46) SB406N 14
9 19PART (nickel plated) 5528564-1 10 Cage nut
10 Rack nut 5510146-1 14
11 Hexagon Socket Head Bolts 5503443-1 10
12 LL washer 5513553-513 10
13 Repeat binder (Cable) 5409042-1 3 For securing cables on the subsystem
(1) Appearance of HP rack frame

Figure 3.2.12 shows appearance of the HP rack frame.
Front door
Figure 3.2.12 Appearance of Rack Frame (HP Model Name: J1501A)

INST 03-0150-01
(2) Installing the rails

If the rails have already been installed, this installation is not required.
For the components list, see Table 3.2.3 Parts Required for Installation of DF-F700-UR7
(Rev.B or C) (INST 03-0150).
y A unit (U) space conforming to EIA standard is 19 inches wide and 44.5 mm high as shown in
the figure below.
y The boundary of the unit falls on the middle of the interval of 12.7 mm.
position by 22.2 mm.
For the HP rack frame
Universal intervals: Repeat of 44.45 mm (15.875 mm + 15.875 mm + 12.7 mm)
12.7 mm Unit boundary
15.875 mm
31.75 mm 1U 44.45 mm
15.875 mm 1 unit (EIA)

Rack frame with the holes (HP, etc.): Universal interval
Rack frame without the holes (U7): Wide interval

INST 03-0160-01
Addresses within the rack frame are called (EIA) unit numbers.
The addresses are given as 1, 2, 3, and so on counted from the bottom of the rack frame.
NOTE : When the HP rack frame has front door, mount the subsystem leaving a space
with a height of 1unit (EIA) unit or more from the bottom of the rack frame.
Addresses of installation The height from the bottom

positions boundary of number 1U

33U
32U
31U
30U
29U
28U
27U
26U
25U
24U
23U
22U
21U
20U
19U
18U
17U
Area of 4 EIA units(*1) 16U
15U
14U 577.85 mm
Unit boundary 13U
12U
11U
10U
9U
8U
7U
6U
5U
4U
3U
2U
1U
Unit boundary
(Starting point of
height direction)
*1 : The grayed are shows a layout of an area for installing the Basic subsystem at the 11U
Figure 3.2.14 Whole Layout of Installation Position Addresses (HP)

INST 03-0170-01
Install the rack rail to the rack frame referring to Figure 3.2.15 - Figure 3.2.17.
(a) Installing the spacer
Install the spacer (there is no vertical distinction) to fix the rail to the front side of the rack
frame. (One right and left place for each)
Fasten the 2nd and 8th holes counted upward from the unit boundary of the subsystem
installation position and the screw holes at both ends of the space with the binding screws
(M5 x 10) from the rear side of the frame.
(b) Remove the rail fixing screws (M4 x 6) of the factory setting.
(c) Fix the places, where the screw holes of the front rail and those of the rear rail are matched,
temporarily with the binding screws (M4 x 6 (six places)) (fix at least four places, temporarily).
(d) Install the rack nuts at the 4th and 6th positions counted from the unit boundary of the
subsystem installation position of the rear side of the rack frame.
(e) Fasten the holes at two places near the center of the front side of the front rail and the
screw holes of the spacer with the binding screws (M5 x 10).
(f) Fasten the rear side of the rear rail and the rack nuts of (d) with the binding screws (M5 x
10).
(g) Fasten the binding screws (M4 x 6) which were temporarily fixed in (c).
(h) Install the rack nuts in the holes at the sheet metal folding part of the front rail (two places).
(i) Perform the above-mentioned installation for the right and left of the rack frame.
Rack frame
(Front side)
Binding screw
Rack frame (M510)
(Rear side)
Rack nut
Spacer
Binding screw
Binding screw (M36)
(M510) Stopper
Binding screw
(M510)
Rack nut
Rear rail
Front rail
Binding screw
(M46)
Figure 3.2.15 Installation of Rails to the Rack frame

INST 03-0180-01
Rack frame
(Front side)
Unit boundary
1 unit
Position of 16U Rack nut
(EIA (*1))
Spacer (For securing the subsystem)
Unit boundary
1 unit A
Position of 15U
(EIA (*1))
Unit boundary B 3 unit (EIA (*1)) 4 unit (EIA (*1))
1 unit Floor Model Floor Model
Position of 14U mounting area mounting area
(EIA (*1))
(RKAJ/RKAJAT) (RKM/RKS)
Unit boundary
1 unit
Position of 13U
(EIA (*1))
Unit boundary
Rail (Front side)
A : Position of the hole to be
used to fix the spacer
B : Position of the hole to be
used to fix the rail
Figure 3.2.16 Location of installing the rail on the front side of the Rack frame
Rack frame
(Rear side)
Rail (Rear side)

Rack nut
Unit boundary
A : Position of the hole to be

used to fix the rail
Figure 3.2.17 Location of installing the rail on the rear side of the Rack frame

INST 03-0190-01
CAUTION
Press the rail against the rack frame as much as possible to secure the rail to the
rack frame. If there is a gap between the rail and the rack frame, the rail may
interfere with the equipment.

INST 03-0200-01
3.2.3 Sun StorEdge Rack Frame (Unpacking/Installing and Installation

areas/maintenance areas)
The RKM/RKAJ/RKAJAT/RKS can be mounted on the Sun 19-inch rack frame by installing the
rack rails (DF-F700-UR7) which are accessory parts.
Installation procedure for the case where the Sun 19-inch rack frame with the rack rails (DF-
F700-UR7) are used is shown below.
The Components-list of SUN StorEdge Rack-frame is shown in Table 3.2.4.

The packaging of the Rack-frame is shown in Figure 3.2.18.
Table 3.2.4 Components of Rack-rail (HT-F-UR7) (per one unit)

6 Bind screw (M510) SB510N 18 For securing the subsystems
10 Rack nut 5510146-1 14
12 LL washer 5513553-5113 10
13 Repeat binder (Cable) 5409042-1 3 Used to fix a slackened part of overlong
cable

INST 03-0210-01
(1) Appearance of Sun 19-inch rack frame

Figure 3.2.18 shows appearance of the Sun 19-inch rack frame.
(There are two types of Sun 19-inch rack frames: Sun StorEdge and Sun Fire.)
For install the

For install the Floor Model
Floor Model
Front door Front door
Sun StorEdge
Sun Fire
(Sun Model Name: SG-XARY030A)
Figure 3.2.18 Appearance of Sun 19-inch Rack Frame

INST 03-0220-01
(2) Installing rails

(a) Remove the rail fixing screws (M4 x 6) of the factory setting.
(b) Fix the places, where the screw holes of the front rail and those of the rear rail are matched,
temporarily with the binding screws (M4 x 6 (four places)).
NOTE : For SUN Fire, fix it temporarily with the binding screws (M4 x 6 (six places)) (fix
at least four places, temporarily).
(c) Fasten the holes at two places near the center of the front side of the front rail and the 4th
and 6th screw holes counted from the boundary of the subsystem installation position of the
front side of the rack frame with the hexagonal socket head bolts and the LL washers M5.
(d) Fasten the holes at two places of the rear side of the rear rail and the 4th and 6th screw
holes counted from the boundary unit of the subsystem installation position with the
hexagonal socket head bolts and the LL washers M5.
(e) Fasten the binding screws (M4 x 6) which were temporarily fixed in (b).
(f) Install the rack nuts in the holes at the sheet metal folding part of the front rail (two places).
(g) Perform the above-mentioned installation for the right and left of the rack frame.
Rack frame (Rear side)
Hexagon socket
Rack frame (Front side)
head bolt
+
LL washer M5
Binding screw
(M46)
Stopper
Front rail
Rear rail
Rack nut
Hexagon socket Binding screw
head bolt (M46)
+
LL washer M5

INST 03-0230-01
Rack frame
(Front side)
Unit boundary
1 unit Rack nut
Position of 14U
(EIA (*1)) (For securing the subsystem)
Unit boundary
Rail (Front side)
1 unit
Position of 13U
(EIA (*1))
Unit boundary 3 unit (EIA (*1)) 4 unit (EIA (*1))
(EIA (*1))
Unit boundary (RKAJ/RKAJAT) (RKM/RKS)
1 unit
Position of 11U
(EIA (*1))
Unit boundary
Rack frame
(Rear side)
Rail (Rear side)
Unit boundary

INST 03-0240-01
CAUTION

INST 03-0250-01
3.2.4 RS6000 Rack Frame (Unpacking/Installing and Installation areas/ maintenance areas)
The subsystems can be mounted on the IBM RS6000 rack frame by installing the rack rails (DF-
F700-UR7), which are accessory parts.
(1) When installingDF-F700-UR7

The Components-list of RS6000 Rack Frame is shown in Table 3.2.7.
Table 3.2.7 Parts Required for Installation of DF-F700-UR7

6 Binding screw (M510) SB510N 18 For securing the subsystems
7 Binding screw (M46) SB406N 14
8 Binding screw (M36) SB306N 6
10 Rack nut 5510146-1 14
12 LL washer 5513553-513 10
13 Repeat binder (Cable) 5409042-1 3 For securing cable routing

INST 03-0260-01
(a) Installing the rails and rack nut

Install the rails and rack nut in order to mount the subsystem(s) on the rack frame.
y A unit (U) space conforming to EIA standard is 19 inches wide and 44.5 mm high as shown in
the figure below.
y The boundary of the unit falls on the middle of the interval of 12.7 mm.
position by 22.2 mm.
For the IBM RS6000 rack frame
Universal intervals: Repeat of 44.45 mm (15.875 mm + 15.875 mm + 12.7 mm)
15.875 mm
31.75 mm 1U 44.45 mm
15.875 mm 1 unit (EIA)

Rack frame with the holes : Universal interval
Rack frame without the holes : Wide interval

INST 03-0270-01
(i ) Remove the rail fixing screws (M4 x 6) of the factory setting.
(ii) Fix the places, where the screw holes of the front rail and those of the rear rail are
matched, temporarily with the binding screws (M4 x 6 (six places))
(fix at least four places, temporarily).
(iii) Install the rack nuts at the 4th and 6th positions counted from the boundary unit of the
subsystem installation position for both front and rear sides of the rack frame.
(iv) Fasten the holes at two places near the center of the front side of the front rail and the
rack nut installation parts of the front side of the rack frame with the binding screws (M5 x
10) (two places).
(v) Fasten the holes of the rear side of the rear rail and the rack nut installation parts of the
rear side of the rack frame with the binding screws (M5 x 10) (two places).
(vi) Fasten the binding screws (M4 x 6) which were temporarily fixed in (ii).
(vii) Install the rack nuts in the holes at the sheet metal folding part of the front rail (two
places).
(viii) Perform the above-mentioned installation for the right and left of the rack frame.
Rack frame
(Rear view)
Binding screw
(M510)
Rack frame
(Front view)
Rack nut
Stopper
Rack nut Binding screw
(M36)
Front rail
Rear rail
Binding screw Rack nut
(M510) Binding screw
(M46)

INST 03-0280-01
Rack frame
(Front side)
Unit boundary
1 unit
Position of 16U
(EIA (*1))
Rail (Front side)
Unit boundary
1 unit
Position of 15U
(EIA (*1)) Rack nut
Unit boundary
3 unit (EIA (*1)) 4 unit (EIA (*1))
(EIA (*1))
Unit boundary (RKAJ/RKAJAT) (RKM/RKS)
1 unit
Position of 13U
(EIA (*1))
Unit boundary
Rack frame
(Rear side)
Rail (Rear side)

Rack nut
Unit boundary

INST 03-0290-01
CAUTION

INST 03-0300-01
3.3 Unpacking the Subsystems
CAUTION
y The unpacking should be done by two or more personnel to prevent turning over
of the subsystem or being caught under the subsystem.
y Work carefully because the mass of the single RKM is about 58 kg, RKS is about
56 kg, RKAJ / RKAJAT is about 40 kg.
(1) Unpacking
Figure 3.3.1 shows the subsystem within the outer package and Figures 3.3.2 show the packed
subsystem without the outer package.
(a) Remove the outer package and packing materials.
(b) Take the subsystem out of the polyethylene bag.
(c) Remove tapes, etc. applied to the subsystem.
(d) Remove desiccating agent from the lower of the subsystem.
(e) Check the exterior of the subsystem visually for distortion or damage owing to the transport.
Accessory box
Front Bezel
Buffer pad (Upper) Buffer pad (Upper)
Desiccating agent
(DESICCANT)
Subsystem
Pad
Buffer pad (Lower)
Corrugated cardboard box
Figure 3.3.1 Packed Subsystem

INST 03-0310-01

(a) Check if the contents of the package (their model names, product serial numbers, and
(b) The key for the front bezel supplied with the subsystem must be kept by service personnel in
order to prevent users from maintaining the subsystem.
The key for Front Bezel is used to mount and dismount Front Bezel
Subsystem serial Subsystem serial

number Markings number Markings
(a) RKM/RKS (b) RKAJ/RKAJAT
Figure 3.3.2 Locations of Subsystem Serial Number Markings

INST 03-0320-01
3.4 Installing the Rackmount Model

3.4.1 Work Procedure before Installing the Rack Mounting
Install it in the Rack Frame with each component mounted when installing it with 1m or less in
height or lifter. (Work from 3.4.3 Mounting on Rack Frame (INST 03-0400).)
In other cases, install it in the Rack Frame after removing each component.
(Work from 3.4.2 Removing Components (INST 03-0330).)
Since the device ID numbers are set at the factory when the subsystem is newly introduced,
make sure of them, and then mount the devices in appropriate order from the lowest one. (For
the setting of the device ID number, refer to 3.4.7 (1-2) Setting Device ID number (INST 03-
0520).
3.4.2 Removing Components
CAUTION
damage the parts.

Disk Drive

face)

INST 03-0330-01
(1) Removing Disk Drive

(1) Remove the Front Bezel. (1.5 How to Open/Close Door or Attach/Remove Front Bezel/Rear
Cover of the Subsystem (INST 01-0100).)
(2) Remove the Disk Drive or a dummy (Disk Drive).
Pull the stopper at the upper part of the Disk Drive handle toward you to have the lock off,
tilt the handle toward you, and then remove the Disk Drive or dummy (Disk Drive) by pulling
it out taking care not to apply a shock to it.
(3) Keep the Disk Drive of dummy (Disk Drive) that has been removed temporarily in the
component safekeeping container at the location shown on the address label with its handle
returned to its original state (locked by the stopper). It is to be installed in the disk array
unit after the unit is mounted on the rack frame.
Address label
Safekeeping of screw
Disk Drive
Stopper Disk Drive

Handle
Safekeeping box
Figure 3.4.1 Removing Disk Drive

INST 03-0340-01
(2) Removing Backup Battery Unit

This Removing work is only applied to RKM/RKS.
(a) Shift the latch on the Battery Units to the Release position and pull the Battery Unit toward
you until the latch pin comes out (to release the Unit).
NOTE : Handle the Battery Unit carefully because its depth is shallow (150mm) and
weight is heavy (3.0kg).
(b) Take out the Battery Unit holding its main body by your both hands.
Latch
Backup Battery Unit #0 Backup Battery Unit #1

READY LED
Battery switch
Figure 3.4.2 Removing Backup Battery Unit

INST 03-0350-01
(3) Removing Fan Assembly

This Removing work is only applied to RKM/RKS.
(a) Loosen the screw which is fixing the lever of the Fan Unit, open the lever, and move it forward.
(b) Remove the Fan Assembly by pulling it out holding its main body with your both hands.
Fan Assembly #0
Fan Assembly #1
ALM LED ALM LED

Fixing screw
Lever
cutout
Figure 3.4.3 Removing Fan Assembly

INST 03-0360-01
(4) Removing the Control Unit

(a) Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down the
levers forward, and pull out the Control Unit.
(b) Remove the Control Unit by pulling it out toward you.
Control Unit #1
Fixing screw
cutout
Control Unit #0
Figure 3.4.4 Removing Control Unit

INST 03-0370-01
(5) Removing ENC Unit (for RKAJ) and SENC Unit (for RKAJAT)
(a) Raise the lever on the ENC Unit/SENC Unit in the direction shown by the arrow c () and
pull out the ENC Unit/SENC Unit a little way toward you.
(b) Remove the ENC Unit/SENC Unit by pulling it out toward you.
Lever
ENC Unit #0 (RKAJ)/ ENC Unit #1 (RKAJ)/

SENC Unit #0 (RKAJAT) SENC Unit #1 (RKAJAT)
Figure 3.4.5 Removing ENC Unit/SENC Unit

INST 03-0380-01
(6) Removing Power Unit

(a) Loosen the screw which is fixing the latch of the Power Unit, shift the latch (fixing screw) to
the Release position, and move it forward by holding the handle.
(b) Remove the Power Unit by pulling it out holding its main body with your both hands.
READY LED
ALARM LED
Lock
Release
AC Power Unit Latch

Switch (fixing screw)
Power Unit #1
Power Unit #0
Handle
Latch (fixing screw)
(a) RKM/RKS
Latch
READY LED ALARM LED (fixing screw)
Lock
Release
AC Power Unit
Switch
Power Unit #1
Power Unit #0
Handle
(b) RKAJ/RKAJAT
Figure 3.4.6 Removing Power Unit

INST 03-0390-01
3.4.3 Mounting on Rack Frame

Install it in the Rack Frame after sticking the EMI gasket on the Frame.
(1) Sticking EMI gasket

Stick the EMI gasket supplied with the rack rail on the top of the RKM/RKAJ /RKAJAT frame.
(a) Peel off the anti-adhesion sheet from the bottom surface of the EMI gasket.
(b) Stick the EMI gasket so that the screws at the front of the top of the frame can be seen.
(c) Stick the EMI gasket by aligning it with the back end of the top of the frame.
Back end of the subsystem.

Frame top
EMI gasket
Stick the EMI gasket so that the screws at the
front of the top of the frame can be seen.
Figure 3.4.7 Position for Sticking EMI Gasket(RKM/RKS)
Back end of the subsystem.

Frame top
EMI gasket
Stick the EMI gasket so that the screws at the
front of the top of the frame can be seen.
Figure 3.4.8 Position for Sticking EMI Gasket(RKAJ/RKAJAT)

INST 03-0400-01
3.4.4 Mounting lifter on rack frame

Figure 3.4.9 shows external appearance of the special lifter.
Handle
590 mm
1,900 mm
Valve
1,611 mm
Band
Base
Stopper
880 mm 970 mm
Figure 3.4.9 External lifter

INST 03-0410-01
CAUTION
y Rack mounting and lifter operation should only be conducted by a person who
has been trained and qualified since the subsystem could turn over or a worker
could be caught under the subsystem.
(1) Bring the special lifter close to the subsystem to be mounted and apply the brake to the lifter.
NOTE : When putting the subsystem on the special lifter, be sure to remove the front
bezel beforehand.
(2) Put the subsystem on the special lifter.

Put the subsystem with its front bezel removed on the lifter.
(3) Secure the subsystem to the lifter with a band of the lifter.
Bind the subsystem with the band tightly by fitting the length of the belt to the subsystem.
Handle
Valve
Front side of the subsystem to be
mounted
Band
Stopper Base Subsystem to be mounted
DF700
Figure 3.4.10 tting the Subsystems on Special Lifter

INST 03-0420-01
3.4.5 Mounting subsystem on rack frame
WARNING
If the Subsystem falls when the elevator of the lifter is at a high position, a
personal injury will be caused.
Perform the positioning, fastening, or other handlings very carefully.
CAUTION
y Rack mounting and lifter operation should only be conducted by a person who
has been trained and qualified since the subsystem could turn over or a worker
could be caught under the subsystem.
y Operate the valve slowly when opening it. If it is opened quickly, the elevator of
the lifter descends rapidly and may cause personal injury.
(1) Take off the brake of the special lifter on which the subsystem has been put, and move the
lifter close to the rack frame.
(2) Adjust the position of the subsystem so that it is seated in the center of the rack frame.
(3) Move the pumping handle of the special lifter to the right and left repeatedly to lift the
subsystem up to the height suitable for the mounting.
Be careful not to lift the elevating base too high. If you lift it too high, lower it by opening
the up/down valve gently.
(4) Remove the band and adjust the position of the subsystem so that the subsystem comes in the
center in front of the rack frame. If the subsystem is positioned off-centered, a screw
contacts the front bezel preventing the bezel from being opened or closed.
(5) Shift the subsystem onto the rails in the rack frame. When shifting the subsystem, push it in
to the end gently.

INST 03-0430-01
CAUTION
Do not move the lifter away from the rack frame nor lower the elevator until the red
line on the label affixed on the subsystem enters the rack frame across the end of
it. Otherwise, falling of the subsystem may be caused.
44kg. 58kg 44kg.

56kg. 56kg 40kg.
58kg.
RKM RKS RKAJ/RKAJAT
(6) After mounting the subsystem on the rack frame, lower the elevating base to the lowermost
position by gently opening the up/down valve of the special lifter and take off the brake of the
lifter.
(7) Move the special lifter to the place where the lifter does not disturb the following works.
DF700
Lifter
Front
U7 rack frame
Push in
Pumping handle
Subsystem already Valve

installed
Base
Up/down
Elevator
Figure 3.4.11 Mounting Subsystem on Rack Frame

INST 03-0440-01
3.4.6 Securing the subsystem

(1) U7 Rack frame
This is common for the three unit and four unit Rackmount models.
(a) Fastening the front side of the subsystem
(i ) Fasten the subsystem to the rack frame with the four M510 binding screws.
Rack frame
Fastener
Cutout
Rail
Binding screw Subsystem
Rack frame
(M510)
Binding screw
(M510)
Subsystem
Figure 3.4.12 Fastening Front Side of the Subsystem
(b) Fastening rear side of the subsystem

(i ) Shift each of the two stoppers in the direction shown by the arrow and make it contact the
frame.
(ii) Tighten the binding screws.
DF700 frame
Rail
Stopper
Binding screw
Figure 3.4.13 Securing Rear Side of the Subsystem

INST 03-0450-01
(2) HP Rack frame

(i) Fasten the cutouts of the subsystem to the rack frame with the binding screws (M5 x 10)
(four places).
Rack nut
Fixing
positions
Binding screw
(M510)
Frame
RKM/RKS (*1)
*1 : Fasten RKAJ/RKAJAT (3U) as well.

(i) Slide each of the two stoppers in the direction shown by the arrow until it contacts with
the frame.
(ii) Tighten the binding screws (M3 x 6) to fix it.
Frame
Frame
Stopper
Installation positions
Binding screw
Contact point (M510)

INST 03-0460-01
(3) Sun StorEdge Rack frame

(four places).
Rack nut
Fixing
positions
Binding screw
(M510)
Frame
RKM/RKS (*1)

the frame.
Frame
Frame
Stopper
Binding screw

INST 03-0470-01
(4) IBM RS6000 Rack frame

(four places).
Rack nut
Fixing
positions
Binding screw
(M510)
Frame
RKM/RKS (*1)

the frame.
Frame
Frame
Stopper
Binding screw

INST 03-0480-01
3.4.7 Installing Components
CAUTION
damage the parts.

Disk Drive

face)

INST 03-0490-01
When the components are not installed, install them. If they have already been installed, go
to the next step since this work is not needed.
Table 3.4.1 Parts Required for Installation of RKM/RKS

No. Component name Model Quantity Remark
1 DISK Drive DF-F700-AGF72 2 to 15(*1) The Disk Drive with a model name selected from those
DF-F700-AGF146 shown on the left is installed.
DF-F700-AGF300
2 Fan Assembly 2
4 Cache Unit DF-F700-C1GJ 1 or 2 The Cache Unit with a model name selected from those
shown on the left is installed.
5 Interface Board DF-F700- DJ4G2 2 for RKM
6 Power Unit 2
*2 : There is only one Backup Battery Unit to be installed in the RKS and it is installed in the left side when seen
from the front of the subsystem.
Table 3.4.2 Components Required for the RKAJ

1 DISK Drive DF-F700-AGF72 2 to 15(*1) The Disk Drive with a model name selected from those
DF-F700-AGF146 shown on the left is installed.
DF-F700-AGF300
1 ENC Unit (RKAJ) 2
2 Power Unit (RKAJ) 2
3 ENC cable 4 See 3.4.10 Connecting the ENC cables (INST 03-
0670)
Table 3.4.3 Components Required for the RKAJAT

1 DISK Drive DF-F700-ATE250R 2 to 15(*1) The Disk Drive with a model name selected from those
DF-F700-ATE400R shown on the left is installed.
1 SENC Unit (RKAJAT) 2
2 Power Unit (RKAJAT) 2
3 ENC cable 2 See 3.4.10 Connecting the ENC cables (INST 03-
0670)

INST 03-0500-01
(1) Installing the Disk Drive

(a) Pull the parts out of the Disk Drives safekeeping of component.
Be sure to install the removed Disk Drive to the original bay.
(b) Insert the Disk Drive into the position (address) where it was by holding it with the handle.
arrow.
(c) Pull the handle lightly to make sure that the Disk Drive cannot be pulled out.
(d) Attach the dummy (Disk Drive) to the each Disk Drive slot in which no Disk Drive is installed.
Address label Guide Rail
Safekeeping
of screw
Disk Drive
Stopper
Handle
Hook
Safekeeping of
component Rectangular Hole
Figure 3.4.21 Installing of Disk Drive
#0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
RKM/RKS/RKAJ/RKAJAT
Disk Drive number
Figure 3.4.22 Disk Drive Mounting Location

INST 03-0510-01
(1-2) Setting Device ID number

The Device ID of the RKM/RKS has been set as #0.
Set the Device ID numbers of the RKAJ/RKAJAT in serial order starting from the RKAJ/RKAJAT
connected next to the RKM/RKS.
In the case of a configuration of one RKM/RKS+ RKAJs + RKAJATs, set the device IDs of the
RKAJ, the RKAJATs connected to the Path 0, and the RKAJATs connected to the Path 1 as #0x,
#2x, and #3x respectively. Set the x as an ascending serial number in each of the Path 0 and
Path 1 without discrimination between the RKAJ and RKAJAT.
For details of the device ID setting, refer to 1.6 Device ID Setting and ENC Cable Connection
(INST 01-0160).
Position of switch for Device ID setting

(RKAJ/RKAJAT)
This figure shows an example in which

the Device ID is set as #01.
(1-3) Setting the subsystem identification switch

Set only the RKAJ.
Subsystem identification switch
The figure is a setting example when the

basic subsystem is the RKM.

INST 03-0520-01
(2) Installing Backup Battery Unit

This installation work is only applied to RKM/RKS.
(a) In the case of the RKM/RKS
(i) Remove the Front Bezel. (1.5 How to Open/Close Door or Attach/Remove Front
Bezel/Rear Cover of the Subsystem (INST 01-0100))
(ii) Make sure that the battery switch on the Backup Battery Unit is turned off.
(iii) Insert the Backup Battery Unit into the specified position in the subsystem.
NOTE : There is only one Backup Battery Unit to be installed in the RKS and it is
installed in the left side when seen from the front of the subsystem.
Latch
READY LED Backup Battery Unit

Battery switch
Figure 3.4.25 Installing Backup Battery Unit

INST 03-0530-01
(3) Installing Fan Assembly

This installing work is only applied to RKM/RKS.
The two same Fan Assembly are installed facing each other in the state in which each of them
faces left and right. When installing them, make each of them face reverse direction
correctly.
(a) Insert the Fan Assembly in the specified position in the subsystem, raise it by fitting the hook
Fan Assembly #0
Fan Assembly #1
ALM LED ALM LED

Fixing screw
Lever
cutout
Figure 3.4.26 Installing Fan Assembly

INST 03-0540-01
(4) Installing the Control Unit, Cache Unit and Interface Board
When the Cache Unit and the Interface Board are already installed, the installing work for
Cache Unit and the Interface Board is not required.
(a) In the case of RKS
Interface Board does not install.
(ii) Install the Cache memory after removing the dust cover from the Cache slot of the Control
Unit.
Be careful not to insert Cache Units at the reversed direction.
(iii) Make sure that the Cache Unit is firmly installed.

(iv) Slide the cover in the opposite direction of which it was removed, attach it, and tighten
(v) Insert it into the position in the Control Unit #0 with the both right and left levers of the
Control Unit #0 with the cover up and #1 with the cover down.

INST 03-0550-01
Control Unit #1
Cover
Control Unit #0
Fixing screw
Lever
Slot lever Removal :

Fixing screw Press open the slot lever to outside
and pull out the cache memory by
Cut holding the both end by hand.
Installation :
Projections
push it into the slot by holding the
cutout inside the slot
Socket both end by hand.

INST 03-0560-01
(b) In the case of RKM

(ii) Place the Interface Board on the Control Unit fitting it to the positioning pin and fasten it
by tightening the five mounting screws. Insert the connectors surely.
(iii) Make sure that the Interface Board is firmly installed.
(iv) Install the Cache memory after removing the dust cover from the Cache slot of the Control
Unit.
Be careful not to insert the Cache Units in the reverse orientation.
Insert the Cache Units in the cache slots in regular order starting from the slot
#0.
Insert the dust cover in the Cache slot in which the Cache memory is not
installed.
(v) Make sure that the Cache Unit is firmly installed.

(vi) Slide the cover in the opposite direction of which it was removed, attach it, and tighten
(vii) Insert it into the position in the Control Unit #0 with the both right and left levers of the
Control Unit #0 with the cover up and #1 with the cover down.

INST 03-0570-01
Control Unit #1
Cover
Positioning hole
Interface Board Fixing screw
Control Unit #0
Positioning pin
Lever
Slot lever : Fixing Screw for Interface Board
Fixing screw
(five screws)
Socket Removal :
Press open the slot lever to outside
Cut and pull out the cache memory by
Projections holding the both end by hand.
cutout Installation :
slot #1 slot #0 inside the slot
both end by hand.

INST 03-0580-01
(5) Installing ENC Unit (for RKAJ) and SENC Unit (for RKAJAT)
Install the ENC unit in the RKA and the SENC unit in the RKAJAT.
(a) Insert the ENC Unit/SENC Unit into the specified location in the subsystem with its lever
being raised, then return the lever in the direction shown by the arrow ().
Take notice that the forms differ between the ENC Unit and SENC Unit.
ENC Unit (RKAJ)
SENC Unit (RKAJAT)
Lever
Release
ENC Unit #0/SENC Unit #0 ENC Unit #1/SENC Unit #1
Lock
Figure 3.4.29 Installing ENC Unit/SENC Unit

INST 03-0590-01
(6) Installing Power Unit

(a ) Make sure that the AC Power Unit Switch is turned off.
(b) Shift the latch (fixing screw) of the Power Unit to the Release position, insert it slowly into
the sheet metal slit part at the top of the power Unit, and then push it to the end.
READY LED
ALARM LED
Lock
Release
AC Power Unit Latch

Power Unit #1
Power Unit #0
Handle
(a) RKM/RKS
Latch
Lock
Release
AC Power Unit
Switch
Power Unit #1
Power Unit #0
Handle
(b) RKAJ/RKAJAT
Figure 3.4.30 Installing Power Unit

INST 03-0600-01
3.4.8 Connecting Cables
CAUTION
Take full care to connect cables correctly.
Because operation of the subsystem is affected by the cable routing, follow the 1.1 (2) Note
on cable routing (INST 01-0010).
NOTE : Power supply system of the RKM/RKS/RKAJ/RKAJAT is duplicated.

It is recommended to connect each system to outlet of one of the two power
sources independent of each other.
The cable routing for the subsystem which is mounted on the rack frame is shown in Figure
3.4.31, Figure 3.4.32. Types of the cables to be used are shown in Table 3.4.4.

No. Cable name Remarks
1 Interface cable (Fibre Channel) See 3.4.9 Connecting the Fibre Channel
interface cable (INST 03-0640)
2 ENC cable See 3.4.10 Connecting the ENC cables (INST
03-0670)
3 Power cable(*1) (100 V) See 3.4.11 Connecting the power cables
(INST 03-0710)
4 Power cable (200 V) (Rack frame PDB) See 3.4.12 Connecting the power cables
(Rack frame PDB) (INST 03-0730)
Power cable (Added PDB) See Addition/Subtraction/Relocation 1.5.2 (5)
Installing the power Cable (Added PDB append
parts) and cable holder. (ADD 01-0480)
*1 : When replacing power cable of the RKM/RKAJ/RKAJAT/RKS, which has already been
connected, with the optional power cable, refer to Addition/Subtraction/Relocation 3.3.1
Disconnecting the power cables (ADD 03-0090).

INST 03-0610-01
PDB #01
PDB #11
Power cables Power cables
Power Unit #0 ENC cables Power Unit #1
PDB #10
PDB #00
ENC cables
Power cables
Fibre cables Power cables
Figure 3.4.31 Cable Routing for the Subsystem (RKM/RKS/RKAJ)

INST 03-0620-01
Power cables Power Unit #0 Power Unit #1 Power cables
PDB #01 PDB #11
PDB #00
PDB #10
ENC cables
ENC cables
Fibre cables
Power cables Power cables
Figure 3.4.32 Cable Routing for the Subsystem (RKM/RKS/RKAJAT)

INST 03-0630-01
3.4.9 Connecting the Fibre Channel interface cable

Two types of cable are provided as the interface cables(1) to be used so that they fit to
connector shapes of the RKM/RKS and host computer (or HUB/SW) to be connected.
Table 3.4.10 shows correspondences between the connector shapes and cable types.
Choose the applicable cables from the table correctly.

Host computer side
Control Unit side Types Cables to be Connected
(HUB/SW)
(for RKM/RKS side)
Parts name of connected Connector Cable connector
Model Connector form Model
cable plug form shape
SC LC-SC cable DF-F700-KBM(*1)

DF-F700-F1JM
Control Unit LC
DF-F700-F1JS(RKS)
Interface Board DF-F700-DJ4G2 (RKM) LC SC LC-SC cable DF-F700-KBM(*1)

*1 : x denotes a valuable (1 to 5) that shows a cable length.
(1) Connect the Fibre Channel interface cables after making sure of the ports to be connected the
label. (Refer to Figure 3.4.33.)
NOTE : When bending the Fibre Channel interface cable to connect it, give it a bend
with a long radius (not less than 30 mm) so as not to apply the cable and the
RKS is limited depending on topologies to be set for port and connection
methods. (See 1.2.2 Mini-HUB (INST 01-0020).)
(2) Pull all the interface cables into the rack frame passing them through an opening for cables on
the bottom plate of the rack frame.
1 : When the multiple ports are used, make sure of the port corresponding to the host computer to be connected.

INST 03-0640-01
Port 1B-0 connection side Port 1A-0 connection side
Port 0A-0 connection side Port 0B-0 connection side
Interface cable for Fibre Channel interface Pulled-in side
(a) RKM
Port 1A-1 connection side Port 1A-0 connection side
Port 0A-0 connection side Port 0A-1 connection side
Interface cable for Fibre Channel interface Pulled-in side
(b) RKS
Figure 3.4.33 Binding Interface Cables
(3) Connect the interface cable to the connector of the each port.
(4) Affix the Clamps (Fibre), which are supplied with the DF-F700-URHT7 (rail kit for the U7), on
the U7 rack frame and route the Fibre Channel interface cable using the Clamps.
(5) Fasten the interface cables to the rack frame at the cable passing opening on the he bottom
plate giving them excessive lengths so that they will not be pulled.

INST 03-0650-01
RKM
U7 rack frame Control Unit #0 Control Unit #0

(Port 0A-0) (Port 0B-0)
Tx Rx
Control Unit #1
Control Unit t #0 Fibre cables
Fibre cables
Cable passing opening
Clamp (Fibre)
(a) RKM
RKS
U7 rack frame Control Unit #0 Control Unit #0

(Port 0A-0) (Port 0A-1)
Tx Rx
Control Unit #1
Control Unit t #0 Fibre cables
Fibre cables
Clamp (Fibre)
(b) RKS
Figure 3.4.34 Routing Interface Cables (RKM/RKS)

INST 03-0660-01
3.4.10 Connecting the ENC cables

When connecting the RKM and RKAJ, execute the procedure (1).
(Refer to (1) When connecting the RKM and RKAJ (INST 03-0670).)
When connecting the RKM and RKAJ/RKAJAT, execute the procedure (2).
(Refer to (2) When connecting the RKM and RKAJ/RKAJAT (INST 03-0690).)
(1) When connecting the RKM and RKAJ
In the case of the RKAJ with both of the Control Unit of RKM/RKAJ, it is required to connect
the Control Unit (RKM) and the ENC Unit with the ENC cables (1). (The ENC cables are supplied
with the RKAJ.)
NOTE : y In single controller configuration, connect the ENC cable only to the Loop #0
(ENC Unit #0) side. Do not connect it to the Loop #1 (ENC unit #1) side.
When two or more RKAJ are connected, however, both cables in ENC Unit #0
and ENC Unit #1 should be connected for the RKAJ.
y When bending the ENC cable to connect it, give it a bend with a long radius
Execute the following referring to Figure 3.4.35 Connecting ENC Cables (INST 03-0680).
(a) Remove the rubber cap on the Control Unit.
(b) Connect the ENC cable to the Control Unit.
(c) Connect the ENC cable to the ENC Unit of the RKAJ.
NOTE : Connect the Control Unit#0 of the RKM with the ENC Unit#0 of the RKAJ and the
Control Unit#1 of the RKM with the ENC Unit 1 of the RKAJ. Connect two
Path#0 connectors (with milk white indication) using the ENC cable and also
connect two Path#1 connectors (with yellow indication) using another ENC cable
(see Figure 3.6.4).
(i ) To the PATH#0 (marked in milky white on the RKM side), connect the ENC cable marked in
milky white.
(ii) To the PATH#1 (marked in yellow on the RKM side), connect the ENC cable marked in yellow.
(d) When the two or more RKAJs are mounted, connect each of the sets of the adjacent
connectors of the same kind, that is, the PATH#0 and PATH#1 of the RKAJs using the ENC
cables. (see Figure 3.4.32)
For the ENC cable connection in which the maximum configuration of RKM and RKAJs is
installed, refer to Figure 1.6.1 Example of RKM+RKAJ ENC cable connection (The figure
shows an example in which the maximum configuration is installed in the U7 rack frame.)
(INST 01-0160).
(i ) Remove the rubber cap of the ENC Units in the locations where the ENC cables are to be
connected.
(ii) Connect each of the connectors PATH#0 (marked in milk white) and PATH#1 (marked in
yellow) of the ENC Unit, from which the rubber cap was removed, with the ENC cables
marked in the same color respectively.
(iii) Connect each of the connectors PATH#0 (marked in milk white) and PATH#1 (marked in
yellow) of the adjacent RKAJ with the ENC cables marked in the same color.
(e) After connecting the ENC cable, roll up the excess part of the cable in a circle, tighten it
lightly with the repeat binder.
NOTE : Do not fix the ENC cable and the power cable together.

INST 03-0670-01
Indication position of color

ENC cable (milk white)
ENC cable (yellow)
PATH #0 (milk white) PATH #1 (yellow) PATH #0 (milk white) PATH #1 (yellow)
IN side ENC Unite #0 IN side ENC Unite #1
OUT side OUT side
IN side ENC Unite #0 IN side ENC Unite #1
OUT side OUT side
ENC Unite #0
Loop #0 Loop #1
ENC Unite #1
RKAJ
RKM (RKS)
Indication
position of color
(yellow)
Indication Control Unit #1

position of color Rubber cap
Control Unit #0
(milk white)
PATH #1 (yellow) PATH #0 (milk white)
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT
PATH #0 (milk white) PATH #1 (yellow)
Figure 3.4.35 Connecting ENC Cables

INST 03-0680-01
(2) When connecting the RKM and RKAJ/RKAJAT

In the case of the RKAJ/RKAJAT with both of the Control Unit of RKM, it is required to connect
the Control Unit (RKM) and the ENC Unit/SENC Unit with the ENC cables (1). (The ENC cables
are supplied with the RKAJ/RKAJAT.)
NOTE : y In single controller configuration, connect the ENC cable only to the Loop #0
(ENC Unit #0/SENC Unit #0) side. Do not connect it to the Loop #1 (ENC unit
#1/SENC unit #1) side.
When two or more RKAJ/RKAJAT are connected, however, both cables in ENC
Unit #0/SENC Unit #0/ and ENC Unit #1/ SENC Unit #1 should be connected
for the RKAJ/RKAJAT.
y The IN and OUT connectors of the SENC unit of the RKAJAT have indications
by means of blue and green labels respectively.
Execute the following referring to Figure 3.4.36 Connecting ENC Cables (RKM) (INST 03-
0700).
(a) Attach milk white or yellow Mini-Binders to the ENC cable.
(b) Remove the rubber cap on the Control Unit.
(c) Connect the ENC cable to the Control Unit.
(d) Connect the ENC cable to the ENC Unit/SENC Unit of the RKAJ/RKAJAT.
NOTE : Connect the Control Unit#0 of the RKM with the ENC Unit#0/SENC Unit#0 of the
RKAJ/RKAJAT and the Control Unit#1 of the RKM with the ENC Unit #1/SENC
Unit #1 of the RKAJ/RKAJAT (see Figure 3.4.32.2).
(i ) Connect the cable marked in milky white from PATH#0 (marked in milky white) of RKM to
the IN side (Blue Label) of the SENC Unit of RKAJAT (Unit ID#1).
(ii) Connect the cable marked in yellow from PATH#1 (marked in yellow) of RKM to the IN side
(Blue Label) of the SENC Unit of RKAJAT (Unit ID#2).
(e) When the two or more RKAJs/RKAJATs are mounted, connect the OUT side (Green Label) and
the IN side (Blue Label) of the SENC Unit of the RKAJATs using the ENC cables. (see Figure
3.4.32.2)
For the ENC cable connection in which the maximum configuration of RKM and RKAJs/
RKAJATs is installed, refer to Figure 1.6.2 Example of RKM+RKAJ+RKAJAT ENC cable
connection (The figure shows an example in which the maximum configuration is installed in
the U7 rack frame.) (INST 01-0170).
(i ) Remove the rubber cap of the ENC Units/SENC Units in the locations where the ENC cables
are to be connected.
(ii) Connect each of the connectors the OUT side (Green Label) and the IN side (Blue Label) of
the SENC Unit, from which the rubber cap was removed, with the ENC cables.
(f) After connecting the ENC cable, roll up the excess part of the cable in a circle, tighten it
lightly with the repeat binder.
NOTE : Do not fix the ENC cable and the power cable together.

INST 03-0690-01

ENC cable (yellow)
IN side IN side
(Blue Label) SENC Unit #0 (Blue Label) SENC Unit #1
OUT Side OUT Side

(Green Label) (Green Label)
IN side IN side
OUT Side OUT Side

Loop #0 SENC Unit #0

SENC Unit #1 Loop #1
RKAJAT
RKM
Indication (RKS)
position of color
(yellow)
Indication
position of color
(milk white) Control Unit #1 Attach milk white or yellow Mini-Binders
Rubber cap
Control Unit #0 to the ENC cable.
Cut off an excess portion of the cable
after the Mini-Binders are attached.
NOTE
y Do not tighten the Mini-Binders
too much.
LASER PRODUCT
CLASS 1
LASER KLASSE 1
y Take care not to damage the

Control Unit #1 ENC cable when cutting the
Mini-Binder.
Control Unit #0 Mini-Binders
LASER KLASSE 1
CLASS 1
LASER PRODUCT
5mm 5mm
PATH #1 (yellow) Positions for attaching Mini-Binders
Figure 3.4.36 Connecting ENC Cables (RKM)

INST 03-0700-01
3.4.11 Connecting the power cables

(1) In the case of the RKM
(a) Connecting the power cables of Power Unit
CAUTION
(i )Make sure that the breaker of the each PDB has been turned off.
(ii)Make sure that the AC Power Unit Switch of the each Power Unit has been turned off.
(iii)
Insert the power cable plug into the receptacle on the each Power Unit.
(iv)In the case of the RKAJ/RKAJAT, pass Repeat Binders through the cleats attached to the
right and left stoppers and fasten the power cable with the Binders.
(v) Insert the each power cable plug into the corresponding receptacle of the PDB. (Use the
PDB receptacles in the order from the J10 to J13.)
NOTE : y Be sure to plug the power cable for the Power Unit#0 in the receptacle of the
PDB#00 or PDB#01.
Be sure to plug the power cable for the Power Unit#1 in the receptacle of the
PDB#10 or PDB#11.
If they are plugged in the receptacles of the PDBs on the same side, the
function of the duplicated power supply does not work.
y Do not plug any cable other than the power cable of the mounted subsystem
in the outlet of the PDB.
y Limit the total current output from the outlets J10 to J13 so that it does not
exceed 20 amperes (1).
(vi) Hang the cable clamp of PDB on the plug of the power cable.
(vii) Route the power cables.
(viii) Push in the plug of the power cable which has been inserted into the PDB again.
It may be loosened owing to a routing.
1 : When installing the two or more RKMs, connect them so that the load on a PDB does not exceed 20 A after checking
the load through a calculation.
RKM one unit : 3.6 A
RKAJ one unit : 2.4 A
RKAJAT one unit : 2.4 A

INST 03-0710-01
PDB #00
Cleat
Repeat binder
Stopper
PDB #10
Power cable
cable cramp
J13
J12
Power supply
connector
Power cable
J11
J10
Figure 3.4.37 Routing Power Cables to the Mounted Subsystem

INST 03-0720-01
3.4.12 Connecting the power cables (Rack frame PDB)
CAUTION
y Make sure that there is no scratch or flaw on a power cable. It can cause an
y The cable of PDB is a fixed type. Do not loosen the installation part. If it is
loosened, the connected part is damaged, and it causes an electric shock or fire.
NOTE : Make sure that conductors shall be provided with 30 A over current protection
in accordance with Article 240 of the National Electrical Code, ANSI/NFPA 70,
and the Canadian Electrical Code, Part 1, CSA C22.1, Section 14.
(1) Open the rear door. (See Subsection, 1.5.4 How to open/close the Rear Door of U7 rack
frame (INST 01-0150).)
(2) Make sure that the power supply switches of the PDBs are turned off.
(3) Put out the power cables of PDBs through the Cable passing opening at the bottom of the Rack.
(4) Remove the cable holders from the rack frame by removing the hexagon socket head bolts.
(5) Fasten the power cables to the rack frame by attaching the cable holders with the Allen bolts.
(6) Make sure that the connecter is securely fixed after the assembly work.
PDB #01
PDB #11
Rear door
Power cable
(Rack frame PDB)
PDB #10
PDB #00 Power supplying switch
Power input connector

cable holder
Hexagon socket head bolt
Power cable
PDB #00/01 side (Rack frame PDB)

PDB #10/11 side
Figure 3.4.38 Connecting Power Cables (Rack frame PDB)

INST 03-0730-01
3.4.13 Attaching Decoration Panels

When a vacant space is left on the front side of the rack frame, install the decoration panels
there.
(1) Fit the decoration panels to the front side of the rack frame one by one starting from the top.
(2) The decoration panel can be installed when the two extrusions of it are aligned with the holes,
which are prepared on the rack frame with intervals of one EIA unit, and then pressed into the
holes.
Gasket
(gasket side is upper)
Decoration panel
(1 U) Protrusion
Figure 3.4.39 Attaching Decoration Panel

INST 03-0740-01
3.4.14 Closing Door or Attaching Front Bezel

(1) Close the rear door. (Refer to 1.5.4 How to open/close the Rear Door of U7 rack frame (INST
01-0150).)
(2) Attach the Front Bezel. (Refer to 1.5.3 How to attach/remove Front Bezel of the Rackmount
Model (INST 01-0130).)

INST 03-0750-01
FE-95DF747-00
Microprogram
Chapter 1. Installation of Microprogram ....................................................................... MICRO 01-0000
Chapter 2. Procedure for Recovery from a Failure ...................................................... MICRO 02-0000
Install partially complete Message Is Output ........... MICRO 03-0000

MICRO 00-0000-01

MICRO 00-0010-01
Chapter 1. Installation of Microprogram

This work is for new installation or update installation of the microprogram in the subsystem.
NOTE : For update installation, replace the Control Unit with the subsystem power
turned off, and then install the microprogram after the subsystem enters the
READY status. Do not perform the updating installation of the microprogram
while the READY LED is high-speed blinking (up to 30/50 minutes).
1.1 Materials necessary for installation

Service PC(1)
LAN cross cable
CD-ROM for microprogram installation
1 : The service PC must have a CD-ROM drive for the microprogram installation. If the service PC has no CD-ROM
drive, it must be set up beforehand via a network.
(See 1.3 (4) Procedure for setting up the service PC (MICRO 01-0050).

MICRO 01-0000-01
1.2 Outline of procedure for installation

(1) Install the microprogram using the WEB or Storage Navigator Modular connection from the
service PC.
(2) The update installation of the microprogram can be done only in the maintenance mode
(cannot be done online).
(3) In the service PC, JRE (1) 1.3.1 03 must be installed. (See 1.3 (4) Procedure for setting up the
service PC (MICRO 01-0050).)
(4) A [User Name] and a [Password] may be requested at the time of Web connection or Web
operation. In that case, input maintenance for the [User Name] and hosyu9500 for the
[Password].
START
Set up a service PC
1.3 Preparation for installation of
microprogram (MICRO 01-0020)
Power on.
The subsystem is not started when the microprogram is not

Does the READY LED on the Front
installed.
Bezel come on? No
When it is high-speed blinking, Install micro-program newly.
wait up to 30/50 minutes.
Yes
The microprogram has already been installed.
No Do you want to continue the update

installation of the microprogram?
Yes
Connect a LAN Cable to the device LAN port IP address:

for maintenance, and perform WEB connection. LAN port for maintenance on CTL No.0:10.0.0.16
LAN port for maintenance on CTL No.1: 10.0.0.17
If connection cannot be made, try again with the following IP
Update install micro-program. address.
1.4 (3) Update Installation of Microprogram LAN port for maintenance on CTL No.0: 192.168.0.16
(MICRO 01-0140) LAN port for maintenance on CTL No.1: 192.168.0.17
END
1 : Java runtime environment.

MICRO 01-0010-01
1.3 Preparation for installation of microprogram

(1) Outline
Set up the service PC before starting the update installation. Outline of the setting up is
shown below
y Installation of the JRE 1.3.1 03
y Setting of the security policy file
y Copying of the microprogram from the CD-ROM for the microprogram installation to the
service PC
(2) Prerequisites for setting up of a service PC

Prerequisites concerning the user ID of Windows are as follows.
y The user ID of Windows at the time when the microprogram is installed in the service PC
must be identical with that at the time when a maintenance work is done.
y The user ID mentioned above must be defined not with full size Japanese characters but with
half size alphabetic characters and/or numerals.
A prerequisite of a drive for booting the OS of the service PC

y The drive for booting the OS must be the c drive.
(3) Java error codes displayed at the time of update installation and actions for coping with them.
When the PC does not satisfy the prerequisite shown in Item (2) in Subsection 6.1.3,
Preparation for update installation of microprogram a Java error occurs. Details of the Java
errors and actions for coping with them are shown below.

MICRO 01-0020-01
Table 1.3.1 Java error codes

Action for coping with the error
Message Message text Time when the error occurs/
code Cause estimated
1216 Access to the property Time when the error occurs c Check if the drive for booting the OS is the
information was rejected. y The error occurs immediately after the c drive. (Refer to the note (a) of (3) in
Confirm the setup of the [Select] key is pressed when the Subsection 1.3.)
security policy. microprogram is selected. In the case of the dual boot, boot Windows
Cause estimated using the c drive and perform the
y A drive for booting the OS is not the c installation again.
drive. d Check if the user name of Windows at the
y The user name of Windows at the time time when the microprogram is installed in
when the microprogram was installed in the service PC is identical with that at the
the service PC is not identical with that at time when the microprogram is updated
the time when the microprogram is and if two-byte characters (such as full size
updated, or two-byte characters (full size characters and Japanese characters) are
characters or Japanese characters) are not used. If an illegal specification has been
used to define the user name made, perform the logon over again using
an appropriate user name and perform the
installation again after connecting the
browser.
1219 An error occurred during the Time when the error occurs c Reboot the subsystem and the service PC
communication with the y The error occurs when the resource for and quit unnecessary application programs.
subsystem. Confirm the the LAN cannot be ensured. Make sure that the subsystem is in the
subsystem status and the LAN Cause estimated Ready status, place the subsystem in the
environment. y The error occurs because the resource Maintenance mode, and perform the
(memory) of the service PC is insufficient. installation again.
d If the error recurs in spite of the operations
above, replace the service PC and perform
the installation over again from the
beginning.
Use a PC whose memory capacity is as
large as possible.

MICRO 01-0030-01
(a) Method for checking the drive for booting the OS

A method for checking the boot drive when the Java message (message code: 1216) is issued
is shown below.
( i ) Double click the [ : Java icon ]on the task tray at the bottom right in the Service PC
window.
(i i ) Since the JavaConsole window opens, make sure that the [User Home Directory] is the
c drive (=C: \*****).
If =C:***** is displayed here, the

boot drive is the c drive.

MICRO 01-0040-01
(4) Procedure for setting up the service PC

(a) Double click the Program\micro upload\micro setup\Setup. exe of the CD-ROM for
microprogram installation.
(b) The initial window of the setting up appears.
When the [Next] button is pressed, the JRE 1.3.1 03 installer is activated in the case where
the JRE 1.3.1 03 is not installed yet.
In the case where the JRE 1.3.1 03 has been installed, windows shown in Steps (c) to (g) are
not displayed.
(c) A dialog box for asking confirmation of starting the JRE 1.3.1 03 installer. Click the [OK]
button.

MICRO 01-0050-01
(d) A window of product licensing contract is displayed. Click the [Yes] button.
(e) A window for selecting a directory in which the JRE 1.3.1 03 is to be installed.
Select the directory for the installation and click the [Next] button.
(f) A window for specifying the Java default browser is displayed. Select the browser being
used and click the [Next] button.

MICRO 01-0060-01
(g) Installation of the JRE 1.3.1 03 is started.
(h) After the installation of the JRE 1.3.1 03 is completed, set the security policy file.
When the security policy file (.java.policy) exists in the home directory of the current user, a
window for asking confirmation of starting the setting is displayed.
Click the [Yes] button.

MICRO 01-0070-01
(i) The microprogram is copied on the service PC.

Create a directory to which the microprogram is to be copied directly under the
C:\diskarray-microprogram\microprogram for each microprogram revision and copy the
microprogram file with the subdirectories (DF700M, DF700S, ENC, ---) into the directory.
(j) The setting up is completed. Press the [OK] button.
(5) Notes
(a) Note that the settings of the security policy file is changed when the service PC is set up.
(b) If the microprogram is transferred to a directory other than C:\diskarray-
microprogram\microprogram which is a directory copied by the installer, the installation
cannot be done. Therefore, care should be taken.
(c) Do not change a name of the unified version directory(1) or directory in a stratum under the
unified version directory. The ENC/SENC firmware becomes unable to be installed if the
directory name is changed.
1 : For the unified version directory, refer to 1.3.1 Hierarchy of Microprogram Storage Directories (MICRO 01-0090).

MICRO 01-0080-01
1.3.1 Hierarchy of Microprogram Storage Directories

The hierarchical structure of Microprogram storage directories is shown in Table 1.3.2.
The structure of directories of the CD-ROM for installing the Microprogram is the same as that
shown in Table 1.3.2.
When the CD-ROM installer is executed, the unified version directory is stored under the
directory, C:\diskarray-microprogram\microprogram.
When installing the Microprogram, specify the unified version directory.
Table 1.3.2 Directory Hierarchy
First stratum Second stratum Third stratum Fourth stratum Fifth stratum
Unified version DF700M disk 01 - disk X Microprogram -
directory fmins file -
DF700S disk 01 - disk X -
fmins -
DF700H disk 01 - disk X -
fmins -
DF700XS disk 01 - disk X -
fmins -
ENC online update ENC/SENC
overwrite firmware
offline update file
overwrite
NAS
NOTE : Do not change a name of the unified version directory or directory in a stratum
under the unified version directory. The Microprogram becomes unable to be
installed if the directory name is changed.

MICRO 01-0090-01
1.4 Procedure for installation

(1) The point to be checked before installation
Make sure of the following before starting installation
y Make sure that the main switch of the subsystem is turned on. If it is turned off, turn it on
to start the subsystem.
y When performing the new installation, the subsystem does not become ready because the
microprogram is not installed.
(RB8400 Download failed is displayed on the Information Message.)
y Make sure that the microprogram has already been installed in the subsystem and the READY
LED (green) on the front bezel is on. When it is blinking at high speed, do not make the
updating work at the maximum of 30/50 minutes until it lights on because the ENC/SENC
firmware is being downloaded.
Besides, make sure that the WARNING LED (yellow) on the front bezel is not on. When the
microprogram is not installed, install it newly referring.
y Make sure that the status of system copy complete by Information Message window in the
WEB window.
If it is in the middle of system copy, please wait until that is completed and update
installation of microprogram.
(2) Procedure for new installation

(a) Set the operation mode in the Maintenance Mode. (See Chapter 3. The Maintenance Mode
Operation Procedure (WEB 03-0000).)
(b) Connect the LAN cross cable to the subsystem LAN connector for maintenance and connect
the subsystem to the Web. (See Subsection 3.1 Procedure to WEB connection (TRBL 03-
0000).)
(c) Click Maintenance, Setup, and Microprogram in this order in the Web window.
A [User Name] and a [Password] may be requested at the time of Web connection or Web
[Password].

MICRO 01-0100-01
(d) When the Microprogram Setup window is displayed, check the Initial Setup radio button of
the Installation Mode.
(e) Set the microprogram path.

Specify the Unified version directory(1) in which the microprogram that has been copied to
the service PC is stored.
When the Select button is clicked, the Select Microprogram window is displayed. Select
the Unified version directory in which the microprogram is stored and click the Open
button.
NOTE : If the window is not displayed, the JRE 1.3.1 03 may have not been installed or
the installation of it may have failed.
Perform the installation of the JRE1.3.1 03 (See 1.3 Preparation for
installation of microprogram (MICRO 01-0020).) again.

MICRO 01-0110-01
(f) Click the [Install] button to install the microprogram.
(g) The following window that asks for confirmation is displayed. When the [OK] button in the
window is clicked, the installation is started.
(h) When the installation is completed, the completion window is displayed. Click the [OK]
button.

MICRO 01-0120-01
(i) Go to the Maintenance Mode window by clicking To Maintenance Mode Top in the
Microprogram Setup window.
(j) Change the mode from Maintenance to Normal by clicking the [Go to Normal Mode] button.
(k) When the [Go to Normal Mode] button is clicked, the following window is displayed.
(l) Click the [OK] button.

MICRO 01-0130-01
(m) The subsystem becomes ready in about four minutes.

Make sure that the READY LED of the front bezel is on.
If the READY LED does not come on, the installation may have failed. Perform the
installation over again.
(3) Update Installation of Microprogram

Please execute (3-1) and (3-2) to the update installation.
Note: Do not perform the update installation of the microprogram while the READY
LED (green) is blinking at high speed (for the maximum of 30 to 50 minutes).
(3-1) Procedure for download

(a) Connect the LAN cross cable to the subsystem LAN connector for maintenance and connect
the subsystem to the Web. (See Subsection Troubleshooting 3.1 Procedure to WEB
connection (TRBL 03-0000).
(b) Start the Storage Navigator Modular and set the operation mode in the Management Mode.
(See Subsection System Parameter 1.1 (3)(b) Changing the Maintenance Mode (SYSPR 01-
0050).))
(c) Click an icon of the disk array subsystem you want to set in the main window.

MICRO 01-0140-01
(d) Select [Tools] [Configuration Settings] in the unit window or click [ : Configuration
Settings] button.
(e) Click the [Boot Option] tab.
(f) Read in the microprogram to the service PC in which Storage Navigator Modular is installed.
Click the [Read] button.
When a microprogram revision is displayed in the [Revision(Read)] box, the microprogram has
already been read in. When only the Unified version directory(1) storing the microprogram is
specified, the whole microprogram is read in automatically.
(g) Since a message asking for confirmation whether or not to read in the microprogram, click
the [OK] button.

MICRO 01-0150-01
In the case where the microprogram has already been read in, the message asking for the
confirmation is displayed. When you click the [OK] button, the microprogram is overwritten.
When you abort the reading in, click the [Cancel] button.
When you eliminate the microprogram that has already been read in to the computer, click
the [Delete] button. Since the message asking for confirmation is displayed, click the [OK]
button.
(h) Since a window for specifying the directory in which the microprogram to be read in is stored
is displayed, specify the Unified version directory(1) . When you click the [OK] button,
reading in of the microprogram is started.
Examples of the path entry are shown below.
When using Windows:
c:/diskarray-microprogram/microprogram/micro/0710A
When using Solaris, IRIX, HP-UX, or Red Hat Linux:
diskarray-microprogram/microprogram/micro/0710A
Unified version directory in the hard disk in

which the micro program is copied.

MICRO 01-0160-01
(j) Since a message is displayed when the reading in of the microprogram is completed, click the
[OK] button.
The revision of the microprogram that has been read in is displayed in the [Revision(Read)] box.
(k) Click the [Download] tab.

(l) The confirmation window is display. Click the [OK] button.

The confirmation window is display. Click the [Yes] button.

MICRO 01-0170-01
The download of the microprogram starts by clicking the [Yes] button, and the dialog is
displayed.
When you abort the downloading, click the [Cancel] button.

A message asking for confirmation is displayed. When you click the [OK] button, the
downloading is aborted.
When you click the [Cancel] button, the downloading is continued.
(m) Since a message is displayed when the downloading is completed normally, click the [OK]
button.
NOTE : After the microprogram is downloaded, be sure to restart the disk array
subsystem or replace the microprogram. If the Control Unit board is replaced
in the online mode before restarting the disk array subsystem or replacing the
microprogram, the replaced Control Unit may be detached. When the
subsystem is burdened with a heavy I/O load by a host at the time of the
downloading, the downloading may be terminated abnormally. Perform the
downloading again.

MICRO 01-0180-01
(3-2) Replacing the microprogram

Replace the microprogram that was downloaded to the disk array subsystem with the
microprogram installed in the Control Unit. When making replacement, be sure to replace
the microprograms of the both Control Units 0 and 1. When the microprogram of one of the
Control Units is replaced and the unit window of Storage Navigator Modular is closed, the
unit window may be opened no more. If the unit window becomes unable to be opened,
replace the microprogram after changing the registration to that in which only the Control
Unit whose microprogram has not be replaced is registered.
(a) Select [Tools] [Configuration Settings] in the unit window or click [ : Configuration
Settings] button.
(b) Click the [Micro Update] tab.

MICRO 01-0190-01
(c) Select the Control Unit whose microprogram is to be replaced and click the [Replace] button.
(d) The confirmation window is display. Check if the selected Control Unit is correctly displayed
and click the [OK] button.

Click the [OK] button according to the dialog message.

MICRO 01-0200-01
(e) When the replacement of the microprogram terminates normally, a completion message is
displayed. When the [OK] button is clicked, the revision of the replaced microprogram is
updated and the window is displayed.
(f) Replace the microprogram in the other Control Unit according to the procedure (c) to (e).
When replacement of the both Control Units is terminated normally, the microprogram
replacement of the disk array subsystem is completed.
NOTE : When the replacement of the microproram is made for only one of the dual
Control Unit, the disk array subsystem is put in the status in which a warning is
issued. The warning is called off when the other one of the dual Control Unit is
replaced. When you replace the microprogram, be sure to make the
replacement for the both Control Units continuously.

MICRO 01-0210-01
1.5 Checking the start and the termination of the ENC/SENC firmware automatic download
The ENC/SENC firmware is a function that is managed as a part of the microprogram and
checks the version of all ENC/SENC firmware in the subsystem when the subsystem starts or
the SENC is replaced, and downloads it automatically if necessary.
(1) Opportunity to start the automatic download

The ENC/SENC firmware starts the download automatically in the following opportunities.
<Start-up Opportunity>
When the main switch of the subsystem is turned on, and the subsystem enters the READY
status
When rebooting on remote
When rebooting automatically
When rebooting the Control Unit in the maintenance mode
<Maintenance Opportunity>
When the Control Unit is inserted online
When the ENC Unit/SENC Unit are inserted online
When the chassis frame is added online
When the microprogram is changed online
When the ENC microprogram automatic download function is enabled
When the following warnings are released before starting the automatic download
Loop Warning/ENC Warning/Control Unit Warning/SNMP Warning/Disk drive Warning/PIN
Warning/Power Unit Warning/UPS Warning/Battery backup Unit Warning/Battery backup
circuit Warning/Fan Unit Warning
When the following warnings, which caused the abnormal termination of the automatic
download, are released
Loop Warning/ENC Unit Warning/Control Unit Warning/Disk drive Warning/ENC replacement
which occurred in the SES error

MICRO 01-0220-01
(2) Restriction items during the automatic download

Do not perform the following work during the ENC/SENC firmware automatic download.
Planned shutdown
Update installation of the microprogram from Storage Navigator Modular
Setting change of Boot Options by Storage Navigator Modular
Setting change of LAN by Storage Navigator Modular
Text file input of Boot Options of the configuration copy information by Storage Navigator
Modular
Unlocking of the priced options by Storage Navigator Modular
Setting change of SNMP by Storage Navigator Modular
Setting change of Cache Residency Manager by Storage Navigator Modular
Parts replacement
Adding optional components
Subtracting optional components
Relocation / Removal work
Execute the above-mentioned work after the ENC/SENC firmware automatic download is
completed.
(3) Checking the start messages and the termination messages of the automatic download.
When the download starts, it takes up to 30/50 minutes to terminate it.
NOTE : The download does not start when the subsystem is in the warning status.
Connect to the WEB and perform the recovery procedure for each WEB message
(Troubleshooting Chapter 4. Trouble Analysis by WEB Connection (TRBL 04-
0000)).
If the warning status is recovered and the subsystem is maintained in the
normal status for one minute, the download starts.
(a) Connect the LAN cross cable to the LAN connector for maintenance of the subsystem and
connect to WEB (Troubleshooting 3.1 Procedure to WEB connection (TRBL 03-0000).)
(b) Click [Information Message] in the main window menu frame in the normal mode.

MICRO 01-0230-01
(c) Check that there are the start message and the normal termination message displayed in
Information Message.
Table 1.5.1 Message Check
Message Content Reference
IZYS00 Automatic ENC microprgram Indicates that the automatic download started.
download start
IZYR00 Automatic ENC microprogram Indicate that the automatic download terminated normally.
download completed successfully
IZYQ00 Automatic ENC microprogram Indicate that the automatic download terminated
download failed abnormally.
<Message Check Example>

When it is normal (ENC Unit #0 and #1 are objects)
Automatic ENC microprogram download start
ENC#0 microprogram download start
ENC#0 microprogram download complete
Automatic ENC microprogram download completed successfully
When it is normal (when there is no object ENC Unit)
Automatic ENC microprogram download completed successfully
When it is abnormal
ENC alarm (Unit-01, ENC-1)
Loop alarm (Path-0, Loop-1)
:
ENC microprogram download error detected (Unit-01)
:
Automatic SENC microprogram download failed
(4) Recovery method when terminating abnormally after starting the automatic download.
(a) Perform the maintenance for the warnings which were output from the automatic download
start to the abnormal termination.
(b) Check the start message and the termination message of the automatic download again.

MICRO 01-0240-01

MICRO 01-0250-01
Chapter 2. Procedure for Recovery from a Failure

2.1 Procedure for recovery from a failure during installation
Identify a factor of the failure based on the statuses of the LEDs and follow the recovery
procedure concerned.
<Failure which causes system down>

LED status
WARNING LED ALARM LED Recovery procedure
Blinking On Turn on the power again, and perform the operation over again from the beginning.
If a recovery from the failure is not successful nevertheless, connect the WEB and
recover from the failure following the recovery procedure against each WEB message.
For the details, refer to Troubleshooting Chapter 4. Trouble Analysis by WEB
Connection (TRBL 04-0000).
Details of WEB error logs (Refer to Message Chapter 5. Flash Detected Messages (MSG 05-
0000) for the detail of content or recovery methods.)
Message code Message text Recovery procedure Remark
RB0000 Upload system error The configuration of the directory from which the
microprogram is installed on the client PC is incorrect.
RB0100 File remove error The file in the RAM disk on the device cannot be deleted.
RB0A00 Upload file SUM check error An error was detected in the file by SUM check.
RB3100 File open error The file in the RAM disk on the device cannot be opened.
RB3200 File read error The file in the RAM disk on the device cannot be read.
RB3500 Bad block ID The block ID is illegal.
RB7000 Program size too large The program size is too large for the storage capacity.
RB8100 Install failed The writing to all the system drives failed.
RB8300 Empty system retry full install The updating installation cannot be done because the
microprogram is not installed.
RBA000 Down grade check NG A downgrade of the program was detected.
RBC000 No drive available The access to all the system drives is disabled.
RBC10x Drive block size error The drive block size is the other than 512 bytes. In the case of
(Unit-0, HDU-x) Newly Installing
Microprogram
RBC1xy Drive block size error The drive block size is the other than 512 bytes. In the case of
(Unit-x, HDU-y) Updating
Microprogram
RBC20x Unknown drive The system area size is larger than the drive capacity. In the case of
(Unit-0, HDU-x) Newly Installing
Microprogram
RBC2xy Unknown drive The system area size is larger than the drive capacity. In the case of
(Unit-x, HDU-y) Updating
Microprogram

MICRO 02-0000-01
<Install partially complete (The installation of some of the Disk Drives failed.)>
LED status
WARNING LED ALARM LED Recovery procedure
Off(*1) Off It may be a Disk Drive failure. For the details, refer to Chapter 3. Procedure for
Isolating Cause of Disk Drive Failure when Install partially complete Message Is
Output (MICRO 03-0000).
*1 : When a beep of the buzzer is stopped by a pressing of the TRACE SW/BUZZER OFF SW, the process is
continued automatically and the blinking of the WARNING LED is stopped.
The subsystem is placed in the READY status.
Details of WEB error logs

Message code Message text Recovery procedure Remake
RB8200 Install partially complete The installation of some of the Disk Drives failed.

MICRO 02-0010-01
Chapter 3. Procedure for Isolating Cause of Disk Drive Failure

when Install partially complete Message Is Output
The message, Install partially complete is displayed in the Web window when a disk drive,
which has failed in the installation of the program, exists. You can see that the disk drive is
in a state of Install partially complete through the status of the LED. Since they show that
a Disk Drive failure may have occurred, make the following analysis and take necessary
actions.
Analysis start
When the subsystem does not become

Has the Device got ready with the READY, and turn off and on the main
READY LED of the Front Bezel on? No switch successively.
When it is high-speed blinking,
wait up to 30/50minutes.
Yes
No
Did the system copying start?(*1)
Yes
No Disk Drive failure occurred. No Did the system copying terminate

(No recovery action is needed.) normally?(*2)
Yes
No Disk Drive failure occurred.
(No recovery action is needed.)
A Disk Drive failure occurred.

The system copying terminated
abnormally.
Replace the Disk Drive.
Analysis completion
*1 : Refer to 3.1 Procedure for Checking whether system copy operation occurred (MICRO 03-0010).
*2 : Refer to 3.2 Procedure for checking the status of system copy complete (MICRO 03-0020).

MICRO 03-0000-01
3.1 Procedure for Checking whether system copy operation occurred

You can verify whether the system copy operation has occurred by viewing the Information
Message window in the WEB window.
Refer to this place.
When the occurred of system copy

MM/DD/YYYY HH:MM:SS Cx I140xy System copy started (Unit-x, HDU-y)
Date Time Detect Controller # x : Unit ID #

y : Disk Drive #
When the not occurred of system copy
The message above is not displayed but a message I10000 Subsystem is Ready is displayed.

MICRO 03-0010-01
3.2 Procedure for checking the status of system copy complete

You can verify whether the system copy operation has occurred by viewing the Information
Message window in the WEB window.
Refer to this place.
When the normal completed of system copy

MM/DD/YYYY HH:MM:SS Cx I10000 Subsystem is Ready
MM/DD/YYYY HH:MM:SS Cx I141xy System copy completed (Unit-x, HDU-y)
Date Time Detect Controller # x : Unit ID #, y : Disk Drive #

System copy start message
System normal completed message
Ready report message of unit
When the not occurred of system copy

MM/DD/YYYY HH:MM:SS Cx I10000 Subsystem is Ready
MM/DD/YYYY HH:MM:SS Cx I142xy System copy failed (Unit-x, HDU-y)
Date Time Detect Controller # x : Unit ID #, y : Disk Drive #

System copy start message
System copy failed completion message
Ready report message of unit

MICRO 03-0020-01
.
FE-95DF748-00
System Parameter
Chapter 1. Setting (Storage Navigator Modular).......................................................... SYSPR 01-0000
Chapter 2. Setting Host Group..................................................................................... SYSPR 02-0000
Chapter 3. Setting the RAID/LU/Spare Disk ................................................................ SYSPR 03-0000
Chapter 4. Setting Configuration Information............................................................... SYSPR 04-0000
Chapter 5. Setting Host Connection Parameters ......................................................... SYSPR 05-0000
Chapter 6. Setting an Extra-cost Optional Feature ...................................................... SYSPR 06-0000
Chapter 7. System Parameter Setting List................................................................... SYSPR 07-0000

SYSPR 00-0000-01

SYSPR 00-0010-01
Chapter 1. Setting (Storage Navigator Modular)

This chapter explains method of setting the subsystem parameters using Storage Navigator
Modular.
The procedures for setting device parameters are described below.
START
When the microprogram has not been installed in the subsystem,

install it newly. (See Microprogram Chapter 1. Installation of
Microprogram (MICRO 01-0000).)
Usually, the subsystem is shipped with the microprograms installed.
Make a connection to the subsystem using Storage Navigator

Modular. (See 1.1 Procedure for connecting Storage Navigator
Modular with the subsystem (SYSPR 01-0010))
Make the setting of the system parameter from the Storage Navigator
Modular. (See Chapter 7. System Parameter Setting List (SYSPR
07-0000))
Make the setting of the Host Group from the Storage Navigator
Modular. (See Chapter 2. Setting Host Group (SYSPR 02-0000))
Make the setting of the RAID/LU/Spare Disk from the Storage

Navigator Modular. (See Chapter 3. Setting the RAID/LU/Spare
Disk (SYSPR 03-0000))
Make the setting of the Configuration Information from the Storage

Navigator Modular. (See Chapter 4. Setting Configuration
Information (SYSPR 04-0000))
Make the setting of the special mode from the Storage Navigator
Modular. (See Chapter 5. Setting Host Connection Parameters
(SYSPR 05-0000).)
Make the setting of the priced optional feature from the Storage
Navigator Modular. (See Chapter 6. Setting an Extra-cost Optional
Feature (SYSPR 06-0000).)
Restart a device.
END

SYSPR 01-0000-01
1.1 Procedure for connecting Storage Navigator Modular with the subsystem
The procedure for connecting Storage Navigator Modular with the subsystem is shown below.
START
(a) Check of the LAN environment setting for the PC
(b) Connection of the LAN cable
(c) Registration of a new DF in the Storage

Navigator Modular
END
(1) Checking the LAN environment setting

(a) Make sure that the Storage Navigator Modular has been installed. (Make sure that the
activation file startsnm.bat exists.)
(b) Check the LAN environment setting for the PC
Make sure that the following settings have been made, or change the settings to the
following.
For the maintenance PC, set the IP address to 10.0.0.xxx as shown in No. 1.
If the maintenance PC cannot establish a connection, set the value to 192.168.0.xxx as
shown in No. 2.
Subsystem (LAN maintenance port) Maintenance PC

No.
IP Address Subnet Mask IP Address Subnet Mask
1 CTL 0: 10.0.0.16 255.255.255.0 10.0.0. 255.255.255.0
CTL 1: 10.0.0.17 (At the time of shipment) (xxx is any value from 1 to
(At the time of shipment) 254 except 16, 17.)
2 CTL 0: 192.168.0.16 255.255.255.0 192.168.0. 255.255.255.0
CTL 1: 192.168.0.17 (xxx is any value from 1 to
254 except 16, 17.)

SYSPR 01-0010-01
Automatic change of network parameters of the LAN Maintenance Port.

Since communication is not performed normally when the network addresses of the LAN User
Management Port and the LAN Maintenance Port are the same, two sets of fixed values of
the network parameters for the LAN Maintenance Port are prepared and either of the two
sets is automatically given to the LAN Maintenance Port depending on the network
parameters of the LAN User Management Port.
When the network address of the LAN User Management Port is set as 10.*.*.*, that of the
LAN Maintenance Port is changed as shown in table below. [maybe bring table to here?]
NOTE : However, if the network address of the LAN device connected to LAN User
Management Port via the Gate Way accords with that of LAN Maintenance Port,
they will collide each other, disabling to communicate normally.
(1) When the LAN User Management Port address is set to other than
10.*.*.*, 10.0.0.(0 to 255) cannot be used for the IP address for LAN
device to be connected to LAN User Management Port through a gateway.
Therefore, set the IP address for the LAN Device to other than 10.0.0.(0
to 255).
(2) When the LAN User Management Port address is set to 10.*.*.*,
192.168.0.(0 to 255) cannot be used for the IP address for LAN device
to be connected to LAN User Management Port through a gateway.
Therefore, set the IP address for the LAN Device to other than
192.168.0.(0 to 255).
Control Unit#0 Control Unit#1

Network parameter
Description LAN Maintenance Port LAN Maintenance Port
< Fixed IP > < Fixed IP >
IP Address The IP Address is changed/set 192.168.0.16 192.168.0.17
up.
Subnet Mask The Subnet Mask is changed/set 255.255.255.0 255.255.255.0
up.
Default Gateway The Default Gateway is 0.0.0.0 0.0.0.0
changed/set up.
DHCP Enable/Disable of the DHCP OFF OFF
function is set up.

SYSPR 01-0020-01
(2) Connecting the LAN cross cable

Connect the Control Unit #0 LAN Maintenance port of the subsystem and the LAN card of a PC.
(a) For the RKM/RKS
RKM /RKS
U7 rack frame
Control Unit #0
PC
LAN cross cable
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Cover LAN connector
Figure 1.1.1 Connecting the LAN cable (for the RKM/RKS)

SYSPR 01-0030-01
(3) Registering the newly introduced DF in the Storage Navigator Modular

(a) Activating the Storage Navigator Modular
(i ) Execute the batch file or shell script for activating the Storage Navigator Modular.
In the case of Windows, activate the batch file, startsnm.bat.
(ii) The Storage Navigator Modular is activated in the Normal Mode and the main window is
displayed(1).
In the case of Windows, the prompt window is also displayed.

The prompt window has nothing to do with operation of Storage Navigator Modular. But
dont close the prompt screen. It is unusually finished.
The icon can be minimized automatically when Program Quitting is selected from the
properties of the batch file.
You can execute the display of the Storage Navigator Modular Operation Mode and state of
the failure monitoring and the following functions in the main window.
For the operation of each function, refer to the page explaining each function.
Registration of the disk array subsystem (registration, deletion, change, and properties
display)
Execution of the failure monitoring and setting of the failure monitoring option
Change of the Operation Mode
Display of the version
1 : The mode change cannot be done at the time of the initial activation of the Storage Navigator Modular. A
registration of a password validates the mode change.

SYSPR 01-0040-01
(b) Changing the Maintenance Mode

Storage Navigator Modular has three Active Modes, that is, the Normal Mode, Management
Mode, and Maintenance Mode. In the Normal Mode, the program displays the configuration
and statuses of the disk array. In the Management or Maintenance Mode, it can set the
configuration of the disk array in addition to the function in the Normal Mode.
( i ) Changing the Normal Mode to the Maintenance Mode
Change the Operation Mode from the Normal Mode to the Maintenance Mode.
When the log-in has been made in the Normal Mode, [Normal Mode] is displayed as a
detailed information of the [Operation Mode] in the upper part of the main window.
c In the main window, position the focus ([ ]) on the icon [ ] of the array subsystem
register by pressing the [Tab] key, and then press the Ctrl, Shift, and E keys at the same
time.
Maintenance Mode is displayed in the Operation Mode field at the top right on the Main
screen, and the Storage Navigator Modular operates in the maintenance mode.

SYSPR 01-0050-01
(c) Registering the disk array subsystem

Register the disk array subsystem to be operated in order to operate it from the Storage
Navigator Modular. A registration of a non-existent disk array subsystem cannot be done.
(i ) Select [Add] in the main window or click [ : Add].

SYSPR 01-0060-01
(ii) Enter the information for the registration and click the [OK] button. Alternative, click
the [Detail] button.
NOTE : y The disk array subsystem with the dual system can also be used with a single
Controller only. [Array Unit Type] is used to select a type of the subsystem to
be connected. For [IP Address, Host Name, or Device Name], enter information
of the Controller connected to the maintenance PC.
y Enter the IP address only in the Control Unit to which the LAN cable is
connected. If the IP address is entered in a Control Unit to which the LAN
cable is not connected, an error is caused.
Simple window Detail window
[Group] : Specify group names when applying group control to the disk array
subsystems. Specify each of them with16 or less half size
alphabetic characters, numerals, and/or symbols (- and/or _).
The maximum number of the groups allowed to be registered is
200. The entrance of the group names is not necessary when the
group control is not applied to the disk array subsystems.
[Name] : Specify a disk array subsystem name to be registered. Specify it
with16 or less half size alphabetic characters, numerals, and/or
symbols (- and/or _).
[Connection] : Select TCP/IP (LAN) connection to be used for the disk array
subsystem. RS232C is not supported in DF700.
When connecting the LAN, select the [TCP/IP (LAN)], and then
specify the [IP Address], [Host Name], and [IP Address] or [Host
Name] of controller 0 and 1.

SYSPR 01-0070-01
[Error Monitoring] : Set whether to apply the failure monitoring or not.

Checking off the box : The failure monitoring is applied.
Not checking off the box : The failure monitoring is not applied.
(iii) When a message informing of a completion of the registration is displayed, click the [OK]
button.
(iv) The updated main window is displayed.
When an entry has been made in [Group Name], the group name is displayed in the tree
diagram on the right side of the window. A clicking on the group name displays an icon(s)
of the disk array subsystem(s) registered in the group.
There are two types of icon of the disk array subsystem as shown below: an icon for the
dual system and that for the single system.
y Icon for the dual system :
y Icon for the single system :
The icons of the disk array subsystem are displayed in the order of the registration of the
disk array subsystems.

SYSPR 01-0080-01
(d) Changing the Maintenance Mode to the Normal Mode

Change the Operation Mode from the Maintenance Mode to the Normal Mode.
When the log-in has been made in the Maintenance Mode, [Maintenance mode] is displayed as
a detailed information of the [Operation Mode] in the upper part of the main window.
(i ) Select [Tool] [Operation Mode] [Change] in the main window or click [ : Change
Operation Mode].
(ii) The message asking for the confirmation is displayed. Click [OK] button.
(iii) [Normal Mode] is displayed for the [Operation Mode] in the upper part of the main
window. When the unit window is displayed, the Storage Navigator Modular operates in
the [Normal Mode].

SYSPR 01-0090-01
Chapter 2. Setting Host Group

y Make a setting for making the subsystem recognized by a server.
y The setting of the host group must be made for each port.
2.1 Before setting host group

(1) Turn on the power supply.
(2) Start the Storage Navigator Modular and set the Operation Mode in the Maintenance Mode.
For the procedure for changing to the Maintenance mode, refer to 1.1 (3)(b) Changing the
Maintenance Mode (SYSPR 01-0050), Registering the newly introduced DF in the Storage
Navigator Modular in Subsection 1.1.
(4) On the unit window, click the [Logical Status] tab.

SYSPR 02-0000-01
2.2 Setting of option

There are two methods for setting the options, that is, the simple setting and detail setting.
When making the simple setting, select elements of an environment of the host computer to be
connected. When the selection is made, the host group options (host connection mode 1 and 2)
necessary for the host computer to be connected are set automatically.
When making the detail setting, directly set the necessary host group options (host connection
mode 1 and 2) in the same way as conventional one.
(1) Simple setting

Set the host group options (host connection mode 1 and 2) necessary for the host computer to
be connected by selecting elements of the environment of the host, that is, platform,
alternative path, fail-over, and additional parameter. Since some host environments require
detail setting as well as the simple setting, refer to the table of host connection parameters.
(a) Click the [Logical Status] tab in the unit window.
(b) Display the [000:G000] by clicking the port through a controller for which you want to set the
host connection mode. Then display the options and logical unit by double clicking on the
[000:G000] and select the options.
(c) Click the [Simple Setting] button that is displayed at the lower right part of the window.

SYSPR 02-0010-01
(d) Option (Simple)Property window is opened.

Select [Platform], [Alternative Path], and [Fail-Over] according to an environment of the host
to be connected.
Table 2.2.1 Simple Setting Item List

Contents
No. Menu item Factory setting
Parameter How to set
1 Platform Not specified Select one of Not selected
HP-UX the items
Solaris
AIX
WindowsNT
Windows2000
Windows2003
Linux
Tru64
2 Alternative path Not specified Select one of Not selected
PV Link the items
HDLM
VxVM
3 Fail-over Not specified Select one of Not selected
MC/ServiceGuard the items
Sun Cluster
VCS
HACMP
MSCS
Tru Cluster

SYSPR 02-0020-01
(e) Click the [Additional Parameters] button.
(f) The Additional Parameters window is opened. Select the [Item] as occasion demands and
click the [OK] button.
Table 2.2.2 Simple Setting Item List

Contents
No. Menu item Factory setting
Parameter How to set
1 Additional Parameters Logical Unit Number more than or equals to 8 can be Select Not selected
recognized by HP-UX.
TrueCopy remote replication is used by HP-UX
VERITAS Database Edition /Advanced Cluster for Oracle
RAC (Solaris) is used
Egenera BladeFrame is used
(g) Click the [Detail] button as occasion demands.

SYSPR 02-0030-01
(h) Select [Host Connection Mode 1] and [Host Connection Mode 2] and click the [OK] button.
(i) Click the [OK] button in the Option (Detail) window.

SYSPR 02-0040-01
(j) The setting that has been made is displayed.

Make sure that the selected host environment (platform, alternative path, and fail-over) and
the Additional Parameter are reflected in the display. Besides, when you have set the host
connection mode 1 and 2 directly, make sure that the mode that has been set is reflected in
the display.
Check if the setting made is

reflected in the display
The necessary host connection modes

1 and 2 have been selected.
(k) Make the settings for the rest of the ports in the same way.

SYSPR 02-0050-01
(2) Detail setting

(a) Display the 000:G000 by double clicking the [Controller] which is an object of the setting and
then double clicking the [Port] in the unit window.
Display the [Option] and [Logical Unit] by clicking the [000:G000], and then click the
[Option].
(b) Click the [Detail Setting] button that is displayed at the lower right part of the window.

SYSPR 02-0060-01
(c) The Detail Setting window is opened.

Set a [Host Connection Mode 1 (select one mode)] and a [Host Connection Mode 2 (more than
one mode can be selected)].
Host Connection Mode 1 : See No. 1 in Table 2.2.3, List of Host Group Setting Items.
Host Connection Mode 2 : See No. 2 in Table 2.2.3, List of Host Group Setting Items.
Table 2.2.3 List of Host Group Setting Items

Contents
No. Menu item How to Factory setting
Parameter
set
1 Host Connection Mode 1 Standard Mode : Open system emulation mode Select Basic mode
(Only one mode can be Open VMS Mode : VMS mode
selected.) TRESPASS Mode : TRESPASS mode
Wolfpack Mode : WolfPack mode
2 Host Connection Mode 2 HP-UX Mode: Select Not selected
(Two or more modes may be This mode makes LUs, whose LU numbers are 8 up to 63, recognized
selected.) when the subsystem is connected to the HP server.
PSUE Read Reject Mode :
Set it when the fence level of TrueCopy remote replication is used with
Data and the pair status suppresses the read access to P-VOL at the
time of PSUE transition.
UA (06/2A00) suppress Mode : Select Not selected
Unit attention (06/2A00) is suppressed.
NACA Mode : Select Not select
Supports NACA (Normal Auto Contingent Allegiance) that is a standard
on SCSI-3.
HISUP OFF Mode : Not use Select Not selected
Reset Propagation Mode : Select Not select
Set it when the own port also resets the command while another
port received the command reset instruction.
Unique Reserve Mode 1 : Select Not select
Supports Persistent Reserve command.
ASL Report Mode (Active/Passive Group) : Not use Select Not selected
ASL Report Mode (Active/Passive) : Not use Select Not selected
ASL Report Mode (Active/Active) : Not use Select Not selected
Port-ID No Report Mode: Not use Select Not selected
Port-ID Conversion Mode: Select Not selected
When using the DBE_AC with direct connection.
Tru Cluster Mode: Select Not selected
When using Tru Cluster, you need to set this mode.

SYSPR 02-0070-01
Contents
No. Menu item How to Factory setting
Parameter set
2 Host Connection Mode 2 Product Serial Response Mode : Select Not select
(Two or more modes may be This mode enables each LU to be assigned a unique DID in the SUN
selected.) Cluster 3.0 system.
Same Node Name Mode : Select Not selected
When using SANsurfer, you need to set this mode.
CCHS Mode : CCHS convert Mode Select Not selected
SPC-2 Mode : Select Not selected
Set it when it indicates the conformity to SPC-2 in the Inquiry
data and responds to Inquiry. Do not set it usually.
(d) The confirmation window is display. Click the [OK] button.

SYSPR 02-0080-01
(e) The detail of the setting that has been made is displayed.
Make sure that the setting that has been made is reflected on the display.
Make sure whether the setting that

has been made is displayed here.
(f) Make the setting for the other ports in the same way.

SYSPR 02-0090-01
2.3 Setting LU mapping

Set mappings of the Port ID, and Host LUN for a LUN so that they are used in the configuration
set by a host computer. The setting of the mapping can be modified while an I/O is being
executed using the existing mapping setting. However enabling mapping stops host I/O
temporarily.
(1) In the unit window, click [Mapping Mode] after double clicking [Access Mode], and then select
[Disable] from the [Mode] menu.
Click the [Modify] button that is displayed at the lower right part of the window.
(2) Since the Modify Mapping Mode dialog box is displayed, select [Enable] for the [Mapping Mode]
and click the [OK] button.

SYSPR 02-0100-01
(3) The confirmation window is display. Click the [OK] button.
(4) In the unit window, display [000: G000] by double clicking the [Port XX] to be specified after
double clicking the [Host Groups].
Display the [Option] and [Logical Unit] by clicking the [000:G000], and then click the [Option].

SYSPR 02-0110-01
(5) Click the [Modify] button that is displayed at the lower right part of the window.
(6) Select one H-LUN from the [H-LUN] list of the mapping. Then select one LUN you want to map
on the H-LUN from the list of the [Available Logical Units] and click the [ ] button.
The H-LUN and LUN that were selected are moved to the [Mapping Information] list.


SYSPR 02-0120-01
The mapping information is updated and the following window is displayed.

SYSPR 02-0130-01
Chapter 3. Setting the RAID/LU/Spare Disk

This function performs the RAID group setting, LU setting, LU formatting, and Spare Disk
setting. Further, it can make the following settings.
Procedure Flow diagram for setting RAID groups, LUns and Spare Disks.
START
Preparing of setting
[Procedure c]Preparing of setting (SYSPR 03-0030)
No Is change of RAID group No

Is a RAID group newly created?
required?
Yes Yes
Preparing of setting RAID group Preparing of setting RAID group
[Procedure d-A]RAID group setting preparation or [Procedure d-A]RAID group setting preparation or
confirmation (SYSPR 03-0050) confirmation (SYSPR 03-0050)
Deleting RAID group

[Procedure d-D]Deleting RAID group (SYSPR 03-
0100)
Setting RAID group
[Procedure d-B]Setting RAID group (SYSPR 03-0060)
Verifying RAID group

[Procedure d-C]Verifying RAID group (SYSPR 03-0090)
Verify RAID group OK? No
Yes
Is a LU newly created? No
A To SYSPR 03-0010
Yes
Preparing of setting LU
[Procedure e-A]Preparing of setting LU (SYSPR 03-0140)
Setting LU
[Procedure e-B]Setting LU (SYSPR 03-0150)
Verifying LU
[Procedure e-C]Verifying LU (SYSPR 03-0220)
Verify LU OK? No
B To SYSPR 03-0010
Yes
Formatting LU
[Procedure e-F]Formatting LU (SYSPR 03-0280)
C To SYSPR 03-0020
Figure 3.1.1 (1/3) Setting Flow the RAID/LU/Spare Disk

SYSPR 03-0000-01
B To SYSPR 03-0010 A To SYSPR 03-0010
Is change of LU required? No
C To SYSPR 03-0020
Yes
Delete Does the default controller that Default Controller change

controls the LU have to be changed?
Or LU Deleting Invalidate?
Deleting LU The change of the controller in charge of a default LU

[Procedure e-D]Deleting LU (SYSPR 03-0230) [Procedure e-E]The change of the controller in charge of a
default LU (SYSPR 03-0260)
Preparing of setting LU
[Procedure e-A]Preparing of setting LU (SYSPR 03-0140) C To SYSPR 03-0020
Setting LU
[Procedure e-B]Setting LU (SYSPR 03-0150)
Verifying LU
[Procedure e-C]Verifying LU (SYSPR 03-0220)
No
Verify LU OK?
Yes
Formatting LU
[Procedure e-F]Formatting LU (SYSPR 03-0280)
C To SYSPR 03-0020

SYSPR 03-0010-01
From SYSPR 03-0000 and

SYSPR 03-0010 C
Is Spare Disk change required? No
Yes
Preparing of setting Spare Disk
[Procedure f-A]Preparing of setting Spare Disk (SYSPR 03-0350)
Setting Spare Disk

[Procedure f-B]Setting Spare Disk (SYSPR 03-0360)
Verifying Spare Disk Deleting Spare Disk

[Procedure f-D]Verifying Spare Disk (SYSPR 03- [Procedure f-C]Deleting Spare Disk (SYSPR 03-
0390) 0380)
No
Verify Spare Disk OK?
Yes
END

SYSPR 03-0020-01
3.1 Preparation of RAID/LU setting

[Procedure c]Preparing of setting
(1) Start the Storage Navigator Modular and set the operation mode to Management Mode(1).

SYSPR 03-0030-01
1 : For details of the setting method, refer to the Subsection 1.1 (3)(b) Changing the Maintenance Mode (SYSPR 01-
0050)

SYSPR 03-0030-01
(3) Check that the unit is ready.
Displayed in green in the ready state.
(4) y When newly creating or changing a RAID group, go to 3.2 RAID group setting (SYSPR 03-
0050).
y Go to 3.3 Setting of LU (SYSPR 03-0140) when changing an LU without changing a RAID
group.
y When neither the RAID group nor LU is to be changed, select [Mode] [Exit] or click [ :
Exit].

SYSPR 03-0040-01
3.2 RAID group setting

This setting is used to set, delete and reference a RAID group. This function can be used in
the device ready state. (The unit does not need to be re-booted.)
NOTE : Deletion of a RAID group indicates that all the user data of the deleted RAID
group are lost. Before deleting the RAID group, back up the user data.
For the RAID group and RAID levels which can be set by this device, refer to
Theory 4.7 Setting RAID Group (THEO 04-0260) in the Theory Part.
[Procedure d-A]RAID group setting preparation or confirmation
(1) Click the [Logical Status] tab in the unit window.
RAID groups and logical units defined for the disk array subsystem are displayed.
[RAID Group] : Information on all RAID groups defined for the disk array
subsystem are displayed.
[Logical Unit] : Information on all Logical Units defined for the disk array

SYSPR 03-0050-01
[Procedure d-B]Setting RAID group
(1) When creating a RAID group by selecting a drive manually
(a) Select [Settings] [RAID Group] [Create], or click the [ : RAID Group Settings] button.
(b) Since the Create RAID Group dialog box is displayed, select or enter the [RAID Level] and
[Drive Configuration] (drive type, combination, and number of parity groups).
(c) Select [Manual Selection] for the [Drives] and click the [Select] button.
NOTE : When setting a RAID group by selecting [Automatic Selection] for the [Drives],
select or enter the [RAID Level] and [Drive Configuration] (drive type, drive
capacity, combination, and number of parity groups) and click the [OK] button.
The drive is selected automatically after a message asking for confirmation is
displayed and a RAID group is set.

SYSPR 03-0060-01
(d) Since the Select Drives dialog box is displayed, select the drive you want to assign to a RAID
group from [Available Drives] by operating the [Shift] key.
(e) Move the selected drive to the [Drives to Use] box by clicking the [ ] button and click
the [OK] button.
(f) Since the Create RAID Group dialog box returns, click the [OK] button.
(g) The confirmation window is display. Click the [OK] button.(1)
When the capacity of the Disk Drive (single unit) to be created in the RAID group exceeds the
capacity of the Spare Disk in the subsystem, the error message is displayed.(1)
1 : Check the Disk Drive capacity (referring to Subsection 3.5 Checking the status of Disk Drive (SYSPR 03-0400).),
replace the Disk Drive with that having the appropriate capacity, and set the RAID group again.

SYSPR 03-0070-01
(h) The screen from which a RAID group was updated is displayed.
When setting the multiples RAID Group, return to the [Procedure d-B]Setting RAID group
(SYSPR 03-0060), and specify the rest of RAID Group to be set.
When verifying RAID group [OK], go to [Procedure e-A]Preparing of setting LU
(SYSPR 03-0140).
When verifying RAID group [NG], go to [Procedure d-D]Deleting RAID group
(SYSPR 03-0100).

SYSPR 03-0080-01
[Procedure d-C]Verifying RAID group
(2) The setting made in [Procedure d-B] can be referred to by double clicking on the icon of the
RAID group created.
When setting the multiples RAID Group, return to the [Procedure d-B]Setting RAID group
(SYSPR 03-0060), and specify the rest of RAID Group to be set.
When verifying RAID group [OK], go to [Procedure e-A]Preparing of setting LU
(SYSPR 03-0140).
When verifying RAID group [NG], go to [Procedure d-D]Deleting RAID group
(SYSPR 03-0100).

SYSPR 03-0090-01
[Procedure d-D]Deleting RAID group
NOTE : All user data is lost by deleting the RAID group and its associated LU. Backup
user data before deleting the RAID group.
NOTE : A specified RAID group can be deleted even if an LU is defined in the RAID
group.
However, the specified RAID group cannot be deleted when a unified LU(1) is
left in the RAID group. When deleting the specified RAID group that includes a
unified LU, do it after dissolving the unification of the unified LU in the
specified RAID group.
(a) Click the RAID group to be deleted, and select.

To delete more than one RAID group, click the RAID group you want to delete and click the
other RAID groups keeping the [Shift] key being pressed.
(b) Select [Settings] [RAID Group] [Delete].
1 : Support a function (LUN Expansion function) that creates a unified LU by combining LUs. The LUN Expansion
function is an optional function.
To use the LUN Expansion function, the P-002D-J304 is required separately. For the procedure to dissolve the
unification of the unified LU, refer to the manual supplied with the P-002D-J304.

SYSPR 03-0100-01
(c) If the confirmation message is displayed. Click the [OK] button.

When there is no formatted LU in a RAID group

SYSPR 03-0110-01
When there is a formatted LU in a RAID group

SYSPR 03-0120-01
(d) The screen from which selected RAID groups were deleted is displayed.
When setting the RAID group, go to [Procedure d-B]Setting RAID group (SYSPR 03-0060).

SYSPR 03-0130-01
3.3 Setting of LU
This setting is used to set, delete, reference and formatting an LU.
This function can be used in the device ready state.
NOTE : Changing (Deletion) of LU and formatting of LU indicates that all the user data
of the deleted RAID group are lost.
Before deleting the RAID group, back up the user data.
[Procedure e-A]Preparing of setting LU

[RAID Group] : Information on all RAID groups defined for the disk array
[RAID Group] : A number of the RAID group is displayed.
[RAID Level] : A RAID level that has been specified is displayed.
[Total Capacity] : A whole capacity of a RAID group is displayed.
[Free Capacity] : A remaining capacity of a RAID group is
displayed.
[Type] : A type of a drive assigned to a RAID group is
displayed.
[Logical Unit] : Information on all the logical units, to which the disk array unit
is assigned, is displayed.
[LUN] : A number of the logical unit (xxx) is displayed.
[Capacity] : A capacity specified for the logical unit is
displayed.
[RAID Group] : The RAID group defined as the logical unit is
displayed.
[RAID Level] : A RAID level of the RAID group defined as the
logical unit is displayed.
[D-CTL] : A number of a controller, which controls the
logical unit according to the default setting, is
displayed.
[C-CTL] : A number of a controller, which controls the
logical unit according to the current setting, is
displayed.
[Type] : A type of a drive defined as a logical unit is
displayed.
[Status] : A status of the logical unit is displayed.

SYSPR 03-0140-01

SYSPR 03-0140-01
[Procedure e-B]Setting LU
(1) Click the RAID group for which an LU is to be created, and then select [Settings] [Logical
Unit] [Create] or click [ : Create New Logical Unit].
(2) Enter the capacity value and select the controller that controls the LU using the Controller
boxes.
Simple Window Detail Window
For an LU number, the number of an LU to be created is displayed, and for a RAID group
number, the number of a RAID group to be created is displayed.
An LU with any number can be created.
When setting the LU, enter a number of the LU you want to create in the LU setting dialog box.

SYSPR 03-0150-01
(a) Capacity specification method

When explicitly specifying a value, select the [Specified Value] radio button and specify a
capacity (the number of blocks) using a decimal number. Besides, for the specification of
the number of blocks, refer to (c) Setting value of the number of logical blocks (SYSPR 03-
0170).
Besides, you can also enter the capacity value by the M byte or G byte in the case of Storage
Navigator Modular.
(b) Controller No. specification method

Select the [Controller 0] or [Controller 1] radio button and specify a Controller in charge of
an LU to be set (if the Controller is incorrectly specified, note that LU switching occurs and
performance is deteriorated).
Even if a Controller in charge is specified when a dual system is connected, nothing is
displayed when a single system is connected.
NOTE : If the dual active mode is selected in a dual system, a controller in charge
needs to be specified when setting an LU. Refer to the following diagram to
perform the setting of the LU for which the controller in charge was specified.
When changing the specification of the controller in charge, refer to the
[Procedure e-E]The change of the controller in charge of a default LU (SYSPR
03-0260) to change the controller in charge.
HOST HOST
#0 #1
CTL CTL
#0 #1
Normal condition
LU0 LU1 Abnormal condition

(You have to switch the
Dual system LU at Host side)
(Dual active mode)
y The function of Dual active mode

Specify a Controller which accesses an LU from a host computer for the
Controller in charge of the LU.
In an example of the above diagram, CTL0 and CTL1 are the controllers in
charge of LUs for LU0 and LU1 respectively. In this example, select the
CTL0 radio button at LU0 setting, and select the CTL1 radio button at
LU1 setting.

SYSPR 03-0160-01
(c) Setting value of the number of logical blocks

( i ) A logical unit can divide all RAID groups into up to 512 (RKS) and 2,048 (RKM).
(ii) Set the number of logical blocks set for each logical unit using the following multiples in
accordance with RAID levels.
Table 3.3.1 Number of Logical Blocks and RAID Levels

RAID level Logical block number Remake
RAID 0(2D) 4,096
RAID 0(3D) 6,144
RAID 0(4D) 8,192
RAID 0(5D) 10,240
RAID 0(6D) 12,288
RAID 0(7D) 14,336
RAID 0(8D) 16,384
RAID 0(9D) 18,432
RAID 0(10D) 20,480
RAID 0(11D) 22,528
RAID 0(12D) 24,576
RAID 0(13D) 26,624
RAID 0(14D) 28,672
RAID 0(15D) 30,720
RAID 0(16D) 32,768
RAID 1(1D+1D) 2,048
RAID 5(2D+1P) 4,096
RAID 5(3D+1P) 6,144
RAID 5(4D+1P) 8,192
RAID 5(5D+1P) 10,240
RAID 5(6D+1P) 12,288
RAID 5(7D+1P) 14,336
RAID 5(8D+1P) 16,384
RAID 5(9D+1P) 18,432
RAID 5(10D+1P) 20,480
RAID 5(11D+1P) 22,528
RAID 5(12D+1P) 24,576
RAID 5(13D+1P) 26,624
RAID 5(14D+1P) 28,672
RAID 5(15D+1P) 30,720
RAID 1+0(2D+2D) 4,096
RAID 1+0(3D+3D) 6,144
RAID 1+0(4D+4D) 8,192
RAID 1+0(5D+5D) 10,240
RAID 1+0(6D+6D) 12,288
RAID 1+0(7D+7D) 14,336
RAID 1+0(8D+8D) 16,384

SYSPR 03-0170-01
(iii) When dividing RAID groups into multiple logical units, set the sum total of the number of
logical blocks of each logical unit below the number of logical blocks per parity shown below.
However, when creating multiple parity groups in each RAID group, set them below the
number of logical blocks of one parity group multiplied by the number of parity groups.
(iv) The number of logical blocks of one parity group is shown below.
Table 3.3.2 Number of Logical Blocks of One Parity Group

Disk Drive capacity 71.3 G bytes 143.3 G bytes 245.7 G bytes 287.6 G bytes 393.4 G bytes
(*1) (*2)
Number of Number of Number of Number of Number of
RAID configuration Logical Blocks Logical Blocks Logical Blocks Logical Blocks Logical Blocks
RAID 0 2D 278,556,672 559,788,032 959,942,656 1,123,549,184 1,536,950,272
3D 417,835,008 839,682,048 1,439,913,984 1,685,323,776 2,305,425,408
4D 557,113,344 1,119,576,064 1,919,885,312 2,247,098,368 3,073,900,544
5D 696,391,680 1,399,470,080 2,399,856,640 2,808,872,960 3,842,375,680
6D 835,670,016 1,679,364,096 2,879,827,968 3,370,647,552 4,610,850,816
7D 974,948,352 1,959,258,112 3,359,799,296 3,932,422,144 5,379,325,952
8D 1,114,226,688 2,239,152,128 3,839,770,624 4,494,196,736 6,147,801,088
9D 1,253,505,024 2,519,046,144 4,319,741,952 5,055,971,328 6,916,276,224
10D 1,392,783,360 2,798,940,160 4,799,713,280 5,617,745,920 7,684,751,360
11D 1,532,061,696 3,078,834,176 5,279,684,608 6,179,520,512 8,453,226,496
12D 1,671,340,032 3,358,728,192 5,759,655,936 6,741,295,104 9,221,701,632
13D 1,810,618,368 3,638,622,208 6,239,627,264 7,303,069,696 9,990,176,768
14D 1,949,896,704 3,918,516,224 6,719,598,592 7,864,844,288 10,758,651,904
15D 2,089,175,040 4,198,410,240 7,199,569,920 8,426,618,880 11,527,127,040
16D 2,228,453,376 4,478,304,256 7,679,541,248 8,988,393,472 12,295,602,176
RAID 1 1D+1D 139,278,336 279,894,016 479,971,328 561,774,592 768,475,136
RAID 5 2D+1P 278,556,672 559,788,032 959,942,656 1,123,549,184 1,536,950,272
3D+1P 417,835,008 839,682,048 1,439,913,984 1,685,323,776 2,305,425,408
4D+1P 557,113,344 1,119,576,064 1,919,885,312 2,247,098,368 3,073,900,544
5D+1P 696,391,680 1,399,470,080 2,399,856,640 2,808,872,960 3,842,375,680
6D+1P 835,670,016 1,679,364,096 2,879,827,968 3,370,647,552 4,610,850,816
7D+1P 974,948,352 1,959,258,112 3,359,799,296 3,932,422,144 5,379,325,952
8D+1P 1,114,226,688 2,239,152,128 3,839,770,624 4,494,196,736 6,147,801,088
9D+1P 1,253,505,024 2,519,046,144 4,319,741,952 5,055,971,328 6,916,276,224
10D+1P 1,392,783,360 2,798,940,160 4,799,713,280 5,617,745,920 7,684,751,360
11D+1P 1,532,061,696 3,078,834,176 5,279,684,608 6,179,520,512 8,453,226,496
12D+1P 1,671,340,032 3,358,728,192 5,759,655,936 6,741,295,104 9,221,701,632
13D+1P 1,810,618,368 3,638,622,208 6,239,627,264 7,303,069,696 9,990,176,768
14D+1P 1,949,896,704 3,918,516,224 6,719,598,592 7,864,844,288 10,758,651,904
15D+1P 2,089,175,040 4,198,410,240 7,199,569,920 8,426,618,880 11,527,127,040
*1 : Maximum number of blocks 1 is applied for the RAID Group excluding the Drives #0 to #4 of the Basic
Chassis.
Maximum number of blocks 2 is applied for the RAID Group including at least one Drive of the Drives
#0 to #4 of the Basic Chassis.

SYSPR 03-0180-01
Disk Drive capacity 71.3 G bytes 143.3 G bytes 245.7 G bytes 287.6 G bytes 393.4 G bytes
(*1) (*2)
Number of Number of Number of Number of Number of
RAID configuration Logical Blocks Logical Blocks Logical Blocks Logical Blocks Logical Blocks
2D+2D 278,556,672 559,788,032 959,942,656 1,123,549,184 1,536,950,272
3D+3D 417,835,008 839,682,048 1,439,913,984 1,685,323,776 2,305,425,408
4D+4D 557,113,344 1,119,576,064 1,919,885,312 2,247,098,368 3,073,900,544
RAID 1+0 5D+5D 696,391,680 1,399,470,080 2,399,856,640 2,808,872,960 3,842,375,680
6D+6D 835,670,016 1,679,364,096 2,879,827,968 3,370,647,552 4,610,850,816
7D+7D 974,948,352 1,959,258,112 3,359,799,296 3,932,422,144 5,379,325,952
8D+8D 1,114,226,688 2,239,152,128 3,839,770,624 4,494,196,736 6,147,801,088
*1 : Maximum number of blocks 1 is applied for the RAID Group excluding the Drives #0 to #4 of the Basic
Chassis.
Maximum number of blocks 2 is applied for the RAID Group including at least one Drive of the Drives
#0 to #4 of the Basic Chassis.
(v) Number of logical blocks per Disk Drive.
Table 3.3.3 Number of Blocks (m) and Capacity per Disk Drive
Disk Drive model name
71.6 G bytes 143.3 G bytes 247.5 G bytes 287.6 G bytes 393.4 G bytes
Capacity(*1)
Capacity Number of blocks (m) 139,279,360 279,895,040 479,972,352 561,774,592 768,475,136
(user area size)
per Disk Drive Capacity (G bytes) 71,311,257,088 143,306,624,521 245,745,845,088 287,628,591,104 393,459,269,632

SYSPR 03-0190-01
(3) After completion of the setting, click [OK] button.

Simple Window Detail Window

SYSPR 03-0200-01
(5) Preset LU information is updated and the screen is displayed.
For a Controller No. at LU creation, specify a controller in charge of a default LU.

Current controller when an LU was created becomes equal to the current of the controller in
charge of the default LU. However, if LU switching might have occurred, it does not become
equal.

SYSPR 03-0210-01
[Procedure e-C]Verifying LU
(1) Click the [Logical Status] tab. Usually, when the setting of an LU is completed, the [Logical
Status] tab is in the clicked state.
(2) The setting made in [Procedure e-B] can be referred to by a double clicking on the icon of the
RAID group created.
If the confirmation of LU is OK, go to the [Procedure e-F]Formatting LU (SYSPR 03-0280).

If the confirmation of LU is NG, and if the change of LU in charge is required, go to the
[Procedure e-E]The change of the controller in charge of a default LU (SYSPR 03-0260).
If the setting of Default LU controller, go to the [Procedure e-D]Deleting LU(SYSPR 03-
0230).

SYSPR 03-0220-01
[Procedure e-D]Deleting LU
NOTE : All user data is lost by deleting the LU. Backup user data before deleting the
RAID group.
(1) Deleting the LU

(a) Click the icon of a logical unit on the Unit screen.
When you select multiple logical units, hold down the [Ctrl] key and click the icons of the
logical units that you wish to delete.
(b) Select [Settings] [Logical Unit] [Delete].
(c) A confirmation message is displayed indicating whether last LUs should be deleted or not.
When there is no formatted LU in a RAID group

SYSPR 03-0230-01
When there is a formatted LU in a RAID group

SYSPR 03-0240-01
(d) The LU information in which last LUs have been deleted is updated and the window is
displayed.
When setting the LU, go to [Procedure e-B]Setting LU (SYSPR 03-0150).

SYSPR 03-0250-01
[Procedure e-E]The change of the controller in charge of a default LU
NOTE : The change of the controller in charge of a default LU can be used only for the
dual active mode configuration of a dual system.
(1) Click an icon of an LU the default Controller controlling which is to be changed, and then
select [Settings] [Logical Unit] [Change Default Controller].

SYSPR 03-0260-01
The window, in which information on the changed LU is updated, is displayed.
Go to [Procedure e-C]Verifying LU (SYSPR 03-0220).

SYSPR 03-0270-01
[Procedure e-F]Formatting LU
An LU is formatted.
(1) Formatting while online

This mode enables the subsystem to start its operation earlier by formatting the specified LU
in the background to make it usable by a host. The number of LUs for which an application
of the formatting can be specified is up to 512. The number can be increased also.
However, the number of LUs that can be formatted in the background at the same time is six
per CTL.
When executing the formatting, Storage Navigator Modular can perform its operation (such as
a RAID group creation) even when the formatting is being executed.
Even when Storage Navigator Modular is quit while the formatting is being executed, the
formatting is continued.
Besides, when Storage Navigator Modular is quit while the formatting is being executed, the
progress of the formatting is displayed in percentage in the logical unit status column when
Storage Navigator Modular is activated again.

SYSPR 03-0280-01
Table 3.3.4 LU Formatting Mode and while Online Description of Operation

Connection mode of array disk management mode and device configuration
No. Single system Dual system + Restriction
Dual system +
LAN single-system connection.
LAN dual-system connection.
1 Can be executed during online Can be executed during online y For ShadowImage in-system replication,
processing. processing. TrueCopy remote replication and Copy-on-
Only the LU in charge of the current write SnapShot, pair definition cannot be
of the controller to which utilities executed when LU is in quick format. If pair
were connected is selected. definition is in process, format cannot be
(When formatting an LU which is not applied.
in charge of the current, the y An LU being formatted cannot be unified or
connection cable needs to be extended. Besides, an extended LU cannot
replaced by a new one.) be formatted.
NOTE : y Host access performance deteriorates during format.

y The LU status in which the LU is being formatted is maintained beyond the
deliberate shutdown.
y When two or more of ShadowImage in-system replication, TrueCopy remote
replication, and Copy-on-write SnapShot are used together, a capacity of the LUs
that can be formatted at a time is limited.
The standard capacity of the LU that format can be done at a time is calculated
by the following formula.
For RKM /RKS ([T byte] in every unit)
(LU capacity that format can be done at a time) =
120-{(primary and secondary capacity of TrueCopy remote replication) +
(primary and secondary capacity of ShadowImage in-system
replication) + (primary capacity of Copy-on-write SnapShot) 16}
However, up to 8 T bytes of LU(s) can be formatted at a time irrespective of
a total capacity of LUs being used by ShadowImage in-system replication,
TrueCopy remote replication, and/or Copy-on-write SnapShot. When
forming a ShadowImage in-system replication, TrueCopy remote replication,
or Copy-on-write SnapShot pair with LUs that are being formatted, the total
capacity of the LUs can be paired is limited.
y When PIN OVER occurs during format, a formatting in the background is
interrupted. The formatting in the background is resumed automatically
after PIN OVER is recovered. Refer to Troubleshooting 6.1.11 A failure
occurred during operation : Case 1 (PIN over) (TRBL 06-0550).
y When a data loss occurs owing to a power failure and battery exhaustion, an
LU being formatted enters the Unrestored status. Basically, use the LU after
the formatting is completed.
y When the host I/O is executed for the LU in formatting, the format
completion may be delayed.
In this case, it may take 400 seconds at maximum from the 99 % progress
status.
y If the owner right to the LU is switched, the formatting operation becomes
standby status depending on the number of operations in the Control Unit in
charge.

SYSPR 03-0290-01
(a) Select an LU or LUs to be formatted, and then select either of the [Settings] [Logical Unit]
[Format].
(b) If the confirmation message is displayed. Click the [OK] button.

y When an LU that has been Quick formatted does not exist

SYSPR 03-0300-01
y When an LU that has been Quick formatted exists

SYSPR 03-0310-01
(c) If [OK] is clicked, the specified LU is formatted(1).

(d) Message is displayed.
y When the Quick is specified
When the Quick is specified, it is displayed in the logical unit status column.
NOTE : The value of percentage is not updated unless the subsystem status is referred
to through selections of [Display] and [Latest Information] in this order.
1 : When a specified LU is formatted, the user data within the specified LU is lost. When incorrectly specifying an LU,
press the [Cancel] button and redo processing by selecting an LU to be reformatted.

SYSPR 03-0320-01
If formatting terminates abnormally, refer to Table 3.3.5.
Table 3.3.5 Contents of Display of Execution Result Screen

No. Status Result
1 Abnormal end CHECK CONDITION (xx-xxxx) is displayed(*1) Unsuccessful
Format Unit
Sense key Sense code Unsuccessful command
2 A message is displayed. Unsuccessful
Other errors than the above
*1 : Because this function internally uses the Format Unit command, it displayers a sense key and a
sense code when the pertinent command returns the Check Condition status.
When Abnormal is indicated on Status, sense-key, sense-code or message-text is indicated.
When sense key and sense code = 02-xx xx, 03-xx xx, 04-xx xx or 0B-xx xx;
For the above code, a hardware fault is assumed. When the subsystem is not recovered from
the failure after retrying, remove the cause of the error considering the type and meaning of
the error. (Refer to Message Chapter 9. Failure Analysis by Sense Data (MSG 09-0000) of
the Maintenance Manual.
When sense key and sense code = 05-xxxx;

For the above code, an operation error is assumed. Upon checking the following items and
re-execute processing. If the error is not recovered, contact our company.
c Is logical unit 0 defined? Codes which will occur are 05-25 00 and 25-25 81.
d In spite of none of drive mounted states, is ALL RAID specified and is an LU specified for
ALL CAPA formatted? A code which will occur is 05-26 00.
e Is an attempt made to define an LU exceeding the capacity of the defined RAID group?
A code which will occur is 05-25 80.
When sense key and sense code = 0B-FD01;

Switching of a controller in charge of an LU occurred during formatting. Check the
controller in charge and re-execute formatting from the controller in charge.
When message-text is indicated, take measure according to the message.

SYSPR 03-0330-01
(f) Preset LU information is updated and the screen is displayed.
y The formatting LU has terminated, go to 3.4 Setting of Spare Disk (SYSPR 03-0350).

SYSPR 03-0340-01
3.4 Setting of Spare Disk

This setting is used to set, delete and reference a Spare Disk.
The drive that can be set as the Spare Disk is a data disk.
[Procedure f-A]Preparing of setting Spare Disk

(1) Select a [Spare Drives] from the tree.
(2) Click the [Set] button that is displayed at the lower right part of the window.

SYSPR 03-0350-01
[Procedure f-B]Setting Spare Disk
(1) Select an HDU you want to specify as a spare drive from the [Available Drives] list and click the
[ ] button.
(2) The selected HDU is moved to the [Drives to Set] list. Click the [OK] button.

SYSPR 03-0360-01
(3) The confirmation window is display.

When incorrectly specifying an Disk Drive, press the [Cancel] button and redo processing by
[Procedure f-B].
y When verifying the Spare Disk, go to [Procedure f-D]Verifying Spare Disk (SYSPR 03-0390).

SYSPR 03-0370-01
[Procedure f-C]Deleting Spare Disk
(1) Select the [Spare Drives] from the tree and select the spare disk to be removed from the [Spare
Drives] by clicking it.
Spare Disk
: Data Disk : Spare Disk
(2) Click the [Release] button that is displayed at the lower right part of the window.
(3) The Spare Disk reset confirmation is displayed.
Click the [OK] button. When incorrectly specifying an Disk Drive, press the [Cancel] button
and redo processing by [Procedure f-C].
y When setting the Spare Disk, go to [Procedure f-B]Setting Spare Disk (SYSPR 03-0360).
NOTE : When you have set a configuration of the [RAID Group] or [Logical Unit], be sure
to execute the [Update to the Latest Information] after closing the parameter
window in order to make the RAID group icon in the unit window the latest.

SYSPR 03-0380-01
[Procedure f-D]Verifying Spare Disk
(1) You can make sure of the spare drive that has been set on the right side of the window by
selecting [Spare Drives] from the tree in the unit window.
: Data Disk : Spare Disk
y If confirmation is OK, go to Chapter 2. Setting Host Group (SYSPR 02-0000)

y If confirmation is NG, go to [Procedure f-C]Deleting Spare Disk (SYSPR 03-0380)

SYSPR 03-0390-01
3.5 Checking the status of Disk Drive

Display the array unit component status and information by using icons. When you double-
click each icon, the information of the component part indicated by the icon is displayed.
(2) To update the component display, on the View menu, select Refresh or click [ : Refresh]
button in the tool bar.

SYSPR 03-0400-01
(3) When you double-click Drive icon, the property screen of the component part is displayed.
NOTE : Vendor ID, Product ID, Revision, and Serial No. may not be displayed depending
on the drive mounting and drive status.
[Unit] : Unit No.

[HDU] : HDU No.
[Type] : Drive using form
Data : Data drive
Spare : Spare drive
Undefine : Normal (LU not defined)
[Capacity] : Storage capacity of a drive
[Drive Type] : Drive type
[Status] : Drive status
Normal : Normal
Detached : Blockade
Detached (Unmount) : The drive in the blockade status is not
installed.
Standby : Normal (LU not defined)
Out of RG : Normal (RAID not defined)
Undefine : Normal (LU not defined)
Unmount : The drive is not installed.
Recovery : Under recovery (correction copy or copy-back in
progress)
Unitx HDUy : Position of a corresponding data drive when using spare
Disk Drives.
Waiting : Spare drive not used
[Vendor ID] : Vendor ID of drive
[Product ID] : Product ID of drive
[Revision] : Firmware revision of drive
[Serial No.] : Serial No. of a drive

SYSPR 03-0410-01
Chapter 4. Setting Configuration Information

4.1 Before setting configuration information
NOTE : If the setting is changed while an I/O is being executed, the I/O may be
abnormally stopped or the succeeding I/O may be unable to be executed.
Therefore, change the setting after stopping the I/O.
Besides, the setting on the host computer side must be changed depending on
the host computer.
Operation as described below.

(2) Start the Storage Navigator Modular and set the Operation Mode to the Maintenance Mode(1).
1 : For details of the setting method, refer to the Subsection 1.1 (3)(b) Changing the Maintenance Mode (SYSPR 01-
0050).

SYSPR 04-0000-01
Settings] button.

SYSPR 04-0010-01
4.2 Setting the subsystem configuration information

The setting of the configuration information has the other functions as shown below.
y The name of the configuration setting shows indication of a tag in the Parameter window.
y The setting entered is validated when the [Apply] button at lower right part of the
Parameter window is clicked.
y The setting of each parameter of the Port Option and Fibre Option must be made for
each port (each of Port 0A, 0B, 1A, and 1B).
Table 4.2.1 The menu items of setting parameter

No. Menu item Use Contents Factory setting Reference page
1 Boot Options Sets parameters necessary for c Setting the system start attributes Depending on the (1) Setting
the reboot of the subsystem. configuration at shipment Boot Options
d Setting the Delay Planned Shutdown 0 minute (SYSPR 04-
e Setting the Drive blocking mode Disable 0040)
f Setting the Vender ID HITACHI
g Setting the Product ID DF600F
h Setting the ROM Microprogram Version Not set
i Setting the RAM Microprogram Version Not set
2 System Parameter To be used to set the system c Selection of system parameters (2) Setting of
parameters. d Setting of an action against a processor failure Reset of occurred. System
e Web title Parameter
f Setting of the mode for executing the Write and ON (SYSPR 04-
Verify 0070)
3 LAN Reference to and setting of the c Reference to and/or setting of enable(*1) or OFF (3) Setting of
LAN configuration information. disable of the DHCP mode. LAN (SYSPR
d Reference to and setting of IP Address. 192.168.0.16 04-0090)
e Reference to and setting of SUB NET MASK. 255.255.255.0
f Reference to and setting of Default Gateway. 0.0.0.0
g Reference to the Ether Address.
4 Port Options Set the port options of a c Reference/setting of the port option for each (4) Setting of
controller port Port Options
(SYSPR 04-
0100)
*1 : When DHCP mode is valid, IP address is obtained from the DHCP server.
When the DHCP server has not started up or DHCP function has been miss-set, obtaining the IP address fails and
the device IP address remains to be 0.0.0.0. (Storage Navigator Modular or WEB cannot be used via LAN.)
In this case, the device IP address can be obtained by starting up the DHCP server or setting DHCP function
correctly if necessary.
When this device is used as an external Disk Drive of the DHCP server and the device IP address is obtained by
DHCP function, and if the IP address of 10.0.0.x is assigned to the device, IP addresses of Ports for User
Management and Maintenance may conflict with each other and the device may not function normally.
Request the system administrator that the DHCP server does not assign IP address of 10.0.0.x to the device.

SYSPR 04-0020-01
No. Menu item Use Contents Factory setting Reference page

5 Restore Options Refers to and/or sets an option c Reference to and/or setting of the mode for Interleave (Normal) (5) Setting of
of drive restoration. Drive Restoration Mode. Restore
d Reference to and/or setting of the occasion for Automatic Options
Drive Restoration. (SYSPR 04-
e Reference to and/or setting of the interval time, (*1) 0120)
processing unit size.
f Reference to and setting of Dynamic Sparing. Execute (Read& Online
Verify mode)
g Reference to and setting of Spare Drive Fixed
operation.
6 Online Verify Refers to and/or sets validity or c Refers to and/or sets validity or invalidity of Yes (Execute mode) (6) Setting of
invalidity of online verification. online verification. Online Verify
(SYSPR 04-
0140)
7 Constitute Writes system parameters and c Output of system parameters and configuration (7) Setting of
configuration information such information to (a) file(s). Constitute
as the RG/LU onto (a) file(s) or d Input of system parameters and configuration (SYSPR 04-
reads them from (a) file(s). information to (a) file(s). 0150)
8 Fibre Channel Reference to and setting of c Reference of Node Name. (8) Setting of
information regarding the Fibre d Reference of Port Name. Fibre Channel
Channel. (SYSPR 04-
e Reference/setting of Topology Information for Loop 0170)
each port
f Setting of Port Address for each port. 0000EF
g Setting of Transfer Rate for each port. Auto
9 Micro Update Down load and replace the c Setting of down load of the microprogram. (9) Setting of
microprogram. Micro Update
d Setting of replacement of the microprogram. (SYSPR 04-
0200)
10 RTC Reference to and setting of c Setting procedure. (10) Setting of
date, time. d Reference to and setting of the date. RTC (SYSPR
e Reference to and setting of the time. 04-0220)
11 Format Mode Setting of Format mode. c Reference to and setting Format Mode. Normal (11) Setting of
Format Mode
(SYSPR 04-
0230)
12 SNMP Writes SNMP information onto c Output of SNMP information to (a) file(s). (12) Setting of
(a) file(s) or reads them from d Input of SNMP information to (a) file(s). SNMP (SYSPR
(a) file(s). 04-0240)
*1 : Interval time : 0 ( 10 ms)
Recoverable data size : 1 ( 128 block)

SYSPR 04-0030-01
(1) Setting Boot Options

Parameter settings, which are shown in the List of DF700 Boot Option/System Parameter
Settings in the Read before you start supplied with the subsystem, have been made when
the subsystem is shipped from the factory. Reset the boot options when necessary.
When any of the Boot Options is changed, the subsystem becomes unable to receive access
from a host computer until the reboot is completed. Reset the Boot Options after making sure
that access from the host computer has been stopped.
Note : Do not perform setting Boot Options while the READY LED (green) is blinking at
high speed (for the maximum of 30 to 50 minutes).
(a) Click the [Boot Options] tab. A window for setting the boot options is displayed in the
[Parameter] window.

SYSPR 04-0040-01
No Parameter name Construction Kind of parameter Default setting

1 System start Specifies the system start Single mode Made in the case of the single Control Unit Depending on the
attributes attributes. configuration. configuration at
Dual Active mode Made in the case of the dual Control Unit shipment
configuration.
2 Delay Planned Specifies the delay time until the 0 to 60 minutes Specifies the delay time until the start of the 0 minute
Shutdown start of the deliberate shutdown deliberate shutdown by the minute.
by the minute.
3 Drive Detach mode Specifies an operation to be Disable Even when a failure occurs in a disk drive in a state Disable
performed when a drive failure in which another disk drive in the same RAID group
occurs in the same RAID group. has already been detached owing to a failure, the
parameter does not detach the disk drive that failed
secondarily.
Enable When a failure occurs in a disk drive in a state in
which another disk drive in the same RAID group
has already been detached owing to a failure, the
parameter detaches the disk drive that failed
secondarily and detaches LUs (makes LUs
unformatted) in the RAID group concerned.
4 Vender ID Specifies the Vender ID 8 or less half size The value that has been set is reported at 8th to HITACHI
alphabetic 15th bytes of the Standard Inquiry. Normally, no
characters and/ or change from the default value, HITACHI, is
numerals. required.
5 Product ID Specifies the Product ID 16 or less half size The value that has been set is reported at 16th to 31th DF600F
alphabetic bytes of the Standard Inquiry. Normally, no change
characters and/ or from the default value, DF600F, is required.
numerals.
6 ROM Microprogram Specifies the ROM Microprogram 2 or less half size The value that has been set is reported at 32th to Not set
Version Version alphabetic 35th bytes of the Standard Inquiry. Normally, no
characters and/ or change from the default value, Not set, is required.
numerals.
7 RAM Microprogram Specifies the RAM Microprogram 2 or less half size
Version Version alphabetic
characters and/ or
numerals.

SYSPR 04-0050-01
(b) Verify that the settings that have been made are correct and click the [Apply] button.
When the [Reset] button is clicked, the change is canceled.
(c) The confirmation window is display. Click the [OK] button.
When you choose to restart the subsystem, the time the restart began is displayed. This
usually takes approximately four to fifteen minutes.
NOTE : It may take time for the subsystem to respond, depending on the condition of
the subsystem. If it does not respond after 15 minutes or more, check the
condition of the subsystem.
(f) A message appears, stating that the restart is successful. Click the [OK] button.
The Unit screen is closed. To perform other operations on the Main screen, select an array
unit from the Main screen and open the selected Unit screen.

SYSPR 04-0060-01
(2) Setting of System Parameter
(a) Click the [System Parameter] tab. The window for setting the System Parameter is
displayed in the Parameter window.
No. Parameter name Construction Kind of parameter Default setting

1 Option Turbo LUN This parameter is to be Disable Even when the Turbo LU becomes unable to be Disable
Warning specified when the Turbo (Not checked) maintained owing to a failure, the parameter allows
LU setting function is used. host access to be issued.
Enable (Checked) When the Turbo LU becomes unable to be maintained
owing to a failure and the performance is lowered, the
parameter suppresses the host access and issue a
warning to the subsystem.
2 Write Unique This parameter is to be Disable The cache memory is used when the write command Disable
Response Mode specified when a host of the (Not checked) is received.
NX series is connected. Enable (Checked) The write command is executed unconditionally in the
Write-Through mode.(*1)
3 Auto This parameter specifies Disable Even when a disk drive is pulled out, the correction Disable
Reconstruction operations to be performed (Not checked) copy to a spare disk drive is not performed.
4 Mode when a disk drive is pulled Enable (Checked) When a disk drive is pulled out, the correction copy to
out. a spare disk drive is performed.
5 Forced Write This parameter specifies Disable Even if the CTL detachment or a power failure has Disable
Through Mode the way to execute the write (Not checked) occurred, the cache memory is used when the write
command to be used after command is received.
the CTL detachment or a Enable (Checked) When the CTL detachment or a power failure has
power failure occurs. occurred, the write command is executed in the Write-
Through mode.
6 Option LU Ownership This parameter specifies an Disable Request the internal processing to the Control Unit in Disable
change Disable operation to re-assign an (Not checked)charge of the LU. However, when there is no access
Mode LU to a controller that is not for one minute from the Control Unit side in charge of
controlling the LU when the the LU, reallocate the Control Unit in charge of the LU.
controller attempts to Enable (Checked)
The access is always made by a Control Unit that
access the LU. controls the LU concerned by request without re-
assigning the LU to a Control Unit that wants to
access the LU.
*1 : Write-Through means an operation to write data directly to disk drives without using the cache memory
when the write command is received from a host. When data is written in the Write-Through mode,
response to the host takes longer time because access to the disk drives is indispensable.

SYSPR 04-0070-01
No. Parameter name Construction Kind of parameter Default setting

7 ShadowImage This parameter specifies an Disable When a double failure occurs in disk drives of a P- Disable
I/O Switch Mode operation of a VOL in the PAIR status of ShadowImage, the status
(Not checked)
ShadowImage P-VOL to is changed to PSUE.
be performed when a disk Enable (Checked) When a double failure occurs in disk drives of a P-
drive double failure occurs. VOL in the PAIR status of ShadowImage, the
executor of the host I/O is switched to an S-VOL to
continue the execution.
8 Synchronize This parameter specifies an Disable No operation is performed when the Synchronize Disable
Cache operation to be performed (Not checked) Cache command is received.
Execution Mode when the Synchronize
Cache command is Enable (Checked) When the Synchronize Cache command is received,
received. the whole data in the cache memory is written to disk
drives.
9 Operation if the This parameter specifies an Reset of occurred The parameter resets the failure and reboots the Reset of
processor failure operation to be performed Control Unit. occurred
occurs when a processor failure
occurs. System down The parameter makes the disk array subsystem go
down.
10 WEB Title In the case where the Web 32 or less half size Characters to be entered are half size alphabetic Not set
function that is built in the alphabetic characters, numerals, and/or characters other than
disk array subsystem is characters and/ or numerals (excluding , , and \).
displayed with the browser, numerals.
this parameter specifies
characters to be displayed
on the title bar of the
browser.
11 Write and verify This parameter specifies an ON The write and verify operation is performed. ON
mode execution mode for write
and verify operation for the OFF The write and verify operation is not performed.
Control Unit #0 or Control
Unit #1.
*1 : Write-Through means an operation to write data directly to disk drives without using the cache memory
when the write command is received from a host. When data is written in the Write-Through mode,
response to the host takes longer time because access to the disk drives is indispensable.
(b) Check if the settings that have been made are correct and click the [Apply] button. When
the [Reset] button is clicked, the settings that have been made are cancelled. To terminate
the setting, click the [Close] button.

SYSPR 04-0080-01
(3) Setting of LAN

Note : Do not perform setting of LAN while the READY LED (green) is blinking at high
speed (for the maximum of 30 to 50 minutes).
(a) Click the [LAN] tab. The window for setting the LAN is displayed in the Parameter
window.
c [DHCP] : Sets the DHCP function

When the check box of the [DHCP] is checked, the DHCP mode is
validated.
d [Network] : Sets the LAN parameter.

When the check box of the [DHCP] is checked, this item is grayed and
cannot be set.
[IP Address] : Sets the IP address.
[Subnet Mask] : Sets the subnet mask.
[Default Gateway] : Sets the default gateway.
[Ether Address] : The Ethernet address (MAC address) is displayed. It cannot
be changed.
Set this item for the both controllers when necessary.
When the [Reset] button is clicked, the change is canceled. To terminate the setting, click
the [Close] button.

SYSPR 04-0090-01
(4) Setting of Port Options

(a) Click the [Port Options] tab. The window for setting the Port Options is displayed in the
Parameter window.
(b) Click the [Port 0A] button.
[Port Options] : Specify a port options. Select an option you want to

set by clicking its check box.
[Reset/LIP Mode Signal] : This is a mode for transmitting the Reset/LIP signal
to another port.
[Reset/LIP Mode (Process)] : This is a mode for propagating the reset operation
to another port.
[Reset ALL LIP Port Mode] : This is a mode for executing the reset operation
when the LIP is received.
NOTE : The Reset/LIP mode (signal transmission) is effective when the Reset/LIP mode
(processing transmission) is set.
(c) When the setting is completed, click the [Apply] button at lower right corner of the
Parameter window. When the [Reset] button is clicked, the change is cancelled.

SYSPR 04-0100-01
(d) A message asking you to verify the setting is displayed.

After making sure that the I/O request from a host is suppressed, click the [OK] button.
(e) When the setting is completed, the following message is displayed. Click the [OK] button.
(f) The setting/verification of the port 0A is completed. Do the same for the other ports.
(g) Click the [Close] button.

SYSPR 04-0110-01
(5) Setting of Restore Options

It becomes availableness as soon as possible when an option is set up by using this function
during the drive is being restored.
(a) Click the [Restore Options] tab. The window for setting the Restore Option is displayed in
the Parameter window.
c [Drive Restoration Mode] : Specify a method of drive restoration.

[Background] : The restoration is performed at a free time when no host
I/O operation is performed.
[Interleave (Normal)] : The restoration is performed regularly (at fixed intervals)
in a manner in which priority is given to a host command.
(The restoration is performed after a host command
execution is completed.)
[Interleave (Prior)] : The restoration is performed regularly (at fixed intervals)
in a manner in which priority is taken to a host command.
d [Drive Restoration] : Specify whether to start operations (data restoration onto a

failed drive, data restoration onto a spare drive, data copying
from a spare drive to an original drive, and dynamic sparing)
automatically or manually.
[Manual] : A data restoration and data copying from a Spare Drive to an original
drive are started manually. (Not supported)
[Auto] : A data restoration and data copying from a Spare Drive to an original
drive are started automatically.

SYSPR 04-0120-01
e [Interval Time] : Specify an interval of the restoration.

The default value is 0x10 ms. Concurrently with I/Os from the
host, the restorations are performed in succession.
Treat 10ms as the unit and specify a multiplier within a range of
0 to 255.
f [Processing Unit Size] : Specify a size of data to be restored.

The default value is 128 blocks; data of 64kbytes is restored
at a time. When Interleave is specified, specified size of
data is restored, a time specified as the interval time is
waited for, and the next restoration is performed.
Treat 512 bytes (1 block) as the unit and specify a multiplier
within a range of 1 to 511.
g [Dynamic Sparing] : Specify a mode (for restoring data onto a Spare Drive) to be
used when the failure count exceeds a threshold value
controlled in the preventive maintenance.
[Execute (Read/Write & Online Verify)] : When the count of read/write errors or
online verification errors exceeds a
threshold value, data is restored onto a
spare drive (in the case where the spare
drive is unused) and failed drive is
detached.
[Execute (Read/Write)] : When the count of read/write errors exceeds a
threshold value, data is restored onto a Spare Drive (in
the case where the Spare Drive is unused) and failed
drive is detached.
When the count of online verification errors exceeds a
threshold value, the dynamic sparing is not performed.
[Do not Execute] : When the count of read/write errors or online
verification errors exceeds a threshold value, the
dynamic sparing is not performed.
h [Spare Drive] : Specify a way of the spare drive operation.

[Variable] : When a failed drive is replaced, the new drive becomes a spare
drive.
[Fixed] : The specified drive is fixed as a spare drive (conventional way).
the [Close] button.

SYSPR 04-0130-01
(6) Setting of Online Verify
(a) Click the [Online Verify] tab. The window for setting the Online Verify is displayed in the
Parameter window.
c [Online Verify Test] : Set whether or not to carry out the online verification test.
When the check box is checked, the test is carried out.
d [Idling Time] : This item cannot be set for the DF700.

[Default] : This item cannot be set for the DF700.
the [Close] button.

SYSPR 04-0140-01
(7) Setting of Constitute

Output configuration information of the disk array subsystem to a text file or set the
configuration by using the text file.
The configuration information to be output to a text file includes RAID group/logical unit,
system parameters, and port/host group information.
The configuration to be set includes RAID group/logical unit, system parameters, and port/host
group information.
Each element of the configuration, that is, RAID group/logical unit, system parameters, or
port/host group information is operated by a respective file.
You can copy the configuration from/to the disk array subsystems by outputting the
configuration information from the disk array subsystem to a text file and setting it for another
disk array subsystem using the text file that has been output.
You can set a disk array subsystem by editing the text file. Use this function to create the
same disk array subsystem. Change the element of the configuration using a respective
function.
Note : Do not perform the text input of Boot Options of the configuration copy
information while the READY LED (green) is blinking at high speed (for the
maximum of 30 minutes to 50 minutes). (Do not select [Input] or [Boot
Options].)
(a) Click the [Constitute] tab. The window for setting the Constitute is displayed in the
Parameter window.
c [Operation] : Output the set information to a text file or enter the information to
be set.
[Output] : Selected information is output to a text file with a specified file name.
[Input] : Selected information is loaded and set with a specified file name.
d [Select Configuration Information] : Select information to be output to the text file

or to be set through a reading of a text file.
[RAID Group/Logical Unit] : This is information on definition of the RAID
group/logical unit set for the disk array subsystem.
[System Parameters] : This is the setting of system parameters made for
the disk array subsystem.

SYSPR 04-0150-01
[Port/Host Group] : This is information on the port/host group set for

[Port/Host Group (Update)] : This is port/host group information to be set for
[Setting Information for Input] : Select information to be set from the following
items.
[Port Options] : Specify this when setting a port option.
[Host Group Options] : Specify this when setting a host group option.
[Mapping Information] : Specify this when setting a mapping information.
[Boot Option] : This is the setting of Boot Option made for the disk
array subsystem.
[Parts Information] : This is the setting of parts information made for
(b) To terminate the setting, click the [Close] button.

(c) The unit screen is displayed. When you set the composition of [RAID/Logical Unit File] ,Click
the RAID group for which an LU is to be created, and then select [View] [Refresh] or click
[ : Refresh].

SYSPR 04-0160-01
(8) Setting of Fibre Channel
(a) Click the [Fibre Channel] tab. The window for setting the Fibre Channel is displayed in
the Parameter window.
(b) Click the [Port 0A] button.
c [Node Name] : Data of eight bytes is displayed with a hexadecimal number

(16 characters).
d [Port Name] : Data of eight bytes is displayed with a hexadecimal number
(with 16 characters).
e [Port Address] : A port address is displayed or set with a six-figure
hexadecimal number.
<Current Value>
A current port address is displayed with a six-figure hexadecimal number.
<Setting>
A port address you want to set with a six-figure hexadecimal number.
f [Transfer Rate] : A transfer rate of the Fibre Channel can be displayed or set.
<Current Value>
A current transfer rate of the Fibre Channel is displayed.
<New Value>
[1Gbps] :Set this when using the Fibre Channel at a fixed transfer rate of 1Gbps.
[Auto] : Set this when using the Fibre Channel at a transfer rate that is
changed automatically.
g [Topology Information] : The topological setting value is specified through a
selection from a pull down menu.
h [Link Status] : This item cannot be set for the DF700.

SYSPR 04-0170-01
(c) When the setting is completed, click the [Apply] button at lower right corner of the
Configuration Settings window.
(d) A message asking you to verify the setting is displayed.

After making sure that the I/O request from a host is suppressed, click the [OK] button.
(e) When the setting is completed, the following message is displayed. Click the [OK] button.

SYSPR 04-0180-01
(f) Click the [Latest Information Display] button at the lower right part of the Parameter
window to check if the setting is reflected on the display.
(g) The setting /verification for the Port 0A is completed. Do the same for the other ports.
(h) When the setting for all the ports are completed, click the [Close] button.

SYSPR 04-0190-01
(9) Setting of Micro Update

Replace microprograms of the controllers with the microprogram downloaded onto the disk
array subsystem.
When performing the replacement, be sure to replace microprograms of the both controllers
(controller #0 and controller #1).
(a) Click the [Micro Update] tab. The window for setting the Micro Update is displayed in the
Parameter window.
<Download Microprogram>
c [Current Revision] : The microprogram revision of each controller of the disk array
subsystem is displayed.
d [Revision(Read)] : The revision of the microprogram loaded on to the computer,

in which Storage Navigator Modular is installed, is displayed.
When the microprogram is not loaded, a blank is displayed.
e [Interval Time] : Set an interval of downloading. Set it within a range of 1 to

60 seconds.
NOTE : You can use it while an I/O requested by a host computer is executed, however,
the I/O performance of the host computer is lowered when the downloading is
performed. To prevent the performance from the lowering, make the interval
longer.
f [Revision Check] : Instruct to perform the revision check of the microprogram to

be downloaded. You can check whether the microprogram
can be replaced while the subsystem power is turned on or not
by instructing to carry out the revision check. Select [Yes].
g [Read] : Load the microprogram onto the computer in which Storage

Navigator Modular is installed. Specify the directory in which the
microprogram is installed following the instructions given in the
window.

SYSPR 04-0200-01
h [Download] : Download the microprogram onto the disk array subsystem.
NOTE : When the microprogram is not loaded, this item is grayed and cannot be
selected.
i [Delete] : Delete the microprogram loaded onto the computer in which Storage
Navigator Modular is installed.
NOTE : When the microprogram is not loaded, this item is grayed and cannot be
selected.
<Replace Microprogram>
c [Revision(Downloaded)] : The microprogram that has been read in is downloaded

to the disk array subsystem.
d [Replace Controller with] : Replace the microprogram of the controller specified.
NOTE : When the replacement is performed for only one of the controllers, the disk
array subsystem is given a warning. The warning is cancelled when the
microprogram of another controller is replaced. When replacing the
microprogram, be sure to perform the replacement for the both controllers
continuously.
(b) To terminate the setting, click the [Close] button.

SYSPR 04-0210-01
(10) Setting of RTC
(a) Click the [RTC] tab. The window for setting the RTC is displayed in the Parameter
window.
c [Setting] : Specify the method for the setting.

[Manual] : Set a date and time to be set.
[Auto] : Set the time of the personal computer or server workstation that
executes Storage Navigator Modular.
d [Date] : The date currently set can be displayed or set.
e [Time] : The time currently set can be displayed or set.
(b) Verify that the setting that has been made is correct and click the [Apply] button. When the
[Reset] button is clicked, the change is canceled. To terminate the setting, click the [Close]
button.

SYSPR 04-0220-01
(11) Setting of Format Mode
(a) Click the [Format Mode] tab. The window for setting the Format Mode is displayed in the
Parameter window.
[Format Priority Mode] : Select a mode for giving/not giving priority to a formatting.
[Normal] : A formatting is performed when no I/O is executed.
[Host] : The priority is given to an I/O instructed by a host.
[Format] : The priority is given to a formatting.
(b) Verify that the setting that has been made is correct and click the [Apply] button. When the
[Reset] button is clicked, the change is canceled. To terminate the setting, click the [Close]
button.

SYSPR 04-0230-01
(12) Setting of SNMP

Note : Do not perform setting of SNMP while the READY LED (green) is blinking at high
speed (for the maximum of 30 to 50 minutes).
(a) Click the [SNMP] tab. The window for setting the SNMP is displayed in the Parameter
window.
<Output SNMP Setting Information to File>
c [Environment Setting File] : Environment setting file is output to a text file with
a specified file name.
d [Array Unit Name Setting File] : Array Unit Name setting file is output to a text file
with a specified file name.
<Read SNMP Information from File>
c [Environment Setting File] : Environment setting file is loaded and set with a
specified file name.
d [Array Unit Name Setting File] : Array Unit Name setting file is loaded and set with a
specified file name.

SYSPR 04-0240-01

SYSPR 04-0250-01
Chapter 5. Setting Host Connection Parameters

Set a subsystem from the Storage Navigator Modular. A procedure for setting the host
connection parameters for the subsystem offline is shown below. Make the setting following
the procedure.
5.1 Simple setting for Connecting to the Host Computer

(2) Start the Storage Navigator Modular and set the Operation Mode to the Maintenance Mode.
For the procedure for changing to the Maintenance Mode, refer to Section 1.1 (3)(b) Changing
the Maintenance Mode (SYSPR 01-0050).

(5) Display the [000: G000] by double clicking the [Port XX] for which you want to set the mode for
connecting a host after double clicking the [Host Groups].
Display the option and logical unit by double clicking the [000: G000], and then click the [Options].

SYSPR 05-0000-01
(6) Click the [Simple Setting] button that is displayed at the lower right part of the window.
(7) The [Options (Simple)] dialog box is opened.
Select [Platform], [Alternative Path], and [Failover] that conform to the environment of a host
to be connected.
Description
No. Menu Item Setting made at the factory
Parameters Selection Method
1 Platforms Not specified Select one of items Not specified
HP-UX
Solaris
AIX
WindowsNT
Windows2000
Windows2003
Linux
Tru64
2 Alternate Path Not specified Select one of items Not specified
PV Link
HDLM
VxVM
MPxIO
3 Fail-over Not specified Select one of items Not specified
MC/ServiceGuard
SunCluster
VCS
HACMP
MSCS
TruCluster

SYSPR 05-0010-01
(8) Click the [Additional Parameters] button. The [Additional Parameters] dialog box is opened.
Select items as occasion demands and click the [OK] button.
No. Menu Item Description Setting made at

Parameters Selection Method the factory
1 Additional Parameter Logical Unit Number more than or equals Selection Not selected.
to 8 can be recognized by HP-UX
TrueCopy is used by HP-UX Selection Not selected.
VERITAS Database Edition/Advanced Selection Not selected.
Cluster for Oracle RAC (Solaris) is used
Egenera BladeFrame is used Selection Not selected.
(9) Click the [Detail] button when necessary. Select the [Host Connection Mode 1] and [Host
Connection Mode 2] and click the [OK] button.

SYSPR 05-0020-01
(11) The settings that have been made are displayed.

Verify that the display reflects the selected host environment (platform, alternative path, and
fail-over) and the additional parameters. When the host connection modes 1 and 2 are set
directly, verify that the display reflects the mode setting that has been made.

SYSPR 05-0030-01
5.2 Simple setting for Connecting to the Host Computer

The following describes the procedure for setting a subsystem offline when the host group
option setting is required for the combination that simple setting does not have.
To make the setting, follow these steps.
(2) Start the Storage Navigator Modular and set the Operation Mode to the Maintenance Mode.
For the procedure for changing to the Maintenance Mode, refer to Section 1.1 (3)(b) Changing
the Maintenance Mode (SYSPR 01-0050).

(5) Display the [000: G000] by double clicking the [Port XX] for which you want to set the mode for
connecting a host after double clicking the [Host Groups].
Display the option and logical unit by double clicking the [000: G000], and then click the [Options].
(6) Click the [Simple Setting] button that is displayed at the lower right part of the window.
(7) Perform the operation corresponding to a model to be set.

SYSPR 05-0040-01
5.3 When using the subsystem in LU blockade Mode
Settings] button.
(2) Click the [Boot Options] tab.
(3) For the [Drive Detach Mode], select the [Enable] radio button.

SYSPR 05-0050-01
(4) After the setting is complete, click the [Apply] button.

When you choose to restart the subsystem, the time the restart began is displayed. This usually
takes approximately four to fifteen minutes.
NOTE : It may take time for the subsystem to respond, depending on the condition of
the subsystem. If it does not respond after 15 minutes or more, check the
condition of the subsystem.

SYSPR 05-0060-01
(7) A message appears, stating that the restart is successful. Click the [OK] button.
The Unit screen is closed. To perform other operations on the Main screen, select an array
unit from the Main screen and open the selected Unit screen.

SYSPR 05-0070-01
Chapter 6. Setting an Extra-cost Optional Feature

For setting optional feature, refer to the installation or setting section in the manual attached
to an extra-cost each extra-cost optional feature.

SYSPR 06-0000-01

SYSPR 06-0010-01
Chapter 7. System Parameter Setting List

(1) DF700 system parameter setting
The following table lists the parameter settings using Storage Navigator Modular.
System Parameter Setting for DF700
System Parameter
1 System Startup Attribute Depends on System Configuration
2 Drive Detach mode enable Disable (Standard setting)
3 Turbo LU Warning Disable (Standard setting)
4 Operation if the Processor failures Occurs Reset a Fault (Standard setting)
5 ROM Microprogram Version No change is needed
6 RAM Microprogram Version No change is needed
7 Write & Verify Executing Mode On (Standard setting)
8 DHCP (*1) OFF (Standard setting)
9 IP Address To be set according to the network setting
10 Subnet Mask To be set according to the network setting
11 Default Gateway To be set according to the network setting
Host Group
1 LU Mapping Mode Depends on System Configuration (*2)
*1 : When the DHCP mode is validated, the IP Address is acquired from the DHCP server.
If the DHCP server is not started up or the DHCP function has been wrongly set, the acquisition of the
IP Address will fail and the IP Address of the subsystem will remain 0.0.0.0. (This is a state in which
Storage Navigator Modular or the Web cannot be used via a LAN.)
In such a case, you can acquire the IP Address by starting up the DHCP server or by setting the DHCP
function correctly when necessary.
*2 : When the SANRISE AMS500 is connected, the logical unit which is not wanted to be accessed by the
port must be masked by means of the LU mapping mode.

SYSPR 07-0000-01
(2) Host Connection Parameters setting

When making the simple setting of the host group options, select items shown on gray
backgrounds.
Only when using the combination not described in the simple setting, select the required
parameter from detail settings.
Host Connection Parameters Setting (1/5)

9: Parameter which is automatically set by the simple setting
blank: Parameter which is manually set if necessary
Host Group Option
Simple Setting
1 Platforms HP-UX
VxVM
2 Alternate Path None PV Link
(*1)
MC/ MC/
3 Fail Over None None None
ServiceGuard ServiceGuard
Detail Setting: The following parameters will be selected automatically according to simple setting.
Standard Mode 9 9 9 9 9
Host Connection Mode 1
Open VMS Mode
(Select one of these
modes) Wolfpack Mode
TRESPASS Mode
HP-UX Mode
PSUE Read Reject Mode
UA(06/2A00) Suppress
Mode
NACA Mode
HISUP OFF Mode
Reset Propagation Mode
Unique Reserve Mode 1
ASL Report Mode
(Active/Passive Group)
Host Connection Mode 2 ASL Report Mode
(Multiple selections) (Active/Passive)
ASL Report Mode
(Active/Active)
Port-ID No Report Mode
Port ID Conversion Mode
TruCluster Mode
Product Serial Response
Mode
Same Node Name Mode
CCHS Conversion Mode
SPC-2 Mode
Additional Parameter: Select these parameters only when you use the appropriate function. When selecting it, the parameter that belongs to the
following host connection mode is automatically selected.
4 Logical Unit Number more than or equals to 8 can be
HP-UX Mode (*2)
recognized by HP-UX
5 TrueCopy is used by Hp-UX PSUE Read Reject Mode
6 VERITAS Database Edition/Advanced Cluster for Oracle
Not selected
7 Egenera BladeFrame Is used Not selected
*1 : When using VERITAS Volume Manager(VxVM), Array Support Library (ASL) for RKM is required. Please
download from the Web screen of VERITAS.
*2 : Up to 256 logical units from logical unit number 0 to logical unit number 255 can be mapped for each host
group. However, the maximum number of logical units a server can recognize is different depending on
the platform.

SYSPR 07-0010-01

Host Group Option
Simple Setting
1 Platforms Solaris
HDLM VxVM MpxIO
2 Alternate Path None
(*1) (*2) (*5)
Sun Sun Sun
VCS VCS
3 Fail Over None Cluster None Cluster None None Cluster
(*3) (*3)
(*4) (*4) (*4)
Standard Mode 9 9 9 9 9 9 9 9 9
Open VMS Mode
TRESPASS Mode
HP-UX Mode
UA(06/2A00) Suppress Mode
NACA Mode
HISUP OFF Mode
ASL Report Mode
ASL Report Mode
(Active/Passive)
(Multiple selections)
ASL Report Mode
(Active/Active)
TruCluster Mode
Mode
Same Node Name Mode
SPC-2 Mode
Not selected
recognized by HP-UX
5 TrueCopy is used by Hp-UX Not selected
6 VERITAS Database Edition/Advanced Cluster for Oracle Unique Unique
RAC (Solaris) is used Reserve Reserv
Not selected Not selected Not selected
Mode 1 e Mode
(*6) 1 (*6)
*1 : When using Hitachi Dynamic Link Manager (HDLM), take notice of the following:
(1) Vendor ID: If this text is changed, it cannot be managed by HDLM. Do not change this text.
(2) Serial Number: When the multiple storages of same types exist, a different Serial Number needs to be
allocated for each disk array subsystem.
*2 : When using VERITAS Volume Manager (VxVM), Array Support Library (ASL) for RKM is required. Please
*3 : VERITAS Cluster Server
*4 : Sun Cluster
*5 : SUN Multi Path (MPxIO)
*6 : When using VERITAS Storage Foundation For Oracle RAC or the IO fencing function supported from the VCS
Ver4.0, the Unique Reserve Mode 1 needs to be set.

SYSPR 07-0020-01

Host Group Option
Simple Setting
1 Platforms AIX
HDLM VxVM
(*1) (*2)
VCS
3 Fail Over None HACMP None HACMP None
(*3)
Standard Mode 9 9 9 9 9 9
Open VMS Mode
TRESPASS Mode
HP-UX Mode
UA(06/2A00) Suppress Mode 9 9 9 9 9 9
NACA Mode (*2) 9 9 9 9 9 9
HISUP OFF Mode
Reset Propagation Mode 9 9
ASL Report Mode
ASL Report Mode
(Active/Passive)
ASL Report Mode
(Active/Active)
TruCluster Mode
Mode
Same Node Name Mode
SPC-2 Mode
Not selected
recognized by HP-UX
6 VERITAS Database Edition/Advanced Cluster for Oracle Unique
RAC (Solaris) is used Not selected Reserve
Mode 1 (*4)

SYSPR 07-0030-01

Host Group Option
Simple Setting
1 Platforms Windows 2000/2003
HDLM VxVM
(*1) (*2)
3 Fail Over None MSCS None MSCS None
Standard Mode 9 9 9 9
Open VMS Mode
modes) Wolfpack Mode 9
TRESPASS Mode
HP-UX Mode
NACA Mode
HISUP OFF Mode
Reset Propagation Mode 9 9
ASL Report Mode
ASL Report Mode
(Active/Passive)
ASL Report Mode
(Active/Active)
TruCluster Mode
Mode
Same Node Name Mode
SPC-2 Mode
Not selected
recognized by HP-UX
6 VERITAS Database Edition/Advanced Cluster for Oracle
Not selected

SYSPR 07-0040-01

Host Group Option
Simple Setting
Others
1 Platforms Linux Tru64 Not
specified
VxVM
2 Alternate Path None None None
(*1)
VCS VCS Tru
3 Fail Over None None None None
(*2) (*2) Cluster
Standard Mode 9 9 9 9 9 9 9
Open VMS Mode
TRESPASS Mode
HP-UX Mode
NACA Mode
HISUP OFF Mode
ASL Report Mode
ASL Report Mode
(Active/Passive)
ASL Report Mode
(Active/Active)
TruCluster Mode 9
Mode
Same Node Name Mode
SPC-2 Mode
4 Logical Unit Number more than or equals to 8 can be Not
Not selected Not selected
recognized by HP-UX selected
5 TrueCopy is used by Hp-UX Not
selected
6 VERITAS Database Edition/Advanced Cluster for Oracle Unique Unique
RAC (Solaris) is used Not Reserve Not Reserve Not
Not selected
selected Mode 1 selected Mode 1 selected
(*3) (*3)
7 Egenera BladeFrame Is used Not
selected

SYSPR 07-0050-01
FE-95DF749-00
Addition/Subtraction/Relocation
Chapter 1. Adding Optional Components .........................................................................ADD 01-0000
Chapter 2. Subtracting Optional Components ..................................................................ADD 02-0000
Chapter 3. Relocation/Removal Work...............................................................................ADD 03-0000

ADD 00-0000-01

ADD 00-0010-01
Chapter 1. Adding Optional Components

1.1 Before Starting Addition of Optional Components
If you make a mistake in operation during an addition of the optional component, it is feared
that user data in the subsystem is lost. Therefore, perform the following before starting the
addition of the optional component to provide against an unexpected accident.
(1) Backup user data.

Backup user data in the subsystem by the operation on the host computer side.
(2) The work to add an optional component varies depending on the component and a location
where the component is to be installed. Besides, perform the addition after making sure
whether the work must be done with the subsystem power on or off.
y An addition with the subsystem power on :
A status in which the subsystem power is turned on irrespective of whether the system (host
computer) is turned on or off.
y An addition with the subsystem power off :
(3) When adding the optional component, it is required to change the settings of the subsystem
using a service PC connected via a LAN. Make the following preparations before starting the
addition of the optional component.
y Prepare a PC in which Storage Navigator Modular is installed. The PC must be used in the
LAN environment.
y Ask the customer whether the subsystem is operable via a LAN. If not, obtain customers
permission to operate the subsystem via a LAN.
(4) Promote mutual understanding with the user about the possibility of a system down in order to
minimize damage caused by failures.
(5) When adding the optional component with the subsystem power on, the operation replacing
dummy Disk Drive with Disk Drive has to be finished within 10 minutes.
(6) Do not make the addition work when the READY LED (green) on the Front Bezel is blinking at
high speed. When it is high-speed blinking, the ENC/SENC firmware is being downloaded.
Make the addition work after making sure that the READY LED (green) lights on after the
maximum of 30/50 minutes.

ADD 01-0000-01
1.2 Procedures for Adding Optional Components

(1) Procedure for adding an optional component while the subsystem power on
NOTE : y For safety use, always close the front bezel after the operation.
y Service personnel must check if a customer has backed up user data. If the
customer does not perform the backup, start the work after getting
customers permission.
Work-1 Unpacking rack frame See Installation 3.2 Unpacking and Installing
Rack Frame (INST 03-0020)
Work-2 Mounting the RKAJ/RKAJAT on rack frame See 1.3 Mounting RKAJ/RKAJAT on Rack
Frame (ADD 01-0100)
Work-3 Adding optional components See 1.4 Adding Optional Components

(1) Adding Disk Drive (ADD 01-0130)
Work-4 Adding Other Optional Devices See 1.5 Adding Other Optional Devices
(ADD 01-0450)
(1) Adding a PDU
(2) Adding a PDB
Floor Model : See Installation 2.6 Connecting

Work-5 Connecting cables Cables (INST 02-0300)
Rackmount Model : See Installation 3.4.8
Connecting Cables (INST 03-0610)
See System Parameter 1.1 Procedure for

Work-6 Connection of a service PC and the subsystem connecting Storage Navigator Modular with the
subsystem (SYSPR 01-0010)
Be sure to make the setting of the system

Work-7 Subsystem setting made information when any of the Disk Drives
by the operation of the service PC RKM/RKS#0 to RKM#4 has been added.
(1) Restoring the system information See Troubleshooting 10.2.7 Drive Maintenance
(2) Setting of a Spare Disk (TRBL 10-0330)
(3) Setting of RAID and an LU See System Parameter Chapter 3. Setting the
RAID/LU/Spare Disk (SYSPR 03-0000)
(4) Setting of a LUN recognition

ADD 01-0010-01
(2) Procedure for adding an optional component while the subsystem power off
y For the see Installation 1.7.2 Subsystem power off (INST 01-0310).
y Service personnel must check if a customer has backed up user data. If the
customer does not perform the backup, start the work after getting
customers permission.
Work-1 Unpacking rack frame See 1.2.1 Unpacking (ADD 01-0090)
Work-2 Setting the power control mode to Local See Installation 1.8 Setting the Power Control
Mode (Local/Remote Mode) (INST 01-0320)
Work-3 Subsystem power off See Installation 1.7.2 Subsystem power off
(INST 01-0310)
Work-4 Mounting the RKAJ/RKAJAT on rack frame See 1.3 Mounting RKAJ/RKAJAT on Rack
Frame (ADD 01-0100)
Work-5 Adding optional components See 1.4 Adding Optional Components

(1) Adding Control Unit (ADD 01-0130)
(2) Adding Disk Drive
(3) Adding Cache Unit
(4) Adding Interface Board (RKM)
Work-6 Adding Other Optional Devices See 1.5 Adding Other Optional Devices
(ADD 01-0450)
(1) Adding a PDU
(2) Adding a PDB
Floor Model : See Installation 2.6 Connecting
Work-7 Connecting cables Cables (INST 02-0300)
Rackmount Model : See Installation 3.4.8
Connecting Cables (INST 03-0610)
Work-8 Subsystem power on See Installation 1.7.1 Subsystem power on
(INST 01-0290)
Work-9 See System Parameter 1.1 Procedure for

Connection of a service PC and the subsystem
connecting Storage Navigator Modular with the
Work-10 Subsystem setting made See System Parameter Chapter 7. System
by the operation of the service PC Parameter Setting List (SYSPR 07-0000),
(1) Setting of System Parameter Chapter 2. Setting Host Group (SYSPR 02-0000) to
Chapter 6. Setting an Extra-cost Optional Feature
(2) Setting of host group
(SYSPR 06-0000)
(3) Setting of RAID, LU, and Spare Disk
(4) Setting of configuration information
mode
(6) Setting a priced optional feature
A To ADD 01-0030

ADD 01-0020-01
A From ADD 01-0020
(INST 01-0310)
Work-12 Check by means of subsystem restart See Installation 1.7.1 Subsystem power on
(INST 01-0290)
Work-13 Setting the Power Control Mode See Installation 1.8 Setting the Power Control
(Local/Remote Mode) Mode (Local/Remote Mode) (INST 01-0320)
y When you do not want to change the setting of
the power control, return the setting of the
local/remote mode, which was changed in Work-
2, to the original one.
(INST 01-0310)

ADD 01-0030-01
(3) Component to be added and condition of addition
(3-1) Rackmount disk array for extension
Condition of addition and number of item

for referring to procedure
Component name Model name Specification Requirements of addition Power on
(A host is in Power off
operation (*1).)
Rackmount disk DF700-RKAJ A set of an disk array and Prepare the following Possible Possible
array for extension DF700-RKAJAT basic accessories to be components at least for the 1.7 Adding the 1.7 Adding the
mounted on a rack frame disk array to be added. RKAJ/RKAJAT to RKAJ/RKAJAT to
Two Disk Drives the Rack Frame the Rack Frame
Up to 14 RKAJs can be (ADD 01-0750) (ADD 01-0750)
added to the one RKM.
y Up to 14 RKAJATs can be
connected to the one RKM
y A mixed configuration, in
which up to the 14
RKAJ(s)/RKAJAT(s) are
connected to the one RKM.
Up to 6 RKAJs can be added
to the one RKS.
y Up to 6 RKAJATs can be
connected to the one RKS
y A mixed configuration, in
which up to the 6
RKAJ(s)/RKAJAT(s) are
connected to the one RKS.
*1 : Data is exchanged between a host computer and the subsystem.

ADD 01-0040-01
(3-2) Optional components for addition

Component name Model name Specification Requirements of addition Power on
operation (*1).)
Control Unit DF-F700-F1JM Array Control Unit Install the Cache memory Impossible Possible
(2port) for duplication with a capacity same as that 1.4.2 Adding a
For RKM of the Cache memory of the Control Unit
DF-F700-F1JS Array Control Unit installed Control Unit (#0 (ADD 01-0140)
(1port) for duplication side).
For RKS
Disk Drive(*2) DF-F700-AGF72 3.5-inch Disk Drive Select from the Disk Drives Varies depending Varies depending
(Including Spare (71.3 G bytes) shown on the left according on the disk array to on) the disk array
Disk) to the intended total capacity be added. to be added.
DF-F700-AGF146 3.5-inch Disk Drive of the subsystem.
(143.3 G bytes) Up to 15 Spare Disks can be
1.4.3 Adding a 1.4.3 Adding a
DF-F700-AGF300 3.5-inch Disk Drive set up in the whole
Disk Drive Disk Drive
(287.6 G bytes) subsystem.
(ADD 01-0190) (ADD 01-0190)
DF-F700-ATE250R 3.5-inch Disk Drive
(RKAJAT) (245.7 G bytes)

Cache Unit DF-F700-C1GJ Cache memory y For the dual Control Unit, Impossible Possible
1,024 M bytes install the Cache Unit of the 1.4.4 Adding a
same capacity in the Control Cache Unit
Unit #0 and #1. (ADD 01-0410)

ADD 01-0050-01
(3-3) Addition/subtraction of Disk Drive/disk array
Addition for storage Replacement for storage capacity

capacity expansion expansion
Replacement with the Disk Drive(s) having
Unit of Addition of the disk array(s) or the Disk Drive(s) in
Component to be larger capacity in order to expand a
No. addition/ order to expand a storage capacity
added/subtracted storage capacity
subtraction
Power on
Power on
Power off (A host is in Power off
(A host is in operation(*1))
operation(*4))
1 Disk array RKAJ Possible(*2) Possible(*2)
(*3) (*3)
(RKM/RKS is connected) (The final RKAJ only) (The final RKAJ only)
Refer to Refer to

1.6 Adding the RKAJ to 1.6 Adding the RKAJ to
the Rack Frame (ADD the Rack Frame (ADD
01-0490) 01-0490)
2 RKAJ/RKAJAT Possible(*2) Possible(*2)
(*3) (*3)
(RKM/RKS is connected) (The final RKAJ/RKAJAT (The final
only) RKAJ/RKAJAT only)
Refer to Refer to

1.7 Adding the 1.7 Adding the
RKAJ/RKAJAT to the RKAJ/RKAJAT to the
Rack Frame (ADD 01- Rack Frame (ADD 01-
0750) 0750)
3 Disk Drive RKM /RKS Possible Impossible Possible(*3) Impossible
#0 to 4 Refer to Refer to
1.4.3 (2-1) Procedure 1.4.3 (3-1) Procedure
for adding Disk Drive (in for replacing Disk Drive
order to expand a (in order to expand a
storage capacity) while storage capacity) while
the subsystem power is the subsystem power is
on (ADD 01-0250) on
(ADD 01-0290)
4 RKM /RKS Possible Possible Possible Possible
#5 to 14 Refer to Refer to Refer to Refer to
1.4.3 (2-1) Procedure 1.4.3 (2-2) Procedure 1.4.3 (3-1) Procedure 1.4.3 (3-2)
for adding Disk Drive (in for adding Disk Drive (in for replacing Disk Drive Procedure for
order to expand a order to expand a (in order to expand a replacing the Disk
storage capacity) while storage capacity) while storage capacity) while Drive (in order to
the subsystem power is the subsystem power is the subsystem power is expand a storage
on (ADD 01-0250) off on capacity) while the
(ADD 01-0260) (ADD 01-0290) subsystem power
is off
(ADD 01-0310)
*2 : The RKAJ/RKAJAT can be added at the end of the configuration. An addition in the middle of the configuration
cannot be done.
*3 : In the replacement for storage capacity expansion, it is not necessary to replace the disk array. Replace only the
Disk Drive(s) installed in the disk array.
*4 : When performing an addition or replacement of any of the Disk Drives #0 to #4 in the RKM/RKS in order to expand
a storage capacity, a restoration of the system information on the added Disk Drive must be done. Be sure to
perform the addition or replacement while the subsystem power is on and restore the system information.

ADD 01-0060-01
Addition for storage Replacement for storage capacity

capacity expansion expansion
Replacement with the Disk Drive(s) having
Unit of Addition of the disk array(s) or the Disk Drive(s) in
Component to be larger capacity in order to expand a
No. addition/ order to expand a storage capacity
added/subtracted storage capacity
subtraction
Power on Power on
(A host is in Power off (A host is in Power off
operation(*1).) operation(*1).)
5 RKAJ Possible(*2) Possible(*2) Possible Possible
is off
(ADD 01-0310)
6 RKAJ Possible Possible Possible Possible
is off
(ADD 01-0310)
7 RKAJAT Possible(*3) Possible(*3) Possible Possible
is off
(ADD 01-0310)
RKAJAT Possible Possible Possible Possible
8 #4 to 14 Refer to Refer to Refer to Refer to
is off
(ADD 01-0310)
*2 : If the RKAJ/RKAJAT is not mounted when adding any of the Disk Drives #0 to #3 to the RKAJ/RKAJAT, add it first
*3 : When performing an addition or replacement of any of the Disk Drives #0 to #4 in the RKM/RKS in order to expand
a storage capacity, a restoration of the system information on the added Disk Drive must be done. Be sure to
perform the addition or replacement while the subsystem power is on and restore the system information

ADD 01-0070-01
(3-4) Other optional additional device

Component
Model name Specification Requirements of addition Power on
name
operation(*1).)
PDB DF-F700-UPDU7 For U7 Additional PDB for U7 rack Possible Possible
frame 1.5.2 Mounting a 1.5.2 Mounting a
PDB (UPDU7) PDB (UPDU7)
(ADD 01-0460) (ADD 01-0460)
(4) Tool for optional work
Table 1.1.1 Tool for Optional Work

Rackmount Model
Division Tool name Specification Floor Model
(U7 rack frame)
Tool Lifter - - {
Phillips screwdriver No.1 { {
Phillips screwdriver No.2 { {
Slotted screwdriver No.1 { {
Allen wrench No.3 { -
Allen wrench No.4 - {
Spanner No.8 - -
Spanner No.13 - -
Spanner No.22 - {
Tool of other LAN cross cable Category 5 { {
PC for maintenance(*1) Pentium { {
Safekeeping box - { {
*1 : For maintenance. (Pentium (Pentium II (233 MHz or more) is recommended.)
Memory 40 Mbytes or more. (64 Mbytes or more is recommended.)
For the usage of the tools for adding optional components, refer to the chapter for each type.

ADD 01-0080-01
1.2.1 Unpacking
(1) Checking exterior of optional component
Check the exterior of each component visually for distortion or damage owing to transport.
Check if the contents of the package (their model names, product serial numbers, and

ADD 01-0090-01
1.3 Mounting RKAJ/RKAJAT on Rack Frame

In the case of adding Disk Drives to a subsystem of the rackmount model, the RKAJ /RKAJAT
must be added when vacant slots for the Disk Drives to be added are insufficient in the
existing subsystem.
There are two procedures for adding the RKAJ/RKAJAT, that is, an addition to be done while
the subsystem power is on and that to be done while the subsystem power is off.
For the procedures, refer to the following items.
For the procedure for the addition performed when the RKM is connected, refer to 1.6.1
Procedure for adding the RKAJ to the subsystem of rackmount model with U7 rack frame
(ADD 01-0490).
For the procedure for the addition performed when the RKM is connected, refer to 1.7.1
Procedure for adding the RKAJ/RKAJAT to the subsystem of rackmount model with U7 rack
frame (ADD 01-0750).

ADD 01-0100-01
1.3.1 Work immediately after abnormal termination

When a trouble occurs during addition of a subsystem nit to a rack frame, you can separate
the part suspected of having failed from the subsystems already installed (including additional
subsystems addition of which has been completed normally).
Take recovery actions against the trouble after performing the following operations, and then
make the addition again.
(1) Make sure of the additional subsystem addition of which terminated abnormally.
Make sure of the additional subsystems addition of which terminated abnormally according to
one of the following messages displayed in the Information Message window of the Web as
shown below.
When the message, #I8040x Unit ADD FAIL is displayed, an additional subsystem with an ID
number pointed out in the message, I8040x Unit ADD FAIL is the one searched for.
When there is an additional subsystem for which the message, I8000x Unit ADD start is not
displayed for longer than five minutes after the message, I8020x Unit ADD complete is
displayed, an additional subsystem with an ID number next to that pointed out in the
message, I8020x Unit ADD complete is the one searched for.
When the message I8020x Unit ADD complete is never displayed, it is the added chassis
connected with the existing subsystem.
(2) Construct the current subsystem configuration with the ACE tool of Storage Navigator
Modular, and then display the ENC cable connection diagram. (Refer to Installation 1.6.2
Checking methods of device ID and ENC cable connection when mounting the newly introduced
rack (INST 01-0180).
(3) Select the additional disk array unit addition of which terminated abnormally in the ENC cable.
Addition of which terminated

abnormally

ADD 01-0110-01
(4) Select the subsystems upper than the additional subsystem, addition of which terminated
abnormally, pressing the Ctrl Key.
(5) Remove the ENC cables, which connect subsystems displayed in orange and blue in the ENC
cable connection diagram and are displayed with red and blue solid lines in the diagram, one
by one at intervals of 20 seconds or more. (1)
CAUTION
If the ENC cables are removed without ensuring intervals of 20 seconds or more, it
is feared that the system goes down.
(6) Turn off all the AC Input Power Switches of the added chassis indicated in orange after
rechecking that the ENC cable of a red solid line and a blue solid line which is connecting the
orange subsystem and the white subsystem was removed (1).
CAUTION
The system may go down if the AC Input Power Switch is turned off with the
instructed ENC cable connected.
1 : When the system goes down, be sure to perform the procedures (5) and (6) continuously, and then turn off the
main switch and turn it on after one or more minutes have elapsed. In that case, do not turn off the battery
switch of the Backup Battery Unit in front of the subsystem. If it is turned off, the user data lost may occur.

ADD 01-0120-01
1.4 Adding Optional Components

1.4.1 Subsystems optional components for addition

Component
name
operation (*1).)
Control Unit DF-F700-F1JM Array Control Unit for Install the Cache memory Impossible Possible
duplication (2port) with a capacity same as that 1.4.2 Adding a
In the RKM of the Cache memory of the Control Unit
DF-F700-F1JS Array Control Unit for installed Controller (#0 side). (ADD 01-0140)
duplication (1port).
In the RKS
Disk Drive(*2) DF-F700-AGF72 3.5-inch Disk Drive Select from the Disk Drives Varies depending Varies depending
(including Spare (71.3 G bytes) shown on the left according to on the disk array to on) the disk array
Disk) the intended total capacity of be added. to be added.
DF-F700-AGF146 3.5-inch Disk Drive
the subsystem.
(143.3 G bytes)
Up to fifteen Spare Disks can 1.4.3 Adding a 1.4.3 Adding a
DF-F700-AGF300 3.5-inch Disk Drive be set up in the whole. Disk Drive Disk Drive
(287.6 G bytes) (ADD 01-0190) (ADD 01-0190)


Cache Unit DF-F700- C1GJ Cache memory For the dual Control Unit, Impossible Possible
1,024 M bytes install the Cache Unit of the 1.4.4 Adding a
same capacity in the Control Cache Unit
Unit #0 and #1. (ADD 01-0410)

ADD 01-0130-01
1.4.2 Adding a Control Unit

An addition of the Control Unit is done when duplicating the Control Unit.
CAUTION
Touching heat sinks or ICs may cause getting burned. Be sure to handle with
care.
CAUTION
damage the parts.

A Control Unit to be unpacked and
replaced for maintenance

Connect this to the metal part
on the frame of subsystem (rear
face)
Support a Control Unit by touching A wrist strap (Be sure to wear this before
its metal part (metal plate) with your starting maintenance.)
fingers

ADD 01-0140-01

(2) Make sure that the PWR (POWER) LED (green) on the panel goes out.
NOTE : When the power has already been turned off, make sure that the cache is not in
the cache backup mode. (Refer to Replacement , 1.1.2 Checking cache
memory in the back-up state (REP 01-0030).)
When the cache is in the cache backup state, cancel the status.
(3) Make sure that the CACHE POWER LED (green) on the Controller is off.
When the CACHE POWER LED (green) is on, user data which has not written on the disk exists in
the cache memory.
(4) Turn off the AC Power Unit Switch of the Power Unit (#0, #1).
(5) Remove the dummy (control Unit).
Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down
the levers forward, and pull out the Control Unit.
(6) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the direction
shown by the arrow (), and remove it.
(7) Remove the dust cover from the cash slot of the Control Unit #1 to be added
(Insert the dust cover in the Cache slot in which the Cache memory is not installed).
(8) Install the Cache memory, which has the same capacity as that of the installed Controller#0, in
the Controller#1 to be added by the set of two boards.
(9) In the case of RKM, Install the Interface Board to be added on the Control Unit fitting it to the
positioning pin and fasten it by tightening the five mounting screws.
(10) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
fixing screw for the cover at the back of the cover.
(11) Insert it into the specified position with the both right and left levers of the Control Unit
pushed down, raise the levers with the hooks fitting to the cutouts of the subsystem, and
tighten the fixing screw for the lever.
NOTE : Do not catch a ENC cable, when the Control Unit for the inserted.
The installation direction is different in the Control Unit # 0 and # 1. Install
the Control Unit #0 with the cover up and #1 with the cover down.
(12) Connect the interface cable, the LAN cable, and the ENC cable.
NOTE : When connecting the Interface cable and the ENC cable, give it a bend with a
long radius (not less than 30 mm) so as not to apply the cable and the
The installed direction is different in the Control Unit #0 and #1, so that be
careful of the connecting position of the cables.
(13) Turn on the AC Power Unit Switch of the Power Unit.

(15) Make sure that the RDY (READY) LED (green) on the front side of the subsystem comes on.

ADD 01-0150-01
(16) Connect the PC to be connected with Storage Navigator Modular and the Control Unit #0 with a
LAN cable. (System Parameter 1.1 Procedure for connecting Storage Navigator Modular with
the subsystem (SYSPR 01-0010))
(17) Set the system starting attribute of the system parameters in order to operate the subsystem
as that having the dual controller system. (System Parameter Chapter 4. Setting
Configuration Information (SYSPR 04-0000))
Besides, since the following message is displayed after the system parameters have been set,
click the [OK] button.

(20) Turn on the main switch after waiting for one minute or longer.
(22) Because the subsystem configuration was changed form single controller to the dual controller,
register the disk array subsystem as having the dual controller configuration with Storage
Navigator Modular. (System Parameter 1.1 Procedure for connecting Storage Navigator
Modular with the subsystem (SYSPR 01-0010)))
(23) Reset the system parameters for the Control Unit #1.
NOTE : A setup for the dual controller is necessary for the controller 1.
(System Parameter Chapter 4. Setting Configuration Information (SYSPR 04-
0000))
When the cache is in the cache backup state, cancel the status.

(26) Remove the LAN cable connected to the Storage Navigator Modular from the Control Unit#0.

ADD 01-0160-01
Control Unit #0
Cover
Control Unit #1
Fixing screw
Lever
Slot lever Removal :
Fixing screw Press open the slot lever to
outside and pull out the cache
Socket memory by holding the both end
by hand.
Cut Installation :
Projections Fit the projection and the cut and
cutout inside the slot push it into the slot by holding the
both end by hand.
Control Unit (front side) CALM LED (red) CACHE POWER LED (green)
CHKSTP LED (green) RST SW Port 1A-1
PATH #1 PATH #0 EALM LED (red) Port 1A-0
Control Unit #1
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0A-0 EALM LED (red) PATH #0 PATH #1

Port 0A-1 RST SW CHKSTP LED (green)
CALM LED (red)
CACHE POWER LED (green)
Figure 1.4.1 Adding the Control Unit (RKS)

ADD 01-0170-01
Control Unit #0
Cover
Positioning hole
Interface Board
Fixing screw
Control Unit #1
Positioning pin Lever

: Fixing Screw for Interface Board
Slot lever (five screws)
Fixing screw
Removal :
Press open the slot lever to
Socket
Cut memory by holding the both end
by hand.
cutout Projections Installation :
slot #1 slot #0 inside the slot Fit the projection and the cut and
both end by hand.
PATH #1 PATH #0 EALM LED (red) Port 1B-0 Control Unit #1
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0B-0 EALM LED (red) PATH #0 PATH #1

CALM LED (red)
Figure 1.4.1.1 Adding the Control Unit (RKM)

ADD 01-0180-01
1.4.3 Adding a Disk Drive

A procedure for adding/subtracting the Disk Drive varies depending on a location of the Disk
Drive and a condition (whether the subsystem power is on or off).
Take care to use a procedure appropriate for the purpose because a use of an inappropriate
procedure may cause an accident such as a loss of user data.
Table 1.4.1 Kinds of Disk Drive Addition and Subtraction

Addition for storage capacity expansion Replacement for storage capacity expansion
Unit of Component to Addition of the disk array(s) or the Disk Drive(s) in Replacement with the Disk Drive(s) having larger
No. addition/ be added/ order to expand a storage capacity capacity in order to expand a storage capacity
subtraction subtracted Power on Power on
Power off Power off
(A host is in operation(*1).) (A host is in operation(*1).)
1 Disk Drive RKM/RKS Possible Impossible Possible(*2) Impossible
#0 to 4 Refer to Refer to
1.4.3 (2-1) Procedure for 1.4.3 (3-1) Procedure for
adding Disk Drive (in replacing Disk Drive (in
order to expand a storage
capacity) while the
capacity) while the
subsystem power is on
(ADD 01-0290)
(ADD 01-0250)
2 RKM/RKS Possible Possible Possible Possible
1.4.3 (2-1) Procedure for 1.4.3 (2-2) Procedure for 1.4.3 (3-1) Procedure for
1.4.3 (3-2) Procedure for
adding Disk Drive (in adding Disk Drive (in replacing Disk Drive (in
replacing the Disk Drive
order to expand a storage order to expand a storage
(in order to expand a
capacity) while the capacity) while thestorage capacity) while
capacity) while the
subsystem power is off subsystem power is on
the subsystem power is
subsystem power is on off
(ADD 01-0260) (ADD 01-0290)
(ADD 01-0250) (ADD 01-0310)
3 RKAJ #0 to 3 Possible (*3)
Possible (*2)
Possible Possible
Refer to Refer to Refer to Refer to
1.4.3 (2-1) Procedure for 1.4.3 (2-2) Procedure for 1.4.3 (3-1) Procedure for 1.4.3 (3-2) Procedure for
adding Disk Drive (in adding Disk Drive (in replacing Disk Drive (in replacing the Disk Drive
order to expand a storage order to expand a storage (in order to expand a
capacity) while the capacity) while the storage capacity) while
capacity) while the
subsystem power is off subsystem power is on the subsystem power is
(ADD 01-0260) (ADD 01-0290)
(ADD 01-0250) (ADD 01-0310)
*2 : If the RKAJ/RKAJAT is not mounted when adding any of the Disk Drives #0 to #3 to the RKAJ/RKAJAT, add it first.
*3 : When performing an addition or replacement of any of the Disk Drives #0 to #4 in the RKM /RKS in order to
expand a storage capacity, a restoration of the system information on the added Disk Drive must be done. Be
sure to perform the addition or replacement while the subsystem power is on and restore the system information.

ADD 01-0190-01
Addition for storage capacity expansion Replacement for storage capacity expansion
Unit of Component to Addition of the disk array(s) or the Disk Drive(s) in Replacement with the Disk Drive(s) having larger
No. addition/ be added/ order to expand a storage capacity capacity in order to expand a storage capacity
subtraction subtracted Power on Power on
Power off Power off
(A host is in operation(*1).) (A host is in operation(*1).)
4 RKAJ #4 to 14 Possible Possible Possible Possible
Refer to Refer to Refer to Refer to
capacity) while the
(ADD 01-0260) (ADD 01-0290)
(ADD 01-0250) (ADD 01-0310)
5 RKAJAT Possible(*3) Possible(*2) Possible Possible
capacity) while the
(ADD 01-0260) (ADD 01-0290)
(ADD 01-0250) (ADD 01-0310)
6 RKAJAT Possible Possible Possible Possible
capacity) while the
(ADD 01-0260) (ADD 01-0290)
(ADD 01-0250) (ADD 01-0310)
*2 : If the RKAJ/RKAJAT is not mounted when adding any of the Disk Drives #0 to #3 to the RKAJ/RKAJAT, add it first.
*3 : When performing an addition or replacement of any of the Disk Drives #0 to #4 in the RKM /RKS in order to
expand a storage capacity, a restoration of the system information on the added Disk Drive must be done. Be
sure to perform the addition or replacement while the subsystem power is on and restore the system information.

ADD 01-0200-01
(1) Before starting addition of Disk Drive
CAUTION
damage the parts.
Disk Drives are precision components.
Be careful not to expose drives to hard shock.
When you install a Disk Drive, support its metal part with your hand that has the
NOTE : The Disk Drive is a precision machine. Never apply a shock or vibration to it.
Before unpacking and replacing maintenance components, be sure to wear a
wrist strap and connect to ground the grounding clip in the opposite end of
the wrist strap to the chassis frame (metal part).
When you insert a Disk Drive into the subsystem, support the Disk Drive as
Disk Drive

Connect this to the metal part on
the frame of subsystem (front
face)
A wrist strap (Be sure to wear this before

Support a Disk Drive by touching its

ADD 01-0210-01
(a) Locations and numbers of Disk Drives

The mounting position number of the Disk Drive is decided by the combination of the Disk
Drive number set to the device number (device ID).
Set #0 for the device ID of RKM/RKS and set the device ID of RKAJ/RKAJAT as follows.
Set #0x for the device ID of RKAJ.
Note : Set x in ascending order in PATH #0 and #1 without the distinction of

RKAJ/RKAJAT.
For details of the device ID setting, refer to Installation 1.6 Device ID Setting and ENC Cable
Connection (INST 01-0160).
Set the subsystem identification switch for the RKAJ.
The Disk Drive number is #0 to #14 from the left sequentially seen sideways (for the floor
model, it is #0 to #14 from the bottom).

Device ID setting
RKAJAT RKAJAT
This figure shows an
example in which the
Device ID is set as
#01.
RKAJ RKAJ Subsystem

identification switch
The figure is a setting
example when the
basic subsystem is the
RKM.
RKM RKM
Disk Drive
RKAJAT
Disk Drive number #0 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
RKAJ
RKM/RKS

ADD 01-0220-01
(b) If necessary number of vacant slots do not exist in the subsystem to which the Disk Drives are
to be added(1).
Arrange to mount two or more Disk Drives(2) on the added RKAJ/RKAJAT.
Set the Device ID number of the RKAJ/RKAJAT to be added.
(c) Up to 15 Disk Drives to be set as the Spare Disks can be mounted in any locations(3).
Assign the Disk Drive, which has not been assigned to be a data disk, to be a Spare Disk.
1 : In the case of adding RKAJ to RKM, refer to 1.6 Adding the RKAJ to the Rack Frame (ADD 01-0490).
In the case of adding RKAJ/RKAJAT to RKM, refer to 1.7 Adding the RKAJ/RKAJAT to the Rack Frame (ADD 01-
0750).
2 : The two of them must be installed in the slots Disk Drive #0 and Disk Drive #1.
3 : No Spare Disk can be set for the Disk Drives #0 to #4 of the RKM and RKS.

ADD 01-0230-01
(2) Procedure for adding Disk Drive (in order to expand a storage capacity)
A procedure for adding the Disk Drive to a vacant slot of the RKM/RKS/RKAJ /RKAJAT is
shown below.
When an addition of the RKAJ /RKAJAT is necessary because of insufficient vacant slots, add
the RKAJ /RKAJAT first following the procedure explained in the item shown below.
1.6 Adding the RKAJ to the Rack Frame (ADD 01-0490).
1.7 Adding the RKAJ/RKAJAT to the Rack Frame (ADD 01-0750).
An addition of a Disk Drive to any of the vacant slots #2 to #4 cannot be done while the
subsystem power is off. Make the addition following the procedure shown in Item
(2-1), and be sure to perform a system copy to the added Disk Drive.
It is recommended to backup data of all LUs to provide against an emergency because user
data may be lost if a wrong operation is done.
The work for addition varies depending on whether the work is done while the power is turned
on or off.
Procedure for adding a Disk Drive while the power is turned on: See (2-1) Procedure for
adding Disk Drive (in order to expand a storage capacity) while the subsystem power is on
(ADD 01-0250).
Procedure for adding a Disk Drive while the power is turned off: See (2-2) Procedure for
adding Disk Drive (in order to expand a storage capacity) while the subsystem power is off
(ADD 01-0260).

ADD 01-0240-01
(2-1) Procedure for adding Disk Drive (in order to expand a storage capacity) while the subsystem
power is on
A procedure for adding the Disk Drive (in order to expand a storage capacity) without
shutting down the subsystem is shown below.
NOTE : When adding the two or more Disk Drives in the installation of the Disk Drives
(Work-4), complete the restoration of the system information (Work-5) for the
each Disk Drive one by one, and then install the Disk Drives one by one.
Start
Work-1 Unpacking the Disk Drive See 1.2.1 Unpacking (ADD 01-0090)
See Installation 1.5 How to Open/Close Door or

Work-2 Detaching the front bezel
Attach/Remove Front Bezel/Rear Cover of the
Subsystem (INST 01-0100)
Work-3 Remove the dummy (Disk Drive). See (4-1) When adding the Disk Drive (in order to
expand a storage capacity) (ADD 01-0330)
Perform Work-3 soon after the completion of Work-4.
Work-4 Installing the Disk Drive Install the Disk Drive to be added taking care not to
apply any shock to it.
See (4-1) When adding the Disk Drive (in order to
Work-5 Restoring the system information Be sure to restore the system information when any of
the Disk Drives#2 to #4 of the RKM/RKS/ is added.
Refer to (5) Restoring the system information (ADD
01-0360)
Work-6 Attaching the front bezel
Work-7 Setting the system information For the added Disk Drive, perform a setting of RAID/LU,
formatting of an LU, setting of a Spare disk, and setting
Setting of RAID/LU
of an LU mapping, etc.
Formatting of an LU See System Parameter Chapter 3. Setting the
Setting of a Spare Disk RAID/LU/Spare Disk (SYSPR 03-0000)
Setting of an LU mapping, etc.
Work-8 Making a host computer recognize the LU Refer to an instruction manual of each host computer.
Example : For operation in the case of a host computer
in which HP-UX is installed, refer to (6)
Making a host computer recognize an LU
while the subsystem power is on (ADD
01-0390).
END

ADD 01-0250-01
(2-2) Procedure for adding Disk Drive (in order to expand a storage capacity) while the subsystem
power is off
A procedure for adding the Disk Drive (in order to expand a storage capacity) after turning
off the subsystem power is shown below.
Start
(INST 01-0310)
Work-3 Checking a status of backing up Make sure that the Cache memory is not being backed
the Cache memory up. If the Disk Drive is added without canceling the
backup, user data may be lost.
Refer to See System Parameter 1.1 Procedure for
subsystem (SYSPR 01-0010).
Work-4 Setting the power control mode to Local(*1) For the Setting the Power Control Mode (Local or
Remote), refer to the following page.
See Installation 1.8 Setting the Power Control Mode
Work-5 Detaching the Front Bezel See Installation 1.5 How to Open/Close Door or
Work-6 Installing the Disk Drive Install the Disk Drive to be added taking care not to
apply any shock to it.
See (4-1) When adding the Disk Drive (in order to
Work-7 Attaching the Front Bezel See Installation 1.5 How to Open/Close Door or
Work-8 Powering on the subsystem See Installation 1.7.1 Subsystem power on
(INST 01-0290)
Setting of RAID/LU formatting of an LU, setting of a Spare disk, and setting
Formatting of an LU
See System Parameter Chapter 3. Setting the
Work-8 Setting of a Spare Disk RAID/LU/Spare Disk (SYSPR 03-0000)
(INST 01-0310)
A To ADD 01-0270
*1 : When the subsystem power control works interlocking with the UPS, etc., make an adjustment so that the power is
supplied to it.

ADD 01-0260-01
A From ADD 01-0260
Work-11 Returning the setting of the power control (Local or For the Setting the Power Control Mode (Local or
Remote) to the original one Remote), refer to the following page.

(INST 01-0290)
Work-13 Installing a host computer Refer to an instruction manual of each host computer.
END

ADD 01-0270-01
(3) Procedure for replacing Disk Drive (in order to expand a storage) capacity
A procedure for replacing the Disk Drive installed in the RKM/RKS/RKAJ/RKAJAT with the Disk
Drive having a larger capacity is shown below.
When replacing two or more Disk Drives, be sure to replace them one by one in order of
location.
The replacement of any of the Disk Drives#0 to #4 of the RKM /RKS cannot be done while the
subsystem power is off. Therefore, perform the replacement following the procedure shown
in Item (2-1), and be sure to perform a system copy to the added Disk Drive.
It is recommended to backup data of all LUs to provide against an emergency because user
The procedure for the replacement varies depending on whether the replacement is performed
while the power is turned on or off.
Procedure for replacing Disk Drive (in order to expand a storage capacity)
while the subsystem power is on.................................(3-1) Procedure for replacing
Disk Drive (in order to expand a storage capacity) while the subsystem power is on (ADD 01-
0290)
Procedure for replacing the Disk Drive (in order to expand a storage capacity)
while the subsystem power is off ................................(3-2) Procedure for replacing
the Disk Drive (in order to expand a storage capacity) while the subsystem power is off (ADD
01-0310)

ADD 01-0280-01
(3-1) Procedure for replacing Disk Drive (in order to expand a storage capacity) while the
A procedure for replacing the Disk Drive (in order to expand a storage capacity) without
shutting down the subsystem is shown below.
NOTE : When adding the two or more Disk Drives in the installation of the Disk Drives
(Work-7), complete the restoration of the system information (Work-8) for the
each Disk Drive one by one, and then install the Disk Drives one by one.
Start
Work-2 Backing up user data. When the data stored in an LU, which the Disk Drive to
be replaced is defined as, is necessary, backup them.
Further, it is recommended to backup data of all LUs to
provide against an emergency because user data may
be lost if a wrong operation is done.
Work-3 Deleting LUs Delete all LUs defined as being belonging to the RAID
group that includes the Disk Drive to be replaced.
When using Storage Navigator Modular, refer to
System Parameter 3.3 Setting of LU
(SYSPR 03-0140).
Work-4 Deleting a RAID group Delete a RAID group that includes the Disk Drive to be
replaced.
System Parameter 3.2 RAID group setting (SYSPR
03-0050).
Work-5 Canceling a Spare Disk When the Disk Drive to be replaced is assigned to a
Spare Disk, cancel the assignment.
System Parameter 3.4 Setting of Spare Disk
(SYSPR 03-0350).
A To ADD 01-0300

ADD 01-0290-01
From ADD 01-0290

A
Work-7 Replacing the Disk Drive When replacing two or more Disk Drives, be sure to
(Replace the Disk Drive without delay.) replace them one by one.
Remove the Disk Drive to be replaced and install the
new one taking care not to apply any shock to it.
See (4-2) When replacing the Disk Drive (in order to
Work-8 Restoring the system information When you have replaced any of the Disk Drives #2 to
#4, be sure to restore the system information.
Refer to (5) Restoring the system information
(ADD 01-0360)
formatting of an LU, setting of a Spare Disk, and Setting
Setting of RAID/LU
Formatting of an LU Refer to System Parameter Chapter 3. Setting the
Setting of a Spare Disk RAID/LU/Spare Disk (SYSPR 03-0000).
Work-11 Refer to an instruction manual of each host computer.

Making a host computer recognize the LU
Example : For operation in the case of a host
computer in which HP-UX is installed,
refer to (6) Making a host computer
recognize an LU while the subsystem
power is on (ADD 01-0390).
END

ADD 01-0300-01
(3-2) Procedure for replacing the Disk Drive (in order to expand a storage capacity) while the
subsystem power is off
A procedure for replacing the Disk Drive (in order to expand a storage capacity) after
powering off the subsystem is shown below.
Start
Work-2 Backing up user data. When the data stored in an LU, which the Disk Drive to
be replaced is defined as, is necessary, backup them.
Further, it is recommended to backup data of all LUs to
provide against an emergency because user data may
be lost if a wrong operation is done.
Work-3 Deleting LUs Delete all LUs defined as being belonging to the RAID
group that includes the Disk Drive to be replaced.
System Parameter 3.3 Setting of LU
(SYSPR 03-0140).
Work-4 Deleting a RAID group Delete a RAID group that includes the Disk Drive to be
replaced.
System Parameter 3.2 RAID group setting (SYSPR
03-0050).
Work-5 Canceling a Spare Disk When the Disk Drive to be replaced is assigned to a
System Parameter 3.4 Setting of Spare Disk
(SYSPR 03-0350).
(INST 01-0310)
Make sure that the Cache memory is not being backed

Work-7 Checking a status of backing up
up. If the Disk Drive is added without canceling the
the Cache memory backup, user data may be lost.
Refer to System Parameter 1.1 Procedure for
subsystem (SYSPR 01-0010).
Work-8 Setting the power control mode to Local(*1) For the Setting the Power Control Mode (Local or
Remote), refer to the following page.
A To ADD 01-0320
*1 : When the subsystem power control works interlocking with the UPS, etc., make an adjustment so that the power is
supplied to it.

ADD 01-0310-01
From ADD 01-0310

A
Work-10 Replacing the Disk Drive When replacing two or more Disk Drives, be sure to
replace them one by one.
Remove the Disk Drive to be replaced and install the
new one taking care not to apply any shock to it.
See (4-2) When replacing the Disk Drive (in order to
Work-11 Attaching the Front Bezel Refer to Installation 1.5 How to Open/Close Door or

(INST 01-0290)
Setting of RAID/LU formatting of an LU, setting of a Spare Disk, and Setting
Formatting of an LU of an LU mapping, etc.
Refer to System Parameter Chapter 3. Setting the
Setting of a Spare Disk
RAID/LU/Spare Disk (SYSPR 03-0000).
(INST 01-0310)
Work-15 Returning the setting of the power control (Local or For the Setting the Power Control Mode (Local or
Remote) to the original one Remote), refer to the following page.

(INST 01-0290)
Work-17 Installing a host computer Refer to an instruction manual of each host computer.
END

ADD 01-0320-01
(4) Installing/removing Disk Drive

When installing/removing the Disk Drive in the addition or subtraction of it, follow the
procedure shown below.
Procedure for adding a Disk Drive (RKM/RKAJ /RKS):
See Item (4-1) When adding the Disk Drive (in order to expand a storage capacity)
(ADD 01-0330).
Procedure for replacing a (RKM/RKAJ /RKS):
See Item (4-2) When replacing the Disk Drive (in order to expand a storage capacity)
(ADD 01-0350).
(4-1) When adding the Disk Drive (in order to expand a storage capacity)
Perform the following operations (a) to (d) for each of the Disk Drives to be added (in order
to expand a storage capacity) one by one.
(a) Pull the stopper at the upper part of the disk drive handle toward you to have the lock off,
tilt the handle toward you, and then remove the dummy (disk drive) by pulling it.
Because the dummy (disk drive) that has been removed will be used when the added Disk
Drive is de-installed, keep it in custody with its handle returned to its original state (locked
by the stopper).
NOTE : Exteriors of the Disk Drive and dummy (Disk Drive) are similar to each other.
Be careful not to install or remove a wrong one.
Disk Drive : A label bearing the model name and revision number is affixed
to the portion near the handle.
Dummy (Disk Drive) : No label is affixed to the portion near the handle.
(b) Install the Disk Drive to be added taking care not to apply any shock to it
(see Figure 1.4.4.1).
arrow.
(c) When the Disk Drive has been added while the subsystem power is on, the ALARM LED on the
Disk Drive will go out a little while after the Disk Drive has been inserted.
Make sure that the LED goes out.

ADD 01-0330-01
Guide Rail
Address label
Safekeeping
of screw
Disk Drive
Stopper
Handle
Hook
Safekeeping of
component Rectangular Hole
Figure 1.4.4.1 Operation of Mount the Disk Drive

ADD 01-0340-01
(4-2) When replacing the Disk Drive (in order to expand a storage capacity)
Perform the following operations (a) and (d) for each of the slots, where the Disk Drive is to
be replaced, one by one.
tilt the handle toward you, and then remove the Disk Drive by pulling it out taking care not
to apply a shock to it. (see Figure 1.4.4.2).
When using the removed Disk Drive for the purpose of addition to another disk array unit,
keep it in custody with its handle returned to its original state (locked by the stopper) taking
care not to apply a shock to it.
(b) Install the Disk Drive to be added taking care not to apply any shock to it
(see Figure 1.4.4.2).
arrow.
(c) When the Disk Drive has been added while the subsystem power is on, the ALARM LED on the
Disk Drive will go out a little while after the Disk Drive has been inserted.
Make sure that the LED goes out.
Remove
Address label
Safekeeping of screw Stopper

Handle
Guide Rail
Mount
Disk Drive
Safekeeping of component
Stopper
Handle Hook
Rectangular Hole
Figure 1.4.4.2 Operation of Mount/Remove the Disk Drive

ADD 01-0350-01
(5) Restoring the system information

A restoration of the system information can be done by using either of the Storage Navigator
Modular.
(5-1) Restoring the system information using Storage Navigator Modular

(a) Start Storage Navigator Modular, position the focus ([ ]) on the [Disk Array Subsystem
Registration] ([ ]) on the tool bar by pressing the [Tab] key, and then press the [Ctrl],
[Shift], and [E] keys at the same time.
Maintenance Mode is displayed in the Operation Mode field at the top right on the Main
screen, and the Storage Navigator Modular operates in the maintenance mode.
(b) Click an icon of the disk array subsystem you want to set in the main window.

ADD 01-0360-01
(c) Select [Tools] [Maintenance] in the unit window.
(d) Click the [Drive Maintenance] tab.
(e) Select the [System Copy] and set the number of the Disk Drive that has been added.
(f) Click the [Apply] button.

ADD 01-0370-01
(g) The confirmation window is display. Click the [OK] button.
(h) A window showing that the setting has been completed is displayed.
Press the [OK] button.
(i) When System copy started (Unit-x, HDU-y) and System copy completed (Unit-x,
HDU-y) are displayed at the Information Message in the WEB window, the system copy has
been completed.

ADD 01-0380-01
(6) Making a host computer recognize an LU while the subsystem power is on
< An example of the case of a host in which HP-UX is installed >

An example of the procedure to make the Disk Drive added while the subsystem power is on
recognized by the host computer in which the HP-UX is installed is shown below.
(a) System configuration
LAN connect the PC, in which the Storage Navigator Modular is installed.
PC
LAN (Disk Array
HUB Utility)
Fibre Port#0A Port#1A

Host computer Channel
(HP-UX) HUB LAN on Control Unit#0
LAN on Control Unit#1

Added Disk Drive
DF700 Disk Drive
:
Disk Drive

ADD 01-0390-01
(b) Operation procedure

( i ) Make sure that the host computer and the DF700 are in the Ready status. (I/Os host
computer can be continued)
(ii) Install the Disk Drives to be added in the DF700.
(iii) Set a new RAID group for the installed Disk Drives.
(iv) Set (an) LU(s) newly for the RAID group which has been set in step (iii).
(v) Format the LU(s) which has been set in step (iv).
(vi) Issue the ioscan -nfC disk command from the host computer to verify that the DF700 has
been recognized by the host computer. (However, the status of the newly added LU is
displayed as NO-NW.)
(vii) Execute the insf -e command from the host to create a device file of the LU which has
been newly added.
(viii) Issue the ioscan -nfC disk command from the host computer to verify that the DF700 has
been recognized by the host computer. (The status of the newly added LU is displayed as
CLAIMED.)
(ix) Execute a creation of a file system by creating the volume group and logical volume for
the newly added LU from the host computer.
By operating as explained above, the LU(s) which has been newly created becomes able to be
used by the host computer.

ADD 01-0400-01
1.4.4 Adding a Cache Unit

This work is for the RKM only.
CAUTION
care.
CAUTION
damage the parts.
y When you install is Control Unit, support its metal part with your hand that has
NOTE : Before unpacking and replacing maintenance components, be sure to wear a wrist
strap and connect to ground the grounding clip in the opposite end of the wrist
strap to the chassis frame (metal part).
Control Unit
Connect this to the metal part on the
frame of subsystem (rear face)
Support a Control Unit by touching A wrist strap (Be sure to wear this before
its metal part (metal plate) with your starting maintenance.)
fingers
NOTE : y When the subsystem operates in the dual controller configuration, do the
works for the both Control Units. In the case of the single controller
configuration, do the work for the Control Unit #0 only.
y After the work is completed, be sure to return the Control Units #0 and #1 to
their original locations. In the case of the single controller configuration,
return the Control Unit to a location of the Control Unit #0.

ADD 01-0410-01
<Working Procedure>
Make sure that the POWER LED (Green) on the Front Bezel go off. If you cannot turn off the
power, troubleshoot the failure by connecting to the Web.
NOTE : If the power has already been turned off, check that Cache memory is not in
the back-up state. (To check for the back-up state, refer to Replacement
1.1.2 Checking cache memory in the back-up state (REP 01-0030).)
When the Cache is in the backup status, cancel the status.
In this case, check that the CACHE POWER LED (Green) on Control Unit is extinguished.
NOTE : If the CACHE POWER LED (Green) is lit, it may be that some of the Cache Unit
data has not been written into the disk. In this case, removing the Control Unit
may cause a loss of user data.
(2) Turn off the AC Power Unit Switch of the both Power Units.
NOTE : It is possible that the recovery is not made normally if the replacement is done
without turning off the AC Power Unit Switch.
(3) Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down
(4) Remove the all cables connected to the Control Unit.
NOTE : When the cable cannot be removed easily, do not pull it by force.
Besides, the cable can be damaged if it is bent upward or downward forcibly.
CAUTION
care.
(5) Remove the Control Unit by pulling it out toward you.

(7) Remove the Cache Unit.
Place the removed Cache Unit in the place where anti-static measures are taken.
(8) Install the Cache Unit in the Control Unit.
NOTE : y For the dual Control Unit, install the Cache Unit of the same capacity in the
y Remove the dust cover when installing the Cache memory.

ADD 01-0420-01
(10) Insert it into the position in the Control Unit #0 with the both right and left levers of the
If the Control Unit is caught by something when it is inserted, do not push it in forcibly. Retry
the insertion from the beginning. If forced, pins might be broken.
NOTE: y Do not catch a ENC cable, when the Control Unit for the inserted.
y The installation direction is different in the Control Unit # 0 and # 1. Install
(11) Connect the removed all cables to the Control Unit.

Note: The installed direction is different in the Control Unit #0 and #1, so that be
(12) Turn on the AC Power Unit Switch of the both Power Units.
(14) Make sure that the WARNING LED (orange) on the Front Bezel is off(1).
(15) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on the
Front Bezel may blink at high speed (up to 30/50 minutes).
1 : When the WARNING LED is blinking, refer to the WEB or collect the trace, and then check if the LED goes out.

ADD 01-0430-01
Control Unit #0
Cover
Control Unit #1
Fixing screw
Lever
Removal :
Slot lever Press open the slot lever to
Fixing screw
memory by holding the both end
Socket by hand.
Cut Installation :
cutout inside the slot both end by hand.
slot #1 slot #0
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT

CALM LED (red)
Figure 1.4.5 Replacing Cache Unit (RKM)

ADD 01-0440-01
1.5 Adding Other Optional Devices

1.5.1 Other optional additional devices

Component
name
operation(*1).)
PDB (UPDU7) DF-F700-UPDU7 For U7 Additional PDB for U7 rack Possible Possible
frame 1.5.2 Mounting a 1.5.2 Mounting a
PDB (UPDU7) PDB (UPDU7)
(ADD 01-0460) (ADD 01-0460)

ADD 01-0450-01
1.5.2 Mounting a PDB (UPDU7)

(1) Height of Required Space in Rack Frame
The height of the space required for mounting the PDB on the rack frame is one unit of the EIA
standard.
(2) Optional Parts for Mounting (Model Name : DF-F700-UPDU7)
NOTE : The current capacity for a PDB is limited to up to 20 amperes. When mounting
the multiple RKMs/RKSs and RKAJs/RKAJATs, connect them avoiding applying the
current of more than 20 amperes to a PDB.
Up to four subsystems in total combining 0 to 1 RKMs and 0 to 4 RKAJs/RKAJATs
can be connected to a single PDB.
Up to four RKMs/RKSs can be connected to a single PDB.
The optional parts and their quantities required to mount the one PDB are shown below.
Table 1.5.1 Composition of DF-F700-UPDU7 (per set)

1 PDB 2 Adding rack frame in PDB
2 Power cable 3259166-A 2 L6-30P 4.5 m
3 Support metal bracket 32663121-1 4 U7 rack frame For U7 rack
4 RAC NUT (Fastener) 5510146-1 10 U7 rack frame rack frame
(2 spare is included)
5 LL Washer 2051001-513 10 U7 rack frame (2 spare is included) For U7 rack
6 Socket bolt (M5 20) BS520 10 U7 rack frame (2 spare is included) For U7 rack
7 Bind screw (M5 10) SB510 10 For securing the PDB
(2 spare is included)
8 Name plate 3243319-232 2 Already affixed to PDB
9 Cable holder 3230194-1 2 Adding PDB
10 Socket bolt (M4 30) BS430 6 For securing the cable holder
11 Plate holder 5519109-1 1 Adding PDB
12 Socket bolt (M4 8) BS408 4 For securing the plate holder
(3) Tool Required

Phillips screwdriver (No.1, No.2)
Allen wrench (No.4)
Allen wrench (No.5)

ADD 01-0460-01
(4) Installing UPDU7 in U7 Rack Frame

Install the PDB making it face the rear of the rack frame.
NOTE : When adding PDB, mount PDB in two-part set due to the duplicated power
supply.
(a) Attach the fasteners (four places) to the positions in the rear of the U7 rack frame where the
rack accommodating the UPDU7 components is to be mounted.
(b) Attach the support metal brackets to the positions where the Fasteners are attached in Step
(a), and fix the brackets with socket bolts of M520 size (two places per bracket).
(c) PDB components onto the rack frame, engaging the front holes of the rack with those of the
support metal brackets attached in Step (b). Then, fix the rack with binding screws of
M510 size (four places).
(d) Add another two-part set of PDB in the same way.
(e) Route and connect cables, observing the rules provided in Installation 1.1 (2) Note on cable
routing (INST 01-0010).
Attach two fasteners to the holes forming a wider clearance on the

right side and two others on the left.
Support metal brackets are also attached to the same positions as
the fasteners.
Rear left of a U7
rack frame Fastener Fastener
LL Washer LL Washer
Support metal bracket Support metal bracket
Socket bolt (M5x20)
PDB
Bind screw (M510)

Bind screw (M510)
Figure 1.5.1 Installing the PDB (UPDU7)

ADD 01-0470-01
(5) Installing the power Cable (Added PDB append parts) and cable holder.
CAUTION
NOTE : Make sure that conductors shall be provided with 30 A over current protection
in accordance with Article 240 of the National Electrical Code, ANSI/NFPA 70,
and the Canadian Electrical Code, Part 1, CSA C22.1, Section 14.
(a) Open the rear door. (See Installation 1.5.4 How to open/close the Rear Door of U7 rack
(b) Make sure that the power supply switches of the PDBs are turned off.
(c) Remove the cable holder (adding PDB).
(d) Put out the power cables of PDBs through the Cable passing opening at the bottom of the Rack.
(e) Fasten the power cables to the rack frame by attaching the cable holders (adding PDB) with the
hexagon socket head bolt M430.
(f) Make sure that the connecter is securely fixed after the assembly work.
Adding PDB
Adding PDB
Rear Door
PDB #01
PDB #11
Power supplying switch
Power cable
Power cable
PDB #10
PDB #00
Power cable
PDB #00/01 side
Power cable Hexagon socket head bolt (M430)
Power cable
Cable clamp
Power cable
Cable clamp PDB #10/11 side
(Adding PDB)
Figure 1.5.2 Installing the PDB (UPDU7)

ADD 01-0480-01
1.6 Adding the RKAJ to the Rack Frame

(In the case of the connection to the RKM)
In the case of adding Disk Drives to a subsystem of the rackmo unt model, the RKAJ must be
added when vacant slots for the Disk Drives to be added are insufficient in the existing
subsystem.
A procedure for adding the RKAJ on the U7 rack frame while the subsystem power is on or
power is off(1) is shown below.
When mounting the RKAJ on the rack frame, installation of as many rack rail kits (DF-F700-
URHT7) as the RKAJs to be added are required.
1.6.1 Procedure for adding the RKAJ to the subsystem of rackmount model with U7 rack frame
(1) Prerequisites
Before starting the addition, make sure that the following requirements are satisfied. If not, an
abnormal termination of the addition or a system down may be caused.
(a) At least the following components must have been installed in the RKAJ to be added.
y Two Disk Drives (a combination of the Disk Drives #0 and #1)
y Two ENC Unit (Standard installation, Four ENC cables are included.)
y Two Power Unit ((RKAJ)s (Standard installation)
(b) Two ENC cables per ENC Unit must have been connected between the RKAJ and the RKM or RKAJ.
(c) Restriction of number of the RKAJs allowed to be added is that the total number of the RKM
and RKAJs must not exceed the allowable maximum of fifteen after the addition.
An RKM can be connected to 14 RKAJs at the maximum.
An RKS can be connected to 6 RKAJs at the maximum.
(d) The addition must be done only when any WARNING (WARN) LED (orange) on the subsystem is
off. If any WARNING (WARN) LED (orange) on the subsystem is on, take an action to make
the LED go out. (Refer to Troubleshooting (TRBL 00-0000).)
(e) No part replacement can be done while operation to make the RKAJ recognized is being
done.
(f) A number of installed Disk Drives when making an addition.
The installed Disk Drives when making an addition must be the #0 to #3 only.
When less than four Disk Drives are to be added, the Disk Drives #0 and #1 must have been
installed.
y When the number of the Disk Drives to be added is two, install two of them in the Disk Drive
#0 and #1.
y When the number of the Disk Drives to be added is three, install three of them in the Disk
Drive #0 to #2.
y When the number of the Disk Drives to be added is four, install four of them in the Disk
Drive #0 to #3.
(g) Install them after all the RKAJs have been recognized(1) (Work-10), connect the ENC cables
between the existing subsystem and the added RKAJ adjacent to the subsystem for the each
loop one by one. (See 1.6.3 Recognition and connection of the added RKAJ (ADD 01-
0590).)

ADD 01-0490-01
1 : The expression with the subsystem power on described here means a state in which the power of the disk array
subsystem is turned on. (System operation with a host is no concern of it.).

ADD 01-0490-01
(h) When failures occur in both of the existing subsystem and the added RKAJ while the
operation to make the RKAJ recognized(1) (Work-10 to Work-11) is being done, take a
recovery action against the failure of the existing subsystem preferentially after the RKAJ has
been recognized(1).
After that, take a recovery action against the failure of the added RKAJ, and then resume the
operation.
(i) Do not perform an LU formatting while the operation to make the RKAJ recognized(1) is being
done (Work-10 to Work-11). Also, do not perform the operation to make the RKAJ
recognized(1) while an LU formatting is in progress.
(j) Do not make the addition work when the READY LED (green) on the Front Bezel is blinking at
(2) Notes when the addition terminated abnormally

The subsystem may go down if the following work is not done when the addition of RKAJ
terminated abnormally.
(a) When the addition of RKAJ terminated abnormally, remove each of the instructed ENC cables
at 20-second or more intervals according to the procedure.
(b) When the addition of RKAJ terminated abnormally, remove all of the instructed ENC cables
according to the procedure, and turn off the AC input power switch of the Power Unit of all
the added subsystems that terminated abnormally.
1 : The expression recognized described here means that the Controller of the existing RKM recognizes the added
RKAJ.

ADD 01-0500-01
(1) Procedures for installation the RKAJ on Rack Frame while the subsystem power is on (Available
only in the dual controller configuration.)
When adding the RKAJ on the rack frame while the subsystem power is on, make sure of the
following work items before starting the addition.
Work-1 Installing rail See Installation 3.2.1 (11) Installing the rails
(INST 03-0100)
Work-2 Unpacking the RKAJ See Installation 3.3 Unpacking the Subsystems
(INST 03-0310)
Work-3 Work before Installing the Rack Mounting See Installation 3.4.1 Work Procedure before
Installing the Rack Mounting (INST 03-0330)
Work-4 Mounting on rack frame See Installation 3.4.3 Mounting on Rack Frame
(INST 03-0400)
Work-5 Securing the RKAJ See Installation 3.4.6 Securing the subsystem
(INST 03-0450)
Work-6 Installing components See Installation 3.4.7 Installing Components

(INST 03-0490)
(1) Installing Disk Drive
(4 and 3 subsystems or 2 is RKAJ)
(2) Other components
See Installation 3.4.8 Connecting Cables

Work-7 Connecting power cable(1)
(INST 03-0610)
No
Do you add the two or more RKAJs?
Yes
Work-8 Connecting multiple RKAJs)
(Connecting multiple RKAJs that are not adjacent to the See 1.6.2 Connecting multiple RKAJs
existing subsystem) (ADD 01-0550)
(1) The replacement of ENC Unit
(The replacement is required when the revision of the
ENC Unit, to which the ENC cable (5 m) is to be
connected, is "B".)
(2) Connecting the ENC cables
(3) Turn on the AC Power Unit Switch
A To ADD 01-0520
1 : When using the UPS for the exclusive use, install and connect the UPS referring to the UPS manual.

ADD 01-0510-01
A From ADD 01-0510
Recognition and connection of the added

Work-9
RKAJ (Recognizing and connecting the added RKAJ
adjacent to the existing subsystem) See 1.6.3 Recognition and connection of the
added RKAJ (ADD 01-0590)
connected, is "B".)
(2) Connecting the ENC cables (Loop #0)
(3) Turn on the AC Power Unit Switch
Verifying the addition of the RKAJ(s) See 1.6.4 Verifying the addition (ADD 01-0670)
Work-10
(Verifying the addition of the RKAJ adjacent to the
existing subsystem)
(1) Verifying completion of the addition to the loop
consequent on the RKAJ addition performed with the
subsystem power on
See 1.6.5 Install the rest of the Disk Drives

Work-11 Install the rest of the Disk Drives (ADD 01-0740)
Work-12 Attaching decoration panels See Installation 3.4.13 Attaching Decoration

Panels (INST 03-0740)
Work-13 Setting the Subsystem Configuration Information


ADD 01-0520-01
(2) Procedures for installation the RKAJ on Rack Frame while the Subsystem Power Is Off
When adding the RKAJ on the rack frame while the subsystem power is off, make sure of the
following work items before starting the addition.
(INST 01-0310)
Make sure that the Cache memory is not being

Work-2 Checking a status of backing up backed up. If the Disk Drive is added without
the Cache memory canceling the backup, user data may be lost.
Refer to System Replacement 1.1.2 Checking
cache memory in the back-up state (REP 01-
0030).
Work-3 Set the mode to Local Setting the Power Control Mode (Local Mode)
See Installation 1.8 Setting the Power Control
Work-4 Installing rail See Installation 3.2 Unpacking and Installing

Work-5 Unpacking the RKAJ See Installation 3.3 Unpacking the Subsystems
(INST 03-0310)
See Installation 3.4.3 Mounting on Rack Frame

Work-7 Mounting on rack frame
(INST 03-0400)
Work-8 Securing the RKAJ See Installation 3.4.6 Securing the subsystem
(INST 03-0450)

(INST 03-0490)

Work-10 Connecting cables(1)
(INST 03-0610)
Work-11 Attaching Decoration Panels See Installation 3.4.13 Attaching Decoration

A
To ADD 01-0540

ADD 01-0530-01
A From ADD 01-0530

(INST 01-0290)
Work-14 Setting the Subsystem Configuration Information See System Parameter Chapter 3. Setting the
(INST 01-0310)
Work-16 Reset the Local or Remote mode to the original one. Setting the Power Control Mode (Local Mode)

ADD 01-0540-01
1.6.2 Connecting multiple RKAJs

When connecting the multiple RKAJs at a time, perform the following.
According to the cable figure to be output from ACE Tool, connect the ENC cable.
For the operation method of ACE Tool, refer to Installation 1.6 Device ID Setting and ENC
Cable Connection (INST 01-0160).
When adding only a single RKAJ, proceed to 1.6.3 Recognition and connection of the added
RKAJ (ADD 01-0590).
(1) Connecting ENC cables (Connecting RKAJ which is not adjacent to the existing unit)
When adding the RKAJ, the ENC Unit has to be connected using the ENC cable(1).
Connect all the ENC cables except those between the existing subsystem and the RKAJ which is
to be connected to the existing subsystem. (Following the instruction given in the procedure
1.6.3 (3) Turn on the AC Power Unit Switch of the Power Units (#0, #1) of the added RKAJ
adjacent to the existing subsystem. (ADD 01-0660).)
excessive stresses.
y The ENC cables are connected to the two paths (PATH#0 and PATH#1) of the
ENC Unit #0 side (Loop #0), and the two paths (PATH#0 and PATH #1) of the
ENC Unit #1 side (Loop #1) (total of four).
The ENC Unit connector and the ENC cable connected to it have the same
color indication. Be careful to keep the color of the PATH #0 in milky white
and the PATH #1 in yellow.
<Working Procedure>
(a) Remove the rubber cap on the ENC Units of each added RKAJ.
The rubber cap on the ENC Units finally connected are not required to be removed.
(b) Connect the ENC Units of the added RKAJs that are not adjacent to the existing subsystem
(see Figure 1.6.1 Connecting the ENC cables (ADD 01-0560)).
NOTE : Keep the same color indication when connecting the ENC cables as shown
below.
Connect the both ENC Unit #0 (Loop #0) and #1 (Loop #1).
( i ) Connect the ENC cable marked in milky white to the PATH #0 (in milky white) in the IN
side of the ENC Unit #0 in the RKAJ adjacent to the PATH #0 (in milky white) in the OUT
side of the ENC Unit #0.
(ii) Connect the ENC cable marked in yellow to the PATH #1 (in yellow) in the IN side of the
ENC Unit #0 in the RKAJ adjacent to the PATH #1 (in yellow) in the OUT side of the ENC
Unit #0.
(iii) For the ENC Unit #1, perform the same work as the above.

ADD 01-0550-01
1 : Keep unused cables carefully to prepare for an occasion to use them.

ADD 01-0550-01
Rack frame
RKAJ
ENC cable
RKAJ
Connect the added RKAJs that are not

RKAJ adjacent to the existing subsystem with the
ENC cables.
RKAJ
RKAJ
Do not connect the added RKAJ adjacent to the

RKAJ existing subsystem with the ENC cables now.
They are to be connected in the step explained in
1.6.3 (3) Turn on the AC Power Unit Switch of the
Power Units (#0, #1) of the added RKAJ adjacent to
the existing subsystem. (ADD 01-0660).
Existing subsystem
Loop #0 side Loop #1 side

Figure 1.6.1 Connecting the ENC cables

ADD 01-0560-01

ENC cable (yellow)
Rubber cap Rubber cap

IN side ENC Unit #0 IN side ENC Unit #1
OUT side OUT side
Loop #0 Loop #1
RKAJ
Indication
position of color
(yellow)
Indication Rubber cap

position of color
(milk white)
OUT side OUT side

ADD 01-0570-01
(3) Turn on breakers of the upper PDBs (#01 and #11).

(4) Turn on AC Power Unit Switch of all the Power Units of the added RKAJs that are not adjacent
to the existing subsystem.
The ALM LED on the ENC Unit of the added RKAJ concerned comes on.
Do not turn on AC Power Unit Switch of the added RKAJ adjacent to the existing subsystem.
Circuit breaker
Added RKAJ adjacent to the existing (CB1)
subsystem the existing subsystem Added RKAJ not adjacent to PDB#01 Power Unit PDB#11
the existing subsystem
(RKAJ)
AC Power Unit
Switch
Existing subsystem
Main switch PDB
Figure 1.6.3 Locations of Switches for Power On

ADD 01-0580-01
1.6.3 Recognition and connection of the added RKAJ

To make the added RKAJ recognized, satisfy the following requirements.
No. Item to be checked Matter to be checked Check result

1 Disk Drive The Disk Drives #0 to #3 must be installed in the RKAJ to be added. When
less than four Disk Drives are to be added, the Disk Drives #0 and #1 must be
installed in the RKAJ.
2 The Disk Drives #4 to #14 must not be installed in the RKAJ to be added
3 ENC Unit The two units must be installed in the RKAJ to be added.
4 Power Unit (RKAJ) The two units must be installed in the RKAJ to be added.
5 WARNING (WARN) LED of the No WARNING (WARN) LED must be on.
subsystem
6 Device ID The device ID must be set correctly.
(Refer to Installation 3.4.7 (1-2) Setting Device ID number (INST 03-0520).)
7 Subsystem identification switch The subsystem identification switch must be set correctly.
(Refer to Installation 3.4.7 (1-3) Setting the subsystem identification switch
(INST 03-0520).)
8 Number of connectable The addition must not make the total number of the RKM and RKAJs exceed
the allowable maximum of fifteen.
9 Formatting No LU formatting must be in progress.
10 Other maintenance works No other maintenance work must be in progress.
When the requirements above are satisfied, perform the operation following the procedure
for making the RKAJ recognized shown below.
When making the multiple RKAJs recognized at a time, satisfy the following requirements in
addition.

1 Making the multiple RKAJs Are the ENC cables connected correctly to the added RKAJs other than the
recognized at a time RKAJ connected with the existing subsystem?
2 Are the Power Units of the added RKAJs other than the RKAJ connected with
the existing subsystem turned on?

ADD 01-0590-01
(1) Procedure for making the added RKAJ recognized

Perform the RKAJ recognition operation following the flowchart below.
If a failure occurs during the work, check a Web message and take an action for recovery from
the failure referring to (4) Troubleshooting (ADD 01-0710).
Start of the recognition procedure

From ADD 06-0610
B
Connect the cables on the Loop #0 side of

the added RKAJ adjacent to the existing
subsystem.
(See Item (2) Connecting ENC cables (on Connect the ENC cables on the Loop #0
the Loop #0 side) (ADD 01-0630).) side removed in 1.3.1 Work immediately
after abnormal termination (ADD 01-0110).
Turn on the AC power input switch of the
Power Unit #0 and #1 in an added RKAJ
Turn on the power supply of the added
adjacent to a subsystem already installed.
subsystem which turned off the power
(See Item (3) Turn on the AC Power Unit
supply in 1.3.1 Work immediately after
Switch of the Power Units (#0, #1) of the
abnormal termination (ADD 01-0110).
added RKAJ adjacent to the existing
(The ALM LED on the ENC Unit comes on.)
subsystem. (ADD 01-0660))
(The ALM LED on the ENC Unit comes on.)
Did the ALM LED of the ENC Unit on the

Loop #0 side go out? Yes
A To ADD 01-0610
1.6.4 Verifying the addition
(ADD 01-0670)
No
Have five minutes elapsed after the RKAJ Yes
was powered on?
Connect the service PC to the Web.
No
(Refer to Troubleshooting 3.1 Procedure to
WEB connection (TRBL 03-0000))
The case where the addition is Is a message that the RKAJ addition (performed with
not recognized. No the subsystem power on) has been started displayed
in the Web message window? (Refer to 1.6.4 (1) (b)
Contents of the WEB message (ADD 01-0680))
Yes
Perform Work immediately after abnormal Perform Work immediately after abnormal
termination (refer 1.3.1 Work immediately termination (refer to 1.3.1 Work immediately
after abnormal termination (ADD 01-0110)). after abnormal termination (ADD 01-0110)).
Replace the ENC cable or the ENC Unit on

the Loop #0 side of the existing subsystem Perform maintenance following the Web
that was finally mounted message
(refer to Replacement 2.2.9 Replacing ENC
Unit/SENC Unit (REP 02-0830)).

ADD 01-0600-01
A From ADD 01-0600

Troubleshooting 3.1 Procedure to WEB
connection (TRBL 03-0000)
Make sure that there is a message displayed in

the Web message window (Refer to 1.6.4 (1) (b)
indicating that the RKAJ addition (performed with
the subsystem power on) to Loop #0 has been
completed.
Connect the cables on the Loop #1 side of

the added RKAJ adjacent to the existing
subsystem. (See (2) Connecting ENC cables
(on the Loop #1 side) (ADD 01-0690))
Did the ALM LED of the ENC Unit on

the Loop #1 side go out? Yes
(ADD 01-0670)
No
Have five minutes elapsed after the
Yes
ENC cables of the Loop #1 were
connected?
No
Is a message that the RKAJ addition
The case where the addition is
(performed with the subsystem power on) has been
No not recognized.
started displayed in the Web message window?
(Refer to 1.6.4 (1) (b) Contents of the WEB
message (ADD 01-0680))
Yes
termination (refer to 1.3.1 Work immediately termination (refer to 1.3.1 Work immediately
Replace the ENC cable or the ENC unit

Perform maintenance following
on the Loop #1 side of the existing
he Web message
subsystem that was finally mounted.
B B
To ADD 01-0600 To ADD 01-0600
C To ADD 01-0620

ADD 01-0610-01
C From ADD 01-0610
Make sure of a message that the RKAJ addition

(performed with the subsystem power on) to the
Loop #1 has been completed displayed in the
Web message window. (Refer to 1.6.4 (1) (b)
When the two or more RKAJs have been

added: Is a message concerning the RKAJ
to be added that the RKAJ addition No
(performed with the subsystem power on)
has been started displayed in the Web
message window?
Yes
Make sure that READY LED (green) on the
Front Bezel lights on (when it is blinking at high
speed, wait until it lights on after the maximum
of 30/50 minutes.)
Yes
Is a Disk Drive installed?
No
Mount one of the Disk Drives#4 to #14 to be

added.(1).
Did the ALARM LED of the Disk Drive

No Replace the Disk Drive concerned
come on and then go out about five
minute later? and make a retry.
Yes
Is there another Disk Drive to be Yes
added?
No
The addition has completed
1 : Refer to 1.4.3 (4-1) When adding the Disk Drive (in order to expand a storage capacity) (ADD 01-0330).

ADD 01-0620-01
(2) Connecting ENC cables (on the Loop #0 side)

When adding the RKAJ while the subsystem power is on, it is required to connect the ENC Unit
for the Loop #0 (ENC #0) of the RKAJ to be added and the ENC Unit with the ENC cables (1).
Do not connect the ENC cables of the both loops Loop #0 and Loop #1 at a time.
Otherwise, the subsystem may go down.
Connect the ENC cables of the Loop #1 after verifying the completion of the addition to the
Loop #0.
NOTE : y Be sure to connect the ENC cable from the subsystem to be added.
If it is connected from the existing subsystem, the loop failures occur.
y For the single Control Unit configuration, connect the Loop #0 (ENC Unit #0)
side only, and do not connect the Loop #1 (ENC Unit #1) side.
When the multiple RKAJs are mounted, however, connect the both ENC Unit
#0 and #1 among the RKAJs by the ENC cables.
excessive stresses.
y The ENC cables are connected to the two paths (PATH#0 and PATH#1) of the
ENC Unit #0 side (Loop #0), and the two paths (PATH#0 and PATH #1) of the
ENC Unit #1 side (Loop #1) (total of four).
<Working Procedure>
(a) Remove the rubber cap on the FC-AL (RKM/RKAJ) connectors of the existing RKM/RKAJ that
was finally mounted.
(b) Connect the ENC Unit on the Loop #0 side in the added RKAJ adjacent to the disk array unit
already installed to the output connector of the FC-AL on the Loop #0 side in the disk array unit
already installed (RKM/RKAJ) with the ENC cables
(see the Loop #0 in Figure 1.6.5 Connecting ENC Cables (ADD 01-0650)).
NOTE : Keep the same color indication when connecting the ENC cables as shown
below.
( i ) Connect the ENC cable marked in milky white to the PATH #0 (in milky white) in the IN
side of the ENC Unit #0 in the RKAJ adjacent to the PATH #0 (in milky white) in the OUT
side of the ENC Unit #0.
(ii) Connect the ENC cable marked in yellow to the PATH #1 (in yellow) in the IN side of the
ENC Unit #0 in the RKAJ adjacent to the PATH #1 (in yellow) in the OUT side of the ENC
Unit #0.
(c) Connect the ENC cables of the Loop #1 after verifying the completion of the addition to the
Loop #0.

ADD 01-0630-01

ADD 01-0630-01
Rack frame
RKAJ
RKAJ
ENC cable
RKAJ Connect the added RKAJs that are not

adjacent to the existing subsystem with the
ENC cables.
RKAJ
RKAJ Do not connect the added RKAJ adjacent to the

existing subsystem with the ENC cables now.
They are to be connected in the step explained in
1.6.2 (1) Connecting ENC cables (Connecting
RKAJ which is not adjacent to the existing unit)
(ADD 01-0550).
Existing subsystem

(Control Unit#0) (Control Unit#1)
Figure 1.6.4 Connecting the ENC cables

ADD 01-0640-01

Added subsystem adjacent to
the existing subsystem ENC cable (yellow)
Rubber cap Rubber cap
OUT side OUT side
Loop #0 Loop #1
Connect the ENC Unit of the Loop #1 with the ENC cables after making sure
that the addition to the Loop #0 has been completed. Do not connect the
ENC Units of the Loop #0 and Loop #1 with the ENC cables at a time.
Added subsystem
Existing subsystem
Indication
position of color
(yellow)
Rubber cap
Indication
position of color
(milk white)
In the case of the PATH #1 (yellow) PATH #0 (milk white)
last subsystem is
the basic
subsystem LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT
PATH #0 (milk white) PATH #1 (yellow)

In the case of the last
subsystem is RKAJ
OUT side OUT side

ADD 01-0650-01
(3) Turn on the AC Power Unit Switch of the Power Units (#0, #1) of the added RKAJ adjacent to
the existing subsystem.
Circuit breaker
(CB1)
Added RKAJ adjacent to the existing subsystem PDB#01 Power Unit PDB#11
(RKAJ)
AC Power Unit
Switch
Existing subsystem
Main switch PDB

ADD 01-0660-01

(a) Procedure for verifying completion of the addition to the loop
When the ALM LED on the ENC Unit to which the ENC cables have been connected and the
WARNING (WARN) LED of the RKAJ are off, the addition to the loop has been completed
normally.
Incidentally, the completion of the addition to the loop or a message output when a trouble
occurs can be checked in the Information Message window that is one of the WEB windows.
RKAJ Rear
Connector for ENC cable
P1 CHECK
ENC Unit#0 ENC Unit#1
P0 ALM
Figure 1.6.7 Locations of LED for ENC Unit

ADD 01-0670-01
(b) Contents of the WEB message

[In the case of normal termination]
MM/DD/YYYY HH:MM:SS Cx I80300 Unit ADD complete (Loop-y)

MM/DD/YYYY HH:MM:SS Cx I80100 Unit ADD start (Loop-y)
MM/DD/YYYY HH:MM:SS Cx I80004 Unit ADD start (Unit-x)
Date Time Detect Controller# x : Unit ID#, y : Loop#

A message informing of a start of the RKAJ addition performed with the system power on
A message informing of a start of the addition to the loop consequent on the RKAJ addition performed with the
subsystem power on
A message informing of completion of the addition to the loop consequent on the RKAJ addition performed with
the subsystem power on
[In the case of abnormal termination]

Take a recovery action according to the message notifying of the abnormal
termination.
MM/DD/YYYY HH:MM:SS Cx I8040x Unit ADD FAIL (Unit-x)

MM/DD/YYYY HH:MM:SS Cx I8050y Unit ADD FAIL (Loop-y)
MM/DD/YYYY HH:MM:SS Cx I80D0y Unit ADD FAIL [cable off] (Loop-y) :MANUAL/TRC
MM/DD/YYYY HH:MM:SS Cx I8010y Unit ADD start (Loop-y)
MM/DD/YYYY HH:MM:SS Cx I8000x Unit ADD start (Unit-x)

A message informing of a start of the addition to the loop consequent on the RKAJ addition performed with the
subsystem power on
A message informing of a factor of an abnormal termination (See Message Chapter 1. Before Starting
Trouble Analysis (MSG 01-0000) in the Maintenance Manual (for Maintenance).
A message informing of an abnormal termination of the addition to the loop consequent on the RKAJ addition
performed with the subsystem power on
Copyright 2005, Hitachi, Ltd. A message informing of an abnormal termination of the RKAJ addition performed with the subsystem power on
ADD 01-0680-01

ADD 01-0680-01

Connect the ENC cables on the Loop #1 side in the same way as the Loop #0.
Refer to 1.6.3 (2) Connecting ENC cables (on the Loop #0 side) (ADD 01-0630) (In the case of
the connection to the RKM).
(3) Verifying completion of the addition to the loop consequent on the RKAJ addition performed
with the subsystem power on
(a) Procedure for verifying completion of the addition to the loop consequent on the RKAJ
addition performed with the subsystem power on.
When the ALM LED of the ENC Unit to which the ENC cables have been connected and the
WARNING (WARN) LED of the RKAJ are off, you can verify completion of the addition to the
loop by viewing the Information message window in the WEB window.
MM/DD/YYYY HH:MM:SS Cx I8020x Unit ADD complete (Unit-x)

MM/DD/YYYY HH:MM:SS Cx I8030y Unit ADD complete (Loop-y)

A message informing of a start of the addition to the loop consequent on the RKAJ addition performed with
A message informing of completion of the addition to the loop consequent on the RKAJ addition performed
A message informing of an l termination of the RKAJ addition performed with the subsystem power on

ADD 01-0690-01

termination.

MM/DD/YYYY HH:MM:SS Cx I8010y Unit ADD FAIL [cable off] (Loop-y)

Trouble Analysis (MSG 01-0000).
A message informing of an abnormal termination of the addition to the loop consequent on the RKAJ addition
A message informing of an abnormal termination of the RKAJ addition performed with the subsystem power
on

ADD 01-0700-01
(4) Troubleshooting
(a) When the ENC cable is connected to the Loop #1 first
It causes the recognition operation itself no problem if the Loop #0 is connected following
the connection of the Loop #1.
It is written in the maintenance procedure that the Loop #1 is to be connected after the Loop
#0 has been connected.
(b) When a failure occurs while the operation to make the RKAJ recognized is in progress Take a
recovery action against the failure, that occurs in the existing subsystem or added RKAJ when
the operation to make the RKAJ recognized is in progress, after checking the message
informing of a normal or abnormal termination of the addition.
If the recovery action is taken when the operation to make the RKAJ recognized is in
progress, an abnormal termination of the addition or a subsystem down may be caused.
(c) Failures that occur when the operation to make the RKAJ recognized is in progress
y When a failure occurs in the existing part while the operation to make the RKAJ recognized
is in progress.
Perform the recovery action, which is against a trouble occurs in the existing subsystem
while operation to make the RKAJ recognized is being done, after the addition terminates
(normally or abnormally) because the action can affect the recognition of the RKAJ.
y When failures occur in both of the existing and added parts while the operation to make the
RKAJ recognized is in progress.
When failures occur in both of the existing and added parts while the operation to make the
RKAJ recognized is in progress, take a recovery action against the failure of the existing
part preferentially after the addition completes, take a recovery action against the failure
of the added part next, and then resume the operation for making the RKAJ recognized.
(d) In the case where the operation for making the RKAJ recognized is started in the state in
which the Disk Drives other than the #0 to #3 have been installed.
NOTE : Install the Disk Drives #4 to #14 after the addition is completed. When adding
the multiple subsystems at the same time, install the Disk Drives after all the
RKAJs are recognized.
The following message is output in the Information message window in the WEB window.
I80E00 Unit ADD warning [HDU number over]
When the message above is displayed, it is possible that the addition does not complete
within the predetermined time (five minutes).
Besides, do not pull out the Disk Drive while the RKAJ is being made to be recognized.
Otherwise, an abnormal termination or a subsystem down may be caused.

ADD 01-0710-01
(e) Procedure for recovery from a system down that occurs while operation to make the RKAJ
recognized is being done.
To recover from a system down that occurs while operation to make the RKAJ recognized is
being done, remove the RKAJ which is intended to be added and in which the failure has
occurred, start up the subsystem again in the original state before the addition has been
done, and then resume the addition of the RKAJ.
If the system down recurs after the retrying, perform the addition (addition performed with
the subsystem power off) after the down occurs, and then start up the subsystem again.
(f) Loop failure that occurs while the operation to make the RKAJ recognized is in progress (in
the case where no part is blocked)
When the addition terminates abnormally because a loop failure occurs while the operation
to make the RKAJ recognized is in progress, a disconnection of a cable of the blocked loop
can recover the subsystem from the failure.
If the recovery fails, recover the subsystem from the loop failure by performing dummy
replacement (1) the finally installed ENC Unit of the existing RKM/RKAJ.
(g) When a loop failure occurs while the operation to make the RKAJ recognized is in progress
and a recovery from it fails even though the cable concerned has been disconnected.
Dummy replacement of the ENC Unit, which is connected to the related loop, of the existing
RKM/RKAJ finally mounted can recover the subsystem from the failure.
(5) Procedure for interrupting the operation for making the RKAJ recognized and notes on it
When the RKAJ recognition was interrupted, disconnect the ENC cables which were in the
process of being added; disconnect the cables of the one loop at a time.
If you disconnect all the cables at a time, the addition may be completed causing a loop
detachment or even an ENC detachment depending on the time when the disconnection is
done.
When you want to remove the RKAJ that has been added once after the addition has been
completed, perform a sequential shutdown before an LU is constructed, and then remove the
RKAJ with the subsystem power off.
When the LU has already been constructed, delete the LU and perform a sequential shutdown
(That is because the subsystem will go down at the time of the next powering on if the LU is
left.)
It causes no problem if a RAID group is constructed before the de-installation, however, the
RAID group will not be deleted after the next powering on.

ADD 01-0720-01
1 : To remove the part concerned once, and then to reinstall it (after waiting for 20 seconds)

ADD 01-0720-01
(6) Procedure for resuming an RKAJ addition with the subsystem power on when the addition has
CAUTION
y If the ENC cables are removed without ensuring intervals of 20 seconds or more,
it is feared that the system goes down.
y The system may go down if the AC Input Power Switch is turned off with the
When you want to add the RKAJ again while the subsystem power is on after the addition has
terminated abnormally, operate following the procedure shown below.
NOTE : y Turn off the AC Input Power Unit Switch of the added RKAJ which was
terminated abnormally, wait for 20 seconds or more, and turn it on again.
y When turning off the AC Power Unit Switch of the added RKAJ, do not turn off
the AC Power Unit Switch of the RKAJ that has been normally recognized (the
ALM LEDs of whose ENC Units for the both loops are off).
When turning off the AC Power Unit Switch or removing the ENC cable of the
RKAJ only that did not complete the addition, operate in the same way.
Never turn off the AC power switch of the recognized RKAJ or disconnect the
ENC cable of it because each of the above operations causes a system down.
Work-1 Check a message informing of an abnormal termination
Work-2 Remove the ENC cables See 1.3.1 Work immediately after abnormal
termination (ADD 01-0110)
Work-3 Turn off an AC Power Unit Switch of the added RKAJ See 1.3.1 Work immediately after abnormal
Work-4 Perform maintenance works according to a message See Message Chapter 1. Before Starting Trouble
informing of a factor of the abnormal termination Analysis (MSG 01-0000)
Work-5 Connect the ENC cables In the case of the connection to the RKM, see
1.6.3 (2) Connecting ENC cables (on the Loop
Work-6 Turn on an AC Power Unit Switch of the added RKAJ #0 side) (ADD 01-0630)
Wait for 20 seconds after turning off an AC Power Unit Switch of the added RKAJ, and then turn
on the AC Power Unit Switch again.

ADD 01-0730-01
1.6.5 Install the rest of the Disk Drives

Install the rest of the Disk Drives in the Disk Drive slots #4 to #14 of the RKAJ.
Attach the dummy (Disk Drive) to the each Disk Drive slot in which no Disk Drive is installed. (1)
(1) Pull the parts out of the Disk Drives safekeeping of component.
(2) Insert the Disk Drive into the position (address) where it was by holding it with the handle.
Insert the Disk Drive aligning its positioning mark with that at the location where the Disk Drive
is to be installed on the indication panel.
(3) Pull the handle lightly to make sure that the Disk Drive cannot be pulled out.
1 : Refer to Item 1.4.3 (4-1) When adding the Disk Drive (in order to expand a storage capacity) (ADD 01-0330)

ADD 01-0740-01
1.7 Adding the RKAJ/RKAJAT to the Rack Frame

(In the case of the connection to the RKM)
In the case of adding Disk Drives to a subsystem of the rackmount model, the RKAJ/RKAJAT
must be added when vacant slots for the Disk Drives to be added are insufficient in the
existing subsystem.
A procedure for adding the RKAJ/RKAJAT on the U7 rack frame while the subsystem power is
on or power is off(1) is shown below.
When mounting the RKAJ/RKAJAT on the rack frame, installation of as many rack rail kits (DF-
F700-URHT7) as the RKAJs/RKAJATs to be added are required.
1.7.1 Procedure for adding the RKAJ/RKAJAT to the subsystem of rackmount model with U7
rack frame
(1) Prerequisites
Before starting the addition, make sure that the following requirements are satisfied. If not, an
abnormal termination of the addition or a system down may be caused.
(a) At least the following components must have been installed in the RKAJ/RKAJAT to beaded.
y Two Disk Drives (a combination of the Disk Drives #0 and #1)
y Two ENC Unit/SENC Unit (Standard installation, four ENC cables (ENC Unit), two ENC cables
(SENC Unit) are included.)
y Power Unit (AC) (RKAJ)s (RKAJAT)s (Standard installation)
(b) Two(2) ENC cables per ENC Unit/SENC Unit must have been connected between the
RKAJ/RKAJAT and the RKM or RKAJ/RKAJAT.
(c) Restriction of number of the RKAJATs/RKAJATs allowed to be added is that the total number
of the RKM and RKAs/RKAJATs must not exceed the allowable maximum of fifteen after the
addition.
(d) The addition must be done only when any WARNING (WARN) LED (orange) on the subsystem is
off. If any WARNING (WARN) LED (orange) on the subsystem is on, take an action to make
the LED go out. (Refer to Troubleshooting (TRBL 00-0000) in the Maintenance Manual
(Volume of Maintenance).)
(e) No part replacement can be done while operation to make the RKAJ/RKAJAT recognized is
being done (Work-10).
1 : The expression with the subsystem power on described here means a state in which the power of the disk array
subsystem is turned on. (System operation with a host is no concern of it.).
2 :Two ENC cables are used for RKM/RKS/RKAJ, and single ENC cable is used for RKAJAT.

ADD 01-0750-01
(f) A number of installed Disk Drives when making an addition.

The installed Disk Drives when making an addition must be the #0 to #3 only.
When less than four Disk Drives are to be added, the Disk Drives #0 and #1 must have been
installed.
y When the number of the Disk Drives to be added is two, install two of them in the Disk Drive
#0 and #1.
y When the number of the Disk Drives to be added is three, install three of them in the Disk
Drive #0 to #2.
y When the number of the Disk Drives to be added is four, install four of them in the Disk
Drive #0 to #3.
(g) Install them after all the RKAJs/RKAJATs have been recognized(1) (Work-9), connect the ENC
cables between the existing subsystem and the added RKAJ/RKAJAT to be connected to the
subsystem for the each loop one by one. (See 1.7.3 Recognition and connection of the
added RKAJ/RKAJAT (ADD 01-0880).)
(h) When failures occur in both of the existing subsystem and the added RKAJ/RKAJAT while the
operation to make the RKAJ/RKAJAT recognized(1) (Work-9) is being done, take a recovery
action against the failure of the existing subsystem preferentially after the RKAJ/RKAJAT has
been recognized(1).
After that, take a recovery action against the failure of the added RKAJ/RKAJAT, and then
resume the operation.
(i) Do not perform an LU formatting while the operation to make the RKAJ/RKAJAT
recognized(1) is being done (Work-9). Also, do not perform the operation to make the
RKAJ/RKAJAT recognized(1) while an LU formatting is in progress.
(j) Do not make the addition work when the READY LED (green) on the Front Bezel is blinking at
(2) Notes when the addition terminated abnormally

The subsystem may go down if the following work is not done when the addition of
RKAJ/RKAJAT terminated abnormally.
(a) When the addition of RKAJ/RKAJAT terminated abnormally, remove each of the instructed
ENC cables at 20-second or more intervals according to the procedure.
(b) When the addition of RKAJ/RKAJAT terminated abnormally, remove all of the instructed ENC
cables according to the procedure, and turn off the AC input power switch of the Power Unit
of all the added subsystems that terminated abnormally.
1 : The expression recognized described here means that the Controller of the existing RKM recognizes the added
RKAJ/RKAJAT.

ADD 01-0760-01
(1) Procedures for installation the RKAJ/RKAJAT on Rack Frame while the subsystem power is on
(Available only in the dual controller configuration.)
When adding the RKAJ/RKAJAT on the rack frame while the subsystem power is on, make sure
of the following work items before starting the addition.
Work-1 Installing rail See Installation 3.2.1 (11) Installing the rails
(INST 03-0100)
Work-2 Unpacking the RKAJ/RKAJAT See Installation 3.3 Unpacking the Subsystems
(INST 03-0310)
Work-4 Mounting on rack frame See Installation 3.4.3 Mounting on Rack Frame
(INST 03-0410)
Work-5 Securing the RKAJ/RKAJAT See Installation 3.4.6 Securing the subsystem
(INST 03-0450)

(INST 03-0490)
(4 and 3 subsystems or 2 is RKAJ/RKAJAT)
Work-7 Connecting power cable(1) See Installation 3.4.8 Connecting Cables

(INST 03-0610)
Is there any RKAJ/RKAJAT, which is not to be

connected to the existing subsystem with the
ENC cables, among the two or more No
A To ADD 01-0780
RKAJs/RKAJATs/that have been added?
(To see the details of the connection, See 1.7.2 Connecting multiple RKAJs/RKAJATs
use the ACE Tool.) (ADD 01-0800)
Yes
Work-8 Connection when there are two or more See 1.7.2 Connecting multiple RKAJs/RKAJATs
RKAJs/RKAJATs not to be connected to the existing (ADD 01-0800)
subsystem
connected, is B.)
(2) Connecting the ENC cables
(3) Turn on the AC Power Unit
A To ADD 01-0780

ADD 01-0770-01
A From ADD 01-0770
Connection of the subsystem to be

connected to the existing
subsystem
Work-9 Recognition and connection of the added
RKAJ/RKAJAT (Recognizing and connecting the added
See 1.7.3 Recognition and connection of the
RKAJ/RKAJATto be connected to the existing
added RKAJ/RKAJAT (ADD 01-0880)
subsystem)

connected, is B.)
(3) Turn on the AC Power Unit
consequent on the RKAJ/RKAJAT addition performed
Is there any subsystem that has not been recognized,

connected, or checked among those to be connected to Yes
the existing subsystem? (1)
No
Is a message informing of completion of the addition of

the RKAJ/RKAJAT that was made while the power was No See 1.7.4 Verifying the addition (ADD 01-0980)
on displayed in the Web message window when the
RKAJs/RKAJATs not to be connected to the existing
subsystem installed were added?
Yes
Work-10 Install the rest of the Disk Drives See 1.7.5 Install the rest of the Disk Drives (ADD
01-1070)
Work-11 Attaching decoration panels See Installation 3.4.13 Attaching Decoration
Work-12 Setting the Subsystem Configuration Information See System Parameter 4.2 Setting the subsystem
configuration information (SYSPR 04-0020)
1 : Perform the operation Work-10 to the adding subsystem (in an order from the subsystem nearest to the basic
subsystem) to be connected to the existing subsystem (two RKAJs/RKAJATs at maximum).

ADD 01-0780-01
(2) Procedures for installation the RKAJ/RKAJAT on Rack Frame while the Subsystem Power Is Off
When adding the RKAJ/RKAJAT on the rack frame while the subsystem power is off, make sure
of the following work items before starting the addition.
(INST 01-0310)
Work-2 Checking a status of backing up Make sure that the Cache memory is not being
the Cache memory backed up. If the Disk Drive is added without
canceling the backup, user data may be lost.
Refer to Replacement 1.1.2 Checking cache
memory in the back-up state (REP 01-0030).
Setting the Power Control Mode (Local Mode)
Work-3 Set the mode to Local
Work-4 Installing rail See Installation 3.2 Unpacking and Installing
Work-5 Unpacking the RKAJ/RKAJAT See Installation 3.3 Unpacking the Subsystems
(INST 03-0310)
Work-7 Mounting rack frame See Installation 3.4.3 Mounting on Rack Frame
(INST 03-0400)
Work-8 Securing the RKAJ/RKAJAT See Installation 3.4.6 Securing the subsystem
(INST 03-0450)
(INST 03-0490)
(4 and 3 subsystems or 2 is RKAJ/RKAJAT)
Work-10 Connecting cable(1) See Installation 3.4.8 Connecting Cables

(INST 03-0610)
Work-11 Attaching Decoration Panels See Installation 3.4.13 Attaching Decoration

(INST 01-0290)
Work-14 Setting the Subsystem Configuration Information See System Parameter Chapter 3. Setting the
(INST 01-0310)
Work-16 Reset the Local or Remote mode to the original one Setting the Power Control Mode (Local Mode)

ADD 01-0790-01
1.7.2 Connecting multiple RKAJs/RKAJATs

When connecting the multiple RKAJs/RKAJATs at a time, perform the following.
According to the cable figure to be output from ACE Tool, connect the ENC cable.
For the operation method of ACE Tool, refer to to Installation 1.6 Device ID Setting and ENC
When adding only a single RKAJ/RKAJAT, proceed to 1.7.3 Recognition and connection of the
added RKAJ/RKAJAT (ADD 01-0880).
Refer to <Example of connection> (ADD 01-0860).

ADD 01-0800-01
(1) Displaying the procedure for connecting the ENC cables using the ACE Tool.
(a) Start the ACE Tool through the service PC.
(b) Select the subsystem.
(c) Make the configuration setting that conforms to the subsystem that have been installed on
the rack frame.
(d) Display the diagram of the ENC cable connections.
(2) Checking the ENC cables not to be connected to the existing subsystems.
Select all the adding subsystems (select the subsystems while the Ctrl key is pressed) in a state
where the diagram of the ENC cable connection is displayed. The color of the displays of the
selected subsystems is changed from gray to orange and the color of the existing subsystems
and connected to the subsystem displayed in orange is changed from gray to white. Cables
other than those that connect subsystem displayed in white and orange or cables between the
subsystems displayed in orange are the ENC cables that are not to be connected to the existing
subsystems.
(3) Connecting ENC cables (Connecting RKAJ/RKAJAT which is not to be connected to the existing
unit)
When adding the RKAJ/RKAJAT, the ENC Unit/SENC Unit has to be connected using the ENC
cable(1). Connect all the ENC cables except those between the existing subsystem and the
RKAJ/RKAJAT which is to be connected to the existing subsystem. (Following the instruction
given in the procedure 1.7.3 (2) Connecting ENC cables (on the Loop #0 side) (ADD 01-
0920).)
y When connecting the ENC cable (0.5 m) between the nearby subsystems, connect using the
ENC cable attached to the RKAJ/RKAJAT
y When connecting 5 m of the ENC cable between the racks, connect using the ENC cable
attached to the FC Cable Assembly for 2 Gbps.
excessive stresses.
y For RKAJ, the ENC cables are connected to the two paths, PATH#0 and PATH#1
of the ENC Unit #0 side (Loop #0), and the two paths, PATH#0 and PATH #1 of
the ENC Unit #1 side (Loop #1) (total of four).
For RKAJAT, the ENC cables are connected to the PATH#0 (or PATH #1) of the
SENC Unit #0 (Loop #0) and the PATH#0 (or PATH #1) of the SENC Unit #1
(Loop #1) (total of two).
y The IN and OUT connectors of the SENC Unit of the RKAJAT have indications

ADD 01-0810-01
(a) See the details of the connections with the ACE Tool.
Connect the ENC cables of the PATH #0 having milk white indications and the ENC cables of
the PATH #1 having yellow indications (see Figure 1.7.2).
Though the connectors of the RKAJAT have indications of blue and green, connect the cables
of the paths as directed by the ACE Tool.
(b) The ENC cables to be connected to the RKAJAT have no Mini-Binders attached when they
were shipped from the factory. Attach the Mini-Binders to the ENC cables of the each path
as directed by the ACE Tool
(c) Attach the milk white or yellow Mini-Binders to the ENC cables not to be connected to the
existing subsystems. Attach the milk white Mini-Binders to the ENC cables of the PATH #0
and the yellow Mini-Binders to those of the PATH #1.
(d) Attach milk white or yellow Mini-Binders to the ENC cable.
Cut off an excess portion of the cable after the Mini-Binders are attached.
NOTE : y Do not tighten the Mini-Binders too much.

y Take care not to damage the ENC cable when cutting the Mini-Binder.
Mini-Binders
5mm 5mm
Figure 1.7.1 Positions for attaching Mini-Binders
(e) Remove the rubber cap of the ENC Unit/SENC Unit of the added RKAJ/RKAJAT. However, it is
not needed to remove the rubber cap of the terminal ENC Unit/SENC Unit.
(see Figure 1.7.4 Connecting ENC Cables (ADD 01-0840))
(f) Connect the paths as directed by the ACE Tool.
1 : Keep unused cables carefully to prepare for an occasion to use them.

ADD 01-0820-01
Rack frame
RKAJ ENC cable
Connect the added RKAJs that are not to be connected
RKAJ to the existing subsystem with the ENC cables.
RKAJ Do not connect the added RKAJ to be connected to the

RKAJ They are to be connected in the step explained in 1.7.3
(ADD 01-0920).
Existing subsystem (RKM+RKAJ)
Figure 1.7.2 Connecting the ENC cables (RKM+RKAJ+RKAJs)
Rack frame
Connect the added RKAJATs that are not to be connected
RKAJAT to the existing subsystem with the ENC cables.
ENC cable
See 1.7.2 (2) Checking the ENC cables not to be
RKAJAT connected to the existing subsystems. (ADD 01-
0810).
RKAJAT Do not connect the added RKAJAT to be connected to the
RKAJAT They are to be connected in the step explained in
1.7.3 (2) Connecting ENC cables (on the Loop #0 side)
(ADD 01-0920).
Figure 1.7.3 Connecting the ENC cables (RKM+RKAJ+RKAJATs)

ADD 01-0830-01
IN side IN side
(Blue Label) Rubber cap (Blue Label) Rubber cap
OUT Side OUT Side

(Green Label) RKAJAT (04) (Green Label)
SENC Unit #0 SENC Unit #1
IN side IN side
(Blue Label) (Blue Label)
OUT Side RKAJAT (03) OUT Side

Loop #0 Loop #1
RKAJAT (04)
RKAJAT (03)
RKAJAT (02)
Indication RKAJAT (01)
position of color
(yellow)
Indication
position of color
(milk white) Rubber cap
IN side IN side
OUT Side OUT Side

(Green Label) RKAJAT (02) (Green Label)
IN side IN side
OUT Side RKAJAT (01) OUT Side


ADD 01-0840-01
(4) Turn on breakers of the upper PDBs (#01 and #11).

(5) Turn on AC Power Unit Switch of all the Power Units of the added RKAJs/RKAJATs that are not
to be connected to the existing subsystem.
The ALM LED on the ENC Unit/SENC Unit of the added RKAJ/RKAJAT concerned comes on.
Do not turn on AC Power Unit Switch of the added RKAJ/RKAJAT to be connected to the
existing subsystem.
Circuit breaker
Added RKAJ/RKAJAT adjacent to the (CB1)
Added RKAJ/RKAJAT not
existing subsystem the existing adjacent to the existing PDB#01 PDB#11
Power Unit
subsystem subsystem
(RKAJ/RKAJAT)
AC Power Unit
Switch
Existing subsystem
Main switch PDB

ADD 01-0850-01
<Example of connection>
y Before the addition: Configuration of RKM + Two RKAJs
y After the addition: Configuration of RKM + Two RKAJs + Two RKAJATs + Two RKAJs + Five
RKAJATs
Refer to
Figure 1.7.6 Example of ENC Cable Connections Directed by ACE Tool (ADD 01-0870).
(1) When all the adding subsystems are selected while the Ctrl Key is pressed, the color of the
displays of the selected subsystems is changed from gray to orange.
Cables other than those that connect subsystems displayed in the color changed from gray to
white and the units displayed in orange or cables between the subsystems displayed in orange
are the ENC cables not to be connected to the existing subsystems.
(2) Connect the ENC cables from the adding subsystem not to be connected to the existing
subsystems in the following order.
c SATA #23 (RKAJAT) and Fibre #05 (RKAJ)
d SATA #34 (RKAJAT) and Fibre #05 (RKAJ)
e Fibre #05 (RKAJ) and Fibre #06 (RKAJ)
f Fibre #06 (RKAJ) and SATA #27 (RKAJAT)
g Fibre #06 (RKAJ) and SATA #38 (RKAJAT)
h SATA #27 (RKAJ) and SATA #29 (RKAJAT)
i SATA #38 (RKAJAT) and SATA #3A (RKAJAT)
j SATA #29 (RKAJAT) and SATA #2B (RKAJAT)
There are four kinds of cable connections as shown below.

From the Fibre (RKAJ) to the SATA (RKAJAT) :
From the OUT connector of the Fibre (RKAJ) to the IN connector of the SATA (RKAJAT) (Up to
the two SATAs (RKAJATs) can be connected to the one Fibre (RKAJ).)
From the SATA (RKAJAT) to the Fibre (RKAJ) :
From the OUT connector of the SATA (RKAJAT) to the IN connector of the Fibre (RKAJ) (The
one Fibre (RKAJ) can be connected to the two SATAs (RKAJATs).)
From the Fibre (RKAJ) to the Fibre (RKAJ) :
From the OUT connector of the Fibre (RKAJ) to the IN connector of the Fibre (RKAJ) (The one
Fibre (RKAJ) can be connected to the one Fibre (RKAJ).)
From the SATA (RKAJAT) to the SATA (RKAJAT) :
From the OUT connector of the SATA (RKAJAT) to the IN connector of the SATA (RKAJAT)
(The one SATA (RKAJAT) can be connected to the one SATA (RKAJAT).)

ADD 01-0860-01
(3) Turn on all the AC Power Unit Switches of the added RKAJs/RKAJATs not to be connected to
the existing subsystems (the units displayed in a color to be changed to gray when all the units
already installed are selected while the Ctrl key is pressed).
In this case, the subsystems to be powered on are Fibre #05 (RKAJ), Fibre #06 (RKAJ), SATA #27
(RKAJAT), SATA #38 (RKAJAT), SATA #29 (RKAJAT), SATA #3A (RKAJAT) and SATA #2B (RKAJAT).
(3)
(1), (2) Adding subsystems
Existing subsystems
Figure 1.7.6 Example of ENC Cable Connections Directed by ACE Tool

ADD 01-0870-01
1.7.3 Recognition and connection of the added RKAJ/RKAJAT

To make the added RKAJ/RKAJAT recognized, satisfy the following requirements.

1 Disk Drive The Disk Drives #0 to #3 must be installed in the RKAJ/RKAJAT to be added.
When less than four Disk Drives are to be added, the Disk Drives #0 and #1
must be installed in the RKAJ/RKAJAT.
2 The Disk Drives #4 to #14 must not be installed in the RKAJ/RKAJAT to be
added
3 ENC Unit/SENC Unit The two units must be installed in the RKAJ/RKAJAT to be added.
4 Power Unit The two units must be installed in the RKAJ/RKAJAT to be added.
(RKAJ/RKAJAT)
5 WARNING (WARN) LED of the No WARNING (WARN) LED must be on
subsystem
6 Device ID The device ID must be set correctly
(Refer to Installation 3.4.7 (1-2) Setting Device ID number (INST 03-0520).)
7 Subsystem identification switch The subsystem identification switch must be set correctly.
(Refer to Installation 3.4.7 (1-3) Setting the subsystem identification switch
(INST 03-0520).)
8 Number of connectable The addition must not make the total number of the RKM and
RKAJs/RKAJATs exceed the allowable maximum of fifteen.
9 Other maintenance works No other maintenance work must be in progress.
When the requirements above are satisfied, perform the operation following the procedure
for making the RKAJ/RKAJAT recognized shown below.
When making the multiple RKAJs/RKAJATs recognized at a time, satisfy the following
requirements in addition.

1 Making the multiple Are the ENC cables connected correctly to the added RKAJs/RKAJATs other
RKAJs/RKAJATs recognized at a than the RKAJ/RKAJAT connected with the existing subsystem?
2 time Are the Power Units of the added RKAJs/RKAJATs other than the
RKAJ/RKAJAT connected with the existing subsystem turned on?

ADD 01-0880-01
(1) Procedure for making the added RKAJ/RKAJAT recognized

Perform the RKAJ/RKAJAT recognition operation following the flowchart below.
If a failure occurs during the work, check a Web message and take an action for recovery from the
failure referring to 1.7.4 (4) Troubleshooting (ADD 01-1030).
Perform the recognition operation for the adding subsystems to be connected to the existing
subsystems one by one starting from the adding subsystem nearest to the basic subsystem.
Start of the recognition procedure D From ADD 01-0910

From ADD 01-0900
B
Connect the cables on the Loop #0 side of the
added RKAJ/RKAJAT to be connected to the
existing subsystem. Connect the ENC cables on the Loop #0 side
(See (2) Connecting ENC cables (on the removed in in 1.3.1 Work immediately after
Loop #0 side) (ADD 01-0920).) abnormal termination (ADD 01-0110).
Turn on the AC power input switch of the

Power Unit #0 and #1 in an added Turn on the power supply of the added
RKAJ/RKAJAT to be connected to a
subsystem already installed. subsystem which turned off the power
(See Item (3) Turn on the AC Power Unit supply in in 1.3.1 Work immediately after
Switch of the Power Units (#0, #1) of the abnormal termination (ADD 01-0110).
added RKAJ/RKAJAT to be connected to
the existing subsystem. (ADD 01-0960)) (The ALM LED on the ENC Unit / SENC Unit
(The ALM LED on the ENC Unit / SENC Unit comes on.)
comes on.)
Did the ALM LED of the ENC Unit/ SENC

Unit on the Loop #0 side go out? Yes A To ADD 01-0900
(Refer to 1.7.4 Verifying the addition
(ADD 01-0980))
No
Have five minutes elapsed after the Yes
RKAJ/RKAJAT was powered on?
No (Refer to Troubleshooting 3.1 Procedure to
WEB connection (TRBL 03-0000))
Is a message that the RKAJ/RKAJAT addition

The case where the addition is
(performed with the subsystem power on) has been
not recognized. No started displayed in the Web message window?
(Refer to 1.7.4 (1) (b) Contents of the WEB message
(ADD 01-0990))
Yes
termination (refer to to 1.3.1 Work immediately termination (refer to to 1.3.1 Work immediately
Replace the ENC cable or the ENC unit/SENC Unit

on the Loop #0 side of the existing subsystem that Perform maintenance following the Web
was finally mounted. (refer to Replacement 2.2.9 message
Replacing ENC Unit/SENC Unit (REP 02-0830)).

ADD 01-0890-01
A From ADD 01-0890

Troubleshooting 3.1 Procedure to WEB
connection (TRBL 03-0000)
Make sure that there is a message displayed in

the Web message window ( Refer to 1.7.4 (1)
(b) Contents of the WEB message (ADD 01-
0990)) indicating that the RKAJ/RKAJAT addition
(performed with the subsystem power on) to
Loop #0 has been completed.
Connect the cables on the Loop #1 side of the

added RKAJ/RKAJAT to be connected to the
existing subsystem. (See (2) Connecting ENC
cables (on the Loop #0 side) (ADD 01-0920))
Did the ALM LED of the ENC

Unit/SENC Unit on the Loop #1 side go Yes
out? (Refer to 1.7.4 Verifying the
addition (ADD 01-0980))
No
Have five minutes elapsed after the
Yes
ENC cables of the Loop #1 were
connected?
No
Is a message that the RKAJ/RKAJAT addition The case where the addition is
(performed with the subsystem power on) has been No not recognized.
started displayed in the Web message window?
( Refer to 1.7.4 (1) (b) Contents of the WEB
Yes
termination (refer to 1.3.1 Work immediately termination (refer to 1.3.1 Work immediately
Replace the ENC cable or the ENC unit/SENC

Perform maintenance following
Unit on the Loop #1 side of the existing
the Web message
subsystem that was finally mounted.
B B
To ADD 01-0890 To ADD 01-0890
C To ADD 01-0910

ADD 01-0900-01
C From ADD 01-0910
Make sure of a message that the RKAJ/RKAJAT

addition (performed with the subsystem power
on) to the Loop #1 has been completed
displayed in the Web message window.
(Refer to 1.7.4 (1) (b) Contents of the WEB
Is there a subsystem to be connected to the

existing subsystems? (See (2) (a) Seeing the Yes To ADD 01-0890
ENC cables to be connected to the existing D
subsystems (ADD 01-0930))
No
When the two or more RKAJs/

RKAJATs have been added: Is a message
concerning the RKAJ/RKAJAT to be added
that the RKAJ/RKAJAT addition No
(performed with the subsystem power on)
has been started displayed in the Web
message window?
Yes
Make sure that READY LED (green) on the
Front Bezel lights on (when it is blinking at
high speed, wait until it lights on after the
maximum of 30/50 minutes.)
Yes
Is a Disk Drive installed?
No
Mount one of the Disk Drives#4 to #14 to be
added.(1).
Did the ALARM LED of the Disk Drive

No Replace the Disk Drive concerned
come on and then go out about five
minute later? and make a retry.
Yes
Is there another Disk Drive to be Yes
added?
No
The addition has completed
1 : Refer to 1.4.3 (4-1) When adding the Disk Drive (in order to expand a storage capacity) (ADD 01-0330).

ADD 01-0910-01

When adding the RKAJ/RKAJAT while the subsystem power is on, it is required to connect the
ENC Unit/SENC Unit for the Loop #0 (ENC #0) of the RKAJ/RKAJAT to be added and the ENC
Unit/SENC Unit with the ENC cables (1).
Do not connect the ENC cables of the both loops Loop #0 and Loop #1 at a time.
Otherwise, the subsystem may go down.
Connect the ENC cables of the Loop #1 after verifying the completion of the addition to the
Loop #0.
NOTE : y Be sure to connect the ENC cable from the subsystem to be added.
If it is connected from the existing subsystem, the loop failure occurs.
y For the single Control Unit configuration, connect the Loop #0 (ENC Unit
#0/SENC Unit #0) side only, and do not connect the Loop #1 (ENC Unit
#1/SENC Unit #1) side.
When the multiple RKAJs/RKAJATs are mounted, however, connect the ENC
Unit #1/SENC Unit #1 as well as the ENC Unit #0/SENC Unit #0 among the
RKAJs/RKAJATs by the ENC cables.
excessive stresses.
y For RKAJ, the ENC cables are connected to the to two paths, PATH#0 and
PATH#1 of the ENC Unit #0 side (Loop #0) and the two paths, PATH#0 and PATH
#1 of the ENC Unit #1 side (Loop #1) (total of four).
color indication. Be careful to keep the color of the PATH #0 in milky-white
For RKAJAT, the ENC cables are connected to the PATH#0 (or PATH #1) of the
SENC Unit #0 (Loop #0) and the PATH#0 (or PATH #1) of the SENC Unit #1
(Loop #1) (total of two).
y The IN and OUT connectors of the SENC Unit of the RKAJAT have indications

ADD 01-0920-01
(a) Seeing the ENC cables to be connected to the existing subsystems

See the required connections using the ACE Tool.
For the operation method of ACE Tool, refer to Installation 1.6 Device ID Setting and ENC
Refer to <Example of connection> (ADD 01-0970).
( i ) Change the color of the displays of all the adding subsystems to orange by selecting them
while the Ctrl key is pressed.
Cables connected to the subsystems displayed in a color changed to white are the ENC
cables to be connected to the existing subsystems.
(ii) In the case of the RKAJAT/RKAJATL, also see the details of the paths because the milk
white or yellow Mini-Binders are to be attached to the ENC cables.
Attach the milk white Mini-Binders to the ENC cables of the PATH #0 and the yellow Mini-
Binders to those of the PATH #1.
(iii) See the details of the Loops using the ACE Tool.
When the ACE Tool is used, the Loop #0 is displayed with red or green lines and the Loop
#1, with blue or pink lines.
(b) Attach the milk white or yellow Mini-Binders to the ENC cables
(see Figure 1.7.9 Connecting ENC Cables (ADD 01-0950)).
(c) Remove the rubber cap of the output connector of the FC-AL of the terminal existing
subsystems (RKM /RKAJ/RKAJAT).
(d) Make connections on the Loop #0 side as directed by the ACE Tool
(see the Loop #0 in Figure 1.7.9 Connecting ENC Cables (ADD 01-0950)).
Connect the ENC Unit/SENC Unit in the Loop #0 of the added RKAJ/RKAJAT to be connected
to the existing subsystem and the output connector of the FC-AL in the Loop #0 of the
existing subsystem (RKM/RKAJ/RKAJAT) with the ENC cables.
(e) Perform the work on the Loop #1 side after completing the Loop #0 side.

ADD 01-0930-01
Rack frame
RKAJ
ENC cable
RKAJ Connect the added RKAJs that are not to be connected to the existing
subsystem with the ENC cables.
RKAJ See 1.7.2 (3) Connecting ENC cables (Connecting RKAJ/RKAJAT
which is not to be connected to the existing unit) (ADD 01-0810).
RKAJ
Connect the added RKAJ to be connected to the existing subsystem
with the ENC cables now.
They are to be connected in the step explained in.

Figure 1.7.7 Connecting the ENC cables (RKM+RKAJ+RKAJs)
Rack frame
RKAJAT Connect the added RKAJATs that are not to be connected to the
ENC cable
existing subsystem with the ENC cables.
RKAJAT See 1.7.2 (3) Connecting ENC cables (Connecting RKAJ/RKAJAT
which is not to be connected to the existing unit) (ADD 01-0810).
RKAJAT
Connect the added RKAJAT to be connected to the existing
RKAJAT subsystem with the ENC cables now.
They are to be connected in the step explained in.

Figure 1.7.8 Connecting the ENC cables (RKM+RKAJ+RKAJATs)

ADD 01-0940-01

ENC cable (yellow)
IN side IN side
OUT Side OUT Side

IN side IN side
OUT Side OUT Side

Loop #0 SENC Unit #0

SENC Unit #1 Loop #1
RKAJAT
RKM
Indication (RKS)
position of color
(yellow)
Indication
position of color
(milk white) Control Unit #1 Attach milk white or yellow Mini-Binders
Rubber cap Control Unit #0 to the ENC cable.
Cut off an excess portion of the cable
after the Mini-Binders are attached.
NOTE
y Do not tighten the Mini-Binders
too much.
LASER PRODUCT
CLASS 1
LASER KLASSE 1
y Take care not to damage the

Control Unit #1 ENC cable when cutting the
Mini-Binder.
Control Unit #0 Mini-Binders
LASER KLASSE 1
CLASS 1
LASER PRODUCT
5mm 5mm
PATH #1 (yellow) Positions for attaching Mini-Binders

ADD 01-0950-01
(3) Turn on the AC Power Unit Switch of the Power Units (#0, #1) of the added RKAJ/RKAJAT to be
connected to the existing subsystem.
Circuit breaker
(CB1)
Added RKAJ/RKAJAT adjacent to
the existing subsystem PDB#01 Power Unit PDB#11
(RKAJ/RKAJAT)
AC Power Unit
Switch
Existing subsystem
Main switch PDB

ADD 01-0960-01
<Example of connection>
y Before the addition: Configuration of RKM + Two RKAJs
y After the addition: Configuration of RKM + Two RKAJs + Two RKAJATs + Two RKAJs + Five
RKAJATs
Refer to Figure 1.7.11 Example of ENC Cable Connections Directed by ACE Tool.
When all the adding subsystems are selected while the Ctrl key is pressed, the color of the
displays of the selected subsystems is changed from gray to orange.
Cables connected to the subsystems displayed in a color changed from gray to white are the
ENC cables that are to be connected to the existing subsystems.
Check the recognition of the adding subsystems to be connected to the existing subsystems one
by one starting from the adding subsystem nearest to the basic subsystem.
Connect the ENC cable on the Loop #1 side after the addition concerning the Loop #0 is
completed.
(i) The first recognition : Fibre #02 (RKAJ) and SATA #23 (RKAJAT)
(ii) The second recognition : Fibre #02 (RKAJ) and SATA #34 (RKAJAT)
NOTE : y Do not connect the ENC cables of the Loops #0 and #1 at the same time
because the system may go down otherwise.
y When the ACE Tool is used, the Loop #0 is displayed with red lines and the
Loop #1, with blue lines.
Adding subsystems
(ii)
(i
(ii) (i)
Existing subsystems

ADD 01-0970-01
Figure 1.7.11 Example of ENC Cable Connections Directed by ACE Tool

ADD 01-0970-01

(a) Procedure for verifying completion of the addition to the loop
When the ALM LED on the ENC Unit/SENC Unit to which the ENC cables have been connected
and the WARNING (WARN) LED of the RKAJ/RKAJAT are off, the addition to the loop has been
completed normally.
Incidentally, the completion of the addition to the loop or a message output when a trouble
occurs can be checked in the Information Message window that is one of the WEB windows.
RKAJ Rear
CHECK
ENC Unit#0 ENC Unit#1
P0 ALM
Figure 1.7.12 Locations of LED for ENC Unit
RKAJAT Rear
CHECK
P0 ALM
Figure 1.7.13 Locations of LED for SENC Unit

ADD 01-0980-01

MM/DD/YYYY HH:MM:SS Cx I80300 Unit ADD complete (Loop-y)

MM/DD/YYYY HH:MM:SS Cx I80100 Unit ADD start (Loop-y)
MM/DD/YYYY HH:MM:SS Cx I80004 Unit ADD start (Unit-x)

A message informing of a start of the RKAJ/RKAJAT addition performed with the system power on
A message informing of a start of the addition to the loop consequent on the RKAJ/RKAJAT addition
A message informing of completion of the addition to the loop consequent on the RKAJ/RKAJAT addition

ADD 01-0990-01

termination.

MM/DD/YYYY HH:MM:SS Cx I80D0y Unit ADD FAIL [cable off] (Loop-y) :MANUAL/TRC

A message informing of a start of the addition to the loop consequent on the RKAJ/RKAJAT addition performed
A message informing of an abnormal termination of the addition to the loop consequent on the RKAJ/RKAJAT
addition performed with the subsystem power on
A message informing of an abnormal termination of the RKAJ/RKAJAT addition performed with the subsystem
power on

ADD 01-1000-01

Connect the ENC cables on the Loop #1 side in the same way as the Loop #0.
When the ACE Tool is used, the Loop #0 is displayed with red or green lines and the Loop #1,
with blue or pink lines. For the procedure for connecting the ENC cables, refer to Figure
1.7.7 Connecting the ENC cables (RKM+RKAJ+RKAJs) (ADD 01-0940) and Figure 1.7.8
Connecting the ENC cables (RKM+RKAJ+RKAJATs) (ADD 01-0940), refer to Figure 1.7.9
Connecting ENC Cables (ADD 01-0950).
(3) Verifying completion of the addition to the loop consequent on the RKAJ/RKAJAT addition
(a) Procedure for verifying completion of the addition to the loop consequent on the
RKAJ/RKAJAT addition performed with the subsystem power on.
When the ALM LED of the ENC Unit/SENC Unit to which the ENC cables have been connected
and the WARNING (WARN) LED of the RKAJ/RKAJAT/RKAJATL are off, you can verify
completion of the addition to the loop by viewing the Information message window in the
WEB window.
MM/DD/YYYY HH:MM:SS Cx I8020x Unit ADD complete (Unit-x)


A message informing of an l termination of the RKAJ/RKAJAT addition performed with the subsystem power
on

ADD 01-1010-01

termination.

MM/DD/YYYY HH:MM:SS Cx I8010y Unit ADD FAIL [cable off] (Loop-y)

A message informing of an abnormal termination of the addition to the loop consequent on the
RKAJ/RKAJAT addition performed with the subsystem power on
A message informing of an abnormal termination of the RKAJ/RKAJAT addition performed with the
subsystem power on

ADD 01-1020-01
(4) Troubleshooting
(a) When the ENC cable is connected to the Loop #1 first
It causes the recognition operation itself no problem if the Loop #0 is connected following
the connection of the Loop #1.
It is written in the maintenance procedure that the Loop #1 is to be connected after the Loop
#0 has been connected.
(b) When a failure occurs while the operation to make the RKAJ/RKAJAT recognized is in
progress Take a recovery action against the failure, that occurs in the existing subsystem or
added RKAJ/RKAJAT when the operation to make the RKAJ/RKAJAT recognized is in progress,
after checking the message informing of a normal or abnormal termination of the addition.
If the recovery action is taken when the operation to make the RKAJ/RKAJAT recognized is in
progress, an abnormal termination of the addition or a subsystem down may be caused.
(c) Failures that occur when the operation to make the RKAJ/RKAJAT recognized is in progress
y When a failure occurs in the existing part while the operation to make the RKAJ/RKAJAT
recognized is in progress.
Perform the recovery action, which is against a trouble occurs in the existing subsystem
while operation to make the RKAJ/RKAJAT recognized is being done, after the addition
terminates (normally or abnormally) because the action can affect the recognition of the
RKAJ/RKAJAT.
y When failures occur in both of the existing and added parts while the operation to make the
RKAJ/RKAJAT recognized is in progress.
When failures occur in both of the existing and added parts while the operation to make the
RKAJ/RKAJAT recognized is in progress, take a recovery action against the failure of the
existing part preferentially after the addition completes, take a recovery action against the
failure of the added part next, and then resume the operation for making the RKAJ/RKAJAT
recognized.

ADD 01-1030-01
(d) In the case where the operation for making the RKAJ/RKAJAT recognized is started in the
state in which the Disk Drives other than the #0 to #3 have been installed.
NOTE : Install the Disk Drives #4 to #14 after the addition is completed.
When adding the multiple subsystems at the same time, install the Disk Drives
after all the RKAJs/RKAJATs are recognized.
The following message is output in the Information message window in the WEB window.
I80E00 Unit ADD warning [HDU number over]
When the message above is displayed, it is possible that the addition does not complete
within the predetermined time (five minutes).
Besides, do not pull out the Disk Drive while the RKAJ/RKAJAT is being made to be
recognized.
Otherwise, an abnormal termination or a subsystem down may be caused.
(e) Procedure for recovery from a system down that occurs while operation to make the
RKAJ/RKAJAT recognized is being done.
To recover from a system down that occurs while operation to make the RKAJ/RKAJAT
recognized is being done, remove the RKAJ/RKAJAT which is intended to be added and in
which the failure has occurred, start up the subsystem again in the original state before the
addition has been done, and then resume the addition of the RKAJ/RKAJAT.
If the system down recurs after the retrying, perform the addition (addition performed with
the subsystem power off) after the down occurs, and then start up the subsystem again.
(f) Loop failure that occurs while the operation to make the RKAJ/RKAJAT recognized is in
progress (in the case where no part is blocked)
When the addition terminates abnormally because a loop failure occurs while the operation
to make the RKAJ/RKAJAT recognized is in progress, a disconnection of a cable of the
blocked loop can recover the subsystem from the failure.
If the recovery fails, recover the subsystem from the loop failure by performing dummy
replacement (1) the finally installed ENC Unit/SENC Unit of the existing RKM/RKAJ/RKAJAT.
(g) When a loop failure occurs while the operation to make the RKAJ/RKAJAT recognized is in
progress and a recovery from it fails even though the cable concerned has been
disconnected.
Dummy replacement of the ENC Unit/SENC Unit, which is connected to the related loop, of
the existing RKM/RKAJ/RKAJAT finally mounted can recover the subsystem from the failure.

ADD 01-1040-01

ADD 01-1040-01
(5) Procedure for interrupting the operation for making the RKAJ/RKAJAT recognized and notes on
it
When the RKAJ/RKAJAT recognition was interrupted, disconnect the ENC cables which were in
the process of being added; disconnect the cables of the one loop at a time.
If you disconnect all the cables at a time, the addition may be completed causing a loop
detachment or even an ENC detachment depending on the time when the disconnection is
done.
When you want to remove the RKAJ/RKAJAT that has been added once after the addition has
been completed, perform a sequential shutdown before an LU is constructed, and then remove
the RKAJ/RKAJAT with the subsystem power off.
When the LU has already been constructed, delete the LU and perform a sequential shutdown
(That is because the subsystem will go down at the time of the next powering on if the LU is
left.)
It causes no problem if a RAID group is constructed before the de-installation, however, the
RAID group will not be deleted after the next powering on.

ADD 01-1050-01
(6) Procedure for resuming an RKAJ/RKAJAT addition with the subsystem power on when the
addition has terminated abnormally.
CAUTION
y If the ENC cables are removed without ensuring intervals of 20 seconds or more,
it is feared that the system goes down.
y The system may go down if the AC Input Power Switch is turned off with the
When you want to add the RKAJ/RKAJAT again while the subsystem power is on after the
addition has terminated abnormally, operate following the procedure shown below.
NOTE : y Turn off the AC Input Power Unit Switch of the added RKAJ/RKAJAT which
was terminated abnormally, wait for 20 seconds or more, and turn it on
again.
y When turning off the AC Power Unit Switch of the added RKAJ/RKAJAT, do not
turn off the AC Power Unit Switch of the RKAJ/RKAJAT that has been normally
recognized (the ALM LEDs of whose ENC Units/SENC Units for the both loops
are off).
When turning off the AC Power Unit Switch or removing the ENC cable of the
RKAJ/RKAJAT only that did not complete the addition, operate in the same
way.
Never turn off the AC power switch of the recognized RKAJ/RKAJAT or
disconnect the ENC cable of it because each of the above operations causes a
system down.
Work-1 Check a message informing of an abnormal termination
Work-2 Remove the ENC cables See 1.3.1 Work immediately after abnormal
Work-3 Turn off an AC Power Unit Switch of the added See 1.3.1 Work immediately after abnormal
RKAJ/RKAJAT termination (ADD 01-0110)
Work-4 Perform maintenance works according to a message See Message Chapter 1. Before Starting Trouble
informing of a factor of the abnormal termination Analysis (MSG 01-0000)
Work-5 Connect the ENC cables See 1.7.3 (2) Connecting ENC cables (on the
Loop #0 side) (ADD 01-0920)
Work-6 Turn on an AC Power Unit Switch of the added
RKAJ/RKAJAT

ADD 01-1060-01
Wait for 20 seconds after turning off an AC Power Unit Switch of the added RKAJ/RKAJAT, and
then turn on the AC Power Unit Switch again.

ADD 01-1060-01
1.7.5 Install the rest of the Disk Drives

Install the rest of the Disk Drives in the Disk Drive slots #4 to #14 of the RKAJ/RKAJAT.
Attach the dummy (Disk Drive) to the each Disk Drive slot in which no Disk Drive is installed. (1)
(1) Pull the parts out of the Disk Drives safekeeping of component
(2) Insert the Disk Drive into the position (address) where it was by holding it with the handle.
Insert the Disk Drive aligning its positioning mark with that at the location where the Disk Drive
is to be installed on the indication panel.
(3) Pull the handle lightly to make sure that the Disk Drive cannot be pulled out.
1 : Refer to 1.4.3 (4-1) When adding the Disk Drive (in order to expand a storage capacity) (ADD 01-0330)

ADD 01-1070-01
Chapter 2. Subtracting Optional Components

2.1 Before Starting Subtraction of Optional Components
If you make a mistake in operation during a subtraction of the optional component, it is feared
that user data in the subsystem is lost. Therefore, perform the following before starting the
subtraction of the optional component to provide against an unexpected accident.

(2) The work to subtraction an optional component varies depending on the component and a
location where the component is to be installed. Besides, perform the addition after making
sure whether the work must be done with the subsystem power on or off.
y An subtraction with the subsystem power on :
y An subtraction with the subsystem power off :
(3) When subtraction the optional component, it is required to change the settings of the
subsystem using a service PC connected via a LAN. Make the following preparations before
starting the addition of the optional component.
y Prepare a PC in which Storage Navigator Modular is installed. The PC must be used in the
LAN environment.
y Ask the customer whether the subsystem is operable via a LAN. If not, obtain customers
permission to operate the subsystem via a LAN.
(4) Promote mutual understanding with the user about the possibility of a system down in order to
minimize damage caused by failures.
(5) Be sure to install a dummy Control Unit and a dummy Disk Drive in a vacant slot because
dummy Control Unit and dummy Disk Drive are required for adjusting the cooling air flow.
When subtracting the optional component with the subsystem power on, the operation
replacing Disk Drive with dummy Disk Drive has to be finished within 10 minutes.
(6) In the case where the operation mode(1) of the spare Disk Drive is specified as variable, it is
possible that the RAID group configuration or the spare Disk Drive configuration has become
different from that, which was at the time when the subsystem was introduced, depending on
the history of Disk Drive failures that have occurred after the subsystem installation.
Check if the configuration examples conform to that described in 2.1.1 Preparatory works for
subtraction (ADD 02-0010) before starting the subtraction. When the conformity is confirmed,
execute the procedure for the preparation.
1 : For details of the spare Disk Drive operation mode, refer to Theory 4.6 (3) Operation after replacing failed
Disk Drive (THEO 04-0240).

ADD 02-0000-01
2.1.1 Preparatory works for subtraction

In the case where the operation mode of the spare Disk Drive is specified as variable, it is
possible that the RAID group configuration or the spare Disk Drive configuration has become
different from that at the time when the subsystem was introduced.
The Configuration examples concerned are shown in the following Items (1) to (4).
When they conform to these configuration examples, execute the following works before
starting the subtraction.
Also, if the RAID group configuration of the additional chassis to be subtracted was changed
from that at the time when the subsystem was introduced, restore the additional chassis to be
subtracted to the configuration at the time when the subsystem was introduced, and then
execute the subtraction work.
(1) When the additional subsystem to be de-installed has a Disk Drive that composes a RAID group
unable to be eliminated
< Status at the time when the subtraction is started > < Status at the time when the subsystem was introduced >
RKAJ (Device ID #01) RKAJ (Device ID #01)
Disk Drive numbers Disk Drive numbers

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14
R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R0 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 R1 S1
RKM (Device ID #00) RKM (Device ID #00)

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14
R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 S1 S0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 R0 S0
RKAJ (Device ID #01) : Additional subsystem to be subtracted * When the R0 has been detached in the past, there
R1 :RAID group that can be eliminated may be a case where its data is restored to a
S1 :Spare Disk Drive that can be relieved of its role spare Disk Drive ( Device ID #01, Drive #14). In
R0 :RAID group that cannot be eliminated the case above, the configuration may become the
S0 :Spare Disk Drive that cannot be relieved of its role one shown on the left.

ADD 02-0010-01
(a) Make sure that the model names of Disk Drive (Device ID #01, Drive #14) and the spare Disk
Drive (Device ID #00, Drive #13) are the same.
You can make sure of it by checking the Product ID and Capacity of the Disk Drive shown
when you select the Component Status tab of Storage Navigator Modular. (For the details,
refer to System Parameter 3.5 Checking the status of Disk Drive (SYSPR 03-0400).)
(b) Output the text file of the RAID group/Logical unit in the configuration copy information.
(For the details, refer to System Parameter 4.2 (7) Setting of Constitute (SYSPR 04-0150).)
(c) Relieve spare Disk Drives other than the S1of their roles. (For the details, refer to System
Parameter [Procedure f-C]Deleting Spare Disk (SYSPR 03-0380).)
(d) Execute the dynamic sparing for the Disk Drive (Device ID #01, Drive #14). (For the details,
refer to Troubleshooting 10.2.7 Drive Maintenance (TRBL 10-0330).)
(e) Make sure that the Disk Drive (Device ID #00, Drive #13) becomes a data Disk Drive that is a
component of the R0 and the Disk Drive (Device ID #01, Drive #14) becomes a detached Disk
Drive(1) as a spare Disk Drive after the dynamic sparing is completed(2).
You can make sure of it by checking the Type and Status of the Disk Drive shown when
you select the Component Status tab of Storage Navigator Modular. (For the details, refer to
System Parameter 3.5 Checking the status of Disk Drive (SYSPR 03-0400).)
(f) Reset the spare Disk Drive that was relieved of its role in Step (c) referring to the text file
that was output in Step (b).
(For the details, refer to System Parameter 3.4 [Procedure f-B]Setting Spare Disk (SYSPR
03-0360).)
However, the Disk Drive (Device ID #00, Drive #13) cannot be set as a spare Disk Drive.
(g) Make sure that there is no other Disk Drive, which composes a RAID group that cannot be
eliminated, than the additional unit to be de-installed. If such a Disk Drive exists, repeat the
works again from Step (c).
(h) Output the text file of the RAID group/Logical unit in the configuration copy information
again. (For the details, refer to System Parameter 4.2 (7) Setting of Constitute (SYSPR 04-
0150).)
(i) Make sure that the current settings of the RAID groups and spare disks are correct and neither
more not less by comparing the text file that was output in Step (b) with that output in Step
(h). At this time roles of the Disk Drives (Device ID #00, Drive #13 and Device ID #01, Drive
#14) as a data Disk Drive and spare Disk Drive are reversed.
1: The Disk Drive (Device ID #01, Drive #14) is detached. However, do not replace it because the detachment does not
mean a trouble.
2: It takes a while to complete the dynamic sparing. For the standard time required, refer to Table 2.2.2 Standard
Time Required for the Correction copy or Copy back in Replacement (4) Confirming completion of data recovery
or copy back (REP 02-0230).

ADD 02-0020-01
(2) When the additional subsystem to be de-installed has a spare Disk Drive that cannot be relieved
of its role

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14
RKAJ (Device ID #01) : Additional subsystem to be subtracted * When the R0 has been detached in the past, there
R1 :RAID group that can be eliminated may be a case where its data is restored to a
S1 :Spare Disk Drive that can be relieved of its role spare Disk Drive ( Device ID #01, Drive #14). In
R0 :RAID group that cannot be eliminated the case above, the configuration may become the
S0 :Spare Disk Drive that cannot be relieved of its role one shown on the left.

ADD 02-0030-01
03-0360).)
eliminated, than the additional unit to be de-installed.
If such a Disk Drive exists, make a dummy replacement(3) of the spare Disk Drive (Device ID
#00, Drive #14) that was detached and repeat the works from Step (c) after making sure that
the Disk Drive was recovered from the detachment(4).
0150).)
mean a trouble.
3: Dummy replacement is to remove a component concerned once, wait for longer than 20 seconds, and then reinstall
the component.
4: I009xy Spare HDU recovered (x: Unit number, y: HDU number) is displayed in the Information Message of the Web
and the ALARM LED (red) on the Disk Drive concerned goes out.

ADD 02-0040-01
(3) When the Disk Drives to be de-installed include a Disk Drive that composes a RAID group unable
to be eliminated

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14
RKAJ (Device ID #01) : Additional subsystem that has a Disk Drive to be * When the R0 has been detached in the past, there
subtracted may be a case where its data is restored to a
R1 :RAID group that can be eliminated spare Disk Drive ( Device ID #01, Drive #14). In
S1 :Spare Disk Drive that can be relieved of its role the case above, the configuration may become the
R0 :RAID group that cannot be eliminated one shown on the left.
S0 :Spare Disk Drive that cannot be relieved of its role

ADD 02-0050-01
03-0360).)
eliminated, than that to be subtracted. If such a Disk Drive exists, repeat the works again
from Step (c).
0150).)
mean a trouble.

ADD 02-0060-01
(4) When a spare Disk Drive that cannot be eliminated is included in Disk Drives to be subtracted

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14

#00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14 #00#01 #02#03 #04 #05 #06 #07 #08 #09 #10 #11 #12 #13 #14
RKAJ (Device ID #01) : Additional subsystem that has a Disk Drive to be * When the R0 has been detached in the past, there
subtracted may be a case where its data is restored to a
R1 :RAID group that can be eliminated spare Disk Drive ( Device ID #01, Drive #14). In
S1 :Spare Disk Drive that can be relieved of its role the case above, the configuration may become the
R0 :RAID group that cannot be eliminated one shown on the left.
S0 :Spare Disk Drive that cannot be relieved of its role

ADD 02-0070-01
03-0360).)
eliminated, than the additional unit to be de-installed.
If such a Disk Drive exists, make a dummy replacement(3) of the spare Disk Drive (Device ID
#00, Drive #14) that was detached and repeat the works from Step (c) after making sure that
the Disk Drive was recovered from the detachment(4).
again. (For the details, refer toSystem Parameter 4.2 (7) Setting of Constitute (SYSPR 04-
0150).)
mean a trouble.
3: Dummy replacement is to remove a component concerned once, wait for longer than 20 seconds, and then reinstall
the component.
4: I009xy Spare HDU recovered (x: Unit number, y: HDU number) is displayed in the Information Message of the Web
and the ALARM LED (red) on the Disk Drive concerned goes out.

ADD 02-0080-01
2.2 Procedures for Subtracting Optional Components

(1) Procedure for subtracting an optional component while the subsystem power on
NOTE : For safety use, always close the front bezel after the operation.
START
Work-1 User data backup Because there is a possibility that user data is
System parameter backup lost, it is recommended to back up user data to
prepare against the risk.(1)
Work-2 Connection of a service PC and the subsystem See System Parameter 1.1 Procedure for

by the operation of the service PC
(1) Setting of a Spare Disk
(2) Setting of RAID and an LU
(3) Setting of a LUN recognition
Work-4 Do the preparatory works for the subtraction See 2.1.1 Preparatory works for subtraction
when necessary. (ADD 02-0010)
Work-5 Remove the cables connected to the subtraction Unit.

See Installation 2.6 Connecting Cables
(INST 02-0300)
(INST 03-0610)
Work-6 Subtracting optional components See 2.4.3 Subtracting a Disk Drive
(1) Subtracting Disk Drive (ADD 02-0200)
Work-7 Subtracting the RKAJ /RKAJAT See 2.3 Subtracting RKAJ/RKAJAT on Rack Frame
to the rack frame (ADD 02-0120)
1 : Service personnel must check if a customer has backed up user data. If the customer does not perform the
backup, start the work after getting customers permission.

ADD 02-0090-01
(2) Procedure for subtracting an optional component while the subsystem power off
y For the see Installation 1.7 Power On/Off Procedure (INST 01-0290).
START
Work-1 User data backup Because there is a possibility that user data is
System parameter backup lost, it is recommended to back up user data to
prepare against the risk.(1)

(INST 01-0290)
Work-3 Connection of a service PC and the subsystem See System Parameter 1.1 Procedure for
Work-5 Subsystem setting made See System Parameter Chapter 3. Setting the
by the operation of the service PC RAID/LU/Spare Disk (SYSPR 03-0000) to
(1) Setting of a priced option System Parameter Chapter 6. Setting an
(2) Setting of a Spare Disk Extra-cost Optional Feature (SYSPR 06-0000)
(3) Setting of RAID and an LU
(4) Setting of a Controller
Work-6 Setting the power control mode to Local Setting the Power Control Mode (Local Mode)
Work-7 Subsystem powering off See Installation 1.7.2 Subsystem power off
(INST 01-0310)
Work-8 Remove the cables connected to the subtraction Unit. See Installation 2.6 Connecting Cables
(INST 02-0300)
(INST 03-0610)
Work-9 Subtracting Other Optional Devices See 2.5 Subtracting Other Optional Devices
(ADD 02-0320)
Work-10 Subtracting optional components See 2.4 Subtracting Optional Components
(1) Subtracting a Control Unit (ADD 02-0150)
(2) Subtracting a Disk Drive
(3) Subtracting a Cache Unit
(4) Subtracting Interface Boards
Work-11 Subtracting the RKAJ/RKAJAT See 2.3 Subtracting RKAJ/RKAJAT on Rack Frame
to the rack frame (ADD 02-0120)
A To ADD 02-0110
1 : Service personnel must check if a customer has backed up user data. If the customer does not perform the
backup, start the work after getting customers permission.

ADD 02-0100-01
A From ADD 02-0100
Work-12 Check by means of subsystem restart See Installation 1.7.1 Subsystem power on (INST 01-
0290)
Work-13 Subsystem powering off See Installation 1.7.2 Subsystem power off (INST 01-
0310)
(Local/Remote Mode) (Local/Remote Mode) (INST 01-0320)

ADD 02-0110-01
2.3 Subtracting RKAJ/RKAJAT on Rack Frame

Select a procedure from the following and execute it.
Subtraction Process
No. Model Power status during the subtraction Restriction
section
1 Rackmount Subtraction with the power turned on Impossible(*1)
2 model Subtraction with the power turned off Remove the Disk Drive. Refer to 1.6 Adding
When subtracting RKAJ /RKAJAT the RKAJ to the
with subsystem power turned off, Rack Frame (In the
only the last added RKAJ/RKAJAT case of the
can be removed. connection to the
While configuring RKAJ/RKAJAT, the RKM) (ADD 01-
RKAJ/RKAJAT cannot be removed. 0490)
Turn off the AC Power Unit Switch of the Refer to 1.7 Adding
subsystem. the RKAJ/RKAJAT
Subtract the RKAJ/RKAJAT in the opposite to the Rack Frame
procedure of the operation of adding the (In the case of the
RKAJ/RKAJAT to the rack frame. connection to the
RKM) (ADD 01-
0750)
*1 : RKAJ/RKAJAT cannot be removed while the subsystem power is on. RKAJ/RKAJAT should be removed while
subsystem power is off.
When removing RKAJ/RKAJAT with subsystem power turned on, system may go down since the subsystem
recognizes that a failure occurs in the removed RKAJ/RKAJAT.

ADD 02-0120-01
(1) Procedure for subtracting RKAJ/RKAJAT while the subsystem power is off
A procedure for subtracting the RKAJ/RKAJAT after powering off the subsystem is shown below.
START
Work-1 Backing up user data. When the data stored in an LU, which the RKAJ
/RKAJAT to be removed is defined as, is necessary,
backup them.
Further, it is recommended to backup data of all LUs
to provide against an emergency because user data
may be lost if a wrong operation is done.
Work-2 Preparation of RAID/LU setting Refer to System Parameter 3.1 Preparation of

RAID/LU setting (SYSPR 03-0030).
[Procedure c] Preparing of setting ((1) to (3))
Work-4 Deleting LUs Delete all LUs defined as being belonging to the
RAID group that includes the Disk Drive to be
removed.
Refer to System Parameter 3.3 Setting of LU
(SYSPR 03-0140).
System Parameter 3.3 [Procedure e-A]Preparing
of setting LU (SYSPR 03-0140)
System Parameter 3.3 [Procedure e-D]Deleting
LU (SYSPR 03-0230)
Work-5 Deleting a RAID group Delete a RAID group that includes the Disk
Drive to be removed.
Refer to System Parameter 3.2 RAID group
setting (SYSPR 03-0050).
System Parameter 3.2 [Procedure d-A]RAID
group setting preparation or confirmation
(SYSPR 03-0050)
System Parameter 3.2 [Procedure d-D]Deleting
RAID group (SYSPR 03-0100)
Work-6 Canceling a Spare Disk When the Disk Drive to be removed is assigned to a
Refer to System Parameter 3.4 Setting of Spare
Disk (SYSPR 03-0350).
System Parameter 3.4 [Procedure f-A] reparing
of setting Spare Disk (SYSPR 03-0350)
System Parameter 3.4 [Procedure f-C]Deleting
Spare Disk (SYSPR 03-0380)
(INST 01-0310)
memory in the back-up state (REP 01-0030).
A To ADD 02-0140

ADD 02-0130-01
From ADD 02-0130 A

Remove the cables in the reverse order of the
Work-10 Disconnecting cables installation referring to the following items.
(1) ENC cable (1) ENC cable (Refer to Installation 3.4.10
(2) Power cable Connecting the ENC cables (INST 03-0670).
(2) Power cable (Refer to Installation 3.4.11
Connecting the power cables (INST 03-
0710)
Install the Disk Drive to be added taking care not
Work-11 Detaching the Disk Drive to apply any shock to it.
Refer to 2.4.3 (3) Installing/removing Disk
Drive (ADD 02-0270).
Perform the removal in the reverse order of the

Work-12 Detaching the RKAJ/ RKAJAT installation referring to the following items.
(1) Releasing the RKAJ/RKAJAT from the
(1) Releasing the RKAJ/RKAJAT from the fastening fastening
(2) Putting the RKAJ/ RKAJAT on/off the lifter U7 Rack frame (Refer to Installation 3.4.6
(1) U7 Rack frame (INST 03-0450).)
HP Rack frame (Refer to Installation 3.4.6
(2) HP Rack frame (INST 03-0460).)
Sun StorEdge Rack frame (Refer to
Installation 3.4.6 (3) Sun StorEdge Rack
frame (INST 03-0470).
IBM RS6000 Rack Frame (Refer to
Installation 3.4.6 (4) IBM RS6000 Rack
(2) Putting the RKAJ/ RKAJAT on/off the lifter
Refer to Installation 3.4.5 Mounting
subsystem on rack frame (INST 03-
0430).)
Perform the removal in the reverse order of the installation

Work-13 Removing the rack rails referring to the following items.
(1) Releasing the RKAJ/RKAJAT from the fastening
(Do this work when de-installation of the rack rails is U7 Rack frame (URHT7) (Refer to Installation
instructed.) 3.2.1 (11) Installing the rails (INST 03-0100).)
HP Rack frame (UR7) (Refer to Installation
3.2.2 (2) Installing the rails (INST 03-0160).)
Sun StorEdge Rack frame (UR7) (Refer to
Installation 3.2.3 (2) Installing rails (INST 03-
0230).)
IBM RS6000 Rack Frame (UR7) (Refer to
Installation 3.2.4 (1) When installingDF-F700-
UR7 (INST 03-0260).)
Work-14 Attaching the front bezel See Installation 1.5.3 How to attach/remove Front
Bezel of the Rackmount Model (INST 01-0130)
Work-15 Attaching the decoration panel See Installation 3.4.13 Attaching Decoration
(INST 01-0290)
END

ADD 02-0140-01
2.4 Subtracting Optional Components

2.4.1 Subsystems optional components for subtraction
Condition of subtraction and number of item
Component name Requirements of
Model name Specification Power on
subtraction
operation(*1).)
Control Unit DF-F700-F1JM Array Controller (2port) Impossible Possible
for duplication. 2.4.2 Subtracting a
For RKM
Control Unit (ADD
DF-F700-F1JS Array Controller (1port)
for duplication. 02-0160)
For RKS
Disk Drive(*2) DF-F700-AGF72 3.5-inch Disk Drive Varies depending on Varies depending on)
(including Spare (Disk rotational speed : (71.3 G bytes) the disk array to be the disk array to be
10,000 min-1) subtraction. subtraction.
Disk)
DF-F700-AGF146 3.5-inch Disk Drive 2.4.3 (2)(2-1) 2.4.3 (2)(2-2)
(Disk rotational speed : (143.3 G bytes) Procedure for Procedure for
10,000 min-1) subtracting Disk Drive subtracting Disk Drive
DF-F700-AGF300 3.5-inch Disk Drive while the subsystem while the subsystem
(Disk rotational speed : (287.6 G bytes) power is on power is off (ADD
10,000 min-1)
Procedure for 02-0250)
subtracting Disk Drive
(Disk rotational speed : (245.7 G bytes)
while the subsystem
7,200 min-1)
(RKAJAT) power is on (ADD
DF-F700-ATE400R 3.5-inch Disk Drive 02-0230)
(Disk rotational speed : (393.4 G bytes)
7,200 min-1)
(RKAJAT)
Cache Unit DF-F700-C1GJ Cache memory y For the dual Control Impossible Possible
1,048 M bytes Unit, install the 2.4.4 Subtracting a
Cache Unit of the
Cache Unit (ADD 02-
same capacity in the
Control Unit #0 and 0280)
#1.

ADD 02-0150-01
2.4.2 Subtracting a Control Unit
CAUTION
care.
CAUTION
damage the parts.



Support a Control Unit by touching its

A wristband (Be sure to wear this before

ADD 02-0160-01
(1) Subtracting Process for the Control Unit

Subtraction Process
section
1 RKM Subtraction with the power turned on Impossible
2 Subtraction with the power turned off The case of the dual Controller configuration Refer to 2.4.2 (2)
only Procedure for
subtraction with the
power turned off
(ADD 02-0180)
3 RKS Subtraction with the power turned on Impossible
4 Subtraction with the power turned off The case of the dual Controller configuration Refer to 2.4.2 (2)
only Procedure for
subtraction with the
power turned off
(ADD 02-0180)

ADD 02-0170-01
(2) Procedure for subtraction with the power turned off

(a) Connect the PC to be connected with Storage Navigator Modular and the Control Unit #0 with
a LAN cable. (System Parameter 1.1 Procedure for connecting Storage Navigator Modular
with the subsystem (SYSPR 01-0010))
(b) Set the system starting attribute of the system parameters in order to operate the subsystem
as that having the single controller system. (System Parameter Chapter 4. Setting
Configuration Information (SYSPR 04-0000))
(c) Turn off the main switch.
(d) Make sure that the PWR (POWER) LED (green) on the panel goes out.
the cache backup mode. (Refer to Replacement 1.1.2 Checking cache memory
in the back-up state (REP 01-0030).)
When the cache is in the cache backup state, make the Subtracting after
canceling the mode.
(e) Make sure that the CACHE POWER LED (green) on the Control Unit is off.
NOTE : When the CACHE POWER LED (green) is on, user data which has not written on
the disk exists in the cache memory.
(f) Turn off the AC Power Unit Switch of the Power Unit .
(g) Remove the Fibre Channel cable, LAN, ENC cable, and RS232C cables connected to the
Control Unit#1.
NOTE : In single controller configuration, connect the ENC cable only to the Loop #0
(ENC Unit #0) side. Do not connect it to the Loop #1 (ENC unit #1) side.
When two or more RKAJ are connected, however, both cables in ENC Unit #0
and ENC Unit #1 should be connected for the RKAJ.
(h) Remove the Control Unit#1.

Loosen the screws (right and left) which are fixing the levers of the Control Unit #1, push
down the levers forward, and pull out the Control Unit.
(i) Install the dummy (control Unit).
Insert it into the specified position with the both right and left levers of the dummy pushed
down, raise the levers with the hooks fitting to the cutouts of the subsystem, and tighten the
fixing screw for the lever.
NOTE : y Do not catch a ENC cable, when the Control Unit for the inserted.
y Install the Control Unit #1 with the cover down.
(j) Turn on the AC Power Unit Switch of the Power Unit.

(k) Turn on the main switch.
(l) Make sure that the RDY (READY) LED (green) on the front side of the subsystem comes on.
NOTE : Because the subsystem configuration was changed to the single controller,
register the disk array subsystem as having the single controller configuration
with Storage Navigator Modular. (System Parameter 1.1 Procedure for
connecting Storage Navigator Modular with the subsystem (SYSPR 01-0010))
ADD 02-0180-01
Control Unit #1
Fixing screw
cutout
Control Unit #0
Control Unit (front side) (RKS) CALM LED (red) CACHE POWER LED (green)
Control Unit #1
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0A-0 EALM LED (red) PATH #0 PATH #1

CALM LED (red)
Control Unit (front side) (RKM) CALM LED (red) CACHE POWER LED (green)
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT

CALM LED (red)
Figure 2.4.1 Subtracting Controller

ADD 02-0190-01
2.4.3 Subtracting a Disk Drive

A procedure for subtracting the Disk Drive varies depending on a location of the Disk Drive and
a condition (whether the subsystem power is on or off).
Take care to use a procedure appropriate for the purpose because a use of an inappropriate
procedure may cause an accident such as a loss of user data.
Table 2.4.1 Kinds of Disk Drive Subtraction

Subtraction
Unit of Removal of the Disk Drive(s) which is not used
No. addition/ Component to be added/ subtracted (from which a setting of a RAID group has been deleted)
subtraction Power on
Power off
(A host is in operation (*1).)
1 Disk Drive RKM/RKS Impossible (*2) Impossible(*2)
#0 to 4

2 RKM/RKS Possible Possible

#5 to14 Refer to 2.4.3 (2-1) Procedure Refer to 2.4.3 (2-2) Procedure
for subtracting Disk Drive while for subtracting Disk Drive while
the subsystem power is on the subsystem power is off
(ADD 02-0230) (ADD 02-0250)
3 RKAJ Possible(*3) Impossible(*3)
#0 to 3 Refer to 2.4.3 (2-1) Procedure Refer to 2.4.3 (2-2) Procedure
(ADD 02-0230) (ADD 02-0250)
4 RKAJ Possible Possible
(ADD 02-0230) (ADD 02-0250)
5 RKAJAT Possible(*2) Possible(*2)
(ADD 02-0230) (ADD 02-0250)
6 RKAJAT Possible Possible
(ADD 02-0230) (ADD 02-0250)
*2 : The Disk Drives #0 to #4 of the RKM/RKS cannot be decreased because the microprogram is stored in them.
*3: Since the Disk Drives #0 to #3 of the RKAJ/RKAJAT are used for monitoring the RKAJ/RKAJAT , be sure to
decrease them so that either set of the two Disk Drives, #0 and #1 or #2 and #3, is left.
All of the Disk Drives #0 to #3 cannot be removed from the RKAJ/RKAJAT at the middle of a configuration.
When you want to remove all of the Disk Drives #0 to #3 of the RKAJ/RKAJAT at the end of a configuration,
remove them together with the RKAJ/RKAJAT while the subsystem power is off.

ADD 02-0200-01
(1) Before starting subtraction of Disk Drive
CAUTION
damage the parts.
y Disk Drives are precision components.
y When you remove a Disk Drive, support its metal part with your hand that has the

Disk Drive

the frame of subsystem (front
face)

Support a Disk Drive by touching its

ADD 02-0210-01

The mounting position number of the disk drive is decided by the combination of the disk
drive number set to the device number (device ID).

RKAJ/RKAJAT.
The disk drive number is #0 to #14 from the left sequentially seen sideways (for the floor

Device ID setting
RKAJAT RKAJAT
Device ID is set as
#01.
RKAJ RKAJ
RKM RKM
Disk Drive
RKAJAT
RKAJ
RKM/RKS

ADD 02-0220-01
(2) Procedure for subtracting Disk Drive

y A procedure for subtracting the Disk Drive installed in the RKM/RKS/RKAJ /RKAJAT is shown
below.
y Any of the Disk Drives #0 to #4 of the RKM/RKS cannot be subtracted.
y To remove all of the Disk Drives #0 and #1 of the RKAJ/RKAJAT, it is required to remove them
together with the RKAJ/RKAJAT in which they are installed.
y It is recommended to backup data of all LUs to provide against an emergency because user
(2-1) Procedure for subtracting Disk Drive while the subsystem power is on
A procedure for subtracting the Disk Drive without shutting down the subsystem is shown
below.
START
Work-1 Backing up user data. When the data stored in an LU, which the Disk
Drive to be removed is defined as, is
necessary, backup them.
Further, it is recommended to backup data
of all LUs to provide against an
emergency because user data may be
lost if a wrong operation is done.

Work-4 Deleting LUs Delete all LUs defined as being belonging to

the RAID group that includes the Disk Drive to
be removed.
Refer to System Parameter 3.3 Setting of
LU (SYSPR 03-0140).
System Parameter 3.3 [Procedure e-A]
Preparing of setting LU (SYSPR 03-0140)
System Parameter 3.3 [Procedure e-D]
Deleting LU (SYSPR 03-0230)
Work-5 Deleting a RAID group Delete a RAID group that includes the Disk
Drive to be removed.
A To ADD 02-0240 System Parameter 3.2 [Procedure d-A]
RAID group setting preparation or
confirmation (SYSPR 03-0050)
System Parameter 3.2 [Procedure d-D]
Deleting RAID group (SYSPR 03-0100)

ADD 02-0230-01
From ADD 02-0230

A
Work-6 Canceling a Spare Disk When the Disk Drive to be removed is assigned
to a Spare Disk, cancel the assignment.
Spare Disk (SYSPR 03-0350).
System Parameter 3.4 [Procedure f-A]
Preparing of setting Spare Disk (SYSPR 03-
0350)
System Parameter 3.4 [Procedure f-C]
Deleting Spare Disk (SYSPR 03-0380)
Work-7 Detaching the front bezel See Installation 1.5.3 How to attach/remove
Front Bezel of the Rackmount Model (INST 01-
0130)
Work-8 Detaching the Disk Drive Install the Disk Drive to be added taking care
Perform Work-7 soon after this work is completed. not to apply any shock to it. Refer to 2.4.3
(3) Installing/removing Disk Drive (ADD 02-
0270).
Work-9 Install the dummy (Disk Drive). See 2.4.3 (3) Installing/removing Disk Drive
(ADD 02-0270).
Work-10 Attaching the front bezel See Installation 1.5.3 How to attach/remove
Front Bezel of the Rackmount Model (INST
01-0130)
END

ADD 02-0240-01
(2-2) Procedure for subtracting Disk Drive while the subsystem power is off
A procedure for subtracting the Disk Drive after powering off the subsystem is shown below.
START
Work-1 Backing up user data. When the data stored in an LU, which the Disk
Drive to be removed is defined as, is
necessary, backup them.
Further, it is recommended to backup data
of all LUs to provide against an
emergency because user data may be lost
Work-4 Deleting LUs Delete all LUs defined as being belonging to the
RAID group that includes the Disk Drive to be
removed.
Refer to System Parameter 3.3 Setting of LU
(SYSPR 03-0140).
System Parameter 3.3 [Procedure e-D]
Deleting LU (SYSPR 03-0230)
Work-5 Deleting a RAID group Delete a RAID group that includes the Disk Drive
to be removed.
System Parameter 3.2 [Procedure d-A]
RAID group setting preparation or confirmation
(SYSPR 03-0050)
System Parameter 3.2 [Procedure d-D]
Deleting RAID group (SYSPR 03-0100)
When the Disk Drive to be removed is assigned

Work-6 Canceling a Spare Disk to a Spare Disk, cancel the assignment.
Spare Disk (SYSPR 03-0350).
System Parameter 3.4 [Procedure f-A]
Preparing of setting Spare Disk (SYSPR 03-
0350)
System Parameter 3.4 [Procedure f-C]
Deleting Spare Disk (SYSPR 03-0380)
(INST 01-0310)
A To ADD 02-0260 memory in the back-up state (REP 01-0030).

ADD 02-0250-01
From ADD 02-0250

A
See Installation 1.5.3 How to attach/remove

Front Bezel of the Rackmount Model (INST
01-0130)
Work-10 Detaching the front bezel Install the Disk Drive to be added taking care
not to apply any shock to it. Refer to 2.4.3 (3)
Installing/removing Disk Drive (ADD 02-0270).
Work-11 Attaching the front bezel See Installation 1.5.3 How to

attach/remove Front Bezel of the
Rackmount Model (INST 01-0130)
Work-12 Subsystem power on See Installation1.7.1 Subsystem power on
(INST 01-0290)
END

ADD 02-0260-01
(3) Installing/removing Disk Drive

When installing or removing a Disk Drive in the work for decreasing the number of Disk Drives,
follow the procedure explained below.
Perform the following operations (a) and (b) for each of the slots, where the Disk Drive is to be
replaced, one by one.
tilt the handle toward you, and then remove the Disk Drive by pulling it out taking care not to
apply a shock to it. (see Figure 2.4.3).
When using the removed Disk Drive for the purpose of addition to another disk array unit,
keep it in custody with its handle returned to its original state (locked by the stopper) taking
care not to apply a shock to it.
Address label
Safekeeping of screw
Disk Drive
Stopper Disk Drive

Handle
Safekeeping box
Figure 2.4.3 Remove the Disk Drive
(b) Install the dummy (Disk Drive) in the slot from which the Disk Drive has been removed.
Be sure to insert the dummy (Disk Drive) in the vacant slot because it is necessary to regulate
a cooling air flow inside the disk array.
NOTE : Exteriors of the Disk Drive and dummy (Disk Drive) are similar to each other.
Be careful not to install or remove a wrong one.
Disk Drive :A label bearing the model name and revision number is affixed to
the portion near the handle.
Dummy (Disk Drive) :No label is affixed to the portion near the handle.

ADD 02-0270-01
2.4.4 Subtracting a Cache Unit
CAUTION
care.
CAUTION
damage the parts.

Control Unit

metal part (metal plate) with your fingers A wrist strap (Be sure to wear this before

ADD 02-0280-01
<Working Procedure>
Note: When the subsystem power has already been turned off, make sure that the
cache memory is not being backed up. (Refer to Replacement 1.1.2 Checking
cache memory in the back-up state (REP 01-0030).)
If the cache memory is being backed up, execute Step (b) and the following
steps after canceling the backing up.
(2) Turn off the AC Power Unit Switch of the both Power Units.
(3) Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down
(4) Remove the all cables connected to the Control Unit.
CAUTION
Touching heat sinks or ICs may cause getting burned. Be sure to handle with care.
(5) Remove the Control Unit by pulling it out toward you.

(7) Remove the Cache Unit.
NOTE : Place the removed Cache Unit in the place where anti-static measures are
taken.
(8) Install the Cache Unit in the Control Unit.

ADD 02-0290-01
(10) Insert it into the specified position with the both right and left levers of the Control Unit
If the Control Unit is caught by something when it is inserted, do not push it in forcibly. Retry
the insertion from the beginning. If forced, pins might be broken.
NOTE : y Do not catch a ENC cable, when the Control Unit for the inserted.
y The installation direction is different in the Control Unit # 0 and # 1. Install
(11) Connect the removed all cables to the Control Unit.
(12) Turn on the AC Power Unit Switch of the both Power Units .
(14) Make sure that the WARNING LED (orange) on the Front Bezel is off(1).
(15) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on the
Front Bezel may blink at high speed (up to 30/50 minutes).
1 : When the WARNING LED is blinking, refer to the WEB or collect the trace, and then check if the LED goes out.

ADD 02-0300-01
Control Unit #0
Cover
Control Unit #1
Fixing screw
Lever
Removal :
Fixing screw
Socket by hand.
Cut Installation :
cutout inside the slot both end by hand.
slot #1 slot #0
LASER PRODUCT
CLASS 1
LASER KLASSE 1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT

CALM LED (red)
Figure 2.4.4 Replacing Cache Unit (RKM)

ADD 02-0310-01
2.5 Subtracting Other Optional Devices

2.5.1 Other optional subtraction devices
Condition of subtraction and number of item

Component Requirements of subtraction
Model name Specification Power on
name
operation(*2).)
PDB (UPDU7) DF-F700-UPDU7 For U7 Additional PDB for U7 rack Possible Possible
frame Refer to 2.5.2 Refer to 2.5.2
Subtracting a PDB Subtracting a PDB
(UPDU7) (UPDU7)
(ADD 02-0330) (ADD 02-0330)

ADD 02-0320-01
2.5.2 Subtracting a PDB (UPDU7)

(1) Subtracting Process for the PDB (UPDU7)
Subtraction Process
section
1 Rackmount Subtraction with the power turned on y This is the dedicated rack for the U4/U7 rack Refer to 2.5.2 (2)
model frame. Procedure for
2 Subtraction with the power turned off y Only the PDB whose all the outlets for subtraction (ADD
output to which the power cable plugs are 02-0330)
not connected can be subtracted.
(2) Procedure for subtraction

(a) Make sure that the power cable plugs are not connected to all the outlets for output on the
PDB to be subtracted.
(b) Disconnect the power cable, which is connected to the PDB to be de-installed to supply
power to it, by pulling its power feeder plug for safety.
(c) Remove the PDB to be subtracted from the rack frame.
Remove the PDB in the opposite procedure of the installing operation referring to 1.5.2
Mounting a PDB (UPDU7) (ADD 01-0460).
Keep the subtracted components as the occasion demands.

ADD 02-0330-01
Chapter 3. Relocation/Removal Work

3.1 Before Starting Relocation/Removal Work
Take notice of the following when performing a installation work for the subsystem.
When moving or removing a subsystem, take care of the following matters.
(1) Note on installing and removing parts

Generally, each part is equipped with high-precision components. Remove and install the part
gently so as not to give it any shock.
CAUTION
damage the parts.
When installing a Disk Drive, Control Unit or ENC Unit/SENC Unit, hold it with your hand
Support a Disk Drive by touching its metal

ENC Unit (RKAJ)/
Disk Drive SENC Unit (RKAJAT)

the frame of subsystem (rear face) starting maintenance.)

ADD 03-0000-01
(2) Note on cable routing

(a) Handling of cables on the floor
Protect cables which cannot be accommodated by the subsystem and thus laid on the floor
or cables which cross a passage with cable protecting, etc.
Do not make inter-device cables apart from the floor but lay them on the floor.
(b) Handling of under-floor cables when the subsystem is installed on the free access floor.
Give excess lengths to cables routed under the floor so that they can easily be laid on the
slab. Do not make them to be hung dangling.
(c) How to route cables
Give adequate margin of length to cables to withstand earthquakes, etc.
Route cables giving them excess lengths lest they should disturb replacement of part to be
done for maintenance.
Make power cable and power cable apart each other. When they have to be positioned
close each other, do not make them run in parallel but make them cross each other.
When using cable protecting duct, be careful not to damage or break cables by catching
them.
(d) Be sure to insert or pull out a cable connector holding it with your hand. If you pull a cable,
a trouble may be caused.
(e) When bending the FC I/F cable and RC (ENC) cable to connect it, give it a bend with a long
radius (not less than 30 mm) so as not to apply the cable and the connector excessive
stresses.

(4) Note on completing a maintenance work

Close all the external covers when a maintenance work is completed.
It is required to make all the external covers closed to operate the subsystem properly.
(Be sure to close all the external covers during operation because it is indispensable to
maintain the performance of the subsystem including prevention of adverse effects caused by
radio frequency energy.)
(5) Note on moving the Floor Model

The allowable maximum inclination angle at the end of the slope for the Floor Model is eight
degrees.
When moving the Floor Model through a slope steeper than the above or across a level
difference of the floor, use a gangway, etc. to make the slope easier.
Floor model
Slope easier
8degrees

ADD 03-0010-01
3.2 Procedure for Relocating or Removing Floor Model

(1) Procedure for relocation from where the subsystem is currently installed
Before performing the relocation from where the subsystem is currently installed, make sure of
work items to be done shown below.
Work-1 Removing rear cover See Installation 1.5.2 How to attach/remove

Rear Cover of Floor Model (INST 01-0120)
(INST 01-0310)
Work-3 UPS power off See UPS MANUAL
Work-4 Check by label of interface cable This work is not necessary for the removal
operation.
When moving it, be sure to label the disk array
subsystem before disconnecting the cable, and
install it so as to make the same configuration as
before the relocation.
Work-5 Disconnecting power cables See 3.2.1 Disconnecting power cable

(ADD 03-0040)
Work-6 Disconnecting interface cables See 3.2.2 Disconnecting interface cables
(ADD 03-0050)
Work-7 Attach the rear cover See Installation 1.5.2 How to attach/remove
Rear Cover of Floor Model (INST 01-0120)
Work-8 Removing skirt See Installation 2.7 Installing Skirt (INST 02-
0350)
Work-9 Packing subsystem See Export Packing Specifications

ADD 03-0020-01
(2) Procedure for installation at a place from where the subsystem is moved
Before performing installation at a place where the subsystem is moved to, make sure of work
items to be done shown below.
Work-1 Unpacking See Installation 2.2 Unpacking the Subsystem

(INST 02-0020)
Work-2 Removing rear cover See Installation 1.5.2 How to attach/remove Rear
Cover of Floor Model (INST 01-0120)
Work-3 Installing the subsystem See Installation 2.4.2 Installing the subsystem
(INST 02-0150)
Work-4 Installing UPS See UPS MANUAL
Work-5 Connecting power cables See Installation 2.6.3 Connecting power cables
(INST 02-0340)
Work-6 Connecting interface cables See Installation 2.6.1 Connecting Fibre Channel
interface cables (INST 02-0300)
Work-7 Attach the rear cover See Installation 1.5.2 How to attach/remove Rear
Cover of Floor Model (INST 01-0120)
Work-8 Installing skirt See Installation 2.7 Installing Skirt (INST 02-0350)

ADD 03-0030-01
3.2.1 Disconnecting power cable

(1) Disconnecting the power cable of Power Unit
CAUTION
Pull out the Power Unit a little, and then perform the cable removal again.
(a) Make sure that AC power input switches (breakers) on the Power Unit have been all turned
off.
(b) Remove the power cable to the power outlet.
(c) Remove the power cables.
Power cable
Power cable
Figure 3.2.1 Disconnecting Power Cable

ADD 03-0040-01
3.2.2 Disconnecting interface cables
Pull out the parts a little, and then perform the cable removal again.
(1) Remove the interface cable to the Control Unit.

(2) Remove the interface cable to the Clamp (Fibre).
Tx
Interface cable
Rx
Interface cable Clamp (Fibre)
Figure 3.2.2 Disconnecting Interface Cable

ADD 03-0050-01
3.3 Procedure for Relocating or Removing Rackmount Model

(1) When moving the subsystem together with a rack frame
(a) Procedure for removal from where the subsystem is currently installed
Before performing the removal from where the subsystem is currently installed, make sure of
(INST 01-0310)
Work-2 Check by label of interface cable This work is not necessary for the removal operation.
subsystem before disconnecting the cable, and install it
so as to make the same configuration as before the
relocation.
Work-3 Disconnecting power cables (for PDB) See 3.3.1 Disconnecting the power cables
(ADD 03-0090)
(ADD 03-0110)
(b) Procedure for installation at a place from where the subsystem is moved
Work-1 Unpacking and installing Rack Frame See Installation 3.2 Unpacking and Installing
Work-2 Connecting power cables (for PDB) See Installation 3.4.12 Connecting the power
cables (Rack frame PDB) (INST 03-0730)
Work-3 Connecting interface cables See Installation 3.4.9 Connecting the Fibre
Channel interface cable (INST 03-0640)

ADD 03-0060-01
(2) When moving the subsystem together with removing of parts

(a) Procedure for removal from where the subsystem is currently installed
Before performing the removal from where the subsystem is currently installed, make sure of
(INST 01-0310)
Work-2 UPS power off See UPS MANUAL
Work-3 Check by label of interface cable This work is not necessary for the removal
operation.
subsystem before disconnecting the cable, and
install it so as to make the same configuration as
before the relocation.
Work-4 Disconnecting power cables See 3.3.1 Disconnecting the power cables
(ADD 03-0090)
Work-5 Disconnecting power cables (for PDB) See 3.3.2 Disconnecting the power cable (for
supplying power to Rack frame) (ADD 03-0100)
(ADD 03-0110)
Work-7 Removing components See Installation 3.4.2 Removing Components

(INST 03-0330)

ADD 03-0070-01
(b) Procedure for installation at a place from where the subsystem is moved
Work-1 Unpacking rack frame See Installation 3.2 Unpacking and Installing Rack
Frame (INST 03-0020)
Work-2 Unpacking the Floor Model See Installation 3.3 Unpacking the Subsystems
(INST 03-0310)
Work-4 Installing UPS See UPS MANUAL
See Installation 3.4.3 Mounting on Rack Frame

Work-5 Mounting on Rack Frame
(INST 03-0400)

(INST 03-0490)
Work-7 Connecting power cables See Installation 3.4.11 Connecting the power
cables (INST 03-0710)
Work-8 Connecting power cables (for PDB) See Installation 3.4.12 Connecting the power
cables (Rack frame PDB) (INST 03-0730)
Work-9 Setting the UPS See UPS MANUAL
Work-10 Connecting interface cables See Installation 3.4.9 Connecting the Fibre Channel
interface cable (INST 03-0640)
Work-11 Attaching Decoration panel See Installation 3.4.13 Attaching Decoration

ADD 03-0080-01
3.3.1 Disconnecting the power cables

(1) Disconnecting the power cable of Power Unit
CAUTION
(a) Disconnect the power cable connected to the PDB.

(b) In the case of the RKAJ/RKAJAT, pass Repeat Binders through the cleats removed to the right
and left stoppers and fasten the power cable with the Binders.
(c) Disconnect the power cable connected to the Power Unit.
PDB #00
Cleat
Repeat binder
Stopper
PDB #10
Power cable
cable cramp
J13
J12
Power supply
connector
Power cable
J11
J10
Figure 3.3.1 Disconnecting Power Cables

ADD 03-0090-01
3.3.2 Disconnecting the power cable (for supplying power to Rack frame)
(1) Open the rear door. (See Installation 1.5.4 How to open/close the Rear Door of U7 rack
(2) Remove the cable holders from the rack frame by removing the hexagon socket head. (three
places)
(3) Disconnecting the power cable to the consent.
(4) Disconnecting the power cable to the Power input connector.
(5) Return all the removed cable holders as they were before.
(6) Close the rear door.
Additional PDB
Additional PDB
Rear door
PDB #01
PDB #11
Power supplying switch

Power cable
Power cable
PDB #10
PDB #00
Power cable
Power cable
PDB #00/01 side
Hexagon socket head bolt (M430)
Power cable
Cable clamp
Cable holder Power cable

(Additional for PDB)
PDB #10/11 side
Figure 3.3.2 Disconnecting Power Cables

ADD 03-0100-01
3.3.3 Disconnecting interface cables
(1) Disconnecting the Fibre Channel interface cable to the clamp

(2) Disconnect the Fibre Channel interface cable connected to the Control Unit.
RKM/RKS
U7 rack frame
Tx Rx
Control Unit #1
Control Unit #0
Fibre cables
Fibre cables
Clamp (Fibre)
Figure 3.3.2 Disconnecting Interface Cable (RKM/RKS)

ADD 03-0110-01
FE-95DF750-00
Troubleshooting
Chapter 1. Flowchart for troubleshooting ........................................................................ TRBL 01-0000
Chapter 2. Before Maintenance Work............................................................................. TRBL 02-0000
Chapter 3. Before Starting WEB Connection .................................................................. TRBL 03-0000
Chapter 4. Trouble Analysis by WEB connection............................................................ TRBL 04-0000
Regarding Fibre Channel Failure............................. TRBL 05-0000
Chapter 6. Details of Recovery Methods ........................................................................ TRBL 06-0000
Chapter 7. Collecting Error Information........................................................................... TRBL 07-0000
Chapter 8. Trouble Analysis by LED Indication............................................................... TRBL 08-0000
Chapter 9. Data Collection when a Failure Occurs in Program Product (P.P.)............... TRBL 09-0000
Chapter 10. Trouble Analysis by Failure Monitoring Function .......................................... TRBL 10-0000

TRBL 00-0000-01

TRBL 00-0010-01
Chapter 1. Flowchart for troubleshooting

This chapter contains information on troubleshooting to be used when failures occur in the
unit. Illustrations in this section show cases of the rackmount model. They are the same for
the floor model.
The following is the flow of troubleshooting to be used when a failure occurs in the unit.
Failure call accepting NOTE : Order of Components replacement when two or more failures
occurred
When failures occurred in two or more components, replace the
When a failure is detected by SNMP Agent Support corresponding components in the following order.
Function. Be sure to follow this order, or it may repeat the failure.
Refer to 10.1 Trouble Analysis by SNMP Agent Support When failures occur in the two or more RKAJ(s)/RKAJAT(s),
Function (TRBL 10-0000). replace the RKAJ/RKAJAT by N of the subsystem ID# xN is
small.
When a failure is detected by In the case where the RKAJATs are installed, perform the
Storage Navigator Modular. replacement taking notice of the subsystem ID number.
Refer to 10.2 Trouble Analysis by Storage Navigator When failures occurs in two or more RKAJs, replace the RKAJs,
Modular (TRBL 10-0080). in ascending order of the device ID numbers. Perform the
following part replacement after verifying that the failed part has
been recovered normally (for a Disk Drive, after verifying that a
When a P.P. failure is detected. recovery has been started).
Refer to Chapter 9. Data Collection when a Failure Occurs 1. Backup Battery Unit (RKM/RKS)
in Program Product (P.P.) (TRBL 09-0000). 2. Power Unit (RKM/RKS)
3. Power Unit (RKAJ), Power Unit (RKAJAT)
Refer to ASSIST-PC Manual when a failure of the failure 4. Fan Assembly (RKM/RKS)
monitoring program was detected. 5. Control Unit (RKM/RKS)
6. Interface Board (RKM)
7. SENC Unit (RKAJAT)
When the sense code concerning the subsystem was
8. Disk Drive (RKM/RKS)
reported to the log in the host computer.
9. ENC Unit (RKM/RKS)
Refer Message Chapter 9. Failure Analysis by Sense Data
10. Host Connector (RKM/RKS)
(MSG 09-0000).
When an LU subordinate to the specific path of the disk

array subsystem cannot be recognized by the host
computer.
Refer to Chapter 5. Procedure for Investigating Disk Array
Subsystem Regarding Fibre Channel Failure (TRBL 05-
0000)
When an error message is displayed during
an operation of the Web.
Refer to Message Chapter 7. Web Error Messages (MSG
07-0000).
When an error message is displayed during an operation of

the Storage Navigator Modular.
Refer to Message Chapter 8. Storage Navigator Modular
Error Messages (MSG 08-0000).
y When a failure is detected from the subsystem (through a

beep of a buzzer or a lighting of the ALARM LED, etc.)
y When a host computer detects a subsystem failure
y When a subsystem failure is detected from WEB
follow the following flow.
A To TRBL 01-0010

TRBL 01-0000-01
From TRBL 01-0000 A
Can the WEB connect to the

subsystem through a LAN? No
(maintenance PC and LAN-cross-
Trouble analysis by LED display
Yes Refer to Chapter 8. Trouble Analysis by LED Indication
(TRBL 08-0000).
No Is the failure isolation by means of

LED completed?
Preparing the WEB based Trouble analysis Yes
Refer to Chapter 3. Before Starting WEB Connection
(TRBL 03-0000).
Trouble analysis by WEB connection Make the WEB connected to the

Refer to Chapter 4. Trouble Analysis by WEB Connection subsystem through a LAN.
(TRBL 04-0000).
Trouble analysis by
the Message based Analysis
Refer to Message Chapter 1. Before Starting Trouble
Analysis (MSG 01-0000).
Is the Failure Isolation complete by the Yes

Message based Analysis?
No
Detailed recovery procedure corresponding to each failure
phenomenon
Refer to Chapter 6. Details of Recovery Methods (TRBL
06-0000).
Is the Failure Isolation complete by WEB Yes

based Analysis?
No
Collecting Failure Information by Trace/Dump
Refer to Chapter 7. Collecting Error Information (TRBL 07-
0000).
Analyzing the Trace/Dump

Request the Technical Support Center to analyze the failure
and take a measure.
Recovery work from a failure

Refer to Replacement Chapter 2. Parts Replacement
(REP 02-0000).
END

TRBL 01-0010-01
Chapter 2. Before Maintenance Work

2.1 Precautions

TRBL 02-0000-01
2.2 Confirming and setting RTC (Real Time Clock)

RTC (Real Time Clock) is a built-in clock in the Controller. It is used to record the time
information of messages and trace/dump when an error occurred. Even if the RTC is out of
order, the host system may not be affected. However, the time information of messages and
trace/dump is not correct. Accordingly, the failure analysis with synchronizing to the host
may be affected.
In the following cases, check the RTC and reset it if it varies.
When the controller was replaced while the subsystem power was turned off.
When there is something wrong with the time on messages, traces and dump.
Set the time on the Japanese Standard Time basis
If you wish to use Storage Navigator Modular to set the RTC, please refer to the System
Parameter 1.1 Procedure for connecting Storage Navigator Modular with the subsystem
(SYSPR 01-0010).
The setting of RTC can be made without rebooting the array unit.
(1) In the main window, position the focus ([ ]) on the icon [ ] of the array subsystem
register by pressing the [Tab] key, and then press the Ctrl, Shift, and E keys at the same time.
Maintenance Mode is displayed in the Active Mode field at the top right on the Main screen, and
the Storage Navigator Modular operates in the maintenance mode.
(2) Click the DF700 icon for setting parameters in the main window.

TRBL 02-0010-01
(3) Click the icon of an array unit on the Main window, and then select the [File] [Open]. Or,
click the [ : Open]button in the tool bar.
Settings] button.

TRBL 02-0020-01
(5) Click the [RTC] tab.
(6) Set the RTC.

Setting : Select Manual or Auto.
Manual : Sets the date and time.
Auto : Sets the time of the PC or Server/Workstation executing the Storage Navigator
Modular.
Date : Displays date.
Time : Displays time.
(7) Click the [Apply] button.
(9) A message appears, stating that the setting is complete. Click the [OK] button.

TRBL 02-0030-01
2.3 Indications and their Functions
(1) Indication positions and their functions of RKM
1-b
1-c
1-d
Front bezel 1-a 1-e Indicating section (STATUS panel)
2-d 2-c 2-b 2-a 2-e 2-f
1-h 7 8 9 10 11 12 13 14
1-f
1-g Interface Board Fan Assembly
0 14
Front view Rear view
Backup Battery Unit Panel Unit Fan Assembly Control Unit Power Unit Interface board
3-b 6-d 6-c
3-c
3-a
6-a 6-b
5-a
8-c 8-d 8-e 8-j

8-i
4-d
8-h
4-a 4-b 4-c 8-a 8-b 8-f 8-g
7-l-2 7-l-3 7-m-2 7-m-3
7-a 7-c 7-f 7-h
LASER KLASSE 1
CLASS 1
LASER PRODUCT
7-p 7-l-1 7-m-1 7-o 7-n 7-b 7-d 7-e 7-g 7-i 7-j 7-k
Figure 2.3.1 Indication Locations of Functional Components

TRBL 02-0040-01
Table 2.3.1 Functions of Indications

No. Section Name Classification Color Function
1-a Front Bezel KEY Key Locks the front bezel.
1-b POWER LED Green Indicates that the power supply is supplied to the subsystem.
1-c READY LED Green Lighting
Indicates that the subsystem can be operated.
Blinking
Indicates that the offline download process is completed.
1-d WARNING LED Orange Lighting
Indicates that a failure, which allows the subsystem to operate,
occurred.
Blinking
High-speed blinking :
Indicates that a failure which does not stop operation occurred
in unit (It must be detected with WEB).
Low-speed blinking :
Indicates that a latest revision maintenance function of flash
program is executed.
1-e ALARM LED Red Lighting
Indicates that a failure, which does not allow the subsystem to
operate, occurred.
Blinking
Indicates that a serious failure occurred while power on.
1-f Main switch (OFF) Switch OFF : Presses off the power.
1-g Main switch (ON) Switch ON : Presses on the power.
1-h BUZZER OFF SW Switch Pressing of this switch while the buzzer sounds stops the beep. (*1)
2-a STATUS Panel PWR (POWER) LED Green Indicates that the power supply is supplied to the subsystem.
2-b (RKM) RDY (READY) LED Green Lighting
Blinking
Indicates that the ENC/SENC firmware is being downloaded.
Indicates that the download processing with the power turned
off is completed.
2-c WARN LED Orange Lighting
(WARNING) Indicates that a failure, which allows the subsystem to operate,
occurred.
Blinking
occurred. (It must be detected with WEB).
2-d ALARM LED Red Lighting
Indicates that a failure occurred which makes the subsystem
unable to operate.
Blinking
2-e ALARM LED Red Indicates that a failure which makes the unable to operate occurred.
*1 : In case of a serious failure of hardware (Electrical surges of both power supplies and so on), the buzzer does not
stop even if you push the button to call attention. In this case, perform the appropriate recovery procedure
depending on each cause.

TRBL 02-0050-01

2-f ACTIVE LED Green No. LED status Meaning
1 Blinking Shows that the Disk Drive is being accessed.
2 On Spin up state.
3 Off During seek on.
3-a Panel Unit Main switch Switch Turns on/off the power.
: Power on
: Power off
3-b BUZZER OFF SW Switch Pressing of this switch while the buzzer sounds stops the beep. (*1)
3-c Mode switch Switch Sets the local/remote mode by the combination of turning on and off
of the four mode switches.
4-a Backup Battery Unit ALARM LED Red Lights when the Backup Battery unit is in trouble.
The battery is not installed.
The BATTERY switch is turned off
Battery voltage is abnormal.
Battery temperature abnormal.
4-b CHARGE LED Orange Charging Battery (On)
4-c READY LED Green Shows the state of the battery.
On : Battery is in the normal condition.
Blinking : Charged up when start-up
Off : Abnormal
The battery switch is turned off.
Temperature of the battery is abnormal.
4-d BATTERY Switch Switch Turns on/off of the battery power.
When this switch is set to the off, the WARNING LED comes on
and the buzzer sounds.
ON: Power on
OFF : Power off
5-a Fan Assembly ALM LED Red Shows the state of the Fan Assembly
On : Abnormal
Off : Normal
6-a Power Unit AC Power Unit Switch Switch Controls the power applied to the subsystem.
| : Power on
{: Power off
6-b Receptor (J1) Connector Connector on the subsystem side to connect the power cable.
6-c READY LED Green Shows the operation state of the Power Unit.
On : Normal operation
Off : Abnormal operation or out of operation
6-d ALARM LED Red Lights when the Power Unit is in trouble.

TRBL 02-0060-01

7-a Control Unit P1 LED Green Indicates that the link status of the FC-AL (loop 1 side) is normal.
7-b P0 LED Green Indicates that the link status of the FC-AL (loop 0 side) is normal.
7-c CHK (CHECK) LED Red Shows error factors by means of a number of times of blinking.
Once : Drive +5 V voltage is abnormal.
Twice : Drive +12 V voltage is abnormal.
Five times : Battery is abnormal.
Six times : Voltage on the Controller is abnormal.
(Reset of the Controller is not canceled.)
Seven times : BS12V voltage is abnormal.
Nine times : Fans are abnormal.
The following blinking is fast because ENC microprogram detects
CUDG error.
Once : SRAM error.
Twice : ENC hard error.
Three times : Microprogram error in flash memory.
Not blinking : BOOT section error of ENC microprogram,
RAM error, or ENC hard configuration error.
7-d EALM LED Red Indicates error factors by means of lighting or blinking.
Lighting
Indicates that a failure, which makes the ENC in the Control Unit
unable to operate, occurred.
Blinking
Normal blinking (CHK LED is on) :
An exceptional process error detected by the ENC
microprogram.
High-speed blinking (CHK LED is on) :
microprogram. (stack over)
Normal blinking (CHK LED is off) :
Indicates that FLASH write is performed during the ENC
microprogram download.
(It is not in the abnormal status.)
7-e RST SW Switch Used to perform a memory dump.
7-f CACHE POWER LED Green You can check whether the Cache memory is being backed up
through indication of this LED.
This LED is effective when the AC Power Unit Switch is turned on
On : Indicates that the cache is being backed up. (The power is
supplied from the battery to the Cache memory.)
Off : The Cache memory is not backed up.
7-g RST LED Orange Indicates that the Controller is being reset.
During power-on reset
During reset for doing a dump
During reset for a reboot at the time of a microprogram down
load
7-h CHKSTP LED Red A failure occurred at Controller and it became not operational.
7-i CALM LED Red Indicates that a failure which makes in the Controller unable to
operate occurred in it.
7-j PATH0 Connector Connection connector for ENC cable (PATH 0 side).
7-k PATH1 Connector Connection connector for ENC cable (PATH 1 side).
7-l-1 LAN0 LAN0 Connector Connects the LAN0 cable. (For maintenance)
7-l-2 ACT LED Orange Indicates that data is being transferred via a LAN 0.
7-l-2 LINK LED Green Indicates that the link status of the LAN 0 is normal.

TRBL 02-0070-01

7m-1 Control Unit LAN1 LAN1 Connector Connects the LAN1 cable. (For User Management)
7-m-2 ACT LED Orange Indicates that data is being transferred via a LAN 1.
7-m-3 LINK LED Green Indicates that the link status of the LAN 1 is normal.
7-n Connector for Connector Used to connect the Remote adapter.
connecting the
Remote adapter (J8)
7-o Connector for Connector Used to connect the UPS for the DF700.
connecting the UPS
interlocking cable (J5)
7-p Jumper Connector Connector There are two cases where the numbers of pins are 8 and 20
respectively depending on the revision of the PCB. (The switch
has nothing to do with maintenance because it is used for
evaluation.)
8-a Interface Board Port 0A-0/ Tx Connector Connector on the signal output side to connect the Fibre Channel
Port 1A-0 interface cable in the Port 0A-0/Port 1A-0 side.
8-b Rx Connector Connector on the signal input side to connect the Fibre Channel
interface cable in the Port 0A-0/Port 1A-0 side.
8-c GP1 LED Green Shows status of the standard Interface Board mounted on the
Controller in the Port 0A-0/Port 1A-0 side.
8-d GP0 LED Green Shows status of the standard Interface Board mounted on the
8-e ALARM LED Red Lights when the Port 0A-0/Port 1A-0 is in trouble.
8-f Port 0B-0/ Tx Connector Connector on the signal output side to connect the Fibre Channel
Port 1B-0 interface cable in the Port 0B-0/Port 1B-0 side.
8-g Rx Connector Connector on the signal input side to connect the Fibre Channel
interface cable in the Port 0B-0/Port 1B-0 side.
8-h GP1 LED Green Shows status of the standard Interface Board mounted on the
Controller in the Port 0B-0/Port 1B-0 side.
8-I GP0 LED Green Shows status of the standard Interface Board mounted on the
Controller in the Port 0B-0/Port 1B-0 side.
8-j ALARM LED Red Lights when the Port 0B-0/Port 1B-0 is in trouble.

TRBL 02-0080-01
(2) Indication positions and their functions of RKS
1-b
1-c
1-d
1-a 1-e
Front bezel Indicating section (STATUS panel)
2-d 2-c 2-b 2-a 2-e 2-f
1-h 7 8 9 10 11 12 13 14
1-f
1-g
0 14
Backup Battery Unit Panel Unit Fan Assembly Control Unit Power Unit Fan Assembly
3-b 6-d 6-c
3-c
3-a
6-a 6-b
5-a
4-d
4-a 4-b 4-c
7-q-1 7-q-2 7-q-3 7-q-4 7-q-5
7-l-2 7-l-3 7-m-2 7-m-3 7-a 7-c 7-e 7-f 7-h
LASER KLASSE 1
CLASS 1
LASER PRODUCT
7-p 7-l-1 7-m-1 7-n 7-o 7-b 7-d 7-g 7-i 7-j 7-k
7-p-1 7-p-2 7-p-3 7-p-4 7-p-5

TRBL 02-0090-01

1-b POWER LED Green Indicates that the power supply is supplied to the subsystem.
1-c READY LED Green Lighting
Blinking
Indicates that the offline download process is completed.
1-d WARNING LED Orange Lighting
occurred.
Blinking
Indicates that a failure which does not stop operation occurred
in unit (It must be detected with WEB).
1-e ALARM LED Red Lighting
Indicates that a failure, which does not allow the subsystem to
operate, occurred.
Blinking
1-f Main switch (OFF) Switch OFF : Presses off the power.
1-g Main switch (ON) Switch ON : Presses on the power.
1-h BUZZER OFF SW Switch Pressing of this switch while the buzzer sounds stops the beep. (*1)
2-a STATUS Panel PWR (POWER) LED Green Indicates that the power supply is supplied to the subsystem.
2-b (RKM) RDY (READY) LED Green Lighting
Blinking
Indicates that the ENC/SENC firmware is being downloaded.
Indicates that the download processing with the power turned
off is completed.
2-c WARN LED Orange Lighting
(WARNING) Indicates that a failure, which allows the subsystem to operate,
occurred.
Blinking
occurred. (It must be detected with WEB).
2-d ALARM LED Red Lighting
Indicates that a failure occurred which makes the subsystem
unable to operate.
Blinking
2-e ALARM LED Red Indicates that a failure which makes the unable to operate occurred.

TRBL 02-0100-01

2-f ACTIVE LED Green No. LED status Meaning
2 On Spin up state.
3-a Panel Unit Main switch Switch Turns on/off the power.
: Power on
: Power off
3-b BUZZER OFF SW Switch Pressing of this switch while the buzzer sounds stops the beep. (*1)
3-c Mode switch Switch Sets the local/remote mode by the combination of turning on and off
of the four mode switches.
4-a Backup Battery Unit ALARM LED Red Lights when the Backup Battery unit is in trouble.
The BATTERY switch is turned off
Battery temperature abnormal.
4-b CHARGE LED Orange Charging Battery (On)
4-c READY LED Green Shows the state of the battery.
On : Battery is in the normal condition.
Blinking : Charged up when start-up
Off : Abnormal
The battery switch is turned off.
Temperature of the battery is abnormal.
4-d BATTERY Switch Switch Turns on/off of the battery power.
When this switch is set to the off, the WARNING LED comes on
and the buzzer sounds.
ON: Power on
OFF : Power off
5-a Fan Assembly ALM LED Red Shows the state of the Fan Assembly
On : Abnormal
Off : Normal
| : Power on
{: Power off

TRBL 02-0110-01

7-a Control Unit P1 LED Green Indicates that the link status of the FC-AL (loop 1 side) is normal.
7-b P0 LED Green Indicates that the link status of the FC-AL (loop 0 side) is normal.
7-c CHK (CHECK) LED Red Shows error factors by means of a number of times of blinking.
Once : Drive +5 V voltage is abnormal.
Twice : Drive +12 V voltage is abnormal.
Five times : Battery is abnormal.
Six times : Voltage on the Controller is abnormal.
(Reset of the Controller is not canceled.)
Seven times : BS12V voltage is abnormal.
Nine times : Fans are abnormal.
The following blinking is fast because ENC microprogram detects
CUDG error.
Once : SRAM error.
Twice : ENC hard error.
Not blinking : BOOT section error of ENC microprogram,
RAM error, or ENC hard configuration error.
7-d EALM LED Red Indicates error factors by means of lighting or blinking.
Lighting
Indicates that a failure, which makes the ENC in the Control Unit
unable to operate, occurred.
Blinking
microprogram.
7-e RST SW Switch Used to perform a memory dump.
7-f CACHE POWER LED Green You can check whether the Cache memory is being backed up
through indication of this LED.
This LED is effective when the AC Power Unit Switch is turned on
On : Indicates that the cache is being backed up. (The power is
supplied from the battery to the Cache memory.)
Off : The Cache memory is not backed up.
7-g RST LED Orange Indicates that the Controller is being reset.
During power-on reset
During reset for doing a dump
During reset for a reboot at the time of a microprogram down
load
7-h CHKSTP LED Red A failure occurred at Controller and it became not operational.
7-i CALM LED Red Indicates that a failure which makes in the Controller unable to
operate occurred in it.
7-j PATH0 Connector Connection connector for ENC cable (PATH 0 side).
7-k PATH1 Connector Connection connector for ENC cable (PATH 1 side).
7-l-1 LAN0 LAN0 Connector Connects the LAN0 cable. (For maintenance)
7-l-2 ACT LED Orange Indicates that data is being transferred via a LAN 0.
7-l-2 LINK LED Green Indicates that the link status of the LAN 0 is normal.

TRBL 02-0120-01

7m-1 Control Unit LAN1 LAN1 Connector Connects the LAN1 cable. (For User Management)
7-m-2 ACT LED Orange Indicates that data is being transferred via a LAN 1.
7-m-3 LINK LED Green Indicates that the link status of the LAN 1 is normal.
7-n Connector for Connector Used to connect the Remote adapter.
connecting the
Remote adapter (J8)
7-o Connector for Connector Used to connect the UPS for the DF700.
connecting the UPS
interlocking cable (J5)
7-p Voltage Check Connector There are two cases where the numbers of pins are 8 and 20
Connector respectively depending on the revision of the PCB. (The switch
has nothing to do with maintenance because it is used for
evaluation.)
7-p-1 Port 0A-0/ Tx Connector Connector on the signal output side to connect the Fibre Channel
7-p-2 Rx Connector Connector on the signal input side to connect the Fibre Channel
7-p-3 GP1 LED Green Shows status of the standard Interface Board mounted on the
7p-4 GP0 LED Green Shows status of the standard Interface Board mounted on the
7-p-5 ALARM LED Red Lights when the Port 0A-0/Port 1A-0 is in trouble.
7-q-1 Port 0A-1/ Tx Connector Connector on the signal output side to connect the Fibre Channel
7-q-2 Rx Connector Connector on the signal input side to connect the Fibre Channel
7-q-3 GP1 LED Green Shows status of the standard Interface Board mounted on the
7-q-4 GP0 LED Green Shows status of the standard Interface Board mounted on the
7-q-5 ALARM LED Red Lights when the Port 0A-1/Port 1A-1 is in trouble.

TRBL 02-0130-01
(3) Indication positions and their functions of RKAJ
Indicating section (STATUS panel)

1-a 1-c 1-b
Front bezel 2-b 2-a 2-c 2-d
7 8 9 10 11 12 13 14
2-e 2-f
0 14
ENC Unit Power Unit ENC Unit
3-c 3-d
4-c 4-d 4-e 4-g
4-a 4-b 4-f 4-h 4-i 4-j

3-a 3-b

TRBL 02-0140-01

1-b POWER LED GreenIndicates that the power supply is supplied to RKAJ.
1-c WARNING LED Orange
Indicates that a failure, which allows RKAJ to operate, occurred.
2-a STATUS Panel PWR (POWER) LED GreenIndicates that the power is supplied to the RKAJ/RKAJAT.
2-b (RKAJ) WARN LED Orange
Indicates that a failure which allows the RKAJ/RKAJAT operation
(WARNING) occurred.
2-c ALARM LED Red Indicates that a failure which makes the unable to operate occurred.
2-d ACTIVE LED Green No. LED status Meaning
2 On Spin up state.
2-e ID Switch Sets the device ID (*1) of the RKAJ/RKAJAT.
2-f Subsystem Switch Sets the basic subsystem to be connected.
identification M : RKM
S : RKS
| : Power on
{: Power off
4-a ENC Unit PATH0 Connector Connection (for input) connector for ENC cable (PATH0 side).
4-b PATH1 (IN side) Connector Connection connector (for input) for ENC cable (PATH1 side).
4-c Jumper Connector Connector Type : Four pins (The switch has nothing to do with maintenance
(J30 : RKAJ) because it is used for evaluation.)
4-d SW Switch Not used (The switch has nothing to do with maintenance because
it is used for evaluation.)
4-e P1 LED Green Indicates that the link status of the FC-AL (loop 1 side) is normal.
4-f P0 LED Green Indicates that the link status of the FC-AL (loop 0 side) is normal.
*1 : 0 is used for the RKM/RKS in default.

TRBL 02-0150-01

4-g ENC Unit CHK LED Red ENC Unit
It indicates error factors by means of number of times of blinking.
Low-speed blinking:
Once : Logic +5 V voltage is abnormal.
Twice : Logic +12 V voltage is abnormal.
Six times : Logic + 2.5V voltage of the ENC Unit is
abnormal.
CUDG error detected by ENC microprogram.
Lighting:
CUDG error detected by ENC microprogram
(BOOT section)
RAM error detected by ENC microprogram
ENC hard configuration error
High-speed blinking:
Once : SRAM error.
Twice : CUDG error in ENC hard.
4-h ALM LED Red Indicates error factors by means of lighting or blinking.
Lighting
Indicates that a failure, which makes the ENC Unit unable to
operate, occurred.
Blinking
microprogram.
4-i PATH0 Connector Connection connector (for output) for ENC cable (PATH 0 side).
4-j PATH1 (OUT side) Connector Connection connector (for output) for ENC cable (PATH 1 side).
Jumper Connector Connector
4 3 Type RKAJ
(J14 : RKAJ)
2 1 Pin No. Meaning
1-2 Short circuit The voltage on LG +12 V and +5
V is dropped by 5%.
3-4 Short circuit The voltage on LG +12 V and +5
V is increased by 5%.

TRBL 02-0160-01
(4) Indication positions and their functions of RKAJAT
Indicating section (STATUS panel)

1-a 1-c 1-b
Front bezel 2-b 2-a 2-c 2-d
7 8 9 10 11 12 13 14
2-e
0 14
ENC Unit Power Unit ENC Unit
4-d 4-e 4-e 4-g 3-c 3-d 3-b

4-a PATH0 (IN) PATH0 (OUT) 4-b
4-f 4-h
3-a

TRBL 02-0170-01

1-b POWER LED Green Indicates that the power supply is supplied to RKAJAT.
1-c WARNING LED OrangeIndicates that a failure, which allows RKAJAT to operate, occurred.
2-a STATUS Panel PWR (POWER) LED Green Indicates that the power is supplied to the RKAJ/RKAJAT.
2-b (RKAJAT) WARN LED OrangeIndicates that a failure which allows the RKAJ/RKAJAT operation
(WARNING) occurred.
2-c ALARM LED Red Indicates that a failure which makes the unable to operate occurred.
2-d ACTIVE LED Green No. LED status Meaning
2 On Spin up state.
2-e ID Switch Sets the device ID (*1) of the RKAJ/RKAJAT.
2-f Switch
M : RKM
S : RKS
| : Power on
{: Power off
4-a SENC Unit PATH0 Connector Connection (for input) connector for ENC cable (PATH0 side).
4-b PATH1 (IN side) Connector Connection connector (for input) for ENC cable (PATH1 side).
4-c Output pin Pin J4 Pin No. Meaning
(J4, : RKAJAT) J4-1 Logic +12 V
J4-2 Logic +5 V
J4-3 Logic +3.3 V
J4-4 Logic +2.5 V
J4-5 Logic +1.8 V
J4-6
J4-7
J4-8 GND
4-d Connector for Connector To be used when connecting the console cable of a processor.
connecting a (For setup before shipment)
processor
4-e SW Switch Not used (The switch has nothing to do with maintenance because
it is used for evaluation.)
4-f P1 LED Green Indicates that the link status of the FC-AL (loop 1 side) is normal.
*1 : 0 is used for the RKM/RKS in default.

TRBL 02-0180-01

4-g SENC Unit CHK LED Red SENC Unit (RKAJAT)
The CHK LED (Red) lights on (for about 10 seconds) while the
CUDG is being executed. Also, it indicates error factors in the
subsystem by the number of times of blinking.
Low-speed blinking:
Twice : CUDG error in SENC
Eight times : Fan selector circuit error.
Lighting:
CUDG error in BOOT section of SENC
High-speed blinking:
Five times : Fixed data error in flash memory.
Six times : Significant surface error in flash memory
Seven times : SUM check error in flash memory
4-h ALM LED Red Indicates error factors by means of lighting or blinking.
Lighting
Indicates that a failure, which makes the ENC Unit unable to
operate, occurred.
Blinking
microprogram.
Jumper Connector Connector
1 2 Type RKAJAT
(J3 : RKAJAT) 3 4 Pin No. Meaning
5 6 1-2
3-4 Short circuit The voltage on LG +12 V to 2.5 V
and 1.25 V is increased by 5%.
5-6 Short circuit The voltage on LG +12 V to 2.5 V
and 1.25 V is dropped by 5%.

TRBL 02-0190-01
Chapter 3. Before Starting WEB Connection

3.1 Procedure to WEB connection
(1) Points to be confirmed before connecting WEB
Unless the subsystem is activated, the subsystem cannot be connected to WEB.
Confirming the following LEDs before connecting to WEB.
y Confirming the power status (POWER LED).

Check if the POWER LED on the Front Bezel lights up.
If the Power LED does not light up, see Chapter 8. Trouble Analysis by LED Indication
(TRBL 08-0000).
POWER
POWER
(a) RKM/RKS (b) RKAJ/RKAJAT
Figure 3.1.1 Locations and Name of LED
y Confirming the CHKSTP LED of the Control Unit

Check if the CHKSTP LED on the Control Unit lights up.
If CHKSTP LED is on, replace Control Unit of which CHKSP LED is on. Refer to Replacement
2.2.5 Replacing Control Unit (REP 02-0390) for replacing a Control Unit.
Control Unit #1
Control Unit #0
RKM (Rear view) RKS (Rear view)

CHKSTP LED (red) CHKSTP LED (red)
LASER KLASSE 1 LASER KLASSE 1

CLASS 1 CLASS 1
LASER PRODUCT LASER PRODUCT
Control Unit (RKM) Control Unit (RKS)

TRBL 03-0000-01
(2) Preparation of maintenance terminal to be used
Table 3.1.1 Decision and Preparation of Maintenance Terminal

Maintenance terminal used Connection procedure reference
Item Customers environment Preparation
destination
1 Using LAN connectors for Connect the portable y PC for maintenance(*1) 3.1 (4) Procedure to connect
maintenance of the Control Unit service PC via a LAN. y LAN cross cable portable maintenance PC to WEB
(TRBL 03-0010).
*1: Refer to 3.3 Note on WEB connecting (TRBL 03-0060) for recommended PC.
(3) Control Unit to be connection

If a system has a dual Control Unit, connect to either Control Unit to connect to the WEB.
First, connect to Control Unit#0.
If Control Unit #0 is blocked, however, information after the blockage of Control Unit #0 is
referenced on only Control Unit #1 side. Accordingly, if Control Unit #0 is blocked, connect to
Control Unit #1.
(4) Procedure to connect portable maintenance PC to WEB

(a) Remove the cover on the Control Unit. Connect the LAN-Connecter for maintenance and
the LAN-Connecter of Maintenance PC with a LAN-cross-cable.
Control Unit #1
Control Unit #0

LAN connector LAN connector
(for maintenance) (for maintenance)
Cover ACTIVE LED (green) Cover ACTIVE LED (green)
LINK LED (green) LINK LED (green)

CLASS 1 CLASS 1
Figure 3.1.3 LAN Connector Position
(b) Start up the maintenance PC.

TRBL 03-0010-01
(c) Change the IP address of the network parameter for the maintenance PC.
For the maintenance PC, set the IP address shown in No. 1 in Table 3.1.2 below.
If the maintenance PC cannot be connected, set the value in No. 2.
Table 3.1.2 Operational Environment

Subsystem (LAN port for maintenance) Maintenance PC
No. IP Address Subnet Mask IP Address Subnet Mask
1 CTL 0: 10.0.0.16 255.255.255.224 10.0.0. 255.255.255.224
CTL 1: 10.0.0.17 (At the time of shipment) (xxx is any value from 1 to
(At the time of shipment) 30 except 16, 17.)
2 CTL 0: 192.168.0.16 255.255.255.224 192.168.0. 255.255.255.224
CTL 1: 192.168.0.17 (xxx is any value from 1 to
30 except 16, 17.)
Automatic change of network parameters of the Port 0 (for maintenance)

Since communication is not performed normally when the network addresses of the Port 1
(for user management) and the Port 0 (for maintenance) are the same, two sets of fixed
values of the network parameters to be used for the Port 0 (for maintenance) are prepared
and either of the two sets is automatically given to the Port 0 (for maintenance) depending
on the network parameters of the Port 1 (for user management).
When the network address of the Port 1 (for user management) is set as 10.*.*.*, that of
the Port 0 (for maintenance) is changed as shown below.
NOTE : However, if the network address of the LAN device connected to Port 1 (User
Management) via the Gate Way accords with that of Port 0 (Maintenance), they
will collide each other, disabling to communicate normally.
(1) When the Port 1(User Management ) address is set to other than 10.*.*.*,
10.0.0.(0 to 31) cannot be used for the IP address for LAN device to be
connected to Port 1(User Management ) through a Gateway. Therefore,
set the IP address to other than 10.0.0.(0 to 31).
(2) When the Port 1(User Management ) address is set to 10.*.*.*,
192.168.0.(0 to 31) cannot be used for the IP address for LAN device to
be connected to Port 1(User Management ) through a Gateway.
Therefore, set the IP address to other than 192.168.0.(0 to 31).

Network parameter Port 0 (Maintenance) Port 0 (Maintenance)
IP Address 192.168.0.16 192.168.0.17
Subnet Mask 255.255.255.224 255.255.255.224
Default Gateway 0.0.0.0 0.0.0.0
DHCP OFF OFF

TRBL 03-0020-01
(5) Setting method of IP Address on Windows 95

The procedure for setting an IP Address of the PC in Windows 95 is shown below.
Also in Windows 98, the IP Address of the PC can be set by the similar operation.
(a) Select [Start]-[Set]-[Control Panel]-[Network].
(b) Select [Configuration]-[The following network components are installed]-[TCP/IP] and click
the [Properties] button to open [TCP/IP].
(c) Select [TCP/IP Properties]-[IP Address]-[Specify an IP address] and set the [IP Address] and
press the [OK] button.

TRBL 03-0030-01
(d) Set the TCP/IP to Disable DNS because the connection takes a long time when the TCP/IP
of the network is set to the condition in which the DNS is used.
For the setting procedure, refer to the instruction manual of the PC to be used.
(e) When confirming message appears whether to reboot the PC, press [OK].
(f) The maintenance PC is rebooted and the changed IP Address and Subnet Mask become
effective.
(g) Start up the Browser. Enter the URL window with the IP address of maintenance port to
which the maintenance PC is connected. When WEB screen appears, the connection is
complete.
NOTE : The Web may be unable to be connected for two to three minutes after a
detachment of the Control Unit because the CTL Alarm Trace is being made.
(h) Make sure that the browser is set to the condition in which the proxy server is not used
because the connection cannot be done if the proxy server is set to be used.
To make sure the setting, refer to the instruction manual of the browser to be used.

TRBL 03-0040-01
3.2 When the WEB has already been connected

If the WEB has been connected, information displayed before may be still displayed.
Before starting trouble analysis based on the WEB connection, [Refresh] the WEB window.
The time when the WEB window is displayed is referenced as shown below.
Window display differs depending on microprogram revision.
(1)
1 : The time determined by the Device Controller RTC (Real Time Clock) is indicated here. (It is not consistent with
the main PC clock.)
For setting the Device Controller RTC, refer to 2.2 Confirming and setting RTC (Real Time Clock) (TRBL 02-
0010).

TRBL 03-0050-01
3.3 Note on WEB connecting

(1) Note on WEB using
(a) The LAN function may become temporarily unable to be connected when the update of the
WEB display is repeated frequently. In this case, wait for a short time (at least one minute),
then update again.
(b) When connecting the WEB of DF700, use the following browsers.
Table3.3.1 Recommended WEB hardware

No. Item Description Remark
1 OS Microsoft Windows 98, NT 4.0, 2000, XP, 2003, Solaris8, IRIX6.5
2 PC Pentium (Pentium II (233 MHz or more) is recommended),
3 WS Turbo Sparc 170 M Hz, Memory 256 Mbytes or more
R10000 195 M Hz, Memory 128 Mbytes or more
4 Disk requirement y 50 Mbytes, under ordinary maintenance work Data compression tool is
y 480 Mbytes per one Controller, under memory dump collection(*1) required for memory
Storing temporary file of Browser : 240 Mbytes dumping.
Storing dumped memory : 240 Mbytes
*1 : Memory dump collection may be requested by the Technical Support Center at the time of a tough
failure.

TRBL 03-0060-01
Table3.3.2 Support Browser List

({ : support : not support)
OS Browser System version : x659/M
No. Platform Supported or Java Aplet supported or not
Type Ver. Type Ver.(*1) not supported supported (*2) (*3)
1 WS IRIX 6.5 Netscape Navigator 4.76 {
Solaris 2.6 Netscape Navigator 4.76 {
8 Netscape Navigator 4.76 {
2 PC Windows 98 Internet Explorer 6.0 { {
NT/2000 Internet Explorer 6.0 { {
XP Internet Explorer 6.0 {
2003 Internet Explorer 6.0 { {
(IA32)
2003 Internet Explorer 6.0 {
(IA64) 6.0 (32 Bit) { {
Windows 98 Netscape Navigator 7.1 (J) {
7.2 (E) {
NT/ 2000/XP Netscape Navigator 7.1 (J) {
7.2 (E) {
2003 Netscape Navigator 7.1 (J) {
(IA32/IA64) 7.2 (E) {
*1 : Service Pack 1 is included.
*2 : When installing the microprogram, the service PC must be started by the OS from the drive C in order to
prevent a problem of security from occurring.
*3 : Java Aplet is used for the following cases.
Microprogram installation, Host command trace download, and Online ENC/SENC firmware download.

TRBL 03-0070-01
Notices on (restriction of) the support browser

In the case of Windows2003, because the strict data security is the default setting, the
Web function cannot work.
In order to solve the above problem, change the setting of the browser as follows.
y Select [Tools] - [Internet Options ] - [Security] - [Custom Level ] - [Custom Setting
Reset] of the browser in this order and select the setting of the security level from
Medium or lower and click the Reset button.
The making of the setting as Medium solves the problem. However, if you want to use
Win2003 leaving the security level as High, make the following settings for the detailed
items of the [Custom Level ].
y Enable the [Active scripting] of the [Scripting].
y Enable the [Allow META REFRESH] of the [Miscellaneous].
y Enable the [File download] of the [Downloads].
y Enable the [Run ActiveX controls and plug-ins] of the [ActiveX controls and plug-ins].
y There may be a case where a new line is started in a window depending on a setting of
the browser. In such a case, make the character size smaller.
< Method of character size change >
In the case of IE
Select Middle or smaller size for the Character Size in the Display.
In the case of Netscape
Select the Reduction of Font Size in the Display and keep it being selected until
paragraphs become easy to be read.
y There may be a case where an empty dialogue box is displayed during operation in the
Maintenance mode. In such a case, close the window by clicking on the mark of X in
the upper left corner of the dialogue box, restart the browser, and then make a retry
from the entry of the URL.
y When a window size is changed while a page is displayed by Netscape, the succeeding
operation in the Refresh mode may not be done normally. In such a case, display the
page over again by clicking the Re-Display button.
y In the case of using Netscape
Memory cache: 1024 kbytes (default) or larger
Disk cache: 7680 kbytes (default) or larger
< Method of cache size setting >
Select the Edition, Setting, Details, and Cache in this order.
Specify sizes of the memory cache and disk cache.
y When obtaining trace information etc. with Netscape, there are cases that a sub-screen
to specify the file download destination does not automatically close.
In such a case, press a close button at the upper right corner of the sub-screen to close
the sub-screen after download complete.

TRBL 03-0080-01
y When using Netscape navigator 7.x, select [Edit]-[Preference...]-[Advanced]-[HTTP

Networking], and set Use HTTP 1.0 in the Direct Connection Options and Proxy
Connection Options.
When this setting is not made, the summary window is not displayed correctly.
y When collecting memory dump (Full Dump) using Netscape Navigator 4.7x, pay attention
to free space in PC because information to be downloaded wont be compressed.
Installed cache of the subsystem Free Capacity needed on PC

RKM 1 G bytes/1 controller 1,710 M bytes/1 controller
2 G bytes/1 controller 2,670 M bytes/1 controller
RKS 1 G bytes/1 controller 1,440 M bytes/1 controller

TRBL 03-0090-01
(2) The procedure for connecting to another subsystem having the same IP address via a LAN.
In the case of connecting and maintaining two or more controllers, whose IP addresses are the
same, using a service PC and cross cable of a LAN, when one of the Controllers is connected to
the PC, the PC memorizes the IP address and physical address of the Controller making a pair
of them. Therefore, if another Controller is connected to the PC via a LAN, the IP address is
not accepted because the physical address is different.
To make the above connection via a LAN, execute the following command from the MS-DOS
prompt of Windows PC in order too delete the information on the IP address stored in the arp
table in the PC.
arp -d IP address
y IP address : IP address stored in the arp table

Example : When deleting an IP address 10.0. 0.16 (default) from the table
arp -d 10.0. 0.16
To make sure that the IP address stored in the arp table has been deleted, execute the
following command from the MS-DOS prompt of Windows PC.
arp -a
The IP address has been deleted when a message, No ARP Entries Found or the one informing
that the specified IP address could not be found is returned from the subsystem.
(3) User authentication when connecting the Web

[Password].

TRBL 03-0100-01

TRBL 03-0110-01
Chapter 4. Trouble Analysis by WEB Connection

Trouble analysis by WEB connection to locate a failed part in the unit and how to repair that
trouble are shown below.
The flow of the trouble analysis by WEB connection is as follows.
Determine the failed part following the procedure below.
Trouble analysis by
WEB connection
Confirm indication of state of unit.

(See 4.1 (1) Confirm indication of state of unit (TRBL 04-0010))
Confirm summary of
Confirm indication of progress. replacement parts.
(See 4.1 (2) Confirm indication (See 4.1 (3) Confirm
of progress (TRBL 04-0020)) replacement part summary
(TRBL 04-0030))
Yes Is Boot completed No

Is the failed part?
displayed?
No Yes
Confirm summary of
replacement parts.
Wait for a while. (See 4.1 (3) Confirm
(10 min)
replacement part summary
(TRBL 04-0030))
Confirm indication of progress. Confirm details of parts.

(See 4.1 (2) Confirm (See 4.2 Confirm state of
indication of progress (TRBL each part (TRBL 04-0040))
04 0020))
Yes
Is Boot completed
No
Confirm log messages Normal Confirm log messages Confirm log messages
(See 4.3 Confirm log (Maintenance operation is (See 4.3 Confirm log (See 4.3 Confirm log
messages (TRBL 04-0100)) unnecessary.) messages (TRBL 04-0100)) messages (TRBL 04-0100))
NOTE : In case the log message is checked while the WARNING LED on the front side of
the subsystem is blinking, the WARNING LED goes out when the warning is
cancelled and stays on when the warning is not cancelled.

TRBL 04-0000-01
4.1 Confirm state of unit

Check the failed part of the unit on the main window in the normal mode of the WEB.
For the replacement of the parts and recovery method, see the log messages (4.3 Confirm
log messages (TRBL 04-0100)).
(1) Confirm indication of state of unit

The state of the unit can be confirmed in the following window.
Confirm state of unit
Booting Ready Warning Alarm
(Black) (Blue) (Yellow) (Red)
Figure 4.1.1 Main Window in the Normal Mode

TRBL 04-0010-01
(2) Confirm indication of progress

If Booting is indicated in the window of (1) (the Controller is being started up), the
progress of start-up operation can be confirmed according to the following procedure.
Update button
Progress Condition display
Page Refresh Mode
(a) Turn on the page refresh mode (Click the [Change] button).
The window is updated automatically at the interval of 5 seconds. (If the [ON] button of the
page refresh mode is indicated, the above operation is not necessary.)
If the page refresh mode is not indicated in the main window, press the update button of the
browser to update the window.
(b) See the indication of progress of the window.
If the start-up operation is completed, Boot completed is indicated in this part.

TRBL 04-0020-01
(3) Confirm replacement part summary

The state of each replacement parts can be confirmed with the replacement part summary.
Summary of exchange
parts status
Backup Battery Unit Power Unit ENC Unit SENC Unit Fan Assembly

Control Unit Cache Unit Loop
(FC) (S-ATA)
Host Connector Remote Path
If any part fails, its summary becomes red.

If the red part summary is clicked, the state confirmation window of the part appears and the
position of the failed part is confirmed more in detail. (See 4.2 Confirm state of each part
(TRBL 04-0040))
Also, when the menu frame Warning Information is clicked, status of each component is
displayed (See 4.2 Confirm state of each part (TRBL 04-0040)) and the status of each
component can be checked.

TRBL 04-0030-01
4.2 Confirm state of each part

When checking the status of a component through an image, a clicking on each component of
the Summary of replacement component statuses in the main window changes the window
to that shown in Item (1) below and a detailed component status is displayed.
In this case, the window is changed in the state in which the selected (clicked) component is
positioned at the top of the window. Also, a clicking on the Parts Information menu in the
main window changes the window.
When checking the status of a component through a message, a clicking on the Warning
Information of the menu frame in the main window changes the window to that shown in
Item (2) Procedure of the Status checking by messages (TRBL 04-0090) and displays a
detailed component status as a message. In this case, detailed status of each component can
be checked. For the replacement for maintenance or recovery procedure, refer to a log
message (See 4.3 Confirm log messages (TRBL 04-0100)) and perform a recovery action
following the procedure given by the each log message.
(1) Procedure for checking the status through an image

Disk Drive
Unit-1
Unit-0

TRBL 04-0040-01
Controller/Battery/Cache/Loop/Host Connector
Unit-1
Unit-0
Unit-1
Unit-0
AC/ENC/Fan
Unit-1
Unit-0

TRBL 04-0050-01
The meaning of the image that displays it with the display screen of exchange part status is
shown below.
(a) Disk Drive (FC)
Image Status
Normal
Blue
Fault has occurred to the Disk Drive
Red
Disk Drive port that the fault occurred is not implementing the Disk Drive
Red and Black

Disk Drive is not implemented (Except for the status where the Disk Drive that the
No display
fault occurred was drawn out)
(b) Disk Drive (S-ATA)

Image Status
Normal
Blue
Red
Red and Black

No display
(c) Control Unit

Image Status
Normal
Green
Shutdown of the Control Unit
(Status where it is not implemented with the setting of the dual system
Red configuration is included)
Fault of the battery backup circuit
Yellow
Even the fault has not occurred without being implemented with the setting of
No display
single system configuration
(d) Backup Battery Unit

Image Status
Normal
Green
There is a fault or not implemented
Red

TRBL 04-0060-01
(e) Cache Unit

Image Status
Normal
Green
Fault
Red (Status where is not implemented and extracted the fault cache memory is
included)
It is not implemented and there is not a fault
No display
(f) Fibre loop

Image Status
Normal
Blue
Fault
Red
(g) Host Connector

Image Status
Normal
Gray
Fault
Red
(h) Power Unit

Image Status
Normal
Blue
It is fault occurred or not implemented
Red
(i) ENC Unit

Image Status
Normal
Green
Red

TRBL 04-0070-01
(j) SENC Unit

Image Status
Normal
Green
Red
(k) Fan Assembly

Image Status
Normal
Black
Red

TRBL 04-0080-01
(2) Procedure of the Status checking by messages

A warning message about the failed part is displayed.
Refer to 4.3 Confirm log messages (TRBL 04-0100) for the details of the warning messages.
Information of the menu frame in the main window changes the screen to the one shown
below and a detailed message explaining the component status is displayed.

TRBL 04-0090-01
4.3 Confirm log messages

(1) Procedure for confirming log messages
Click the [Information Message] menu in the main window, and the Information Message
window appears.
In the Information Message window, you can identify the cause of the failure and confirm the
recovery method.
The information on the failures which were detected during operation of the unit and state of
the unit s indicated in the above window.
The information on the failures and state after the unit starts up is indicated in the [Controller
0/1 Common] box.
The information on the failures and state at the time of start-up of the unit is indicated for
each Controller in the [Controller 0] and [Controller 1] boxes.
The contents of each message are shown below.

TRBL 04-0100-01
(a) CUDG (Self-test at power-on) detection message

( i ) Indicated message
The CUDG detection message is indicated in the [Controller 0] or [Controller 1] box as
shown below.
Controller x
MM/DD/YYYY HH:MM:SS Cx C0
MM/DD/YYYY HH:MM:SS Cx B0
MM/DD/YYYY HH:MM:SS Cx A0
MM/DD/YYYY HH:MM:SS Cx 90
MM/DD/YYYY HH:MM:SS Cx 60 Y Y M M D D H H M M S S
MM/DD/YYYY HH:MM:SS Cx {{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{
MM/DD/YYYY HH:MM:SS Cx CTLx
MM/DD/YYYY : Date of occurrence
HH:MM:SS : Time of occurrence
Cx : # of Controller in which failure is detected
: PCI Config information
: Detailed information
: Message code
{{{{{{{{{{{ : Message text (Any number of letters)
Y Y M M D D : Date of occurrence
H H M M S S : Time of occurrence
: Reservation area
CTLx : CUDG executing controller #
(ii) Recovery method

Recover from the failure according to the recovery method for each message code.
(For the recovery method for each message, see Message Chapter 2. CUDG Detected
Messages (MSG 02-0000).)

TRBL 04-0110-01
(b) Flash/RAM micro detection message

( i ) Indicated message
The Flash/RAM micro detection message is indicated in the [Controller 0/1 Common],
[Controller 0], or [Controller 1] box as shown below.
The latest one is indicated at the top line.
NOTE : As the date and time of occurrence indicated by the message, the RTC set in
the detection controller is used.
If the RTC is different from one control to another, the indicated time of
occurrence may be different from one message to another (the message on the
upper line is indicated earlier than the one on the lower line).
In this case, the actually latest message is indicated at the top, too.
MM/DD/YYYY HH:MM:SS Cx {{{{{{{{{{{ : /

:
MM/DD/YYYY : Confirmed date

HH:MM:SS : Confirmed times
Cx : Error detected Controller#
: Message Code(1)
Hxxxxx : Failure messages (See Message Chapter 3. Failure Messages (MSG
03-0000))
Ixxxxx : Progress messages (See Message Chapter 4. Progress Message (MSG
04-0000))
Rxxxxx : Flash detected messages (See Message Chapter 5. Flash Detected
Messages (MSG 05-0000))
Wxxxxx : Warning messages (See Message Chapter 6. Warning Messages (MSG
06-0000))
{{{{{{{{{{{ : Message text (Optional font number)
: Recovery method code (see (ii))
: Collecting failure information code (see (ii))
1 : For the message in which no recovery method is written, follow the recovery method shown in another message
issued at the same time.

TRBL 04-0120-01
(ii) Recovery method

c Collect the failure information according to ().
Table 4.3.1 Collecting Failure Information List

Display code Error information you must collect
STRC Simple trace
CTRC Controller shutdown trace
FDMP Memory dump
No display None
Refer to Chapter 7. Collecting Error Information (TRBL 07-0000) for the details.
d Recover from the failure according to Recovery method code ( ).

Refer to the Message Chapter 1. Before Starting Trouble Analysis (MSG 01-0000) for the
details of the messages.
Table 4.3.2 Recovery Method Code List

Display code Recovery methods Reference page
CTL c Replace the Control Unit, the CALM LED of which is on. Replacement 2.2.5 Replacing
d If the system is still abnormal, replace the other Control Unit. Control Unit (REP 02-0390)
BAT Replace the Backup Battery Unit. Replacement 2.2.2 Replacing
Backup Battery Unit (REP 02-
0240)
CACHE Replace the Cache Unit indicated in the message text. Replacement 2.2.6 Replacing
Cache Unit (REP 02-0540)
CTL Replace the Control Unit, the CALM LED of which is on. Replacement 2.2.5 Replacing
Control Unit (REP 02-0390)
ENC Replace the ENC Unit/SENC Unit indicated in the message text. Replacement 2.2.9 Replacing
ENC Unit/SENC Unit (REP 02-
0830)
FAN Replace the Fan Assembly. Replacement 2.2.3 Replacing
Fan Assembly (REP 02-0300)
HDU Replace the Disk Drive indicated in the message text. Replacement 2.2.1 Replacing
Disk Drive (REP 02-0050)
MANUAL Refer to the manual, and recover from the failure according to the recovery Message Chapter 1. Before
methods for each message code. Starting Trouble Analysis (MSG
Hxxxxx : Failure messages (See Message Chapter 3. 01-0000)
Failure messages (MSG 03-0000))
Ixxxxx : Progress messages (See Message Chapter 4.
Progress messages (MSG 04-0000))
Rxxxxx : Flash detected messages (See Message Chapter 5.
Flash detected messages (MSG 05-0000))
Wxxxxx : Warning messages (See Message Chapter 6.
Warning messages (MSG 05-0000))
PON Turn on the power again.
PS Replace the Power Unit indicated in the message text. Replacement 2.2.4 Replacing
Power Unit (REP 02-0340)

TRBL 04-0130-01
Display code Recovery methods Reference page

RETRY c Retry the operation. Message Chapter 1. Before
d If the same failure still occurs, refer to the message list in the manual, and Starting Trouble Analysis (MSG
recover from the failure according to the recovery methods for each 01-0000)
message code.
SYSPM Set the system parameter in the WEB maintenance mode correctly. WEB Chapter 3. The
Maintenance Mode Operation
Procedure (WEB 03-0000)
UPS When a UPS is connected, take a recovery action referring to the UPS manual.
No display This is not a problem.
Recovery operation is not necessary.

TRBL 04-0140-01
(iii) How to read failure information

y The history of the unit after it is turned on is indicated in the Information Message.
y The message of Subsystem is Ready indicates the time when the unit is ready.
The messages made after the power is turned on until the unit is ready are indicated
before this message. The messages made after the unit is ready are indicated after this
message.
y Particularly pay attention to Wxxxxx (Warning message), Hxxxxx (Failure messages), and
Rxxxxx (Flash detection message).
y The following messages are indicated when failures occur and when they are solved. (See
Table 2.2.3.)
If the recovery message is indicated after a failure occurrence message, the failure has
been solved and you do not need to solve it.
Table 4.3.3 Failure Message List

No. Description Failure detected messages Failure recovery messages
1 Controller error/recovery W00100 CTL alarm (CTL-x) I0010x CTL recovered (CTL-x)
2 Cache memory error/ recovery W0D0xy CACHE alarm (CTL-x, CACHE-y) I0020x CACHE recovered (CACHE-x)
3 Battery error/recovery W0300x Battery alarm I00300 Battery recovered
W0310x Battery removed I0030x Battery recovered (Battery-x)
W0320x Battery SW off
W0330x Battery Thermal alarm
4 Battery backup circuit error/ W0340x Battery backup circuit alarm (CTL-x) I0040x Battery backup circuit recovered (CTL-x)
recovery
5 Fan error/recovery W040xy FAN alarm (Unit-x, FAN-y) I005xy FAN recovered (Unit-xx, FAN-y)
W04100 FAN alarm (CTL-Unit, FAN-x) I00500 FAN recovered (CTL-Unit, FAN-x)
6 Power supply error/ recovery W050xy PS alarm (Unit-x, PS-y) I006xy PS recovered (Unit-x, PS-y)
W0G400 PS alarm [RKA] (Unit-x, PS-y)
W0G500 PS alarm [RKAAT] (Unit-x, PS-y)
W0G600 PS alarm [RKAJ] (Unit-x, PS-y)
W0G700 PS alarm [RKAJAT] (Unit-x, PS-y)
W05100 PS alarm (CTL-Unit, PS-x) I00600 PS recovered (CTL-Unit, FAN-x)
7 Disk Drive error/recovery W060AT SATA HDU alarm (Unit-x, HDU-y) I007xy HDU recovered (Unit-x, HDU-y)
W060xy HDU alarm (Unit-x, HDU-y)
W0GG00 HDU alarm [RKA] (Unit-x, HDU-y)
W0GH00 HDU alarm [RKAJ] (Unit-x, HDU-y)
8 Spare Disk error/recovery W061AT SATA Spare HDU alarm (Unit-x, HDU-y) I009xy Spare HDU recovered (Unit-x, HDU-y)
W061xy Spare HDU alarm (Unit-x, HDU-y)
W0GJ00 Spare HDU alarm [RKA] (Unit-x, HDU-y)
W0GK00 Spare HDU alarm [RKAJ] (Unit-x, HDU-
y)
9 Loop error/recovery W080xy Loop alarm (Path-x, Loop-y) I00Axy Loop recovered (Path-x, Loop-y)
10 ENC Unit error/SENC Unit W090AT SENC alarm (Unit-x, ENC-y) I00Bxy ENC recovered (Unit-x, ENC-y)
error/recovery W090xy ENC alarm (Unit-x, ENC-y)
W0GA00 ENC alarm [RKA] (Unit-x, ENC-y)
W0GB00 SENC alarm [RKAAT] (Unit-x, ENC-y)
W0GC00 ENC alarm [RKAJ] (Unit-x, ENC-y)
W0GD00 SENC alarm [RKAJAT] (Unit-x, ENC-y)

TRBL 04-0150-01
No. Description Failure detected messages Failure recovery messages

11 UPS W0C000 UPS alarm (UPS-x) I00D00 UPS recovered (UPS-x)
12 Path failure (detachment)/ W0F0xy Path alarm (Remote-x, Path-y) I030xy Path recovered by web operation
recovery (Remote-x, Path-y)
I031xy Path recovered automatically
13 Occurrence/ rectification of an W0G0xy Unreadable PIN detected (Unit-x, HDU-y) I04000 Unreadable PIN recovered
incomplete writing W0G100 Unreadable PIN detected (Unit-*, HDU-
*)
14 Issue/callback of a resident LU W440xy Permanent LU warning (CTL-x, ERR-y) I1A2xy Permanent LU warning recovered (CTL-
off warning x, ERR-y)
15 Excess/rectification of the W49100 PIN is over directory threshold [write I6EG00 PIN over recovered [directory threshold]
threshold value of the number through] (DIR-x) (DIR-x)
of pinned sub-segments W49300 PIN is over partition threshold [write I6EH00 PIN over recovered [partition threshold]
through] (DIR-x, PTT-y) (DIR-x, PTT-y)
W49500 PIN is over RAID group threshold [write I6EJ00 PIN over recovered [RAID group
through] (DIR-x, RG-y) threshold] (DIR-x, RG-y)
16 The DM-LU failure/recovery W49700 DM-LU write disable (LU-x) I6EM00 DM-LU recovered (LU-x)
W49800 All DM-LU write disabled
17 The host connector W0G300 Host connector alarm (Portxy-z) I53A00 Host connector recovered (Portxy-z)
failure/recovery
Example of message analysis :
07/02/2000 08:02:34 C0 W06011 HDU alarm(Unit-1,HDU-1) :HDU /STRC

Messages which require
07/01/2000 23:55:35 C1 W01000 CTL alarm(CTL-0) :CTL /CTRC
maintenance
07/01/2000 23:55:34 C1 H90210 CTL failure :CTL /CTRC
Recovery
06/29/2000 20:18:23 C1 I00724 HDU recovered(Unit-2,HDU-4) completed
Recovery
06/29/2000 20:15:10 C0 I00610 PS recovered(Unit-1,PS-0) completed
06/29/2000 19:30:23 C1 W06024 HDU alarm(Unit-2,HDU-4) :HDU /STRC
06/29/2000 19:30:23 C1 I00824 Spare HDU recovered(Unit-2,HDU-4) Messages indicated with
regard to Disk drive alarm
06/29/2000 19:30:23 C1 I15102 Data recovery completed(Unit-0,HDU-2)
(These do not require
06/29/2000 19:26:33 C1 I15002 Data recovery started(Unit-0,HDU-2) maintenance.)
06/29/2000 19:26:33 C1 I15A24 Dynamic sparing start(Unit-2,HDU-4)
06/29/2000 19:26:33 C1 I51024 D_PT error(HDU Unit-2,HDU-4)
Messages after the
06/29/2000 18:32:06 C0 W05010 PS alarm(Unit-1,PS-0) :PS unit is ready
06/15/2000 09:45:31 C0 I00100 CTL recovered(CTL-0) Recovery
06/15/2000 08:30:08 C1 I10000 Subsystem is Ready completed
06/15/2000 08:29:25 C1 W01000 CTL alarm(CTL-0) :CTL /CTRC

Messages before the
unit is ready

TRBL 04-0160-01
4.4 TrueCopy remote replication path confirm state

(1) Procedure for confirming log messages
By clicking the path of [Summary of the replacement parts state] in the main window, the
window is changed to the following one. And the details about the path state are displayed.
Also by clicking [TrueCopy Path Information] on the menu frame in the main screen, the
window is changed to the following window. And the details about the path state are
displayed.
Perform the maintenance operation for replacement and the recovery operation referring to
6.3 Procedure for Recovery from Path Blockade when the TrueCopy remote replication
Function Is Used (TRBL 06-1170).

TRBL 04-0170-01
4.5 The Priority Error Messages when W0100x CTL alarm is displayed
When both "W0100x CTL alarm" and the priority error messages listed below are displayed,
then ignore "W0100x CTL alarm", and take recovery actions according to the error messages.
(1) CUDG Detected Messages

Message
Message text
code
01824010 TWSI CACHE#0 information error [OWN_CTL]
0184A101 DCTL HP#00 transfer error [OWN_CTL]
0184A102 DCTL HP#00 transfer time out error [OWN_CTL]
0184A103 DCTL HP#00 transfer data compare error [OWN_CTL]
0184xxC1 DCTL DP#00-DFPC#0 transfer error [OWN_CTL]
DCTL DP#01-DFPC#1 transfer error [OWN_CTL]
DCTL HP#S1-HFPC#S1 transfer error [OWN_CTL]
DCTL HP#00-HFPC#0 transfer error [OWN_CTL]

TRBL 04-0180-01
Message
Message text
code
0184xxCA DCTL DP#00-DFPC#0 transfer error [OWN_CTL]
0184xxCB DCTL DP#00-DFPC#0 transfer error [OWN_CTL]
0184xxCC DCTL DP#00-DFPC#0 transfer error [OWN_CTL]

TRBL 04-0190-01
Message
Message text
code
0184xxCD DCTL DP#00-DFPC#0 transfer error [OWN_CTL]
0184xxCE DCTL DP#00-DFPC#0 transfer error [OWN_CTL]
0184xxCF DCTL DP#00-DFPC#0 transfer error [OWN_CTL]
01851101 CACHE#0 implementation check error in MP access [OWN_CTL]
01851201 CACHE#0 implementation check error in Shadow image [OWN_CTL]
01851401 CACHE#0 implementation check error in Shadow image & TWSI [OWN_CTL]
01851411 CACHE#1 implementation check error in Shadow image & TWSI [OWN_CTL]
01851501 CACHE#0 data line error [OWN_CTL]
01851502 CACHE#0 data line error [OWN_CTL]
01851601 CACHE#0 address line error [OWN_CTL]
01851701 CACHE#0 data compare error [OWN_CTL]
01851B01 CACHE#0 data compare error [OWN_CTL]
01851D01 CACHE#0 data compare error [OWN_CTL]
01852101 CACHE#0 ECC R/W data compare error [OWN_CTL]
01852201 CACHE#0 ECC circuit error [OWN_CTL]
0185220A CACHE#0 ECC circuit error [OWN_CTL]
0185220B CACHE#0 ECC circuit error [OWN_CTL]
0185220C CACHE#0 ECC circuit error [OWN_CTL]
0185220D CACHE#0 ECC circuit error [OWN_CTL]

TRBL 04-0200-01
Message
Message text
code
0185221A CACHE#0 ECC circuit error [OWN_CTL]
0185221B CACHE#0 ECC circuit error [OWN_CTL]
0185221C CACHE#0 ECC circuit error [OWN_CTL]
0185221D CACHE#0 ECC circuit error [OWN_CTL]

TRBL 04-0210-01
Message
Message text
code
01D57101 HFPC#0 MADDR error [OWN_CTL]
01D57301 HFPC#0 register data compare error [OWN_CTL]
01D57303 HFPC#0 hard status error [OWN_CTL]
01D57401 HFPC#0 transfer data compare error [OWN_CTL]
01D57601 HFPC#1 MADDR error [OWN_CTL]
01D57803 HFPC#1 hard status error [OWN_CTL]
01D5xxC1 HFPC #S1 loop back transfer error [OWN_CTL]
HFPC #0 loop back transfer error [OWN_CTL]
01D5xxC4 HFPC#S1 loop back transfer error [OWN_CTL]
01D5xxCA HFPC #S1 loop back transfer error [OWN_CTL]
01D5xxCB HFPC #S1 loop back transfer error [OWN_CTL]

TRBL 04-0220-01
Message
Message text
code
01D5xxCC HFPC #S1 loop back transfer error [OWN_CTL]
01D5xxCD HFPC #S1 loop back transfer error [OWN_CTL]
01D5xxCE HFPC #S1 loop back transfer error [OWN_CTL]
01D5xxCF HFPC #S1 loop back transfer error [OWN_CTL]
01xxxxB1 DFPC#0 loop initialize error [OWN_CTL]
DFPC#1 loop initialize error [OWN_CTL]
HFPC#S1 loop initialize error [OWN_CTL]
HFPC#0 loop initialize error [OWN_CTL]

TRBL 04-0230-01
Message
Message text
code
01xxxxBA DFPC#0 loop initialize error [OWN_CTL]
01xxxxBB DFPC#0 loop initialize error [OWN_CTL]
01xxxxBC DFPC#0 loop initialize error [OWN_CTL]
01xxxxBD DFPC#0 loop initialize error [OWN_CTL]
01xxxxD1 DFPC#0 soft reset error [OWN_CTL]
DFPC#1 soft reset error [OWN_CTL]
HFPC#S1 soft reset error [OWN_CTL]
HFPC#0 soft reset error [OWN_CTL]

TRBL 04-0240-01
Message
Message text
code

TRBL 04-0250-01
(2) Failure Messages

Message
Message text
code
H20Q00 DCTL CACHE ECC uncorrectable error [REG82001238, Bit29] (CTL-x, CACHE-y)
H21700 EDC error (Port-xy)
H3030x ECC uncorrectable error (CACHE-x)
H3050x ECC uncorrectable error (CTL-x)
H307xy DCTL CACHE ECC uncorrectable error [REG82001238, Bit29](CTL-x, CACHE-y)
H308xy DCTL ECC correction failed [MPU] [REG82001238, Bit28] (CTL-x, CACHE-y)
H30B0x CACHE uncorrectable ERR [OTH_CTL] (CTL-x)
H30Bxy CACHE uncorrectable ERR [OTH_CTL] (CTL-x, CACHE-y)
H30Gxx ECC uncorrectable error (CACHE-x)
H30Hxx ECC correction failed (CACHE-x)
H30Ixy CACHE uncorrectable ERR [OTH_CTL] (CTL-x, CACHE-y)
H30Jxy CACHE uncorrectable ERR [OTH_CTL] (CTL-x, CACHE-y)
H90320 Watch-dog time-out
HB0Cxx H-FPC is not detected (Port-xy)
HD220x CACHE error over (CACHE-x) [CRECT]
HE21xy I/F board type error (CTL-x, I/F board-y)
HF0103 Data transfer check error [RDSEGERR]
HF0105 Data transfer check error [WSEGPDEV]
HF0106 Data transfer check error [WSEGLOCK]
HF0107 Data transfer check error [CCPLUNERR]
HF0108 Data transfer check error [CCPLBAERR]
HF0109 Data transfer check error [PARLUNERR]
HF010A Data transfer check error [PARLBAERR]
HF010B Data transfer check error [QUEUEERR]
HF010C Data transfer check error [COWDRVERR]
HF010E Data transfer check error [DSTPOSERR]
HF010F Data transfer check error [SEGPOSOTH]
HF0117 Data transfer check error [BUFSGQATERR]
HF0118 Data transfer check error [WRBUFTODTY]
HF020x Directory check error (CTL-x)
HF0300 Data transfer check error [STGLUNERR]
HF0400 Data transfer check error [NTMPRD]
HH0E0x CACHE access error (CACHE-x) [PON]
HH270x I/F Board is not installed (CTL-x)
HH2900 Cache capacity reduced although copy function enable
HJ3Axy Unsupported CACHE detected (CTL-x, CACHE-y)
HZ0300 Not enough Cache memory to use QuickShadow function
HZ0H0x Directory reinitialization failed (CTL-x)
HZ0Pxx Cache capacity reduced although Cache Partition Manager enable

TRBL 04-0260-01
(3) Flash Detected Messages

Message
Message text
code
R20M00 DCTL CACHE uncorrectable ERR [REG82001238, Bit29](CTL-x, CACHE-y)
R302xy DCTL CACHE uncorrectable error [REG82001238, Bit29] (CTL-x, CACHE-y)
R312xy ECC uncorrectable error (CTL-z)
RA30xy CACHE size mismatch b/w. CTL (CACHE-x/y)
RA7700 CTL unit type cache size over
RA780x Unsupported CACHE (CACHE-x)
RA7A00 CACHE installation error (CACHE-0/1)
RA7B0x CACHE size get error (CACHE-x)
RB0B0x CACHE property error (CACHE-x)
RB0Cxy CACHE pair check error (CACHE-x/y)

TRBL 04-0270-01

Regarding Fibre Channel Failure
When a failure occurs in a Fibre Channel Link between a host computer and the disk array
subsystem, judge whether or not the failure has occurred in the interface portion of the disk
array subsystem following the flowchart shown below.
When the basic subsystem is RKM, refer to <When the basic subsystem is RKM> (TRBL 05-
0000) and when the basic subsystem is RKS, refer to <When the basic subsystem is RKS>
(TRBL 05-0010).
<When the basic subsystem is RKM>
Start of an investigation
Is it after HBA is No
exchanged?
Yes
Is LUN Manager unlocked and being
enabled? (Check it in http://IP
No
Address of Controller/lun_opt. Refer
to (1) World Wide Name of LUN
Manager (TRBL 05-0040).)
Yes
Check the WWN information of the port,
which LUN Manager is enabled, on the
Web. (Refer to (1) World Wide Name of
LUN Manager (TRBL 05-0040).)
Is there WWN before HBA is No

exchanged in the WWN information?
Yes Is the ALARM LED (RED) of the Yes
Please set WWN of LUN Manager again Fibre Channel onto the Interface
by the Storage Navigator Modular. Board on? (*1) Replace the Host Connector of the disk
(Refer to (2) Change of WWN of LUN No array subsystem. (See Replacement
Manager (TRBL 05-0050).) 2.2.8 Replacing Host Connector (REP
02-0770).)
No Check if a failure is recovered with

Fibre Channel?
Yes
END
Check the state of the Fibre Normal
Channel interface (*2).
Abnormal
The failure is not that of the Fibre Channel of
Take recovery action according to the the disk array subsystem. Investigate the
state of Fibre Channel Interface (*2) hostFibre Channel Switch, Host Adapter,
Fibre Channel Cable and GBIC(Host
Adapter, Fibre Channel Switch, etc.) to see if
the failure occurred in it.
*1 : This is the status of No. 8 in Table 8.2.8 of 8.2 (6) LED Indication Patterns on Interface Board (RKM) (TRBL 08-0260).
*2 : Refer to Table 8.2.8 of 8.2 (6) LED Indication Patterns on Interface Board (RKM) (TRBL 08-0260).

TRBL 05-0000-01
<When the basic subsystem is RKS>
Preparations before the procedure for investigating RKS regarding fibre channel failure
In this investigation, change the doubtful parts step by step and check interface is in Link Up state stably. While this investigation,
the Host computer connected to controller of PATH that a failure occurs cannot be used. So, before start this investigation, ask a
customer for the following steps.
(1) If customers system uses Alternate Path system, ask a customer to change a path to the controller of PATH that a failure
does not occur. Then, ask the customer not to fail back path automatically till this investigation is finished.
(2) If customers system doesnt uses Alternate Path system, ask a customer to stop using a host computer connected to the the
controller of PATH that a failure occurs.
Start of an investigation
No
Is it after HBA is exchanged?
Yes
Is LUN Manager unlocked and being
No
enabled? (Check it in http://IP
Address of Controller/lun_opt. Refer
to (1) World Wide Name of LUN
Yes
Check the WWN information of the port,

which LUN Manager is enabled, on the
Web. (Refer to (1) World Wide Name of
LUN Manager (TRBL 05-0040).)
Is there WWN before HBA is No

exchanged in the WWN information?
Yes
Please set WWN of LUN Manager again

by the Storage Navigator Modular. (Refer
to (2) Change of WWN of LUN
A
go to TRBL 05-0020

TRBL 05-0010-01
A from TRBL 05-0010
Is the ALARM LED (RED) of the

Yes
Fibre Channel onto the Interface
Board on? (*1)
Replace the Host Connector of the disk
No array subsystem. (See Replacement
2.2.8 Replacing Host Connector (REP
02-0770).)
No Check if a failure is recovered with

Fibre Channel?
Yes
END
Check the state of the Normal

Fibre Channel interface (*2).
Abnormal
The failure is not that of the Fibre Channel

of the disk array subsystem. Investigate
the hostFibre Channel Switch, Host
Adapter, Fibre Channel Cable and
GBIC(Host Adapter, Fibre Channel Switch,
etc.) to see if the failure occurred in it.
Are both two ports (port A-0 and Yes

port B-0) on a controller used? B
go to TRBL 05-0030
No
Take recovery action according to the

state of Fibre Channel Interface (*2)
*1 : This is the status of No. 8 in Table 8.2.7 of 8.2 (5-3) LED Indication Patterns on Control Unit (Fibre Channel)
(RKS) (TRBL 08-0230).
*2 : Refer to Table 8.2.7 of 8.2 (5-3) LED Indication Patterns on Control Unit (Fibre Channel) (RKS) (TRBL 08-0230).

TRBL 05-0020-01
B from TRBL 05-0020
Is port setting (Transfer Rate) of No

RKS "1Gbps" or "2Gbps?"
Yes Choose port setting (Transfer Rate) of
RKS either "1Gbps" or "2Gbps" according
to the setting of connected system
No Check if a failure is recoverd with

Fibre Channel?
Yes
END
Pull a Fibre Channel cable
out of port A-1 of RKS
Check the state of the Fibre Abnormal

Normal Take recovery action according to the
No Check if a failure is detected state of Fibre Channel Interface (*2).
with Fibre Channel
Yes
Investigate the hostFibre Channel Switch,
Host Adapter, Fibre Channel Cable and
GBIC(Host Adapter, Fibre Channel Switch,
etc.) to see if the failure occurred in it.
Did you check a state of Fibre Channel Yes

interface of port A-1 of RKS?
No
Pull a Fibre Channel cable out of port A-0

Connect a Fibre Channel Cable to both
of RKS, and connect a Fibre Channel
port A-0 and port B-0 of RKS
cable to port A-1
Check the state of the Fibre Normal

Abnormal
END
Replace the Control Unit of the
subsystem. (See Replacement 2.2.5
Replacing Control Unit (REP 02-0390).)
*1 : This is the status of No. 8 in Table 8.2.7 of 8.2 (5-3) LED Indication Patterns on Control Unit (Fibre Channel)
(RKS) (TRBL 08-0230).
*2 : Refer to Table 8.2.7 of 8.2 (5-3) LED Indication Patterns on Control Unit (Fibre Channel) (RKS) (TRBL 08-0230).

TRBL 05-0030-01
(1) World Wide Name of LUN Manager

[Password].
http://IP address of
controller/lun_opt
unlock and lock state display

enable and disable state display
Display of state of security of

each port, name of node, name of
port, and host group

TRBL 05-0040-01
(2) Change of WWN of LUN Manager
(a) Turn on the power supply.

(b) Start the Storage Navigator Modular and set the Active Mode in the Maintenance Mode(1).
(c) Click an icon of the disk array subsystem you want to set in the main window.
(d) On the unit window, click the [Logical Status] tab.
1 : For details of the setting method, refer to the System Parameter 1.1 (3) (b) Changing the Maintenance Mode
(SYSPR 01-0050).

TRBL 05-0050-01
(e) Select the [Access Mode] from the tree in the unit window by double clicking it and select the
[Host Group Security].
(f) Select a port, for which the WWN information is to be changed, from the [Host Group
Security] displayed on the right side of the window.

TRBL 05-0060-01
(g) Click the [Modify] button that is displayed at the lower right part of the window.
(h) Since the Modify Host Group Security dialog box is displayed, select [Enable] for the [Host
Group Security] and click the [OK] button.
(i ) The confirmation window is display. Click the [OK] button.
(j ) Make sure that the host group security of the specified port was changed to [Enable].

TRBL 05-0070-01
( k ) Double click the [Host Groups] in the tree, and then double click the port for which you have
validated the host group security. Select [WWN] by clicking the [000:G000].
(l ) Click the [Modify WWN Information] button that is displayed at the lower right part of the
window.
(m) Select a Name to be changed, and click the [Change] button.
(n) Enter the [Name], the [Port Name]. Then click the [OK] button.
c Name : Enter the name with half size alphabetic characters and/or numerals.
(Excluding \, /, : , , , ;, *, ?, ", <, >, | and ')
Spaces at the top or end are ignored.
An identical name cannot be used in an identical Port.
d Port Name : Enter the Port Name with sixteen hexadecimal numerals

TRBL 05-0080-01
(o) Click the [OK] button on WWN Information Property.

(p) The confirmation window is display. Click the [OK] button.

TRBL 05-0090-01
Chapter 6. Details of Recovery Methods

6.1 Error recovery methods
Table 6.1.1 shows error recovery methods(1). Errors are classified into power-on errors,
operation errors, data recovery errors, and power-off errors.
Table 6.1.1 Error Recovery Methods for Each Error

No. Classification Description Reference page
1 The subsystem goes Both controllers are blocked in the dual controller configuration. 6.1.1 System down (TRBL
down. Only one controller is blocked in the single or dual controller configuration. 06-0020)
2 POWER LED on the subsystem lighted off because a Drive short-circuit failure (on Chapter 8. Trouble Analysis
the Basic Chassis or the Additional Chassis) occurred. by LED Indication (TRBL 08-
0000)
3 The subsystem does A loading of information from a Disk Drive failed. 6.1.2 The subsystem does not
not become ready. become ready : Case 1
(Loading failure) (TRBL 06-
0050)
4 POWER LED on the subsystem lighted off because a Drive short-circuit failure (on Chapter 8. Trouble Analysis
the Basic Chassis or the Additional Chassis) occurred. by LED Indication (TRBL 08-
0000)
5 The failure occurred The user data in the cache memory was lost because data stored in the cache 6.1.3 The failure occurred
immediately after memory volatilized. (A forced parity correction is required(*1).) immediately after being ready
being ready. (Forced parity correction)
(TRBL 06-0060)
6 The power cannot Planned shutdown cannot be performed because the number of PIN data is too 6.1.4 The power cannot be
be turned off. large. (due to Disk Drive and Controller error.) turned off : Case 1 (The
number of PIN data is too
large) (TRBL 06-0420)
7 An attempt was made to save PIN data to the Disk Drive during planned shutdown 6.1.5 The power cannot be
but failed because a hardware error occurred. turned off : Case 2 (Hardware
failure) (TRBL 06-0450)
8 Planned shutdown cannot be performed because all the Disk Drives to which 6.1.6 The power cannot be
inheritance information is to be saved disappeared due to a DMA double error or a turned off : Case 3 (Control Unit
Disk Drive quintuple error. failure) (TRBL 06-0470)
9 Planned shutdown cannot be performed because PIN data cannot be saved due 6.1.7 The power cannot be
to a Cache memory error, etc. turned off : Case 4 (Cache
memory failure) (TRBL 06-
0490)
*1 : When user data is lost because of volatilization of data in the cache memory, restore it in the procedure given in
No.5.
1 : Since the latest state of the unit is always referenced in this recovery operation, turn on the Page Refresh Mode
of the WEB. (Click the [ON] button to indicate [OFF].)
If the power is turned on again in the recovery operation, the WEB connection between the unit and browser is
cut out, make it again. (Press the update button of the browser.)

TRBL 06-0000-01
No. Classification Description Reference page

10 Data recovery does Forced recovery was performed because a RD error occurred in the copy source 6.1.8 Data recovery does not
not terminate during a correction copy. terminate normally : Case 1
normally. (Read error) (TRBL 06-0510)
11 Data recovery terminated abnormally because a Disk Drive error occurred in the 6.1.9 Data recovery does not
copy source during a correction copy. terminate normally : Case 2
(Disk Drive failure) (TRBL 06-
0520)
12 Data recovery terminated abnormally because a Spare Disk error occurred during 6.1.10 Data recovery does not
a copyback. terminate normally : Case 3
(Spare Disk Drive failure)
(TRBL 06-0540)
13 A failure occurred The number of PIN segments exceeded its threshold value. (Actions to be taken 6.1.11 A failure occurred
during operation. when PIN OVER occurs) during operation : Case 1 (PIN
over) (TRBL 06-0550)
14 Data containing a LA/LRC error was detected. 6.1.12 A failure occurred
during operation : Case 2
(LA/LRC error) (TRBL 06-
0570)
15 Actions to be taken when a LU blockade occurs. 6.1.13 A failure occurred
during operation : Case 3 (LU
blockade) (TRBL 06-0590)
16 A loop failure occurred, however, the failed part cannot be located. 6.1.14 A failure occurred
during operation : Case 4 (Loop
failure) (TRBL 06-0600)
17 The command for reassignment was sent from a host computer to an LU of RAID 6.1.15 A failure occurred
0. during operation : Case 5
(Incomplete writing) (TRBL 06-
1110)
18 Copy-on-write When Copy-on-write SnapShot is restored, a write error was recorded to the primary VOL to 6.1.16 A failure in Copy-on-
SnapShot failure be copied since the unreadable area exists on the pool side. write SnapShot occurs (TRBL
occurred. 06-1120)

TRBL 06-0010-01
6.1.1 System down

[WEB Information Message display]
MM/DD/YYYY HH:MM:SS Cx Hxxxxxx {{{{{{{ : /
Date Time Detect Controller#

xxxxx, {{{{{{{ : / Optional
NOTE : When the READY LED lights off, refer to Chapter 8. Trouble Analysis by LED
Indication (TRBL 08-0000) to recover the failures.
The recovery method shown below is for the case where blockades of both
Controllers in a dual Controller configuration occur.
The ALARM LED on the front side of the basic frame comes on and the both
controllers are detached. As to the CALM LED on the controller PCBA, only
the CALM LED on one of the controllers, in which the failure was detected
earlier, comes on.
Make sure on which controller the CALM LED is on because the recovery work
is to be done starting from the controller whose CALM LED is on.
[Recovery method]
START
Collect the memory dump (*1).
Turn off the main switch (*2).
When restarting the subsystem, power it on after

Turn on the main switch.
waiting for a minute or more from the power off.
Does the READY LED light up
within 10 minutes? No Did you repeat the powering off and No
When it is high-speed blinking, wait on of the main switch three times?
up to 30/50 minutes.
Yes
Yes Confirm the message displayed on the
WEB, and identify the failed part.
Turn off the main switch.
No
Was the failed part identified?
No Is the power off when the main switch
is turned off? Yes
Yes Turn off the main switch.
Turn on the main switch and make sure
that the READY LED comes on. Replace the failed component (*3).
When it is high-speed blinking, wait up
to 30/50 minutes.
Recover from the failure according the
WEB message. Is the READY LED on?
Yes
When it is high-speed blinking, wait
up to 30/50 minutes.
No
END
B To TRBL 06-0030 B To TRBL 06-0030
*1: For the Error trace with power on, refer to 7.5 Collecting Memory Dump (TRBL 07-0130).
*2: When the ALARM LED does not go out five minutes or longer after the main switch is turned off, turn off the AC
input power switch.
*3: For the replacement of the failed component, refer to Replacement Chapter 2. Parts Replacement (REP 02-
0000).

TRBL 06-0020-01
From TRBL 06-0020 B
The contents of an obstacle are checked by the

message of WEB. Is it applied to following either? No
c H20100 Parity generation LA error[DRR] C To TRBL 06-0040
d HJxxxx Microprogram error [XXX]
Yes
When doing the following works,
get a permission of the Technical
Support Center.
Turn off the all AC input Power Switch
Pull out the both controllers and wait for ten
Insert the both controllers in their original
Turn on the all AC input Power Switch(*1).
WARNING LED comes blinking.
Make a connection to the WEB and

make sure of the lost LU.
Make a forced parity correction after the

subsystem enters the Ready status.
(For the forced parity correction, refer to
Item 6.1.3 The failure occurred
immediately after being ready (Forced
parity correction) (TRBL 06-0060).)
END
*1: If two or more Disk Drive are not mounted on RKAJ in the Floor models (RKM/RKS+RKAJ+H2J), turn off the AC input
power switch of RKAJ.

TRBL 06-0030-01
From TRBL 06-0030 C

Recovery the forced parity.
When doing the following works, get a
permission of the Technical Support Center.
Turn off the all AC input Power Switch
Replace the both Control Unit.
Turn on the all AC input Power Switch(*1).
Displayed the following message.

MM/DD/YYYY HH:MM:SS Cx W12000 User data lost :MANUAL/TRC
The above is displayed and forced parity correction is started(*1).

Extension of cache data that has not been written on
the disk cannot be decided because the both controllers
were replaced. Therefore, a message notifying of the
user data lost is displayed concerning all the LUs.

Item 6.1.3 The failure occurred
immediately after being ready (Forced
parity correction) (TRBL 06-0060).)
END
*1 : If two or more Disk Drive are not mounted on RKAJ in the Floor models (RKM/RKS+RKAJ+H2J), turn off the AC input

TRBL 06-0040-01
6.1.2 The subsystem does not become ready : Case 1 (Loading failure)
(Information could not be loaded from the Disk Drive.)

MM/DD/YYYY HH:MM:SS Cx RB8400 Download fail :MANUAL
[Recovery method]
START
Collect the memory dump.

(7.5 Collecting Memory Dump (TRBL 07-0130))
Main switch OFF
Main switch ON
Does the same phenomenon recur? No
Yes
Main switch OFF
Reinstall microprogram(*1).
Yes
Initialization of the configuration
information(*2)(*3).
Set system again.

Set file system, etc. (by host operation)
Recover user data with backup data. (user
backup)
Main switch OFF
Main switch ON

Yes Make sure that the READY LED on the Front
Bezel is on.
When it is high-speed blinking, wait up to 30/50
minutes.
Call the Technical Support Center for coping with Call the Technical Support Center for coping with
troubles in order to request to analyze the troubles in order to request to analyze the
memory dump that has been got. memory dump that has been got.
END END
*1 : For the installation procedure of the microprogram, refer to the Microprogram Chapter 1. Installation of
Microprogram (MICRO 01-0000).
*2 : If this operation is executed, all the data in the Disk Drive are deleted (the RAID group and LU definition are
initialized).
*3 : For initialization of the information on configuration, refer to 6.2 Initialization procedure for configuration
information (TRBL 06-1130).

TRBL 06-0050-01
6.1.3 The failure occurred immediately after being ready (Forced parity correction)
A failure occurred immediately after the subsystem had been started up. The user data in the
cache memory was lost because data stored in the cache memory volatilized.

MM/DD/YYYY HH:MM:SS Cx xxxxxx Forced parity correction LU is detected :MANUAL
< Explanation >

A forced parity correction is made in order to synchronize parities in the disk array subsystem
when data is lost because of volatilization of data in the cache memory caused by a power
failure, etc. (when the subsystem cannot execute the deliberate shutdown).
The forced parity correction is made for each LU. Each LU can be in the following statuses.
< Notes on making forced parity correction >

y The restoration is made using the maintenance function of Storage Navigator Modular. For
the procedure concerned, refer to 10.2.4 Displaying Logical Unit Failure Data Information
(TRBL 10-0250).
y For a failure of a part other than the drive that occurs during forced parity correction, refer
to the Replacement 2.1 Locations of Replacement Components (REP 02-0000). For a
drive failure, refer to the Replacement 2.2.1 Replacing Disk Drive (REP 02-0050).
y The dynamic sparing cannot be instructed in the Storage Navigator Modular during the
forced parity correction. When the dynamic sparing is required because the threshold
value is exceeded, the dynamic sparing is not performed but the correction copy is made
through a detachment of the drive concerned.
y The copy back cannot be instructed in the Storage Navigator Modular during the forced
parity correction. When the copy back is required, the copy back is started automatically
after the forced parity correction is completed.
y When a drive failure, PIN Over or incomplete write occurs during the forced parity
correction, the data check and the operation using the Storage Navigator Modular are
required again.
y For the LU status or its transfer in the forced parity correction described in the maintenance
operation flow, refer to < Change of the status in the forced parity correction > (TRBL 06-
0380). Also, for the standard time required for the recovery, refer to < Standard time
required for the forced parity correction > (TRBL 06-0400).
y The forced parity correction recovers one LU per Control Unit. Therefore, if the LU needs
multiple forced parity correction, the order of the forced parity correction should be
determined by checking the Control Unit in charge of each LU (Refer to (e) Execution of
forced parity correction (TRBL 06-0260)).

TRBL 06-0060-01
y If the data on the Cache memory is volatilized due to a power failure within one minute
after performing the following work, all LUs may be required for the forced parity
correction.
c The forced parity correction is performed using the maintenance function of the Storage
Navigator Modular.
d The pair operation by RAID Manager
y If the data on the Cache memory is volatilized due to a power failure within one minute
after performing the setting of the system parameter configuration information in the
Storage Navigator Modular, the set contents may not be reflected. Check the
configuration. Be sure to check the configuration when a power failure occurs. If the
configuration is not reflected, set the configuration information again.

TRBL 06-0070-01
(1) Data reading/writing instructed by a host

y An LU, a status of which concerning the forced parity correction is Being Restored or On
standby, can be instructed by a host to be read or written, however, performance of the
host I/Os may be lowered because the forced parity correction is in progress.
y When an LU, a status of which concerning the forced parity correction is Being Restored,
exists in the disk array subsystem, performance of host I/Os is lowered.
(2) Relations between statuses of forced parity correction and operations of the other functions
y The operation of other functions for the LU concerned is partially restricted depending on the
status of the LU which is performing the forced parity correction.
Status of forced parity correction

No. Instruction function Parity correcting / Uncorrected / Skip /
Waiting parity correction Correction aborted Restored
1 The delete of LU {
2 LU Unification {
3 The change of the controller in charge of a default LU { { {
4 Instruction to make an LU resident { { {
5 LU mapping { { {
6 Setting a prefetch size { { {
7 ShadowImage in-system replication pair formation {(*1) {
8 ShadowImage in-system replication pair restoration {(*2) {
9 TrueCopy remote replication pair formation {(*1) {
10 TrueCopy remote replication pair restoration {(*2) {
11 Copy-on-write SnapShot pair formation(*3) { {
12 Copy-on-write SnapShot pair restoration(*4) {
13 Command device registration { {
14 LUN Manager setting { { {
15 Password protection { { {
16 Format instruction {
17 Hot replacement of the microprogram {
18 Pseudo deliberate shutdown { { {
19 Data Retention Utility { { {
20 Instruction to make forced parity correction { {
21 Instruction to skip forced parity correction { {
22 Instruction to abort forced parity correction {
23 The delete of RAID Group {
*1 : When a status of an LU concerning the forced parity correction for a secondary LU is On Standby or Being
Restored, a pair cannot be formed.
*2 : When a status of an LU concerning the forced parity correction for a primary LU is On Standby or Being
Restored, a pair cannot be formed.
*3 : When a status of either a P-VOL or a POOL (when two or more P-VOLs/POOLs exist, any one of them) is
Unrestored or Unrestored 2, a pair cannot be formed.
When a POOL (when two or more POOLs exist, any one of them) is in the On Standby or Being Restored
status, a pair cannot be formed.
*4 : The restoration cannot be made unless a status of a P-VOL and a POOL (when two or more P-VOLs/POOLs
exist, all of them) is Skip or Restored.

TRBL 06-0080-01
y In contrast with the above, instructions to make the forced parity correction are partially
restricted while the other function is operating.
Possibility of forced
No. Function in operation Description
parity correction
1 Unification LU Partially impossible Though an instruction to make the restoration for a child LU
cannot be issued, the restoration instructed to be made for a
parent LU is also applied to a child LU.
2 Format instruction Impossible An instruction to make the restoration cannot be issued to an
LU being formatted.
3 Microprogram hot replacement Impossible An instruction to make the parity correction cannot be issued
during replacement of the microprogram.
4 Pseudo deliberate shutdown Impossible An instruction to make the restoration cannot be issued
because the disk array subsystem is shut down deliberately.
(3) Process of forced parity correction

y If data in the cache memory volatilizes again because the subsystem is powered off without
execution of the deliberate shutdown when a power failure, etc. occurs, all the LUs are
restored by forced parity correction.
y When a failure occurs in a Control Unit that is making the forced parity correction, the
restoration is taken over by a mate Control Unit and continued. However, when the mate
Control Unit is making the forced parity correction, it stands by for the restoration taken
over. When the failed Control Unit is recovered, it makes the parity correction.

TRBL 06-0090-01
< Forced Parity Collection Maintenance Flow >

Perform the maintenance operation for the forced parity collection following the flow shown
below.
START
Has a failure occurred before the No

forced parity collection?
Yes
Has the following failure occurred?
PIN over y Drive failure
occurrence
y PIN over occurrence
Drive failure
Perform the recovery method following Perform the recovery method following
[Recovery method-7] : PIN over has [Recovery method-6] : The drive
occurred before the forced parity blockade has occurred before the forced
collection. (TRBL 06-0240). parity collection. (TRBL 06-0230).
Was the system parameter set in the

Storage Navigator Modular just No
before the power failure occurred?
Yes
Check the configuration. If the
configuration is not reflected, set the
configuration information again.
Perform the forced parity correction?

If performed, it can be used only
when the data warranty is acquired by No
the users confirmation of the data
consistency check. Instruct to skip the forced parity
Yes correction.
Perform the recovery method following (The format and the restoration from the
[Recovery method-1] : Making a backup data are required for the LU
forced parity correction. (TRBL 06- which indicated to skip the forced parity
0110). correction.)
END
Did a failure occur during the forced No
parity collection?
Yes END
Did the following failure occur?
PIN over y Drive failure Incomplete write
occurrence y PIN over occurrence occurrence
y Incomplete write
Drive failure
Perform the recovery method following Perform the recovery method following Perform the recovery method following
[Recovery method-4] : PIN over [Recovery method-3] : Drive blockade [Recovery method-5] : Incomplete write
occurred during the forced parity occurred during the forced parity occurred during the forced parity
correction. (TRBL 06-0190). correction. (TRBL 06-0140). correction. (TRBL 06-0210).
END END END

TRBL 06-0100-01
[Recovery methods]
[Recovery method-1] : Making a forced parity correction.
The forced parity correction resynchronizes data in Disk Drives, however,
it cannot restore the data completely. Ask a user to verify the data and
restore data that could not be restored using the backup data.
START
Connect the Web (Refer to Chapter 3. Before Starting WEB Connection (TRBL 03-0000)) and
make sure of existence of an LU which requires the forced parity correction through the following
information message.
MM/DD/YYYY HH:MM:SS Cx W48000 Forced parity correction LU is detected : MANUAL/STRC
Connect Storage Navigator Modular. (< Procedure given in windows > (TRBL 06-0250))
Perform the forced parity correction. ((e) Execution of forced parity correction (TRBL 06-0260))
The WARNING LED on the Front Bezel goes out.
Since a host computer becomes able to access all LUs from this point of time,
a user becomes able to verify files(*1).
Is the data confirmation acquired resulting No

A
from the users file test?
Yes To TRBL 06-0120
Make sure that the forced parity correction has been started by displaying the following information
message(*2).
MM/DD/YYYY HH:MM:SS Cx I1GB00 Forced parity correction is started (LU-xxxx)
Make sure that the forced parity correction has been completed by displaying the following
MM/DD/YYYY HH:MM:SS Cx I1GC00 Forced parity correction is completed (LU-xxxx)
Display the following Information Message and check that there is no target LU for the forced parity
correction.
MM/DD/YYYY HH:MM:SS Cx I6DJ00 Forced parity correction LU is gone
END
*1 : When a drive detachment, pin over, or incomplete writing occurs during a period from the verification of files by a
user to the completion of the forced parity correction, the verification of files by the user must be done again.
When a failure occurs, take recovery actions referring to [Recovery method-3] : Drive blockade occurred during
the forced parity correction. (TRBL 06-0140), [Recovery method-4] : PIN over occurred during the forced parity
correction. (TRBL 06-0190), [Recovery method-5] : Incomplete write occurred during the forced parity
correction. (TRBL 06-0210).
*2 : For a standard time required for the forced parity correction, refer to < Standard time required for the forced
parity correction > (TRBL 06-0400).

TRBL 06-0110-01
From TRBL 06-0110 A
Suspend the forced parity correction.

(Refer to [Cancellation of forced parity correction] (TRBL 06-0340))
Perform the backup restoration.

(Cancel all the data and retry from the LU format (*1).)
END
*1 : There may be a case that the LU formatting fails. In this case, request a user to check if a sense code is reported
in the log of a host computer. When the reported sense code is 05-9552 or 05-9577, the LU concerned is an
object of ShadowImage in-system replication, TrueCopy remote replication or Copy-on-write SnapShot.
Therefore, request a user to release the pair and execute the LU formatting again after it is released (refer to
System Parameter 3.3 Setting of LU [Procedure e-F] Formatting LU (SYSPR 03-0280)).
Also, the backup restoration cannot be done for the LU whose access attribute is set as other than Read/Write by
Data Retention Utility because it cannot be formatted or written.

TRBL 06-0120-01
[Recovery method-2] : A forced parity correction is not made (a forced parity correction is
skipped).
Because a forced parity correction is not made, data in a Disk Drive are
not synchronized and an LA error, etc. may occur. Issue an instruction
to skip the forced parity correction from Storage Navigator Modular,
format the LU, and then make a backup restoration.
START
Connect the Web (Refer to Chapter 3. Before Starting WEB Connection (TRBL 03-0000)) and
make sure that the following information message is displayed.
MM/DD/YYYY HH:MM:SS Cx W48000 Forced parity correction LU is detected :MANUAL
Connect Storage Navigator Modular. (< Procedure given in windows > (TRBL 06-0250)).
Skip the forced parity correction. ([ When skipping the forced parity correction ] (TRBL 06-0310))
correction.
MM/DD/YYYY HH:MM:SS Cx I6DJ00 Forced parity correction LU is gone :MANUAL
Make the backup restoration. (Abandon all data and then restore it starting from the LU formatting(*1).)
END

TRBL 06-0130-01
[Recovery method-3] : Drive blockade occurred during the forced parity correction.
When a Disk Drive is detached during forced parity correction, the
restoration is interrupted and a drive recovery action is taken. When
a drive, which belongs to a RAID group including an LU for which the
forced parity correction is being made, is detached, a status of the LU
concerned is changed to Unrestored 2. The LU status in the other
RAID Group is not transferred.

MM/DD/YYYY HH:MM:SS Cx W060XX HDU alarm (Unit-xx, HDR-yy) :HDU /STRC
START
The WARNING LED on the front bezel blinks.
Make sure that the drive detachment has occurred through the following information message.
MM/DD/YYYY HH:MM:SS Cx W060XX HDU alarm(Unit-xx, HDU-yy) HDU /STRC
MM/DD/YYYY HH:MM:SS Cx I1GD00 Forced parity correction is stopped [HDU alarm]
Is the following message displayed in the Web window? No

Uncorrectable forced parity correction LU is detected. B
Yes To TRBL 06-0160
Statuses of some LUs were changed to Unrestored 2 in which
no host access is accepted. No
C
Do you want to make the host access acceptable immediately?
To TRBL 06-0170
Yes
Instruct the LU in the Unrestored 2 status to skip the restoration using
Storage Navigator Modular.
Since the host access to any of the LUs becomes possible from this point of time, have the files
verified again by a user.
Is the data confirmation acquired resulting No D

from the users file test?
Yes To TRBL 06-0180
It can be confirmed that LUs in the Unrestored 2 status have disappeared through the following
MM/DD/YYYY HH:MM:SS Cx IXXXXX Uncorrectable forced parity correction LU is gone
Replacing Disk Drive (Refer to the Replacement 2.2.1 Replacing Disk Drive (REP 02-0050)).
A To TRBL 06-0150

TRBL 06-0140-01
From TRBL 06-0140 A
Make sure that the drive restoration has been completed through the following information message.
MM/DD/YYYY HH:MM:SS Cx I007XX HDU recovered (Unit-xx, HDU-yy)
The status of the LU is changed from Unrestored 2 to "Restored" owing to the completion of the
drive recovery(*1). When the LU in the skip status exists, perform the forced parity correction
again.
Display the following Information Message and check that the forced parity correction per LU is
completed.
correction.
END
*1 : An LU that conforms to any of the following conditions does not enter the Restored status and remains in the
Skip status.
If an LU remaining in the Skip status exists, issue an instruction to make the forced parity correction newly.
y An LU of RAID 1+0
y A unified LU a part of which is included in a RAID group having a drive detachment
y An LU whose parity group is deeper than 1

TRBL 06-0150-01
From TRBL 06-0140 B
MM/DD/YYYY HH:MM:SS Cx I007XX HDU recovered (Unit-xx, HDU-yy)
completed.
correction.
Otherwise, ask a user to verify files.
END

TRBL 06-0160-01
From TRBL 06-0140 C
MM/DD/YYYY HH:MM:SS Cx Cx I007XX HDU recovered (Unit-xx, HDU-yy)
After the Disk Drive is recovered, issue an instruction to skip the restoration to the LU in the
Unrestored 2 status using Storage Navigator Modular.
The status is changed to Restored when the drive recovery is completed(*1).
If an LU remaining in the Skip status exists, issue an instruction to make the parity correction newly.
completed.
correction.
END
Skip status.
If an LU remaining in the Skip status exists, issue an instruction to make the forced parity correction newly.
y An LU of RAID 1+0

TRBL 06-0170-01
From TRBL 06-0140 D
Suspend the forced parity correction.

(Refer to [Cancellation of forced parity correction] (TRBL 06-0340)).
Perform the backup restoration.

(Cancel all the data and retry from the LU format (*1).)
END

TRBL 06-0180-01
[Recovery method-4] : PIN over occurred during the forced parity correction.
When a pin over occurs, the status of the LU, the forced parity
correction for which has been instructed to be made, is changed to
Unrestored.

MM/DD/YYYY HH:MM:SS Cx W41100 PIN over [PNLEVLOV]
MM/DD/YYYY HH:MM:SS Cx Ixxxxx Forced Parity correction stopped [Too Many PINs] (LU-xxxx)
START
The following Information Massage is displayed. Check PIN over.

MM/DD/YYYY HH:MM:SS Cx I1GF00 Forced parity correction is stopped [Too Many PINs] (LU-xxxx)
Take a recovery action referring to 6.1.11 A failure occurred during operation : Case 1 (PIN over)
(TRBL 06-0550).
However, skip the forced parity correction for the LU other than [Status] is Normal on the Parity
Correction window of Storage Navigator Modular before replacing the Disk Drive. ((g) Select
whether or not to make the forced parity correction. (TRBL 06-0290).)
Did you make recovery from the failure with any of the
following methods to eliminate the pinned data?
y Powering off and on of the subsystem
Yes
y Replacing of a Control Unit (Refer to the Replacement A
2.2.5 Replacing Control Unit (REP 02-0390))
To TRBL 06-0200
y Replacing of a Disk Drive (Refer to the Replacement 2.2.1
Replacing Disk Drive (REP 02-0050))
No
y Recovery conducted by the Technical Support Center for coping with problems
y Recovery by means of an LU formatting(*1)
END
*1 : To perform recovery by the LU format, skip the LU which is in the not performed status in the Storage Navigator
Modular before the LU format.

TRBL 06-0190-01
From TRBL 06-0190 A
Issue an instruction to make the forced parity correction for the LU in the Skip status using Storage
Navigator Modular.
completed.
correction.
END

TRBL 06-0200-01
[Recovery method-5] : Incomplete write occurred during the forced parity correction.
When an incomplete writing occurs, the status of the LU, the forced
parity correction for which has been instructed to be made, is changed
to Unrestored 2.

MM/DD/YYYY HH:MM:SS Cx W0G0HH Unreadable PIN detected (Unit-x,HDU-y) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx I153HH Data recovery partial (Unit-x, HDU-y)
MM/DD/YYYY HH:MM:SS Cx I1GE00 Forced parity correction is stopped [Too Many Unreadable PINs] (LU-xxxx)
START
The following Information Message is displayed. Check if incomplete write occurred.

MM/DD/YYYY HH:MM:SS Cx W0G0XX Unreadable PIN detected (Unit-x, HDU-y) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx I153XX Data recovery partial (Unit-x, HDU-y)
MM/DD/YYYY HH:MM:SS Cx I1GE00 Forced parity correction is stopped [Too Many Unreadable PINs] (LU-xxxx)
Skip the LU which is in the Correction Aborted status due to incomplete write in the Storage Navigator
Modular.
Take a recovery action according to the information message.
Did you make recovery from the failure with any of the
following methods to eliminate the pinned data?
y Replacing of a Control Unit (Refer to the Replacement No
2.2.5 Replacing Control Unit (REP 02-0390))
y Replacing of a Cache Unit (Refer to the Replacement
2.2.6 Replacing Cache Unit (REP 02-0540))
Yes
Recovery by means of an LU formatting(*1)
END
Perform the forced parity correction for the LU which is in the Skip status in the Storage Navigator Modular.
Display the following Information Message and check that the forced parity correction per LU is completed.
A To TRBL 06-0220
*1 : When making a restoration by means of the LU formatting, instruct the LU in the Uncorrected status to skip the
parity correction using Storage Navigator Modular before formatting the LU.

TRBL 06-0210-01
From TRBL 06-0210 A
Display the following Information Message and check that there is no target LU for the forced parity correction.
END

TRBL 06-0220-01
[Recovery method-6] : The drive blockade has occurred before the forced parity collection.
If the Disk Drive has been blocked before the forced parity collection,
the drive restoration is already operated.
The LU status in which the drive restoration has already operated is
changed to not performed 2. The other LU status is changed to not
performed.

MM/DD/YYYY HH:MM:SS Cx W060XX HDU alarm (Unit-xx, HDR-yy) :HDU /STRC
START
Make sure that the drive detachment has occurred through the following information message.
MM/DD/YYYY HH:MM:SS Cx W060XX HDU alarm(Unit-xx, HDU-yy) : HDU /STRC
Instruct the LU in the Unrestored 2 status to skip the restoration using

Since the host access to any of the Lus that instruct to skip becomes possible from this point
of time, have the files verified again by a user.
correction.
MM/DD/YYYY HH:MM:SS Cx I007XX HDU recovered (Unit-XX, HDU-yy)
END

TRBL 06-0230-01
[Recovery method-7] : PIN over has occurred before the forced parity collection.
If PIN over occurred, change the LU in which PIN over occurred to not
performed status.

MM/DD/YYYY HH:MM:SS Cx W060HH HDU alarm(Unit-xx,HDR-yy) :HDU /STRC
START
The following Information Massage is displayed. Check PIN over.

Take a recovery action referring to 6.1.11 A failure occurred during operation : Case 1 (PIN over)
(TRBL 06-0550).
END

TRBL 06-0240-01
< Procedure given in windows >
(a) Connect the Web. (Refer to Chapter 3. Before Starting WEB Connection (TRBL 03-0000).)
(b) Check that there is LU for which the forced parity correction is necessary by the W48000
message in the WEB window.
(c) Connect Storage Navigator Modular.

(i) Start the Storage Navigator Modular and set the operation mode in the Management
Mode.
For details of the setting method, refer to the System Parameter 1.1 (3)-(b) Changing the
Maintenance Mode (SYSPR 01-0050).
(ii) Click an icon of the disk array subsystem you want to set in the main window.

TRBL 06-0250-01
(d) Click the [RAID Groups] tab after Clicking the [Logical Status] tab in the unit window.
(e) Execution of forced parity correction

Since the LU required for the forced parity correction is displayed, execute the forced parity
correction.
Select [Settings] [Logical Unit] [Parity Correction] in this order.

TRBL 06-0260-01
Status Symbol of Storage Status seen from a

Meaning Recovery method
Navigator Modular host
Uncorrected Uncorrected : A status in which a Perform the forced parity correction or skip
A status in which the subsystem is waiting for an host cannot instruct in the Storage Navigator Modular according
instruction to make or skip the forced parity the LU to read or to < Procedure given in windows > (TRBL
correction issued by Storage Navigator Modular. write. 06-0250).
Parity Correcting (n%) Correcting : A status in which a
A status in which Storage Navigator Modular has host can instruct the
issued an instruction to make the forced parity LU to read or write.
correction and the restoration is in progress.
Waiting Parity Waiting : A status in which a
Correction(o) (n%) A status in which Storage Navigator Modular has host can instruct the
correction and is waiting for making of the
restoration.
Correction Skipped Skip : A status in which a Make an LU formatting (refer to System
A status in which Storage Navigator Modular has host can instruct the Parameter [Procedure e-F]Formatting LU
issued an instruction to skip the forced parity LU to read or write. (SYSPR 03-0280.) and backup restoration.
correction.
Restored : A status in which a
A status in which Storage Navigator Modular host can instruct the
correction and the restoration has been
completed.
Correction Aborted Uncorrected 2 : A status in which a c Connect the WEB (refer to Chapter 3.
A status in which the forced parity correction is host cannot instruct Before Starting WEB Connection (TRBL
interrupted because of a drive detachment the LU to read or 03-0000).).
although Storage Navigator Modular has issued write. d Replace the blocked Disk Drive referring
an instruction to make the restoration. to the Information Message on the WEB
(refer to Replacement 2.2.1 Replacing
Disk Drive (REP 02-0050).).
e Skip the forced parity correction
according to < Procedure given in
windows > (TRBL 06-0250) (refer to
[ When skipping the forced parity
correction ] (TRBL 06-0310).).
f Execute the forced parity correction
according to
< Procedure given in windows > (TRBL
06-0250).
(f) Status checking of the logical unit for the forced parity correction.
y When the status of the logical unit is Uncorrected
(i) Because the dialog, indicating that the LU which needs the forced parity correction exists,
is displayed, click the [OK] button. The parity correction process is interrupted by
clicking the [Cancel] button.

TRBL 06-0270-01
y When the status of the logical unit is other than Uncorrected

(i) Because the dialog, indicating that the logical unit for the forced parity correction target
does not exist, is displayed, click the [OK] button.
(ii) Check the LU which needs to execute the forced parity correction referring to the status
of the logical unit.
(iii) When there is the LU to be executed by the forced parity correction, select [Setting]
[Logical Unit] [Parity Correction] after specifying the logical unit of the target.

TRBL 06-0280-01
(g) Select whether or not to make the forced parity correction.

[ When making the forced parity correction ]
When aborting the forced parity correction while it is in progress, refer to [ Cancellation of
forced parity correction ] (TRBL 06-0340).
(i) Sort the LUs in order of making forced parity correction.(1)(2)
(ii) When the sort is completed, select the [Start] radio button and click the [OK] button.
(iii) Click the [OK] button.
1 : The forced parity correction operates LU one by one in order for each Control Unit in charge of LU. Therefore,
the Control Unit in charge of the LU which performs the forced parity correction should be considered to decide
the sorting order.
2 : The forced parity correction is performed in order of the sorted LU.
However, if the LU belongs in the same RAID Group, it may not be executed in the sorted order because the
process is not performed in each Control Unit.
If the forced parity correction order of the LU which belongs in the same RAID Group needs to be assured, select
one LU following (g). For the remaining LU, follow the procedure for the indication of the forced parity correction
from skip status or completion of correction, and indicate the addition of the forced parity correction LU.

TRBL 06-0290-01
(iv) Click the [OK] button.

TRBL 06-0300-01
[ When skipping the forced parity correction ]

(i) Select the [Skip] radio button and click the [OK] button.
(ii) Click the [OK] button.
(iii) Click the [OK] button.
(h) Refer to a message in the Web window.

TRBL 06-0310-01
(i) Displaying a progress rate of the forced parity correction

For the LU, the forced parity correction for which has been instructed to be made, rate of
progress of the restoration is displayed in the Status column of the LU concerned.
LU statuses concerning a forced parity correction and display of statuses by Storage Navigator
Modular.
# Status Display by Storage Navigator Modular Remarks

1 Being Restored Parity Correction (n%) n: Progress rate
2 On Standby Waiting Parity Correction(o) (n%) o: Waiting order
n: Rate of progress
3 Unrestored Uncorrected
4 Unrestored 2 Correction Aborted
5 Restored (No display)
6 Skip Correction Skipped

TRBL 06-0320-01
(j) Make sure that the forced parity correction has been completed in the Web window.
When making the forced parity correction for an LU in the Skip or Restored status, refer
to [ Instruction to make a forced parity correction for an LU in the Waiting Parity
Correction or Restored status ] (TRBL 06-0360).
(k) Make sure that the WARNING LED on the Front Bezel has gone out.
(l) Make the backup restoration. (Abandon all data and then restore it starting from the LU
formatting.) Otherwise, ask a user to verify files.

TRBL 06-0330-01
[ Cancellation of forced parity correction ]

The forced parity correction can be cancelled while the LU is in progress or after the
correction is instructed.
(a) Select an LU whose status displayed in the Logical unit status column is Parity Correcting or
Waiting Parity Correction.
(b) Select [Settings], [Logical Unit], and [Parity Correction] in this order.
(c) Select [Cancel] and press the [OK] button.

TRBL 06-0340-01
(d) Click the [OK] button.
(e) Click the [OK] button.

TRBL 06-0350-01
[ Instruction to make a forced parity correction for an LU in the Waiting Parity Correction or
Restored status ]
A forced parity correction can be made for an LU in the Waiting Parity Correction status or
for an LU for which the forced parity correction has been made.
(a) Select an LU for which the Waiting Parity Correction status is displayed in the column of
the logical unit state.
(b) In the state in which the selection above is made, select [Settings], [Logical Unit], and [Parity
Correction] in this order.
(c) Click the [OK] button.

TRBL 06-0360-01
(d) Select [Start], specify an order of making the forced parity correction, and press the [OK]
button.
(e) Click the [OK] button.
(f) Click the [OK] button.

TRBL 06-0370-01
< Change of the status in the forced parity correction >

The status of the forced parity correction changes as shown below. The status and progress
rate of the restoration can be referred to for each LU using Storage Navigator Modular.
(a) Change of the status after user data is lost
Occurrence of a
Issue of an instruction to make the forced parity PIN over (see
correction from Storage Navigator Modular (see (e) [Recovery method-
Execution of forced parity correction (TRBL 06- Waiting Parity 4] : PIN over
Uncorrected occurred during the
0260).) Correction
forced parity
correction. (TRBL
Issue of an instruction to Issue of instruction to abort the restoration from Storage 06-0190).)
Navigator Modular(see [ Cancellation of forced parity
skip the forced parity
correction ] (TRBL 06-0340).)
correction from Storage Automatic execution for
Navigator Modular (see Occurrence of a drive detachment (see each LU of each Control
[ When skipping the forced [Recovery method-3] : Drive blockade Unit
parity correction ] (TRBL 06- occurred during the forced parity
0310).) correction. (TRBL 06-0140).) Occurrence of a
PIN over (see
Issue of an instruction to abort the [Recovery method-
restoration from Storage Navigator 4] : PIN over
Skip Parity Correcting
Modular (see [ Cancellation of forced occurred during the
parity correction ] (TRBL 06-0340).) forced parity
Issue of an instruction to correction. (TRBL
skip the forced parity 06-0190).)
correction from Storage
Occurrence of a drive detachment (see [Recovery Completion of forced
Navigator Modular (see
method-3] : Drive blockade occurred during the parity correction
[ When skipping the forced
forced parity correction. (TRBL 06-0140).)
parity correction ] (TRBL Occurrence of an incomplete write (see [Recovery
06-0310).) method-5] : Incomplete write occurred during the
forced parity correction. (TRBL 06-0210).)
Correction
Restored
Aborted Issue of instruction to skip the forced parity correction
from Storage Navigator Modular (After the drive is
recovered)(*1) (see [ When skipping the forced parity
Explanation of figure
Cause of status change

Tatus name
Completion of forced
parity correction
Restored
Tatus
Direction of change
Skip status.
In this case, issue an instruction to skip the forced parity correction and then issue an instruction to make the
restoration.
y An LU of RAID 1+0

TRBL 06-0380-01
(b) Forced parity correction for an LU in the Restored status
Issue of an instruction to make the forced parity

correction from Storage Navigator Modular (see (e)
Execution of forced parity correction (TRBL 06-
0260).)
Waiting Parity
Restored Correction
When either of the following (a) and (b) occurs
(a) Issue of an instruction to abort the restoration from
Storage Navigator Modular (see [ Cancellation of forced
parity correction ] (TRBL 06-0340).) Automatic execution for each
(b) Drive detachment (see [Recovery method-3] : Drive LU of each Control Unit
blockade occurred during the forced parity correction.
(TRBL 06-0140).)
Parity Correcting
When either of the following (a) to (c) occurs
(a) Completion of forced parity correction
(b) Issue of an instruction to abort the restoration from Storage
Navigator Modular (see [ Cancellation of forced parity
(c) Drive detachment (see [Recovery method-3] : Drive blockade
occurred during the forced parity correction. (TRBL 06-0140).)
(c) Forced parity correction for an LU in the Skip status
Issue of an instruction to make the forced parity

correction from Storage Navigator Modular (see (e)
Execution of forced parity correction (TRBL 06-
0260).)
Waiting Parity
Skip Correction
When either of the following (a) and (b) occurs
(a) Issue of an instruction to abort the restoration from
Storage Navigator Modular (see [ Cancellation of forced
Issue of an instruction to parity correction ] (TRBL 06-0340).)
(b) Drive detachment (see [Recovery method-3] : Drive Automatic execution for each
skip the forced parity LU of each Control Unit
correction from Storage blockade occurred during the forced parity correction.
Navigator Modular (see (TRBL 06-0140).)
[ When skipping the
forced parity correction ] Parity Correcting
(TRBL 06-0310).) When either of the following (a) to (c) occurs
(a) Issue of an instruction to abort the restoration from Storage
Navigator Modular(see [ Cancellation of forced parity correction ]
(TRBL 06-0340).)
(b) Drive detachment (see [Recovery method-3] : Drive blockade Completion of forced parity
occurred during the forced parity correction. (TRBL 06-0140).) correction
Completion of drive recovery(*1)

Restored
Skip status.
y An LU of RAID 1+0

TRBL 06-0390-01
< Standard time required for the forced parity correction >
A forced parity correction takes a long time from start to completion. (Refer to Table 6.1.2
and Table 6.1.3.)
Standard times required for the forced parity correction are shown below.
RAID 5 (In the case of nD+1P):

For DF700: 23+9n minutes (n= 2 to 15)
RAID 1+0 (In the case of nD+nD):
For DF700: 35n10,000/Revolution speed of Disk Drive (min-1) minutes
(n= 1 to 8)
RAID 1 (In the case of 1D+1D):
For DF700: 3010,000/Revolution speed of Disk Drive (min-1) minutes
NOTE : The data above are standard times required for a forced parity correction for
one RAID group in the case where 72-Gbyte Disk Drives are used. The times
required for the restoration vary in proportion to the Disk Drive capacity.
Further, the times required for the restoration vary depending on the Disk Drive
capacity, number of Disk Drives, and RAID configuration.
Besides, as to some types of Disk Drives, the times required for the restoration
is shortened by 10 to 20 percent.
Table 6.1.2 Standard Times Required for Forced Parity Correction (When No Host I/O Is Executed)
RAID level Capacity(*1) 1LU/System 2LU/System
DF700 RAID 5 4D+1P 533.8 Gbytes 102 min 108 min
(143.3 Gbytes) 15D+1P 2001.9 Gbytes 323 min 323 min
RAID 1+0 2D+2D 266.9 Gbytes 94 min 96 min
8D+8D 1067.7 Gbytes 418 min 420 min
RAID 1 1D+1D 133.4 Gbytes 47 min 47 min
*1 : All Disk Drive capacities were calculated on the condition of 1 Gbyte =1,000,000,000 bytes.
They are different from those calculated on the condition of 1 kbytes =1,024 bytes, which are
actually displayed on PCs that you are using
Table 6.1.3 Standard Times Required for Forced Parity Correction (When Host I/Os Are Executed)
2LU/System
RAID level Capacity(*1)
Host performance Parity correction
DF700 RAID 5 4D+1P 533.8 Gbytes 765 IOPS 322 min
(143.3 Gbytes) 15D+1P 2001.9 Gbytes 774 IOPS 502 min
RAID 1+0 2D+2D 266.9 Gbytes 774 IOPS 300 min
8D+8D 1067.7 Gbytes 846 IOPS 804 min
*1 : All Disk Drive capacities were calculated on the condition of 1 Gbyte =1,000,000,000 bytes.
They are different from those calculated on the condition of 1 kbytes =1,024 bytes, which are
actually displayed on PCs that you are using

TRBL 06-0400-01
Conditions of measurement of a time required for the forced parity correction are as follows.
y Each of all LUs belongs to different RAID group.
y Only one LU per CTL is restored and an host I/O of random reading (75%) and writing (25%)
of 4-kbyte data TAG8 is executed for all the LUs.
Host
CTL0 CTL1
Object of Object of
parity parity
correction correction

TRBL 06-0410-01
6.1.4 The power cannot be turned off : Case 1 (The number of PIN data is too large)
(The planned shutdown cannot be performed due to the Disk Drive/Control Unit failure)

MM/DD/YYYY HH:MM:SS Cx HI0600 PS OFF failed [PIN] :MANUAL/CTRC
[Recovery method]
START
Turn off the all AC input Power Switch.
Turn on the all AC input Power Switch. (*1).
Check that READY LED

on the Front Bezel.
When it is high-speed blinking, wait up to
30/50 minutes.
PIN data is found(*2)? No
Yes
Collecting simple trace(*3). Collecting simple trace(*3).
Back up LU having the PIN data. Trace analysis

Call the Technical Support Center for
coping with troubles in order to require to
execute an analysis.
END
Yes
Did an Disk Drive error occurred?(*4) A
No To TRBL 06-0430
A pin over occurred during parity No

correction.
Yes Perform the LU formatting.
Restore user data using backup data
(prepared by a user).
Turn off the all AC input Power Switch.
B To TRBL 06-0440 END
*2 : Checking the presence of PIN data is performed by the Maintenance function of Storage Navigator Modular. Refer
to 10.2.4 Displaying Logical Unit Failure Data Information (TRBL 10-0250).
*3 : For the collection simple trace, refer to 7.3 Collecting simple trace (TRBL 07-0040).
*4 : For checking a Disk Drive error, refer to 8.2 (2) Trouble analysis based on LED indication of Disk Drive (TRBL 08-
0160) or Chapter 4. Trouble Analysis by WEB Connection (TRBL 04-0000).

TRBL 06-0420-01
From TRBL 06-0420 A
Replace the filed Disk Drive.(*1)

The data recovery is The data recovery is
terminated normally terminated abnormally
Data recovery status confirmation
The forced data recovery is terminated
When the data recovery is terminated abnormally.

[WEB Information Message display] (*2)
MM/DD/YYYY HH:MM:SS Cx I152xy DATA recovery failed (Unit-x, HDU-y) :MANUAL/STRC
xy denotes a Unit ID of Disk Drive number and a drive number of the Disk Drive replaced)
When the forced data recovery is terminated.

MM/DD/YYYY HH:MM:SS Cx I153xy DATA recovery partial (Unit-x, HDU-y) :MANUAL/STRC
(xy denotes a Unit ID of Disk Drive number and a drive number of the Disk Drive replaced)
When the data recovery is terminated normally.
MM/DD/YYYY HH:MM:SS Cx I151xy DATA recovery completed (Unit-x, HDU-y)
(xy denotes a Unit ID of Disk Drive number and a drive number of the Disk Drive replaced)
Check that this is not PIN.(*3). Recover it according to the failure Collecting simple trace(*4)
recovery method. (Refer to 6.1.7 The
power cannot be turned off : Case 4 Call the Technical Support Center for
(Cache memory failure) (TRBL 06- coping with troubles in order to identify a
0490).) Disk Drive that caused the abnormal
termination of a data restoration.
Back up the all LU, including the above

Disk Drive.
Replace the filed Disk Drive.(*1)
Format the LU(*5).
Recover the user data by using backup

data. (backed up by the user).
END END END

*1 : For the replacement of the Disk Drive, refer to the Replacement 2.2.1 Replacing Disk Drive (REP 02-0050).
*2 : For the connection of the WEB, refer to Chapter 3. Before Starting WEB Connection (TRBL 03-0000).
*4 : For the Collection simple trace, refer to 7.3 Collecting simple trace (TRBL 07-0040).
Therefore, request a user to release the pair and execute the LU formatting again after it is released (Refer to

TRBL 06-0430-01
From TRBL 06-0420 B
Replace the Control Unit(*1).
Turn off the all AC input Power.(*2)
The WARNING LED

on the Front Bezel blinks.

6.1.3 The failure occurred immediately
after being ready (Forced parity
correction) (TRBL 06-0060).)
END
*1 : For the replacement of the Control Unit, refer to the Replacement 2.2.5 Replacing Control Unit (REP 02-0390).

TRBL 06-0440-01
6.1.5 The power cannot be turned off : Case 2 (Hardware failure)

(It tried to store the PIN data in the Disk Drive at the time of the planned shutdown, but it
cannot POWER OFF because a hardware failure occurred)

MM/DD/YYYY HH:MM:SS Cx W41000 PIN write error :MANUAL/STRC
[Recovery method]
START
Turn off the all AC Power Unit Switch.
Turn on the all AC Power Unit.(*1)
When restarting the unit, wait for at least 1 minute after turning off
the power, then turn on the power.

on the Front Bezel.
30/50 minutes.
Yes
END
Collecting simple trace(*3).
Backup LU containing PIN data. If the LU has been backed up, this operation is not necessary.
Does failure occurs again? No
Yes END
A To TRBL 06-0460

TRBL 06-0450-01
From TRBL 06-0450 A
Is there LU for which the forced No

parity correction is necessary?(*1)
Yes
No Does PIN OVER occur? (*2)
Yes
Turn off the all AC Power Unit Switch. Perform the LU formatting.
Replace the Control Unit(*3). Restore user data using backup data
Turn on the all AC Power Unit Switch.(*4)
END
WARNING LED on the Front Bezel

comes blinking

END
*1 : The message code W48000 Forced parity correction LU is detected is displayed in the Information Message on the
WEB, and the Warning LED (orange) on the basic chassis (front side of the subsystem) lights on or blinks.
*2 : The message codes W41100, W49100, W49200, W49300, W49400, W49500 and W49600 are
displayed in the Information Message on the WEB, and the Warning LED (orange) on the basic chassis (front side of
the subsystem) lights on or blinks.

TRBL 06-0460-01
6.1.6 The power cannot be turned off : Case 3 (Control Unit failure)
(Planned shutdown cannot be performed because all the Disk Drives to which inheritance
information is to be saved disappeared due to a DMA double error or a disk quintuple error.)

MM/DD/YYYY HH:MM:SS Cx W22000 PS OFF failed [NO HDU] :MANUAL/STRC
[Recovery method]
START
Turn on the all AC Power Unit Switch. (*1)
Turn on the main switch. When restarting the unit, wait for at least 1 minute after turning off
the power, then turn on the power.
on the Front Bezel.
30/50 minutes.
Backup all LUs. If the LU has been backed up, this operation is not necessary.
No
Does failure occurs again?
Yes
END
A To TRBL 06-0480
*2 : For the Collection simple trace, refer to7.3 Collecting simple trace (TRBL 07-0040).

TRBL 06-0470-01
From TRBL 06-0470

A

Yes No
Does PIN OVER occur? (*2)
Yes
Replace the Control Unit(*3). Restore user data using backup data
END

comes blinking

END

TRBL 06-0480-01
6.1.7 The power cannot be turned off : Case 4 (Cache memory failure)
(The PIN data cannot be saved because a Cache memory or other failure occurs, and the
planned shutdown cannot be performed)

MM/DD/YYYY HH:MM:SS Cx W23000 PS OFF failed [CACHE ERR] :MANUAL/STRC
[Recovery method]
START

When restarting the unit, wait for at least 1 minute after turning off
Turn on the main switch. the power, then turn on the power.

on the Front Bezel.
30/50 minutes.
Yes
Collecting simple trace(*3). END
Backup pinned data LUs. If the LU has been backed up, this operation is not necessary.
Does failure occurs again? No
Yes
END
A To TRBL 06-0500

TRBL 06-0490-01
From TRBL 06-0490 A

Yes
No Does PIN OVER occur? (*2)
Yes
Replace the Cache Unit(*3). Restore user data using backup data
END

comes blinking

END
*3 : For the replacement of the Cache Unit, refer to the Replacement 2.2.6 Replacing Cache Unit (REP 02-0540).

TRBL 06-0500-01
6.1.8 Data recovery does not terminate normally : Case 1 (Read error)
(Forced recovery was performed because a read error occurred in the copy source during a
correction copy)
Forced recovery When attempting to read the data which was recovered forcibly, it is
reported as a read error.

MM/DD/YYYY HH:MM:SS Cx I153xy Data recovery partial :MANUAL/STRC
[Recovery method]
START
Check the LU which was recovered

forcibly by using the menu(*1) for
referring to the information on
presence/absence of the pinned data.
Back up the LU that was forcibly

recovered.
Formatting the LU that was forcibly

recovered.(*2)
Restore all the backup data of the LU

that was forcibly recovered.
If a part of the data cannot be backed
up when doing the above, restore the
data previously backed up.
END

TRBL 06-0510-01
6.1.9 Data recovery does not terminate normally : Case 2 (Disk Drive failure)
(Recovery was terminated abnormally because a Disk Drive error occurred in the copy source
during a correction copy)
MM/DD/YYYY HH:MM:SS Cx I152x0y0 Data recovery failed (Unit- x0, HDU- y0) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx I301x1y1 HDU error (Unit- x1, HDU- y1) :MANUAL/STRC
:
MM/DD/YYYY HH:MM:SS Cx W060x0y0 HDU alarm (Unit- x0, HDU- y0) :HDU /STRC
Failure occurred the Disk Drive (Unit#x0, Disk Drive#y0).

Disk Drivex0y0, Disk Drivex1y1 : The same parity group
MM/DD/YYYY HH:MM:SS Cx I152x0y0 Data recovery failed (Unit-x0, HDU-y0) :MANUAL/STRC

MM/DD/YYYY HH:MM:SS Cx I301AT SATA HDU error (Unit-x1, HDU-y1) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W060AT SATA HDU alarm (Unit-x0, HDU-y0) :HDU /STRC

[Recovery method]
START
Backup all LUs included in the row in

which a Disk Drive failure occurred.
Turn on the main switch. When restarting the subsystem, power it on after waiting for
a minute or more from the power off.

on the Front Bezel comes on.
30/50 minutes.
Replace the Disk Drive of which device

number is #x0 and drive number is #y0.
Data recovery is terminated normally? Yes
No Replace the Disk Drive of which device

number is #x1 and drive number is #y1.
No Data recovery is terminated normally?
Yes
A END
To TRBL 06-0530
TRBL 06-0520-01
From TRBL 06-0520 A
Set system again.

Resetting of the configuration
information.
Creation of the RAID groups.
Creation and formatting(*1) of the LUs.
Set file system, etc. (by host operation)
Recover user data with backup data.
(user backup)
END

TRBL 06-0530-01
6.1.10 Data recovery does not terminate normally : Case 3 (Spare Disk Drive failure)
(A Spare Disk failure occurred while the correction is copied and the recovery failed.)

MM/DD/YYYY HH:MM:SS Cx I152XX Data recovery failed (Unit-x1, HDU-y1) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W061XX Spare HDU alarm (Unit-x1, HDU-y1) :HDU /STRC
MM/DD/YYYY HH:MM:SS Cx I150XX Data recovery started (Unit-x1, HDU-y1)
MM/DD/YYYY HH:MM:SS Cx W060XX HDU alarm (Unit-x0, HDU-y0) :HDU /STRC

Recovery start the Spare Disk (Unit#x1, Disk Drive#y1).
Failure occurred the Spare Disk (Unit#x1, Disk Drive#y1).
Failure occurred the Spare Disk (Unit#x1, Disk Drive#y1).
[Recovery method]
START
Replace the blocked Disk Drive(*1).

(Unit #x0, Disk Drive #y0)
Data recovery is terminated normally?(*2). No
Yes
Replace the Spare Disk.
(Unit #x1, Disk Drive #y1)
No
Spin-up is terminated normally?(*3).
Yes
Take an action according to
the WEB message.
END
*2 : Check that the message of I151x0y0 Data recovery completed (Unit-x0, HDU-y0) is displayed.
*3 : Check that the message of I009x1y1 HDU recovery (Unit-x1, HDU-y1) is displayed.

TRBL 06-0540-01
6.1.11 A failure occurred during operation : Case 1 (PIN over)

MM/DD/YYYY HH:MM:SS Cx W41100 PIN over[PNLEVLOV] :MANUAL/STRC
[Recovery method]
START
PIN over occurred.
Disk Drive failure?(*1) No
Yes
Replace the Disk Drive(*2). Turn off the main switch by Power off. No
Yes
Check if there is PIN data(*3)? Yes Turn on the main switch.
No No
PIN data is found(*3)?
Yes
Turn off the main switch by Power off. No

Yes

See the procedure of recovering from a
Turn on the all AC Power Unit Switch(*4). failure when the power cannot be turned
off.
Turn on the main switch. (Refer to 6.1.4 The power cannot be
turned off : Case 1 (The number of PIN
data is too large) (TRBL 06-0420) to
Turn off the main switch.(*5) 6.1.7 The power cannot be turned off :
Case 4 (Cache memory failure) (TRBL
Turn on the main switch.(*6) 06-0490).)
END A To TRBL 06-0560 END
*1 : For checking a Disk Drive error, refer to 8.2 (2) Trouble analysis based on LED indication of Disk Drive (TRBL 08-
0160) or Chapter 4. Trouble Analysis by WEB Connection (TRBL 04-0000).
*2: For the replacement of the failed component, refer to the Replacement Chapter 2. Parts Replacement (REP 02-
0000).
*5 : To write pinned data on a drive, replace the Control Unit, and then execute the deliberate shutdown.
*6 : When restarting the subsystem, power it on after waiting for a minute or more from the power off.

TRBL 06-0550-01
From TRBL 06-0550 A
No
Check if there is PIN data(*1)?
Yes
Call the Technical Support Center for

copying with troubles in order to request
to analyze the simple trace collected.
Replace the failed component (*3).
END
*3 : For the replacement of the failed component, refer to the Replacement Chapter 2. Parts Replacement (REP 02-
0000).

TRBL 06-0560-01
6.1.12 A failure occurred during operation : Case 2 (LA/LRC error)

Any one of the following is displayed.
MM/DD/YYYY HH:MM:SS Cx W320xy LA error [errcode:LUN] (D-PT-00,CTL=x,TRNS-y) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W321xy LA error [errcode:LUN] (D-PT-01,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W322xy LA error [errcode:LBA] (H-PT-00,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W324xy LA error [errcode:LUN] (D-PT-00,CTL=x,TRNS-y) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W325xy LA error [errcode:LUN] (D-PT-01,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W328xy LA error [errcode:LUN] (D_PT-02, CTL-x, TRNS-y) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W329xy LA error [errcode:LUN] (D_PT-03, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W32Axy LA error [errcode:LBA] (D_PT-02, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W32Bxy LA error [errcode:LBA] (D_PT-03, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W32Cxy LA error [errcode:LUN] (H_PT-02, CTL-x, TRNS-y) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W32Dxy LA error [errcode:LUN] (H_PT-03, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W32Exy LA error [errcode:LBA] (H_PT-02, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W32Fxy LA error [errcode:LBA] (H_PT-03, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W330xy LRC error [errcode:LUN] (D-PT-00,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W331xy LRC error(D-PT-01,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W332xy LRC error (D_PT-02, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W333xy LRC error (D_PT-03, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W334xy LRC error (H_PT-02, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W335xy LRC error (H_PT-03, CTL-x, TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W340xy LRC error(H-PT-00,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W341xy LRC error(H-PT-01,CTL=x,TRNS-y) :MANUAL/ STRC
MM/DD/YYYY HH:MM:SS Cx W3360x Data transfer check error [SEGPOSERR] (CTL-x) :MANUAL/DMP

x : Controller# (0-1)
y : Transfer direction (R : Read, W : Write)
xx : DMA#(0-1)

TRBL 06-0570-01

Any one of the following is displayed.
MM/DD/YYYY HH:MM:SS Cx W0G20x Parity generation LA error [DRR] (CTL-x) :MANUAL/DMP
MM/DD/YYYY HH:MM:SS Cx HF0100 Data transfer check error [SEGPOSERR] :MANUAL/DMP
MM/DD/YYYY HH:MM:SS Cx H20100 Parity generation LA error [DRR] :MANUAL/DMP
MM/DD/YYYY HH:MM:SS Cx HD21xx Host transfer DMA error over (DMA-xx) :MANUAL/DMP
MM/DD/YYYY HH:MM:SS Cx HD27xx Drive transfer DMA error over (DMA-xx) :MANUAL/DMP

x : Controller# (0-1)
y : Transfer direction (R : Read, W : Write)
xx : DMA#(0-1)
[Recovery method]
START
Is there a block Disk Drive? No
Yes
Replace the blocked Disk Drive(*1) and
perform a data restoration.
Check to see if there is the PIN data (*2).
PIN data is found? Yes
No Back up the LU having the PIN.
For the LU having PIN data, perform:(*3)

an LU formatting(*4).
a restoration of backup data.
Replace the Controller indicated by x(*5).
END
*3 : This operation is required because an LA/LRC error occurs even after the controller has been replaced if the
LA/LRC data remains in the cache as PIN data.

TRBL 06-0580-01
6.1.13 A failure occurred during operation : Case 3 (LU blockade)

MM/DD/YYYY HH:MM:SS Cx W0H000 LU alarm (*1). :MANUAL/STRC
MM/DD/YYYY HH:MM:SS Cx W060x1y1 HDU alarm (Unit-x1,HDU-y1) :HDU /STRC
MM/DD/YYYY HH:MM:SS Cx W060x0y0 HDU alarm (Unit-x0,HDU-y0) :HDU /STRC

LUxx is blocked
[Recovery method]
The recovery operation must be reformed with the subsystem power turned on.
START
Replacement of failed Disks

Replace the Disk Drives in which the failures occurred (*2).
(An order of the Disk Drive replacements is not specified.)
Check the states of the new Disk Drives

after they are replaced.
Wait until the ALARM LED on Disk Drives go out.
Have all the failed Disk Drives in the No

same row been replaced?
Yes
Which is the objective Disk Drive in No
Disk Drives #0 to #4 having unit ID #0?
Yes
Recover the system information(*3).
y Execute the LU format(*4,5) which has been set in the

parity group, the Disk Drive of that were replaced. (This
LU has not been formatted.)
y Set the file system. (By the host operation)
y Recover the user data with the backup data. (backed up
by the user data.)
END
*1 : The blocked LU number is not displayed, with the message code W0H000 LU alarm. Check the blocked LU in the
*3 : Recover the system information with the maintenance function of the Storage Navigator Modular. For the
operating procedure, refer to the Addition/Subtraction/Relocation 1.4.3 (5) Restoring the system information
(ADD 01-0360).
*4 : For the operating procedure, refer to the System Parameter 3.3 Setting of LU (SYSPR 03-0140).
System Parameter 3.3 Setting of LU Procedure e-F Formatting LU (SYSPR 03-0280)).

TRBL 06-0590-01
6.1.14 A failure occurred during operation : Case 4 (Loop failure)

A loop failure occurred, however, the failed part cannot be located

MM/DD/YYYY HH:MM:SS Cx W0801y Loop alarm (Path-1,Loop-y) : /STRC
MM/DD/YYYY HH:MM:SS Cx W0800y Loop alarm (Path-0,Loop-y) : /STRC
MM/DD/YYYY HH:MM:SS Cx I60200 Link Failure [LIMIT OVER] :MANUAL/STRC
Date Time Detect Controller #

Link failures occurred exceeding its threshold number of occurrences.
Loop-y was blocked and the loop was switched to the alternating one.
Loop-y was blocked and the loop was switched to the alternating one.
When the codes, W080xy and I5Y400 to I5Y700, are indicated in the above messages, follow
(4) Actions to be taken when one of the message codes I5Y400 through I5Y700 is displayed
(TRBL 06-1090) for the maintenance.
When error messages other than W080xy Loop alarm (Path-x, Loop-y) occur at the same time,
give priority to the recovery methods of those messages for the maintenance.
When the failed part cannot be identified because the above message is not displayed, go to Step
(1) Procedure for Recovery from Loop Failure (TRBL 06-0680) and take a recovery action
explained in it. When a subsystem down has occurred in the case of the dual controller
configuration, go to Step (2) Procedure for Recovery from Loop Failure (in the case of a
subsystem down occurs in the dual controller configuration) (TRBL 06-0830). When a subsystem
down has occurred in the case of the single controller configuration, go to Step (3) Procedure
for Recovery from Loop Failure (in the case of a subsystem down occurs in the single controller
configuration) (TRBL 06-1020) and take a recovery action explained in it.

TRBL 06-0600-01
y Explanation of a Fibre Channel interface failure between a Control Unit and HDDs
The Fibre Channel interface between a Control Unit and HDDs connects three points, that is,
a controller, ENCs and HDDs. These three points compose a big loop.
Control Unit to Usage of loop RKM+RKAJ 14 RKM+RKAJ AT 14

be used normally (For HDDs) Number of HDDs in the same loop
LOOP #0 Control Unit #0 Path #0 Max. 120 Max. 113
Path #1 Max. 105 Max. 112
LOOP #1 Control Unit #1 Same as the above Same as the above Same as the above
Control Unit to Usage of loop RKS+RKAJ 6 RKS+RKAJAT 6
be used normally (For HDDs) Number of HDDs in the same loop
LOOP #0 Control Unit #0 Path #0 Max. 56 Max. 53
Path #1 Max. 49 Max. 52
LOOP#1 Control Unit #1 Same as the above Same as the above Same as the above

TRBL 06-0610-01
Loop structure of RKM/RKAJ

Fibre Chip Fibre Chip Fibre Chip Fibre Chip
Alternative loop Unit ID#0
Normal Normal (RKM)
loop loop
Path#0 Path#1 Path#0 Path#1

Disk Drive#
Loop#0 Loop#0 Loop#1 Loop#1
0
10
11
12
13
Cables between units Cables between units
ENC ENC Unit ID#1

Unit#0 Unit#1
(RKAJ)
Path#0 Path#1 Disk Drive# Path#0 Path#1
0
10
11
12
13
14
When a loop failure occurs, the controller that detects the failure uses a path used by
another system as an alternating path.

TRBL 06-0620-01
Loop structure of RKS

Normal loop Normal loop (RKS)

Disk Drive#
0
10
11
12
13

TRBL 06-0630-01
Loop structure of RKAJ

ENC ENC ENC ENC ENC ENC ENC ENC

Path#0 Path#1 Path#2 Path#3 Path#0 Path#1 Path#2 Path#3
Loop#0 Loop#0 Loop#0 Loop#0 Loop#1 Loop#1 Loop#1 Loop#1
Cables between units
Unit ID#0 Unit ID#1

(RKAJ) (RKAJ)
ENC ENC ENC ENC
Unit#0 Disk Drive# Unit#1 Unit#0 Disk Drive# Unit#1
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12 12
13 13
14 14
Unit ID#0
(RKAJ)
ENC ENC ENC ENC
Unit#0 Unit#1 Unit#0 Unit#1
Disk Drive# Disk Drive#
0 0
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12 12
13 13
14 14
TRBL 06-0640-01
A case where the RKM+RKAJATs+RKAJs are connected

Fibre Chip Fibre Chip Fibre Chip Fibre Chip Unit ID#0
Alternative loop
(RKM)

0
12
13

(RKAJAT) (RKAJAT)
SENC SENC SENC SENC
Path CTL Path CTL
0 0
Path CTL Path CTL
1 1
Path CTL Path CTL

FC-SATA FC-SATA FC-SATA FC-SATA
Conversion Conversion Conversion Conversion
2 2
Path CTL Path CTL
3 3
Path CTL Path CTL
14 14

(RKAJ) (RKAJ)
SENC SENC
Unit#0 Unit#1
0
13
14

TRBL 06-0650-01
A case where the RKAJs+RKAJATs are connected


(RKAJ) (RKAJAT)
Disk Drive# Path CTL Path CTL

Loop#0 Loop#0 Loop#1 Loop#1 0 0
0
Path CTL Path CTL
1
2 FC- 1 FC- FC- 1 FC-

SATA SATA SATA SATA
3 Con- Path CTL Con- Con- Path CTL Con-
version version version version
2 2
Path CTL Path CTL

13
ENC ENC 14 14
14 SENC SENC SENC SENC
Unit#0 Unit#1 Unit#0 Unit#1 Unit#0 Unit#1
Cables
(RKAJAT) (RKAJAT) between units (RKAJAT) (RKAJAT)
Disk Drive# Disk Drive# Disk Drive# Disk Drive#
Path CTL Path CTL Path CTL Path CTL
0 0 0 0
FC- 1 FC- FC- 1 FC- FC- 1 FC- FC- 1 FC-

SATA SATA SATA SATA SATA SATA SATA SATA
Con- Path CTL Con- Con- Path CTL Con- Con- Path CTL Con- Con- Path CTL Con-
version version version version version version version version
2 2 2 2
14 14 14 14
SENC SENC SENC SENC SENC SENC SENC SENC
Unit#0 Unit#1 Unit#0 Unit#1 Unit#0 Unit#1 Unit#0 Unit#1
Cables
(RKAJAT) (RKAJAT) between units (RKAJAT) (RKAJAT)
0 0 0 0

2 2 2 2
14 14 14 14
TRBL 06-0660-01
When a fibre channel interface failure occurs, all of these components are suspected.
Therefore, identify the failed part by means of a Web message.
[Display of the WEB Information Message window]

MM/DD/YYYY HH:MM:SS Cx I1C1xy Loop diagnostic end An automatic diagnosis of a failed part in the loop (Path-x,
(PATH-x, LOOP-y) Loop-y), in which the failure occurred, was completed.
MM/DD/YYYY HH:MM:SS Cx I603xy Obstacle part unknown The failed part could not be identified though an automatic
(PATH-x, LOOP-y) diagnosis of the loop (Path-x, Loop-y), in which the failure
occurred, was done.
MM/DD/YYYY HH:MM:SS Cx I1C0xy Loop diagnostic start An automatic diagnosis of a failed part in the loop (Path-x,
(PATH-x, LOOP-y) Loop-y), in which the failure occurred, was started.
MM/DD/YYYY HH:MM:SS Cx W0801y Loop alarm (PATH-1, Detach the Loop-y and change the loop to the alternating loop.
LOOP-y)
MM/DD/YYYY HH:MM:SS Cx W0800y Loop alarm (PATH-0, Detach the Loop-y and change the loop to the alternating loop.
LOOP-y
MM/DD/YYYY HH:MM:SS Cx I60200 Link Failure [LIMIT OVER] Link failures have occurred more than its threshold value.
Perform a diagnosis with a loop test after the W080xy loop alarm was given. Then the path
in which the loop failure occurred is shown in the message (I1C0xy/I1C1xy).
Example:
MM/DD/YYYY HH:MM:SS C0 I1C110 Loop diagnostic end (Path-1,Loop-0) c
MM/DD/YYYY HH:MM:SS C0 I60310 Obstacle part unknown (Path-1,Loop-0) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS C0 I1C010 Loop diagnostic start (Path-1,Loop-0)
d
MM/DD/YYYY HH:MM:SS C0 W06013 HDU alarm (Unit-1,HDU-3) :HDU /STRC
MM/DD/YYYY HH:MM:SS C0 W08000 Loop alarm (Path-0,Loop-0) :MANUAL/STRC
MM/DD/YYYY HH:MM:SS C0 W08010 Loop alarm (Path-1,Loop-0) :MANUAL/STRC
In this case, a loop failure occurred in the loop, Loop-0 and Path-1 (on the CTL-0 side, for
HDDs with odd numbers), shown in c.
When error messages other than W080xy Loop alarm (Path-x, Loop-y) occur at the same time,
give priority to the recovery methods of those messages for the maintenance.

TRBL 06-0670-01
(1) Procedure for Recovery from Loop Failure

If a loop failure (W080xy) occurs, you can open the diagnostic window of the Loop Failure
Detection Function using a Web browser and execute the loop failure detection function to
identify the failed HDU(s).
(a) Conditions for and notes on executing the Loop Failure Detection Function
(i ) Do not execute the Loop Failure Detection Function while an LU formatting is in progress.
(ii) Do not perform the LU formatting while the Loop Failure Detection Function is being
executed.
(iii) Do not pull out/insert a replacement component while the Loop Failure Detection Function
is being executed.
Replace it when single execution of the Loop Failure Detection Function is completed.
(Replacement components: Disk Drive, Backup Battery Unit, Power Unit, Fan Assembly,
and Control Unit, ENC Unit, SENC Unit)
(iv) Procedure for recovery from a new failure occurs while the recovery operation using the
Loop Failure Detection Function is in progress.
Make a recovery from the new failure preferentially. Re-execute the recovery operation
using the Loop Failure Detection Function after the recovery from the new failure is
completed.
[Occurrence of a new failure]
y Interrupt the recovery operation by means of the Loop Failure Detection Function once.
y Perform a recovery action against the new failure (usual recovery procedure).
y Perform the recovery operation by means of the Loop Failure Detection Function again from the beginning.
(v) Time required to execute the Loop Failure Detection Function (Required time per HDU
diagnosis)
Normally, single execution of the Loop Failure Detection Function finishes in ten seconds.
(vi) Use of the Check List for Failed HDU Isolation.
When performing the recovery operation using the Loop Failure Detection Function, do it
recording execution results of the Loop Failure Detection Function in the (f) Check List
#1 for Failed HDU Isolation (TRBL 06-0980) and (g) Check List #2 for Failed HDU Isolation
(for all HDUs)(TRBL 06-0990) appended to the Maintenance Manual.
To use the Check List #1 and #2 for Failed HDU Isolation, make as many copies of it as
necessary for the recovery operation.
(vii) Result of Loop Failure Detection Function Execution.
y The diagnostic results by the loop failure detection function appear as shown below in
the upper right of the diagnostic window of the Loop Failure Detection Function or in the
Information Message field.
When the diagnosis result is OK : I5Z5xy Failure check OK (Path-x, Loop-y)
When the diagnosis result is not OK : I5Z6xy Failure check NG (Path-x, Loop-y)
y When the result of the execution of the Loop Failure Detection Function is shown as
check OK, check the [OK] check box of the Check List for Failed HDU Isolation.

TRBL 06-0680-01
(viii) When a failure other than the loop failure (an HDU failure (W060xy, I301xy), a CTL failure
(W0100x) or an ENC Unit failure (W070xy)) has also occurred, take a recovery action
against it according to the message before using the Loop Failure Detection Function.
(ix) Do not turn off the AC Power Unit Switch of the subsystem while the Loop Failure
Detection Function is being executed.
If the AC Power Unit Switch of the subsystem is turned off while the Loop Failure
Detection Function is being executed, turn off the AC Power Unit Switch of the added
RKAJ one, turn it on again, then turn on the AC Power Unit Switch of the subsystem.
(b) How to open the Loop Failure Detection Function

(i ) Connect a PC and subsystem via a LAN (in order to use the WEB function).
(ii) Connect to the website, http://subsystem IP address(1)/drvdiag.
operation. In that case, input maintenance for the [User Name] and hosyu9500 for
the [Password].
1 : As for the IP address of the subsystem, refer to 3.1 (4) Procedure to connect portable maintenance PC to WEB
(TRBL 03-0010).

TRBL 06-0690-01
(c) Procedure for executing the Loop Failure Detection Function

(c-1) Confirming occurrence of a loop failure / Identifying a failed component using the Loop
Failure Detection Function
y Make sure that "W080xy Loop Alarm (Path # xx, Loop # xx) (Loop failure)" is displayed in
the Information Message window. Enter the Path # and Loop # shown in the message
in the check list.
y Execute each procedure for identifying the failed component by means of the Loop
Failure Detection Function twice to make the identification of the failed component
certain. (Sets of two check boxes, the 1st diagnosis result and 2nd diagnosis result, are
prepared in the Check List for Failed HDU Isolation.)
(i ) Id e nti f yin g Failed Loops and Paths

c Id e nti f y the failed loop in which the failed HDU is installed by executing the Loop
Failure Detection Function for each Path # and Loop # in the state in which all the HDUs
are connected to the loop.
d Execute the Loop Failure Detection Function for both of the Loop-0 and Loop-1 of the
path observed to have the loop failure.
Diagnosis for Loop Failure Detection Function window

Specify the [PATH Number] and [LOOP Number]. When "Wxxxx Loop Alarm (Path #0, Loop #0)" is
Click the [Check ALL] button. displayed.
(All the HDUs are connected within the Loop.) Specify the [PATH Number] as [PATH 0].
Click the [Diagnosis Start] button. Specify the [LOOP Number] as [LOOP 0].
e When [I5Z6xy Failure check NG (Path-x, Loop-y)] (x and y denote specified Path # and
Loop # respectively) is displayed in the Information Message window as a result of the
execution of the Loop Failure Detection Function, the Path # and Loop # shown in
parentheses represent the failed loop. Enter the failed loop identified in the check
sheet.
NOTE : When the failed loop cannot be identified, identify the failed HDU by executing
the Loop Failure Detection Function for all the HDU following the procedure
explained in Step (c-2) (i) Id e n tif yin g Failed HDU (TRBL 06-0750). (When
doing that, use the Check List #2 for Failed HDU Isolation (For checking all
HDUs).)

TRBL 06-0700-01
(ii) Judging whether or not the HDU caused the failure

c Confirm that the failed HDU exists in the failed loop concerned by executing the Loop
Failure Detection Function bypassing all the HDUs in the failed loop (separating them
from the loop).

Specify the [PATH Number] and [LOOP Number]. Specify the Path # and Loop # of the failed loop
Click the [Clear ALL] button.
(All the HDUs are connected within the Loop.)
Click the [Diagnosis Start] button.
Was [I5Z6xy Failure check NG (Path-x, Loop-y)]

(x and y denote specified Path # and Loop #
No No RKS or additional frame (RKAJ)
respectively) displayed in the Information Message
exists.
window as a result of the execution of the Loop
Failure Detection Function? Yes No
Yes
(iv) Identifying Failed HDU (iii) Identifying Failed Unit
(TRBL 06-0730) (TRBL 06-0720)
No failed HDU exists in the failed loop.

Identify the failed component as shown below and replace it.
Replace the ENC cable(*1).
Was [W080xy Loop Alarm (Path # xx, Loop # xx)]

No
(Loop failure) displayed in the Information
Message?
Yes
Replace the ENC Unit/SENC
Unit(*1).

No
Message?
Yes

No
Message?
Yes
Replace the subsystem(*1). Recovery is completed.
ENC cable and ENC Unit/SENC Unit occur only in a configuration which includes the RKAJ/RKAJAT.
0000).

TRBL 06-0710-01
(iii) Identifying Failed Unit

c Identify the unit in which the failed HDU is installed by executing the Loop Failure
Detection Function for each of all the units.
Execute the Loop Failure Detection Function for each unit

once at a time
Specify the [PATH Number] and [LOOP Number]. Specify the Path # and Loop # of the failed loop.
Click the [Clear All] button.
(Clear the conditions for the preceding check.)
Check all the HDU# check boxes of the Unit-x.
Click the [Diagnosis Start] button
d Enter the unit number, for which [I5Z6xy Failure check NG (Path-x, Loop-y)] (x and y
denote specified Path # and Loop # respectively) is displayed in the Information
Message window, in the check sheet. (It is determined that the failed component exists
in the failed unity.)
Was [I5Z6xy Failure check NG (Path-x, Loop-y)] (x

and y are specified path # and loop # respectively)
displayed in the Information Message window for No
(The failed unit can not
all the unit when the loop failure detection function
be identified.)
was executed?
Yes (The failed unit has been
identified)
(iv) Identifying Failed HDU Contact (RSD) after collecting
(TRBL 06-0730) the trace.

TRBL 06-0720-01
(iv) Identifying Failed HDU

c Identify a failed HDD by applying the loop failure detection function to each HDD in the
failed unit, which was identified in Step (iii), one by one.
Execute the Loop Failure Detection Function for all the HDUs
of the Unit-x.
Check the HDU# check box of the Unit-x.
d Enter the HDU number, for which [I5Z6xy Failure check NG (Path-x, Loop-y)] (x and y
Message window, in the check sheet.

(x and y are specified path # and loop # respectively)
displayed in the Information Message window for Yes
two or more HDUs when the loop failure detection
function was executed?
No (Failure of a single HDU)
( v ) Reconfirming Failed HDU Contact (RSD) after collecting


TRBL 06-0730-01
(v) Reconfirming Failed HDU

c Execute the loop failure detection function in the state in which only the HDU, which was
identified as a cause of the failure in Step (iv), is disconnected from the loop and verify
that no error occurs.

Click the [Check All] button.
Delete the check mark from the HDU# check box of the Unit-x.
After executing the loop failure detection function,

does the Information Message window field show
the following message? Yes
[I5Z6xy Failure check NG (Path-x, Loop-y)]
(x and y: specified Path # and Loop #).
No
Replacing failed HDU Contact (RSD) after collecting

(If more than one HDU were identified as faulty, the trace.
replace them one by one.)
Procedure for replacing Disk Drive :
Refer to the Replacement 2.2.1 Replacing
Disk Drive (REP 02-0050).

TRBL 06-0740-01
(c-2) Confirming occurrence of a loop failure / Specifying a failed component using the Loop
Failure Detection Function (Failed loop could not identified)
y When the failed loop could not identified although the operation was performed
according to (c-1) (i) Identifying Failed Loops and Paths (TRBL 06-0700), Confirming
occurrence of a loop failure/Identifying a failed component using the Loop Failure
Detection Function, identify the failed component by executing the Loop Failure
Detection Function for each of all the HDUs.
(i) Identifying Failed HDU

c Identify the failed HDU by executing the Loop Failure Detection Function for each HDU.
Execute the Loop Failure Detection Function for all the HDUs Execute those operations for both of the Path #0
of the each unit. and Path #1 of the loop for which [w080xy] was
Diagnosis for Loop Failure Detection Function window indicated in the Information Message window.
Specify the [PATH Number] and [LOOP Number].
Check the HDU # check box of the Unit-x.

None of failed HDU be
identified.
Yes
(ii) Reconfirming the HDU that Contact (RSD) after collecting

caused the failure the trace.
(TRBL 06-0760)

TRBL 06-0750-01
(ii) Reconfirming the HDU that caused the failure

c Execute the Loop Failure Detection Function in the state in which only the identified HDU
is separated in order to verify the failed HDU.

Click the [Check ALL] button.

Yes
Failure Detection Function?
No
Replacing failed HDU Contact (RSD) after collecting

(If more than one HDU were identified as faulty, the trace.
replace them one by one.)
Procedure for replacing Disk Drive :
Disk Drive (REP 02-0050).

TRBL 06-0760-01
(d) WEB window of the Loop Failure Detection Function

(i ) Window for instructing the Loop Failure Detection Function
(a)
(c) (b)
(h)
(d)
(g)
(e) (f)
(i)
Element in the window Description

(a) A list for selecting a path number To be used to select a path number of a loop to be diagnosed.
(b) A list for selecting a loop number To be used to select a number of a loop to be diagnosed.
(c) Check All button Makes all check boxes selected.
(d) Clear All button Makes all check boxes unselected.
(e) All button Makes all check boxes selected for each unit.
(f) Clear button Makes all check boxes unselected for each unit.
(g) Each check box To be used to specify whether to link the drive concerned to a selected loop.
The check box is not displayed when no frame exists or no drive is installed.
(h) Diagnosis Start button Starts a diagnosis.
(i) Information Message Displays information on the entire system. Result of a diagnosis is also
displayed here.

TRBL 06-0770-01
(ii) Window displayed during execution of the Loop Failure Detection Function
(iii) Window displayed when the Loop Failure Detection Function ends
c
d

c Display of a summary of a diagnosis Displays a result of a diagnosis.
result
d Complete button Changes a window to that of a diagnosis by the Loop Failure Detection
Function.

TRBL 06-0780-01
(e) Check List #1 for Failed HDU Isolation
NOTE : To use this check list, make as many copies of it as necessary for the recovery
operation.
Data Maintenance execution time to

End users name Service persons name
Subsystem serial No.: Subsystem IP addres
Failed and Path#,Loop# Path[ ],Loop[ ] Path[ ],Loop[ ]
CL#1
1. Identifying a failed loop and path
PATH Number( ) LOOP Number( ) With All HDUs connected 1st diagnosis result 2nd diagnosis result
(with [Check ALL] clicked) OK NG OK NG

PATH Number( ) LOOP Number( ) With All HDUs connected 1st diagnosis result 2nd diagnosis result

Failed Loop: PATH ( ), LOOP( )
2. Isolating an HDU that caused the failure

PATH Number( ) LOOP Number( ) With All HDUs bypass 1st diagnosis result 2nd diagnosis result
(with [Clear ALL] clicked) OK NG OK NG

3. Identifying a failed unit

PATH Number( ) LOOP Number( )
Unit-0 with all 1st diagnosis result 2nd diagnosis result Unit-1 with all 1st diagnosis result 2nd diagnosis result
HDUs Connected OK NG OK NG HDUs Connected OK NG OK NG







Unit-14 with all 1st diagnosis result 2nd diagnosis result
HDUs Connected OK NG OK NG

Failed Unit Unit( ), (Unit( ), Unit( ))
4. Identifying an HDU that caused the failure

(with [Clear] clicked)
With HDU-0 1st diagnosis result 2nd diagnosis result With HDU-1 1st diagnosis result 2nd diagnosis result
Connected OK NG OK NG Connected OK NG OK NG







With HDU-14 1st diagnosis result 2nd diagnosis result
Connected OK NG OK NG

Failed HDU HDU( ), (HDU( ), HDU( ))
5. Confirming the HDU that caused the failure

(with [Chek ALL] clicked)
With the failed HDU separated 1st diagnosis result 2nd diagnosis result
OK NG OK NG


TRBL 06-0790-01
(f ) Check List #2 for Failed HDU Isolation (for all HDUs)
operation.
CL#2-1
1 Identifying an HDU that caused the failure [Path ( ) Loop ( )]
--------------------------------------------------------------------------------------------------------
Unit (0) with all HDUs separated (with Clear clicked)
Installation OK NG OK NG Installation OK NG OK NG
With HDU-0 connected With HDU-1 connected
With HDU-14 connected
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------

TRBL 06-0800-01
CL#2-2
Unit (6) with all HDUs separated (with Clear clicked )
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------

TRBL 06-0810-01
CL#2-3
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------

OK NG OK NG


TRBL 06-0820-01
(2) Procedure for Recovery from Loop Failure (in the case of a subsystem down occurs in the dual
controller configuration)
If the subsystem went down due to a loop failure (W080xy), you can open the diagnostic
window of the Loop Failure Detection Function using a Web browser and execute the loop
failure detection function to identify the failed HDU(s).
(a) Conditions for and notes on executing the Loop Failure Detection Function
(i ) Do not pull out/insert a replacement component while the Loop Failure Detection Function
is being executed.
Replace it when single execution of the Loop Failure Detection Function is completed.
(Replacement components: Disk Drive, Backup Battery Unit, Power Unit, Fan Assembly,
and Control Unit, ENC Unit, SENC Unit)
(ii) Procedure for recovery from a new failure occurs while the recovery operation using the
Loop Failure Detection Function is in progress.
Make a recovery from the new failure preferentially. Re-execute the recovery operation
using the Loop Failure Detection Function after the recovery from the new failure is
completed.
[Occurrence of a new failure]
y Interrupt the recovery operation by means of the Loop Failure Detection Function once.
y Perform a recovery action against the new failure (usual recovery procedure).
y Perform the recovery operation by means of the Loop Failure Detection Function again from the beginning.
(iii) Time required to execute the Loop Failure Detection Function (Required time per HDU
diagnosis)
Normally, single execution of the Loop Failure Detection Function finishes in ten seconds.
Use of the Check List for Failed HDU Isolation.
When performing the recovery operation using the Loop Failure Detection Function, do it
recording execution results of the Loop Failure Detection Function in the (f ) Check List
#1 for Failed HDU Isolation (TRBL 06-0980) or (g) Check List #2 for Failed HDU Isolation
(for all HDUs) (TRBL 06-0990) appended to the Maintenance Manual.
To use the Check List #1 and #2 for Failed HDU Isolation, make as many copies of it as
necessary for the recovery operation.
(iv) Result of Loop Failure Detection Function Execution.
y The diagnostic results by the loop failure detection function appear as shown below in
the upper right of the diagnostic window of the Loop Failure Detection Function or in the
Information Message field.
When the diagnosis result is OK : I5Z5xy Failure check OK (Path-x, Loop-y)
When the diagnosis result is not OK : I5Z6xy Failure check NG (Path-x, Loop-y)
y When the result of the execution of the Loop Failure Detection Function is shown as
check OK, check the [OK] check box of the Check List for Failed HDU Isolation.
(v) When a failure other than the loop failure (an HDU failure (W060xy, I301xy), a CTL failure
(W0100x) or an ENC Unit failure (W070xy)) has also occurred, take a recovery action
against it according to the message before using the Loop Failure Detection Function.

TRBL 06-0830-01
(vi) If the failure occur in all of the four loops, the Loop Failure Detection function cannot be
used.
(vii) When an instruction to isolate two or more HDUs in the same RAID group is given using the
Failed HDU Isolation function, user data will be lost.
(viii) When a failure has occurred in a loop of the Path #0 and Loop #0 in the case of the single
controller configuration, the Loop Failure Detection Function cannot be used.
Take a recovery action according to Step (3) Procedure for Recovery from Loop Failure
(in the case of a subsystem down occurs in the single controller configuration) (TRBL 06-
1020).
(b) How to start the loop failure detection function

(i ) Connect the PC and the subsystem via the LAN (for using the Web function).
(ii) Press the RST SW on the both controllers to enter the Web maintenance mode.
Use a tool with a thin tip (a precise screwdriver, etc.) because the hole of RST SW is small
(3 mm in diameter).
(iii) Connect to the website, http://subsystem IP address(1)/drvdiag.
operation. In that case, input maintenance for the [User Name] and hosyu9500 for
the [Password].
(iv) In the startup mode window (Boot Up Mode Backend Diagnostic), select Enable and then
choose the OK button.
(v) In the startup mode window, choose the Reboot button to restart the device.
(vi) Check the READY LED on the front of the device.
y If the READY LED is Low-speed blinking, connect to http://device-IP-address/drvdiag,
and then open the loop failure detection function window.
y In a case other than that where the READY LED is Low-speed blinking, retry the operation
in (b).
If the READY LED is not Low-speed blinking after the retry, contact the (RSD) (for
replacing the subsystem).
1 : As for the IP address of the subsystem, refer to 3.1 (4) Procedure to connect portable maintenance PC to WEB
(TRBL 03-0010).

TRBL 06-0840-01
(c) Procedure for executing the Loop Failure Detection Function

(c-1) Confirming occurrence of a loop failure / Identifying a failed component using the Loop
Failure Detection Function
y Execute each procedure for identifying the failed component by means of the Loop
Failure Detection Function twice to make the identification of the failed component
certain. (Sets of two check boxes, the 1st diagnosis result and 2nd diagnosis result, are
prepared in the Check List for Failed HDU Isolation.)
(i ) Identifyng Failed Loops and Paths

c Identify the failed loop in which the failed HDU is installed by executing the Loop Failure
Detection Function for each Path # and Loop # in the state in which all the HDUs are
connected to the loop.
d Execute the Loop Failure Detection Function for both of the Loop-0 and Loop-1 of the
path observed to have the loop failure.

Specify the [PATH Number] and [LOOP Number]. When "Wxxxx Loop Alarm (Path #0, Loop #0)" is
Click the [Check ALL] button. displayed.
(All the HDUs are connected within the Loop.) Specify the [PATH Number] as [PATH 0].
Click the [Diagnosis Start] button. Specify the [LOOP Number] as [LOOP 0].
e When [I5Z6xy Failure check NG (Path-x, Loop-y)] (x and y denote specified Path # and
Loop # respectively) is displayed in the Information Message window as a result of the
execution of the Loop Failure Detection Function, the Path # and Loop # shown in
parentheses represent the failed loop. Enter the failed loop identified in the check
sheet.
f Perform the procedures from (ii) Judging whether or not the HDU caused the failure
(TRBL 06-0860) to (v) Reconfirming Failed HDU (TRBL 06-0890), and identify the failed
HDU for each one of the failed loops.
NOTE : When the failed loop cannot be identified, identify the failed HDU by executing
the Loop Failure Detection Function for all the HDU following the procedure
explained in Step (c-2) (i) Identifying Failed HDU (TRBL 06-0910). (When
doing that, use the Check List #2 for Failed HDU Isolation (For checking all
HDUs).)

TRBL 06-0850-01
(ii) Judging whether or not the HDU caused the failure

c Confirm that the failed HDU exists in the failed loop concerned by executing the Loop
Failure Detection Function bypassing all the HDUs in the failed loop (separating them
from the loop).

Click the [Clear ALL] button.
(All the HDUs are connected within the Loop.)

No No RKS or additional frame (RKAJ)
exists.
Failure Detection Function? Yes No
Yes
(iv) Identifying Failed HDU (iii) Identifying Failed Unit
(TRBL 06-0880) (TRBL 06-0870)
No failed HDU exists in the failed loop.

Identify the failed component as shown below and replace it.
Replace the ENC cable(*1).

(Loop failure) displayed in the Information No
Message?
Yes
Replace the ENC Unit/SENC
Unit(*1).

No
Message?
Yes

No
Message?
Yes
Replace the subsystem(*1). Recovery is completed.
ENC cable and ENC Unit/SENC Unit occur only in a configuration which includes the RKAJ/RKAJAT.
0000).

TRBL 06-0860-01
(iii) Identifying Failed Unit

c Identify the unit in which the failed HDU is installed by executing the Loop Failure
Detection Function for each of all the units.
Execute the Loop Failure Detection Function for each unit

once at a time
Check all the HDU# check boxes of the Unit-x.
lick the [Diagnosis Start] button.
d Enter the unit number, for which [I5Z6xy Failure check NG (Path-x, Loop-y)] (x and y
Message window, in the check sheet. (It is determined that the failed component exists
in the failed unit.)
Was [I5Z6xy Failure check NG (Path-x, Loop-y)] (x

and y are specified path # and loop # respectively)
(The failed unit can not
all the unit when the loop failure detection function be identified.)
was executed?
Yes (The failed unit has been
identified)
(iv) Identifying Failed HDU Contact (RSD) after collecting

TRBL 06-0870-01
(iv) Identifying Failed HDU

c Identify a failed HDD by applying the loop failure detection function to each HDD in the
failed unit, which was identified in Step (iii), one by one.
Execute the Loop Failure Detection Function for all the HDUs
of the Unit-x.
d Enter the HDU number for which [I5Z6xy Failure check NG (Path-x, Loop-y)] (x and y

displayed in the Information Message window for Yes
No (Failure of a single HDU)
( v ) Reconfirming Failed HDU Contact (RSD) after collecting


TRBL 06-0880-01
(v) Reconfirming Failed HDU

c Execute the loop failure detection function in the state in which only the HDU, which was
identified as a cause of the failure in Step (iv), is disconnected from the loop and verify
that no error occurs.

Click the [Check All] button.
After executing the loop failure detection function,

does the Information Message window field show
the following message? Yes
(x and y: specified Path # and Loop #).
No
(vi) Isolating Failed HDU Contact (RSD) after collecting


TRBL 06-0890-01
(vi) Isolating Failed HDU
Have you executed the loop error detection function No

for all the failed loops to identify the failed drive?
Yes Execute the loop failure

detection function for the
failed loop for which you did
not identify the failed HDU.
As a result of executing the loop failure detection

function for all the failed loops, does the Information
Message window field show the following message Yes
for some HDUs?
[I5Z6xy Failure check NG(Path-x, Loop-y)]
(x and y: specified Path # and Loop #). Contact (RSD) after collecting
the trace.
No
In the Complete Loop Failure Detection Function

window, click To Drive Bypass to open the Failed
HDU Isolation Function window.
Isolate the failed HDU identified by the loop failure

detection function from the loop.
After executing the failed drive disconnection

function, does the Information Message window No
field show [I5ZA00 HDD bypass succeeded]?
Yes Consult the (RSD).
(Replacing subsystem)
Click the Reboot button to restart the subsystem.
After restarting the device, replace the HDU

shown in W0600xx HDU alarm (Unix-x, HDU-y) in
the Information Message window field, one by
one.
NOTE : If you isolated multiple HDU in the same RAID group from the loop, restarting
the subsystems deletes the user data.

TRBL 06-0900-01
(c-2) Confirming occurrence of a loop failure / Specifying a failed component using the Loop
Failure Detection Function (Failed loop could not identified)
y When the failed loop could not identified although the operation was performed
according to (c-1) (i) Identifyng Failed Loops and Paths (TRBL 06-0850), Confirming
occurrence of a loop failure/Identifying a failed component using the Loop Failure
Detection Function, identify the failed component by executing the Loop Failure
Detection Function for each of all the HDUs.
(i ) Identifying Failed HDU

c Identify the failed HDU by executing the Loop Failure Detection Function for each HDU.
Execute the Loop Failure Detection Function for all the HDUs Execute those operations for both of the Path#0
of the each unit. and Path#1 of the loop for which [w080xy] was
Diagnosis for Loop Failure Detection Function window indicated in the Information Message window.
Specify the [PATH Number] and [LOOP Number].

None of failed HDU be
identified.
Yes
(ii) Reconfirming Failed HDU Contact (RSD) after collecting


TRBL 06-0910-01
(ii) Reconfirming Failed HDU

c Execute the Loop Failure Detection Function in the state in which only the identified HDU
is separated in order to verify the failed HDU.

Click the [Check ALL] button.

respectively) displayed in the Information Message Yes
Failure Detection Function?
No
(iii) Isolating Failed HDU Contact (RSD) after collecting


TRBL 06-0920-01
(iii) Isolating Failed HDU
Have you executed the loop error detection function No

for all the failed loops to identify the failed drive?
Yes Execute the loop failure

detection function for the
failed loop for which you did
not identify the failed HDU.
As a result of executing the loop failure detection

function for all the failed loops, does the Information
Message window field show the following message Yes
for some HDUs?
(x and y: specified Path # and Loop #). Contact (RSD) after collecting
the trace.
No
In the Complete Loop Failure Detection Function

window, click To Drive Bypass to open the Failed
HDU Isolation Function window.
Isolate the failed HDU identified by the loop failure

detection function from the loop.
After executing the failed drive disconnection

function, does the Information Message window No
field show [I5ZA00 HDD bypass succeeded]?
Yes Consult the (RSD).
(Replacing subsystem)
Click the Reboot button to restart the subsystem.
After restarting the device, replace the HDU

shown in W0600xx HDU alarm (Unix-x, HDU-y) in
the Information Message window field, one by
one.

TRBL 06-0930-01
(d) WEB window of the Loop Failure Detection Function

(i ) Window for instructing the Loop Failure Detection Function
(a)
(c) (b)
(h)
(d)
(g)
(e) (f)
(i)

(a) A list for selecting a path number To be used to select a path number of a loop to be diagnosed.
(b) A list for selecting a loop number To be used to select a number of a loop to be diagnosed.
(c) Check All button Makes all check boxes selected.
(d) Clear All button Makes all check boxes unselected.
(e) All button Makes all check boxes selected for each unit.
(f) Clear button Makes all check boxes unselected for each unit.
(g) Each check box To be used to specify whether to link the drive concerned to a selected loop.
The check box is not displayed when no frame exists or no drive is installed.
(h) Diagnosis Start 2 button Starts a diagnosis.
(i) Information Message Displays information on the entire system. Result of a diagnosis is also
displayed here.
(ii) Window displayed during execution of the Loop Failure Detection Function

TRBL 06-0940-01
(iii) Window displayed when the Loop Failure Detection Function ends
c
d

c Display of a summary of a diagnosis Displays a result of a diagnosis.
result
d A linkage with the Failed HDU Change a window to that of the Failed HDU Disconnection function.
Disconnection function
e Complete button Changes a window to that of a diagnosis of the Loop Failure Detection
functions.

TRBL 06-0950-01
(e) WEB window of the Failed HDU Isolation Function

(i ) Starting window of Failed HDU Isolation Function
(b)
(a)
(c)

c Each check box To be used to specify whether to bypass the drive concerned (whether to
remove the check mark).
d Bypass Start button Starts the bypassing operation.
e Information Message Displays progress of the bypassing operation.
(ii) Window showing a running state of the Failed HDU Isolation Function

TRBL 06-0960-01
(iii) Completion window of the Failed HDU Isolation Function
d e f

c Display of a summary of a diagnosis Displays a result of the diagnosis.
result
d Retry button Changes a window to that for disconnecting a failed HDU.
e Trace button Starts a collection of a trace.
f Reboot button Restarts the subsystem.

TRBL 06-0970-01
(f) Check List #1 for Failed HDU Isolation
operation.
Data Maintenance execution time to

End users name Service persons name
Subsystem serial No.: Subsystem IP addres
Failed and Path#,Loop# Path[ ],Loop[ ] Path[ ],Loop[ ]
CL#1
1. Identifying a failed loop and path
PATH Number(0) LOOP Number(1) With All HDUs connected 1st diagnosis result 2nd diagnosis result




Failed Loop: PATH ( ), LOOP( ) Failed Loop: PATH ( ), LOOP( ) Failed Loop: PATH ( ), LOOP( )
2. Isolating an HDU that caused the failure

PATH Number( ) LOOP Number( ) With All HDUs bypass 1st diagnosis result 2nd diagnosis result
(with [Clear ALL] clicked) OK NG OK NG

3. Identifying a failed unit








Unit-14 with all 1st diagnosis result 2nd diagnosis result
HDUs Connected OK NG OK NG

Failed Unit Unit( ), (Unit( ), Unit( ))
4. Identifying an HDU that caused the failure

(with [Clear] clicked)







With HDU-14 1st diagnosis result 2nd diagnosis result
Connected OK NG OK NG

Failed HDU HDU( ), (HDU( ), HDU( ))

OK NG OK NG


TRBL 06-0980-01
(g) Check List #2 for Failed HDU Isolation (for all HDUs)
operation.
CL#2-1
1 Identifying an HDU that caused the failure [Path ( ) Loop ( )]
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------

TRBL 06-0990-01
CL#2-2
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------

TRBL 06-1000-01
CL#2-3
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------

OK NG OK NG


TRBL 06-1010-01
(3) Procedure for Recovery from Loop Failure (in the case of a subsystem down occurs in the single
controller configuration)
The Loop Failure Detection Function cannot be used because it is impossible to start the
subsystem. Therefore, identify the failed HDU following the procedure below.
NOTE : Execute the procedure recording the history of locating the failed part on the
(e) Check List #3 for Failed HDU Isolation (for all HDUs) (TRBL 06-1060).
(a) Turn off/on the subsystem.

Check if the subsystem recovers from a starting failure.
START
Turn off the AC Power Unit Switches of

all the disk array units.
Turn on the AC Power Unit Switches of

Yes
Subsystem can be started?
No
A simple trace is got and sent to the
(b) Identifying the failed HDU Technical Support Center for coping with
(TRBL 06-1030) troubles in order to be analyzed.
END

TRBL 06-1020-01
(b) Identifying the failed HDU

Start the subsystem in the status that the HDU is isolated from the subsystem, and identify
the HDU causing a starting failure.
START
The HDU that has been pulled out is not
the failed one. Examine the next HDU.(*1)

Pull out one of the HDUs whose

ACTIVE LEDs for indicating subsystem
status are blinking in a manner different
from the other HDUs. (If an HDU has
already been pulled out, insert it into its
original position, and then pull the next
HDU out.)

Which of the following messages was displayed when starting the subsystem?
When the following message was displayed, go to c.
A Loop initialization failure message is displayed (the removed HDU is not detached since the
subsystem is in the ALARM status)
Cx RA1000 Loop Error (All unusable Loops were detected in the FLASH control part.)
or
C0 HE0710 Backend loop change error [OWN]
(The unusable Loop on the Controller #0 side was detected in the RAM control part.)
(The unusable Loop on the Controller #1 side was detected in the RAM control part.) c
or
Cx HE0100 Backend down [All loop NG]
(The subsystem cannot be controlled/monitored since usable Loop is unavailable in the subsystem.)
When the following message was displayed, go to d.
Loop initialization succeeded, but an error message for the configuration check on the starting
process was displayed (the removed HDU is not detached since the subsystem is in the ALARM
status).
Cx HH0C50 HDU changed before PS ON (The Disk Drive, which was used up to the last time, is not
installed when PS is ON.)
d
The HDU that has been pulled out is a
failed HDU.(*1)
(c) Reconfirm that the HDU concerned

caused the failure (TRBL 06-1040)
*1 : Because the recovery actions are started automatically when the spare disk exists, it is necessary to wait for
completion of the disk drive recovery twice.

TRBL 06-1030-01
(c) Reconfirm that the HDU concerned caused the failure

Install the specified HDU in the original location, start the subsystem and check that the error
occurs again.
START

Insert the HDU identified in Step (b) into

its original position.


Check that the following message is displayed.

The following displayed message confirms that the HDU identified in the procedure (b) is a cause of the
failure.
A Loop initialization failure message is displayed (the removed HDU is not detached since the
subsystem is in the ALARM status)
Cx RA1000 Loop Error (All unusable Loops were detected in the FLASH control part.)
or
or
Cx HE0100 Backend down [All loop NG]
(The subsystem cannot be controlled/monitored since usable Loop is unavailable in the subsystem.)
Processed to Step (d) and replace the HDU.
(d) Replacing a failed HDU

(TRBL 06-1050)

TRBL 06-1040-01
(d) Replacing a failed HDU
START

Replace the failed HDU with a new HDU.

(Refer to the Replacement 2.2.1
Replacing Disk Drive (REP 02-0050).)

The subsystem is started in the state in

which a WARNING has been issued to it.
The new Disk Drive that has been

replaced is detached because of
inconsistency of the WWN.
Because the Disk Drive is detached, data

restoration to the Spare Disk is started.
After the data restoration to the Spare Disk

is completed, pull out the detached Disk
Drive (replaced Disk Drive) and insert it
again.
Restoration of the Disk Drive is started

and the WARNING has been issued to
the subsystem is removed after the
restoration is completed.
END

TRBL 06-1050-01
(e) Check List #3 for Failed HDU Isolation (for all HDUs)
operation.
CL#3-1
--------------------------------------------------------------------------------------------------------
Unit (0)
Installation OK NG Installation OK NG
--------------------------------------------------------------------------------------------------------
Unit (1)
--------------------------------------------------------------------------------------------------------
Unit (2)
--------------------------------------------------------------------------------------------------------
Unit (3)
--------------------------------------------------------------------------------------------------------
Unit (4)
--------------------------------------------------------------------------------------------------------
Unit (5)
--------------------------------------------------------------------------------------------------------

TRBL 06-1060-01
CL#3-2
--------------------------------------------------------------------------------------------------------
Unit (6)
--------------------------------------------------------------------------------------------------------
Unit (7)
--------------------------------------------------------------------------------------------------------
Unit (8)
--------------------------------------------------------------------------------------------------------
Unit (9)
--------------------------------------------------------------------------------------------------------
Unit (10)
--------------------------------------------------------------------------------------------------------
Unit (11)
--------------------------------------------------------------------------------------------------------
Unit (12)
--------------------------------------------------------------------------------------------------------

TRBL 06-1070-01
CL#3-3
--------------------------------------------------------------------------------------------------------
Unit (13)
--------------------------------------------------------------------------------------------------------
Unit (14)
--------------------------------------------------------------------------------------------------------

TRBL 06-1080-01
(4) Actions to be taken when one of the message codes I5Y400 through I5Y700 is displayed
[Recovery method]
START
Collect the simple trace.

(Refer to 7.3 Collecting simple trace
(TRBL 07-0040).)
Combined messages are displayed

following the W080xy.
Is a message showing the detached Yes

part displayed following the W080xy?
No
Is a message showing the detached Yes
part displayed following the I301xy or
I301AT? Replace the part that was displayed as a detached
No part in the message.
yW060xy, W060AT, : Refer to the
Replace the part that was given the highest
W061xy, W061AT, Replacement 2.2.1
priority in the message I5Y900.(*1)
W0GG00, W0GH00, Replacing Disk Drive
y I5Y400: Refer to the Replacement 2.2.1
W0GJ00, W0GK00 (REP 02-0050).
Replacing Disk Drive (REP 02-0050).
yW090xy, W090AT, : Refer to the
W0GA00, W0GB00, Replacement 2.2.9
Replacing ENC Unit/SENC Unit (REP
W0GC00, W0GD00 Replacing ENC
02-0830).
Unit/SENC Unit (REP
y I5Y60x: Refer to the Replacement 2.2.5
02-0830).
Replacing Control Unit (REP 02-0390).
y W0100x:
y I5Y700: Refer to the Replacement
2.2.10 Replacing ENC cable (REP
Control Unit (REP 02-0390).
02-0910).
(Up to five parts are displayed in order of
priority.)
Follow the recovery procedures, I301xy

Replace the same parts again.
or I301AT for the maintenance
Is a message notifying of the recovery No

displayed after the replacement?
Yes
Is the message W080xy displayed Yes

after the replacement?
No
A To TRBL 06-1100 END
*1 : Replace parts according to the order of priority shown in the message I5Y900 displayed after the first
detachment of the loop. Though a message of the same kind may be displayed repeatedly, neglect it.

TRBL 06-1090-01
From TRBL 06-1090 A

displayed after the replacement?(*1)
Yes
after the replacement? END
No
Replace the part which was given the next

highest priority in the message, I5Y900.(*2)
Replacing Disk Drive (REP 02-0050).
y I5Y500: Refer to the the Replacement
2.2.9 Replacing ENC Unit/SENC Unit
(REP 02-0830).
y I5Y60x: Refer to the Replacement 2.2.5
Replacing Control Unit (REP 02-0390).
y I5Y700: Refer to the Replacement
2.2.10 Replacing ENC cable (REP
02-0910).

displayed after the replacement?(*1)
Yes
END
after the replacement?
No
Were all the parts displayed in the No
message I5Y900 replaced?
Yes
Subsystem went down? Yes
No
Contact the Technical Support Center. Follow (2) Procedure for Recovery from
(Send the trace that was collected before Loop Failure (in the case of a subsystem
starting the part replacement.) down occurs in the dual controller
configuration) (TRBL 06-0830) for the
maintenance.
END END
*1 : The message on recovery displayed for each part is shown below.
I007xy, I009xy: Disk Drive
I00Bxy: ENC Unit or ENC cable
I0010x: Control Unit
In the same way, the message on failure displayed for each part is shown below. If any of the following messages
is displayed, replace the same part again.
W073xy: Disk Drive
I605xy, W0B0xy: ENC Unit or ENC cable
W0100x: Control Unit
*2 : Replace parts according to the order of priority shown in the message I5Y900 displayed after the first
detachment of the loop. Though a message of the same kind may be displayed repeatedly, neglect it.

TRBL 06-1100-01
6.1.15 A failure occurred during operation : Case 5 (Incomplete writing)

(The command for reassignment was sent from a host computer to an LU of RAID 0)

MM/DD/YYYY HH:MM:SS Cx W0G0xy Unreadable PIN detected (Unit-x, HDU-y) :MANUAL/STRC
Date Time Detect Controller #
[Recovery method]
START
Find LUs with pinned data (the number of

segments is not 0) using the menu(*1)
for reference of information on whether
pinned data exists or not.
Find an LU defined as a RAID group one

of whose components is the failed Disk
Drive, from the LUs with pinned data.
Back up the LU that was found.
Request the customer to check data to

see if the user data is not destroyed.
Is there destroyed data? Yes
No
Format(*2) the object LU concerned. Format(*2) the object LU concerned.
Make sure that an Information Message, Make sure that an Information Message,
ID4000 Unreadable PIN recovered is ID4000 Unreadable PIN recovered is
displayed and the WARNING LED displayed and the WARNING LED
(orange) on the front side of the (orange) on the front side of the
subsystem goes out. subsystem goes out.
Restore(*2) all the backed up data of the Because the backup may be unable to
LU concerned. be done, restore the data previously
backed up (data that the customer
backed up).
END END
*2 : Concerning the backup and restoration, request the customer to do them.
System Parameter 3.3 Setting of LU [Procedure e-F]Formatting LU (SYSPR 03-0280)).

TRBL 06-1110-01
6.1.16 A failure in Copy-on-write SnapShot occurs

When Copy-on-write SnapShot is restored, an incomplete write error was recorded to the
primary VOL to be copied since the unreadable area exists on the pool side.

MM/DD/YYYY HH:MM:SS Cx I6D300 Unreadable PIN resisted (Unit-x,HDU-y,LU-z) :MANUAL/STRC
Date Time Detect Controller# Pool LU Disk Drive(*1) Primary VOL (*2)
[Recovery method]
START
Replace the Disk Drive with an

incomplete write error in the pool LU.
Replacing Disk Drive (REP 02-0050).)
Back up the primary VOL recorded an

incomplete write error and the secondary
VOL set in the pool LU with an
incomplete write error.(*1)
Request to cancel the pair of the primary

VOL and the secondary VOL set in the
LU with an incomplete write error in the
user, and cancel pool setting in the pool
LU with an incomplete write error.
Format the pool LU with an incomplete

write error and the primary VOL recorded
an incomplete write error.
Restore all the primary VOL data backed

up for the primary VOL recorded an
incomplete write error. Moreover, if
some data cannot be backed up, restore
the previously backed up data.
Request a pair recovery to the user. (*2)
END
*1 : If the pair is cancelled, the secondary VOL data is lost. Back up the secondary VOL before canceling the pair.
*2 : The secondary VOL data backed up and the primary VOL have the same capacity. Therefore, do not restore the
secondary VOL data backed up for the secondary VOL, which executed pair setting again.

TRBL 06-1120-01
6.2 Initialization procedure for configuration information
NOTE : Be careful that the whole data on the disk will be erased (RAID groups and LU
definitions will be initialized.) when this operation is performed.
NOTE : Be careful that if there is a LU whose access attribute is set by Data Retention
Utility, initialization of configuration information is not possible.
(1) Turn on the main switch of the subsystem.

(2) Entering the Maintenance mode by WEB is required to initialize Configuration Information.
The method for entering the Maintenance mode varies depending on statuses of the READY LED
(green) and ALARM LED (red).
y When the READY LED (green) is on, proceed to the procedure starting from the step (4).
y When the ALARM LED (red) is on, wait for three minutes after making sure of the lighting of
it, proceed to the procedure starting from the step (4).
y Also proceed to the procedure starting from the step (3) in the case where the READY LED
(green) and ALARM LED (red) do not come on after waiting for ten minutes when the power is
turned on. (Refer to Figure 6.2.1.)
(3) Make sure that the WARNING LED (orange) on the Front Bezel of RKM/RKS is not blinking fast (at
intervals of 125 ms). If it is blinking fast, wait for a while (80 seconds at the longest). It will
cease to blink fast. There is no problem if it blinks slowly (at intervals of one second).
(4) Changing the Maintenance Mode.
y Single Controller
Press the RST SW of the single Control Unit. (While pressing RST SW, the RST LED is on.)
Use a tool with a thin tip (a precise screwdriver, etc.) because the hole of RST SW is small (3
mm in diameter).
y Dual Controller
(a) Press the RST SW of the Control Unit #0. (While pressing RST SW, the RST LED is on.)
mm in diameter).
(b) Press RST SW on Controller No.1, right after CALM LED turned on (within ten (10) seconds
after CALM LED turned on).
(Sometimes the buzzer may beeps when the RST SW is pressed, however, you do not have to
stop it until these operations are completed.)
When the CALM LED of the Control Unit #0 does not go out in spite of the above operation,
power off the subsystem, return to step (1) without pulling out nor insert the Controller, and
execute the procedure over again.
NOTE : Because the Control Unit is shutdown status for the Maintenance Mode, the
command from the host is impossible execution. Please change it to the
Maintenance Mode after the confirmation of separation of the device from the
host or shutdown of the host.
When CALM LED on Control Unit #0 turns off and READY LED on Front Bezel turns off, it
transfers to Maintenance mode.

TRBL 06-1130-01
ALARM LED (red)

WARNING LED (orange)
READY LED (green)
POWER LED (green)
WARNING LED (o
POWER LED (gree
(a) Rackmount model of RKM/RKS (b) Rackmount model of RKAJ

RST SW CALM LED (red) RST SW CALM LED (red

CLASS 1 CLASS 1

Control Unit #1
Control Unit #0
(c) Control Unit of RKM (c) Control Unit of RKS
Figure 6.2.1 Indication Locations of LED
(5) Enter the IP address of the LAN connector for maintenance, to which the service PC is
connected, from the browser. When the Web has already been connected, update the page by
pressing the Update button. (For the procedure for connecting the Web, refer to Chapter 3.
Before Starting WEB Connection (TRBL 03-0000).)
[Password].

TRBL 06-1140-01
(6) Click Others in the menu frame.

The following window appears.
(7) Select the Configuration Clear radio button of [Configuration Clear Mode], then click the
Change button.
Current of the Configuration Clear Mode is displayed as Configuration Clear.
(8) Click Go To Normal Mode. There are two Go To Normal Mode buttons, one at the top of
the menu frame and the other at the bottom. Select either of them.
The following window is displayed while the above operation is executed.

TRBL 06-1150-01
(9) The following confirmation message is displayed at the later time for a while. Please click
[OK] for the continuation.
The following window is displayed while the above operation is executed.
(10) If rebooting is finished, the subsystem is ready. (It takes about three minutes usually to get
Ready.)
Make sure that the READY LED on the front side of the subsystem comes on.
When it is blinking at high speed, make sure that it lights on after waiting for the maximum of
30/50 minutes.

TRBL 06-1160-01
6.3 Procedure for Recovery from Path Blockade when the TrueCopy remote replication Function
Is Used
(1) Procedure for recovery from path detachment
(a) General flowchart of procedure for recovery from path detachment
Occurrence of path
detachment
Get a cause of the path detachment from See [Window 1] Image of Information Message
the Information Message window. window (TRBL 06-1180).
Yes Is the cause of detachment displayed

in the information messages?
No
Get the cause of the path detachment from See [Window 2] Image of Path Detachment Cause
the TrueCopy remote replication Path window (TRBL 06-1180).
Information window(*1).
Make the recovery following the procedure
Was the getting of the cause of the No given in the message shown in Table
path detachment successful(*2)? 6.3.1 Path Detachment Causes and
Priority Orders of Maintenance Works
Yes (TRBL 06-1220).
Perform the maintenance work appropriate See (b) Maintenance to be done against each
for the cause of the path detachment. cause of path detachment (TRBL 06-1200) Yes
No Is a message, This recovery failed.
displayed?
Perform revalidation(*1) using the See [Window 3] Image of revalidation
TrueCopy remote replication Path direction window (TRBL 06-1180).
Information window. Make the recovery following the procedure
given in the message shown in Table
See [Window 4] Image of revalidation 6.3.2 List of Messages Displayed when
result window (in the case of abnormal Getting of Path Detachment Cause Failed
termination) (TRBL 06-1190). (TRBL 06-1240).
Was the revalidation completed No
normally(*3)?
Yes
See [Window 5] Image of revalidation result window
(in the case of normal termination) (TRBL 06-1190).
Verify that the recovery from the path
detachment was completed successfully
by viewing the Information Message and
Warning Information windows.
Is any of the other paths detached? Yes

Repeat the same procedure
No for the other detached path.
Work has completed
*1 : The recovery from the path detachment may have been made by virtue of the automatic path recovery function.
When a message informing of the completion of the recovery is displayed in the Information Message window, no
revalidation is necessary. If the recovery has not been made, be sure to perform the revalidation.
*2 : For the message when the acquisition of the cause of the path detachment was unsuccessful, refer to Table 6.3.1
Path Detachment Causes and Priority Orders of Maintenance Works (TRBL 06-1220).
*3 : For the message when the revalidation is performed, refer to Table 6.3.3 List of Messages Displayed when Path Is
Revalidated (TRBL 06-1250).

TRBL 06-1170-01
[Window 1] Image of Information Message window
[Window 2] Image of Path Detachment Cause window
[Window 3] Image of revalidation direction window

TRBL 06-1180-01
[Window 4] Image of revalidation result window (in the case of abnormal termination)
[Window 5] Image of revalidation result window (in the case of normal termination)

TRBL 06-1190-01
(b) Maintenance to be done against each cause of path detachment

The failed part cannot be ascertained depending on the type of the failure because the path
detachment is a route failure.
Therefore, this manual only defines zones where a failure occurs for each path connection
form and make the priority order of the zones and parts within the each zone clear.
[Procedure 1] Make sure of the path connection form.
c e
Direct g
Local DF d f Remote DF
connection
c : Local DF main body

d : Local DF interface
e : Remote DF main body
f : Remote DF interface
g : Connecting cable between the DFs
h l 13
j
Connection 16 17 18
Local DF i 11 SW 12 14 SW 15 k Remote DF
via SW
A B C D E F G
h : Local DF main body Zone A :h

i : Local DF interface Zone B : i 11 16
j : Remote DF main body Zone C :l

k : Remote DF interface Zone D : 12 14 17
l : Local side SW Zone E : 13 15 18
11 : Local side GBIC of the local side SW Zone F :k

12 : Remote side GBIC of the local side SW Zone G :j
13 : Remote side SW
14 : Local side GBIC of the remote side SW
15 : Remote side GBIC of the remote side SW
16 : Connection cable between the local DF and the local
side SW
17 : Connection cable between the local side SW and the
remote side SW
18 : Connection cable between the remote DF and the
remote side SW

TRBL 06-1200-01
[Procedure 2] Perform a maintenance work referring to the priority order of zones and parts
shown in Table 6.3.1 according to a cause of the path detachment.
NOTE : y Every time when a part is replaced from the order with a high priority, go to
[Procedure 3] (TRBL 06-1240), and perform the revalidation in the
TrueCopy Path Information window of the WEB following 6.3 (1) (a) General
flowchart of procedure for recovery from path detachment (TRBL 06-1170).
y The maintenance method varies depending on the reference number (c to 18 )
that represents each part.
The maintenance method corresponding to each number is shown below.
cehj Since a failure of some kind has occurred in each DF700
subsystem, perform a maintenance work according to the LED
indications or a WEB message.
dfik Replacement of the I/F portion is required.
When replacing the I/F portion, an entire CTL must be
replaced in the case of the part of the basic port (Port #0)
because the part is integrated with the CTL, whereas only the
Interface Board is to be replaced in the case of the part of the
added port (Port #1).
Other than the above Replacement the SW main body, the GBIC, or the
cable.

TRBL 06-1210-01
Table 6.3.1 Path Detachment Causes and Priority Orders of Maintenance Works
Priority order of maintenance
No. Message text Path detachment cause Failure symptom Path recovery method
objects(*1)
1 Link error in the attached The threshold value of the A link down was detected. Direct : d f g The path revalidation
link route failure counter on the A link failure was detected. SW : B C from the WEB must
(Port-x) local side was exceeded. be done.
2 Link error in the path The threshold value of the An illegal transferred data Direct : d f g
path route failure counter length was detected. SW :
was exceeded. BFDCE
3 Link down time-out The link down time of the The link down time of the Direct : d f g Automatic recovery
(Port-x) path set for the port port for which a path has SW : B C
concerned elapsed longer already been set elapsed
than 15 seconds. longer than 15 seconds.
4 Path not connected The remote DF concerned No remote DF, for which a Direct :
is not connected. path was to be set, existed a f e d g
on the loop though a log- SW :
in was requested. a G F D E C
The WWN which has been a : Firstly, check if the
set was not registered in remote DF is connected
the SW. and if the connection is
correctly made.
5 Path login failed The log-in to the path Though a log-in to a port Direct : The path revalidation
concerned failed. expected to exist was fdg from the WEB must
attempted, it failed SW : be done.
because allowable number GFDBE
of retrials were not C
successful. (F : k 15 18 )
6 Path login resource Resource of the path Insufficiency of the
(*2)
Direct : f
shortage concerned was insufficient. resource was reported in a SW : k
response made at the time The system configuration is
of the log-in. illegal. (Propriety of the
system configuration must be
checked by an SE or a user.)
7 Fabric connection failed Switch trouble The FLOGI sequence Direct : None
(Port-x) terminated abnormally. SW : B C
(Sending and response of
FLOGI/ PLOGI/ RCS_ID/
RFT_ID/ PRT_ID/
SCR/RSCN terminated
abnormally.)
*1 : A numeral and alphabetic character denote a part and zone respectively.
Priority order of failed parts in each zone (a zone contains more than one part) is shown below.
11
Zone B : i 16
Zone D : 12
14
17
Zone F : 15
k 18
*2 : The insufficient resource means that 128 log-ins have already been made for the port when 128 log-ins per port
are allowed.

TRBL 06-1220-01
Priority order of maintenance

No. Message text Path detachment cause Failure symptom Path recovery method
objects(*1)
8 RSP not ready Command RSP failure Not Ready Direct : e The path revalidation
(Key [02], Code [xxyy]) (Failure of the command SW : j from the WEB must
9 RSP medium error issued from a DF to Medium Error Direct : e be done.
(Key [03], Code [xxyy]) another DF) SW : j
10 RSP hard error Hard Error Direct : e
(Key [04], Code [xxyy]) SW : j
11 RSP illegal request Illegal Request Direct : c e
(Key [05], Code [xxyy]) SW : h j
12 RSP abort command P Aborted Command (path) Direct : f d g
(Key [0B], Code [xxyy]) SW :
FBDEC
13 RSP abort command C Aborted Command (CTL) Direct : e
(Key [0B], Code [xxyy]) SW : j
14 RSP miscompare Others Direct : c e
(Key [0E], Code [xxyy]) SW : h j
RSP status error [xx]
RSP other field error
RSP etc. (Key [xx])
15 Command time out Command time-out (Failure Two or more times of time- Direct : f d g The path revalidation
of the command issued out were detected in SW : from the WEB must
from a DF to another DF) execution of the same G F D B E be done.
command. C
(F : k 15 18 )
16 Remote sequence Inconsistency of the remote The sequence No. of the Direct : e The path revalidation
number error DF sequence No. remote DF is inconsistent. SW : j from the WEB must
be done.
17 Path alarm for CTL CTL detachment A detachment of the own Direct : c Automatic recovery
alarm controller occurred. SW : h
(Remote-x, Path-y)
18 Port un-mounting error Non-installation of the port The port is not installed. Direct : d The path revalidation
SW : i from the WEB must
be done.
19 Remote option disable Locking of the remote DF The [TrueCopy remote Direct : e The path revalidation
[TrueCopy Basic] [TrueCopy remote replication] priced optional SW : j from the WEB must
replication] function of the remote DF be done
is locked.
*1 : A numeral and alphabetic character denote a part and zone respectively.
Priority order of failed parts in each zone (a zone contains more than one part) is shown below.
Zone B : 11
i 16
Zone D : 12
14
17
Zone F : 15
k 18

TRBL 06-1230-01
[Procedure 3] Proceed to the procedure subsequent to 6.3 (1) (a) General flowchart of
procedure for recovery from path detachment (TRBL 06-1170).
When the getting of the path detachment cause has failed or the revalidation has terminated
abnormally, perform a maintenance work following the recovery procedure shown in Table
6.3.2 and Table 6.3.3 according to the message displayed.
Table 6.3.2 List of Messages Displayed when Getting of Path Detachment Cause Failed
No. Sub-window message Meaning of message Recovery method
1 Cannot get alarm information because The cause cannot be get because the Unlock and validate the [TrueCopy remote
specified function is lock. [TrueCopy remote replication] function is replication] function and get the cause of the
locked. path detachment again.
2 Cannot get alarm information because it The cause cannot be get because the Get the cause of the path detachment again
is booting now. subsystem is being booted. after the subsystem enters the Ready status.
3 Cannot get alarm information because it The cause cannot be get because the Update the browser. If the path is still
does not register for remote equipment. specified remote DF number is illegal. detached, get the cause of the path
detachment again.
4 Cannot get alarm information because The cause cannot be get because the Validate the [TrueCopy remote replication]
specified function is disable. [TrueCopy remote replication] function is function and get the cause of the path
invalid although it is unlocked. detachment again.
5 Cannot get alarm information because it The cause cannot be get because the Update the browser. If the path is still
does not register for this path. specified path does not exist. detached, get the cause of the path
detachment again.
6 Cannot get alarm information because The cause cannot be get because the Update the browser. If the path is still
this paths status is normally. specified path has already become detached, get the cause of the path
normal. detachment again.

TRBL 06-1240-01
Table 6.3.3 List of Messages Displayed when Path Is Revalidated

No. Sub-window message Meaning of message Recovery method
1 Do you recover this path? Do you want to revalidate the specified
path?
2 Executing... The revalidation of the specified path is
being executed.
3 This recovery was completed The revalidation of the specified path was
successfully. completed normally.
4 This recovery failed. The revalidation of the specified path It is presumed that the path was detached
terminated abnormally. owing to another cause or the replaced part
was not correct.
Perform a maintenance work again following
the procedure against the path detachment.
5 Cannot recover this path because The path revalidation cannot be done Unlocked and validate the [TrueCopy remote
specified function is lock. because the [TrueCopy remote replication] replication] function and execute the path
function is locked. revalidation again.
6 Cannot recover this path because it is The path revalidation cannot be done Execute the path revalidation again after the
booting now. because the subsystem is being booted. subsystem enters the Ready status.
7 Cannot recover this path because it does The path revalidation cannot be done Execute the path revalidation again after
not register for this remote equipment. because the specified remote DF number updating the browser.
is illegal.
8 Cannot recover this path because CTL is The path revalidation cannot be done Execute the path revalidation again after
alarm. because the controller is detached. recovering the controller from the detachment.
9 Cannot recover this path because The path revalidation cannot be done Execute the path revalidation again after
specified function is disable. because the [TrueCopy remote replication] validating the [TrueCopy remote replication]
function is invalid though it is unlocked. function.
10 Cannot recover this path because it does The path revalidation cannot be done Execute the path revalidation again after
not register for this path. because the specified path does not exist. updating the browser.
11 Cannot recover this path because this The path revalidation cannot be done Execute the path revalidation again after
paths status is normally. because the specified path has already updating the browser.
become normal.
executing LU Format. because an LU formatting is being LU formatting is completed.
executed.
executing Synchronized cache. because the SyncCache command is execution of the SyncCache command is
being executed. completed.
executing Array unit shutdown. because the pseudo-deliberate shutdown pseudo-deliberate shutdown has been
is being executed. completed.
15 Cannot recover this path because Power The path revalidation cannot be done Execute the path revalidation again after
OFF> because the deliberate shutdown is being starting up the subsystem.
executed.

TRBL 06-1250-01
Chapter 7. Collecting Error Information

When any failure occurs, the information on it saved in the Control Unit can be collected.
The purpose of this function is to facilitate pursuit of factors of failures and shorten the time
consumed for analysis of them.
The failure information is collected by the following three methods.
(1) Collection simple trace

Use the normal or maintenance mode using a Web browser to download the trace information
and configuration information from the controller to the browser terminal.
You can collect a simple trace while the device is running. You can also collect it when the
ALARM LED is lit on the device.
For details of the procedure for the collection, refer to 7.3 Collecting simple trace (TRBL 07-
0040).
(2) Collecting CTL alarm trace

The controller contains information about the time when the controller is shut down. Use the
normal or maintenance mode using a Web browser to download this information from the
controller to the browser terminal.
The CTL alarm trace can be collected after recovering the blocked controller.
For details of the procedure for the collection, refer to 7.4 Collecting CTL Alarm Trace
(TRBL 07-0080).
(3) Collecting memory dump

The information saved in the Controller is downloaded to the browser terminal by using the
maintenance mode of WEB.
Controller 0/1 Common
:
For details of the procedure for the collection, refer to 7.5 Collecting Memory Dump (TRBL
07-0130).
The failure information is collected by different methods, depending on the configuration and
condition of the unit.
Collect the failure information securely according to 7.2 Judge collection of failure
information (TRBL 07-0020).

TRBL 07-0000-01
7.1 Time to collect failure information

Collect the failure information in the following cases.
(1) A failure was reported to the work-station server, client for maintenance, WEB browser, or
(2) The WARNING LED (Orange) of the unit blinked or lighted up.
(3) The ALARM LED (Red) of the unit lighted up.

TRBL 07-0010-01
7.2 Judge collection of failure information

(1) Flow of judgment of collection of failure information for system having single Controller
(without a redundancy Controller)
START Without a redundant Controller : Only one Controller is installed.
Is there any
environment connectable with Yes
subsystem to LAN?
(maintenance PC and close cable)
No Do you need to collect a No

memory dump(*1)?
Yes
Can you stop the customers No
application?
Yes
No Do you need to collect
System off operation(*2). the CTL alarm
*
Yes
No Can you collect
the CTL alarm trace?
END
Collecting Memory Dump. Collecting Simple trace. CTL alarm trace.
For details, refer to 7.5 (2) For details, refer to 7.3 For details, refer to 7.4
Procedure for a memory dump Collecting simple trace (TRBL Collecting CTL Alarm Trace
collection in the single system 07-0040). (TRBL 07-0080).
(for RKM/RKS) (TRBL 07-
0140).
*1 : How to determine whether you need to collect the memory dump and controller shutdown trace for a log message
c See the last five characters (124th to 128th characters) in the log message.
(For details about the log messages, refer to 4.3 Confirm log messages (TRBL 04-0100).)
d /STRC : You need to collect the simple trace.
/CTRC : You need to collect the controller shutdown trace.
/FDMP : You need to collect the memory dump.
*2 : When the power control mode is Remote (when the rotary switch is set to 2, 4, 5, 6, or 8), take care that the
subsystem power is also turned off if the host computer is powered off. (Refer to the Installation 1.8 Setting the
Power Control Mode (Local/Remote Mode) (INST 01-0320). When the subsystem is powered off, a memory dump
cannot be done.)
When the mode is Remote, perform the memory dump in the state in which no access (I/O) from the host
computer is made. (Refer to 7.5 Collecting Memory Dump (TRBL 07-0130).)

TRBL 07-0020-01
(2) Flowchart for determining to produce a memory dump in the case of the dual configuration.
(with the redundant Controller.)
START With a redundant Controller : Two CONTROLLERS are installed.
Is there any environment

connectable with subsystem Yes
to LAN?
(Maintenance PC and close
cable)
No
Do you need to collect a No

memory dump(*1)?
Method of confirming blockage of single Controller
Yes
The following message is displayed in the WEB error log.
W0100X CTL alarm (CTL-X)
x : Blocked Controller #
CALM LED (Red) on the Controller is lighting up.
Can you stop the customers No

application?
Yes
Is one of the controllers
No
blocked (is W0100X CTL
alarm-X (CTL-x) displayed)?
Yes
System off operation(*2). No Do you need to
collect the CTL alarm
Yes
No Can you collect
the CTL alarm trace?
Yes
END Proceed to a memory

Proceed to a memory Collecting Simple trace. CTL alarm trace.
dump. dump of the blocked
Controller.
For details, see 7.5 (3) For details, see 7.5 (4) For details, see 7.3 For details, see 7.4
Method of collecting Method of collecting Collecting simple trace Collecting CTL Alarm
memory dump from dual- memory dump from dual- (TRBL 07-0040). Trace (TRBL 07-0080).
Controller system-1 Controller system-2
(TRBL 07-0170). (TRBL 07-0200).
*1 : How to determine whether you need to collect the memory dump and controller shutdown trace for a log message
c See the last five characters (124th to 128th characters) in the log message.
(For details about the log messages, refer to 4.3 Confirm log messages (TRBL 04-0100).)
d /STRC : You need to collect the simple trace.
/CTRC : You need to collect the controller shutdown trace.
/FDMP : You need to collect the memory dump.
*2 : When the power control mode is Remote (when the rotary switch is set to 2, 4, 5, 6, or 8), take care that the
subsystem power is also turned off if the host computer is powered off. (Refer to the Installation 1.8 Setting the
Power Control Mode (Local/Remote Mode) (INST 01-0320). When the subsystem is powered off, a memory dump
cannot be done.)
When the mode is Remote, perform the memory dump in the state in which no access (I/O) from the host
computer is made. (Refer to 7.5 Collecting Memory Dump (TRBL 07-0130).)

TRBL 07-0030-01
7.3 Collecting simple trace

Using Simple Trace Collection, the trace information stored in the controller and the
configuration information are collected.
The method of collecting the simple trace is shown below.

TRBL 07-0040-01
(1) Before collecting the simple trace

(a) Items to be prepared
Collection is performed using the normal mode of WEB or Maintenance mode.
For connecting to the WEB, a PC terminal with Browser installed is necessary.
For collecting the simple trace, a Disk Drive with a space of 5 Mbytes at least is necessary.
(b) Connect the Device LAN Port for maintenance and the PC terminal with a LAN-cross-cable.
Control Unit #1
Control Unit #0

Cover Cover

CLASS 1 CLASS 1
(c) With Simple Trace Collection, the information of both controllers can be collected from one
controller. Therefore, this function does not need to be performed from both Controllers. (As a
file name during the collection, smpl_trc0.dat is provided for the collection from Control Unit
#0, and simpl_trc1.dat for the collection from Control Unit #1.)
(d) Make sure that the WARNING LED (orange) on the Front Bezel of RKM/RKS is not blinking fast
(at intervals of 125 ms). If it is, wait for a while (up to 80 seconds), and it stops blinking
fast. (If this LED is blinking slow (at the interval of 1 second), there are no problems.)
(e) Clear the cache of the browser following the procedure shown below so that the old data,
which was collected at the preceding time, should not be saved.
y In the case of Internet Explorer, select the [Tools] - [Internet Options] - [General] -
[Temporary Internet files] - [Delete Files] in this order.
y In the case of Netscape, select the [Edit] - [Preferences] - [Cache] - [Clear Cache] in this
order.
WARNING LED (orange) READY LED (green)

ALARM LED (red) POWER LED (green) WARNING LED (orange)
POWER LED (green)
(a) Rackmount model of RKM/RKS (b) Rackmount model of RKAJ/RKAJAT
Figure 7.3.2 Indication Locations and Names of LED (Front Bezel)

TRBL 07-0050-01
(2) Procedure for a simple trace collection

(a) Enter the IP address of the LAN connector for maintenance, to which the service PC is
connected, from the browser. When the Web has already been connected, update the page
by pressing the Update button. (For the procedure for connecting the Web, refer to Chapter
3. Before Starting WEB Connection (TRBL 03-0000).)
(b) Collect the simple trace according to the WEB and the following procedure.
Click Trace in the menu frame of Simple Trace.

TRBL 07-0060-01
(c) The following dialog is displayed.

Click the [Save] button.
(d) Select the place to save the file and file name (Default file name: CTL#0:smpl_trc0.dat,
CTL#1: smpl_trcl.dat) and click [Save](1).
The down-loading is started and the progress indicating message window is displayed.
When the down-loading completes, the progress indicating message window is closed.
In this procedure Simple trace is collected by WEB Normal mode. Similarly, Simple trace can
be collected by WEB Maintenance mode through Menu Frame.
For entering Maintenance mode, refer to the WEB 3.1 Transferring to the Maintenance
Mode (WEB 03-0000).
When the USB memory needs to store the simple trace information, refer to 7.6 Storing
simple trace information in the USB memory (TRBL 07-0230).
1 : There may be a case where the default file name is given as ctla_trc0.dat..dat depending on the setting of the
PC. In this case, reset the file name to ctla_trc0.dat or any other name.

TRBL 07-0070-01
7.4 Collecting CTL Alarm Trace

Through the CTL Alarm Trace collection, detailed information (the CTL Alarm Trace) on the
immediately previous Controller blockage stored in the Controller is collected.
Since the above-mentioned CTL Alarm Trace information is taken over from the blocked
Control Unit to the replaced Control Unit, it can be collected after the Control Unit is
recovered from the failure. If the Control Unit is blocked while collecting the CTL ALARM
TRACE may not be collected normally. Therefore, in this case, collect the CTL ALARM TRACE
again.
The method of collecting the CTL ALARM TRACE is shown below.
(1) Before collecting the CTL ALARM TRACE

The CTL Alarm Trace is collected in the normal mode or the maintenance mode of the WEB.
For collecting the CTL Alarm Trace, a Disk Drive with a space of 10 Mbytes at least is
necessary.
(b) Connect the Device LAN Port for maintenance and the PC terminal with a LAN cross cable.
Control Unit #1
Control Unit #0
RKM/RKS (Rear view) RKM/RKS (Rear view)

Cover Cover

CLASS 1 CLASS 1
(c) Collect the CTL Alarm Trace information from each Control Unit.
Save the files collected from different controllers into different directories or put different
names to them so that you will see from which controller they were collected.

TRBL 07-0080-01

POWER LED (green)
[Temporary Internet files] - [Delete Files] in this order.
y In the case of Netscape, select the [Edit] - [Preferences] [Cache] - [Clear Cache] in this
order.

TRBL 07-0090-01
(2) Procedure for collecting a CTL Alarm Trace

(a) Enter the IP address of the LAN connector for maintenance, to which the service PC is
by pressing the Update button. (For the procedure for connecting the Web, refer to Chapter
3. Before Starting WEB Connection (TRBL 03-0000).)
(b) Collect the memory dump according to the WEB and the following procedure.
Click CTL Alarm Trace in the menu frame of Trace.

TRBL 07-0100-01
If CTL Alarm Trace exists, the CTL Alarm Trace information window is displayed.
Description of information
Not Ready Indicates the situation where the trace area is not established in the
device.
No Data CTL Alarm Trace information does not exist or while information is
being created.
MM/DD/20YY hh:mm:ss CTL Alarm Trace information exists.
NOTE : When Not Ready or No Data is displayed on the description of
Information, or when the date of the information is different from that of the
collection of this time, the CTL Alarm Trace may not be collected normally.
Therefore, collect the Simple Trace.
If Simple Trace cannot be obtained through detached Control Unit, connect the
Maintenance PC to the Control Unit at the opposite side, and collect the Simple
Trace.
(c) Press the Download button on the Control Unit side to be collected in CTL Alarm Trace
information.(1)
(d) The following dialog is displayed. Click the [Save] button.
1 : An error message may be displayed. If it is displayed, click [OK], and collect the CTL Alarm Trace again after
waiting for a while.

TRBL 07-0110-01
(e) Select the place to save the file and file name (Default file name: ctla_trc0.dat) and click
[Save](1).
In this procedure is collected by WEB Normal mode. Similarly, CTL Alarm Trace can be
collected by WEB Maintenance mode through Menu Frame.
For entering Maintenance mode refer to WEB 3.1 Transferring to the Maintenance Mode
(WEB 03-0000).
1 : There may be a case where the default file name is given as ctla_trc0.dat.dat depending on the setting of the

TRBL 07-0120-01
7.5 Collecting Memory Dump

The method of collecting the Memory Dump is shown below.
(1) Before collecting the Memory Dump
The Memory Dump is collected in the maintenance mode of the WEB.
For collecting Memory Dump information, disk space of 480 Mbytes per one Control Unit is
required (RKM/RKS). (240 Mbytes for temporary data and 240 Mbytes for dumped memory
data)
Under ordinary maintenance works, disk space of no less than 50 Mbytes is required.
(b) Remove the cover on the Device Control Unit. Connect the LAN-Connecter for maintenance
and the LAN-Connecter of Maintenance PC with a LAN-cross-cable.
Control Unit #1
Control Unit #0

Cover Cover

CLASS 1 CLASS 1
(c) Collect the memory dump information from each Control Unit.
Save the files collected from different controllers into different directories or put different
names to them so that you will see from which controller they were collected.
[Temporary Internet files] - and [Delete Files] in this order.
y In the case of Netscape, select the [Edit] - [Preferences] - [Cache] - [Clear Cache] in this
order.

POWER LED (green)

TRBL 07-0130-01
(2) Procedure for a memory dump collection in the single system (for RKM/RKS)
(a) Please push the RST SW of Control Unit. (While pressing RST SW, the RST LED is on.)
mm in diameter).
(The Controller enters the WEB maintenance mode.)
Control Unit #1
Control Unit #0

RST SW CALM LED (red) RST SW CALM LED (red)

CLASS 1 CLASS 1
Figure 7.5.3 Indication Locations of Control Unit
(b) Enter the IP address of the LAN connector for maintenance, to which the service PC is
by pressing the Refresh button or click the [View] [Refresh]. (For the procedure for
connecting the Web, refer to Chapter 3. Before Starting WEB Connection (TRBL 03-0000).)
[Password].

TRBL 07-0140-01
The cache memory access failure occurs when the following window is displayed. refer to
WEB 3.1.1 WEB Operation in the Maintenance Mode during the Cache Memory Access
Failure (WEB 03-0040).
(c) Collect the memory dump according to the WEB and the following procedure.
Click Full Dump in the menu frame of Trace/Dump.
The following dialog is displayed. Click the [Save] button.

TRBL 07-0150-01
Select the place to save the file and file name (Default file name: logx.dat) and click
[Save](1).
There is no problem although it is displayed that the presumption remaining time is uncertain
in the dialog box during the download.
(d) Turn the power off.
(e) Compress the collected information. (for RKM/RKS)

Provide each personal computer with a data compression tool and compress the collected
information.
1 : There may be a case where the default file name is given as logx.dat.dat depending on the setting of the PC. In
this case, reset the file name to logx.dat or any other name. (x: Controller serial numbers)

TRBL 07-0160-01
(3) Method of collecting memory dump from dual-Controller system-1

Interrupting the customer operation and collecting memory-dump information of the both
Control Units under dual system configuration
NOTE : If either Control Unit is blocked, collect the memory dump from that Controller
first.
(a) Press the RST SW of the blocked Control Unit. (If both Control Units are normal or blocked,
press the RST SW of either one.) (While pressing RST SW, the RST LED is on.)
mm in diameter).
Wait for a while (about ten seconds) and check that the CALM LED of the Control Unit lights
up.
Within ten seconds after the CALM LED lights up, press the RST SW of the other Control Unit.
When ten seconds or longer pass after the CALM LED of the Control Unit concerned comes on,
return to the beginning of the step (a) and execute the procedure over again. (When the
above procedure is executed, the both Control Units enter the Maintenance mode of the
WEB.)
The CALM LED on the Control Unit of which RST SW was pressed first goes off, and READY LED
on the Front Bezel goes off.
Control Unit #1
Control Unit #0


CLASS 1 CLASS 1
(b) Input the IP address of the controller from which the memory dump will be collected, through
the browser. If the system has been connected to the WEB, press the Refresh button to
update the page.
[Password].

TRBL 07-0170-01

TRBL 07-0180-01
Select the place to save the file and file name (Default file name: logx.dat <x:Controller
serial numbers>) and click [Save](1).
(d) Return to (b) and collect the memory dump from the other Control Unit.
(Save the memory dump files collected from different Control Units into different directories
or put different names to them so that you will see from which controller they were
collected.)
(e) Turn off the power of the unit.
(f) Compress the collected information.

information.
this case, reset the file name to logx.dat or any other name.

TRBL 07-0190-01
(4) Method of collecting memory dump from dual-Controller system-2

Collecting memory-dump information of detached Control Unit under dual system configuration
NOTE : Precaution: Collect the memory dump from only the blocked Control Unit. (The
CALM LED (red) of the blocked controller is lighting up.)
(a) Press the RST SW of the blocked Control Unit. (While pressing RST SW, the RST LED is on.)
mm in diameter).
(The Control Unit will be set in the maintenance mode of the WEB.)
Control Unit #1
Control Unit #0


CLASS 1 CLASS 1
(b) Input the IP address of the Control Unit from which the blocked Control Unit, through the
browser.
If the system has been connected to the WEB, press the update button to update the page.
[Password].

TRBL 07-0200-01

If the following dialog is not displayed even after five minutes passed, click the [Close]
button on the upper right of the browser and close the browser. After that, open the
browser again and retry from the procedure (b).

TRBL 07-0210-01
Select the place to save the file and file name (Default file name: logx.dat <x:Controller
serial numbers>) and click [Save](1).
When the download is not completed(2) or the message window is not displayed even after
five minutes passed, click the [Close] button on the upper right of the browser and close the
browser. After that, open the browser again and retry from the procedure (b).
(d) Compress the collected information.

information.
this case, reset the file name to logx.dat or any other name.
2 : Refer to the content displayed in Full Dump in Trace/Dump listed in the menu frame of WEB for the standard
at time that the download of the memory dump is completed.

TRBL 07-0220-01
7.6 Storing simple trace information in the USB memory

Insert the USB memory in a service PC and give procedure to store the collected Simple Trace
in the USB memory.
(1) The USB memory outline

Data read/write is enabled only by inserting the USB memory in the USB port in the service PC.
(a) How to use the USB memory
NOTE : When using the USB memory in Windows XP/2000 for the first time, the USB
memory is automatically recognized and the driver is installed.
(i) Remove the USB memory cap and insert the memory in the USB port in the service PC.
USB port
Status indication light
USB memory
Figure 7.6.1 USB Memory Insertion
(ii) The Removal Disk icon is added to the My Computer.

(iii) The added icon indicates the USB memory.
(iv) Data read/write is enabled as well as the hard disk.
(b) The status indication light identifis the USB memory operation
The status indication light can identify the USB memory operation status inserted in the
service PC. Handle the USB memory with care depending on the operation status.
y Fast blink: during read/write operation
Do not remove the USB memory.
y Slow blink: waiting
It can be removed following the procedure when removing.

TRBL 07-0230-01
(2) Procedure for storing in the USB memory

(a) Store simple trace in the USB memory.
Store the simple trace information collected in 7.3 Collecting simple trace (TRBL 07-0040)
in the USB memory by copying and pasting.
(b) How to remove the USB memory

Perform the following procedure when removing the memory in the status that the service PC
power is on.
The following procedure is not necessary when removing the memory with the service PC
power turned off.
(i) Click the [ icon] in the task tray.

(ii) Click the displayed message.
(iii) Click the [OK] button if the message is displayed.
(iv) Check that the status indication light is slowly blinking (waiting) or lighting off before
removing the memory.

TRBL 07-0240-01

TRBL 07-0250-01
Chapter 8. Trouble Analysis by LED Indication

8.1 Trouble Analysis by LED Indication of Front Bezel
(1) LED positions on Front Bezel
The positions on LEDs are shown below.

POWER LED (green)
(2) Trouble analysis procedure

The states of the units indicated by the LED indication patterns of the Front Bezel and the
actions to take against them are shown below.
Table 8.1.1 LED Indication Patterns on Front Bezel

({ : On : Blinking : Off : Not depend)
LEDs
No RKM/RKS RKAJ/RKAJAT
State of unit Actions to take Failure
ALARM WARNING READY POWER POWER WARNING
(Red) (Orange) (Green) (Green) (Green) (Orange)
1(*1) { { { Normal. Recovery operation is not
necessary.
2 Power is turned off, Analyze the failure following Parts failure:
or failures of the 8.1 (3) (a) Trouble analysis (Basic Chassis)
Power Unit, two on the indication on the Drive failure:
Fan Assemblies or POWER LED of RKM/RKS. (Basic Chassis)
short-circuit of each (When the POWER LED is (RKM/RKS)
part occurs. not on) (TRBL 08-0040).
{ { Analyze the failure following Parts failure:
8.1 (3) (b) Trouble analysis (Additional
on the indication on the Chassis)
POWER LED of Drive failure:
RKAJ/RKAJAT. (Not POWER (Additional
LED on) (TRBL 08-0100). Chassis)
(RKAJ/RKAJAT)
*1 : This is not a failure status

TRBL 08-0000-01

LEDs
RKM/RKS RKAJ/RKAJAT
No State of unit Actions to take Failure
3 { Power Unit, Control 1. Check that power cable is Parts failure.
Unit or ENC connected correctly. (RKM/RKAJ/RKS
Unit/SENC Unit has 2. Check LED indication of /RKS/RKAJAT)
dual failed.
Power Unit. (Refer to
Table 8.2.3 LED
Indication Patterns on
Power Unit (TRBL 08-
0170).)
3. Check LED indication of
Control Unit. (Refer to
Table 8.2.5 LED
Indication Pattern-1 on
Control Unit (RKM/RKS)
(TRBL 08-0190), Table
8.2.6 LED Indication
Pattern-2 on Control Unit
(TRBL 08-0210).)
4. Check LED indication of
ENC Unit/SENC Unit.
(Refer to Table 8.2.9 LED
Indication Patterns on ENC
Unit (TRBL 08-0290),
Table 8.2.10 LED
SENC Unit (TRBL 08-
0310).)
4 { A failure occurred 1. Check LED indication of Parts failure.
during power-on Control Unit. (Refer to (RKM/RKS)
process. Table 8.2.7 LED
Control Unit (Fibre
Channel) (TRBL 08-
0230).)
2. If CALM LED of one
Control Unit or more does
not light up, wait READY
LED to light up (for at least
10 min).
3. Proceed to Chapter 3. Failure must be
Before Starting WEB detected with
Connection (TRBL 03- WEB.
0000), and then detect a
failure with WEB.

TRBL 08-0010-01

LEDs
RKM/RKS RKAJ/RKAJAT
5 (*1) { A serious failure Proceed to Chapter 3. Failure must be
(Slowly occurred while Before Starting WEB detected with
blinking) power on. Connection (TRBL 03-0000), WEB.
Example: and then detect a failure with
User data was WEB.
lost.
6 { { A failure occurred Check LED indication of Parts failure.
during self-test at Control Unit. (Refer to Table (RKM/RKS)
time when power is 8.2.7 LED Indication Patterns
turned on. on Control Unit (Fibre
Channel) (TRBL 08-0230).)
7 { { { { A failure which Check LED indication of each Parts error.
does not stop RKM/RKS part. (Refer to 8.2 (RKM/RKS)
operation occurred Trouble Analysis by LED
in RKM/RKS. Indication of Each Part
(TRBL 08-0150)).
{ { A failure which Check LED indication of each Parts error.
does not stop RKAJ/RKAJAT part. (Refer to (RKAJ/RKAJAT)
operation occurred 8.2 Trouble Analysis by LED
in RKAJ/RKAJAT. Indication of Each Part
(*2) (TRBL 08-0150).)
8 (*1) { { A failure which Proceed to Chapter 3. Failure must be
(Slowly does not stop Before Starting WEB detected with
blinking) operation occurred Connection (TRBL 03-0000), WEB.
in unit (It must be and then detect a failure with
detected with WEB.
WEB).
9 { (*1) { A failure which Proceed to Chapter 3. Failure must be
(Slowly does not stop Before Starting WEB detected with
blinking) operation occurred Connection (TRBL 03-0000), WEB.
in unit. and then detect a failure with
WEB.
*1 : Slowly blinking
Blinking (Once times/1 s)
(1 s)
*2 : Under the following conditions, RKAJs/RKAJATs WARNING LED could not light up. However, the each parts
ALARM LED or ALM LED lights up. (Excluding the condition (2) below.)
(1) When the ALM LED of the ENC Unit/SENC Unit came on before the subsystem became ready during startup of
the subsystem.
(2) When the ALM LED of the ENC Unit/SENC Unit came on and the ENC Unit/SENC Unit was pulled out.
(3) When the failed ENC Unit/SENC Unit was replaced and the ALM LED of the ENC Unit/SENC Unit came on after
that (However, the ALM LED is on immediately after the ENC Unit/SENC Unit is inserted. If the ALM LED does
not go out after one minute elapses, the replaced ENC Unit/SENC Unit should be judged out of order.)

TRBL 08-0020-01

LEDs
RKM/RKS RKAJ/RKAJAT
10 (*1) Latest revision Wait until fast blinking stops. No error.
(Fast maintenance
blinking) function of flash
program is
executed.
11 (*2) { The ENC/SENC Restart a device.
(Slowly firmware download
blinking) or Drive firmware
download process
is completed.
12 { (*2) { The ENC/SENC Proceed to Chapter 3. Failure must be
(Slowly firmware download Before Starting WEB detected with
blinking) or Drive firmware Connection (TRBL 03-0000), WEB.
download process and then detect a failure with
is terminated WEB.
abnormally.
13 (*1) { The ENC/SENC Wait as it is until there is no
(Fast firmware is being high-speed blinking (up to
blinking) automatic 30/50 minutes).
downloaded.
*1 : Fast blinking
Blinking (Eight times/1 s)
(1 s)
Blinking (Four times/500 ms) Off (500 ms)
(1 s)
*2 : Slowly blinking
Blinking (Once times/1 s)
(1 s)

TRBL 08-0030-01
(3) Trouble analysis by the indication of the POWER LED

Analyze the cause of the POWER LED failure following the flowchart.
(a) Trouble analysis on the indication on the POWER LED of RKM/RKS. (When the POWER LED is
not on)
Check the following items.

1. The power cable is connected correctly.
2. The output voltage is at the power outlet.
3. The Power Unit is inserted.
Yes Has a failure occurred in Yes

Is the UPS connected?
the UPS?
No No
Does UPS output voltage? No
Yes
Turn on the AC Power Unit

Solve the trouble of the UPS.
Switch.(2)
Turn on the main switch.(2)
Is the READY LED of No

the Power Unit on?
Yes Is there input voltage No
Is the CHK LED on the Control Yes on the unit?
Unit blinking nine times? Yes
No Replace the failed part
Check that both of two Fan Replace the power cable
c Power Unit
Assemblies are inserted correctly. For the replacement
procedure, refer to the
Replace the failed part Replacement 2.2.4
c Power Unit For the replacement Replacing Power Unit (REP
procedure, refer to the 02-0340)
Replacement 2.2.3
Replacing Fan Assembly Yes
Recovered?
Is the CALM LED of Yes(1) No
the Control Unit on? END
No(1)
Replace the failed part.
c Control Unit
For the replacement procedure, B To TRBL 08-0060
refer to the Replacement 2.2.5
Replacing Control Unit (REP
02-0390).
Is the POWER LED on the Yes

Front Bezel on?
No
Normal
A To TRBL 08-0050
1 : The CALM LED of the Control Unit is on until the subsystem becomes ready, however, this does not mean that the Control
Unit is faulty. If the CALM LED does not go out after the subsystem has become ready, replace the Control Unit.
2 : This operation is not needed when the AC Power Unit Switch and the main switch have already been turned on.

TRBL 08-0040-01
From TRBL 08-0040 A
Is the control mode of the Remote

power supply remote or local?
Local
Replace the failed part Is the control mode set to

c Control Unit Remote correctly in accordance No
with the type of the host Reset the mode correctly
For the replacement
interface?
Yes
Replacement 2.2.5 Replacing Connect the Remote adapter
Control Unit (REP 02-0390). Are the Remote adapter No cables correctly and make the
d Power Unit cables connected?
check once again.
For the replacement Yes
Is the host computer powered No Power on the host computer and
Replacement 2.2.4 Replacing
on? make the check once again.
Power Unit (REP 02-0340)
Yes
Replace the failed part
c Replace the Remote adapter
whose POWER LED is not on.
Are the POWER LEDs of all the OFF For the replacement
connected Remote Adapters on? (Not all ON) procedure, refer to
Replacement 2.2.13
All ON
Replacing Remote Adapter
(REP 02-1030).
Replace the failed part

c Replace the Remote adapter
any of whose LEDs for the
connected ones among the
Are the LEDs for the connected connectors J100 to J105 are
ones among the connectors J100 OFF not on.
to J105 on all the connected (Not all ON) For the replacement
Remote adapters on? procedure, refer to the
All ON Replacement 2.2.13
Replacing Remote Adapter
Replace the failed part (REP 02-1030).
c Control Unit
For the replacement
Control Unit (REP 02-0390).

TRBL 08-0050-01
From TRBL 08-0040 B
Turn off the all AC Power Unit

Switch (two spots) on all the
chassis.
Remove the Fan Assembly #0(1).
Turn on the all AC Power Unit

chassis.
Did the failure occur again? No
Yes
Turn off the main switch. Replace the failed part
c Fan Assembly #0 (RKM/RKS)
Turn off the all AC Power Unit For the replacement
Switch (two spots) on all the procedure, refer to the
chassis. Replacement 2.2.3
Replacing Fan Assembly
(REP 02-0300)
Install the removed Fan
Assembly #0 in the original
position.
Remove the Fan Assembly #1(1).

chassis.
No
Did the failure occur again?
Yes
Install the removed Fan Replace the failed part
Assembly #1 in the original c Fan Assembly #1 (RKM/RKS)
position. For the replacement
Replacement 2.2.3
Replacing Fan Assembly
C To TRBL 08-0070 (REP 02-0300)
1 : If leaving it as this part removed for 10 or more minutes, the thermal alarm is detected and the subsystem stops.
Check the condition within 10 minutes and turn off the power supply.

TRBL 08-0060-01
From TRBL 08-0060 C

chassis.
Remove the Disk Drive #7 to #13(1). Be sure to check the original

mount position.
chassis.
No
Yes
Turn off the main switch. Turn off the main switch.
Turn off the all AC Power Unit Turn off the all AC Power Unit
Switch (two spots) on all the Switch (two spots) on all the
chassis. chassis.
Mount the removed Disk Drive #7 Mount one of the removed Disk
to #14 on the original position. Drive on the original position.
Remove the Disk Drive #0 to Turn on the all AC Power Unit

#6(1). Switch (two spots) on all the
Be sure to check the original chassis.
mount position.
No
chassis. Did the failure occur again?
Yes
Replace the inserted Disk Drive
No Replacing Disk Drive (REP 02-
0050).)
Yes
D To TRBL 08-0080
1 : If leaving it as this part removed for 10 or more minutes, the thermal alarm is detected and the subsystem stops.

TRBL 08-0070-01
From TRBL 08-0070 D

chassis.
Loosen the fixing screws (left and

right) of the Control Unit #0, open
both left and right levers at the
same time, and pull out the
Control Unit #0 slightly (1).

chassis.
Yes
c Contrl Unit #0 (RKM/RKS)
Turn off the all AC Power Unit For the replacement
Switch (two spots) on all the procedure, refer to the
chassis. Replacement 2.2.5
02-0390)
Return the Control Unit #0 to the
original position and fasten the
fixing screws (left and right).
Loosen the fixing screws (left and

right) of the Control Unit #1, open
both left and right levers at the
same time, and pull out the
Control Unit #1 slightly (1).

chassis.
E
1 : If leaving it as this partTo TRBL 08-0090
removed for 10 or more minutes, the thermal alarm is detected and the subsystem stops.

TRBL 08-0080-01
From TRBL 08-0080 E
Yes
Return the Control Unit #1 to the Replace the failed part
original position and fasten the c Contrl Unit #1 (RKM/RKS)
fixing screws (left and right). For the replacement
Replace the failed part Replacement 2.2.5
c Basic Chassis (RKM/RKS) Replacing Control Unit (REP
For the replacement 02-0390)
Replacement 2.2.11
Replacing Basic Chassis of
Rack Mount Style (REP 02-
0950)

TRBL 08-0090-01
(b) Trouble analysis on the indication on the POWER LED of RKAJ/RKAJAT. (Not POWER LED on)
Check the following items.

1. The power cable is connected correctly.
2. The output voltage is at the power outlet.
3. The Power Unit (RKAJ/RKAJAT) is inserted.
4. The ENC Unit (RKAJ)/SENC Unit (RKAJAT) is inserted.
Yes Has a failure occurred in Yes

Is the UPS connected? the UPS?
No No
Does UPS output voltage? No
Yes
Is the READY LED on the No

Power Unit of RKAJ/RKAJAT on? Solve the trouble of the UPS.
Yes
Is the ALM LED of Is there input voltage No
Yes on the unit?
the ENC Unit (RKAJ) or
Yes
SENC Unit (RKAJAT) on? ( 1)
No Replace the failed part.
Replace the power cable
c ENC Unit (RKAJ)/SENC Unit
(RKAJAT)
For the replacement
No Recovered?
Yes
ENC Unit/SENC Unit (REP
02-0830). END
Is the POWER LED on the Yes Is the AC input Power Unit No

Front Bezel on? Switch of RKAJ/RKAJAT on?(2)
No Yes
Turn on the AC input Power
Replace the failed part. Normal Unit Switch of RKAJ/RKAJAT.
c Power Unit
For the replacement
No Recovered
Replacement 2.2.4
Replace the failed part Yes
Replacing Power Unit (REP
02-0340) c Power Unit END
d ENC Unit (RKAJ)/ SENC Unit For the replacement
(RKAJAT) procedure, refer to the
For the replacement procedure, Replacement 2.2.4
refer to the Replacement 2.2.9 Replacing Power Unit (REP
Replacing ENC Unit/SENC 02-0340)
Unit (REP 02-0830).
Recovered? Yes
No
END
A To TRBL 08-0110
1 : The ALM LED of the ENC Unit/SENC Unit is on until the subsystem becomes ready, however, this does not mean that
the ENC Unit/SENC Unit is faulty. If the ALM LED of the subsystem which has become ready does not go out,
replace the ENC Unit/ SENC Unit.
2 : When two or more sets of Disk Drive are not mounted, please give an AC Power Unit Switch as off.

TRBL 08-0100-01
From TRBL 08-0100 A

chassis.
Remove the Disk Drive #10 to Be sure to check the original

#14. (1) (2) mount position.

Switch on all the chassis.
No
Yes
Turn off the main switch. Turn off the main switch.
Turn off the all AC Power Unit Turn off the all AC Power Unit
Switch (two spots) on all the Switch (two spots) on all the
chassis. chassis.
Mount the removed Disk Drive Mount one of the removed Disk
#10 to #14 on the original Drive on the original position.
position.
Remove the Disk Drive #4 to #9 Switch (two spots) on all the
(1) (2). chassis.
Be sure to check the original
mount position. Turn on the main switch.

Switch (two spots) on all the No
chassis.
Yes
Replace the inserted Disk Drive
Replacing Disk Drive (REP 02-
No 0050).)
Yes
Mount the removed Disk Drive #4
to #9 on the original position.
B To TRBL 08-0120
*1 : RKAJ/RKAJAT of Disk Drive nearest to RKM/RKS.
*2 : If leaving it as this part removed for 10 or more minutes, the thermal alarm is detected and the subsystem stops.

TRBL 08-0110-01
From TRBL 08-0110 B
Turn off the AC Power Unit Switch

(two spots) on all the chassis.
Remove the ENC Unit #0/SENC

Unit #0. (1) (2)
Turn on the AC Power Unit Switch

Yes
c ENC Unit #0 (RKAJ)/SENC
Turn off the AC Power Unit Unit #0 (RKAJAT)
Switch (two spots) on all the For the replacement
chassis. procedure, refer to the
Replacement 2.2.5
Install the removed ENC Unit #0/
02-0390)
SENC Unit #0 in the original
position.
Remove the ENC Unit #1/SENC

Unit #1. (1) (2)
Turn on the AC Power Unit Switch

Yes
Install the removed ENC Unit #1/ Replace the failed part
SENC Unit #1 in the original c ENC Unit #1 (RKAJ)/SENC
position. Unit #1 (RKAJAT)
For the replacement
Replace the failed part procedure, refer to the
c Additional Chassis Replacement 2.2.5
(RKAJ/RKAJAT) Replacing Control Unit (REP
For the replacement 02-0390)
Replacement 2.2.12
Replacing Additional Chassis
of Rack Mount Style (REP
02-0990)
*1 : RKAJ/RKAJAT of ENC Unit/SENC Unit nearest to RKM/RKS.
*2 : If leaving it as this part removed for 10 or more minutes, the thermal alarm is detected and the subsystem stops.

TRBL 08-0120-01
(4) Trouble analysis based on the indication of READY LED (When in the Fibre Channel interface)
Analyze the cause of the READY LED failure following the flowchart.

B From TRBL 08-0140
Switch (*1) (*2).
When in the remote mode, the host computer

must be turned on.
Trouble analysis based on the indication of the

POWER LED
y 8.1 (3) (a) Trouble analysis on the indication
Is the POWER LED No on the POWER LED of RKM/RKS. (When the
on the Front Bezel on? POWER LED is not on) (TRBL 08-0040)
Yes y 8.1 (3) (b) Trouble analysis on the indication
on the POWER LED of RKAJ/RKAJAT. (Not
POWER LED on) (TRBL 08-0100)
Is the READY LED

on the Front Bezel on? Yes Normal
No
Trouble analysis by WEB
Is the ALARM LED Yes
Refer to Chapter 4. Trouble Analysis by WEB
on the Front Bezel on?
Connection (TRBL 04-0000).
No
Replace the Controller whose a failure has been
occurred.
Are the GP0 and GP1 LEDs Abnormal c Replace the Control Unit.
on the Control Unit normal?(*3) (No) For the replacement procedure, refer to the
Normal (Yes) Replacement 2.2.5 Replacing Control Unit
(REP 02-0390).
After turning off the main switch,

make sure that the POWER LED
on the Front Bezel goes out.

Switch.
Remove the Fibre Channel cable

and attach the loop back
connectors to the connectors
(Tx and Rx) on the Control Unit.

Switch(*2).
Turn on the main switch(*4).
A To TRBL 08-0140
*1 : This operation is not needed when the AC Power Unit Switch and the main switch have already been turned on.
*2 : If two or more Disk Drive are not mounted on RKAJ in the Floor models (RKM/RKS+RKAJ +H2J), turn off the AC input
*3 : Refer to Table 8.2.7 LED Indication Patterns on Control Unit (Fibre Channel) (TRBL 08-0230) in 8.2 (5-3) LED
Indication Patterns on Control Unit (Fibre Channel) (RKS) (TRBL 08-0230).
*4 : When the mode is Remote, change it to Local.

TRBL 08-0130-01
From TRBL 08-0130 A
Check the status of the

Off READY LED. On
The subsystem failed. The subsystem is normal.
Trouble analysis based on the Replace the Fibre Channel cable.

WEB connection. (It is possible that the host
(Refer to Chapter 4. Trouble computer or other device, which
Analysis by WEB Connection uses the same Fibre Channel
(TRBL 04-0000).) interface, is faulty.)
Turn off the main switch and

make sure that the POWER LED
on the Front Bezel goes out.
Turn off the AC Power Unit

Switch.(*1)
B To TRBL 08-0130
*1 : Return the Remote/Local setting as it was. It may take three minutes at the longest until the READY LED comes
on after the main switch is turned on. For the setting of the Remote/Local mode, refer to the Installation 1.8
Setting the Power Control Mode (Local/Remote Mode) (INST 01-0320).

TRBL 08-0140-01
8.2 Trouble Analysis by LED Indication of Each Part

Check whether a failure has occurred in each part or not.
(1) Trouble analysis based on LED indication of Backup Battery Unit
ALARM LED CHARGE LED READY LED

(Red) (Orange) (Green)
Backup Battery Unit #0 Backup Battery Unit #1 Backup Battery Unit #0

RKM RKS
Table 8.2.1 LED Indication Patterns on Backup Battery Unit

LEDs
No. ALARM CHARGE READY Cause or status Action(s) to be taken Reference page
(Red) (Orange) (Green)
1 { Normal. Recovery operation is unnecessary
(*1,
*2)
2 { { Under periodical charge.

(*1,
*2)
3 { Under initial charge. (up to six hours)

(*1)
4 The microcomputer termination is in

(*1) progress in the Backup Battery Unit
(within 10 seconds).
5 {(*3) 1. Battery voltage is abnormal. Replace the Backup Battery Unit. Replacement 2.2.2
2. Battery temperature abnormal. Replacing Backup
3. The Backup Battery Unit is in the state Battery Unit (REP
of the over discharge. 02-0240)
*1 : This is not a failure status.
*2 : RKM/RKS: Backup time is 24 hours in the state of 1 or 2.
*3 : If the ALARM LED on the Backup Battery Unit (ASSY) lights on, be sure to replace the Backup Battery Unit (it
cannot be recharged).

TRBL 08-0150-01
(2) Trouble analysis based on LED indication of Disk Drive
ALARM LED (Red) WARN LED (Orange) PWR LED

GREEN (ACTIVE) LED (RKM/RKS) (RKM/RKS) (Green)
0 14
RED (ALARM) LED RKM/RKS: RDY LED (Green) RKAJ/RKAA

RKAJ/RKAJAT: WARN LED (Orange)
Disk Drive indication
RKM/RKS RKAJ/RKAJAT
Table 8.2.2 LED Indication Patterns on Disk Drive

LEDs
No. Green Red Cause or status Action(s) to be taken Reference page
(ACTIVE) (ALARM)
1 The Disk Drive is being accessed/spun up. This is not a problem.
(*1)
2 { Completed spin up. This is not a problem.

(*1)
3 Seeking. This is not a problem.

(*1)
4 { A failure that makes the Disk Drive of lighting LED 1. When the WARN LED of RKM/RKS is
unable to operate occurred in it. blinking, refer to the LOG Message by
WEB connection, and check the
backup status to the Spare Disk.(*2).
2. Replace the Disk Drive. Replacement 2.2.1
Replacing Disk Drive
(REP 02-0050)
*2 : The WARN LED of RKM/RKS blinks when a data recovery on a Spare Disk fails, a data recovery on a replaced Disk
Drive fails, or a writing of recovery data is not completed. The blinking of WARN LED stops after referring to the
LOG Message by WEB.

TRBL 08-0160-01
(3) Trouble analysis based on LED indication of Power Unit

(a) Power Unit
NOTE : When the READY LED is off, it shows that a failure has occurred even if the fan
rotating.
READY LED ALARM LED

ALARM LED READY LED (Green) (Red)
(Red) (Green)
Power Unit #0 Power Unit #1

RKM RKAJ

RKS RKAJAT
Table 8.2.3 LED Indication Patterns on Power Unit

LEDs
No. READY ALARM Cause or status Action(s) to be taken Reference page
(Green) (Red)
1 { This shows the normal operation of the Power This is not a problem.
(*1) Unit.
2 In resting. Make sure that the AC Power Unit Switch is Replacement 2.2.4
turned on. Replacing Power
1. If the READY LED is kept off when the AC Unit (REP 02-0340)
Power Unit Switch is turned on, replace
the Power Unit.
3 { In trouble. Replace the Power Unit. Replacement 2.2.4
Replacing Power
4 { { Unit (REP 02-0340)

TRBL 08-0170-01
(4) Trouble analysis based on LED indication of Fan Assembly
ALM LED
(Red)
ALM LED
(Red)
Fan Assembly #0 Fan Assembly #1
RKM
Fan Assembly #0 Fan Assembly #1
RKS
NOTE : While the ALM LED of a Fan Assembly is on, when a Control Unit has been
blocked (the CALM LED or EALM LED is on), be sure to correct the Control Unit
blockade failure first.
Table 8.2.4 LED Indication Patterns on Fan Assembly

LED
No. ALM Cause or status Action(s) to be taken Reference age
(Red)
1 This shows that the Fan Assemblies are This is not a problem.
(*1) normal.
2 { This shows that there is a trouble in the Fan Replace the Fan Assembly. Replacement 2.2.3
Assemblies. Replacing Fan
Assembly (REP 02-
0300)

TRBL 08-0180-01
(5) Trouble analysis based on LED indication of Control Unit

(5-1) LED Indication Pattern-1 on Control Unit (RKM/RKS)
NOTE : If all the LEDs on the Control Unit are turned off, connect to WEB (Refer to
Chapter 3. Before Starting WEB Connection (TRBL 03-0000)) and check if the
control unit is blocked. If the Control Unit is blocked, replace the blocked
Control Unit (Refer to the Replacement 2.2.5 Replacing Control Unit (REP 02-
0390).)
ACT LED CACHE POWER LED CHKSTP LED ACT LED CACHE POWER LED CHKSTP LED
(Green) (Green) (Red) (Green) (Green) (Red)

CLASS 1 CLASS 1
LINK LED RST LED CALM LED LINK LED RST LED CALM LED
(Green) (Orange) (Red) (Green) (Orange) (Red)
Control Unit#1
Control Unit#0
Table 8.2.5 LED Indication Pattern-1 on Control Unit (RKM/RKS)

LEDs
CACHE CHK
No. CALM RST LINK ACT Cause or status Action(s) to be taken Reference page
POWER STP
(Green) (Red)
1 { It is shown that the Cache Cancel the cache backing Replacement 1.1.2
(*1) memory is being backed up. Checking cache
up because a sequential (Refer to the procedure for memory in the back-
shutdown was not canceling the backing up of up state (REP 01-
executed normally. the Cache memory on 0030)
page.)
2 This shows that the This is not a problem.
(*1) Cache memory is not
being backed up.
3 { The LED comes on when This is not a problem.
(*1) the controller is being
reset in the following
cases.
y During power-on reset
y During reset for WEB
maintenance mode
y During reboot process

TRBL 08-0190-01

LEDs
CACHE CHK
No. CALM RST LINK ACT Cause or status Action(s) to be taken Reference page
POWER STP
(Green) (Red)
4 { This shows that the This is not a problem.
(*1) linkage of LAN is normal.
5 { This shows that data is This is not a problem.
(*1) being transferred via
LAN.
6 { While an active LAN Check the LAN cable. Replacement 2.2.5
cable is connected, LINK If it is normal, replace the Replacing Control
LED does not on. Control Unit. Unit (REP 02-0390)
7 { A failure that makes the Connect PC to WEB and
Control Unit unable to check the message, then
operate occurred in it. follow the instruction.
(Refer to the Message
Chapter 1. Before Starting
Trouble Analysis (MSG
01-0000).)
1. Replace the Control Unit. Replacement 2.2.5
Replacing Control
Unit (REP 02-0390)
If the operation is not
recovered, replace the
following items in order.
2. Replace the Cache Unit. Replacement 2.2.6
Replacing Cache
Unit (REP 02-0540)
8 { A failure that makes the Replace the Control Unit. Replacement 2.2.5
Control Unit unable to Replacing Control
operate occurred in it. Unit (REP 02-0390)

TRBL 08-0200-01
(5-2) LED Indication Pattern-2 on Control Unit (RKM/RKS)
P1 LED CHK LED P1 LED CHK LED

(Green) (Red) (Green) (Red)

CLASS 1 CLASS 1
P0 LED EALM LED P0 LED EALM LED

(Green) (Red) (Green) (Red)
Control Unit#1
Control Unit#0
Table 8.2.6 LED Indication Pattern-2 on Control Unit

LEDs
No. CHK EALM P1 P0 Cause or status Action(s) to be taken Reference page
(Red) (Red) (Green) (Green)
1 (*1) This shows a trouble in the Power Unit. Replace the Power Unit on which Replacement 2.2.4
(Once) Drive +5 V voltage is abnormal. the same READY as that of Replacing Power
2 (*1) This shows a trouble in the Power Unit. Control Unit is turned off. Unit (REP 02-0340)
(Twice) Drive +12 V voltage is abnormal.
3 (*1) Battery is abnormal Confirm the LED indication on the Table 8.2.1 LED
(Five) Backup Battery Unit. Indication Patterns
on Backup Battery
Unit (TRBL 08-0150)
4 (*1) Voltage on the controller is abnormal. Replace the Control Unit Replacement 2.2.5
(Six) (Resetting of the Control Unit cannot be Replacing Control
cancelled.) Unit (REP 02-0390)
5 (*1) This shows a trouble in the Power Unit. Replace the Power Unit. Replacement 2.2.4
(Seven) BS12V voltage is abnormal. Replacing Power
Unit (REP 02-0340)
*1 : Indication of status with LED.
On Off
(500 ms) (500 ms)
Blinks n times. 3s
On Off
(400 ms) (200 ms)
Blinks n times. 1s

TRBL 08-0210-01

LEDs
No. CHK EALM P1 P0 Cause or status Action(s) to be taken Reference page
(Red) (Red) (Green) (Green)
6 (*2) Rotation failure in two or more fans of Replace the Fan Assembly. Replacement 2.2.3
(Nine) both Fan Assemblies. (RKM/RKS) Replacing Fan
Assembly (REP 02-
0300)
7 { ENC Unit CUDG error is occurred. Replace the Control Unit Replacement 2.2.5
BOOT section of ENC microprogram. Replacing Control
RAM error Unit (REP 02-0390)
ENC Unit configuration error
8 (*3) ENC Unit CUDG error is occurred.
(Once) SRAM error
(Twice) ENC Unit error
(Three) Microprogram error in flash memory.
11 { A failure that makes the ENC Unit
unable to operate occurred in it.
12 { (*2) An exceptional process error detected
by the ENC microprogram.
13 { (*4) An exceptional process error detected
by the ENC microprogram. (Stack over)
14 (*2) Indicates that FLASH write is performed Recovery operation is
(*1) during the ENC microprogram unnecessary.
download.
15 The input on loop PATH-0 side is Replace the Control Unit Replacement 2.2.5
abnormal. Replacing Control
16 The input on loop PATH-1 side is Unit (REP 02-0390)
abnormal.
On Off
(500 ms) (500 ms)

On Off
(400 ms) (200 ms)
Blinks n times. 1s
On Off
(100 ms) (100 ms)

TRBL 08-0220-01
(5-3) LED Indication Patterns on Control Unit (Fibre Channel) (RKS)
ALARM (Red) ALARM (Red)

GP1 (Green) GP1 (Green)
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Control Unit (RKS)
Control Unit #1
Control Unit #0
RKS (Rear view)
Table 8.2.7 LED Indication Patterns on Control Unit (Fibre Channel)

LEDs
No. ALARM GP1 GP0 Cause or status Action(s) to be taken Reference page
(Red) (Green) (Green)
1 { { Link-up state. This is not a problem.
(*1)
2 y Interface is in initial state. This is not a problem.

(*1) y Interface is in reset state. However, it is abnormal if this status continues.
y Loop port is bypassed.
3 { Loop (Link) is being initialized. This is not a problem.
(*1) However, it is abnormal if this status continues.

TRBL 08-0230-01

LEDs
4 { Link failed. 1. There is no problem even if it is in this status
when Fibre Channel Cable is not connected.
2. Check the connections of the following Fibre
Channel interfaces.
y Fibre Channel Cable
y Fibre Channel Switch
y Host Adapter
y GBIC (When Host Adapter or Fibre
Channel switch is connected)
3. When the host node is connected to port A-1 System Parameter
of RKS, check if the port setting of RKS 4.2 (8) Setting of
(transfer rate) is 1Gbps or 2Gbps. Fibre Channel
4. Check if the consistency of the port setting (SYSPR 04-0170)
(transfer rate) and the host node setting
(transfer rate) of RKS is taken.
5. Check if the port setting (Topology) and the
host node setting (Topology) of RKS are the
same.
6. Check if it links up by replacing the equipment
listed below sequentially.
y Host Connector
y Control Unit
7. When there is a possibility of a failure on the
host node side, replace the equipment listed
below sequentially and check if it links up.
y Host Adapter

TRBL 08-0240-01

LEDs
5 { Link failure often occurs. 1. Check the connections of the following Fibre
Channel interfaces.
y Host Adapter
2. When the host node is connected to port A-1 System Parameter
of RKS, check if the port setting of RKS 4.2 (8) Setting of
6 { Loop (Link) is often initialized. (transfer rate) is 1Gbps or 2Gbps. Fibre Channel
3. Check if the consistency of the port setting (SYSPR 04-0170)
(transfer rate) and the host node setting
(transfer rate) of RKS is taken.
4. Check if the port setting (Topology) and the
host node setting (Topology) of RKS are the
same.
7 y Link failure often occurs. y Host Connector
y Loop (Link) is often initialized. y Control Unit
y Host Adapter
8 { The host connector is defective. Replace the host connector of which the LED Replacement 2.2.8
lights on. Replacing Host
Connector (REP 02-
0770)

TRBL 08-0250-01
(6) LED Indication Patterns on Interface Board (RKM)
ALARM (Red) ALARM (Red)

Interface Board (RKM)

Interface Board
Interface Board
RKM (Rear view)
Table 8.2.8 LED Indication Patterns on Control Unit (Fibre Channel)

LEDs
1 { { Link-up state. This is not a problem.
(*1)
2 y Interface is in initial state. This is not a problem.

(*1) y Interface is in reset state. However, it is abnormal if this status continues.
y Loop port is bypassed.
3 { Loop (Link) is being initialized. This is not a problem.
(*1) However, it is abnormal if this status continues.

TRBL 08-0260-01

LEDs
4 { Link failed. 1. There is no problem even if it is in this status
when Fibre Channel Cable is not connected.
2. Check the connections of the following Fibre
Channel interfaces.
y Host Adapter
3. Check if the consistency of the port setting System Parameter
(transfer rate) and the host node setting 4.2 (8) Setting of
(transfer rate) of RKM is taken. Fibre Channel
4. Check if the port setting (Topology) and the (SYSPR 04-0170)
host node setting (Topology) of RKM are the
same.
y Host Connector
y Interface Board
y Host Adapter

TRBL 08-0270-01

LEDs
5 { Link failure often occurs. 1. Check the connections of the following Fibre
Channel interfaces.
y Host Adapter
6 { Loop (Link) is often initialized. Channel switch is connected)
2. Check if the consistency of the port setting System Parameter
(transfer rate) and the host node setting 4.2 (8) Setting of
(transfer rate) of RKM is taken. Fibre Channel
3. Check if the port setting (Topology) and the (SYSPR 04-0170)
host node setting (Topology) of RKM are the
7 Link failure often occurs. same.
Loop (Link) is often initialized. 4. Check if it links up by replacing the equipment
y Host Connector
y Interface Board
y Host Adapter
8 { The host connector is defective. Replace the host connector of which the LED Replacement 2.2.8
lights on. Replacing Host
Connector (REP 02-
0770)

TRBL 08-0280-01
(7) Trouble analysis based on LED indication of ENC Unit/SENC Unit

(a) ENC Unit
CHK LED (Green)

P0 LED (Green) ALM LED (Red)
ENC Unit #0 ENC Unit #1
RKAJ (Rear view)
Table 8.2.9 LED Indication Patterns on ENC Unit

LEDs
No. ALM CHK P0 Cause or status Action(s) to be taken Reference page
(Red) (Red) (Green)
1 { Normal. Recovery operation is unnecessary.
(*1)
2 (*2) This shows a trouble in the Power Unit. Replace the Power Unit on which the Replacement 2.2.4
(Once Logic +5 V voltage error. same READY LED as that of ENC Replacing Power
times) Unit is turned off. Unit (REP 02-0340)
3 (*2) This shows a trouble in the Power Unit.
(Twice Logic +12 V voltage error.
times)
4 (*2) This shows a trouble in the Power Unit. Replace the ENC Unit. Replacement 2.2.9
(Six The voltage on the ENC Unit is Replacing ENC
times) abnormal. (Logic +2.5 V) Unit/SENC Unit
(REP 02-0830)
On Off
(500 ms) (500 ms)
Blinks n times. 3s

TRBL 08-0290-01

LEDs
(Red) (Red) (Green)
5 { ENC unit CUDG error is occurred. Replace the ENC Unit. Replacement 2.2.9
y BOOT section of ENC microprogram. Replacing ENC
y RAM error Unit/SENC Unit
y ENC Unit configuration error. (REP 02-0830)
6 (*2) ENC unit CUDG error is occurred.
(Once y SRAM error
time)
(Twice y ENC Unit error
time)
(Three y Microprogram error in flash memory.
time)
9 { A failure that makes the ENC Unit unable
to operate occurred in it.
10 (*3) { An exceptional process error detected by
the ENC microprogram.
11 (*4) { An exceptional process error detected by
the ENC microprogram. (Stack over)
12 (*3) Indicates that FLASH write is performed Recovery operation is unnecessary.
(*1) during the ENC microprogram download.
13 The input on loop PATH-0 side is Replace the Control Unit whose EALM Replacement 2.2.5
abnormal. LED is on. Replacing Control
14 The input on loop PATH-1 side is Unit (REP 02-0390)
abnormal.
On Off
(400 ms) (200 ms)
Blinks n times. 1s
On Off
(500 ms) (500 ms)

On Off
(100 ms) (100 ms)

TRBL 08-0300-01
(b) SENC Unit
CHK LED (Green)

P0 LED (Green) ALM LED (Red)
RKAJAT (Rear view)
Table 8.2.10 LED Indication Patterns on SENC Unit

LEDs
(Red) (Red) (Green)
1 { Normal. Recovery operation is unnecessary.
(*1)
2 (*2) SENC Unit CUDG error is occurred. Replace the SENC Unit. Replacement 2.2.9
(Twice Replacing ENC
times) Unit/SENC Unit
3 (*2) Fan selector circuit error in SENC Unit. (REP 02-0830)
(Eight
times)
4 {(*3) CUDG error in BOOT section of SENC.
5 (*4) Fixed data error in flash memory.

(Five
times)
6 (*4) Significant surface error in flash memory.
(Six
times)
On Off
(500 ms) (500 ms)
Blinks n times. 3s
*3 : The CHK LED (Red) lights on for about 10 seconds (while the CUDG is being executed) after the power was turned
on, but it is not an error.
On Off
(400 ms) (200 ms)
Blinks n times. 1s

TRBL 08-0310-01

LEDs
(Red) (Red) (Green)
7 (*4) SUM check error in flash memory. Replace the SENC Unit. Replacement 2.2.9
(Seven Replacing ENC
times) Unit/SENC Unit
8 { A failure that makes the SENC Unit unable (REP 02-0830)
to operate occurred in it.
9 The input on loop PATH-0/1/2/3 side is Replace the Control Unit whose EALM Replacement 2.2.5
abnormal. LED is on. Replacing Control
Unit (REP 02-0390)
On Off
(400 ms) (200 ms)
Blinks n times. 1s

TRBL 08-0320-01
(8) Trouble analysis based on LED indication of Remote Adapter
POWER ON J100 J101
OUT
J1
Remote Adapter (main body)

POWER ON J100 J101 J102
J200 J201 J202
J203 J204 J205 IN OUT
J1
J103 J104 J105

Remote Adapter (HUB)
Table 8.2.11 LED Indication Patterns on Remote Adapter

LEDs
Power J100 Reference
No. Cause or status Action(s) to be taken
ON J105 page
(Green) (Green)
1 The remote adapter is operable and outputs This is not a trouble.
(*1) the Remote On signal.
2 The Remote Adapter is operable in the case This is not a trouble.
where the Remote Adapter cable is not
connected.
The Remote On signal is not output in the Check the cable connection.
case where the Remote Adapter cable is
connected.
3 The POWER ON LED is out of order. Replace the Remote Adapter
4 The remote adapter is not in operation. Check the connection of the power cable. Replacement 2.2.13
If the cable is connected, replace the Replacing Remote
Remote Adapter. Adapter (REP 02-
1030)

TRBL 08-0330-01
Chapter 9. Data Collection when a Failure Occurs in Program

Product (P.P.)
9.1 Locating Failed Part
Identify a part which presents the phenomenon using Table 3.1.1 and execute an appropriate
procedure. Collect a trace from the DF700 in every case.
Table 9.1.1 Program Product To Be Recovered

Object for Related part
No. Program product Type maintenance Basic Host Related manual
(*1) Monitoring
Microprogram computer
1 Storage Navigator Modular P-002D-J301 e { { y Storage Navigator Modular (for
GUI) Users Guide
2 ShadowImage in-system P-002D-J311 c,d { { y ShadowImage in-system
replication replication Users Guide
3 TrueCopy remote P-002D-J312 c,d { { y TrueCopy remote replication
replication Users Guide
4 Copy-on-write SnapShot P-002D-J310 c,d { { y Copy-on-write SnapShot Users
5 Data Retention Utility P-002D-J309 c,d { { y Data Retention Utility Users
6 LUN Manager P-002D-J308 c { y LUN Manager Users Guide
7 Cache Residency P-002D-J305 c { y Cache Residency Manager
Manager Users Guide
8 SNMP Agent Support P-002D-J303 c { y SNMP Agent Support Function
Function Users Guide
9 LUN Expansion P-002D-J304 c { y LUN Expansion Function Users
Guide
10 Password Protection P-002D-J302 c { y Password Protection Users
Guide
11 Performance Monitor P-002D-J306 c { y Performance Monitor Users
Guide
12 Cache Partition Manager P-002D-J307 c { y Cache Partition Manager Users
Guide
*1 : c: DF700 main body (Refer to 9.1.1 When a failure occurs in the DF700 main body (TRBL 09-0020).)
d: Host system server connected to the DF700 (Refer to 9.1.2 When a failure occurs in a host system server
(TRBL 09-0020).)
e: Server for monitoring and setting connected to the DF700 (Refer to 9.1.3 When a failure occurs in a server
for monitoring and setting (TRBL 09-0030).)

TRBL 09-0000-01
In the cases of a difficult failure that has a complicated relation with the system
configuration, also collect information on configurations of the system and the DF700 and
types of program products being used because they may be important.

TRBL 09-0010-01
9.1.1 When a failure occurs in the DF700 main body

Take recovery actions referring to Chapter 1. Flowchart for troubleshooting (TRBL 01-0000)
in the Maintenance Manual for Maintenance.
9.1.2 When a failure occurs in a host system server

(1) In the case of RAID Manager
c If a failure has occurred in the DF700, give priority to investigation of it (see
Troubleshooting).
d Getting an error message
In the case where an error occurs when a command is input, an error cord and an error
message are output in the following line.
A format of a set of an error cord and message is shown below.
[EX-xxxxxx] error message text
Refer to Section 5.2, Command Control Interface (CCI) User and Reference Guide.
Refer to an error message and recovery measures given based on the error code.
e Collecting the SYS log
Check the system log because an error message may be written in it.
Since information on the error code, [HORM-xxx], is related to Command Control
Interface (CCI) User and Reference Guide, refer to Section 5.2, System Log and
Command Error Message and follow instructions given in it.
f For the log peculiar to the product, refer to Appendix B, Log File for Maintenance and
Trace Function in the Command Control Interface (CCI) User and Reference Guide and
collect the information.

TRBL 09-0020-01
9.1.3 When a failure occurs in a server for monitoring and setting

(1) In the case of Storage Navigator Modular
c Taking an action following an error message
Since an error message is displayed when an error occurs in operation of Storage
Navigator Modular, take a recovery action following the message.
d Collecting log files
Collect log files of Storage Navigator Modular
Get all files that are subordinate to the log directory under the program installation
directory of Storage Navigator Modular together with the log directory.
When no log directory exists under the program installation directory of Storage Navigator
Modular, get all files that are subordinate to the log directory under the directory, for
which the environmental variable is specified as STONAVM_HOME, together with the log
directory.
e Getting operation environment
Get a version number, operation environment (OS and model) and operation of Storage
Navigator Modular.

TRBL 09-0030-01
9.2 List of Data to Be Collected when a P.P. Failure Occurs
Table 9.2.1 List of Data of Program Product (to Be Recovered) to Be Collected

Legend: : Collection is needed.
Subsystem Information needed to be collected
No. Program product (P.P.) main body SYS P.P
P.P LOG Getting of operation environment
trace LOG message
1 Storage Navigator { Get all files that are subordinate to the { P.P. version
Modular following log directories together with Operation environment (OS and
the log directories. model)
The storage directory Connection configuration diagram
A log directory under the program Operation details
installation directory of Storage
Navigator Modular. When the
directory described above does not
exist, a log directory under the
directory for which the environmental
variable is specified as
STONAVM_HOME.
2 ShadowImage in- { (See Table 3.2.2)
system replication
(include RAID Manager)
3 TrueCopy remote {
replication
4 Copy-on-write {
SnapShot
5 Data Retention Utility {
6 LUN Manager { { P.P. version
Operation environment (OS and
model)
Connection configuration diagram
Operation details
7 Cache Residency {
Manager
8 SNMP Agent Support {
Function
9 LUN Expansion {
10 Password Protection {
11 Performance Monitor { { P.P. version
Operation environment (OS and
model)
Operation details
12 Cache Partition { { P.P. version
Manager Operation environment (OS and
model)
Operation details

TRBL 09-0040-01
Table 9.2.2 List of ShadowImage in-system replication / TrueCopy remote replication to Be Collected
No. Program product Information to be collected Collection method/Storage
1 ShadowImage in-system Trace (dump) of subsystem Refer to Chapter 7. Collecting Error Information (TRBL 07-0000).
replication (include RAID Manager log Collect all the files under the directory specified with the following environmental
RAID Manager) variables for each operation process/instance.
The environmental variables can be referred to using the set or echo command.
$HORCM_LOG (operation log, error log, trace, core)
$HPRCC_LOG (command log)
$HPRCC_LOGS (start log)
< Examples of reference to the environmental variable >
Unix family: set, echo $HORCM_LOG, etc.
Windows family: "set," "set HORC," etc.
When the environmental variable above is not specified, collect all files under the
following directories will be collected.
/HORCM/log* *: Instance number
/HORCM/log/curlog
For the details, refer to Appendix B, Log File and Trace Function in the
Command Control Interface (CCI) User and Reference Guide.
Configuration definition file UNIX family /etc/horcm*conf *: Instance number
Windows family Windows installation drive, \WINNT\horcm*conf *: Instance
number
System log file (PP failure UNIX family Syslog
message) Windows family Eventing
System configuration diagram Request of a user
Host OS revision Request of a user
2 TrueCopy remote Trace (dump) of two units of Refer to Chapter 7. Collecting Error Information (TRBL 07-0000).
replication subsystem which make-up a
(include RAID Manager) pair
RAID Manager log Collect all the files under the directory specified with the following environmental
variables for each operation process/instance.
Windows family: "set," "set HORC," etc.
/HORCM/log/curlog
number
message)
Windows family Eventing
System configuration diagram Request of a user.
Host OS revision Request of a user.

TRBL 09-0050-01
No. Program product Information to be collected Collection method/Storage

3 Copy-on-write SnapShot Trace (dump) of subsystem Refer to Chapter 7. Collecting Error Information (TRBL 07-0000).
(include RAID Manager) RAID Manager log Collect all the files under the directory specified with the following environmental
Windows family: set, set HORC, etc.
/HORCM/log/curlog
number
4 Data Retention Utility Trace (dump) of subsystem Refer to Chapter 7. Collecting Error Information (TRBL 07-0000).
(include RAID Manager) RAID Manager log Collect all the files under the directory specified with the following environmental
Windows family: set, set HORC, etc.
/HORCM/log/curlog
number

TRBL 09-0060-01

TRBL 09-0070-01
Chapter 10. Trouble Analysis by Failure Monitoring Function

10.1 Trouble Analysis by SNMP Agent Support Function
The SNMP Agent Support Function notifies a network monitoring personal computer or
workstation, in which the SNMP manager program is installed, of failures of the disk array
subsystem via the SNMP (Simple Network Management Protocol). This section explains the
trouble analysis operation to be performed when the SNMP Agent Support Function is used.
10.1.1 Maintenance with TRAP Codes

(1) Ascertaining failure information
An example of an output bay the TRAP issued by the disk array subsystem. (a) is an example
of output by HP OpenView/NetM*COMET. (b) is an example of output by SunNet Manager.
(a) Example of trapped output by HP OpenView/NetM*COMET

If an error occurs, the following screen is popped up.
Trap name
fan Failure event
Apr 20 (Wednes), 2005 4p.m. 21 minutes 15 seconds
OK
fan
Error event in the Event Category box changes to . Double-clicking this box displays
an Error Event browser. For detailed information refer to the browser.
Event Category
Error event
Threshold event
Status event
Setting event
Application warning event
All events
[Read only]

TRBL 10-0000-01
IP address or registered host model name

Generic Trap Code
Specific Trap Code
Error Event Browser

File Action View Help
Significance Date Source Message
Important warning area 2005/04/20 16:21:15 DF700 Trap:generic 6 specific:3 args (0):
1 Event - Dangerous:0 Serious warning:1 Warning:0 Caution:0 Normal:0
(b) Example of trapped output by SunNet Manager

Event/Trap Report-DF700
Save Device name:
Remarks 6 1 6
Wed Apr 20 13:29:06 2005 [DF700] : Trap :
sequence=1
receive- time=Fri Apr 12 13:29:06 2000
version=0
community=public
enterprise=Hitach,Ltd..system. storage. dfraid. dfraid
Lan
source-time=00:00:00.00
trap- type=Fan_Failure
Trap name

TRBL 10-0010-01
(2) Trouble analysis method

Perform maintenance referring to the output examples in (1) and according to Table 10.1.1,
Recovery Method for Each Trap Code.
Table 10.1.1 Recovery Method for Each Trap Code

Generic Specific
No. Trap name Description Recovery methods Remarks
Trap Code Trap Code
1 0 0 coldStart Power-on This is not an error.
Recovery operation is not necessary.
2 4 0 authentication- Invalid SNMP access Change the community name set for the
Failure (The community name subsystem or the community name
set for the subsystem accessed by the SNMP manager so that
differs from the they match.
community name When changing the community name set
accessed by the SNMP for the subsystem, refer to SNMP Agent
manager) Support Function Users Guide.
When changing the community name
accessed by the SNMP manager, refer to
the manual of each manager.
3 6 1 systemDown Controller down It is shown that a failure indicated by a Refer to the Message
message code with H at the top. Message (MSG 00-
For the detailed failure information, refer to 0000).
the display of the WEB log message of the
subsystem.
Perform the maintenance instructed for
message code H#####. ##### is
optional.
4 6 2 driveFailure Disk shutdown Perform the maintenance instructed.
Message code : W060AT, W060xy
Message text : HDU alarm
(Unit-x, HDU-y)
The information corresponding to xy in the
manual is not notified regarding the trap.
Refer to the display of the WEB log
message of the subsystem.
5 6 3 fanFailure Fan failure Perform the maintenance instructed.
Message code : W040xy
Message text : FAN alarm
(Unit-x, FAN-y)
6 6 4 powerSupply- Power supply failure Perform the maintenance instructed.
Failure Message code : W050xy
Message text : PS alarm
(Unit-x, PS-y)

TRBL 10-0020-01
Generic Specific
Trap Code Trap Code
7 6 5 batteryFailure Battery voltage error Perform the maintenance instructed. Refer to the Message
Message code : Message (MSG 00-
W0300x, W0310x, W0320x, W0330x 0000).
Message text :
Battery alarm,
Battery alarm,
Battery SW off,
Battery Thermal alarm
8 6 6 cacheFailure Cache access error Perform the maintenance written.
occurred Message code : W0D0xy
Message text : CACHE alarm
(CTL-x, CACHE-y)
The information corresponding to x, y, and
z, in the manual is not notified regarding
the trap.
9 6 7 upsFailure UPS error Perform the maintenance instructed.
Message code : W0C00x
Message text : UPS alarm (UPS-x)
10 6 9 backupCircuit- Battery circuit failure Perform the maintenance instructed.
Failure Message code : W0340x
Message text : Battery back up circuit
alarm (CTL-x)
The information corresponding to x in the
11 6 10 other-controller- Another side controller Perform the maintenance instructed.
Failure blockade (For dual Message code : W0100x
configuration only) Message text : CTL alarm (CTL-x)
The information corresponding to x in the
When this trap is displayed following the
No.14 microprogram Replacement
executed, it does not mean a failure
because it is reported owing to the
microprogram replacement.

TRBL 10-0030-01
Generic Specific
Trap Code Trap Code
12 6 11 warning A warning was issued in It is shown that a failure indicated by a Refer to the
the disk array message code with W at the top. For Message Message
subsystem. the detailed failure information, refer to the (MSG 00-0000).
display of the WEB log message of the
subsystem.
Perform the maintenance instructed for
message code W#####. ##### is
optional.
13 6 12 spareDrive- Spare Disk blockade Perform the maintenance instructed.
Failure Message code : W061AT, W061HH,
W061xy
Message text : Spare HDU alarm
(Unit-x, HDU-y)
14 6 13 microprogram- A micro program Perform the maintenance instructed.
Replacement- replacement executed Message code : W4600x
executed (For dual configuration Message text : Online Micro-update
only) started (CTL-x)
The message is the one informing that the
microprogram replacement has been
started as shown below, therefore, no
maintenance work is necessary.
15 6 14 encFailure ENC failure Perform the maintenance instructed.
Message code : W090AT, W090xy
Message text : ENC alarm
(Unit-x, ENC-y)
16 6 15 loopFailure Loop failure Perform the maintenance instructed.
Message text : Loop alarm
(Path-x, Loop-y)
17 6 16 PathFailure Path detachment Perform the maintenance instructed.
Message code : W0F0xy
Message text : Path alarm
(Remote-x, Path-y)

TRBL 10-0040-01
10.1.2 Maintenance with MIB (df Regression) Values

(1) Confirming error information
Examples of output caused by a trap issued by the subsystem are shown below. (a) is an
example of output by HP OpenView/NetM*COMET. (b) is an example of output by SunNet
Manager.
For MIB values, refer to Table 10.1.3 dfRegressionStatus Value Corresponding to Each Failure
(TRBL 10-0070).
(a) Example of MIB value output by HP OpenView/NetM*COMET
MIB Browse
Node name or IP address Community name
hsp1FSswh
MIB object ID
terprises.hitachi.systemExMib.storageExMib.dfraidExMib.dfraidLanExMib.dfWarningCondition
dfRegressionStatus Move tree upward
dfPreventiveMaintenanceInformation Move tree downward

dfWarningReserve1
Details
dfWarningReserve2
Inquiry start
Inquiry quit
Graph
MIB interface SNMP set value
Setting (Set)
MIB value
0:1048576
Message
Note : Community public is used for node DF700.
Close Reselect Save... Help
dfRegressionStatus value IP address or registered host model name

TRBL 10-0050-01
(b) Example of MIB value output by SunNet Manager

Event/Trap Report-DF700
Save Device name:
Remarks 19 1 19
Wed Apr 20 16:42:07 2005 [DF700] : Event : Hitachi-DF-RAID-LAN-MIB
dfRegressionStatus=1048576 (Greater Than 0 Priority Low)

dfPreventiveMaintenanceInformationn=0
dfWarningReserve1=0
dfWarningReserve2=0
dfRegressionStatus value
Table 10.1.2 Format of dfRegressionStatus

Bit
7 6 5 4 3 2 1 0
Byte
0 0 0 0 0 0 0 0 Cache
1 0 0 0 Fan BK 0 D.C.PS Battery
2 0 0 NAS UPS NAS Path NAS Sever Path Loop UPS
3 CTL Warning 0 0 ENC D-Drive S-Drive Drive
When a regression is applied to the part concerned, turn on the corresponding bit.
Value of the object corresponding to each failure status is shown in Table 10.1.3
dfRegressionStatus Value Corresponding to Each Failure (TRBL 10-0070).

TRBL 10-0060-01
Table 10.1.3 dfRegressionStatus Value Corresponding to Each Failure

Bit location Object value
No. Description
Byte Bit (in decimal)
1 0 The disk array is normal.
2 3 0 1 Disk Drive (data disk or Spare Disk) detachment.
3 3 1 2 Disk Drive (Spare Disk) detachment.
4 3 2 4 Disk Drive (data Disk) detachment.
5 3 3 8 ENC error.
6 3 6 64 Warning is raised in the disk array.
7 3 7 128 Mate controller blockade.
8 2 0 256 UPS error.
9 2 1 512 Loop error.
10 2 2 1024 Path detachment.
11 2 3 2048 NAS server failure.
12 2 4 4096 NAS path failure.
13 2 5 8192 NAS UPS failure.
14 1 0 65536 Battery error.
15 1 1 131072 Power Unit error.
16 1 3 524288 Battery circuit error.
17 1 4 1048576 Fan error.
18 0 0 16777216 Cache access error.
When two or more failed parts exist, the object value is the sum of each object value.
Example : When failures occur in the battery and the fan, the object value is
1114112 (65536+1048576).
The object value converted into binary form corresponds to the format shown in Table
10.1.2 Format of dfRegressionStatus (TRBL 10-0060).
(2) Troubleshooting procedure

Perform a maintenance by associating the item in the description column in Table 10.1.3
dfRegressionStatus Value Corresponding to Each Failure (TRBL 10-0070) with the contents of
Table 10.1.1 Recovery Method for Each Trap Code (TRBL 10-0020).

TRBL 10-0070-01
10.2 Trouble Analysis by Storage Navigator Modular

The Storage Navigator Modular notifies of failures of the disk array subsystem by the failure
monitoring function.
This section explains the trouble analysis operation to be performed when the Storage
Navigator Modular is used.
10.2.1 Maintenance with the Storage Navigator Modular (GUI version)

(1) Display of subsystem status
A screen which indicates the status of components of Array device under Storage Navigator
Modular is shown below.
An example of the window for referring to the information on installation and capacities of the
Cache Units is shown below.
When a failure occurs in the array subsystem, the part concerned is displayed by the icon of
Red.

TRBL 10-0080-01
(2) Trouble analysis method

Perform maintenance referring to the display examples in (1) and according to Table 10.2.1,
Recovery Method for Each Error Display (Refer to Message Message (MSG 00-0000).).
Table 10.2.1 Recovery Method for Each Error Display (1)

No. Error Display Description Recovery methods
1 Busy or Disk Drive detached for Perform the maintenance instructed.
: Red Restoring/Waiting for Restore Message code : W060HH, W060xy
Inserted Disk Drive did not spin-up Message text : HDU alarm
(RAID group defined) (Unit-x, HDU-y)
2 The Disk Drive is blocked and
: Red + Black uninstalled
3 Busy or Spare Disk detached for Perform the maintenance instructed.
4 Though the disk array subsystem is set to Message text : Spare HDU alarm
: Red + Black use a Spare Disk, but the Spare Disk is (Unit-x, HDU-y)
not installed
: Red Restoring/Waiting for Restore Message code : W060AT
: uninstalled
Red + Black
8 Though the disk array subsystem is set to (Unit-x, HDU-y)
: use a Spare Disk, but the Spare Disk is
Red + Black not installed
9 A cache backup circuit error occurred Perform the maintenance instructed.
Message code : W0340x
: Yellow
Message text : Battery back up circuit alarm
(CTL-x)
10 Controller down Issuance of this trap indicates that an error
: Red beginning with message code H occurred.
For detailed error information, see the WEB
log message display of the subsystem.
Perform the maintenance instructed.
Message code H#####. ##### is optional.
11 Fan error Perform the maintenance instructed.
: Red Message code : W040xy
(Unit-x, FAN-y)
12 Power Unit error Perform the maintenance instructed.
: Red
Message text : PS alarm (Unit-x, PS-y)

TRBL 10-0090-01
No. Error Display Description Recovery methods

13 Battery voltage error Perform the maintenance instructed.
Message code :
: Red
W0300x, W0310x, W0320x, W0330x
Message text :
Battery alarm,
Battery alarm,
Battery SW off,
See the WEB log message display of the
subsystem.
14 Cache access error Perform the maintenance instructed.
Message code : W0D0xy
: Red
(CTL-x, CACHE-y)
15 ENC error Perform the maintenance instructed.
Message code : W090HH, W090xy
: Red
(Unit-x, ENC-y)
16 SENC error Perform the maintenance instructed.
Message code : W090AT
: Red
(Unit-x, ENC-y)
17 Loop error Perform the maintenance instructed.
: Red
(Path-x, Loop-y)
18 Path detachment Perform the maintenance instructed.
: Red
(Remote-x, Path-y)

TRBL 10-0100-01
Table 10.2.1.1 Recovery Procedure for Each Error Display (2)

No. Error Display Description Recovery procedure
: Red (RAID group defined) (Unit-x, HDU-y)
: Red + Black
Message text : Spare HDU alarm
: Red (Unit-x, HDU-y)
4 Though the disk array subsystem is set
: Red + Black to use a Spare Disk, but the Spare Disk
is not installed
: Red + Black
8 Though the disk array subsystem is set (Unit-x, HDU-y)
: Red + Black to use a Spare Disk, but the Spare Disk
is not installed
9 A cache backup circuit error occurred Perform the maintenance instructed.
Message code : W0340x
: Yellow
Message text : Battery back up circuit alarm
(CTL-x)
10 Controller down Issuance of this trap indicates that an error
: Red beginning with message code H occurred.
For detailed error information, see the WEB
log message display of the subsystem.
Perform the maintenance instructed.
Message code H#####. ##### is optional.
11 Fan error Perform the maintenance instructed.
: Red Message code : W040xy
(Unit-x, FAN-y)
12 Power Unit error Perform the maintenance instructed.
: Red
Message text : PS alarm (Unit-x, PS-y)

TRBL 10-0110-01
No. Error Display Description Recovery procedure

13 Battery voltage error Perform the maintenance instructed.
Message code :
: Red
W0300x, W0310x, W0320x, W0330x
Message text :
Battery alarm,
Battery alarm,
Battery SW off,
See the WEB log message display of the
subsystem.
14 Cache access error Perform the maintenance instructed.
Message code : W0D0xy
: Red
(CTL-x, CACHE-y)
15 ENC error Perform the maintenance instructed.
Message code : W090HH, W090xy
: Red
(Unit-x, ENC-y)
16 SENC error Perform the maintenance instructed.
Message code : W090AT
: Red
(Unit-x, ENC-y)
17 Loop error Perform the maintenance instructed.
: Red
(Path-x, Loop-y)
18 Path detachment Perform the maintenance instructed.
: Red
(Remote-x, Path-y)

TRBL 10-0120-01
10.2.2 Storage Navigator Modular Maintenance Function

Maintenance functions of the Storage Navigator Modular are listed in Table 10.2.2.
Table 10.2.2 Storage Navigator Modular Maintenance Function List

No Classification Function name Outline of function Notes
1 Display of statistical Display of state of the controller Statistical information is displayed An array unit not supported is
information operation by selecting an item. displayed in half tone and
Display of number of host cannot be selected.
command receptions
Display of state of command
execution
Display of state of the cache
load
Display number of drive
restoration starting
Display of cache memory
failures statistical information
Display of drive failures
statistical information
Display of drive DMA failures
Display of host DMA failures
Display of DUAL I/F system
failures statistical information
Display of preventive
maintenance failures statistical
information
2 Display of logical unit Display of logical unit failure The segments for each logical unit
failure data information data information are displayed.
3 Setting a prefetch size Setting prefetch information It sets a prefetch staging size by Prefetch information is set at an
the RAID levels, a next starting optimum value on shipment. If
opportunity and host data transfer the setting is changed
access size. unpreparedly, it will affect
performance and may interfere
with operation:
4 Setting a threshold Setting a threshold for It sets a threshold for the number of
preventive maintenance failures of a disk controlled by
preventive maintenance.
5 Drive maintenance Detach Blocks a specified drive forcibly.
Data reconstruction Reconstructs data on a specified

drive.
Copyback Copies data from a spare drive to a
specified drive.
Dynamic sparing Copies data forcibly from a
specified drive to a spare drive, and
then blocks the specified drive.
System copy Copies the system area of a
system drive from another system
drive.

TRBL 10-0130-01
No Classification Function name Outline of function Notes

6 Setting a mode for Setting a mode for reporting to This setting specifies a mode for
reporting to the host the host using an SSB reporting an SSB to the host when
a trouble such as a failure in a part
of the disk array subsystem occurs.
7 System Upgrade System Upgrade When upgrading a subsystem, with
reference to the variety of
information of partner equipment,
the information is set as self-
equipment.
8 Setting SATA Drive SATA Drive Options Refer to or set up the Sweep
Options function and the SMART function,
which are the SATA options.
9 Setting SATA Drive SATA Drive Restore Options Refer to or set up the restoration
Restore Options size of the SATA correction copy.
10 Replacing the Online Download and replacing of Download the ENC/SENC
ENC/SENC Firmware ENC/SENC Firmware. firmwareto the array subsystem,
and replacce it.
11 Drive Performance Drive Performance Delay If it is clear that the performance
Delay Diagnostic Diagnostic Function delay problem is caused by the
Function drive, setting this function notifies
the drive number of which caused
the problem through the message
and executes the dynamic sparing.

TRBL 10-0140-01
10.2.3 Displaying Statistical Information

You can display the statistical information in the array unit.
(1) Start the Storage Navigator Modular.
(3) Double-click the icon of an array unit on the Main screen.

The Unit screen is displayed.
(4) On the View menu select [Tools] [Statistical Information] or click : Statistical Information
in the tool bar.

TRBL 10-0150-01
The Statistical Information dialogue box is displayed.
- Statistical Information : Type of statistical information

Controller : State of the controller operation-------------------------------------------
(a) Displaying the Controller Use Condition (TRBL 10-0170)
Host Commands : Number of host command receptions--------------------------------------
(b) Displaying the Numbers of Host Commands Received (TRBL 10-
0170)
Execution : State of command execution------------------------------------------------
(c) Displaying the Command Execution Condition (TRBL 10-0180)
Cache Load : State of the cache load ------------------------------------------------------
(d) Displaying the Cache Load Condition (TRBL 10-0180)
Drive Restorations : Number of drive restoration starting --------------------------------------
(e) Displaying Number of Drive Restoration Starting (TRBL 10-0190)
Cache Memory : Cache memory failures statistical information---------------------------
(f) Displaying Cache Memory Failures Statistical Information (TRBL
10-0190)
Drive Obstacle : Drive failures statistical information --------------------------------------
(g) Displaying Drive Failures Statistical Information (TRBL 10-0200)
DDMA : Drive DMA failures statistical information --------------------------------
(h) Displaying Drive DMA failures statistical information (TRBL 10-
0210)
HDMA : Host DMA failures statistical information ---------------------------------
(i) Displaying Host DMA Failures Statistical Information (TRBL 10-
0210)
DUAL I/F : DUAL I/F system failures statistical information-------------------------
(j) Displaying DUAL I/F System Failures Statistical Information (TRBL
10-0220)
Drive Threshold : Preventive maintenance failures statistical information ---------------
(k) Displaying Preventive Maintenance Failures Statistical
Information (TRBL 10-0230)

TRBL 10-0160-01
(a) Displaying the Controller Use Condition

Click the Controller tab.
- Array Time:
Controller being active for (Integrated) : The accumulated power distribution time from
turning on the power supply of the array
subsystem to doing the planned stop is displayed in
minutes. When the planned stop is not executed
after the power supply of the array subsystem is
turned on, 0 (minute) is displayed.
Power on for (Work) : The progress time from turning on the power supply of the array
subsystem to the present is displayed in milliseconds.
- Controller:
Powered on counts : Integrated number of power ON times (at interruption) of the controller.
H-SCSI reset counts : An accumulated number of SCSI bus resets received from a host
computer is displayed.
(b) Displaying the Numbers of Host Commands Received

Click the Host Commands tab.
- LU : Logical unit number

- Read : Accumulated number of received read commands in each logical unit
- Write : Accumulated number of received write commands in each logical unit
TRBL 10-0170-01
(c) Displaying the Command Execution Condition

Click the Execution tab.
- A:Logical Unit : Logical unit number

- B:Read Cache Hits : Total of READ commands (hitting cache or partially hitting cache)
- C:Write Cache Hits : Total of WRITE commands (cache read hits)
- D:Sequential Read : Total of READ commands (recognized as sequential reading)
- E:Sequential Write : Total of WRITE commands (recognized as sequential writing)
- F:Prefetch Strings : Total of prefetch jobs executed
- G:Write Through Operation : Total of WRITE or WRITE & VERIFY commands (substituted by
Write-Through operations)
(d) Displaying the Cache Load Condition

Click the Cache Load tab.
- Number of Inflow Threshold Reached : Total number of occurrences of inflow limitations.
This equipment manages the amount of data in cache as an inflow limit. When the host tries
to write data exceeding this limit, an inflow limitation occurs. In this case, the write
request from the host waits until part of write data is transferred to the drive.

TRBL 10-0180-01
(e) Displaying Number of Drive Restoration Starting

Click the Drive Restoration tab.
- Drive Restoration Count:

Interleave : Accumulated number of starting of drive restoration using interleave
Background : Accumulated number of starting of drive restoration performed in the
background
- Total Number of System Restoration Starting : Accumulated number of system restoration
starts
(f) Displaying Cache Memory Failures Statistical Information

Click the Cache Memory tab.
- Number of Battery Power Drops : Accumulated number of cache battery voltage drops
- Correctable Error Threshold : Threshold number of correctable errors
- Number of Correctable Errors : Accumulated number of correctable errors per cache slot

TRBL 10-0190-01
(g) Displaying Drive Failures Statistical Information

Click the Drive Obstacle tab.
Double-click on the drive icon you want to display.

Drive Obstacle information dialogue box is displayed.
- Drive:
Unit No. : Unit No. of the selected drive.
HDU No. : HDU No. of the selected drive.
- Number of Online Verify Errors : Accumulated number of errors that occurred when
executing the read/write operations.
Correctable : Accumulated number of correctable errors occurred in on-line verify
execution.
Uncorrectable : Accumulated number of uncorrectable errors occurred in on-line verify
execution.
Restoration Count : Accumulated number of restorations occurred in on-line verify
execution
- Number of Read/Write Errors : Accumulated number of errors that occurred when
Mechanical Errors : Accumulated number of mechanism-related errors.
Medium Errors : Accumulated number of medium-related errors.
Read/Write Errors : Accumulated number of read/write-related errors.

TRBL 10-0200-01
Drive I/F Errors : Accumulated number of drive interface errors.

Controller Hard Errors : Accumulated number of controller hardware errors.
SCSI I/F Errors :Accumulated number of SCSI interface errors.

TRBL 10-0200-01
(h) Displaying Drive DMA failures statistical information

Click the DDMA tab.
- Retry Count:
DMA Error : Number of DMA error retries
Alternate Path : Number of alternate path retries against DMA errors
DRR Error : Number of DRR error retries
- Number of Errors : Number of DMA, DRR, Bus, and LA errors per DMA occurred in the
controller 0 and controller 1
(i) Displaying Host DMA Failures Statistical Information

Click the HDMA tab.
- Error Retries : Number of DMA error retries

- Errors Around DMA : Accumulated number of DMA-related errors
- Errors Around Bus : Accumulated number of bus-related errors
- LA Errors : Accumulated number of LA errors

TRBL 10-0210-01
(j) Displaying DUAL I/F System Failures Statistical Information

Click the Dual I/F tab.
- Other Correctable Errors : Accumulated number of correctable errors occurred in the

controller of another system
- Other Dual I/F Errors : Accumulated number of Dual I/F errors occurred in the controller of
another system
- Own Dual I/F Errors : Accumulated number of Dual I/F errors occurred in the controller of
own system

TRBL 10-0220-01
(k) Displaying Preventive Maintenance Failures Statistical Information

Click the Drive Threshold tab.
Double-click on the drive icon you want to display.

Drive Threshold state information dialog box is displayed.
- Drive:
Unit No. : Unit No. of the selected drive.
HDU No. : HDU No. of the selected drive.
- Number of Online Verify Errors : Accumulated number of errors that occurred when
Correctable : Accumulated number of correctable errors occurred in on-line verify
execution.
Uncorrectable : Accumulated number of uncorrectable errors occurred in on-line verify
execution.
Restoration Count : Accumulated number of restorations occurred in on-line verify
execution
- Number of Read/Write Errors : Accumulated number of errors that occurred when
Mechanical Errors : Accumulated number of mechanism-related errors.
Medium Errors : Accumulated number of medium-related errors.
Read/Write Errors : Accumulated number of read/write-related errors.

TRBL 10-0230-01
Drive I/F Errors : Accumulated number of drive interface errors.

Controller Hard Errors : Accumulated number of controller hardware errors.
SCSI I/F Errors : Accumulated number of SCSI interface errors.

TRBL 10-0230-01
(5) On the Mode menu, click the Exit. The Main screen is displayed.
(6) Click : Change Mode in the tool bar on the Main screen.
(7) A confirming message appears. Click the [OK] button.
Storage Navigator Modular enters Normal Mode, and Normal Mode appears at Active Mode at
the upper of the Main screen.

TRBL 10-0240-01
10.2.4 Displaying Logical Unit Failure Data Information

The PIN information of each logical unit is displayed.


TRBL 10-0250-01
(4) On the Settings menu, click the Maintenance.

Maintenance dialogue box is displayed.
(5) Click the LU Obstacle tab on the Maintenance dialogue box.
The number of segments, including PIN, in each logical unit is displayed.

TRBL 10-0260-01
10.2.5 Setting Pre-fetch Information

A prefetch staging size for each RAID level, next starting opportunity and host data transfer
access size are set.


TRBL 10-0270-01
(4) Select [Tools] [Tuning Parameter] in the unit window.
(5) Click the Prefetch tab on the Tuning Parameter dialogue box.
NOTE : The prefetch staging size, next starting opportunity and host data transfer
access size are set at optimum values. If the setting is changed unpreparedly,
it will affect performance and may interfere with operation. When changing
them, contact the manufacturer in advance.
(6) Select the LUN you want to modify the prefetch size, click the [Modify] button.
(7) Specify the Prefetch Size, click the [OK] button.

TRBL 10-0280-01
(8) Check if the settings that have been made are correct and click the [Apply] button.
(9) A message asking you to verify the setting is displayed. Click the [OK] button.
(10) When the setting is completed, the following message is displayed. Click the [OK] button.
(11) Click the [Close] button on the Tuning Parameter dialogue box.

TRBL 10-0290-01
10.2.6 Setting a Threshold for Preventive Maintenance

A threshold for the number of drive failure managed in preventive maintenance is set.


TRBL 10-0300-01

(5) Click the Threshold tab on the Maintenance dialogue box.
- Number of Read/Write Errors : Specifies a threshold of a read/write error.

Mechanical Errors : Accumulated number of mechanical error occurrences
Medium Errors : Accumulated number of medium error occurrences
Read/Write Errors : Accumulated number of read/write error occurrences
Drive I/F Errors : Accumulated number of drive interface error occurrences
Controller Hard Errors : Accumulated number of controller hardware error occurrences
SCSI I/F Errors : Accumulated number of SCSI interface error occurrences
- Number of Online Verify Errors : Specifies a threshold of a read/write error.
Correctable : Accumulated number of occurrences of correctable error in on-line verify
execution
Uncorrectable : Accumulated number of occurrences of uncorrective error in on-line verify
execution
A threshold is specified in the range of 1 to 65,535 with 1 as a unit. If you specify 0, it will not
be an object of preventive maintenance.
NOTE : A threshold is set at an optimum value : If the setting is changed unpreparedly,
it may perform preventive maintenance operation outside the range of it or
may not operate even though there is an object for it: When changing it,
contact the manufacturer in advance.

TRBL 10-0310-01
(6) Change the value and click the Apply button.


TRBL 10-0320-01
10.2.7 Drive Maintenance

Performs maintenance functions on drives mounted in array units such as blocking a drive
forcibly and instructing to restore.


TRBL 10-0330-01

(5) Click the Drive Maintenance tab on the Maintenance dialogue box.
- Drive Maintenance Function:

Detach : Blocks a drive specified in the Drive Location box forcibly.
Data Reconstruction : Reconstructs data on a drive specified in the Drive Location box. To a
drive specified in the Drive Location box, execute reconstruction after
replacing its HDU. If executing without replacing an HD, this results in
an error without executing the reconstruction.
Copy Back : Copies data from a spare drive to a drive specified in the Drive Location box.
Dynamic Sparing : Copies data forcibly from a drive specified in the Drive Location box to a
spare drive.
System Copy : Copies the system area from the current system drive to a system drive
specified in the Drive Location box.
- Drive Location:
Unit No. : Unit No. of a drive on which to perform a maintenance function
HDU No. : HDU No. of a drive on which to perform a maintenance function

TRBL 10-0340-01
(6) Select the Drive Maintenance Function to perform, and specifies the Drive Location of a drive
on which to perform a selected function.
(7) If you click the Apply button, a selected function will be performed.
(9) Click [ : Change Mode] in the tool bar on the Main screen.

TRBL 10-0350-01
10.2.8 Setting a Mode for Reporting to the Host Using an SSB

This setting specifies a mode for reporting an SSB to the host when a trouble such as a failure
in a part of the disk array subsystem occurs.


TRBL 10-0360-01

(5) Click the Warning Information tab on the Maintenance dialogue box.
- Report occurrence of warning to the host : Reporting an SSB to the host when a failure that
causes a warning occurs.
- Report recovery of warning to the host : Reporting an SSB to the host when the subsystem
recovers from a failure which caused a warning.
- Report over of statistics threshold to the host : Reporting an SSB to the host when any of the
statistical data exceeds its threshold value.
- Warning Information Report Mode:
Port : Reports the failure information of the port.
Logical Unit : Reports the failure information of the port, initiator, and logical unit.
(6) Click on an item you want to set to validate it, and then click the Apply button.

TRBL 10-0370-01

TRBL 10-0380-01
10.2.9 Setting SATA Drive Options

Refer to or set the SATA drive option.
(2) In the main window, position the focus ([ ]) on the icon [ ] of the array subsystem register
by pressing the [Tab] key, and then press the Ctrl, Shift, and E keys at the same time.


TRBL 10-0390-01

(5) Click the SATA tab on the Maintenance dialogue box.
- Sweep Function:
Enable/Disable : Make a selection whether to enable or disable the Sweep Function.
Drive I/O Suspended Time : Specify the drive I/O Suspended Time for the SATA drive with
Interval and Suspended Time.
Unload : Make a selection whether to enable or disable the Unload Function.
Online Verify Restriction : Make a selection whether to enable or disable the Online Verify
Restriction for the SATA drive. When you selected Enable, the
operating rate of online verification of a SATA drive will be
controlled to 1/6 times of FC drive. When you selected Disable,
it will be made the same as FC drive.
- SMART Function:
Enable/Disable : Make a selection whether to enable or disable the SMART Function.
Threshold : Specify the threshold value of the Reassign Mount to start the dynamic
sparing.
(6) Change the value and click the [Apply] button.

TRBL 10-0400-01
(7) A confirming message appears. Click [OK] button.

TRBL 10-0410-01
10.2.10 Setting SATA Drive Restore Options

Refer to or set the SATA drive restore option.
(2) In the main window, position the focus ([ ]) on the icon [ ] of the array subsystem register
by pressing the [Tab] key, and then press the Ctrl, Shift, and E keys at the same time.


TRBL 10-0420-01

(5) Click the SATA Restore Options tab on the Maintenance dialogue box.
- Correction Copy Mount : Specify the size of data to be restored at a time with by means of a
correction copy as a multiple n of the FC drive capacity.
(6) Change the value and click the [Apply] button.

(7) A confirming message appears. Click [OK] button.

TRBL 10-0430-01

TRBL 10-0440-01
10.2.11 Replacing the Online ENC/SENC Firmware

The function downloads and replaces the ENC/SENC Firmware in the array unit. When
replacing the ENC/SENC Firmware, download it, and then replace it.
Perform the replacement work of the ENC/SECN firmware referring to the following manual.
y HT-4064 Disk Array Subsystem Procedure for Online ENC/SENC Firmware Download
(a) Start the Storage Navigator Modular.
(b) In the main window, position the focus ([ ]) on the icon [ ] of the array subsystem
time.
Maintenance Mode is displayed in the Active Mode field at the top right on the Main screen,
and the Storage Navigator Modular operates in the maintenance mode.

TRBL 10-0450-01
(c) Double-click the icon of an array unit on the Main screen.

(d) On the Settings menu, click the Maintenance.


TRBL 10-0460-01
(e) Click the ENC Micro Update tab on the Maintenance dialogue box.
- Automatic Download : Specify whether or not to download the ENC/SENC Firmware

automatically. When you replace the ENC/SENC Firmware
manually, make the automatic downloading invalid using the
changing button.
- Revision (Read) (Base Unit) : A base unit revision stored in the computer in which the
Storage Navigator Modular is installed. When the base unit
revision is not read, a blank is displayed.
- Revision (Read) (External Unit) : An external unit revision stored in the computer in which
the Storage Navigator Modular is installed. When the
external unit revision is not read, a blank is displayed.
- Interval Time : Interval time for download. Specify the time between one second and 60
seconds. For the LAN connection, when the interval time is specified as 3
seconds, the download requires approximately 9 minutes. The time required
for the execution varies with the network status and depends on the I/Os
issued by the host. When the interval time is specified as one second longer,
the time required for the download is prolonged by 3 minutes. This function
can be used during execution of the I/O instructed by the host. However,
when the download function is executed, I/O performance of the host is
reduced. To enhance performance, specify a longer interval time.
- Revision (Downloaded) (Base Unit) : A base unit revision downloaded in the subsystem.
When the base unit revision is not downloaded, a
blank is displayed.
- Revision (Downloaded) (External Unit) : An external unit revision downloaded in the
subsystem. When the external unit revision is not
downloaded, a blank is displayed.
- Replace ENC with: : Specify the ENC whose firmware is to be replaced.
When no firmware is read, the Delete and Download buttons are displayed in gray and cannot
be selected.

TRBL 10-0470-01
10.2.12 Drive Performance Delay Diagnostic Function

If it is clear that the performance delay problem is caused by the drive, setting this function
notifies the drive number of which caused the problem through the message and executes the
dynamic sparing.
(1) Setting the drive performance delay diagnostic function in the Storage Navigator Modular.
(a) Start the Storage Navigator Modular.
(b) In the main window, position the focus ([ ]) on the icon [ ] of the array subsystem
time.
Maintenance Mode is displayed in the Active Mode field at the top right on the Main screen,
and the Storage Navigator Modular operates in the maintenance mode.
(c) Double-click the icon of an array unit on the Main screen.

(d) On the Settings menu, click the Maintenance.


TRBL 10-0480-01
(e) Click the Drive Response Diagnosis tab on the Maintenance dialogue box.
- Disable : The drive response time is not diagnosed.

- Enable (Output Message only):
The drive response time is diagnosed and a number of the drive that caused the response
delay is displayed in a message.
Diagnose SATA Drive:
Fill the check box when you want to diagnose the SATA drives.
Difference in response time of each drive :
The response time difference of the normal drive and the delay drive to specify the delay
drive in the same RAID group.
NOTE : Specify 2 for the value of Difference in response time of each drive. If setting
the value other than 2, contact the Technical Support Center.

TRBL 10-0490-01
- Enable (Output Message and Dynamic Sparing):

The drive response time is diagnosed, a number of the drive that caused the response delay is
displayed in a message, and the dynamic sparing is executed.
Diagnose SATA Drive:
Fill the check box when you want to diagnose the SATA drives.
Difference in response time of each drive :
The response time difference of the normal drive and the delay drive to specify the delay
drive in the same RAID group.
NOTE : Specify 2 for the value of Difference in response time of each drive. If setting
the value other than 2, contact the Technical Support Center.
(f) Click the [Apply] button.

TRBL 10-0500-01
.
FE-95DF751-00
Message
Chapter 1. Before Starting Trouble Analysis.................................................................... MSG 01-0000
Chapter 2. CUDG Detected Messages ............................................................................ MSG 02-0000
Chapter 3. Failure Messages ........................................................................................... MSG 03-0000
Chapter 4. Progress Message ......................................................................................... MSG 04-0000
Chapter 5. Flash Detected Messages.............................................................................. MSG 05-0000
Chapter 6. Warning Messages......................................................................................... MSG 06-0000
Chapter 7. Web Error Messages...................................................................................... MSG 07-0000
Chapter 8. Storage Navigator Modular Error Messages .................................................. MSG 08-0000
Chapter 9. Failure Analysis by Sense Data ..................................................................... MSG 09-0000
Chapter 10. ACE Tool Error Message ............................................................................... MSG 10-0000

MSG 00-0000-01

MSG 00-0010-01
Chapter 1. Before Starting Trouble Analysis

The contents of each failure detected during operation are reported by a message.
The failures detected during operation after the main switch of this unit is turned on and the
state of the unit are reported.
The failed parts of the Fibre Channel are classified into the path and loop.
c The following messages are indicated.

y CUDG detected message : 018 (Chapter 2. CUDG Detected Messages (MSG
02-0000))
y Failure messages : H (Chapter 3. Failure Messages (MSG 03-0000))
y Progress messages : I (Chapter 4. Progress Message (MSG 04-0000))
y Flash detected messages : R (Chapter 5. Flash Detected Messages (MSG
05-0000))
y Warning messages : W (Chapter 6. Warning Messages (MSG 06-0000))
y WEB messages : (Chapter 7. Web Error Messages (MSG 07-0000))
y Storage Navigator Modular messages : (Chapter 8.Storage Navigator Modular Error
Messages (MSG 08-0000))
y Sense Data : (Chapter 9. Failure Analysis by Sense Data (MSG 09-0000))
y ACE Tool Error Message : (Chapter 10. ACE Tool Error Message (MSG 10-0000))
d Message text : Message text is indicated.
e Description : Contents of failure are described concretely.
f Collection of errors
Collect the error
Simple CTL Memory
Trace Trace Dump
Gather
Simple trace : Collect simple trace

CTL Trace : Collect CTL trace
Dump : Collect memory dump.
Gather : Must be collected.
Space : Does not need to be collected.
g Recovery methods : How to recover from failure is indicated.
c,d : Recovery method number.
When - is written here, no recovery operation is required.
Resides this, when another message is indicated, analyze the another failure.
h Reference page : No. of page in which the recovery methods are described.

MSG 01-0000-01
1.1 Failed parts of the internal Fibre Channel

The failed parts of the internal Fibre Channel of DF700 are classified into the path and loop.
The respective configurations of these items are shown below.
In the case of RKM/RKAJ

Normal Normal (RKM)
loop loop

Disk Drive#
0
10
11
12
13
Cables between units Cables between units
ENC ENC
Unit#0 Unit#1
Loop#0 Loop#1 Unit ID#1
Loop#0 Loop#1
0
(RKAJ)
1
10
11
12
13
14

MSG 01-0010-01
RKM, RKAJ has four loops at the back end, which have the following names.
Path#0, Loop#0
Path#1, Loop#0
Path#0, Loop#1
Path#1, Loop#1
The paths and loops have the following meanings.
Path
Path Meaning
Path#0 2 Fibre lines connected to Disk Drive of even number
Path#1 2 Fibre lines connected to Disk Drive of odd number
Loop
Loop Meaning
Loop#0 2 Fibre lines on Control Unit #0 and ENC Unit #0
Loop#1 2 Fibre lines on Control Unit #1 and ENC Unit #1

MSG 01-0020-01
In the case of RKS

Normal Normal (RKS)
loop loop

Disk Drive#
0
10
11
12
13
RKS has two loops at the back end, which have the following names.
Path#0, Loop#0
Path#1, Loop#0
Path#0, Loop#1
Path#1, Loop#1
Path
Path Meaning
Path#0 2 Fibre lines connected to Disk Drive of even number
Path#1 2 Fibre lines connected to Disk Drive of odd number
Loop
Loop Meaning
Loop#0 2 Fibre lines on Control Unit #0
Loop#1 2 Fibre lines on Control Unit #1

MSG 01-0030-01
A case where the RKM+RKAJATs+RKAJs are connected

Fibre Chip Fibre Chip Fibre Chip Fibre Chip Unit ID#0
Alternative loop
(RKM)

Disk Drive#
0
12
13

(RKAJAT) (RKAJAT)
SENC SENC SENC SENC
Path CTL Path CTL
0 0
Path CTL Path CTL
1 1
Path CTL Path CTL

FC-SATA FC-SATA FC-SATA FC-SATA
Conversion Conversion Conversion Conversion
2 2
Path CTL Path CTL
3 3
Path CTL Path CTL
14 14

(RKAJ) (RKAJ)
SENC SENC
Unit#0 Unit#1
0
13
14

MSG 01-0040-01
RKM, RKAJ, RKAJAT has four loops at the back end, which have the following names.
Path#0, Loop#0
Path#1, Loop#0
Path#0, Loop#1
Path#1, Loop#1
Path
Path Meaning
Path#0 Two Fibre lines connected to Disk Drives with even numbers, or two Fibre lines connected to
the FC-SATA converter on the device ID #2x side in the case of a connection to the RKAJAT.
Path#1 Two Fibre lines connected to Disk Drives with odd numbers, or two Fibre lines connected to
the FC-SATA converter on the device ID #3x side in the case of a connection to the RKAJAT.
Loop
Loop Meaning
Loop#0 Two Fibre lines on the Control Unit #0, ENC Unit #0, and SENC Unit #0.
(In the case of the RKAJAT, the FC-SATA converter is connected to the Fibre lines.)
Loop#1 Two Fibre lines on the Control Unit #1, ENC Unit #1, and SENC Unit #1.

MSG 01-0050-01
A case where the RKAJs+RKAJATs are connected


(RKAJ) (RKAJAT)
Disk Drive# Path CTL Path CTL

Pat h#0 Pat h#1 Pat h#0 Pat h#1
Loop#0 Loop#0 Loop#1 Loop#1 0 0
0
Path CTL Path CTL
1
2 FC- 1 FC- FC- 1 FC-

SATA SATA SATA SATA
3 Con- Path CTL Con- Con- Path CTL Con-
version version version version
2 2
Path CTL Path CTL

13
ENC ENC 14 14
14 SENC SENC SENC SENC
Unit#0 Unit#1 Unit#0 Unit#1 Unit#0 Unit#1
Cables
between units
(RKAJAT) (RKAJAT) (RKAJAT) (RKAJAT)
0 0 0 0

2 2 2 2
14 14 14 14
Cables
between units
(RKAJAT) (RKAJAT) (RKAJAT) (RKAJAT)
0 0 0 0

2 2 2 2
14 14 14 14

MSG 01-0060-01
RKAJ, RKAJAT has two loops at the back end, which have the following names.
Path#0, Loop#0
Path#1, Loop#0
Path#2, Loop#0
Path#3, Loop#0
Path#0, Loop#1
Path#1, Loop#1
Path#2, Loop#1
Path#3, Loop#1
Path
Path Meaning
Path#0 Two Fibre lines connected to Disk Drives with even numbers on the device ID #0x side, or two
Fibre lines connected to the FC-SATA converter on the device ID #2x side in the case of a
connection to the RKAJAT.
Path#1 Two Fibre lines connected to Disk Drives with odd numbers on the device ID #0x side, or two
Path#2 Two Fibre lines connected to Disk Drives with even numbers on the device ID #1x side, or two
Path#3 Two Fibre lines connected to Disk Drives with odd numbers on the device ID #1x side, or two
Loop
Loop Meaning
Loop#0 Four Fibre lines on the Control Unit #0, ENC Unit #0, and SENC Unit #0.
Loop#1 Four Fibre lines on the Control Unit #1, ENC Unit #1, and SENC Unit #1.

MSG 01-0070-01
Chapter 2. CUDG Detected Messages

Collect the error
Message
Message text Description Simple CTL Full Recovery methods Reference page
code
Trace Trace Dump
01801101 DUAL register data Inconsistency between write and Gather cWhen W0100x CTL alarm Chapter 6. Warning
compare error read data was detected in the is displayed following this Messages (MSG 06-
[OWN_CTL] dual register R/W test of the message, take recovery 0000)
data transfer control LSI. actions according to the
message.
01801102 DUAL register data Inconsistency between write and Gather dReplace the Control Unit of Replacement 2.2.5
compare error read data was detected in the which the CALM LED lights Replacing Control
[ALL_CTL] dual register R/W test of the on except for c. Unit (REP 02-0390)
data transfer control LSI. e If not recovered, replace
01801201 DUAL IORDY status DUAL IORDY status error of the Gather not the inserted Control
error [OWN_CTL] data transfer control LSI was Unit but the other Control
detected. Unit. (The replacement
01801202 DUAL IORDY status DUAL IORDY status error of the Gather cannot be done when the
error [OWN_CTL] data transfer control LSI was subsystem power is on.)
detected.
01801301 DUAL DESKEW DESKEW status error of the Gather
status error data transfer control LSI was
[OWN_CTL] detected.
[OWN_CTL] detected.
01802101 FM1 SEL Check The SUM1 of the Flash Memory Gather c When W0100x CTL alarm Chapter 6. Warning
SUM1 error SEL was inconsistent with the is displayed following this Messages (MSG 06-
[OWN_CTL] calculated SUM1. message, take recovery 0000)
01802102 FM1 SEL Check The SUM2 of the Flash Memory Gather actions according to the
SUM2 error SEL was inconsistent with the message.
[OWN_CTL] calculated SUM2. d Replace the Control Unit of Replacement 2.2.5
01803101 FM1 MAIN SEL The SUM1 of the Flash Memory Gather which the CALM LED lights Replacing Control
Check SUM1 error MAIN was inconsistent with the on except for c. Unit (REP 02-0390)
[OWN_CTL] calculated SUM1.
01803102 FM1 MAIN SEL The SUM2 of the Flash Memory Gather
Check SUM2 error MAIN was inconsistent with the
01804101 FM1 INS SEL Check The SUM1 of the Flash Memory Gather
SUM1 error INS was inconsistent with the
01804102 FM1 INS SEL Check The SUM2 of the Flash Memory Gather
01805101 CSDS data line error Inconsistency between the write Gather
[OWN_CTL] and read data was detected in
the data line test of the local
memory (CSDS).

MSG 02-0000-01
Collect the error

Message
code
Trace Trace Dump
01805201 CSDS address line Inconsistency between the write Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] and read data was detected in is displayed following this Messages (MSG 06-
the address line test of the local message, take recovery 0000)
memory (CSDS). actions according to the
01805301 CSDS ECC circuit The ECC error could not be Gather message.
error [OWN_CTL] detected in the ECC Circuit test d Replace the Control Unit of Replacement 2.2.5
of the local memory (CSDS). which the CALM LED lights Replacing Control
01805401 CSDS 4byte data Inconsistency between the write Gather on except for c. Unit (REP 02-0390)
compare error and read data was detected in
[OWN_CTL] the 4byte R/W test of the local
memory (CSDS).
01805501 CSDS 2byte data Inconsistency between the write Gather
memory (CSDS).
01805601 CSDS 1byte data Inconsistency between the write Gather
memory (CSDS).
01806101 L1 data cache error Inconsistency between the write Gather
the R/W test of the L1 data
cache in the CPU.
01806201 L1 instruction cache The instruction was executed Gather
error [OWN_CTL] incorrectly in the instruction test
of the L1 instruction cache in the
CPU.
01807101 L2 cache error Inconsistency between the write Gather
the R/W test of the L2 cache in
the CPU.
01807201 L2 cache error Inconsistency between the write Gather
the R/W test of the L2 cache in
the CPU.
0180C001 CSDS 4byte data Inconsistency between the write Gather
memory (CSDS).
01804201 FM1 INS Check The SUM1 of the Flash Memory Gather
01804202 FM1 INS Check The SUM2 of the Flash Memory Gather

MSG 02-0010-01
Collect the error

Message
code
Trace Trace Dump
01812101 CSDS 4byte data Inconsistency between the write Gather c When W0100x CTL alarm Chapter 6. Warning
compare error and read data was detected in is displayed following this Messages (MSG 06-
[OWN_CTL] the 4byte R/W test of the local message, take recovery 0000)
memory (CSDS). actions according to the
01823001 Bridge SRAM data Inconsistency between the write Gather message.
line error [OWN_CTL] and read data was detected in dReplace the Control Unit of Replacement 2.2.5
the data line test of the SRAM in which the CALM LED lights Replacing Control
the Bridge. on except for c. Unit (REP 02-0390)
01823002 Bridge SRAM Inconsistency between the write Gather
address line error and read data was detected in
[OWN_CTL] the address line test of the
SRAM in the Bridge.
SRAM in the Bridge.
SRAM in the Bridge.
01823005 Bridge SRAM ECC The ECC error could not be Gather
circuit error detected in the ECC circuit test
[OWN_CTL] of the SRAM in the Bridge.
01823006 Bridge SRAM 4byte Inconsistency between the write Gather
data compare error and read data was detected in
[OWN_CTL] the 4byte R/W test of the SRAM
in the Bridge.
in the Bridge.
in the Bridge.
01824001 TWSI CTL number The CTL number information Gather
information error that was got via the TWSI (Two
[OWN_CTL] Wired Serial Interface) was
incorrect.
01824002 TWSI unit type The Unit type information that Gather
information error was got via the TWSI (Two
incorrect.
01824003 TWSI host I/F type The Interface Board information Gather
information error that was got via the TWSI (Two
incorrect.

MSG 02-0020-01
Collect the error

Message
code
Trace Trace Dump
01824010 TWSI CACHE#0 Getting of information on the Gather cCheck whether a cache Replacement 2.2.6
information error cache memory of the DIMM slot memory is installed in the Replacing Cache
[OWN_CTL] #0 via the TWSI (Two Wired cache slot #0 of the Control Unit (REP 02-0540)
Serial Interface) was attempted, Unit whose CALM LED is
but the getting failed. on. If it is not installed,
install a cache memory in
the cache slot #0.
dWhen the cache memory is
installed firmly, replace it.
If not, install it firmly in the
cache memory slot.
eIf not recovered, replace Replacement 2.2.5
the Control Unit. Replacing Control
Unit (REP 02-0390)
01825101 IDMA data transfer A transfer failed in the IDMA Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] transfer test. is displayed following this Messages (MSG 06-
01825102 IDMA data transfer A time-out of transfer occurred Gather message, take recovery 0000)
time out [OWN_CTL] in the IDMA transfer test. actions according to the
01825103 IDMA data compare Data that was transferred in the Gather message.
error [OWN_CTL] IDMA transfer test was dReplace the Control Unit of Replacement 2.2.5
inconsistent with the test data of which the CALM LED lights Replacing Control
the sender. on except for c. Unit (REP 02-0390)
01826101 LAN register data Inconsistency between write and Gather
compare error read data was detected in the
[OWN_CTL] R/W test of the LAN register.
01826102 LAN register data Inconsistency between write and Gather
[OWN_CTL] R/W test of the LAN register.
01826201 LAN loop back A transfer failed in the LAN loop Gather
transfer time out back transfer test.
[OWN_CTL]
01826202 LAN loop back A time-out of transfer occurred Gather
transfer status error in the LAN loop back transfer
[OWN_CTL] test.
01826203 LAN loop back Data that was transferred in the Gather
transfer data compare LAN loop back transfer test was
error [OWN_CTL] inconsistent with the test data of
the sender.
01831101 MCTL register data Inconsistency between write and Gather
[OWN_CTL] R/W test of the MCTL register in
the data transfer control LSI.
01831102 MCTL register data Inconsistency between write and Gather
[OWN_CTL] R/W test of the MCTL register in
the data transfer control LSI.
01831103 MCTL status error An illegal error status occurred Gather
[OWN_CTL] in the R/W test of the MCTL
register in the data transfer
control LSI.

MSG 02-0030-01

MSG 02-0030-01
Collect the error

Message
code
Trace Trace Dump
01833101 MCTL CTC CH0 stop The CTC CH0 was out of Gather c When W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] operation in the MCTL CTC is displayed following this Messages (MSG 06-
CH0 test in the data transfer message, take recovery 0000)
control LSI. actions according to the
01833201 MCTL CTC CH0 The CTC CH0 count was Gather message.
count error incorrect in a test of the MCTL dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] CTC CH0 in the data transfer which the CALM LED lights Replacing Control
control LSI. on except for c. Unit (REP 02-0390)
01833202 MCTL CTC CH0 A parity error of the CTC CH0 Gather
parity error occurred in a test of the MCTL
[OWN_CTL] CTC CH0 in the data transfer
control LSI.
01833203 MCTL CTC CH0 The CTC CH0 count was Gather
count check timeout incorrect in a test of the MCTL
error [OWN_CTL] CTC CH0 in the data transfer
control LSI.
count error incorrect in a test of the MCTL
control LSI.
01833502 MCTL CTC CH1 A parity error of the CTC CH1 Gather
parity error occurred in a test of the MCTL
control LSI.
count check timeout incorrect in a test of the MCTL
error [OWN_CTL] CTC CH1 in the data transfer
control LSI.
01834101 MCTL error force NG The Read Only Register Write Gather
[OWN_CTL] Error did not occurred in the
MCTL force test in the data
transfer control LSI.
01834102 MCTL error force NG The MPCTL1 Input Data Parity Gather
01834103 MCTL error force NG The INVDIN Input Data Parity Gather
01834104 MCTL error force NG The MPCTL1 CTCCH0 Parity Gather
01834105 MCTL error force NG The CTCCH1 Parity Error Test Gather
[OWN_CTL] did not occurred in the MCTL
force test in the data transfer
control LSI.

MSG 02-0040-01
Collect the error

Message
code
Trace Trace Dump
01834106 MCTL error force NG The MPCTL1 WCDGCNT Parity Gather c When W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] Error did not occurred in the is displayed following this Messages (MSG 06-
MCTL force test in the data message, take recovery 0000)
transfer control LSI. actions according to the
01835101 Backend path#0 The setting of the Path #0 was Gather message.
control error not reflected on the TWSI (Two dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] Wired Serial Interface) GPI0 in which the CALM LED lights Replacing Control
the backend path control test. on except for c. Unit (REP 02-0390)
01835102 Backend path#1 The setting of the Path #1 was Gather
control error not reflected on the TWSI (Two
[OWN_CTL] Wired Serial Interface) GPI0 in
the backend path control test.
01844101 DCTL register data Inconsistency between the write Gather
[OWN_CTL] the system register R/W test of
the data transfer control LSI
(DCTL).
[OWN_CTL] the system register R/W test of
(DCTL).
01844103 DCTL status error An illegal error status occurred Gather
[OWN_CTL] in the system register R/W test
of the data transfer control LSI
(DCTL).
[OWN_CTL] the own system dual register
R/W test of the data transfer
control LSI (DCTL).
[OWN_CTL] the own system dual register
control LSI (DCTL).
[OWN_CTL] in the own system dual register
control LSI (DCTL).

MSG 02-0050-01
Collect the error

Message
code
Trace Trace Dump
01844301 DCTL buffer write A write time-out occurred in the Gather c When W0100x CTL alarm Chapter 6. Warning
time out [OWN_CTL] primary PCI buffer R/W test of is displayed following this Messages (MSG 06-
the data transfer control LSI message, take recovery 0000)
(DCTL). actions according to the
01844302 DCTL buffer read A read time-out occurred in the Gather message.
time out [OWN_CTL] primary PCI buffer R/W test of dReplace the Control Unit of Replacement 2.2.5
the data transfer control LSI which the CALM LED lights Replacing Control
(DCTL). on except for c. Unit (REP 02-0390)
01844303 DCTL buffer parity A parity error occurred in the Gather
error [OWN_CTL] primary PCI buffer R/W test of
(DCTL).
01844304 DCTL buffer data Inconsistency between the write Gather
[OWN_CTL] the primary PCI buffer R/W test
(DCTL).
01844401 DCTL buffer write A write time-out occurred in the Gather
time out [OWN_CTL] Drive PCI #0 buffer R/W test of
(DCTL).
01844402 DCTL buffer read A read time-out occurred in the Gather
time out [OWN_CTL] Drive PCI #0 buffer R/W test of
(DCTL).
error [OWN_CTL] Drive PCI #0 buffer R/W test of
(DCTL).
[OWN_CTL] the Drive PCI #0 buffer R/W test
(DCTL).
time out [OWN_CTL] Host PCI #0 buffer R/W test of
(DCTL).
time out [OWN_CTL] Host PCI #0 buffer R/W test of
(DCTL).
error [OWN_CTL] Host PCI #0 buffer R/W test of
(DCTL).

MSG 02-0060-01
Collect the error

Message
code
Trace Trace Dump
01844604 DCTL buffer data Inconsistency between the write Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] the Host PCI #0 R/W test of the message, take recovery 0000)
data transfer control LSI actions according to the
(DCTL). message.
01844801 DCTL buffer write A write time-out occurred in the Gather dReplace the Control Unit of Replacement 2.2.5
time out [OWN_CTL] MDMA buffer R/W test of the which the CALM LED lights Replacing Control
data transfer control LSI on except for c. Unit (REP 02-0390)
(DCTL).
time out [OWN_CTL] MDMA buffer R/W test of the
data transfer control LSI
(DCTL).
error [OWN_CTL] MDMA buffer R/W test of the
(DCTL).
[OWN_CTL] the MDMA buffer R/W test of the
(DCTL).
time out [OWN_CTL] own system dual buffer R/W test
(DCTL).
time out [OWN_CTL] own system dual buffer R/W test
(DCTL).
error [OWN_CTL] own system dual buffer R/W test
(DCTL).
[OWN_CTL] the own system dual buffer R/W
test of the data transfer control
LSI (DCTL).
[OWN_CTL] the DMA #0 system register
buffer R/W test of the data
transfer control LSI (DCTL).
[OWN_CTL] the DMA #0 system register
buffer R/W test of the data

MSG 02-0070-01
Collect the error

Message
code
Trace Trace Dump
01845103 DCTL status error An illegal error status occurred Gather c When W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] in the DMA #0 system register is displayed following this Messages (MSG 06-
R/W test of the data transfer message, take recovery 0000)
control LSI (DCTL). actions according to the
01845201 DCTL register data Inconsistency between the write Gather message.
compare error and read data was detected in dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] the D_Port system register which the CALM LED lights Replacing Control
buffer R/W test of the data on except for c. Unit (REP 02-0390)
[OWN_CTL] the D_Port system register R/W
LSI (DCTL).
[OWN_CTL] in the D_Port system register
control LSI (DCTL).
[OWN_CTL] the H_Port system register R/W
LSI (DCTL).
[OWN_CTL] the H_Port system register R/W
LSI (DCTL).
[OWN_CTL] in the H_Port system register
control LSI (DCTL).
time out [OWN_CTL] DMA #0 buffer R/W test of the
(DCTL).
time out [OWN_CTL] DMA #0 buffer R/W test of the
(DCTL).
error [OWN_CTL] DMA #0 buffer R/W test of the
(DCTL).
[OWN_CTL] the DMA #0 buffer R/W test of
(DCTL).

MSG 02-0080-01
Collect the error

Message
code
Trace Trace Dump
01845501 DCTL buffer write A write time-out occurred in the Gather c When W0100x CTL alarm Chapter 6. Warning
time out [OWN_CTL] D_Pprt #00 buffer R/W test of is displayed following this Messages (MSG 06-
the data transfer control LSI message, take recovery 0000)
01845502 DCTL buffer read A read time-out occurred in the Gather message.
time out [OWN_CTL] D_Pprt #00 buffer R/W test of dReplace the Control Unit of Replacement 2.2.5
the data transfer control LSI which the CALM LED lights Replacing Control
error [OWN_CTL] D_Port #00 buffer R/W test of
(DCTL).
[OWN_CTL] the D_Port #00 buffer R/W test
(DCTL).
time out [OWN_CTL] D_Port #01 buffer R/W test of
(DCTL).
time out [OWN_CTL] D_Port #01 buffer R/W test of
(DCTL).
error [OWN_CTL] D_Port #01 buffer R/W test of
(DCTL).
[OWN_CTL] the D_Port #01 buffer R/W test
(DCTL).
time out [OWN_CTL] H_Port #00 buffer R/W test of
(DCTL).
(DCTL).
error [OWN_CTL] H_Port #00 buffer R/W test of
(DCTL).

MSG 02-0090-01
Collect the error

Message
code
Trace Trace Dump
01845904 DCTL buffer data Inconsistency between the write Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] the H_Port #00 buffer R/W test message, take recovery 0000)
of the data transfer control LSI actions according to the
(DCTL). message.
01845A01 DCTL buffer write A write time-out occurred in the Gather dReplace the Control Unit of Replacement 2.2.5
time out [OWN_CTL] H_Port #01 buffer R/W test of which the CALM LED lights Replacing Control
the data transfer control LSI on except for c. Unit (REP 02-0390)
(DCTL).
01845A02 DCTL buffer read A read time-out occurred in the Gather
(DCTL).
01845A03 DCTL buffer parity A parity error occurred in the Gather
error [OWN_CTL] H_Port #01 buffer R/W test of
(DCTL).
01845A04 DCTL buffer data Inconsistency between the write Gather
[OWN_CTL] the H_Port #01 buffer R/W test
(DCTL).
01845D01 DCTL buffer write A write time-out occurred in the Gather
time out [OWN_CTL] H_Port #S1 buffer R/W test of
(DCTL).
01845D02 DCTL buffer read A read time-out occurred in the Gather
time out [OWN_CTL] H_Port #S1 buffer R/W test of
(DCTL).
01845D03 DCTL buffer parity A parity error occurred in the Gather
error [OWN_CTL] H_Port #S1 buffer R/W test of
(DCTL).
01845D04 DCTL buffer data Inconsistency between the write Gather
[OWN_CTL] the H_Port #S1 buffer R/W test
(DCTL).
01845E01 DCTL register data Inconsistency between the write Gather
[OWN_CTL] the NAS system register R/W
LSI (DCTL).
01845E02 DCTL register data Inconsistency between the write Gather
[OWN_CTL] the NAS system register R/W
LSI (DCTL).

MSG 02-0100-01
Collect the error

Message
code
Trace Trace Dump
01845E03 DCTL status error An illegal error status occurred Gather c When W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] in the NAS system register R/W is displayed following this Messages (MSG 06-
test of the data transfer control message, take recovery 0000)
LSI (DCTL). actions according to the
01845F01 DCTL register data Inconsistency between the write Gather message.
compare error and read data was detected in dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] the Monitor system register R/W which the CALM LED lights Replacing Control
test of the data transfer control on except for c. Unit (REP 02-0390)
LSI (DCTL).
01845F02 DCTL register data Inconsistency between the write Gather
[OWN_CTL] the Monitor system register R/W
LSI (DCTL).
01845F03 DCTL status error An illegal error status occurred Gather
[OWN_CTL] in the Monitor system register
control LSI (DCTL).
01846101 DUAL register data Inconsistency between the write Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] the other system dual register message, take recovery 0000)
R/W test of the data transfer actions according to the
control LSI. message.
01846102 DUAL register data Inconsistency between the write Gather dReplace the Control Unit of Replacement 2.2.5
compare error and read data was detected in which the CALM LED lights Replacing Control
[OWN_CTL] the other system dual register on except for c. Unit (REP 02-0390)
R/W test of the data transfer e If not recovered, replace
control LSI. not the inserted Control
01846103 DUAL status error An illegal error status occurred Gather Unit but the other Control
[OWN_CTL] in the other system dual register Unit. (The replacement
R/W test of the data transfer cannot be done when the
control LSI. subsystem power is on.)
01846141 DUAL register data Inconsistency between the write Gather
[ALT_CTL] the other system dual register
control LSI.
01846142 DUAL register data Inconsistency between the write Gather
[ALT_CTL] the other system dual register
control LSI.
01846143 DUAL status error Inconsistency between the write Gather
[ALT_CTL] and read data was detected in
the other system dual register
control LSI.

MSG 02-0110-01
Collect the error

Message
code
Trace Trace Dump
01846201 DUALS buffer write A write time-out occurred in the Gather c When W0100x CTL alarm Chapter 6. Warning
time out [OWN_CTL] other system dual buffer R/W is displayed following this Messages (MSG 06-
test of the data transfer control message, take recovery 0000)
LSI. actions according to the
01846202 DUALS buffer read A read time-out occurred in the Gather message.
time out [OWN_CTL] other system dual buffer R/W dReplace the Control Unit of Replacement 2.2.5
test of the data transfer control which the CALM LED lights Replacing Control
LSI. on except for c. Unit (REP 02-0390)
01846203 DUALS buffer parity A parity error occurred in the Gather e If not recovered, replace
error [OWN_CTL] other system dual buffer R/W not the inserted Control
test of the data transfer control Unit but the other Control
LSI. Unit. (The replacement
01846204 DUALS buffer data Inconsistency between the write Gather cannot be done when the
compare error and read data was detected in subsystem power is on.)
[OWN_CTL] the other system dual buffer
control LSI.
01846241 DUALS buffer write A write time-out occurred in the Gather
time out [ALT_CTL] other system dual buffer R/W
LSI.
01846242 DUALS buffer read A read time-out occurred in the Gather
time out [ALT_CTL] other system dual buffer R/W
LSI.
01846243 DUALS buffer parity A parity error occurred in the Gather
error [ALT_CTL] other system dual buffer R/W
LSI.
01846244 DUALS buffer data Inconsistency between the write Gather
[ALT_CTL] the other system dual buffer
control LSI.
01846301 DUALM error force The ADR_PTY_ERR did not Gather
NG [OWN_CTL] occur in the own system dual
force test of the data transfer
control LSI.
01846302 DUALM error force The WDT_PTY_ERR did not Gather
control LSI.
01846303 DUALM error force The WRDY_TIME_OUT did not Gather
control LSI.

MSG 02-0120-01
Collect the error

Message
code
Trace Trace Dump
01846304 DUALM error force The CNT_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
NG [OWN_CTL] occur in the own system dual is displayed following this Messages (MSG 06-
force test of the data transfer message, take recovery 0000)
01846305 DUALM error force The RRDY_TIME_OUT did not Gather message.
NG [OWN_CTL] occur in the own system dual dReplace the Control Unit of Replacement 2.2.5
force test of the data transfer which the CALM LED lights Replacing Control
control LSI. on except for c. Unit (REP 02-0390)
01846306 DUALM error force The RDT_PTY_ERR did not Gather e If not recovered, replace
NG [OWN_CTL] occur in the own system dual not the inserted Control
force test of the data transfer Unit but the other Control
control LSI. Unit. (The replacement
01846341 DUALM error force The ADR_PTY_ERR did not Gather cannot be done when the
NG [ALT_CTL] occur in the own system dual subsystem power is on.)
control LSI.
01846342 DUALM error force The WDT_PTY_ERR did not Gather
NG [ALT_CTL] occur in the own system dual
control LSI.
01846343 DUALM error force The WRDY_TIME_OUT did not Gather
control LSI.
01846344 DUALM error force The CNT_PTY_ERR did not Gather
control LSI.
01846345 DUALM error force The RRDY_TIME_OUT did not Gather
control LSI.
01846346 DUALM error force The RDT_PTY_ERR did not Gather
control LSI.
01846401 DUAL IORDY status DUAL IORDY status error of the Gather
error [OWN_CTL] data transfer control LSI was
detected.
[OWN_CTL] detected.
01846441 DUAL IORDY status DUAL IORDY status error of the Gather
error [ALT_CTL] data transfer control LSI was
detected.
[ALT_CTL] detected.

MSG 02-0130-01
Collect the error

Message
code
Trace Trace Dump
01846901 DUALS error force The WDT_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
NG [OWN_CTL] occur in the other system dual is displayed following this Messages (MSG 06-
01846902 DUALS error force The WDT_PTY_ERR (peculiar Gather message.
NG [OWN_CTL] to the MP) did not occur in the dReplace the Control Unit of Replacement 2.2.5
other system dual force test of which the CALM LED lights Replacing Control
the data transfer control LSI. on except for c. Unit (REP 02-0390)
01846903 DUALS error force The MP_CAC_RD_PERR did Gather e If not recovered, replace
NG [OWN_CTL] not occur in the other system not the inserted Control
dual force test of the data Unit but the other Control
transfer control LSI. Unit. (The replacement
01846904 DUALS error force The CNT_PTY_ERR did not Gather cannot be done when the
NG [OWN_CTL] occur in the other system dual subsystem power is on.)
control LSI.
01846905 DUALS error force The CA_WDT_PTY_ERR did Gather
NG [OWN_CTL] not occur in the other system
dual force test of the data
01846906 DUALS error force The CA_ECC_GEN_ERR did Gather
01846907 DUALS error force The CMD_ERR did not occur in Gather
NG [OWN_CTL] the other system dual force test
of the data transfer control LSI.
01846908 DUALS error force The CA_RD_ECC_COR_ERR Gather
NG [OWN_CTL] did not occur in the other system
01846909 DUALS error force The CA_RD_ECC_COR did not Gather
NG [OWN_CTL] occur in the other system dual
control LSI.
0184690A DUALS error force The Gather
NG [OWN_CTL] CA_RD_ECC_UNCOR_ERR did
not occur in the other system
0184690B DUALS error force The CA_RD_RCLK_ERR did Gather

MSG 02-0140-01
Collect the error

Message
code
Trace Trace Dump
01846941 DUALS error force The WDT_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
NG [ALT_CTL] occur in the other system dual is displayed following this Messages (MSG 06-
01846942 DUALS error force The WDT_PTY_ERR (peculiar Gather message.
NG [ALT_CTL] to the MP) did not occur in the dReplace the Control Unit of Replacement 2.2.5
other system dual force test of which the CALM LED lights Replacing Control
the data transfer control LSI. on except for c. Unit (REP 02-0390)
01846943 DUALS error force The MP_CAC_RD_PERR did Gather e If not recovered, replace
NG [ALT_CTL] not occur in the other system not the inserted Control
dual force test of the data Unit but the other Control
transfer control LSI. Unit. (The replacement
01846944 DUALS error force The CNT_PTY_ERR did not Gather cannot be done when the
NG [ALT_CTL] occur in the other system dual subsystem power is on.)
control LSI.
01846945 DUALS error force The CA_WDT_PTY_ERR did Gather
NG [ALT_CTL] not occur in the other system
01846946 DUALS error force The CA_ECC_GEN_ERR did Gather
01846947 DUALS error force The CMD_ERR did not occur in Gather
NG [ALT_CTL] the other system dual force test
of the data transfer control LSI.
01846948 DUALS error force The CA_RD_ECC_COR_ERR Gather
NG [ALT_CTL] did not occur in the other system
01846949 DUALS error force The CA_RD_ECC_COR did not Gather
NG [ALT_CTL] occur in the other system dual
control LSI.
0184694A DUALS error force The Gather
NG [ALT_CTL] CA_RD_ECC_UNCOR_ERR did
not occur in the other system
0184694B DUALS error force The CA_RD_RCLK_ERR did Gather

MSG 02-0150-01
Collect the error

Message
code
Trace Trace Dump
01846A01 DUAL IORDY status DUAL IORDY status error of the Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] data transfer control LSI was is displayed following this Messages (MSG 06-
detected. message, take recovery 0000)
01846A02 DUAL DESKEW DESKEW status error of the Gather actions according to the
status error data transfer control LSI was message.
[OWN_CTL] detected. d Replace the Control Unit of Replacement 2.2.5
01846A41 DUAL IORDY status DUAL IORDY status error of the Gather which the CALM LED lights Replacing Control
error [ALT_CTL] data transfer control LSI was on except for c. Unit (REP 02-0390)
detected. e If not recovered, replace
01846A42 DUAL DESKEW DESKEW status error of the Gather not the inserted Control
status error data transfer control LSI was Unit but the other Control
[ALT_CTL] detected. Unit. (The replacement
cannot be done when the
subsystem power is on.)
01847101 DCTL DMA0 transfer A transfer failed in the DMA #0 Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] transfer test of the data transfer is displayed following this Messages (MSG 06-
control LSI (DCTL). message, take recovery 0000)
01847102 DCTL DMA0 transfer A time-out of transfer occurred Gather actions according to the
time out error in the DMA #0 transfer test of message.
[OWN_CTL] the data transfer control LSI d Replace the Control Unit of Replacement 2.2.5
(DCTL). which the CALM LED lights Replacing Control
01847103 DCTL DMA0 transfer The transferred data was Gather on except for c. Unit (REP 02-0390)
data compare error inconsistent with the expected
[OWN_CTL] parity generation data (data
part) in the DMA #0 transfer test
(DCTL).
01847104 DCTL DMA0 transfer The transferred data was Gather
[OWN_CTL] parity generation data (LA part)
in the DMA #0 transfer test of
(DCTL).
[OWN_CTL] parity generation data (LRC
part) in the DMA #0 transfer test
(DCTL).
[OWN_CTL] FILL data (data part) in the DMA
#0 transfer test of the data
[OWN_CTL] FILL data (LA part) in the DMA
#0 transfer test of the data

MSG 02-0160-01
Collect the error

Message
code
Trace Trace Dump
01847108 DCTL DMA0 transfer The transferred data was Gather cWhen W0100x CTL alarm Chapter 6. Warning
data compare error inconsistent with the expected is displayed following this Messages (MSG 06-
[OWN_CTL] FILL data (LRC part) in the DMA message, take recovery 0000)
#0 transfer test of the data actions according to the
transfer control LSI (DCTL). message.
01847109 DCTL DMA0 transfer The transferred data was Gather dReplace the Control Unit of Replacement 2.2.5
data compare error inconsistent with the expected which the CALM LED lights Replacing Control
[OWN_CTL] LA replacement data (data part) on except for c. Unit (REP 02-0390)
(DCTL).
0184710A DCTL DMA0 transfer The transferred data was Gather
[OWN_CTL] LA replacement data (LA part) in
the DMA #0 transfer test of the
(DCTL).
0184710B DCTL DMA0 transfer The transferred data was Gather
[OWN_CTL] LA replacement data (LRC part)
(DCTL).
01848101 DCTL DP#00 transfer A transfer failed in the D_Port Gather
error [OWN_CTL] #00 transfer test of the data
01848102 DCTL DP#00 transfer A time-out of transfer occurred Gather
time out error in the D_Port #00 transfer test of
[OWN_CTL] the data transfer control LSI
(DCTL).
01848103 DCTL DP#00 transfer The transferred data was Gather
data compare error inconsistent with the test data
[OWN_CTL] (data part) of the sender in the
D_Port #00 transfer test of the
(DCTL).
[OWN_CTL] (check code part) of the sender
in the D_Port #00 transfer test of
(DCTL).

MSG 02-0170-01
Collect the error

Message
code
Trace Trace Dump
01848201 DCTL DP#00 transfer A transfer failed in the D_Port Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] #00 transfer test of the data is displayed following this Messages (MSG 06-
transfer control LSI (DCTL). message, take recovery 0000)
01848202 DCTL DP#00 transfer A time-out of transfer occurred Gather actions according to the
time out error in the D_Port #00 transfer test of message.
[OWN_CTL] the data transfer control LSI d Replace the Control Unit of Replacement 2.2.5
01848203 DCTL DP#00 transfer The transferred data was Gather on except for c. Unit (REP 02-0390)
[OWN_CTL] LA replacement data (data part)
(DCTL).
[OWN_CTL] LA replacement data (check
code part) in the D_Port #00
transfer test of the data transfer
control LSI (DCTL).
(DCTL).
D_Port #01 transfer test of the
(DCTL).
(DCTL).
(DCTL).

MSG 02-0180-01
Collect the error

Message
code
Trace Trace Dump
01848703 DCTL DP#01 transfer The transferred data was Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] LA replacement data (data part) message, take recovery 0000)
in the D_Port #01 transfer test of actions according to the
the data transfer control LSI message.
(DCTL). d Replace the Control Unit of Replacement 2.2.5
01848704 DCTL DP#01 transfer The transferred data was Gather which the CALM LED lights Replacing Control
data compare error inconsistent with the expected on except for c. Unit (REP 02-0390)
[OWN_CTL] LA replacement data (check
code part) in the D_Port #01
transfer test of the data transfer
control LSI (DCTL).
0184A101 DCTL HP#00 transfer A transfer failed in the H_Port Gather c When W0100x CTL alarm Replacement 2.2.7
error [OWN_CTL] #00 transfer test of the data is displayed following this Replacing Interface
transfer control LSI (DCTL). message, replace the Board (REP 02-
0184A102 DCTL HP#00 transfer A time-out of transfer occurred Gather Interface Board #0 of the 0660)
time out error in the H_Port #00 transfer test of Control Unit pointed out in
[OWN_CTL] the data transfer control LSI the message.
(DCTL). d In a case other than c, Replacement 2.2.5
0184A103 DCTL HP#00 transfer The transferred data was Gather replace the Interface Board Replacing Control
data compare error inconsistent with the test data #0 of the Control Unit Unit (REP 02-0390)
[OWN_CTL] (data part) of the sender in the whose CALM LED is on.
H_Port #00 transfer test of the e If not recovered, replace
data transfer control LSI not the inserted Control
(DCTL). Unit but the other Control
0184A104 DCTL HP#00 transfer The transferred data was Gather Unit. (The replacement
data compare error inconsistent with the test data cannot be done when the
[OWN_CTL] (check code part) of the sender subsystem power is on.)
in the H_Port #00 transfer test of
(DCTL).
0184A201 DCTL HP#00 transfer A transfer failed in the H_Port Gather
0184A202 DCTL HP#00 transfer A time-out of transfer occurred Gather
time out error in the H_Port #00 transfer test of
(DCTL).
0184A203 DCTL HP#00 transfer The transferred data was Gather
[OWN_CTL] primary data (data part) in the
H_Port #00 transfer test of the
(DCTL).
[OWN_CTL] primary data (check code part)
in the H_Port #00 transfer test of
(DCTL).

MSG 02-0190-01
Collect the error

Message
code
Trace Trace Dump
0184A205 DCTL HP#00 transfer The transferred data was Gather cWhen W0100x CTL alarm Replacement 2.2.7
data compare error inconsistent with the expected is displayed following this Replacing Interface
[OWN_CTL] secondary data (data part) in the message, replace the Board (REP 02-
H_Port #00 transfer test of the Interface Board #0 of the 0660)
data transfer control LSI Control Unit pointed out in
(DCTL). the message.
0184A206 DCTL HP#00 transfer The transferred data was Gather dIn a case other than c, Replacement 2.2.5
data compare error inconsistent with the expected replace the Interface Board Replacing Control
[OWN_CTL] secondary data (check code #0 of the Control Unit Unit (REP 02-0390)
part) in the H_Port #00 transfer whose CALM LED is on.
test of the data transfer control e If not recovered, replace
LSI (DCTL). not the inserted Control
0184A601 DCTL HP#01 transfer A transfer failed in the H_Port Gather Unit but the other Control
error [OWN_CTL] #01 transfer test of the data Unit. (The replacement
transfer control LSI (DCTL). cannot be done when the
0184A602 DCTL HP#01 transfer A time-out of transfer occurred Gather subsystem power is on.)
(DCTL).
(DCTL).
in the H_Port #01transfer test of
(DCTL).
0184A701 DCTL HP#01 transfer A transfer failed in the H_Port Gather
0184A702 DCTL HP#01 transfer A time-out of transfer occurred Gather
(DCTL).
(DCTL).

MSG 02-0200-01
Collect the error

Message
code
Trace Trace Dump
0184A704 DCTL HP#01 transfer The transferred data was Gather cWhen W0100x CTL alarm Replacement 2.2.7
data compare error inconsistent with the expected is displayed following this Replacing Interface
[OWN_CTL] primary data (check code part) message, replace the Board (REP 02-
in the H_Port #01 transfer test of Interface Board #0 of the 0660)
the data transfer control LSI Control Unit pointed out in
(DCTL). the message.
0184A705 DCTL HP#01 transfer The transferred data was Gather dIn a case other than c, Replacement 2.2.5
data compare error inconsistent with the expected replace the Interface Board Replacing Control
[OWN_CTL] secondary data (data part) in the #0 of the Control Unit Unit (REP 02-0390)
H_Port #01 transfer test of the whose CALM LED is on.
data transfer control LSI e If not recovered, replace
(DCTL). not the inserted Control
0184A706 DCTL HP#01 transfer The transferred data was Gather Unit but the other Control
data compare error inconsistent with the expected Unit. (The replacement
[OWN_CTL] secondary data (check code cannot be done when the
part) in the H_Port #01 transfer subsystem power is on.)
LSI (DCTL).
0184BB01 DCTL HP#S1 transfer A transfer failed in the H_Port Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] #S1 transfer test of the data is displayed following this Messages (MSG 06-
transfer control LSI (DCTL). message, take recovery 0000)
0184BB02 DCTL HP#S1 transfer A time-out of transfer occurred Gather actions according to the
time out error in the H_Port #S1 transfer test message.
[OWN_CTL] of the data transfer control LSI d Replace the Control Unit of Replacement 2.2.5
0184BB03 DCTL HP#S1 transfer The transferred data was Gather on except for c. Unit (REP 02-0390)
H_Port #S1 transfer test of the
(DCTL).
0184BB04 DCTL HP#S1 transfer The transferred data was Gather
in the H_Port #S1transfer test of
(DCTL).
0184BC01 DCTL HP#S1 transfer A transfer failed in the H_Port Gather
error [OWN_CTL] #S1 transfer test of the data
0184BC02 DCTL HP#S1 transfer A time-out of transfer occurred Gather
time out error in the H_Port #S1 transfer test
[OWN_CTL] of the data transfer control LSI
(DCTL).
0184BC03 DCTL HP#S1 transfer The transferred data was Gather
(DCTL).

MSG 02-0210-01
Collect the error

Message
code
Trace Trace Dump
0184BC04 DCTL HP#S1 transfer The transferred data was Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] primary data (check code part) message, take recovery 0000)
in the H_Port #S1 transfer test actions according to the
of the data transfer control LSI message.
(DCTL). d Replace the Control Unit of Replacement 2.2.5
0184BC05 DCTL HP#S1 transfer The transferred data was Gather which the CALM LED lights Replacing Control
data compare error inconsistent with the expected on except for c. Unit (REP 02-0390)
[OWN_CTL] secondary data (data part) in the
(DCTL).
0184BC06 DCTL HP#S1 transfer The transferred data was Gather
[OWN_CTL] secondary data (check code
part) in the H_Port #S1 transfer
LSI (DCTL).
0184D101 DCTL MP access The ECC_WR_PTY ERR did Gather
error force NG not occur in the MP force test of
(DCTL).
0184D102 DCTL MP access The ECC_GEN_ERR did not Gather
error force NG occur in the MP force test of the
[OWN_CTL] data transfer control LSI
(DCTL).
0184D103 DCTL MP access The ECC_UNCORE did not Gather
(DCTL).
0184D104 DCTL MP access The ECC_COR_ERR did not Gather
(DCTL).
0184D105 DCTL MP access The DBF_BYTE_WR_ERR did Gather
(DCTL).
0184D106 DCTL MP access The ECC_CORRECT did not Gather
(DCTL).
0184D107 DCTL MP access The RCTL_ERR did not occur in Gather
error force NG the MP force test of the data
[OWN_CTL] transfer control LSI (DCTL).
0184D108 DCTL MP access The RCLK_ERR did not occur in Gather
error force NG the MP force test of the data

MSG 02-0220-01
Collect the error

Message
code
Trace Trace Dump
0184D109 DCTL MP access The DRD_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the MP force test of the is displayed following this Messages (MSG 06-
[OWN_CTL] data transfer control LSI message, take recovery 0000)
0184D10A DCTL MP access The CADROV_MP did not occur Gather message.
error force NG in the MP force test of the data d Replace the Control Unit of Replacement 2.2.5
[OWN_CTL] transfer control LSI (DCTL). which the CALM LED lights Replacing Control
0184D10B DCTL MP access The ADR_PTY_ERR did not Gather on except for c. Unit (REP 02-0390)
(DCTL).
0184D10C DCTL MP access The WLEN_PTY_ERR did not Gather
(DCTL).
0184D10D DCTL MP access The DUMY_AREA_WR_ERR Gather
error force NG did not occur in the MP force
[OWN_CTL] test of the data transfer control
LSI (DCTL).
0184D10E DCTL MP access The DBF_BYTE_WR (blk) did Gather
(DCTL).
0184D10F DCTL MP access The PBF_SEL_CNT_PERR did Gather
(DCTL).
0184D110 DCTL MP access The CBF_SEL_CNT_PERR did Gather
(DCTL).
0184D111 DCTL MP access The REFCNT_PTY_PERR did Gather
(DCTL).
0184D601 DCTL MDMA access The DRD_PTY_ERR did not Gather
error force NG occur in the MDMA force test of
(DCTL).
0184D602 DCTL MDMA access The ECC_WPTY_ERR did not Gather
(DCTL).
0184D603 DCTL MDMA access The ECC_GEN_ERR did not Gather
(DCTL).

MSG 02-0230-01
Collect the error

Message
code
Trace Trace Dump
0184D604 DCTL MDMA access The ECC_UNCORE did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the MDMA force test of is displayed following this Messages (MSG 06-
[OWN_CTL] the data transfer control LSI message, take recovery 0000)
0184D605 DCTL MDMA access The ECC_COR_ERR did not Gather message.
error force NG occur in the MDMA force test of dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] the data transfer control LSI which the CALM LED lights Replacing Control
0184D606 DCTL MDMA access The RCTL_ERR did not occur in Gather
error force NG the MDMA force test of the data
0184D607 DCTL MDMA access The RCLK_ERR did not occur in Gather
0184D608 DCTL MDMA access The ADR_PTY_ERR did not Gather
(DCTL).
0184D609 DCTL MDMA access The WLEN_PTY_ERR did not Gather
(DCTL).
0184D60A DCTL MDMA access The DBF_BYTE_WR_ERR did Gather
error force NG not occur in the MDMA force
LSI (DCTL).
0184D60B DCTL MDMA access The BWACNT_PTY_ERR did Gather
LSI (DCTL).
0184D60C DCTL MDMA access The BRACNT_PTY_ERR did Gather
LSI (DCTL).
0184D60D DCTL MDMA access The WADRCNT_PTY_ERR did Gather
LSI (DCTL).
0184D60E DCTL MDMA access The RADRCNT_PTY_ERR did Gather
LSI (DCTL).
0184D60F DCTL MDMA access The CADROV did not occur in Gather

MSG 02-0240-01
Collect the error

Message
code
Trace Trace Dump
0184D610 DCTL MDMA access The DUMY_AREA_WR_ERR Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG did not occur in the MDMA force is displayed following this Messages (MSG 06-
[OWN_CTL] test of the data transfer control message, take recovery 0000)
0184D611 DCTL MDMA access The DBF_BYTE_WR (blk) did Gather message.
error force NG not occur in the MDMA force dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] test of the data transfer control which the CALM LED lights Replacing Control
LSI (DCTL). on except for c. Unit (REP 02-0390)
0184D612 DCTL MDMA access The ECC_CORECT did not Gather
(DCTL).
0184D701 DCTL DMA0 access The RCTL_ERR did not occur in Gather
error force NG the DMA #0 force test of the
(DCTL).
0184D702 DCTL DMA0 access The RCLK_ERR did not occur in Gather
(DCTL).
0184D703 DCTL DMA0 access The CADROV did not occur in Gather
(DCTL).
0184D704 DCTL DMA0 access The BUF_WDT_PTY_ERR did Gather
error force NG not occur in the DMA #0 force
LSI (DCTL).
0184D705 DCTL DMA0 access The LRC_GEN_ERR did not Gather
error force NG occur in the DMA #0 force test
(DCTL).
0184D706 DCTL DMA0 access The LIST_DT_ERR did not Gather
(DCTL).
0184D707 DCTL DMA0 access The LUN_ERR did not occur in Gather
(DCTL).
0184D708 DCTL DMA0 access The LBA_ERR did not occur in Gather
(DCTL).
0184D709 DCTL DMA0 access The LRC_ERR did not occur in Gather
(DCTL).

MSG 02-0250-01
Collect the error

Message
code
Trace Trace Dump
0184D70A DCTL DMA0 access The ECC_WR_PTY_ERR did Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG not occur in the DMA #0 force is displayed following this Messages (MSG 06-
0184D70B DCTL DMA0 access The ECC_GEN_ERR did not Gather message.
error force NG occur in the DMA #0 force test dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] of the data transfer control LSI which the CALM LED lights Replacing Control
0184D70C DCTL DMA0 access The ECC_UNCORE did not Gather
(DCTL).
0184D70D DCTL DMA0 access The ECC_COR_ERR did not Gather
(DCTL).
0184D70E DCTL DMA0 access The VERIFY_ERR did not occur Gather
error force NG in the DMA #0 force test of the
(DCTL).
0184D70F DCTL DMA0 access The BLKCNT_PTY_ERR did not Gather
(DCTL).
0184D710 DCTL DMA0 access The VERIFYQ_ERR did not Gather
(DCTL).
0184D711 DCTL DMA0 access The ADR_CNT_PTY_ERR did Gather
LSI (DCTL).
0184D712 DCTL DMA0 access The LBA_CNT_PTY_ERR did Gather
LSI (DCTL).
0184D713 DCTL DMA0 access The CNT_CNT_PTY_ERR did Gather
LSI (DCTL).
0184D714 DCTL DMA0 access The ADR_PTY_ERR did not Gather
(DCTL).
0184D715 DCTL DMA0 access The WLEN_PTY_ERR did not Gather
(DCTL).

MSG 02-0260-01
Collect the error

Message
code
Trace Trace Dump
0184D716 DCTL DMA0 access The ECC_CORRECT did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the DMA #0 force test is displayed following this Messages (MSG 06-
[OWN_CTL] of the data transfer control LSI message, take recovery 0000)
0184D720 DCTL DMA0 transfer The DMA #0 transfer failed in Gather message.
error [OWN_CTL] the DMA #0 force test of the dReplace the Control Unit of Replacement 2.2.5
data transfer control LSI which the CALM LED lights Replacing Control
0184D801 DCTL DP#00 access The RCTL_ERR did not occur in Gather
error force NG the D_Port #00 force test of the
(DCTL).
0184D802 DCTL DP#00 access The RCLK_ERR did not occur in Gather
(DCTL).
0184D803 DCTL DP#00 access The CADROV did not occur in Gather
(DCTL).
0184D804 DCTL DP#00 access The BLEN0_ERR did not occur Gather
error force NG in the D_Port #00 force test of
(DCTL).
0184D805 DCTL DP#00 access The WORDCNT_ERR did not Gather
error force NG occur in the D_Port #00 force
LSI (DCTL).
0184D806 DCTL DP#00 access The DBF_BYTE_WR (Block) did Gather
error force NG not occur in the D_Port #00
[OWN_CTL] force test of the data transfer
control LSI (DCTL).
0184D807 DCTL DP#00 access The 512_ADR_ERR did not Gather
LSI (DCTL).
0184D808 DCTL DP#00 access The LRC_GEN_ERR did not Gather
LSI (DCTL).
0184D809 DCTL DP#00 access The PCI_ADR_ERR did not Gather
LSI (DCTL).

MSG 02-0270-01
Collect the error

Message
code
Trace Trace Dump
0184D80B DCTL DP#00 access The DRD_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the D_Port #00 force is displayed following this Messages (MSG 06-
0184D80C DCTL DP#00 access The LUN_ERR did not occur in Gather message.
error force NG the D_Port #00 force test of the dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] data transfer control LSI which the CALM LED lights Replacing Control
0184D80D DCTL DP#00 access The LBA_ERR did not occur in Gather
(DCTL).
0184D80E DCTL DP#00 access The LRC_ERR did not occur in Gather
(DCTL).
0184D80F DCTL DP#00 access The ECC_WR_PTY_ERR did Gather
control LSI (DCTL).
0184D810 DCTL DP#00 access The ECC_GEN_ERR did not Gather
LSI (DCTL).
0184D811 DCTL DP#00 access The ECC_UNCORRECT did not Gather
LSI (DCTL).
0184D812 DCTL DP#00 access The ECC_COR_ERR did not Gather
LSI (DCTL).
0184D813 DCTL DP#00 access The WR_SEQ_ERR did not Gather
LSI (DCTL).
0184D814 DCTL DP#00 access The BLKCNT_PTY_ERR did not Gather
LSI (DCTL).
0184D815 DCTL DP#00 access The WORDCNT_PTY_ERR did Gather
control LSI (DCTL).
0184D816 DCTL DP#00 access The ADRCNT_PTY_ERR did Gather
control LSI (DCTL).

MSG 02-0280-01
Collect the error

Message
code
Trace Trace Dump
0184D817 DCTL DP#00 access The LBACNT_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
0184D818 DCTL DP#00 access The CTLCNT_PTY_ERR did not Gather message.
error force NG occur in the D_Port #00 force dReplace the Control Unit of Replacement 2.2.5
0184D819 DCTL DP#00 access The ADR_PTY_ERR did not Gather
LSI (DCTL).
0184D81A DCTL DP#00 access The WLEN_PTY_ERR did not Gather
LSI (DCTL).
0184D81B DCTL DP#00 access The ECC_CORRECT did not Gather
LSI (DCTL).
0184D901 DCTL DP#01 access The RCTL_ERR did not occur in Gather
(DCTL).
0184D902 DCTL DP#01 access The RCLK_ERR did not occur in Gather
(DCTL).
0184D903 DCTL DP#01 access The CADROV did not occur in Gather
(DCTL).
0184D904 DCTL DP#01 access The BLEN0_ERR did not occur Gather
error force NG in the D_Port #01 force test of
(DCTL).
0184D905 DCTL DP#01 access The WORDCNT_ERR did not Gather
LSI (DCTL).
0184D906 DCTL DP#01 access The DBF_BYTE_WR (Block) did Gather
control LSI (DCTL).
0184D907 DCTL DP#01 access The 512_ADR_ERR did not Gather
LSI (DCTL).

MSG 02-0290-01
Collect the error

Message
code
Trace Trace Dump
0184D908 DCTL DP#01 access The LRC_GEN_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
0184D909 DCTL DP#01 access The PCI_ADR_ERR did not Gather message.
error force NG occur in the D_Port #01 force dReplace the Control Unit of Replacement 2.2.5
0184D90B DCTL DP#01 access The DRD_PTY_ERR did not Gather
LSI (DCTL).
0184D90C DCTL DP#01 access The LUN_ERR did not occur in Gather
(DCTL).
0184D90D DCTL DP#01 access The LBA_ERR did not occur in Gather
(DCTL).
0184D90E DCTL DP#01 access The LRC_ERR did not occur in Gather
(DCTL).
0184D90F DCTL DP#01 access The ECC_WR_PTY_ERR did Gather
control LSI (DCTL).
0184D910 DCTL DP#01 access The ECC_GEN_ERR did not Gather
LSI (DCTL).
0184D911 DCTL DP#01 access The ECC_UNCORRECT did not Gather
LSI (DCTL).
0184D912 DCTL DP#01 access The ECC_COR_ERR did not Gather
LSI (DCTL).
0184D913 DCTL DP#01 access The WR_SEQ_ERR did not Gather
LSI (DCTL).
0184D914 DCTL DP#01 access The BLKCNT_PTY_ERR did not Gather
LSI (DCTL).

MSG 02-0300-01
Collect the error

Message
code
Trace Trace Dump
0184D915 DCTL DP#01 access The WORDCNT_PTY_ERR did Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG not occur in the D_Port #01 is displayed following this Messages (MSG 06-
[OWN_CTL] force test of the data transfer message, take recovery 0000)
0184D916 DCTL DP#01 access The ADRCNT_PTY_ERR did Gather message.
error force NG not occur in the D_Port #01 dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] force test of the data transfer which the CALM LED lights Replacing Control
control LSI (DCTL). on except for c. Unit (REP 02-0390)
0184D917 DCTL DP#01 access The LBACNT_PTY_ERR did not Gather
LSI (DCTL).
0184D918 DCTL DP#01 access The CTLCNT_PTY_ERR did not Gather
LSI (DCTL).
0184D919 DCTL DP#01 access The ADR_PTY_ERR did not Gather
LSI (DCTL).
0184D91A DCTL DP#01 access The WLEN_PTY_ERR did not Gather
LSI (DCTL).
0184D91B DCTL DP#01 access The ECC_CORRECT did not Gather
LSI (DCTL).
0184DC01 DCTL primary PCI The D_PERR did not occur in Gather
error force NG the primary PCI bridge (on the
[OWN_CTL] data transfer control LSI (DCTL)
side) force test of the data
0184DC02 DCTL primary PCI The S_T_ABORT did not occur Gather
error force NG in the primary PCI bridge (on the
[OWN_CTL] data transfer control LSI (DCTL)
0184DC03 DCTL primary PCI The DSCON_CNT_PTYERR Gather
error force NG did not occur in the primary PCI
[OWN_CTL] bridge (on the data transfer
control LSI (DCTL) side) force
LSI (DCTL).
0184DC04 DCTL primary PCI The D_PERR did not occur in Gather
error force NG the Primary PCI Bridge (Bridge
[OWN_CTL] side) force test of the data

MSG 02-0310-01
Collect the error

Message
code
Trace Trace Dump
0184DC05 DCTL primary PCI The R_SERR did not occur in Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG the Primary PCI Bridge (Bridge is displayed following this Messages (MSG 06-
[OWN_CTL] side) force test of the data message, take recovery 0000)
transfer control LSI (DCTL). actions according to the
0184DC06 DCTL primary PCI The R_M_ABORT did not occur Gather message.
error force NG in the Primary PCI Bridge dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] (Bridge side) force test of the which the CALM LED lights Replacing Control
(DCTL).
0184DC07 DCTL primary PCI The R_T_ABORT did not occur Gather
error force NG in the Primary PCI Bridge
[OWN_CTL] (Bridge side) force test of the
(DCTL).
0184DC08 DCTL primary PCI The S_T_ABORT did not occur Gather
error force NG in the Primary PCI Bridge
(DCTL).
0184DC09 DCTL primary PCI The DPERR_D did not occur in Gather
error force NG the Primary PCI Bridge (Bridge
0184DC0A DCTL primary PCI The ADR_PTY_ERR did not Gather
error force NG occur in the Primary PCI Bridge
(DCTL).
0184DC0B DCTL primary PCI The ADR_PTY_ERR did not Gather
(DCTL).
0184DC0C DCTL primary PCI The DRD_PTY_ERR did not Gather
(DCTL).
0184DC0D DCTL primary PCI The CMD_PTY_ERR did not Gather
(DCTL).
0184DC0E DCTL primary PCI The CNT_PTY_ERR did not Gather
(DCTL).

MSG 02-0320-01
Collect the error

Message
code
Trace Trace Dump
0184DC0F DCTL primary PCI The TIME_OUT did not occur in Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG the Primary PCI Bridge (Bridge is displayed following this Messages (MSG 06-
[OWN_CTL] side) force test of the data message, take recovery 0000)
0184DC10 DCTL primary PCI The SPC_TIME_OUT did not Gather message.
error force NG occur in the Primary PCI Bridge dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] (Bridge side) force test of the which the CALM LED lights Replacing Control
(DCTL).
0184DC11 DCTL primary PCI The SPC_ERR_MSG did not Gather
(DCTL).
0184DD01 DCTL drive PCI0 The D_PERR did not occur in Gather
error force NG the Drive PCI Bridge #0 (Cache
[OWN_CTL] access side) force test of the
(DCTL).
0184DD02 DCTL drive PCI0 The S_T_ABORT did not occur Gather
error force NG in the Drive PCI Bridge #0
[OWN_CTL] (Cache access side) force test
(DCTL).
0184DD03 DCTL drive PCI0 The DSCON_CNT_PTYERR Gather
error force NG did not occur in the Drive PCI
[OWN_CTL] Bridge #0 (Cache access side)
control LSI (DCTL).
0184DD04 DCTL drive PCI0 The D_PERR did not occur in Gather
error force NG the Drive PCI Bridge #0 (Bridge
0184DD05 DCTL drive PCI0 The R_SERR did not occur in Gather
0184DD06 DCTL drive PCI0 The R_M_ABORT did not occur Gather
(DCTL).
0184DD07 DCTL drive PCI0 The R_T_ABORT did not occur Gather
(DCTL).

MSG 02-0330-01
Collect the error

Message
code
Trace Trace Dump
0184DD08 DCTL drive PCI0 The S_T_ABORT did not occur Gather cWhen W0100x CTL alarm Chapter 6. Warning
error force NG in the Drive PCI Bridge #0 is displayed following this Messages (MSG 06-
[OWN_CTL] (Bridge side) force test of the message, take recovery 0000)
(DCTL). message.
0184DD09 DCTL drive PCI0 The DPERR_D did not occur in Gather dReplace the Control Unit of Replacement 2.2.5
error force NG the Drive PCI Bridge #0 (Bridge which the CALM LED lights Replacing Control
[OWN_CTL] side) force test of the data on except for c. Unit (REP 02-0390)
0184DD0A DCTL drive PCI0 The ADR_PTY_ERR did not Gather
error force NG occur in the Drive PCI Bridge #0
(DCTL).
0184DD0B DCTL drive PCI0 The DRD_PTY_ERR did not Gather
(DCTL).
0184DD0C DCTL drive PCI0 The CMD_PTY_ERR did not Gather
(DCTL).
0184DD0D DCTL drive PCI0 The CNT_PTY_ERR did not Gather
(DCTL).
0184DD0E DCTL drive PCI0 The TIME_OUT did not occur in Gather
0184DD0F DCTL drive PCI0 The SPC_TIME_OUT did not Gather
(DCTL).
0184DD10 DCTL drive PCI0 The SPC_ERR_MSG did not Gather
(DCTL).
0184DD11 DCTL drive PCI0 The UNEXPECT_SPC did not Gather
(DCTL).

MSG 02-0340-01
Collect the error

Message
code
Trace Trace Dump
0184E101 DCTL HP#00 access The RCTL_ERR did not occur in Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG the H_Port #00 force test of the is displayed following this Messages (MSG 06-
0184E102 DCTL HP#00 access The RCLK_ERR did not occur in Gather message.
error force NG the H_Port #00 force test of the dReplace the Control Unit of Replacement 2.2.5
0184E103 DCTL HP#00 access The CADROV did not occur in Gather
error force NG the H_Port #00 force test of the
(DCTL).
0184E104 DCTL HP#00 access The BLEN0_ERR did not occur Gather
error force NG in the H_Port #00 force test of
(DCTL).
0184E105 DCTL HP#00 access The WORDCNT_ERR did not Gather
error force NG occur in the H_Port #00 force
LSI (DCTL).
0184E106 DCTL HP#00 access The DBF_BYTE_WR (Block) did Gather
error force NG not occur in the H_Port #00
control LSI (DCTL).
0184E107 DCTL HP#00 access The 512_ADR_ERR did not Gather
LSI (DCTL).
0184E108 DCTL HP#00 access The LRC_GEN_ERR did not Gather
LSI (DCTL).
0184E109 DCTL HP#00 access The PCI_ADR_ERR did not Gather
LSI (DCTL).
0184E10B DCTL HP#00 access The DRD_PTY_ERR did not Gather
LSI (DCTL).
0184E10C DCTL HP#00 access The LUN_ERR did not occur in Gather
(DCTL).
0184E10D DCTL HP#00 access The LBA_ERR did not occur in Gather
(DCTL).

MSG 02-0350-01
Collect the error

Message
code
Trace Trace Dump
0184E10E DCTL HP#00 access The LRC_ERR did not occur in Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG the H_Port #00 force test of the is displayed following this Messages (MSG 06-
0184E10F DCTL HP#00 access The ECC_WR_PTY_ERR did Gather message.
error force NG not occur in the H_Port #00 dReplace the Control Unit of Replacement 2.2.5
0184E110 DCTL HP#00 access The ECC_GEN_ERR did not Gather
LSI (DCTL).
0184E111 DCTL HP#00 access The ECC_UNCORRECT did not Gather
LSI (DCTL).
0184E112 DCTL HP#00 access The ECC_COR_ERR did not Gather
LSI (DCTL).
0184E114 DCTL HP#00 access The BLKCNT_PTY_ERR did not Gather
LSI (DCTL).
0184E115 DCTL HP#00 access The WORDCNT_PTY_ERR did Gather
control LSI (DCTL).
0184E116 DCTL HP#00 access The ADRCNT_PTY_ERR did Gather
control LSI (DCTL).
0184E117 DCTL HP#00 access The LBACNT_PTY_ERR did not Gather
LSI (DCTL).
0184E118 DCTL HP#00 access The CTLCNT_PTY_ERR did not Gather
LSI (DCTL).
0184E119 DCTL HP#00 access The ADR_PTY_ERR did not Gather
LSI (DCTL).

MSG 02-0360-01
Collect the error

Message
code
Trace Trace Dump
0184E11A DCTL HP#00 access The WLEN_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the H_Port #00 force is displayed following this Messages (MSG 06-
0184E11B DCTL HP#00 access The ECC_CORRECT did not Gather message.
error force NG occur in the H_Port #00 force dReplace the Control Unit of Replacement 2.2.5
0184E11C DCTL HP#00 access The EDC_LUN_ERR did not Gather
LSI (DCTL).
0184E11D DCTL HP#00 access The EDC_LBA_ERR did not Gather
LSI (DCTL).
0184E11E DCTL HP#00 access The EDC_CRC_ERR did not Gather
LSI (DCTL).
0184E11F DCTL HP#00 access The CRC_GEN_ERR did not Gather
LSI (DCTL).
0184E201 DCTL HP#01 access The RCTL_ERR did not occur in Gather
(DCTL).
0184E202 DCTL HP#01 access The RCLK_ERR did not occur in Gather
(DCTL).
0184E203 DCTL HP#01 access The CADROV did not occur in Gather
(DCTL).
0184E204 DCTL HP#01 access The BLEN0_ERR did not occur Gather
error force NG in the H_Port #01 force test of
(DCTL).
0184E205 DCTL HP#01 access The WORDCNT_ERR did not Gather
LSI (DCTL).
0184E206 DCTL HP#01 access The DBF_BYTE_WR (Block) did Gather
control LSI (DCTL).

MSG 02-0370-01
Collect the error

Message
code
Trace Trace Dump
0184E207 DCTL HP#01 access The 512_ADR_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the H_Port #01 force is displayed following this Messages (MSG 06-
0184E208 DCTL HP#01 access The LRC_GEN_ERR did not Gather message.
error force NG occur in the H_Port #01 force dReplace the Control Unit of Replacement 2.2.5
0184E209 DCTL HP#01 access The PCI_ADR_ERR did not Gather
LSI (DCTL).
0184E20B DCTL HP#01 access The DRD_PTY_ERR did not Gather
LSI (DCTL).
0184E20C DCTL HP#01 access The LUN_ERR did not occur in Gather
(DCTL).
0184E20D DCTL HP#01 access The LBA_ERR did not occur in Gather
(DCTL).
0184E20E DCTL HP#01 access The LRC_ERR did not occur in Gather
(DCTL).
0184E20F DCTL HP#01 access The ECC_WR_PTY_ERR did Gather
control LSI (DCTL).
0184E210 DCTL HP#01 access The ECC_GEN_ERR did not Gather
LSI (DCTL).
0184E211 DCTL HP#01 access The ECC_UNCORRECT did not Gather
LSI (DCTL).
0184E212 DCTL HP#01 access The ECC_COR_ERR did not Gather
LSI (DCTL).
0184E214 DCTL HP#01 access The BLKCNT_PTY_ERR did not Gather
LSI (DCTL).

MSG 02-0380-01
Collect the error

Message
code
Trace Trace Dump
0184E215 DCTL HP#01 access The WORDCNT_PTY_ERR did Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG not occur in the H_Port #01 is displayed following this Messages (MSG 06-
[OWN_CTL] force test of the data transfer message, take recovery 0000)
0184E216 DCTL HP#01 access The ADRCNT_PTY_ERR did Gather message.
error force NG not occur in the H_Port #01 dReplace the Control Unit of Replacement 2.2.5
0184E217 DCTL HP#01 access The LBACNT_PTY_ERR did not Gather
LSI (DCTL).
0184E218 DCTL HP#01 access The CTLCNT_PTY_ERR did not Gather
LSI (DCTL).
0184E219 DCTL HP#01 access The ADR_PTY_ERR did not Gather
LSI (DCTL).
0184E21A DCTL HP#01 access The WLEN_PTY_ERR did not Gather
LSI (DCTL).
0184E21B DCTL HP#01 access The ECC_CORRECT did not Gather
LSI (DCTL).
0184E21C DCTL HP#01 access The EDC_LUN_ERR did not Gather
LSI (DCTL).
0184E21D DCTL HP#01 access The EDC_LBA_ERR did not Gather
LSI (DCTL).
0184E21E DCTL HP#01 access The EDC_CRC_ERR did not Gather
LSI (DCTL).
0184E21F DCTL HP#01 access The CRC_GEN_ERR did not Gather
LSI (DCTL).

MSG 02-0390-01
Collect the error

Message
code
Trace Trace Dump
0184E501 DCTL HP#S1 access The RCTL_ERR did not occur in Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG the H_Port #S1 force test of the is displayed following this Messages (MSG 06-
0184E502 DCTL HP#S1 access The RCLK_ERR did not occur in Gather message.
error force NG the H_Port #S1 force test of the dReplace the Control Unit of Replacement 2.2.5
0184E503 DCTL HP#S1 access The CADROV did not occur in Gather
error force NG the H_Port #S1 force test of the
(DCTL).
0184E504 DCTL HP#S1 access The BLEN0_ERR did not occur Gather
error force NG in the H_Port #S1 force test of
(DCTL).
0184E505 DCTL HP#S1 access The WORDCNT_ERR did not Gather
error force NG occur in the H_Port #S1 force
LSI (DCTL).
0184E506 DCTL HP#S1 access The DBF_BYTE_WR (Block) did Gather
error force NG not occur in the H_Port #S1
control LSI (DCTL).
0184E507 DCTL HP#S1 access The 512_ADR_ERR did not Gather
LSI (DCTL).
0184E508 DCTL HP#S1 access The LRC_GEN_ERR did not Gather
LSI (DCTL).
0184E509 DCTL HP#S1 access The PCI_ADR_ERR did not Gather
LSI (DCTL).
0184E50B DCTL HP#S1 access The DRD_PTY_ERR did not Gather
LSI (DCTL).
0184E50C DCTL HP#S1 access The LUN_ERR did not occur in Gather
(DCTL).
0184E50D DCTL HP#S1 access The LBA_ERR did not occur in Gather
(DCTL).

MSG 02-0400-01
Collect the error

Message
code
Trace Trace Dump
0184E50E DCTL HP#S1 access The LRC_ERR did not occur in Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG the H_Port #S1 force test of the is displayed following this Messages (MSG 06-
0184E50F DCTL HP#S1 access The ECC_WR_PTY_ERR did Gather message.
error force NG not occur in the H_Port #S1 dReplace the Control Unit of Replacement 2.2.5
0184E510 DCTL HP#S1 access The ECC_GEN_ERR did not Gather
LSI (DCTL).
0184E511 DCTL HP#S1 access The ECC_UNCORRECT did not Gather
LSI (DCTL).
0184E512 DCTL HP#S1 access The ECC_COR_ERR did not Gather
LSI (DCTL).
0184E514 DCTL HP#S1 access The BLKCNT_PTY_ERR did not Gather
LSI (DCTL).
0184E515 DCTL HP#S1 access The WORDCNT_PTY_ERR did Gather
control LSI (DCTL).
0184E516 DCTL HP#S1 access The ADRCNT_PTY_ERR did Gather
control LSI (DCTL).
0184E517 DCTL HP#S1 access The LBACNT_PTY_ERR did not Gather
LSI (DCTL).
0184E518 DCTL HP#S1 access The CTLCNT_PTY_ERR did not Gather
LSI (DCTL).
0184E519 DCTL HP#S1 access The ADR_PTY_ERR did not Gather
LSI (DCTL).

MSG 02-0410-01
Collect the error

Message
code
Trace Trace Dump
0184E51A DCTL HP#S1 access The WLEN_PTY_ERR did not Gather c When W0100x CTL alarm Chapter 6. Warning
error force NG occur in the H_Port #S1 force is displayed following this Messages (MSG 06-
0184E51B DCTL HP#S1 access The ECC_CORRECT did not Gather message.
error force NG occur in the H_Port #S1 force dReplace the Control Unit of Replacement 2.2.5
0184E51C DCTL HP#S1 access The EDC_LUN_ERR did not Gather
LSI (DCTL).
0184E51D DCTL HP#S1 access The EDC_LBA_ERR did not Gather
LSI (DCTL).
0184E51E DCTL HP#S1 access The EDC_CRC_ERR did not Gather
LSI (DCTL).
0184E51F DCTL HP#S1 access The CRC_GEN_ERR did not Gather
LSI (DCTL).
0184E601 DCTL host PCI0 error The D_PERR did not occur in Gather
force NG [OWN_CTL] the Host PCI Bridge #0 (Cache
access side) force test of the
(DCTL).
0184E602 DCTL host PCI0 error The S_T_ABORT did not occur Gather
force NG [OWN_CTL] in the Host PCI Bridge #0
(Cache access side) force test
(DCTL).
0184E603 DCTL host PCI0 error The DSCON_CNT_PTYERR Gather
force NG [OWN_CTL] did not occur in the Host PCI
Bridge #0 (Cache access side)
control LSI (DCTL).
0184E604 DCTL host PCI0 error The D_PERR did not occur in Gather
force NG [OWN_CTL] the Host PCI Bridge #0 (Bridge
0184E605 DCTL host PCI0 error The R_SERR did not occur in Gather

MSG 02-0420-01
Collect the error

Message
code
Trace Trace Dump
0184E606 DCTL host PCI0 error The R_M_ABORT did not occur Gather cWhen W0100x CTL alarm Chapter 6. Warning
force NG [OWN_CTL] in the Host PCI Bridge #0 is displayed following this Messages (MSG 06-
(Bridge side) force test of the message, take recovery 0000)
(DCTL). message.
0184E607 DCTL host PCI0 error The R_T_ABORT did not occur Gather dReplace the Control Unit of Replacement 2.2.5
force NG [OWN_CTL] in the Host PCI Bridge #0 which the CALM LED lights Replacing Control
(Bridge side) force test of the on except for c. Unit (REP 02-0390)
(DCTL).
0184E608 DCTL host PCI0 error The S_T_ABORT did not occur Gather
force NG [OWN_CTL] in the Host PCI Bridge #0
(Bridge side) force test of the
(DCTL).
0184E609 DCTL host PCI0 error The DPERR_D did not occur in Gather
0184E60A DCTL host PCI0 error The ADR_PTY_ERR did not Gather
force NG [OWN_CTL] occur in the Host PCI Bridge #0
(DCTL).
0184E60B DCTL host PCI0 error The DRD_PTY_ERR did not Gather
(DCTL).
0184E60C DCTL host PCI0 error The CMD_PTY_ERR did not Gather
(DCTL).
0184E60D DCTL host PCI0 error The CNT_PTY_ERR did not Gather
(DCTL).
0184E60E DCTL host PCI0 error The TIME_OUT did not occur in Gather
0184E60F DCTL host PCI0 error The SPC_TIME_OUT did not Gather
(DCTL).

MSG 02-0430-01
Collect the error

Message
code
Trace Trace Dump
0184E610 DCTL host PCI0 error The SPC_ERR_MSG did not Gather cWhen W0100x CTL alarm Chapter 6. Warning
force NG [OWN_CTL] occur in the Host PCI Bridge #0 is displayed following this Messages (MSG 06-
(Bridge side) force test of the message, take recovery 0000)
(DCTL). message.
0184E611 DCTL host PCI0 error The UNEXPECT_SPC did not Gather dReplace the Control Unit of Replacement 2.2.5
force NG [OWN_CTL] occur in the Host PCI Bridge #0 which the CALM LED lights Replacing Control
(Bridge side) force test of the on except for c. Unit (REP 02-0390)
(DCTL).
0184xxC1 DCTL DP#00- The ERQ consumer index of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
DFPC#0 transfer DFPC #0 was not upped in the is displayed following this Messages (MSG 06-
error [OWN_CTL] D_Port #00 transfer of the data message, take recovery 0000)
x : Diagnostic item code message.
DCTL DP#01- The ERQ consumer index of the Gather dReplace the Control Unit of Replacement 2.2.5
DFPC#1 transfer DFPC #1 was not upped in the which the CALM LED lights Replacing Control
error [OWN_CTL] D_Port #01 transfer of the data on except for c. Unit (REP 02-0390)
x : Diagnostic item code
DCTL HP#S1- The ERQ consumer index of the Gather
HFPC#S1 transfer HFPC #S1 was not upped in the
error [OWN_CTL] H_Port #S1 transfer of the data
DCTL HP#00- The ERQ consumer index of the Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#0 transfer HFPC #0 was not upped in the is displayed following this Replacing Interface
error [OWN_CTL] H_Port #00 transfer of the data message, replace the Board (REP 02-
transfer control LSI (DCTL). Interface Board #0 of the 0660)
x : Diagnostic item code Control Unit pointed out in
DCTL HP#01- The ERQ consumer index of the Gather the message.
HFPC#1 transfer HFPC #1 was not upped in the dIn a case other than c,
error [OWN_CTL] H_Port #01 transfer of the data replace the Interface Board
transfer control LSI (DCTL). #0 of the Control Unit
x : Diagnostic item code whose CALM LED is on.
Control Unit. Replacing Control
Unit (REP 02-0390)

MSG 02-0440-01
Collect the error

Message
code
Trace Trace Dump
0184xxC2 DCTL DP#00- The INT of the DFPC #0 did not Gather cWhen W0100x CTL alarm Chapter 6. Warning
DFPC#0 transfer occur in the D_Port #00 transfer is displayed following this Messages (MSG 06-
error [OWN_CTL] of the data transfer control LSI message, take recovery 0000)
DCTL DP#01- The INT of the DFPC #1 did not Gather dReplace the Control Unit of Replacement 2.2.5
DFPC#1 transfer occur in the D_Port #01 transfer which the CALM LED lights Replacing Control
error [OWN_CTL] of the data transfer control LSI on except for c. Unit (REP 02-0390)
(DCTL).
DCTL HP#S1- The INT of the HFPC #S1 did Gather
HFPC#S1 transfer not occur in the H_Port #S1
error [OWN_CTL] transfer of the data transfer
control LSI (DCTL).
DCTL HP#00- The INT of the HFPC #0 did not Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#0 transfer occur in the H_Port #00 transfer is displayed following this Replacing Interface
error [OWN_CTL] of the data transfer control LSI message, replace the Board (REP 02-
(DCTL). Interface Board #0 of the 0660)
DCTL HP#01- The INT of the HFPC #1 did not Gather the message.
HFPC#1 transfer occur in the H_Port #01 transfer dIn a case other than c,
error [OWN_CTL] of the data transfer control LSI replace the Interface Board
(DCTL). #0 of the Control Unit
Unit (REP 02-0390)

MSG 02-0450-01
Collect the error

Message
code
Trace Trace Dump
0184xxC3 DCTL DP#00- The IMQ producer index of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] D_Port #00 of the data transfer message, take recovery 0000)
DCTL DP#01- The IMQ producer index of the Gather dReplace the Control Unit of Replacement 2.2.5
error [OWN_CTL] D_Port #01 of the data transfer on except for c. Unit (REP 02-0390)
control LSI (DCTL).
DCTL HP#S1- The IMQ producer index of the Gather
error [OWN_CTL] H_Port #S1 of the data transfer
control LSI (DCTL).
DCTL HP#00- The IMQ producer index of the Gather c When W0100x CTL alarm Replacement 2.2.7
error [OWN_CTL] H_Port #00 of the data transfer message, replace the Board (REP 02-
control LSI (DCTL). Interface Board #0 of the 0660)
DCTL HP#01- The IMQ producer index of the Gather the message.
error [OWN_CTL] H_Port #01 of the data transfer replace the Interface Board
control LSI (DCTL). #0 of the Control Unit
Unit (REP 02-0390)

MSG 02-0460-01
Collect the error

Message
code
Trace Trace Dump
0184xxC4 DCTL DP#00- The expected completion Gather cWhen W0100x CTL alarm Chapter 6. Warning
DFPC#0 transfer message of the DFPC #0 was is displayed following this Messages (MSG 06-
error [OWN_CTL] not got in the D_Port #00 message, take recovery 0000)
transfer of the data transfer actions according to the
control LSI (DCTL). message.
x : Diagnostic item code d Replace the Control Unit of Replacement 2.2.5
DCTL DP#01- The expected completion Gather which the CALM LED lights Replacing Control
DFPC#1 transfer message of the DFPC #1 was on except for c. Unit (REP 02-0390)
error [OWN_CTL] not got in the D_Port #01
transfer of the data transfer
control LSI (DCTL).
DCTL HP#S1- The expected completion Gather
HFPC#S1 transfer message of the HFPC #S1 was
error [OWN_CTL] not got in the H_Port #S1
control LSI (DCTL).
DCTL HP#00- The expected completion Gather cWhen W0100x CTL alarm Replacement 2.2.7
HFPC#0 transfer message of the HFPC #0 was is displayed following this Replacing Interface
error [OWN_CTL] not got in the H_Port #00 message, replace the Board (REP 02-
transfer of the data transfer Interface Board #0 of the 0660)
control LSI (DCTL). Control Unit pointed out in
x : Diagnostic item code the message.
DCTL HP#01- The expected completion Gather dIn a case other than c,
HFPC#1 transfer message of the HFPC #1 was replace the Interface Board
error [OWN_CTL] not got in the H_Port #01 #0 of the Control Unit
transfer of the data transfer whose CALM LED is on.
control LSI (DCTL). eIf not recovered, replace Replacement 2.2.5
x : Diagnostic item code Control Unit. Replacing Control
Unit (REP 02-0390)

MSG 02-0470-01
Collect the error

Message
code
Trace Trace Dump
0184xxC5 DCTL DP#00- The FCP_CMND was not stored Gather cWhen W0100x CTL alarm Chapter 6. Warning
DFPC#0 transfer in the SFQ area of the DFPC #0 is displayed following this Messages (MSG 06-
error [OWN_CTL] in the D_Port #00 transfer of the message, take recovery 0000)
(DCTL). message.
DCTL DP#01- The FCP_CMND was not stored Gather which the CALM LED lights Replacing Control
DFPC#1 transfer in the SFQ area of the DFPC #1 on except for c. Unit (REP 02-0390)
error [OWN_CTL] in the D_Port #01 transfer of the
(DCTL).
DCTL HP#S1- The FCP_CMND was not stored Gather
HFPC#S1 transfer in the SFQ area of the HFPC
error [OWN_CTL] #S1 in the H_Port #S1 transfer
(DCTL).
DCTL HP#00- The FCP_CMND was not stored Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#0 transfer in the SFQ area of the HFPC #0 is displayed following this Replacing Interface
error [OWN_CTL] in the H_Port #00 transfer of the message, replace the Board (REP 02-
data transfer control LSI Interface Board #0 of the 0660)
DCTL HP#01- The FCP_CMND was not stored Gather the message.
HFPC#1 transfer in the SFQ area of the HFPC #1 dIn a case other than c,
error [OWN_CTL] in the H_Port #01 transfer of the replace the Interface Board
data transfer control LSI #0 of the Control Unit
Unit (REP 02-0390)

MSG 02-0480-01
Collect the error

Message
code
Trace Trace Dump
0184xxC6 DCTL DP#00- The ERQ consumer index of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
Unit (REP 02-0390)

MSG 02-0490-01
Collect the error

Message
code
Trace Trace Dump
0184xxC7 DCTL DP#00- The INT of the DFPC #0 did not Gather cWhen W0100x CTL alarm Chapter 6. Warning
(DCTL).
control LSI (DCTL).
Unit (REP 02-0390)

MSG 02-0500-01
Collect the error

Message
code
Trace Trace Dump
0184xxC8 DCTL DP#00- The IMQ producer index of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
Unit (REP 02-0390)

MSG 02-0510-01
Collect the error

Message
code
Trace Trace Dump
0184xxC9 DCTL DP#00- The expected completion Gather cWhen W0100x CTL alarm Chapter 6. Warning
control LSI (DCTL).
control LSI (DCTL).
Unit (REP 02-0390)

MSG 02-0520-01
Collect the error

Message
code
Trace Trace Dump
0184xxCA DCTL DP#00- The ERQ consumer index of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
Unit (REP 02-0390)

MSG 02-0530-01
Collect the error

Message
code
Trace Trace Dump
0184xxCB DCTL DP#00- The INT of the DFPC #0 did not Gather cWhen W0100x CTL alarm Chapter 6. Warning
(DCTL).
control LSI (DCTL).
Unit (REP 02-0390)

MSG 02-0540-01
Collect the error

Message
code
Trace Trace Dump
0184xxCC DCTL DP#00- The IMQ producer index of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
Unit (REP 02-0390)

MSG 02-0550-01
Collect the error

Message
code
Trace Trace Dump
0184xxCD DCTL DP#00- The expected completion Gather cWhen W0100x CTL alarm Chapter 6. Warning
control LSI (DCTL).
control LSI (DCTL).
Unit (REP 02-0390)

MSG 02-0560-01
Collect the error

Message
code
Trace Trace Dump
0184xxCE DCTL DP#00- The FCP_RSP of the DFPC #0 Gather cWhen W0100x CTL alarm Chapter 6. Warning
DFPC#0 transfer was not transferred in the is displayed following this Messages (MSG 06-
DCTL DP#01- The FCP_RSP of the DFPC #1 Gather dReplace the Control Unit of Replacement 2.2.5
DFPC#1 transfer was not transferred in the which the CALM LED lights Replacing Control
DCTL HP#S1- The FCP_RSP of the HFPC Gather
HFPC#S1 transfer #S1 was not transferred in the
DCTL HP#00- The FCP_RSP of the HFPC #0 Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#0 transfer was not transferred in the is displayed following this Replacing Interface
DCTL HP#01- The FCP_RSP of the HFPC #1 Gather the message.
HFPC#1 transfer was not transferred in the dIn a case other than c,
Unit (REP 02-0390)

MSG 02-0570-01
Collect the error

Message
code
Trace Trace Dump
0184xxCF DCTL DP#00- An error occurred in the DFPC Gather cWhen W0100x CTL alarm Chapter 6. Warning
DFPC#0 transfer #0 in the D_Port #00 transfer of is displayed following this Messages (MSG 06-
error [OWN_CTL] the data transfer control LSI message, take recovery 0000)
DCTL DP#01- An error occurred in the DFPC Gather dReplace the Control Unit of Replacement 2.2.5
DFPC#1 transfer #1 in the D_Port #01 transfer of which the CALM LED lights Replacing Control
error [OWN_CTL] the data transfer control LSI on except for c. Unit (REP 02-0390)
(DCTL).
DCTL HP#S1- An error occurred in the HFPC Gather
HFPC#S1 transfer #S1 in the H_Port #S1 transfer
error [OWN_CTL] of the data transfer control LSI
(DCTL).
DCTL HP#00- An error occurred in the HFPC Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#0 transfer #0 in the H_Port #00 transfer of is displayed following this Replacing Interface
error [OWN_CTL] the data transfer control LSI message, replace the Board (REP 02-
DCTL HP#01- An error occurred in the HFPC Gather the message.
HFPC#1 transfer #1 in the H_Port #01 transfer of dIn a case other than c,
error [OWN_CTL] the data transfer control LSI replace the Interface Board
Unit (REP 02-0390)

MSG 02-0580-01
Message
Message text Description Collect the error Recovery methods Reference page
code
01851101 CACHE#0 The cache memory of the DIMM Gather c Check whether a cache Replacement 2.2.6
implementation check Slot #0 is not installed. (It was memory is installed in the Replacing Cache
error in MP access found through the MP access cache slot #0 of the Control Unit (REP 02-0540)
[OWN_CTL] examination.) Unit whose CALM LED is
01851201 CACHE#0 A failure occurred during an Gather on. If it is not installed,
implementation check examination of a size of the install a cache memory in
error in Shadow cache memory in the DIMM Slot the cache slot #0.
image [OWN_CTL] #0. d When the cache memory is
01851202 CACHE#0 The size of the cache memory in Gather installed firmly, replace it.
implementation check the DIMM Slot #0 was that If not, install it firmly in the
error in Shadow which could not be controlled by cache memory slot.
image [OWN_CTL] the data transfer control LSI eIf not recovered, replace Replacement 2.2.5
(DCTL). the Control Unit. Replacing Control
01851211 CACHE#1 A failure occurred during an Gather Unit (REP 02-0390)
implementation check examination of a size of the
error in Shadow cache memory in the DIMM Slot
image [OWN_CTL] #1.
01851212 CACHE#1 A failure occurred during an Gather
implementation check examination of a size of the
error in Shadow cache memory in the DIMM Slot
image [OWN_CTL] #1.
01851401 CACHE#0 The result of an examination of Gather
implementation check a size of the cache memory in
error in Shadow the DIMM Slot #0 was different
image & TWSI from the size information written
[OWN_CTL] in the cache memory.
01851411 CACHE#1 The result of an examination of Gather
implementation check a size of the cache memory in
error in Shadow the DIMM Slot #1 was different
image & TWSI from the size information written
[OWN_CTL] in the cache memory.
01851501 CACHE#0 data line Inconsistency between write and Gather
error [OWN_CTL] read data was detected in the
data line test of the cache
memory in the DIMM Slot #0.
01851502 CACHE#0 data line Inconsistency between write and Gather
error [OWN_CTL] read data was detected in the
data line test of the cache
01851601 CACHE#0 address Inconsistency between write and Gather
line error [OWN_CTL] read data was detected in the
address line test of the cache
01851701 CACHE#0 data Inconsistency between write and Gather
[OWN_CTL] R/W test of the cache memory
in the DIMM Slot #0.

MSG 02-0590-01
Collect the error

Message
code
Trace Trace Dump
01851B01 CACHE#0 data Inconsistency between the write Gather c Check whether a cache Replacement 2.2.6
compare error and read data was detected in memory is installed in the Replacing Cache
[OWN_CTL] the RMW address switching cache slot #0 of the Control Unit (REP 02-0540)
R/W test of the cache memory Unit whose CALM LED is
in the DIMM Slot #0. on. If it is not installed,
01851B02 CACHE#0 data Inconsistency between the write Gather install a cache memory in
compare error and read data was detected in the cache slot #0.
[OWN_CTL] the RMW address switching d When the cache memory is
R/W test of the cache memory installed firmly, replace it.
in the DIMM Slot #0. If not, install it firmly in the
01851B03 CACHE#0 data Inconsistency between the write Gather cache memory slot.
compare error and read data was detected in e If not recovered, replace Replacement 2.2.5
[OWN_CTL] the RMW address switching the Control Unit. Replacing Control
R/W test of the cache memory Unit (REP 02-0390)
01851D01 CACHE#0 data Inconsistency between the write Gather
[OWN_CTL] the Data Write Mask R/W test of
the cache memory in the DIMM
Slot #0.
Slot #0.
Slot #0.

MSG 02-0600-01
Collect the error

Message
code
Trace Trace Dump
01852101 CACHE#0 ECC R/W Inconsistency between the write Gather c Check whether a cache Replacement 2.2.6
data compare error and read data was detected in memory is installed in the Replacing Cache
[OWN_CTL] the ECC R/W test of the cache cache slot #0 of the Control Unit (REP 02-0540)
memory in the DIMM Slot #0. Unit whose CALM LED is
01852201 CACHE#0 ECC The ECC correctable error was Gather on. If it is not installed,
circuit error not detected in the ECC circuit install a cache memory in
[OWN_CTL] test of the cache memory in the the cache slot #0.
01852202 CACHE#0 ECC DIMM Slot #0. Gather d When the cache memory is
circuit error installed firmly, replace it.
[OWN_CTL] If not, install it firmly in the
01852203 CACHE#0 ECC Gather cache memory slot.
circuit error eIf not recovered, replace Replacement 2.2.5
[OWN_CTL] the Control Unit. Replacing Control
01852204 CACHE#0 ECC Gather Unit (REP 02-0390)
circuit error
[OWN_CTL]
01852205 CACHE#0 ECC Gather
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
0185220A CACHE#0 ECC Gather
circuit error
[OWN_CTL]
0185220B CACHE#0 ECC Gather
circuit error
[OWN_CTL]
0185220C CACHE#0 ECC Gather
circuit error
[OWN_CTL]
0185220D CACHE#0 ECC Gather
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]

MSG 02-0610-01
Collect the error

Message
code
Trace Trace Dump
01852219 CACHE#0 ECC The ECC correctable error was Gather c Check whether a cache Replacement 2.2.6
circuit error not detected in the ECC circuit memory is installed in the Replacing Cache
[OWN_CTL] test of the cache memory in the cache slot #0 of the Control Unit (REP 02-0540)
0185221A CACHE#0 ECC DIMM Slot #0. Gather Unit whose CALM LED is
circuit error on. If it is not installed,
[OWN_CTL] install a cache memory in
0185221B CACHE#0 ECC Gather the cache slot #0.
circuit error d When the cache memory is
[OWN_CTL] installed firmly, replace it.
0185221C CACHE#0 ECC Gather If not, install it firmly in the
circuit error cache memory slot.
[OWN_CTL] e If not recovered, replace Replacement 2.2.5
0185221D CACHE#0 ECC Gather the Control Unit. Replacing Control
circuit error Unit (REP 02-0390)
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]

MSG 02-0620-01
Collect the error

Message
code
Trace Trace Dump
01852401 CACHE#0 ECC The ECC uncorrectable error Gather c Check whether a cache Replacement 2.2.6
circuit error was not detected in the ECC memory is installed in the Replacing Cache
[OWN_CTL] circuit test of the cache memory cache slot #0 of the Control Unit (REP 02-0540)
01852402 CACHE#0 ECC in the DIMM Slot #0. Gather Unit whose CALM LED is
01852403 CACHE#0 ECC Gather the cache slot #0.
01852404 CACHE#0 ECC Gather If not, install it firmly in the
01852405 CACHE#0 ECC Gather the Control Unit. Replacing Control
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]

MSG 02-0630-01
Collect the error

Message
code
Trace Trace Dump
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]

MSG 02-0640-01
Collect the error

Message
code
Trace Trace Dump
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
circuit error
[OWN_CTL]
01853101 CACHE#0 The peculiar code of the cache Gather
unsupported memory in the DIMM Slot #0
[OWN_CTL] was illegal.
01853111 CACHE#1 The peculiar code of the cache Gather
unsupported memory in the DIMM Slot #1
[OWN_CTL] was illegal.
01853201 CACHE#0 The capacity of the cache Gather
unsupported memory in the DIMM Slot #0 is
[OWN_CTL] not supported.
01853211 CACHE#1 The capacity of the cache Gather
unsupported memory in the DIMM Slot #1 is
[OWN_CTL] not supported.

MSG 02-0650-01
Collect the error

Message
code
Trace Trace Dump
01853311 CACHE#1 data line Inconsistency between write and Gather c Check whether a cache Replacement 2.2.6
error [OWN_CTL] read data was detected in the memory is installed in the Replacing Cache
data line test of the cache cache slot #0 of the Control Unit (REP 02-0540)
memory in the DIMM Slot #1. Unit whose CALM LED is
01853312 CACHE#1 data line Inconsistency between write and Gather on. If it is not installed,
error [OWN_CTL] read data was detected in the install a cache memory in
data line test of the cache the cache slot #0.
memory in the DIMM Slot #1. d When the cache memory is
01853411 CACHE#1 address Inconsistency between write and Gather installed firmly, replace it.
line error [OWN_CTL] read data was detected in the If not, install it firmly in the
address line test of the cache cache memory slot.
memory in the DIMM Slot #1. e If not recovered, replace Replacement 2.2.5
01853511 CACHE#1 data Inconsistency between write and Gather the Control Unit. Replacing Control
compare error read data was detected in the Unit (REP 02-0390)
[OWN_CTL] R/W test of the cache memory
[OWN_CTL] data write mask R/W test of the
cache memory in the DIMM Slot
#1.
#1.
#1.
01864101 RTC memory data Inconsistency between write and Gather cWhen W0100x CTL alarm Chapter 6. Warning
compare error read data was detected in the is displayed following this Messages (MSG 06-
[OWN_CTL] R/W test of the RTC memory. message, take recovery 0000)
actions according to the
message.
dReplace the Control Unit of Replacement 2.2.5
which the CALM LED lights Replacing Control
on except for c. Unit (REP 02-0390)

MSG 02-0660-01
Collect the error

Message
code
Trace Trace Dump
01D05101 DFPC#0 MADDR The MADDR value of the DFPC Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] #0 was illegal. is displayed following this Messages (MSG 06-
01D05301 DFPC#0 register data Inconsistency between write and Gather message, take recovery 0000)
compare error read data was detected in the actions according to the
[OWN_CTL] register R/W test of the DFPC message.
#0. d Replace the Control Unit of Replacement 2.2.5
01D05302 DFPC#0 register data Inconsistency between write and Gather which the CALM LED lights Replacing Control
compare error read data was detected in the on except for c. Unit (REP 02-0390)
[OWN_CTL] register R/W test of the DFPC
#0.
01D05303 DFPC#0 hard status An illegal error status occurred Gather
error [OWN_CTL] in the register R/W test of the
DFPC #0.
01D05401 DFPC#0 transfer data The transferred data was Gather
compare error inconsistent with test data of a
[OWN_CTL] sender in the test of transfer
between the local memories
(CSDSs) of the DFPC #0.
01D05601 DFPC#1 MADDR The MADDR value of the DFPC Gather
error [OWN_CTL] #1 was illegal.
01D05801 DFPC#1 register data Inconsistency between write and Gather
#1.
01D05802 DFPC#1 register data Inconsistency between write and Gather
#1.
01D05803 DFPC#1 hard status An illegal error status occurred Gather
DFPC #1.

MSG 02-0670-01
Collect the error

Message
code
Trace Trace Dump
01D0xxC1 DFPC#0 loop back The ERQ consumer index was Gather c When W0100x CTL alarm Chapter 6. Warning
transfer error not upped in the loop back is displayed following this Messages (MSG 06-
[OWN_CTL] transfer of the DFPC #0. message, take recovery 0000)
x : Diagnostic item code actions according to the
DFPC#1 loop back The ERQ consumer index was Gather message.
transfer error not upped in the loop back dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] transfer of the DFPC #1. which the CALM LED lights Replacing Control
x : Diagnostic item code on except for c. Unit (REP 02-0390)
01D0xxC2 DFPC#0 loop back The INT did not occur in the Gather c When W0100x CTL alarm Chapter 6. Warning
transfer error loop back transfer of the DFPC is displayed following this Messages (MSG 06-
[OWN_CTL] #0. message, take recovery 0000)
DFPC#1 loop back The INT did not occur in the Gather message.
transfer error loop back transfer of the DFPC dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] #1. which the CALM LED lights Replacing Control
01D0xxC3 DFPC#0 loop back The IMQ producer index was Gather c When W0100x CTL alarm Chapter 6. Warning
DFPC#1 loop back The IMQ producer index was Gather message.
01D0xxC4 DFPC#0 loop back The expected completion Gather c When W0100x CTL alarm Chapter 6. Warning
transfer error message was not got in the loop is displayed following this Messages (MSG 06-
[OWN_CTL] back transfer of the DFPC #0. message, take recovery 0000)
DFPC#1 loop back The expected completion Gather message.
transfer error message was not got in the loop dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] back transfer of the DFPC #1. which the CALM LED lights Replacing Control
01D0xxC5 DFPC#0 loop back The FCP_CMND was not stored Gather c When W0100x CTL alarm Chapter 6. Warning
transfer error in the SFQ area of the loop back is displayed following this Messages (MSG 06-
[OWN_CTL] transfer of the DFPC#0. message, take recovery 0000)
DFPC#1 loop back The FCP_CMND was not stored Gather message.
transfer error in the SFQ area of the loop back dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] transfer of the DFPC#1. which the CALM LED lights Replacing Control
01D0xxC6 DFPC#0 loop back The ERQ consumer index was Gather c When W0100x CTL alarm Chapter 6. Warning

MSG 02-0680-01
Collect the error

Message
code
Trace Trace Dump
01D0xxC7 DFPC#0 loop back The INT did not occur in the Gather c When W0100x CTL alarm Chapter 6. Warning
01D0xxC8 DFPC#0 loop back The IMQ producer index was Gather c When W0100x CTL alarm Chapter 6. Warning
01D0xxC9 DFPC#0 loop back The expected completion Gather c When W0100x CTL alarm Chapter 6. Warning
01D0xxCA DFPC#0 loop back The ERQ consumer index was Gather c When W0100x CTL alarm Chapter 6. Warning
01D0xxCB DFPC#0 loop back The INT did not occur in the Gather c When W0100x CTL alarm Chapter 6. Warning
01D0xxCC DFPC#0 loop back The IMQ producer index was Gather c When W0100x CTL alarm Chapter 6. Warning

MSG 02-0690-01
Collect the error

Message
code
Trace Trace Dump
01D0xxCD DFPC#0 loop back The expected completion Gather c When W0100x CTL alarm Chapter 6. Warning
01D0xxCE DFPC#0 loop back The FCP_RSP was not Gather c When W0100x CTL alarm Chapter 6. Warning
transfer error transferred in the loop back is displayed following this Messages (MSG 06-
DFPC#1 loop back The FCP_RSP was not Gather message.
transfer error transferred in the loop back dReplace the Control Unit of Replacement 2.2.5
01D0xxCF DFPC#0 loop back An error occurred in the loop Gather c When W0100x CTL alarm Chapter 6. Warning
transfer error back transfer of the DFPC #0. is displayed following this Messages (MSG 06-
[OWN_CTL] x : Diagnostic item code message, take recovery 0000)
DFPC#1 loop back An error occurred in the loop Gather actions according to the
transfer error back transfer of the DFPC #1. message.
[OWN_CTL] x : Diagnostic item code dReplace the Control Unit of Replacement 2.2.5

MSG 02-0700-01
Collect the error

Message
code
Trace Trace Dump
01D57101 HFPC#0 MADDR The MADDR value of the HFPC Gather c When W0100x CTL alarm Replacement 2.2.7
error [OWN_CTL] #0 was illegal. is displayed following this Replacing Interface
01D57301 HFPC#0 register data Inconsistency between write and Gather message, replace the Board (REP 02-
compare error read data was detected in the Interface Board #0 of the 0660)
[OWN_CTL] register R/W test of the HFPC Control Unit pointed out in
#0. the message.
01D57302 HFPC#0 register data Inconsistency between write and Gather dIn a case other than c,
compare error read data was detected in the replace the Interface Board
[OWN_CTL] register R/W test of the HFPC #0 of the Control Unit
#0. whose CALM LED is on.
01D57303 HFPC#0 hard status An illegal error status occurred Gather eIf not recovered, replace Replacement 2.2.5
error [OWN_CTL] in the register R/W test of the Control Unit. Replacing Control
HFPC #0. Unit (REP 02-0390)
01D57401 HFPC#0 transfer data The transferred data was Gather
(CSDSs) of the HFPC #0.
01D57601 HFPC#1 MADDR The MADDR value of the HFPC Gather
error [OWN_CTL] #1 was illegal.
01D57801 HFPC#1 register data Inconsistency between write and Gather
[OWN_CTL] register R/W test of the HFPC
#1.
01D57802 HFPC#1 register data Inconsistency between write and Gather
#1.
01D57803 HFPC#1 hard status An illegal error status occurred Gather
HFPC #1.

MSG 02-0710-01
Collect the error

Message
code
Trace Trace Dump
01D59101 HFPC#S1 MADDR The MADDR value of the HFPC Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] #S1was illegal. is displayed following this Messages (MSG 06-
01D59301 HFPC#S1 register Inconsistency between write and Gather message, take recovery 0000)
data compare error read data was detected in the actions according to the
[OWN_CTL] register R/W test of the HFPC message.
#S1. d Replace the Control Unit of Replacement 2.2.5
01D59302 HFPC#S1 register Inconsistency between write and Gather which the CALM LED lights Replacing Control
data compare error read data was detected in the on except for c. Unit (REP 02-0390)
#S1.
01D59303 HFPC#S1 hard status An illegal error status occurred Gather
HFPC #S1.
01D59401 HFPC#S1 transfer The transferred data was Gather
data compare error inconsistent with test data of a
(CSDSs) of the HFPC #S1.
01D59402 HFPC#S1 transfer The transferred data was Gather
data compare error inconsistent with test data of a
(CSDSs) of the HFPC #S1.

MSG 02-0720-01
Collect the error

Message
code
Trace Trace Dump
01D5xxC1 HFPC #S1 loop back The ERQ consumer index was Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] transfer of the HFPC #S1. message, take recovery 0000)
message.
HFPC #0 loop back The ERQ consumer index was Gather c When W0100x CTL alarm Replacement 2.2.7
transfer error not upped in the loop back is displayed following this Replacing Interface
[OWN_CTL] transfer of the HFPC #0. message, replace the Board (REP 02-
x : Diagnostic item code Interface Board #0 of the 0660)
HFPC #1 loop back The ERQ consumer index was Gather Control Unit pointed out in
transfer error not upped in the loop back the message.
[OWN_CTL] transfer of the HFPC #1. dIn a case other than c,
x : Diagnostic item code replace the Interface Board
#0 of the Control Unit
whose CALM LED is on.
Unit (REP 02-0390)
01D5xxC2 HFPC #S1 loop back The INT did not occur in the loop Gather cWhen W0100x CTL alarm Chapter 6. Warning
transfer error back transfer of the HFPC #S1. is displayed following this Messages (MSG 06-
message.
HFPC #0 loop back The INT did not occur in the loop Gather c When W0100x CTL alarm Replacement 2.2.7
transfer error back transfer of the HFPC #0. is displayed following this Replacing Interface
[OWN_CTL] x : Diagnostic item code message, replace the Board (REP 02-
Interface Board #0 of the 0660)
HFPC #1 loop back The INT did not occur in the loop Gather Control Unit pointed out in
transfer error back transfer of the HFPC #1. the message.
[OWN_CTL] x : Diagnostic item code dIn a case other than c,
replace the Interface Board
Unit (REP 02-0390)

MSG 02-0730-01
Collect the error

Message
code
Trace Trace Dump
01D5xxC3 HFPC #S1 loop back The IMQ producer index was Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
HFPC #0 loop back The IMQ producer index was Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC #1 loop back The IMQ producer index was Gather Control Unit pointed out in
Unit (REP 02-0390)
01D5xxC4 HFPC#S1 loop back The expected completion Gather cWhen W0100x CTL alarm Chapter 6. Warning
[OWN_CTL] back transfer of the HFPC #S1. message, take recovery 0000)
message.
HFPC #0 loop back The expected completion Gather c When W0100x CTL alarm Replacement 2.2.7
transfer error message was not got in the loop is displayed following this Replacing Interface
[OWN_CTL] back transfer of the HFPC #0. message, replace the Board (REP 02-
HFPC #1 loop back The expected completion Gather Control Unit pointed out in
transfer error message was not got in the loop the message.
[OWN_CTL] back transfer of the HFPC #1. dIn a case other than c,
Unit (REP 02-0390)

MSG 02-0740-01
Collect the error

Message
code
Trace Trace Dump
01D5xxC5 HFPC #S1 loop back The FCP_CMND was not stored Gather cWhen W0100x CTL alarm Chapter 6. Warning
transfer error in the SFQ area of the loop back is displayed following this Messages (MSG 06-
message.
HFPC #0 loop back The FCP_CMND was not stored Gather c When W0100x CTL alarm Replacement 2.2.7
transfer error in the SFQ area of the loop back is displayed following this Replacing Interface
HFPC #1 loop back The FCP_CMND was not stored Gather Control Unit pointed out in
transfer error in the SFQ area of the loop back the message.
Unit (REP 02-0390)
01D5xxC6 HFPC #S1 loop back The ERQ consumer index was Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)

MSG 02-0750-01
Collect the error

Message
code
Trace Trace Dump
01D5xxC7 HFPC #S1 loop back The INT did not occur in the loop Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)
01D5xxC8 HFPC #S1 loop back The IMQ producer index was Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)

MSG 02-0760-01
Collect the error

Message
code
Trace Trace Dump
01D5xxC9 HFPC #S1 loop back The expected completion Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)
01D5xxCA HFPC #S1 loop back The ERQ consumer index was Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)

MSG 02-0770-01
Collect the error

Message
code
Trace Trace Dump
01D5xxCB HFPC #S1 loop back The INT did not occur in the loop Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)
01D5xxCC HFPC #S1 loop back The IMQ producer index was Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)

MSG 02-0780-01
Collect the error

Message
code
Trace Trace Dump
01D5xxCD HFPC #S1 loop back The expected completion Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
Unit (REP 02-0390)
01D5xxCE HFPC #S1 loop back The FCP_RSP was not Gather cWhen W0100x CTL alarm Chapter 6. Warning
transfer error transferred in the loop back is displayed following this Messages (MSG 06-
message.
HFPC #0 loop back The FCP_RSP was not Gather c When W0100x CTL alarm Replacement 2.2.7
transfer error transferred in the loop back is displayed following this Replacing Interface
HFPC #1 loop back The FCP_RSP was not Gather Control Unit pointed out in
transfer error transferred in the loop back the message.
Unit (REP 02-0390)

MSG 02-0790-01
Collect the error

Message
code
Trace Trace Dump
01D5xxCF HFPC #S1 loop back An error occurred in the loop Gather cWhen W0100x CTL alarm Chapter 6. Warning
message.
HFPC #0 loop back An error occurred in the loop Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC #1 loop back An error occurred in the loop Gather Control Unit pointed out in
Unit (REP 02-0390)

MSG 02-0800-01
Collect the error

Message
code
Trace Trace Dump
01xxxxA0 TWSI read access The TWSI (Two Wired Serial Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] Interface) read access failed. is displayed following this Messages (MSG 06-
x : Diagnostic item code message, take recovery 0000)
01xxxxA1 TWSI read access The TWSI (Two Wired Serial Gather actions according to the
error [OWN_CTL] Interface) read access failed. message.
01xxxxA8 CSDS data path A data path parity error occurred Gather which the CALM LED lights Replacing Control
parity error in the local memory (CSDS). on except for c. Unit (REP 02-0390)
[OWN_CTL] x : Diagnostic item code
01xxxxA9 CSDS 2bit ECC error A 2-bit ECC error occurred in Gather
[OWN_CTL] the local memory (CSDS).
01xxxxAA CSDS 1bit ECC error A 1-bit ECC error occurred in Gather
[OWN_CTL] the local memory (CSDS).
01xxxxAC Bridge SRAM 2bit The 2-bit ECC error occurred in Gather
ECC error the SRAM in the bridge.
01xxxxAD Bridge SRAM 1bit The 1-bit ECC error occurred in Gather
ECC error the SRAM in the bridge.
01xxxxB1 DFPC#0 loop Though the Loop Initialize Gather
initialize error instruction was issued in the
[OWN_CTL] loop initialize of the DFPC #0,
the INT did not occur.
DFPC#1 loop Though the Loop Initialize Gather
[OWN_CTL] loop initialize of the DFPC #1,
HFPC#S1 loop Though the Loop Initialize Gather
[OWN_CTL] loop initialize of the HFPC #S1,
HFPC#0 loop Though the Loop Initialize Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error instruction was issued in the is displayed following this Replacing Interface
[OWN_CTL] loop initialize of the HFPC #0, message, replace the Board (REP 02-
the INT did not occur. Interface Board #0 of the 0660)
HFPC#1 loop Though the loop initialize Gather the message.
initialize error instruction was issued in the dIn a case other than c,
[OWN_CTL] loop initialization of the HFPC replace the Interface Board
#1, the INT did not occur. #0 of the Control Unit
Unit (REP 02-0390)

MSG 02-0810-01
Collect the error

Message
code
Trace Trace Dump
01xxxxB2 DFPC#0 loop The IMQ producer index was Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error not upped in the loop initialize of is displayed following this Messages (MSG 06-
[OWN_CTL] the DFPC #0. message, take recovery 0000)
DFPC#1 loop The IMQ producer index was Gather message.
initialize error not upped in the loop initialize of dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] the DFPC #1. which the CALM LED lights Replacing Control
HFPC#S1 loop The IMQ producer index was Gather
initialize error not upped in the loop initialize of
[OWN_CTL] the HFPC #S1.
HFPC#0 loop The IMQ producer index was Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error not upped in the loop initialize of is displayed following this Replacing Interface
[OWN_CTL] the HFPC #0. message, replace the Board (REP 02-
HFPC#1 loop The IMQ producer index was Gather Control Unit pointed out in
initialize error not upped in the loop initialize of the message.
[OWN_CTL] the HFPC #1. dIn a case other than c,
Unit (REP 02-0390)
01xxxxB3 DFPC#0 loop The expected completion Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error message could not be got in the is displayed following this Messages (MSG 06-
[OWN_CTL] loop initialize of the DFPC #0. message, take recovery 0000)
DFPC#1 loop The expected completion Gather message.
initialize error message could not be got in the dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] loop initialize of the DFPC #1. which the CALM LED lights Replacing Control
HFPC#S1 loop The expected completion Gather
initialize error message could not be got in the
[OWN_CTL] loop initialize of the HFPC #S1.
HFPC#0 loop The expected completion Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error message could not be got in the is displayed following this Replacing Interface
[OWN_CTL] loop initialize of the HFPC #0. message, replace the Board (REP 02-
HFPC#1 loop The expected completion Gather Control Unit pointed out in
initialize error message could not be got in the the message.
[OWN_CTL] loop initialize of the HFPC #1. dIn a case other than c,
Unit (REP 02-0390)

MSG 02-0820-01
Collect the error

Message
code
Trace Trace Dump
01xxxxB4 DFPC#0 loop The expected Frame Manager Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error Status could not be got in the is displayed following this Messages (MSG 06-
DFPC#1 loop The expected Frame Manager Gather message.
initialize error Status could not be got in the dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] loop initialize of the DFPC #1. which the CALM LED lights Replacing Control
HFPC#S1 loop The expected Frame Manager Gather
initialize error Status could not be got in the
HFPC#0 loop The expected Frame Manager Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error Status could not be got in the is displayed following this Replacing Interface
HFPC#1 loop The expected Frame Manager Gather Control Unit pointed out in
initialize error Status could not be got in the the message.
[OWN_CTL] loop initialize of the HFPC #1. dIn a case other than c,
Unit (REP 02-0390)
01xxxxB5 DFPC#0 loop The INT did not occur in the loop Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error initialize of the DFPC #0. is displayed following this Messages (MSG 06-
DFPC#1 loop The INT did not occur in the loop Gather actions according to the
initialize error initialize of the DFPC #1. message.
[OWN_CTL] x : Diagnostic item code d Replace the Control Unit of Replacement 2.2.5
HFPC#S1 loop The INT did not occur in the Gather which the CALM LED lights Replacing Control
initialize error loop initialize of the HFPC #S1. on except for c. Unit (REP 02-0390)
HFPC#0 loop The INT did not occur in the loop Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error initialize of the HFPC #0. is displayed following this Replacing Interface
HFPC#1 loop The INT did not occur in the loop Gather Interface Board #0 of the 0660)
initialize error initialize of the HFPC #1. Control Unit pointed out in
[OWN_CTL] x : Diagnostic item code the message.
dIn a case other than c,
Unit (REP 02-0390)

MSG 02-0830-01
Collect the error

Message
code
Trace Trace Dump
Unit (REP 02-0390)
01xxxxB7 DFPC#0 loop The SFQ producer index was Gather c When W0100x CTL alarm Chapter 6. Warning
DFPC#1 loop The SFQ producer index was Gather message.
HFPC#S1 loop The SFQ producer index was Gather
HFPC#0 loop The SFQ producer index was Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#1 loop The SFQ producer index was Gather Control Unit pointed out in
Unit (REP 02-0390)

MSG 02-0840-01
Collect the error

Message
code
Trace Trace Dump
Unit (REP 02-0390)
01xxxxB9 DFPC#0 loop The expected frame manager Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error status was not got in the loop is displayed following this Messages (MSG 06-
[OWN_CTL] initialize of the DFPC #0. message, take recovery 0000)
DFPC#1 loop The expected frame manager Gather message.
initialize error status was not got in the loop dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] initialize of the DFPC #1. which the CALM LED lights Replacing Control
HFPC#S1 loop The expected frame manager Gather
initialize error status was not got in the loop
[OWN_CTL] initialize of the HFPC #S1.
HFPC#0 loop The expected frame manager Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error status was not got in the loop is displayed following this Replacing Interface
[OWN_CTL] initialize of the HFPC #0. message, replace the Board (REP 02-
HFPC#1 loop The expected frame manager Gather Control Unit pointed out in
initialize error status was not got in the loop the message.
[OWN_CTL] initialize of the HFPC #1. dIn a case other than c,
Unit (REP 02-0390)

MSG 02-0850-01
Collect the error

Message
code
Trace Trace Dump
01xxxxBA DFPC#0 loop The SFQ producer index was Gather c When W0100x CTL alarm Chapter 6. Warning
DFPC#1 loop The SFQ producer index was Gather message.
HFPC#S1 loop The SFQ producer index was Gather
HFPC#0 loop The SFQ producer index was Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#1 loop The SFQ producer index was Gather Control Unit pointed out in
Unit (REP 02-0390)
01xxxxBB DFPC#0 loop The loop map was incorrect in Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error the loop initialize of the DFPC is displayed following this Messages (MSG 06-
DFPC#1 loop The loop map was incorrect in Gather message.
initialize error the loop initialize of the DFPC dReplace the Control Unit of Replacement 2.2.5
HFPC#S1 loop The loop map was incorrect in Gather
initialize error the loop initialize of the HFPC
[OWN_CTL] #S1.
HFPC#0 loop The loop map was incorrect in Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error the loop initialize of the HFPC is displayed following this Replacing Interface
[OWN_CTL] #0. message, replace the Board (REP 02-
HFPC#1 loop The loop map was incorrect in Gather Control Unit pointed out in
initialize error the loop initialize of the HFPC the message.
[OWN_CTL] #1. dIn a case other than c,
Unit (REP 02-0390)

MSG 02-0860-01
Collect the error

Message
code
Trace Trace Dump
01xxxxBC DFPC#0 loop The expected Frame Manager Gather cWhen W0100x CTL alarm Chapter 6. Warning
initialize error status could not be got in the is displayed following this Messages (MSG 06-
message.
DFPC#1 loop The expected Frame Manager Gather dReplace the Control Unit of Replacement 2.2.5
initialize error status could not be got in the which the CALM LED lights Replacing Control
[OWN_CTL] loop initialize of the DFPC #1. on except for c. Unit (REP 02-0390)
HFPC#S1 loop The expected Frame Manager Gather
initialize error status could not be got in the
HFPC#0 loop The expected Frame Manager Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error status could not be got in the is displayed following this Replacing Interface
HFPC#1 loop The expected Frame Manager Gather Control Unit pointed out in
initialize error status could not be got in the the message.
[OWN_CTL] loop initialize of the HFPC #1 dIn a case other than c,
Unit (REP 02-0390)
01xxxxBD DFPC#0 loop An error occurred in the loop Gather c When W0100x CTL alarm Chapter 6. Warning
initialize error initialize of the DFPC #0. is displayed following this Messages (MSG 06-
DFPC#1 loop An error occurred in the loop Gather actions according to the
initialize error initialize of the DFPC #1. message.
[OWN_CTL] x : Diagnostic item code d Replace the Control Unit of Replacement 2.2.5
HFPC#S1 loop An error occurred in the loop Gather which the CALM LED lights Replacing Control
initialize error initialize of the HFPC #S1. on except for c. Unit (REP 02-0390)
HFPC#0 loop An error occurred in the loop Gather c When W0100x CTL alarm Replacement 2.2.7
initialize error initialize of the HFPC #0. is displayed following this Replacing Interface
HFPC#1 loop An error occurred in the loop Gather Interface Board #0 of the 0660)
initialize error initialize of the HFPC #1. Control Unit pointed out in
[OWN_CTL] x : Diagnostic item code the message.
Unit (REP 02-0390)

MSG 02-0870-01
Collect the error

Message
code
Trace Trace Dump
01xxxxD1 DFPC#0 soft reset The NPT was incorrect in the Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] soft reset of the DFPC #0. is displayed following this Messages (MSG 06-
DFPC#1 soft reset The NPT was incorrect in the Gather actions according to the
error [OWN_CTL] soft reset of the DFPC #1. message.
HFPC#S1 soft reset The NPT was incorrect in the Gather which the CALM LED lights Replacing Control
error [OWN_CTL] soft reset of the HFPC #S1. on except for c. Unit (REP 02-0390)
HFPC#0 soft reset The NPT was incorrect in the Gather c When W0100x CTL alarm Replacement 2.2.7
error [OWN_CTL] soft reset of the HFPC #0. is displayed following this Replacing Interface
x : Diagnostic item code message, replace the Board (REP 02-
HFPC#1 soft reset The NPT was incorrect in the Gather Interface Board #0 of the 0660)
error [OWN_CTL] soft reset of the HFPC #1. Control Unit pointed out in
Unit (REP 02-0390)
01xxxxD2 DFPC#0 soft reset The SRO was incorrect in the Gather c When W0100x CTL alarm Chapter 6. Warning
DFPC#1 soft reset The SRO was incorrect in the Gather actions according to the
HFPC#S1 soft reset The SRO was incorrect in the Gather which the CALM LED lights Replacing Control
HFPC#0 soft reset The SRO was incorrect in the Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#1 soft reset The SRO was incorrect in the Gather Interface Board #0 of the 0660)
Unit (REP 02-0390)

MSG 02-0880-01
Collect the error

Message
code
Trace Trace Dump
01xxxxD3 DFPC#0 soft reset The OFFLINE was incorrect in Gather c When W0100x CTL alarm Chapter 6. Warning
error [OWN_CTL] the soft reset of the DFPC #0. is displayed following this Messages (MSG 06-
DFPC#1 soft reset The OFFLINE was incorrect in Gather actions according to the
error [OWN_CTL] the soft reset of the DFPC #1. message.
HFPC#S1 soft reset The OFFLINE was incorrect in Gather which the CALM LED lights Replacing Control
error [OWN_CTL] the soft reset of the HFPC #S1. on except for c. Unit (REP 02-0390)
HFPC#0 soft reset The OFFLINE was incorrect in Gather c When W0100x CTL alarm Replacement 2.2.7
error [OWN_CTL] the soft reset of the HFPC #0. is displayed following this Replacing Interface
HFPC#1 soft reset The OFFLINE was incorrect in Gather Interface Board #0 of the 0660)
error [OWN_CTL] the soft reset of the HFPC #1. Control Unit pointed out in
Unit (REP 02-0390)
01xxxxD4 DFPC#0 soft reset The SSDR was incorrect in the Gather c When W0100x CTL alarm Chapter 6. Warning
DFPC#1 soft reset The SSDR was incorrect in the Gather actions according to the
HFPC#S1 soft reset The SSDR was incorrect in the Gather which the CALM LED lights Replacing Control
HFPC#0 soft reset The SSDR was incorrect in the Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#1 soft reset The SSDR was incorrect in the Gather Interface Board #0 of the 0660)
Unit (REP 02-0390)

MSG 02-0890-01
Collect the error

Message
code
Trace Trace Dump
01xxxxD5 DFPC#0 soft reset The RCS was incorrect in the Gather c When W0100x CTL alarm Chapter 6. Warning
DFPC#1 soft reset The RCS was incorrect in the Gather actions according to the
HFPC#S1 soft reset The RCS was incorrect in the Gather which the CALM LED lights Replacing Control
HFPC#0 soft reset The RCS was incorrect in the Gather c When W0100x CTL alarm Replacement 2.2.7
HFPC#1 soft reset The RCS was incorrect in the Gather Interface Board #0 of the 0660)
Unit (REP 02-0390)

MSG 02-0900-01
Collect the error

Message
code
Trace Trace Dump
01xxxxE0 CACHE#0 ECC An ECC uncorrectable error Gather c Check whether a cache Replacement 2.2.6
uncorrectable error occurred in the cache memory memory is installed in the Replacing Cache
[OWN_CTL] of the DIMM Slot #0. cache slot #0 of the Control Unit (REP 02-0540)
x : Diagnostic item code Unit whose CALM LED is
01xxxxE1 CACHE#1 ECC An ECC uncorrectable error Gather on. If it is not installed,
uncorrectable error occurred in the cache memory install a cache memory in
[OWN_CTL] of the DIMM Slot #1. the cache slot #0.
x : Diagnostic item code d When the cache memory is
01xxxxE4 CACHE#0 ECC An ECC correctable error Gather installed firmly, replace it.
correctable error occurred in the cache memory If not, install it firmly in the
[OWN_CTL] of the DIMM Slot #0. cache memory slot.
x : Diagnostic item code e If not recovered, replace Replacement 2.2.5
01xxxxE5 CACHE#1 ECC An ECC correctable error Gather the Control Unit. Replacing Control
correctable error occurred in the cache memory Unit (REP 02-0390)
[OWN_CTL] of the DIMM Slot #1.
01xxxxEA DCTL error An error status occurred in the Gather c When W0100x CTL alarm Chapter 6. Warning
MP_ERROR MP_ERROR register of the data is displayed following this Messages (MSG 06-
[OWN_CTL] transfer control LSI (DCTL). message, take recovery 0000)
01xxxxEE MCTL error MPINT An error status occurred in the Gather message.
[OWN_CTL] MPINT register of MCTL in the dReplace the Control Unit of Replacement 2.2.5
data transfer control LSI which the CALM LED lights Replacing Control
01xxxxF1 Bridge PCI0 status An error status occurred in the Gather
error [OWN_CTL] bridge PCI0.
01xxxxF2 Bridge PCI1 status An error status occurred in the Gather
error [OWN_CTL] bridge PCI1.
01xxxxF3 DCTL primary PCI An error status occurred in the Gather
status error primary PCI of the data transfer
[OWN_CTL] control LSI (DCTL).
01xxxxF4 DCTL primary PCI An error status occurred in the Gather
status error primary PCI of the data transfer
01xxxxF5 DCTL host PCI0 An error status occurred in the Gather
status error Host PCI0 of the data transfer
01xxxxF6 DCTL host PCI0 An error status occurred in the Gather
status error Host PCI0 of the data transfer

MSG 02-0910-01
Collect the error

Message
code
Trace Trace Dump
01xxxxF9 DCTL drive PCI0 An error status occurred in the Gather c When W0100x CTL alarm Chapter 6. Warning
status error Drive PCI0 of the data transfer is displayed following this Messages (MSG 06-
[OWN_CTL] control LSI (DCTL). message, take recovery 0000)
01xxxxFA DCTL drive PCI0 An error status occurred in the Gather message.
status error Drive PCI0 of the data transfer dReplace the Control Unit of Replacement 2.2.5
[OWN_CTL] control LSI (DCTL). which the CALM LED lights Replacing Control

MSG 02-0920-01

MSG 02-0930-01
.
Chapter 3. Failure Messages

Collect the error
Message
code
Trace Trace Dump
H00200 MCTL data parity A parity error was detected in Gather cReplace the Control Unit Replacement 2.2.5
error [DP3] data bits 31 to 24 during readout whose CALM LED is on. Replacing Control
[REG80000014, Bit15] from the M-CTL register. Unit (REP 02-0390)
H00300 MCTL data parity A parity error was detected in Gather
error [DP2] data bits 23 to 16 during readout
[REG80000014, Bit14] from the M-CTL register.
H00600 MCTL REG access A writing was done on the read- Gather
error [RDRGWR] only register of the
[REG80000014, Bit11] M-CTL.
H00700 CTC parity error A parity error was detected in Gather
(CH-0) the timer CH0 of the
[REG80000014, Bit5] M-CTL
H00800 CTC parity error A parity error was detected in Gather
(CH-1) the timer CH1 of the M-CTL
[REG80000014, Bit4]
H00900 Watchdog-timer A parity error occurred in the Gather
counter parity error counter for the watchdog timer.
[REG80000014, Bit0]
H10N0x DCTL PPCI data The parity error was detected in Gather
parity error the DCTL (PPCI).
[REG8200127C, x : Control Unit # (0-1)
Bit31]
(CTL-x)
H10P00 DCTL PPCI system A system error was detected in Gather
error the DCTL (PPCI).
[REG8200127C,
Bit30]
H10Q00 DCTL PPCI master A master abortion was received Gather
abort in the DCTL (PPCI).
[REG8200127C,
Bit29]
H10R00 DCTL PPCI received A target abortion was received Gather
target abort in the DCTL (PPCI).
[REG8200127C,
Bit28]
H10S00 DCTL PPCI signaled The target abortion was Gather
target abort executed in the DCTL (PPCI).
[REG8200127C,
Bit27]

MSG 03-0000-01
Collect the error

Message
code
Trace Trace Dump
H10T00 DCTL PPCI PERR The data buffer controller LSI Gather c When W0100x CTL alarm Chapter 6. Warning
detected (D-CTL) asserted or received at is displayed following this Messages (MSG 06-
[REG8200127C, the PERR when the bus master message, take recovery 0000)
Bit24] was used. (PPCIERR) actions according to the
H10U0x DCTL PPCI ADR An address parity error was Gather message.
parity error detected in the DCTL. dReplace the Control Unit of Replacement 2.2.5
[REG8200127C, (PPCIERR) which the CALM LED lights Replacing Control
Bit23] x : Control Unit # (0-1) on except for c. Unit (REP 02-0390)
(CTL-x)
H10V00 DCTL PPCI data read A parity error was detected in the Gather
parity error DCTL in the data read from the
[REG8200127C, data FIFO. (PPCIERR)
Bit22]
H10W00 DCTL PPCI CMD A parity error was detected in Gather cReplace the Control Unit Replacement 2.2.5
parity error the DCTL (PPCI) when the whose CALM LED is on. Replacing Control
[REG8200127C, ADR/CMD was read from the Unit (REP 02-0390)
Bit21] CMD buffer.
H10X00 DCTL PPCI CNT A parity error was detected in Gather
parity error the DCTL (PPCI) during
[REG8200127C, counting by the FIFO control
Bit20] counter.
H10Y00 DCTL PPCI target A data response time-out of a Gather
data response time- target was detected in the DCTL
out (PPCI) in the case of the DCTL
[REG8200127C, master.
Bit19]
H11000 DCTL H0PCI parity The parity error was detected in Gather
error the DCTL (H#0).
[REG82001280, Bit31]
H11100 DCTL H0PCI system A system error was detected in Gather
error the DCTL (H#0).
[REG82001280, Bit30]
H11200 DCTL H0PCI master A master abortion was received Gather
abort in the DCTL (H#0).
[REG82001280, Bit29]
H11300 DCTL H0PCI A target abortion was received Gather
received target abort in the DCTL (H#0).
[REG82001280, Bit28]
H11400 DCTL H0PCI The target abortion was Gather
signaled target abort executed in the DCTL (H#0).
[REG82001280, Bit27]
H11500 DCTL H0PCI PERR The data buffer controller LSI Gather
detected (D-CTL) asserted or received at
[REG82001228, Bit24] the PERR when the bus master
was used. (H#0)
H11600 DCTL H0PCI ADR An address parity error was Gather
parity error detected in the DCTL (H#0).
[REG82001280, Bit23]
H11700 DCTL H0PCI DRD A parity error was detected in Gather
parity error the DCTL (H#0) in the data read

MSG 03-0010-01
[REG82001280, Bit22] from the data FIFO.

MSG 03-0010-01
Collect the error

Message
code
Trace Trace Dump
H11800 DCTL H0PCI CMD A parity error was detected in Gather cReplace the Control Unit Replacement 2.2.5
parity error the DCTL (H#0) when the whose CALM LED is on. Replacing Control
[REG82001280, Bit21] ADR/CMD was read from the Unit (REP 02-0390)
CMD buffer.
H11900 DCTL H0PCI CNT A parity error was detected in Gather
parity error the DCTL (H #0) during counting
[REG82001280, Bit20] by the FIFO control counter.
H11A00 DCTL H0PCI target A data response time-out of a Gather
out (H #0) in the case of the DCTL
[REG82001280, Bit19] master.
H11C00 DCTL D0PCI parity The parity error was detected in Gather
error the DCTL (D #0).
[REG82001288, Bit31]
H11D00 DCTL D0PCI system A system error was detected in Gather
error the DCTL (D #0).
[REG82001288, Bit30]
H11E00 DCTL D0PCI master A master abortion was received Gather
abort in the DCTL (D #0).
[REG82001288, Bit29]
H11F00 DCTL D0PCI A target abortion was received Gather
received target abort in the DCTL (D #0).
[REG82001288, Bit28]
H11G00 DCTL D0PCI The target abortion was Gather
signaled target abort executed in the DCTL (D #0).
[REG82001288, Bit27]
H11H00 DCTL D0PCI PERR The data buffer controller LSI Gather
[REG82001288, Bit24] the PERR when the bus master
was used (D #0).
H11I00 DCTL D0PCI ADR An address parity error was Gather
parity error detected in the DCTL (D #0).
[REG82001288, Bit23]
H11J00 DCTL D0PCI DRD A parity error was detected in Gather
parity error the DCTL (D #0) in the data
[REG82001288, Bit22] read from the data FIFO.
H11K00 DCTL D0PCI CMD A parity error was detected in Gather
parity error the DCTL (D #0) when the
[REG82001288, Bit21] ADR/CMD was read from the
CMD buffer.
H11L00 DCTL D0PCI CNT A parity error was detected in Gather
parity error the DCTL (D #0) during counting
[REG82001288, Bit20] by the FIFO control counter.
H11M00 DCTL D0PCI target A data response time-out of a Gather
out (D #0) in the case of the DCTL
[REG82001288, Bit19] master.

MSG 03-0020-01
Collect the error

Message
code
Trace Trace Dump
H20000 DCTL data parity A data parity error was detected Gather cReplace the Control Unit Replacement 2.2.5
error [DRDPTYERR] during an output from the data whose CALM LED is on. Replacing Control
[REG82001238, Bit23] buffer to the PCI bus. Unit (REP 02-0390)
H20100 Parity generation LA Illegal LA was detected when Gather cSee Troubleshooting Troubleshooting
error [DRR] the (DRR Failure) 6.1.12 A failure occurred 6.1.12 A failure
during operation : Case 2 occurred during
(LA/LRC error). operation : Case 2
(LA/LRC error)
(TRBL 06-0570)
H2020x DCTL byte write error Writing access beyond the 4- Gather cWhen W0100x CTL alarm Chapter 6. Warning
[REG82001238, Bit27] byte boundary was detected. is displayed following this Messages (MSG 06-
(CTL-x) x : Control Unit # (0-1) message, take recovery 0000)
message.
H203A0 DCTL time-out D-CTL finish time-out was Gather cReplace the Control Unit Replacement 2.2.5
[H_PORT] detected. whose CALM LED is on. Replacing Control
H204A1 DCTL time-out D-CTL finish time-out was Gather Unit (REP 02-0390)
[D_PORT] detected.
H205B0 DMA forced stop Forced stopping of DMA failed. Gather
failed
H206B1 DMA#0 hard error Resetting of factors after Gather
end reset failed hardware error end of DRR
failed.
H2070x DCTL dummy area Access, which was done to the Gather
access error access restricted area in the
[REG82001238, Bit17] area for 4-byte dummy data
(CTL-x) addition of the cache, was
detected.
x : Control Unit # (0-1)
H20800 DCTL REF counter A parity error was detected in Gather
parity error the counter for the cache
[REG82001238, Bit1] memory refreshment.
H2091x CACHE address over A cache address over error Gather
[OTH_CTL] occurred in another Control Unit.
(CTL-x) x : Control Unit # (0-1)
H20A0x DCTL CACHE The cache address over was Gather
address over [MPU] detected when the MPU
[REG82001238, Bit21] accessed the cache. (MP)
H20B0x DCTL address parity An address parity error was Gather
error [MPU] detected in the transfer address
[REG82001238, Bit20] received by the cache Control
(CTL-x) Unit.

MSG 03-0030-01
Collect the error

Message
code
Trace Trace Dump
H20C0x DCTL LEN parity A word length parity error was Gather cWhen W0100x CTL alarm Chapter 6. Warning
error detected in the transfer word is displayed following this Messages (MSG 06-
[REG82001238, Bit19] length received by the cache message, take recovery 0000)
(CTL-x) Control Unit. actions according to the
x : Control Unit # (0-1) message.
H20D00 DCTL address over The cache address over was Gather cReplace the Control Unit Replacement 2.2.5
[DMA] detected when the H/D_PORT, whose CALM LED is on. Replacing Control
[REG82001238, Bit18] DMA#0 or MDMA accessed the Unit (REP 02-0390)
cache.
H20E00 DCTL D0PCI The invalid split completion Gather
unexpected SPC message was detected (D #0).
detected
[REG82001288, Bit12]
H20F00 DCTL D0PCI SPC The split completion message Gather
error message that informs of an occurrence of
[REG82001288, Bit13] an error was detected (D #0).
H20G00 DCTL D0PCI SPC The data buffer controller LSI Gather
time-out (D-CTL) detected time-out of
[REG82001288, Bit13] waiting for the split completion
(D #0).
H20H00 DCTL D0PCI SPC The data buffer controller LSI Gather
ADB error (D-CTL) detected that the PCI
[REG82001288, Bit15] transfer was disconnected at an
address other than the ADB
(allowable disconnect boundary)
when it received the split
completion message (D #0).
H20J00 DCTL D0PCI master The data buffer controller LSI Gather
ADB disconnection (D-CTL) detected that the PCI
error transfer was disconnected at an
[REG82001288, Bit18] address other than the ADB
when it was a PCI slave (D #0).
H20K00 DCTL PPCI ADB The data buffer controller LSI Gather
error (D-CTL) detected that the PCI
[REG8200127C, transfer was disconnected at an
Bit18] address other than the ADB
when it was a PCI slave
(PPCIERR).

MSG 03-0040-01
Collect the error

Message
code
Trace Trace Dump
H20L00 DCTL PPCI SPC The data buffer controller LSI Gather cReplace the Control Unit Replacement 2.2.5
ADB error (D-CTL) detected that the PCI whose CALM LED is on. Replacing Control
[REG8200127C, transfer was disconnected at an Unit (REP 02-0390)
completion message.
(PPCIERR)
H20M00 DCTL PPCI SPC The data buffer controller LSI Gather
[REG8200127C, waiting for the split completion
Bit14] (PPCIERR).
H20N00 DCTL PPCI SPC The split completion message Gather
[REG8200127C, an error was detected
Bit13] (PPCIERR).
H20P00 DCTL PPCI The invalid split completion Gather
unexpected SPC message was detected
detected (PPCIERR).
[REG8200127C,
Bit12]
H20Q00 DCTL CACHE ECC During a reading from the Gather cReplace the Cache Unit. Replacement 2.2.6
uncorrectable error cache, an ECC error of two or Replacing Cache
[REG82001238, Bit29] more bits occurred in the two Unit (REP 02-0540)
(CTL-x, CACHE-y) cache memory boards (MP).
y : Cache memory slot #
(RKM/RKS=0-1)
H20R0x DCTL DBUF byte Writing to the outside of the 4- Gather cReplace the Control Unit Replacement 2.2.5
write error byte boundary was detected in whose CALM LED is on. Replacing Control
[REG82001238, Bit16] the ByteCnt in the PCI attribute Unit (REP 02-0390)
(CTL-x) (MP).
H20S0x DCTL PBUF SELCNT A parity error was detected in Gather
parity error the counter for the input pointer
[REG82001238, Bit15] of a buffer for writing to the
(CTL-x) cache (MP).
H20T0x DCTL CBUF A parity error was detected in Gather
SELCNT parity error the counter for the output
[REG82001238, Bit14] pointer of a buffer for writing to
(CTL-x) the cache (MP).
H20U0x DCTL register wait A parity error was detected in Gather
parity error the counter of the waiting time of
[REG82001238, Bit13] the SEQ for writing to the
(CTL-x) register (MP).

MSG 03-0050-01
Collect the error

Message
code
Trace Trace Dump
H20V0x DCTL RCLK error No response with the RCLK Gather cWhen W0100x CTL alarm Chapter 6. Warning
[REG82001238, Bit25] (CACHE-IF) signal, which was a is displayed following this Messages (MSG 06-
(CTL-x) clock signal for taking in the message, take recovery 0000)
read data, was made to the actions according to the
cache controller (MP). message.
x : Control Unit # (0-1) d Replace the Control Unit of Replacement 2.2.5
H20W0x DCTL RCLK error No response with the RCTL Gather which the CALM LED lights Replacing Control
[REG82001238, Bit24] (CACHE-IF) signal, which on except for c. Unit (REP 02-0390)
(CTL-x) showed a read response, was
made to the cache controller
(MP).
H20Y00 DCTL H0PCI The invalid split completion Gather cReplace the Control Unit Replacement 2.2.5
unexpected SPC message was detected (H #0). whose CALM LED is on. Replacing Control
detected Unit (REP 02-0390)
[REG82001280, Bit12]
H20Z00 DCTL H0PCI SPC The split completion message Gather
[REG82001280, Bit13] an error was detected (H #0).
H21000 DCTL address over The cache address over Gather
[DMA#0] occurred.
[D_PORT] occurred.
[H_PORT] occurred.
H21400 DCTL H0PCI SPC The data buffer controller LSI Gather
(H #0).
H21500 DCTL H0PCI master The data buffer controller LSI Gather
when it was a PCI slave (H #0).
H21600 DCTL H0PCI SPC The data buffer controller LSI Gather
completion message (H #0).

MSG 03-0060-01
Collect the error

Message
code
Trace Trace Dump
H21700 EDC error (Port-xy) A number of the EDC errors Gather cWhen a message, Chapter 6. Warning
exceeded its threshold value. W0100x CTL alarm is Messages (MSG 06-
x : Control Unit # (0-1) displayed following this 0000)
y : Port # (RKM/RKS=A-D) message, take a recovery Replacement 2.2.7
action according to it. Replacing Interface
Besides, replace the Board (REP 02-
interface board when doing 0660)
that.
dIn the cases other than c, Replacement 2.2.5
replace the Control Unit Replacing Control
whose CALM LED is on Unit (REP 02-0390)
and the Interface Board Replacement 2.2.7
installed in it. Replacing Interface
Board (REP 02-
0660)
H3000x DCTL ECC write A parity error was detected in Gather cWhen W0100x CTL alarm Chapter 6. Warning
parity error the ECC adding part during a is displayed following this Messages (MSG 06-
[REG82001238, Bit31] writing on the cache. message, take recovery 0000)
(CTL-x) x : Control Unit # (0-1) actions according to the
message.
H301xx ECC write parity error A parity error was detected Gather cReplace the Control Unit Replacement 2.2.5
(DMA-x) when the Cache memory was whose CALM LED is on. Replacing Control
written. Unit (REP 02-0390)
x : DMA #
H302xx ECC generate error A failure was detected in Gather
(DMA-x) generation of ECC when the
Cache memory was written.
x : DMA #
H3030x ECC uncorrectable An uncorrectable ECC failure Gather cReplace the Cache Unit. Replacement 2.2.6
error (CACHE-x) was detected when the Cache Replacing Cache
memory was read. Unit (REP 02-0540)
x : Cache memory slot # dIf not recovered, replace Replacement 2.2.5
(RKM/RKS=0-1) the above Control Unit. Replacing Control
Unit (REP 02-0390)
H304xx ECC correction failed A failure was detected when the Gather cWhen W0100x CTL alarm Chapter 6. Warning
(DMA -x) ECC correction was made is displayed following this Messages (MSG 06-
during a reading from the cache message, take recovery 0000)
memory. actions according to the
x : DMA # message.

MSG 03-0070-01
Collect the error

Message
code
Trace Trace Dump
H3050x ECC uncorrectable Processing cannot be continued Gather cReplace the Cache Unit. Replacement 2.2.6
error (CTL-x) because of uncorrectable ECC Replacing Cache
error. Unit (REP 02-0540)
x : No. of the Control Unit dIf not recovered, replace Replacement 2.2.5
which cannot continue the above Control Unit. Replacing Control
processing. Unit (REP 02-0390)
H3060x DCTL ECC generate An ECC generation error was Gather cWhen W0100x CTL alarm Chapter 6. Warning
error detected in the ECC adding part is displayed following this Messages (MSG 06-
[REG82001238, Bit30] during a writing on the cache. message, take recovery 0000)
message.
H307xy DCTL CACHE ECC During a reading from the Gather cReplace the Cache Unit. Replacement 2.2.6
uncorrectable error cache, an EC error of two or Replacing Cache
[REG82001238, Bit29] more bits occurred in a single Unit (REP 02-0540)
(CTL-x, CACHE-y) cache memory board. dIf not recovered, replace Replacement 2.2.5
x : Control Unit # (0-1) the above Control Unit. Replacing Control
y : Cache memory slot # Unit (REP 02-0390)
(RKM/RKS=0-1)
H308xy DCTL ECC correction A correction inconsistency of the Gather
failed [MPU] ECC was detected during a
[REG82001238, Bit28] readout from the cache.
(CTL-x, CACHE-y) x : Control Unit # (0-1)
(RKM/RKS=0-1)
H3090x CACHE read BUS A bus error occurred during a Gather cReplace the Control Unit Replacement 2.2.5
ERR [OTH_CTL] readout from the cache. whose CALM LED is on. Replacing Control
(CTL-x) x : Control Unit # (0-1) Unit (REP 02-0390)
H30A0x CACHE read DCTL A DCTL access error occurred Gather
access error during a readout from the cache.
[OTH_CTL] (CTL-x) x : Control Unit # (0-1)
H30B0x CACHE Cache uncorrectable error Gather cReplace the Cache Unit. Replacement 2.2.6
uncorrectable ERR x : Control Unit # (0-1) Replacing Cache
[OTH_CTL] Unit (REP 02-0540)
(CTL-x) dIf not recovered, replace Replacement 2.2.5
the above Control Unit. Replacing Control
Unit (REP 02-0390)
H30Bxy CACHE A Cache uncorrectable error Gather cReplace the Cache Replacement 2.2.6
uncorrectable ERR occurred. Memory designated in the Replacing Cache
[OTH_CTL] x : Control Unit # (0-1) message. Unit (REP 02-0540)
(CTL-x, CACHE-y) y : Cache memory slot # When the Cache Memory
(RKM/RKS=0-1) number displayed is *,
replace all the Cache
Memories mounted on the
Controller designated.

MSG 03-0080-01
Collect the error

Message
code
Trace Trace Dump
H30C0x CAHCE read DCTL A DCTL hardware error Gather cReplace the Control Unit Replacement 2.2.5
hard error [OTH_CTL] occurred during a readout from whose CALM LED is on. Replacing Control
(CTL-x) the cache. Unit (REP 02-0390)
H30D0x CACHE write BUS A bus error occurred during a Gather
ERR writing on the cache.
H30E0x CACHE write DCTL A DCTL access error occurred Gather
access error during a writing on the cache.
H30F0x CACHE write DCTL A DCTL hardware error Gather
hard error occurred during a writing on the
[OTH_CTL] (CTL-x) cache.
H30Gxx ECC uncorrectable An ECC uncorrectable error was Gather cReplace the Cache Unit. Replacement 2.2.6
error (CACHE-x) detected during reading from the Replacing Cache
cache memory. (It was highly dWhen the trouble is not Unit (REP 02-0540)
possible that the trouble that solved in spite of the
occurred between the two slots replacement of the cache
and data buffer controller LSI memory, replace all the
(D-CTL) was failures of cache Cache Unit.
memories installed in the two eIf not recovered, replace Replacement 2.2.5
slots.) the other Control Unit. Replacing Control
x : Cache memory slot # Unit (REP 02-0390)
(RKM/RKS=0-1)
H30Hxx ECC correction failed A failure was detected when the Gather
(CACHE-x/x) ECC correction was in progress
during reading from the cache
memory. (It was highly possible
that the trouble that occurred
between the two slots and data
buffer controller LSI (D-CTL)
was failures of cache memories
installed in the two slots.)
x : Cache memory slot #
(RKM/RKS=0-1)
H30Ixy CACHE A Cache uncorrectable error Gather cReplace the Cache Replacement 2.2.6
uncorrectable ERR occurred. (The slot concerned Memories designated in the Replacing Cache
[OTH_CTL] cannot be specified.) message in pairs. Unit (REP 02-0540)
(CTL-x, CACHE-y) x : Control Unit # (0-1) dIf the problem is not solved Replacement 2.2.5
y : Cache memory slot # in spite of the replacement, Replacing Control
(RKM/RKS=0-1) replace a controller in Unit (REP 02-0390)
which the cache memory
concerned is installed.

MSG 03-0090-01
Collect the error

Message
code
Trace Trace Dump
H30Jxy CACHE A Cache uncorrectable error Gather cReplace the Cache Replacement 2.2.6
uncorrectable ERR occurred. Memory designated in the Replacing Cache
[OTH_CTL] x : Control Unit # (0-1) message. Unit (REP 02-0540)
(CTL-x, CACHE-y) y : Cache memory slot # When the Cache Memory
(RKM/RKS=0-1) number displayed is *,
replace all the Cache
Memories mounted on the
Controller designated.
dIf not recovered, replace Replacement 2.2.5
the above Control Unit. Replacing Control
Unit (REP 02-0390)
H40200 DUAL I/F address An address parity error was Gather c Take recovery actions Chapter 6. Warning
parity error detected when the HP #00 according to a message Messages (MSG 06-
[INT/HP#00] wrote on a certain part in W0100x CTL alarm 0000)
[REG82001444, Bit31] another system. displayed following this
H40300 DUAL I/F write data A data parity error was detected Gather message.
parity error when the HP #00 wrote on a
[INT/HP#00] certain part in another system.
[REG82001444, Bit30]
H40400 DUAL I/F write ready A ready time-out was detected Gather cTake recovery actions Chapter 6. Warning
time-out [INT/HP#00] when the HP #00 wrote on a according to a message Messages (MSG 06-
[REG82001444, Bit29] certain part in another system. W0100x CTL alarm 0000)
displayed following this
message.
the other Control Unit. Replacing Control
Unit (REP 02-0390)
H40500 DUAL I/F CNT parity A CNT parity error was detected Gather c Take recovery actions Chapter 6. Warning
error [INT/HP#00] when the HP #00 wrote on a according to a message Messages (MSG 06-
H40700 DUAL I/F address An address parity error was Gather displayed following this
parity error detected when the HP #01 message.
[INT/HP#01] wrote on a certain part in
[REG82001444, Bit23] another system.
H40800 DUAL I/F write data A data parity error was detected Gather
parity error when the HP #01 wrote on a
[INT/HP#01] certain part in another system.
[REG82001444, Bit22]
H40900 DUAL I/F write ready A ready time-out was detected Gather cTake recovery actions Chapter 6. Warning
time-out [INT/HP#01] when the HP #01 wrote on a according to a message Messages (MSG 06-
displayed following this
message.
Unit (REP 02-0390)

MSG 03-0100-01
Collect the error

Message
code
Trace Trace Dump
H40A00 DUAL I/F CNT parity A CNT parity error was detected Gather c Take recovery actions Chapter 6. Warning
error [INT/HP#01] when the HP #01 wrote on a according to a message Messages (MSG 06-
H40C00 DUAL I/F address An address parity error was Gather displayed following this
parity error detected when the DP #00 message.
[INT/DP#00] wrote on a certain part in
H40D00 DUAL I/F write data A data parity error was detected Gather
parity error when the DP #00 wrote on a
[INT/DP#00] certain part in another system.
[REG82001440, Bit30]
H40E00 DUAL I/F write ready A ready time-out was detected Gather
time-out [INT/DP#00] when the DP #00 wrote on a
[REG82001440, Bit29] certain part in another system.
H40F00 DUAL I/F CNT parity A CNT parity error was detected Gather
error [INT/DP#00] when the DP #00 wrote on a
H40H00 DUAL I/F address An address parity error was Gather
parity error detected when the DP #01
[INT/DP#01] wrote on a certain part in
H40I00 DUAL I/F write data A data parity error was detected Gather
parity error when the DP #01 wrote on a
[INT/DP#01] certain part in another system.
[REG82001440, Bit22]
H40J00 DUAL I/F write ready A ready time-out was detected Gather
time-out [INT/DP#01] when the DP #01 wrote on a
H40K00 DUAL I/F CNT parity A CNT parity error was detected Gather
error [INT/DP#01] when the DP #01 wrote on a
H40L00 DUAL I/F clock error A clock trouble was detected in Gather cReplace the Control Unit Replacement 2.2.5
[INT/DMA#0] the DUAL_CLK from the CTL in whose CALM LED is on. Replacing Control
[REG82001228, Bit0] another system (DMA #0). dIf not recovered, replace Unit (REP 02-0390)
the other Control Unit.
H40M00 DUAL I/F address An address parity error was Gather c Take recovery actions Chapter 6. Warning
parity error detected when the DMA #0 according to a message Messages (MSG 06-
[INT/DMA#0] wrote on a certain part in W0100x CTL alarm 0000)
[REG82001448, Bit31] another system. displayed following this
H40N00 DUAL I/F write data A data parity error was detected Gather message.
parity error when the DMA #0 wrote on a
[INT/DMA#0] certain part in another system.
[REG82001448, Bit30]
H40P00 DUAL I/F write ready A ready time-out was detected Gather
time-out [INT/DMA#0] when the DMA #0 wrote on a
H40Q00 DUAL I/F CNT parity A CNT parity error was detected Gather
error [INT/DMA#0] when the DMA #0 wrote on a

MSG 03-0110-01
Collect the error

Message
code
Trace Trace Dump
H40S00 DUAL I/F address An address parity error was Gather cReplace the Control Unit Replacement 2.2.5
parity error [INT/MP] detected when the MP wrote on whose CALM LED is on. Replacing Control
[REG82001448, Bit15] a certain part in another system. Unit (REP 02-0390)
H40T00 DUAL I/F write data A data parity error was detected Gather
parity error [INT/MP] when the MP wrote on a certain
[REG82001448, Bit14] part in another system.
H40U00 DUAL I/F write ready An ADR sending ready time-out Gather cReplace the Control Unit Replacement 2.2.5
time-out [INT/MP] was detected when the MP whose CALM LED is on. Replacing Control
[REG82001448, Bit13] wrote/read on/from a certain dIf not recovered, replace Unit (REP 02-0390)
part in another system. the other Control Unit.
H40V00 DUAL I/F CNT parity A CNT parity error was detected Gather cReplace the Control Unit Replacement 2.2.5
error [INT/MP] when the MP wrote on a certain whose CALM LED is on. Replacing Control
[REG82001448, Bit12] part in another system. Unit (REP 02-0390)
H40W00 DUAL I/F read data A data parity error was detected Gather cReplace the Control Unit Replacement 2.2.5
parity error [INT/MP] when the MP read from a whose CALM LED is on. Replacing Control
[REG82001448, Bit11] certain part in another system. d If not recovered, replace Unit (REP 02-0390)
H40X00 DUAL I/F read data A data ready time-out was Gather the other Control Unit.
ready time-out detected when the MP read
[INT/MP] from a certain part in another
[REG82001448, Bit10] system.
H40Z00 DUAL I/F clock error A clock trouble of the Gather
[EXT/HP#00] DUAL_CLK was detected in the
[REG82001810, Bit1] CTL in another system.
NOTE : The ERR_ST of each
port is set when this
error occurs. (HP #00)
H41000 DUAL I/F address A parity error was detected in Gather c Take recovery actions Chapter 6. Warning
parity error the address used for access by according to a message Messages (MSG 06-
[EXT/HP#00] each port to another system. W0100x CTL alarm 0000)
[REG82001820, Bit0] displayed following this
H41100 DUAL I/F write data A parity error was detected in Gather message.
parity error write data when the HP #00 dIf not recovered, replace Replacement 2.2.5
[EXT/HP#00] wrote on a certain part in the other Control Unit. Replacing Control
[REG82001824, Bit31] another system. Unit (REP 02-0390)
H41200 DUAL I/F ECC write An ECC write parity error was Gather c Take recovery actions Chapter 6. Warning
[EXT/HP#00] wrote on the cache in another W0100x CTL alarm 0000)
[REG82001824, Bit30] system. displayed following this
H41300 DUAL I/F ECC GEN An ECC_GEN error was Gather message.
error [EXT/HP#00] detected when the HP #00
[REG82001824, Bit29] wrote on the cache in another
system.
H41400 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the HP #00
[EXT/HP#00] wrote on the cache in another
H41500 DUAL I/F WLEN A WLEN parity error was Gather
parity error detected when the HP #00

MSG 03-0120-01

MSG 03-0120-01
Collect the error

Message
code
Trace Trace Dump
H41600 DUAL I/F CNT parity A counter parity error was Gather cTake recovery actions Chapter 6. Warning
error [EXT/HP#00] detected when the HP #00 according to a message Messages (MSG 06-
[REG82001824, Bit21] wrote on the cache in another W0100x CTL alarm 0000)
system. displayed following this
message.
H41700 DUAL I/F address A cache address over was Gather cTake recovery actions Chapter 6. Warning
over [EXT/HP#00] detected when the HP #00 according to a message Messages (MSG 06-
[REG82001824, Bit25] wrote on the cache in another W0100x CTL alarm 0000)
system. displayed following this
message.
Unit (REP 02-0390)
H41800 DUAL I/F clock error A clock trouble of the Gather cReplace the Control Unit Replacement 2.2.5
[EXT/HP#01] DUAL_CLK was detected in the whose CALM LED is on. Replacing Control
[REG82001810, Bit1] CTL in another system. dIf not recovered, replace Unit (REP 02-0390)
NOTE : The ERR_ST of each the other Control Unit.
error occurs. (HP #01)
H41900 DUAL I/F address A parity error was detected in an Gather c Take recovery actions Chapter 6. Warning
parity error address of each port to which according to a message Messages (MSG 06-
[EXT/HP#01] the other system accesses. W0100x CTL alarm 0000)
H41A00 DUAL I/F write data A parity error was detected in Gather message.
parity error write data when the HP #01 dIf not recovered, replace Replacement 2.2.5
[EXT/HP#01] wrote on a certain part in the other Control Unit. Replacing Control
[REG82001824, Bit15 another system. Unit (REP 02-0390)
H41B00 DUAL I/F ECC write An ECC write parity error was Gather c Take recovery actions Chapter 6. Warning
[EXT/HP#01] wrote on the cache in another W0100x CTL alarm 0000)
[REG82001824, Bit14 system. displayed following this
H41C00 DUAL I/F ECC GEN An ECC_GEN error was Gather message.
system.
H41D00 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the HP #01
H41E00 DUAL I/F WLEN A WLEN parity error was Gather
parity error detected when the HP #01
H41F00 DUAL I/F CNT parity A counter parity error was Gather
system.

MSG 03-0130-01
Collect the error

Message
code
Trace Trace Dump
H41G00 DUAL I/F address A cache address over was Gather c Take recovery actions Chapter 6. Warning
over [EXT/HP#01] detected when the HP #01 wrote according to a message Messages (MSG 06-
[REG82001824, Bit9] on the cache in another system. W0100x CTL alarm 0000)
H41H00 DUAL I/F clock error A clock trouble of the Gather displayed following this
[EXT/DP#00] DUAL_CLK was detected in the message.
[REG82001810, Bit1] CTL in another system. dIf not recovered, replace Replacement 2.2.5
the other Control Unit.. Replacing Control
Unit (REP 02-0390)
H41I00 DUAL I/F address A parity error was detected in Gather cTake recovery actions Chapter 6. Warning
[EXT/DP#00] each port to another system. W0100x CTL alarm 0000)
[REG82001820, Bit0] NOTE : The ERR_ST of each displayed following this
port is set when this message.
error occurs. (DP #00)
H41J00 DUAL I/F write data A parity error was detected in Gather
parity error write data when the DP #00
[EXT/DP#00] wrote on a certain part in
[REG8200182C, another system.
Bit31]
H41K00 DUAL I/F ECC write An ECC write parity error was Gather
[EXT/DP#00] wrote on the cache in another
[REG8200182C, system.
Bit30]
H41L00 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXT/DP#00] detected when the DP #00
[REG8200182C, wrote on the cache in another
Bit29] system.
H41M00 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the DP #00
Bit27]
H41N00 DUAL I/F WLEN A WLEN parity error was Gather
Bit26]
H41P00 DUAL I/F CNT parity A counter parity error was Gather
Bit21] system.
H41Q00 DUAL I/F address A cache address over was Gather
over [EXT/DP#00] detected when the DP #00 wrote
[REG8200182C, on the cache in another system.
Bit25]
H41R00 DUAL I/F clock error A clock trouble of the Gather cReplace the Control Unit Replacement 2.2.5
[EXT/DP#01] DUAL_CLK was detected in the whose CALM LED is on. Replacing Control

MSG 03-0140-01
NOTE : The ERR_ST of each the other Control Unit.

MSG 03-0140-01
Collect the error

Message
code
Trace Trace Dump
H41S00 DUAL I/F address A parity error was detected in Gather cTake recovery actions Chapter 6. Warning
[EXT/DP#01] each port to another system. W0100x CTL alarm 0000)
[REG82001820, Bit0] NOTE : The ERR_ST of each displayed following this
port is set when this message.
H41T00 DUAL I/F write data A parity error was detected in Gather
parity error write data when the DP#01
[EXT/DP#01] wrote on a certain part in
[REG8200182C, another system.
Bit15]
H41U00 DUAL I/F ECC write An ECC write parity error was Gather
Bit14]
H41V00 DUAL I/F ECC GEN An ECC_GEN error was Gather
Bit13] system.
H41W00 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the DP #01
Bit11]
H41X00 DUAL I/F WLEN A WLEN parity error was Gather
Bit10]
H41Y00 DUAL I/F CNT parity A counter parity error was Gather
[REG8200182C, Bit5] wrote on the cache in another
system.
H41Z00 DUAL I/F address A cache address over was Gather
over [EXT/DP#01] detected when the DP #01
[REG8200182C, Bit9] wrote on the cache in another
system.

MSG 03-0150-01
Collect the error

Message
code
Trace Trace Dump
H42000 DUAL I/F clock error A clock trouble of the Gather cReplace the Control Unit Replacement 2.2.5
[EXT/DMA#0] DUAL_CLK was detected in the whose CALM LED is on. Replacing Control
the other Control Unit. (The
replacement cannot be
done when the subsystem
power is on.)
H42100 DUAL I/F address A parity error was detected in Gather c Take recovery actions Chapter 6. Warning
[EXT/DMA#0] each port to another system. W0100x CTL alarm 0000)
parity error write data when the DMA #0
[EXT/DMA#0] wrote on a certain part in
H42300 DUAL I/F ECC write An ECC write parity error was Gather
parity error detected when the DMA #0
[EXT/DMA#0] wrote on the cache in another
H42400 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXT/DMA#0] detected when the DMA #0
system.
H42500 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the DMA #0
parity error detected when the DMA #0
H42700 DUAL I/F CNT parity A counter parity error was Gather
error [EXT/DMA#0] detected when the DMA #0
system.
H42800 DUAL I/F address A cache address over was Gather
over [EXT/DMA#0] detected when the DMA #0
system.

MSG 03-0160-01
Collect the error

Message
code
Trace Trace Dump
H42A00 DUAL I/F address When each port accessed a Gather cReplace the Control Unit Replacement 2.2.5
parity error [EXT/MP] register of the other one of the whose CALM LED is on. Replacing Control
[REG82001820, Bit0] dual Control Unit, the data buffer d If not recovered, replace Unit (REP 02-0390)
controller LSI (D-CTL) detected the other Control Unit. (The
a parity error in the address replacement cannot be
phase. done when the subsystem
H42B00 DUAL I/F CACHE The D-CTL detected a margin Gather power is on.)
address over error when it acquired data from e If not recovered yet, call the
[EXT/DMA] the other one of the dual Control Technical Support Center
[REG82001838, Bit18] Unit. for coping with troubles.
H42C00 DUAL I/F read data A data parity error was detected Gather
parity error [EXT/MP] when the MP read from a
H42D00 DUAL I/F ECC An ECC_COR error was Gather
correction error detected when the MP read
[EXT/MP] from a certain part in another
H42E00 DUAL I/F ECC An ECC_UNCORRE error was Gather
uncorrectable error detected when the MP read
H42F00 DUAL I/F write parity A parity error was detected in Gather
error [EXT/MP] write data when the MP wrote
[REG82001838, Bit31] on a certain part in another
system.
H42G00 DUAL I/F ECC write An ECC write parity error was Gather
parity error [EXT/MP] detected when the MP wrote on
[REG82001838, Bit30] the cache in another system.
H42H00 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXT/MP] detected when the MP wrote on
H42I00 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the MP
[EXT/MP] wrote on the cache in another
H42J00 DUAL I/F WLEN A WLEN parity error was Gather
H42K00 DUAL I/F counter A counter parity error was Gather
H42L00 DUAL I/F CACHE A cache address over error was Gather
address over detected when the MP wrote on
[EXT/MP] the cache in another system.
[REG82001838, Bit25]
H42N00 DUAL I/F error An error was detected when the Gather
[MDTDCHK] MP accessed another system.
[REG82001228, Bit17]

MSG 03-0170-01
Collect the error

Message
code
Trace Trace Dump
H42Q00 DUAL I/F address An address parity error was Gather c Take recovery actions Chapter 6. Warning
parity error detected during a writing into according to a message Messages (MSG 06-
[INT/DP#02] another system performed via W0100x CTL alarm 0000)
[REG82001440, Bit15] the DP #02. displayed following this
H42R00 DUAL I/F write data A data parity error was detected Gather message.
parity error during a writing into another
[INT/DP#02] system performed via the DP
[REG82001440, Bit14] #02.
H42S00 DUAL I/F write ready A ready time-out was detected Gather
time-out [INT/DP#02] during a writing into another
[REG82001440, Bit13] system performed via the DP
#02.
H42T00 DUAL I/F CNT parity An CNT parity error was Gather
error [INT/DP#02] detected during a writing into
[REG82001440, Bit12] another system performed via
the DP #02.
H42V00 DUAL I/F address An address parity error was Gather
parity error detected during a writing into
[INT/DP#03] another system performed via
[REG82001440, Bit7] the DP #03.
H42W00 DUAL I/F write data A data parity error was detected Gather
[INT/DP#03] system performed via the DP
[REG82001440, Bit6] #03.
H42X00 DUAL I/F write ready A ready time-out was detected Gather
time-out [INT/DP#03] during a writing into another
#03.
H42Y00 DUAL I/F CNT parity A CNT parity error was detected Gather
error [INT/DP#03] during a writing into another
#03.
H42Z00 DUAL I/F clock error A clock error was detected in Gather cReplace the Control Unit Replacement 2.2.5
[EXT/DP#02] the DUAL_CLK signal sent from whose CALM LED is on. Replacing Control
[REG82001810, Bit1] a CTL of another system. (Every dIf not recovered, replace Unit (REP 02-0390)
PORT ERR_ST was set.) (DP the other Control Unit. (The
#02) replacement cannot be
power is on.)

MSG 03-0180-01
Collect the error

Message
code
Trace Trace Dump
H43000 DUAL I/F address An address parity error was Gather c Take recovery actions Chapter 6. Warning
parity error detected during DUAL access. according to a message Messages (MSG 06-
[EXT/DP#02] (DP #02) W0100x CTL alarm 0000)
parity error write data during a writing into
[EXT/DP#02] another system performed via
[REG82001830, Bit31] the DP #02.
H43200 DUAL I/F ECC write An ECC write parity error was Gather
data parity error detected during a writing onto a
[EXT/DP#02] cache of another system
[REG82001830, Bit30] performed via the DP #02.
H43300 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXT/DP#02] detected during a writing onto a
[REG82001830, Bit29] cache of another system
performed via the DP #02.
H43400 DUAL I/F CACHE A cache address parity parity Gather
address parity error error was detected during a
[EXT/DP#02] writing onto a cache of another
#02.
parity error detected during a writing onto a
H43600 DUAL I/F CNT parity A CNT parity error was detected Gather
error [EXT/DP#02] during a writing onto a cache of
the DP #02.
H43700 DUAL I/F address A cache address over error was Gather
over [EXT/DP#02] detected during a writing onto a
performed via the DP #02.
H43800 DUAL I/F clock error A clock error was detected in Gather cReplace the Control Unit Replacement 2.2.5
[EXT/DP#03] the DUAL_CLK signal sent from whose CALM LED is on. Replacing Control
[REG82001810, Bit1] a CTL of another system. (Every dIf not recovered, replace Unit (REP 02-0390)
PORT ERR_ST was set.) (DP the other Control Unit.
#03)
H43900 DUAL I/F address An address parity error was Gather cTake recovery actions Chapter 6. Warning
[EXT/DP#03] (DP #03) W0100x CTL alarm 0000)
message.

MSG 03-0190-01
Collect the error

Message
code
Trace Trace Dump
H43A00 DUAL I/F write data A parity error was detected in Gather c Take recovery actions Chapter 6. Warning
parity error write data during writing into according to a message Messages (MSG 06-
[EXT/DP#03] another system performed via W0100x CTL alarm 0000)
[REG82001830, Bit15] the DP #03. displayed following this
H43B00 DUAL I/F ECC write An ECC write parity error was Gather message.
H43C00 DUAL I/F ECC GEN An ECC_GEN error was Gather
error detected during a writing onto a
H43D00 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected during a writing
[EXT/DP#03] onto a cache of another system
H43E00 DUAL I/F WLEN A WLEN parity error was Gather
H43F00 DUAL I/F CNT parity A CNT parity error was detected Gather
error during a writing onto a cache of
[EXT/DP#03] another system performed via
[REG82001830, Bit5] the DP#03.
H43G00 DUAL I/F address A cache address over error was Gather
over detected during a writing onto a
[REG82001830, Bit9] performed via the DP# 03.
H43J00 DUAL I/F address An address parity error was Gather
parity error detected during a writing into
[INT/HP#02] another system performed via
[REG82001444, Bit15] the HP #02.
H43K00 DUAL I/F address An address parity error was Gather
parity error detected during writing into
[INT/HP#03] another system performed via
[REG82001444, Bit7] the HP #03.
H43L00 DUAL I/F write data A data parity error was detected Gather
[INT/HP#02] system performed via the HP
[REG82001444, Bit14] #02.
H43M00 DUAL I/F write data A data parity error was detected Gather
[INT/HP#03] system performed via the HP
[REG82001444, Bit6] #03.

MSG 03-0200-01
Collect the error

Message
code
Trace Trace Dump
H43N00 DUAL I/F write ready A ready time-out was detected Gather c Take recovery actions Chapter 6. Warning
time-out [INT/HP#02] during a writing into another according to a message Messages (MSG 06-
[REG82001444, Bit13] system performed via the HP W0100x CTL alarm 0000)
#02. displayed following this
H43P00 DUAL I/F write ready A ready time-out was detected Gather message.
time-out [INT/HP#03] during a writing into another dIf not recovered, replace Replacement 2.2.5
[REG82001444, Bit5] system performed via the HP the other Control Unit. Replacing Control
#03. Unit (REP 02-0390)
H43Q00 DUAL I/F CNT parity A CNT parity error was detected Gather c Take recovery actions Chapter 6. Warning
error [INT/HP#02] during a writing into another according to a message Messages (MSG 06-
[REG82001444, Bit12] system performed via the HP W0100x CTL alarm 0000)
#02. displayed following this
H43R00 DUAL I/F CNT parity A CNT parity error was detected Gather message.
error [INT/HP#03] during a writing into another
[REG82001444, Bit4] system performed via the HP
#03.
H43S00 DUAL I/F address An address parity error was Gather c Take recovery actions Chapter 6. Warning
[EXT/HP#02] (DP #02) W0100x CTL alarm 0000)
H43T00 DUAL I/F address An address parity error was Gather message.
parity error detected during DUAL access. dIf not recovered, replace Replacement 2.2.5
[EXT/HP#03] (DP #02) the other Control Unit. Replacing Control
[REG82001820, B0it0] Unit (REP 02-0390)
H43U00 DUAL I/F write data A parity error was detected in Gather
[EXT/HP#02] another system performed via
[REG82001828, Bit31] the HP #02.
H43V00 DUAL I/F write data A parity error was detected in Gather
[EXT/HP#03] another system performed via
[REG82001828, Bit15] the HP #03.
H43W00 DUAL I/F ECC write An ECC write parity error was Gather c Take recovery actions Chapter 6. Warning
data parity error detected during a writing onto a according to a message Messages (MSG 06-
[EXT/HP#02] cache of another system W0100x CTL alarm 0000)
[REG82001828, Bit30] performed via the HP #02. displayed following this
H43X00 DUAL I/F ECC write An ECC write parity error was Gather message.
[EXT/HP#03] cache of another system
[REG82001828, Bit14] performed via the HP #03.
H43Y00 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXT/HP#02] detected during a writing onto a
performed via the HP #02.
H43Z00 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXT/HP#03] detected during a writing onto a
performed via the HP #02.

MSG 03-0210-01
Collect the error

Message
code
Trace Trace Dump
H44000 DUAL I/F CACHE A cache address parity error Gather c Take recovery actions Chapter 6. Warning
address parity error was detected during a writing according to a message Messages (MSG 06-
[EXT/HP#02] onto a cache of another system W0100x CTL alarm 0000)
[REG82001828, Bit27] performed via the HP #02. displayed following this
H44100 DUAL I/F CACHE A cache address parity error Gather message.
address parity error was detected during a writing
[EXT/HP#03] onto a cache of another system
H44300 DUAL I/F WLEN A WLEN parity error was
error [EXT/HP#02] during a writing onto a cache of
the HP #02.
error [EXT/HP#03] during a writing onto a cache of
the HP #03.
H44600 DUAL I/F address A cache address over error was Gather c Take recovery actions Chapter 6. Warning
over [EXT/HP#02] detected during a writing onto a according to a message Messages (MSG 06-
[REG82001828, Bit25] cache of another system W0100x CTL alarm 0000)
performed via the HP #02. displayed following this
H44700 DUAL I/F address A cache address over error was Gather message.
over [EXT/HP#03] detected during a writing onto a dIf not recovered, replace Replacement 2.2.5
[REG82001828, Bit9] cache of another system the other Control Unit. (The Replacing Control
performed via the HP #03. replacement cannot be Unit (REP 02-0390)
power is on.)
H44800 DUAL I/F ready error The EXT_IORDY became 0. Gather cReplace the Control Unit Replacement 2.2.5
[INT/MP] whose CALM LED is on. Replacing Control
[REG82001454, Bit21] Unit (REP 02-0390)

MSG 03-0220-01
Collect the error

Message
code
Trace Trace Dump
H44900 DUAL I/F write ready A ready time-out was detected Gather cReplace the Control Unit Replacement 2.2.5
error [INT/HP#00] in the HP #00 when the DCTL of whose CALM LED is on. Replacing Control
[REG82001454, Bit21] the other system was reset. d If not recovered, replace Unit (REP 02-0390)
H44A00 DUAL I/F write ready A ready time-out was detected Gather the other Control Unit. (The
error [INT/HP#01] in the HP #01 when the DCTL of replacement cannot be
[REG82001454, Bit21] the other system was reset. done when the subsystem
H44B00 DUAL I/F write ready A ready time-out was detected Gather power is on.)
error [INT/HP#02] in the HP #02 when the DCTL of e If not recovered yet, call the
[REG82001454, Bit21] the other system was reset. Technical Support Center
H44C00 DUAL I/F write ready A ready time-out was detected Gather for coping with troubles.
error [INT/HP#03] in the HP #03 when the DCTL of
[REG82001454, Bit21] the other system was reset.
H44D00 DUAL I/F write ready A ready time-out was detected Gather
error [INT/DP#00] in the DP #00 when the CTL of
H44E00 DUAL I/F write ready A ready time-out was detected Gather
H44F00 DUAL I/F write ready A ready time-out was detected Gather
H45000 DUAL I/F write ready A ready time-out was detected Gather
H45100 DUAL I/F write ready A ready time-out was detected Gather
error [INT/DMA#0] in the DMA #0 when the CTL of
H46000 DUAL I/F write ready A time-out was detected during Gather c Take recovery actions Chapter 6. Warning
error [INT/DMA#00] the impedance adjustment of according to a message Messages (MSG 06-
[REG82001428, Bit21] the Control Unit in the other W0100x CTL alarm 0000)
system (HP #00). displayed following this
H46100 DUAL I/F write ready A time-out was detected during Gather message.
error [INT/HP#01] the impedance adjustment of d If not recovered, replace Replacement 2.2.5
[REG82001428, Bit21] the Control Unit in the other the other Control Unit. (The Replacing Control
system (HP #01). replacement cannot be Unit (REP 02-0390)
H46200 DUAL I/F write ready A time-out was detected during Gather done when the subsystem
error [INT/HP#02] the impedance adjustment of power is on.)
[REG82001428, Bit21] the Control Unit in the other
system (HP #02).
H46300 DUAL I/F write ready A time-out was detected during Gather
error [INT/HP#03] the impedance adjustment of
[REG82001428, Bit21] the Control Unit in the other
system (HP #03).
H46900 DUAL I/F The SELF_IORDY changed Gather cReplace the Control Unit Replacement 2.2.5
SELF_IORDY from RDY to NotRDY (MP). whose CALM LED is on. Replacing Control
changed RDY into Unit (REP 02-0390)
NotRDY [INT/MP]
[REG82001428, Bit28]

MSG 03-0230-01
Collect the error

Message
code
Trace Trace Dump
H46A00 DUAL I/F The EXT_IORDY changed from Gather cReplace the Control Unit Replacement 2.2.5
EXT_IORDY changed RDY to NotRDY (MP). whose CALM LED is on. Replacing Control
RDY into NotRDY Unit (REP 02-0390)
[INT/MP]
[REG82001428, Bit26]
H46B00 DUAL I/F MRGN The data buffer controller LSI Gather
error [INT/MP] (D-CTL) detected a margin error
[REG82001484, Bit2] when it acquired data from the
other one of the dual Control
Unit.
H46C00 DUAL I/F SEQ error The control signal when data Gather
[INT/MP] buffer controller LSI (D-CTL)
[REG82001484, Bit1] takes data from the other one of
the dual Control Unit was not a
regular procedure.
H46D00 DUAL I/F DCNT error The delay counter exceeded the Gather
[INT/MP] allowable delay limit of the delay
[REG82001484, Bit0] element.
H46E00 DUAL I/F RCLK error The RCLK error was detected Gather
[EXT/MP] during a reading from the cache
[REG82001838, Bit23] of the other one of the dual
Control Unit of the MP.
H46F00 DUAL I/F RCTL error The RCTL error was detected Gather
H46G00 DUAL I/F SLV error An error in the other one of the Gather
[INT/MP] dual Control Unit was reported.
[REG82001484, Bit3]

MSG 03-0240-01
Collect the error

Message
code
Trace Trace Dump
H50200 BRG CPU address A CPU address out of range Gather cReplace the Control Unit Replacement 2.2.5
out of range occurred. [BRG] whose CALM LED is on. Replacing Control
[REGF1000140, Bit0] Unit (REP 02-0390)
H50300 BRG CPU bad The CPU-PCI bridge LSI Gather cWhen W0100x CTL alarm Chapter 6. Warning
address parity detected an illegal parity in the is displayed following this Messages (MSG 06-
detected address phase. message, take recovery 0000)
[REGF1000140, Bit1] actions according to the
message.
H50400 BRG CPU transfer A transfer type violation Gather cReplace the Control Unit Replacement 2.2.5
type violation occurred. [BRG] whose CALM LED is on. Replacing Control
[REGF1000140, Bit2] Unit (REP 02-0390)
H50500 BRG CPU transfer The CPU-PCI bridge LSI Gather cWhen W0100x CTL alarm Chapter 6. Warning
type violation detected a contravention of the is displayed following this Messages (MSG 06-
[REG14000140, Bit2] transfer type. message, take recovery 0000)
message.
H50600 BRG CPU write to a A writing on a write-protected Gather cReplace the Control Unit Replacement 2.2.5
write protected region region occurred. [BRG CPU] whose CALM LED is on. Replacing Control
[REGF1000140, Bit4] Unit (REP 02-0390)
H50700 BRG CPU read from A readout from a caching- Gather
a caching protected protected region occurred. [ERG
region CPU]
[REGF1000140, Bit5]
H5080x BRG CPU bad write The bad write data parity was Gather c When W0100x CTL alarm Chapter 6. Warning
data parity detected detected. [BRG CPU] is displayed following this Messages (MSG 06-
[REG14000140, Bit6] x : Control Unit # (0-1) message, take recovery 0000)
(CTL-x) actions according to the
BRG CPU bad write message.
data parity detected dReplace the Control Unit of Replacement 2.2.5
[REGF1000140, Bit6] which the CALM LED lights Replacing Control
(CTL-x) on except for c. Unit (REP 02-0390)
H5090x BRG CPU bad read The bad read data parity was Gather
data parity detected detected. [BRG CPU]
[REG14000140, Bit7]
(CTL-x)
BRG CPU bad read
data parity detected
[REGF1000140, Bit7]
(CTL-x)

MSG 03-0250-01
Collect the error

Message
code
Trace Trace Dump
H50A00 BRG PCI0 PCI The PCI transaction was Gather cWhen W0100x CTL alarm Chapter 6. Warning
transaction generated generated while the master PCI is displayed following this Messages (MSG 06-
while master is was disabled. [BRG CPU0] message, take recovery 0000)
disabled actions according to the
[REGF1001D58, Bit10] message.
H50B0x BRG PCI0 the PCI The PCI slave detected the bad dReplace the Control Unit of Replacement 2.2.5
slave detected bad write data parity. [BRG PCI0] which the CALM LED lights Replacing Control
write data parity x : Control Unit # (0-1) on except for c. Unit (REP 02-0390)
[REG14001D58, Bit1]
(CTL-x)
BRG PCI0 PCI slave The PCI slave detected the bad Gather
detected bad write write data parity. [BRG PCI0]
data parity x : Control Unit # (0-1)
[REGF1001D58, Bit1]
(CTL-x)
H50C0x BRG PCI0 PERR The PERR response to read Gather cReplace the Control Unit Replacement 2.2.5
response to read data data by the PCI slave occurred. whose CALM LED is on. Replacing Control
driven by PCI slave [BRG PC10] Unit (REP 02-0390)
[REGF1001D58, Bit2] x : Control Unit # (0-1)
(CTL-x)
H50D00 BRG PCI0 slave The PCI slave detected a read Gather cWhen W0100x CTL alarm Chapter 6. Warning
detected read error in error in a transfer of the split is displayed following this Messages (MSG 06-
Split Completion completion. message, take recovery 0000)
transaction actions according to the
[REGF1001D58, Bit23] message.
H50E00 BRG PCI0 PERR The CPU-PCI bridge detected Gather dReplace the Control Unit of Replacement 2.2.5
response to write that the transfer of write data which the CALM LED lights Replacing Control
data driven by the output by the PCI master being on except for c. Unit (REP 02-0390)
PCI master responded with the PERR.
[REG14001D58, Bit5]
H50F0x BRG PCI0 bad data A Bad data parity was Gather cReplace the Control Unit Replacement 2.2.5
parity detected during detected when the PCI master whose CALM LED is on. Replacing Control
a PCI master read was being read. [BRG PCIO] Unit (REP 02-0390)
[REGF1001D58, Bit6] x : Control Unit # (0-1)
(CTL-x)
H50G00 BRG PCI0 the PCI The PCI master generated the Gather c When W0100x CTL alarm Chapter 6. Warning
master generated master abort. [BGR PCIO] is displayed following this Messages (MSG 06-
master abort message, take recovery 0000)
[REG14001D58, Bit8] actions according to the
H50H00 BRG PCI0 the PCI The PCI master detected the Gather message.
master detected target abort. [BRG PCIO] dReplace the Control Unit of Replacement 2.2.5
target abort which the CALM LED lights Replacing Control
[REG14001D58, Bit9] on except for c. Unit (REP 02-0390)
H50I00 BRG PCI0 PCI The PCI master received the Gather
master received split completion the length of
incorrect split which (number of bytes) does
completion not conform to the original
[REGF1001D58, Bit13] requirement.

MSG 03-0260-01
Collect the error

Message
code
Trace Trace Dump
H50J00 BRG PCI0 the PCI The CPU-PCI bridge detected Gather c When W0100x CTL alarm Chapter 6. Warning
master reached retry the number of retries made by is displayed following this Messages (MSG 06-
counter limit the PCI master reaching the message, take recovery 0000)
[REG14001D58, Bit11] limit. actions according to the
H50K00 BRG PCI0 PCI The CPU-PCI bridge detected Gather message.
master split the split completion discard dReplace the Control Unit of Replacement 2.2.5
completion discard timer of the PCI master which the CALM LED lights Replacing Control
timer expired exceeding the time limit on except for c. Unit (REP 02-0390)
[REGF1001D58, Bit12]
H50L00 BRG PCI0 the PCI The PCI slave generated the Gather
slave terminates a target abort.
transaction with target
abort
[REG14001D58, Bit17]
H50P00 BRG PCI0 a PCI The CPU-PCI bridge detected Gather
slave read buffer the read buffer discard timer of
discard timer expired the PCI slave exceeding the
[REG14001D58, Bit20] time limit.
H50Q00 BRG PCI0 internal The internal PCI arbiter detected Gather
PCI arbiter detection the PCI master being out of
of a broken master order.
[REG14001D58, Bit21]
H50R00 BRG PCI0 PCI BIST A PCI BIST interrupt occurred. Gather cReplace the Control Unit Replacement 2.2.5
interrupt [BRG PCIO] whose CALM LED is on. Replacing Control
[REGF1001D58, Bit24] Unit (REP 02-0390)
H50S00 BRG PCI0 PCI power A PCI Power Management Gather
management interrupt Interrupt occurred. [BRG PCIO]
H50T00 BRG PCI0 PCI reset A PCI Reset Assert occurred. Gather
assert [BRG PCIO]
H50X00 BRG PCI1 the PCI The PCI slave detected a bad Gather
slave detected bad write data parity. [BRG PCI1]
write data parity
[REGF1001DD8,
Bit1]
H50Y00 BRG PCI1 PERR The PERR response to address Gather
response to read data made by the PCI slave
driven by PCI master occurred. [BRG PCI1]
[REGF1001DD8,
Bit2]

MSG 03-0270-01
Collect the error

Message
code
Trace Trace Dump
H51000 BRG PCI1 PERR The PERR response to write Gather cReplace the Control Unit Replacement 2.2.5
response to write data made by the PCI master whose CALM LED is on. Replacing Control
data driven by the occurred. [BRG PCI1] Unit (REP 02-0390)
PCI master
[REGF1001DD8,
Bit5]
H51100 BRG PCI1 bad data A bad data parity was detected Gather
parity detected during during a reading performed by
the PCI master read the PCI master. [BRG PCI1]
[REGF1001DD8,
Bit6]
H51200 BRG PCI1 the PCI The master abort occurred in Gather
master generated the PCI master. [BRG PCI1]
master abort
[REGF1001DD8,
Bit8]
H51300 BRG PCI the PCI The PCI master detected the Gather
master detected target abort. [BRG PCI1]
target abort
[REGF1001DD8,
Bit9]
H51500 BRG PCI1 the PCI The threshold value of the retry Gather
master reached retry counter was exceeded in the
counter limit PCI master. [BRG PCI1]
[REGF1001DD8,
Bit11]
H51700 BRG PCI1 the PCI The PCI slave terminated a Gather
slave terminates a transaction with the target abort.
transaction with target [BRG PCI1]
abort
[REGF1001DD8,
Bit17]
H51A00 BRG PCI1 a PCI The read buffer discard timer Gather
slave read buffer expired occurred in the PCI
discard timer expired slave. [BRG PCI1]
[REGF1001DD8,
Bit20]
H51B00 BRG PCI1 internal The Internal PCI arbiter Gather
PCI arbiter detection detection of a broken master
of a broken master occurred. [BRG PCI1]
[REGF1001DD8,
Bit21]
H51C00 BRG PCI1 PCI BIST The PCI BIST interrupt Gather
interrupt occurred. [BRG PCI1]
[REGF1001DD8,
Bit22]
H51D00 BRG PCI1 power The PCI Power Management Gather
management interrupt Interrupt occurred. [BRG PCI1]
[REGF1001DD8,
Bit23]

MSG 03-0280-01
H51E00 BRG PCI1 reset The PCI Reset Assert occurred. Gather
assert [BRG PCI1]
[REGF1001DD8,
Bit24]

MSG 03-0280-01
Collect the error

Message
code
Trace Trace Dump
H51F00 BRG PCI0 DWORD It was detected that CPU-PCI Gather c When W0100x CTL alarm Chapter 6. Warning
boundary error bridge LSI attempts to issue the is displayed following this Messages (MSG 06-
[REGF1001D58, Bit4] transfer exceeding the DWORD message, take recovery 0000)
boundary. actions according to the
H51G0x BRG PCI0 internal An internal data path error was Gather message.
data path error in the detected in the PCI interface. dReplace the Control Unit of Replacement 2.2.5
PCI interface x : Control Unit # (0-1) which the CALM LED lights Replacing Control
[REGF1001D58, Bit0] on except for c. Unit (REP 02-0390)
(CTL-x)
H51H0x BRG CPU punit An internal data path parity error Gather
internal data path was detected in the CPU
parity error detected interface.
[REGF1000140, Bit8] x : Control Unit # (0-1)
(CTL-x)
H51J00 BRG PCI0 slave as a The PCI slave detected the Gather
completer detected target abort as a completer of
target abort the data transfer.
H51K00 BRG PCI0 slave The PCI slave generated the Gather
generated master master abort as a completer of
abort as a completer the data transfer.
H51L00 BRG PCI0 retry The number of retries made by Gather
counter of a PCI slave the PCI slave reached its limit
reached its limit when the PCI slave was about
[REGF1001D58, Bit22] to generate the split completion.
H51M00 BRG PCI0 master The PCI master received a Gather
received message message error.
error
H51N00 BRG PCI0 master The PCI master generated the Gather
generated target abort target abort in response to the
for split completion split completion.
[REGF1001D58, Bit7]

MSG 03-0290-01
Collect the error

Message
code
Trace Trace Dump
H70000 E-CTL access error Write access to a read area Gather cReplace the Control Unit Replacement 2.2.5
[READ_AREA_ occurred. whose CALM LED is on. Replacing Control
WRITE_ERR] Unit (REP 02-0390)
[REGF0002009, Bit7]
H70100 E-CTL MEM address An address parity error occurred Gather
parity error when the ECTL internal RAM
[REGF0002009, Bit6] was accessed.
H70200 E-CTL SH detected An excess of time occurred Gather
time-over when the ECTL internal RAM
[REGF000202E, Bit4] was accessed from the SH
microprogram.
H70300 E-CTL SH CNT parity An error occurred in the CMD Gather
error counter on the SH
[REGF000202E, Bit3] microprogram side.
H70400 E-CTL SH MEM read A read data parity error occurred Gather
data parity error during a reading from the ECTL
[REGF000202E, Bit2] internal RAM performed by the
SH microprogram.
H70500 E-CTL SH MEM A address parity error occurred Gather
address parity error during a reading from the ECTL
[REGF000202E, Bit1] internal RAM performed by the
SH microprogram.
H70600 E-CTL SH access The SH microprogram made Gather
error write access to a read area of
[SH_READ_AREA_ the ECTL internal RAM (write
WRITE_ERR] area of the main microprogram).
[REGF000202E, Bit0]
H70700 E-CTL D_CMT parity A parity error occurred in a Gather
error counter that detects difference
[REGF0002009, Bit3] between data of the main
microprogram CMD counter and
the counter on the SH side.
H70800 E-CTL CNT parity A parity error occurred in the Gather
error CMD counter.
[REGF0002009, Bit2]
H70900 E-CTL access error The CMD information was Gather
[CMD_OVWT] overwritten throughout.
[REGF0002009, Bit1]
H70A00 E-CTL RAM parity A parity error occurred during a Gather
error reading from the ECTL internal
[REGF0002009, Bit0] RAM.

MSG 03-0300-01
Collect the error

Message
code
Trace Trace Dump
H90210 CTL failure The Control Unit was blocked Gather cReplace the Control Unit Replacement 2.2.5
whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
H90320 Watch-dog time-out A watchdog time-out occurred. Gather cBecause it is possible that
the cache memory has
become out of order,
replace it according to a
judgment to be made
through the following
operation.
Make the operation mode
Maintenance mode and
connect Storage Navigator
Modular to the subsystem.
Display the cache memory
failure statistical information
by selecting the Cache
Memory tab on the
Statistical Information
panel displayed in the
Array System View
window through the
sequential selections of
Tool and Statistical
Information in the window.
Then get the total number
of occurrence of
correctable errors.
When the accumulated Replacement 2.2.5
occurrence number of Replacing Control
correctable errors is not Unit (REP 02-0390)
0:
Replace the Control Unit Replacement 2.2.6
of which CALM LED lights Replacing Cache
on and the Cache Unit (REP 02-0540)
memory on the Control
Unit concerned.
When the accumulated
occurrence number of
correctable errors is 0:
Replace the Control Unit
of which CALM LED lights
on.
H90330 Connection unit The number of connected units Gather cCheck that five or more
excess exceeded limit. units are not connected.
H90400 Obstacle is detected Failures were detected in the cReplace the Control Unit Replacement 2.2.5
by two or more SENC two or more SENCs. whose CALM LED is on. Replacing Control
Unit (REP 02-0390)

MSG 03-0310-01
Collect the error

Message
code
Trace Trace Dump
HA0100 CUDG error A CUDG error was detected Gather cSolve the failure according Message Chapter 2.
during the start-up operation. to the CUDG detection CUDG Detected
(RAM CUDG) message indicated before Messages (MSG 02-
the message. 0000)
HA020x RTC alarm (CTL-x) A RTC failure occurred or the Gather cReplace the Control Unit Replacement 2.2.5
RTC battery was used up. whose CALM LED is on. Replacing Control
x : Control Unit # (0-1) Unit (REP 02-0390)
HA0310 IDMA transfer time- IDMA transfer time-out Gather
out occurred. (2 msec)
HA0311 IDMA retry error IDMA failed in retry. Gather
HA0312 IDMA multiple run The system was running when Gather
IDMA was started.
HA0313 IDMA stop time-out IDMA forced stop time-out Gather
occurred. (2 msec)
HA042x FLASH write error Writing in flash memory failed. Gather
(FM1-x) x : Chip information that
caused the error
(0=FM1-0, 1=FM1-1,
2=FM both chips)
HA0530 SERIAL open error An OPEN error was caused by Gather cReplace the RS232C cable.
RS232C.
dReplace the Control Unit Replacement 2.2.5
Unit (REP 02-0390)
HA0531 SOCKET open error An OPEN error was caused by Gather cReplace the LAN cable.
the socket.
HA0532 ACCEPT open error An OPEN error was caused by Gather dReplace the Control Unit Replacement 2.2.5
the accept. whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
HB0210 Target abort INT The target abortion INT status is Gather cReplace the Control Unit Replacement 2.2.5
status error illegal. whose CALM LED is on. Replacing Control
HB0421 H-FPC PCI STS REG A master abortion occurred Gather Unit (REP 02-0390)
error [RMA] when Tachyon made a master
access to the PCI.
HB0522 H-FPC PCI STS REG Tachyon PCI Status Reg error. Gather
error [DPE] (DPE)
HB0623 H-FPC PCI INT STS An access was attempted in Gather
REG err [UBE] units of other than four bytes to
the Tachyon Chip resistor
disregarding that accesses to
which must be done in units of
four bytes.

MSG 03-0320-01
Collect the error

Message
code
Trace Trace Dump
HB0800 Command end INI An illegal operation, in which an Gather cReplace the Control Unit Replacement 2.2.5
INT status error interruption to terminate the whose CALM LED is on. Replacing Control
execution of the command Unit (REP 02-0390)
issued from the local DF to the
remote DF occurred though
there was no table concerned,
occurred.
HB0900 Target abort INI INT Inconsistency of termination Gather
status error status of a command issued
from the local DF to the remote
DF occurred. (Tachyon detected
a target abortion whereas the
DMA did not.)
HB0A0x H-FPC hardware Operations which the Tachyon Gather
error (Port-x) DX2 did not expect occurred
more times than the threshold
value.
x : Port #
(RKM/RKS=A-B)
HB0B0x H-FPC soft reset has A soft reset of the H-FPC failed. Gather
ended in failure x : Port #
(Port-x) (RKM/RKS=A-B)
HB0Cxx H-FPC is not Though the Interface Board is Gather cReplace the interface board Replacement 2.2.6
detected (Port-xy) installed, the HFPC cannot be in which the port concerned Replacing Cache
recognized on the PCI. is installed. Unit (REP 02-0540)
x : Control Unit # (0-1) dWhen the trouble is not Replacement 2.2.5
y : Code solved, replace the Control Replacing Control
z : Object port # Unit in which the interface Unit (REP 02-0390)
(multiple ports available) board concerned is
(y : z) = (1 : A) installed.
(2 : B)
(3 : A, B)
(4 : C)
(5 : A, C)
(6 : B, C)
(7 : A, B, C)
(8 : D)
(9 : A, D)
(A : B, D)
(B : A, B, D)
(C : C, D)
(D : A, C, D)
(E : B, C, D)
(F : A, B, C, D)

MSG 03-0330-01
Collect the error

Message
code
Trace Trace Dump
HB0Dyy FPC is not detected The detection of the FPC failed. Gather cWhen W0100x CTL alarm Chapter 6. Warning
(CTL-x) x : Control Unit # (0-1) is displayed following this Messages (MSG 06-
y : Code message, take recovery 0000)
z : Chip error code
(y:z) =
(01 : Path-0) message.
(02 : Path-1) dReplace the Control Unit of Replacement 2.2.5
(03 : Path-0/1) which the CALM LED lights Replacing Control
(04 : Path-2) on except for c. Unit (REP 02-0390)
(05 : Path-0/2)
(06 : Path-1/2)
(07 : Path-0/1/2)
(08 : Path-3)
(09 : Path-0/3)
(0A : Path-1/3)
(0B : Path-0/1/3)
(0C : Path-2/3)
(0D : Path-0/2/3)
(0E : Path-1/2/3)
(0F : Path-0/1/2/3)
(10 : Port-0A)
(11 : Path-0/PortA)
HD0100 DFPC error over The Control Unit was blocked Gather cReplace the Control Unit Replacement 2.2.5
[DFPCINM] since the failure of D-FPC whose CALM LED is on. Replacing Control
exceeded the threshold value. Unit (REP 02-0390)
HD020x D-FPC hardware A soft reset of the D-FPC failed. Gather
error (Path-x, Code-y) x : Path #
(RKM/RKS=0-1)
y : Detailed code
HD0300 D-FPC detected PCI The D-FPC detected a PCI Gather cWhen W0100x CTL alarm Chapter 6. Warning
error error. is displayed following this Messages (MSG 06-
message, take recovery 0000)
message.
HD1100 HDU CDB check The Control Unit was blocked Gather cReplace the Control Unit Replacement 2.2.5
code error since the retry NG occurred in whose CALM LED is on. Replacing Control
[RETRY] the drive check code. Unit (REP 02-0390)
HD1200 HDU CDB check The Control Unit was blocked Gather
code error since the drive check code
[OVER] exceeded the threshold value.
HD21xx Host transfer DMA The number of DMA hardware Gather cWhen W0100x CTL alarm Chapter 6. Warning
error over failure occurrences exceeded its is displayed following this Messages (MSG 06-
(DMA-x) threshold value in the host message, take recovery 0000)
transfer. [CTL blockade factor] actions according to the
x : DMA# (0-1) message.

MSG 03-0340-01
Collect the error

Message
code
Trace Trace Dump
HD220x CACHE error over The number of cache Gather cReplace the Cache Unit. Replacement 2.2.6
(CACHE-x) correctable error occurrences Replacing Cache
[CRECT] exceeded its threshold value in Unit (REP 02-0540)
the DMA transfer. (during the dIf not recovered, replace Replacement 2.2.5
dual system operation) the above Control Unit. Replacing Control
x : Cache memory slot # Unit (REP 02-0390)
(RKM/RKS=0-1)
HD230x Buffer to Cache copy A failure occurred in a copying Gather cReplace the Control Unit Replacement 2.2.5
failed (CTL-x) between the buffer and cache. whose CALM LED is on. Replacing Control
x : Control Unit # (0-1) Unit (REP 02-0390)
HD2400 DRR time-out A time-out of the waiting for Gather
DRR completion occurred.
HD250x Data pool init error An error occurred in a CTL in Gather
other (CTL-x) the other system owing to a pool
initialization by the DMA.
HD260x Data pool init error An error occurred in a CTL in Gather
self (CTL-x) the self system owing to a pool
initialization by the DMA.
HD27xx Drive transfer DMA Number of DMA hardware Gather cSee Troubleshooting Troubleshooting
error over failures concerning data transfer 6.1.12 A failure occurred 6.1.12 A failure
(DMA-x) to a drive exceeded the during operation : Case 2 occurred during
threshold value. (LA/LRC error). operation : Case 2
x : DMA number (0 or 1) (LA/LRC error)
(TRBL 06-0570)
HD2800 DUAL I/F The I/O Not Ready of the self Gather cReplace the Control Unit Replacement 2.2.5
SELF_IORDY system was detected (HP #00). whose CALM LED is on. Replacing Control
changed to NotRDY d If not recovered, replace Unit (REP 02-0390)
[INT/HP#00] the other Control Unit. (The
[REG82001428, Bit28] replacement cannot be
HD2900 DUAL I/F The I/O Not Ready of the self Gather done when the subsystem
SELF_IORDY system was detected (HP #01). power is on.)
changed to NotRDY eIf not recovered yet, call the
[INT/HP#01] Technical Support Center
[REG82001428, Bit28] for coping with troubles.
HD2A00 DUAL I/F The I/O Not Ready of the self Gather
SELF_IORDY system was detected (HP #02).
changed to NotRDY
[INT/HP#02]
[REG82001428, Bit28]
HD2B00 DUAL I/F The I/O Not Ready of the self Gather
SELF_IORDY system was detected (HP #03).
changed to NotRDY
[INT/HP#03]
[REG82001428, Bit28]

MSG 03-0350-01
Collect the error

Message
code
Trace Trace Dump
HD2C00 DUAL I/F The I/O Not Ready of the other Gather cReplace the Control Unit Replacement 2.2.5
EXT_IORDY changed system was detected (HP #00). whose CALM LED is on. Replacing Control
to NotRDY d If not recovered, replace Unit (REP 02-0390)
[INT/HP#00] the other Control Unit. (The
[REG82001428, Bit26] replacement cannot be
HD2D00 DUAL I/F The I/O Not Ready of the other Gather done when the subsystem
EXT_IORDY changed system was detected (HP #01). power is on.)
to NotRDY eIf not recovered yet, call the
[INT/HP#01] Technical Support Center
[REG82001428, Bit26] for coping with troubles.
HD2E00 DUAL I/F The I/O Not Ready of the other Gather
EXT_IORDY changed system was detected (HP #02).
to NotRDY
[INT/HP#02]
[REG82001428, Bit26]
HD2F00 DUAL I/F The I/O Not Ready of the other Gather
EXT_IORDY changed system was detected (HP #03).
to NotRDY
[INT/HP#03]
[REG82001428, Bit26]
HD3000 DUAL I/F MRGN After the Control Unit in the Gather
error [INT/HP#00] other system adjusted the data
[REG82001484, Bit2] input timing while it was
sending/receiving data to/from
the Control Unit in the self
system, the Control Unit in the
self system detected a margin
error. (HP #00) [Failure in the
bus between the CTLs]

MSG 03-0360-01
Collect the error

Message
code
Trace Trace Dump
HD3300 DUAL I/F MRGN After the Control Unit in the Gather cReplace the Control Unit Replacement 2.2.5
error [INT/HP#03] other system adjusted the data whose CALM LED is on. Replacing Control
[REG82001484, Bit2] input timing while it was dIf not recovered, replace Unit (REP 02-0390)
sending/receiving data to/from the other Control Unit. (The
the Control Unit in the self replacement cannot be
system, the Control Unit in the done when the subsystem
self system detected a margin power is on.)
error. (HP #03) [Failure in the e If not recovered yet, call the
bus between the CTLs] Technical Support Center
HD3400 DUAL I/F SEQ error When the Control Unit in the self Gather for coping with troubles.
[INT/HP#00] system adjusted the data input
[REG82001484, Bit1] timing during data
sending/reception to/from the
Control Unit in the other system,
it detected a sequence error.
(HP #00) [Failure in the bus
between the CTLs]
HD3500 DUAL I/F SEQ error When the Control Unit in the self Gather
between the CTLs]
between the CTLs]
between the CTLs]
HD3800 DUAL I/F DCNT error A delay counter error in de-skew Gather
[INT/HP#00] control of the other system was
[REG82001484, Bit0] detected (HP #00).
HD3900 DUAL I/F DCNT error A delay counter error in de-skew Gather
[INT/HP#01] control of the other system was
[REG82001484, Bit0] detected (HP #01).

MSG 03-0370-01
Collect the error

Message
code
Trace Trace Dump
HD3A00 DUAL I/F DCNT error A delay counter error in de-skew Gather cReplace the Control Unit Replacement 2.2.5
[INT/HP#02] control of the other system was whose CALM LED is on. Replacing Control
[REG82001484, Bit0] detected (HP #02). d If not recovered, replace Unit (REP 02-0390)
HD3B00 DUAL I/F DCNT error A delay counter error in de-skew Gather the other Control Unit. (The
[INT/HP#03] control of the other system was replacement cannot be
[REG82001484, Bit0] detected (HP #03). done when the subsystem
HD3C00 DUAL I/F SLV error A de-skew error in the other Gather power is on.)
[INT/HP#00] system was detected (HP #00). e If not recovered yet, call the
[REG82001484, Bit3] Technical Support Center
HD3D00 DUAL I/F SLV error A de-skew error in the other Gather for coping with troubles.
[INT/HP#01] system was detected (HP #01).
[REG82001484, Bit3]
HD3E00 DUAL I/F SLV error A de-skew error in the other Gather
[REG82001484, Bit3]
HD3F00 DUAL I/F SLV error A de-skew error in the other Gather
[REG82001484, Bit3]
HD4000 DUAL I/F The SELF_IORDY changed Gather
SELF_IORDY from RDY to NotRDY (DMA #0).
changed to NotRDY
[INT/DMA#0]
[REG82001428, Bit28]
HD4100 DUAL I/F The EXT_IORDY changed from Gather cReplace the Control Unit Replacement 2.2.5
EXT_IORDY change RDY to NotRDY (DMA #0). whose CALM LED is on. Replacing Control
to NotRDY Unit (REP 02-0390)
[INT/DMA#0]
[REG82001428, Bit26]
HD4200 DUAL I/F SLV error An error was reported from the Gather
[INT/DMA#0] other Control Unit (DMA #0).
[REG82001484, Bit3]
error [INT/DMA#0] other system adjusted the data
error. (DMA #0) [Failure in the
[INT/DMA#0] system adjusted the data input
(DMA #0) [Failure in the bus
between the CTLs]

MSG 03-0380-01
Collect the error

Message
code
Trace Trace Dump
HD4500 DUAL I/F DCNT error The delay counter exceeded the Gather cReplace the Control Unit Replacement 2.2.5
[INT/DMA#0] allowable delay limit of the delay whose CALM LED is on. Replacing Control
[REG82001484, Bit0] element (DMA #0). Unit (REP 02-0390)
SELF_IORDY change from RDY to NotRDY (DP #00).
to NotRDY
[INT/DP#00]
[REG82001428, Bit28]
to NotRDY
[INT/DP#01]
[REG82001428, Bit28]
to NotRDY
[INT/DP#02]
[REG82001428, Bit28]
SELF_IORDY from RDY to NotRDY (DP #3).
changed to NotRDY
[INT/DP#03]
[REG82001428, Bit28]
HD4A00 DUAL I/F The EXT_IORDY changed from Gather
EXT_IORDY changed RDY to NotRDY (DP #00).
to NotRDY
[INT/DP#00]
[REG82001428, Bit26]
HD4B00 DUAL I/F The EXT_IORDY changed from Gather
to NotRDY
[INT/DP#01]
[REG82001428, Bit26]
HD4C00 DUAL I/F The EXT_IORDY changed from Gather
to NotRDY
[INT/DP#02]
[REG82001428, Bit26]
HD4D00 DUAL I/F The EXT_IORDY changed from Gather
to NotRDY
[INT/DP#03]
[REG82001428, Bit26]
HD4E00 DUAL I/F SLV error An error was reported from the Gather
[INT/DP#00] other Control Unit (DP #00).
[REG82001484, Bit3]
HD4F00 DUAL I/F SLV error An error was reported from the Gather
[REG82001484, Bit3]

MSG 03-0390-01
Collect the error

Message
code
Trace Trace Dump
HD5000 DUAL I/F SLV error An error was reported from the Gather cReplace the Control Unit Replacement 2.2.5
[INT/DP#02] other Control Unit (DP #02). whose CALM LED is on. Replacing Control
[REG82001484, Bit3] Unit (REP 02-0390)
HD5100 DUAL I/F SLV error An error was reported from the Gather
[REG82001484, Bit3]
HD5200 DUAL I/F MRGN When the Control Unit in the Gather
error [INT/DP#00] other system adjusted the data
[REG82001484, Bit2] input timing during data
Control Unit in the self system, it
detected a margin error. (DP
#00) [Failure in the bus between
the CTLs]
the CTLs]
the CTLs]
the CTLs]
[INT/DP#00] system adjusted the data input
(DP #00) [Failure in the bus
between the CTLs]

MSG 03-0400-01
Collect the error

Message
code
Trace Trace Dump
HD5700 DUAL I/F SEQ error When the Control Unit in the self Gather cReplace the Control Unit Replacement 2.2.5
[INT/DP#01] system adjusted the data input whose CALM LED is on. Replacing Control
[REG82001484, Bit1] timing during data Unit (REP 02-0390)
between the CTLs]
between the CTLs]
between the CTLs]
HD5A00 DUAL I/F DCNT error The delay counter exceeded the Gather
[INT/DP#00] allowable delay limit of the delay
[REG82001484, Bit0] element (DP #00).
HD5B00 DUAL I/F DCNT error The delay counter exceeded the Gather
HD5C00 DUAL I/F DCNT error The delay counter exceeded the Gather
HD5D00 DUAL I/F DCNT error The delay counter exceeded the Gather

MSG 03-0410-01
Collect the error

Message
code
Trace Trace Dump
HE0100 Backend down Backend blockage: The Gather cCheck if the ENCs #0 and
[All Loop NG] subsystem cannot be #1 of the subsystem
controlled/monitored since concerned are installed
usable LOOP is unavailable in accurately.
the subsystem. dWhen an alarm has been Troubleshooting
issued to the subsystem, Chapter 6. Details of
refer to Troubleshooting Recovery Methods
Chapter 6 Details of (TRBL 06-0000)
Recovery Procedures.
eIf any of the ENCs #0 and Replacement 2.2.9
#1 of the subsystem Replacing ENC
concerned is blocked, Unit/SENC Unit
replace the ENC Unit and (REP 02-0830)
restart the subsystem.
HE020x Backend down The back end was blocked : Gather cCheck if the ENCs #0 and
[NO SES-HDU BKW] Since there are no usable SES #1 of the subsystem
(Unit-x) Disk Drives in the unit, the unit concerned are installed
cannot be the unit cannot be accurately.
controlled or monitored. dIf the Unit is 0, replace the Replacement 2.2.5
x : Unit ID# Control Unit for which the Replacing Control
(RKM/RKS=0) CALM LED is lit. Unit (REP 02-0390)
(RKAJ/RKAJAT eIf any of the ENCs #0 and Replacement 2.2.9
=1-14) #1 of the subsystem Replacing ENC
HE030x Backend down The back end was blocked : Gather cENC cable may have been Installation 1.6
[NO SES-HDU BKD] Since there are no usable SES misconnected. Check the Device ID Setting and
(Unit-x) Disk Drives in the unit, the unit ENC cable connection. ENC Cable
cannot be controlled or Connection (INST
monitored. 01-0160)
x : Unit ID # dCheck if the ENCs #0 and
(RKM/RKS=0) #1 of the subsystem
(RKAJ/RKAJAT concerned are installed
=1-14) accurately.
eIf the Unit is 0, replace the Replacement 2.2.5
Control Unit for which the Replacing Control
CALM LED is lit. Unit (REP 02-0390)
fIf any of the ENCs #0 and Replacement 2.2.9

MSG 03-0420-01
Collect the error

Message
code
Trace Trace Dump
HE040x Backend down The back end was blocked : Gather cIf the Unit is 0, replace the Replacement 2.2.5
[NO ENC] (Unit-x) There are no usable ENC. Control Unit for which the Replacing Control
x : Unit ID # CALM LED is lit. Unit (REP 02-0390)
(RKM/RKS=0) dCheck if the HDUs #0 to #3
(RKAJ/RKAJAT of the subsystem
=1-14) concerned are installed
accurately.
eIf a failure has occurred in Replacement 2.2.1
any of the HDUs #0 to #3 Replacing Disk Drive
of the subsystem (REP 02-0050)
concerned, replace the
Disk Drive and restart the
subsystem.
HE050x Backend down The back end was blocked : Gather cCheck if the subsystem is Installation 1.6
[Unit# ERR] Abnormality in the connection connected in the correct Device ID Setting and
(Unit-x) order of the units or a wrong ID device connection order. ENC Cable
of a unit was detected. dCheck if the device ID of Connection (INST
x : Unit ID # the subsystem is set 01-0160)
(RKM/RKS=0) correctly.
(RKAJ/RKAJAT eENC cable may have been
=1-14) misconnected. Check the
ENC cable connection.
fIf the Unit is 0, replace the Replacement 2.2.5
Control Unit for which the Replacing Control
CALM LED is lit. Unit (REP 02-0390)
gTurn off the main switch Installation 1.7
and turn off all the AC Input Power On/Off
Power Switches on the Procedure (INST 01-
subsystem. 0290)
hTurn on all the AC Input
Power Switches on the
subsystem and turn on the
main switch.
iRefer to Troubleshooting Troubleshooting
Chapter 8. Trouble Chapter 8. Trouble
Analysis by LED Analysis by LED
Indication. Indication (TRBL 08-
0000)
HE06xy Backend down The back end was blocked: Gather cCheck if the subsystem is Installation 1.6
[AL_PA] Abnormality was detected in AL- connected in the correct Device ID Setting and
(Path-x, Loop-y) PA of the drive connected to the device connection order. ENC Cable
loop. dCheck if the device ID of Connection (INST
x : Path # the subsystem is set 01-0160)
(RKM/RKS=0-1) correctly.
y : Loop # (0-1)

MSG 03-0430-01
Collect the error

Message
code
Trace Trace Dump
HE0710 Backend loop change The loop switch was changed Gather cPower on the subsystem Installation 1.7
error [OWN] and the newly selected loop had and boot it. Power On/Off
a failure, too. Procedure (INST 01-
0290)
dWhen a message, I5YG00 Chapter 4. Progress
Unit # ERR is displayed, Message (MSG 04-
take a recovery action 0000)
according to the message.
eWhen an alarm has been Troubleshooting
issued to the subsystem, Chapter 6. Details of
refer to see Recovery Methods
Troubleshooting Chapter 6 (TRBL 06-0000)
Details of Recovery
Procedures.
fWhen any one of the
following messages is
displayed before this
message, replace a part
according to the message
and reboot the subsystem.
W0100x CTL alarm
W060AT SATA HDU
alarm
W060xy, W0GG00,
W0GH00 HDU alarm
W061AT SATA Spare
HDU alarm
W061xy, W0GJ00,
W0GK00 Spare HDU
alarm
W090xy, W0GA00,
W0GC00 ENC alarm
W090AT, W0GB00,
W0GD00 SENC alarm
I301AT SATA HDU
error
I301xy HDU error
gIf the section to be replaced Troubleshooting
is not displayed before this Chapter 6. Details of
message, see Recovery Methods
Troubleshooting Chapter 6 (TRBL 06-0000)
Details of Recovery
Procedures.
hRefer to Troubleshooting Troubleshooting
0000)

MSG 03-0440-01
Collect the error

Message
code
Trace Trace Dump
HE0711 Backend loop change The loop switch was changed Gather cWhen any one of the
error [OTH] and the newly selected loop had following messages is
a failure, too displayed before this
message, replace a part
according to the message
and reboot the subsystem.
W0100x CTL alarm
W060AT SATA HDU
alarm
W060xy, W0GG00,
W0GH00 HDU alarm
W061AT SATA Spare
HDU alarm
W061xy, W0GJ00,
W0GK00 Spare HDU
alarm
W090xy, W0GA00,
W0GC00 ENC alarm
W090AT, W0GB00,
W0GD00 SENC alarm
I301AT SATA HDU
error
I301xy HDU error
dRefer to Troubleshooting Troubleshooting
6.1.14 A failure occurred 6.1.14 A failure
(Loop failure) operation : Case 4
(Loop failure) (TRBL
06-0600)
eRefer to Troubleshooting Troubleshooting
0000)
HE082x CTL loop failure A loop failure occurred in the Gather cReplace the Control Unit Replacement 2.2.5
(CTL-x) Control Unit of the system or the whose CALM LED is on. Replacing Control
other system. Unit (REP 02-0390)
HE0930 BKD job time-out Back end diagnosis job time-out Gather
occurred.

MSG 03-0450-01
Collect the error

Message
code
Trace Trace Dump
HE0A31 BKW job time-out Back end monitoring job finish Gather cReplace the Control Unit Replacement 2.2.5
waiting time-out occurred. whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
HE0Bxy ENC thermal alarm The sequential shutdown was Gather cCheck if the environment is
[PSOFF] executed because a set in accordance with the
(Unit-x, ENC-y) temperature error was detected specifications.
in the ENC. (Additional Chassis) dTurn the power on and
x : Unit ID # check if the fan is not in the
(RKM/RKS=0) state in which it has been
(RKAJ=1-14) given an alarm.
y : ENC Unit # (0-1) eReplace the ENC Unit. Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
HE0B0x ENC thermal alarm The sequential shutdown was Gather cCheck if the environment is
[PSOFF] executed because a set in accordance with the
(CTL-x) temperature error was detected specifications.
in the ENC. dTurn the power on and
(Basic Chassis) check if the fan is not in the
x : Control Unit # (0-1) state in which it has been
given an alarm.
eReplace the Control Unit Replacement 2.2.5
Unit (REP 02-0390)
HE0C00 Controller thermal The Control Unit of own system Gather cCheck if the environment is
alarm [OWN] was blocked because a set in accordance with the
temperature error was detected specifications.
in the Control Unit. d Check if the fan is not in the
HE0D00 Controller thermal The Control Unit of another Gather state in which it has been
alarm [OTH] system was blocked because a given an alarm.
temperature error was detected eReplace the Control Unit Replacement 2.2.5
in the Control Unit. whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
HE0E00 Controller thermal The sequential shutdown was Gather cCheck if the environment is
alarm [PSOFF] executed because a set in accordance with the
temperature error was detected specifications.
in the Control Unit. dTurn the power on and
check if the fan is not in the
state in which it has been
given an alarm.
eReplace the Control Unit Replacement 2.2.5
Unit (REP 02-0390)

MSG 03-0460-01
Collect the error

Message
code
Trace Trace Dump
HE0Fxy Backend down [Cable The back end was blocked : Gather cCheck that the connection Installation 1.6
ERR] Abnormality in the connection order of the unit cables is Device ID Setting and
(Unit-x, ENC-y) order of the cables was correct. (Check that a ENC Cable
detected. connector and a cable of Connection (INST
x : Unit ID # the same color are 01-0160)
(RKM/RKS=0) connected together.)
(RKAJ = 1-14)
y : ENC Unit # (0-1)
HE100x ENC error An ENC Unit error (SW Gather cReplace the Control Unit Replacement 2.2.5
[ENC NG] malfunction) occurred. whose CALM LED is on.. Replacing Control
(CTL-x) x : Control Unit # (0-1) Unit (REP 02-0390)
HE110x ENC error An ENC Unit error (unusable Gather
[NO SES HDU] SES drive) occurred.
HE120x ENC error An ENC Unit error (detection of Gather
[ENC check NG] a link trouble or request for the
(CTL-x) ENC unit replacement)
occurred.
HE200x ENC recovery failed The insertion of the ENC Unit Gather cVerify that the ENC cable is Installation 1.6
(CTL-x) failed (Basic Chassis). correctly connected. Device ID Setting and
x : Control Unit # (0-1) ENC Cable
Connection (INST
01-0160)
Unit (REP 02-0390)
HE21xy I/F board type error An illegal value was detected Gather cCheck if the Interface Replacement 2.2.7
(CTL-x, I/F board-y) when the installation status of Board displayed in the Replacing Interface
the Interface Board was message is that supported Board (REP 02-
acquired with TWSI. Or by the microprogram 0660)
unsupported Interface Board installed in the disk array
was installed. unit.
x : Control Unit # (0-1) dWhen it is found that the
y : Interface Board # (0-1) unsupported Interface
Board is installed, replace it
with a supported one.
eIf not recovered, check if
the interface board installed
in the Control Unit is not
loose. If it is loosely
installed, reinstall it firmly.
fIf not recovered yet,
replace the Interface Board.
gIf not recovered yet, Chapter 6. Warning
maintain it according to the Messages (MSG 06-
message when W0100x 0000)
CTL alarm is displayed
after this message.

MSG 03-0470-01
Collect the error

Message
code
Trace Trace Dump
HF0100 Data transfer check (Data assurance check) Gather cRefer to Troubleshooting Troubleshooting
error An illegal cache writing segment 6.1.12 A failure occurred 6.1.12 A failure
[SEGP0SERR] position was detected. during operation : Case 2 occurred during
(LA/LRC error)
(TRBL 06-0570)
HF0101 Data transfer check (Data assurance check) Gather cReplace the Control Unit Replacement 2.2.5
error A block which was not dirty was whose CALM LED is on. Replacing Control
[WRN0DTYBK] written in the Disk Drive. Unit (REP 02-0390)
HF0102 Data transfer check (Data assurance check) Gather
error Data were read into a dirty
[RDDTYBLK] block.
HF0103 Data transfer check (Input/Output data assurance Gather cReplace the Control Unit Replacement 2.2.5
error check) whose CALM LED is on. Replacing Control
[RDSEGERR] An illegal segment to be read Unit (REP 02-0390)
was detected. dIf not recovered, replace Replacement 2.2.6
the Cache Unit. Replacing Cache
Unit (REP 02-0540)
error [WSGQATERR] Contradiction occurred in the whose CALM LED is on. Replacing Control
queue attribute of the write Unit (REP 02-0390)
segment.
HF0105 Data transfer check (Input/Output data assurance Gather cReplace the Control Unit Replacement 2.2.5
error [WSEGPDEV] check) whose CALM LED is on. Replacing Control
An illegal Disk Drive to be Unit (REP 02-0390)
written was detected. d If not recovered, replace Replacement 2.2.6
HF0106 Data transfer check (Input/Output data assurance Gather the all Cache Unit. Replacing Cache
error [WSEGLOCK] check) Unit (REP 02-0540)
An illegal Disk Drive to be
written was detected.
error [CCPLUNERR] An illegal LUN was detected
when data were copied between
Cache memories.
error [CCPLBAERR] An illegal LBA was detected
when data were copied between
Cache memories.
error [PARLUNERR] An illegal LUN was detected
when parity was generated.
HF010A Data transfer check (Data assurance check) Gather
error [PARLBAERR] An illegal LBA was detected
when parity was generated.
HF010B Data transfer check (Data assurance check) Gather
error [QUEUEERR] Contradiction occurred in
transfer of the queue.

MSG 03-0480-01
Collect the error

Message
code
Trace Trace Dump
HF010C Data transfer check (Data assurance check) Gather cReplace the Control Unit Replacement 2.2.5
error [COWDRVERR] Data to be written together are whose CALM LED is on. Replacing Control
dispersed in multiple Disk Unit (REP 02-0390)
Drives. dIf not recovered, replace Replacement 2.2.6
the all Cache Unit. Replacing Cache
Unit (REP 02-0540)
HF010D Data transfer check (Data assurance check) Gather cReplace the Control Unit Replacement 2.2.5
error [LACHEKMOD] Contradiction occurred in whose CALM LED is on. Replacing Control
specification of LA check. Unit (REP 02-0390)
HF010E Data transfer check (Data assurance check) Gather cReplace the Control Unit Replacement 2.2.5
error [DSTP0SERR] An illegal writing position was whose CALM LED is on. Replacing Control
detected during destaging. Unit (REP 02-0390)
HF010F Data transfer check (Data assurance check) Gather dIf not recovered, replace Replacement 2.2.6
error[SEGP0SOTH] An illegal cache writing segment the Cache Unit. Replacing Cache
position was detected. Unit (REP 02-0540)
error [CMPNGHE] A duplex compare of SGCB was whose CALM LED is on. Replacing Control
detected. (Non-specialized Unit (REP 02-0390)
writing) d If not recovered, replace Replacement 2.2.6
HF0111 Data transfer check Data assurance check) Gather the other Control Unit. Replacing Cache
error [CMPNGSP] A duplex compare of SGCB was Unit (REP 02-0540)
detected. (Specialized writing)
HF0112 Data transfer check Data assurance check) Gather
error[CMPNGSP] A duplex compare of SGCB was
detected. (Generation of parity)
error [CMPNGCP] A duplex compare of SGCB was
detected. (Copying between
Cache memories)
error [CMPNGDC] A duplex compare of SGCB was
detected. (Transfer from disk to
Cache memory)
error [CMPNGCD] A duplex compare of SGCB was
detected. (Transfer from Cache
memory to disk)
error [SSGQATERR] An illegal segment queue whose CALM LED is on. Replacing Control
attribute was detected in the Unit (REP 02-0390)
intermediate skip mode.
HF0117 Data transfer check A contradiction in the queue Gather cReplace the Control Unit Replacement 2.2.5
error attribute of the buffer segment whose CALM LED is on. Replacing Control
[BUFSGQATERR] occurred. Unit (REP 02-0390)
HF0118 Data transfer check (Data assurance check) Gather dIf not recovered, replace Replacement 2.2.6
error WRBUFTODTY] A writing of data in a buffer the all Cache Units. Replacing Cache
segment into a dirty block was Unit (REP 02-0540)
attempted.

MSG 03-0490-01
Collect the error

Message
code
Trace Trace Dump
error [MAPERR] An illegal operation, in which a whose CALM LED is on. Replacing Control
transfer of a block with no data Unit (REP 02-0390)
was attempted, was detected.
HF011A Data transfer check (Data assurance check) Gather
error [LOCLUERR] An illegal operation, in which a
transfer of a segment of a
different LU was attempted, was
detected.
HF011B Data transfer check (Data assurance check) Gather
error [RMTLUERR] An illegal operation, in which a
specification of a transfer
destination LU was wrong, was
detected.
HF011C Data transfer check (Data assurance check) Gather
error [PAIRERR] An illegal operation, in which a
data transfer was attempted
although the status of the
TrueCopy remote replication pair
did not allow it, was detected.
HF020x Directory check error An uncorrectable contradiction Gather cReplace the Control Unit Replacement 2.2.5
(CTL-x) was detected in a cache whose CALM LED is on. Replacing Control
directory. Unit (REP 02-0390)
x : Control Unit # (0-1) d If not recovered, replace Replacement 2.2.6
HF0300 Data transfer check (Data assurance check) Gather the Cache Units. Replacing Cache
error [STGLUNERR] A LUN error was detected Unit (REP 02-0540)
during a staging.
error [NTMPRD] A LUN error was detected whose CALM LED is on. Replacing Control
during a staging. Unit (REP 02-0390)
dIf the problem is not solved Replacement 2.2.6
in spite of the replacement, Replacing Cache
replace a controller in Unit (REP 02-0540)
error [DTYMPERR] An incorrect dirty map was whose CALM LED is on. Replacing Control
detected. Unit (REP 02-0390)
HG0100 CTL communication Communication receiving Gather
send time-out waiting time-out occurred.
HG0210 OTH CTL Response Time-out occurred in Gather
time-out communication of request for
[CMDFMWR] updating the flash memory of
the other system. (CMD)
HG0311 OTH CTL Response Communication waiting time-out Gather
time-out [OFW] occurred in the other system
during off-line monitoring.
HG0312 Resource release General resource release Gather
time-out waiting time-out occurred.
HG0413 Data share job time- Job time-out occurred for Gather
out request for share.
HG0514 LU-CTL change time- Time-out occurred while LU was Gather
out changed.

MSG 03-0500-01
Collect the error

Message
code
Trace Trace Dump
HGA000 Staging job time-out A time-out occurred because a Gather cReplace the Control Unit Replacement 2.2.5
staging job was not completed whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
within a certain period.
HGA100 Data staging time-out A time-out of waiting for staging Gather
completion occurred during the
Copy-on-write SnapShot
restoration copy job.
HGA200 Data pool copy time- A time-out of waiting for Copy- Gather
out on-write SnapShot copy
completion occurred during the
restoration control job.
HGA300 Data restore time-out A time-out of waiting for restore Gather
copy completion occurred during
the Copy-on-write SnapShot
HGA400 Data pool wait time- A time-out of waiting for the pool Gather
out resource ensuring occurred during
the Copy-on-write SnapShot
HH010x System parameter A system parameter is not set. Gather cSet the system parameter WEB Chapter 3.
undefined (CTL-x) x : Control Unit # (0-1) correctly in the WEB The Maintenance
maintenance mode. Mode Operation
Procedure (WEB 03-
0000)
HH020x Flash revision A Control Unit which the Gather cCheck setting of the system WEB Chapter 3.
mismatch (CTL-x) currently installed microprogram parameter in the WEB The Maintenance
could not operate was detected. maintenance mode to see if Mode Operation
x : Control Unit # (0-1) a function which the Procedure (WEB 03-
currently installed 0000)
microprogram cannot
operate is set.
dIf setting is correct, replace Replacement 2.2.5
the Control Unit, the CALM Replacing Control
LED of which is lighting up. Unit (REP 02-0390)
HH030x FLASH-RAM program Illegal interface between the Gather cReplace the Control Unit Replacement 2.2.5
I/F error flash boot program and RAM whose CALM LED is on. Replacing Control
(CTL-x) program was detected. Unit (REP 02-0390)
HH0400 Unsupported function A function which the system did Gather cSet the system parameter WEB Chapter 3.
enabled not support was set. correctly in the WEB The Maintenance
maintenance mode. Mode Operation
Procedure (WEB 03-
0000)
HH0510 Task make error Generation of the initial setting Gather cReplace the Control Unit Replacement 2.2.5
[INMTSKERR] task failed. whose CALM LED is on. Replacing Control
HH0620 JOB make error Generation of a job at start up Gather Unit (REP 02-0390)
failed.

MSG 03-0510-01
Collect the error

Message
code
Trace Trace Dump
HH0930 No system HDU The system area of the all Disk Gather cContact the Technical
Drives became unavailable. Support Center.
HH0931 No system HDU Information on takeover in the Gather
system area for all Disk Drives
became unusable.
HH0A40 System HDU access Since access could not be made Gather cReplace the Control Unit Replacement 2.2.5
error to the system area of the all Disk whose CALM LED is on. Replacing Control
Drives because of a system area Unit (REP 02-0390)
access error, the Control Unit was
blocked.
HH0CAT SATA HDU removed The Disk Drive used until Gather cCheck the mounting
before PS ON previous operation is not position of the Disk Drive.
(Unit-x, HDU-y) mounted when P/S is turned on.
x : Unit ID #
(RKAJAT=1-29)
y : Disk Drive # (0-14)
HH0Cxy HDU removed before The Disk Drive used until Gather
PS ON previous operation is not
(Unit-x, HDU-y) mounted when P/S is turned on.
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
HH0E0x CACHE access error A cache access error Gather cReplace the Cache Unit. Replacement 2.2.6
(CACHE-x) [PON] (unrecoverable) occurred when Replacing Cache
P/S was turned on. Unit (REP 02-0540)
x : Cache Unit slot # dIf not recovered, replace Replacement 2.2.5
(RKM/RKS=0-1) the above Control Unit. Replacing Control
Unit (REP 02-0390)
HH0FAT RKAJAT removed The additional frame which the Gather cMake sure that the
before PS ON Disk Drive used last time Additional Chassis is
(Unit-x) belonged to was not connected installed and connected,
when the power was turned on. and then start up the
x : Unit ID # subsystem again.
(RKAJAT=1-29) d Analyze the failure following Troubleshooting 8.1
HH0Fxx RKAJ removed The additional frame which the Gather Troubleshooting 8.1 Trouble Analysis by
before PS ON Disk Drive used last time Trouble Analysis by LED LED Indication of
(Unit-x) belonged to was not connected Indication of Front Bezel Front Bezel (TRBL
when the power was turned on. for the Unit # concerned. 08-0000)
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
HH1070 PIN segment error Cache segments are insufficient Gather cReplace the Control Unit Replacement 2.2.5
[PINSEGOV] for recovery of the PIN data of whose CALM LED is on. Replacing Control
the information taken over. Unit (REP 02-0390)
HH1180 DCTL hard error A DMA hardware failure Gather
[PS ON] occurred while PS is turned on.

MSG 03-0520-01
Collect the error

Message
code
Trace Trace Dump
HH1290 System down When data were lost, system Gather cSee Troubleshooting 6.1.2 Troubleshooting
selected shutdown was selected by the The subsystem does not 6.1.2 The
[USRDATLST] user. become ready : Case 1 subsystem does not
(Loading failure). become ready : Case
1 (Loading failure)
(TRBL 06-0050)
HH12A0 Forced parity Time-out occurred during forced Gather cReplace the Disk Drive. Replacement 2.2.1
correction time-out parity correction operation while When you want to know a Replacing Disk Drive
P/S is turned on model name of the Disk (REP 02-0050)
. Drive or a revision of the Replacement 1.1.3
drive firmware, refer to Procedure for making
Replacement 1.1.3 sure of model name
Procedure for making sure and drive firmware of
of model name and drive Disk Drive (REP 01-
firmware of Disk Drive. 0100)
Unit (REP 02-0390)
HH13B0 System change failed The upgrade cannot be made Gather cReturn the Disk Drive to the Installation 1.7.1
[PIN] because a pinned segment subsystem of the lower Subsystem power on
exists in the state in which the grade model and reboot the (INST 01-0290)
system change has not been subsystem.
made normally. dMake the upgrade again
after eliminating the pinned
segment.
HH13B1 System change failed The upgrade cannot be made Gather cReturn the Disk Drive to the Installation 1.7.1
[PSOFF] because the system change has subsystem of the lower Subsystem power on
not been made normally. grade model and reboot the (INST 01-0290)
subsystem.
dMake the upgrade again
after performing the
deliberate shutdown.
HH16D0 CTL recovery failed The DRR failure was detected Gather cReplace the Control Unit Replacement 2.2.5
[DRR ERR] when the Control Unit was whose CALM LED is on. Replacing Control
inserted in the state in which the Unit (REP 02-0390)
subsystem power was on, and
then the cache memory of the
inserted Control Unit was being
restored.
HH17xx Unit which cannot be A frame with no drive installed Gather cMake sure of installation of
managed was detected in the powering on Disk Drives in the frame
(Unit-x) diagnosis. concerned and start up the
x : Unit ID # subsystem again.
(RKM/RKS=0) dENC cable may have been Installation 1.6
(RKAJ/RKAJAT=1-14) misconnected. Check the Device ID Setting and
ENC cable connection. ENC Cable
Connection (INST
01-0160)

MSG 03-0530-01
Collect the error

Message
code
Trace Trace Dump
HH19xy ENC alarm An ENC failure occurred in the Gather cPower off the added RKAJ Replacement 2.2.9
(Unit-x, ENC-y) back end diagnostic mode. and replace the ENC Unit. Replacing ENC
(Additional Chassis) Unit/SENC Unit
x : Unit ID # (REP 02-0830)
(RKM/RKS=0) dThen execute the back end
(RKAJ/RKAJAT=1-14) diagnosis again
y : ENC Unit/SENC Unit #
(0-1)
HH190x ENC alarm An ENC failure occurred in the Gather cReplace the Control Unit Replacement 2.2.5
(CTL-x) back end diagnostic mode. whose CALM LED is on. Replacing Control
(Basic Chassis) Unit (REP 02-0390)
x : Control Unit # (0-1) dThen execute the back end
diagnosis again
HH1Axy ENC recovery NG Though recovery of the Control Gather cInsert the Control Unit Replacement 2.2.1
HDD-NG Unit (in the basic frame) was again after making the Replacing Disk Drive
(Unit-x, HDU-y or z) attempted, it failed because a recovery by replacing the (REP 02-0050)
failure occurred in the Disk Drive Disk Drive (y or z). Replacement 2.2.5
(y or z) connected to the ENC. Replacing Control
x : Unit ID #=0 Unit (REP 02-0390)
(RKM/RKS=0)
(RKAJ=1-14)
y or z : Disk Drive # (0-14)
HH1B0x ENC recovery NG Though recovery of the Control Gather cReplace the Control Unit Replacement 2.2.5
HDD-NG Unit (in the Basic Chassis) was whose CALM LED is on. Replacing Control
(CTL-x) attempted, it failed because a Unit (REP 02-0390)
failure occurred in the ENC.
HH1J00 ENC error inf. The Control Unit was detached Gather
[CUDG because an CUDG ECTL
ECTLREGERR] register error occurred in the
ENC.
HH1K00 ENC error inf. A ready time-out of the ENC in Gather
[CUDG ENC another system was detected.
RDYTOV]
HH1L00 ENC error inf. The Control Unit was detached Gather
[CUDG SRAMERR] because an CUDG SRAM Parity
error occurred in the ENC.
HH1M00 ENC error inf. The Control Unit was detached Gather cReplace the Control Unit Replacement 2.2.5
[CUDG because an CUDG whose CALM LED is on. Replacing Control
ENCCOMERR] ENCCOMERR error occurred in d If not recovered yet, Unit (REP 02-0390)
the ENC. contact the Technical
HH1N00 ENC error inf. The Control Unit was detached Gather Support Center. (*1)
[ENCCOMERR] because an CUDG
ENCCOMERR error occurred in
the ENC.
*1 : If CALM LED lights on, and the same message is displayed again in spite of replacing the Control Unit in c, the
Control Unit on the opposite side may have a failure. Replace the Control Unit on the opposite side with the
power turned off after checking with the customer.

MSG 03-0540-01
Collect the error

Message
code
Trace Trace Dump
HH1P00 ENC error inf. The Control Unit was detached Gather cReplace the Control Unit Replacement 2.2.5
[ECTL force test] because an parity error occurred whose CALM LED is on. Replacing Control
in the ENC. Unit (REP 02-0390)
HH1Q00 SES error inf. The Control Unit was detached Gather
[SES-HDU error] because both of the two SES
drives could not access the
ENC.
HH1W00 ENC inf. [REGPERR] REGPERR occurred in ENC Gather
and the corresponding CTL was
detached.
HH1X00 ENC inf. [RAMPERR] RAMPERR occurred in ENC Gather
and the corresponding CTL was
detached.
HH1Y00 ENC inf. WDTCNTPERR occurred in Gather
[WDTCNTPERR] ENC and the corresponding
CTL was detached.
HH1Z0x ENC recovery NG An ENC recovery failure (Basic cCollect Simple trace and Replacement 2.2.5
Loop-NG Chassis) contact the Technical Replacing Control
(CTL-x,) x : Control Unit # (0-1) Support Center. Unit (REP 02-0390)
HH2000 DUAL I/F A failure of the impedance Gather c When W0100x CTL alarm Chapter 6. Warning
SELF_IORDY error adjustment circuit of own system is displayed following this Messages (MSG 06-
[REG82001428, Bit22] occurred during a readjustment message, take recovery 0000)
of the impedance. actions according to the
HH2100 DUAL I/F A failure of the impedance Gather message.
EXT_IORDY error adjustment circuit of another dReplace the Control Unit of Replacement 2.2.5
[REG82001428, Bit21] system occurred during a which the CALM LED lights Replacing Control
readjustment of the impedance. on except for c. Unit (REP 02-0390)
HH2200 DUAL I/F A failure of the impedance Gather
DUAL_IORDY error adjustment circuit of own system
[REG82001428, Bit29] occurred during a readjustment
of the impedance.
HH250x Rotary switch number The not supported rotary switch Gather cConfirm the setting of the Installation 1.8
is not supported number is set. rotary switch. Setting the Power
x : Rotary switch Control Mode
(7 or 8 =1, other=0) (Local/Remote
Mode) (INST 01-
0320)
HH270x Interface Board is not The Interface Board is not Gather cInstall at least one Interface Installation 3.4.7 (4)
installed (CTL-x) installed. Board in this Control Unit. Installing the Control
x : Control Unit # (0-1) Unit, Cache Unit and
Interface Board
(INST 03-0550)
HH2900 Cache capacity The cache capacity was reduced Gather cReturn the cache capacity Replacement 2.2.6
reduced although in the state in which any one of to that at the time when the Replacing Cache
copy function enable the copy functions (TrueCopy power was turned off. Unit (REP 02-0540)
remote replication, ShadowImage
in-system replication, Copy-on-
write SnapShot, and Hi-Copy)
was valid.

MSG 03-0550-01
Collect the error

Message
code
Trace Trace Dump
HH2A00 Single or Hot Stand- The Single mode was set Gather cReturn the system System Parameter
by although although the Copy-on-write parameters of the Chapter 3. Setting
QuickShadow enable SnapShot function was enabled subsystem to those for the the RAID/LU/Spare
when the subsystem was Dual Active mode and Disk (SYSPR 03-
started up. restart the subsystem. 0000)
HH2B00 Upgrade failed The upgrade from the lower Gather cDo the upgrading For Microprogram
[PSOFF] grade model to the higher grade installation of the Chapter 1.
model cannot be made because microprogram for the lower Installation of
the deliberate shutdown has not grade model after disabling Microprogram
been performed. the installation guard. (MICRO 01-0000)
dPower off the subsystem Installation 1.7.1
after the updating Subsystem power on
installation is completed. (INST 01-0290)
eReturn the hardware
configuration to that of the
lower grade model.
fPerform the deliberate Installation 1.7.1
shutdown of the subsystem Subsystem power on
after booting it while it is the (INST 01-0290)
lower grade model.
gExecute the procedure for
the upgrade from the lower
grade model to the higher
grade model.
HH2C00 Upgrade failed The upgrade from the lower Gather cDo the upgrading For Microprogram
[Single] grade model to the upper grade installation of the Chapter 1.
model could not be made microprogram for the lower Installation of
because the System Startup grade model after disabling Microprogram
Attribute was set as the Single the installation guard. (MICRO 01-0000)
Mode. dPower off the subsystem Installation 1.7.1
after the updating Subsystem power on
installation is completed. (INST 01-0290)
eReturn the hardware
configuration to that of the
lower grade model.
fChange the mode to the WEB 3.1
Maintenance mode after Transferring to the
booting the subsystem while Maintenance Mode
it is the lower grade model. (WEB 03-0000)
gExecute the Go to Normal WEB 3.2.1
Mode after setting the Subsystem (WEB
System Setup Attribute as 03-0060)
the Dual Active Mode.
hBoot the subsystem. Installation 1.7.1
Subsystem power on
(INST 01-0290)
iExecute the procedure for
the upgrade from the lower
grade model to the higher
grade model.

MSG 03-0560-01

MSG 03-0560-01
Collect the error

Message
code
Trace Trace Dump
HH2D00 Upgrade failed The upgrade from the lower Gather cInstall the microprogram of For Microprogram
[Microprogram grade model to the higher grade the higher grade model, Chapter 1.
revision] model cannot be made because whose system revision is Installation of
the versions of their the same as that of the Microprogram
microprograms are different microprogram of the lower (MICRO 01-0000)
from each other. model, in the Disk Drive.
HH2F00 Downgrade failed The subsystem start-up of the Gather cExecute the initial setup to
[Subsystem can not lower model failed because it the subsystem that is the
take over the user tried to downgrade from the hardware configuration of
data] upper model to the lower model. the lower model, and start
up the subsystem when
operating the subsystem as
a lower model.
dTurn on all the AC input
power supply switches of
the subsystem after
returning the hardware
configuration of the
subsystem to the status
that is upgraded to the
upper model, and start up
the subsystem of the upper
model when operating the
subsystem as an upper
model.
HH2I00 DUAL I/F stabilization When the impedance of the I/O Gather cWhen W0100x CTL alarm Chapter 6. Warning
error in an impedance buffer was going to be is displayed following this Messages (MSG 06-
adjustment readjusted, it was found that the message, take recovery 0000)
[REG82001428, impedance was not fixed in the actions according to the
Bit24, Bit25] preceding adjustment. message.
HH2J00 DUAL I/F DESKEW is When the Control Unit in the self Gather cWhen W0100x CTL alarm Chapter 6. Warning
not completed system adjusted the data input is displayed following this Messages (MSG 06-
timing during data message, take recovery 0000)
sending/reception to/from the actions according to the
Control Unit in the other system, message.
a time-out occurred. d If not recovered, replace Replacement 2.2.5
HH2K00 DUAL I/F SLV error When the Control Unit in the self Gather the other Control Unit. (The Replacing Control
[INT/MP] system adjusted the data input replacement cannot be Unit (REP 02-0390)
[REG82001484, bit3] timing during data done when the subsystem
sending/reception to/from the power is on.)
it received an error report from
the Control Unit in the other
system.

MSG 03-0570-01
Collect the error

Message
code
Trace Trace Dump
HH2L00 DUAL I/F SEQ error When the Control Unit in the self Gather cWhen W0100x CTL alarm Chapter 6. Warning
[INT/MP] system adjusted the data input is displayed following this Messages (MSG 06-
[REG82001484, Bit1] timing during data message, take recovery 0000)
sending/reception to/from the actions according to the
Control Unit in the other system, message.
it detected a sequence error. dIf not recovered, replace Replacement 2.2.5
the other Control Unit. (The Replacing Control
replacement cannot be Unit (REP 02-0390)
power is on.)
HH2M00 DUAL I/F DESKEW is Though the inserted Control Unit Gather cWhen W0100x CTL alarm Chapter 6. Warning
not completed attempted to adjust the data is displayed following this Messages (MSG 06-
input timing when it was message, take recovery 0000)
sending/receiving data to/from a actions according to the
Control Unit not blocked, the message.
adjustment was not completed dIf not recovered, replace Replacement 2.2.5
within the time limit. the other Control Unit. (The Replacing Control
replacement cannot be Unit (REP 02-0390)
power is on.)
HH2N00 DUAL I/F SLV error When the inserted Control Unit Gather cReplace not the inserted Replacement 2.2.5
[INT\MP] was adjusting the data input Control Unit but the other Replacing Control
[REG82001484, Bit3] timing while it was Control Unit. (The Unit (REP 02-0390)
sending/receiving data to/from a replacement cannot be
Control Unit not blocked, it done when the subsystem
received an error report from the power is on.)
Control Unit not blocked. d When this message is
HH2P00 DUAL I/F SEQ error When the inserted Control Unit Gather displayed again after the
[INT/MP] was adjusting the data input replacement of the Control
[REG 82001484, Bit1] timing while it was Unit, replace the Control
sending/receiving data to/from a Unit that has been inserted
Control Unit not blocked, it in the state in which the
detected a sequence error. subsystem power is on.

MSG 03-0580-01
Collect the error

Message
code
Trace Trace Dump
HH30xx Obstacle HDU search Automatic diagnosis of backend Gather c When any one of the
failed loop cannot be continued. following messages is
(Both system are blocked) displayed before this
x : Optional code message, replace a part
HH31xx Backend loop change Automatic diagnosis of backend Gather according to the message
error loop cannot be continued. and reboot the subsystem.
[OWN] (Own system is blocked) W0100x CTL alarm
x : Optional code W060AT SATA HDU
alarm
W060xy, W0GG00,
W0GH00 HDU alarm
W061AT SATA Spare
HDU alarm
W061xy, W0GJ00,
W0GK00 Spare HDU
alarm
W090xy, W0GA00,
W0GC00 ENC alarm
W090AT, W0GB00,
W0GD00 SENC alarm
I301AT SATA HDU
error
I301xy HDU error
dSee Troubleshooting Troubleshooting
(Loop failure). operation : Case 4
06-0600)
HH3200 ENC error inf. The write data is not reflected cReplace the Control Unit Replacement 2.2.5
[CMPERR] on the read side of the cache whose CALM LED is on. Replacing Control
after it has been written onto the Unit (REP 02-0390)
ENC of the DKC frame.
HH3300 ENC error inf. The write operation is not
[WTTOUT] completed though 1.2 seconds
have passed after the write
instruction was issued to the
ENC of the DKC frame.
HH3400 ENC error inf. Though 40 ms have passed
[RENEWERR] after the data update request bit
was turned on, the bit is not
turned off.
HH3500 ENC error inf. The SES information that was
[DARAERR] read was incorrect.
HH3600 Unit-00 removed The number of installed frames cCheck the connection of
before PS ON was zero when the subsystem the ENC cable between the
was started up. controller unit and the Unit
00, and then restart the
subsystem.

MSG 03-0590-01
Collect the error

Message
code
Trace Trace Dump
HH3700 ENC error inf. The Write data is not reflected cReplace the Control Unit Replacement 2.2.5
[BKD CMPERR] on the Read side after it was whose CALM LED is on. Replacing Control
written in the ENC. Unit (REP 02-0390)
HH3800 ENC error inf. The read SES information was
[BKD ECTLERR] incorrect. (ECTLERROR)
HH3900 ENC error inf. The read SES information was
[BKD SWCUDGERR] incorrect. (SWCUDGERR)
HH3A00 ENC error inf. The read SES information was cWhen W0100x CTL alarm Chapter 6. Warning
[BKD ENCCOMERR] incorrect. (ENCCOMERR) is displayed following this Messages (MSG 06-
message.
eIf not recovered, replace
the other Control Unit. (The
replacement cannot be
power is on.)
HH3B00 ENC error inf. The read SES information was c Replace the Control Unit Replacement 2.2.5
[BKD FIXEDNG] incorrect. (FIXEDNG) whose CALM LED is on. Replacing Control
HH3C00 ENC error inf. The read SES information was Unit (REP 02-0390)
[BKD IDMODENG] incorrect. (IDMODENG)
HH3D00 ENC error inf. The read SES information was
[BKD REVREGNG] incorrect. (REVREGNG)
HH3E0x Obstacle ENC A part (CLT), in which the back
detected end loop failure occurred, was
(CTL-x) identified.
HH3F00 Unsupported unit is An unsupported frame was c Since the subsystem went
connected [RKA] detected when the subsystem down because an
(Unit-x) was booted. unsupported frame was
x : Unit ID # connected, disconnect the
(RKA=1-14) unsupported frame and
HH4000 Unsupported unit is An unsupported frame was reboot the subsystem.
connected [RKAAT] detected when the subsystem
(Unit-x) was booted.
x : Unit ID #
(RKAAT=1-14)

MSG 03-0600-01
Collect the error

Message
code
Trace Trace Dump
HH4100 All HDUs in the Unit All drives in both of the Loop-0 Gather cPerform the failure analysis Troubleshooting 8.1
missing (Unit-x) and Loop-1 in the RKAJ no on the unit with the number Trouble Analysis by
longer exist in the position map. displayed in the message LED Indication of
(The system goes down after according to Section 8.1, Front Bezel (TRBL
this message is issued. Trouble Analysis by LED 08-0000)
Though a message, W0100x, is indication of Front Bezel in
displayed following this the Troubleshooting.
message in the case of the dual dCheck if the ENC cable,
configuration, neglect it. which is connected to the
x : Unit ID # unit with the number
(RKAJ=1-14) displayed in the message,
is correctly connected.
HH4E00 Backend down [SES Monitoring of the disk array unit Gather cCheck if the subsystem is Installation 1.6
access error BKW] became impossible because the connected in the correct Device ID Setting and
(Unit-x) SES access to the both ENC device connection order. ENC Cable
Units became impossible. dCheck if the device ID of Connection (INST
In the case of RKM/RKS the subsystem is set 01-0160)
x : Unit ID # correctly.
(RKM/RKS=0) eENC cable may have been
(RKAJ/RKAJAT=1-14) misconnected. Check the
fCheck if the ENCs #0 and
#1 of the subsystem
concerned are installed
accurately.
gIf the Unit0 is the basic Replacement 2.2.5
frame (RKM/RKS), replace Replacing Control
the Control Unit for which Unit (REP 02-0390)
the CALM LED is lit.
hIf any of the ENCs #0 and Replacement 2.2.9
HI0100 PS OFF failed Hang-up of destaging Gather cReplace the Control Unit Replacement 2.2.5
[DSTG HUNG] processing of the other system whose CALM LED is on. Replacing Control
was detected when the plan was Unit (REP 02-0390)
stopped.
HI0201 PS OFF failed When PS is turned off, the Gather
[POFNONCLD] information taken over is not set
in the COLD state.
HI0202 PS OFF failed When PS is turned off, the plan Gather
[POFNOJOB] stopping job has not been
executed.
HI0310 OTHPS OFF time-out Time-out in waiting for Gather
communication of the other
system occurred while the plan
was being stopped.

MSG 03-0610-01
Collect the error

Message
code
Trace Trace Dump
HI0420 System down When the plan could not be Gather cSee 6.1.2 The subsystem Troubleshooting
selected [PS OFF] stopped, system shutdown was does not become ready : 6.1.2 The
selected by the user. Case 1 (Loading failure). subsystem does not
HI050x CACHE access error When the plan was stopped, Gather become ready : Case
(CACHE-x) system shutdown was caused 1 (Loading failure)
[POFF] by a cache access error. (TRBL 06-0050)
(unrecoverable)
(RKM/RKS=0-1)
HI0600 PS OFF failed The sequential shutdown could Gather
[PIN] not be done because of the too
much pinned data.
HJ01xx Microprogram error Logical illegality was detected in Gather cReplace the Control Unit Replacement 2.2.5
[INM] the microprogram. whose CALM LED is on. Replacing Control
(Initial setting) Unit (REP 02-0390)
x : Optional code
HJ02xx Microprogram error Logical illegality was detected in Gather
[POF] the microprogram.
(Stop of plan)
x : Optional code
[RST] the microprogram. (Reset)
x : Optional code
[SCK] the microprogram. (Kernel)
x : Optional code
HJ050x Microprogram error Logical illegality was detected in Gather
[CIT] the microprogram. (Interruption)
x : Optional code
[RSM] the microprogram.
(Resource control)
x : Optional code
[FTD] the microprogram.
(Tachyon driver control)
x : Optional code
[FSM] the microprogram.
(Sequence Manager)
x : Optional code
[LSM] the microprogram.
(Link service control)
x : Optional code

MSG 03-0620-01
Collect the error

Message
code
Trace Trace Dump
HJ0Axx Microprogram error Logical illegality was detected in Gather cReplace the Control Unit Replacement 2.2.5
[HSC] the microprogram. whose CALM LED is on. Replacing Control
x : Optional code Unit (REP 02-0390)
HJ0Bxx Microprogram error Logical illegality was detected in Gather
[NCR] the microprogram. (NCR)
x : Optional code
HJ0Dxx Microprogram error Logical illegality was detected in Gather
[SCP] the microprogram.
(SCP control)
x : Optional code
HJ0Exx Microprogram error Logical illegality was detected in Gather
[CMD] the microprogram.
(Command)
x : Optional code
HJ0Fxx Microprogram error Logical illegality was detected in Gather
[PRS] the microprogram.
(Reading first)
x : Optional code
[COW] the microprogram.
(Writing together)
x : Optional code
[RCH] the microprogram.
(Cache control)
x : Optional code
[RAD] the microprogram.
(RAID control)
x : Optional code
[DSC] the microprogram.
(Execution of input/output)
x : Optional code
[DMA] the microprogram.
(Data transfer control)
x : Optional code
[ERR] the microprogram. (Assistance
in failure processing)
x : Optional code
[RCF] the microprogram.
(Configuration control)
x : Optional code
[DRC] the microprogram.
(Recovery of Disk Drive)
x : Optional code

MSG 03-0630-01

MSG 03-0630-01
Collect the error

Message
code
Trace Trace Dump
HJ18xx Microprogram error Logical illegality was detected in Gather cReplace the Control Unit Replacement 2.2.5
[OFW] the microprogram. whose CALM LED is on. Replacing Control
(Off-line monitoring) Unit (REP 02-0390)
x : Optional code
[ONW] the microprogram.
(On-line monitoring)
x : Optional code
HJ1Axx Microprogram error Logical illegality was detected in Gather
[DST] the microprogram.
(Emergency destaging)
x : Optional code
HJ1Bxx Microprogram error Logical illegality was detected in Gather
[CPR] the microprogram.
(Forced recovery of parity)
x : Optional code
HJ1Cxx Microprogram error Logical illegality was detected in Gather
[COM] the microprogram.
(Common function)
x : Optional code
HJ1Dxx Microprogram error Logical illegality was detected in Gather
[SV1] the microprogram.
(SVP I/F)
x : Optional code
HJ1Exx Microprogram error Logical illegality was detected in Gather
[LUC] the microprogram.
(Common function)
x : Optional code
HJ1Fxx Microprogram error Logical illegality was detected in Gather
[PR0] the microprogram.
(Communication between
Control Units)
x : Optional code
[BKW] the microprogram.
(Back end control)
x : Optional code
[BKD] the microprogram.
(Back end diagnosis)
x : Optional code
[CCP] the microprogram.
(Coupling copy job)
x : Optional code
HJ23xx Microprogram error A logical illegality of the Gather
[MDU] microprogram was detected
(during an execution of drive
firmware renewal job).
x : Optional code

MSG 03-0640-01

MSG 03-0640-01
Collect the error

Message
code
Trace Trace Dump
HJ24xx Microprogram error A logical illegality of the Gather cReplace the Control Unit Replacement 2.2.5
[SDW] microprogram was detected whose CALM LED is on. Replacing Control
(Takeover writing job). Unit (REP 02-0390)
x : Optional code
[RVD] microprogram was detected
(RVR data transfer job).
x : Optional code
[RVP] microprogram was detected
(RVR communication job).
x : Optional code
[RVM] microprogram was detected
(RVR management).
x : Optional code
[STG] microprogram was detected
(Staging job).
x : Optional code
HJ29xx Microprogram error Logical incorrectness of Gather
[SPL] microprogram was detected
(mistake specializing control).
x : Optional code
HJ2Axx Microprogram error Logical incorrectness (in the Gather
[SML] SendMail control) of the
microprogram was detected.
x : Optional code
HJ2Bxx Microprogram error A logical error occurred. (Copy- Gather
[SNP] on-write SnapShot job)
x : Optional code
HJ2Cxx Microprogram error A logical error occurred. (Pool Gather
[POM] management)
x : Optional code
HJ2Dxx Microprogram error A logical error occurred. (Copy- Gather
[SNR] on-write SnapShot restoration
control)
x : Optional code
HJ2Exx Microprogram error A logical error occurred. Gather
[SAM] (S-Vol area management
control)
x : Optional code
HJ2Fxx Microprogram error Self contradiction of Format. Gather
[QFM] x : Optional code

MSG 03-0650-01
Collect the error

Message
code
Trace Trace Dump
HJ30xx Microprogram error A logical error occurred. Gather cReplace the Control Unit Replacement 2.2.5
[SMR] (SMART control) whose CALM LED is on. Replacing Control
x : Optional code Unit (REP 02-0390)
HJ31xx Microprogram error A logical error occurred. (Drive Gather
[DRF] flash control)
x : Optional code
HJ32xx Microprogram error Contradiction of the forced parity Gather
[OPR] correction that is made in the
state in which the subsystem
power is on.
x : Optional code
HJ33xx Microprogram error Logical illegality of the Gather
[MPC] microprogram was detected.
(Multi-protocol management
control)
x : Optional code
[JSD] microprogram was detected.
(Job support driver)
x : Optional code
[DMI] microprogram was detected
(DDCB management
information R/W job)
x : Optional code
HJ3800 Backend down [Path Abnormality of the chassis mode Gather cSet the PATH mode setting Installation 1.7.1
switch status error] setting was detected. again conforming to the Subsystem power on
(Unit-x, ENC-y) x : Unit ID # system, and start up the (INST 01-0290)
(RKAJ=1-14) subsystem.
y : ENC Unit # (0-1) dReplace the ENC unit when Replacement 2.2.9
the subsystem does not Replacing ENC
start up. Unit/SENC Unit
(REP 02-0830)
eIf the subsystem still does Replacement 2.2.12
not start up, replace the Replacing Additional
Additional Chassis of Rack Chassis of Rack
Mount Style, and start it up Mount Style (REP
again. 02-0990)
HJ3900 Backend down [Unit Abnormality of the connected Gather Replace it to the chassis Replacement 2.2.12
type error] (Unit-x, chassis was detected that can connect the Unit Replacing Additional
ENC-y) x : Unit ID # concerned. Chassis of Rack
(RKAJ=1-14) Mount Style (REP
y : ENC Unit # (0-1) 02-0990)
dStart up the subsystem Installation 1.7.1
again. Subsystem power on
(INST 01-0290)

MSG 03-0660-01
Collect the error

Message
code
Trace Trace Dump
HJ3Axy Unsupported CACHE It was detected that the Gather cReplace the memory to be Replacement 2.2.6
detected (CTL-x, unsupported Cache memory is installed in the Control Unit Replacing Cache
CACHE-y) installed. to the Cache memory in 1G Unit (REP 02-0540)
x : Control Unit # (0-1) bytes.
(RKM/RKS=0-1)
HL0000 Other CTL The processing became unable Gather cReplace the Control Unit Replacement 2.2.5
workQPanic to be continued because a whose CALM LED is on. Replacing Control
capacity of the task control Unit (REP 02-0390)
queue became full.
HL010x Machine check Machine check occurred. Gather
occurred (CTL-x) (Internal bus parity error
[200] occurred.)
HN0000 NAS-DMA forced The forced interruption of the Gather
stop failed NAS-DMA transfer failed.
HN0100 NAS-DMA error After the NAS-DMA failure Gather cCollect Full Dump from the Troubleshooting 7.5
(NAS-0, SPL, NNC- (NAS#0 special transfer Control Unit indicated by Collecting Memory
CACHE) (Transfer direction: From NNC W0100x CTL alarm which Dump (TRBL 07-
to cache), both Control Units of is displayed after this 0130)
the dual system were forced to message.
be detached by the debug
option.
HN0200 NAS-DMA error After the NAS-DMA failure Gather
(NAS-0, SPL, (NAS#0 special transfer
CACHE-NNC) (Transfer direction: From cache
to NNC), both Control Units of
the dual system were forced to
option.
(NAS-1, SPL, NNC- (NAS#1 special transfer
CACHE) (Transfer direction: From NNC
to cache), both Control Units of
option.
(NAS-1, SPL, (NAS#1 special transfer
CACHE-NNC) (Transfer direction: From cache
to NNC), both Control Units of
option.

MSG 03-0670-01
Collect the error

Message
code
Trace Trace Dump
HN0500 NAS-DMA error After the NAS-DMA failure (NAS Gather cCollect Full Dump from the Troubleshooting 7.5
(NAS-0, HC, CACHE- #0 non-specialized transfer Control Unit indicated by Collecting Memory
NNC) (Transfer direction: From Cache W0100x CTL alarm which Dump (TRBL 07-
to NNC), both Control Units of is displayed after this 0130)
the dual system were forced to message.
option.
HN0600 NAS-DMA error After the NAS-DMA failure (NAS Gather
(NAS-0, HC, NNC- #0 non-specialized transfer
CACHE) (Transfer direction: From NNC
to Cache), both Control Units of
option.
HN0700 NAS-DMA error After the NAS-DMA failure (NAS Gather cAfter this message is Chapter 6. Warning
(NAS-1, HC, NNC- #1 non-specialized transfer issued, get the full dump Messages (MSG 06-
CACHE) (Transfer direction: From Cache from a Control Unit related 0000)
to NNC), both Control Units of to a message, W0100x Troubleshooting 7.5
the dual system were forced to CTL alarm. Collecting Memory
be detached by the debug Dump (TRBL 07-
option. 0130)
HN0800 NAS-DMA error After the NAS-DMA failure (NAS Gather
(NAS-1, HC, CACHE- #1 non-specialized transfer
NNC) (Transfer direction: From NNC
to Cache), both Control Units of
option.
HZ0300 Not enough Cache The capacity of the cache Gather cIncrease the cache Addition/Subtraction/
memory to use memory is not sufficient to use memory capacity to 2 Relocation 1.4.4
QuickShadow the Copy-on write SnapShot Gbytes per controller. Adding a Cache Unit
function function. (ADD 01-0410)
HZ040x BRG DRAM internal The Dunit internal data path Gather cWhen W0100x CTL alarm Chapter 6. Warning
data path parity error parity error was detected. is displayed following this Messages (MSG 06-
detected x : Control Unit # (0-1) message, take recovery 0000)
[REGF10014D0, Bit2] actions according to the
(CTL-x) message.
HZ050x BRG SRAM double The SRAM two-bit ECC error Gather dReplace the Control Unit of Replacement 2.2.5
bit ECC error was detected. which the CALM LED lights Replacing Control
detected x : Control Unit # (0-1) on except for c. Unit (REP 02-0390)
[REGF1000388, Bit1]
(CTL-x)
HZ060x BRG DRAM double The DRAM two-bit ECC error Gather
bit ECC error was detected.
detected x : Control Unit # (0-1)
[REGF10014D0, Bit1]
(CTL-x)

MSG 03-0680-01
Collect the error

Message
code
Trace Trace Dump
HZ0700 BRG DRAM single bit The number of the DRAM single Gather
ECC threshold bit ECC errors reached the
expired threshold value.
[REGF10014D0, Bit0]
HZ0A00 BRG SRAM single bit The number of the SRAM single Gather cWhen W0100x CTL alarm Chapter 6. Warning
ECC error threshold bit ECC errors reached the is displayed following this Messages (MSG 06-
expired threshold value. message, take recovery 0000)
[REGF1000388, Bit0] actions according to the
message.
HZ0B0x CTL recovery failed Recovery of the Control Unit Gather cReplace not the inserted Replacement 2.2.5
[TWSI ERR] (CTL-x) failed because of the TWSI Control Unit but the other Replacing Control
failure occurred not in the Control Unit. (The Unit (REP 02-0390)
Control Unit, which was inserted replacement cannot be
during the recovery of the done when the subsystem
Control Unit while the power is on.)
subsystem power was on, but in
the other Control Unit.
HZ0C00 TWSI access error An error was detected during Gather cReplace the Control Unit Replacement 2.2.5
[Read, XX-YY-AA- the I2C reading. whose CALM LED is on. Replacing Control
BB] Unit (REP 02-0390)
HZ0D00 TWSI access error An error was detected during Gather
[Write, XX-YY-AA-BB] the I2C writing.
HZ0E00 TWSI access error The triple reading error was Gather
[3 times reading, X] detected during the I2C reading.
HZ0F00 PCDG1 error The PCDG1 error occurred. Gather cTake a recovery action Chapter 6. Warning
[Code x y] (CTL-z) x : Test ID according to W0100x CTL Messages (MSG 06-
y : Error code alarm displayed following 0000)
z : Control Unit # (0-1) this message.
HZ0G00 PCDG2 error The PCDG2 error occurred. Gather
[Code x y] (CTL-z) x : Test ID
y : Error code
z : Control Unit # (0-1)
HZ0H0x Directory Writing to the cache memory Gather cReplace the Control Unit Replacement 2.2.5
reinitialization failed failed when the directory was shown in this message. Replacing Control
(CTL-x) reinitialized after the other one Besides, take appropriate Unit (REP 02-0390)
of the dual Control Unit was actions against the
detached while the subsystem detachment of the other
was being booted. one of the dual Control
x : Control Unit # (0-1) Unit.
dIf the trouble is not solved, Replacement 2.2.6
replace all the cache Replacing Cache
memories in the Control Unit (REP 02-0540)
Unit displayed in this
message.

MSG 03-0690-01
Collect the error

Message
code
Trace Trace Dump
HZ0J00 TWSI access error A writing error occurred in the Gather cReplace the Control Unit Replacement 2.2.5
[Configuration register TWSI initialization (setting of the whose CALM LED is on. Replacing Control
write, XX-YY-AA-BB] TWSI-GPIO I/O attribute) at the Unit (REP 02-0390)
time of the subsystem boot.
HZ0K00 TWSI access error A write error occurred in the Gather
[Polarity inversion TWSI initialization (setting of the
register write, XX-YY- TWSI-GPIO polarity inversion)
AA-BB] at the time of the subsystem
start.
HZ0Lxx DSC detected IOLIST An illegal transition status of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
error I/O request list queue was is displayed following this Messages (MSG 06-
detected by the I/O execution message, take recovery 0000)
control. actions according to the
message.
HZ0M00 DM-LU write failed When the deliberate shutdown Gather cReboot the subsystem and Replacement 2.2.1
was performed, writing to the replace the Disk Drive Replacing Disk Drive
DM-LU failed owing to a trouble pointed out in the message, (REP 02-0050)
such as a drive error. HDU alarm.
dPerform the deliberate
shutdown again.
HZ0N0x Kernel processing The Kernel of the Control Units Gather cWhen W0100x CTL alarm Chapter 6. Warning
error (CTL-x) OS stopped illegally. is displayed following this Messages (MSG 06-
x : Control Unit # (0-1) message, take recovery 0000)
message.
HZ0Pxx Cache capacity The cache memory capacity Gather cReturn the cache memory Replacement 2.2.6
reduced although was reduced though Cache capacity to the original one. Replacing Cache
Cache Partition Partition Manager was valid Unit (REP 02-0540)
Manager enable (causing detachment of the both dReboot the disk array unit. Installation 1.7.1
Control Units). Subsystem power on
x : The original cache (INST 01-0290)
memory capacity per
Control Unit (G bytes)
(01-08)
HZ0Q00 DCTL micro access Logical illegality was detected Gather cWhen W0100x CTL alarm Chapter 6. Warning
error [PNDIRECTEN] because it tried to execute the is displayed following this Messages (MSG 06-
[REG82001D8C, direct memory access without message, take recovery 0000)
Bit30] turning on the PNDIRECTEN actions according to the
bit. message.
HZ0R00 DCTL micro access Logical illegality was detected Gather dReplace the Control Unit of Replacement 2.2.5
error [NPDIRECTEN] because it tried to execute the which the CALM LED lights Replacing Control
[REG82001D8C, direct memory access without on except for c. Unit (REP 02-0390)
Bit26] turning on the NPDIRECTEN
bit.

MSG 03-0700-01
Collect the error

Message
code
Trace Trace Dump
HZ0T00 Changing to Single The system start attribute was Gather cRestore the system start System Parameter
Mode failed as Cache changed although the Cache attribute. 4.2 (1) Setting Boot
Partition Manager is partition management function Options (SYSPR 04-
enable was effective. 0040)
Changing to Dual dRestart the subsystem. Installation 1.7
Active Mode failed as Power On/Off
Cache Partition Procedure (INST 01-
Manager is enable 0290)

MSG 03-0710-01
.
Chapter 4. Progress Message

Collect the error
Message
code
Trace Trace Dump
I0010x CTL recovered The Control Unit recovered by
(CTL-x) replacing the Control Unit in the
status of the subsystem
powering on.
I0020x CACHE recovered The blocked cache package
(CACHE-x) was made normal through the
Control Unit replacement
performed while the subsystem
power was on.
x : Cache Unit slot # (0,1,*)
(* means the recovery of
both 0 and 1.)
I00300 Battery recovered The battery voltage became
normal.
I0030x Battery recovered The battery voltage became
(Battery-x) normal.
x : Backup Battery Unit #
(0-1)
I0040x Battery backup circuit The battery charging circuit
recovered recovered.
I00500 FAN recovered The fan failure was recovered.
(CTL-Unit, FAN-x) x : FAN Assembly # (0-1)
I005xy FAN recovered The fan failure was recovered.
(Unit-x, FAN-y) x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
y : FAN Assembly # (0-1)
I00600 PS recovered The Power Unit (CTL/DRV PS)
(CTL-Unit, FAN-x) voltage became normal.
x : Power Unit # (0-1)
I006xy PS recovered The Power Unit (CTL/DRV PS)
(Unit-x, PS-y) voltage became normal.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
y : Power Unit # (0-1)
I007xy HDU recovered The Disk Drive was recovered.
(Unit-x, HDU-y) x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0000-01
Collect the error

Message
code
Trace Trace Dump
I008xy Spare HDU Data was recovered to the
recovered Spare Disk.
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I009xy Spare HDU The Spare Disk was recovered.
recovered x : Unit ID #
(Unit-x, HDU-y) (RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I00Axy Loop recovered The loop recovered.
(PATH-x, LOOP-y) x : Path # (RKM/RKS=0-1)
y : Loop # (0-1)
I00Bxy ENC recovered A SW P/K failure was solved.
(Unit-x, ENC-y) x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
(0-1)
I00D0x UPS recovered The UPS was recovered.
(UPS-x) x : UPS # (0-1)
I00E00 Battery removed The Backup Battery Unit was cReplace the Backup Replacement 2.2.2
removed from the subsystem Battery Unit concerned, Replacing Backup
when a battery failure had and then install the battery Battery Unit (REP
occurred. unit in the subsystem. 02-0240)
I00E0x Battery removed The Backup Battery Unit was
(Battery-x) removed from the subsystem
when a battery failure had
occurred.
(0-1)
I00F00 Battery SW OFF The switch of the Backup c Replace the Backup Replacement 2.2.2
Battery Unit was turned off when Battery Unit concerned, Replacing Backup
a battery failure had occurred. and then turn on the switch Battery Unit (REP
I00F0x Battery SW OFF The switch of the Backup of the battery unit that has 02-0240)
(Battery-x) Battery Unit was turned off when been inserted.
a battery failure had occurred.
(0-1)
I01000 Battery Thermal Abnormal temperature was cReplace the Backup Replacement 2.2.2
alarm detected in the battery. Battery Unit concerned. Replacing Backup
I0100x Battery Thermal Abnormal temperature was Battery Unit (REP
alarm detected in the battery. 02-0240)
(Battery-x) x : Backup Battery Unit #
(0-1)

MSG 04-0010-01
Collect the error

Message
code
Trace Trace Dump
I02000 Battery alarm A battery voltage error or a cReplace the Backup Replacement 2.2.2
battery charging circuit error Battery Unit concerned. Replacing Backup
occurred when a battery failure Battery Unit (REP
had occurred. 02-0240)
I0200x Battery alarm A battery voltage error or a
(Battery-x) battery charging circuit error
occurred when a battery failure
had occurred.
(0-1)
I02100 FAN status Detailed information at the time
(CTL-Unit, FAN-x, of the fan module failure.
Code-y) x : FAN Assembly # (0-1)
y : Detail code
I021xy FAN status Detailed information at the time
(Unit-x, FAN-y, Code- of the fan module failure.
z) x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
y : FAN Assembly # (0-1)
z : Detail code
I030xy Path recovered by The path was recovered by an
web operation operation from the Web.
(Remote-x, Path-y) x : Remote DF # (0)
y : Path # (RKM/RKS=0-1)
I031xy Path recovered The path recovered
automatically automatically.
(Remote-x, Path-y) x : Remote DF # (0)
y : Path # (RKM/RKS=0-1)
I04000 Unreadable PIN Data has been restored due to
recovered recovery of the drives from the
unreadable PIN.
I10000 Subsystem is ready The unit is ready.
I11000 All raid group All RAID groups were deleted.

initialized
I111xx RAID group deleted All LUs were deleted.
(RG-x) x : RAID group #
(RKM/RKS=0-44)
I12000 ALL LU initialized All LUs were deleted.
(This is also displayed when the
LU #0 is created.)
I12100 LU deleted LUs were deleted.
(LU-x) x : LU #
(RKM/RKS=0-2047)
I12200 LU format completed LU formatting was completed.
(LU-x) x : LU #
(RKM/RKS=0-2047)

MSG 04-0020-01
Collect the error

Message
code
Trace Trace Dump
I12300 LU format failed LU formatting stopped Gather cWhen the message Chapter 6. Warning
(LU-x) abnormally. W060xy HDU alarm is Messages (MSG 06-
x : LU # displayed at the same time, 0030)
(RKM/RKS=0-2047) follow the recovery method.
dA Confirm that a Disk Drive
to which the objective LU is
allotted is mounted.
eIf it is confirmed in the step
d that all the Disk Drives
are installed and no failure
has occurred in them,
format the object LU again.
I12400 LU format start An LU formatting was started.
(LU-x) x : LU #
(RKM/RKS=0-2047)
I12500 Unified LUs Dissolution of all LU unification
separated (to dissolve unification of all the
(UNI:LU-x) unified LUs and to split them
into internal LUs) was executed.
x : LU # of a unified LU to be
spitted. (RKM/RKS=0-
2047)
I12600 Last LU separated A separation of a final LU of a
from unified LU unified LU (to separate the last
(UNI:LU-x) one of the internal LUs which
have been combined with a
unified LU) was executed.
x : LU # of a unified LU to be
spitted. (RKM/RKS=0-
2047)
I12700 LU reappeared An internal LU(s) was validated
(LU-x) again through splitting of all
unified LUs or a separation of a
final LU.
x : An LU # of an internal LU
which has been separated
and validated.
(RKM/RKS=0-2047)
I12800 LU format start The I/O instruction issued by a cStart the execution of the
[Host I/O is not host computer could not be I/O instructed by a host
executable] executed because the multiple computer after making sure
(LU-x) formatting must be started. that all the LU formatting
x : LU # are completed.
(RKM/RKS=0-2047)

MSG 04-0030-01
Collect the error

Message
code
Trace Trace Dump
I130xy Spare HDU defined A Spare Disk is registered.
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I131xy Spare HDU deleted Registration of a disk is called
(Unit-x, HDU-y) off.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I140xy System copy started System copy was started. cDo not change the
(Unit-x, HDU-y) x : Unit ID # configuration during the
(RKM/RKS=0) system copy.
(RKAJ=1-14) Because of copying the
y : Disk Drive # (0-14) system information after the
configuration change, if the
operations for changing the
system configuration (LU
creation, format, LU owner
right change) are
overlapped, the message
may be displayed multiple
times.
I141xy System copy System copy terminated
completed normally.
(RKM/RKS=0)
(RKAJ=1-14)
I142xy System copy failed System copy failed. Gather cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) x : Unit ID # When you want to make Replacing Disk Drive
(RKM/RKS=0) sure of a model name and (REP 02-0050)
(RKAJ=1-14) drive firmware revision of Replacement 1.1.3
y : Disk Drive # (0-14) the Disk Drive, refer to Procedure for making
I150xy Data recovery started Data recovery was started.
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I151xy Data recovery Data recovery terminated
completed normally.
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0040-01
Collect the error

Message
code
Trace Trace Dump
I152xy Data recovery failed Data recovery failed. Gather cWhen the I301AT SATA Troubleshooting
(Unit-x, HDU-y) x : Unit ID # HDU error or I301xy HDU 6.1.8 Data recovery
(RKM/RKS=0) error is displayed before does not terminate
(RKAJ/RKAJAT=1-14) this message, refer to normally : Case 1
y : Disk Drive # (0-14) Troubleshooting 6.1.8 (Read error) (TRBL
Data recovery does not 06-0510)
terminate normally : Case 1 Troubleshooting
(Read error). 6.1.9 Data recovery
When the W061AT SATA does not terminate
Spare HDU alarm, normally : Case 2
W061xy Spare HDU (Disk Drive failure)
alarm, W0GJ00 Spare (TRBL 06-0520).
HDU alarm [RKA] or
W0GK00 Spare HDU
alarm [RKAJ] is displayed
before this message, refer
to Troubleshooting 6.1.9
Data recovery does not
terminate normally : Case 2
(Disk Drive failure).
I153xy Data recovery partial Recovery of data is finished Gather cSee Troubleshooting 6.1.7 Troubleshooting
(Unit-x, HDU-y) normally. (Incomplete writing is The power cannot be 6.1.7 The power
registered.) turned off : Case 4 (Cache cannot be turned off :
x : Unit ID # memory failure). Case 4 (Cache
(RKM/RKS=0) memory failure)
(RKAJ/RKAJAT=1-14) (TRBL 06-0490)
I15Axy Dynamic sparing start Dynamic sparing started.
(Unit-x, HDU-y) [z] x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
z : Detailed code
I160xx FLASH other revision When the Control Unit was
edit inserted in the state in which the
(REV-x) subsystem power was on, the
version up of the flash was
detected.
x : Micro (Rev.)
I18000 PIN-over recovered The PIN threshold value
lowered.
I19000 Online micro-update The hot replacement of the
completed microprogram was completed.

MSG 04-0050-01
Collect the error

Message
code
Trace Trace Dump
I1A00x Permanent LU LU residence is not changed. cSet the unit in the ready
disable x : Default Control Unit # state and turn off the
(Default CTL-x) (0-2) power, then turn on the
(In case of 2, it is applied power again.
to both Control Units.)
I1A10x Permanent LU LU residence is deleted. (When
deleted RAID group/LU is deleted)
(Default CTL-x) x : Default Control Unit #
(0-2)
I1A2xy Permanent LU LU residence OFF warning was
warning recovered called off.
(CTL-x, ERR-y) x : Default Control Unit #
y : Factor code
0: Too large LU
1: Cache access error
2: Regression of Control
Unit
3: Abnormal battery
voltage
4: Abnormal battery
charging circuit
5: Larger than PIN
threshold value
I1A30x Permanent LU enable The Turbo LU residence
(Default CTL-x) function was turned on.
x : Default Control Unit #
(0-1)
I1B000 Forced parity Forced parity correction
correction started processing was started.
I1B100 Forced parity Forced parity correction
correction completed processing was finished.
I1C0xy Loop diagnostic start Loop diagnosis was started.
(Path-x, Loop-y) x : Path # (RKM/RKS=0-1)
y : Loop # (0-1)
I1C1xy Loop diagnostic end Loop diagnosis was finished.
(Path-x, Loop-y) x : Path # (RKM/RKS=0-1)
y : Loop # (0-1)
I1E000 Online verify Check of the frames with odd
completed [odd unit] numbers was completed in the
online verification.
I1E100 Online verify Check of the frames with even
completed [even unit] numbers was completed in the
I1E200 LU access enable Read/Write to P-VOL enabled. Gather
[QuickShadow pair x : LU #
canceled] (RKM/RKS=0-2047)
(LU-x)

MSG 04-0060-01
Collect the error

Message
code
Trace Trace Dump
I1E300 LU access disable Read/Write to P-VOL disabled. Gather cCancel all the pairs of the
[QuickShadow x : LU # V-VOL in the P-VOL.
restore failed] (RKM/RKS=0-2047)
(LU-x)
I1F000 Data pool load failed The loading of pool information Gather
failed.
I1G00x PSUE occurred All pairs in the data pool Gather cCancel the pair being
[QuickShadow] changed to PSUE status. PSUE once, and then make
(Data pool-x) x : Data pool # (0-1) a pair again.
I1G100 PSUE occurred All pairs to which P-VOL Gather
(LU-x) belongs changed to PSUE
status.
x: LU #
(RKM/RKS=0-2047)
I1G200 PSUE occurred A pair, whose status was Gather cRefer to Troubleshooting Troubleshooting
(ShadowImage) changed to PSUE,exists. Chapter 9. Data Collection Chapter 9. Data
when a Failure Occurs in Collection when a
Program Product (P.P.). Failure Occurs in
Program Product
(P.P.) (TRBL 09-
0000)
I1G300 CTL recovery start Because the recovery operation
(CTL-x) has been started, do not pull out
the Control Unit.
I1G400 Quick Format started The Quick Format started a job
(LU-x) that executes a formatting in the
background.
x : LU #
(RKM/RKS=0-2047)
I1G500 Quick Format A formatting of the whole area in
completed (LU-x) the LU was completed.
x : LU #
(RKM/RKS=0-2047)
I1G600 QuickFormat QuickFormat was suspended cUser data may be lost. System Parameter
Suspended since power shutdown and Confirm the situation to 3.3 Setting of LU
battery lost occurred, and the user. (SYSPR 03-0140)
map controlling the formatted And execute format again.
area was lost. Afterwards, restore the
backup data.
I1G70x FC I/F ports remain The Fibre Channel interface cWhen Storage Navigator
offline (CTL-x) board was made offline Modular completes
according to the instruction execution of the procedure
issued by Storage Navigator for hot replacement of the
Modular at the time of the microprogram, the Fibre
microprogram hot replacement. Channel interface port
x : Control Unit # (0-1) becomes online.

MSG 04-0070-01
Collect the error

Message
code
Trace Trace Dump
I1G80x FC I/F ports change The Fibre Channel interface
to online (CTL-x) board was made online
according to the instruction
issued by Storage Navigator
Modular at the time of the
microprogram hot replacement.
I1G900 SATA HDU limit over The count of drive errors cReplace the Disk Drive. Replacement 2.2.1
[Self-monitoring] exceeded its threshold value. Replacing Disk Drive
(Unit-x, HDU-y) x : Unit ID # (REP 02-0050)
(RKAJAT=1-29)
I1GA00 Forced parity The forced parity correction was
correction is stopped suspended because the Storage
[user directions] Navigator Modular instructed for
the suspension during the
forced parity correction process.
I1GB00 Forced parity The forced parity correction,
correction is started which is made while the
(LU-x) subsystem power was on, was
started.
x : LU #
(RKM/RKS=0-2047)
I1GC00 Forced parity The forced parity correction,
correction is which is made while the
completed subsystem power was on, was
(LU-x) completed.
x : LU #
(RKM/RKS=0-2047)
I1GD00 Forced parity The forced parity correction was
correction is stopped stopped because of a drive
[HDU alarm] detachment.
I1GE00 Forced parity The forced parity correction was
correction is stopped stopped because a number of
[Too Many registered unwritten data per LU
Unreadable PINs] exceeded a certain value.
(LU-x) x : LU #
(RKM/RKS=0-2047)
I1GG00 HDU changed to The configuration information Gather
spare (Unit-x, HDU-y) was changed as follows. The
data drive, which had been
restored in the Active Spare
mode, was changed to a Spare
Drive.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0080-01
Collect the error

Message
code
Trace Trace Dump
I1GH00 Forced parity The forced parity correction of Gather cRefer to Troubleshooting Troubleshooting
correction stopped by the target LU was suspended 6.1.3 [Recovery method- 6.1.3 [Recovery
too many PINs because the PIN over for each 4] : PIN over occurred method-4] : PIN over
(RG-x, LU-y) RAID group became near. during the forced parity occurred during the
x : RAID group # correction. forced parity
(RKM/RKS=0-44) correction. (TRBL
y : LU # 06-0190)
(RKM/RKS=0-2047)
I1GJ00 Forced parity The forced parity correction of Gather
correction stopped by the target LU stopped because
too many PINs PIN-over for each partition
(PTT-x, LU-y) became close.
x : Partition #
(RKS/RKM=0-15)
y : LU #
(RKM/RKS=0-2047)
I1GK00 Forced parity The forced parity correction of Gather
correction stopped by the target LU stopped because
too many PINs PIN-over for each DIR became
(DIR-x, LU-y) close.
x : Directory # (0 or 1)
y : LU #
(RKM/RKS=0-2047)
I1GT00 All DM-LU canceled Only one DM-LU was defined
and the system released DM-LU
in WARNING with write of all
DM-LU disabled.

MSG 04-0090-01
Collect the error

Message
code
Trace Trace Dump
I1GU00 Modification of Cache The setting of cache partitions Gather cRefer to Troubleshooting Troubleshooting
Partition skipped (PIN could not be changed because 6.1.12 A failure occurred 6.1.12 A failure
or Unreadable PIN) pinned data existed. during operation : Case 2 occurred during
(LA/LRC error)
(TRBL 06-0570)
d When either of the following Chapter 6. Warning
messages is displayed Messages (MSG 06-
before this message, take 0060)
recovery actions according
to the message.
W0G0xy Unreadable PIN
detected
W0G100 Unreadable PIN
detected
e Check whether pinned data Troubleshooting
exist or not. 10.2.4 Displaying
When the pinned data Logical Unit Failure
exist, refer to Data Information
Troubleshooting 6.1.11 A (TRBL 10-0250)
failure occurred during Troubleshooting
operation : Case 1 (PIN 6.1.11 A failure
over). occurred during
operation : Case 1
(PIN over) (TRBL 06-
0550)
f Boot the subsystem after Installation 1.7.1
executing the deliberate Subsystem power on
shutdown in order to (INST 01-0290)
change the setting of cache
partitions.

MSG 04-0100-01
Collect the error

Message
code
Trace Trace Dump
I301AT SATA HDU error PDEV should be blocked Gather cRefer to Troubleshooting Troubleshooting
(Unit-x, HDU-y) because of an error, but it is not 6.1.9 Data recovery does 6.1.9 Data recovery
blocked since redundancy is not terminate normally : does not terminate
insufficient. Case 2 (Disk Drive failure). normally : Case 2
x : Unit ID # (Disk Drive failure)
(RKAJAT=1-29) (TRBL 06-0520)
I301xy HDU error PDEV should be blocked
(Unit-x, HDU-y) because of an error, but it is not
blocked since redundancy is
insufficient.
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
I30200 System HDU error There is a drive which cannot Gather cSolve the failure according
handle the system before the to I142xy System copy
system is ready. failed indicated before the
message.
I303xy HDU read capacity The insertion of the Disk Drive cReplace it with the Disk Replacement 2.2.1
failed failed because the capacity of Drive of the same capacity Replacing Disk Drive
(Unit-x, HDU-y) the replaced Disk Drive was or more as the Disk Drive (REP 02-0050)
small. before the replacement.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I304xy HDU spin up failed An insertion of a Disk Drive cPull out the Disk Drive and Replacement 2.2.1
(Unit-x, HDU-y) failed because of a Disk Drive insert it again.(*1) Replacing Disk Drive
failure. dIf the trouble is not solved (REP 02-0050)
x : Unit ID # in spite of the above
(RKM/RKS=0) operation, replace the Disk
(RKAJ/RKAJAT=1-14) Drive.
I305xy HDU read capacity An insertion of a Disk Drive cPull out the Disk Drive and Replacement 2.2.1
failed failed because of an illegal read insert it again.(*1) Replacing Disk Drive
(Unit-x, HDU-y) capacity. dIf the trouble is not solved (REP 02-0050)
x : Unit ID # in spite of the above
(RKM/RKS=0) operation, replace the Disk
(RKAJ/RKAJAT=1-14) Drive.
*1 : If this message is issued frequently, it is suspected that one of the following cases have occurred.
Symptom : Spin-up operation repeats interruption and restart because of contention with the RAID Manager
command in the case where the ShadowImage in-system replication function is used.
Corrective action : Contact the system manager. If RAID Manager command is issued by polling in a short
period, check the manual and change the value to be appropriate.
Symptom : A spin up operation repeats an interruption and restart because LU switchings occur frequently.
Corrective action : Check the setting of the owner right to the LU and change it so that the LU switching does not
occur owing to an I/O command issued by a host.

MSG 04-0110-01
Collect the error

Message
code
Trace Trace Dump
I306xy Response time over The drive took longer than 200 Gather
(Unit-x, HDU-y) ms or 300 ms to respond.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I30700 Details information The drive took longer than 200 Gather
(x ms: WRITE) ms or 300 ms to respond.
(WRITE)
x : Time taken for the drive to
respond
I30800 Details information The drive took longer than 200 Gather
(x ms: READ) ms or 300 ms to respond.
(READ)
x : Time taken for the drive to
respond
I30900 HDU startup diag Insertion of the Disk Drive failed Gather cReplace the blocked Disk Replacement 2.2.1
failed when it was inserted with the Drive. Replacing Disk Drive
power turned on. (REP 02-0050)
I410xy HDU error over The disk at the position cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) indicated with x and y exceeds When you want to make Replacing Disk Drive
[HDRVC] the threshold value because of sure of a model name and (REP 02-0050)
an error in the recovered drive firmware revision of Replacement 1.1.3
mechanism system. the Disk Drive, refer to Procedure for making
x : Unit ID # Replacement 1.1.3 sure of model name
(RKM/RKS=0) Procedure for making sure and drive firmware of
(RKAJ/RKAJAT=1-14) of model name and drive Disk Drive (REP 01-
y : Disk Drive # (0-14) firmware of Disk Drive. 0100)
I411xy HDU error over The disk at the position
(Unit-x, HDU-y) indicated with x and y exceeds
[HDUNR] the threshold value because of
an error in the un-recovered
mechanism system.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
[MDRCV] the threshold value because of
an error in the recovered
medium system.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0120-01
Collect the error

Message
code
Trace Trace Dump
[MDUNR] the threshold value because of sure of a model name and (REP 02-0050)
an error in the un-recovered drive firmware revision of Replacement 1.1.3
medium system. the Disk Drive, refer to Procedure for making
[RWRCV] the threshold value because of
an error in the recovered R/W
system.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
[RWUNR] the threshold value because of
R/W system.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
[IFRCV] the threshold value because of
an error in the recovered disk
I/F.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
[IFUNR] the threshold value because of
an error in the un-recovered disk
I/F.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0130-01
Collect the error

Message
code
Trace Trace Dump
[CHRCV] the threshold value because of sure of a model name and (REP 02-0050)
an error in the recovered drive firmware revision of Replacement 1.1.3
hardware. the Disk Drive, refer to Procedure for making
[CHUNR] the threshold value because of
hardware.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I41Axy HDU error over The disk at the position
[SCRCV] the threshold value because of
an error in the recovered SCSI
I/F.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I41Bxy HDU error over The disk at the position
[SCUNR] the threshold value because of
SCSI I/F.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I41Cxy HDU error over The disk at the position
[ONVRCV] the threshold value because of a
correctable error in the on-line
verification.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0140-01
Collect the error

Message
code
Trace Trace Dump
I41Dxy HDU error over The disk at the position cReplace the Disk Drive. Replacement 2.2.1
[ONVUNR] the threshold value because of sure of a model name and (REP 02-0050)
an uncorrectable error in the on- drive firmware revision of Replacement 1.1.3
line verification. the Disk Drive, refer to Procedure for making
I41Exy HDU error over In the disk located at a position
(Unit-x, HDU-y) shown as xy, the error count
[ONVHER] exceeded its threshold value
owing to hardware errors (errors
other than recovered error and
media error) occurred in an
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I41Fxy HDU error over An excess over the threshold
(Unit-x,HDU-y) value of the reassignment
[REAOV] execution count occurred.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I4200x Online micro-update The Control Unit was micro-
(CTL-x) replaced in the ON state.
I430xy HDU byte check error A failure was detected by the Gather cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) disk drive diagnosis. When you want to make Replacing Disk Drive
x : Unit ID # sure of a model name and (REP 02-0050)
(RKM/RKS=0) drive firmware revision of Replacement 1.1.3
(RKAJ/RKAJAT=1-14) the Disk Drive, refer to Procedure for making
y : Disk Drive # (0-14) Replacement 1.1.3 sure of model name

MSG 04-0150-01
Collect the error

Message
code
Trace Trace Dump
I501xy ENC change Info Report on SW P/K to be cReplace the ENC Unit on Replacement 2.2.9
(Unit-x, ENC-y) replaced. (Additional Chassis) which the EALM LED lights Replacing ENC
x : Unit ID # up. Unit/SENC Unit
(RKM/RKS=0) (REP 02-0830)
(RKAJ/RKAJAT=1-14)
(0-1)
I5010x ENC change Info The Control Unit was micro- cReplace the Control Unit Replacement 2.2.5
(CTL-x) replaced in the ON state. (Basic whose CALM LED is on. Replacing Control
Chassis) Unit (REP 02-0390)
I502xy HDU change Info Report on a drive to be cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) replaced. When you want to make Replacing Disk Drive
x : Unit ID # sure of a model name and (REP 02-0050)
(RKM/RKS=0) drive firmware revision of Replacement 1.1.3
(RKAJ/RKAJAT=1-14) the Disk Drive, refer to Procedure for making
y : Disk Drive # (0-14) Replacement 1.1.3 sure of model name
I5030x Change Info Report on CTL to be replaced. cReplace the Control Unit Replacement 2.2.5
(CTL-x) x : Control Unit # (0-1) whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
I510xy D_PT error A drive port failure. c Replace the Disk Drive. Replacement 2.2.1
(HDU Unit-x, HDU-y) x : Unit ID # When you want to make Replacing Disk Drive
(RKM/RKS=0) sure of a model name and (REP 02-0050)
(RKAJ= 1-14) drive firmware revision of Replacement 1.1.3
y : Disk Drive # (0-14) the Disk Drive, refer to Procedure for making
I511xy D_PT error 1 Drive blockade factor report Replacement 1.1.3 sure of model name
(HDU Unit-x, HDU-y) (Drive port failure 1) Procedure for making sure and drive firmware of
x : Unit ID # of model name and drive Disk Drive (REP 01-
(RKM/RKS=0) firmware of Disk Drive. 0100)
(RKAJ=1-14)
I512xy D_PT error 2 Drive blockade factor report
(HDU Unit-x, HDU-y) (Drive port failure 2)
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
(HDU Unit-x, HDU-y) (Drive port failure 3)
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)

MSG 04-0160-01
Collect the error

Message
code
Trace Trace Dump
(HDU Unit-x, (Drive port failure 5)
HDU-y) x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
I516xy D_PT error 6 Drive port failure 6 occurred.
(HDU Unit-x, x : Unit ID #
HDU-y) (RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I51700 D_PT error 7 Drive port failure 7 occurred. cWhen the message Chapter 6. Warning
(HDU Unit-x, x : Unit ID # W060AT SATA HDU Messages (MSG 06-
HDU-y) (RKAJAT=1-14) alarm is displayed at the 0020)
y : Disk Drive # (0-14) same time, follow the
recovery method.
I520xy Loop error2 Exceeded threshold value of the
(Path-x ,Loop-y) loop failure 2 (command
rejection, inconsistent
transferred data length, frame
time-out, ABTS rejection,
PLOG/PRLI time-out, and log-in
error) count (Threshold value: 9)
x : Path # (RKM/RKS=0-1)
y : Loop # (0-1)
(Path-x, Loop-y) loop failure 3 (illegal frame
reception and ABTS/PRQ time-
out) count (Threshold value: 34)
y : Loop # (0-1)
(Path-x, Loop-y) loop failure 4 (intermittent failure
of the PDEV time-out) count
(Threshold value: 34)
y : Loop # (0-1)
(Path-x, Loop-y) loop failure 4.
y : Loop # (0-1)
I524xy HDU response A Disk Drive failure was cReplace the Disk Drive. Replacement 2.2.1
timeout detected by frame sending When you want to make Replacing Disk Drive
(Unit-x, HDU-y) diagnosis. sure of a model name and (REP 02-0050)
x : Unit ID # drive firmware revision of Replacement 1.1.3
(RKM/RKS=0) the Disk Drive, refer to Procedure for making
(RKAJ/RKAJAT=1-14) Replacement 1.1.3 sure of model name
y : Disk Drive # (0-14) Procedure for making sure and drive firmware of

MSG 04-0170-01
Collect the error

Message
code
Trace Trace Dump
I525xy Loop error7 Exceeded threshold value of the cWhen the message Chapter 6. Warning
(Path-x, Loop-y) loop failure 7. W080xy Loop alarm is Messages (MSG 06-
x : Path # (RKM=0-1) displayed at the same time, 0040)
y : Loop # (0-1) follow the recovery method.
I530xy ENC error An ENC Unit error (SW
[ENC NG] malfunction) occurred.
(RKM/RKS=0)
(RKAJ=1-14)
I531xy ENC error An ENC Unit error (unusable
[NO SES HDU] SES drive) occurred.
(RKM/RKS=0)
(RKAJ=1-14)
I532xy ENC error An ENC Unit error (detection of
[ENC check NG] a link trouble or request for the
(Unit-x, ENC-y) ENC Unit replacement)
occurred.
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
I533xy ENC error An ENC Unit error (ENC cable
[CBL not connect] non-connection) occurred.
(RKM/RKS=0)
(RKAJ=1-14)
I534xy ENC error An ENC Unit error (ENC
[ENC CABLE OUT] detachment owing to ENC cable
(Unit-x, ENC-y) disconnection) occurred.
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
I53500 PSUE occurred When Copy-on-write SnapShot Gather cRefer to Troubleshooting Troubleshooting
[QuickShadow] was executed, it was moved to Chapter 9 Data Collection Chapter 9. Data
PSUE. when a Failure Occurs in Collection when a
Program Product (P.P.) to Failure Occurs in
collect necessary Program Product
information. (P.P.) (TRBL 09-
0000)
I53600 ENC error Inf.[LPF0] The other ENC Unit was cReplace the SENC Unit Replacement 2.2.9
detached because the LPFO concerned whose EALM Replacing ENC
was detected. LED is on. Unit/SENC Unit
I53700 ENC error Inf.[MPF] The ENC Unit was detached (REP 02-0830)
because the LPF was detected.

MSG 04-0180-01
Collect the error

Message
code
Trace Trace Dump
I53800 ENC error Inf.[SPF] The ENC Unit was detached cReplace the SENC Unit Replacement 2.2.9
because the SPF was detected. concerned whose EALM Replacing ENC
LED is on. Unit/SENC Unit
(REP 02-0830)
I53A00 Host connector The Host Connector was
recovered (Portxy-z) recovered from a failure.
y : Port # (A-D)
z : Host Connector # (0-1)
I540xy ENC recovery failed The insertion of the ENC Unit cVerify that the ENC cable is
(Unit-x, ENC-y) failed (Additional Chassis) correctly connected.
x : Unit ID # dReplace the ENC Unit Replacement 2.2.9
(RKM/RKS=0) designated in the message. Replacing ENC
(RKAJ=1-14) Unit/SENC Unit
y : ENC Unit # (0-1) (REP 02-0830)
I5F100 FAN speed error [Too Abnormality occurred in the FAN c Since one of the following
low despite Middle- rotational speed of the messages is displayed
speed setting] subsystem. after this message, take
(Unit-x, FAN-y) x : Unit ID # recovery actions according
I5F200 FAN speed error [Too (RKM/RKS=0) to the message.
high despite Middle- (RKAJ/RKAJAT=1-14) W0100x CTL alarm
speed setting] y : Fan Assembly W04100 FAN alarm
(Unit-x, FAN-y) 00 : Fan Assembly #0(*), W050xy PS alarm
I5F300 FAN speed error [Too FAN #0 W05100 PS alarm
low despite High- 01 : Fan Assembly #0(*),
speed setting] FAN #1
(Unit-x, FAN-y) 02 : Fan Assembly #0,
I5F400 FAN speed error [Too FAN #2
low despite Low- 10 : Fan Assembly #1(*),
speed setting] (Unit-x, FAN #0
FAN-y) 11 : Fan Assembly #1(*),
I5F500 FAN speed error [Too FAN #1
high despite Low- 12 : Fan Assembly #1,
speed setting] (Unit-x, FAN #2
FAN-y) (* : Power Unit for the
additional chassis)
I5Y000 Obstacle HDU search Automatic diagnosis of backend
start loop started.
When this message appears,
please restart the maintenance
work which interrupted after the
maintenance work is temporarily
interrupted, and the message
code of I5Y100" appears .
I5Y100 Obstacle HDU search Automatic diagnosis of backend
end loop terminated.

MSG 04-0190-01
Collect the error

Message
code
Trace Trace Dump
I5Y2xy Obstacle HDU Failed part (HDU) of backend cIt plans it according to the
bypassed loop was identified. message of W060xy,
(HDU Unit-x, HDU-y) x : Unit ID # W0GG00, W0GH00
(RKM/RKS=0) HDU alarm and W061xy,
(RKAJ/RKAJAT=1-14) W0GJ00, W0GK00
y : Disk Drive # (0-14) Spare HDU alarm or
I301xy HDU error.
I5Y300 Obstacle HDU search Automatic Loop failure isolation
retry diagnosis is retried.
I5Y400 BKE diagnostic result It is possible that the loop failure Gather cFollow the recovery Troubleshooting
(Unit-x, HDU-y) was caused by a drive. measure Troubleshooting 6.1.14 A failure
x : Unit ID # 6.1.14 A failure occurred occurred during
(RKM/RKS=0) during operation : Case 4 operation : Case 4
(RKAJ=0-29) (Loop failure) for the (Loop failure) (TRBL
(RKAJAT=1-29) maintenance. 06-0600)
I5Y500 BKE diagnostic result It is possible that the loop failure Gather
(Unit-x, ENC-y) was caused by an ENC Unit.
x : Unit ID #
(RKM/RKS=0)
(RKAJ=0-29)
(RKAJAT=1-29)
(0-1)
I5Y60x BKE diagnostic result It is possible that the loop failure Gather
(CTL-x) was caused by a Control Unit.
I5Y700 BKE diagnostic result It is possible that the loop failure Gather
(Unit-CTU-x, ENC-y) was caused by an ENC cable.
x : Unit ID #
(RKAJ=0-1)
(RKAJAT=1-2)
(0-1)
BKE diagnostic result It is possible that the loop failure Gather
(Unit-x-y, ENC-z) was caused by an ENC cable.
x, y : Unit ID #
(RKM=0)
(RKAJ=0-29)
(RKAT=1-29)
z : ENC Unit/SENC Unit #
(0-1)
I5Y800 BKE diagnostic result Failed part cannot be identified. cCollect Simple trace and Troubleshooting 7.3
(unknown) contact the Technical Collecting simple
Support Center. trace (TRBL 07-
0040)

MSG 04-0200-01
Collect the error

Message
code
Trace Trace Dump
I5Y900 Part change priority Indicates priorities of failed parts cFollow the recovery Troubleshooting
(number-x) to be replaced. measure Troubleshooting 6.1.14 A failure
x : Priorities # (1-8) 6.1.14 A failure occurred occurred during
during operation : Case 4 operation : Case 4
(Loop failure) for the (Loop failure) (TRBL
maintenance. 06-0600)
I5YA00 SENC error over The count of SENC errors cReplace the SENC Unit Replacement 2.2.9
(Unit-x, ENC-y) exceeded its threshold value. concerned whose EALM Replacing ENC
x : Unit ID # LED is on. Unit/SENC Unit
(RKAJAT=1-29) (REP 02-0830)
y : SENC Unit # (0-1)
I5YB00 Loop S1 error The error count of LOOP S1
(Path-x, Loop-y) exceeded its threshold value.
x : Path #
(RKAJAT=0-1)
y : Loop # (0-1)
I5YC00 Obstacle ENC Failed part of backend loop cReplace the SENC Unit Replacement 2.2.9
detected (SENC) was identified. concerned whose EALM Replacing ENC
(Unit-x, ENC-y) x : Unit ID # LED is on. Unit/SENC Unit
(RKAJAT=1-29) (REP 02-0830)
(0-1)
I5YD00 ENC Error A fail-over of the SENC internal
[LPF0 occurred] path occurred.
I5YE00 ENC Error A SATA port failure occurred.
[SPF occurred]
I5YF00 ENC Error A SATA management port
[MPF occurred] failure occurred.

MSG 04-0210-01
Collect the error

Message
code
Trace Trace Dump
I5YG00 Unit# ERR An incorrect order of connecting cCheck if the Power Unit is Installation 3.4.7
(Unit-x, Loop-y) the subsystems (in one of the installed firmly. When no (6) Installing Power
systems) Power Unit is installed, Unit (INST 03-0600)
x : Unit ID # install the two Power Units.
(RKAJ=0-29) dCheck if the READY LED
(RKAJAT=1-29) of the Power Unit is on.
y : Loop # (0-1) Since the AC Power Unit
Switch may not be turned
on, the power cable may
not be connected firmly, or
the power may not be
supplied when the READY
LED of the Power Unit is
off, check them.
eCheck the connections of
ENC cables. If any one of
them is loosely connected,
reconnect it firmly.
fCheck if the device ID is Installation 3.4.7
set correctly. If it is (1-2) Setting Device
wrongly set, reset it. ID number (INST 03-
0520)
gCheck if the device Installation 3.4.7
identification switch is set (1-3) Setting the
correctly. If it is wrongly subsystem
set, reset it. identification switch
(INST 03-0520)
hTurn off all the Power Unit Installation 1.7
Switches of the failed Power On/Off
subsystem, and then turn Procedure (INST 01-
them on. 0290)
iCheck the state of the ENC Replacement 2.2.9
Unit in the relevant loop of Replacing ENC
the relevant unit. Unit/SENC Unit
(REP 02-0830)
jSolve the trouble found in Installation 1.7
the checks above and Power On/Off
restart the subsystem. Procedure (INST 01-
0290)
kAnalyze the failure following Troubleshooting 8.1
Troubleshooting 8.1 Trouble Analysis by
Trouble Analysis by LED LED Indication of
Indication of Front Bezel Front Bezel (TRBL
for the Unit # concerned. 08-0000)

MSG 04-0220-01
Collect the error

Message
code
Trace Trace Dump
I5YJ00 ENC error An ENC Unit error (unusable cWhen one of the following
[SES access error] SES drive) occurred. messages is displayed at
(Unit-x, ENC-y) x : Unit ID # the same time, follow the
(RKAJ=0-29) recovery procedure given
y : ENC Unit # (0-1) by the message.
W0GA00 ENC alarm
W0GB00 SENC alarm
W0GC00 ENC alarm
W0GD00 SENC alarm
I5YH00 Unit ADD Connect An incorrect order of connecting cCheck the cable connection
error the subsystems (occurred status of the concerned
(Unit-x, Loop-y) during addition of the subsystem Unit # or later, using the
made while the power is turned ACE tool of the Storage
on) Navigator Modular.
x : Unit ID # dCheck the device ID of the
(RKAJ=0-29) concerned Unit # or later,
(RKAJAT=1-29) using the ACE tool of the
y : Loop # (0-1) Storage Navigator Modular.
eCheck the Unit ID # Addition/Subtraction/
displayed by the message Relocation 1.3.1
after I8040x Unit ADD Work immediately
FAIL is displayed, and after abnormal
perform termination (ADD 01-
Addition/Subtraction/ 0110)
Relocation 1.3.1 Work
immediately after abnormal
termination (if not
performed, the system may
go down).
fReset the abnormal part, Addition/Subtraction/
and add it again. Relocation
Chapter 1. Adding
Optional Components
(ADD 01-0000)
I5YL00 ENC microprogram A drive error (5/2x00) was cReplace the ENC Replacement 2.2.9
download info. detected during a downloading Unit/SENC Unit on which Replacing ENC
[SENC] of the ENC microprogram (SR the EALM LED lights up. Unit/SENC Unit
(Unit-x, ENC-y) firmware). (REP 02-0830)
x : Unit ID #
(RKAJAT=1-29)
I5YM00 ENC microprogram Replacement of the ENC
download info. microprogram was completed
[Revision Check NG] normally, however, the
(Unit-x, CTL-y) microprogram that replaced was
not the expected one.
x : Unit ID #
(RKAJ=0-29)
y : Control Unit # (0-1)

MSG 04-0230-01
Collect the error

Message
code
Trace Trace Dump
I5YP00 ENC microprogram Replacement of the ENC cReplace the ENC Replacement 2.2.9
download info. microprogram was completed Unit/SENC Unit on which Replacing ENC
[Revision Check NG] normally, however, the the EALM LED lights up. Unit/SENC Unit
(Unit-x, ENC-y) microprogram that replaced was (REP 02-0830)
not the expected one.
x : Unit ID #
(RKAJ=0-29)
I5YPAT ENC microprogram Replacement of the ENC
download info. microprogram was completed
[SENC] normally, however, the
[Revision Check NG] microprogram that replaced was
(Unit-x, ENC-y) not the expected one.
x : Unit ID #
(RKAJAT=1-29)
I5YQ00 Loop errorS1 Number of the loop S1 errors cRefer to Troubleshooting Troubleshooting
(Path-x, Loop-y) exceeded its threshold value. 6.1.14 A failure occurred 6.1.14 A failure
x : Unit ID # during operation : Case 4 occurred during
(RKAJAT=1-29) (Loop failure). operation : Case 4
y : Loop # (0-1) (Loop failure) (TRBL
06-0600)
I5YR00 D_PT errorS1 Number of the drive S1 errors cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) exceeded its threshold value. Replacing Disk Drive
x : Unit ID # (REP 02-0050)
(RKAJAT=1-29)
I5YT00 BAD_ALPA error The RTR was blocked due to cWhen the message
(Unit-x, ENC-y) the BAD_ALPA failure. W090AT SENC alarm is
x : Unit ID # displayed at the same time,
(RKAJAT=1-29) follow the recovery method.
(0-1)
I5YU00 SENC errorS1 The SENC was blocked due to cWhen the message
(Unit-x, ENC-y) the PDEV time out failure. W090AT SENC alarm is
(RKAJAT=1-30) follow the recovery method.
(0-1)
I5YV00 ENC error inf [CUDG The ENC Unit concerned was cTake recovery actions Chapter 6. Warning
ECTLREGERR, detached because an ECTL according to a message Messages (MSG 06-
code-x] register error occurred during W090xy ENC alarm 0040)
the CUDG of the ENC. displayed following this
x : Reading of the register on message.
the ENC that shows
details of an error.

MSG 04-0240-01
Collect the error

Message
code
Trace Trace Dump
I5YW00 ENC error inf The ENC Unit concerned was cTake recovery actions Chapter 6. Warning
[ENCCOMERR, detached because an according to a message Messages (MSG 06-
code-x] ENCCOMERR occurred in the W090xy ENC alarm 0040)
ENC. displayed before this
x : Reading of the register on message.
the ENC that shows
I5YX00 ENC error inf The ENC Unit concerned was
[I2CERR code-x] detached because the I2C
failure occurred during the
CUDG of the ENC.
x : Reading of the register on
the ENC that shows
I5YY00 ENC error inf The ENC Unit concerned was
[PKERR code-x] detached because a PK failure
occurred during the CUDG of
the ENC.
the ENC that shows
I5YZ0x CTL recovery failed Recovery of the Control Unit Gather cReplace a Control Unit on Replacement 2.2.5
[TWSI ERR] (CTL-x) failed because of a TWSI failure the opposite side of the Replacing Control
of a Control Unit on the opposite Control Unit that was Unit (REP 02-0390)
side of the Control Unit that was inserted. (The replacement
inserted during the recovery cannot be done when the
action taken while the power subsystem power is on.)
was on.
I5Z0xy Loop test start Loop test was started.
(Unit-x, ENC-y) (Additional Chassis)
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
(0-1)
I5Z00x Loop test start Loop test was started. (Basic
(Unit-x, ENC-y) Chassis)
I5Z1xy Fail bypassed Loop test terminated normally.
(Path-x, Loop-y) x : Path #
(RKM/RKS=0-1)
y : Loop # (0-1)
I5Z2xy Fail remains Loop test failed.
(Path-x, Loop-y) x : Path #
(RKM/RKS=0-1)
y : Loop # (0-1)

MSG 04-0250-01
Collect the error

Message
code
Trace Trace Dump
I5Z3xy Failure search start
The failed part isolation started. cRefer to Troubleshooting Troubleshooting
(Path-x, Loop-y) x : Path # 6.1.14 A failure occurred 6.1.14 A failure
(RKM/RKS=0-1) during operation : Case 4 occurred during
y : Loop # (0-1) (Loop failure). operation : Case 4
I5Z4xy Failure search end The failed part isolation (Loop failure) (TRBL
(Path-x, Loop-y) terminated. 06-0600)
x : Path #
(RKM/RKS=0-1)
y : Loop # (0-1)
I5Z5xy Failure check OK The diagnosis terminated
(Path-x, Loop-y) normally (without a failed part).
x : Path #
(RKM/RKS=0-1)
y : Loop # (0-1)
I5Z6xy Failure check NG The diagnosis terminated
(Path-x, Loop-y) abnormally (with a failed part).
x : Path #
(RKM/RKS=0-1)
y : Loop # (0-1)
I5Z70x Failure search The SES drive cannot be used
aborted [NOSES] during the diagnosis.
(Unit-x) x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I5Z8xy Failure check The diagnosis for the loop cSelect the detached loop Troubleshooting
impossible specified could not be done. correctly and execute the 6.1.14 A failure
(Path-x, Loop-y) (That was because the diagnosis for it. occurred during
diagnosis was attempted to be Refer to Troubleshooting operation : Case 4
done for the undetached loop 6.1.14 A failure occurred (Loop failure) (TRBL
when either of the main and during operation : Case 4 06-0600)
alternating loops was detached. (Loop failure) for the
x : Path # (RKM/RKS=0-1) maintenance.
y : Loop # (0-1)
I5Z900 HDD bypass start HDD bypass start
I5ZA00 HDD bypass HDD bypass succeeded

succeeded
I5ZB00 HDD bypass failed Abnormal termination of a failed
drive bypassing
I5ZD0x HDD bypass aborted The SES drive was disabled
[NO SES] (Unit-xx) during a bypassing.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
I5ZE00 HDD bypass end The failed drive bypassing
ended.

MSG 04-0260-01
Collect the error

Message
code
Trace Trace Dump
I6010x LAN failure The LAN state is invalid. cConfirm the LAN cable.
(CTL-x) x : Control Unit # (0-1) dA Replace the Control Unit Replacement 2.2.5
of the No. indicated with x. Replacing Control
Unit (REP 02-0390)
I60200 Link failure Link failures were detected more Gather cWhen the failure occurs Addition/Subtraction/
[LIMIT OVER] than the threshold value. during an addition of the Relocation 1.6.2
RKAJ performed while the Connecting multiple
subsystem power is turned RKAJs (ADD 01-
on, make sure of the 0550)
procedure referring to the
Addition/Subtraction/
Relocation 1.6.2
Connecting multiple
RKAJs.
dWhen one of the following
messages is displayed
before this message, take
to the message.
W0100x CTL alarm
W060AT SATA HDU
alarm
W060xy, W0GG00,
W0GH00 HDU alarm
W061AT SATA Spare
HDU alarm
W061xy, W0GJ00,
W0GK00 Spare HDU
alarm
W090xy, W0GA00,
W0GC00 ENC alarm
W090AT, W0GB00,
W0GD00 SENC alarm
I301AT SATA HDU
error
I301xy HDU error
eRefer to Troubleshooting Troubleshooting
06-0600)

MSG 04-0270-01
Collect the error

Message
code
Trace Trace Dump
I603xy Obstacle part Failed part was not identified by Gather cWhen one of the following
unknown Loop diagnosis. messages is displayed
(Path-x, Loop-y) x : Path # (RKM/RKS=0-1) before this message, take
y : Loop # (0-1) recovery actions according
to the message.
W0100x CTL alarm
W060AT SATA HDU
alarm
W060xy, W0GG00,
W0GH00 HDU alarm
W061AT SATA Spare
HDU alarm
W061xy, W0GJ00,
W0GK00 Spare HDU
alarm
W090xy, W0GA00,
W0GC00 ENC alarm
W090AT, W0GB00,
W0GD00 SENC alarm
I301AT SATA HDU
error
I301xy HDU error
6.1.14 A failure
6.1.14 A failure occurred
during operation : Case 4occurred during
06-0600)
I604xy ENC recovery NG Since a Disk Drive (y or z) Gather cReplace the Disk Drive (y Replacement 2.2.1
HDU-NG connected to an ENC to be or z) to recover it, then Replacing Disk Drive
(Unit-x, HDU-y or z) recovered had a failure, this insert the ENC Unit again. (REP 02-0050)
ENC was not recovered.
(Additional Chassis)
x : Unit ID #
(RKAJ/RKAJAT=1-14)
y or z : Disk Drive # (0-14)
I605xy ENC recovery NG Since an ENC to be recovered cReplace the ENC Unit on Replacement 2.2.9
ENC-NG had a failure, it was not which the EALM LED lights Replacing ENC
(Unit-x, ENC-y) recovered. (Additional Chassis) up. Unit/SENC Unit
x : Unit ID # (REP 02-0830)
(RKAJ/RKAJAT=1-14)
(0-1)
I6050x ENC recovery NG Since an ENC to be recovered Gather cReplace the Control Unit Replacement 2.2.5
ENC-NG had a failure, it was not whose CALM LED is on. Replacing Control
(CTL-x) recovered. (Basic Chassis) Unit (REP 02-0390)

MSG 04-0280-01
Collect the error

Message
code
Trace Trace Dump
I606xy ENC Thermal alarm Because a temperature error cCheck if the environment is
(Unit-x, ENC-y) was detected in the ENC of the set in accordance with the
extended subsystem, the ENC specifications.
concerned was blocked. dCheck if the fan is not in the
x : Unit ID # state in which it has been
(RKAJ/RKAJAT=1-14) given an alarm.
y : ENC Unit/SENC Unit # eReplace the ENC Unit Replacement 2.2.9
(0-1) whose EALM LED is on. Replacing ENC
Unit/SENC Unit
(REP 02-0830)
I6070x CACHE error over The number of cache cRemove the Cache Unit in Replacement 2.2.6
(CACHE-x) [CRECT] correctable error occurrences which the failure occurred Replacing Cache
exceeded its threshold value in after the sequential Unit (REP 02-0540)
the DMA transfer. (during the shutdown.
single system operation.)
x : Cache Unit slot #
(RKM/RKS=0-1)
I60800 LU change over The LU switching occurred cCheck the access paths
frequently. from the host computer to
each LU again and make
accesses to the each LU
done by the Control Unit
having the owner right.
I609xy The cable disconnection caused Gather
ENC cable error cInsert the ENC cable again,
(Unit-x, ENC-y)
a blockade of the corresponding and then remove and insert
ENC. the blocked ENC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ=1-14)
I60D0x Data pool enough The use rate of the pool went Gather
free down below the PFUS
(Data pool-x) cancellation threshold value
specified by the user.
x : pool #0, 1
I61000 ENC error inf. Because a parity error occurred
[parity error] in the ENC, the ENC concerned
was blocked.
I61700 ENC error inf. Because a CUDG ECTL register
[CUDG error occurred in the ENC, the
ECTLREGERR] ENC concerned was blocked.
I61800 ENC error inf. Because a CUDG SRAM parity
[CUDG SRAMERR] error occurred in the ENC, the
ENC concerned was blocked.
I61900 ENC error inf. Because a CUDG ENCCOM
[CUDG error occurred in the ENC, the
ENCCOMERR] ENC concerned was blocked

MSG 04-0290-01
Collect the error

Message
code
Trace Trace Dump
I61A00 ENC error inf. Because an ENCCOM error cWhen one of the following
[ENCCOMERR] occurred in the ENC, the ENC messages is displayed at
concerned was blocked. the same time, follow the
recovery procedure given
by the message.
W0GA00 ENC alarm
W0GB00 SENC alarm
W0GC00 ENC alarm
W0GD00 SENC alarm
I61B00 ENC error inf. Because a parity error occurred
[ECTL force test] in the ENC, the ENC concerned
was blocked.
I61C00 SES error inf. The ENC was blocked because
[SES-HDU error] both of the two SES drives
became unable to access the
ENC.
I61D00 Shutdown Warning The cache volatilized because cFrom the next time on, turn
the previous sequential off the power using the
shutdown had not been main switch.
executed.
I61E00 PIN-over A parity correction was Gather
[Forced parity terminated because an amount
correction] of pinned data exceeded its
threshold value.
I61F00 ENC error inf. A ready time-out of the ENC in
[CUDG ENC another system was detected.
RDYTOV]
I6200x Link error in the Link failures occurred more Gather c Refer to the Troubleshooting 6.3
attached link times than the threshold value in Troubleshooting 6.3 Procedure for
(Port-x) the link, to which the port Procedure for Recovery Recovery from Path
concerned is connected, within from Path Blockade when Blockade when the
a certain period. the TrueCopy remote TrueCopy remote
x : Port # (A or D) replication Function Is replication Function Is
I621xy Link error in the path The illegal transferred data Gather Used. Used (TRBL 06-
length occurred more times than 1170)
the threshold value within a
certain period caused by a
failure that had occurred in the
path concerned.
y : Target ID (0)
I6220x Link down time-out A state in which no link up is Gather
(Port-x) done has kept on longer than
the regulated time at the port for
which a path has been set.
x: Port # (A or B)

MSG 04-0300-01
Collect the error

Message
code
Trace Trace Dump
I62300 Path not connected <In the case of the direct Gather cRefer to the Troubleshooting 6.3
connection> Troubleshooting 6.3 Procedure for
The remote DF that attempted Procedure for Recovery Recovery from Path
to log in to the set path is not from Path Blockade when Blockade when the
connected, or the LoopMap of the TrueCopy remote TrueCopy remote
the LILP is not connected one- replication Function Is replication Function Is
to-one. Used. Used (TRBL 06-
<In the case of the connection 1170)
via SW>
A serial number (WWN) of the
remote DF that attempted to
log in to the set path is not
registered in the name server
of the SW.
I62400 Path login resource Insufficiency of a resource of the Gather
shortage remote DF was reported in a
response from the PLOGI when
a log-in to the set path was
done.
I6250x Fabric connection The sending and response of Gather
failed (Port-x) FLOGI, PLOGI, RSCN, etc. to
the SW terminated abnormally
when a log-in to the set path
was done in the case of the
connection via the SW.
x : Port # (A or D)
I62600 Path login failed Sending and response of PLOGI Gather
and PRLI done at the time of a
log-in to the set path terminated
abnormally.
I62700 Link down time-out To a port for which a path has Gather
[Path] been set but no link up to the
path has been done for longer
than the regulated time, a
setting of another path was
requested.
I62800 Path alarm for CTL The path was detached as a Gather cReplace the Control Unit Replacement 2.2.5
alarm result of the CTL detachment. whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
I62900 Remote equipment ID Path detach occurred due to Gather cRefer to Troubleshooting Troubleshooting 6.3
error inconsistency of remote 6.3 Procedure for Procedure for
equipment IDs. Recovery from Path Recovery from Path
Blockade when the Blockade when the
TrueCopy remote TrueCopy remote
replication Function Is replication Function Is
Used. Used (TRBL 06-
1170)

MSG 04-0310-01
Collect the error

Message
code
Trace Trace Dump
I62B00 Port un-mounting A path detachment occurred Gather c Refer to Troubleshooting Troubleshooting 6.3
error because the port was not 6.3 Procedure for Procedure for
installed. Recovery from Path Recovery from Path
I62D00 Remote option A path detachment occurred Gather Blockade when the Blockade when the
disable because the optional TrueCopy TrueCopy remote TrueCopy remote
[TrueCopy Basic] remote replication function of replication Function Is replication Function Is
the remote DF was locked. Used. Used (TRBL 06-
1170)
I63000 Write uncompleted An incomplete writing was Gather cReformat the LU System Parameter
block detected detected at the time of the concerned. 3.3 [Procedure e-F]
staging in a data copying from Formatting LU
the primary LU to the secondary (SYSPR 03-0280)
LU.
I64000 Simple trace failed The simple trace failed because cPerform the deliberate
an RAM disk was not created. shutdown.
dThen power on the
subsystem and collect the
simple trace again after the
subsystem becomes ready.
I64100 Simple trace interrupt The simple trace was Gather cWait for a while (about ten
interrupted because an minutes) and collect the
automatic dump was performed. simple trace again.
I69000 E-Mail parameter set A setting of the E-mail Gather cCheck the E-mail
failed parameters failed when making parameters and make the
initial settings of the E-mail. setting again.
I69100 E-Mail send failed A sending of a mail for informing Gather
of a failure occurrence failed.
I6A000 ENC error inf. The ENC concerned was
[REGPERR] detached because a REGPERR
occurred in the ENC.
[RAMPER] detached because a RAMPER
occurred in the ENC.
[WDTCNTPERR] detached because a
WDTCNTPERR occurred in the
ENC.
I6A300 Power failure Power failure was detected Gather cCollect a simple trace. Troubleshooting 7.3
occurred while Additional Battery Unit Refer to Troubleshooting Collecting simple
Mode. 7.3 Collecting simple trace (TRBL 07-
trace. 0040)
I6B0xy ENC recovery NG An ENC recovery failure c Collect Simple trace and Troubleshooting 7.3
Loop-NG (Additional Chassis) contact the Technical Collecting simple
(Unit-x, ENC-y) x : Unit ID # Support Center. trace (TRBL 07-
(RKM/RKS=0) 0040)
(RKAJ=1-14)

MSG 04-0320-01
Collect the error

Message
code
Trace Trace Dump
I6D00x Data pool no free The free capacity of the pool ran Gather
(Data pool-x) short.
x : pool # (0, 1)
I6D10x Data pool threshold The use rate of the pool Gather cSecure the data pool free
over exceeded its threshold value capacity
(Data pool-x) specified by the user.
x : pool # (0, 1)
I6D300 Unreadable PIN During a restoration using Copy- Gather cRefer to Troubleshooting Troubleshooting
resisted on-write SnapShot, an 6.1.16 Copy-on-write 6.1.16 A failure in
(Unit-x, HDU-y, LU-z) incomplete writing is registered SnapShot occurs. Copy-on-write
with the P-Vol, which is a SnapShot occurs
copying destination, because (TRBL 06-1120)
there is unreadable area on the
pool side. (Unit/HDU is a drive
that is a source of the copying;
LU is a destination of the
copying.)
x : Unit ID #
(RKM/RKS=0)
(RKAJ=0-29)
(RKAJAT=1-29)
z : LU #
(RKM/RKS=0-2047)
I6D400 Remote path setting The version of the microprogram Gather cThe configuration is not
unsupported on the on the secondary side does not supported by the
remote Subsystem support to make a path Microrevision installed in
extending over subsystems of the subsystem. Check the
different models. configuration again.
I6D500 PSUE occurred The subsystem was started up Gather cRefer to Troubleshooting Troubleshooting 6.3
[TrueCopy Basic] with the cache that had 6.3 Procedure for Procedure for
volatilized owing to a power Recovery from Path Recovery from Path
failure when a TrueCopy remote Blockade when the Blockade when the
replication pair is in the status TrueCopy remote TrueCopy remote
other than SMPL. replication Function Is replication Function Is
1170)
I6D600 SENC error [Queue The Queue Full occurred and cReplace the SENC Unit Replacement 2.2.9
Full] the count of SENC errors concerned whose EALM Replacing ENC
(Unit-x, ENC-y) exceeded its threshold value. LED is on. Unit/SENC Unit
x : Unit ID # (REP 02-0830)
(RKAJAT=1-29)

MSG 04-0330-01
Collect the error

Message
code
Trace Trace Dump
I6D700 SENC error The SENC was detached cReplace the SENC Unit Replacement 2.2.9
[Communication Path] because of a communication concerned whose EALM Replacing ENC
(Unit-x, ENC-y) path failure. LED is on. Unit/SENC Unit
x : Unit ID # dIf the failure is not solved, (REP 02-0830)
(RKAJAT=1-29) replace the SENC Unit on
y : SENC Unit # (0-1) the opposite side.
eIf not recovered yet, call the
Technical Support Center
for coping with troubles.
I6D800 Disk initialization error The Disk initialization error cReplace the SENC Unit Replacement 2.2.9
(Unit-x, ENC-y) occurred and the count of SENC concerned whose EALM Replacing ENC
errors exceeded its threshold LED is on. Unit/SENC Unit
value. (REP 02-0830)
x : Unit ID #
(RKAJAT=1-29)
I6D900 SENC logic error SENC self contradiction.
(RKAJAT=1-29)
I6DA00 CDB check code The Check code error occurred
error and the SENC was detached.
(RKAJAT=1-29)
I6DB00 Unit Type Error A unit of inappropriate FC/SATA cCheck the type and
(Unit-x) type was added. connection of the unit.
x : Unit ID #
(RKAJ=0-29)
(RKAJAT=1-29)
I6DC00 ENC error inf. SES access to the ENC
[SES access error] concerned resulted in an error.
I6DD00 HDU error over The error count of a disk at a c Replace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) location shown as xy exceeded When you want to make Replacing Disk Drive
[LNKTO] its threshold value because of a sure of a model name and (REP 02-0050)
drive link error (time-out) of drive firmware revision of Replacement 1.1.3
online verification. the Disk Drive, refer to Procedure for making
(RKAJAT=1-29) Procedure for making sure and drive firmware of
y : Disk Drive # (0-14) of model name and drive Disk Drive (REP 01-
I6DE00 HDU error over The error count of a disk at a firmware of Disk Drive. 0100)
(Unit-x, HDU-y) location shown as xy exceeded
[LNKUT] its threshold value because of a
drive link error (other than a
time-out) of online verification.
x : Unit ID #
(RKAJAT=1-29)

MSG 04-0340-01
Collect the error

Message
code
Trace Trace Dump
I6DF00 HDU error over The error count of a disk at a cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) location shown as xy exceeded When you want to make Replacing Disk Drive
[ONVLNKTO] its threshold value because of a sure of a model name and (REP 02-0050)
drive link error (time-out) of drive firmware revision of Replacement 1.1.3
online verification. the Disk Drive, refer to Procedure for making
(RKAJAT=1-29) Procedure for making sure and drive firmware of
y : Disk Drive # (0-14) of model name and drive Disk Drive (REP 01-
I6DG00 HDU error over The error count of a disk at a cReplace the Disk Drive. Replacement 2.2.1
(Unit-x, HDU-y) location shown as xy exceeded Replacing Disk Drive
[ONVLNKUT] its threshold value because of a (REP 02-0050)
drive link error (time-out) of
x : Unit ID #
(RKAJAT=1-29)
I6DH00 Staging failed The correction cannot be made Gather cAfter the forced parity Troubleshooting 7.3
[Forced parity because of the forced parity correction, which is made Collecting simple
correction] correction which is made while while the subsystem power trace (TRBL 07-
(LU-x) the subsystem power is turned is turned on, is completed, 0040)
on get the simple trace and
x : LU # contact the Technical
(RKM/RKS=0-2047) Support Center for coping
with problems.
I6DJ00 Forced parity The LU that required the forced
correction LU is gone parity correction disappeared.
I6DK00 Incomplete differential An incomplete DDCB was Gather c Split the TrueCopy remote
data detected detected in the cascade replicationpair. When
connection of Copy-on-write forming the pair again, form
SnapShot with TrueCopy Basic. a Copy-on-write SnapShot
I6DL00 P-VOL read failed The P-VOL became unable to pair first and then form a
[TrueCopy Basic] be read. TrueCopy remote
I6DM00 QuickShadow SMPL Copy-on-write SnapShot replication pair.
command received received a command to split its
[TrueCopy Basic] pair.
I6DN00 Uncorrectable forced The LU, the forced restoration
parity correction LU is for which by means of parity
gone could not be continued,
disappeared.
I6DP00 Bitmap Data Error Data of a TrueCopy remote cSplit a pair whose LU,
[TrueCopy Basic] replication pair may have been which is in RAID 1 or RAID
lost. 1+0 TC and has a capacity
of 1 T bytes or larger, is in
the PSUE status. If an LU
next to the LU concerned is
in the PSUE status, split it
also.

MSG 04-0350-01
Collect the error

Message
code
Trace Trace Dump
I6DQ00 Unit ADD start FAIL Addition of the subsystem, cCheck the Unit ID # Addition/Subtraction/
[Online micro-update] which was made while the displayed by the message Relocation 1.3.1
power was turned on, failed to after I8040x Unit ADD Work immediately
be started because FAIL is displayed, and after abnormal
microprogram replacement in perform termination (ADD 01-
the online mode was in Addition/Subtraction/Reloca 0110)
progress. tion 1.3.1 Work
termination (if not
go down).
dMake the addition after the Addition/Subtraction/
microprogram replacement Relocation
in the online mode is Chapter 1. Adding
completed. Optional Components
(ADD 01-0000)
I6DR00 Unit ADD start FAIL Addition of the subsystem, cCheck the Unit ID # Addition/Subtraction/
[cable error] which was made while the displayed by the message Relocation 1.3.1
(Loop-x) power was turned on, failed after I8040x Unit ADD Work immediately
because the cables required for FAIL is displayed, and after abnormal
adding the relevant loop of the perform termination (ADD 01-
FC subsystem were not Addition/Subtraction/ 0110)
connected. Relocation 1.3.1 Work
x : Loop # (0-1) immediately after abnormal
termination (if not
go down).
dCorrectly connect the two Installation
cables required for adding Chapter 3. Installing
the relevant loop of the FC Rackmount Model
subsystem. (INST 03-0000)
Addition/Subtraction/
Relocation
Chapter 1. Adding
Optional Components
(ADD 01-0000)
I6DS00 Cable connection The ENC cable was connected
detected to the ENC Unit path of the
(Unit-x, ENC-y, subsystem.
Path-z) x : Unit ID #
(RKAJAT=1-29)
y : SENC Unit #
(RKAJAT=0-1)
z : Path #
(RKM/RKS=0-1)
I6DY00 Drive Response Diag Drive response time delay was Gather
NG detected.
(RKM/RKS=0)
(RKAJ=0-29)
(RKAJAT=1-29)

MSG 04-0360-01

MSG 04-0360-01
Collect the error

Message
code
Trace Trace Dump
I6DZ00 Unit missing Position mapping mismatch was cIf this message is displayed
(Unit-x, Loop-y) detected for both loops of the same
(the subsystem unit was Unit #, perform d, e and
missing). f. If it is displayed for
x : Unit ID # only one loop, perform f.
(RKM/RKS=0) dAnalyze the failure following Troubleshooting 8.1
(RKAJ=0-29) Troubleshooting 8.1 Trouble Analysis by
(RKAJAT=1-29) Trouble Analysis by LED LED Indication of
y : Loop # (0 or 1) Indication of Front Bezel Front Bezel (TRBL
for the Unit # concerned. 08-0000)
eCheck the mounting and
connecting conditions of
the subsystem.
fFollow the recovery method
of W080xy Loop alarm.
I6E000 Unit ADD ENC INIT During the RKAJ addition that c Check the Unit ID # Addition/Subtraction/
data error was made while the power was displayed by the message Relocation 1.3.1
[PRESESWRERR, on, the SES Write failure after I8040x Unit ADD Work immediately
code-x] occurred in the ENC FAIL is displayed, and after abnormal
initialization. perform termination (ADD 01-
x : Reading of the register on Addition/Subtraction/ 0110)
the ENC that shows Relocation 1.3.1 Work
details of an error. immediately after abnormal
I6E100 Unit ADD ENC INIT During the RKAJ addition that termination (if not
data error was made while the power was performed, the system may
[SHERR, code-x] on, the SES Read failure go down).
occurred in the ENC dRefer to the Unit number of Replacement 2.2.9
initialization. I800x Unit ADD start and Replacing ENC
x : Reading of the register on the Loop number of I8010x Unit/SENC Unit
the ENC that shows Unit ADD start displayed (REP 02-0830)
details of an error. before this message, and
replace the ENC unit (ENC-
0 for Loop #0 and ENC-1
for Loop #1) corresponding
to the Unit number and the
Loop number.
eMake the addition of the Addition/Subtraction/
RKAJ again. Relocation 1.6
Adding the RKAJ to
the Rack Frame
(ADD 01-0490)
I6E200 ENC error inf The SES Write failure occurred cTake recovery actions Chapter 6. Warning
[PRESESWRERR, during the CUDG on the ENC. according to a message Messages (MSG 06-
code-x] x : Reading of the register on W090xy ENC alarm 0040)
the ENC that shows displayed following this
details of an error. message.
I6E300 ENC error inf The SES Read failure occurred
[SHERR, code-x] during the CUDG on the ENC.
the ENC that shows

MSG 04-0370-01

MSG 04-0370-01
Collect the error

Message
code
Trace Trace Dump
I6E400 Ixxxxxx Ownership The change of the LU unit failed Gather cTry again after giving some
change by LU failed because of the heavy I/O load pause to operation of
(LU-x) given by a host computer. Storage Navigator Modular
x : LU # or RAID Manager.
(RKM/RKS=0-2047) dWhen operation of RAID
Manager failed, a pair
status of TrueCopy remote
replication, ShadowImage
in-system replication, or
has been changed to
PSUE. Therefore, change
the status from PSUE first.
eWhen the operation is not
successful after trying it
twice, stop the job and then
perform the operation.
I6E500 TWSI access error An error was detected during Gather
[Read, XX-YY-AA- the I2C reading.
BB]
I6E600 TWSI access error An error was detected during Gather
[Write, XX-YY-AA-BB] the I2C writing.
I6E700 TWSI access error The triple reading error was Gather
[3 times reading, XX] detected during the I2C reading.
I6E800 Unit ADD ENC INIT During RKAJ addition that was Gather c Check the Unit ID # Addition/Subtraction/
data error made while the power was on, displayed by the message Relocation 1.3.1
[ENCCOMERR, an ENCCOMERR occurred in after I8040x Unit ADD Work immediately
code-x] the ENC. FAIL is displayed, and after abnormal
x : Reading of the register on perform termination (ADD 01-
the ENC that shows Addition/Subtraction/ 0110)
details of an error. Relocation 1.3.1 Work
I6E900 Unit ADD ENC INIT The SWCUDG error (E-CTL Gather immediately after abnormal
data error register error) occurred in the termination (if not
[CUDGECTLREG, ENC initialization during the performed, the system may
code-x] RKAJ addition that was made go down).
while the power was on. dReplace the ENC Unit. Replacement 2.2.9
x : Reading of the register on Replacing ENC
the ENC that shows Unit/SENC Unit
details of an error. (REP 02-0830)
I6EA00 Unit ADD ENC INIT The TWSI failure occurred in the Gather
data error ENC initialization during the
[TWSIERR, code-x] RKAJ addition that was made
while the power was on.
the ENC that shows

MSG 04-0380-01
Collect the error

Message
code
Trace Trace Dump
I6EB00 Unit ADD ENC INIT The PK failure occurred in the Gather cCheck the Unit ID # Addition/Subtraction/
data error ENC initialization during the displayed by the message Relocation 1.3.1
[PKERR, code-x] RKAJ addition that was made after I8040x Unit ADD Work immediately
while the power was on. FAIL is displayed, and after abnormal
x : Reading of the register on perform termination (ADD 01-
the ENC that shows Addition/Subtraction/ 0110)
details of an error. Relocation 1.3.1 Work
termination (if not
go down).
d Replace the ENC Unit. Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
I6EC000 PCDG1 error The PCDG1 error occurred. Gather cTake a recovery action Chapter 6. Warning
[Code x y] (NNC-z) x : Test ID according to W0100x CTL Messages (MSG 06-
y : Error code alarm displayed following 0000)
z : NNC No. this message.
I6ED000 PCDG2 error The PCDG2 error occurred. Gather
[Code x y] (NNC-z) x : Test ID
y : Error code
z : NNC No.
I6EE01 PS status Detailed information on the c Since one of the following
(Unit-x, PS-y) [PS] trouble in the AC/DC Power Unit messages is displayed
is shown. after this message, take
I6EE02 PS status
(Unit-x, PS-y) [FAN0] x : Unit ID # to the message.
I6EE03 PS status (RKM/RKS=0) W050xy PS alarm
(Unit-x, PS-y) (RKAJ=0-29) W05100 PS alarm
[PS, FAN0] (RKAJAT=1-29) W0G400 PS alarm
I6EE04 PS status y : Power Unit # (0 or 1) W0G500 PS alarm
W0G600 PS alarm
(Unit-x, PS-y) [FAN1]
W0G700 PS alarm
I6EE05 PS status
(Unit-x, PS-y)
[PS, FAN1]
I6EE06 PS status
(Unit-x, PS-y)
[FAN0, FAN1]
I6EE07 PS status
(Unit-x, PS-y)
[PS, FAN0, FAN1]
I6EE08 PS status
(Unit-x, PS-y)

MSG 04-0390-01
Collect the error

Message
code
Trace Trace Dump
I6EF00 Forced parity Because the parity correction in
correction LU the hot condition was executed
changed status or skipped, LUs in the state in
which the status of the parity
correction in the hot condition is
Unrestored 1 (execution of or
instruction to skip the parity
correction in the hot condition is
necessary) no longer existed.
I6EG00 PIN over recovered The excess of the threshold
[directory threshold] value of pinned data in each
(DIR-x) directory was solved. (Directory:
Unit of cache domain
management)
I6EH00 PIN over recovered The excess of the threshold
[partition threshold] value of pinned data in each
(DIR-x, PTT-y) partition was solved.
y : Partition #
(RKS/RKM=0-15)
I6EJ00 PIN over recovered The excess of the threshold
[RAID group value of pinned data in a RAID
threshold] group was solved.
(DIR-x, RG-y) x : Directory # (0 or 1)
y : RAID group #
(RKM/RKS=0-44)
I6EK00 DM-LU canceled The write disabled DM-LU was
(LU-x) cancelled (Display of the DM-LU
cancellation message).
x : LU #
(RKM/RKS=0-2047)
I6EL00 DM-LU read failed When the subsystem was Gather cReplace the Disk Drive Replacement 2.2.1
booted, reading from the DM-LU pointed out in the message, Replacing Disk Drive
failed owing to a trouble such as HDU alarm. (Resolve the (REP 02-0050)
a drive error. pair and reform it.)
I6EM00 DM-LU recovered The DM-LU was recovered from
(LU-x) the trouble.
x : LU #
(RKM/RKS=0-2047)
I6EN00 DM-LU write enable The deliberate shutdown was
enabled because the DM-LU,
which was accessible for
writing, was created.

MSG 04-0400-01
Collect the error

Message
code
Trace Trace Dump
I6EP00 Changing to Single The system start attribute was Gather cRestore the system start System Parameter
Mode failed as Cache changed although the Cache attribute. 4.2 (1) Setting Boot
Partition Manager is partition management function Options (SYSPR 04-
enable was effective. 0040)
Changing to Dual dRestart the subsystem. Installation 1.7
Active Mode failed as Power On/Off
Cache Partition Procedure (INST 01-
Manager is enable 0290)

MSG 04-0410-01
Collect the error

Message
code
Trace Trace Dump
I70000 Path switch status An abnormal mode of the added Gather This recovery method is from
error (Unit-x, ENC-y) frame was detected. steps c to j.
x : Unit ID # cCheck the Unit ID # Addition/Subtraction/
(RKAJ=1-14) displayed by the message Relocation 1.3.1
y : ENC Unit # (0-1) after I8040x Unit ADD FAIL Work immediately
is displayed, and perform after abnormal
Addition/Subtraction/ termination (ADD 01-
Relocation 1.3.1 Work 0110)
termination (if not
go down).
dCheck if the device Installation 3.4.7
identification switch of the (1-3) Setting the
RKAJ pointed out in the subsystem
message is set correctly. identification switch
Check the above on all the (INST 03-0520)
RKAJs to be added.
eReset the subsystem
correctly.
fExecute the recognition of Addition/Subtraction/
the RKAJ again. Relocation 1.6.3
Recognition and
connection of the
added RKAJ (ADD
01-0590)
gWhen this message is Addition/Subtraction/
displayed again, check the Relocation 1.3.1
Unit ID # displayed by the Work immediately
message after I8040x Unit after abnormal
ADD FAIL is displayed, termination (ADD 01-
and perform Addition/ 0110)
Subtraction/Relocation
1.3.1 Work immediately
after abnormal termination
(if not performed, the
system may go down).
hReplace the ENC Unit Replacement 2.2.9
pointed out in the message. Replacing ENC
Unit/SENC Unit
(REP 02-0830)
iExecute the recognition of Addition/Subtraction/
Recognition and
connection of the
added RKAJ (ADD
01-0590)

MSG 04-0420-01
Collect the error

Message
code
Trace Trace Dump
jWhen the addition cannot Replacement 2.2.12
be made, replace the Replacing Additional
additional unit. Chassis of Rack
Mount Style (REP
02-0990)
I70100 Backend down [Path A mode setting error of the Gather cCheck if the device Installation 3.4.7
switch status error] frame was detected. identification switch of the (1-3) Setting the
(Unit-x, ENC-y) x : Unit ID # RKAJ pointed out in the subsystem
(RKAJ=1-14) message is set correctly. identification switch
y : ENC Unit # (0-1) Check the above on all the (INST 03-0520)
RKAJs.
dWhen the setting has been Installation 1.7
made wrongly, make the Power On/Off
setting correctly after Procedure (INST 01-
turning off all the AC Power 0290)
Unit Switches.
eReboot the subsystem.
fWhen the frame is not Replacement 2.2.9
started, replace the ENC Replacing ENC
Unit that is designated and Unit/SENC Unit
start it again. (REP 02-0830)
gIf the frame is not started in Replacement 2.2.12
spite of the operation Replacing Additional
above, replace the frame Chassis of Rack
and start the new frame. Mount Style (REP
02-0990)
I70200 Backend down Abnormality of the connected Gather cReplace the frame having Replacement 2.2.12
[Unit type error] frame was detected. the unit number concerned Replacing Additional
(Unit-x, ENC-y) x : Unit ID # with a connectable frame Chassis of Rack
(RKAJ=1-14) and restart the new frame. Mount Style (REP
y : ENC Unit # (0-1) 02-0990)
I70300 Unit type error An unsupported frame was Gather cCheck the Unit ID # Addition/Subtraction/
(Unit-x, ENC-y) detected during the frame displayed by the message Relocation 1.3.1
addition that was made while after I8040x Unit ADD Work immediately
the power was on. FAIL is displayed, and after abnormal
x : Unit ID # perform termination (ADD 01-
(RKAJ=1-14) Addition/Subtraction/ 0110)
y : ENC Unit # (0-1) Relocation 1.3.1 Work
termination (if not
go down).
dReplace the frame having
the unit number concerned
with a connectable frame.
ePerform the recognition Addition/Subtraction/
operation again. Relocation 1.6.3
Recognition and
connection of the
added RKAJ (ADD

MSG 04-0430-01
01-0590)

MSG 04-0430-01
Collect the error

Message
code
Trace Trace Dump
I70400 CTL recovery failed Though the Control Unit not Gather c Replace the Control Unit Replacement 2.2.5
[DESKEW is not blocked attempted to adjust the whose CALM LED is on. Replacing Control
completed] data input timing when it was Unit (REP 02-0390)
an inserted Control Unit, the
adjustment was not completed
within the time limit. [Failure in
the bus between the CTLs]
I70500 CTL recovery failed When the Control Unit not Gather
[SLV ERR] blocked was adjusting the data
input timing while it was
the inserted Control Unit, it
received an error report from the
inserted Control Unit. [Failure in
the bus between the CTLs]
I70600 CTL recovery failed After the inserted Control Unit Gather
[MRGN ERR] adjusted the data input timing
while it was sending/receiving
data to/from a Control Unit not
blocked, the Control Unit not
blocked detected a margin error.
[Failure in the bus between the
CTLs]
I70700 CTL recovery failed When the Control Unit not Gather
[SEQ ERR] blocked was adjusting the data
input timing while it was
the inserted Control Unit, it
detected a sequence error.
CTLs]
I70800 CTL recovery failed When the inserted Control Unit Gather
[DCNT ERR] was adjusting the data input
timing while it was
sending/receiving data to/from a
Control Unit not blocked, the
Control Unit not blocked
detected a failure in the delay
counter. [Failure in the bus
between the CTLs]

MSG 04-0440-01
Collect the error

Message
code
Trace Trace Dump
I70900 Unsupported unit is It tried to add RKAJ to the Gather c Check the Unit ID # Addition/Subtraction/
connected [RKA] subsystem, but the addition of displayed by the message Relocation 1.3.1
(Unit-x) RKAJ on-line failed because the after I8040x Unit ADD Work immediately
subsystem concerned did not FAIL is displayed, and after abnormal
support RKAJ. perform termination (ADD 01-
x : Unit ID # Addition/Subtraction/ 0110)
(RKAJ=1-14) Relocation 1.3.1 Work
I70A00 Unsupported unit is It tried to add RKAJAT to the Gather immediately after abnormal
connected [RKAAT] subsystem, but the addition of termination (if not
(Unit-x) RKAJAT on-line failed because performed, the system may
the subsystem concerned did go down).
not support RKAJAT. dReplace the chassis frame Replacement 2.2.12
x : Unit ID # to be added (RKAJ or Replacing Additional
(RKAATJ=1-14) RKAJAT). Chassis of Rack
Mount Style (REP
02-0990)
I8000x Unit ADD start A process of an RKAJ addition
(Loop-x) performed with the subsystem
power on was started.
x : Unit ID #
(RKAJ=1-14)
I8010x Unit ADD start An addition to a loop was started.
(Loop-x) x : Loop # (1-14)
I8020x Unit ADD complete An RKAJ addition performed
(Loop-x) with the subsystem power on
completed normally.
x : Unit ID #
(RKAJ=1-14)
I8030x Unit ADD complete An addition to a loop completed
(Loop-x) normally.
x : Loop # (0 or 1)
I8040x Unit ADD FAIL An RKAJ addition performed c Check the Unit ID # Addition/Subtraction/
(Loop-x) with the subsystem power on displayed by the message Relocation 1.3.1
terminated abnormally. after I8040x Unit ADD Work immediately
x : Unit ID # FAIL is displayed, and after abnormal
(RKAJ=1-14) perform termination (ADD 01-
I8050x Unit ADD FAIL An addition to a loop terminated Addition/Subtraction/ 0110)
(Loop-x) abnormally. Relocation 1.3.1 Work
x : Loop # (0 or 1) immediately after abnormal
termination (if not
go down).

MSG 04-0450-01
Collect the error

Message
code
Trace Trace Dump
I806xy Unit ADD ENC INIT An ENC failure was detected in cCheck the Unit ID # Addition/Subtraction/
FAIL an initialization of an added displayed by the message Relocation 1.3.1
(Unit-x, ENC-y) ENC Unit or when the CALM after I8040x Unit ADD Work immediately
LED was turned off. FAIL is displayed, and after abnormal
x : Unit ID # perform termination (ADD 01-
y : ENC Unit # (0-1) Relocation 1.3.1 Work
termination (if not
go down).
dReplace the ENC Unit Replacement 2.2.9
Replacing ENC
eWhen this message is still Unit/SENC Unit
displayed, replace the (REP 02-0830)
existing final unit.
I807xy Unit ADD ENC INIT An SES HDU failure was cCheck the Unit ID # Addition/Subtraction/
FAIL detected in an initialization of an displayed by the message Relocation 1.3.1
(Unit-x, HDU-y/z) added ENC Unit or when the after I8040x Unit ADD Work immediately
CALM LED was turned off. FAIL is displayed, and after abnormal
x: Unit ID # perform termination (ADD 01-
y, z : Disk Drive # Relocation 1.3.1 Work
(RKAJ=0-2, 1-3) immediately after abnormal
termination (if not
go down).
dReplace either one of the Replacement 2.2.1
Disk Drives displayed. Replacing Disk Drive
eWhen this message is still (REP 02-0050)
displayed, replace the
existing final ENC Unit.
I8080x Unit ADD start FAIL An RKAJ addition performed cCheck the Unit ID # Addition/Subtraction/
(Unit-x) with the subsystem power on displayed by the message Relocation 1.3.1
could not be done. after I8040x Unit ADD Work immediately
termination (if not
go down).
dA cause of the addition
failure is displayed in
another message.
Take a recovery action
following the message.

MSG 04-0460-01
Collect the error

Message
code
Trace Trace Dump
I80900 Unit ADD start FAIL An RKAJ addition performed with cCheck the Unit ID # Addition/Subtraction/
(Command) the subsystem power on could displayed by the message Relocation 1.3.1
not be done because the after I8040x Unit ADD Work immediately
Format/SyncCache command FAIL is displayed, and after abnormal
was being executed. perform termination (ADD 01-
termination (if not
go down).
dWait until execution of the
Format/SyncCache
command completes. Or,
abort the execution of the
Format/Sync Cache
command.
I80A0x Unit ADD start FAIL Though an RKAJ addition was cCheck the Unit ID # Addition/Subtraction/
[Loop] (Loop-x) attempted while the subsystem displayed by the message Relocation 1.3.1
power was on, it could not be after I8040x Unit ADD Work immediately
started because a loop failure FAIL is displayed, and after abnormal
had occurred. perform termination (ADD 01-
x : Loop # (0-1) Addition/Subtraction/ 0110)
termination (if not
go down).
dRetry the addition after
completing the recovery
from the loop failure.

MSG 04-0470-01
Collect the error

Message
code
Trace Trace Dump
I80Bxy Unit ADD FAIL no No SES drive was found. Gather cCheck the Unit ID # Addition/Subtraction/
SES x : Unit ID # displayed by the message Relocation 1.3.1
(Unit-x, HDU-y/z) (RKAJ=1-14) after I8040x Unit ADD Work immediately
y, z : Disk Drive # FAIL is displayed, and after abnormal
(RKAJ=0-2, 1-3) perform termination (ADD 01-
termination (if not
go down).
dCheck if the device Installation 3.4.7
identification switch of the (1-3) Setting the
RKAJ pointed out in the subsystem
message is set correctly. identification switch
Check the above on all the (INST 03-0520)
RKAJs to be added.
eReset the device
correctly.
fCheck the Unit ID # Addition/Subtraction/
displayed by the message Relocation 1.3.1
termination (if not
go down).
gExecute the recognition of Addition/Subtraction/
Recognition and
connection of the
added RKAJ (ADD
01-0590)
hPower off the added RKAJ Replacement 2.2.1
and replace the Disk Drive. Replacing Disk Drive
(REP 02-0050)
iIf the same message is Replacement 2.2.9
displayed in spite of the Replacing ENC
replacement, replace the Unit/SENC Unit
ENC Unit after powering off (REP 02-0830)
the added RKAJ.
jWhen this message is still
existing final unit.

MSG 04-0480-01
Collect the error

Message
code
Trace Trace Dump
I80C0x Unit ADD FAIL A loop was blocked during the Gather cCheck the Unit ID # Addition/Subtraction/
[Loop alarm](Loop-x) addition. displayed by the message Relocation 1.3.1
x : Loop # (0 or 1) after I8040x Unit ADD Work immediately
termination (if not
go down).
dReplace the ENC Unit. Replacement 2.2.9
Replacing ENC
eWhen this message is still Unit/SENC Unit
I80D0x Unit ADD FAIL A disconnection from a loop was Gather cCheck the Unit ID # Addition/Subtraction/
[cable off] (Loop-x) detected. displayed by the message Relocation 1.3.1
x : Loop # (0 or 1) after I8040x Unit ADD Work immediately
termination (if not
go down).
dReplace the ENC cable Replacement 2.2.10
Replacing ENC cable
(REP 02-0840)
eWhen this message is still Replacement 2.2.9
displayed, replace the Replacing ENC
existing final ENC Unit. Unit/SENC Unit
(REP 02-0830)
I80E00 Unit ADD warning Drives other than the SES drive
[HDU number over] are installed.
The adding process may not be
completed within the regular
time (five minutes).
Do not pull out the Disk Drive
while RKAJ is recognized. The
addition of RKAJ/RKAJAT may
terminate abnormally or the
subsystem may go down.

MSG 04-0490-01
Collect the error

Message
code
Trace Trace Dump
I80F00 Unit ADD FAIL The Format/SyncCache cCheck the Unit ID # Addition/Subtraction/
[Command] command was executed during displayed by the message Relocation 1.3.1
an addition of the RKAJ after I8040x Unit ADD Work immediately
performed with the subsystem FAIL is displayed, and after abnormal
power on. perform termination (ADD 01-
termination (if not
go down).
dWait until execution of the
Format/SyncCache
command completes. Or,
abort the execution of the
Format/Sync Cache
command.
I81700 Unit ADD ENC INIT During an addition of the RKAJ Gather c Check the Unit ID # Addition/Subtraction/
data error performed with the subsystem displayed by the message Relocation 1.3.1
[CUDGECTLR] power on, an SWCUDG (E-CTL after I8040x Unit ADD Work immediately
Register error) was detected FAIL is displayed, and after abnormal
when the ENC was initialized. perform termination (ADD 01-
I81800 Unit ADD ENC INIT During an addition of the RKAJ Gather Addition/Subtraction/ 0110)
data error performed with the subsystem Relocation 1.3.1 Work
[CUDGECTLF] power on, an SWCUDG (E-CTL immediately after abnormal
Force Test error) was detected termination (if not
when the ENC was initialized. performed, the system may
go down).
I81900 Unit ADD ENC INIT During an addition of the RKAJ Gather dPower off the added RKAJ Replacement 2.2.9
data error performed with the subsystem and replace the ENC Unit. Replacing ENC
[CUDGSRAM] power on, an SWCUDG (SRAM Unit/SENC Unit
Test error) was detected when (REP 02-0830)
the ENC was initialized.
I81A00 Unit ADD ENC INIT During an addition of the RKAJ Gather
data error performed with the subsystem
[CUDGENCCOM] power on, an SWCUDG (ENC
COM RS232C Test error) was
detected when the ENC was
initialized.
I81B00 Unit ADD ENC INIT During an addition of the RKAJ Gather
data error performed with the subsystem
[ENCCOMERR] power on, an ENCCOMERR
was detected when the ENC
was initialized.

MSG 04-0500-01
Collect the error

Message
code
Trace Trace Dump
I82000 Unit ADD Unit A number of the RKAJs to be cCheck the Unit ID # Addition/Subtraction/
number over connected are too large. displayed by the message Relocation 1.3.1
termination (if not
go down).
dConnection disabled.
Confirm how many RKAJs
are connected
I8210x Unit ADD Loop error A failure was detected in the Gather cCheck the Unit ID # Addition/Subtraction/
(Loop-x) added loop (loop-x). displayed by the message Relocation 1.3.1
x : Loop number (0-1) after I8040x Unit ADD Work immediately
termination (if not
go down).
dMake a retry after
recovering the subsystem
from the loop failure.
I8220x Unit ADD cable error A cable connection error was cCheck the Unit ID # Addition/Subtraction/
(Loop-x) detected in the loop-x during an displayed by the message Relocation 1.3.1
addition to the loop. after I8040x Unit ADD Work immediately
x : Loop # (0-1) FAIL is displayed, and after abnormal
termination (if not
go down).
dConfirm the order of cables
that are connected to the
device (check whether the
color of connectors and
cables matches together)

MSG 04-0510-01
Collect the error

Message
code
Trace Trace Dump
I8230x Unit ADD HDU No HDU exists in the added cCheck the Unit ID # Addition/Subtraction/
nothing loop-x. displayed by the message Relocation 1.3.1
(Unit-x) x : Unit ID # after I8040x Unit ADD Work immediately
(RKAJ=1-14) FAIL is displayed, and after abnormal
termination (if not
go down).
dENC cable of the last Installation 3.4.10
cabinet has been Connecting the ENC
misconnected. Check the cables (INST 03-
ENC cable connection. 0670)
eCheck if the device ID is
correct.
fReplace the Disk Drive. Replacement 2.2.1
(REP 02-0050)
gWhen this message is still Replacement 2.2.9
displayed, replace the ENC Replacing ENC
Unit. Unit/SENC Unit
hWhen this message is still (REP 02-0830)
I824xy Unit ADD ENC DIAG An ENC failure was detected in cCheck the Unit ID # Addition/Subtraction/
FAIL a diagnosis of the added ENC. displayed by the message Relocation 1.3.1
(Unit-x, ENC-y) x : Unit ID # after I8040x Unit ADD Work immediately
y : ENC Unit # (0-1) perform termination (ADD 01-
termination (if not
go down).
dWhen the failure occurs Addition/Subtraction/
during an addition of the Relocation 1.6.2
RKAJ performed while the Connecting multiple
subsystem power is turned RKAJs (ADD 01-
on, make sure of the 0550)
procedure referring to Addition/Subtraction/
Addition/Subtraction/ Relocation 1.7.2
Relocation 1.6.2 Connecting multiple
Connecting multiple RKAJs/RKAJATs
RKAJs. (ADD 01-0800)
eReplace the ENC Unit Replacement 2.2.9
Replacing ENC

MSG 04-0520-01
fWhen this message is still Unit/SENC Unit


MSG 04-0520-01
Collect the error

Message
code
Trace Trace Dump
I825xy Unit ADD ENC DIAG An Disk Drive failure was cCheck the Unit ID # Addition/Subtraction/
FAIL detected in a diagnosis of the displayed by the message Relocation 1.3.1
(Unit-x, HDU-y/z) added ENC. after I8040x Unit ADD Work immediately
y, z : Disk Drive # Addition/Subtraction/ 0110)
(RKAJ=0-2, 1-3) Relocation 1.3.1 Work
termination (if not
go down).
dReplace the Disk Drive. Replacement 2.2.1
(REP 02-0050)
eMake the addition of the Addition/Subtraction/
Adding the RKAJ to
the Rack Frame
(ADD 01-0490)
fWhen this message is Addition/Subtraction/
gReplace the ENC Unit. Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
hMake the addition of the Addition/Subtraction/
Adding the RKAJ to
the Rack Frame
(ADD 01-0490)
iWhen this message is Replacement 2.2.9
displayed and the addition Replacing ENC
of RKAJ is not completed, Unit/SENC Unit
replace the existing final (REP 02-0830)
ENC Unit.
jMake the addition of the Addition/Subtraction/
Adding the RKAJ to
the Rack Frame
(ADD 01-0490)

MSG 04-0530-01
Collect the error

Message
code
Trace Trace Dump
I82600Unit ADD ENC DIAG An H8SIOERR was detected in Gather c Check the Unit ID # Addition/Subtraction/
data error a diagnosis of the added ENC. displayed by the message Relocation 1.3.1
[H8SIOERR] after I8040x Unit ADD Work immediately
I82C00 Unit ADD DIAG data An RAMPERR was detected in Gather FAIL is displayed, and after abnormal
error a diagnosis of the added ENC. perform termination (ADD 01-
[RAMPERR] Addition/Subtraction/ 0110)
I82E00 Unit ADD DIAG data An CUDGECTLR was detected Gather Relocation 1.3.1 Work
error in a diagnosis of the added immediately after abnormal
[CUDGECTLR] ENC. termination (if not
I82F00 Unit ADD DIAG data An CUDGCTLF was detected in Gather performed, the system may
error a diagnosis of the added ENC. go down).
[CUDGECTLF] dReplace the ENC Unit. Replacement 2.2.9
I83000 Unit ADD DIAG data An CUDGSRAM was detected Gather Replacing ENC
error in a diagnosis of the added Unit/SENC Unit
[CUDGSRAM] ENC. (REP 02-0830)
e Make the addition of the Addition/Subtraction/
I83100 Unit ADD DIAG data An CUDGH8SIO was detected Gather RKAJ again. Relocation 1.6
error in a diagnosis of the added Adding the RKAJ to
[CUDGH8SIO] ENC. the Rack Frame
(ADD 01-0490)
I83200 Unit ADD ENC INIT The added ENC detected a
data error ready time-out of the ENC in
[CUDGRDYTOV] another system.
I83300 Unit ADD ENC INIT A REGPERR occurred in the
data error added ENC.
[REGPERR]
I83400 Unit ADD ENC INIT A RAMPERR occurred in the
data error added ENC.
[RAMPERR]
I83500 Unit ADD ENC INIT A WDTCNTPERR occurred in
data error the added ENC.
[WDTCNTPERR]
I83600 Unit ADD ENC DIAG An E-CTL register parity error
data error was detected in a diagnosis of
[REGPERR] the added ENC.
I83700 Unit ADD ENC DIAG An E-CTL register parity error
data error was detected in a diagnosis of
[WDTCNTPERR] the added ENC.

MSG 04-0540-01
Collect the error

Message
code
Trace Trace Dump
I83900 Unit ADD ENC DIAG The SWCUDGERR was Gather c Check the Unit ID # Addition/Subtraction/
data error detected in the ENC diagnosis displayed by the message Relocation 1.3.1
[SWCUDGERR] performed during the RKAJ after I8040x Unit ADD Work immediately
addition that was made while FAIL is displayed, and after abnormal
the power was on. perform termination (ADD 01-
I83A00 Unit ADD ENC DIAG The ENCCOMERR was Gather Addition/Subtraction/ 0110)
data error detected in the ENC diagnosis Relocation 1.3.1 Work
[ENCCOMERR] performed during the RKAJ immediately after abnormal
addition that was made while termination (if not
the power was on. performed, the system may
go down).
I83B00 Unit ADD ENC DIAG The TWSIERR was detected in Gather dReplace the ENC Unit. Replacement 2.2.9
data error [TWSIERR] the ENC diagnosis performed Replacing ENC
during the RKAJ addition that Unit/SENC Unit
was made while the power was (REP 02-0830)
on. e Make the addition of the Addition/Subtraction/
I83C00 Unit ADD ENC DIAG The PKERR was detected in the Gather RKAJ again. Relocation 1.6
data error [PKERR] ENC diagnosis performed Adding the RKAJ to
during the RKAJ addition that the Rack Frame
was made while the power was (ADD 01-0490)
on.
I83D00 Unit ADD ENC DIAG The PRESESWRERR was Gather
data error detected in the ENC diagnosis
[PRESESWRERR] performed during the RKAJ
addition that was made while
the power was on.
I83E00 Unit ADD ENC DIAG The SHERR was detected in the Gather
data error [SHERR] ENC diagnosis performed
during the RKAJ addition that
was made while the power was
on.
I83F00 ENC error inf. The ENCCUDG occurred in the Gather cReplace the detached ENC Replacement 2.2.9
[BKD SWCUDGERR] ENC Unit. Therefore, the ENC Unit. Replacing ENC
Unit concerned cannot be used Unit/SENC Unit
normally. (REP 02-0830)

MSG 04-0550-01
Collect the error

Message
code
Trace Trace Dump
I840xy Unit ADD no SES A drive non-installation error of cApply the following
HDU the added RKAJ. recovery procedure only
(Unit-x, HDU-y) x : Unit ID # when I80Bxy Unit ADD
(RKAJ=1-14) FAIL no SES is displayed
y : Disk Drive # (1-14) after this message.
I841xy Unit ADD SES spinup A spin up error of a drive in the Gather dCheck the Unit ID # Addition/Subtraction/
error added RKAJ. displayed by the message Relocation 1.3.1
(Unit-x, HDU-y) x : Unit ID # after I8040x Unit ADD Work immediately
y : Disk Drive # (1-14) perform termination (ADD 01-
termination (if not
go down).
eReplace the Disk Drive. Replacement 2.2.1
(REP 02-0050)
fMake the addition of the Addition/Subtraction/
Adding the RKAJ to
the Rack Frame
(ADD 01-0490)
gWhen this message is Addition/Subtraction/
hReplace the ENC Unit. Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
iMake the addition of the Addition/Subtraction/
Adding the RKAJ to
the Rack Frame
(ADD 01-0490)
I84200 ENC error inf. The ENCCOMERR occurred in Gather cReplace the detached ENC Replacement 2.2.9
[BKD ENCCOMERR] the ENC Unit. Therefore, the Unit. Replacing ENC
ENC Unit concerned cannot be Unit/SENC Unit
used normally. (REP 02-0830)

MSG 04-0560-01
Collect the error

Message
code
Trace Trace Dump
I84300 ENC error inf. The TWSIERR occurred in the Gather cReplace the detached ENC Replacement 2.2.9
[TWSIERR] ENC Unit. Therefore, the ENC Unit. Replacing ENC
Unit concerned cannot be used Unit/SENC Unit
normally. (REP 02-0830)
I84400 ENC error inf. The PKERR occurred in the Gather
[BKD PKERR] ENC Unit. Therefore, the ENC
Unit concerned cannot be used
normally.
I84500 ENC error inf. The PRESESWRERR occurred Gather
[BKD in the ENC Unit. Therefore, the
PRWSESWRERR] ENC Unit concerned cannot be
used normally.
I84600 ENC error inf. The SHERR occurred in the Gather
[BKD SHERR] ENC Unit. Therefore, the ENC
Unit concerned cannot be used
normally.
I84700 Unit ADD FAIL info. While the RKA/RKAJAT was cCheck the Unit ID # Addition/Subtraction/
[CTLALARM] being added in the state in displayed by the message Relocation 1.3.1
which the power was applied, after I8040x Unit ADD Work immediately
the Control Unit was detached. FAIL is displayed, and after abnormal
termination (if not
go down).
dWhen a message, I8000x Replacement 2.2.5
Unit ADD start is not Replacing Control
displayed, power off the Unit (REP 02-0390)
additional unit and replace
the blocked Control Unit.
eWhen a message, I8000x
Unit ADD start is
displayed, take recovery
actions according to
messages that follow it.

MSG 04-0570-01
Collect the error

Message
code
Trace Trace Dump
I84800 Unit ADD FAIL info. While the RKA/RKAJAT was cCheck the Unit ID # Addition/Subtraction/
[CTK1] being added in the state in displayed by the message Relocation 1.3.1
which the power was applied, an after I8040x Unit ADD Work immediately
internal retrying operation FAIL is displayed, and after abnormal
occurred in the Control Unit. perform termination (ADD 01-
termination (if not
go down).
dWhen a message, I8000x Replacement 2.2.5
Unit ADD start is not Replacing Control
displayed, power off the Unit (REP 02-0390)
additional unit and perform
the operation over again
from the check whether the
preconditions for the
addition are met.
eWhen a message, I8000x
Unit ADD start is
displayed, take recovery
actions according to
messages that follow it.
I900xx RSP abort command The response failure (Aborted Gather cRefer to Troubleshooting Troubleshooting 6.3
P (Key [OB], Code Command Path) exceeds the 6.3 Procedure for Procedure for
[xy]) threshold value in an execution Recovery from Path Recovery from Path
of a command issued from the Blockade when the Blockade when the
local DF to the remote DF. TrueCopy remote TrueCopy remote
x : Upper two figures of a replication Function Is replication Function Is
sense code Used. Used (TRBL 06-
y : Lower two figures of a 1170)
sense code
I90100 Command time out The time-out exceeds the Gather
threshold value in an execution
of a command issued from the
local DF to the remote DF.
I902xx RSP abort command The response failure (Aborted Gather
C (Key [OB], Code Command CTL) exceeds the
[xy]) threshold value in an execution
x : Upper two figures of a
sense code
y : Lower two figures of a
sense code

MSG 04-0580-01
Collect the error

Message
code
Trace Trace Dump
I903xx RSP etc. (Key [x]) The response failure (off-range Gather c Refer to Troubleshooting Troubleshooting 6.3
sense key) exceeds the 6.3 Procedure for Procedure for
threshold value in an execution Recovery from Path Recovery from Path
of a command issued from the Blockade when the Blockade when the
local DF to the remote DF. TrueCopy remote TrueCopy remote
x : Sense key replication Function Is replication Function Is
I904xx RSP hard error (Key The response failure (Hard Gather Used. Used (TRBL 06-
[04, Code [xy]) Error) exceeds the threshold 1170)
value in an execution of a
command issued from the local
DF to the remote DF.
sense code
sense code
I905xx RSP medium error The response failure (Medium Gather
(Key [03], Code [xy]) Error) exceeds the threshold
sense code
sense code
I906xx RSP illegal request The response failure (Illegal Gather
(Key [05], Code [xy]) Request) exceeds the threshold
sense code
sense code
I907xx RSP miscompare The response failure Gather
(Key [0E], Code [xy]) (Miscompare) exceeds the
threshold value in an execution
sense code
sense code

MSG 04-0590-01
Collect the error

Message
code
Trace Trace Dump
I908xx RSP not ready (Key The response failure (Not Gather cRefer to Troubleshooting Troubleshooting 6.3
[02], Code [xy]) Ready) exceeds the threshold 6.3 Procedure for Procedure for
value in an execution of a Recovery from Path Recovery from Path
command issued from the local Blockade when the Blockade when the
DF to the remote DF. TrueCopy remote TrueCopy remote
x : Upper two figures of a replication Function Is replication Function Is
sense code Used. Used (TRBL 06-
y : Lower two figures of a 1170)
sense code
I909xx RSP status error [x] The SCSI status error in a
response exceeds the threshold
x : SCSI status
I90A00 RSP other field error The field error in a response
exceeds the threshold value in
an execution of a command
issued from the local DF to the
remote DF.
IA0000 Coupling started An initial copy was started.
(LU-x/y) x : Copy source LU #
(RKM/RKS=0-2047)
y : Copy destination LU #
(RKM/RKS=0-2047)
IB0000 Coupling completed An initial copy completed
(LU- x/y) normally.
x : Copy source LU #
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
IC0000 Coupling failed An initial copy terminated cDefine the pair of the
(LU- x/y) abnormally. ShadowImage in-system
x : Copy source LU # replication again.
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
ID0000 Resync started A resynchronization was
(LU- x/y) started.
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
IE0000 Resync completed A resynchronization completed
(LU- x/y) normally.
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)

MSG 04-0600-01
Collect the error

Message
code
Trace Trace Dump
IF0000 Resync failed A resynchronization terminated cDefine the pair of the
(LU- x/y) abnormally. ShadowImage in-system
x : Copy source LU # replication again.
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
IG0000 PSUE occurred The pair status was changed to Gather cMake a recovery from the Troubleshooting
(LU- x/y) PSUE when the Shadow Image failure already occurred. Chapter 9. Data
function was being used. Refer to Troubleshooting Collection when a
x : Primary LU # Chapter 9 Data Collection Failure Occurs in
(RKM/RKS=0-2047) when a Failure Occurs in Program Product
y : Secondary LU # Program Product (P.P.) to (P.P.) (TRBL 09-
(RKM/RKS=0-2047) collect necessary 0000)
information.
IH0000 LU unified LUs were unified.
(UNI : LU-x,M : LU-x, x : LU # of the unified LU after
S : LU-y) the unification and a Main
LU
(RKM/RKS=0-2047)
y : LU # of a Sub LU before
the unification
(RKM/RKS=0-2047)
IQ0000 Remote copy started The TrueCopy remote replication
(LU- x/y) initial copy was started.
x : Number of an internal LU
of the local DF
(RKM/RKS=0-2047)
y : Number of an internal LU
of the remote DF
(RKM/RKS=0-2047)
IR0000 Remote copy The initial copy by the TrueCopy
completed remote replication was
(LU- x/y) completed normally.
of the local DF
(RKM/RKS=0-2047)
of the remote DF
(RKM/RKS=0-2047)
IS0000 Remote copy failed The initial copy by the TrueCopy Gather cDefine the pair of the
(LU- x/y) remote replication terminated TrueCopy remote
abnormally. replication again.
of the local DF
(RKM/RKS=0-2047)
of the remote DF
(RKM/RKS=0-2047)

MSG 04-0610-01
Collect the error

Message
code
Trace Trace Dump
IT0000 Remote resync The re-synchronization by the S
started TrueCopy remote replication RC
(LU- x/y) was started.
of the local DF
(RKM/RKS=0-2047)
of the remote DF
(RKM/RKS=0-2047)
IU0000 Remote resync The re-synchronization by the
completed TrueCopy remote replication
(LU- x/y) was completed normally.
of the local DF
(RKM/RKS=0-2047)
of the remote DF
(RKM/RKS=0-2047)
IV0000 Remote resync failed The re-synchronization by the Gather cPerform the re-
(LU- x/y) TrueCopy remote replication synchronization using the
terminated abnormally. TrueCopy remote
x : Number of an internal LU replication again.
of the local DF
(RKM/RKS=0-2047)
of the remote DF
(RKM/RKS=0-2047)
IW0000 Remote PSUE In the local DF (own DF) Gather cRefer to Troubleshooting Troubleshooting 6.3
occurred controlled by the TrueCopy 6.3 Procedure for Procedure for
(LU-xP/yS) remote replication, the pair Recovery from Path Recovery from Path
status of the primary LU was Blockade when the Blockade when the
changed to PSUE. TrueCopy remote TrueCopy remote
x : Number of an internal LU replication Function Is replication Function Is
of the local DF Used. Used (TRBL 06-
(RKM/RKS=0-2047) 1170)
of the remote DF
(RKM/RKS=0-2047)
IX0000 SRC PSUE occurred In the local DF (own DF) Gather
(LU-xS/yP) controlled by the SRC, the pair
status of the secondary LU was
changed to PSUE.
of the local DF
(RKM/RKS=0-2047)
of the remote DF
(RKM/RKS=0-2047)

MSG 04-0620-01
Collect the error

Message
code
Trace Trace Dump
IXX000 SELF HEATRUN: The self heatrun was started.
Began self heatrun
IXX100 SELF HEATRUN: The defined LUN (self heatrun
The number of execution target LU) was
defined LU is x displayed.
x : LU #
(RKM/RKS=0-2047)
IXX200 SELF HEATRUN: The execution of the self
Finished self heatrun heatrun was completed.
IXX300 SELF HEATRUN: The loop test was started.
Began loop test [loop x : Loop # (0-1)
(x)]
IXX400 SELF HEATRUN: The loop test was completed.
Finished loop test x : Loop # (0-1)
[loop (x)]
IXX500 SELF HEATRUN: The execution of the test pattern
Began the test pattern for Fibre Channel was started.
FC-[x] x : Test pattern number
Began the test pattern for SATA was started.
SATA-[x] x : Test pattern number
Began the test pattern of the input file was started.
[x] x : Test pattern number
Finished the test was completed.
pattern [x] x : Test pattern number
IXX900 SELF HEATRUN: The time required for the test
execution time [x:y:z] was displayed.
x : Execution time (hh)
y : Execution time (mm)
z : Execution time (ss)
IXXA00 SELF HEATRUN: The drive failure occurred. Gather cAnalyze the failure of the
HDU alarm (Unit-x, x : Unit ID # Disk Drive displayed in this
HDU-y) (RKM/RKS=0) message.
(RKAJ/RKAJAT=1-14)
IXXB00 SELF HEATRUN: The online verify was stopped.
Online verify stopped
IXXC00 SELF HEATRUN: The online verify was started.
Online verify started
IXXD00 SELF HEATRUN: The statistical information
started the collection collection was started.
of statistical
information (Time
takes 85~300sec.)

MSG 04-0630-01
Collect the error

Message
code
Trace Trace Dump
IXXE00 SELF HEATRUN: The statistical information
finished the collection collection was completed.
of statistical
information
IXXF00 LBA = x LBA was detected when the
drive failure occurred.
IXXG00 Key/Code = x/y The sense key/sense code was
detected when the drive failure
occurred.
x : sense key
y : sense code
IXXH00 Cmd/Len(blk) =x/y The operation code and the
number of transfer blocks were
detected when the drive failure
occurred.
x : Operation code
y : Number of transfer blocks
IY00xy HDU error report Drive detachment because of a
(Unit-x, HDU-y) [z-z] failure (bad ALPA) drive error
report receipt
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
z-z : Detail code
IY01xy DFPC error detect Drive detachment because of a
(Unit-x, HDU-y) failure (bad ALPA) detected by
[Bad ALPA] the DFPC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
(Unit-xx, HDU-y) failure (drive non-installation)
[NO HDU] detected by the DFPC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0640-01
Collect the error

Message
code
Trace Trace Dump
IY03xy DFPC error detect Drive detachment because of a cThe message concerned is
(Unit-x, HDU-y) failure (WWN inconsistency) output when the Disk Drive
[WWN NG] detected by the DFPC. is replaced while the
x : Unit ID # subsystem power is turned
(RKM/RKS=0) off. Pull out and then insert
(RKAJ/RKAJAT=1-14) the Disk Drive concerned to
y : Disk Drive # (0-14) check it out.
dIf the Disk Drive is not Replacement 2.2.1
recovered in spite of the Replacing Disk Drive
above operation, replace (REP 02-0050)
the Disk Drive because it is
considered to be out of
order.
eCheck if the subsystem is Installation 1.6
connected in the correct Device ID Setting and
device connection order. ENC Cable
fCheck if the device ID of Connection (INST
the subsystem is set 01-0160)
correctly.
gENC cable may have been
misconnected. Check the
(Unit-x, HDU-y) failure (Drive busy status)
[HDU BUSY] detected by the DFPC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
(Unit-x, HDU-y) failure (Drive queue full status)
[QUEUE FULL] detected by the DFPC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
(Unit-x, HDU-y) failure (PDEV time-out) detected
[HDU TIME OUT] by the DFPC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0650-01
Collect the error

Message
code
Trace Trace Dump
(Unit-x, HDU-y) failure (Exceeded drive log-out
[LOGOUT] threshold value) detected by the
DFPC.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY08xy HDU online verify Drive detachment owing to
error detection of sector exhaustion in
(Unit-x, HDU-y) the online verification.
[04-3200] x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY09xy HDU removed Drive detachment because of
(Unit-x, HDU-y) pulling out of the drive.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Axy HDU detach Drive detachment instructed by
command receive the Mode Select command.
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Bxy Dynamic sparing Drive detachment owing to a
command receive dynamic sparing instructed by
(Unit-x, HDU-y) the Mode Select command.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
y : Disk Drive #
(RKM/RKS=0-14)
(RKAJ/RKAJAT=0-14)
IY0Cxy Staging error Drive detachment because of a
(Unit-x, HDU-y) staging failure.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Dxy HDU intermittent error Drive detachment because of
over the exceeded threshold value of
(Unit-x, HDU-y) the HDU intermittent failure
count.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0660-01
Collect the error

Message
code
Trace Trace Dump
IY0Exy Dynamic sparing Drive detachment because of
error the exceeded threshold value of
(Unit-x, HDU-y) media error count occurs in the
[MEDIUM] dynamic sparing.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Fxy LA error Drive detachment because of an
[errcode:LUN] LA error. (LUN)
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
(RKAJAT=1-3)
IY0Gxy LA error Drive detachment because of an
[errcode:LBA] LA error. (LBA)
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Hxy LRC error Drive detachment because of an
(Unit-x, HDU-y) LA error.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Ixy Backend diagnostic Drive detachment because of a
error (Unit-x, HDU-y) backend diagnostic error.
[HDU ERROR] x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Jxy Backend diagnostic Drive detachment because of a
error (Unit-x, HDU-y) dual port failure of a drive
[DUAL PORT] x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Kxy HDU inquiry failed Drive detachment because of a
(Unit-x, HDU-y) failure of the Inquiry command
at the time of the drive start-up
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0670-01
Collect the error

Message
code
Trace Trace Dump
IY0Lxy HDU read capacity Drive detachment because of a
failed failure of the ReadCapacity
(Unit-x, HDU-y) command at the time of the
drive start-up
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0Mxy Forced party The drive was detached owing c Replace the Disk Drive. Replacement 2.2.1
correction PIN-over to a PIN-over during a forced When you want to make Replacing Disk Drive
(Unit-x, HDU-y) parity correction. sure of a model name and (REP 02-0050)
x : Unit ID # drive firmware revision of Replacement 1.1.3
(RKM/RKS=0) the Disk Drive, refer to Procedure for making
IY0Nxy HDU intermittent error The drive was detached of model name and drive Disk Drive (REP 01-
over due to rash of because of a PDEV time-out firmware of Disk Drive. 0100)
media errors caused by frequent occurrences
(Unit-x, HDU-y) of media error.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IY0P00 HDU error outside of Detachment of the drive under cReplace the Disk Drive. Replacement 2.2.1
regulation [SMR] the SMART control because of Replacing Disk Drive
(Unit-x, HDU-y) its nonstandard head (REP 02-0050)
x : Unit ID #
(RKAJAT=1-29)
IY0Q00 HDU error time-out Detachment of a drive under the
[SMR] SMART control because of a
(Unit-x, HDU-y) time-out of a response to a
command.
x : Unit ID #
(RKAJAT=1-29)
IY0R00 HDU error status Detachment of a drive under the
[SMR] SMART control because of an
(Unit-x, HDU-y) abnormal state of the heads.
x : Unit ID #
(RKAJAT=1-29)
IY0S00 HDU SES detection The drive was detached
error because the ENC Unit detected
(Unit-x, HDU-y) a trouble of a drive.
x : Unit ID #
(RKAJAT=1-29)

MSG 04-0680-01
Collect the error

Message
code
Trace Trace Dump
IY0T00 Write and compare The drive was detached Gather cReplace the Disk Drive. Replacement 2.2.1
error occurred because a comparison error Replacing Disk Drive
(Unit-x, HDU-y) occurred during the write and (REP 02-0050)
compare operation of the writing
assurance function.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-29)
IY0U00 SMART sequence Detachment of a drive under the
error over SMART control.
[SMR] x : Unit ID #
(Unit-x, HDU-y) (RKAJAT=1-29)
IY0V00 P-VOL HDU error A double failure of drives (a cRefer to Troubleshooting Troubleshooting
[ShadowImage] failure of a single drive in the 6.1.9 Data recovery does 6.1.9 Data recovery
case of RAID 0) occurred in a not terminate normally : does not terminate
ShadowImage in-system Case 2 (Disk Drive failure) normally : Case 2
replication P-VOL. and 6.1.10 Data recovery (Disk Drive failure)
does not terminate (TRBL 06-0520)
normally: Case 3 (Spare Troubleshooting
Disk Drive failure). 6.1.10 Data
recovery does not
terminate normally :
Case 3 (Spare Disk
Drive failure) (TRBL
06-0540)
IY0W00 HDU intermittent error Drive blockade 3 due to the cWhen the message
over 3 exceeded threshold value of the I301AT SATA HDU error
(Unit-x, HDU-y) HDU intermittent failure. or I301xy HDU error is
(RKAJ=1-29) follow the recovery method.
(RKAJAT=1-29) dWhen the message, Replacement 2.2.1
y: Disk Drive # (0-14) I301xy HDU error is not Replacing Disk Drive
displayed, replace a Disk (REP 02-0050)
Drive that is pointed out in
this message.
When you want to make Replacement 1.1.3
sure of a model name and Procedure for making
drive firmware revision of sure of model name
the Disk Drive, refer to and drive firmware of
Replacement 1.1.3 Disk Drive (REP 01-
Procedure for making sure 0100)
of model name and drive
firmware of Disk Drive.

MSG 04-0690-01
Collect the error

Message
code
Trace Trace Dump
IY0X00 Data recovery Because drive detachment of a
restarted over by RAID group of RAID 6 occurred
HDU alarm during the correction operation of
(Unit-x, HDU-y) it, the correction operation was
restarted from the beginning.
x : Unit ID #
(RKAJ=1-29)
(RKAJAT=1-29)
y: Disk Drive # (0-14)
IY0Y00 WR SEQ error Drive detachment owing to an
(Unit-x, HDU-y) error (Error code: WR_SEQ).
x : Unit ID #
(RKAJ=1-29)
(RKAJAT=1-29)
y: Disk Drive # (0-14)
IY0Z00 Unsupported HDU The inserted Disk Drive was cTake a recovery action Chapter 6. Warning
inserted blocked because it was outside according to the message, Messages (MSG 06-
(Unit-x, HDU-y) the support. W060AT SATA Spare 0020)
x : Unit ID # HDU alarm or W061AT
(RKAJ=1-29) SATA Spare HDU alarm
(RKAJAT=1-29) (Unit-x, HDU-y) displayed
y: Disk Drive # following this message.
(RKAJ=0-14) When doing that, replace Replacement 2.2.1
(RKAJAT=0-14) the Disk Drive with the one Replacing Disk Drive
that is supported. (REP 02-0050)
IY2000 Restore started The restoration copy started.
(LU-x/y) x : Copy source LU #
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
IY2100 Restore completed The restoration copy terminated
(LU-x/y) normally.
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
IY2200 Restore failed The restoration copy terminated Gather cRestore the data using the
(LU-x/y) abnormally. backup data after splitting
x : Copy source LU # the pair.
(RKM/RKS=0-2047)
(RKM/RKS=0-2047)
IY3000 Subsystem is going to The SES access could not be
re-boot to recognize made to the ENC of the
additional Units subsystem pointed out in the
message issued at the time
when the subsystem was
started. Both of the Control
Units are to be rebooted now in
order to retry the SES access.

MSG 04-0700-01
Collect the error

Message
code
Trace Trace Dump
IZ0000 HDU firmware An updating of the drive
download start firmware was started.
IZ0100 HDU firmware An updating of the drive cTurn off the subsystem
download end firmware was completed. power, and turn it on again.
IZ02xy HFWD completed An updating of the drive
(Unit-x, HDU-y) firmware was completed
normally.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
IZ03xy HDU update failed The drive firmware updating or Gather cTurn off the main switch
(Unit-x, HDU-y) the physical format utility after a rewriting of the drive
processing failed. firmware or a process of
x : Unit ID # the physical format utility is
(RKM/RKS=0) completed (after a
(RKAJ/RKAJAT=1-14) message, IZ0100 HDU
y : Disk Drive # (0-14) firmware download end is
displayed and the READY
LED (green) on the front
side of the subsystem
blinks slowly (once/second)).
dTurn off all the AC Power Installation 1.7
Unit Switches of the Power On/Off
subsystems that are Procedure (INST 01-
installed. 0290)
ePower on the subsystem.
(Make sure that the READY
LED (green) comes on four
minutes later normally.)
fWhen the Alarm LED (red)
or Warning LED (orange)
on the front side of the
subsystem is on, maintain it
according to the
Information message.
gReplace a Disk Drive Replacement 2.2.1
pointed out in the message. Replacing Disk Drive
(REP 02-0050)
hExecute the drive firmware Drive Firmware
update of the physical Replacement Users
format utility again (refer to Guide
Drive Firmware
Replacement Users Guide
when replacing the drive
firmware).

MSG 04-0710-01
Collect the error

Message
code
Trace Trace Dump
IZ0600 HFWD no target HDU When an attempt is made to cCheck whether the
update the drive firmware, the specified drive firmware is
target drive does not exist. correct or not. If it is
However, there is no problem if wrong, replace the drive
this message appears when the firmware again by
target Disk Drive already has specifying the correct one.
the latest version of firmware.
IZ07xy HFWD no Though the drive was the one
redundancy [PG] whose firmware was to be
(Unit-x, HDU-y) updated, the updating was
aborted because it was
impossible to preserve
redundancy of a parity group.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
redundancy [SYS] whose firmware was to be
redundancy of the system drive.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
redundance [SES] whose firmware was to be
redundancy of the SES drive.
x : Unit ID #
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)

MSG 04-0720-01
Collect the error

Message
code
Trace Trace Dump
IZ0Axy HDU update failed by The drive firmware updating or Gather cMake sure that W0100x
CTL alarm the physical format utility CTL alarm is displayed in
(Unit-x, HDU-y) processing failed due to the the Information message or
Control Unit blockade. the CLAL LED on the
x : Unit ID # Control Unit is lit.
(RKM/RKS=0) dSearch a cause of the
(RKAJ/RKAJAT=1-14) failure by referring to
y : Disk Drive # (0-14) (recording) a statement
displayed in the Information
message.
eTurn off the main switch
after a rewriting of the drive
firmware or a process of
the physical format utility is
completed (IZ0100 HDU
firmware download end is
fTurn off all the AC Power Installation 1.7
installed. 0290)
gTake recovery actions
according to the procedure
that was got in Step d.
hPower on the subsystem. Installation 1.7
(Make sure that the READY Power On/Off
LED (green) comes on four Procedure (INST 01-
minutes later normally.) 0290)
iWhen the Alarm LED (red)
according to the
jExecute the drive firmware Drive Firmware
Drive Firmware
Replacement Users
Guide when replacing the
drive firmware).

MSG 04-0730-01
Collect the error

Message
code
Trace Trace Dump
IZ0B00 CACHE destage Execution is impossible because Gather cPerform the regular
check error unsaved information remains on sequential shutdown.
the cache. dPower on the subsystem. Installation 1.7
(Make sure that the READY Power On/Off
LED (green) comes on four Procedure (INST 01-
minutes later normally.) 0290)
eWhen the Alarm LED (red)
subsystems is on, maintain
it according to the
fExecute the drive firmware Drive Firmware
Drive Firmware
Replacement Users
drive firmware).

MSG 04-0740-01
Collect the error

Message
code
Trace Trace Dump
IZ0Cxy HDU update failed by The drive firmware updating or Gather cMake sure that the Fibre
Loop alarm the physical format utility Channel loop is detached
(Unit-x, HDU-y) processing failed due to the through a message,
Loop failure. W080xy Loop alarm in the
x : Unit ID # Information message.
(RKM/RKS=0) dSearch a cause of the
(RKAJ/RKAJAT=1-14) detachment by referring to
y : Disk Drive # (0-14) (recording) a statement on
the Fibre Channel loop
detachment in the
eTurn off the main switch
after a rewriting of the drive
firmware or a process of
the physical format utility is
completed (IZ0100 HDU
firmware download end is
fTurn off all the AC Power Installation 1.7
installed. 0290)
gPower on the subsystem.
(Make sure that the READY
LED (green) comes on four
minutes later normally.)
hWhen the Alarm LED (red)
according to the
iWhen the recovery method
given in Step c (W080xy
Loop alarm) was not
executed in Steph,
maintain it following the
recovery method that was
got in Step d.
jExecute the drive firmware Drive Firmware
Drive Firmware
Replacement Users
drive firmware).

MSG 04-0750-01
Collect the error

Message
code
Trace Trace Dump
IZY000 ENC microprogram An ENC microprogram
download start downloading was started.
download complete downloading was completed.
IZY20x ENC#x microprogram An ENC microprogram
download start downloading was started.
download FAIL downloading failed.
(CTL-Unit)
IZY30x ENC microprogram An ENC microprogram
download FAIL downloading failed.
(Unit-x) x : Unit ID #
(RKM/RKS=0-13)
(RKAJ/RKAJAT=1-14)
IZY40x ENC#x microprogram An ENC microprogram
download complete downloading was completed.
IZY5AT ENC microprogram A SENC microprogram cReplace the SENC Unit. Replacement 2.2.9
download Info.[SENC] downloading failed. Replacing ENC
(Unit-x, ENC-y) x : Unit ID # Unit/SENC Unit
(RKAJAT=1-29) (REP 02-0830)
IZY5xy ENC microprogram A failure was detected in the cReplace the ENC Unit.
download info. ENC during an ENC
(Unit-x, ENC-y) downloading.
x : Unit ID #
(RKAJ=1-14)
IZY6AT ENC microprogram A job timeout was detected cPerform replacement of Replacement 2.2.5
download during an SENC downloading. components in the following Replacing Control
Info.[SENC] x : Unit ID # order to specify the failed Unit (REP 02-0390)
(SES Unit-x) (RKAJAT=1-29) component. Replacement 2.2.9
yControl Unit replacement Replacing ENC
ySENC Unit replacement Unit/SENC Unit
(REP 02-0830)
IZY6xy ENC microprogram A job timeout was detected cPerform replacement of Replacement 2.2.1
download info. during an ENC downloading. components in the following Replacing Disk Drive
(SES Unit-x, HDU-y) x : SES Unit ID # order to specify the failed (REP 02-0050)
(RKAJ=1-14) component. Replacement 2.2.5
y : Disk Drive # (0-14) yDisk Drive replacement Replacing Control
yControl Unit replacement Unit (REP 02-0390)
yENC Unit replacement Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)

MSG 04-0760-01
Collect the error

Message
code
Trace Trace Dump
IZY7AT ENC microprogram A drive error (other than cPerform replacement of Replacement 2.2.1
download xx/35xx) was detected during an components in the following Replacing Disk Drive
Info.[SENC] SENC downloading. order to specify the failed (REP 02-0050)
(SES Unit-x, HDU-y) x : Unit ID # component. Replacement 2.2.5
(RKAJAT=1-29) yDisk Drive replacement Replacing Control
y : Disk Drive # (0-14) yControl Unit replacement Unit (REP 02-0390)
ySENC Unit replacement Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
IZY7xy ENC microprogram A drive error (other than cPerform replacement of Replacement 2.2.1
download info. xx/35xx) was detected during an components in the following Replacing Disk Drive
(SES Unit-x, HDU-y) ENC downloading. order to specify the failed (REP 02-0050)
x : SES Unit ID # component. Replacement 2.2.5
(RKAJ=1-14) yDisk Drive replacement Replacing Control
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
IZY8AT ENC microprogram A drive error (incorrect post) cPerform replacement of Replacement 2.2.1
download was detected during an SENC components in the following Replacing Disk Drive
Info.[SENC] downloading. order to specify the failed (REP 02-0050)
(SES Unit-x, HDU-y) x : SES Unit ID # component. Replacement 2.2.5
(RKAJAT=1-29) yDisk Drive replacement Replacing Control
ySENC Unit replacement Replacement 2.2.9
Replacing ENC
Unit/SENC Unit
(REP 02-0830)
IZY8xy ENC microprogram A drive error (incorrect post) cPerform replacement of Replacement 2.2.1
download info. was detected during an ENC components in the following Replacing Disk Drive
(SES Unit-x, HDU-y) downloading. order to specify the failed (REP 02-0050)
x : SES Unit ID # component. Replacement 2.2.5
(RKAJ=1-14) yDisk Drive replacement Replacing Control
Replacing ENC
Unit/SENC Unit
(REP 02-0830)

MSG 04-0770-01
Collect the error

Message
code
Trace Trace Dump
IZY9AT ENC microprogram A sum check error occurred in cReplace the data file and Replacement 2.2.9
download execution of the Status Read the SENC Unit in this order Replacing ENC
Info.[SENC] command during an SENC to specify the failed part. Unit/SENC Unit
(ENC microprogram downloading. (REP 02-0830)
Unit-x, ENC-y) x : Unit ID #
(RKAJAT=1-29)
IZY9xy ENC microprogram A sum check error occurred in cReplace the data file and
download info. execution of the Status Read the ENC Unit in this order
(ENC microprogram command during an ENC to specify the failed part.
Unit-x, ENC-y) downloading.
x : Unit ID #
(RKAJ=1-14)
IZYA00 ENC microprogram Unsaved information remained cRetry after shutdown.
download CACHE in the cache.
destage check error
IZYB00 ENC microprogram A display file open error cReplace the ENC microfile
file open error occurred to the Ramsdisk. in the service PC.
[xxxxxxxxxxxx] xxxxxxxxxxxx :
Error replacement file name
IZYB01 ENC microprogram A display file read error occurred
file read error to the Ramsdisk.
IZYB02 ENC microprogram The display file size exceeds the
file size over specified value.
IZYB03 ENC microprogram The display file size and the
file size mismatch designated value are
[xxxxxxxxxxxx] mismatched.
xxxxxxxxxxxx :
IZYB04 ENC microprogram A contents error in the file
read data error occurred.
IZYE00 ENC microprogram CTL-Unit ENC microgram Gather cRetry the download after
download info. download time out occurred. powering off and on.
[Data transfer time- x : Internal classification of the dIf the same message Replacement 2.2.5
out x] ENC microprogram (0-7) appears again, replace the Replacing Control
(CTL-y) y : Control Unit # (0-1) Control Unit remaining. Unit (REP 02-0390)

MSG 04-0780-01
Collect the error

Message
code
Trace Trace Dump
IZYF00 ENC microprogram When a download of the Gather cRetry the download after
download info. microprogram was attempted, the powering off and on.
[Write data found x] download could not be done dIf the same message Replacement 2.2.5
(CTL-y) because unprocessed data appears again, replace the Replacing Control
existed in the write area. Control Unit remaining. Unit (REP 02-0390)
x : Internal classification of the
ENC microprogram (0-7)
IZYG00 ENC microprogram When a down load of the Gather
download info. microprogram was attempted,
[Start bit clear NG x] the download could not be done
(CTL-y) because the start bit could not
be cleared.
IZYH00 ENC microprogram When a download of the Gather
[Status error x] the download could not be done
(CTL-y) because of a status error.
IZYI00 ENC microprogram When a download of the Gather
[Data write error x] the download could not be done
(CTL-y) because of a write error.
IZYJ00 ENC microprogram The file to be downloaded is Gather cCheck the file to be
download info. illegal. downloaded.
[Download file error x] x : Internal classification of the
IZYK00 Read command 50 or more read commands,
response time over which were instructed by a host
and took longer than 100 ms for
the drive to respond, were
detected.
IZYL00 Write command 50 or more write commands,
response time over which were instructed by a host
and took longer than 100 ms for
the drive to respond, were
detected.
IZYM00 ENC microprogram An ENC microprogram
download error downloading failed.
detected (CTL-Unit)

MSG 04-0790-01
Collect the error

Message
code
Trace Trace Dump
IZYM0x ENC microprogram An ENC microprogram
download error downloading failed.
detected (Unit-x) x : Unit ID #
(RKAJ=1-14)
(RKAJAT=1-14)
IZYN00 ENC microprogram When a download of the Gather cDownload the ENC
download info. microprogram was attempted, microprogram again.
[other SES error] the SES of the ENC in another
(Unit-x, ENC-y) system was in the unusable
status.
x : Unit ID #
(RKAJ=0-29)
(RKAJAT=1-29)
y : ENC Unit #/SENC Unit #
(0-1)
IZYP00 An error detected in Because the SES of the other cSince one of the IZYMOO
the other SES HDUs one of the ENC became ENC microprogram
(Unit-x) unusable during the ENC download error detected,
microprogram downloading, the and IZYMOx ENC
downloading terminated microprogram download
abnormally error detected is displayed
x : Unit ID # following this message,
(RKAJ=0-29) take recovery actions
(RKAJAT=1-29) following the message.
IZYQ00 Automatic ENC The automatic ENC Gather cMake sure that the IZY20x
microprogram microprogram downloading ENC#x microprogram
download failed terminated abnormally. download start and
IZY30x ENC
microprogram download
FAIL were displayed
before this message.
dTake recovery actions
following messages
displayed between the
IZY20x ENC#x
start and IZY30x ENC
FAIL.
IZYR00 Automatic ENC The automatic ENC
microprogram microprogram downloading was
download completed completed normally.
successfully

MSG 04-0800-01
Collect the error

Message
code
Trace Trace Dump
IZYS00 Automatic ENC The automatic ENC cInterrupt the recovery
microprogram microprogram downloading was action temporarily.
download start started. dMake sure that Ixxxxx
define name
C_LCD_IAUTOENCDLCO
MP or Ixxxxx define name
C_LCD_I_AUTOENCDLFA
IL is displayed following
this message, and then
resume the recovery action
that was interrupted.
IZZ000 HFWD file open error A file open error was detected. c Copy the drive firmware file
[xxxxxxxxxxxx] xxxxxxxxxxxx: A name of the file from the supplied medium
concerning the error to the PC and replace the
IZZ001 HFWD file read error A file read error was detected. drive firmware again.
[x] x : A name of the file d If not recovered yet, call the
concerning the error Technical Support Center
IZZ002 HFWD file size over A file size over occurred. for coping with troubles.
[x] xxxxxxxxxxxx: A name of the
file concerning the error
IZZ003 HFWD read data over Data read from the file was
[x] illegal.
x : A name of the file
concerning the error
IZZ004 HFWD file size A file size is different from the
mismatch [x] estimated one.
x : A name of the file
concerning the error

MSG 04-0810-01
Chapter 5. Flash Detected Messages

Collect the error
Message
code
Trace Trace Dump
R00200 MCTL data parity A parity error was detected in Gather cReplace the Control Unit Replacement 2.2.5
error [DP3] data bits 31 to 24 during a whose CALM LED is on. Replacing Control
[REG80000014, Bit15] readout from the M-CTL internal Unit (REP 02-0390)
register.
R00300 MCTL data parity A parity error was detected in Gather
error [DP2] data bits 23 to 16 during a
[REG80000014, Bit14] readout from the M-CTL internal
register.
register.
register.
R00600 MCTL REG access A writing was attempted on the Gather
error [RDRGWR] read-only register of the M-CTL
[REG80000014, Bit11] internal register.
R00700 CTC parity error A parity error occurred in the Gather
(CH-0) timer CH0.
[REG80000014, Bit5]
R00800 CTC parity error A parity error occurred in the Gather
(CH-1) timer CH1.
[REG80000014, Bit4]
R00900 Watchdog-timer A parity error occurred in the Gather
counter parity error counter for the watchdog timer.
[REG80000014, Bit0]
R100yy FPC is not detected The detection of the FPC failed. Gather cWhen W0100x CTL alarm Chapter 6. Warning
(CTL-x) x : Control Unit# (0-1) is displayed following this Messages (MSG 06-
y : Chip error code message, take recovery 0000)
(y:z) = actions according to the
(01 : Path-0) message.
(02 : Path-1) dReplace the Control Unit of Replacement 2.2.5
(03 : Path-0/1) which the CALM LED lights Replacing Control
(04 : Path-2) on except for c. Unit (REP 02-0390)
(05 : Path-0/2)
(06 : Path-1/2)
(07 : Path-0/1/2)
(08 : Path-3)
(09 : Path-0/3)
(0A : Path-1/3)
(0B : Path-0/1/3)
(0C : Path-2/3)
(0D : Path-0/2/3)
(0E : Path-1/2/3)
(0F : Path-0/1/2/3)
(10 : Port-0A)
(11 : Path-0/PortA)

MSG 05-0000-01
Collect the error

Message
code
Trace Trace Dump
R20000 DCTL byte write error A writing done beyond the 4- Gather cWhen W0100x CTL alarm Chapter 6. Warning
[REG82001238, Bit27] byte boundary was detected. is displayed following this Messages (MSG 06-
message.
R20100 DCTL data read A data parity error was detected Gather cReplace the Control Unit Replacement 2.2.5
parity error during an output from the data whose CALM LED is on. Replacing Control
[REG82001238, Bit23] buffer to the PCI bus. Unit (REP 02-0390)
R20300 DCTL address over A CADROV was detected when Gather
[MPU] the MPU accessed the cache.
[REG82001238, Bit21]
R20400 DCTL address parity An address parity error was Gather
error [MPU] detected in the transfer address
[REG82001238, Bit20] received by the cache.
R20500 DCTL LEN parity An LEN parity error was Gather
error detected in the transfer word
[REG82001238, Bit19] length received by the cache.
R20600 DCTL address over A CADROV was detected when Gather
[DMA] the H/D_PORT, DMA#0 or
[REG82001238, Bit18] MDMA accessed the cache.
R20700 DCTL dummy area Access, which was done to the Gather
access error access restricted area in the area
[REG82001238, Bit17] for 4-byte dummy data addition of
the cache, was detected.
R20800 DCTL REF counter A parity error was detected in Gather
parity error the counter for the cache
[REG82001238, Bit1] memory refreshment timing.
R20900 DCTL PPCI parity A parity error was detected. Gather
error
[REG8200127C,
Bit31]
R20A00 DCTL PPCI system An assertion of a system error Gather
error was detected.
[REG8200127C,
Bit30]
R20B00 DCTL PPCI master A master abortion was Gather
abort executed.
[REG8200127C,
Bit29]
R20C00 DCTL PPCI received A target abortion was received. Gather
target abort
[REG8200127C,
Bit28]
R20D00 DCTL PPCI signaled A target abortion was executed. Gather
target abort
[REG8200127C,
Bit27]

MSG 05-0010-01
R20E00 DCTL PPCI PERR The data buffer controller LSI Gather
assert or reception (D-CTL) asserted or received at
[REG8200127C, the PERR when the bus master
Bit24] was used.

MSG 05-0010-01
Collect the error

Message
code
Trace Trace Dump
R20F00 DCTL PPCI ADR An address parity error was Gather cReplace the Control Unit Replacement 2.2.5
parity error detected. whose CALM LED is on. Replacing Control
[REG8200127C, Unit (REP 02-0390)
Bit23]
R20G00 DCTL PPCI DRD A parity error was detected in Gather
parity error the data read from the data
[REG8200127C, FIFO.
Bit22]
R20H00 DCTL PPCI CMD A parity error was detected Gather
parity error when the ADR/CMD was read
[REG8200127C, from the CMD buffer.
Bit21]
R20I00 DCTL PPCI CNT A parity error was detected Gather
parity error during counting by the FIFO
[REG8200127C, control counter.
Bit20]
R20J00 DCTL PPCI target A data response time-out Gather
data response time- (caused by 216 times of access)
out of a target was detected in the
[REG8200127C, case of the DCTL master.
Bit19]
R20K00 DCTL PPCI target An illegal termination of a target Gather
illegal termination was detected in the case of the
[REG8200127C, DCTL master. (The DEVSEL
Bit18] and STOP were negated at the
same time in the data phase.)
R20L00 DUAL I/F A failure in the impedance Gather
DUAL_IORDY error adjustment circuit in the self
[REG82001428, Bit29] system. (DUAL_IORDY)
R20M00 DCTL CACHE During a reading from the Gather cReplace the Cache Unit. Replacement 2.2.6
uncorrectable ERR cache, the ECC error of two or Replacing Cache
[REG82001439, Bit29] more bits occurred in the two Unit (REP 02-0540)
(CTL-x, CACHE-y) cache memory boards (MP). dIf not recovered, replace Replacement 2.2.5
x : Control Unit# (0-1) the above Control Unit. Replacing Control
y : Cache memory slot# Unit (REP 02-0390)
(RKM/RKS=0,1,*)
(* means the detection of
both 0 and 1.)
R20N00 Hard register error The error is A_CTLIN=1 (The Gather cReplace the Control Unit Replacement 2.2.5
[A_CTLIN] Control Unit of the other system whose CALM LED is on. Replacing Control
is not installed.) of the I2C Unit (REP 02-0390)
GPIO#1 register and it is also
EXT_IORDY=1 (Impedance
adjustment in the other system
was completed.) of the
impedance adjustment_1
register.
R20P00 Vector registration The vector registration of the Gather
failure [KEYINT] KEYINTSTS interrupt failed.
R20Q00 Vector registration The vector registration of the Gather

MSG 05-0020-01
failure [OFFREQ] OFFREQ interrupt failed.

R20R00 Vector registration The vector registration of the Gather
failure [DCTLERR] DCTLERR interrupt failed.

MSG 05-0020-01
Collect the error

Message
code
Trace Trace Dump
R20S00 Vector registration The vector registration of the Gather cReplace the Control Unit Replacement 2.2.5
failure [DRAMERR] DRAMERR interrupt failed. whose CALM LED is on. Replacing Control
R20T00 Vector registration The vector registration of the Gather Unit (REP 02-0390)
failure [SRAMERR] SRAMERR interrupt failed.
R20U00 Vector registration The vector registration of the Gather
failure [PCI0ERR] PCI0ERR interrupt failed.
R20V00 Vector registration The vector registration of the Gather
failure [PCI1ERR] PCI1ERR interrupt failed.
R20W00 Vector registration The vector registration of the Gather
failure [CPUERR] CPUERR interrupt failed.
R20Y00 DCTL D0PCI The invalid split completion Gather
unexpected SPC message was detected (D #0).
detected
[REG82001288, Bit12]
R20Z00 DCTL D0PCI SPS The split completion message Gather
[REG82001288, Bit13] an error was detected (D #0).
R21000 DCTL D0PCI split The data buffer controller LSI Gather
completion time-out (D-CTL) detected time-out of
(D #0).
R21100 DCTL D0PCI master The data buffer controller LSI Gather
completion message (D #0).
R21200 DCTL D0PCI SPC The data buffer controller LSI Gather
when it was a PCI slave (D #0).
R21300 DCTL D0PCI data Data response time-out of the Gather
response time-out target was detected at the time
[REG82001288, Bit19] of the DCTL master.
R21400 DCTL D0PCI counter A parity error was detected Gather
parity error when the FIFO counter was
[REG82001288, Bit20] counting.
R21500 DCTL D0PCI A parity error was detected Gather
command parity error when an address/command was
[REG82001288, Bit21] read from the command buffer.
R21600 DCTL D0PCI data A parity error was detected in Gather
parity error the data that was read from the
[REG82001288, Bit22] data FIFO.
R21700 DCTL D0PCI address A parity error of an address was Gather
parity error detected.
[REG82001288, Bit23]

MSG 05-0030-01
Collect the error

Message
code
Trace Trace Dump
R21800 DCTL D0PCI PERR The PERR was asserted at the Gather cReplace the Control Unit Replacement 2.2.5
detected time of the bus master. whose CALM LED is on. Replacing Control
[REG82001288, Bit24] Unit (REP 02-0390)
R21900 DCTL D0PCI single The target abort was executed. Gather
target abort
[REG82001288, Bit27]
R21A00 DCTL D0PCI target The target abort was received. Gather
abort received
[REG82001288, Bit28]
R21B00 DCTL D0PCI master The master abort was executed. Gather
abort
[REG82001288, Bit29]
R21C00 DCTL D0PCI system An assert of the SERR was Gather
error detected.
[REG82001288, Bit29]
R21D00 DCTL D0PCI parity A parity error was detected. Gather
error
[REG82001288, Bit29]
R21E00 DCTL PPCI ADB The data buffer controller LSI Gather
error (D-CTL) detected that the PCI
when it was a PCI slave.
R21F00 DCTL PPCI SPC The data buffer controller LSI Gather
completion message.
R21G00 DCTL PPCI SPC The data buffer controller LSI Gather
[REG8200127C, waiting for the split completion.
Bit14]
R21H00 DCTL PPCI SPC The split completion message Gather
[REG8200127C, an error was detected.
Bit13]
R21J00 DCTL PPCI The invalid split completion Gather
unexpected SPC message was detected
detected
[REG8200127C,
Bit12]
R21K00 DCTL CBUF A parity error was detected in Gather
SELCNT parity error the counter for the output
[REG82001238, Bit14] pointer of a buffer for writing to
the cache
R21L00 DCTL PBUF SELCNT A parity error was detected in Gather
parity error the counter for the input pointer

MSG 05-0040-01
[REG82001238, Bit14] of a buffer for writing to the

cache

MSG 05-0040-01
Collect the error

Message
code
Trace Trace Dump
R21M00 DCTL DBUF byte Writing to the outside of the 4- Gather cReplace the Control Unit Replacement 2.2.5
write error byte boundary was detected in whose CALM LED is on. Replacing Control
[REG82001238, Bit16] the ByteCnt in the PCI attribute Unit (REP 02-0390)
R21N00 DCTL register wait A parity error was detected in Gather
counter parity error the counter of the waiting time of
[REG82001238, Bit13] the SEQ for writing to the
register
R21P00 DCTL RCTL error No response with the RCTL Gather c When W0100x CTL alarm Chapter 6. Warning
[REG82001238, Bit25] (CACHE-IF) signal, which is displayed following this Messages (MSG 06-
showed a read response, was message, take recovery 0000)
made to the cache controller. actions according to the
R21Q00 DCTL RCTL error No response with the RCLK Gather message.
[REG82001238, Bit24] (CACHE-IF) signal, which was a dReplace the Control Unit of Replacement 2.2.5
clock signal for taking in the which the CALM LED lights Replacing Control
read data, was made to the on except for c. Unit (REP 02-0390)
cache controller.
R21R00 DCTL D1PCI The invalid split completion Gather cReplace the Control Unit Replacement 2.2.5
unexpected SPC message was detected. whose CALM LED is on. Replacing Control
detected Unit (REP 02-0390)
[REG8200128C,
Bit12]
R21S00 DCTL D1PCI SPC The split completion message Gather
[REG8200128C, an error was detected.
Bit13]
R21T00 DCTL D1PCI SPC Time-out of the split completion Gather
time-out response was detected.
[REG8200128C,
Bit14]
R21U00 DCTL D1PCI SPC The data buffer controller LSI Gather
completion message.
R21V00 DCTL D1PCI master The data buffer controller LSI Gather
[REG8200128C, address other than the ADB
Bit18] (allowable disconnect boundary)
when it was a PCI slave.
R21W00 DCTL D1PCI data Data response time-out of the Gather
response time-out target was detected at the time
[REG8200128C, of the DCTL master.
Bit19]
R21Y00 DCTL D1PCI counter A parity error was detected Gather
parity error when the FIFO counter was
[REG8200128C, counting.
Bit20]

MSG 05-0050-01
R21Z00 DCTL D1PCI A parity error was detected Gather

command parity error when an address/command was
[REG8200128C, read from the command buffer.
Bit21]

MSG 05-0050-01
Collect the error

Message
code
Trace Trace Dump
R22000 DCTL D1PCI data A parity error was detected in Gather cReplace the Control Unit Replacement 2.2.5
read parity error the data that was read from the whose CALM LED is on. Replacing Control
[REG8200128C, data FIFO. Unit (REP 02-0390)
Bit22]
R22100 DCTL D1PCI address A parity error of an address was Gather
parity error detected.
[REG8200128C,
Bit23]
R22200 DCTL D1PCI PERR The data buffer controller LSI Gather
[REG8200128C, the PERR when the bus master
Bit24] was used.
R22300 DCTL D1PCI signal The target abort was executed. Gather
target abort
[REG8200128C,
Bit27]
R22400 DCTL D1PCI The target abort was received. Gather
received target abort
[REG8200128C,
Bit28]
R22500 DCTL D1PCI master The master abort was executed. Gather
abort
[REG8200128C,
Bit29]
R22600 DCTL D1PCI system An assert of the SERR was Gather
error detected.
[REG8200128C,
Bit30]
R22700 DCTL D1PCI data A parity error was detected. Gather
parity error
[REG8200128C,
Bit31]
R30000 DCTL ECC write A parity error was detected in Gather c When W0100x CTL alarm Chapter 6. Warning
parity error the ECC adding part during a is displayed following this Messages (MSG 06-
[REG82001238, Bit31] writing on the cache. message, take recovery 0000)
R30100 DCTL ECC generate An ECC generation error was Gather actions according to the
error detected in the ECC adding part message.
[REG82001238, Bit30] during a writing on the cache. dReplace the Control Unit of Replacement 2.2.5
R302xy DCTL CACHE During a reading from the Gather cReplace the Cache Unit. Replacement 2.2.6
uncorrectable ERR cache, an EC error of two or Replacing Cache
[REG82001238, Bit29] more bits occurred in a single Unit (REP 02-0540)
(CTL-x, CACHE-y) cache memory board. dIf not recovered, replace Replacement 2.2.5
x : Control Unit # (0-1) the above Control Unit. Replacing Control
y : Cache memory slot # Unit (REP 02-0390)
(RKM/RKS=0,1,*)
(* means the detection of
both 0 and 1.)

MSG 05-0060-01
R3030x DCTL ECC correction An inconsistent correction of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
failed ECC was detected during a is displayed following this Messages (MSG 06-
[REG82001238, Bit28] readout from the cache. message, take recovery 0000)
message.

MSG 05-0060-01
Collect the error

Message
code
Trace Trace Dump
R312xy ECC uncorrectable The ECC uncorrectable error Gather cReplace all the cache Replacement 2.2.6
error (CTL-zx) occurred while the hardware memories installed in the Replacing Cache
error interrupt was being Control Unit. Unit (REP 02-0540)
suppressed. dIf not recovered, replace Replacement 2.2.5
x : Code the Control Unit. Replacing Control
(1 : LDR) Unit (REP 02-0390)
(2 : MNT)
(3 : INS)
(4 : COM)
y : Detail code #
z : Control Unit # (0-1)
R40100 DUAL I/F address An address parity error was Gather cReplace the Control Unit Replacement 2.2.5
parity error [INT/MP] detected when the MP wrote on whose CALM LED is on. Replacing Control
[REG82001448, Bit15] a certain part in another system. Unit (REP 02-0390)
R40200 DUAL I/F write data A data parity error was detected Gather
parity error [INT/MP] when the MP wrote on a certain
[REG82001448, Bit14] part in another system.
R40300 DUAL I/F write ready An ADR sending ready time-out Gather
time-out [INT/MP] was detected when the MP
[REG82001448, Bit13] wrote/read on/from a certain
part in another system.
R40400 DUAL I/F CNT parity A count parity error was Gather
error [INT/MP] detected when the MP wrote on
[REG82001448, Bit12] a certain part in another system.
R40500 DUAL I/F read data A data parity error was detected Gather
parity error [INT/MP] when the MP read from a
R40600 DUAL I/F read data A data ready time-out was Gather
ready time-out detected when the MP read
[INT/MP] from a certain part in another
R40900 DUAL I/F address A parity error was detected in Gather
parity error [EXT/MP] the address used for access by
[REG82001820, Bit0] each port to another system.
R40A00 DUAL I/F CACHE A CADROV was detected when Gather
address over the DMA wrote on the cache in
[EXT/DMA] another system.
[REG82001838, Bit18]
R40B00 DUAL I/F read data A data parity error was detected Gather
parity error [EXT/MP] when the MP read from a
R40C00 DUAL I/F ECC An ECC_COR error was Gather
correction error detected when the MP read
R40D00 DUAL I/F ECC An ECC_UNCORRE error was Gather
uncorrectable error detected when the MP read

MSG 05-0070-01
Collect the error

Message
code
Trace Trace Dump
R40E00 DUAL I/F write parity A parity error was detected in Gather cReplace the Control Unit Replacement 2.2.5
error [EXT/MP] write data when the MP wrote whose CALM LED is on. Replacing Control
[REG82001838, Bit31] on a certain part in another Unit (REP 02-0390)
system.
R40F00 DUAL I/F ECC write An ECC_WPTY error was Gather
R40G00 DUAL I/F ECC GEN An ECC_GEN error was Gather
error [EXTMP] detected when the MP wrote on
R40H00 DUAL I/F CACHE A cache address parity error Gather
address parity error was detected when the MP
[EXT/MP] wrote on the cache in another
R40I00 DUAL I/F WLEN A WLEN parity error was Gather
R40J00 DUAL I/F counter A counter parity error was Gather
R40K00 DUAL I/F CACHE A CARDOV error was detected Gather
address over when the MP wrote on the
[EXT/MP] cache in another system.
[REG82001838, Bit25]
R40M00 DUAL I/F error An error was detected when the Gather
[MDTDCHK] MP accessed another system.
[REG82001228, Bit17]
R40N00 DUAL I/F A failure of the impedance Gather
SELF_IORDY error adjustment circuit in the own
[REG82001428, Bit22] system was detected.
R40P00 DUAL I/F A failure of the impedance Gather
SELF_IORDY error adjustment circuit in another
[REG82001428, Bit21] system was detected.
R40Q00 DUAL I/F The SELF_IORDY changed Gather
SELF_IORDY from RDY to NotRDY.
changed RDY into
NotRDY [INT/MP]
[REG82001428, Bit28]
R40R00 DUAL I/F The EXT_IORDY changed from Gather
EXT_IORDY changed RDY to NotRDY.
RDY into NotRDY
[INT/MP]
[REG82001428, Bit26]
R40S00 DUAL I/F MRGN The data buffer controller LSI Gather
error [INT/MP] (D-CTL) detected a margin error
[REG82001484, Bit2] when it acquired data from the
other one of the dual Control
Unit.

MSG 05-0080-01
Collect the error

Message
code
Trace Trace Dump
R40T00 DUAL I/F SEQ error When the Control Unit in the self Gather cReplace the Control Unit Replacement 2.2.5
[INT/MP] system adjusted the data input whose CALM LED is on. Replacing Control
[REG82001484, Bit1] timing during data Unit (REP 02-0390)
CTLs]
R40U00 DUAL I/F SLV error An error was reported from the Gather
[INT/MP] other Control Unit.
[REG82001484, Bit3]
R40V00 DUAL I/F DCNT error The delay counter exceeded the Gather
[INT/MP] allowable delay limit of the delay
[REG82001484, Bit0] element.
R40W00 DUAL I/F RCLK error The RCLK error was detected Gather
[EXT/MP] when the other one of the dual
[REG82001838, Bit23] Control Unit of the MP was
reading from the cache.
R40Y00 DUAL I/F RCLK error The RCLK error was detected Gather
R50200 BRG CPU address The CPU address out of range Gather
out of range was detected.
[REGF1000140, Bit0] [BRG CPU]
R50300 BRG CPU bad The Bad Address Parity was Gather
address parity detected.
detected [BRG CPU]
[REGF1000140, Bit1]
R50400 BRG CPU transfer The transfer type violation was Gather
type violation detected.
R50500 BRG CPU access to Access to a protected region Gather
a protected region was detected.
R50600 BRG CPU write to a A writing on a write-protected Gather
write protected region region occurred.
R50700 BRG CPU read from A readout from a caching- Gather
a caching protected protected region occurred. [BRG
region CPU]
[REGF1000140, Bit5]
R50800 BRG CPU bad write The bad write data parity was Gather
[REGF1000140, Bit6]
R50900 BRG CPU bad read The bad read data parity was Gather
[REGF1000140, Bit7]

MSG 05-0090-01
Collect the error

Message
code
Trace Trace Dump
R50B00 BRG PCI0 the PCI The PCI slave detected the bad Gather cReplace the Control Unit Replacement 2.2.5
slave detected bad write data parity. whose CALM LED is on. Replacing Control
write data parity [BRG CPU] Unit (REP 02-0390)
[REGF1001D58, Bit1]
R50C00 BRG PCI0 PERR The PERR response to read Gather
response to read data data by the PCI slave occurred.
driven by PCI slave [BRG PCIO]
[REGF1001D58, Bit2]
R50D00 BRG PCI0 PERR The PERR response to Gather
response to address address by the PCI master
driven by the PCI occurred. [BRG PCIO]
master
[REG14001D58, Bit4]
R50E00 BRG PCI0 PERR The PERR response to write Gather
response to write data by the PCI master
data driven by the occurred. [BRG PCIO]
PCI master
[REGF1001D58, Bit5]
R50F00 BRG PCI0 bad data The bad data parity was Gather
parity detected during detected during a readout by the
the PCI master read PCI master.
[REGF1001D58, Bit6] [BRG PCIO]
R50G00 BRG PCI0 the PCI A master abortion occurred in Gather
master generated the PCI master.
master abort [BRG PCIO]
[REGF1001D58, Bit8]
R50H00 BRG PCI0 the PCI The PCI master detected a Gather
master detected target abortion. [BRG PCIO]
target abort
[REGF1001D58, Bit9]
R50I00 BRG PCI0 generate The slave PCI terminated the Gather
transaction while process because of a target
master is not enabled abortion. [BRG PCIO]
[REG14001D58,
Bit10]
R50J00 BRG PCI0 the PCI The threshold value of the retry Gather
master reached retry counter was exceeded in the
counter limit PCI master. [BRG PCIO]
R50L00 BRG PCI0 the PCI The PCI slave terminated the Gather
slave terminates a process because of a target
transaction with abortion. [BRG PCIO]
Target Abort
R50P00 BRG PCI0 a PCI The read buffer discard timer Gather
slave read buffer expired occurred in the PCI
discard timer expired slave. [BRG PCIO]

MSG 05-0100-01
Collect the error

Message
code
Trace Trace Dump
R50Q00 BRG PCI0 Internal The internal PCI arbiter Gather cReplace the Control Unit Replacement 2.2.5
PCI arbiter detection detection of a broken master whose CALM LED is on. Replacing Control
of a broken master occurred. Unit (REP 02-0390)
[REGF1001D58, Bit21] [BRG PCIO]
R50R00 BRG PCI0 PCI BIST The PCI BIST interrupt Gather
interrupt occurred. [BRG PCIO]
R50S00 BRG PCI0 PCI power The PCI power management Gather
management interrupt interrupt occurred. [BRG PCIO]
R50T00 BRG PCI0 PCI reset The PCI reset assert occurred. Gather
assert [BRG PCIO]
R50V00 BRG CPU internal An internal data path parity error Gather
data path parity error was detected in the CPU
detected interface unit.
[REGF1000140, Bit8]
R50W00 BRG DRAM internal The Dunit internal data path Gather
data path parity error parity error was detected.
[REGF10014D0, Bit2]
R50Y00 BRG DRAM double bit The DRAM two-bit ECC error Gather
ECC error detected was detected.
[REGF10014D0, Bit1]
R50Z00 BRG DRAM single bit The number of the DRAM single Gather
ECC threshold expired bit ECC errors reached the
[REGF10014D0, Bit0] threshold value.
R51000 BRG SRAM double bit The SRAM two-bit ECC error Gather
ECC error detected was detected.
[REGF10014D0, Bit0]
R51100 BRG SRAM single bit The number of the SRAM single Gather
ECC error threshold bit ECC errors reached the
expired threshold value.
[REGF10014D0, Bit0]
R51200 BRG PCI0 master The PCI master generated the Gather
generated target abort target abort for the split
for split completion completion.
[REGF1001D58, Bit7]
R51300 BRG PCI0 slave SPC The PCI slave terminated the Gather
transaction terminated transaction with the target abort.
with an abort
R51400 BRG PCI0 slave The excess of the threshold Gather
reached the retry value of the retry counter
counter limit occurred in the PCI slave when
[REGF1001D58, Bit22] generation of the split
completion was attempted.

MSG 05-0110-01
Collect the error

Message
code
Trace Trace Dump
R51500 BRG PCI0 slave as a The PCI slave detected the Gather cReplace the Control Unit Replacement 2.2.5
completer detected target abort as a completer. whose CALM LED is on. Replacing Control
target abort Unit (REP 02-0390)
R51600 BRG PCI0 slave The master abort occurred in Gather
generated master the PCI slave as a completer.
abort as a completer
R51700 BRG PCI0 master The PCI master received a Gather
received message message error.
error
R51800 BRG PCI0 master The PCI master received the Gather
received incorrect Split Completion with a size
split completion (number of bytes) that does not
[REGF1001D58, Bit3] meet the requirement.
R51900 BRG PCI0 master The time when the PCI master Gather
split completion discards the Split Completion
discard timer expired has come.
R51A00 BRG PCI0 The PCI transaction was Gather
transaction generated generated while the master PCI
while master is was disabled.
disabled
R51B00 BRG PCI0 internal An internal data path error was Gather
data path error in the detected in the PCI interface.
PCI interface
[REGF1001D58, Bit0]
R51C00 BRG PCI0 DWORD An issue of an I/O instruction Gather
boundary error beyond the DWORD boundary
[REGF1001D58, Bit4] was attempted.

MSG 05-0120-01
Collect the error

Message
code
Trace Trace Dump
RA00xx Microprogram error A system shutdown occurred Gather cTurn on the power again.
[FLS] because of a logical
contradiction.
x : Any code
RA01xy Microprogram error Logical illegality of the Gather cWhen W0100x CTL alarm Chapter 6. Warning
[COM] microprogram was detected. is displayed following this Messages (MSG 06-
(common function). message, take recovery 0000)
xy : Any code actions according to the
message.
RA0410 Host name delete The network download function Gather c Check the directory, in
error failed to delete the host name. which the main system is
RA0411 NFS unmount error An NFS unmounting resulted in Gather stored, entered in the WEB
an error during operation of the window.
network download function. d Replace the Control Unit if Replacement 2.2.5
RA0412 NFS mount error An NFS mounting resulted in an Gather the error recurs. Replacing Control
error during operation of the Unit (REP 02-0390)
network download function.
RA0413 Host name add error The network download function Gather
failed to add the host name.
RA0414 NFS file open error A file opening resulted in an Gather
error during operation of the
network download function.
RA0415 System file error An error was detected in a file in Gather cCheck if the directory, in
the directory storing the system which the main system is
during operation of the network stored, entered in the Web
download function. window and the files stored
in it are correct.
dReplace the Control Unit if Replacement 2.2.5
the error recurs. Replacing Control
Unit (REP 02-0390)
RA1000 Loop error A system shutdown occurred Gather cCollect and analyze Troubleshooting 7.5
because of a loop failure. memory dump and specify Collecting Memory
the failed part. Dump (TRBL 07-
0130)
06-0600)

MSG 05-0130-01
Collect the error

Message
code
Trace Trace Dump
RA30xy CACHE size A cache mounting error cCheck if the Cache Unit is Troubleshooting
mismatch b/w. CTL occurred. installed in a correct 10.2.1 Maintenance
(CACHE-x) x : Cache memory slot # location by referring to the with the Storage
(RKM/RKS=0-1) location of the Navigator Modular
corresponding Cache Unit (GUI version)(TRBL
on the normal mate Control 10-0080)
Unit.
dReplace the Cache Unit. Replacement 2.2.6
Replacing Cache
Unit (REP 02-0540)
RA4000 CTL synchronized Synchronization failed. Gather cReplace the Control Unit Replacement 2.2.5
error whose CALM LED is on. Replacing Control
RA4100 CTL initial Time-out occurred in another Unit (REP 02-0390)
synchronized error system because of an initial
synchronization.
RA4200 Maintenance mode A synchronization error
synchronized error occurred in maintenance mode.
RA6000 CTL number The single mode is set in the cSet the system parameter For WEB Chapter 3.
mismatch system parameter but dual correctly in the WEB The Maintenance
mode is selected actually. maintenance mode. Mode Operation
RA6100 System parameter System parameter information Procedure (WEB 03-
undefined (common) is not set. 0000)
RA7000 Microprogram The systems drive-loaded cTurn the power off, then
revision mismatch between Control Units are turn it on again.
mismatched.
RA7600 CTL unit type Inconsistency of Control Unit Gather cCheck types of the two
mismatch type was detected. Control Units and replace
the wrong Control Unit with
a correct one.
RA7700 CTL unit type cache A unsupported cache memory Gather cCheck the cache capacity
size over capacity size (larger then 1GB) and replace the cache
was detected in the DF700 memory with that supported
RKS. by the DF700 RKS.
RA780x Unsupported CACHE A start-up was attempted using Gather cReplace the Cache Unit. Replacement 2.2.6
(CACHE-x) a unsupported cache. Replacing Cache
x : Cache memory # Unit (REP 02-0540)
(RKM/RKS=0-1) dIf the problem is not solved Replacement 2.2.5
in spite of the replacement, Replacing Control
RA7900 System HDU spin up Spin-up of the system drive Gather cReplace the part in which
failed failed. the failure occurred, and
then turn on the power
again.

MSG 05-0140-01
Collect the error

Message
code
Trace Trace Dump
RA7A00 CACHE installation Cache memories are not Gather cInstall the cache memories Replacement 2.2.6
error installed in both of the Slots #0 in both of the Slots #0 and Replacing Cache
(CACHE-0/1) and #1. #1. Unit (REP 02-0540)
RA7B0x CACHE size get error Acquisition of the cache Gather cReplace a cache memory Replacement 2.2.6
(CACHE-x) capacity failed. inserted in the cache slot Replacing Cache
x : Cache memory slot # whose number was shown Unit (REP 02-0540)
(RKM/RKS=0-1) in the message.
in spite of the replacement, Replacing Control
RA7C00 Unsupported unit is A unsupported disk array unit is Gather cWhen the RKAJAT is
connected connected. mounted, disconnect the
connected RKAJ.
RA7D00 MAC address error MAC address is illegal Gather cBecause a controller Replacement 2.2.5
[usrport]/[mntport] detachment is caused by Replacing Control
the MAC address error, Unit (REP 02-0390)
replace a controller whose
CALM LED is on.
RA7E0x CTL unit type error An illegal Frame type was Gather cWhen W0100x CTL alarm Chapter 6. Warning
detected (CTL-x) detected. is displayed following this Messages (MSG 06-
x : Control Unit # (0-1) message, take recovery 0000)
message.
RA7F00 TWSI access error An error was detected during Gather
[Read, XX-YY-AA- the I2C reading in the flash
BB] operation.
RA8000 TWSI access error An error was detected during Gather
[Write, XX-YY-AA-BB] the I2C writing in the flash
operation.
RA8100 TWSI access error The triple reading error was Gather
[3 times reading, X] detected during the I2C reading
in the flash operation.
RA8200 DUAL I/F DESKEW is Though the Control Unit in the Gather cReplace the Control Unit Replacement 2.2.5
not completed self system attempted to adjust whose CALM LED is on. Replacing Control
the data input timing when it Unit (REP 02-0390)
was sending/receiving data
to/from the Control Unit in the
other system, the adjustment
was not completed within the
time limit. [Failure in the bus
between the CTLs]

MSG 05-0150-01
Collect the error

Message
code
Trace Trace Dump
RA8300 CACHE sleep A time-out error occurred Gather cReplace the Control Unit Replacement 2.2.5
termination time-out because the status in which the whose CALM LED is on. Replacing Control
cache was sleeping status was Unit (REP 02-0390)
not removed.
RA8400 PONCNT parity error PONCNT parity error. Gather
RA8500 DDR2 I/O buffer error An impedance adjustment Gather

failure of the DDR2 I/O buffer
was detected.
RA8600 The setting of The setting of the cache control Gather
CACHE control mode mode failed.
failed
RA8700 The setting of The setting of the cache Gather
CACHE terminate memory termination value failed.
failed
RA8800 CTL number error The Slot# bit failure of the TWSI Gather
GPIO#1 register was detected.
RA8900 DCTL register error When the Control Unit of the Gather
[EMACIN/A_CTLIN] other system requested the
DCTL_MODE register to be
detached (EMACIN=1), it was
detected that the Control Unit of
the other system of the TWSI
GPO#1 register was not
installed (A_CTLIN=1).
RA8A00 DCTL EMACIN not The EMACIN bit failure occurred Gather
detected when the Control Unit was
inserted while the power was
on.
RA8B00 TWSI access error A reading error occurred in the Gather
[Configuration register TWSI initialization (setting of the
read, XX-YY-AA-BB] TWSI-GPIO I/O attribute) at the
RA8C00 TWSI access error A writing error occurred in the Gather
[Configuration register TWSI initialization (setting of the
write, XX-YY-AA-BB] TWSI-GPIO I/O attribute) at the
RA8D00 TWSI access error The triple reading error occurred Gather
[Configuration register in the TWSI initialization (setting
3 times, X] of the TWSI-GPIO I/O attribute)
at the time of the subsystem
boot

MSG 05-0160-01
Collect the error

Message
code
Trace Trace Dump
RA9000 Task make error Generation of a task or a Gather cReplace the Control Unit Replacement 2.2.5
semaphore failed. whose CALM LED is on. Replacing Control
Unit (REP 02-0390)
RAA000 CUDG skip CUDG skip was made.
RAA100 Remote reboot A remote rebooting was done.

execute
RAA200 Option data initialized The unlocking information was
initialized owing to an
occurrence of a sumcheck error
in the take-over information area
(FM) in which the unlocking
information is stored.
RB0000 Upload system error An incorrect microprogram (with Gather cCheck the microprogram
an incorrect file and/or directory you want to install and
configuration) was specified install it over again.
during a upload.
RB0100 File remove error Deletion of a file on the RAM Gather cTurn on the power again.
disk failed.
in spite of the above Replacing Control
operation, replace the Unit (REP 02-0390)
Control Unit on which the
CALM LED is lit
RB0400 System parameter Update of the system Gather cReset the system
update error parameters failed at the time of parameters correctly in the
start-up. (The threshold value Maintenance mode of the
concerning the system Web.
parameter update was dIf the system is still Replacement 2.2.5
exceeded.) abnormal, replace the Replacing Control
above Control Unit. Unit (REP 02-0390)
RB0500 System parameter Reading of the system Gather cReset the system
load failed parameter information from the parameters correctly in the
system area failed. Maintenance mode of the
Web.
dIf the system is still Replacement 2.2.5
abnormal, replace the Replacing Control
above Control Unit. Unit (REP 02-0390)
RB0600 No micro program No microprogram is present in Gather cInstall the microprogram
the system drive. newly.
RB0700 NO micro program No system parameter Gather cReset the system
information is present in the parameters correctly in the
system drive. Maintenance mode of the
Web.

MSG 05-0170-01
Collect the error

Message
code
Trace Trace Dump
RB0800 System parameter Writing on all drives failed. Gather cReset the system
update failed parameters correctly in the
Maintenance mode of the
Web.
in spite of the above Replacing Disk Drive
operation, replace the Disk (REP 02-0050)
Drives #0 to #4 of the RKM.
RB0900 System parameter Writing on one to four system Gather cTurn on the power again.
update partially drives failed. dIf the system is still
complete abnormal, reset the system
parameters correctly in the
Maintenance mode of the
Web.
RB0A00 Upload file SUM A sum check error occurred in a Gather cCheck the microprogram
check error read file during a upload. you want to install and
install it over again.
RB0B0x CACHE property Cache property error (A Gather cCheck if the capacity of the
error (CACHE-x) unsupported cache is installed.) cache installed is 512
x : Cache memory slot # Mbytes or 1024 Mbytes.
(RKM/RKS=0-1)
RB0Cxy CACHE pair check Cache pair check error (Caches Gather cMake the caches in the two
error (CACHE-x/y) installed in the Slot #0 and Slot slots the same.
#1 are different each other.)
(RKM/RKS=0-1)
RB0D00 RAM disk create Creation of the RAM disk failed. Gather cTurn on the power again.
failed dIf the problem is not solved Replacement 2.2.5
in spite of the above Replacing Control
operation, replace the Unit (REP 02-0390)
CALM LED is lit
RB0I00 Bad LBA detected in Illegal write LBA owing to illegal Gather cGet the microprogram For Microprogram
START70M.DAT contents of the uploading file. again and then reinstall it. Chapter 1.
RB0J00 Bad LBA detected Illegal write LBA owing to illegal Gather Installation of
START70S.DAT contents of the uploading file. Microprogram
(MICRO 01-0000)

MSG 05-0180-01
Collect the error

Message
code
Trace Trace Dump
RB3000 File size error An error was detected in file Gather cCheck the microprogram
size. you want to install
RB3100 File open error Opening of file failed. Gather
RB3200 File read error Reading of file failed. Gather
RB3500 Bad block ID An illegal block ID was detected. Gather
RB7000 Program size too The program is too large in size.

large
RB8000 Old microprogram There was another system when cIf installation may be For Microprogram
exists installation was started. continued (In this case, all Chapter 1.
the data in the Disk Drive Installation of
are deleted (The RAID Microprogram
group and LU deformation (MICRO 01-0000)
are initialized)), insert the
next FD and continue
installation.
dWhen the data in the Disk
Drive need to be saved,
stop the work and perform
update installation.
RB8100 Install failed Installation failed. Gather cThe cause of the failure is
indicated under the
message. Solve the failure
according to the procedure
indicated under the
message.
RB8200 Install partially Installation failed in a part of the Gather cSee [Procedure of locating For Microprogram
complete drive. failed part when the Chapter 1.
message of Install partially Installation of
complete is output]. Microprogram
(MICRO 01-0000)
RB8300 Empty system retry Update installation cannot be cExecute new installation.
full install executed since a system does
not exist in the Disk Drive.
RB8400 Download failed Drive-loading failed. Gather cRefer to Troubleshooting Troubleshooting
6.1.2 The subsystem 6.1.2 The
does not become ready : subsystem does not
Case 1 (Loading failure). become ready : Case
Besides, use the FC disk 1 (Loading failure)
array unit for the Unit #0 (TRBL 06-0050)
RB8500 Microprogram extract Depression of main cExecute update installation. For Microprogram
error microprogram failed. Chapter 1.
Installation of
Microprogram
(MICRO 01-0000)
the Control Unit whose Replacing Control
CALM LED is on. Unit (REP 02-0390)

MSG 05-0190-01
Collect the error

Message
code
Trace Trace Dump
RBA000 Down grade check Down-grade check result was cCancel the downgrade
NG NG. check and reboot the
subsystem.
dUpdate the microprogram For Microprogram
again. Chapter 1.
Installation of
Microprogram
(MICRO 01-0000)
RBC000 No drive available There is not a Disk Drive to Gather cReplace the disk drives #0 Replacement 2.2.1
install. to #4 of the RKM disk array Replacing Disk Drive
unit. Besides, use the FC (REP 02-0050)
disk array unit for the Unit
#0.
RBC10x Drive block size error Illegal drive block size was cReplace the Disk Drive. Replacement 2.2.1
(Unit-0, HDU-x) detected during read capacity Check the model name of Replacing Disk Drive
check. the Disk Drive or the drive (REP 02-0050)
x : Unit ID# firmware revision. Replacement 1.1.3
(RKM/RKS=0) Procedure for making
(RKAJ/RKAJAT=1-14) sure of model name
y : Disk Drive# (0-14) and drive firmware of
RBC2xy Unknown drive Writing a program in FM0 failed. Disk Drive (REP 01-
(Unit-x, HDU-y) x : Unit ID# 0100)
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
y : Disk Drive# (0-14)
RBE000 Flash memory write Writing in the flash memory Gather cReplace the Control Unit Replacement 2.2.5
error (FM-x) failed. whose CALM LED is on. Replacing Control
x : Chip information that Unit (REP 02-0390)
caused the error
(0=FM1-0, 1=FM1-1,
2=FM both chips)
RBE100 Flash memory SUM A sum check error is detected in Gather
check error the flash memory.
RBE200 Flash program update When the FM microprogram cPerform the installation For Microprogram
error which failed in maintenance of upgrade. Chapter 1.
the flash version is updated, its Installation of
version is not matched to the Microprogram
version of the main (MICRO 01-0000)
microprogram. dIf not recovered, replace Replacement 2.2.5
the Control Unit whose Replacing Control
RBE300 Flash program update Updating of the FM1 flash
start program was started by the
latest REV maintenance
function of the flash program.
RBE301 Flash program update Updating of the FM1 flash
end program was started by the
latest REV maintenance
function of flash program.

MSG 05-0200-01
Collect the error

Message
code
Trace Trace Dump
RBE500 Initial setup error by The Initial setup failed because Gather cThe Initial setup is
LU access restriction access to the LU was restricted. impossible. To update the
microprogram, do it by
means of the update
installation.
RBE600 Config clear restart The Config clear restart failed Gather cThe Config clear restart is
error by LU access because access to the LU was impossible. To reboot,
restriction restricted. specify the TakeOver
(takeover reboot).
RBE700 Bad LBA in The LBA to be written, which is Gather cPerform a updating For Microprogram
START60A.DAT stored in the START60A.DAT installation. Chapter 1.
file, is incorrect. Installation of
Microprogram
(MICRO 01-0000)
RBE900 Upgrade failed The upgrade failed because the Gather cSelect the unified version For Microprogram
[the installed microprogram, installation of directory, whose version is Chapter 1.
microprogram is which was attempted, was a unified version same as Installation of
incorrect] incorrect. that of the microprogram of Microprogram
the lower grade model, and (MICRO 01-0000)
install the microprogram in
the subsystem of the higher
grade model for the
purpose of upgrade.
RBEA00 Downgrade failed The Downgrade failed because Gather cSelect the unified version
[the installed the microprogram, installation of directory, whose version is
microprogram is which was attempted, was a unified version of the
incorrect] incorrect. microprogram of the higher
grade model already
installed, and install the
microprogram in the
subsystem of the higher
grade model for the
purpose of update.
RBED00 System HDU spin up The type of the system drive is Gather cAssign an FC disk array
failed illegal. (The Unit #0 is not the unit to the Unit #0, or make
[unsupported Unit is FC disk array unit.) sure of the rule of the
connected Unit-00] connection.
RBEG00 Download failed The startup failed because the Gather cInstall the microprogram For Installation
[unsupported Unit is microprogram did not support that supports the S-ATA Chapter 3. Installing
connected] the S-ATA disk array unit. disk array unit after Rackmount Model
changing the mode to (INST 03-0000),
Maintenance, or start up Addition/Subtraction/
the subsystem after Relocation Chapter
removing the S-ATA disk 1. Adding Optional
array unit from the Components (ADD
configuration. 01-0000)

MSG 05-0210-01
Collect the error

Message
code
Trace Trace Dump
RBEN00 Installation of the The start-up could not be made Gather cWhen the FM MODE is the
other CTL detected because the FM mode was the installation mode, pull out
on install mode installation mode (for the JP and make the start-
emergency) at the time of the up again.
installation of a Control Unit of dIf not recovered, replace Replacement 2.2.5
the other system. the Control Unit whose Replacing Control

MSG 05-0220-01

MSG 05-0230-01
.
Chapter 6. Warning Messages

Collect the error
Message
code
Trace Trace Dump
W0100x CTL alarm (CTL-x) The Control Unit was regressed Gather cWhen I19000 Online
(It had a failure or was not micro-update completed is
connected), or a failure was displayed before this
detected in the Control Unit of message, it shows that no
another system during the initial Control Unit failure has
setting operation. occurred.
x : Control Unit # (0-1) dWhen the ALARM LED is Troubleshooting
lit, take a recovery action 6.1.1 System down
according to in (TRBL 06-0020)
Troubleshooting 6.1.1
System down.
eTake the recovery actions Troubleshooting 4.5
according to the messages The Priority Error
listed in Troubleshooting Messages when
4.5 The Priority Error W0100x CTL alarm
Messages when W0100x is displayed (TRBL
CTL alarm is displayed. 04-0180)
fIf only H90210 CTL failure
is displayed besides this
message, connect the
CALM LED is illuminating
to the Web, and follow the
recovery instruction
message displayed on the
Web.
gReplace the Control Unit Replacement 2.2.5
Unit (REP 02-0390)
W02000 Other CTL removed A shutdown occurred in MPU on Gather cReplace the Control Unit Replacement 2.2.5
the Control Unit of another whose CALM LED is on. Replacing Control
system. Unit (REP 02-0390)
W03000 Battery alarm Abnormal battery voltage or a cReplace the Backup Replacement 2.2.2
failure in the battery charging Battery Unit. (*1) Replacing Backup
circuit was detected. Battery Unit (REP
W0300x Battery alarm Abnormal battery voltage or a 02-0240)
(Battery-x) failure in the battery charging
circuit was detected.
(0-1)
*1 : If this massage is displayed and the ALARM LED on the Battery Unit (ASSY) lights on, be sure to replace the Battery
Unit (it cannot be recharged).

MSG 06-0000-01
Collect the error

Message
code
Trace Trace Dump
W03100 Battery removed A Backup Battery Unit has been cAttach a Backup Battery Replacement 2.2.2
removed from an subsystem. Unit to a subsystem. Replacing Backup
W0310x Battery removed A Backup Battery Unit has been Battery Unit (REP
(Battery-x) removed from an array unit. 02-0240)
(0-1)
W03200 Battery SW OFF The switch of a Backup Battery cSet the switch of a Backup
Unit has been set to OFF. Battery Unit to ON.
W0320x Battery SW OFF The switch of a Backup Battery
(Battery-x) Unit has been set to OFF.
(0-1)
W03300 Battery Thermal The battery thermal failed. cReplace the Backup Replacement 2.2.2
alarm Battery Unit. Replacing Backup
W0330x Battery Thermal The battery thermal failed. Battery Unit (REP
alarm x : Backup Battery Unit # 02-0240)
(Battery-x) (0-1)
W0340x Battery back up The battery backup circuit failed. cWhen any one of the
circuit alarm x : Control Unit # (0-1) following messages is
(CTL-x) displayed, follow the
recovery procedure given
by it.
W0300x Battery alarm
W0310x Battery removed
W0320x Battery SW OFF
W0330x Battery Thermal
alarm
dIf only W0340x Battery Replacement 2.2.5
back up circuit alarm is Replacing Control
displayed, replace a Control Unit (REP 02-0390)
Unit that has the number x.
W040xy FAN alarm The Fan Assembly failed. cReplace the Fan Assembly Replacement 2.2.3
(Unix-x, FAN-y) x : Unit ID # immediately since the Replacing Fan
(RKM/RKS=0) subsystem can go down Assembly (REP 02-
(RKAJ/RKAJAT=1-14) because of thermal alarm if 0300)
y : FAN Assembly # (0-1) the subsystem is left in this
state.
dReplace the Power Unit. Replacement 2.2.4
Replacing Power
Unit (REP 02-0340)
W04100 FAN alarm The Fan Assembly failed. cReplace the Fan Assembly Replacement 2.2.3
(CTL-Unit, FAN-x) x : FAN Assembly # (0-1) immediately since the Replacing Fan
subsystem can go down Assembly (REP 02-
because of thermal alarm if 0300)
the subsystem is left in this
state.

MSG 06-0010-01
Collect the error

Message
code
Trace Trace Dump
W050xy PS alarm The Power Unit failed. c When a trouble reported by Chapter 6. Warning
(Unit-x, PS-y) x : Unit ID # the message, W040xy Messages (MSG 06-
(RKM/RKS=0) FAN alarm has occurred at 0010)
(RKAJ/RKAJAT=1-14) the same time, take a
y : Power Unit # (0-1) recovery action against it
W05100 PS alarm The Power Unit failed. first.
(CTL-Unit, PS-x) x : Power Unit # (0-1) dReplace the Power Unit. Replacement 2.2.4
Replacing Power
Unit (REP 02-0340)
W060AT SATA HDU alarm The Disk Drive is blocked. Gather cReplace the Disk Drive. (*1)
Replacement 2.2.1
(Unit-x, HDU-y) x : Unit ID # When you want to know a Replacing Disk Drive
(RKAJAT=1-29) model name of the Disk (REP 02-0050)
y : Disk Drive # (0-14) Drive or a revision of the Replacement 1.1.3
drive firmware, refer to Procedure for making
of model name and drive Disk Drive(REP 01-
dIf the trouble is not solved Replacement 2.2.9
in spite of the above Replacing ENC
operation, replace the Unit/SENC Unit
SENC Unit in which the (REP 02-0830)
blocked Disk Drive is
installed.
Replace the SENC Unit #0
in which the blocked Disk
Drive is installed for the
Disk Drive with an even
number or the SENC Unit
#1 in which the blocked
Disk Drive is installed for
the Disk Drive with an odd
number.
W060xy HDU alarm The Disk Drive is blocked. Gather c Replace the Disk Drive.(*1) Replacement 2.2.1
(Unit-x, HDU-y) x : Unit ID # When you want to know a Replacing Disk Drive
(RKM/RKS=0) model name of the Disk (REP 02-0050)
(RKAJ/RKAJAT=1-14) Drive or a revision of the Replacement 1.1.3
y : Disk Drive # (0-14) drive firmware, refer to Procedure for making
W061AT SATA Spare HDU The Spare Disk failed. Gather Replacement 1.1.3 sure of model name
alarm (Unit-x, HDU-y) x : Unit ID # Procedure for making sure and drive firmware of
(RKAJAT=1-29) of model name and drive Disk Drive (REP 01-
W061xy Spare HDU alarm The Spare Disk failed. Gather
(RKM/RKS=0)
(RKAJ/RKAJAT=1-14)
*1 : The sequential shutdown may be failed if the Disk Drive is in the blocked status. Maintain the blocked Disk Drive
before executing the sequential shutdown.

MSG 06-0020-01
Collect the error

Message
code
Trace Trace Dump
W071xy HDU inquiry error An inquiry error occurred in a cReplace the Disk Drive.(*1) Replacement 2.2.1
(Unit-x, HDU-y) Disk Drive inserted with the When you want to know a Replacing Disk Drive
power turned on. model name of the Disk (REP 02-0050)
x : Unit ID # Drive or a revision of the Replacement 1.1.3
(RKM/RKS=0) drive firmware, refer to Procedure for making
W073xy HDU replace failed Insertion of a Disk Drive failed cWhen HDU alarm is Replacement 2.2.1
(Unit-x, HDU-y) when it was inserted with the displayed following this Replacing Disk Drive
power turned on. message, replace the Disk (REP 02-0050)
x : Unit ID # Drive (FC Disk Drive).
(RKM/RKS=0) dWhen S-ATA HDU alarm
(RKAJ/RKAJAT=1-14) is displayed following this
y : Disk Drive # (0-14) message, insert the Disk
Drive (S-ATA Disk Drive)
again. If the failure is not
solved in spite of this
operation, replace the Disk
Drive.

MSG 06-0030-01
Collect the error

Message
code
Trace Trace Dump
W080xy Loop alarm Since the Fibre Channel loop Gather cWhen one of the following
(Path-x, Loop-y) failed, the operation is continued messages is displayed
with the alternative loop. before this message, take
x : Path # recovery actions according
(RKM/RKS=0-1) to the message.
y : Loop # (0-1) W0100x CTL alarm
W060AT SATA HDU
alarm
W060xy, W0GG00,
W0GH00 HDU alarm
W061AT SATA Spare
HDU alarm
W061xy, W0GJ00,
W0GK00 Spare HDU
alarm
W090xy, W0GA00,
W0GC00 ENC alarm
W090AT, W0GB00,
W0GD00 SENC alarm
I301AT SATA HDU
error
I301xy HDU error
I5YG00 Unit# ERR
06-0600)

MSG 06-0040-01
Collect the error

Message
code
Trace Trace Dump
W090AT SENC alarm The SENC Unit failed. cWhen this message is
(Unit-x, ENC-y) x : Unit ID # displayed at the time of the
(RKAJAT=1-29) subsystem startup, the
y : SENC Unit # (0-1) ENC cable may also have a
connection error. Check
the cable connection.
dReplace the SENC unit Replacement 2.2.9
Unit/SENC Unit
(REP 02-0830)
W090xy ENC alarm The ENC Unit failed. Gather cWhen the ENC alarm is Replacement 2.2.1
(Unit-x, ENC-y) x : Unit ID # given at the same time as Replacing Disk Drive
(RKAJ/RKAJAT=1-14) the HDU alarm or SATA (REP 02-0050)
y : ENC Unit # (0-1) HDU alarm, replace the
Disk Drive before replacing
the ENC Unit.
dWhen this message is
displayed at the time of the
subsystem startup, the
ENC cable may also have a
connection error. Check
eReplace the ENC Unit or Replacement 2.2.9
SENC Unit pointed out in Replacing ENC
the message. Unit/SENC Unit
(REP 02-0830)
W0B0xy ENC recovery failed The ENC Unit was inserted but Gather cThe cause of failure in
(Unit-x, ENC-y) recovery failed. recovery is indicated by
x : Unit ID # another message.
(RKAJ/RKAJAT=1-14) Maintain according to that
y : ENC Unit/SENC Unit # message.
(0-1)
W0C00x UPS alarm A trouble of the UPS was cWhen the UPS is
(UPS-x) detected. connected, take a recovery
x : UPS # (0-1) action referring to the UPS
manual.
W0D0xy CACHE alarm A cache access error occurred. Gather cReplace the Cache Unit. Replacement 2.2.6
(CTL-x, CACHE-y) (unrecoverable) Replacing Cache
x : Control Unit # Unit (REP 02-0540)
x=0 : Control Unit #0 dIf not recovered, replace Replacement 2.2.5
x=1 : Control Unit #1 the above Control Unit. Replacing Control
x=2 : Control Unit #0 and #1 Unit (REP 02-0390)
y : Cache slot #
(RKM/RKS=0-1)
W0E000 LU alarm LU was blocked. Gather cRefer to Troubleshooting Troubleshooting
(LU-x) x : LU # (RKM/RKS=0-2047) 6.1.13 A failure occurred 6.1.13 A failure
(LU blockade). operation : Case 3
(LU blockade) (TRBL
06-0590)

MSG 06-0050-01

MSG 06-0050-01
Collect the error

Message
code
Trace Trace Dump
W0F0xy Path alarm A detachment of the path cCheck whether the power
(Remote-x, Path-y) between the DFs occurred. supply of the remote
x : Remote DF # (0) subsystem as a pair turns
y : Path # on or not.
(RKM/RKS=0-1) Turn on if the power off.
dCheck whether the remote
equipment is in the Ready
status and the path
blockage is recovered or
not.
eIf it has not recovered, refer Troubleshooting 6.3
to Troubleshooting 6.3 Procedure for
Procedure for Recovery Recovery from Path
from Path Blockade when Blockade when the
the TrueCopy remote TrueCopy remote
replication Function Is replication Function Is
1170)

MSG 06-0060-01
Collect the error

Message
code
Trace Trace Dump
W0G0xy Unreadable PIN A unreadable PIN with a failed Gather This recovery method is from
detected drive identified has occurred. steps c to i.
(Unit-x, HDU-y) x : Unit ID # cWhen H20100 Parity Troubleshooting
(RKM/RKS=0) generation LA error is 6.1.1 System down
(RKAJ/RKAJAT=1-14) displayed after this (TRBL 06-0020)
y : Disk Drive # (0-14) message and the ALARM
LED (red) on the Front
Bezel lights on, perform
System down.
d When W48000 Forced Troubleshooting
W0G100 Unreadable PIN A unreadable PIN without a Gather parity correction LU is 6.1.3 The failure
detected failed drive identified has detected is displayed occurred immediately
(Unit-*, HDU-*) occurred. before this message and after being ready
the forced parity correction (Forced parity
is in progress, take correction) (TRBL
recovery actions according 06-0060)
to Troubleshooting 6.1.3
The failure occurred
immediately after being
ready (Forced parity
correction).
eWhen the message cord, Chapter 3. Failure
H20100 Parity generation Messages (MSG 03-
LA error is displayed 0030)
following this message,
take recovery actions
according to it.
fWhen this message is Troubleshooting
displayed during a 6.1.7 The power
restoration of the drive and cannot be turned off :
the code I153xy Data Case 4 (Cache
recovery partial is memory failure)
displayed at the time when (TRBL 06-0490)
the drive restoration is
completed, take an action
following Procedure
Troubleshooting 6.1.7 The
power cannot be turned
off : Case 4 (Cache
memory failure).

MSG 06-0070-01
Collect the error

Message
code
Trace Trace Dump
gWhen this message is Troubleshooting
displayed during a 6.1.8 Data recovery
restoration of the drive and does not terminate
the code I152xy Data normally : Case 1
recovery partial is (Read error) (TRBL
displayed at the time when 06-0510)
the drive restoration is
completed, take an action
following Procedure
Data recovery does not
terminate normally : Case 1
(Read error).
hWhen I6D300 Unreadable Chapter 4. Progress
PIN resisted is displayed Message (MSG 04-
at the same time with this 0330)
message, take recovery
actions according to it.
iWhen a RAID level of the Troubleshooting
RAID group, one of whose 6.1.15 A failure
components is the failed occurred during
Disk Drive, is RAID 0, refer operation : Case 5
to Troubleshooting 6.1.15 (Incomplete writing)
A failure occurred during (TRBL 06-1110).
operation: Case 5
(Incomplete writing).
W0G20x Parity generation LA An LA error occurred during the Gather cRefer to Troubleshooting Troubleshooting
error [DRR] parity generation. (DRR failure) 6.1.12 A failure occurred 6.1.12 A failure
(CTL-x) x : Control Unit # (0-1) during operation : Case 2 occurred during
(LA/LRC error)
(TRBL 06-0570)
W0G300 Host connector alarm A trouble occurred in the Host Gather cWhen the Host Connector Replacement 2.2.8
(Portxy-z) Connector. has come off, reconnect it. Replacing Host
x : Control Unit # (0-1) dReplace the Host Connector (REP 02-
y : Port # (A-D) Connector. 0770)
z : Host Connector # (0-1)
W0G400 PS alarm [RKA] The Power Unit failed. c When a trouble reported by Chapter 6. Warning
(RKA=1-29) FAN alarm has occurred at 0010)
y : Power Unit # (0-1) the same time, take a
W0G500 PS alarm [RKAAT] The Power Unit failed. recovery action against it
(Unit-x, PS-y) x : Unit ID # first.
(RKAAT=1-29) dReplace the Power Unit. Replacement 2.2.4
y : Power Unit # (0-1) Replacing Power
W0G600 PS alarm [RKAJ] The Power Unit failed. Unit (REP 02-0340)
(Unit-x, PS-y) x : Unit ID #
(RKAJ=1-29)
y : Power Unit # (0-1)

MSG 06-0080-01
Collect the error

Message
code
Trace Trace Dump
W0G700 PS alarm [RKAJAT] The Power Unit failed. cWhen a trouble reported by Chapter 6. Warning
(RKAJAT=1-29) FAN alarm has occurred at 0010)
y : Power Unit # (0-1) the same time, take a
recovery action against it
first.
dReplace the Power Unit. Replacement 2.2.4
Replacing Power
Unit (REP 02-0340)
W0GA00 ENC alarm [RKA] The ENC Unit failed. Gather cWhen the ENC alarm is Replacement 2.2.1
(RKA=1-29) the HDU alarm, replace (REP 02-0050)
y : ENC Unit # (0-1) the Disk Drive before
replacing the ENC Unit.
dWhen this message is Installation 1.6
displayed at the time of the Device ID Setting and
subsystem startup, the ENC Cable
ENC cable may also have a Connection (INST
connection error. Check 01-0160)
eReplace the ENC unit Replacement 2.2.9
Unit/SENC Unit
(REP 02-0830)
W0GB00 SENC alarm [RKAAT] The SENC Unit failed. Gather cWhen this message is Installation 1.6
(Unit-x, ENC-y) x : Unit ID # displayed at the time of the Device ID Setting and
(RKAT=1-29) subsystem startup, the ENC Cable
y : SENC Unit # (0-1) ENC cable may also have a Connection (INST
Unit/SENC Unit
(REP 02-0830)
W0GC00 ENC alarm [RKAJ] The ENC Unit failed. Gather cWhen the ENC alarm is Replacement 2.2.1
(RKAJ=1-29) the HDU alarm, replace (REP 02-0050)
y : ENC Unit # (0-1) the Disk Drive before
replacing the ENC Unit.
dWhen this message is Installation 1.6
displayed at the time of the Device ID Setting and
subsystem startup, the ENC Cable
ENC cable may also have a Connection (INST
eReplace the ENC unit Replacement 2.2.9
Unit/SENC Unit
(REP 02-0830)

MSG 06-0090-01
Collect the error

Message
code
Trace Trace Dump
W0GD00 SENC alarm The SENC Unit failed. Gather cWhen this message is Installation 1.6
[RKAJAT] x : Unit ID # displayed at the time of the Device ID Setting and
(Unit-x, ENC-y) (RKAJAT=1-29) subsystem startup, the ENC Cable
y : SENC Unit # (0-1) ENC cable may also have a Connection (INST
Unit/SENC Unit
(REP 02-0830)
W0GG00 HDU alarm [RKA] A blockade of a Disk Drive Gather c Replace the Disk Drive Replacement 2.2.1
(Unit-x, HDU-y) occurred. pointed out in the Replacing Disk Drive
x : Unit ID # message(*1). (REP 02-0050)
(RKA=1-29) When you want to know a Replacement 1.1.3
y : Disk Drive # (0-14) model name of the Disk Procedure for making
W0GH00 HDU alarm [RKAJ] A blockade of a Disk Drive Gather Drive or a revision of the sure of model name
(Unit-x, HDU-y) occurred. drive firmware, refer to and drive firmware of
x : Unit ID # Replacement 1.1.3 Disk Drive (REP 01-
(RKAJ=1-29) Procedure for making sure 0100)
y : Disk Drive # (0-14) of model name and drive
W0GJ00 Spare HDU alarm A blockade of a Spare Disk Gather c Replace the Disk Drive Replacement 2.2.1
[RKA] (Unit-x, HDU-y) Drive occurred. pointed out in the Replacing Disk Drive
x : Unit ID # message(*1). (REP 02-0050)
(RKA=1-29) When you want to know a Replacement 1.1.3
y : Disk Drive # (0-14) model name of the Disk Procedure for making
W0GK00 Spare HDU alarm A blockade of a Spare Disk Gather Drive or a revision of the sure of model name
[RKAJ] Drive occurred. drive firmware, refer to and drive firmware of
(Unit-x, HDU-y) x : Unit ID # Replacement 1.1.3 Disk Drive (REP 01-
(RKAJ=1-29) Procedure for making sure 0100)
y : Disk Drive # (0-14) of model name and drive
W0H000 LU alarm LU blockage occurred. Gather cRefer to Troubleshooting Troubleshooting
(LU blockade). operation : Case 3
(LU blockade) (TRBL
06-0590)
W12000 User data lost The user data were lost since Gather cRefer to Troubleshooting Troubleshooting
(LU-x) the Cache memory was 6.1.3 The failure occurred 6.1.3 The failure
volatilized. (*2) immediately after being occurred immediately
x : LU # ready (Forced parity after being ready
(RKM/RKS=0-2047) correction). (Forced parity
correction) (TRBL
06-0060)
*2 : When LU-0000 is displayed, the LU #0 data or the configuration information on the subsystem is lost.
Check the LU #0 status in the Storage Navigator Modular, and if LU #0 has errors, follow the recovery methods c.
If it is normal, the recovery operation is not needed.

MSG 06-0100-01
Collect the error

Message
code
Trace Trace Dump
W22000 PS OFF failed The plan was not stopped since Gather cRefer to Troubleshooting Troubleshooting
[NO HDU] there was not a Disk Drive to 6.1.6 The power cannot 6.1.6 The power
save the information to be taken be turned off : Case 3 cannot be turned off :
over. (Control Unit failure). Case 3 (Control Unit
failure) (TRBL 06-
0470)
W23000 PS OFF failed The plan was not stopped since Gather cRefer to Troubleshooting Troubleshooting
[CACHE ERR] a cache failure occurred and the 6.1.7 The power cannot 6.1.7 The power
PIN data could not be saved. be turned off : Case 4 cannot be turned off :
(Cache memory failure). Case 4 (Cache
memory failure)
(TRBL 06-0490)
W310xx DMA error DMA failed. Gather cControl Unit of the No. Replacement 2.2.5
(DMA-x) x : DMA # indicated by "Cx" (x: Replacing Control
Control Unit #) in the log Unit (REP 02-0390)
message.
W320xy LA error An LA error (including a LUN Gather cRefer to Troubleshooting Troubleshooting
[errcode:LUN] error) occurred in the Drive Port 6.1.12 A failure occurred 6.1.12 A failure
(D_PT-00, CTL-x, #00. during operation : Case 2 occurred during
TRNS-y) x : Control Unit # (0-1) (LA/LRC error). operation : Case 2
y : Transfer direction (LA/LRC error)
R : Read direction (TRBL 06-0570)
W : Write direction
W321xy LA error An LA error (including a LUN Gather
[errcode:LUN] error) occurred in the Drive Port
(D_PT-01,CTL-x, #01.
TRNS-y) x : Control Unit # (0-1)
y : Transfer direction
R : Read direction
W : Write direction
[errcode:LUN] error) occurred in the Host Port
(H PT-00, CTL-x, #00.
R : Read direction
W : Write direction
[errcode:LUN] error) occurred in the Host Port
(H PT-01, CTL-x, #01.
R : Read direction
W : Write direction

MSG 06-0110-01
Collect the error

Message
code
Trace Trace Dump
W324xy LA error An LA error (including a LUN Gather cRefer to Troubleshooting Troubleshooting
[errcode:LBA] error) occurred in the Drive Port 6.1.12 A failure occurred 6.1.12 A failure
(D_PT-00, CTL-x, #00. during operation : Case 2 occurred during
TRNS-y) x : Control Unit # (0-1) (LA/LRC error). operation : Case 2
y : Transfer direction (LA/LRC error)
R : Read direction (TRBL 06-0570)
W : Write direction
[errcode:LBA] error) occurred in the Drive Port
(D_PT-01, CTL-x, #01.
R : Read direction
W : Write direction
[errcode:LBA] error) occurred in the Host Port
(H PT-00, CTL-x, #00.
R : Read direction
W : Write direction
[errcode:LBA] error) occurred in the Drive Port
(H PT-01, CTL-x, #01.
R : Read direction
W : Write direction
W328xy LA error A LUN error occurred. Gather
[errcode:LUN] (D_PORT #2)
(D_PT-02, CTL-x, x : Control Unit # (0-1)
TRNS-y) y : Transfer direction
R : Read direction
W : Write direction
W329xy LA error A LUN error occurred. Gather
[errcode:LUN] (D_PORT #3)
R : Read direction
W : Write direction
W32Axy LA error A LBA error occurred. (D_PORT Gather
[errcode:LBA] #2)
R : Read direction
W : Write direction

MSG 06-0120-01
Collect the error

Message
code
Trace Trace Dump
W32Bxy LA error A LBA error occurred. (D_PORT Gather cRefer to Troubleshooting Troubleshooting
[errcode:LBA] #3) 6.1.12 A failure occurred 6.1.12 A failure
(D_PT-03, CTL-x, x : Control Unit # (0-1) during operation : Case 2 occurred during
TRNS-y) y : Transfer direction (LA/LRC error). operation : Case 2
R : Read direction (LA/LRC error)
W : Write direction (TRBL 06-0570)
W32Cxy LA error A LUN error occurred. Gather
[errcode:LUN] (H_PORT #2)
(H_PT-02, CTL-x, x : Control Unit # (0-1)
R : Read direction
W : Write direction
W32Dxy LA error A LUN error occurred. Gather
[errcode:LUN] (H_PORT #3)
R : Read direction
W : Write direction
W32Exy LA error A LBA error occurred. (H_PORT Gather
[errcode:LBA] #2)
R : Read direction
W : Write direction
W32Fxy LA error A LBA error occurred. (H_PORT Gather
[errcode:LBA] #3)
R : Read direction
W : Write direction
W330xy LRC error An LRC error (including a LUN Gather
(D_PT-00, CTL-x, error) occurred in the Drive Port
TRNS-y) #00.
R : Read direction
W : Write direction
(D_PT-01, CTL-x, error) occurred in the Drive Port
TRNS-y) #01.
R : Read direction
W : Write direction
W332xy LRC error A LRC error occurred in the Gather
(D_PT-02, CTL-x, Drive Port #02.
R : Read direction
W : Write direction

MSG 06-0130-01
Collect the error

Message
code
Trace Trace Dump
W333xy LRC error A LRC error occurred in the Gather cRefer to Troubleshooting Troubleshooting
(D_PT-03, CTL-x, Drive Port #03. 6.1.12 A failure occurred 6.1.12 A failure
TRNS-y) x : Control Unit # (0-1) during operation : Case 2 occurred during
y : Transfer direction (LA/LRC error). operation : Case 2
(H_PT-02, CTL-x, Host Port #02.
R : Read direction
W : Write direction
(H_PT-03, CTL-x, Host Port #03.
R : Read direction
W : Write direction
W3360x Data transfer check (Data assurance check) Gather
error [SEGPOSERR] An illegal cache writing segment
(CTL-x) position was detected.
W33700 EDC LA error A EDC_LUN error occurred in Gather
[error code : LUN] the Host Port #00.
TRANS-y) y : Transfer direction
R : Read direction
W : Write direction
R : Read direction
W : Write direction
R : Read direction
W : Write direction
W33A00 EDC LA error A EDC_LUN error occurred in Gather
R : Read direction
W : Write direction
W33B00 EDC LA error A EDC_LBA error occurred in Gather
[error code : LBA] the Host Port #00.
R : Read direction
W : Write direction

MSG 06-0140-01

MSG 06-0140-01
Collect the error

Message
code
Trace Trace Dump
W33C00 EDC LA error A EDC_LBA error occurred in Gather cRefer to Troubleshooting Troubleshooting
[error code : LBA] the Host Port #01. 6.1.12 A failure occurred 6.1.12 A failure
(H_PT-01, CTL-x, x : Control Unit # (0-1) during operation : Case 2 occurred during
TRANS-y) y : Transfer direction (LA/LRC error). operation : Case 2
W33D00 EDC LA error A EDC_LBA error occurred in Gather
R : Read direction
W : Write direction
W33E00 EDC LA error A EDC_LBA error occurred in Gather
R : Read direction
W : Write direction
W33F00 EDC LA error A EDC_CRC error occurred in Gather
[error code : CRC] the Host Port #00.
R : Read direction
W : Write direction
(H PT-00, CTL-x, error) occurred in the Host Port
TRNS-y) #00.
R : Read direction
W : Write direction
(H PT-01, CTL-x, error) occurred in the Host Port
TRNS-y) #01.
R : Read direction
W : Write direction
W34200 EDC LA error A EDC_CRC error occurred in Gather
R : Read direction
W : Write direction
W34300 EDC LA error A EDC_CRC error occurred in Gather
R : Read direction
W : Write direction

MSG 06-0150-01
Collect the error

Message
code
Trace Trace Dump
W34400 EDC LA error A EDC_CRC error occurred in Gather cRefer to Troubleshooting Troubleshooting
[error code : CRC] the Host Port #03. 6.1.12 A failure occurred 6.1.12 A failure
(H_PT-03, CTL-x, x : Control Unit # (0-1) during operation : Case 2 occurred during
TRANS-y) y : Transfer direction (LA/LRC error). operation : Case 2
W41000 PIN write error PIN data were not saved in the Gather
Disk Drive since a hardware
error occurred.
W41100 PIN over The number of the PIN Gather
[PNLEVLOV] segments exceeded the
threshold value PIN.
W4200x SNMP invalid There is not SNMP information cInstall the information for
(CTL-x) [Config] but SNMP information has not SNMP.
been introduced. The SNMP
function has not started up.
W43000 SNMP invalid When SNMP was initialized, Gather cControl Unit of the No. Replacement 2.2.5
[RAM Device MAKE making of a RAM device failed. indicated by Cx (x: Control Replacing Control
ERR] Unit #) in the log message. Unit (REP 02-0390)
W43100 SNMP invalid When SNMP was initialized, Gather
[RAM Device INIT initialization of a RAM device
ERR] failed.
W43200 SNMP invalid When SNMP was initialized, Gather
[RAM Device generation of a RAM device
CREATE ERR] failed.
W43300 SNMP invalid When SNMP was initialized, Gather cControl Unit of the No. Replacement 2.2.5
[RAM Device WRITE writing in a RAM device failed. indicated by Cx (x: Control Replacing Control
ERR] Unit #) in the log message. Unit (REP 02-0390)
W43400 SNMP failure An application error of SNMP Gather
[APL ERR] was detected.

MSG 06-0160-01
Collect the error

Message
code
Trace Trace Dump
W440xy Permanent LU Residence OFF warning Gather cy=0 : Return the
warning occurred in the LU residence configuration of
(CTL-x, ERR-y) mode. Cache memory. (Add
x : Default Control Unit # cache memory.)
(0-1) y=1 : Perform maintenance
y : Factor code described in message
0 : Too large LU code W0D0x0
1 : Cache access error CACHE alarm.
2 : Regression of Control To resume the LU cache
Unit resident function after
3 : Abnormal battery recovering from a cache
voltage failure, turn off and then on
4 : Abnormal battery an array unit.
charging circuit y=2 : Perform maintenance
5 : Larger than PIN described in message
threshold value code W0100x CTL
alarm.
y=3 : Perform maintenance
described in message
codeW0300x Battery
alarm, W0310x
Battery removed,.
W0320x Battery SW
OFF, and W0330x
Battery Thermal
alarm.
described in message
codeW0340x Battery
back up circuit alarm.
described in
message code
W41100 PIN over.
W4500x Online micro-update The microprogram of a Control
executing (CTL-x) Unit has not been replaced with
the power turned on.
This message is indicated to
warn that microprogram of a
Control Unit is being replaced
with the power turned on.
If replacement of the
microprogram is finished, this
warning disappears.

MSG 06-0170-01
Collect the error

Message
code
Trace Trace Dump
W4600x Online micro-update The Control Unit was blocked
started (CTL-x) falsely to replace the
microprogram with the power
turned on, or the Control Unit of
another system was blocked
falsely.
W4700x Serial number error WWW could not be set since the cCheck if the serial number System Parameter
[WWN] serial number of the subsystem of the subsystem is set 4.2 Setting the
(CTL-x) was set incorrectly. correctly. subsystem
x : Control Unit # (0-1) configuration
information (SYSPR
04-0020)
W48000 Forced parity An LU, which required the cRefer to Troubleshooting Troubleshooting
correction LU is forced parity correction, was 6.1.3 The failure occurred 6.1.3 The failure
detected detected. immediately after being occurred immediately
ready (Forced parity after being ready
correction). (Forced parity
correction) (TRBL
06-0060)
W48100 Uncorrectable forced An LU, the forced restoration for cCheck the LU information
parity correction LU is which by means of parity could using the Storage
detected not be continued, was detected. Navigator Modular.
dHave the LU, the forced
restoration for which by
means of parity cannot be
continued, skip the
restoration by issuing an
instruction to skip the
restoration using the
The warning is removed
after all the LUs, the forced
restoration for which by
means of parity cannot be
continued, receive an
instruction to skip the
restoration.

MSG 06-0180-01
Collect the error

Message
code
Trace Trace Dump
W49000 Forced parity Drive detachment occurred in a cReplace the detached Disk Troubleshooting
correction LU is RAID group whose RAID level Drive pointed out in the 6.1.3 The failure
detected by HDU was 6 and an LU in a state in message, HDU alarm occurred immediately
alarm which the status of the forced referring to Troubleshooting after being ready
parity correction in the hot 6.1.3 The failure occurred (Forced parity
condition was Unrestored 1 was immediately after being correction) (TRBL
detected. ready (Forced parity 06-0060)
correction). Replacement 2.2.1
(REP 02-0050)
dSelect either to execute the Chapter 4. Progress
forced parity correction or Message (MSG 04-
to skip it after either one of 0000) and (MSG 04-
the messages, I007xy 0010)
HDU recovered and
I009xy Spare HDU
recovered, is displayed.
W49100 PIN is over directory The number of pinned sub- Gather cRefer to Troubleshooting Troubleshooting
threshold [write segments in the directory (that 6.1.11 A failure occurred 6.1.11 A failure
through] (DIR-x) is, unit of cache domain during operation : Case 1 occurred during
management) exceeded the (PIN over). operation : Case 1
threshold value of performing (PIN over) (TRBL 06-
the write through operation. 0550)
W49200 PIN is over directory The number of PIN sub- Gather
threshold [write will segments in the directory (unit
not run] (DIR-x) of the Cache area management)
exceeded the threshold for the
check condition to respond to
the write command.
W49300 PIN is over partition The number of pinned sub- Gather
threshold [write segments in the partition
through] exceeded the threshold value of
(DIR-x, PTT-y) performing the write through
operation.
y : Partition #
(RKS/RKM=0-15)
W49400 PIN is over partition The number of PIN sub- Gather
threshold [write will segments in the partition
not run] exceeded the threshold for the
(DIR-x, PTT-y) check condition to respond to
the write command.
y : Partition #
(RKS/RKM=0-15)

MSG 06-0190-01
Collect the error

Message
code
Trace Trace Dump
W49500 PIN is over RAID The number of pinned sub- Gather cRefer to Troubleshooting Troubleshooting
group threshold [write segments in the RAID group 6.1.11 A failure occurred 6.1.11 A failure
through] exceeded the threshold value of during operation : Case 1 occurred during
(DIR-x, RG-y) performing the write through (PIN over). operation : Case 1
operation. (PIN over) (TRBL 06-
x : Directory # (0 or 1) 0550)
y : RAID group #
(RKM/RKS=0-44)
W49600 PIN is over RAID The number of PIN sub- Gather
group threshold [write segments in the RAID group
will not run] exceeded the threshold to
(DIR-x, RG-y) execute the write command.
y : RAID group #
(RKM/RKS=0-14)
W49700 DM-LU write disable Write to DM-LU disabled was Gather c Replace the detached Disk Troubleshooting
(LU-x) detected. Drive pointed out in the 6.1.3 The failure
x : LU # message, HDU alarm occurred immediately
(RKM/RKS=0-2047) referring to Troubleshooting after being ready
W49800 All DM-LU write Write to all DM-LUs disabled Gather 6.1.3 The failure occurred (Forced parity
disabled was detected, so that the immediately after being correction) (TRBL
planned shutdown could not be ready (Forced parity 06-0060)
executed. correction). Replacement 2.2.1
(REP 02-0050)
dFormat DM-LU.

MSG 06-0200-01

MSG 06-0210-01
Chapter 7. Web Error Messages

7.1 Web error messages (Uploading Function)
Message
Message text Description Recovery methods Reference page
code
- Abnormal End The number of areas is other than cMake sure of the system to be Microprogram
AT xxxx ******** either of one and two. installed and execute the installation Chapter 1.
Upload System Error again. (The START600. DAT is Installation of
illegal.) Microprogram
- Abnormal End The block ID is illegal. cMake sure of the system to be (MICRO 01-0000)
Bad Block ID installed and execute the installation
again.
- Abnormal End The LBA, in which the installation is cMake sure of the system to be
Bad LBA In START600.DAT to be done, is abnormal because of installed and execute the installation
0x******** xxxx an illegal contents of the again. (The START700. DAT is
"START700. DAT." illegal.)
- Abnormal End Config clear restart failed due to the cConfig clear restart cannot be done.
Config Clear Restart Error LU access restriction. Select Take Over from Configuration
by LU Access Restriction Clear Mode and restart.
- Abnormal End Though the downgrade of the cCancel the downgrade check and
Down Grade Check NG microprogram was attempted, the reboot the subsystem.
updating installation terminated dExecute the updating installation Microprogram
abnormally because of the illegal again. Chapter 1.
procedure. Installation of
Microprogram
(MICRO 01-0000)
- Abnormal End The drive block size is other than cReplace a Disk Drive whose unit ID Replacement 2.2.1
Drive Block Size Error 520 bytes. number is 0 and Disk Drive number is Replacing Disk Drive
AT CDEV ** **. (REP 02-0050)

MSG 07-0000-01
Message
code
- Abnormal End Empty System The updating installation cannot be cWhen it is evident that the old Microprogram
Retry Full Install done because the old microprogram microprogram does not exist in the Chapter 1.
does not exist in the system Disk system Disk Drive, install the Installation of
Drive. microprogram newly. Microprogram
dExecute the updating installation (MICRO 01-0000)
again after making sure that the
system copy has been completed
through the Information Message of
the Web.
y I140xy System copy started is
not displayed.
y I140xy System copy started and
I141xy System copy completed
are displayed consecutively.
When the system copy is being

made, turn off the main switch and
then turn it on again later than 20
seconds.
In the following case, the system
copy is being made.
y While I140xy System copy
started is displayed, I141xy
System copy completed is not
displayed successively.
Execute the updating installation
again after making sure that the
READY LED (green) comes on and
then the system copy is completed.
- Abnormal End File open error c Make sure of the system to be Microprogram
File Open Error installed and execute the installation Chapter 1.
- Abnormal End File read error again. Installation of
File Read Error Microprogram
(MICRO 01-0000)
- Abnormal End File elimination error cExecute the utility program load after
File Remove Failed restarting the subsystem.

MSG 07-0010-01
Message
code
- Abnormal End All the drives became abnormal after cMake sure of the system to be Microprogram
Install Failed the installation had been completed. installed and the system drive, and Chapter 1.
then execute the installation again. Installation of
- Abnormal End Initial Setup failed due to the LU cInitial Setup cannot be done. Microprogram
Initial Setup Error access restriction. Execute update installation for (MICRO 01-0000)
by LU Access Restriction updating the microprogram.
- Abnormal End Initial Setup was done when the cExecute installation after changing
Initial Setup of Microprogram installation check on the the installation classification to
Failed microprogram for DF700 was Update.
Disable.
- Abnormal End A loop failure occurred. cExecute the installation again after
Loop Error making sure of the ENC and the loop.
- Abnormal End No normal drive is available. cReplace the system drive. Replacement 2.2.1
No Drives Available Replacing Disk Drive
(REP 02-0050)
- Abnormal End The program size is larger than the cMake sure of the system to be Microprogram
PGMS **** allowable limit. installed and execute the installation Chapter 1.
Too Large again. Installation of
Microprogram
(MICRO 01-0000)
- Abnormal End Utility program decompression error cSpecify a normal utility program and
Program extract error re-execute the utility program load.
- Abnormal End Sum check error of the utility
Program SUM check error program that has been
decompressed
- Abnormal End The system area capacity is larger cReplace a Disk Drive whose unit ID Replacement 2.2.1
Unknown Drive than the drive capacity. number is 0 and Disk Drive number is Replacing Disk Drive
AT CDEV ** **. (REP 02-0050)
- Abnormal End Read file sum check error c Make sure of the system to be Microprogram
Upload File SUM Check Error installed and execute the installation Chapter 1.
- Abnormal End The "PRGMAG. DAT" file does not again. Installation of
Upload System Error exist. Microprogram
The "START600. DAT" file does not (MICRO 01-0000)
exist.
The "END DAT" file does not exist.
The file required does not exist.
- Cannot Execute Upload Java Applet cannot be activated. cCheck if the Java Plug-in is installed.
dCheck if it is validated through the
setting of Java Plug-in on the
operator panel.
e(IE) Check if the setting of ActiveX is
validated.
fCheck if the (NN) Java plug-in setting
is valid.
- Complete The installation was completed
MICRO REV:07**/* normally.
- Complete The utility program load was
Utility Program REV: completed.

MSG 07-0020-01
Message
code
- Drive firmware download start The drive firmware (microprogram)
downloading of the firmware was
started.
- Drive mode parameter A drive parameter change and
change & format start formatting were started.
- Drive mode parameter A drive parameter change was
change start started.
- ENC microprogram download A microprogram downloading for
start replacing the microprogram was
started.
- File open error [file name] File open error cMake sure of the system to be
installed.
- File read data err [file name] File read data error
- File read err [file name] File read error
- File size mismatch [file name] File size inconsistency cMake sure of the system to be
installed.
- File size over [file name] File size error
- Install revision Display of a revision of the installed

program
- Initial Setup Make sure that the initial setting up
(Config and System has been done.
Parameter Clear)
Install Microprogram
Rev.07**/*
- Microprogram download Microprogram replacement was
ENC# started. [ENC number]
- Micro Update Make sure that the update
Install Microprogram installation of the microprogram has
Rev.07**/* been done.
- Old System Exists A system had already been installed
when an installation of a new system
was attempted.
- Partially Completed The installation was terminated cRefer to the procedure for finding a
MICRO REV:07**/* abnormally. cause of a Disk Drive failure to be
used when a message, "Install
partially complete," is output.
- System parameter update All the drives do not accept a read cReset the system parameters. System Parameter
failed instruction. (SYSPR 00-0000)
dIf the trouble recurs, replace the Replacement 2.2.1
system drive. Replacing Disk Drive
(REP 02-0050)
- Target HDU not found The target HDU is not found. cMake sure of the drive to be
rewritten.

MSG 07-0030-01
Message
code
1003 Cannot Upload File. Write error of the RAM disk. cPerform the operation over again
from the software reset.
1004 System is Other Boot Up Inconsistency of statuses of Applet cReload the page.
Mode. and the subsystem (Example: The
subsystem has started an dIf the correct page is not displayed,
installation of drive firmware, perform the operation over again from
whereas Applet is loading the utility.) the software reset.
1005 Booting. Please Retry Again. The subsystem is being started up. cOperate over again after waiting for a
while.
1006 System is Executing Other The subsystem is already executing cMake sure of the information
Event. the process. message or reload the page.
1007 System is Executing Main The utility is being processed. cReload the page.
Process. The drive firmware is being
replaced.
1008 System is Down. The subsystem cannot execute the cPerform the operation over again
process (it has gone down). from the software reset.
1009 Please. Retry Again. The subsystem stands ready to start cInstall the microprogram over again. Microprogram
the microprogram installation. Chapter 1.
Installation of
Microprogram
(MICRO 01-0000)
1010 Please. Retry Again on Other Have the controller in another cHave the controller in another system
CTL. system re-execute the process. re-execute the process.
1011 Please Confirm Information Make sure of the information cMake sure of the information
Message. message. message.
1200 The Java Plug-in version in Java Applet was activated with Java cActivate Java Applet again after
use is not supported. Confirm Plug-in of a version not supported. making sure of the version of Java
the Java Plug-in version. Plug-in currently used.
1202 A path to the Microprogram The path to the microprogram to be cSpecify the path to the microprogram.
isn't being input. Specify a installed is not specified.
path.
1204 A specified file doesn't exist. The specified file does not exist. cMake sure that the path to the
Confirm elements of directory of the microprogram to be
designation. installed is specified correctly.
1206 A specified path is not a A file other than the normal file was cCheck if the specification is correct.
normal file. Specify a file. specified when the normal file must
be specified.
1207 A specified path is not a A file other than the directory file
directory. Specify a directory. was specified when the directory file
must be specified.
1210 A specified file is not possible The specified file cannot be read. cMake sure of a status of the specified
to read. Confirm the condition file.
of the file.
1212 Access to the specified file Access to the specified file was cSet up the service PC again.
was rejected. Confirm the rejected according to the security
setup of the security policy. policy.
1213 Access to the specified Access to the specified directory
directory was rejected. was rejected according to the
Confirm the setup of the security policy.
security policy.

MSG 07-0040-01
Message
code
1214 An error occurred during the An error occurred during an I/O cMake sure of a status of the specified
file I/O. Confirm the status of operation to/from the specified file. file.
the specified file.
1215 A runtime permission wrong A request for access to the cSet up the service PC again.
matter occurred. Confirm the java.lang.RuntimePermission object
setup of the security policy. was rejected.
1216 Access to the property A request for access to the
information was rejected. java.util.OropertyPermission object
Confirm the setup of the was rejected.
security policy.
1217 A security wrong matter A security trouble occurred.
occurred. Confirm the setup
of the security policy.
1218 An invalid response was Communication with the subsystem cMake sure of the subsystem status
received from the subsystem. failed. and the LAN environment, and then
Confirm the subsystem status retry.
and the LAN environment,
and then try again.
1219 An error occurred during the An error occurred during the cMake sure of the subsystem status
communication with the communication with the subsystem. and the LAN environment, press the
subsystem. Confirm the Software Reset button, and retry.
subsystem status and the
LAN environment.
1220 A path to the Utility Program The path to the utility program to be cSpecify the path to the utility program.
isn't being input. Specify a installed is not specified.
path.
1221 A path to the Utility The path to the parameter file to be cSpecify the path to the utility
Parameter Files isn't being installed is not specified. parameter file.
input. Specify a path.
1222 A path to the Drive Firmware The path to the drive firmware cSpecify the path to the drive firmware
Program isn't being input. program to be installed is not program.
Specify a path. specified.
1223 A HTTPClient library isn't The HITTPClient library is not found. cActivate the browser again after Microprogram
found. Confirm the execution setting up the service PC, and then Chapter 1.
environment. re-execute the microprogram Installation of
installation. Microprogram
(MICRO 01-0000)
1224 A path to the ENC The path to the ENC microprogram cSpecify the path to the ENC
Microprogram isnt being to be installed is not specified. microprogram.
input. Specify a path.
2000 File upload was cancelled. The installation of the file was cRe-execute the installation after
interrupted (artificially). activating the browser again.
2001 Microprogram installation was The installation of the microprogram cRe-execute the microprogram
cancelled. was interrupted (artificially). installation after activating the
browser again.

MSG 07-0050-01
7.2 Web error messages (Simple Trace)
Message
code
- Executing [Simple Trace] The simple trace is already being cPerform maintenance after making
executed. sure of the subsystem status.
- Not Ready When the result of a check done at cRetry after making sure of the
the time of the simple trace subsystem status.
execution was illegal
- Simple trace failed The simple trace could not be cMake sure of the subsystem status.
executed because the subsystem
status was abnormal.
- Simple trace interrupt The simple trace was interrupted cPerform maintenance after making
(because the automatic dump sure of the subsystem status.
operation was done).

MSG 07-0060-01
7.3 Web error messages (Web Control Management)
Message
code
- Booting. Please Retry Again. A boot is in progress. cRetry after making sure of the
subsystem status.
- CTL Alarm. CTL detachment cReplacing the Control Unit. Replacement 2.2.1
(REP 02-0050)
- Executing [Simple Trace] The simple trace is being executed. cRetry after making sure of the
subsystem status.
- "Invalid machine status." Illegal status cRestart the subsystem.
- Invalid Parameter. When the restriction placed on cReset the parameter.

inputting is not followed.
- Not Ready When the drive separating function cRetry after making sure of the
exclusive check and the trace subsystem status.
collection check are abnormal.
- Subsystem is Executing The process is being executed in the cRetry after making sure of the
Other Event. [OWN] self system. subsystem status.
- "Web Task" is executing The Web task is executing another cRetry after making sure of the
other request. request. subsystem status.
- Web Task Booting.. The Web task is being booted. cRetry after making sure of the
subsystem status.
- Web Task Down! The Web task cannot be executed. cRestart the subsystem.
1003 Cannot Upload File. Write error of the RAM disk cPerform the operation over again
from the software reset.
1004 System is Other Boot Up Inconsistency of statuses of Applet c Reload the page.
Mode. and the subsystem (Example: The
subsystem has started an dIf the correct page is not displayed,
installation of drive firmware, perform the operation over again from
whereas Applet is loading the utility.) the software reset.
1005 Booting. Please Retry Again. The subsystem is being started up. cOperate over again after waiting for a
while.
1006 System is Executing Other The subsystem is already executing cMake sure of the information
Event. the process. message or reload the page.
1007 System is Executing Main The utility is being processed. cReload the page.
Process. The drive firmware is being
replaced.
1008 System is Down. The subsystem cannot execute the cPerform the operation over again
process (it has gone down). from the software reset.
1009 Please. Retry Again. The subsystem stands ready to start cInstall the microprogram over again.
the microprogram installation.
1010 Please. Retry Again on Other Have the CTL in another system re- cHave the controller in another system
CTL. execute the process. re-execute the process.
1011 Please Confirm Information Make sure of the information cMake sure of the information
Message. message. message.

MSG 07-0070-01
Chapter 8. Storage Navigator Modular Error Messages

Table 8.1 Storage Navigator Modular error messages
Message code Message text/Recovery methods
DMEA000001 Busy status was reported from the subsystem. Please retry after waiting for a while.
DMEA000002 The Queue Full status was reported from the subsystem. Please retry after waiting for a while.
DMEA000003 LU0 is reserved by another host. Please retry after the reservation is canceled.
DMEA000004 An error was detected in the data received from the subsystem. Confirm the subsystem status and the LAN environment,
and then try again.
DMEA000005 An error occurred while communicating with the subsystem. Confirm the subsystem status and the LAN environment, and
then try again.
DMEA000006 Failed to connect with the subsystem. Confirm the subsystem status and the LAN environment, and then try again.
DMEA000007 An invalid response was received from the subsystem. Confirm the subsystem status and the LAN environment, and then try
again.
DMEA000008 An unexpected error was reported from the subsystem. Please retry after waiting for a while.
DMEA00000A The CHECK CONDITION status was reported from the subsystem, but the details could not be acquired. Please retry after
DMEA00000B Failed to transfer data. Confirm the subsystem status and the LAN environment, and then try again.
DMEA00000C Failed to issue the SCSI command. Confirm the subsystem status and the LAN environment, and then try again.
DMEA00000D Insufficient memory. Terminate other programs and then try again.
DMEA00000E An internal program error occurred. Wait for a while and then try again. If the problem cannot be solved, contact the
maintenance personnel.
DMEA000201 The specified user ID or password is incorrect.
DMEA001000 The information file for the subsystem cannot be opened. Confirm the execution environment.
DMEA001001 The information file for the subsystem is invalid. Confirm the execution environment.
DMEA001002 The specified subsystem name is already registered. Specify another name.
DMEA001003 The specified subsystem name is not registered.
DMEA001004 The registered information does not match the status of the subsystem. Correct the information and then try again.
DMEA001005 The number of registered subsystems has reached the maximum. Delete unnecessary information and then try again.
DMEA001006 Invalid parameter.
DMEA001007 The specified controller is incorrect.
DMEA001008 Failed to open the specified file. Confirm the file name and then try again.
DMEA001009 The contents of the file are invalid. Confirm the file and then try again.
DMEA00100A Failed to connect with the server. Confirm the registered information and the LAN environment, and then try again.
DMEA00100B The password is not specified.
DMEA00100C The password is corrupted. Delete the password file and then try again.
DMEA00100D The specified logical unit is not defined. Specify a defined logical unit.
DMEA00100E Formatting failed. Confirm the subsystem status and the LAN environment, and then try again.
DMEA00100F The file for e-mail setting contains an error.
DMEA001010 The e-mail information is not set up.
DMEA001011 The parameter for e-mail setting is invalid.
DMEA001012 An error was detected while connecting to the mail server. Confirm the mail server and then try again.
DMEA001013 An internal program error occurred. Wait for a while and then try again. If the problem cannot be solved, contact the
maintenance personnel.
DMEA001014 The connection type is invalid.
DMEA001015 The microprogram revision is not supported. Confirm the subsystem status.
DMEA001016 Failed to start the specified application program. Confirm the path to the specified application and the operational
environment.
DMEA001017 An error occurred during the file I/O. Please check the permission and available capacity.

MSG 08-0000-01

DMEA001018 The specified directory path is invalid. Please specify a right directory path.
DMEA001019 The process cannot be performed because the microprogram on the subsystem does not support the function.
DMEA001020 Could not finish replacing the micro program. Please see if there are any alarms or warnings in the subsystem.
DMEA001021 The number of groups reached the maximum. Specify an already registered group or delete an unnecessary group and try
again.
DMEA001022 Hardware error occurred. Confirm the subsystem.
DMEA001023 The process cannot be performed because the current subsystem does not support the function.
DMEA001024 Environment variable: STONAVM_HOME is not defined. Specify STONAVM_HOME.
DMEA001025 The controller in charge of the LU is not registered. Register the controller and then try again.
DMEA001026 The specified information does not match the configuration of the subsystem. Confirm the configuration information.
DMEA001027 The JRE ( Java Runtime Environment ) version in use is not supported. Confirm the JRE version.
DMEA001028 Failed to restart the subsystem.
DMEA001029 Environment variable: STONAVM_HOME does not match. Confirm STONAVM_HOME.
DMEA00102A The JRE ( Java Runtime Environment ) version in use is not supported. Confirm the JRE version.
DMEA00102B The process cannot be performed because the current controller in charge of the specified LU is different. Retry from the
current controller for the LU.
DMEA001030 The parameter for System Startup Attribute or the item name is invalid.
DMEA001031 The parameter for Spare Disk or the item name is invalid.
DMEA001032 The parameter for Host Connection Mode or the item name is invalid.
DMEA001033 The parameter for Serial Number or the item name is invalid.
DMEA001034 The parameter for Drive Capacity or the item name is invalid.
DMEA001035 The parameter for Option 1 or the item name is invalid.
DMEA001036 The parameter for Option 2 or the item name is invalid.
DMEA001037 The parameter for Data Striping Size or the item name is invalid.
DMEA001038 The parameter for Buzzer or the item name is invalid.
DMEA001039 The parameter for LU Size Report to the Host or the item name is invalid.
DMEA00103A The parameter for SCSI Reset/LIP Mode for all Ports or the item name is invalid.
DMEA00103B The parameter for Operation if the Processor failures Occurs or the item name is invalid.
DMEA00103C The parameter for INQUIRY Information or the item name is invalid.
DMEA00103D The parameter for Cache Mode or the item name is invalid.
DMEA00103E The parameter for Target ID or the item name is invalid.
DMEA00103F The parameter for Port Type or the item name is invalid.
DMEA001040 The parameter for ROM Pseudo-response command processing or the item name is invalid.
DMEA001041 The parameter for Save Data Pointer response or the item name is invalid.
DMEA001042 The parameter for Controller Identifier or the item name is invalid.
DMEA001043 The parameter for RS232C Error Information Outflow Mode or the item name is invalid.
DMEA001044 The parameter for Write & Verify Execution Mode or the item name is invalid.
DMEA001045 The parameter for LAN CONST or the item name is invalid.
DMEA001046 The parameter for SYNC CONTROL or the item name is invalid.
DMEA001047 There is no file header.
DMEA001048 The present drive configuration for the subsystem cannot support the drive configuration information of the specified file.
DMEA001049 The RAID configuration data is invalid.
DMEA00104A The LU configuration data is invalid.
DMEA00104B The drive configuration data is invalid.
DMEA00104C The parameter for FD Back UP or the item name is invalid.
DMEA00104D The password length is invalid. Use 12 or fewer characters.
DMEA00104E The process failed because the function is disabled.
DMEA00104F Failed to obtain the controller failure dump information. Retry after 10 minutes.
DMEA001050 The parameter for Web Title or the item name is invalid.
DMEA001051 The parameter for Delay Planned Shutdown or the item name is invalid.

MSG 08-0010-01

MSG 08-0010-01

DMEA001052 The additional information file cannot be opened. Confirm the execution environment.
DMEA001053 The additional information file is invalid. Confirm the execution environment.
DMEA001054 The mail additional information length is invalid.
DMEA001055 The number of registered mail additional information reached the maximum. Delete unnecessary information and then try
again.
DMEA001056 An e-mail information cannot be saved. Please check the permission and available capacity of the install directory.
DMEA001070 This program is not installed correctly.
DMEA001071 The function cannot be executed because the LU has already been reserved.
DMEA001072 The specified path name is over 250 characters.
DMEA001073 Failed to create a log directory. Confirm the execution environment.
DMEA001074 The specified path name is incorrect.
DMEA001075 The specified path does not exist, or no effective files exist under the specified path.
DMEA001076 The micro program in the specified path does not exist. Please confirm whether the micro program is stored in the path or
the specified path is right.
DMEA001077 Failed to create a micro file directory. Confirm the execution environment.
DMEA001078 The specified key was not found. Confirm the file and then try again.
DMEA001079 Cannot use this function for the specified device.
DMEA00107A The micro program replacement of the specified controller cannot be performed. Please replace the micro program of the
other controller first.
DMEA00107B The micro program cannot be read. Please check the permission and available capacity of the install directory.
DMEA00107C The micro program is not read.
DMEA001080 Cannot set the LU mapping in case of mapping mode is off.
DMEA001081 Failed to get drive information.
DMEA001082 The parameter for Additional Battery Unit Mode or the item name is invalid.
DMEA001083 The parameter for PortOption or the item name is invalid.
DMEA001084 The parameter for HostGroupInformation or the item name is invalid.
DMEA001085 The parameter for HostGroupOption or the item name is invalid.
DMEA001086 The parameter for LuMapping or the item name is invalid.
DMEA001087 The parameter for FibreSecurityInformation or the item name is invalid.
DMEA001088 The parameter for Common Information or the item name is invalid.
DMEA001089 Failed to set up a Mapping Mode. Confirm the setting file and then try again.
DMEA001090 The CTL Header is invalid.
DMEA001091 The PORT Header is invalid.
DMEA001092 Illegal option set.
DMEA001093 The function cannot be used because it is not installed, locked, or disabled.
DMEA001094 The specified host group is already defined. Confirm the name or number, and specify a new host group.
DMEA001095 The specified host group is not defined. Confirm the name or number, and specify a defined host group.
DMEA001096 The host group security on the specified port is set on disable. Set host group security to enable and then try again.
DMEA001097 The function cannot be executed because host group 0 is specified. Specify other than host group 0 and try again.
DMEA001098 The specified host group name or WWN name is invalid. Confirm the name and try again.
DMEA001099 The specified host group number is invalid. Confirm the number and try again.
DMEA001100 The specified node name is invalid. Confirm the name and try again.
DMEA001101 The specified port name is invalid. Confirm the name and try again.
DMEA001102 The parameter for LUN Manager Information or the item name is invalid.
DMEA001103 The same host group name exists in a port. Confirm the setting file and then try again.
DMEA001104 The same WWN name exists in a port. Confirm the setting file and then try again.
DMEA001105 The same port name exists in a port. Confirm the setting file and then try again.
DMEA001106 The same host group number exists in a port. Confirm the setting file and then try again.
DMEA001107 The information of the host group number 0 is not in a setting file. Confirm the information on the host group number 0 for
every port and then try again.

MSG 08-0020-01

DMEA001108 The specified Web Title is invalid. Confirm the Web Title and try again.
DMEA001109 In the installed micro program revision, a setup of the Read Frame Min 128 Byte Mode cannot be performed. Please update
to the micro program which can set up the Read Frame Min 128 Byte Mode.
DMEA00110A The process cannot be performed because the micro program on the subsystem does not support the function.
DMEA00110B There is no parameter to change the data pool information.
DMEA00110C The specified RAID groups and logical units cannot be created because the drive type is different.
DMEA00110D The parameter for Options or the item name is invalid.
DMEA00112A The hardware configuration of the subsystem differs from the configuration in the input file. Confirm the subsystem status
and try again.
DMEA00112B The specified port is not available because it is physically unequipped. Confirm the port status and try again.
DMEA00112C In the installed micro program revision, a setup of the HostSystemConfiguration cannot be performed. Please update to the
micro program which can set up the HostSystemConfiguration.
DMEA00112D The parameter for HostSystemConfiguration or the item name is invalid.
DMEA00112E The process cannot be performed because the attribute is not Read/Write. Please change the attribute to Read/Write and
then try again.
DMEA00112F The specified LU is not set retention term. Confirm the LU status.
DMEA001130 The specified RAID group is already defined. Specify a new RAID group.
DMEA001131 The specified RAID group is not defined. Specify a defined RAID group.
DMEA001132 Failed to create a file. Confirm the execution environment.
DMEA001133 The file cannot be outputted. Because the performance statistics acquisition failed.
DMEA001134 The retention term cannot be shortened. Specify the retention term is equal to or more than current value and try again.
DMEA001135 The ENC micro program download and replacement cannot be performed in the single-controller system.
DMEA001136 The directory for storing the ENC micro program cannot be created. Please check the permission of the install directory.
DMEA001137 The ENC micro program cannot be read. Please check the permission and available capacity of the install directory.
DMEA001138 The ENC micro program is not read.
DMEA001139 The ENC micro program of the specified subsystem is not read.
DMEA001140 The ENC micro program in the specified path does not exist. Please confirm whether the ENC micro program is stored in the
path or the specified path is right.
DMEA001141 The ENC micro program cannot be read. Please confirm the file and then try again.
DMEA001142 The contents of the ENC micro program are invalid. Please confirm the file and then try again.
DMEA001143 Incorrect character in the group name.
DMEA001144 Incorrect character in the array unit name.
DMEA001145 The character length of the array unit name or group name is incorrect.
DMEA001146 The specified path name of the directory for storing the management file is over 250 characters, or there is not sufficient
memory. Please specify the pass name of 250 or less characters, or terminate other programs and then try again.
DMEA001147 The directory for storing the management file cannot be created. Please check the permission and available capacity of the
directory.
DMEA001148 The specified path name for storing the management file is over 250 characters. Please specify the pass name of 250 or
less characters and then try again.
DMEA001149 Failed to write the management file. Please check the permission and available capacity of the directory.
DMEA00114A Failed to open the management file. Confirm the file name and then try again.
DMEA00114B The contents of the management file are invalid. Confirm the file and then try again.
DMEA00114C The specified path name for the file is over 250 characters. Please specify the pass name of 250 or less characters and then
try again.
DMEA00114D Failed to write the file. Please check the permission and available capacity of the directory.
DMEA00114E Failed to open the file. Confirm the file name and then try again.
DMEA001150 The specified time of output CSV file is incorrect.
DMEA001151 The specified path name for storing the CSV file is over 250 characters. Please specify the pass name of 250 or less
characters and then try again.
DMEA001152 Failed to write the CSV file. Please check the permission and available capacity of the directory.

MSG 08-0030-01

DMEA001153 Failed to open the CSV file. Confirm the file name and then try again.
DMEA001154 The specified path name of the directory for storing the CSV file is over 250 characters, or there is not sufficient memory.
Please specify the pass name of 250 or less characters, or terminate other programs and then try again.
DMEA001155 The specified path name for the management file is over 250 characters. Please specify the pass name of 250 or less
characters and then try again.
DMEA001156 The specified path name of the deletion file is over 250 characters. Please specify the pass name of 250 or less characters
and then try again.
DMEA001157 The monitoring data cannot be read because the data version is new. Confirm the version of this program and then try again.
DMEA001158 The specified number of output CSV file is incorrect.
DMEA001159 The process cannot be performed because the mapping guard LU exists.
DMEA00115A Failed to open the management file. Confirm the file name and then try again.
DMEA00115B The contents of the management file are invalid. Confirm the file and then try again.
DMEA00115C Failed to connection. Confirm the connection and then try again.
DMEA00115D A response without subsystem was received. Confirm the connection and then try again.
DMEA00115E The process cannot be performed because there is not free area in the specified RAID group.
DMEA001160 The logical unit cannot be defined in the specified area.
DMEA001161 The process cannot be performed because the logical unit is already defined in the first area of the specified RAID group.
DMEA001162 The process cannot be performed because there is not free area in the specified area.
DMEA001163 The value received from the subsystem is invalid.
DMEA001164 The specified IP address is incorrect. Please specify a right IP address.
DMEA001165 The specified subnet mask is incorrect. Please specify a right subnet mask.
DMEA001166 The specified default gateway address is incorrect. Please specify a right default gateway address.
DMEA001167 The information can not be set because the Environment Setting File is over 4096 Bytes. Please confirm the specified file.
DMEA001168 The information can not be set because the Array Unit Name Setting File is over 255 Bytes. Please confirm the specified file.
DMEA001169 The process cannot be performed because the term of the temporary key or emergency key is expired.
DMEA001170 The character length of the serial number is incorrect.

MSG 08-0040-01

DMEC002000 Cannot write the directory specified STONAVM_HOME.
DMEC002003 Essential option/parameter not enough.
DMEC002006 No entry.
DMEC002015 No information displayed.
DMEC002016 Illegal option set.
DMEC002017 Cannot execute the command for the array unit of current microprogram revision.
DMEC002018 Could not execute the function, because the array unit does not support the password protection function.
DMEC002019 No array units registered for error alert.
DMEC002020 Cannot add Send to address, because 20 addresses are already defined.
DMEC002021 The function cannot be executed because option is locked, or disabled.
DMEC002022 The function cannot be executed because the target mode of connected controller is not M-TID,M-LUN.
DMEC002023 The additional information was not registered to the specified subsystem.
DMEC002024 The specified RAID group cannot be deleted because it contains an already defined LU.
DMEC002025 Cannot delete the logical unit, because no logical units defined.
DMEC002026 Failed to open the manual file.
DMEC002027 The specified drive is not defined.
DMEC002028 Cannot use this command for the specified device.
DMEC002029 Cannot use this function for the specified device of this configuration.
DMEC002030 The function cannot be executed because mapping mode is off.
DMEC002031 Insufficient memory. Terminate other programs and then try again.
DMEC002032 The specified port is not available because its host group security is disabled. Enable the host group security and try again.
DMEC002033 The specified host group is already defined. Try with another name or number.
DMEC002034 The specified host group is not defined. Confirm the name or number, and specify a defined host group.
DMEC002035 The specified WWN name is already defined. Specify a new WWN name.
DMEC002036 The specified WWN is not defined. Specify a defined WWN.
DMEC002037 The specified WWN is already assigned to a host group. Specify a WWN that is not assigned to any of the host groups.
DMEC002038 The specified WWN is not assigned to any of the host groups. Specify a WWN that is already assigned to a host group.
DMEC002039 The number of registered WWNs reached the maximum. Delete unnecessary information and then try again.
DMEC002040 The number of registered host group reached the maximum. Delete unnecessary information and then try again.
DMEC002041 The specified WWN has not been logged in. Specify a WWN that is logged in.
DMEC002042 The function cannot be executed because host group 0 is specified. Specify except host group 0 and try again.
DMEC002043 The specified port name is already defined. Specify a new port name.
DMEC002044 No option entry.
DMEC002045 The number of defined logical unit reached the maximum. Delete unnecessary logical units and then try again.
DMEC002046 The specified logical unit capacity is not reallocated.
DMEC002047 The specified logical unit number is already defined. Specify a new logical unit.
DMEC002048 The specified logical unit is not defined. Specify a defined logical unit.
DMEC002049 The function cannot be executed because the password protection function is enabled.
DMEC002050 The function cannot be executed because the format mode is not queue.
DMEC002051 The specified logical unit(s) contain sub logical unit. Confirm the logical unit status and try again.
DMEC002052 The specified logical unit(s) contain invalid logical unit. Confirm the logical unit status and try again.
DMEC002053 The information on the specified logical unit cannot be displayed.
DMEC002054 The number of logical units have reached the maximum. Delete unnecessary logical units and then try again.
DMEC002055 The specified logical unit is not a Snapshot image. Specify a Snapshot image.
DMEC002056 The process cannot be performed because the number of logical units in the data pool reached the maximum. Delete
unnecessary logical units and then try again.
DMEC002057 The data pool cannot be used. Please restart the subsystem.
DMEC002058 The process cannot be performed because no logical units is in the data pool. Add a logical unit to the data pool and try
again.
DMEC002059 When changing the attribute to Read/Write, the retention term cannot be specified.

MSG 08-0050-01

DMEC002060 The process cannot be performed because there are some uncorrected logical units. Start or skip parity correction and try
again.
DMEC002061 Cannot execute the option for the array unit of current micro program revision.
DMEC002062 The specified logical unit number is already defined as a command device. Specify another logical unit number.
DMEC002063 The command device is not registered. Register the command device and try again.
DMEC002065 The specified logical unit number is not defined as a command device. Specify a logical unit that is already defined to a
command device.
DMEC002066 The Cache Residency function cannot be used because it is not installed, locked, or disabled.
DMEC002067 The specified RAID group is not defined. Specify a defined RAID group.
DMEC002068 The logical unit cannot be created because there is not free area in the specified RAID group.
DMEC002069 The logical unit cannot be created because the specified area does not exist. Confirm the free area of the RAID group, and
try again.
DMEC002070 The number of registered subsystems has reached the maximum. Delete unnecessary information and then try again.
DMEC002071 The number of spare drives reach the maximum. Confirm the specified spare drives, and try again.
DMEC002072 The number of DM-LU have reached the maximum. Release unnecessary DM-LU and then try again.
DMEC002073 The specified logical unit number is not defined as a DM-LU. Specify a logical unit that is already defined to a DM-LU.
DMEC002074 The specified logical unit is not Main logical unit. Specify a Main logical unit.
DMEC002075 The manual file of specified command is not found.
DMEC002076 The number of spare drives have reached the maximum. Delete unnecessary spare drives and then try again.
DMEC002077 The logical units are undefined. Please confirm logical units definition and try again.
DMEC002078 The RAID groups are undefined. Please confirm RAID groups definition and try again.
DMEC002079 The number of cache partition have reached the maximum. Delete unnecessary cache partition and then try again.
DMEC002080 The CTL0 cannot be specified because the cache partition to set up is not deleted. When specifying the CTL0, please restart
and then try again.
DMEC002081 The CTL1 cannot be specified because the cache partition to set up is not deleted. When specifying the CTL1, please restart
and then try again.
DMEC002100 The specified port is not available because it is physically unequipped. Confirm the port status and try again.
DMEC002101 The specified LU is not invalid. Specify the invalid LU and try again.
DMEC002102 The collection of performance statistics information is not started. Please start it.
DMEC002103 The directory does not exit.

MSG 08-0060-01

DMED010001 The same host group name exists in a port. Confirm the host group name and then try again.
DMED010002 The same WWN name exists in a port. Confirm the WWN name and then try again.
DMED010003 WWN cannot be assigned to an undefined host group. Specify a defined host group and try again.
DMED010004 The function cannot be executed because host group security on some port is set to enabled. Set host group security to
disable on all ports and try again.
DMED020001 The value of Dirty Data Opportunity is outside the effective range. Specify the value in the effective range and try again.
DMED020002 The value of Dirty Data Stop Opportunity is outside the effective range. Specify the value in the effective range and try again.
DMED020003 The value of Dirty Data Opportunity is equal to or less than value of Dirty Data Stop Opportunity. Specify the value and try
again.
DMED020004 Prefetch Starting Opportunity is outside the effective range. Specify the value of effective range and try again.
DMED020005 LU number is outside the effective range. Specify the LU number of effective range and try again.
DMED020006 Reserved Random Simple Buffer Size is outside the effective range. Specify the value of effective range and try again.
DMED020007 The process failed due to an invalid parameter of Random Simple Buffer Size 0% Mode. Confirm the specified parameter.
DMED020008 Prefetch Count is outside the effective range. Specify the value in the effective range and try again.
DMED020009 Prefetch Size is outside the effective range. Specify the value in the effective range and try again.
DMED02000A The process failed due to an invalid parameter of Next Prefetch Opportunity Mode. Confirm the specified parameter.
DMED020010 Count of Judgment Sequential is outside the effective range. Specify the value in the effective range and try again.
DMED020011 Prefetch Size of Base is outside the effective range. Specify the value in the effective range and try again.
DMED020012 Prefetch Size of Fixed is outside the effective range. Specify the value in the effective range and try again.
DMED030001 The specified LU is already invalid. Confirm the LU status and try again.
DMED030002 The number of LU reached the maximum. Delete unnecessary LUs and try again.
DMED030003 The specified LU is not invalid. Specify the invalid LU and try again.
DMED030004 The specified LU capacity is equal to or more than the capacity of original LU. Confirm the LU capacity and try again.
DMED030006 The specified LU is not invalid. Specify the invalid LU and try again.
DMED030007 The specified LU is unformatted. Specify the formatted LU and try again.
DMED030008 The number of LU reached the maximum. Delete unnecessary LUs and try again.
DMED030009 The process cannot be performed because the specified LU is a Cache Residency LU or a reserved one. Disable the LU,
and then try again.
DMED03000A The specified LU capacity is equal to or less than the minimum capacity of an LU. Specify a larger capacity than the
minimum capacity and try again.
DMED03000B The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
VOL mode to enable, then try again.
DMED040001 The specified LUs contain Sub LU. Confirm the LU status and try again.
DMED040003 The specified LUs contain regressed or detached LU. Confirm the LU status and try again.
DMED040004 The specified LUs contain an un-mounted drive. Confirm the drive status and try again.
DMED040005 The specified LUs contains an invalid LU. Confirm the LU status and try again.
DMED040006 Someone already logged in. Set password protection function to disabled and try again.
DMED040007 There is no LU entered to format.
DMED040008 Format of the logical unit cannot be performed under drive blockage mode. Please turn off the drive blockade mode system
parameter.
DMED040009 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED050001 The process cannot be performed because the specified LU is in a PIN exceeded state. Restore PIN data and try again.
DMED050002 The process cannot be performed because cache segment is insufficient. Wait for a while and then try again.
DMED050003 The process cannot be performed because the specified LU is receiving the Write command continuously from the host.
Wait for a while and then try again.
DMED050004 The process cannot be performed because the specified LU is a Cache Residency LU or a reserved one. Disable the LU, and
then try again.
DMED050005 The process cannot be performed because the partition of necessary conditions for LU changing does not exist. Please
confirm the partition definition and try again.

MSG 08-0070-01

DMED050006 The process cannot be performed because the directory configuration is changing. Please wait for a while and then try again.
DMED050007 The process cannot be performed because the LU change is in progress. Please wait for a while and then try again.
DMED050008 The process cannot be performed because the LU change is in progress. Please wait for a while and then try again.
DMED050009 The LU change could not be performed.
DMED05000A The process cannot be performed because the controller is detached. Please recover the controller status and then try
again.
DMED070001 Cannot set dual ID success because either mounted numbers or types of the host interface boards are different between
controllers. Confirm the interface boards status and try again.
DMED070002 The specified IP address is incorrect. Please specify a right IP address.
DMED070006 When the ShadowImage pair of a S-VOL Switch status exists the ShadowImage I/O Switch Mode cannot be disabled.
Please retry after solving the error.
DMED070007 The configuration of single or dual controller system cannot be changed because Cache Partition Manager is enabled.
Please change Cache Partition Manager to locked or disabled and try again.
DMED080001 The data pool cannot be used. Please restart the subsystem.
DMED080002 The process cannot be performed because the logical unit under restoration. Wait for a while and try again.
DMED080003 The process cannot be performed because the logical unit added to the data pool is not specified.
DMED080004 The process cannot be performed because the same logical unit number has been specified more than twice. Confirm the
logical unit number and try again.
DMED080005 The specified logical unit number is outside of the effective range. Specify the logical unit number within the range and try
again.
DMED080006 The process cannot be performed because the specified logical unit is neither in normal nor in regressed state. Specify the
logical unit of normal or regressed state and try again.
DMED080007 The process cannot be performed because the RAID level or HDU combination of the specified logical unit is not supported.
Confirm the RAID level and the HDU combination currently supported and try again.
DMED080008 The process cannot be performed because the number of logical units in the data pool reached the maximum. Delete the
logical units in the data pool and then try again.
DMED080009 The process cannot be performed because the specified logical unit is a unified LU. Separate the unified LU and try again.
DMED08000A The process cannot be performed because the specified logical unit is a part of ShadowImage pair. Cancel the
ShadowImage pair and try again.
DMED08000B The process cannot be performed because the specified logical unit is a part of TrueCopy pair. Cancel the TrueCopy pair
and try again.
DMED08000C The process cannot be performed because the specified logical unit is a command device. Cancel the command device and
try again.
DMED08000D The process cannot be performed because the specified logical unit has been invalidated. Restore the logical unit and try
again.
DMED08000E The process cannot be performed because the specified logical unit is a part of Snapshot pair. Cancel the Snapshot pair and
try again.
DMED08000F The process cannot be performed because the specified logical unit is defined as a Snapshot image. Specify another logical
unit and try again.
DMED080010 The process cannot be performed because the specified logical unit is added to a data pool. Specify another logical unit and
try again.
DMED080012 The process cannot be performed because the owner controller is different between the specified logical unit and the data
pool. Confirm the logical unit owner controller and try again.
DMED080013 The process cannot be performed because the specified logical unit has been receiving the Write command continuously
from the hosts. Wait for a while and then try again.
DMED080014 The process cannot be performed because other logical unit is changing the Default Controller. Wait for a while and then try
again.
DMED080015 The process cannot be performed because the specified logical unit is in the PIN exceeded state. Restore PIN data and try
again.
DMED080016 The process cannot be performed because the specified logical unit is not enough for sufficient cache blocks. Specify
another logical unit and try again.

MSG 08-0080-01

DMED080017 The process cannot be performed because no logical units in data pool.
DMED080018 The process cannot be performed because the Snapshot pair exists in the specified data pool. Cancel the Snapshot pair and
try again.
DMED080019 The process cannot be performed because data pool deleted is not specified.
DMED08001A The process cannot be performed because the threshold of usage rate in the data pool is not specified.
DMED08001B The specified threshold is outside of the effective range. Specify the value of effective range and try again.
DMED08001C The process cannot be performed because the specified logical unit is capacity equal to or less than 2GB. Specify the logical
unit of bigger capacity than 2GB and try again.
DMED08001D The process cannot be performed because S-VOL mode of the specified logical unit is disabled. Set S-VOL mode to enable
then try again.
DMED08001F The number of specified logical units is over 64. Please specify the logical units in 64 or less.
DMED080020 The process cannot be performed because the drive type of specified logical unit is different from the data pool. Please
confirm the drive type and try again.
and then try again.
then try again.
DMED080023 The logical units in the data pool cannot be mixed with ones in Unit0 or in the latter units.
DMED080024 The process cannot be performed because DM-LU is not defined. Please define DM-LU and then try again.
DMED080025 The process cannot be performed because the specified logical unit is reserved for cache partition modification. Please
specify another logical unit and try again.
DMED090001 The logical unit number of specified P-VOL is outside of the effective range. Specify the logical unit number of effective range
and try again.
DMED090003 The logical unit number of specified Snapshot image is outside of the effective range. Specify the logical unit number of
effective range and try again.
DMED090004 The process cannot be performed because the logical unit number of the Snapshot image created or deleted is not specified.
DMED090005 The process cannot be performed because the same logical unit number has been specified as a Snapshot image more than
twice. Confirm the logical unit number and try again.
DMED090006 The process cannot be performed because the specified logical unit of the P-VOL is neither in normal nor in regressed state.
Specify the logical unit of normal or regressed state and try again.
DMED090007 The process cannot be performed because no logical unit exists in the data pool by the side of the controller of specified P-
VOL. Add the logical unit to the data pool and try again.
DMED090008 The process cannot be performed because the RAID level or HDU combination of the specified logical unit differs from the
logical unit is not supported. Confirm the RAID level and the HDU combination currently supported and try again.
DMED090009 The process cannot be performed because the number of created Snapshot Image for the specified P-VOL has reached its
maximum. Delete unnecessary Snapshot Image and try again.
DMED09000A The logical unit number has already been defined. Specify a new number.
DMED09000B The process cannot be performed because the specified P-VOL is a unified LU. Separate the unified LU and try again.
DMED09000C The process cannot be performed because the specified P-VOL is a part of ShadowImage pair. Cancel the ShadowImage
pair and try again.
DMED09000D The process cannot be performed because the specified P-VOL is a part of TrueCopy pair. Cancel the TrueCopy pair and try
again.
DMED09000E The process cannot be performed because the specified P-VOL is a part of Snapshot pair. Cancel the Snapshot pair and try
again.

MSG 08-0090-01

DMED09000F The process cannot be performed because the specified P-VOL is a command device. Cancel the command device and try
again.
DMED090010 The process cannot be performed because the specified P-VOL is invalid. Restore the LU and try again.
DMED090011 The process cannot be performed because the specified P-VOL has already been added to a data pool. Specify another LU
number and try again.
DMED090012 The process cannot be performed because the specified P-VOL is not enough for sufficient cache capacity. Check cache
capacity and try again.
DMED090013 The process cannot be performed because the HDU combination of the specified P-VOL differs from registered logical units
to the data pool. Confirm the HDU combination and try again.
DMED090014 The process cannot be performed because the specified P-VOL has been receiving the Write command continuously from
the hosts. Wait for a while and then try again.
DMED090015 The process cannot be performed because other logical unit is changing the Default Controller. Wait for a while and then try
again.
DMED090016 The process cannot be performed because the specified P-VOL is in the PIN exceeded state. Restore PIN data and try
again.
DMED090017 The process cannot be performed because the specified P-VOL is not defined. Specify a defined logical unit and try again.
DMED090018 The process cannot be performed because the specified Snapshot image has been creating the pair. Cancel the Snapshot
pair and try again.
DMED090019 The process cannot be performed because P-VOL is under deletion. Wait for a while and then try again.
DMED09001A The process cannot be performed because the specified set of P-VOL and Snapshot image is not a pair. Confirm the pair
status and try again.
DMED09001B The process cannot be performed because the number of Snapshot pair reached the maximum. Delete unnecessary
Snapshot pair(s) and try again.
DMED09001C The process cannot be performed because the unified LU is composed of 17 or more sub logical units. Specify another
logical unit and try again.
DMED09001D The process cannot be performed because the unified LU contains a sub logical unit whose size is less than 1GB. Specify
DMED09001E The process cannot be performed because a management area of Snapshot is shortage. Delete unnecessary Snapshot
pair(s) and try again.
DMED09001F The process cannot be performed because the drive type of specified logical unit is different from the V-VOL. Please confirm
the drive type and try again.
and then try again.
and then try again.
DMED090022 The process cannot be performed because the specified Snapshot image is a part of TrueCopy pair. Cancel the TrueCopy
pair and try again.
DMED090023 The process cannot be performed because the specified Snapshot image is a part of Hi-Copy pair. Cancel the Hi-Copy pair
and try again.
DMED090024 The process cannot be performed because the P-VOL of specified Snapshot image is reserved for cache partition
modification. Please retry after cache partition modification is completed.
DMED0A0001 The process cannot be performed because the specified LU is invalid. Restore the LU and try again.
DMED0A0002 The process cannot be performed because the specified LU is a Sub LU of the unifying LUs. Separate the unified LU and try
again.
DMED0A0003 The process cannot be performed because the specified LU is S-VOL of ShadowImage. Specify another logical unit and try
again.
DMED0A0004 The process cannot be performed because the specified LU is S-VOL of TrueCopy. Specify another logical unit and try
again.
DMED0A0005 The process cannot be performed because the specified LU is Snapshot image. Specify another logical unit and try again.
DMED0A0006 The process cannot be performed in the retention term. The retention term expires and try again.
DMED0A0007 The process cannot be performed because ShadowImage is in progress. Please wait a moment and then try again.

MSG 08-0100-01

DMED0A0008 The process cannot be performed because SnapShot is in progress. Please wait a moment and then try again.
DMED0A0009 The retention term cannot be shortened. Specify the retention term is equal to or more than current value and try again.
DMED0A000A The process cannot be performed because expiration lock is enabled. Set expiration lock to disable and try again.
DMED0A000B The process cannot be performed because the status of ShadowImage pair is not SMPL or PSUS. Please retry after
changing the status of pair.
DMED0A000C The process cannot be performed because the status of TrueCopy pair is not SMPL or PSUS. Please retry after changing
the status of pair.
DMED0A000D The process cannot be performed because the status of Snapshot pair is not PSUS. Please retry after changing the status of
pair.
DMED0B0001 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED0C0001 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED0C0002 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED0C0003 The unification cannot be performed because the drive type is different. Please confirm the drive type and try again.
DMED0C0004 The logical unit in Unit0 cannot be unified with the latter units.
DMED0C0005 The process cannot be performed because the unified LU reached the maximum.
DMED0C0006 The unification cannot be performed because the cache partition is different. Please confirm the cache partition of the
specified logical unit.
DMED0C0007 The process cannot be performed because the specified logical unit is reserved for cache partition modification. Please retry
after changing the cache partition, or specify another logical unit.
DMED0D0001 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED0D0002 The process cannot be performed because the temporary key cannot be used for the next 180 days after it is locked or
expired.
DMED0D0003 The specified function has already been unlocked.
DMED0E0001 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED0F0001 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED0F0002 The process cannot be performed because the drives of Unit0 and the latter units are contained within the range of the
DMED0F0003 The process cannot be performed because the non-supported drive on this subsystem are contained within the range of the
DMED0F0004 The function cannot be used because it is not installed, locked, or disabled.
DMED0F0005 The process cannot be performed because the number of drive is incorrect. Please confirm the mounted drive and try again.
DMED0F0007 The number of defined RAID group reached the maximum. Delete unnecessary RAID groups and then try again.

MSG 08-0110-01

DMED100001 The process cannot be performed because the access level is set up. Please change the attribute to Read/Write and set S-
DMED100002 The process cannot be performed because the RAID level of the specified logical unit is not supported. Confirm the RAID
level currently supported and try again.
DMED100003 The process cannot be performed because the specified logical unit is a unified LU. Separate the unified LU and try again, or
please execute online/offline formatting.
DMED100004 The process cannot be performed because the specified logical unit is extended and not formatted. Please execute
online/offline formatting.
DMED100005 The preparations of quick formatting are incomplete. Please retry after waiting for a while.
DMED100006 The process cannot be performed because the specified logical unit contain an un-mounted drive or a blocked drive. Confirm
the drive status and try again.
DMED100007 Format of the logical unit cannot be performed under drive blockage mode. Please turn off the drive blockade mode system
parameter.
DMED110001 The mapping mode cannot be changed because the mapping guard LU exists.
DMED110002 The mapping information cannot be changed because the mapping guard LU exists.
DMED120001 The specified drive cannot be defined as a spare drive because it is not supported on this subsystem.
DMED130001 The process cannot be performed because the specified remote path is not set up.
DMED140001 The process cannot be performed because the term of the temporary key or emergency key is expired.
DMED140002 The process cannot be performed because the DM-LU has already been set. Please cancel the DM-LU and try again.
DMED150001 The process cannot be performed because the cache partition is not initial status. Please change the cache partition to initial
DMED150004 The process cannot be performed because the cache partition is less than minimum size. Please confirm the cache partition
size and try again.
DMED150005 The process cannot be performed because the PIN is exceeded state. Please restore PIN data and try again.
DMED150006 The segment size of cache partition (0 or 1) cannot be changed.
DMED150007 The process cannot be performed because ShadowImage is in use. Please cancel the ShadowImage pair and try again.
DMED150009 The process cannot be performed because SnapShot is in use. Please cancel the SnapShot pair and try again.
DMED15000B The process cannot be performed because process of Write command from the hosts is not completed. Please wait for a
while and then try again, or delete the logical unit.
DMED15000C The function cannot be executed because a Cache Residency LU or a reserved one exists. Disable the LU, and then try
again.
DMED15000D The specified segment size is incorrect. Please confirm the segment size and try again.
DMED15000E The process cannot be performed because the LU change is in progress. Please wait a moment and try again.
DMED15000F The specified cache partition number is incorrect. Please confirm the cache partition number and try again.
DMED150010 The controller of current cache partition cannot be changed. Please delete the cache partition, and set up again.
DMED150011 The process cannot be performed because the total size of cache partition is over the cache capacity. Please confirm the
cache partition size and try again.
DMED150012 The cache partition with which the logical unit is set up, or the cache partition of 0 or 1 cannot be deleted. Please confirm the
cache partition number.
DMED150013 The process cannot be performed because the specified cache partition is not defined. Please specify a defined cache
partition and try again.
DMED160002 The process cannot be performed because the specified logical unit is a Sub LU of the unifying LUs. Please separate the
unified LU and try again.
DMED160011 The logical unit cannot be allocated the specified cache partition. Please specify another cache partition number and try
again.
DMED160012 The process cannot be performed because the Cache Partition Manager is not installed, locked, or disabled.
DMED160013 The process cannot be performed because the specified logical unit is Snapshot image. Please specify another logical unit
number and try again.

MSG 08-0120-01

DMED170001 The process cannot be performed because the specified logical unit is capacity less than 5GB. Specify the logical unit is
equal to or more than 5GB and try again.
DMED170002 The process cannot be performed because the specified logical unit is RAID level 0. Specify another logical unit and try
again.
DMED170003 The process cannot be performed because the specified logical unit is neither in normal nor in regressed state. Specify the
logical unit of normal or regressed state and try again.
DMED170004 The process cannot be performed because the specified logical unit is a unified LU. Separate the unified LU and try again.
and then try again.
DMED170006 The process cannot be performed because the specified logical unit is a command device. Cancel the command device and
try again.
DMED180001 The specified logical unit cannot be set as Cache Residency LU because its cache partition is not 0 or 1. Please try again
after changing a cache partition into 0 or 1, or specify the logical unit of the cache partition 0 or 1.
DMED200001 The process cannot be performed because cache memory size 1GB or less. Please increase the cache memory and try
again.
DMED200002 This function is unsupported in the single-controller system.
DMED200003 SnapShot cannot be unlocked because Cache Partition Manager is enabled. Please change Cache Partition Manager to
locked or disabled and try again.
DMED200004 Cache Partition Manager cannot be unlocked because the subsystem is not restarted after SnapShot is unlocked. Please
restart the subsystem, and then try again.
DMED300001 The serial number or equipment ID cannot be changed because the path and pair information does not exist.
DMED300002 The serial number or equipment ID cannot be changed because the path and pair information does not exist.
DMED300005 The specified serial number or equipment ID is incorrect. Please specify it in 0-9.
DMED300006 The specified serial number is incorrect. Please specify a right serial number.
DMED300007 The specified serial number is incorrect. Please specify a right serial number.
DMED300008 0 is specified as 6 figures of low order of the serial number. Please specify a right serial number.
DMED300009 The same serial number as a self subsystem is specified. Please specify the serial number of connected subsystem.
DMED30000A The same equipment ID as a self subsystem is specified. Please specify the equipment ID of connected subsystem.
DMED400001 The process cannot be performed because the specified logical units contain an unformatted LU. Confirm the logical unit
DMED400002 The process cannot be performed because the specified logical units contain V-VOL of Snapshot. Confirm the logical unit
DMED400003 The process cannot be performed because some logical units are under quick formatting. Confirm the logical unit status and
try again.
DMED400004 The process cannot be performed because the specified logical units contain a Sub LU of the unifying Lus. Confirm the
logical unit status and try again.
DMED400005 The process cannot be performed because the specified logical units contain an invalid LU. Confirm the logical unit status
and try again.
DMED400006 The specified LUs contain regressed LU. Confirm the LU status and try again.
DMED400007 The process cannot be performed because ShadowImage, TrueCopy, or SnapShot is in progress. Please wait a moment
and then try again.
DMED400007 The process cannot be performed because ShadowImage in-system replication, TrueCopy remote replication, or Copy-on-
write Snapshot is performed. Please wait a moment and then try again.
DMED400008 The operation of 'start' or 'skip', and 'cancel' is specified at the same time. Confirm the operation and try again.
DMED400009 The process cannot be performed because the specified logical units contain an undefined LU. Confirm the logical unit status
and try again.
DMED400011 The process cannot be performed because parity correction is not completed. Please try again, after it is completed.
DMED400012 The process cannot be performed because parity correction is not executed or is aborted. Please try again, after it is
completed.

MSG 08-0130-01

DMED400015 The process cannot be performed because parity correction is not executed or is aborted. Please try again, after it is
completed.
DMED400021 The 'cancel' operation cannot be specified to the uncorrected logical units. Confirm the parity correction status and try again.
DMED400022 The 'start' operation cannot be specified to the aborted logical units. Confirm the parity correction status and try again.
DMED400023 The 'cancel' operation cannot be specified to the aborted logical units. Confirm the parity correction status and try again.
DMED400024 The 'start' operation cannot be specified to the correcting logical units. Confirm the parity correction status and try again.
DMED400025 The 'skip' operation cannot be specified to the correcting logical units. Confirm the parity correction status and try again.
DMED400026 The 'start' operation cannot be specified to the waiting logical units. Confirm the parity correction status and try again.
DMED400027 The 'skip' operation cannot be specified to the waiting logical units. Confirm the parity correction status and try again.
DMED400028 The 'cancel' operation cannot be specified to the skipped logical units. Confirm the parity correction status and try again.
DMED400029 The 'cancel' operation cannot be specified to the corrected logical units. Confirm the parity correction status and try again.
DMED500001 The command device is not registered. Please register the command device and try again.
then try again.
DMED700001 The specified logical unit is not defined. Specify a defined logical unit.
DMED700002 The process cannot be performed because the status of pair is SMPL. Confirm the LU status and try again.

MSG 08-0140-01

DMES000000 Please retry.
DMES015B00 Please retry.
DMES018A03 Please retry.
DMES019621 A reboot is required to confirm a setup.
DMES01EA05 The micro program has been downloaded to the system drives, but some system drives could not be used. The subsystem
can be used.
DMES020404 The process cannot be performed because formatting is now occurring. Retry after formatting completes.
DMES020484 The subsystem is under shutdown process. Retry when the subsystem is in Ready status.
DMES023E00 Please retry.
DMES029500 The process cannot be performed because the subsystem is under shutdown process. Please wait a moment and restart the
subsystem, then try again.
DMES029501 The process cannot be performed because the subsystem is under shutdown. Please restart the subsystem and then try
again.
DMES02959A Please retry.
DMES02959B Please retry.
DMES030C02 Please retry.

MSG 08-0150-01

DMES031D00 Please retry.
DMES033101 Formatting ended abnormally. Please retry after waiting for a while.
DMES033180 The specified LU is unformatted. Specify a formatted LU and try again.
DMES03F000 Please retry.
DMES049502 The requested operation cannot be performed. Please confirm there are any alarms or warnings in the subsystem.
DMES04EA01 Please retry.
DMES04EA02 Please retry.
DMES04EA10 An error was detected in micro program downgrade check. Please retry by using another micro program.
DMES04EA11 The specified micro program could not be installed on to the RKL type because the micro program version is old.
DMES04EB00 The information could not be set because the backup floppy disk is not inserted.
DMES04EB01 The backup information could not be written on to the FD because the FDD is in use or an error occurred in the FDD on the
subsystem.

MSG 08-0160-01

DMES04EB02 An error occurred while writing on to the floppy disk.
DMES04EB03 The SCSI ID could not be set online due to other controller blockage.
DMES04F8F0 Please retry.
DMES04F9F0 Please retry.
DMES052500 The process cannot be performed because the LU is undefined or cannot be recognized from a host.
DMES052580 Failed to allocate LU. Confirm the specified value.
DMES052581 The RAID group is not defined. Please specify an existing RAID group.
DMES052583 The Cache Residency function cannot be enabled.
DMES052584 The last LBA in the RAID group defined at RAID1+0 full mapping does not match the current value.
DMES052590 The LU non-owner controller received an LU replacement command (for TRESPASS mode only).

MSG 08-0170-01

DMES052600 The process failed due to an invalid parameter. Confirm the specified value.
DMES052601 The process failed due to an unsupported parameter. Confirm the specified value.
DMES052602 The process failed due to an invalid parameter. Confirm the specified value.
DMES052604 It failed in release of Persistent Reservation because the type of the Persistent Reserve command was different.
DMES055504 It is impossible to register over 32 LU Reservation Keys.
DMES059510 The process cannot be performed because the microprogram is being replaced.
DMES059511 The process cannot be performed because the SVP is being replaced.
DMES059520 The specified function cannot be performed because the subsystem is in an incorrect status for execution. Please confirm
there are no alarms/warnings in the subsystem, or the configuration is changed.
DMES059530 The specified User ID is not registered.
DMES059531 Could not execute the function, because another user is already logged in.
DMES059532 The specified User ID is already registered.
DMES059533 Failed in registration, because 20 users have already been registered.
DMES059534 Specified password is not confirmed.
DMES059535 Another user already logged in.
DMES059536 The function cannot be used because it is not installed, locked, or disabled.
DMES059537 The function cannot be executed because you haven't logged in.
DMES059540 A spare disk is defined within the range of the specified RAID group. Please specify the range which does not contain a
spare disk.
DMES059541 The drive capacity of RAID group is invalid, or the RAID group capacity is too large.
DMES059542 The specified drive cannot be used as a spare drive.
DMES059543 The number of spare drives has reached the maximum.
DMES059544 The specified drive is already defined as a spare drive, or is already being used in the RAID group.
DMES059545 The specified drive capacity is smaller than that of the RAID group.
DMES059546 The specified drive is not defined as a spare drive.
DMES059547 The specified spare drive cannot be released because it is in use.
DMES059548 The specified function has already been unlocked.
DMES059549 The specified function has already been locked.
DMES05954A Invalid key code.
DMES05954B The RAID group cannot be defined because the drive is not mounted, or a blocked drive exists.
DMES05954C The specified drive cannot be defined as a spare drive because it is not mounted or is in blocked status.
DMES05954D The process cannot be performed because the target mode is not M-TID, M-LUN.
DMES05954E The process cannot be performed because the addition of target information required but changed or deleted information
exist.
DMES059550 The function cannot be executed because of write prohibition.
DMES059551 The function cannot be executed because concealment mode is enabled.
DMES059552 The function cannot be executed because the coupling LU or command device exists.
DMES059554 The function cannot be executed because the command device is not registered.
DMES059555 The function cannot be executed because the stripe size is not 64KB.
DMES059558 The process cannot be performed because the specified LU is a unified LU, or unified LUs exist.
DMES059559 The process cannot be performed because the specified LU is a Cache Residency LU or a reserved one. Disable the LU, and
then try again.
DMES05955A The unification cannot be performed because the controllers in charge of the LUs do not match.
DMES05955B The unification cannot be performed because the controller in charge of LU is reserved to be changed. Cancel the
reservation and then try again.
DMES05955C The LU of RAID0 cannot be unified. Specify an LU which the RAID level is not RAID0.
DMES05955D The unification cannot be performed because the size of the unified LU will exceed 4294967295 blocks.
DMES05955E The separation cannot be performed because the specified LU is not a unified LU. Specify a unified LU and then try again.

MSG 08-0180-01

DMES059560 The process cannot be performed because the target mode is not M-TID, M-LUN.
DMES059561 The process cannot be performed because the target mode is M-TID, M-LUN, but target information have already been set.
DMES059562 The unification cannot be performed because the specified Sub LU is a unified LU. Specify a non-unified LU for Sub LU and
then try again.
DMES059563 The unification or separation cannot be performed because the specified LU is a Sub LU. Specify a Main LU (unified LU) and
then try again.
DMES059564 LU0 cannot be specified as a Sub LU. Specify an LU other than LU0 for Sub LU and then try again.
DMES059565 The unification ( LU concatenation ) cannot be performed because the status of the LU is not normal ( a disk might have
failed ). Specify an LU where the status is normal, and then try again.
DMES059566 The process cannot be performed because the LU number is over max LU number. Specify a number under max LU number
and then try again.
DMES059568 The specified RAID group cannot be deleted because it contains LU0, and Lus exists in other RAID groups.
DMES059569 The specified LU cannot be deleted because it is not the last defined LU.
DMES05956A Cannot define the specified LU because LU0 is not yet defined. Define LU0 first, and then try again.
DMES059571 Failed to set the path. Please confirm the conditions required for a path setup are met.
DMES059572 Failed to delete the path. Please confirm the conditions required for path deletion are met.
DMES059573 The option which cannot be specified at the same time is unlocked.
DMES059574 The process cannot be performed because TrueCopy is in progress.
DMES059575 The option cannot be locked or disabled because the path has already been set.
DMES059577 The process cannot be performed because the pair creation is in progress.
DMES05957A The process cannot be performed because the status of pair is suspend. Please retry after solving the error.
DMES05957B The process cannot be performed under pair status. Please retry after splitting the pair.
DMES05957C The process cannot be performed because the pair has been created in other subsystem.
DMES05957D The process cannot be performed because the subsystem is over the inflow threshold.
DMES05957E The process cannot be performed because the status of ShadowImage pair is incorrect.
DMES05957F The option cannot be unlocked because it is in use in the fibre channel subsystem.
DMES059580 The process cannot be performed because the RAID Manager is doing a conflicting process. Please wait a moment and
then try again.
DMES059590 The process cannot be performed because the subsystem is for the exclusive use of 128 Lus.
DMES059591 The process cannot be performed because the number of ShadowImage pairs reached the maximum.
DMES059600 The process cannot be performed. Wait for a while and then try again.
DMES059601 The specified host group number is invalid.
DMES059602 The process cannot be performed because the specified option is a fee-basis option.
DMES059603 The process cannot be performed because the specified size of LU is over max LU size.
DMES059606 The specified LU is invalid. Specify a valid LU and try again.
DMES059607 The function cannot be executed because the pair LU already exists.
DMES05960A The function cannot be executed because there already exists logical units added to the data pool.
DMES059612 The process cannot be performed because quick formatting is now occurring. Retry after quick formatting is completed.
DMES059615 The process cannot be performed because the specified logical unit is a part of Snapshot pair. Cancel the Snapshot pair and
try again.
DMES059617 The process cannot be performed because the specified RAID level is not supported. Specify the RAID level currently
supported and try again.
DMES05961A The process cannot be performed because parity correction is not completed. Please try again, after It is completed.
DMES05961D The RAID group cannot be created because the different drives are specified within the range of a RAID group. Please
confirm the drive type and try again.
DMES05961E One internal LUN cannot be mapped to two or more host LUN in a port. Please confirm the mapping information and try again.
DMES05961F The function cannot be executed because the Hi-Copy pair LU already exists. Cancel the Hi-Copy pair and try again.

MSG 08-0190-01

DMES05EA03 Failed to download the micro program. Please confirm the combination of the specified micro program and the subsystem.
DMES05EA04 Failed to replace the microprogram. Confirm the subsystem.
DMES05EA10 An error was detected in micro program downgrade check. Please retry by using another micro program.
DMES05EA12 It is impossible to change from the 128LU version micro program to the 64LU version micro program.
DMES05EA15 The micro program cannot be downgraded because the Random Simple Buffer Size 0% Mode is enabled. Please set the
Random Simple Buffer Size 0% Mode to disable then try again.
DMES05EA16 The micro program cannot be downgraded on this current spare drive configuration. Please release all spare drives then try
again.
DMES05EA17 The micro program cannot be downgraded because the units are intermixed. Please remove the AT units then try again.
DMES05EA18 The micro program cannot be downgraded because the ShadowImage I/O Switch Mode is enabled. Please set the
ShadowImage I/O Switch Mode to disable then try again
DMES05EA19 The micro program cannot be downgraded because SnapShot and Cache Residency are unlocked together or not restarted
the subsystem after locked. Please lock either option and restart the subsystem, and then try again.
DMES05EA1A Cannot download, because the micro program does not match to this subsystem. Please retry by using another micro
program.
DMES05EA20 The subsystem cannot be restarted.
DMES05EA30 The ENC micro program download and replacement cannot be performed because there is an error in the loop. Please retry
after solving the error.
DMES05EA31 The process cannot be performed because the ENC micro program is being replaced. Please retry after replacement
completes.
DMES05EA32 Failed to download the ENC micro program. Please confirm the combination of the specified ENC micro program and the
subsystem.
DMES05EA33 The ENC micro program of this revision cannot be downloaded. Please retry by using another ENC micro program.
DMES05EA34 The sum check error of the ENC micro program occurred. Please retry by using another ENC micro program.
DMES05EA35 The ENC micro program is not downloaded. Please try again after downloading.
DMES05EA36 Failed to replace the ENC micro program. Please confirm the subsystem.
DMES05EA40 The process cannot be performed because the Automatic Download is enabled. Please set the Automatic Download to
disable then try again.
DMES05EA41 The process cannot be performed because the ENC micro program is being replaced. Please retry after replacement
completes.
DMES05EB04 The FDD on the subsystem could not be diagnosed because the FDD is in use.
DMES062A03 About LU, all Reservation Keys and Persistent Reservations were cleared by the Clear service action of the Persistent
Reserve command.
DMES062A04 By register of the Persistent Reserve command or Register & Ignore Key service action, the Reservation Key was cleared,
and Persistent Reservation was released.
DMES062A05 Reservation Key was cleared by Preempt of the Persistent Reserve command, or the Preempt & Abort service action.
DMES063F01 The microprogram is downloaded.

MSG 08-0200-01

DMES06821A Please retry.
DMES079578 The process cannot be performed because the data is being copied.
DMES0B3D00 Please retry.
DMES0B4A00 Please retry.
DMES0B4B00 Please retry.
DMES0B4E00 Please retry.
DMES0B9531 Could not execute the function, because another user is already logged in.
DMES0BC000 Please retry.
DMES0BDA00 The process cannot be performed because the drive recovery is in progress. Please retry after waiting for a while.
DMES0BFD00 The process cannot be performed due to LU replacement. Connect to the controller with owner permission and try again.
DMES0BFD01 The process for LU replacement is suspended. Please retry after waiting for a while.

MSG 08-0210-01
.
Chapter 9. Failure Analysis by Sense Data

In case of Fibre Channel, when an error occurs Sense Data is stored in Payload of FCP_RSP and
transferred to Host Computer.
9.1 Details of sense code

The details of Sense Code are shown below.
Sense Sense
Description Recovery methods Reference page
key code
0/5 00 00 There is no valid additional sense information. Collect Simple trace and request the Technical Troubleshooting 7.3
Support Center to analyze the failure and take a Collecting simple
4 01 00 The INDEX signal cannot be detected. measure. trace (TRBL 07-0040)
The SECTOR signal cannot be detected.
1/4 02 00 Seek operation in the Disk Drive cannot be
executed correctly.
4 03 00 A Write Fault was detected in the Disk Drive.
2 04 00 The LU connected cannot execute a command This is not failure. If this error code frequently
because LUs are being formatted. appears, collect Simple trace and request the
2 04 01 The Disk Drive will soon become ready although it Technical Support Center to analyze the failure.
is currently not ready.
2 04 02 The Disk Drive is currently not ready; it has not
been spun-up.
2 04 04 The logical unit is currently not ready.
(It is executing the formatting command.)
2 04 84 A sequential shutdown is in progress.
2 05 00 An error occurred in the drive interface in the Collect Simple trace and request the Technical
logical unit. Support Center to analyze the failure and take a
1/4 06 00 The positioning to Track 0 failed. measure.
4 07 00 Two or more Disk Drives were selected at the

same time.
4 08 00 An error occurred in the drive interface in the
logical unit.
4 08 01 A time-out error occurred in the drive interface in
the logical unit.
1/4 08 02 A parity error occurred in the drive interface in the
logical unit.
1/4 09 00 A track positioning failed.
3 0C 02 An automatic allocation was executed against the

write error but failed.
3 0C FF Write processing time exceeded Recovery Time
Limit, write processing was terminated.
3 10 00 A CRC error occurred in the ID field.

MSG 09-0000-01
Sense Sense
key code
3 11 00 An error occurred in the data field. Collect Simple trace and request the Technical Troubleshooting 7.3
3 11 01 Reading of the data field was retried but the error measure. trace (TRBL 07-0040)
was not recovered. (An error correction was not
applied.)
3 11 02 The read error in the data field could not be
corrected by means of the ECC.
3 11 04 An automatic reallocation was executed against
the recoverable error but failed
3 11 FF Read or Verify processing time exceeded
Recovery Time Limit, read or verify processing
was terminated.
3 12 00 The address mark of the ID field could not be
detected.
1/3 13 00 The address mark of the data field could not be
detected.
1/3 14 01 The block with the identical ID field could not be
detected.
1/4 15 01 A seek error occurred.
1/4 15 02 The seek operation terminated normally but the

head was positioned at an address not intended.
1 17 00 The error was recovered by a retry. This is not failure. If this error code frequently
appears, collect Simple trace and request the
1 17 01 The error was recovered by a retry (without a head Technical Support Center to analyze the failure.
offset).
1 17 02 The error was recovered by a retry with a head
offset in the positive direction.
1 17 03 The error was recovered by a retry with a head
offset in the negative direction.
1 18 00 The error was recovered by the ECC (without a
retry).
1 18 01 The error was recovered by the ECC applied in a
retry.
1 18 02 Data was recovered by an automatic reallocation.
1/3 19 02 An error occurred during an access to the Primary Collect Simple trace and request the Technical
(P) list. Support Center to analyze the failure and take a
1/3 19 03 An error occurred during an access to the Grown measure.
(G) list.
5 1A 00 The parameter list length is illegal.
4 1B 00 A synchronous data transfer error occurred in a

data transfer.
3 1C 01 The positioning to the Primary (P) list failed.
3 1C 02 The positioning to the Primary (P) list failed.
3 1D 00 A data compare error occurred during write or

read buffer verify processing.

MSG 09-0010-01
Sense Sense
key code
5 20 00 The operation code is invalid. This is not failure. If this error code frequently Troubleshooting 7.3
appears, collect Simple trace and request the Collecting simple
Technical Support Center to analyze the failure. trace (TRBL 07-0040)
5 21 00 An attempt was made to access beyond the Collect Simple trace and request the Technical
logical block address reported with Read Capacity Support Center to analyze the failure and take a
(PMI bit=0). measure.
5 22 00 The Read command could not be executed
because the access level had been set with Data
Retention Utility.
5 24 00 There is an invalid field in the CDB. This is not failure. If this error code frequently Troubleshooting 7.3
Ex.: RESERVED Bit/VALUE ZERO appears, collect Simple trace and request the Collecting simple
5 25 00 The LUN shown by the CDB or Identify message Technical Support Center to analyze the failure. trace (TRBL 07-0040)
is not supported.
5 25 80 The logical unit allocation failed. Collect Simple trace and request the Technical
Support Center to analyze the failure and take a
measure.
5 25 81 The RAID group (RG) is not defined. This is not failure. If this error code frequently
Technical Support Center to analyze the failure.
5 25 83 P The Turbo LU specification was rejected by the Collect Simple trace and request the Technical
specification condition check. Support Center to analyze the failure and take a
5 25 84 The current value of the Row Last LBA in the measure.
RAID group is different from that when RAID 1+0
full mapping was defined.
5 25 90 The controller with no LU owner right received a This is not failure. If this error code frequently
command to switch the LU (in the case of the appears, collect Simple trace and request the
Trespass mode). Technical Support Center to analyze the failure.
5 25 A0 The divisional transfer failed. Collect Simple trace and request the Technical
Support Center to analyze the failure and take a
5 26 00 There is an invalid field in the parameter list. measure.
5 26 01 An unsupported parameter was received.
5 26 02 The parameter value is invalid.
5 26 04 The release from the Persistent Reservation failed

because the type of the Persistent Reserve
command was different.
7 27 00 The write command could not be executed
because the access level had been set with Data
Retention Utility.
6 29 00 A Power On Reset occurred. This is not failure. If this error code frequently Troubleshooting 7.3
An internal reset occurred owing to a serious appears, collect Simple trace and request the Collecting simple
hardware error. Technical Support Center to analyze the failure. trace (TRBL 07-0040)

MSG 09-0020-01
Sense Sense
key code
6 2A 00 The Mode Select parameter was changed. This is not failure. If this error code frequently Troubleshooting 7.3
Another system received the SCSI Reset in the appears, collect Simple trace and request the Collecting simple
dual configuration. Technical Support Center to analyze the failure. trace (TRBL 07-0040)
Ex,: A parameter was changed by the Mode
Select command.
6 2A 03 The Reservation Key and Persistent Reservation
of the LU concerned were all cleared by the Clear
service action of the Persistent Reserve
command.
6 2A 04 The Reservation Key was deleted and the
Persistent Reservation was cancelled by the
Register or Resister &Ignre Key service action of
the Persistent Reserve command.
6 2A 05 The Reservation Key was deleted by the Preempt
or Preempt & Abort service action of the
Persistent Reserve command.
6 2F 00 The command was cleared according to the Clear
Queue message from another initiator or owing to
an occurrence of the CA status in the initiator.
3 31 00 The medium is not formatted correctly; it must be Collect Simple trace and request the Technical
reformatted by the Format Unit command Support Center to analyze the failure and take a
3 31 01 The Format command terminated abnormally; it measure.
must be reformatted by the Format Unit command.
3 31 80 The data format for the disk array is not
established.
3 31 81 The format command cannot be executed
because the Disk Drive configuration is
incomplete (i.e., the data or parity drive is
detached).
An attempt was made to execute the format
command beyond the actual disk capacity.
1/4 32 00 The reallocation cannot be done because the
alternative area is insufficient.
1/3 32 01 The update of the Grown (G) list failed.
5 35 01 An ENC time-out (FC) or an illegal frame was sent Collect Simple trace and request the Technical
(SATA). Support Center to analyze the failure and take a
measure.
1 37 00 The processing was executed with the parameter
value rounded because it could not be executed
with the original value.
B 3D 00 An invalid bit was detected in the Identify Collect Simple trace and request the Technical Troubleshooting 7.3
message. Support Center to analyze the failure and take a Collecting simple
2 3E 00 The self- configuration of the Disk Drive is not measure. trace (TRBL 07-0040)
established yet.
6 3F 01 The microprogram was downloaded. This is not failure. If this error code frequently

MSG 09-0030-01
Sense Sense
key code
B 43 00 The operation cannot be continued because the Collect Simple trace and request the Technical Troubleshooting 7.3
message was rejected or an error occurred in the Support Center to analyze the failure and take a Collecting simple
Message phase. measure. trace (TRBL 07-0040)
4 44 00 A hardware or firmware error was detected in the
Controller during the command execution.
4 44 00 A abnormal end of the Formatting job generated
by the read command was detected.
4 44 00 A abnormal end of the Formatting job generated
by the write command was detected.
4 44 A0 No sector to be reassigned cannot be detected.
B 45 00 A Select/ Reselect time-over was detected.

An invalid selection was detected.
B 47 00 A Fibre Channel bus on CRC error occurred.
B 48 00 The Initiator Detected Error message was

received from the initiator.
B 49 00 An invalid message was detected.
The communication via a LAN was not done

normally because of a LAN failure.
B 4A 00 An error occurred during accepting of the
command.
B 4B 00 An error occurred during data transfer.
4 4C 00 A loading of a microcode or parameter failed when

starting up the controller.
B 4E 00 Two commands with no tag was issued to the
same I-T-L.
Commands with and without tags were issued to
the same I-T-L. (When this code is reported, all
the commands queuing for the I-T-L concerned
are cleared.)
5 55 04 A registration of 32 or more Reservation Keys in
an LU was attempted.
1 5B 00 An exceptional log in the Disk Drive was detected.
1 5B 02 The log counter in the Disk Drive reached its

maximum value.
1 5B 03 All log list codes in the Disk Drive were used up.
1/6 5C 02 A synchronous withdrawal failure or an off-

synchronization after a passing synchronization
was detected.

MSG 09-0040-01
Sense Sense
key code
6 82 00 The disk recovery by means of a drive recovery This is not failure. If this error code frequently Troubleshooting 7.3
completed normally(*1). appears, collect Simple trace and request the Collecting simple
Technical Support Center to analyze the failure. trace (TRBL 07-0040)
6 82 01 Unrecoverable data was generated although the Collect Simple trace and request the Technical
disk recovery by means of a drive recovery Support Center to analyze the failure and take a
completed normally. measure.
6 82 02 The Disk Drive recovery by means of a Disk Drive
recovery completed normally. But the
configuration status was not changed to that in
which the recovery had completed because a
unrecoverable error occurred(*1).
6 82 10 The Disk Drive recovery was forcibly terminated This is not failure. If this error code frequently
by an operator instruction(*1). appears, collect Simple trace and request the
6 82 11 The Disk Drive recovery was forcibly terminated Collect Simple trace and request the Technical
because a media error was detected in the Disk Support Center to analyze the failure and take a
Drive recovery source disk during the drive measure.
recovery(*1).
6 82 12 The Disk Drive recovery was forcibly terminated
because a media error was detected in the Disk
Drive recovery destination disk during the drive
recovery(*1).
because a hardware error was detected in the
Disk Drive recovery source disk during the drive
recovery(*1).
because a hardware error was detected in the
Disk Drive recovery destination Disk Drive during
the drive recovery(*1).
because the Disk Drive recovery source disk was
blocked during the Disk Drive recovery(*1).
because the Disk Drive recovery destination Disk
Drive was blocked during the drive recovery(*1).
because a hardware error was detected in an
inter-cache control during the Disk Drive
recovery.(*1).
because the status of the configuration information
changed (*1).
6 82 19 The Disk Drive could not be started because data
for write-after remains in the recovery destination
Spare Disk(*1).
*1 : The sense code is not reported to the host. (It is reported as the Sense Information on Mode Sense page 34H.)

MSG 09-0050-01
Sense Sense
key code
6 82 1A The Disk Drive recovery was forcibly terminated Collect Simple trace and request the Technical Troubleshooting 7.3
because an time-out occurred in an internal Support Center to analyze the failure and take a Collecting simple
process(*1). measure. trace (TRBL 07-0040)
B 83 00 The dump information was changed because
another controller was blocked during a collection
of the Send Diag drive dump.
4 8A 01 A parity error was detected during a medium parity
consistency check.
4 8A 02 A parity error was detected during a medium LA
consistency check.
1 8A 03 Intermediate pinned data and dirty data were
found during a parity consistency check.
1 8A 04 Remaining intermediate or physical dirty data and
pinned data were found during an LA consistency
check of a medium.
1 8B 01 An inoperable command was issued to the
blocked logical unit.
5 8C 01 Parity check was required in the Regression
mode.
3 8E 01 An instruction to read or verify was given to the
block on which a writing has not completed.
3 8E 02 Reading on the V-Vol was attempted it could not
be done because of the incomplete DDCB.
3 8E 03 Writing on the V-Vol was attempted it could not be
done because of the incomplete DDCB.
3 8E 04 An intermediate or logical dirty pinned data was This is not failure. If this error code frequently
found to be left in an LU consistency check of a appears, collect Simple trace and request the
medium. Technical Support Center to analyze the failure.
3 8E 05 A copy or restore by a general purpose ASYNC Collect Simple trace and request the Technical
job was not completed in execution of Copy-on- Support Center to analyze the failure and take a
write SnapShot. measure.
4 90 00 An unrecoverable data error occurred during a
data recovery with parity disk data.
3/4 90 01 An unrecoverable data error occurred during
operation in the Regression mode.
4 91 00 Data could not be reconstructed because an
unrecoverable error was detected during an
automatic allocation
4 91 01 The alternative block could not be reallocated in
an automatic reallocation.
3 93 00 A parity adjustment error occurred in the Cache
memory.
5 94 01 The Control Unit with no LU owner right received a This is not failure. If this error code frequently
command to switch the LU (in the case of the appears, collect Simple trace and request the
Alternate Paths 1 and 2). Technical Support Center to analyze the failure.
*1 : The sense code is not reported to the host. (It is reported as the Sense Information on Mode Sense page 34H.)

MSG 09-0060-01
Sense Sense
key code
2 95 00 The pseudo sequential shutdown is in progress. This is not failure. If this error code frequently Troubleshooting 7.3
2 95 01 The pseudo sequential shutdown terminated Technical Support Center to analyze the failure. trace (TRBL 07-0040)
normally.
4 95 02 The pseudo sequential shutdown terminated Collect Simple trace and request the Technical
abnormally. Support Center to analyze the failure and take a
measure.
5 95 10 The command cannot be executed because the This is not failure. If this error code frequently
microprogram is being replaced. appears, collect Simple trace and request the
5 95 20 The Mode Select/Mode Sense 3EH (extended Collect Simple trace and request the Technical
code 03H/04H/05H/06H) was received in the state in Support Center to analyze the failure and take a
which no command could be executed. measure.
4 95 36 The priced option function is in the unsupported This is not failure. If this error code frequently
status. appears, collect Simple trace and request the
5 95 40 A Spare Disk has been defined within a range of Collect Simple trace and request the Technical
the designated RG (at the time of the RG setting). Support Center to analyze the failure and take a
5 95 41 The Disk Drive capacity is illegal (when the RG is measure.
set).
The cause may be one the following.
1. The capacity of the data disk exceeds that of
the Spare Disk.
2. When the RG was expanded, the Disk Drive
capacity of the added portion was smaller
than that of the Disk Drive that had already
been defined.
5 95 42 The designated Disk Drive is that which cannot be .
defined as a Spare Disk (at the time of the Spare
Disk designation).
5 95 43 The number of the specified Spare Disks exceeds
maximum definable value (at the time of the Spare
Disk designation).
5 95 44 The designated drive has already been defined as
a Spare Disk or an RG (at the time of the Spare
Disk specification).
5 95 45 The value of the designated Last LBA is less than
the maximum Last LBA of the RG (at the time of
the Spare Disk designation). (The cases where the
drive is blocked or uninstalled are excluded.)
5 95 46 An instruction to release a drive of a Spare Disk
was issued to the Disk Drive which was not
designated as a Spare Drive (at the time of the
Spare Disk release).
5 95 47 The Spare Disk is being used though it was This is not failure. If this error code frequently
specified to be released of the Spare Disk. appears, collect Simple trace and request the
5 95 48 An unlocking instruction was given to the drive Collect Simple trace and request the Technical
which was not locked. Support Center to analyze the failure and take a
measure.

MSG 09-0070-01
Sense Sense
key code
5 95 49 A locking instruction was given to the drive which Collect Simple trace and request the Technical Troubleshooting 7.3
was already locked. Support Center to analyze the failure and take a Collecting simple
5 95 4A The pricing key code is invalid. measure. trace (TRBL 07-0040)
5 95 4B The RAID group cannot be set because the Select the installed Disk Drive, and set the RAID System Parameter
uninstalled or blocked Disk Drive is included in the group. Chapter 3. Setting
specified Disk Drive. Or, set the RAID group again after replacing the the RAID/LU/Spare
blocked Disk Drive. Disk (SYSPR 03-
0000)
Replacement 2.2.1
(REP 02-0050)
5 95 4D The process cannot be performed because the Collect Simple trace and request the Technical Troubleshooting 7.3
target mode is mode is not M-TID, M-LUN. Support Center to analyze the failure and take a Collecting simple
(Mapping mode) measure. trace (TRBL 07-0040)
5 95 4E The process cannot be performed because the
target information are changed or deleted.
5/7 95 50 Command not execute for write prohibition.
5 95 51 Command not execute for concealment mode.
5 95 52 Command not execute for coupling LU or

Command Device exist.
5 95 53 Ap distinction number is full.
5 95 54 Command response can not be done because

command device is not set.
5 95 56 Command not execute because failure occurred in
reverse resync.
5 95 57 y (LU Size Non-Rounding mode is off)
A pair cannot be formed because the primary
and secondary LU sizes (host LU size = rounded
LU size) are not the same.
y (LU Size Non-Rounding mode is on)
A pair cannot be formed because the primary
and secondary LU sizes (either or both of the
host LU sizes and rounded LU sizes) are not the
same.
5 95 58 The command cannot be issued because LU
unification is in progress.
5 95 59 LU unification, a dissolution of LU unification, or a
separation of a final LU could not be done
because an internal LU to have been used for the
operation above was a Turbo LU or a reserved
Turbo LU.
5 95 5A The LU unification could not be done because
Controllers that control LUs to be unified were not
the same.

MSG 09-0080-01
Sense Sense
key code
5 95 5B The LU unification could not be done because a Collect Simple trace and request the Technical Troubleshooting 7.3
Controller that controls the LUs to be unified was Support Center to analyze the failure and take a Collecting simple
being changed. measure. trace (TRBL 07-0040)
5 95 5C The LU unification could not be done because a
RAID level of the LUs to be unified was RAID 0.
5 95 5D The LU unification could not be done because an
LU size after the unification would be larger than 2
Tbytes.
5 95 5E A dissolution of LU unification or a separation of a
final LU could not be done because the LU
concerned was not a unified LU.
5 95 62 The LU unification could not be done because a
unified LU was selected as a Sub LU to be unified.
5 95 63 LU unification, a dissolution of a unified LU or a
separation of a final LU could not be done
because a Sub LU had been selected.
5 95 64 The LU unification could not be done because the
LU #0 was selected as the Sub LU.
7 95 65 The LU unification could not be done because an
LU status was other than normal or regression.
5 95 66 The LU unification could not be done because the
number of the internal LU that configures the
unified LU exceeded 2047.
5 95 67 LU unification, a dissolution of an LU unification, or
a expansion of a final LU could not be done
because the LU unifying function (enhancing
function) was not validated.
5 95 69 The final LU could not be deleted because it was
not specified.
5 95 6B Because the differential bit could not be assigned,
the pair forming command of the MRCF-Lite could
not be executed.
5 95 71 The path could not be set.
5 95 72 The path could not be deleted.
5 95 73 Since a function that cannot coexist with the

function was being used in the system, the key for
the extra-cost option could not be open.
5 95 74 The command could not be executed because the
remote copy function was being used.
5 95 75 The command could not be executed because the
path was already defined.
5 95 76 The pair operation command from RAID Manager
could not be executed.
5 95 77 The command (host or Storage Navigator
Modular) could not be executed because the pair
was being generated.
7 95 78 The host command could not be executed
because data copy was on progress.

MSG 09-0090-01
Sense Sense
key code
5 95 79 The host command could not be executed Collect Simple trace and request the Technical Troubleshooting 7.3
because the primary volume was write-protected. Support Center to analyze the failure and take a Collecting simple
5 95 7A The host command could not be executed measure. trace (TRBL 07-0040)
because the pair status is PSUE (suspended due
to failure).
5 95 7B The command could not be executed between the
devices because the pair status was invalid.
5 95 7C The command could not be executed between the
devices because the remote device was already
paired with another device.
5 95 7D The command issued by a DF to another DF cannot
be executed because the limit of the inflow has
been exceeded.
5 95 7E The command issued by a DF to another DF
cannot be executed because a status of the pair
formed by the ShadowImage in-system replication
is invalid.
5 95 80 The command cannot be executed because the
command from RAID Manager is being received.
B 95 81 Any further processing cannot be executed Execute it again after waiting for a while.
because the SEL command is received
consecutively.
5 95 91 The setting of or reference to the pairs, number of Collect Simple trace and request the Technical Troubleshooting 7.3
which exceeds the allowable maximum value, was Support Center to analyze the failure and take a Collecting simple
attempted. measure. trace (TRBL 07-0040)
because the fence level was data.
5 95 96 The read command could not be executed
because the concealment mode was turned on for
the remote copy function.
because the secondary volume was in the paired
status in the remote copy function.
7 95 98 The write command could not be executed due to
the restriction on the secondary volume access in
the remote copy function.
4 95 99 The pair status transited to PSUE because the
write command failed duplicate write.
2 95 9A The vendor unique command cannot be executed
in order to avoid a deadlock owing to a duplex
writing.
2 95 9B The read/write command cannot be executed
because the read access mode is Enable when
the fence level is "data."
5 96 00 Storage Navigator Modular command sequence
error (Another command is being executed in the
disk array subsystem.)
5 96 01 The setting was made for a host group other than 0.

MSG 09-0100-01
Sense Sense
key code
5 96 02 The command could not be executed because Collect Simple trace and request the Technical Troubleshooting 7.3
locking or unlocking operation for the feature other Support Center to analyze the failure and take a Collecting simple
than purchasable optional features was attempted. measure. trace (TRBL 07-0040)
5 96 03 The command could not be executed because
locking or unlocking operation for the feature other
than purchasable optional features was attempted.
5 96 04 Writing of the system parameters on five drives
failed.
5 96 05 The execution could not be done because the LU
concerned was concealed.
5 96 07 The execution could not be done because the pair
was a Copy-on-write SnapShot pair.
5 96 08 The pair operation command issued by RAID
Manager could not be executed.
2 96 09 The pair operation command cannot be executed
from RAID Manager. (Waiting for a command to
be retried from RAID Manager.)
5 96 0A The command could not be executed because the
LU was that in the pool filed.
5 96 0B The pool management filed is invalid.
5 96 0C The command could not be executed because a

reading was prohibited.
5 96 0D A reading in an S-VOL was attempted when the
pair status was special PSUE, however, it failed.
5 96 11 The access level could not be changed.
5 96 12 The execution was impossible because the

Format was in progress.
5 96 13 The execution was impossible because the access
level had been specified.
because the LU forming the Copy-on-write
SnapShot pair was in the status in which writing to
it was prohibited.
7 96 15 The LU could not be formatted because it formed
a Copy-on-write SnapShot pair.
5 96 16 No pair formation enabled because more than 33
pairs existed in the same group ID with the
specified group ID.
5 96 17 The RG (RAID group) could not be defined Specify a RAID level other than RAID 0.
because a RAID level specified for the RG was
RAID 0.
5 96 18 The execution was impossible because the status Retry after issuing an instruction to make or skip
of the LU concerning the parity correction was the parity correction using the Storage Navigator
Unrestored or Unrestored 2. Modular.
5 96 19 The command of the Juke Box function could not Collect Simple trace and request the Technical Troubleshooting 7.3
be executed. Support Center to analyze the failure and take a Collecting simple
measure. trace (TRBL 07-0040)

MSG 09-0110-01
Sense Sense
key code
5 96 1A The execution was impossible because the Issue an instruction to make or skip the parity Troubleshooting <
restoration for the LU by means of parity was correction using the Storage Navigator Modular Procedure given in
undone, undone 2, in progress, or on standby. and retry after the restoration for the LU by windows > (TRBL 06-
means of parity is completed or skipped. 0250)
7 96 1B A command was issued to an inaccessible area Execute the forced parity correction or skip it.
while the forced parity correction, which was made
with the subsystem power turned on, was in
progress.
5 96 1C The ShadowImage in-system replication pair Collect Simple trace and request the Technical Troubleshooting 7.3
operation could not be executed. Support Center to analyze the failure and take a Collecting simple
5 96 1D The RG (RAID group) could not be defined Make sure of the operation and try again.
because the specified RG included both of the FC
and SATA drives.
B 96 1E A response with a notification that the status had Retry the execution of the command.
been changed to special PSUE was made during
execution of the R/W command.
5 96 1F It cannot be executed due to the Hi-Copy pair. Execute it again after releasing the Hi-Copy pair.
5 96 20 The Hi-Copy operation cannot be executed. Check the status of the subsystem on the other
side.
4 97 00 A copy job of Copy-on-write SnapShot terminated Collect Simple trace and request the Technical Troubleshooting 7.3
abnormally. Support Center to analyze the failure and take a Collecting simple
4 97 01 A restoration job of Copy-on-write SnapShot measure. trace (TRBL 07-0040)
4 97 02 The status of the Copy-on-write SnapShot pair
was changed to PSUE.
4 97 03 The status of the Copy-on-write SnapShot pair
was changed to PSUE because the restoration
failed.
4 99 00 Data in the cache cannot be written on the drive in
a synchronized cache.
5 9F FF A sense key and sense code to be used Take a recovery action referring to 9.2List of 9.2 List of detail
exclusively for responding to Storage Navigator detail codes of sense code (05/9FFF). codes of sense code
Modular and RAID Manager. (05/9FFF) (MSG 09-
0190)
4 A0 00 A failure occurred in the cache circuit. Collect Simple trace and request the Technical Troubleshooting 7.3
B A1 00 An invalid boundary error occurred during DMA measure. trace (TRBL 07-0040)
transfer.
B C0 00 A time-out occurred during an internal processing.
0/B C0 00 DRR time-out detected in Format process.
B C0 01 A time-out occurred during a data transfer

between a host computer.
B C0 02 A time-out occurred during communication between
the Controllers.
B C0 03 A time-out occurred during a data transfer

MSG 09-0120-01
Sense Sense
key code
B C0 04 A time-out of the Formatting job generated by the Collect Simple trace and request the Technical Troubleshooting 7.3
read command was detected. Support Center to analyze the failure and take a Collecting simple
B C0 04 A time-out of the Formatting job generated by the measure. trace (TRBL 07-0040)
write command was detected.
B C0 05 The command was terminated abnormally due to
another Control Unit failure.
B C0 0A A CRC error occurred during a data transfer
B C1 00 The cache necessary for the formatting cannot be
assigned.
B C2 00 The system current drive was changed
B DA 00 The new data recovery request cannot be

accepted because another Disk Drive is being
recovered
6 E0 00
6 E2 00
4 E4 00 The system area overflowed(*1). (Pinned data Collect Simple trace and request the Technical Troubleshooting 7.3
management area) Support Center to analyze the failure and take a Collecting simple
6 E5 00
6 E5 01
6 EA 00 There was a Disk Drive on which the take-over
information could not be written.
4 EA 01 The program size which the write buffer received Collect Simple trace and request the Technical Troubleshooting 7.3
was larger than that of the program area. Support Center to analyze the failure and take a Collecting simple
4 EA 02 The take-over information size which the write
buffer received was larger than that of the take-
over information of the system.
5 EA 03 A microprogram download error was detected.
5 EA 04 An error was detected when online microprogram

replacement was specified.
1 EA 05 A microprogram installation is in the state in which
it has been partially completed.
4 EA 10 An error in the microprogram downgrade check.
5 EA 13 An error in the microprogram upgrade check.
5 EA 15 A downgrade was made though a specification for Replace the microprogram after invalidating the
the random simple buffer size as 0% was size of the random simple buffer specified as 0%.
validated.
5 EA 16 Downgrade of the microprogram was performed Reduce the number of the spare disk drives to 15
when 16 or more Spare Disk Drives were used. or less.
5 EA 17 Downgrade of the microprogram was performed Make the system configuration have the FC disk
when the FC and SATA disk array units coexisted. array unit only. (A configuration with the SATA
disk array unit only is not supported.)
*1 : In the case where WAR = 1 in the Mode Select command when reporting the sense code to a host, Sense key: 4/
Code: F8 04 H are also reported.

MSG 09-0130-01
Sense Sense
key code
5 EA 1A A system version check error occurred in the Use the microprogram corresponding to the Microprogram
microprogram download. subsystem and do the update installation of the Chapter 1.
microprogram again. Installation of
Microprogram
(MICRO 01-0000)
5 EA 30 The ENC microprogram download or replacement Perform the ENC microprogram download or
in the online mode could not be performed replacement in the online mode after solving the
because of a loop trouble or the Single mode. loop trouble.
5 EA 31 The command cannot be executed because ENC Execute the command after the ENC
microprogram replacement in the online mode is in microprogram replacement in the online mode is
progress. completed.
5 EA 32 The ENC microprogram download in the online Perform the ENC microprogram download in the
mode cannot be performed. online mode again.
5 EA 33 A revision check error occurred in the ENC Check the ENC microprogram revision again and
microprogram download in the online mode. perform the ENC microprogram download in the
online mode again.
5 EA 34 A sum check error occurred in the ENC Check the ENC microprogram again and perform
microprogram download in the online mode the ENC microprogram download in the online
occurred. mode again.
5 EA 35 The ENC microprogram replacement in the online Perform the microprogram replacement in the
mode cannot be performed because the ENC online mode after performing the ENC
microprogram download in the online mode has microprogram download in the online mode.
not been performed.
5 EA 36 A parameter for the ENC microprogram Perform the ENC microprogram replacement in
replacement in the online mode is illegal. the online mode again.
5 EA 40 Since the automatic ENC microprogram download Disable the option and execute the command
function is enabled, the command cannot be again.
executed.
5 EA 41 Since the automatic ENC microprogram download Execute the command at the time of the
is executing, the command cannot be executed. automatic download.
5 EB 10 The information on the traceability cannot be set.
4 F4 00 The cache module was blocked because a Cache Replace the Cache Unit. Replacement 2.2.6
memory error occurred. Replacing Cache Unit
(REP 02-0540)
4 F6 10 A Disk Drive emerged in which the number of Replace the Disk Drive. Replacement 2.2.1
recovered mechanical errors exceeded the Replacing Disk Drive
threshold value(*1). (REP 02-0050)
4 F6 11 A Disk Drive emerged in which the number of
unrecovered mechanical errors exceeded the
threshold value(*1).
recovered medium errors exceeded the threshold
value(*1).

MSG 09-0140-01
Sense Sense
key code
4 F6 21 A Disk Drive emerged in which the number of Replace the Disk Drive. Replacement 2.2.1
unrecovered medium errors exceeded the Replacing Disk Drive
threshold value(*1). (REP 02-0050)
recovered R/W errors exceeded the threshold
value(*1).
unrecovered R/W errors exceeded the threshold
value(*1).
recovered interface errors exceeded the threshold
value(*1).
unrecovered interface errors exceeded the
recovered hardware errors exceeded the threshold
value(*1).
unrecovered hardware errors exceeded the
correctable errors in the online verify exceeded the
uncorrectable errors in the online verify exceeded
the threshold value(*1).
4 F8 00 Battery failure(*2) Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem and replace the Confirm log messages
Backup Battery Unit. (TRBL 04-0100)
Replacement 2.2.2
Replacing Backup
Battery Unit (REP 02-
0240)
4 F8 01 Fan failure(*2) Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem and replace the Fan Confirm log messages
Assembly. (TRBL 04-0100)
Replacement 2.2.3
Replacing Fan
Assembly (REP 02-
0300)
4 F8 02 DC failure(*2) Specify a part to be replaced by checking the log Troubleshooting 4.3
Power Unit. (TRBL 04-0100)
Replacement 2.2.4
Replacing Power Unit
(REP 02-0340)
*2 : The sense code is reported to the host only when WAR = 1 in the Mode Select command (page35 H ).

MSG 09-0150-01
Sense Sense
key code
4 F8 03 Drive failure (regression)(*1) Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem and replace the Disk Confirm log messages
Drive. (TRBL 04-0100)
Replacement 2.2.1
(REP 02-0050)
4 F8 04 Pin data over(*2) Collect Simple trace and request the Technical Troubleshooting 7.3
4 F8 05 Module blockade(*2) Specify a part to be replaced by checking the log Troubleshooting 4.3
Cache Unit. (TRBL 04-0100)
Replacement 2.2.6
Replacing Cache Unit
(REP 02-0540)
4 F8 07 AC LINE/INBOX failure Specify a part to be replaced by checking the log Troubleshooting 4.3
Power Unit. (TRBL 04-0100)
Replacement 2.2.4
Replacing Power Unit
(REP 02-0340)
4 F8 08 UPS failure Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem. When the UPS is Confirm log messages
connected, take a recovery action referring the (TRBL 04-0100)
UPS manual. (If a sense code, FB F2, is Replacement 2.1
displayed at the same time, take an action Locations of
following the recovery procedure corresponding to Replacement
it first.) Components (REP
02-0000)
4 F8 09 Battery backup circuit failure Specify a part to be replaced by checking the log Troubleshooting 4.3
Backup Battery Unit. (TRBL 04-0100)
Replacement 2.2.2
Replacing Backup
Battery Unit (REP 02-
0240)
4 F8 0A ENC blockade Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem and replace the ENC Confirm log messages
Unit. (TRBL 04-0100)
Replacement 2.2.9
Replacing ENC
Unit/SENC Unit (REP
02-0830)
4 F8 0B Loop failure Collect Simple trace and request the Technical Troubleshooting 7.3
4 F8 0C A path detachment occurred. Replace the LOOP.
*2 : The sense code is reported to the host only when WAR = 1 in the Mode Select command (page35 H ).

MSG 09-0160-01
Sense Sense
key code
4 F8 0D SATA Drive failure (regression) Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem and replace the Disk Confirm log messages
Drive. (TRBL 04-0100)
Replacement 2.2.1
(REP 02-0050)
4 F8 0E SENC failure Specify a part to be replaced by checking the log Troubleshooting 4.3
message of the subsystem and replace the ENC Confirm log messages
Unit/SENC Unit. (TRBL 04-0100)
Replacement 2.2.9
Replacing ENC
Unit/SENC Unit (REP
02-0830)
4 F8 F0 The controller of another system was blocked(*1). Get the CTL alarm trace of the detached Control Troubleshooting 7.4
Unit and replace the Control Unit. Collecting CTL Alarm
Trace (TRBL 07-
0080)
Refer to Replacement
2.2.5 Replacing
Control Unit (REP 02-
0390)
4 F8 F1 Host conector failure Collect Simple trace and request the Technical Troubleshooting 7.3
4 F9 00 Battery failure recovery(*1) This is not failure. If this error code frequently
4 F9 01 Fan failure recovery(*1) Technical Support Center to analyze the failure.
4 F9 02 DC failure recovery(*1)
4 F9 03 Drive failure (regression) recovery(*1)
4 F9 04 Pin data over recovery(*1)
4 F9 05 Module blockade release(*1)
4 F9 06 Own Controller recovery(*1)
4 F9 07 AC LINE/INBOX recovery
4 F9 08 UPS failure recovery
4 F9 09 Battery backup circuit failure recovery
4 F9 0A ENC failure recovery
4 F9 0B Loop failure recovery
4 F9 0C The path recovered from the detachment.

MSG 09-0170-01
Sense Sense
key code
4 F9 0D SATA Drive failure (regression) recovery This is not failure. If this error code frequently Troubleshooting 7.3
4 F9 0E SENC failure recovery appropriate section to analyze the failure. trace (TRBL 07-0040)
4 F9 F0 Another system Controller failure recovery
4 F9 F1 Host connector failure recovery
B FD 00 Command execution was disabled because the Collect Simple trace and request the appropriate
LU was switched. section to analyze the failure and take a measure.
B FD 01 The command execution was interrupted owing to
an LU switching.

MSG 09-0180-01
9.2 List of detail codes of sense code (05/9FFF)
Detail
Storage Navigator Modular indication Recovery methods Reference page
code
010001 DMED010001: The same host group name exists in a port. Check if the host group name that has been
Confirm the host group name and then try again. entered is correct.
010002 DMED010002: The same WWN name exists in a port. Check if the WWN nickname that has been
Confirm the WWN name and then try again. entered is correct.
010003 DMED010003: WWN cannot be assigned to an undefined Check if the host group name to which the
host group. Specify a defined host group and try again. WWN has been assigned is actually the same
as that to which you want to assign the WWN.
010004 DMED010004: The function cannot be executed because Disable the host group security of the LUN
host group security on some port is set to enabled. Set host Manager function for all ports, and then lock or
group security to disable on all ports and try again. disable the LUN Manager function.
020001 DMED020001: The value of Dirty Data Opportunity is Specify the trigger for de-staging dirty data as
outside the effective range. Specify the value in the effective one of integers ranging from 1 to 50 and
range and try again. smaller than a trigger for stopping the de-
staging of the dirty data.
020002 DMED020002: The value of Dirty Data Stop Opportunity is Specify the trigger for stopping the de-staging
outside the effective range. Specify the value in the effective of dirty data as one of integers ranging from 0
range and try again. to 49 and larger than a trigger for de-staging
the dirty data.
020003 DMED020003: The value of Dirty Data Opportunity is equal Specify the trigger for de-staging dirty data as
to or less than value of Dirty Data Stop Opportunity. Specify an integer larger than the trigger for stopping
the value and try again. the de-staging of the dirty data.
020004 DMED020004: Prefetch Starting Opportunity is outside the Specify the trigger for starting the pre-fetch as
effective range. Specify the value of effective range and try one of integers ranging from 0 to 100.
again.
020005 DMED020005: LU number is outside the effective range. Specify the default LUN of the performance
Specify the LU number of effective range and try again. tuning parameter as one of integers ranging
from 0 to 2047.
020006 DMED020006: Reserved Random Simple Buffer Size is Specify the size of the Reserved Random
outside the effective range. Specify the value of effective Simple Buffer as one of integers ranging from
range and try again. 0 to 100.
020007 DMED020007: The process failed due to an invalid Specify the size within the effective range.
parameter of Random Simple Buffer Size 0% Mode.
Confirm the specified parameter.
020008 DMED020008: Prefetch Count is outside the effective Specify the size within the effective range.
range. Specify the value in the effective range and try again.
020009 DMED020009: Prefetch Size is outside the effective range. Specify the size within the effective range.
Specify the value in the effective range and try again.
02000A DMED02000A: The process failed due to an invalid Specify the size within the effective range.
parameter of Next Prefetch Opportunity Mode. Confirm the
specified parameter.
020010 DMED020010: Count of Judgment Sequential is outside the Specify a value that falls within a valid range.
effective range. Specify the value in the effective range and
try again.
020011 DMED020011: Prefetch Size of Base is outside the effective Specify a value that falls within a valid range.
range. Specify the value in the effective range and try again.
020012 DMED020012: Prefetch Size of Fixed is outside the Specify a value that falls within a valid range.
effective range. Specify the value in the effective range and
try again.

MSG 09-0190-01
Detail
code
040001 DMED040001: The specified LUs contain Sub LU. Confirm When formatting the unified LU, specify the
the LU status and try again. Main LU.
050001 DMED050001: The process cannot be performed because The controller that controls the LU cannot be Troubleshooting
the specified LU is in a PIN exceeded state. Restore PIN changed because the number of pinned 6.1.11 A failure
data and try again. segments exceeded its threshold value. occurred during
Eliminate the pinned segments of the specified operation : Case 1
LU referring to the Troubleshooting 6.1.11 A (PIN over) (TRBL 06-
failure occurred during operation : Case 1 (PIN 0550)
over) and then change the controller that
controls the LU again.
050002 MED050002: The process cannot be performed because Perform the same operation again after waiting
cache segment is insufficient. Wait for a while and then try for a while.
again.
050003 DMED050003: The process cannot be performed because Perform the same operation again after waiting
the specified LU is receiving the Write command for a while.
continuously from the host. Wait for a while and then try
again.
050004 DMED050004: The process cannot be performed because Retry after eliminating the Turbo or reserved
the specified LU is a Cache Residency LU or a reserved Turbo LU.
one. Disable the LU, and then try again.
050005 DMED050005: The process cannot be performed because Check the partition number that was specified. Troubleshooting
the partition of necessary conditions for LU changing does Check if the capacity of the specified partition Chapter 6. Details of
not exist. Please confirm the partition definition and try is larger than that of the LU. Recovery Methods
again. Check if the segment size is the same. (TRBL 06-0000)
Retry after eliminating the pinned segment of
the specified LU or the partition to which the
switching was made referring to
Troubleshooting Chapter 6 Details of
Recovery Procedures.
050006 DMED050006: The process cannot be performed because Perform the operation again after determining
the directory configuration is changing. Please wait for a the Cache partition change (the re-start-up).
while and then try again.
050007 DMED050007: The process cannot be performed because Perform the operation again.
the LU change is in progress. Please wait for a while and
then try again.
050008 DMED050008: The process cannot be performed because Perform the operation again
the LU change is in progress. Please wait for a while and
then try again.
050009 DMED050009: The LU change could not be performed. Perform the same operation again after waiting
for a while.
05000A DMED05000A: The process cannot be performed because Perform the operation again
the controller is detached. Please recover the controller
status and then try again.

MSG 09-0200-01
Detail
code
070002 DMED700002: The specified IP address is incorrect. Please Set a correct IP address.
specify a right IP address
070006 DMED070006: When the ShadowImage pair of a S-VOL Turn off the ShadowImage I/O Switching mode
Switch status exists the ShadowImage I/O Switch Mode after the pair in the special PSUE status
cannot be disabled. Please retry after solving the error. disappears.
070007 DMED070007: The configuration of single or dual controller Perform the operation after invalidating or
system cannot be changed because Cache Partition locking the of Cache Partition Manager which
Manager is enabled. Please change Cache Partition is an onerous option.
Manager to locked or disabled and try again.
080001 DMED080001: The data pool cannot be used. Please Restart the disk array subsystem.
080005 DMED080005: The specified logical unit number is outside Specify an integer within the range of 0 to 2047
of the effective range. Specify the logical unit number within for the number of the LU to be assigned to the
the range and try again. data pool.
080006 DMED080006: The process cannot be performed because The status of the specified LU is neither normal
the specified logical unit is neither in normal nor in nor regressed. Correct the status of the
regressed state. Specify the logical unit of normal or specified LU, and then assign the LU to the
regressed state and try again. data pool.
080007 DMED080007: The process cannot be performed because Make sure of the RAID level of the specified
the RAID level or HDU combination of the specified logical LU and assign an LU, whose RAID level is
unit is not supported. Confirm the RAID level and the HDU other than RAID 0, to the data pool.
combination currently supported and try again.
080008 DMED080008: The process cannot be performed because The 64 LUs have been assigned to the data
the number of logical units in the data pool reached the pool. Make the assignment over again after
maximum. Delete the logical units in the data pool and then canceling the assignment of all the LUs to the
try again. data pool.
080009 DMED080009: The process cannot be performed because Dissolve the unification of the specified LU,
the specified logical unit is a unified LU. Separate the and then assign the LU to the data port.
08000A DMED08000A: The process cannot be performed because Split the specified LU from the ShadowImage
the specified logical unit is a part of ShadowImage pair. pair, and then assign it to the data pool.
Cancel the ShadowImage pair and try again.
08000B DMED08000B: The process cannot be performed because Split the specified LU from the TrueCopy pair,
the specified logical unit is a part of TrueCopy pair. Cancel and then assign it to the data pool.
the TrueCopy pair and try again.
08000C DMED08000C: The process cannot be performed because Release the specified LU from the command
the specified logical unit is a command device. Cancel the device, and then assign it to the data pool.
command device and try
08000D DMED08000D: The process cannot be performed because Restoration the specified LU, and then assign
the specified logical unit has been invalidated. Restore the it to the data pool.
08000E DMED08000E: The process cannot be performed because Split the specified LU from the Snapshot pair,
the specified logical unit is a part of Snapshot pair. Cancel and then assign it to the data pool.
the SnapShot pair and try again.

MSG 09-0210-01
Detail
code
080010 DMED080010: The process cannot be performed because The specified LU has already been assigned to
the specified logical unit is added to a data pool. Specify the data pool. Check the LU structure.
080012 DMED080012: The process cannot be performed because Change the controller that controls the
the owner controller is different between the specified specified LU, and then assign the LU to the
logical unit and the data pool. Confirm the logical unit owner data pool again.
controller and try again.
080016 DMED080016: The process cannot be performed because The size of the specified LU is too large.
the specified logical unit is not enough for sufficient cache Check the LU structure and specify an LU
blocks. Specify another logical unit and try again. whose size is appropriate and enables the LU
to be assigned to the data pool.
080017 DMED080017: The process cannot be performed because Check if the specified data pool is the one from
no logical units in data pool. which you want to eliminate all the Lus. Also
check whether all the Lus have already been
eliminated from it or not.
080018 DMED080018: The process cannot be performed because Perform the elimination after eliminating all the
the Snapshot pair exists in the specified data pool. Cancel Snapshot images.
the Snapshot pair and try again.
08001B DMED08001B: The specified threshold is outside of the Specify the threshold value for the data pool as
effective range. Specify the value of effective range and try an integer within a range of 50 to 80 %.
again.
08001D DMED08001D: The process cannot be performed because Invalidate the S-Vol disable mode and make
S-VOL mode of the specified logical unit is disabled. Set S- the setting again.
VOL mode to enable then try again.
08001F DMED08001F: The number of specified logical units is over Specify Lus less than the maximum number 64
64. Please specify the logical units in 64 or less. of the pool Lus.
080020 DMED080020: The process cannot be performed because Specify the LU on the drive of the same type
the drive type of specified logical unit is different from the and execute it again.
data pool. Please confirm the drive type and try again.
080021 DMED080021: The process cannot be performed because Release the Turbo LU of the LU specified for
the specified LU is a Cache Residency LU or a reserved the pool LU, and execute it again.
the specified LU is a Cache Residency LU or a reserved the pool LU, and execute it again.
080024 DMED080024: The process cannot be performed because Retry after setting the DM-LU.
DM-LU is not defined. Please define DM-LU and then try
again.
080025 DMED080025: The process cannot be performed because Retry after settling the cache partition change
the specified logical unit is reserved for cache partition (rebooting the subsystem).
modification. Please specify another logical unit and try
again.

MSG 09-0220-01
Detail
code
090001 DMED090001: The logical unit number of specified P-VOL Specify the LUN for the P-VOL as an integer
is outside of the effective range. Specify the logical unit within a range of 0 to 2047.
number of effective range and try again.
090003 DMED090003: The logical unit number of specified Specify the LUN for the Snapshot image as an
Snapshot image is outside of the effective range. Specify integer within a range of 0 to 2047.
the logical unit number of effective range and try again.
090006 DMED090006: The process cannot be performed because A status of the LU assigned to the P-VOL is
the specified logical unit of the P-VOL is neither in normal neither normal or regressed. Correct the status
nor in regressed state. Specify the logical unit of normal or of the LU, and then assign the LU to the P-
regressed state and try again. VOL.
090007 DMED090007: The process cannot be performed because Set the Snapshot image again after changing
no logical unit exists in the data pool by the side of the the Controller that controls the LU assigned to
controller of specified P-VOL. Add the logical unit to the the P-VOL.
data pool and try again.
090008 DMED090008: The process cannot be performed because Check the RAID level of the LU assigned to a
the RAID level or HDU combination of the specified logical P-Vol and specify an LU whose RAID level is
unit differs from the logical unit is not supported. Confirm the other than RAID 0.
RAID level and the HDU combination currently supported
and try again.
090009 DMED090009: The process cannot be performed because Check the structure of the Snapshot images,
the number of created Snapshot Image for the specified P- eliminate unnecessary ones of Snapshot
VOL has reached its maximum. Delete unnecessary images, and then retry.
Snapshot Image and try again.
09000A DMED09000A: The logical unit number has already been The specified LUN already exists. Check the
defined. Specify a new number. LU structure, and set the Snapshot image.
09000B DMED09000B: The process cannot be performed because Dissolve the unification of the LU assigned to
the specified P-VOL is a unified LU. Separate the unified LU the P-VOL, and then set the Snapshot image.
and try again.
09000C DMED09000C: The process cannot be performed because Split the LU assigned to the P-VOL from the
the specified P-VOL is a part of ShadowImage pair. Cancel ShadowImage pair, and then set the Snapshot
the ShadowImage pair and try again. image.
09000E DMED09000E: The process cannot be performed because Split the LU assigned to the P-VOL from the
the specified P-VOL is a part of Snapshot pair. Cancel the Snapshot pair, and then set the Snapshot
Copy-on-write Snapshot pair and try again. image.
09000F DMED09000F: The process cannot be performed because Release the LU assigned to the P-VOL from
the specified P-VOL is a command device. Cancel the the command device, and then set the
command device and try again. Snapshot image.
090010 DMED090010: The process cannot be performed because Set the Snapshot image after restoring the LU
the specified P-VOL is invalid. Restore the LU and try again. assigned to the P-VOL.
090011 DMED090011: The process cannot be performed because Check the LU structure and specify an LU that
the specified P-VOL has already been added to a data pool. has not been assigned to the data pool as the
Specify another LU number and try again. P-VOL.
090012 DMED090012: The process cannot be performed because A size of the LU assigned to the P-VOL is too
the specified P-VOL is not enough for sufficient cache large. Check the LU structure and specify an
capacity. Check cache capacity and try again. LU whose size is appropriate and enables the
LU to be assigned to the P-VOL.
090018 DMED090018: The process cannot be performed because Split the pair of the specified Snapshot image,
the specified Snapshot image has been creating the pair. and then perform the elimination again.
Cancel the SnapShot pair and try again.

MSG 09-0230-01
Detail
code
090019 DMED090019: The process cannot be performed because Eliminate the Snapshot image again after
P-VOL is under deletion. Wait for a while and then try again. waiting for a while.
09001B DMED09001B: The process cannot be performed because Check the number of pairs (number of P-Vols),
the number of Snapshot pair reached the maximum. Delete dissolve unnecessary pairs, and set the
unnecessary Snapshot pair(s) and try again. Snapshot image again.
09001C DMED09001C: The process cannot be performed because Specify a unified LU number of whose sub-LUs
the unified LU is composed of 17 or more sub logical units. is 16 or less.
Specify another logical unit and try again.
09001D DMED09001D: The process cannot be performed because Specify a unified LU consisting of main and
the unified LU contains a sub logical unit whose size is sub-LUs whose respective size is 1 Gbyte or
under 1GB. larger.
09001E DMED09001E: The process cannot be performed because Delete V-VOL after performing pairsplit-S when
a management area of Snapshot is shortage. Delete VOL, which is using the differential bit map, is
unnecessary Snapshot pair(s) and try again. a Snapshot pair.
Perform pairsplit-S when VOL, which is using
the differential bit map, is ShadowImage or
TrueCopy.
the specified LU is a Cache Residency LU or a reserved the P-VOL, and execute it again.
the specified LU is a Cache Residency LU or a reserved the P-VOL, and execute it again.
090022 DMED090022: The process cannot be performed because Execute it again after canceling the TrueCopy
the specified Snapshot image is a part of TrueCopy pair. pair.
Cancel the TrueCopy pair and try again.
090024 DMED090024: The process cannot be performed because Retry after settling the cache partition change
the P-VOL of specified Snapshot image is reserved for (rebooting the subsystem).
cache partition modification. Please retry after cache
partition modification is completed.
0A0001 DMED0A0001: The process cannot be performed because Specify a correct (valid) LU.
the specified LU is invalid. Restore the LU and try again.
the specified LU is a Sub LU of the unifying LUs. Separate
the unified LU and try again.
the specified LU is S-VOL of ShadowImage. Specify
the specified LU is S-VOL of TrueCopy. Specify another
the specified LU is Snapshot image. Specify another logical
unit and try again.
0A0006 DMED0A0006: The process cannot be performed in the Make the setting of the access level again after
retention term. The retention term expires and try again. canceling the setting of the retention period.
0A0007 DMED0A0007: The process cannot be performed because Make the setting of the access level again after
ShadowImage is in progress. Please wait a moment and the reverse resynchronization is completed.
then try again.

MSG 09-0240-01
Detail
code
0A0008 DMED0A0008: The process cannot be performed because Make the setting of the access level again after
Snapshot is in progress. Please wait a moment and then try the restore is completed.
again.
0A0009 DMED0A0009 : The retention term cannot be shortened. Make the setting of the access level again after
Specify the retention term is equal to or more than current specifying the correct retention period.
value and try again.
0A000A DMED0A000A : The process cannot be performed because Make the setting of the access level again after
expiration lock is enabled. Set expiration lock to disable and invalidating the Audit Lock.
try again.
0A000B DMED0A000B: The process cannot be performed because Specify the correct (enable) LU.
the status of ShadowImage pair is not SMPL or PSUS.
Please retry after changing the status of pair.
0A000C DMED0A000C: The process cannot be performed because Specify the correct (enable) LU.
the status of TrueCopy pair is not SMPL or PSUS. Please
retry after changing the status of pair.
0A000D DMED0A000D: The process cannot be performed because Specify the correct (enable) LU.
the status of Snapshot pair is not PSUS. Please retry after
changing the status of pair.
0B0001 DMED0B0001: The process cannot be performed because Make the Command device registration again
the access level is set up. Please change the attribute to after changing the access level to the normal
Read/Write and set S-VOL mode to enable, then try again. mode.
0C0001 DMED0C0001: The process cannot be performed because Make the integration of LU again after
the access level is set up. Please change the attribute to changing the access level to the normal mode.
Read/Write and set S-VOL mode to enable, then try again.
0C0002 DMED0C0002: The process cannot be performed because Make the separation of LU again after
0C0003 DMED0C0003: The unification cannot be performed Specify the LU on the drive of the same type
because the drive type is different. Please confirm the drive and execute it again.
type and try again.
0C0005 DMED0C0005: The process cannot be performed because The number of unified LUs cannot be more the
the unified LU reached the maximum. 128.
0C0006 DMED0C0006: The unification cannot be performed LUs that belongs to different partitions cannot
because the cache partition is different. Please confirm the be unified.
cache partition of the specified logical unit.
0C0007 DMED0C0007: The process cannot be performed because Perform the operation after fixing a partition to
the specified logical unit is reserved for cache partition which the logical unit belongs.
modification. Please retry after changing the cache partition,
or specify another logical unit.
0D0001 DMED0D0001: The process cannot be performed because Make the setting of Priced Optional Features
the access level is set up. Please change the attribute to again after changing the access level to the
Read/Write and set S-VOL mode to enable, then try again. normal mode.
0D0002 DMED0D0002: The process cannot be performed because Retry 180 days later.
the temporary key cannot be used for the next 180 days
after it is locked or expired.
0D0003 DMED0D0003: The specified function has already been The unlocking cannot be done with the
unlocked. temporary key.

MSG 09-0250-01
Detail
code
0E0001 DMED0E0001:The process cannot be performed because Execute the LU deletion again during LU
the access level is set up. Please change the attribute to deleting after changing the access level to the
Read/Write and set S-VOL mode to enable, then try again. normal mode.
Execute the V-VOL deletion again during V-
VOL deleting.
0F0001 DMED0F0001:The process cannot be performed because Make the delete of RAID group again after
0F0002 DMED0F0002: The process cannot be performed because Execute again by specifying the drive of the
the drives of Unit0 and the latter units are contained within same type.
the range of the specified RAID group.
0F0003 DMED0F0003: The process cannot be performed because Specify the drive for the subsystem concerned.
the non-supported drive on this subsystem are contained
within the range of the specified RAID group.
0F0004 DMED0F0004: The function cannot be used because it is Retry after opening or unlocking the key of
not installed, locked, or disabled. RAID 6.
0F0005 DMED0F0005: The process cannot be performed because Retry after specifying the RAID width as the
the number of drive is incorrect. Please confirm the number of installed drives.
mounted drive and try again.
0F0006 DMED0F0006: The RAID group is already defined in the Retry after specifying a number of a drive for
specified drive. Please specify another drive and try again. which a RAID group has not been defined.
0F0007 DMED0F0007: The number of defined RAID group reached No more RAID groups can be defined because
the maximum. Delete unnecessary RAID groups and then the number of defined RAID groups has
try again. reached the maximum.
100001 DMED100001: The process cannot be performed because Retry after changing the access level to the
the access level is set up. Please change the attribute to normal mode.
100005 DMED100005:The preparations of quick formatting are Retry after waiting for a while.
incomplete. Please retry after waiting for a while.
100006 DMED100006: The process cannot be performed because Execute the quick format after installing or
the specified logical unit contain an un-mounted drive or a normalizing the drive in the RAID Group
blocked drive. Confirm the drive status and try again. belonging to the specified LU.
100007 DMED100007: Format of the logical unit cannot be Execute the quick format after turning off the
performed under drive blockage mode. Please turn off the drive blockade mode of the system parameter.
drive blockade mode system parameter.
110001 DMED100001: The mapping mode cannot be changed When changing the mapping mode to OFF,
because the mapping guard LU exists. take all the LU mapping guards OFF.
110002 DMED100002: The mapping information cannot be changed Change the LU mapping after the LU mapping
because the mapping guard LU exists. guard is taken OFF.
120001 DMED120001: The specified drive cannot be defined as a Specify the drive for the subsystem concerned.
spare drive because it is not supported on this subsystem.
130001 DMED130001: The process cannot be performed because Set the time-out value after the path is defined.
the path is not set up.
140001 MED140001: The process cannot be performed because Unlock with the permanent key.
the term of the temporary key or emergency key is expired.
140002 DMED140002: The process cannot be performed because Retry after specifying an LU other than the
the DM-LU has already been set. Please cancel the DM-LU DM-LU.
and try again.

MSG 09-0260-01
Detail
code
150001 DMED150001: The process cannot be performed because Retry after returning the partition into the initial
the cache partition is not initial status. Please change the status.
cache partition to initial status and try again.
150004 DMED150004: The process cannot be performed because Change the partition size to an appropriate
the cache partition is less than minimum size. Please one.
confirm the cache partition size and try again.
150005 MED150005: The process cannot be performed because Troubleshooting
Retry after eliminating a pinned segment of the
the PIN is exceeded state. Please restore PIN data and try 6.1.11 A failure
specified LU referring to Troubleshooting
again. occurred during
6.1.11 A failure occurred during operation :
Case 1 (PIN over). operation : Case 1
(PIN over) (TRBL 06-
0550)
150006 DMED150006: The segment size of cache partition (0 or 1) A segment size of the master partition cannot
cannot be changed. be changed.
150007 DMED150007: The process cannot be performed because Retry after dissolving the pair.
ShadowImage is in use. Please cancel the ShadowImage
pair and try again.
150009 DMED150009: The process cannot be performed because Retry after dissolving the pair.
SnapShot is in use. Please cancel the SnapShot pair and
try again.
15000B DMED15000B: The process cannot be performed because Retry after eliminating the unwritten LU(s).
process of Write command from the hosts is not completed.
Please wait for a while and then try again, or delete the
logical unit.
15000C DMED15000C: The function cannot be executed because a Cancel the specification of the LU residence.
Cache Residency LU or a reserved one exists. Disable the
LU, and then try again.
15000D DMED15000D: The specified segment size is incorrect. Check the specified segment size.
Please confirm the segment size and try again.
15000E DMED15000E: The process cannot be performed because Retry after the change of the LU unit is
the LU change is in progress. Please wait a moment and try completed.
again.
15000F DMED15000F: The specified cache partition number is Specify Dir 0 for the partition #0 and Dir 1 for
incorrect. Please confirm the cache partition number and try the partition #1.
again.
150010 DMED150010: The controller of current cache partition Define the LU again after eliminating it.
cannot be changed. Please delete the cache partition, and
set up again.
150011 DMED150011: The process cannot be performed because Change the partition size to an appropriate
the total size of cache partition is over the cache capacity. one.
Please confirm the cache partition size and try again.
150012 DMED150012: The cache partition with which the logical Change the partition size to an appropriate
unit is set up, or the cache partition of 0 or 1 cannot be one.
deleted. Please confirm the cache partition number.
150013 DMED150013: The process cannot be performed because Specify a partition that exists.
the specified cache partition is not defined. Please specify a
defined cache partition and try again.

MSG 09-0270-01
Detail
code
160002 DMED160002: The process cannot be performed because A partition to which a sub-LU of a unified LU
the specified logical unit is a Sub LU of the unifying LUs. belongs cannot be changed.
Please separate the unified LU and try again.
160011 DMED160011: The logical unit cannot be allocated the Check a number of the specified partition.
specified cache partition. Please specify another cache A capacity of the partition is smaller than that
partition number and try again. of the LU.
160012 DMED160012: The process cannot be performed because Retry after unlocking the PP.
the Cache Partition Manager is not installed, locked, or
disabled.
170001 DMED170001: The process cannot be performed because Specify an LU whose capacity is 5 Gbytes or
the specified logical unit is capacity less than 5GB. Specify larger.
the logical unit is equal to or more than 5GB and try again.
170002 DMED170002: The process cannot be performed because Retry after specifying an LU whose RAID level
the specified logical unit is RAID level 0. Specify another is other than RAID 0.
170003 DMED170003: The process cannot be performed because Set the specified LU as an object of the
the specified logical unit is neither in normal nor in differential control after relieving it of command
regressed state. Specify the logical unit of normal or device.
regressed state and try again.
170004 DMED170004: The process cannot be performed because Specify an LU other than a unified LU.
the specified logical unit is a unified LU. Separate the
170005 DMED170005: The process cannot be performed because Specify an LU other than a Turbo LU (reserved
the specified LU is a Cache Residency LU or a reserved Turbo LU).
170006 DMED170006: The process cannot be performed because Specify an LU that is not a command device.
the specified logical unit is a command device. Cancel the
command device and try again.
180001 DMED180001: The specified logical unit cannot be set as Retry after specifying an LU that belongs to the
Cache Residency LU because its cache partition is not 0 or master partition or changing the specified LU
1. Please try again after changing a cache partition into 0 or to the master partition.
1, or specify the logical unit of the cache partition 0 or 1.
200002 DMED200002: This function is unsupported in the single- Review the system configuration.
controller system
200003 DMED200003: SnapShot cannot be unlocked because Enlarge the cache capacity. Replacement 2.2.6
Cache Partition Manager is enabled. Please change Cache Replacing Cache Unit
Partition Manager to locked or disabled and try again. (REP 02-0540)
200004 DMED200004: Cache Partition Manager cannot be Retry after executing a reboot.
unlocked because the subsystem is not restarted after
Snapshot is unlocked. Please restart the subsystem, and
then try again.

MSG 09-0280-01
Detail
code
300001 DMED300001: The serial number or equipment ID cannot Serial number or device ID changes are not
be changed because the path and pair information does not required.
exist.
300002 DMED300002: The serial number or equipment ID cannot Serial number or device ID changes are not
be changed because the path and pair information does not required.
exist.
300005 DMED300005: The specified serial number or equipment ID Specify the range between zero and nine.
is incorrect. Please specify it in 0-9.
300006 DMED300006: The specified serial number is incorrect. Specify the serial number for the other system.
Please specify a right serial number.
300007 DMED300007: The specified serial number is incorrect. Specify the serial number for the other system.
Please specify a right serial number.
300008 DMED300008: 0 is specified as 6 figures of low order of the Specify the serial number for the other system.
serial number. Please specify a right serial number.
300009 DMED300009: The same serial number as a self subsystem Specify the serial number for the other system.
is specified. Please specify the serial number of connected
subsystem.
30000A DMED30000A: The same equipment ID as a self subsystem Specify the equipment ID for the other system.
is specified. Please specify the equipment ID of connected
subsystem.
400001 DMED400001: The process cannot be performed because None (No forced parity correction is required.)
the specified logical units contain an unformatted LU.
Confirm the logical unit status and try again.
400002 DMED400002: The process cannot be performed because Retry it specifying a POOL LU.
the specified logical units contain V-VOL of Snapshot.
Confirm the logical unit status and try again.
400003 DMED400003: The process cannot be performed because None (No forced parity correction is required.)
some logical units are under quick formatting. Confirm the
logical unit status and try again.
400004 DMED400004: The process cannot be performed because Instruct again to make a parity correction
the specified logical units contain a Sub LU of the unifying specifying a parent LU of a unified LU.
LUs. Confirm the logical unit status and try again.
400006 DMED400006: The specified LUs contain regressed LU. Issue an instruction to make the parity
Confirm the LU status and try again. correction after the drive is recovered.
400007 DMED400007: The process cannot be performed because Instruct again to make a parity correction after
ShadowImage, TrueCopy, or Snapshot is in progress. forming and resynchronizing a pair.
Please wait a moment and then try again.
400008 DMED400008: The operation of 'start' or 'skip', and 'cancel' Give instructions to restore, skip, and abort
is specified at the same time. Confirm the operation and try separately.
again.
400009 DMED400009: The process cannot be performed because Retry it specifying a correct LU.
the specified logical units contain an undefined LU. Confirm
the logical unit status and try again.

MSG 09-0290-01
Detail
code
400011 DMED400011: The process cannot be performed because As to an LU for which the parity correction is
parity correction is not completed. Please try again, after it being made or standing by, instruct to wait for
is completed. the completion of the restoration or abort the
restoration.
As to an LU the restoration for which by means
of parity is undone or undone 2, instruct to skip
the restoration or make the parity correction
and wait for completion of the restoration.
Retry after performing the operation above.
400012 DMED400012: The process cannot be performed because Instruct to skip the restoration or make the
parity correction is not executed or is aborted. Please try parity correction and wait for completion of the
again, after it is completed. restoration.
400013 DMED400013: The process cannot be performed because Issue an instruction to make or skip the parity
parity correction is not completed. Please try again, after it correction and wait for completion of the
is completed. restoration.
parity correction is not completed. Please try again, after it correction and wait for completion of the
is completed. restoration.
parity correction is not executed or is aborted. Please try correction and wait for completion of the
again, after it is completed. restoration.
400021 DMED400021: The 'cancel' operation cannot be specified to Instruct to make a parity correction or skip the
the uncorrected logical units. Confirm the parity correction restoration.
400022 DMED400022: The 'start' operation cannot be specified to None (Only a skip can be instructed.)
the aborted logical units. Confirm the parity correction status
and try again.
400023 DMED400023: The 'cancel' operation cannot be specified to None (Only a skip can be instructed.)
the aborted logical units. Confirm the parity correction status
and try again.
400024 DMED400024: The 'start' operation cannot be specified to Instruct again to make the parity correction
the correcting logical units. Confirm the parity correction after an instruction to abort has been given.
400025 DMED400025: The 'skip' operation cannot be specified to Give an instruction to abort.
the correcting logical units. Confirm the parity correction
400026 DMED400026: The 'start' operation cannot be specified to Instruct again to make the parity correction
the waiting logical units. Confirm the parity correction status after an instruction to abort has been given.
and try again.
400027 DMED400027: The 'skip' operation cannot be specified to Instruct again to make the parity correction
the waiting logical units. Confirm the parity correction status after an instruction to abort has been given.
and try again.
400028 DMED400028: The 'cancel' operation cannot be specified to None (No instruction to abort is required.)
the skipped logical units. Confirm the parity correction status
and try again.
400029 DMED400029: The 'cancel' operation cannot be specified to None (No instruction to abort is required.)
the corrected logical units. Confirm the parity correction

MSG 09-0300-01
Detail
code
500001 DMED500001: The command device is not registered. Set up the command device.
Please register the command device and try again.
600001 DMED600001: The process cannot be performed because Specify the correct (enable) LU.
the specified LU is a Cache Residency LU or a reserved
700001 DMED700001: The specified logical unit is not defined. Specify the correct (enable) LU.
Specify a defined logical unit.
700002 DMED700002: The process cannot be performed because Specify the correct (enable) LU.
the status of pair is SMPL. Confirm the LU status and try
again.

MSG 09-0310-01
Chapter 10. ACE Tool Error Message

No. Message Description Recovery methods
101 Saved as X successfully. The saving of the configuration information file
succeeded.
x : File name
102 It has not been saved. The saving of the configuration information file Check the free capacity in the PC in
failed, or it was canceled. which the file is to be saved and
retry the saving.
103 Please select a proper file name. The reading of the configuration information Check the specification of the file
file failed. and retry the saving.
104 Loaded from X successfully. The reading of the configuration information
file succeeded.
x : File name
105 It has not been loaded. The reading of the configuration information Check the specification of the file
file failed, or it was canceled. and retry the saving.
106 The format of this file is different. The reading of the configuration information
file failed.
107 X already exists. Does it overwrite? The reading of the configuration information
file failed.
111 This model is not supported. The model not supported was read.
301 Please be sure to input one or more numerical In the window for entering the number of the Change the number to one or more
values into Fibre Unit. disk units, zero was entered as the number of and make the entry again.
the Fibre disk units.
302 It exceeds the maximum number of Units. In the window for entering the number of the Make the number of the disk units
disk units, a number larger than the maximum smaller than the maximum allowable
allowable one was entered. one and make the entry again.
304 One or more Units on the PATH0 are skipped. Disk units were set for Path 0 leaving an Set the disk units in regular order
empty space for one or more disk units. starting from the bottom without
305 One or more Units on the PATH1 are skipped. Disk units were set for Path 1 leaving an leaving an empty space.
empty space for one or more disk units.
306 More Units to PATH1 than PATH0 are installed. More disk units were set for Path 1 than those Check if the setting is correct.
for Path 0.
307 Two or more Units to PATH0 than PATH1 are The disk units set for Path 1 were more than
installed. those set for Path 0 by two or more.
308 It exceeds the number of Units which can be When the physical configuration was derived Check if the number of the disk units
carried on a rack. from the logical configuration, disk units more on each rack is correct.
than those mountable on a rack were set.
309 It is carried on the RackX exceeding the number When the logical configuration was derived
of maximum Units. from the physical configuration, disk units
more than those mountable on a rack were
set.
x : Rack number (1 - 3)
310 Please install SATA Unit by two Units. The FC disk units were set on and under the When setting the FC disk units on
one SATA disk unit. and under the SATA disk unit(s), set
the two SATA disk units.
311 It exceeds the number of Units which can be When the number of the disk units was Check if the setting is correct.
carried on a physical rack. entered, the number was larger than the
maximum allowable one.
329 Please install X Unit in the first Unit. When the physical configuration of the
DF700M/DF700S was made, the [OK] button
was pressed without specifying the first disk
unit.

MSG 10-0000-01
No. Message Description Recovery methods

501 Clear a logic composition figure? The Edit button of the physical configuration
diagram was pressed
502 Clear a physical composition figure? The Edit button of the logical configuration
diagram was pressed.
503 Please save before exit. Exit? The End button was pressed.
504 A logic composition figure is under edit. When the logical configuration diagram was
being made, the Edit button of the logical
configuration diagram was pressed.
505 A physical composition figure is under edit. When the physical configuration diagram was
being made, the Edit button of the physical
configuration diagram was pressed.
506 Clear a physical composition figure and a The Clear button was pressed.
physical composition figure?

MSG 10-0010-01
FE-95DF752-00
Replacement
Chapter 1. Before Starting Maintenance Work ................................................................. REP 01-0000
Chapter 2. Parts Replacement.......................................................................................... REP 02-0000
Chapter 3. Periodic Maintenance...................................................................................... REP 03-0000
Chapter 4. Maintenance Tools .......................................................................................... REP 04-0000
Chapter 5. Recycling......................................................................................................... REP 05-0000

REP 00-0000-01

REP 00-0010-01
Chapter 1. Before Starting Maintenance Work

This chapter explains procedures for replacing parts which is specified as maintenance parts
and identified as failed parts through troubleshooting, etc..
1.1 Before Starting Maintenance Work

1.1.1 Cautionary Notes
(1) Perform the powering on/off operation correctly.
The power supplying condition applicable to the parts replacement varies depending on the
part to be replaced. The powering on/off procedure also varies depending on the power
supplying condition.
Perform the powering on/off operation following the procedure specified for each part
replacement work. It is feared that user data is lost if the powering on/off operation is not
done following the procedure correctly.
Since the power supplying system is duplicated, operate AC Power Unit Switch of the both
systems when turning on/off the Power Unit.
CAUTION
y Do not disassemble or remodel parts for maintenance. Otherwise, a failure or a
serious accident may be caused. Be sure to replace parts in units of formally
defined maintenance part.
y When replacing the power supply, do it in haste after preparing a replacement
power supply and arranging cables, etc. so that they do not disturb the
replacement.
CAUTION
y When doing a hot replacement of a part, do not wear metallic accessories or a
watch so as to avoid an electric shock. Be careful not to touch any of live parts
with a screwdriver, etc.

REP 01-0000-01
(2) Notes when Unpacking, Installing or Removing the Parts

For installing or removing the parts, do not apply any shock as the precise parts are installed.
Be sure to wear a wrist strap connected to the chassis frame before starting the work and do
not take it off until it is finished.
For installing the Disk Drive, Control Unit, ENC Unit, or SENC Unit, support it as touching the
metal part at the side with the fingers of the hand that wears a wrist strap.
CAUTION
damage the parts.
electricity by touching the metal plate
Support a Disk Drive by touching its metal ENC Unit /SENC Unit
Disk Drive

Connect this to the metal part on the A wristband (Be sure to wear this before
frame of subsystem (rear face) starting maintenance.)
(3) Notes on cable routing

(a) Handling of cables placed on the installation floor
Protect the cables, which cannot be accommodated by the subsystem and thus laid on the
floor or cross a passage, with the cable protection duct.
For cables that relay between the subsystems, lay them on the floor and do not leave them
from the floor.

REP 01-0010-01
(b) Handling of under floor cables when the subsystem is installed on the free access floor.
Give extra lengths to cables routed under the floor and do not make them float in the air.
(c) Routing method
Give a room for routing as earthquake and the like are considered.
Give a room for routing not to disturb the part replacement for maintenance.
Make the AC cables apart from each other and when they should be adjacent, do not make
them in parallel but make them cross at right angle.
When using a cable protection duct, be careful not to damage or cut cables by catching
them.
(d) Hold the connector to insert or pull out a cable. If the cable part is pulled, it may cause a
failure.
(e) For connecting the FC I/F cable or the FC (ENC) cable, bend it with a long radius (not less
than 30mm) and do not give the load to the cable and the connector.
When restarting the subsystem, turn off the main switch (after the POWER LED lights off),
and then turn on the main switch after waiting for one minute or more.
(5) Note on completing the work
Close all the external covers when the work is completed.
(The cover is to maintain the performance of the subsystem (radio wave noise suppression and
others), so that be sure to keep all the external covers closed to operate the subsystem
normally.)
(7) When replacing a Disk Drive, Control Unit, Cache Unit, Interface Board, Backup Battery Unit, an
ENC Unit/SENC Unit, a Fan Assembly, and an Power Unit while an array unit is powered on,
replace those units 20 seconds or more after their respective failed units are removed.
(8) When replacing the Disk Drive, Control Unit, Cache Unit, Interface Board, Backup Battery Unit,
ENC Unit/SENC Unit, Fan Assembly, and Power Unit while the subsystem power is turned on,
complete the replacement within five minutes. Otherwise, a powering off (subsystem down)
may occur because of an abnormal temperature rise. Perform the part replacement in haste.
(9) When the Power Unit and another module fail at the same time, replace the Power Unit first,
duplicate the power supply again, and then replace the module. Otherwise, a powering off
(subsystem down) may occur because of an abnormal temperature rise.
(10) When inserting a component, do it completely to the end and quickly. If the insertion is made
incompletely or extremely slowly, it is possible that the recovery from the error fails.
(11) When an allowable time limit for part replacement is specified in the replacement procedure,
observe the time limit.
(12) With only the main switch power off, BS power supply is supplied. In this situation, do not
leave the components removed from the subsystem for a long time. Because of an abnormal
temperature, the power supply alarm can be given.
(13) Do not make the maintenance work when the READY LED (green) on the Front Bezel is blinking
at high speed. When it is high-speed blinking, the ENC/SENC firmware is being downloaded.
Make the maintenance work after making sure that the READY LED (green) lights on after the

REP 01-0020-01
1.1.2 Checking cache memory in the back-up state

Before turning off the power, be sure to check the state of the cache memory backup, and
perform the work in the state that the cache backup mode is canceled.
The Cache memory installed in the subsystem is controlled with a write-after method.
When the power is turned off, the subsystem automatically writes data in the Cache Unit left
unwritten onto the Disk Drive. This operation is called a destaging.
When process is completed, the POWER LED goes out and the power supplied to each section
installed is turned off.
However, when the destaging cannot be completed when the power is turned off owing to the
unexpected power failure or by the operation of the circuit breaker, the Cache Unit enters the
cache backup mode in which the power is supplied by the battery to secure the data.
If the backup is not done normally, configuration information may be lost and user data may
be destroyed.
Confirming state of the Cache Unit backup

You can confirm whether the subsystem is in the cache backup state by viewing the
indication of the CACHE POWER LED (green) on the Control Unit.
The state of the cache backup can be confirmed in the following procedure.
Confirm that the POWER LED on the front side of the

subsystem has gone out.
(Confirm the completion of the destaging process.)
Yes
Is the CACHE POWER LED on?
No
The cache backup mode has been canceled. The subsystem is in the cache backup mode.
(Data in the Cache Unit has been stored in the Disk (Data in the Cache Unit is not stored in the Disk Drive.)
Drive.)
Turn off the AC Power Unit Switch and cancel the cache
backup state according to the procedure explained on the
following page.
Control Unit #1
Control Unit #0
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Control Unit
Figure 1.1.1 Procedure for Confirming State of Cache Backup

REP 01-0030-01
Procedure for canceling the cache backup state of the Cache memory
Follow the powering off procedure shown below to cancel the cache backup state of the
Cache memory. The location of components referred to in the flow chart is shown in Figure
1.1.3 Indication Name (Rackmount Model) (REP 01-0050) and Figure 1.1.3.1 Indication
Name (Floor Model) (REP 01-0060).
START
Turn off the AC Power Unit No Did you do it three times? Yes
Switch of the subsystem.
Is the subsystem floor model Yes

(RKM/RKS+RKAJ+H2J)?
No Are two or more Disk Drives
Yes No
mounted on RKAJ?
Turn on the power unit switch of RKM/RKS,

Turn on the AC Power Unit and turn off the AC Power Unit Switch of
RKAJ.
Turn on the main switch. The powering off is not executed even if
the power is turned off when the ALARM
Yes LED is on.
Is the ALARM LED on?
(The state of the cache backup mode
No before the turning off of the main switch
Is the READY LED on? is succeeded.)
When it is high-speed blinking, No
wait up to 30/50minutes.
Yes The READY LED usually comes on Perform the process for the case where the
about three minutes later. CACHE POWER LED cannot be turned off.
(Refer Procedure for the process to be
performed when the CACHE POWER LED
Turn off the main switch. cannot be turned off (REP 01-0070).)
Yes Cache backup mode

Is the ALARM LED on?
No
Is the WARNING LED on?
No
Yes
Is the READY LED on?
No
Is the POWER LED on?
No
Is the CACHE POWER LED Yes Cache backup mode
on?
No Canceling a status of the cache backup.
Turn off the AC Power Unit

END
Figure 1.1.2 Procedure for Canceling the Cache Backup Mode of the Cache Memory

REP 01-0040-01
Control Unit CACHE POWER LED (green)

ALARM LED
WARNING LED LASER KLASSE 1
CLASS 1
LASER PRODUCT
Front Bezel READY LED

POWER LED AC Power Unit Switch
BUZZER OFF SW
Control Unit
Main switch Power Unit

(a) RKM/RKS
Front Bezel WARNING LED

Power Unit
(b) RKAJ
Front Bezel WARNING LED

Power Unit
(c) RKAJAT
Figure 1.1.3 Indication Name (Rackmount Model)

REP 01-0050-01
BUZZER OFF SW
AC Power Unit Switch
POWER LED Control Unit
READY LED Main switch
WARNING LED Control Unit
ALARM LED
Front Bezel
CACHE POWER LED

(green)
Power Unit
(a) Floor (RKM+H1J) Model
LASER KLASSE 1
LASER PRODUCT
CLASS 1
BUZZER OFF SW
POWER LED Control Unit
WARNING LED Main switch
Front Bezel POWER LED
READY LED
WARNING LED Power Unit
ALARM LED
AC Power Unit Switch
(b) Floor (RKM+RKAJ+H2J) Model

Figure 1.1.3.1 Indication Name (Floor Model)

REP 01-0060-01
Procedure for the process to be performed when the CACHE POWER LED cannot be turned off
Items to be informed or asked the customer before starting the work
Inform that user data in the cache memory will be lost owing to the replacement of the
Cache memory.
Ask whether backup data exists or not.
Ask whether it is permitted to erase user data entirely and restore it using users backup
data.
Inform that data recovery and verification will be required.
Effect
User data in the Cache memory which has not been written onto the Disk Drive will be lost
owing to the replacement of the Controller.
Processing procedures
Either of the two procedures is used; a procedure using the forced parity correction(1) or
that in which the data is entirely erased once, and then recovered.
(1) Procedure using the forced parity correction
It takes long times at the longest from start to completion of the process to execute the
forcible parity correction. (Refer to Table 1.1.1 Standard Time Required for the forced
parity correction or an LU Formatting (REP 01-0080))
The following describes standard time required for the forced parity correction.
RAID5 :nD+1P : 40+6n [minute](n=2-15)

RAID1+0 :nD+nD : 145n10,000/Rotational speed of the Disk Drive (min-1) [minute]
(n=1-8)
RAID1 :1D+1D : 14510,000/Rotational speed of the Disk Drive (min-1) [minute]
NOTE : The time is standard time required for the forced parity recovery per a RAID
group with 72GB Disk Drive.
The time change in proportion to the Disk Drive capacity.
The time required for the recovery process varies depending on the Disk Drive
capacity and number of rows.
The time decrease the ratio 1-2 of 10 depend on the kind of the Disk Drive.
1 : A process to ensure the Disk Drive data consistency which has been lost owing to a loss of cache data. It cannot
recover the data unwritten onto the Disk Drive completely when an error occurs, therefore, verification of user
data and restoration of backup data are necessary.

REP 01-0070-01
Table 1.1.1 Standard Time Required for the forced parity correction or an LU Formatting
Unit : min
Disk Drives(*3)
71.3 G byte 143.3 G byte 245.7 G byte 287.6 G byte 393.4 G byte
Item
LU formatting(*1) (*2) 5 Disk Drives RAID 5 (4D+1P) 35 70 305 140 440
16 Disk Drives RAID 5 (15D+1P) 115 245 975 465 1065
4 Disk Drives RAID 1+0 (2D+2D) 25 45 280 90 420
2 Disk Drives RAID 1 (1D+1D) 25 45 350 80 400
*1 : The time shown above is a general guideline of a recovery time for a case where no I/O operation is requested by a
host computer. If an I/O operation is requested by a host computer, the time becomes longer.
*2 : The time shown above is a general guideline of a formatting time when LUs are formatted one by one.
When two or more LUs (n LUs) are formatted in a multiplexed manner, the formatting time becomes shorter than n
times the time shown above.
(2) Procedure not using the forced parity correction

When the forced parity correction takes a long time depending on the system
configuration, it is faster to restore data using the backup data after erasing and
resetting configuration information than to do it by executing the procedure in (1).
NOTE : When not performing Forced Parity Correction, be sure to format the LU.
If formatting is not performed, parity consistency is lost and data inconsistency
may occur.

REP 01-0080-01
START
Replacing Control Unit.
Is the subsystem floor model Yes

(RKM/RKS+RKAJ+H2J)?
No
Yes Are two or more Disk Drives No
mounted on RKAJ?
Turn on the power unit switch of RKM/RKS, and turn off the
Turn on the all AC Power Unit Switch of the subsystem.
AC power unit switch of RKAJ.
When the WEB can be connected, connect it and make

sure that the message, W12000 User data lost:
MANUAL/TRC is displayed for the Information
Message. (Refer to WEB 2.5 Information
Message(WEB 02-0120).)
When WEB connection is not possible, make sure that
WARNING LED on Front Bezel blinks before the device
becomes ready.
Do you want to execute the Yes

forcible parity correction?
No
Make not a forced parity correction after the subsystem Make a forced parity correction after the
enters the Ready status. subsystem enters the Ready status.
(For the forced parity correction, refer to Troubleshooting (For the forced parity correction, refer to
[Recovery method-1] Making a forced parity correction
Troubleshooting [Recovery method-2] A
(TRBL 06-0110)
forced parity correction is not made (TRBL
06-0130)
END END
Figure 1.1.4 Procedure for the Process to be Performed when the BACK UP LED cannot be turned off

REP 01-0090-01
1.1.3 Procedure for making sure of model name and drive firmware of Disk Drive
When it is required to make sure of a model name and/or drive firmware of the Disk Drive in
the case of Disk Drive replacement, etc., make sure of them following the procedure shown
below.
(1) Displaying the reference window
To display the reference window, enter http://(IP address)/drvfirm in the [Address] of the
WEB browser.
In the case of the dual system configuration, enter an IP address of any one of the control
units. When the connection is made, the following window is displayed.
[Password].
(2) Displaying the list of model names and drive firmware revisions of Disk Drives click [Drive
Information] in the [Menu] of the [Drive Firmware Information].
List of model names and drive firmware revisions of

the Disk Drives.
Product ID : Disk Drive Model name.
Revision : Drive firmware revision.

REP 01-0100-01
(3) Making sure of a model name and drive firmware revision of the Disk Drive concerned
Since information on the Disk Drive concerned is displayed at the top of the list when the
position of the Disk Drive concerned is clicked, make sure of the model name and drive
firmware revision of the Disk Drive concerned. (The following figure shows an example in which
HDU-6 are selected.)
When the two or more Disk Drives concern, make sure of the necessary information by clicking
each position of them.

REP 01-0110-01
Chapter 2. Parts Replacement

2.1 Locations of Replacement Components
Floor model is installed on the floor in combination with the dedicated kit to RKM/RKAJ.
The RKAJAT has no floor model.
Check the installed parts and the power supply status at the time of replacement in Table
2.1.1 and replace the parts.
Table 2.2.1 Locations of the parts to be replaced and power supply status
Status of the
host/subsystem(*1)
No. Part name Part No. Model Reference section
With I/O Without I/O
On line On line Off line
1 Disk Drive (71.3 G bytes) 3272219-A DF-F700-AGF72 { { 2.2.1 Replacing
Disk Drive (143.3 G bytes) 3272219-C DF-F700-AGF146 { { Disk Drive (REP
Disk Drive (287.6 G bytes) 3272219-E DF-F700-AGF300 { { 02-0050)
Disk Drive (245.7 G bytes) (RKAJAT) 3272215-A DF-F700-ATE250R { {
Disk Drive (393.4 G bytes) (RKAJAT) 3272215-B DF-F700-ATE400R { {
2 Backup Battery Unit 3272172-B { { { 2.2.2 Replacing
Backup Battery Unit
(REP 02-0240)
3 Fan Assembly 3272172-C { { { 2.2.3 Replacing
Fan Assembly
(REP 02-0300)
Parts 4 Power Unit (RKM/RKS) 3272172-A { { { 2.2.4 Replacing
Power Unit (RKAJ) 3272170-A { { { Power Unit (REP
Power Unit (RKAJAT) 3272170-A { { { 02-0340)
5 Control Unit 3272218-A DF-F700-F1JM {(*2) {(*2) {(*3) 2.2.5 Replacing
3272218-B DF-F700-F1JS {(*2) {(*2) {(*3) Control Unit (REP
02-0390)
6 Cache Unit (1,024 M bytes) 3272218-F DF-F700-C1GJ {(*4) {(*4) { 2.2.6 Replacing
Cache Unit (REP
02-0540)
7 Interface Board (RKM) 3272218-C {(*4) {(*4) { 2.2.7 Replacing
Interface Board
(REP 02-0660)
*1 : The status definitions of the host and the subsystem are as shown below.
y With I/O: Status that there is I/O from the host
y Without I/O: Status that there is no I/O from the host
y Online: Status of the subsystem powering on
y Off-line: Status of the subsystem powering off
*2 : The power can be on as long as the Power Unit is duplicated.
*3 : When Web cannot be connected, Control Unit, which is powering off in the dual controller configuration, cannot
be replaced.
*4 : The power can be off if the Control Unit is duplicated.

REP 02-0000-01
Status of the
host/subsystem(*1)
No. Part name Part No. Model Reference section
With I/O Without I/O
On line On line Off-line
8 Host Connector (2 G bps) 3272218-G {(*2) {(*2) { 2.2.8 Replacing
Host Connector (4 G bps) 3272218-H {(*2) {(*2) { Host Connector
(REP 02-0770)
9 ENC Unit (RKAJ) 3272170-B { { { 2.2.9 Replacing
10 SENC Unit (RKAJAT) 3272170-C { { { ENC Unit/SENC
Unit (REP 02-0830)
11 ENC Cable (5 m) 3272185-K DF-F4064-K5B { { { 2.2.10 Replacing
ENC cable (REP
ENC Cable (1 m) 3272185-A { { {
02-0910)
12 Basic Chassis of Rack Mount Style 5523443-H DF-F700-RKM { 2.2.11 Replacing
Parts Basic Chassis of
5523443-G DF-F700-RKS { Rack Mount Style
(REP 02-0950)
13 Additional Chassis of Rack Mount Style 5523443-C DF-F700-RKAJ { 2.2.12 Replacing
Additional Chassis
5523443-D DF-F700-RKAJAT { of Rack Mount
Style (REP 02-
0990)
14 Remote Adapter 3274538-A DF-F700-VR4A {(*3) {(*3) { 2.2.13 Replacing
3274538-B DF-F700-VR4H (Hub) Remote Adapter
(REP 02-1030)
*1 : The status definitions of the host and the subsystem are as shown below.
y With I/O: Status that there is I/O from the host
y Without I/O: Status that there is no I/O from the host
y Online: Status of the subsystem powering on
y Off-line: Status of the subsystem powering off
*2 : The power can be off if the Control Unit is duplicated.
*3 : The power can be on as long as the Power Unit is duplicated.

REP 02-0010-01
2.1.1 Part Locations of Rackmount Model

U7 rack frame
Front view
RKM/RKS RKAJ
RKAJAT
Backup Battery Unit #0 Backup Battery Unit #1(*1) Disk Drive
Rear view
RKM/RKS RKAJ
Fan Assembly #0 Control Unit #1(*2) Fan Assembly #1 ENC Unit #0 ENC Unit #1
Power Unit #0 Control Unit #0(*2) Power Unit #1
RKM/RKS RKAJAT
Fan Assembly #0 Control Unit #1(*2) Fan Assembly #1 ENC Unit #0 ENC Unit #1

Power Unit #0 Control Unit #0(*2)
Power Unit #1
*2 : Cache Memory and Interface Board are installed in the Control Unit.
Figure 2.1.1 Replaceable Part Locations of Rackmount Model

REP 02-0020-01
2.1.2 Part Locations of Floor Model

(1) Floor (H1J) Model
Disk Drive
Fan Assembly #0
Power Unit #0
Backup Battery Unit #1(*1)
Control Unit #0(*2) Control Unit #1(*2)
Power Unit #1
Backup Battery Unit #0
Fan Assembly #1
RKM+H1J/RKS+H1J RKM+H1J/RKS+H1J

Figure 2.1.2 Replaceable Part Locations of Floor Model (H1J)

REP 02-0030-01
(2) Floor (H2J) Model

Fan Assembly #0
Disk Drive
Power Unit #0 ENC Unit #0
Control Unit #0(*2) Control Unit #1(*2)
Power Unit #1
ENC Unit #1
Fan Assembly #1
Floor (RKM/RKS+RKAJ+H2J) Model Floor (RKM/RKS+RKAJ+H2J) Model

Figure 2.1.3 Replaceable Part Locations of Floor Model (H2J)

REP 02-0040-01
2.2 Replacement of Components

The parts replacements here are illustrated using a rackmount model. For floor model, install
each part in the vertical position.
Where to install a component is shown in 2.1 Locations of Replacement Components (REP

02-0000).
2.2.1 Replacing Disk Drive

The replacement procedure for the disk drive differs depending on the spare disk setting,
RAIID configuration, data recovery setting mode, or the spare drive operation mode (1)
(variable or fixed).
Perform the replacement following the procedure shown below.
The Disk Drive is a precision machine that may have troubles because of electrostatic
discharge. Be sure to put on the wristband before star Sting work in order to protect Disk
Drives from electrostatic discharge.

A Disk Drive to be unpacked

and replaced for maintenance The clip side of wrist strap:
the frame of subsystem (rear
face)
Support a Disk Drive by touching

its metal part (metal plate) with
your fingers
1 : Spare Drive:Specify a way of the spare drive operation.

( Refer to System Parameter 4.2 (5) Setting of Restore Options (SYSPR 04-0120).)
Variable :When a failed drive is replaced, the new drive becomes a spare drive.
Fixed :The specified drive is fixed as a spare drive (conventional way).

REP 02-0050-01

The mounting position number of the Disk Drive is decided by the combination of the Disk
Drive number set to the device number (device ID).

RKAJ/RKAJAT.
The Disk Drive number is #0 to #14 from the left sequentially seen sideways (for the floor

Device ID setting
RKAJAT RKAJAT
Device ID is set as
#01.
RKAJ RKAJ Subsystem

The figure is a setting
example when the
basic subsystem is the
RKM.
RKM/RKS RKM/RKS
Red (ALARM) LED Green (ACTIVE) LED
Disk Drive
RKAJAT
RKAJ
RKM/RKS

REP 02-0060-01
(1) Replacing Disk Drive
CAUTION
damage the parts.
y Disk Drives are precision components.
y When you install a Disk Drive, support its metal part with your hand that has the
y For the system Disk Drives (Disk Drive #0 to #4 of RKM\RKS) regardless of the
data Disk Drives, the Spare Drives and the Disk Drives which do not configure
the RAID group, do not remove the Disk Drives #0 and #1 at the same time with
the subsystem power turned on.
y Do not remove these two at the same time for RKM/RKS on which only two Disk
Drives are mounted (Disk Drive #0 and #1).
Be careful of the subsystem down if removing them.
NOTE : y Back end LOOP automatic operation diagnosis is being executed, and
interrupt the maintenance work even of the diagnosis end, please when
I5Y000 Obstacle HDU search start is displayed on Information Message of
WEB. Please restart the maintenance work after confirming diagnosis end
message (I5Y100 Obstacle HDU search end). Please execute the maintenance
work according to the instruction when an abnormal device and another
trouble message have been generated the diagnosis and after the diagnosis
ends.
y When the buzzer sound rumbles in the maintenance work, back end LOOP
automatic operation diagnosis might be executed by another trouble
occurrence. Please reconfirm the state of the disk array device (device LED
and WEB, etc.) after the maintenance work is temporarily interrupted, and it
waits for one minute or more.

REP 02-0070-01

Power status during the
No. Restrictions RAID level Reference section
replacement
1 Replacement with the power y Replaceable only while power is The Spare Disk is set RAID 0(*1)
When the red (ALARM)
turned on on RAID 1, RAID 5, and LED on the disk drive
(hot replacement) y Complete the replacement RAID 1+0 to be replaced is on.
within five minutes. Otherwise, See (a-1) When the
a powering off may occur red (ALARM) LED on
because of an abnormal the Disk Drive to be
temperature rise. Perform the replaced is on. (REP
part replacement in haste. 02-0090).
y If the READY LED (green) on When the red (ALARM)
the Front Bezel is blinking at LED on the disk drive
high speed for the preventive to be replaced is off.
replacement work, do not make See (a-2) When the
the replacement because the red (ALARM) LED on
ENC/SENC firmware is being the Disk Drive to be
downloaded. Make the replaced is off. (REP
replacement after the LED 02-0130).
lights on. The Spare Disk is RAID 0(*1) See (b-3)
not set or there is no Replacement of Disk
Spare Disk that can Drive under RAID 0
be used configuration (REP
02-0180).
RAID 1, RAID 5, and When the red (ALARM)
RAID 1+0 LED on the disk drive
to be replaced is on.
See (b-1) Replacing
Disk Drive in RAID 1,
5, or 1+0 configuration
(When the red
(ALARM) LED is on)
(REP 02-0150).
When the red (ALARM)
LED on the disk drive
to be replaced is off.
See (b-2) Replacing a
Disk Drive in the RAID
1, 5, or RAID 1+0
configuration (REP
02-0170).
2 Replacement with the power Not applicable
turned off
*1 : Be sure to backup the user data before replacing a Disk Drive in RAID 0 configuration. When the set RAID group
and LU are deleted or formatted, related user data will be lost.
(A backing up and restoration of user data are operations to be performed by users.)
*2 : You can replace the Disk Drive using the procedure (a) for the case of RAID 0 with a Spare Disk only when the data
migration to the Spare Disk by means of the dynamic sparing has terminated normally.
When the data migration to the Spare Disk has failed, replace the Disk Drive using the procedure (b-2) for the case
of RAID 0 without Spare Disk.

REP 02-0080-01
If no Spare Disk is provided, go to (b).

(a) The Spare Disk is set
(a-1) When the red (ALARM) LED on the Disk Drive to be replaced is on.
START
Collect errors of simple trace, CTL y Collect errors of simple trace

alarm, and memory dump following refer to Troubleshooting 7.3 Collecting simple trace
the generated error message. (TRBL 07-0040).
Store the collected simple trace y CTL alarm trace
information in the USB memory. refer to Troubleshooting 7.4 Collecting CTL Alarm
Trace (TRBL 07-0080).
y memory dump
refer to Troubleshooting 7.5 Collecting Memory Dump
(TRBL 07-0130).
y Store the collected simple trace information in the USB
memory
refer to Troubleshooting 7.6 Storing simple trace
information in the USB memory (TRBL 07-0230).
Refer to Information Message on Refer to WEB 2.5 Information Message

WEB, and check to see that [W060xy (WEB 02-0120).
HDU alarm (Unit-x, HDU-y)] or
[W060AT SATA HDU alarm (Unit-x,
HDU-y)] is displayed.
Make sure of the state of the

Refer to WEB 2.5 Information Message
data restoration to the Spare
(WEB 02-0120).
Disk.
No
Is [I008xy Data recovery to spare
HDU (Unit-x, HDU-y)] displayed
(1) in the Information Message
on WEB ?
Yes
Follow the Information Message Refer to WEB 2.5 Information Message
on WEB for the maintenance. (WEB 02-0120)
For the blocked disk drive, is

[I1GG00 HDU changed to Refer to WEB 2.5 Information Message
spare(Unit-X,HDU-Y)] displayed (WEB 02-0120).
in the Information Message on
WEB, and is [W061XY Spare
HDU alarm(Unit-X,HDU-Y)] or
[W061AT SATA Spare HDU B To REP 02-0110
alarm (Unit-X,HDU-Y)] displayed
in the Warning Information on
WEB?
A To REP 02-0100
1 : It will take time until this message is displayed. Refer to Table 2.2.2 Standard Time Required for the Correction
copy or Copy back (REP 02-0230) for the standard of the time required.

REP 02-0090-01
From REP 02-0090

A
Removing the front bezel Refer to Installation 1.5 How to Open/Close Door or
Attach/Remove Front Bezel/Rear Cover of the Subsystem
(INST 01-0100)
Make sure that the Red (ALARM)
LED on the Disk Drive to replace is lit Refer to Figure 2.2.1 Disk Drive Mounting Location
and it is detached. (REP 02-0060).
Removing the Disk Drive. Refer to Figure 2.2.2.1 Removing the Disk Drive
(REP 02-0140).
Installing the new Disk Drive Refer to Figure 2.2.2.2 Installing the Disk Drive
Wait for more than 20 seconds, and (REP 02-0140).
then insert the replacement Disk Drive.
If the Disk Drive is inserted without
waiting for 20 seconds, it is possible
that the Disk Drive is not recovered
from the failure normally.
Refer to Figure 2.2.1 Disk Drive Mounting Location

Dose the Red (ALARM) LED of No (REP 02-0060).
the replaced Disk Drive goes out
(1)?
Yes Refer to WEB 2.5 Information Message

Is [I009xy Spare HDU recovered (WEB 02-0120).
(Unit-x, HDU-y)] displayed (2) in No
the Information Message on
WEB ?
Refer to the Information Message Refer to WEB 2.5 Information Message
Yes on WEB, and replace the new disk (WEB 02-0120).
drive again.
Is the WARN LED (orange) on Refer to Figure 2.2.1 Disk Drive Mounting Location
No (REP 02-0060).
the front side of the subsystem is
lighting off (3)?
Yes

Is the RDY LED (green) on the (REP 02-0060).
front side of the subsystem is on
No
off (1)?
The RDY LED (green) may blink at
high speed (up to 30/50 minutes). Refer to WEB 2.5 Information Message
Follow the Information Message
Yes on WEB for the maintenance. (WEB 02-0120).
Attaching the front bezel Refer to Installation 1.5 How to Open/Close Door or
(INST 01-0100)
END
1 : The red (ALARM) LED of the Disk Drive lights off within about five minutes after the Disk Drive is inserted.
2 : This message is displayed within about five minutes after the red (ALARM) LED of the Disk Drive lights off.
3 : When the WARN LED (orange) on the front side of RKM/RKS blinks, refer to WEB, and check to see that the WARN
LED turns off.

REP 02-0100-01
B From REP 02-0090
(INST 01-0100)
(REP 02-0140).

Dose the Red (ALARM) LED of
No (REP 02-0060).
(1)?
Yes
The data is restored automatically on Refer to the Information Message Refer to WEB 2.5 Information Message
the replaced Disk Drive. (2) (3) on WEB, and replace the new disk (WEB 02-0120).
drive again.
Is [I151xy Data recovery Refer to WEB 2.5 Information Message

No (WEB 02-0120).
completed] displayed (4) in the
Information Message on
WEB ?
Is [I007xy HDU recovered (Unit- Refer to WEB 2.5 Information Message
x, HDU-y)] or [I009xy Spare (WEB 02-0120).
No
HDU recovered (Unit-x, HDU-y)]
displayed (5) in the Information
Message on WEB ? Refer to the Information Message Refer to WEB 2.5 Information Message
on WEB, and replace the new disk (WEB 02-0120).
Yes drive again.
C To REP 02-0120
2 : In case of it is set to automatic recovery mode.
3 : Open the Unit screen in the Storage Navigator Modular. Double click the Disk Drive under recovery procedure
(indicated in yellow) in the Component Status Tag, then the progress of data recovery can be checked. (For detail,
5 : This message is displayed within about five minutes after "I151xy Data recovery completed" is displayed in the
"Information Message" on WEB.

REP 02-0110-01
C From REP 01-0110
Is the WARN LED (orange) on No Refer to Figure 2.2.1 Disk Drive Mounting Location
the front side of the subsystem is (REP 02-0060).
lighting off (1)?
Yes
Is the RDY LED (green) on the
front side of the subsystem is on Refer to Figure 2.2.1 Disk Drive Mounting Location
No (REP 02-0060).
off (1)?
high speed (up to 30/50 minutes). Follow the Information Message
on WEB for the maintenance.
Yes
(INST 01-0100)
END
LED turns off.

REP 02-0120-01
(a-2) When the red (ALARM) LED on the Disk Drive to be replaced is off.
START
Perform the dynamic sparing Refer to Troubleshooting 10.2.7 Drive Maintenance

for the Disk Drive to be replaced. (TRBL 10-0330).
Replace the Disk Drive Refer to (a-1) When the red (ALARM) LED on the disk
following the procedure (a-1). drive to be replaced is on. (REP 02-0090).
END

REP 02-0130-01
Disk Drive
Disk Drive
c
Stopper
Handle
c Pull the stopper at the upper part of the disk drive handle toward you to have the lock
off, tilt the handle toward you, and then remove the dummy (Disk Drive) by pulling it.
Figure 2.2.2.1 Removing the Disk Drive
Guide Rail
Disk Drive
d
Disk Drive e
Stopper Handle
Hook
c
Rectangular Hole
c Slide the disk drive following the guide rail to the direction of the arrow without adding
an impact.
d Push it in until it reaches the position where a hook of the handle can be entered into
the rectangular hole at the lower part of a frame on the front side of the disk array unit.
e Raise the stopper, which has been titled toward you, and then have the lock on by
pressing the stopper. (*1)
*1 : If the handle is raised in the state in which its hook cannot be entered into the rectangular hole, the Disk Drive
cannot be installed correctly because it runs into the frame of the disk array unit.
Figure 2.2.2.2 Installing the Disk Drive

REP 02-0140-01
(b) The Spare Disk is not set or there is no Spare Disk that can be used
(b-1) Replacing Disk Drive in RAID 1, 5, or 1+0 configuration
(When the red (ALARM) LED is on)
START

y memory dump
(TRBL 07-0130).
memory
Refer to Information Message on Refer to WEB 2.5 Information Message

WEB, and check to see that [W060xy (WEB 02-0120).
HDU alarm (Unit-x, HDU-y)] or
[W060AT SATA HDU alarm (Unit-x,
HDU-y)] is displayed.
(INST 01-0100)
B From REP 02-0160
(REP 02-0140).
A To REP 02-0160


REP 02-0150-01
From REP 02-0150

A

Dose the Red (ALARM) LED of
No (REP 02-0060).
(1)?
Yes
The data is restored automatically on Refer to the Information Message Refer to WEB 2.5 Information Message
the replaced Disk Drive. (2) (3) on WEB, and replace the new disk (WEB 02-0120).
drive again.
B To REP 02-0150
Is [I151xy Data recovery Refer to WEB 2.5 Information Message

completed] displayed (4) in the No (WEB 02-0120).
WEB ? Yes Follow the Information Message Refer to WEB 2.5 Information Message
on WEB for the maintenance. (WEB 02-0120).
Is [I007xy HDU recovered (Unit- Refer to WEB 2.5 Information Message

No (WEB 02-0120).
x, HDU-y)] displayed (5) in the
WEB ? Yes Refer to the Information Message Refer to WEB 2.5 Information Message
drive again.
B To REP 02-0150
the front side of the subsystem is No (REP 02-0060).
lighting off (6)?
Yes

off (1)? No (REP 02-0060).
high speed (up to 30/50 minutes). Follow the Information Message
on WEB for the maintenance.
Yes
(INST 01-0100)
END
5 : This message is displayed within about five minutes after "I151xy Data recovery completed" is displayed in the
"Information Message" on WEB.
LED turns off.

REP 02-0160-01
(b-2) Replacing a Disk Drive in the RAID 1, 5, or RAID 1+0 configuration

(when the red (ALARM) LED is off)
STAR
Detach the Disk Drive

Refer to Troubleshooting 10.2.7 Drive Maintenance
to be replaced forcibly.
(TRBL 10-0330).
Replace the Disk Drive

Refer to (b-1) Replacing Disk Drive in RAID 1, 5, or 1+0
following the procedure (b-1).
configuration (When the red (ALARM) LED is on)
(REP 02-0150).
END

REP 02-0170-01
(b-3) Replacement of Disk Drive under RAID 0 configuration
START

y memory dump
(TRBL 07-0130).
memory
Make a backup of user data.
Make sure whether the Disk Drive to Refer to WEB 2.5 Information Message
be replaced is blocked or not by (WEB 02-0120).
viewing the message of the WEB.
(INST 01-0100)
B
From REP 02-0190
(REP 02-0140).
A
To REP 02-0190

REP 02-0180-01
From REP 02-0180

A

Dose the Red (ALARM) LED of No (REP 02-0060).
(1)?
Yes
Refer to the Information Message Refer to WEB 2.5 Information Message
drive again.
B To REP 02-0180
the front side of the subsystem is No (REP 02-0060).
lighting off (2)?
Yes

No (REP 02-0060).
off (1)?
high speed (up to 30/50 minutes).
Format the LU. Refer to System Parameter 3.3 Setting of LU

(SYSPR 03-0140)
Restore the user data

using the backup data.
(INST 01-0100)
END
LED turns off.

REP 02-0190-01
(2) Disk Drive threshold

Errors counted in this subsystem and default threshold values are listed below.
The dynamic sparing functions when the error count threshold value is exceeded. After the
dynamic sparing operation is completed, the failed disk drive is detached.
Table 2.2.1 Error and threshold value
Threshold (Default) (Once/24 hours)
No. Kind of error The Spare Disk is set The Spare Disk is not set
FC SATA FC SATA
1 Disk mechanical error. (Recovered) 50 50 50 50
2 Disk mechanical error. (Un-recovered) 2 2 2 2
3 A Disk Drive failure that becomes a
factor to execute reassignment
y Disk medium error. (Recovered)
25 50 200 100
y Disk medium error. (Un-recovered)
y Collectable errors in online verify.
y Un-correctable errors in online verify.
4 Disk R/W error. (Recovered) 10 10 10 10
5 Disk R/W error. (Un-recovered) 2 2 2 2
6 Disk I/F error. (Recovered) 50 50 50 50
7 Disk I/F error. (Un-recovered) 2 2 2 2
8 Disk hardware error. (Recovered) 50 50 50 50
9 Disk hardware error. (Un-recovered) 2 2 2 2
10 Disk SCSI I/F error. (Recovered) 50 50 50 50
11 Disk SCSI I/F error. (Un-recovered) 2 2 2 2
There threshold values above can be referred to and updated from the Storage Navigator
Modular (1).
However, the recovered or un-recovered disk media errors and the correctable or
uncorrectable errors in online verify operations are count up together in the reassigned count,
so that the threshold value can be updated but it is not effective.
1 : For the details of the Storage Navigator Modular, refer to the Storage Navigator Modular (for GUI) Users Guide.

REP 02-0200-01
(3) Transition of WEB of spare recovery operation of the [Information Message]

When the recovery completes normally, the Information Message from the WEB (WEB 2.5
Information Message (WEB 02-0120)) change successively as shown below.
(a ) Data recover (Data recovery onto the Spare Disk when a disk blocked is detected)
W060xy HDU alarm / W060HH HDU alarm / W060AT SATA HDU alarm
: Data Disk blocked
I150xy Data recovery started / I150HH Data recovery started
: Start of data area recovery
I151xy Data recovery completed / I151HH Data recovery completed
: Completion of data area recovery
I008xy Data recovery to spare HDU / I008HH Data recovery to spare HDU
: Completion of recovery onto Spare
Disk
I1GG00 HDU changed to apare(Unit-x, HDU-y)
: The blocked data disk is changed to
the spare disk, and the spare disk
before the failure is changed to the
data disk. ( 1)
W061xy Spare HDU alarm(Unit-x, HDU-y) or W061AT SATA Spare HDU alarm(Unit-x, HDU-y)
: Spare Disk blocked( 1) ( 2)
(b) Data recover (Dynamic sparing from data disk to Spare Disk)
I15Axy Dynamic sparing start / I15AHH Dynamic sparing start
: Start of Dynamic sparing
: Start of disk recovery
: Completion of data recovery
I008xy Data recovery to spare HDU / I008HH Data recovery to spare HDU
: Completion of recovery onto Spare
Disk
I1GG00 HDU changed to apare(Unit-x, HDU-y)
: The blocked data disk is changed to
the spare disk, and the spare disk
before the failure is changed to the
data disk. ( 1)
W060xy HDU alarm / W060HH HDU alarm / W060AT SATA HDU alarm
: Data Disk blocked
W061xy Spare HDU alarm(Unit-x, HDU-y) or W061AT SATA Spare HDU alarm(Unit-x, HDU-y)
: Spare Disk blocked( 1) ( 4)
1 : This message is displayed after the drive restoration is completed only when the spare drive operation mode of
Configuration Settings - Restore Options of Storage Navigator Modular is set as variable (default value), and
the capacity and the number of rotations of the blocked disk drive and the data recovery destination spare drive
are matched.
2 : This message is displayed in the Warning Information.

REP 02-0210-01
3 : This message is displayed only when I1GG00 HDU changed to spare(Unit-x, HDU-y) is not displayed before this.
4 : This message is displayed only when I1GG00 HDU changed to spare(Unit-x, HDU-y) is displayed before this.

REP 02-0210-01
(c) Copy back

I140xy System copy started / I140HH System copy started
: Start of system area recovery(1)
I141xy System copy completed / I141HH System copy completed
: Completion of system area recovery(1)
: Start of data area recovery
: Completion of data area recovery
When the recovery terminates abnormally, whichever [I142xy System copy failed (Unit-x, HDU-
y)] or [I142HH System copy failed (Unit-x, HDU-y)] or [I152xy Data recover failed (Unit-x, HDU-y)]
or [I152HH Data recover failed (Unit-x, HDU-y)] is displayed. Take a recovery action following
the messages.
1 : This message is displayed only when replacing Disk Drive (#0 to #3) on the RKM/RKS.

REP 02-0220-01
(4) Confirming completion of data recovery or copy back

Select Information Message from the WEB (WEB 2.5 Information Message (WEB 02-0120))
and make sure that the data recovery is completed normally.
Table 2.2.2 Standard Time Required for the Correction copy or Copy back
Unit : min
Disk Drive(*2)
71.3 G byte 143.3 G byte 245.7 G byte 287.6 G byte 393.4 G byte
Item
Correction copy 5 Disk Drives RAID 5 (4D+1P) 30 60 190 90 285
(*1) 16 Disk Drives RAID 5 (15D+1P) 90 200 440 380 510
Copy back(*1) 5 Disk Drives RAID 5 (4D+1P) 25 60 185 95 285
16 Disk Drives RAID 5 (15D+1P) 30 65 190 105 275
*1 : The time shown above is a general guideline of a recovery time for a case where no I/O operation is
requested by a host computer. If an I/O operation is requested by a host computer, the time becomes
longer.

REP 02-0230-01
2.2.2 Replacing Backup Battery Unit

NOTE : There is only one Backup Battery Unit for the RKS. This Backup Battery Unit is
not installed in #1.
No. Power status during the replacement Restriction Reference section

1 Replacement with the power turned on y When the power is turned off during the Refer to (1) Procedure for
(hot replacement) replacement, user data on the cache that has not replacement with the power turned
(In the case of RKM/RKS) been written on a disk is not backed up because on (REP 02-0250).
the power is not supplied from the battery.
y Complete the replacement within ten minutes.
Otherwise, a powering off may occur because of
an abnormal temperature rise. Perform the part
replacement in haste.
y When replacing two Backup Battery Units at the
same time (replacing one Backup Battery Unit for
the RKS), the Cache is changed to the Write
Through mode and the R/W performance is
somewhat deteriorated, so that replace them
quickly.
y If the READY LED (green) on the Front Bezel is
blinking at high speed for the preventive
replacement work, do not make the replacement
because the ENC/SENC firmware is being
downloaded. Make the replacement after the
LED lights on.
2 Replacement with the power turned off Refer to (2) Procedure for
replacement with the power turned
off (REP 02-0270).
CAUTION
y A closed type nickel-hydrogen battery can cause an electric shock or explosion
if it is handled wrongly. Observe the following requirements for handling.
y Do not disassemble or remake the battery.
y Do not deform the battery.
y Do not connect plus and minus poles with a metallic article such as a wire.
y Do not reverse the connections of plus and minus poles.
y Do not peel off the covering tube.
y Do not connect the battery directly to the outlet.
y Do not connect the battery to anything other than this subsystem for
charging/discharging.
y Do not leave the battery in a hot place. Store it in a dark and cool place.
y Do not discard a used battery at the site where it was removed for
replacement.

REP 02-0240-01
(1) Procedure for replacement with the power turned on

(Refer to Figure 2.2.3 Replacing Backup Battery Unit (REP 02-0260).)
Collect errors of simple trace (Troubleshooting 7.3 Collecting simple trace (TRBL 07-0040)),
CTL alarm trace (Troubleshooting 7.4 Collecting CTL Alarm Trace (TRBL 07-0080)), and
memory dump (Troubleshooting 7.5 Collecting Memory Dump (TRBL 07-0130)) following the
generated error message, and then perform the replacement operation following the procedure
shown below.
(a) Remove the Front Bezel. (Installation 1.5 How to Open/Close Door or Attach/Remove Front
Bezel/Rear Cover of the Subsystem (INST 01-0100).)
(b) Turn off the battery switch of the Backup Battery Unit to be replaced.
(c) In the case of the RKM/RKS, shift the latch on the Battery Units to the Release position and
pull the Battery Unit toward you until the latch pin comes out (to release the Unit).
NOTE : Handle the Battery Unit carefully because its depth is shallow (150mm) and
weight is heavy (3.0kg).
(d) Take out the Battery Unit holding its main body by your both hands.
(e) Make sure that the Battery switch on the new Backup Battery Unit has been turned off.
(f) Wait for more than 20 seconds, and then insert the Backup Battery Unit in the specified location
in the subsystem to the position where it is completely fixed until latch moves to Lock side.
If the Backup Battery Unit is inserted without waiting for 20 seconds, it is possible that the
Backup Battery Unit is not recovered from the failure normally.
(g) Turn on the battery switch of the Backup Battery Unit.
(h) Keep the power on for six hours or longer to charge the battery. If Power Unit has not been
powered on for no less than six hours, the battery does not function well (It is charging when
READY LED (green) is blinking.).
(i ) Make sure that the READY LED (green) on the Backup Battery Unit is on.
Make sure that the RDY LED on the front side is on and the ALARM and WARN LEDs are off(1).
The RDY LED (green) on the front side may blink at high speed (up to 30/50 minutes).
(j) Refer to Information Message on WEB, and check to see that [I00300 Battery recovered] or
[I0030x Battery recovered (Battery-x)] is indicated. (Refer to WEB 2.5 Information Message
(WEB 02-0120).)
When this is indicated, the replacement of Backup Battery Unit has completed.
(k) Attach the front bezel.
(l) Dispose of recycling the battery in the removed Backup Battery Unit. For recycling, refer to
Chapter 5. Recycling (REP 05-0000).
1 : When the WARNING LED is blinking, refer to the WEB, and then check if the LED goes out.

REP 02-0250-01
Latch

READY LED
Battery switch
Figure 2.2.3 Replacing Backup Battery Unit

REP 02-0260-01
(2) Procedure for replacement with the power turned off

(Refer to Figure 2.2.3 Replacing Backup Battery Unit (REP 02-0260).)
Check the state of Device main switch at first.
y When main switch is on (2-1)
y When main switch is off (2-2)
(2-1) When main switch is on

Collect errors of simple trace (Troubleshooting 7.3 Collecting simple trace (TRBL 07-
0040)), CTL alarm trace (Troubleshooting 7.4 Collecting CTL Alarm Trace (TRBL 07-0080)),
and memory dump (Troubleshooting 7.5 Collecting Memory Dump (TRBL 07-0130))
following the generated error message, and then perform the replacement operation
following the procedure shown below.
(a) Turn off the main switch
(b) Check to see that PWR LED (green) on the Front Bezel turns off (POWER OFF).
If it does not go POWER OFF, connect the Maintenance PC to WEB (Refer to Troubleshooting
Chapter 3. Before Starting WEB Connection (TRBL 03-0000).), and analyze the cause of
failure.
(c) After turning off the main switch, check to see that CACHE POWER LED (green) on the
Controller is off.
NOTE : If the CACHE POWER LED (Green) is lit, it may be that some of the Cache
memory data has not been written into the disk. In this case, removing the
Control Unit may cause a loss of user data.
If the power has already been turned off, check that Cache memory is not in
the back-up state. (To check for the back-up state, refer to 1.1.2 Checking
(d) Turn off the AC Power Unit Switch of the both Power Units.
(e) Remove the Front Bezel. (Installation 1.5 How to Open/Close Door or Attach/Remove Front
(f) Turn off the battery switch of the Backup Battery Unit to be replaced.
(g) In the case of the RKM/RKS, shift the latch of the Battery Unit to the Release position and
pull out the unit toward you.
NOTE : Since the depth of a battery unit is as short as 150mm and it is as heavy as
about 3.0kg, please pull out carefully.
(h) Remove the Backup Battery Unit you holding the Backup Battery Unit main body.
(i) Make sure that the Battery switch on the new Backup Battery Unit has been turned off.
(j) Insert the Backup Battery Unit in the specified location in the subsystem to the position
where it is completely fixed until the latch moves to Lock side.

REP 02-0270-01
(k) Turn on the battery switch of the Backup Battery Unit.

(l) Turn on the AC Power Unit Switch of the both Power Units.
(m) Turn on the main switch.
(n) Keep the power on for six hours or longer to charge the battery. If Power Unit has not been
(o) Make sure that the READY LED (green) on the Backup Battery Unit is on.
(p) Make sure that the RDY LED on the front side is on and the ALARM and WARN LEDs are off(1).
(q) Refer to Information Message on WEB, and check to see that [I00300 Battery recovered] or
(WEB 02-0120).)
(r) Attach the Front Bezel.
(s) Recycle the removed battery. For the recycling procedure, refer to Chapter 5. Recycling
(REP 05-0000).

REP 02-0280-01
(2-2) When main switch is off

(a) Check that Cache memory is not in the back-up state. (To check for the back-up state, refer
to 1.1.2 Checking cache memory in the back-up state (REP 01-0030).)
If the memory is still being backed up, first release it from the back-up state, and then
replace the Control Unit.
(b) Turn off the AC Power Unit Switch of the both Power Units.
(c) Remove the Front Bezel. (Installation 1.5 How to Open/Close Door or Attach/Remove Front
(d) Turn off the battery switch of the Backup Battery Unit to be replaced.
(e) In the case of the RKM/RKS, shift the latch of the Battery Unit to the Release position and
pull out the unit toward you.
NOTE : Since the depth of a battery unit is as short as 150mm and it is as heavy as
about 3.0kg, please pull out carefully.
(f) Remove the Backup Battery Unit you holding the Backup Battery Unit main body.
(g) Make sure that the Battery switch on the new Backup Battery Unit has been turned off.
(h) Insert the Backup Battery Unit in the specified location in the subsystem to the position
where it is completely fixed until the latch moves to Lock side.
(i ) Turn on the battery switch of the Backup Battery Unit.
(j ) Turn on the AC Power Unit Switch of the both Power Units.
(k) Turn on the main switch.
(l) Keep the power on for six hours or longer to charge the battery. If Power Unit has not been
(m) Make sure that the READY LED (green) on the Backup Battery Unit is on.
(n) Make sure that the RDY LED on the front side is on and the ALARM and WARN LEDs are off(1).
(o) Refer to Information Message on WEB, and check to see that [I00300 Battery recovered] or
(WEB 02-0120).)
(p) Attach the Front Bezel.
(q) Recycle the removed battery. For the recycling procedure, refer to Chapter 5. Recycling
(REP 05-0000).

REP 02-0290-01
2.2.3 Replacing Fan Assembly
CAUTION
Since each fan is rotating with high-speed, be careful not to be caught by it.
CAUTION
The replacement of the component is restricted in time. This operation requires
referring to the manual. If the subsystem is left with this component removed
for more than 10 minutes, it will stop by detecting the thermal alarm.
When the CALM LED on the Control Unit is on while the ALM LED of the Fan
Assembly is on, be sure to solve the trouble of the Control Unit first.
When replacing the Fan Assembly, do it in haste after preparing a replacement
Fan Assembly and arranging cables, etc. so that they do not disturb the
replacement.
The same parts are used for both of the left and right (upper and lower) Fan Assemblies of the
RKM/RKS/RKAJ/RKAJAT. However, care should be taken when installing them because each
of them must face a peculiar direction (up or down, or left or right).

1 Replacement with the power turned on Complete the replacement within five minutes See (1) Procedure for replacement
(hot replacement) and restart the fans of the Fan Assembly to with the power turned on (REP 02-
rotate. Otherwise, a powering off may occur 0310)
because of an abnormal temperature rise.
Perform the part replacement in haste.
When the Power Unit and another module fail at
the same time, replace the Power Unit first.
Otherwise, a powering off may occur because of
an abnormal temperature rise.
If the READY LED (green) on the Front Bezel is
LED lights on.
The array subsystem becomes a planned
shutdown and the power supply is turned off, so
that, work so not to pull out two Fan Assemblies.
2 Replacement with the power turned off See (2) Procedure for replacement
with the power turned off (REP 02-
0330)

REP 02-0300-01

(Refer to Figure 2.2.5 Replacing Fan Assembly (REP 02-0320).)
shown below.
(a) Make sure that the ALM LED (red) on the Fan Assembly is on.
(b) Loosen the screw which is fixing the lever of the Fan Unit, open the lever, and move it forward.
(c) Remove the Fan Assembly by pulling it out holding its main body with your both hands.
(d) After waiting for longer than 20 seconds, and then insert the new Fan Unit into the specified
position in the subsystem, raise it by fitting the hook of the lever to the cutout of the
subsystem, and tighten it with the fixing screw. If the Fan Assembly is inserted without
waiting for 20 seconds, it is possible that the Fan Assembly is not recovered from the failure
normally.
NOTE : Do not catch a ENC cable, when the Fan Assembly for the inserted.
Place the same Fan Assembly in the right and left of the subsystem facing
them in the reverse direction.
(e) Make sure that the status of the ALM LED (red) on the Fan Assembly changes from on to off.
(f) Check if the fans of the mounted Fan Assembly are rotating.
(g) Make sure that the READY LED on the Front Bezel is on and the ALARM and WARNING LEDs are
off(1). The READY LED (green) on the Front Bezel may blink at high speed (up to 30/50
minutes).
(h) Refer to Information Message on WEB, and check to see that [I00500 FAN recovered (CTL-
Unit, FAN-x)] or [I005xy FAN recovered (Unit-x, FAN-y)] is indicated. (Refer to WEB 2.5
Information Message(WEB 02-0120).)
When this is indicated, the replacement of Fan Assembly has completed.
1 : When the WARNING LED of RKM/RKS is blinking, refer to the WEB, and then check if the LED goes out.

REP 02-0310-01
Fan Assembly #0
Fan Assembly #1
ALM LED Fixing screw
Lever
cutout
Figure 2.2.5 Replacing Fan Assembly

REP 02-0320-01

(Refer to Figure 2.2.5 Replacing Fan Assembly (REP 02-0320).)
Collect errors of simple trace (Troubleshooting 7.3 Collecting simple trace (TRBL 07-0040)), CTL
alarm trace (Troubleshooting 7.4 Collecting CTL Alarm Trace (TRBL 07-0080)), and memory
dump (Troubleshooting 7.5 Collecting Memory Dump (TRBL 07-0130)) following the generated
error message, and then perform the replacement operation following the procedure shown below.
(a) Turn off the main switch.
power, troubleshoot the failure by connecting to the WEB.
If the memory is still being backed up, first release it from the back-up state,
and then replace the Control Unit.
without turning off the AC Power Unit Switch .
(c) Loosen the screw which is fixing the lever of the Fan Unit, open the lever, and move it forward.
(d) Remove the Fan Assembly by pulling it out holding its main body with your both hands.
(e) Insert the new Fan Unit into the specified position in the subsystem, raise it by fitting the hook
NOTE : Do not catch a ENC cable, when the Fan Assembly for the inserted.
Place the same Fan Assembly in the right and left of the subsystem facing
them in the reverse direction.
(f) Turn on the AC Power Unit Switch of the both Power Units.
(g) Turn on the main switch.
Make sure that the status of the ALM LED (red) changes from on to off.
(h) Check if the fans of the mounted Fan Assembly are rotating.
(i) Make sure that the READY LED on the Front Bezel is on and the ALARM and WARNING LEDs are
minutes).
(j) Refer to Information Message on WEB, and check to see that [I00500 FAN recovered (CTL-
Unit, FAN-x)] or [I005xy FAN recovered (Unit-x, FAN-y)] is indicated. (Refer to WEB 2.5
Information Message(WEB 02-0120).)
When this is indicated, the replacement of Fan Assembly has completed.

REP 02-0330-01
2.2.4 Replacing Power Unit

The Power Units differ among the RKM/RKS, RKAJ and RKAJAT. Be careful not to install wrong
ones by checking their part model names.
CAUTION
The replacement of the component is restricted in time. This operation requires
referring to the manual. If the subsystem is left with this component removed for
more than 10 minutes, it will stop by detecting the thermal alarm.
When a trouble of the Power Unit is detected due to a trouble of the Fan
Assembly, the Power Unit does not need to be replaced.
When a trouble of the Power Unit is detected during replacement of the Fan
Assembly, pull out and then insert the Power Unit.
When replacing the Power Unit, do it in haste after preparing a replacement
Power Unit and arranging cables, etc. so that they do not disturb the
replacement.

1 Replacement with the power turned on Complete the replacement within five minutes. Refer to (1-1) Procedure for
(hot replacement) When the Power Unit and another module fail replacement with the power turned
at the same time, replace the Power Unit first. on (Be sure to perform the following
Otherwise, a powering off (subsystem down) operations (a) to (j) within 10
may occur because of an abnormal minutes.) (REP 02-0350)
temperature rise.
If the READY LED (green) on the Front Bezel
is blinking at high speed for the preventive
replacement work, do not make the
replacement because the ENC/SENC firmware
is being downloaded. Make the replacement
after the LED lights on.
When both of the two power supplies are required Refer to (1-1) Procedure for
to be replaced, be sure to replace each one of replacement with the power turned
them at a time, or replace them while the power is on (Be sure to perform the following
turned off. operations (a) to (j) within 10
minutes.) (REP 02-0350)
2 Replacement with the power turned off Refer to (1-2) Procedure for
off (REP 02-0370)

REP 02-0340-01
(1-1) Procedure for replacement with the power turned on (Be sure to perform the following
operations (a) to (j) within 10 minutes.)
(Refer to Figure 2.2.6 Replacing Power Unit (REP 02-0360).)
Store the collected simple trace information in the USB memory (refer to Troubleshooting
7.6 Storing simple trace information in the USB memory (TRBL 07-0230)).
(a) Make sure ALARM LED (Red) of the Power Unit to be replaced is on.
Make sure that READY LED (Green) of the Power Unit not to be replaced is on.
NOTE : When the ALARM LEDs of Power Unit of the both systems are on, replace the
Power Unit in the state in which the power is turned off.
(b) Turn on the AC Power Unit Switch of the Power Unit to be replaced.
(c) Disconnect all the power cables connected to the Power Unit to be replaced.
(d) Loosen the screw which is fixing the latch of the Power Unit, shift the latch (fixing screw) to
(e) Remove the Power Unit by pulling it out holding its main body with your both hands.
(f) Make sure that the AC Power Unit Switch of the new Power Unit is turned off.
(g) After waiting for 20 seconds or more, shift the latch (fixing screw) of the new Power Unit
(RKM/RKS) to the Release position, insert it slowly into the sheet metal slit part at the top of
the Power Unit, and then push it to the end.
If you insert the Power Unit without waiting for more than 20 seconds, Power Unit may not
be recovered.
NOTE : Do not catch a ENC cable, when the AC Power Unit for the inserted.
(h) Connect all the removed cables.

(i) Turn on the AC Power Unit Switch of the installed Power Unit.
Make sure that the READY LED (green) of the Power Unit is on.
(j) Make sure that the WARNING LED (orange) on the Front Bezel gone out(1).
(k) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
the Front Bezel may blink at high speed (up to 30/50 minutes).
(l) Refer to Information Message on WEB, and check to see that [I006xy PS recovered (Unit-x,
PS-y)] is indicated. (Refer to WEB 2.5 Information Message(WEB 02-0120).)
When this is indicated, the replacement of Power Unit has completed.

REP 02-0350-01
READY LED
ALARM LED
Lock
Release
AC Power Unit Latch

Power Unit #1
Power Unit #0
Handle
(a) RKM/RKS
Latch
Lock
Release
AC Power Unit
Switch
Power Unit #1
Power Unit #0
Handle
(b) RKAJ/RKAJAT
Figure 2.2.6 Replacing Power Unit

REP 02-0360-01
(1-2) Procedure for replacement with the power turned off

(Refer to Figure 2.2.6 Replacing Power Unit (REP 02-0360).)
(c) Remove the all cables connected to the Power Unit to be replaced.
(d) Loosen the screw which is fixing the latch of the Power Unit, shift the latch (fixing screw) to
(e) Remove the Power Unit by pulling it out holding its main body with your both hands.
(f) Make sure that the AC Power Unit Switch on the Power Unit is off.
(g) Shift the latch (fixing screw) of the new Power Unit (RKM/RKS) to the Release position, insert
it slowly into the sheet metal slit part at the top of the Power Unit, and then push it to the
end.
NOTE : Do not catch a ENC cable, when the AC Power Unit for the inserted.
(h) Connect the all cables as they were before.

(i ) Turn on the AC Power Unit Switch of the both Power Units, and then turn on the main switch.
Make sure that the READY LEDs (green) of the both Power Units are on.
(j) Make sure that the WARNING LED (orange) on the Front Bezel has gone out(1).
(k) When the remote adapter is connected, make sure that the LED of the Remote Adapter
connected is on.

REP 02-0370-01
(l) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(m) Refer to Information Message on WEB, and check to see that [I006xy PS recovered (Unit-x,
PS-y)] is indicated. (Refer to WEB 2.5 Information Message(WEB 02-0120).)
When this is indicated, the replacement of Power Unit has completed.

REP 02-0380-01
2.2.5 Replacing Control Unit
CAUTION
care.
CAUTION
damage the parts.


the frame of subsystem (rear face)


REP 02-0390-01

1 Replacement with the power turned on 1. Complete the replacement within five minutes. When the CALM LED is on
(hot replacement) Otherwise, a powering off may occur because of In the case of the RKM/RKS :
an abnormal temperature rise. Perform the part See (1-1) When the CALM LED
replacement in haste. or EALM LED of the RKM/RKS
2. The procedure varies depending on whether the is on (REP 02-0410).
CALM LED or EALM LED is on or off. When the CALM LED is off
3. Replace the Control Unit after blocking the (Preventive replacement)
Control Unit to be replaced. In the case of the RKM/RKS :
4. When replacing Control Unit of both systems See (1-2) When the CALM LED
(CTL 0 and CTL 1), power off the subsystem or EALM LED of the RKM/RKS
before the replacement. is off (REP 02-0460).
5. In the case of the single Controller configuration,
perform the replacement after turning off the
power.
6. In the case of Preventive replacement, there
may be an error report in the host computer
depending on the operating conditions of the
host computer.
The prior contact to the customer is required.
7. If the READY LED (green) on the Front Bezel is
LED lights on.
2 Replacement with the power turned off In the case of the RKM/RKS : See
(2) Procedure for replacement
with the power turned off (REP
02-0500).
3 Replacement to be made with the power Make the replacement after getting a permission of In the case of the RKM/RKS : See
turned off (with the cache memory data the Technical Support Center because user data in (3) Procedure for replacement
volatilized forcibly) the cache will be lost. with the power turned off (with the
cache memory data volatilized
forcibly) (REP 02-0520).

REP 02-0400-01
(1) Procedure for replacement with the power turned on (for the case of the dual Controller
configuration only)
(1-1) When the CALM LED or EALM LED of the RKM/RKS is on
(Refer to Figure 2.2.7 Control Unit replacement and LED locations (RKS) (REP 02-0440)
and Figure 2.2.7.1 Control Unit replacement and LED locations (RKM) (REP 02-0450).)
NOTE : Do not replace the Control Unit which operates normally.

Before replacing the Control Unit, confirm that it is the CALM LED (RED) or
EALM LED (RED) in on.
When replacing the Control Unit while the subsystem power is turned on, be
sure to replace them one by one. When replacing the Control Unit of the
both systems (Control Unit#0 and Control Unit#1) at the same time, follow the
procedure explained in (2) Procedure for replacement with the power
turned off (REP 02-0500).
System parameters are automatically loaded to the new Control Unit from the
built in Disk Drive. Accordingly no setting, such as operating manually is
required.
When the Control Unit is replaced while the LU of the subsystem is being
formatted, restoration of the Control Unit which is inserted may be delayed
until the LU formatting is completed.
(a) Make sure that the CALM LED (RED) or EALM LED (RED) on the Control Unit to be replaced is on.
(b) Connect OUT (J100-J10x) of the remote adaptor in the final steps and the connector (REMOTE
ADAPTER) of the Control Unit are connected with the remote cable (VRCx) when the remote
adaptor is connected. Check that the LED of the connected remote adaptor lights on when
the remote cable has already been connected. Next, remove the remote cable connected to
the Control Unit to be replaced is installed.
(c) Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down the

REP 02-0410-01
(d) Remove the all cables connected to the Control Unit. (When the Additional Chassis of Rack
Mount Style is connected, disconnect the ENC cable also.)
CAUTION
care.
(e) Remove the Control Unit by pulling it out toward you.

(f) Remove the Host Connector for the RKS.
(g) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the
(h) Remove the Cache Unit mounted on the Control Unit.
Push the slot levers which fix the Cache Unit, and pull up the Cache Unit by holding both the
end of the Cache Unit, and then the cache memory can be removed.
NOTE : Place the removed Cache Unit temporarily in the place where the anti-static
measures are taken.
(i) In the case of RKM, Remove the Interface Board mounted on the Control Unit.
Remove the fixing screws (five places) fastening the Interface Board and the Control Unit.
(Loosen two screws on the front side.)
Pull up the Interface Board and remove it from the Control Unit.
(j) Loosen the fixing screw for the cover at the back of the cover of the new Control Unit, slide
the cover in the direction shown by the arrow (), and remove it.
(k) Be sure to install the removed Cache memory in the position with the same slot number as
before in the new Control Unit.
(l) Install the removed Interface Board in the Control Unit fitting it to the positioning pin, and
tightening five screws.
At this time, check that the connectors are surely inserted.
(m) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
(n) Install the removed Host Connector in the new Control Unit for the RKS.
(o) Make sure that 20 seconds or longer has elapsed after the Control Unit was taken out.
(p) When the RKAJ/RKAJAT is connected, connect the ENC cable. When the RKAJ/RKAJAT is not
connected, go to Step (q).
NOTE : When the RKAJ/RKAJAT is connected, the loop is not recovered and the
Control Unit fails again unless the Control Unit is inserted in the state in
which the ENC cable is connected.

REP 02-0420-01
(q) Insert it into the specified position with the both right and left levers of the Control Unit
CALM LED and EALM LED of newly installed Control Unit turn on, then EALM LED turns off and
CALM LED turns off next.
If the Control Unit is inserted without waiting for 20 seconds, it is possible that the Control
Unit is not recovered from the failure normally.
When it is not recovered even if ten minutes or more elapsed, perform the dummy
replacement(1) of the Control Unit which was inserted.
When the Control Unit is not recovered (ten minutes or more elapsed) even if I1G300 CTL
recovery start is displayed in the Information Message of WEB after the dummy
replacement, perform the dummy replacement of the Control Unit which was inserted, again.
When it is not recovered after another ten minutes, service personnel connects it to the WEB
and takes recovery actions according to "Information Message" on WEB.
(There may be a problem on the Control Unit or the cache memories installed.)
But, when any messages are displayed on WEB about the Control Unit or the cache memories
installed, then service personnel connects the other Control Unit to the WEB and takes
recovery actions according to "Information Message" in the other Control Unit.
When pushing the levers at the same time in the direction shown by the
arrows (), perform this operation within one minute. If it has taken
more than one minute to perform the operation, it may not be recovered. In
this case, execute the replacement procedure again. Nevertheless, if it is
not recovered, perform the Control Unit replacement since the failure may be
caused in the Control Unit.
(r) Make sure that the WARNING LED (orange) on the Front Bezel is off(2).
(The Control Unit usually recovers in about three (3) minutes, but if the I/O load from the
host computer is high, it may take three (3) minutes or more to recover.)
(s) Connect the removed all cables to the Control Unit.
(t) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(u) Refer to Information Message on WEB, and check to see that [I0010x CTL recovered (CTL-x)] is
indicated. (Refer to WEB 2.5 Information Message(WEB 02-0120).)
When this is indicated, the replacement of Control Unit has completed.
(v) Check that the LED of the remote adaptor connected to the Control Unit is installed lights on
when the remote adaptor is connected.

REP 02-0430-01
Control Unit #0
Cover
Control Unit #1
Fixing screw
Lever Slot lever Removal :

Socket memory by holding the both end
by hand.
Cut Installation :
cutout inside the slot push it into the slot by holding the
both end by hand.
Control Unit #1
LASER PRODUCT
CLASS 1
LASER KLASSE 1
REMOTE ADAPTER
REMOTE ADAPTER
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0A-0 EALM LED (red) Control Unit #0

PATH #0 PATH #1
CALM LED (red)
Figure 2.2.7 Control Unit replacement and LED locations (RKS)

REP 02-0440-01
Control Unit #0
Cover
Positioning hole
Interface Board
Fixing screw
Control Unit #1
Positioning pin
Lever Slot lever (five screws)
Fixing screw
Removal :
Press open the slot lever to
Socket
Cut memory by holding the both end
by hand.
cutout Projections Installation :
slot #1 slot #0 inside the slot Fit the projection and the cut and
both end by hand.
LASER PRODUCT
CLASS 1
LASER KLASSE 1
REMOTE ADAPTER
REMOTE ADAPTER
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0B-0 EALM LED (red) Control Unit #0

PATH #0 PATH #1
CALM LED (red)
Figure 2.2.7.1 Control Unit replacement and LED locations (RKM)

REP 02-0450-01
(1-2) When the CALM LED or EALM LED of the RKM/RKS is off
(Refer to Figure 2.2.7 Control Unit replacement and LED locations (RKS) (REP 02-0440)
and Figure 2.2.7.1 Control Unit replacement and LED locations (RKM) (REP 02-0450).)
NOTE : When replacing the Control Unit while the subsystem power is turned on, be
sure to replace them one by one. When replacing the Control Unit of the
both systems (Control Unit #0 and Control Unit #1) at the same time, follow
the procedure explained in (2) Procedure for replacement with the power
built in Disk Drive. Accordingly no setting, such as operating manually, is
required.
There may be an error report in the host computer depending on the
operating conditions of the host computer.
(a) For preventive detaching of the Control Unit, press RST SW.
mm in diameter).
Make sure that the CALM LED (red) or EALM LED (red) turns on within one second and the
WARNING LED (orange) on the Front Bezel blinks.
ADAPTER) of the Control Unit are connected with the remote cable (VRCx) when the remote
adaptor is connected. Check that the LED of the connected remote adaptor lights on when
the remote cable has already been connected. Next, remove the remote cable connected to
the Control Unit to be replaced is installed.
(d) Remove the all cables connected to the Control Unit that was blocked for prevention against
a failure. (When the Additional Chassis of Rack Mount Style is connected, disconnect the ENC
cable also.)
CAUTION
care.

(f) Remove the Host Connector for the RKS.

REP 02-0460-01
(g) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the
(h) Remove the Cache Unit mounted on the Control Unit.
NOTE : Place the removed Interface Board and Cache Unit temporarily in the place
where the anti-static measures are taken.
(i) In the case of RKM, Remove the Interface Board mounted on the Control Unit.
(j) Loosen the fixing screw for the cover at the back of the cover of the new Control Unit, slide
(k) Be sure to install the removed Cache memory in the position with the same slot number as
(l) Install the removed Interface Board in the Control Unit fitting it to the positioning pin, and
(m) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
(n) Install the removed Host Connector in the new Control Unit for the RKS.
(o) When the RKAJ/RKAJAT is connected, connect the ENC cable. When the RKAJ/RKAJAT is not
connected, go to Step (p).

REP 02-0470-01
(p) Wait for more than 20 seconds, and then insert it into the specified position with the both
right and left levers of the Control Unit pushed down, raise the levers with the hooks fitting
to the cutouts of the subsystem, and tighten the fixing screw for the lever.
recovery start is displayed in the Information Message of WEB after the dummy
replacement, perform the dummy replacement of the Control Unit which was inserted, again.
When pushing the levers at the same time in the direction shown by the
arrows (), perform this operation within one minute. If it has taken
more than one minute to perform the operation, it may not be recovered. In
this case, execute the replacement procedure again. Nevertheless, if it is
not recovered, perform the Control Unit replacement since the failure may be
caused in the Control Unit.

REP 02-0480-01
(q) Make sure that the WARNING LED (orange) on the Front Bezel is off(1).
If WARNING LED (orange) is on, replace the Control Unit again.
If WARNING LED (orange) is blinking, make sure WARNING LED (orange) goes off by referring
to WEB.
(r) Connect the removed all cables to the Control Unit.
(s) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(t) Refer to Information Message on WEB, and check to see that [I0010x CTL recovered (CTL-x)] is
(u) Check that the LED of the remote adaptor connected to the Control Unit is installed lights on
when the remote adaptor is connected.

REP 02-0490-01

shown below.
Store the collected simple trace information in the USB memory (refer to Troubleshooting 7.6
Storing simple trace information in the USB memory (TRBL 07-0230)).
(a) Confirm the installation location of the Control Unit whose CALM LED is on.
(b) Turn off the main switch.
(c) Turn off the AC Power Unit Switch of the both Power Units.
(d) Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down the
(e) Remove the all cables connected to the Control Unit.
CAUTION
care.
(f) Remove the Control Unit by pulling it out toward you.

(g) Remove the Host Connector for the RKS.

REP 02-0500-01
(h) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the
(i) Remove the Cache Unit mounted on the Control Unit.
NOTE : Place the removed Interface Board and Cache Unit temporarily in the place
where the anti-static measures are taken.
(j) In the case of RKM, Remove the Interface Board mounted on the Control Unit.
(k) Loosen the fixing screw for the cover at the back of the cover of the new Control Unit, slide
(l) Be sure to install the removed Cache memory in the position with the same slot number as
(m) Install the removed Interface Board in the Control Unit fitting it to the positioning pin, and
(n) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
(o) Install the removed Host Connector in the new Control Unit for the RKS.
(p) Insert it into the specified position with the both right and left levers of the Control Unit
If the Control Unit is caught by something when it is inserted, do not push it in forcibly.
Retry the insertion from the beginning. If forced, pins might be broken.
(q) Connect the removed all cables to the Control Unit.
NOTE : The installed direction is different in the Control Unit #0 and #1, so that be
(r) Turn on the AC Power Unit Switch of the both Power Units.
(s) Turn on the main switch. (Usually the Control Unit recovers in about five minutes.)
Make sure that the WARNING LED (orange) on the Front Bezel has gone out(1).
(t) Make sure that the READY LED (green) on the Front Bezel is off. The READY LED (green) on

REP 02-0510-01
(3) Procedure for replacement with the power turned off (with the cache memory data volatilized
forcibly)
shown below.
Storing simple trace information in the USB memory (TRBL 07-0230).
NOTE: When doing the following works, get a permission of the Technical Support
Center. When replacing the controller with the power turned on (with the
cache memory data not volatilized) in a maintenance work, refer to procedure
(2) Procedure for replacement with the power turned off (REP 02-0500).
(a) Confirm the installation location of the Control Unit whose CALM LED is on.
(c) Turn off the main switch.
Make sure that the POWER LED (Green) on the Front Bezel go off
(d) Loosen the screws (right and left) which are fixing the levers of the Control Unit, push down the
(e) Remove the all cables connected to the Control Unit.
CAUTION
(f) Remove the Control Unit by pulling it out toward you.

(g) Remove the Host Connector for the RKS.
(h) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the
(i) Remove the Cache Unit.
ends of the Cache Unit, and then the cache memory can be removed.
taken.
(j) In the case of RKM, Remove the Interface Board mounted on the Control Unit.

REP 02-0520-01
(k) Loosen the fixing screw for the cover at the back of the cover of the new Control Unit, slide
(l) Be sure to install the removed Cache memory in the position with the same slot number as
(m) Install the removed Interface Board in the Control Unit fitting it to the positioning pin, and
(n) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
(o) Install the removed Host Connector in the new Control Unit for the RKS.
(p) Insert it into the specified position with the both right and left levers of the Control Unit
(q) Connect the removed all cables to the Control Unit.
(r) Turn on the AC Power Unit Switch of the both Power Units.
(s) Turn on the main switch. (Usually the Control Unit recovers in about five minutes.)
Make sure that the WARNING LED (orange) on the Front Bezel has gone out(1).
(t) Make sure that the READY LED (green) on the Front Bezel is off. The READY LED (green) on

REP 02-0530-01
2.2.6 Replacing Cache Unit
CAUTION
care.
CAUTION
damage the parts.




REP 02-0540-01
Replace the specified slot number only for the Cache memory replacement.

(hot replacement) Otherwise, a powering off may occur because of In the case of the RKM/RKS :
an abnormal temperature rise. Perform the part See (1-1) When the CALM
replacement in haste. LED of the RKM/RKS on the
2. The procedure varies depending on whether the Control Unit is on (REP 02-
CALM LED or EALM LED is on or off. 0560).
3. Replace the Control Unit after blocking the When the CALM LED is off
Control Unit to be replaced. (Preventive replacement)
4. When replacing Control Unit of both systems In the case of the RKM/RKS :
(CTL 0 and CTL 1), power off the subsystem See (1-2) When the CALM
before the replacement. LED of the RKM/RKS on the
5. In the case of the single Controller configuration, Control Unit is off (REP 02-
perform the replacement after turning off the 0610).
power.
host computer.
LED lights on.
2 Replacement with the power turned off In the case of the RKM/RKS : See
(2) Procedure for replacement
02-0640).

REP 02-0550-01

(1-1) When the CALM LED of the RKM/RKS on the Control Unit is on
(Refer to Figure 2.2.8 Cache Memory replacement and LED locations (RKS) (REP 02-0590)
and Figure 2.2.8.1 Cache Memory replacement and LED locations (RKM) (REP 02-0600).)

Before replacing the Control Unit, confirm that it is blocked (the CALM LED
(RED) in on).
required.
(a) Make sure that CALM LED (RED) on the Control Unit mounting the Cache Unit to be replaced
lights up. If it does not light up, remove the Cache memory following (1-2) When the CALM
LED of the RKM/RKS on the Control Unit is off (REP 02-0610).
ADAPTER) of the Control Unit installing the Cache memory that is not replaced in DF700 are
connected with the remote cable (VRCx) when the remote adaptor is connected. Check that
the LED of the connected remote adaptor lights on when the remote cable has already been
connected. Next, remove the remote cable connected to the Control Unit in which the Cache
memory to be replaced is installed.
(d) Remove all the power cables connected to the Control Unit mounting the Cache Unit to be
replaced.
CAUTION
care.

(f) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the direction

REP 02-0560-01
(g) Remove the Cache Unit, in which the failure occurred, after recording its installation
location, capacity, and model name.
taken.
(h) Install the new Cache Unit to the Control Unit.

Install a new Cache Unit with the same capacity as that of the former one in the same slot.
(i) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
(j) Make sure that 20 seconds or longer has elapsed after the Control Unit was taken out. If the
controller is inserted before 20 seconds has elapsed, the Control Unit may not be recovered
normally.
(k) When the RKAJ/RKAJAT is connected, connect the ENC cable. When the RKAJ/RKAJAT is not
connected, go to Step (l).

REP 02-0570-01
(l) Insert it into the specified position with the both right and left levers of the Control Unit
recovery start is displayed in the Information Message of WEB after the dummy replacement,
perform the dummy replacement of the Control Unit which was inserted, again.
When returning the levers in the arrow directions () at the same time,
operate them within one second. If the operation takes longer than one
second, the Control Unit may not be recovered. If it occurs, execute the
recovery procedure once again. If the Control Unit is not recovered in spite
of the re-execution, replace the Control Unit because it may be faulty.
(m) Make sure that the CALM LED (red) on the Control Unit is off.
(n) Make sure that the WARNING LED (orange) on the Front Bezel is off(2).
(o) Connect the removed all cables to the Control Unit.
(p) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(q) Refer to Information Message on WEB, and check to see that [I0020x CAHE recovered
(CACHE-x)] is indicated. (Refer to WEB 2.5 Information Message (WEB 02-0120).)
When this is indicated, the replacement of Cache Unit has completed.
(r) Check that the LED of the remote adaptor connected to the Control Unit in which the
replaced Cache memory is installed lights on when the remote adaptor is connected.

REP 02-0580-01
Control Unit #1
Cover
Control Unit #0
Fixing screw
Lever Removal :
Fixing screw
Cut by hand.
Installation :
inside the slot push it into the slot by holding the
cutout Socket both end by hand.
Control Unit #1
LASER PRODUCT
CLASS 1
LASER KLASSE 1
REMOTE ADAPTER
REMOTE ADAPTER
LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0A-0 EALM LED (red) Control Unit #0

PATH #0 PATH #1
CALM LED (red)
Figure 2.2.8 Cache Memory replacement and LED locations (RKS)

REP 02-0590-01
Control Unit #0
Cover
Control Unit #1
Fixing screw
Removal :
Lever Slot lever
Socket by hand.
Cut Installation :
Cutout inside the slot both end by hand.
slot #1 slot #0
PATH #1 PATH #0 EALM LED (red) Port 1B-0
Control Unit #1
LASER PRODUCT
CLASS 1
LASER KLASSE 1
REMOTE ADAPTER
REMOTE ADAPTER
LASER KLASSE 1
CLASS 1
LASER PRODUCT

PATH #0 PATH #1
CALM LED (red)
Figure 2.2.8.1 Cache Memory replacement and LED locations (RKM)

REP 02-0600-01
(1-2) When the CALM LED of the RKM/RKS on the Control Unit is off
(Refer to Figure 2.2.8 Cache Memory replacement and LED locations (RKS) (REP 02-0590)
and Figure 2.2.8.1 Cache Memory replacement and LED locations (RKM) (REP 02-0600).)
NOTE : System parameters are automatically loaded to the new Control Unit from the
required.
(a) Press the RST SW on the Control Unit, in which the Cache Unit to be replaced is installed, and
make sure that the CALM LED (red) comes on. Use a tool with a thin tip (a precise
screwdriver, etc.) because the hole of RST SW is small (3 mm in diameter). If not, remove
the Cache Unit following the (2) Procedure for replacement with the power turned off
(REP 02-0640).
ADAPTER) of the Control Unit installing the Cache memory that is not replaced in DF700 are
connected. Next, remove the remote cable connected to the Control Unit in which the Cache
memory to be replaced is installed.
(d) Remove the all cables connected to the Control Unit on which the Cache Unit to be replaced
is mounted.
CAUTION
care.

(g) Remove the Cache Unit to be replaced for the purpose of preventive maintenance after
recording its installation location, capacity, and model name.
taken.

REP 02-0610-01
(h) Install the Cache Unit in the Control Unit.

(j) Make sure that 20 seconds or longer has elapsed after the Control Unit was taken out. If the
normally.
(k) When the RKAJ/RKAJAT is connected, connect the ENC cable. When the RKAJ/RKAJAT is not
connected, go to Step (l).
(l) Insert it into the specified position with the both right and left levers of the Control Unit

REP 02-0620-01
(m) Make sure that the CALM LED (red) on the Control Unit is off.
(o) Connect the removed all cables to the Control Unit.
(p) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(q) Refer to Information Message on WEB, and check to see that [I0020x CAHE recovered
(r) Check that the LED of the remote adaptor connected to the Control Unit in which the
replaced Cache memory is installed lights on when the remote adaptor is connected.

REP 02-0630-01

shown below.
NOTE : If the power has already been turned off, check that Cache memory is not in the
back-up state. (To check for the back-up state, refer to 1.1.2 Checking cache
(d) Remove the all cables connected to the Control Unit.
CAUTION
care.

(g) Remove the Cache Unit, in which the failure occurred, after recording its installation
location, capacity, and model name.
taken.
(h) Install the Cache Unit in the Control Unit.


REP 02-0640-01
(j) Insert it into the specified position with the both right and left levers of the Control Unit
(k) Connect the removed all cables to the Control Unit.
(l) Turn on the AC Power Unit Switch of the both Power Units.
(m) Turn on the main switch.
(o) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(p) Refer to Information Message on WEB, and check to see that [I0020x CAHE recovered

REP 02-0650-01
2.2.7 Replacing Interface Board

This work is for the RKM only.
CAUTION
care.
CAUTION
damage the parts.




REP 02-0660-01

(hot replacement) Otherwise, a powering off may occur because See (1-1) When the CALM
of an abnormal temperature rise. Perform the LED on the Control Unit is on
part replacement in haste. (REP 02-0680).
2. The procedure varies depending on whether the When the CALM LED is off
CALM LED or EALM LED is on or off. (Preventive replacement)
3. Replace the Control Unit after blocking the See (1-2) When the CALM
Control Unit to be replaced. LED on the Control Unit is off
4. When replacing Control Unit of both systems (REP 02-0720).
(CTL 0 and CTL 1), power off the subsystem
before the replacement.
host computer.
replacement work, do not make the
replacement because the ENC/SENC firmware
is being downloaded. Make the replacement
after the LED lights on.
02-0750).

REP 02-0670-01

(1-1) When the CALM LED on the Control Unit is on
(Refer to Figure 2.2.8.4 Replacing Interface Board (REP 02-0710).)

Before replacing the Control Unit, confirm that it is blocked (the CALM LED
(RED) in on).
required.
(a) Make sure that CALM LED (RED) on the Control Unit mounting the Interface Board to be
replaced lights up. If it does not light up, remove the Interface Board following (1-2) When
the CALM LED on the Control Unit is off (REP 02-0720).
ADAPTER) of the Control Unit installing the Interface Board that is not replaced in DF700 are
connected. Next, remove the remote cable connected to the Control Unit in which the
Interface Board to be replaced is installed.
(d) Remove all the power cables connected to the Control Unit mounting the Interface Board to
be replaced.
CAUTION
care.

(f) Remove the Host Connector.
(g) Loosen the fixing screw for the cover at the back of the cover, slide the cover in the direction

REP 02-0680-01
(h) Remove the Interface Board mounted on the Control Unit.

(i) Install the new Interface Board in the Control Unit fitting it to the positioning pin, and
(j) Install the removed Host Connector in the new Control Unit.
(k) Slide the cover in the opposite direction of which it was removed, attach it, and tighten the
(l) Make sure that 20 seconds or longer has elapsed after the Control Unit was taken out.
If the controller is inserted before 20 seconds has elapsed, the Control Unit may not be
recovered normally.
(m) When the RKAJ/RKAJAT is connected, connect the ENC cable.
When the RKAJ/RKAJAT is not connected, go to Step (n).

REP 02-0690-01
(n) Insert it into the specified position with the both right and left levers of the Control Unit
(o) Make sure that the CALM LED (red) on the Control Unit is off.
(p) Make sure that the WARNING LED (orange) on the Front Bezel is off(2).
(q) Reconnect all cables that were disconnected.
(r) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(s) Refer to Information Message on WEB, and check to see that [I0010x CTL recovered (CTL-
x)] is indicated. (Refer to WEB 2.5 Information Message (WEB 02-0120).)
When this is indicated, the replacement of Interface Board has completed.
(t) Check that the LED of the remote adaptor connected to the Control Unit in which the
replaced Interface Board is installed lights on when the remote adaptor is connected.

REP 02-0700-01
Control Unit #0
Cover
Positioning hole
Interface Board
Fixing screw
Control Unit #1
Positioning pin

Lever
(five screws)
Fixing screw
cutout
LASER PRODUCT
CLASS 1
LASER KLASSE 1
REMOTE ADAPTER
REMOTE ADAPTER
LASER KLASSE 1
CLASS 1
LASER PRODUCT

PATH #0 PATH #1
CALM LED (red)
Figure 2.2.8.4 Replacing Interface Board

REP 02-0710-01
(1-2) When the CALM LED on the Control Unit is off

NOTE : System parameters are automatically loaded to the new Control Unit from the
required.
(a) Press the RST SW on the Control Unit, in which the Interface Board to be replaced is
installed, and make sure that the CALM LED (red) comes on. Use a tool with a thin tip (a
precise screwdriver, etc.) because the hole of RST SW is small (3 mm in diameter). If not,
remove the Interface Board following the (2) Procedure for replacement with the power
ADAPTER) of the Control Unit installing the Interface Board that is not replaced in DF700 are
connected. Next, remove the remote cable connected to the Control Unit in which the
Interface Board to be replaced is installed.
(d) Remove the all cables connected to the Control Unit on which the Interface Board to be
replaced is mounted.
CAUTION
care.


REP 02-0720-01
(l) Make sure that 20 seconds or longer has elapsed after the Control Unit was taken out. If the
normally.
(m) When the RKAJ/RKAJAT is connected, connect the ENC cable.
When the RKAJ/RKAJAT is not connected, go to Step (n).

REP 02-0730-01
(n) Insert it into the specified position with the both right and left levers of the Control Unit
(o) Make sure that the CALM LED (red) on the Control Unit is off.
(q) Reconnect all cables that were disconnected.
NOTE : The installed direction is different in the Control Unit #0 and #1, so that be
(r) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(s) Refer to Information Message on WEB, and check to see that [I0010x CTL recovered (CTL-
(t) Check that the LED of the remote adaptor connected to the Control Unit in which the
replaced Interface Board is installed lights on when the remote adaptor is connected.

REP 02-0740-01

shown below.
NOTE : If the power has already been turned off, check that Interface Board is not in
(d) Remove the all cables connected to the Control Unit.
CAUTION


REP 02-0750-01
(l ) Insert it into the specified position with the both right and left levers of the Control Unit
The installation direction is different in the Control Unit #0 and #1. Install
(m) Reconnect all cables that were disconnected.
(n) Turn on the AC Power Unit Switch of the both Power Units.
(o) Turn on the main switch.
(q) Make sure that the READY LED (green) on the Front Bezel is on. The READY LED (green) on
(r) Refer to Information Message on WEB, and check to see that [I0010x CTL recovered (CTL-

REP 02-0760-01
2.2.8 Replacing Host Connector
CAUTION
damage the parts.
Host Connector is precision instrument. Before starting the operation, make sure to wear a
wrist strap to protect Host Connector against the electric shock.

A Host Connector to be unpacked and




REP 02-0770-01
Refer to the figure below for the Host Connector replacement work. Host Connector can be
replaced with the power turned on.
When the Host Connector is installed or removed, SNMP Trap is sent.
NOTE : Host Connector can be Type1and Type2. When removing or installing a Host
Connector, work according to each type.

1 Replacement with the power turned on 1. The procedure varies depending on whether the When the ALARM LED is on
(hot replacement) ALARM LED is on or off. See (1-1) When the ALARM
2. In the case of Preventive replacement, there LED on the Host Connector is
may be an error report in the host computer on (REP 02-0790).
depending on the operating conditions of the When the ALARM LED is off
host computer. (Preventive replacement)
The prior contact to the customer is required. See (1-2) When the ALARM
3. The host connectors different from each other LED on the Host Connector is
are installed in the RKM and RKS respectively. off (REP 02-0810).
When replacing each of them, be careful not to
use a wrong one.
02-0820).

REP 02-0780-01

(1-1) When the ALARM LED on the Host Connector is on
(Refer to Figure 2.2.8.5 Replacing Host Connector (REP 02-0800).)
NOTE : Do not replace the Host Connector which operates normally.

Before replacing the Host Connector, confirm that it is blocked (the ALARM LED
(RED) in on).
(a) Make sure that ALARM LED (RED) on the Host Connector to be replaced lights up. If it does
not light up, remove the Host Connector following (1-2) When the ALARM LED on the Host
Connector is off (REP 02-0810).
(b) Remove the Fibre Channel cables connected to the Control Unit mounting the Host Connector
to be replaced.
(c) Remove the Host Connector.

In the case of Host Connector (Type1), pull out the Host Connector after pushing down
the Lever to the forward.
In the case of Host Connector (Type2), pull out the Host Connector after raising the
Lever.
(d) Make sure that 20 seconds or longer has elapsed after the Host Connector was taken out. If
the Host Connector is inserted before 20 seconds has elapsed, the Host Connector may not be
recovered normally.
(e) Check the insertion direction of the Host Connector and inset the Host Connector in the port
until it clicks.
(f) Connect the Fibre Channel Interface cables.
(g) If the port LED does not light on, the other failure may be considered, so that restore it
following Troubleshooting Chapter 1. Flowchart for troubleshooting (TRBL 01-0000).
(h) Refer to Information Message on WEB, and check to see that [I53A00 Host Connector
recovered (Port xy-z)] is indicated. (Refer to WEB 2.5 Information Message (WEB 02-
0120).)
When this is indicated, the replacement of Host Connector has completed.

REP 02-0790-01
(a) Host Connector (Type1) (b) Host Connector (Type2)
Lever
Host Connector (Type1) Lever Host Connector (Type2)
Figure 2.2.8.5 Replacing Host Connector
Port 1B-0 Port 1A-0 Control Unit #1 Port 1A-1 Port 1A-0
LASER PRODUCT
CLASS 1
LASER PRODUCT
LASER KLASSE 1
CLASS 1
ALARM LED
LASER KLASSE 1
ALARM LED
ALARM LED LASER KLASSE 1
CLASS 1
LASER PRODUCT LASER KLASSE 1
CLASS 1
LASER PRODUCT
Port 0A-0 Port 0B-0 Port 0A-0 Port 0A-1

Control Unit #0
RKM RKS
Figure 2.2.8.6 Replacing Host Connector

REP 02-0800-01
(1-2) When the ALARM LED on the Host Connector is off

NOTE : There may be an error report in the host computer depending on the operating
conditions of the host computer.
(a) Remove the Fibre Channel cables connected to the Control Unit mounting the Host Connector
to be replaced.
(b) Remove the Host Connector.

In the case of Host Connector (Type1), pull out the Host Connector after pushing down
In the case of Host Connector (Type2), pull out the Host Connector after raising the
Lever.
(c) Make sure that 20 seconds or longer has elapsed after the Host Connector was taken out. If
the Host Connector is inserted before 20 seconds has elapsed, the Host Connector may not be
recovered normally.
(d) Check the insertion direction of the Host Connector and inset the Host Connector in the port
until it clicks.
(e) Connect the Fibre Channel Interface cables.
(f) If the port LED does not light on, the other failure may be considered, so that restore it
(g) Refer to Information Message on WEB, and check to see that [I53A00 Host Connector
0120).)

REP 02-0810-01

shown below.
(c) Remove the Fibre Channel cables connected to the Control Unit mounting the Host Connector
to be replaced.
(d) Remove the Host Connector.
y In the case of Host Connector (Type1), pull out the Host Connector after pushing down
y In the case of Host Connector (Type2), pull out the Host Connector after raising the
Lever.
(e) Check the insertion direction of the Host Connector and inset the Host Connector in the port
until it clicks.
(f) Connect the Fibre Channel Interface cables.
(g) Turn on the AC Power Unit Switch of the both Power Units.
(h) Turn on the main switch.
(i) If the port LED does not light on, the other failure may be considered, so that restore it
(j) Refer to Information Message on WEB, and check to see that [I53A00 Host Connector
0120).)

REP 02-0820-01
2.2.9 Replacing ENC Unit/SENC Unit
CAUTION
damage the parts.
y When you install an ENC Unit/SENC Unit, support its metal part with your hand
that has the wrist strap. By so doing, you can discharge the static electricity
from your body may change the parts.
The ENC Unit/SENC Unit is a precision machine that may have troubles because of electrostatic
discharge. Be sure to put on the wristband before starting work in order to protect ENC
Units/SENC Units from electrostatic discharge.

When you insert an ENC Unit/SENC Unit into the subsystem, support the ENC
Unit/SENC Unit as touching its metal part with fingers of your hand that wears a
wrist strap.
An ENC Unit/SENC Unit to be

unpacked and replaced for
maintenance

Support an ENC Unit/SENC Unit by
touching its metal part (metal plate)
with your fingers A wrist strap (Be sure to wear this before

REP 02-0830-01

1 Replacement with the power turned on 1. Complete the replacement within five minutes. When the ALM LED (red) of the
(hot replacement) Otherwise, a powering off may occur because of ENC Unit/ SENC Unit to be
an abnormal temperature rise. Perform the part replaced is on
replacement in haste. Refer to (1-1) When the ALM
2. When replacing the ENC Unit/SENC Unit, the LED of the ENC Unit/SENC Unit
subsystem must be in the status shown below. to be replaced is on (REP 02-
y The microprogram is not being performed. 0850)
y The Control Unit is not being replaced. When the ALM LED (red) of the
y Any part other than the above is not being ENC Unit/ SENC Unit to be
replaced. replaced is off
3. If the READY LED (green) on the Front Bezel is (Preventive replacement)
blinking at high speed for the preventive Refer to (1-2) When the ALM
replacement work, do not make the replacement LED of the ENC/SENC Unit to be
because the ENC/SENC firmware is being replaced is off (REP 02-0870)
LED lights on.
off (REP 02-0890)
excessive stresses.
y When it is required to replace the two or more ENC Units/SENC Units in the
same loop, replace the Control Unit of the RKM/RKS first, then the ENC
Unit/SENC Unit of the RKAJ/RKAJAT next.
When replacing the ENC/SENC Units of two or more RKAJs/RKAJATs, it is
required to replace them from the RKAJ/RKAJAT of the number that N of the
subsystem ID# xN is small.
y When a failure of the battery system (whose message code is W03000,
W0300x, W03100, W0310x, W03200, W0320x, W03300, W0330x, or W0340x)
has occurred, recover the subsystem from the battery system failure before
replacing the ENC Unit/SENC Unit.
y When the subsystem power is turned off because of an ENC Unit/SENC Unit
failure using an improper procedure such as an operation of a breaker in the
case where the interlocking with the UPS is in use, the subsystem power may
not be turned on after that. In such a case, power on the subsystem after
turning off and on the output from the UPS.
If the UPS cannot be turned off and on, power off the subsystem after
removing the cable for interlocking with the UPS. (When the cable is
removed, a warning will be issued.)

REP 02-0840-01

(1-1) When the ALM LED of the ENC Unit/SENC Unit to be replaced is on
(a) Make sure that the ALM LED (Red) of the ENC Unit/SENC Unit to be replaced is lit.
When ALM LED (red) on the ENC Unit/SENC Unit is off, remove the ENC Unit/SENC Unit
following (1-2) When the ALM LED of the ENC/SENC Unit to be replaced is off (REP 02-
0870).
(b) Raise the lever on the ENC Unit/SENC Unit in the direction shown by the arrow c () and
(c) Remove the ENC cable connected to the ENC Unit/SENC Unit to be replaced.
(d) Remove the ENC Unit/SENC Unit by pulling it out toward you.
(e) After waiting for 20 seconds or longer, insert a new ENC Unit/SENC Unit into the specified
location with its lever raised. When doing this, do not insert the ENC Unit/SENC Unit
completely.
If the ENC Unit/SENC Unit is inserted without waiting for 20 seconds or longer, it is possible
that the ENC Unit/SENC Unit is not recovered from the failure normally.
NOTE : Do not catch a ENC cable, when the ENC Unit/SENC Unit is inserted.
(f) Connect the ENC cable to new ENC Unit/SENC Unit.

(g) Return the levers in the direction shown by the arrows d (>).
NOTE : When returning the both levers in the directions shown by the arrows d (>)
at the same time, operate the levers within one second.
If the returning of the levers takes longer time, it is possible that the recovery
from the error fails. When this happens, execute the replacement procedure
again.
If the subsystem is not recovered from the failure nevertheless, replace the ENC
Unit/SENC Unit because the ENC Unit/SENC Unit is considered to have failed.
For the SENC Unit, the CHK LED (Red) lights on for about 10 seconds (while the
CUDG is being executed) after the SENC Unit has been inserted.

REP 02-0850-01
(h) Make sure that the ALM LED (red) on the ENC Unit/SENC Unit is off.
minutes).
(j) Refer to Information Message on WEB, and check to see that [I00Axy Loop recovered (Path-
x, Loop-y)] or [I00Bxy ENC recovered (Unit-x, ENC-y)] is indicated. (Refer to WEB 2.5
Information Message (WEB 02-0120).)
When this is indicated, the replacement of ENC Unit/SENC Unit has completed.
ENC Unit (Front)

P1 LED CHK LED
SW P0 LED ALM LED
SENC Unit (Front) CHK LED
SW P0 LED ALM LED
Lever
d
c ENC Unit #1 (RKAJ)/
ENC Unit #0 (RKAJ)/ SENC Unit #1 (RKAJAT)
SENC Unit #0 (RKAJAT)
Figure 2.2.9 Replacing of ENC Unit/SENC Unit

REP 02-0860-01
(1-2) When the ALM LED of the ENC/SENC Unit to be replaced is off
(Refer to Figure 2.2.9 Replacing of ENC Unit/SENC Unit (REP 02-0860).)
(a) Raise the lever on the ENC Unit/SENC Unit in the direction shown by the arrow c () and
NOTE : When raising the lever on the ENC Unit/SENC Unit in the directions shown by
the arrows c () at the same time, operate the levers within one second.
(b) Remove the ENC cable connected to the ENC Unit/SENC Unit to be replaced.
(c) Remove the ENC Unit/SENC Unit by pulling it out toward you.
(d) After waiting for 20 seconds or longer, insert a new ENC Unit/SENC Unit into the specified
location with its lever raised. When doing this, do not insert the ENC Unit/SENC Unit
completely.
(e) Connect the ENC cable to new ENC Unit/SENC Unit.

(f) Return the levers in the direction shown by the arrows d (>).
NOTE : When returning the both levers in the directions shown by the arrows d (>)
at the same time, operate the levers within one second.
If the returning of the levers takes longer time, it is possible that the recovery
from the error fails. When this happens, execute the replacement procedure
again.
If the subsystem is not recovered from the failure nevertheless, replace the ENC
Unit/SENC Unit because the ENC Unit/SENC Unit is considered to have failed.
For the SENC Unit, the CHK LED (Red) lights on for about 10 seconds (while the
CUDG is being executed) after the SENC Unit has been inserted.
(g) Make sure that the ALM LED (red) on the ENC Unit/SENC Unit is off.
(h) When an ENC Unit/SENC Unit other than that to be replaced is detached in the replacement
of the ENC Unit/SENC Unit installed in the RKM/RKS or removal of the ENC cable connected
to it, remove the ENC cable connected to the detached ENC Unit/SENC Unit. (You may
replace the ENC cables in any order because the ENC Unit/SENC Unit to be replaced is
detached. An ENC Unit/SENC Unit other than that to be replaced cannot be detached no
matter which cable connected to the front or rear ENC Unit/SENC Unit is removed first.)
Perform a restoration of the detached ENC Unit /SENC Unit following the procedure starting
from step (b).
When the ENC Unit/SENC Unit cannot be restored because of a wrong restoration procedure,
restore it by performing turning off and on of the subsystem power.

REP 02-0870-01
minutes).
1 : When the WARNING LED of RKM/RKS is blinking, refer to the WEB or collect the trace, and then check if the LED
goes out.

REP 02-0880-01

(Refer to Figure 2.2.9 Replacing of ENC Unit/SENC Unit (REP 02-0860).)
shown below.
Storing simple trace information in the USB memory (TRBL 07-0230)).
Make sure that the CACHE POWER LED (green) of the Control Unit has gone out.
(c) Raise the lever on the ENC Unit/SENC Unit in the direction shown by the arrow c () and
(d) Remove the cables connected to the ENC Unit/SENC Unit.
(e) Remove the ENC Unit/SENC Unit by pulling it out toward you.
(f) Insert a new ENC Unit/SENC Unit into the specified location with its lever raised. When
doing this, do not insert the ENC Unit/SENC Unit completely.
(g) Connect the ENC cable to new ENC Unit/SENC Unit.

(h) Return the levers in the direction shown by the arrows d (>).
(i ) Turn on the AC Power Unit Switch of the both Power Units.

REP 02-0890-01
(j) Turn on the main switch.

Make sure that the ALM LED (red) has not gone out.
NOTE : For the SENC Unit, the CHK LED (Red) lights on for about 10 seconds (while the
CUDG is being executed) after the power of the SENC Unit was turned on.
After doing this, make sure that the ALM LED (red) on the ENC Unit/SENC Unit is not on.
When the ENC Unit/SENC Unit is replaced without turning off the AC Power Unit Switch of the
Power Unit (Item (c)) by mistake, an unexpected error message may be displayed.
Examples of error message:
W03100 Battery removed
W08000 Loop alarm (Path-0, Loop-0)
If the above occurs, execution of the following procedure will make the recovery.
(a) (b) (h) (i)
(k) Make sure that the READY LED on the Front Bezel is on and the ALARM and WARNING LEDs are
minutes).
(l) Refer to Information Message on WEB, and check to see that [I00Axy Loop recovered (Path-

REP 02-0900-01
2.2.10 Replacing ENC cable
CAUTION

1 Replacement with the power turned on When replacing the ENC Unit/SENC Unit, the Refer to (1) Procedure for
subsystem must be in the status shown below. replacement with the power turned
y The microprogram is not being performed. on (REP 02-0920)
y The Control Unit is not being replaced.
y Any part other than the above is not being
replaced.
If the READY LED (green) on the Front Bezel is
downloaded. Make the replacement after the LED
lights on.
off (REP 02-0930)
excessive stresses.
y When a failure of the battery system (whose message code is W03000,
W0300x, W03100, W0310x, W03200, W0320x, W03300, W0330x, or W0340x)
has occurred, recover the subsystem from the battery system failure before
replacing the ENC cable.
y When the subsystem power is turned off because of an ENC Unit/ SENC Unit
failure using an improper procedure such as an operation of a breaker in the
case where the interlocking with the UPS is in use, the subsystem power may
not be turned on after that. In such a case, power on the subsystem after
turning off and on the output from the UPS.
If the UPS cannot be turned off and on, power off the subsystem after
removing the cable for interlocking with the UPS. (When the cable is
removed, a warning will be issued.)

REP 02-0910-01

(See Figure 2.2.9.1 Locations of the Lever and LEDs on the ENC Unit/SENC Unit (REP 02-
0930).)
shown below.
(a) Among the ENC/SENC Units which are connected to the ENC cables to be replaced, open the
lever, which is attached to the ENC/SENC Unit of the one whose N of the subsystem ID# xN is
large, rapidly in the direction of release, and pull it out a little.
NOTE : When raising the lever on the ENC Unit/SENC Unit in the directions shown by
the arrows c () at the same time, operate the levers within one second.
(b) Remove the ENC cable to be replaced.
(c) Connect a new ENC cable. (Refer to Installation 3.4.10 Connecting the ENC cables (INST
03-0670) )
(d) After waiting for 20 seconds or longer, return the lever in the arrow direction d (--->).
NOTE : y When returning the both levers in the directions shown by the arrows d
(>) at the same time, operate the levers within one second.
If the returning of the levers takes longer time, it is possible that the
recovery from the error fails. When this happens, execute the replacement
procedure again. If the subsystem is not recovered from the failure
nevertheless, replace the ENC Unit/SENC Unit because the ENC Unit/SENC
Unit is considered to have failed.
y Do not catch a ENC cable, when the ENC Unit/SENC Unit is inserted.
(e) Make sure that the ALM LED (red) on the ENC Unit/SENC Unit is off.
(f) Make sure that the READY LED on the Front Bezel is on and the ALARM and WARNING LEDs are
minutes).
(g) Refer to Information Message on WEB, and check to see that [I00Axy Loop recovered (Path-
When this is indicated, the replacement of ENC cable has completed.
1 : When the WARNING LED of RKM/RKS/RKH/RKHE is blinking, refer to the WEB, and then check if the LED goes out.

REP 02-0920-01
ENC Unit (Front)

P1 LED CHK LED
ENC Unit #0 (RKAJ)/

SW P0 LED ALM LED
SENC Unit (Front) CHK LED
Lever
Release
SW P0 LED ALM LED ENC Unit #1 (RKAJ)/
Lock SENC Unit #1 (RKAJAT)
Figure 2.2.9.1 Locations of the Lever and LEDs on the ENC Unit/SENC Unit

(See Figure 2.2.9.1 Locations of the Lever and LEDs on the ENC Unit/SENC Unit (REP 02-
0930).)
shown below.
Make sure that the CACHE POWER LED (green) of the Control Unit has gone out.

REP 02-0930-01
(c) Among the ENC/SENC Units which are connected to the ENC cables to be replaced, open the
lever, which is attached to the ENC/SENC Unit of the one whose N of the subsystem ID# xN is
large, rapidly in the direction of release, and pull it out a little.
(d) Remove the ENC cable to be replaced.
(e) Connect a new ENC cable. (Refer to Installation 3.4.10 Connecting the ENC cables (INST
03-0670))
(f) Return the lever in the arrow direction d.
(g) Turn on the AC Power Unit Switch of the both Power Units.
(h) Turn on the main switch.
After doing this, make sure that the ALM LED (red) on the ENC Unit/SENC Unit is not on.
minutes).
When this is indicated, the replacement of ENC cable has completed.

REP 02-0940-01
2.2.11 Replacing Basic Chassis of Rack Mount Style

Perform this work only when an instructed to do so is given by the Technical Support Center
CAUTION
Be sure to perform the operation with two or more workers.
CAUTION
y When you install a Disk Drive or Control Unit, support its metal part with your
hand that has the wrist strap. You can discharge static electricity by touching
the metal plate.
Disk Drive or Control Unit is precision instrument. Before starting the operation, make sure to
wear a wrist strap to protect Disk Drive or Control Unit against the electric shock.

When you insert a Disk Drive or Control Unit into the subsystem, support the
Disk Drive or Control Unit as touching its metal part with fingers of your hand
that wears a wrist strap.

Disk Drive
Support a part by touching its metal part

(metal plate) with your fingers A wrist strap (Be sure to wear this before

1 Replacement with the power turned on Not applicable
(hot replacement)
off (REP 02-0960)

REP 02-0950-01

shown below.
NOTE : y When the power has already been turned off, make sure that the cache is not
in the cache backup mode. (Refer to 1.1.2 Checking cache memory in the
back-up state (REP 01-0030).)
When the cache is in the cache backup mode, make the replacement after
canceling the mode.
y Write down the serial number of the subsystem before the replacement. Write
down the same serial number as the removed subsystem in the new
subsystem.
(a) Turn off the main switch. (The POWER LED goes out.)
Make sure that the POWER LED (green) on the Front Bezel goes out. If the power cannot be
turned off, have the Web be connected and find out a cause of the trouble
(d) Remove all the cables connected to the components (Control Unit, and Power Unit).
Pull out the Control Unit and Power Unit a little, and then perform the cable
removal again. Besides, the cable can be damaged if it is bent upward or
downward forcibly.

REP 02-0960-01
(e) Remove parts (Disk Drives, Backup Battery Unit, Fan Assembly, Control Unit, Power Unit, and
ENC Unit) referring to each removal procedure of them.
Affix labels bearing HDD numbers on the removed Disk Drives and put the drives in the box for
temporary storage arranging them in the same order as they were installed in the subsystem.
(f) Remove the frame and replace it with a new one. (The weight of the frame whose each part
is removed is 13 kg.)
In the case of the Floor Model, refer to Installation 2.3 Installing Floor Stand Kit (INST 02-
0050) in the for Installation.
In the case of the rackmount model, refer to Installation 3.4.3 Mounting on Rack Frame
(INST 03-0400) in the for Installation.
(g) Reinstall the parts. (Refer to 2.2 Replacement of Components (REP 02-0050).)
Reinstall all the removed parts in the same positions where they were installed before.
(h) Return all the removed cables as they were before.
(k) Make sure that the READY LED (green) on the Front Bezel comes on. The READY LED (green)
on the Front Bezel may blink at high speed (up to 30/50 minutes).
(l) Attach the Front Bezel.
(m) Affix the new subsystem and write down the same serial number as the removed subsystem.

REP 02-0970-01
Disk Drive

Address label
Screw box
Safekeeping of Disk Drive
Fan Assembly #0
Power Unit #0 Equipment Serial

Number
Control Unit #1
Power Unit #1
Control Unit #0 Fan Assembly #1

Figure 2.2.10 Replacing Basic Chassis of Rack Mount Style (RKM/RKS)

REP 02-0980-01
2.2.12 Replacing Additional Chassis of Rack Mount Style

Perform this work only when an instructed to do so is given by the Technical Support Center
CAUTION
Be sure to perform the operation with two or more workers.
CAUTION
y When you install a Disk Drive and ENC Unit/SENC Unit, support its metal part
with your hand that has the wrist strap. You can discharge static electricity by
touching the metal plate.
Disk Drive and ENC Unit/SENC Unit are precision instrument. Before starting the operation,
make sure to wear a wrist strap to protect Disk Drive and ENC Unit/SENC Unit against the
electric shock.

When you insert a Disk Drive and ENC Unit/SENC Unit into the subsystem,
support the Disk Drive and ENC Unit/SENC Unit as touching its metal part with
fingers of your hand that wears a wrist strap.
ENC Unit (RKAJ)/ The clip side of wrist strap:

SENC Unit (RKAJAT) Connect this to the metal part on the frame
of subsystem (rear face)
Disk Drive
Support a part by touching its metal part A wrist strap (Be sure to wear this before
(metal plate) with your fingers starting maintenance.)

1 Replacement with the power turned on Not applicable
(hot replacement)
off (REP 02-1000)

REP 02-0990-01

shown below.
the cache backup mode. (Refer to 1.1.2 Checking cache memory in the back-
up state (REP 01-0030).)
When the cache is in the cache backup mode, make the replacement after
canceling the mode.
(a) Turn off the main switch. (The POWER LED goes out.)
(d) Remove all the cables connected to the components (Control Unit, Power Unit, and ENC
Unit/SENC Unit).
Pull out the Control Unit, Power Unit, and ENC Unit/SENC Unit a little, and then
perform the cable removal again.

REP 02-1000-01
(e) Remove parts (Disk Drives, Fan Assembly, Power Unit, and ENC Unit/SENC Unit) referring to
each removal procedure of them.
Affix labels bearing HDD numbers on the removed Disk Drives and put the drives in the box for
temporary storage arranging them in the same order as they were installed in the subsystem.
(f) Remove the frame and replace it with a new one. (The weight of the frame whose each part
has been removed is 13 kg.)
In the case of the Floor Model, refer to Installation 2.3 Installing Floor Stand Kit (INST 02-
0050) in the Maintenance Manual for Installation.
In the case of the rackmount model, refer to Installation 3.4.3 Mounting on Rack Frame
(INST 03-0400) in the Maintenance Manual for Installation.
(g) Install all the removed parts in the same positions as before in the new chassis.
(Refer to 2.2 Replacement of Components (REP 02-0050).)
(h) Return all the removed cables as they were before.
(k) Make sure that the READY LED (green) on the Front Bezel comes on. The READY LED (green)
on the Front Bezel may blink at high speed (up to 30/50 minutes).
(l) Attach the Front Bezel.

REP 02-1010-01
RKAJ/RKAJAT
Disk Drive
Address label
Screw box
Safekeeping of Disk Drive
ENC Unit #0 (RKAJ)/

Equipment Serial
Number
Power Unit #0
Power Unit #1
ENC Unit #1(RKAJ)/

Figure 2.2.11 Replacing Additional Chassis of Rack Mount Style (RKAJ/RKAJAT)

REP 02-1020-01
2.2.13 Replacing Remote Adapter

Remote adapter condition at the time of Reference for replacement

No. Restriction
replacement procedure
1 One Remote adapter The replacement cannot be done in the state in See (1) Replacement procedure
which the subsystem power is on. with the one Remote Adapter (REP
02-1030).
2 When the Remote adapter is duplicated. If both of the two remote adapters are required to See (2) Replacement procedure to
be replaced, be sure to replace them one by one, be used when the Remote Adapter
or replace them in the state in which the is duplicated (REP 02-1040).
subsystem power is turned off.
(1) Replacement procedure with the one Remote Adapter

shown below.
(a) Turn off the main switch of the subsystem connected to the Remote Adapter to be replaced.
NOTE : Make sure that the subsystem is not in the Cache Backup mode. (Refer to 1.1.2
Checking cache memory in the back-up state (REP 01-0030).) When the
subsystem is in the Cache Backup mode, perform the replacement after
canceling the mode.
(b) Turn off the AC Power Unit Switch of the Power Units.
(c) Remove all the remote and power cables from the Remote adapter.
(d) Replacing the new Remote Adapter
(e) Connect the removed remote cable and power cable.
(f) Turn on the AC Power Unit Switch of the Power Units.
Make sure that the READY LEDs (green) of the both Power Units are on.
(g) Turn on the main switch.
(h) Make sure that the following LEDs on the Remote Adapter are on.
y POWER LED
y LEDs for the connectors among the J100 to J105 to which the remote cables are connected.

REP 02-1030-01
Remote Adapter
Power cable
(Input Remote adapter J1)
Remote cable
Figure 2.2.12 Replacing Remote Adapter
(2) Replacement procedure to be used when the Remote Adapter is duplicated

generated error message, and then perform the replacement operation following the
procedure shown below.
(a) Make sure that all the LEDs of the Remote Adapter not to be replaced are on.
(b) Remove the remote and power cables from the Remote Adapter to be replaced.
(c) Replacing the new Remote Adapter
(d) Connect the removed remote cable and power cable.
(e) Make sure that the following LEDs on the Remote Adapter are on.
y POWER LED
y LEDs for the connectors among the J100 to J105 to which the remote cables are connected.

REP 02-1040-01

REP 02-1050-01
.
Chapter 3. Periodic Maintenance

This chapter contains information on items of periodical maintenance which is performed to
prevent failures of the subsystem from occurring and to maintain operation performance.
3.1 Periodic Maintenance Items

Table 7.1.1 shows periodical maintenance items of the subsystem. Inspect and clean the
subsystem regularly according to the operation environment.
Table 3.1.1 Periodic Maintenance Items

Inspection item for each model
Floor Model Rackmount Model Standard
Interval
No. Item (*1) RKM+RKAJ+ time required
(*2)
RKM+H1J/RKS+H1J H2J/RKS+RKAJ+H2 Rackmount Model (U7)
J
1 Inspection Inspecting Fan Assembly Y1 3.2.1 Inspecting 3.2.1 Inspecting 3.3.1 Inspecting fans 5 min
FANs fans (REP 03-0020) fans (REP 03-0020) (REP 03-0040)
2 Cleaning Cleaning the Front bezel Y1 3.2.2 Cleaning the 3.2.2 Cleaning the 3.3.2 Cleaning the 5 min
subsystem subsystem (REP 03- subsystem (REP 03- subsystem (REP 03-
0030) 0030) 0060)
Rear cover Y1 3.2.2 Cleaning the 3.2.2 Cleaning the 5 min
subsystem (REP 03- subsystem (REP 03-
0030) 0030)
Rear door Y1 3.3.2 Cleaning the 5 min
subsystem (REP 03-
0060)
3 Replacement of Battery Y2 3.4.1 Replacing 3.4.1 Replacing 3.4.1 Replacing Battery 10 min
periodical replacement Battery Unit (REP Battery Unit (REP Unit (REP 03-0070)
part 03-0070) 03-0070)
*1 : The maintenance intervals were set on the assumption that the average operation hours of the subsystem is 400
hours/month. Therefore, in the following cases, consult the customer to decide whether to change the intervals
or not taking the actual operation hours in consideration. (See Table 7.1.2.)
*2 : Working hours change by the case where one RKM/RKS is checked, and the number of RKAJ/RKAJAT.
Table 3.1.2 Change of Maintenance Interval

Factors requiring change of maintenance interval
Object item Remarks
Case of shortening the interval Case of lengthening the interval
Inspection of fans Operation hours are long. Operation hours are short. Also examine items to be added to
Cleaning of the Installation environment is bad. Installation environment is excellent. the factors shown on the left such as
subsystem To fit the interval for user's operation the frequency of the subsystem
schedule. failure occurrence and items
To improve service for user common to the subsystem and a
Necessity to shorten the interval is connected system.
recognized for other reason.

REP 03-0000-01
3.2 Inspecting and Cleaning Floor Model

Perform the inspection and cleaning periodically. Parts of the floor models to be inspected
and cleaned are shown in Figure 3.2.1 (for the RKM/RKS+RKAJ+H2J).
Key
To unlockc
To lockd
Places where cleaning is

required
(Rear cover)
Places where cleaning is (*1)

required
(Front bezel (RKAJ))

required
(Front bezel (RKM/RKS))
RKM/RKS
(Rear view) Inspecting fan
RKAJ (Fans of Fan Assembly)
(Rear view)
*1 : The floor model H1J does not have this part.
Figure 3.2.1 Inspecting and Cleaning of Floor Model (RKM/RKS+RKAJ+H2J)

REP 03-0010-01
3.2.1 Inspecting fans

Inspect the fans while the subsystem powered on.
CAUTION
(1) In the case of the Floor (RKM+H1J/RKS+H1J/RKM/RKS+RKAJ+H2J) Model, remove the rear
cover.
(2) Make sure that fans of the Fan Assembly on the rear side of the subsystem are rotating.
(3) In the case of the Floor (RKM+H1J/RKS+H1J/RKM/RKS+RKAJ+H2J) Model, reinstall the rear
cover after the inspection and cleaning are completed.

REP 03-0020-01
3.2.2 Cleaning the subsystem

To clear the subsystem, check whether or not air vents are clogged by dust. If they are
clogged, remove the dust with a vacuum cleaner or wipe the dust out from it with a dry cloth.
CAUTION
y Be sure to keep the front bezel and rear panel clean.
Or else, the ventilation is deteriorated so that the temperature inside the
subsystem may rise causing a failure or even a fire.
CAUTION
If you touch a live part, it is feared that you receive an electric shock.
(1) Clean the outside of the Front Bezel.

(2) Insert the key in the Front Bezel and turn it in the direction shown by the arrow c () to
unlatch the bezel.
(3) Remove the Front Bezel. (See Installation 1.5 How to Open/Close Door or Attach/Remove
Front Bezel/Rear Cover of the Subsystem (INST 01-0100))
(4) Clean the internal surfaces of the Front Bezel.
(5) Attach the Front Bezel.
(6) Turn the key in the direction shown by the allow d (<) to latch the front bezel.
(7) In the case of the Floor (RKM+H1J/RKS+H1J/RKM/RKS+RKAJ+H2J) Model, remove the rear
cover.
(8) Clean the outer and inner sides of the rear cover.
(9) In the case of the Floor (RKM+H1J/RKS+H1J/RKM/RKS+RKAJ+H2J) Model, reinstall the rear
cover after the inspection and cleaning are completed.

REP 03-0030-01
3.3 Inspecting and Cleaning Rackmount Model with U7 Rack Frame

3.3.1 Inspecting fans
This work is for the RKM/RKS only.
Perform the inspection of the fans with the power turned on.
CAUTION
(1) Open the rear door. To open it, insert an Allen wrench into the keyhole on the door, turn it in
the direction shown by the arrow c (), and open the door leaving the wrench as it is. (See
Figure 3.3.1.)
(2) Make sure that the fans of the Fan Assembly in the rear of the mounted unit are rotating.
(3) Fit the Allen wrench in the key socket on the door turn it in the direction shown by the arrow
c (), and close the door leaving the wrench as it is.

REP 03-0040-01
Rackmount model with U7

rack frame

required
Front Bezel Rear Door
(RKAJ)
To open c
Allen wrench
The case where one RKM
To close d
and eleven RKAJs are
mounted is shown as an
example.

required
(Front bezel)
To unlockc
RKM/RKS
To lockd (Rear view)
Key Latch
Front bezel
(RKM/RKS)
Inspecting fan (Fans of Fan Assembly)
Figure 3.3.1 Inspecting and Cleaning Rackmount Mode with U7 Rack Frame

REP 03-0050-01
3.3.2 Cleaning the subsystem

To clear the subsystem, check whether or not air vents are clogged by dust. If they are
clogged, remove the dust with a vacuum cleaner or wipe the dust out from it with a dry cloth.
CAUTION
y Be sure to keep the front bezel and rear panel clean.
Or else, the ventilation is deteriorated so that the temperature inside the
subsystem may rise causing a failure or even a fire.
CAUTION
If you touch a live part, it is feared that you receive an electric shock.
(1) Clean the outside of the Front Bezel.

(2) Insert the key in the Front Bezel and turn it in the direction shown by the arrow c () to
unlatch the bezel.
CAUTION
Attach or remove the front bezel carefully following the procedure. Otherwise, you
may hurt your fingers by pinching them.
(3) Slide the latch and remove the Front Bezel. (Installation 1.5 How to Open/Close Door or
Attach/Remove Front Bezel/Rear Cover of the Subsystem (INST 01-0100).)
(4) Clean the internal surfaces of the Front Bezel.
(5) Attach the Front Bezel.
(6) Turn the key in the direction shown by the allow d (>) to latch the Front Bezel.
(7) Clean the external surfaces of the rear door.
(8) Open the rear doors. (Installation 1.5.4 How to open/close the Rear Door of U7 rack frame
(INST 01-0150).)
(9) Clean the internal surfaces of the rear door.
(10) Close the rear door. To close it, insert the Allen socket wrench into the keyhole on the door,
turn it in the direction shown by the arrow c (), and close the door leaving the wrench as
it is.

REP 03-0060-01
3.4 Replacing Periodical Replacement Parts

In the subsystem, a battery, which is a part with limited life, is used and it must be replaced
periodically. To replace the battery, replace the Backup Battery Unit containing the battery.
The battery has a usable period. Confirm the time limit and do not use the battery which
passed the time limit.
It is no problem to perform periodical replacement of the Backup Battery Unit while the
subsystem is being operated (being used for customers job).
3.4.1 Replacing Battery Unit
CAUTION
y Do not disassemble the battery, or a burn or electric shock may be caused.
y If a battery is handled wrongly, it is feared that an explosion is caused.
CAUTION
When a device is kept with power-off for more than three months, the battery may
be excessively discharged, and it may cause an unrecoverable damage. In such a
storing condition, either charge the battery at least once every three months for
more than six (6) hours, or switch off the battery. Even though the battery is
switched off, to prevent damages from natural discharge, the battery must be
charged once every six months for more than six (6) hours.
(1) Procedure for replacing a Disk Drive is 2.2.2 Replacing Backup Battery Unit (REP 02-0240).
(2) For disposing and keeping the used battery, refer to Chapter 5. Recycling (REP 05-0000).

REP 03-0070-01
Chapter 4. Maintenance Tools

4.1 Maintenance Tools for Hardware
Names and usages of maintenance tools to be used for installation and maintenance are shown
below.
No. Tool name Specification Usage

1 Phillips screwdriver No.1 For Local/Remote Mode Setting Switch (rotary switch)
2 Phillips screwdriver No.2 General use
3 Slotted screwdriver No.1 For Device ID Setting Switch
4 Allen wrench No.3 For installing floor stand kit
5 Allen wrench No.4 For fastening of AC power cable.
6 Allen wrench No.6 For opening/closing doors (of rack frame)
7 Spanner No.22 For adjusting leveling bolt (of U7 rack frame)
8 USB memory - For storing simple trace information

REP 04-0000-01
4.2 Maintenance Tools for Software

Maintenance tool consists of Storage Navigator Modular or Subsystems built-in Web, trace
analysis tool (TDCONV), and back-end diagnostic tool.
The following describes the outline of each maintenance tool.
(1) Storage Navigator Modular

Storage Navigator Modular is operated on the terminal device (RC and WEB etc) connected
through a LAN or RS232C with Array unit. This program enables you to perform the operation
for Array unit such as referencing the state of Array unit and setting a configuration.
For details, refer to Storage Navigator Modular (for GUI) Users Guide.
(2) Subsystems built-in WEB

By having WEB function in Array unit, you can access the Array unit from the terminal device
connected through a LAN using a WEB browser. Subsystems built-in WEB enables you to
perform the maintenance operations such as confirming a failure status of the subsystem,
referencing a error message, installing the microprogram, and collecting failure information.
For details, refer to Maintenance manual for WEB.
(3) Back-end diagnostic tool

When Loop Failure (W080xy) occurs, Back-end diagnostic tool performs the Loop Failure
Detection Function from Diagnosis for Loop Failure Detection Function window in Subsystems
built-in WEB, and identifies the failed Disk Drive.
For details, refer to Troubleshooting 6.1.14 A failure occurred during operation : Case 4
(Loop failure) (TRBL 06-0600).
Connection of maintenance tools for software is shown in Figure 4.2.1.

REP 04-0010-01
WS/PC
WEB Browser
Storage Navigator Modular
Host computer
Fibre Channel I/F
Port connection for user

Port for user management
Subsystem's L management
A Port connection for
built-in WEB N Port for maintenance
maintenance
Maintenance PC
WEB Browser
Back-end diagnostic tool
Storage Navigator Modular
Figure 4.2.1 Connection of maintenance tool for software

REP 04-0020-01

REP 04-0030-01
Chapter 5. Recycling
(1) Parts to be recycled
The battery used in the subsystem is a sealed Nickel-hydride rechargeable battery.
The lead battery is a valuable resource which can be recycled.
When you replace it or dispose of a used subsystem, please cooperate in the recycling.
How to dispose of the battery or Backup Battery Unit which becomes useless owing to
replacement etc. is shown below.
DANGER
y Do not disassemble the case, do not modify it, or do not peel off the
label. There are high voltage parts inside: If you attempt any of
these actions, you may get an electrical shock or burn.
y Do not disassemble the battery; this may cause short circuits
inside or outside of the battery. If the components are exposed to
the air, the battery may cause overheat, burst or ignite.
Disassembling the battery may expose you to its alkaline solution,
which can be dangerous.
y Do not cut the output cable. Do not modify the connector. If you
attempt any of these actions, you may get an electrical shock or
burn. A short-circuit may cause abnormal chemical reactions
inside the battery which leads to overheating, bursting or ignition.
y Follow the instructions when you recharge the battery pack. If you
recharge it in a way different from specified here, it may cause the
following problems: The battery may become charged excessively;
excessive current may be produced; or the battery cannot be
recharged. As a result, the battery may leak, become overheated,
burst, or ignite.
y Do not use excessive force when you connect the battery pack to
the charger or other devices. If you cannot connect it easily, check
the positive and negative are correct for the connector. If you
connect the battery in reverse, it will be charged incorrectly and
abnormal chemical reactions may occur inside. As a result, the
battery may become overheated, burst or ignite.
y Do not connect the battery to a power receptacle. If you apply an
excessive amount of voltage to the battery, it may produce
excessive current making the battery overheat, burst or ignite.
y Do not use or leave the battery where the temperature can become
high, such as, near a fire or a heating element. High temperatures
may damage the batterys separator, which may cause short circuit,
making it overheat, burst or ignite.

REP 05-0000-01
y Do not incinerate the battery pack or heat it. If you do so, the
insulator may melt, the safety fuse/
mechanism may be damaged, or the electrolyte may gush out. As
a result, the battery may become burst, explode or ignite.
y Do not connect the negative terminal to the positive with metal wire.
Do not carry or store the battery with other metal parts. This may
cause a short circuit or produce excessive current which can cause
the battery to leak, overheat, burst or ignite.
y Do not let the battery become wet by soaking it in the water or
seawater. If the battery gets wet, a short circuit may occur and an
excessive amount of current may be produced causing abnormal
chemical reactions inside. As a result, the battery may become
y Do not nail the battery, hit it with a hammer, or stamp on it. The
battery may be broken or dented and a short circuit may occur
inside. As a result, the battery may become overheated, burst or
ignite.
y Do not solder directly to the battery. If you do so, heat will melt the
insulator and damage the safety fuse/mechanism. As a result, the
battery may leak or may become overheated, burst or ignite.
y Do not recharge the battery where there is a high temperature, such
as near a fire.
This may cause abnormal chemical reactions inside the battery and
it may become overheated, burst or ignite. High temperatures may
also cause deterioration of performance/life of the battery.

REP 05-0010-01
WARNING
y Do not place the battery pack in the microwave oven or under high
pressure. Either of these actions will rapidly heat the battery or
break its seals: As a result, the battery may become overheated,
burst or ignite.
y If you find anything strange or unusual with the battery when you
use/carry/store it, remove the battery from the device and stop
using it. For example, strange smells, strange colors, or
deformation are a sign you must stop using the battery.
y If it takes longer than the specified time to complete recharging,
stop recharging the battery: Otherwise, the battery may become
y If the battery leaks and gets into your eyes, immediately flush your
eyes with clean water (tap water) and do not rub your eye. Then
visit the doctor immediately. If you do not seek any treatment for
your eyes, problems may occur later. Because the battery uses
highly concentrated alkaline as electrolyte, it may burn or you may
lose your sight if it contacts your skin or eyes. If the batterys
liquid contacts your skin or eyes, you must flush them with plenty
of clean water and visit the doctor at once.
(2) Display of recycling mark

The following three-arrow recycling mark shows that the sealed Nickel-hydride rechargeable
battery is a part to be recycled. A label bearing the mark is affixed on the battery.
(3) Specifications of lead battery
Table 5.1 Specifications of sealed Nickel-hydride rechargeable battery (RKM/RKS)

No. Specification Backup Battery Unit
1 Manufacturer Matsushita Battery Industrial Co., Ltd.
2 Model HHR-33AH15W1
3 Voltage (V) 6
4 Capacity (mAh) 9600min

REP 05-0020-01
(4) Disposal and safety in storage

Before storing a sealed Nickel-hydride rechargeable battery, cover its terminals with electric
tape, etc. to prevent a short circuit. Store it separately from batteries of other type such as
dry battery.
(5) Method of storage

Table 5.3 Storage method
No. Item Requirement
1 Storage method Store a Backup Battery Unit being packed in the following conditions.
Do not apply it any unusual vibration or shock.
Do not put it on its side.
Keep it in a place where the temperature is within a range of 0 to 35 oC.
2 Allowable storage term The expiration date of the storage able term is a date indicated on the usable term
label.
3 Stock management(*1) Manage stored batteries or Backup Battery Units in the way of FIFO.
Since a label for entering the usable time limit is affixed on each package, please
utilize it.
*1 : When replacing the Backup Battery Unit, check the usable time limit of it following (6)
Checking usable term of maintenance part (REP 05-0030).
(6) Checking usable term of maintenance part

If the battery is left uncharged for longer than six months, it will discharge excessively and
becomes unable to be fully recharged. Therefore, when the Backup Battery Unit is stored as a
maintenance part, it must be stored on charge under the following condition, and used within
one year. (Concerning the batteries mounted on the subsystem, since they are charged while
the subsystem power is on, no problem will occur.)
No. Items Conditions

1 Period of Long-term storage One year
2 Storage temperature 0~35
3 Supplemental charge interval Once per six months

REP 05-0030-01
FE-95DF753-00
Parts Catalog
Chapter 1. Parts Catalog.............................................................................................. PARTS 01-0000

PARTS 00-0000-01

PARTS 00-0010-01
Chapter 1. Parts Catalog

This chapter contains catalogs of the parts of the subsystem and the devices composing the
system.
Names and installation locations of parts are shown for the each model and the device.
In addition, classification of parts (into maintenance parts and optional parts) is also
contained.
1.1 How to Use this Parts Catalog

c d e f g h i j
PART UNIT
No. NAME OF PART REMARK
NUMBER PER ASSY
1-
1 2103668-A FINAL ASSY (RKM) (SEE LIST 1-1-1)

2
3 y CONTROL UNIT 1 to 2 SP, OP
4
5
6
7 CANISTER UNIT (DF-F700-AGF72) (2 to 15) SP, OP
8 CANISTER UNIT (DF-F700-AGF146) (2 to 15) SP, OP
9
10
11
12
13
14
c : Indicates a list number of an assembly which is a broad division of the subsystem.

d : Indicates a serial number of a part listed in the above list.
e : Indicates a part number (drawing number).
f : Indicates relationship of parts as follows.
No dots: Main assembly
y : Detail part of a main assembly
yy : Detail part of a one-dot subassembly
yyy : Detail part of a two-dot subassembly
g : Indicates a part name
h : Indicates a number of a detailed list when it exists. (Ex.: See No. 3-1-1.)
i : Indicates a quantity per assembly.
Number in parentheses indicates the minimum and maximum quantities of the installed
parts.
j : SP and OP means maintenance part and optional part respectively.

PARTS 01-0000-01
1.2 System of Parts Catalog

The parts and devices which composes the system are classified as shown below.
(1) System of DF700 Parts Catalog
Division No.2 (Floor Model)
Division No.1
(Rackmount Model)
RKM+H1J RKM+RKAJ+H2J RKM

RKS+H1J RKS+RKAJ+H2J
RKAJ
RKS
RKAJAT
Division No.3 (Rackmount Model)
Division Classification Name of Part No. Sheet No.

1 RKM, RKS, RKAJ, DF700-RKM 1-1 01-0020
RKAJAT DF700-RKAJ 1-2 01-0050
DF700-RKAJAT 1-3 01-0080
DF700-RKS 1-1 01-0020
2 Floor Model Floor (RKM+H1J) model 2-1 01-0110
Floor (RKM+RKAJ+H2J) model 2-2 01-0130
Floor (RKS+H1J) model 2-3 01-0140
Floor (RKS+RKAJ+H2J) model 2-4 01-0160
3 Rackmount Model U7 Rack frame 3-1 01-0170

PARTS 01-0010-01
1.3 Parts Catalog

No. 1-1 DF700-RKM/RKS
4,5
No.1-1 RKM/RKS (1)
PART UNIT
NUMBER PER ASSY
1-1- DF700-RKM / DF700-RKS
1
2
3 5274515-C y FRONT BEZEL 1
4 y EXCHANGE CHASSIS (RKM) 1
5 y EXCHANGE CHASSIS (RKS) 1

PARTS 01-0020-01
5-7,16
18
18
No.1-1 RKM/RKS (2)
PART UNIT
NUMBER PER ASSY
1-1- DF700-RKM / DF700-RKS
5 3272219-A CANISTER UNIT (DF-F700-AGF72) 2 to 15 SP, OP

6 3272219-C CANISTER UNIT (DF-F700-AGF146) 2 to 15 SP, OP
7 3272219-E CANISTER UNIT (DF-F700-AGF300) 2 to 15 SP, OP
8
9
10
11
12
13
14
15
16 2105109-A y DUMMY (DISK DRIVE) 0 to 13
17
18 3272172-B y BACKUP BATTERY UNIT 1 to 2(*1) SP
19
20
*1 : RKS is mounted of #0 only.

PARTS 01-0030-01
21
24
26,27,36
24
21
33
29
30, 31
No.1-1 RKM/RKS (3)
PART UNIT
NUMBER PER ASSY
1-1- DF700-RKM / DF700-RKS
21 3272172-C y FAN ASSEMBLY 2 SP

22
23
24 3272172-A y POWER UNIT 2 SP
25
26 3272218-A y CONTROL UNIT (RKM : DF-F700-F1JM) 1 to 2 SP, OP
27 3272218-B y CONTROL UNIT (RKS : DF-F700-F1JS) 1 to 2 SP, OP
28
29 3272218-C yy Interface Board (RKM: 4 G bps Fibre I/F Board) 1 to 2 SP
30 3272218-G Host Connector (2 G bytes) (For RKS) 2 to 4 SP
31 3272218-H Host Connector (4 G bytes) (For RKM) 2 to 4 SP
32
33 3272218-F yy CACHE UNIT (DF-F700-C1GJ) 1 to 4 SP, OP
34
35
36 3266277-A y DUMMY (CONTROL UNIT) 0 to 1

PARTS 01-0040-01
No. 1-2 DF700-RKAJ
No.1-2 RKAJ (1)
PART UNIT
NUMBER PER ASSY
1-2- DF700-RKAJ
1
2
3 5274515-D y FRONT BEZEL 1
4 y EXCHANGE CHASSIS 1

PARTS 01-0050-01
No. 1-2 DF700-RKAJ
5-7,16
No.1-2 RKAJ (2)
PART UNIT
NUMBER PER ASSY
1-2- DF700-RKAJ
5 3272219-A CANISTER UNIT (DF-F700-AGF72) 2 to 15 SP, OP

6 3272219-C CANISTER UNIT (DF-F700-AGF146) 2 to 15 SP, OP
7 3272219-E CANISTER UNIT (DF-F700-AGF300) 2 to 15 SP, OP
8
9
10
11
12
13
14
15
16 2105109-A y DUMMY (DISK DRIVE) 0 to 13
17
18
19
20

PARTS 01-0060-01
No. 1-2 DF700-RKAJ
27
24
27
29,30
No.1-2 RKAJ (3)
PART UNIT
NUMBER PER ASSY
1-2- DF700-RKAJ
21
22
23
24 3272170-A y POWER UNIT (RKAJ) 2 SP
25
26
27 3272170-B y ENC UNIT 2 SP
28
29 3272185-A y ENC CABLE (1 m) 2 SP
30 3272185-K y ENC CABLE (5 m) (DF-F700-K5B) (*1) (*2) 2 OP
31
32
33
34
35
*1 : The ENC cable is manufactured by Hitachi, Ltd. It cannot be used for other products.
*2 : The ENC cable (5 m) can be used only for two places in the system.

PARTS 01-0070-01
No. 1-3 DF700-RKAJAT
No.1-3 RKAJAT (1)
PART UNIT
NUMBER PER ASSY
1-3- DF700-RKAJAT
1
2
3 5274515-D y FRONT BEZEL 1
4 y EXCHANGE CHASSIS 1

PARTS 01-0080-01
9,10,16
No.1-3 RKAJAT (2)
PART UNIT
NUMBER PER ASSY
1-3- DF700-RKAJAT
5
6
7
8
9 3272215-A CANISTER UNIT (DF-F700-ATE250R) 2 to 15 SP, OP
10 3272215-B CANISTER UNIT (DF-F700-ATE400R) 2 to 15 SP, OP
11
12
13
14
15
16 3256813-E y DUMMY (DISK DRIVE) 0 to 13
17
18
19
20

PARTS 01-0090-01
27
24
27
29,30
No.1-3 RKAJAT (3)
PART UNIT
NUMBER PER ASSY
1-3- DF700-RKAJAT
21
22
23
24 3272170-A y POWER UNIT (RKAJAT) 2 SP
25
26
27 3272170-C y SENC UNIT 2 SP
28
29 3272185-A y ENC CABLE (1 m) 2 SP
30 3272185-K y ENC CABLE (5 m) (DF-F700-K5B) (*1) (*2) 2 OP
31
32
33
34
35
*1 : The ENC cable is manufactured by Hitachi, Ltd. It cannot be used for other products.
*2 : The ENC cable (5 m) can be used only for two places in the system.

PARTS 01-0100-01
No. 2-1 Floor (RKM+H1J) Model
1 2
No.2-1 Floor (RKM+H1J) Model (1)
PART UNIT
NUMBER PER ASSY
2-1- Floor (RKM+H1J) model Catalog No.2-1
1 3274503-A FLOOR STAND KIT 1

2 3266241-A y REAR COVER 1
3
4 DF700-RKM 1 Catalog No.1-1
5
6

PARTS 01-0110-01
No. 2-1 Floor (RKM+H1J) Model
11
No.2-1 Floor (RKM+H1J) Model (2)
PART UNIT
NUMBER PER ASSY
2-1- Floor (RKM+H1J) Model

8
9
10
11 3272181-A y POWER CABLE (J1H) 2 SP
12
13
14
15

PARTS 01-0120-01
No. 2-2 Floor (RKM+RKAJ+H2J) Model
1 2
No.2-2 Floor (RKM+RKAJ+H2J) model (1)
PART UNIT
NUMBER PER ASSY
2-2- Floor (RKM+RKAJ+H2J) Model

2 3266234-A REAR COVER 1
3 DF700-RKM 1 Catalog No.1-1

4 DF700-RKAJ 1 Catalog No.1-2

PARTS 01-0130-01
No. 2-3 Floor (RKS+H1J) Model
1 2
No.2-3 Floor (RKS+H1J) Model (1)
PART UNIT
NUMBER PER ASSY
2-3- Floor (RKS+H1J) model Catalog No.1-1

3
4 DF700-RKS 1 Catalog No.1-1
5
6

PARTS 01-0140-01
No. 2-3 Floor (RKS+H1J) Model
11
No.2-3 Floor (RKS+H1J) Model (2)
PART UNIT
NUMBER PER ASSY
2-3- Floor (RKS+H1J) Model

8
9
10
11 3272181-A y POWER CABLE (J1H) 2 SP
12
13
14
15

PARTS 01-0150-01
No. 2-4 Floor (RKS+RKAJ+H2J) Model
1 2
No.2-4 Floor (RKS+RKAJ+H2J) model (1)
PART UNIT
NUMBER PER ASSY
2-4- Floor (RKS+RKAJ+H2J) Model

2 3266234-A REAR COVER 1
3 DF700-RKS 1 Catalog No.1-1

4 DF700-RKAJ 1 Catalog No.1-2

PARTS 01-0160-01
No. 3-1 Rackmount Model with U7 Rack Frame
10
3,7
9
2,4
No.3-1 Rackmount Model with U7 Rack Frame (1)
PART UNIT
NUMBER PER ASSY
3-1- U7 RACK FRAME
1 DF-F700-U7 1 OP
2 DF700-RKM 1 to 6 Catalog No.1-1
3 DF700-RKAJ 0 to 9 Catalog No.1-2
4 DF700-RKS 1 to 9 Catalog No.1-1
5
6
7 DF700-RKAJAT 0 to 9 Catalog No.1-3
8
9 3272202-A RAIL KIT (DF-F700-URHT7) 1-10 OP
10 3274544-A DECORATION PANEL (DF-F700-U71D) (1U) 0 to 34 OP
11
12
13

PARTS 01-0170-01
No. 3-1 Rackmount Model With U7 Rack Frame
12
17
No.3-1 Rackmount Model with U7 Rack Frame (2)
PART UNIT
NUMBER PER ASSY
3-1- DF-F700-U7
8 FINAL ASSY (U7) 1

9
10
11
12 3272222-A y PDB 4 SP
13
14
15
16
17 y HEXAGON SOCKET BOLT (M5x8) 16
18
19
20

PARTS 01-0180-01
.
FE-95DF754-00
WEB
Chapter 1. Before Using Web .......................................................................................... WEB 01-0000
Chapter 2. The Normal Mode Operation Procedure ........................................................ WEB 02-0000
Chapter 3. The Maintenance Mode Operation Procedure ............................................... WEB 03-0000

WEB 00-0000-01

WEB 00-0010-01
Chapter 1. Before Using Web

1.1 The Operating Environment
The operating environment where is able to use Web is shown below.
Table 1.1.1 Operating Environment

No. Item Description Remark
1 OS Microsoft Windows 98, NT 4.0, 2000, XP, 2003, Solaris8, IRIX6.5
2 PC Pentium (Pentium II (233 MHz or more) is recommended),
Memory 40 M bytes or more (64 M bytes or more is recommended)
3 WS Turbo Sparc 170 M Hz, Memory 256 M bytes or more
R10000 195 M Hz, Memory 128 M bytes or more
4 Disk requirement y 50 M bytes, under ordinary maintenance work y Data compression tool
y 480 M bytes per one Controller, under memory dump collection(*1) is required for
Storing temporary file of Browser : 240 M bytes memory dumping.
Storing dumped memory : 240 M bytes y Refer to 3.5.3
Collecting Full Dump
(WEB 03-0370) or
3.5.4 Collecting Full
Dump (Full
Dump(SnapShot))
(WEB 03-0400) for
the capacity of Full
Dump when it is
uncompressed.
*1 : Memory dump collection may be requested by the Technical Support Center at the time of a tough
failure.

WEB 01-0000-01
1.2 Notices on (restriction of) the support browser

In the case of Windows2003, because the strict data security is the default setting, the
Web function cannot work.
In order to solve the above problem, change the setting of the browser as follows.
y Select [Tools] - [Internet Options ] - [Security] - [Custom Level ] - [Custom Setting
Reset] of the browser in this order and select the setting of the security level from
Medium or lower and click the Reset button.
The making of the setting as Medium solves the problem. However, if you want to use
Win2003 leaving the security level as High, make the following settings for the detailed
items of the [Custom Level ].
y Enable the [Active scripting] of the [Scripting].
y Enable the [Allow META REFRESH] of the [Miscellaneous].
y Enable the [File download] of the [Downloads].
y Enable the [Run ActiveX controls and plug-ins] of the [ActiveX controls and plug-ins].
y There may be a case where a new line is started in a window depending on a setting of
the browser. In such a case, make the character size smaller.
< Method of character size change >
In the case of IE
Select Middle or smaller size for the Character Size in the Display.
In the case of Netscape
Select the Reduction of Font Size in the Display and keep it being selected until
paragraphs become easy to be read.
y There may be a case where an empty dialogue box is displayed during operation in the
Maintenance mode. In such a case, close the window by clicking on the mark of X in
the upper left corner of the dialogue box, restart the browser, and then make a retry
from the entry of the URL.
y When a window size is changed while a page is displayed by Netscape, the succeeding
operation in the Refresh mode may not be done normally. In such a case, display the
page over again by clicking the Re-Display button.
y In the case of using Netscape
Memory cache: 1024 k bytes (default) or larger
Disk cache: 7680 k bytes (default) or larger
< Method of cache size setting >
Select the Edition, Setting, Details, and Cache in this order.
Specify sizes of the memory cache and disk cache.
y When obtaining trace information etc. with Netscape, there are cases that a sub-screen
to specify the file download destination does not automatically close.
In such a case, press a close button at the upper right corner of the sub-screen to close
the sub-screen after download complete.

WEB 01-0010-01
y When using Netscape navigator 7.x, select [Edit]-[Preference...]-[Advanced]-[HTTP

Networking], and set Use HTTP 1.0 in the Direct Connection Options and Proxy
Connection Options. When this setting is not made, the summary window is not
displayed correctly.
y When collecting memory dump (Full Dump) using Netscape Navigator 4.7x, pay attention
to free space in PC because information to be downloaded wont be compressed.
Installed cache of the subsystem Free Capacity needed on PC

RKM 1 G bytes/1 controller 1,710 M bytes/1 controller
2 G bytes/1 controller 2,670 M bytes/1 controller
RKS 1 G bytes/1 controller 1,440 M bytes/1 controller

WEB 01-0020-01
1.3 The Characteristic of the Network Function

LAN interface
The connector for 10Base-T/100Base-TX is equipped with the Controller. 10Base-
T/100Base-TX is selected automatic.
Network parameter
DF700 has the following network parameters and they can be set or changed by Web Browser
or Storage Navigator Modular concerning only the Port 1 (for user management) of each
Controller.
Values set when shipped from the factory

Port 1 Port 1
Network parameter Description Port 0 Port 0 Remark
(User (User
(Maintenance) (Maintenance)
Management) Management)
<Variable IP> <Variable IP>
IP Address The IP Address is changed/set up. 10.0.0.16 192.168.0.16 10.0.0.17 192.168.0.17 (*1)
Subnet Mask The Subnet Mask is changed/set 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
up.
Default Gateway The Default Gateway is 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
changed/set up.
DHCP Enable/Disable of the DHCP OFF OFF OFF OFF (*2)
function is set up.
*1 : The network connection is possible in the above IP Address (192.168.0.16) for the unchanging from the factory
setting value. Please manage the IP Address after the change certainly, if the IP Address is changed from the IP
Address of factory setting.
When the DHCP server has not started up or DHCP function has been miss-set, obtaining the IP address fails and
the device IP address remains to be 0.0.0.0. (Storage Navigator Modular or Web cannot be used via LAN.)
DHCP function, and if the IP address of 10.x.x.x is assigned to the device, IP addresses of Ports for User
Request the system administrator that the DHCP server does not assign IP address of 10.x.x.x to the device.

WEB 01-0030-01
Automatic change of network parameters of the Port 0 (for maintenance)

Since communication is not performed normally when the network addresses of the Port 1
(for user management) and the Port 0 (for maintenance) are the same, two sets of fixed
values of the network parameters to be used for the Port 0 (for maintenance) are prepared
and either of the two sets is automatically given to the Port 0 (for maintenance) depending
on the network parameters of the Port 1 (for user management).
When the network address of the Port 1 (for user management) is set as 10.*.*.*, that of
the Port 0 (for maintenance) is changed as shown below.
NOTE : However, if the network address of the LAN device connected to Port 1 (User
Management) via the Gateway accords with that of Port 0 (Maintenance), they
will collide each other, disabling to communicate normally.
(1) When the Port 1(User Management) address is set to other than
10.*.*.*, 10.0.0.(0 to 255) cannot be used for the IP address for LAN
device to be connected to Port 1(User Management) through a Gateway.
(2) When the Port 1(User Management) address is set to 10.*.*.*,
192.168.0.(0 to 255) cannot be used for the IP address for LAN device
to be connected to Port 1(User Management) through a Gateway.

Network parameter Port 0 (Maintenance) Port 0 (Maintenance)
IP Address 192.168.0.16 192.168.0.17
Subnet Mask 255.255.255.0 255.255.255.0
Default Gateway 0.0.0.0 0.0.0.0
DHCP OFF OFF

WEB 01-0040-01
1.4 Support Browser List

Table 1.1.2 Support Browser List
({ : support : not support)
OS Browser System version : 07x10
No. Platform Supported or Java Aplet supported or not
Type Ver. Type Ver.(*1) not supported supported (*2) (*3)
1 WS IRIX 6.5 Netscape Navigator 4.76 {
Solaris 2.6 Netscape Navigator 4.76 {
8 Netscape Navigator 4.76 {
2 PC Windows 98 Internet Explorer 6.0 { {
NT/2000 Internet Explorer 6.0 { {
XP Internet Explorer 6.0 {
2003 Internet Explorer 6.0 { {
(IA32)
2003 Internet Explorer 6.0 {
(IA64) 6.0 (32 Bit) { {
Windows 98 Netscape Navigator 7.1 (J) {
7.2 (E) {
NT/ 2000/XP Netscape Navigator 7.1 (J) {
7.2 (E) {
2003 Netscape Navigator 7.1 (J) {
(IA32/IA64) 7.2 (E) {
*1 : Service Pack 1 is included.
*2 : When installing the microprogram, the service PC must be started by the OS from the drive C in order to
prevent a problem of security from occurring.
*3 : Java Aplet is used for the following cases.
Microprogram installation, Host command trace download, and Online ENC/SENC firmware download.

WEB 01-0050-01
Chapter 2. The Normal Mode Operation Procedure

2.1 Transferring to the Normal Mode
For entering Normal mode, input IP address of Maintenance LAN connecter to which the LAN
cable is connected into the [address] window of Web Browser.
Under dual system configuration, input one of IP addresses of LAN-Connecter for maintenance.
The status of the devices (both Controllers) can be monitored from one controller.
If it is connected, the next screen is displayed.
NOTE : Set the TCP/IP to Disable DNS because the connection takes a long time
when the TCP/IP of the network is set to the condition in which the DNS is
used. For the setting procedure, refer to the instruction manual of the PC to
be used.
Make sure that the browser is set to the condition in which the proxy server is
not used because the connection cannot be done if the proxy server is set to
be used. To make sure the setting, refer to the instruction manual of the
browser to be used.

WEB 02-0000-01
2.2 Screen Outline

If the function of the Normal Mode is shown with the menu form and clicked, the proper
function is executed. The main screen outline of the Normal Mode is shown below.
Window display differs depending on microprogram revision.
Menu frame Version frame

Main frame
Figure 2.2.1 Main screen outline of the Normal Mode
(1) Version frame

Web Title
A Web title set by a user is displayed as it is. When it is not set, nothing is displayed.
Serial No
The subsystem serial number is shown.
CTL
Shows the number of the Controller to which the Web is connected.
IP
The IP Address of the controller where it was connected is shown.
Ver
The version of the Microprogram of the device is shown.

WEB 02-0010-01
(2) Menu frame

If the function of the Normal Mode is displayed with the menu frame and clicked, the proper
function is executed.
Main
The Main screen of the Normal Mode is displayed.
Parts Information
The status of the exchange parts is displayed.
Warning Information
The fault information that was detected during the status of the device information are
displayed.
Information Message
The fault information that was detected during the device operation and the status of the
device information are displayed.
Simple Trace
A window for collecting the Simple trace is displayed.
CTL Alarm Trace
A window for collecting the CTL Alarm trace is displayed.
Buzzer Volume
The screen that the Buzzer Volume is set up is displayed.
Page Refresh Mode
The mode for setting turning on or off of the automatic display function is displayed.
When the [Change] button is clicked, the mode is changed to on or off.
As the [OFF] display : This is not refreshed.
As the [ON] display : The screen of the mainframe is refreshed every 5 seconds.
The time of the latest refreshment (RTC) is displayed in the upper
right part of the main frame.
NOTE : When the PC enters the suspension status during operation while the Page
Refresh Mode is set to [ON], the Web may not operate correctly after the PC is
released from the suspension status.
In the case where the Web is connected for the purpose of status monitoring,
etc., set the power management of the PC so that the PC should not enter the
suspension status.
(3) Main frame

Subsystem Status
The status of the device and the status of the exchange parts are displayed.
Progress Condition
The Progress Condition as the device booting is displayed.

WEB 02-0020-01
2.3 Main Screen of the Normal Mode

The main screen of the Normal Mode is consisted of the Patrol Lamp, the summary of
exchange parts status, the Progress Condition display box.
The Patrol Lamp shows the status of subsystem.
The summary of exchange parts status notifies replacement parts errors by turning the parts
in red.
If the image of the part is clicked, the details information of the proper part are displayed.
The Main screen of the Normal Mode is shown below.

Summary of exchange
parts status
Progress Condition
Patrol Lamp display box
Figure 2.3.1 Main screen of the Normal Mode

WEB 02-0030-01
(1) Patrol Lamp

Monitoring the device, the status is displayed. The Status of the Patrol Lamp is shown below
Image Status
During the start
Black
Normal
Blue
Warning status
Yellow
Alarm status
Red
(2) Display of Progress Condition

The Progress Condition as the device booting is displayed.
(3) Summary of Exchange Parts Status

The condition of the exchange parts is displayed. If the image of the part is clicked, the
details of the proper part are displayed. The status of each exchange part is shown below.
Backup Battery Unit

Image Status
Normal
Blue
Backup Battery Unit error
Red
Power Unit
Image Status
Normal
Blue
Power Unit error
Red
ENC Unit
Image Status
Normal
Green
ENC Unit error
Red

WEB 02-0040-01
SENC Unit
Image Status
Normal
Green
SENC Unit error
Red
Fan Assembly
Image Status
Normal
Black
Fan Assembly error
Red
Disk Drive (FC)

Image Status
Normal
Blue
Disk Drive error
Red
Disk Drive (SATA)

Image Status
Normal
Blue
Disk Drive error
Red
Control Unit
Image Status
Normal
Green
Control Unit error
Red
Cache Unit
Image Status
Normal
Green
Cache Unit error
Red

WEB 02-0050-01
Fibre Loop
Image Status
Normal
Blue
Fibre Loop error
Red
Path Loop
Image Status
Normal
Orange
Path Loop error
Red
Fibre Loop error
Red
Host Connector
Image Status
Normal
Gray
Host Connector error
Red
Remote Path
Image Status
Normal
Gray
Remote Path error
Red

WEB 02-0060-01
2.4 Display of Exchangeable Parts Status (Parts Information)

The display screen of exchange part status displays the status of the Disk Drive, Control Unit,
Cache Unit, Fan Assembly, Backup Battery Unit, Power Unit, ENC Unit (SENC Unit), Fiber Loop
that are implemented. Furthermore, this is not displayed, if it is not implemented.
Also, the exchange part of abnormal status displays a red image. The Parts Information
screen is shown below.
y Disk Drive
y CTL/Battery/Cache/Loop/Host Connector

WEB 02-0070-01
y AC/ENC/Fan

WEB 02-0080-01
The meaning of the image that displays it with the display screen of exchange part status is
shown below.
(1) Disk Drive (FC)
Image Status
Normal
Blue
Red
Red and Black

No display
(2) Disk Drive (SATA)

Image Status
Normal
Blue
Red
Red and Black

No display
(3) Control Unit

Image Status
Normal
Green
Shutdown of the Control Unit
(Status where it is not implemented with the setting of the dual system
Red configuration is included)
Fault of the battery backup circuit
Yellow
Even the fault has not occurred without being implemented with the setting of
No display
single system configuration

WEB 02-0090-01
(4) Backup Battery Unit

Image Status
Normal
Green
Red
(5) Cache Unit

Image Status
Normal
Green
Fault
Red (Status where is not implemented and extracted the fault cache memory is
included)
It is not implemented and there is not a fault
No display
(6) Loop
Image Status
Normal
Blue
Fault
Red
(7) Host Connector

Image Status
Normal
Gray
Fault
Red
(8) Power Unit

Image Status
Normal
Blue
Red

WEB 02-0100-01
(9) ENC Unit

Image Status
Normal
Green
Red
(10) SENC Unit

Image Status
Normal
Green
Red
(10) Fan Assembly

Image Status
Normal
Black
Red
Information of the menu frame in the main window changes the screen to the one shown
below and a detailed message explaining the component status is displayed.

WEB 02-0110-01
2.5 Information Message

The fault information and status information of the device that detected it in during the
device operation are displayed.
The fault information and status information after the device booting are displayed in the
Controller 0/1 Common box.
The fault information and status information as the device booting are displayed in the box of
Controller 0 and Controller 1 every the controller.
The Information Message screen is shown below.
The fault information and status information are displayed.

WEB 02-0120-01
2.6 Collecting Simple Trace

This is a function to download current trace information.
To perform the down-lord, a free capacity of approximately 20 Mbytes is required in the PC.
Simple Trace of both the Control Units can be collected through one Control Unit.
It is not necessary to collect from both the controllers. (When it is collected from Control Unit
#0, File name is smpl_trc0.dat. When collected from Control Unit #1, file name is
smpl_trc1.dat.)
(1) Click Simple Trace in the menu frame.
(2) When the Simple Trace is clicked, the following window is displayed.
(3) When the [OK] button is clicked, the following window is displayed.
(4) The following window is displayed. Click the [Download] button.

WEB 02-0130-01
(5) Please click [Save], if it is continued. Please click [Cancel], if it is stopped.
(6) If the following window is displayed. Please click [Save] after file name is setting, if it is
continued.(1) Please click [Cancel], if it is stopped.
(7) The following window is displayed during execution download.
(8) The [Download] button changes to the [Close] button, so that, click the [Close] button and
close the window when the download is completed.

WEB 02-0140-01
2.7 Collecting CTL Alarm Trace

This is a function to download CTL Alarm trace information which is saved on the cache when a
Controller is detached.
To perform the down-lord, a free capacity of approximately 20 M bytes (When Copy-on-write
SnapShot Function is valid: approximately 40 M bytes) is required in the PC.
Collect CTL Alarm Trace from each Control Unit.
In order to distinguish from which Control Unit it is collected, store the collected data in
different directories or with different file names.
(1) Click CTL Alarm Trace in the menu frame.

The CTL Alarm Trace Information window is displayed when the CTL alarm trace information is
present.
The following is displayed as contents of the information.

[Not Ready] ...........................: A status in which the trace area is not established in
the subsystem
[Not Data] .............................: A status in which the CTL Alarm trace information is
not present or being generated
[MM/DD/20XY hh:mm:ss] ...........: A status in which the CTL alarm trace information is
present
collection of this time, the CTL alarm trace may not be collected normally.
Connect the Maintenance PC to the LAN port of the blocked Control Unit, and
collect the simple trace.
If simple trace cannot be obtained through detached Controller, connect the
Maintenance PC to the Controller at the opposite side, and collect the simple
trace.

WEB 02-0150-01
(2) To download the CTL Alarm trace information, select a controller (CTL 0 or CTL 1) in the Get
CTL Alarm Trace, and then press the Get Trace button.
(3) The following window is displayed. Please click [Save], if it is continued. Please click
[Cancel], if it is stopped.
(6) The download completes.

WEB 02-0160-01
2.8 Setting of the Buzzer Volume

The Buzzer Volume can be adjusted with 5 stages.
NOTE : Make this setting in the environment in which I/Os from a host computer are
not issued while the system is maintained or before the host is started up.
Please click Buzzer Volume of menu frame to enter into the Buzzer Volume setting screen.
The Buzzer Volume setting screen is shown below.
Select buzzer sound volume on the radio button and click [OK]. The buzzer sounds once at
the selected volume, and it is recognized the volume is set.

WEB 02-0170-01
2.9 Host Command Trace Download

The following conditions are necessary to download the host command trace.
The host command trace information is required to analyze by executing the performance
measurement.
If the host command trace exceeds a certain range, the new information is overwritten, so that
the old information is deleted and cannot be analyzed.
This function is to collect the command information from the host in the service PC at a
maximum.
Use this function only when the performance analysis is required. Do not use it normally.
The READY LED (green) on the Front Bezel lights on.

For MICROPROGRAM 1.3 Preparation for installation of microprogram (MICRO 01-0020) is
performed and the service PC is set up.
The data size of the host command trace that can be downloaded is affected by environments
of the service PC and a LAN.
Therefore, it is recommended to do the downloading in the following environment.
The downloading is done through the LAN port for maintenance.

The LAN interface used by the service PC is 100Base-TX or the superior.
Incidentally, the size of the data that can be downloaded varies depending on the load of I/Os
issued to the disk array subsystem.
The setting methods to download the host command trace are shown below.
(1) Display in the host command trace download window.
Enter http://(IP address)/hcmd_trc in the [Address] of the Web browser.
In the case of the dual system configuration, enter an IP address of any one of the control
units. (Only the information of the input IP address is collected. If the information for both
Control Units is required, start two Web browsers.)
[Password].

WEB 02-0180-01
(2) Input of Maximum Output Size, Interval Time of Communication and Download Directory
Path.
[Maximum Output Size] : Check the empty drive space of the service PC and input the
maximum output size (the initial value is 200 M bytes).
[Interval Time of Communication] : Input the interval time of downloading the host
command trace (the initial value is 0.1 second).
[Download Directory Path] : Input the folder which stores the host command trace (the
initial value is C:diskarray-microprogramtrace and the
folder can be selected by pressing the [Select] button).
It is required to create the storage folder beforehand.
The folder can be created only in the C:diskarray-
microprogram folder.
The collected host command trace is divided into two
or more files hcmdtrc$p#_xxxxx.trc ($: Control Unit
number, #: port number, and xxxxx: following number)
and output. When collecting the host command trace
two or more times, create the folder in every case.
(3) Click the [Start] button to start the download.
(4) The following window is displayed when the stored file exists.
Click the [OK] button.

Click [Cancel] if stopping it.

WEB 02-0190-01
(5) The following window is displayed when executing the download.
(6) The following window is displayed when the download is completed.
If the [OK] button is clicked, the host command trace download window is displayed.
Standard of the host command trace collection

When collecting the host command trace, make the following a standard and set it.
If the empty drive space of the host decreases, the system becomes unstable. Therefore,
set the host command trace collection after checking the empty space.
Also, when the command issue from the host exceeds the collectable IOPS, all the host
commands are not collected.
Host command trace collection time (second)
Required disk capacity (M bytes) = 76.8 (k bytes)
Interval time of communication (second)
Table 2.9.1 Required disk capacity for host command trace collection (M bytes)
Communication interval (second) and 0.1 0.2 0.5
the collectable IOPS 6000 3000 1200
Collection time (second)
1 0.8 0.4 0.2
10 7.7 3.8 1.5
60 46.1 23.0 9.2
The collection time and the disk capacity vary depending on the issue interval of the command
from the host.

WEB 02-0200-01

WEB 02-0210-01
Chapter 3. The Maintenance Mode Operation Procedure

3.1 Transferring to the Maintenance Mode
The method of making the subsystem enter the maintenance mode varies depending on the
lighting status of the READY LED (green) and ALARM LED (red) on the front bezel.
When the READY LED (green) is on, proceed to the procedure starting from the step (2).
When the ALARM LED (red) is on, wait for three minutes after making sure of the lighting of
it, proceed to the procedure starting from the step (2).
Also proceed to the procedure starting from the step (1) in the case where the READY LED
(green) and ALARM LED (red) do not come on after waiting for ten minutes when the power is
turned on.
(1) Make sure that the WARNING LED (orange) is not blinking fast (at intervals of 125 ms). If it is
blinking fast, wait for a while (80 seconds at the longest). It will cease to blink fast. There is
no problem if it blinks slowly (at intervals of one second).
(2) Changing the maintenance mode.
Single Controller
Press the RST SW of the single Control Unit. (While pressing RST SW, the RST LED is on.) Use
a tool with a thin tip (a precise screwdriver, etc.) because the hole of RST SW is small (3 mm
in diameter).
Dual Controller
(a) Press the RST SW of the Control Unit #0. (While pressing RST SW, the RST LED is on.)
mm in diameter).
(b) Press the RST SW of the Control Unit #1 immediately (within ten seconds) checking the CALM
LED (red) of the Control Unit#0 comes on.
When the CALM LED of the Control Unit #0 does not go out in spite of the above operation,
power off the subsystem and then power on the subsystem without pulling out or insert the
Control Unit. After that, return to step (1) and execute the procedure over again.
NOTE : Because the Control Unit is shutdown status for the Maintenance Mode, the
command from the host is impossible execution. Rebooting of the Control Unit
is required for the return.
When CALM LED on Control Unit#0 turns off and READY LED on Front Bezel turns off, it
transfers to Maintenance mode.

WEB 03-0000-01
(c) Start the setting after making sure that the subsystem has entered the Ready status.
ALARM LED (red)

WARNING LED (orange)
READY LED (green)
POWER LED (green)
Front

CLASS 1 CLASS 1
Control Unit
Rear Rear
(a) RKM (b) RKS
Figure 3.1.1 Indication Position
Illustrations in Figure 3.1.1 show cases of the rackmount model. They are the same for the
floor model.
NOTE : Set the TCP/IP to Disable DNS because the connection takes a long time
when the TCP/IP of the network is set to the condition in which the DNS is
used. For the setting procedure, refer to the instruction manual of the PC to
be used.
Make sure that the browser is set to the condition in which the proxy server is
not used because the connection cannot be done if the proxy server is set to
be used. To make sure the setting, refer to the instruction manual of the
browser to be used.

WEB 03-0010-01
(3) Please input the IP Address of the Control Unit where it was connected with the network to the
browser. Please input the page by the update button of the browser if it has already been
connected with WEB.
NOTE : The contents that were set up with System Parameter and the Microprogram
that was installed with Setup come into effect after the rebooting of the
Control Unit.
[Password].
(4) Usually, the following window is displayed in the browser.

WEB 03-0020-01
When this window is displayed in the browser, check if the Series No, the CTL number and
the IP address, which are displayed in the upper part of the window, match with the device
number, the CTL number and the IP address of the subsystem to be connected to WEB. The
WEB connection in the maintenance mode is completed when these are matched. If not
matched, the specification of the IP address at the WEB connection is incorrect. Enter the
correct IP address of the Control Unit to be connected to WEB in the browser again.
Also, when the Cache memory access failure occurs, in the Control Unit connected to WEB, the
following window is displayed in the browser. At this time, refer to 3.1.1 WEB Operation in
the Maintenance Mode during the Cache Memory Access Failure (WEB 03-0040).

WEB 03-0030-01
3.1.1 WEB Operation in the Maintenance Mode during the Cache Memory Access Failure
The message display and the setting operation do not function during the Cache memory
access failure. Select Full Dump (Compressed File) on the window, and collect Full Dump.
And then, contact the Technical Support Center.
* The time displayed on the window changes by the model or the status of the subsystem.
Also, connect WEB to the other Control Unit, and continue the maintenance work for the
dualControl Unit system.

WEB 03-0040-01
3.2 Reference/Setting of the System Parameter and Initialize

System Parameter is being classified to the following group and selecting each group executes
the reference/setting and Initialize.
(1) Subsystem
Reference and setting of the system parameter regarding the Subsystem is executed (refer to
Subsection 3.2.1 Subsystem (WEB 03-0060)).
(2) Host Interface
Reference and setting of the system parameter regarding the host interfacing are executed
(refer to Subsection 3.2.2 Host Interface (WEB 03-0120)).
(3) Network
Reference and setting of the system parameter regarding the network are executed (refer to
Subsection 3.2.3 Network (WEB 03-0170)).
(4) Name
Reference and setting of the system parameter such as the Vendor ID, Product ID, Controller
Name are executed (refer to Subsection 3.2.4 Name (WEB 03-0220)).
(5) ALL
The system parameter information is initialized. (refer to Subsection 3.2.5 ALL (WEB 03-
0260)).

WEB 03-0050-01
3.2.1 Subsystem
This function sets up/refer to the item regarding the Subsystem in the device.
(1) Please click Subsystem.
(2) The present setting value (the current value) is displayed.

WEB 03-0060-01
(3) Please click [Change] for the setting.

Please click [Back] of the browser for the unsetting.
(4) Please select the item that is set up from the pull-down menu of the corresponding item that is
set up. At this time, please set up the item that is set up all.

WEB 03-0070-01
Explanation with regard to each item

[Controller 0/1 Common]
System Startup Attribute
The System Operation Attribute is designated.
[Single Mode] : This is Single controller configuration.
[Dual Active Mode] : This is Dual controllers configuration.
Operation if the Processor failures Occurs
The operation as the processor fault occurrence is designated.
[Reset a Faule] : A fault is reset.
[Shutdown the System] : The controller is shutdown.
Drive Detach mode
The Drive Shutdown Mode is designated.
[Enable] : The Drive Shutdown Mode is effectively.
[Disable] : The Drive Shutdown Mode is ineffectively.
Turbo LU Warning
Suppression of the R/W command operation regarding the LU concerned for the case
where the Turbo LU Residence function becomes ineffective is set.
[Enable] : The operation is suppressed.
[Disable] : The operation is not suppressed
Auto Reconstruction Mode
The Auto Reconstruction Mode (Data restoration to a spare drive to be done when a
drive is pulled out) is designated.
[Enable] : The Auto Reconstruction Mode is effectively.
[Disable] : The Auto Reconstruction Mode is ineffectively.
Forced Write Through Mode
The Forced Write Through Mode is designated.
[Enable] : The Forced Write Through Mode is effectively.
[Disable] : The Forced Write Through Mode is ineffectively.
LU Ownership Change Disable Mode
The LU Ownership Change Disable Mode (A mode in which no LU switching is done) is
designated.
[Enable] : The LU Ownership Change Disable Mode is effectively.
[Disable] : The LU Ownership Change Disable Mode is ineffectively.
Delay Planned Shutdown
The Delay Planned Shutdown (Time from the power switch turning off to the deliberate
shutdown) is designated.
00 to 60 minute
Write Unique Response Mode
Specify this when setting the Write Unique Response Mode.
[Enable] : The Write Unique Response Mode is effectively.
[Disable] : The Write Unique Response Mode is ineffectively.

WEB 03-0080-01
Synchronize Cache Execution Mode

This is specified when the Synchronize Cache command is executed.
[Enable] : The Synchronize Cache Execution Mode is effectively.
[Disable] : The Synchronize Cache Execution Mode is ineffectively.

WEB 03-0090-01
(5) Please click [Set] after setting completion.
(6) The screen that confirms the following setting contents is displayed.
Please click [Save] if the setting is correct. Please click [Resume] if the setting contents are
changed.

WEB 03-0100-01
(7) If [Resume] is clicked, it returns to the setting window of before.

If [Save] is clicked, the following window is displayed.
(8) The following window is displayed at the later time for a while.
Please click [OK], if the setting is continued. Please click [Cancel], if the setting is stopped.
If [Cancel] was clicked, the system parameter is not set up.
(9) If [OK] is clicked, the following window is displayed.
(10) If the following window is displayed at the later time for a while, the setting is completion.
If [OK] is clicked, it returns to the menu.

WEB 03-0110-01
3.2.2 Host Interface

This function sets up/refer to the item regarding the host interfacing of the device.
(1) Please click Host Interface.

WEB 03-0120-01


WEB 03-0130-01
(4) Please select the item that is set up from the pull-down menu of the corresponding item that is
set up. At this time, please set up the item that is set up all.

ROM Microprogram Version :
The response value of Product Revision Level (ROM Microprogram Version) in the Inquiry
command is shown.
RAM Microprogram Version :
The response value of Product Revision Level (RAM Microprogram Version) in the Inquiry
command is shown.
[Controller]
Write & Verify Execution Mode
The operations inside the Write & Verify command from the host are shown.
[ON (Does not inhibit)] : The Write & Verify are executed.
[OFF (Inhibit)] : This is executed and replace to the Write.

WEB 03-0140-01
changed.

WEB 03-0150-01

(8) The following window is displayed at the later time for a while.

WEB 03-0160-01
3.2.3 Network
This function sets up/refer to the item regarding the network (Setting the user management
LAN port) of the device.
(1) Please click Network.

WEB 03-0170-01

(4) Please set up/select the corresponding item that is set up from the pull-down menu or input
them.
At this time, please set up the item that is set up all.

WEB 03-0180-01

[Controller 0]/[Controller 1]
DHCP(1)
[OFF]
Valid the DHCP mode.
[ON]
Identifier the DHCP mode.
IP Address
Sets the IP ADDRESS.
Subnet Mask
Sets the SUB NET MASK.
Default Gateway
Sets the DEFAULT GATEWAY.
When the DHCP server has not started up or DHCP function has been miss-set, obtaining the IP address fails and the
device IP address remains to be 0.0.0.0. (Storage Navigator Modular or WEB cannot be used via LAN.)
DHCP function, and if the IP address of 10.x.x.x is assigned to the device, IP addresses of Ports for User
Request the system administrator that the DHCP server does not assign IP address of 11.x.x.x to the device.

WEB 03-0190-01
changed.

(8) The following window is displayed.


WEB 03-0200-01

WEB 03-0210-01
3.2.4 Name
This function can set up/refer to the item of the vendor name, model name etc. of the device.
(1) Please click Name.

WEB 03-0220-01

(4) Please set up/select the corresponding item that is set up from the pull-down menu or input
them.
At this time, please set up the item that is set up all.

Vendor ID
The vendor name that is reported with the Inquiry command is set up.
Product ID
The model name that is reported with the Inquiry command is set up.
Web Title
Sets the Web Title.

WEB 03-0230-01
changed.


WEB 03-0240-01
(8) Please click [OK], if the setting is continued. Please click [Cancel], if the setting is stopped.

WEB 03-0250-01
3.2.5 ALL
(1) Initialize
This function sets up the system parameter information of the device to the initial state.
If this function was executed, the resetting of the system parameter becomes needed, because
the system parameter becomes the initial state.
(a) Please click Initialize.
(b) If [Initialize] is clicked, the following window is displayed.
(c) If the following confirmation message is displayed for a while. Please click [OK], if it is
continued.
(d) If [OK] is clicked, the following window is displayed.

WEB 03-0260-01
(e) The system parameter becomes the initial state, the following window is displayed.

WEB 03-0270-01
3.3 Setup
3.3.1 Microprogram
This function installs microprograms of the subsystem. There are two types of installation as
shown below.
y Update installation ........ To install the microprograms with configuration information and
system parameters taken over
y Initial setting up ........... To install the microprograms with configuration information and
system parameters cleared
(1) Click Microprogram.
(2) When the Microprogram is clicked, the following window is displayed.

WEB 03-0280-01
(3) Select the installation type in the Install Mode.

y Update............. Update installation
y Initial Setup....... Initial setting up
In the Microprogram Path field, specify the Unified version directory(1) in which the
microprogram to be installed is stored.
Enter the path character string directly into the entrance field or operate the [Select...] button
and select the directory from the file chooser (shown below).
Click the [Open] button.
The path that can be specified is a set of directories directly under the C:\diskarray-
microprogram\microprogram for each revision.
(4) Press the [Install] button.

(5) A dialog box for confirming whether to execute the installation is displayed. Press the [OK]
button when you want to install or [Cancel] when you want to abort.
(6) The following dialog box is displayed when the microprogram has already been installed in the
subsystem in the case where the initial setting up is specified.

WEB 03-0290-01
(7) When you want to continue the installation, press the [OK] button. When you want to abort the
installation, press the [Cancel] button.
(8) When the installation is started, the following dialog box showing that the installation is in
progress is displayed. The installation type and a name of a file being processed is displayed
in the dialog box. When you abort the installation, press the [Stop] button.
(9) Since the following completion message is displayed when the installation is completed, press
the [OK] button.

WEB 03-0300-01
3.4 Reference
3.4.1 Information Message
If the abnormality occurred to the array device, this function displays the fault information.
The fault information of Controller # 0 is displayed in Information Message and the fault
information of Controller # 1 is displayed in Information Message.

WEB 03-0310-01
3.5 Trace/Dump
3.5.1 Collecting Simple Trace
This is a function to download current trace information.
To perform the down-load, a free capacity of approximately 20 M bytes is required in the PC.
Simple Trace of both the Controllers can be collected through one Controller. It is not
necessary to collect from both the controllers. (When it is collected from Control Unit #0, File
name is smpl_trc0.dat. When collected from Control Unit #1, file name is
smpl_trc1.dat.)
(1) Clear the cache of the browser following the procedure shown below so that the old data,
y In the case of Internet Explorer, select the [Tools], [Internet Options], [General], [Temporary
Internet files], and [Delete Files] in this order.
y In the case of Netscape, select the [Edit], [Preferences], [Cache], and [Clear Cache] in this order.
(2) Click Simple Trace in the menu frame.
(3) When the Simple Trace is clicked, the following window is displayed.
(4) When the [OK] button is clicked, the following window is displayed.
(5) The following window is displayed. Click the [Download] button.

WEB 03-0320-01

WEB 03-0320-01
(6) Please click [Save], if it is continued. Please click [Cancel], if it is stopped.
(9) The [Download] button changes to the [Close] button, so that, click the [Close] button and
close the window when the download is completed.

WEB 03-0330-01
3.5.2 Collecting CTL Alarm Trace

This is a function to download CTL Alarm trace information which is saved on the cache when
a Controller is detached.
To perform the down-lord, a free capacity of approximately 20 M bytes (When Copy-on-write
SnapShot Function is valid: approximately 40 M bytes) is required in the PC.
Collect CTL Alarm Trace from each Control Unit.
(1) Clear the cache of the browser following the procedure shown below so that the old data,
y In the case of Internet Explorer, select the [Tools], [Internet Options], [General], [Temporary
Internet files], and [Delete Files] in this order.
y In the case of Netscape, select the [Edit], [Preferences], [Cache], and [Clear Cache] in this order.
(2) Click CTL Alarm Trace in the menu frame.

The CTL Alarm Trace Information window is displayed when the CTL alarm trace information is
present.

WEB 03-0340-01
(3) To download the CTL Alarm trace information, press the Download button on the Control
Unit side to be collected in CTL Alarm Trace information.(1)
The following is displayed as contents of the information.

[Not Ready] ................. : A status in which the trace area is not established in the
subsystem
[Not Data] ................... : A status in which the CTL Alarm trace information is not
present or being generated
[MM/DD/20XY hh:mm:ss] . : A status in which the CTL alarm trace information is present
collection of this time, the CTL alarm trace may not be collected normally.
Therefore, collect the simple trace.
If simple trace cannot be obtained through detached Controller, connect the
Maintenance PC to the Controller at the opposite side, and collect the simple
trace.
(4) The following window is displayed. Please click [Save], if it is continued. Please click
1 : An error message may be displayed. If it is displayed, click [OK], and collect the CTL Alarm Trace again after

WEB 03-0350-01
continued. Please click [Cancel], if it is stopped.
(7) The download completes.

WEB 03-0360-01
3.5.3 Collecting Full Dump

This function (Full Dump) is to download the logging information of the subsystem. The menu frame
differs whether the priced optional feature, Copy-on-write SnapShot Function, is installed or not.
Copy-on-write SnapShot Function uninstalled Copy-on-write SnapShot Function installed
The cache memory access failure occurs when the following window is displayed. Refer to
(WEB 03-0040).

WEB 03-0370-01
(1) For RKM/RKS

When Copy-on-write SnapShot Function is installed, the information downloaded by this
function (Full Dump) does not include the information in Copy-on-write SnapShot.
Collect Full Dump from each Control Unit. In order to distinguish from which Control Unit it is
collected, store the collected data in different directories or with different file names.
To download, the following free capacity size is needed on PC.
y When Copy-on-write SnapShot Function is not installed

Installed cache of the Free Capacity needed on PC
subsystem no compression compression
RKM 1 G bytes/1 controller 1,510 M bytes/1 controller 151 M bytes/1 controller
2 G bytes/1 controller 1,650 M bytes/1 controller 165 M bytes/1 controller
RKS 1 G bytes/1 controller 840 M bytes/1 controller 84 M bytes/1 controller
y When Copy-on-write SnapShot Function is installed

RKS 1 G bytes/1 controller 1,440 M bytes/1 controller 144 M bytes/1 controller
NOTE : When this function is used, the menu other than Logging Data comes not to use it.
Please enter into the Maintenance Mode again by the reset switch of the
Controller, once again, if other menus are used, after this function was used.
(a) Clear the cache of the browser following the procedure shown below so that the old data,
y In the case of Internet Explorer, select the [Tools], [Internet Options], [General],
[Temporary Internet files], and [Delete Files] in this order.
y In the case of Netscape, select the [Edit], [Preferences], [Cache], and [Clear Cache] in this
order.
(b) Please click Full Dump.

WEB 03-0380-01
(c) The following window is displayed. Please click [Save], if it is continued. Please click
(d) If the following window is displayed. Please click [Save] after file name is setting, if it is
(e) The following window is displayed during execution download.

There is no problem although it is displayed that the presumption remaining time is
uncertain.
(f) The download completes.

WEB 03-0390-01

WEB 03-0390-01
3.5.4 Collecting Full Dump (Full Dump(SnapShot))

This function (Full Dump(SnapShot)) is effective only when the priced optional feature, Copy-on-
write SnapShot Function, is installed. If not, this menu frame may not be displayed.
The cache memory access failure occurs when the following window is displayed. Refer to
(WEB 03-0040).
(1) For RKM/RKS

This function (Full Dump(SnapShot)) downloads the logging information of the subsystem. The
downloaded information includes the information in Copy-on-write SnapShot.
Collect Full Dump from each Control Unit.
To download, the following free capacity size is needed on PC.

RKS 1 G bytes/1 controller 1,440 M bytes/1 controller 144 M bytes/1 controller
NOTE : When this function is used, the menu other than Logging Data comes not to use
it.
Please enter into the Maintenance Mode again by the reset switch of the
Controller, once again, if other menus are used, after this function was used.

WEB 03-0400-01
(a) Please click Full Dump(SnapShot).
(b) The following window is displayed. Please click [OK], if it is continued. Please click
(c) The following window is displayed. Please click [Save], if it is continued. Please click

WEB 03-0410-01
(d) If the following window is displayed. Please click [Save] after file name is setting, if it is
(e) The following window is displayed during execution download.

There is no problem although it is displayed that the presumption remaining time is
uncertain.
(f) The download completes.

WEB 03-0420-01

WEB 03-0420-01
3.6 Other
The others are set up.
The contents that were set up in this function are not taken over and not step over the PS-
OFF/ON.
(1) Please confirm the setting value of each item and click the check box of the item that the
setting contents are changed. Please click [Change], if the setting contents are updated.

Configuration Clear Mode
The transfer information initialization as the booting is designated.
[Take Over] : Transfer booting (default).
[Configuration Clear] : Default booting.
World Wide Name Check Mode
The World Wide Name Check Mode as the booting is designated.
[Enable] : The WWN Check is executed (default).
[Disable] : The WWN Check is not executed.
Data Down Grade Check Mode
The Data Down Grade Check as the Update Microprogram (update) installation is
designated.
[Enable] : The Down Grade Check is executed (default).
[Disable] : The Down Grade Check is not executed.
(2) Please confirm that the setting value was updated.

WEB 03-0430-01
3.7 Return Method to the Normal Mode

The method that returns from the Maintenance Mode to the Normal Mode is shown.
(1) Please click [Go To Normal Mode]. The button of [Go To Normal Mode] is in the top and down
on the menu window. Please select either button.
(2) The following window is displayed during execution.
(3) If the following confirmation message is displayed for a while. Please click [OK], if it is
continued.
(4) The following window is displayed during execution.
(5) If the return to the Usually Mode completes, the array device becomes the Ready status.
Please confirm that the READY LED of the device entire surface is lighted. (Usually Controller
recovers in about three minutes.)

WEB 03-0440-01
Revision Control
Legend for revision codes : AD : Addition CH : Change CR : Correction DL : Deletion

REV. Date DRW CHKD APPD Sheet No. Description Code
0 Apr.28.2005 A.Hirasawa A.Hirasawa Y.Takeuchi All Issued -
1 May.20.2005 A.Hirasawa A.Hirasawa Y.Takeuchi All All pages were re-numbers and CH/CR
correction was changed.
Hitachi RAID ManagerRAID CH
manager.
SPC-2 Mode was added at Host AD
Connection Mode 2.
User PortUser Management CH
Port
Changed SNM screen. CH
A description of Remote Adapter in DL
the Addition/ Subtraction/ Relocation
was deleted.
Installation Figure of I/F Board was CH
changed. (Positioning hole/pin)
Regarding Fibre Channel Failure was CH
changed in Troubleshooting 5.
Flow chart of 6.1.5, 6.1.6 and 6.1.7 in CH
the Troubleshooting was changed.
Action(s) to be taken of 8.2 (5-3) and CH
(6) in the Troubleshooting was
changed.
Message code was added. AD
(HH2B00, HH2C00, HH2D00,
HZ0T00, I0030x, RBE800,
RBE900)
Message code was deleted. AD
(HH2300, HH2400, R50000,
R50100)
Battery switch was changed. CH
(There may be ...installed.) was AD
added to Procedure for replacement
with the power turned on.

REV 0000-01

Df7150all - df700 Maintenance Manual Rev1 05-05 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Df7150all - df700 Maintenance Manual Rev1 05-05 PDF

Uploaded by

Copyright:

Available Formats

DF700 Hitachi Proprietary K6603122-

Copyright 2005, Hitachi, Ltd.

Copyright 2005, Hitachi, Ltd.

General Cautionary Notes

The part to be unpacked and

The clip side of wrist strap:

Copyright 2005, Hitachi, Ltd.

HP is a company name of Hewlett Packard Company, in the U.S.A.

Copyright 2005, Hitachi, Ltd.

EMI Regulation Labels Affixed on the Subsystem.

The EMI test was done in the following configuration.

Copyright 2005, Hitachi, Ltd.

Model Name Conversion

Floor model (RKM + H1J)

DF-F700- HT-F4064- Optional component

Copyright 2005, Hitachi, Ltd.

For the composition of the each volume, refer to the following.

Maintenance Manual - for Safety Summary :

Maintenance Manual - for Theory :

Maintenance Manual - for Installation :

Maintenance Manual - for Microprogram :

Copyright 2005, Hitachi, Ltd.

Chapter 3. Procedure for Isolating Cause of Disk Drive Failure when

Copyright 2005, Hitachi, Ltd.

Maintenance Manual - for System Parameter :

Maintenance Manual - for Addition/Subtraction/Relocation :

Maintenance Manual - for Troubleshooting :

Copyright 2005, Hitachi, Ltd.

Maintenance Manual - for Messages:

Maintenance Manual - for Replacement :

Maintenance Manual - for Parts Catalog :

Maintenance Manual - for WEB :

Copyright 2005, Hitachi, Ltd.

Preface ............................................................................................... GENE 0010

Cautionary Notes ................................................................................... GENE 0020

Note................................................................................................... GENE 0050

Model Name Conversion .......................................................................... GENE 0060

Manual Composition ............................................................................... GENE 0070

Chapter 2. Outline of Subsystem .......................................................... THEO 02-0000

Copyright 2005, Hitachi, Ltd.

Chapter 3. Major Specifications of the Subsystem ..................................... THEO 03-0000

Chapter 4. Theory of Operation ........................................................... THEO 04-0000

Chapter 5. Outline of P.P. ................................................................... THEO 05-0000

Copyright 2005, Hitachi, Ltd.

Copyright 2005, Hitachi, Ltd.

2.5 Installing Components............................................................ INST 02-0170

Chapter 3. Installing Rackmount Model.................................................... INST 03-0000

Copyright 2005, Hitachi, Ltd.

Chapter 2. Procedure for Recovery from a Failure ................................... MICRO 02-0000

Chapter 3. Procedure for Isolating Cause of Disk Drive Failure when

Chapter 2. Setting Host Group ............................................................ SYSPR 02-0000

Chapter 3. Setting the RAID/LU/Spare Disk ............................................. SYSPR 03-0000

Chapter 4. Setting Configuration Information.......................................... SYSPR 04-0000

Copyright 2005, Hitachi, Ltd.

Chapter 5. Setting Host Connection Parameters ...................................... SYSPR 05-0000

Chapter 6. Setting an Extra-cost Optional Feature ................................... SYSPR 06-0000

Chapter 7. System Parameter Setting List .............................................. SYSPR 07-0000

Copyright 2005, Hitachi, Ltd.

Chapter 2. Subtracting Optional Components ............................................ADD 02-0000

Chapter 3. Relocation/Removal Work.......................................................ADD 03-0000

Copyright 2005, Hitachi, Ltd.

Chapter 2. Before Maintenance Work .................................................... TRBL 02-0000

Chapter 3. Before Starting WEB Connection ............................................ TRBL 03-0000