HiCommand® Device Manager Error Codes

Hitachi Device Manager Software

Error Codes

F

AST

F

IND

L

INKS

Document Organization

Software Version

Getting Help

Contents

MK-92HC016-23

Copyright © 2010 Hitachi, Ltd., Hitachi Data Systems

Corporation, ALL RIGHTS RESERVED

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. (hereinafter referred to as “Hitachi”) and Hitachi Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).

Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any time without notice and assume no responsibility for its use. This document contains the most current information available at the time of publication. When new and/or revised information becomes available, this entire document will be updated and distributed to all registered users.

All of the features described in this document may not be currently available. Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information on feature and product availability.

Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of Hitachi Data

Systems’ applicable agreement(s). The use of Hitachi Data

Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems.

By using this software, you agree that you are responsible for: a) Acquiring the relevant consents as may be required under local privacy laws or otherwise from employees and other individuals to access relevant data; and b) Ensuring that data continues to be held, retrieved, deleted or otherwise processed in accordance with relevant laws.

Hitachi is a registered trademark of Hitachi, Ltd. in the United

States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi in the United

States and other countries.

Lightning 9900, Hitachi USP and Hitachi USP V are trademarks of Hitachi Data Systems Corporation in the United States and other countries.

All other trademarks, service marks, and company names are properties of their respective owners.

Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation. ii

Hitachi Device Manager Error Codes

Contents

Preface................................................................................................... v

Intended Audience ..............................................................................................vi

Software Version.................................................................................................vi

Release Notes.....................................................................................................vi

Document Revision Level .....................................................................................vi

Document Organization ..................................................................................... viii

Referenced Documents........................................................................................ix

Document Conventions.........................................................................................x

Convention for Storage Capacity Values ................................................................ xi

Getting Help .......................................................................................................xi

Comments......................................................................................................... xii

Hitachi Device Manager Messages.......................................................... 1-1

Device Manager Server Messages .......................................................................1-2

Device Manager Web Client Messages............................................................. 1-124

Device Manager Agent Messages.................................................................... 1-163

Device Manager Agent's Provisioning Manager Messages.................................. 1-190

Device Manager Agent's Replication Manager Messages ................................... 1-209

Device Manager VDS Provider Messages ......................................................... 1-212

Device Manager CLI Messages ....................................................................... 1-214

Device Manager CLIEX Messages.................................................................... 1-228

Universal Storage Platform V/VM Messages ............................................ 2-1

Details About Universal Storage Platform V/VM Messages.....................................2-2

Hitachi USP Messages ........................................................................... 3-1

Details About Hitachi USP Messages ...................................................................3-2


Lightning 9900V series Messages........................................................... 4-1

Details About Lightning 9900V series Messages................................................... 4-2

Lightning 9900 Messages...................................................................... 5-1

Details About Lightning 9900 Messages.............................................................. 5-2

Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V series, and Thunder 9200 series Messages ............................................................................. 6-1

Details About Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V, and Thunder 9200

Messages .................................................................................................. 6-2

Alerts Produced by Hitachi Device Manager Software .............................. 7-1

Alerts Output by Hitachi Device Manager............................................................ 7-2

Trap Information Output by Storage Subsystems ................................................ 7-3

Alerts about Storage Subsystem Components ................................................... 7-28

Error Messages from the Hitachi Storage Command Suite Common

Component .................................................................................... 8-1

Error Messages Output by Hitachi Storage Command Suite Common Component... 8-2

Error Messages from HiRDB .................................................................. 9-1

Error Messages Output by HiRDB....................................................................... 9-2

Troubleshooting ..................................................................................10-1

General Troubleshooting ................................................................................. 10-2

Calling the Hitachi Data Systems Support Center............................................... 10-3

Acronyms and Abbreviations .................................................................... 1

iv Contents


Preface

This document lists and describes the error codes and error messages that may be reported by the Hitachi Device Manager.

This preface includes the following information:



Intended Audience



Software Version



Release Notes



Document Revision Level



Document Organization



Referenced Documents



Document Conventions



Convention for Storage Capacity Values



Getting Help



Comments

Notice: The use of Hitachi Tiered Storage Manager and all other Hitachi Data

Systems products is governed by the terms of your agreement(s) with Hitachi

Data Systems.

Preface v


Intended Audience

This document is intended for users who manage systems containing storage subsystems (disk array devices). Such users should have a basic knowledge of:



Data processing and peripheral storage device subsystems and their basic functions,



Hitachi Device Manager and the operating systems (OS) on which it operates (e.g., Windows, Solaris and Red Hat Linux for Device Manager server; Windows, Solaris, AIX, HP-UX, Red Hat Linux and SUSE LINUX for

Device Manager agents),



Relevant operating systems (if using the Device Manager Web Client), such as Windows, Solaris, HP-UX, or Red Hat Linux,



Relevant operating systems (if using Device Manager CLI), such as

Windows, Solaris, AIX, HP-UX, or Red Hat Linux,



Relevant operating systems (if using Device Manager CLIEX), such as

Windows, Solaris, or AIX,



Management tools appropriate to the individual storage subsystem (e.g.,

Storage Navigator for Universal Storage Platform and Lightning 9900V,

DAMP for Thunder 9500V), and



SANs (storage area networks).

Note: The use of Hitachi Device Manager and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data

Systems.

Software Version

This document revision applies to Hitachi Device Manager version 6.4.

Release Notes

Release notes can be found on the documentation CD. Release notes contain requirements and more recent product information that may not be fully described in this manual. Be sure to review the release notes before installation.

Document Revision Level

vi Preface


Revision

MK-92HC016-00

MK-92HC016-01

MK-92HC016-02

MK-92HC016-03

MK-92HC016-04

MK-92HC016-05

MK-92HC016-06

MK-92HC016-07

MK-92HC016-08

MK-92HC016-09

MK-92HC016-10

MK-92HC016-11

MK-92HC016-12

MK-92HC016-13

MK-92HC016-14

MK-92HC016-15

MK-92HC016-16

MK-92HC016-17

MK-92HC016-18

MK-92HC016-19

MK-92HC016-20

MK-92HC016-21

MK-92HC016-22

MK-92HC016-23

Date

November 2002

May 2003

September 2003

February 2004

April 2004

August 2004

October 2004

February 2005

June 2005

July 2005

November 2005

February 2006

May 2006

November 2006

February 2007

June 2007

October 2007

January 2008

May 2008

February 2009

July 2009

October 2009

December 2009

June 2010

Description

Initial Release

Revision 1, supersedes and replaces MK-92HC016-00
























Document Organization

The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter.

The first page of each chapter provides links to the sections in that chapter.

Chapter

Hitachi Device Manager

Messages

Universal Storage Platform

V/VM Messages

Hitachi USP Messages

Lightning 9900V series

Messages

Lightning 9900 Messages

Description

Describes the error messages for Device Manager server, Device

Manager Web Client, Device Manager Agent, Device Manager VDS

Provider, Device Manager CLI, and Device Manager CLIEX.

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Universal Storage Platform V/VM.

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Hitachi USP.

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for the Lightning 9900V series.

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Lightning 9900.

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Hitachi AMS2000/AMS/WMS/SMS,

Thunder 9500V, and Thunder 9200.

Hitachi

AMS2000/AMS/WMS/SMS,

Thunder 9500V series, and

Thunder 9200 series

Messages

Alerts Produced by Hitachi

Device Manager Software

Error Messages from the

Hitachi Storage Command

Suite Common Component

Error Messages from HiRDB

Troubleshooting

Acronyms and Abbreviations

Outputs alerts to the event log or to the syslog file on the Device

Manager Server. This chapter lists and describes those alerts.

Lists and describes the error messages output by the Hitachi Storage

Command Suite Common Component.

Lists and describes the error messages output by the HiRDB.

Provides resources for troubleshooting Device Manager.

Defines the acronyms and abbreviations used in this document. viii Preface


Referenced Documents

The following Hitachi referenced documents can be found on the applicable

Hitachi documentation CD:

Hitachi Storage Command Suite:



Hitachi Device Manager Server Configuration and Operation Guide, MK-

08HC157



Hitachi Storage Command Suite Server Installation Guide, MK-98HC150



Hitachi Device Manager Command Line Interface (CLI) User's Guide,

MK-91HC007



Hitachi Device Manager Agent Installation Guide, MK-92HC019

Hitachi Enterprise Storage Systems documents:



User and Reference Guide for USP, MK-94RD231



Hitachi Lightning 9900V Series User and Reference Guide, MK-92RD100



Hitachi Lightning 9900 User and Reference Guide, MK-90RD008

Hitachi Modular Storage Systems documents:



Hitachi Thunder 9500 V Series User and Reference Guide, MK-92DF601



Hitachi Thunder 9200 User and Reference Guide, MK-90DF504

Other Hitachi documents:



Hitachi Device Manager Server XML API Manual, MK-91HC008


Document Conventions

This document uses the following typographic conventions:

Convention Description

Bold

Italic

screen/code

Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK.

Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file

Note: Angled brackets (< >) are also used to indicate variables.

Indicates text that is displayed on screen or entered by the user.

Example:

# pairdisplay -g oradb

< > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example:

# pairdisplay -g <group>

Note: Italic font is also used to indicate variables.

[ ] square brackets

Indicates optional values. Example: [ a | b ] indicates that you can choose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options or arguments.

Examples:

[ a | b ] indicates that you can choose a, b, or nothing.

{ a | b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important and/or additional information.

Provides helpful information, guidelines, or suggestions for performing tasks more effectively.

Tip

Caution Warns the user of adverse conditions and/or consequences (e.g., disruptive operations).

WARNING Warns the user of severe conditions and/or consequences (e.g., destructive operations). x Preface


Convention for Storage Capacity Values

Physical storage capacity values (e.g., disk drive capacity) are calculated based on the following values:

1 KB

1 MB

1 GB

1 TB

1 PB

1 EB

Physical Capacity Unit

1,000 bytes

1,000 2 bytes

1,000

3

bytes

1,000

4

bytes

1,000 5 bytes

1,000

6

bytes

Value

Logical storage capacity values (e.g., logical device capacity) are calculated based on the following values:

Logical Capacity Unit

1 KB

1 MB

1 GB

1 TB

1 PB

1 EB

1 BLOCK

1,024 (2 10 ) bytes

1,024 KB or 1,024

2

bytes

1,024 MB or 1,024

3

bytes

1,024 GB or 1,024 4 bytes

1,024 TB or 1,024

5

bytes

1,024 PB or 1,024

6

bytes

512 BYTES

Value

Getting Help

The Hitachi Data Systems Support Center staff is available 24 hours a day, seven days a week. To reach us, please visit the support Web site for current telephone numbers and other contact information: http://www.hds.com/services/support/ . If you purchased this product from an authorized HDS reseller, contact that reseller for support.

Before calling the Hitachi Data Systems Support Center, please provide as much information about the problem as possible, including:



The circumstances surrounding the error or failure.



The exact content of any error message(s) displayed on the host system(s).


Comments

Please send us your comments on this document: [email protected]

.

Include the document title, number, and revision, and refer to specific section(s) and paragraph(s) whenever possible.

Thank you! (All comments become the property of Hitachi Ltd., Hitachi Data

Systems Corporation.) xii Preface



Hitachi Device Manager Messages

This chapter describes the error messages for the Hitachi Device Manager server, Web Client, Agent, VDS Provider, CLI, and CLIEX.



Device Manager Server Messages



Device Manager Web Client Messages



Device Manager Agent Messages



Device Manager Agent's Provisioning Manager Messages



Device Manager Agent's Replication Manager Messages



Device Manager VDS Provider Messages



Device Manager CLI Messages



Device Manager CLIEX Messages

Hitachi Device Manager Messages


1-1

Device Manager Server Messages

Hitachi Device Manager displays error messages when errors occur. All error notifications, including Server errors, are displayed at the Hitachi Device

Manager client (e.g., Web Client, CLI, third-party application). The error message includes:



Error code: The error code range indicates the type of error (see Table 1-

1). The error code indicates the specific error condition.



Error level: The error level indicates the severity of the error:

I: Non-error information

W: Warning

E: Error



Description: The error description provides information on the error condition.

Table 1-1 Server Error Code Ranges

Error Code Range

KAIC00000-KAIC00999

Description

Device Manager Server (SRV) errors.

KAIC02000-KAIC02999

Security (SEC) layer errors (user authentication, etc.).

See:

Table 1-2

Table 1-3

Table 1-4

KAIC06000-KAIC06999

KAIC07000-KAIC08999

Storage array errors (SNMP, etc.).

Command (Agent) errors.

Table 1-5

Table 1-6

Table 1-7

Table 1-8

Table 1-9

Table 1-10

Table 1-11

Note: Variable parameters in the error description are represented as

"parameter" or "value". These parameters or values are replaced in the message by the appropriate parameter or value. For example, "name" in the message "Duplicate name error, "name" already exists in the collection

" is replaced with the name that was duplicated.

1-2 Hitachi Device Manager Messages


The tables shown below list Hitachi Device Manager server error messages, and provide recommended actions for resolving those errors. The error messages are listed in numerical order of their error code. For errors whose recommended action is "Contact the Support Center", first collect maintenance information by executing the hcmdsgetlogs command, and then contact the

Hitachi Data Systems Support Center (see

Calling the Hitachi Data Systems

Support Center

for contact information).

Table 1-2 KAIC00000-KAIC00999: Hitachi Device Manager Server Errors

Error Code

KAIC00000-E

KAIC00001-E

KAIC00002-E

KAIC00003-E

KAIC00004-E

KAIC00100-E

KAIC00101-E

KAIC00102-E

KAIC00103-E

KAIC00104-E

KAIC00105-E

KAIC00106-E

KAIC00107-E

Description Recommended Action

An unspecified error was encountered.

An unspecified server error was encountered.

Contact the Support Center.

An error occurred in initializing the Device Manager Server.

See the server "error.log" for additional details.

The servlet instance is invalid. A request referenced a servlet not supported by Device Manager.

The transfer request format is incorrect.

Server initialization error: an invalid HTTP port number

"port-number" has been specified.

Server initialization error: an invalid HTTPS port number

"port-number" has been specified.

Server initialization error: an invalid document root directory

"directory-name" has been specified.

The transfer request format is invalid; correct the format, and then retry.

Check the Device Manager Server manual, confirm the value of "server.properties", and restart the Device Manager Server.

Server initialization error: an invalid bind address "bind-

address" has been specified.

Server initialization error: an unsupported JRE version "JRE-

version" has been specified.

Server initialization error:

Unable to load Servlet v2.2 classes.

Server initialization error:

Unable to load SNMP classes.

Make sure the version is JRE version, and restart Device Manager Server.

Make sure the servlet (JSDK v2.2+) can be loaded.

Server initialization error: An attempt to load Service

Modules has failed.

Make sure the Sun SNMP (JDMK) classes can be loaded and restart the Device Manager

Server.

The direct cause of this error is the immediately preceding error. Carry out the recommended action for that error. If this error continues to occur even after performing the action, or if these actions are inapplicable, contact the Support Center.



1-3

1-4

Error Code

KAIC00108-E

KAIC00110-E

KAIC00112-E

KAIC00113-E

KAIC00114-E

KAIC00115-E

KAIC00116-E

KAIC00120-E

KAIC00121-E

KAIC00123-E

KAIC00124-E

KAIC00125-E

KAIC00126-E

KAIC00150-E

KAIC00180-E

Description

Server initialization error: An error occurred while the entry

"entry-name" was loaded in the Device Manager Server

KeyStore.

An attempt to start Server failed: Serious errors occurred checking or updating the database.

The maximum number of connection threads, "number-

specified-for-maxThreads", was exceeded.

An attempt to construct

ServiceConnection failed.

An attempt to start the HTTP server on port "port-number" failed.

An attempt to start the HTTPS server on port "port-number" failed.

Server initialization error: The

IP address of localhost is unsolvable.

The config file

"server.properties" cannot be read.

Unable to read servlet config file "servlet.properties".

The MIME types file cannot be read.

During an attempt to change the user, group or root directory, and error occurred with the message "error-

message".

An attempt to read the configuration file

"product.properties" has failed.

An attempt to read the configuration file "file-name" has failed. Error detail : "error-

details".

An attempt to find the entry

"entry-name" in the Device

Manager Server KeyStore has failed.

Common Component is not installed.

Recommended Action


Check the Device Manager Server manual, confirm the value of "server.properties", and restart the Device Manager Server.


Check "server.http.port" in

"server.properties".

Check "server.https.port" in

"server.properties".


Check "server.properties", and restart the

Device Manager Server.

Check "servlet.properties", and restart the


Check "mime.properties", and restart the



Check the configuration file

"product.properties", and then restart the


Remove the cause of the error, and then restart the Device Manager Server. If this error continues to occur even after performing the action, contact the Support

Center.

The Device Manager Server KeyStore must be present and contain at least one entry to run the Device Manager Server in secure mode.




Error Code

KAIC00181-E

KAIC00182-E

KAIC00183-E

KAIC00184-E

KAIC00300-E

KAIC00405-E

KAIC00407-E

KAIC00408-E

Description

An attempt to set the installation destination of

Common Component has failed.

An attempt to acquire the

Common Component address has failed. ("method-name")

An error occurred in initializing the Provisioning Manager.

("method-name")

A directory necessary for storage subsystem management does not exist.

The Device Manager environment is invalid.

(directory name = directory-

name)

An attempt to bind the port

"port-number" for receiving the SNMP Trap has failed. This port is being used by other software.

An unexpected error occurred in the email notification functionality.

An email send error occurred.

(unsent email = (recipient email address = "recipient-

email-address"), Alert =

(messageID = "alert-ID", number = "number", type =

"type", source = "source", severity = "severity", component = "component", description = "description", actionToTake = "action-to-

take", data = "data", timeOfAlert = "time-of-alert"))

An attempt to connect to the

SMTP server has failed. (SMTP server = (host = "hostname-

or-IP-address", port = "port-

number"), unsent email =

(recipient email address =

"recipient-email-address"),

Alert = (messageID = "alert-

ID", number = "number", type

= "type", source = "source", severity = "severity", component = "component", description = "description", actionToTake = "action-to-

take", data = "data", timeOfAlert = "time-of-alert"))


Check "server.base.home" in

"server.properties", and contact the Support

Center.


Terminate any other software using this port, or set 'false' for

"server.dispatcher.daemon.receiveTrap" in the "dispatcher.properties" file, and restart



Make sure the following environment related items are correct:





Status and settings of the SMTP server

Status of the network

Make sure the following items related to the environment and the sending of email are correct:







Property settings for sending email

Status and settings of the SMTP server

Status of the network



1-5

1-6

Error Code

KAIC00409-E

KAIC00410-E

KAIC00411-E

KAIC00412-E

KAIC00413-E

KAIC00414-E

Description

A connection to the SMTP server could not be established because authentication failed.

(SMTP server = (host =

"hostname-or-IP-address", port = "port-number"), unsent email = (recipient email address = "recipient-email-

address"), Alert = (messageID

= "alert-ID", number =

"number", type = "type", source = "source", severity =

"severity", component =

"component", description =

"description", actionToTake =

"action-to-take", data =

"data", timeOfAlert = "time-of-

alert"))

The value specified for a property is incorrect. The system will use the default value for the property. (file name = "file-name", property name = "property-name", specified value = "specified-

value", default value =

"default-value")

Authentication information for connecting to the SMTP server has not been set. The email will be sent without SMTP authentication.

The recipient email address is invalid. (user ID = "user-ID", recipient email address =

"recipient-email-address") The email will not be sent to this user ID.

The template file was not found. (template file path name = "template-file-path-

name") The default template file will be used to send the email.

An error occurred while the template file was being loaded.

(template file path name =

"template-file-path-name", detailed information =

"detailed-information") The default template file will be used to send the email.


Change the SMTP server settings so that the relevant user can be authenticated. Also, use the command for setting the SMTP authentication user information to set the

SMTP authentication user information (user

ID and password).

If the default value does not cause any problems, no further action is required. If you specify a value different from the default value, make sure that the property settings are correct, and then restart the Device

Manager server.

Set the SMTP authentication user information

(user ID and password) by using the hdvmmodmailuser command. If SMTP authentication is not required for the email, no further action is required.

Specify a valid address by using the user management functionality's Edit Profile dialog box.

Check whether the template file indicated in the message exists. If you use the default template file, no further action is required.

Remove the cause of the error according to the detailed information. If you use the default template file, no further action is required.



Error Code

KAIC00415-E

KAIC00416-E

KAIC00417-E

KAIC00418-E

KAIC00419-E

KAIC00420-E


The size of the template file is too large. (template file name

= "template-file-name", template file size (bytes) =

"template-file-size-in-bytes", maximum file size (bytes) =

"maximum-file-size-in-bytes")

The default template file will be used to send the email.

An invalid header exists.

(template file name =

"template-file-name", line number = "line-number", header name = "header-


A header has not been specified. (template file name

= "template-file-name", header name = "header-


The same header name is duplicated. (template file name

= "template-file-name", line number = "line-number", header name = "header-


The header section in the template file contains an invalid line. The name and contents of a header must be separated with a colon (:).


"template-file-name", line number = "line-number") The default template file will be used to send the email.

In the template file, the size of a line is too large. (template file name = "template-file-

name", line number = "line-

number", detected line size

(bytes) = "detected-line-size-

in-bytes", maximum line size

(bytes) = "maximum-line-size-

in-bytes") The default template file will be used to send the email.

Revise the contents of the template file, and reduce the file size. If you use the default template file, no further action is required.

Revise the characters used in the header name specified in the template file. If you use the default template file, no further action is required.

Revise the headers specified in the template file. If you use the default template file, no further action is required.

Revise the contents of the template file to reduce the line size. If the default template file is used, no action is required.



1-7

1-8

Error Code

KAIC00422-E

KAIC00423-E

KAIC00424-E

KAIC00425-E

KAIC00426-E

KAIC00427-E

KAIC00428-E

KAIC00500-E

KAIC00501-E

KAIC00504-E

KAIC00505-E

KAIC00506-E

Description

The user ID entered for SMTP authentication is invalid.

The password entered for

SMTP authentication is invalid.


Enter a valid user ID for SMTP authentication, using from 1 to 64 characters. Specifiable characters for an SMTP authentication user ID are as follows:

A to Z, a to z, 0 to 9, and the following characters:

- _ . , @ ! # $ % & ' * + = ? ^ |

When specifying a password for SMTP authentication, enter a valid password using from 0 to 64 characters. Specifiable characters for the SMTP authentication password are as follows:

A to Z, a to z, 0 to 9, and the following characters:

- _ . , @ ! # $ % & ' * + = ? ^ |

The password can be omitted.

Specify the correct user ID and password. The user ID or password of

Device Manager is invalid.

The entered Device Manager user does not have permission to execute the command.

An internal error occurred.

The command syntax is invalid.

In the template file, there is no blank line to indicate the end of the header section.


"template-file-name")

The request contained improperly formatted data.

The device is not supported by


Explanation = "subsystem".

"specified-name" is a reserved name and cannot be used as a top-level logical group name.

The Device Manager server does not support the specified array family.

Simultaneous LUN Scans of the subsystem are not allowed.

When executing the command, make sure the

Device Manager user has the Admin permission.


Revise the command syntax.

Add a blank line at the end of the header section. If the default template file is used, no action is required.

Correct the request, and then retry.

Confirm that the IP Address in the request is correct. It is also possible that a configuration error exists in the subsystem.

The CLI or another client has tried to use a reserved group name (e.g., Unallocated). You cannot use the names "Unallocated" or "LUN

Scan" for a top-level logical group.

Check the array family.

Only one LUN Scan can be performed on a storage array at a time. Make sure that only one Device Manager Server is actively managing the subsystem.



Error Code

KAIC00507-E

KAIC00508-E

KAIC00509-E

KAIC00510-E

KAIC00511-E

KAIC00513-E

KAIC00514-E

KAIC00515-E

KAIC00530-E

KAIC00600-E

KAIC00601-E

KAIC00604-E

KAIC00700-E

KAIC00800-E

KAIC00801-E

KAIC00802-E

KAIC00805-E

KAIC00806-E

KAIC00807-E


The command "command-

name" is not supported under this API version.

The command "command" is not supported for the array family "family-name" under this API version.

This Device Manager Server does not support the API version "version".

The family of the target storage is not "storage-family".

The definition of storage name

"storage-name" is invalid.

The servlet name "xml-servlet-

name" in the request does not match the specified servlet name "specified-servlet-

name".

The command "specified API

name" is not supported by the


The executed command

"command-name" does not support the specified array family in this API version.

Device Manager Server does not support the operation by

API version "version" for this subsystem.

An internal server error occurred.

Check the Device Manager Server XML API manual and make sure that the running API version supports the command.

Make sure that the specification is valid.

Make sure the storage name relations in the config files are valid.

Make sure that the servlet name in the request is same as the specified servlet name.

Check the Device Manager Server XML API manual and make sure that the running API supports the command.

Find out which API versions support this command.


If this problem persists, contact the Support

Center.

Make sure that the objects are valid. An invalid parameter of a managed object was detected.

An attempt to initialize the

Common Component Logger has failed.




An internal error occurred while Dynamic Link Manager was starting.

An internal error occurred while NAS Manager was starting.

Make sure that the Common Component is installed.


An attempt to start NAS

Manager has failed.


Center.

An attempt to start has failed. Contact the Support Center.



1-9

1-10

Error Code

KAIC00809-E

KAIC00810-E

KAIC00811-E

KAIC00812-E

KAIC00813-E

KAIC00814-E

KAIC00816-E

KAIC00817-E

KAIC00818-E

KAIC00819-E

KAIC00820-E

KAIC00821-E

KAIC00822-E

KAIC00823-E

Description

The specified program cannot start because of a communication failure with the host agent.

The parameter "parameter-

name", which is required to start the specified program, is missing.

An error occurred in Common

Component. Device Manager cannot be started.

A file access error occurred.

Device Manager cannot be started.

An attempt to connect the device at IP Address "IP-

address" has failed. NAS

Manager cannot be started.

The correct IP address for the device is not found. NAS


An I/O error occurred. Device


Startup cannot be performed because an I/O error occurred.

An I/O error occurred. NAS


The startup method for

"Function the user tried to

execute" is invalid.

Settings for linking with program-name(Disk Array

Management Program or

Storage Navigator Modular) are invalid.

An internal error occurred while Disk Array Management

Program was starting.

An attempt to start Disk Array

Management Program has failed. The Disk Array

Management Program service might not be running correctly, or a setting in the launchapp.properties file might be incorrect, or a setting related to the Disk Array

Management Program network might be incorrect.

Disk Array Management

Program could not be started because an I/O error occurred.



Center.


Check the state of the network and the device.


Check the operating environment. If this problem persists, contact the Support Center.

Use Device Manager Web Client to start

"Function the user tried to execute".

Revise the settings for linking with programname(Disk Array Management Program or

Storage Navigator Modular) by referring to the Device Manager Server manual. If this problem persists, contact the Support Center.


Make sure the Disk Array Management

Program service is running correctly, the settings in the launchapp.properties file are correct, and the settings related to the Disk

Array Management Program network are correct. Also, if the Storage Navigator

Modular service is running, stop it. If the error continues to occur after you perform these actions, or if the actions do not apply, contact the Support Center.

Check the operating environment. If this problem persists, contact the Support Center.



Error Code

KAIC00824-E

KAIC00825-E

KAIC00826-E

KAIC00827-E

KAIC00828-E

Description

An attempt to delete registered unit information from Disk

Array Management Program has failed.

The launch parameter is invalid.

A Disk Array Management

Program server error occurred.

(error code = "Error Code from

DAMP Server", error message

= "Error Message of DAMP

server error code")

A setting for using "Disk Array

Management Program" has not been made or is invalid. The corresponding storage subsystem is not registered or is incorrectly registered with

Disk Array Management

Program. To use "Disk Array

Management Program", a setting for linking with Disk

Array Management Program is necessary. Confirm that the corresponding storage subsystem is correctly registered in Disk Array

Management Program.

Startup cannot be performed because a refresh has not been executed for the storage subsystem.



Reference the Device Manager Server manual and revise the settings for linking with related products. If this problem persists, contact the

Support Center.

Refresh the storage subsystem.



1-11

Error Code

KAIC00829-E

KAIC00830-E

KAIC00831-E

KAIC00832-E

KAIC00833-E

Description

An internal error occurred while Storage Navigator

Modular was starting.

An unexpected error occurred while Storage Navigator

Modular was starting.

An error occurred in the

Storage Navigator Modular.

(error code = "error code from

Storage Navigator Modular

Server", error message =

"error message for Storage

Navigator Modular error code")

A setting for using "function

name(Physical View or Storage

Navigator Modular)" has not been made or is invalid. The corresponding storage subsystem is not registered or is incorrectly registered with

Storage Navigator Modular. To use "function name(Physical

View or Storage Navigator

Modular)", a setting for linking with Storage Navigator

Modular is necessary. Confirm that the corresponding storage subsystem is correctly registered in Storage Navigator

Modular.

An attempt to start Storage

Navigator Modular has failed.

The Storage Navigator Modular service might not be running correctly, or a setting in the launchapp.properties file might be incorrect, or a setting related to the Storage

Navigator Modular network might be incorrect.




Support Center.

Make sure the Storage Navigator Modular service is running correctly, the settings in the launchapp.properties file are correct, and the settings related to the Storage Navigator

Modular network are correct. Also, if the Disk

Array Management Program service is running, stop it. If the error continues to occur after you perform these actions, or if the actions do not apply, contact the Support

Center.



Error Code

KAIC00834-E

KAIC00835-E

KAIC00836-E

KAIC00837-E

KAIC00838-E

KAIC00839-E

KAIC00840-E

Description

A setting for using "function

name(Physical View or Storage

Navigator Modular)" has not been made or is invalid.

Storage Navigator Modular cannot be accessed

(URL="access URL"). To use

"function name(Physical View

or Storage Navigator

Modular)", a setting for linking with Storage Navigator

Modular is necessary. Revise the access URL and alias settings. Specify the Storage

Navigator Modular URL for the launchapp.damp.url property in the launchapp.properties file. To set alias information, execute the alias information setting command (HWSAlias).

To apply the settings, restart

Common Component and


The target storage subsystem does not support launching.

(microcode version =

"microcode version")

The registration for the linking functions failed

(cause="cause"). Check again after some time.



Support Center.

Check the version of the storage subsystem microcode.

Access to the storage subsystem may be in conflict. Please wait and then retry the operation. If this error continues to occur, the value set for server.http.host

in the server.properties

file might be invalid.

Refer to the Device Manager Server manual and, if necessary, revise the value set for server.http.host

. If you change the setting, restart the Device Manager server. If this problem still occurs after these actions, contact the Support Center.

Delete unnecessary users from storage subsystem, and then retry the operation.

The launch has failed. No more launch users can be registered because the maximum number of launch users has already been registered in the specified storage subsystem.

The launch has failed. A user

ID that is the same as the launch user ID is already registered in the storage subsystem.

An internal error occurred while Storage Navigator was starting.

The launch has failed. The configuration of purchasable optional features on the storage subsystem might have changed.

Delete the already registered user ID from the storage subsystem, and then retry the operation.


Refresh the storage subsystem, and then try again.



1-13

1-14

Error Code

KAIC00841-E

KAIC00843-E

KAIC00850-E

KAIC00851-E

KAIC00852-E

KAIC00853-E

KAIC00854-E

KAIC00855-E

KAIC00856-E

KAIC00857-E

KAIC00858-E

Description

The launch has failed. Storage

Navigator Modular (for Web) set for linking does not support the specified subsystem.

The launch has failed. Based on the current Device Manager server settings, the specified subsystem cannot be launched.

An attempt to read a file has failed. The file does not exist or you do not have read permission for it. (file path =

"file path")

An attempt to create a temporary file has failed. You do not have write permission or disk space is insufficient.

(file path = "file path")

Configuration of the remote connection settings for the

DBMS has failed. Disk space is insufficient.


DBMS has failed. An internal error occurred.


DBMS has failed. Execution of an internal command failed.

(executed command =

"executed command")

An error occurred while a value was being entered from standard input.

An internal error occurred while executing the Tuning

Manager connection setup tool.

An internal error occurred while processing to set up database users for other suite products.


DBMS has failed. Execution of an internal command failed.

(executed command =

"executed command", exit code = "exit code", command message = "command

message")


Check the version of Storage Navigator

Modular (for Web).

If the specified storage subsystem is managed using an IPv6 IP address, specify the IPv6 IP address or host name for the

"server.http.host" property in the

"server.properties" file.

Make sure that the file exists and that you have read permission for it, and then execute the setup tool again.

Make sure that you have write permission and that disk space is sufficient, and then execute the setup tool again.

Make sure disk space is sufficient, and then execute the setup tool again.


Execute the setup tool again.




Error Code

KAIC00859-E

KAIC00860-E

Description


DBMS has failed. The Common

Component service is running.

The storage array was not found in the Device Manager database.


Stop the Common Component service, and then execute the setup tool again.

Check the coding of storage array.

Table 1-3 KAIC01000-KAIC01999: Translation Errors (HTTP, XML format)

Error Code

KAIC01000-E

KAIC01001-E

KAIC01003-E

KAIC01011-E

KAIC01012-E

KAIC01013-E

KAIC01014-E

KAIC01015-E

KAIC01016-E

KAIC01017-E

KAIC01018-E

Error Message

An unspecified XML translation error was encountered.

XML translation error: An error occurred parsing the XML: "XML-

parser-error-message".

XML translation error: Posted entity is not XML.

"attribute-value" is not a valid value for parameter "attribute-

name". Enter a parameter of the

"attribute-data-type" type.

XML translation error: An internal error occurred.

An invalid element "element-

name" was specified in the XML request.

An invalid parameter

"parameter-name" was specified in the XML request element

"element-name".

An invalid value was specified for the parameter "parameter-

name" in the XML request element "element-name".

An invalid child element "child-

element-name" was specified in the XML request element

"parent-element-name".

An attempt to execute a request has failed. Under the current license, the user who made the request does not have permission to execute commands.

An attempt to execute a request has failed. Under the current license, the specified command cannot be executed.



Check the request code.

Correct the value of "attribute-data-type", and then retry.


Check the request code.

Execute this command as a user who has

Core License permissions.

This command can only be executed when using the Full License.



1-15

1-16

Error Code

KAIC01019-E

KAIC01021-E

KAIC01022-E

Error Message Recommended Action

The license is invalid.

The format of command option 2 is incorrect.

The name "option-name" is specified twice for command option 2.

Specify either the Full License or Core

License.

Revise the request, and then retry the operation.

Table 1-4 KAIC02000-KAIC02999: Security Layer Errors: User

Authentication, Etc

Error Code

KAIC02001-E

KAIC02002-E

KAIC02004-E

KAIC02006-E

KAIC02007-E

KAIC02009-E

KAIC02010-E

KAIC02011-E

KAIC02012-E

KAIC02013-E

KAIC02014-E

KAIC02015-E

KAIC02016-E

KAIC02017-E

KAIC02018-E


Duplicate user group names are not allowed.

The user group was not found in the Device Manager database.

The rule was not found in the

Device Manager database.

The user ID or the password is incorrect.

Duplicate user IDs are not allowed.

The record was not found in the Device Manager database.

Duplicate records are not allowed.

The user "user-ID" has an active request, and cannot be deleted.

The specified user group cannot be added under this API version.

The specified user cannot be added under this API version.

Access permission error.

An internal error occurred during user authority checking.

The specified logical group is already being used by another user group.

The specified user group is already associated with another logical group.

A user is already registered in the specified user group.

Make sure that the user group name is not a duplicate, and then retry.

Make sure that the user group name exists in the Device Manager database, and then retry.

Check the ACL ruleID.

Make sure that the user ID and the password exist.

A duplicate user ID cannot be registered into the Device Manager ACL database. Change the user ID.

This is an informational message only. No additional action is required.

Try to delete the user once the operation completes.

Check the Device Manager Server XML API manual and make sure the running API version supports the command.

Check the access permission of the user.


Specify another logical group, and then retry.

Remove the old association, and then retry.

Remove all users from this user group, and then retry.



Error Code

KAIC02019-E

KAIC02020-E

KAIC02021-E

KAIC02022-E

KAIC02023-E

KAIC02024-E

KAIC02025-E

KAIC02026-E

KAIC02027-E

KAIC02028-E

KAIC02030-E

KAIC02032-E

KAIC02033-E

KAIC02034-E

KAIC02035-E

KAIC02036-E

KAIC02037-E

Description

A user group is registered under the specified logical group.

A user group is registered in the specified logical group.

The specified object ID

"ObjectID" was not permitted for the login user.

The logged-in user does not have permissions for the specified host "host-name".

The login user cannot remove a LUSE that includes an unpermitted LDEV.

The login user cannot add a path to an unpermitted LDEV.

The login user cannot remove a path that set an unpermitted

LDEV.

The local user does not have permission to add a new subsystem.

The local user does not have permission to remove a subsystem.

An object for which the loggedin user does not have permissions was specified.

The user "userID" does not have permission to run this

API.

The login user cannot modify own user group and user role.

The login user cannot operate a replication using an unpermitted LDEV.

The user group name is invalid. Use name less than 25 bytes.

The specified ACL rule already exists in the Device Manager database.

A path related to the LDEV to be deleted is registered in the logical group "logical-group-

name".

This operation cannot be performed because the specified user ID is reserved within Device Manager.


Remove all user groups under the specified logical group, and then retry.

Create a new logical group, and then add a path in the logical group.

Check the ACL rule, and then retry.

Check the ACL rule for the logged-in user.


Ask Global-Admin or Global-Storage_Admin to add the new subsystem.

Check the ACL rule for the logged-in user.


Check the login user authorization, and then retry.


The user group name is invalid. Use name less than 25 bytes.

Revise the rule, and then retry.

From the logical group, remove the path related to the LDEV to be deleted.

Change the user ID, and then retry.



1-17

1-18

Error Code

KAIC02038-E

KAIC02040-E

KAIC02041-E

KAIC02042-E

KAIC02043-E

KAIC02044-E

KAIC02045-E

KAIC02046-E

KAIC02047-E

KAIC02048-E

KAIC02100-E

KAIC02101-E

KAIC02150-E

KAIC02250-E

KAIC02251-E

KAIC02252-E

Description

The storage port "Host Name" cannot set access permissions.

Built-in user groups cannot be deleted.

The own user group cannot be deleted.

Built-in user groups cannot be modified.

The own user group cannot be modified.

The login user cannot delete own account.

A user being used by other products (using shared user information) cannot be deleted.

The requested operation cannot be executed to the specified user.

The specified ACL rule ID is invalid. It cannot be deleted.

The specified user group name cannot be used because it is reserved.

The logged-in user does not have the permissions for using

Device Manager functions.

The logged-in user cannot use

Device Manager functions because that user does not belong to a user group.

There are no permissions to use the journal group.


Check and, if necessary, revise the target host specification.

Revise the user group specifications.

Revise the user specifications.

Revise the ACL rule specifications.


Try again as a user who can use Device

Manager functions.

A PP Name (VolumeMigration) migration plan related to an

LDEV for which the logged-on user does not have the necessary permissions cannot be specified.

An LDEV that does not have the necessary permissions cannot be specified as a source volume.

An LDEV that does not have the necessary permissions cannot be specified as a target volume.

Revise the request, and then retry. To use a journal group, the user must have permissions for all the volumes that make up the journal group.

Check the ACL rule for the logged-on user.



Error Code

KAIC02253-E

KAIC02500-E

KAIC02501-E

KAIC02502-E

KAIC02503-E

KAIC02504-E

KAIC02505-E

KAIC02506-E

KAIC02507-E

KAIC02508-E

Description

For an LDEV that does not have the necessary permissions, no PP Name

(VolumeMigration) reserved volume set or release operation can be performed.

An unspecified error occurred while performing an operation on the common user information.

An exception occurred in the common user management function.

Part of the user group information is inconsistent with part of the common user information.

The specified user is not registered in the common user information.

The specified user has already been registered in the common user information.

The specified user group is not registered in the common user information.

The specified user group has already been registered in the common user information.

The common user management function is unavailable.

This operation cannot be processed since it is invalid.



The common user information might not contain the latest information. Restart the

Device Manager server.

Revise the user specifications.


Check whether the Common Component service is running.

Revise the operation.



1-19

1-20

Error Code

KAIC02509-E

Description

A communication error occurred during an attempt to authenticate a user on an external authentication server.


Perform one of the following procedures:

For LDAP:

1. By using the host, port, and protocol set in exauth.properties, check whether the authentication server can be accessed, the settings of the external authentication server, and the status of the network.

2. By using the hcmdsldapuser command, check that the information for the server names specified in the auth.server.name attribute in exauth.properties is registered.

3. If StartTLS is used, check the SSL settings.

4. If you cannot resolve the problem, collect maintenance information, and then contact the Support Center.

For RADIUS:


2. By using the hcmdsradiussecret command, check that the information for the server names specified in the auth.server.name attribute in exauth.properties is registered.


Table 1-5 KAIC03000-KAIC03999: Database Errors

Error Code

KAIC03000-E

KAIC03001-E

KAIC03002-E

KAIC03003-E

KAIC03004-E

KAIC03005-E

KAIC03006-E

Description

An unspecified database error was encountered.

The specified object was not found in the Device Manager database.

The ManagedObject does not support name updates.

The device cannot read/write to


The database manager handle is not valid.

An error was encountered during database query.

An error was encountered during database insert.



Make sure that the specified object exists in the Device Manager database, and then retry.

If the name has to be changed, the object will have to be deleted and re-added.

An internal server error was encountered. If this problem persists, contact the Support

Center.


Center.



Error Code

KAIC03007-E

KAIC03008-E

KAIC03009-E

KAIC03010-E

KAIC03011-E

KAIC03012-E

KAIC03013-E

KAIC03014-E

KAIC03015-E

KAIC03016-E

KAIC03017-E

KAIC03018-E

KAIC03019-E

KAIC03020-E

KAIC03021-E

KAIC03022-E

Description

An error was encountered during database update.

An error was encountered during database delete.

The database column "column-

name" was not found in the result set.

An error was encountered during the formatting of the database results for the column

"column-name".

An attempt to acquire a database connection from the pool failed. Check communications to the Device

Manager database.

A failure was encountered during the closing of a database connection.

A failure was encountered during the committing of a database transaction.

A failure was encountered during the rolling back of a database transaction.

Database transaction commit/rollback failed. No transaction is in progress.

The entered value exceeds the maximum number of allowable digits. Enter a valid value.

Due to competing database locks, all or a part of the requested update has failed.

An attempt to migrate the

Device Manager database has failed. (return code="return

code")

An attempt to convert a character code has failed.

An attempt to execute the command for releasing index free pages has failed.

An attempt to add the command for updating the database has failed.

Device Manager access to DB is blocked. Problem is detected in

Common Component. Call server administrator.


Enter a valid value.


Center.

If this problem occurs repeatedly, contact the

Support Center.

If this problem occurs repeatedly, contact the

Support Center.


Center.

Call server administrator.



1-21

1-22

Error Code

KAIC03023-E

KAIC03050-E

KAIC03051-E

KAIC03052-E

KAIC03100-E

KAIC03141-E

KAIC03143-E

KAIC03144-E

KAIC03145-E

KAIC03146-E

KAIC03147-E

KAIC03148-E

KAIC03149-E

KAIC03402-E

Description


Device Manager database. Call server administrator.

The ID of table "Table" has exceeded the maximum.

Mapping of the "type-name" type for database access cannot be resolved.

Initialization of table "Table

name" ("Key") has been duplicated.

An error occurred during the connecting to the Device

Manager database.

An internal server error was encountered. An attempt to acquire the URL of the host agent failed.

An internal server error was encountered. An attempt to acquire the replication information failed.

An internal server error was encountered. An attempt to acquire license key information from the database has failed.

(Cause:"cause")

An internal error occurred. The record relating to the subsystem could not be deleted from the database. (cause =

"cause")

An internal error occurred. The

SMI-S Enabled subsystem information could not be acquired from the database.

(table name = "table name")


Acquisition of information used for managing the status of table

"table name" has failed.


Acquisition of information to set for table "table name" has failed.

An internal error occurred. An attempt to acquire the virtualization server information from the database failed. (table name: table name)

A connection error occurred when logging into the Common

Component.





Center.





Check Common Component, and then retry.



Error Code

KAIC03403-E

KAIC03404-E

KAIC03405-E

KAIC03406-E

KAIC03410-E

KAIC03411-E

KAIC03412-E

KAIC03414-E

KAIC03415-E

KAIC03416-E

KAIC03420-E


An attempt to log into the

Common Component failed.

Application "ApplicationName" is not permitted to log in.

Authentication was refused when logging into the Common

Component. "userID"

A Common Component error occurred.

An error occurred while connecting to the Common

Component database.

An error occurred during operation of the Common

Component database. (CIM error: "error-code")


Data in the Device Manager database might not match data in the Common Component database. Specify "true" for the property

"server.base.initialsynchro" in the

"server.properties" file, restart Device

Manager Server, and then retry the operation. If this problem still occurs after these actions, Contact the Support Center.

Contact the Support Center. An attempt to acquire Device

Manager information for synchronizing with Common

Component has failed.

An internal error occurred while updating the Common

Component database.

An exception occurred in the

Common Component linkage of

Provisioning Manager.

Specify "true" for the property


"server.properties" file, and then restart

Device Manager Server. If this problem persists, contact the Support Center.

Specify "true" for the property server.base.initialsynchro in the server.properties file, and then restart Device

Manager Server.

An error occurred while updating the Common

Component database.

Mismatching data existed in the

Device Manager database and the Common Component database.

The rollback of the Device

Manager database was performed after updating the

Common Component database.Therefore, mismatching occurred in the

Device Manager database and

Common Component database.

An attempt to register the initial data into the Common

Component database has failed.

Specify "true" for the property


"server.properties" file, and restart Device

Manager Server.

Check whether the Common Component service is running.



1-23

Error Code

KAIC03421-E

KAIC03422-E

KAIC03423-E

KAIC03440-E

KAIC03441-E

KAIC03500-E

KAIC03999-E

Description

An attempt to synchronize with

Common Component has failed.

An attempt to determine synchronization with Common


"StartingState"

An attempt to synchronize with the information for the displayed list has failed.

An attempt to acquire the accessing user ID and password for the database has failed.



Database migration has failed.

A database error occurred during an attempt to add a storage subsystem or refresh the database. Try again.

An error occurred during the initialization of the Device

Manager database functionality.

Make sure that the Common Component service has started, and then restart Device

Manager Server. If this problem occurs repeatedly, contact the Support Center.



Center.

Make sure that the Device Manager service is started, and that the Device Manager database exists. If this problem persists, contact the Support Center.

Table 1-6 KAIC04000-KAIC04999: Network Errors

Error Code

KAIC04001-E

KAIC04002-E

Description

An attempt to resolve the specified IP address "IP-

address" has failed.

The specified IP address "IP

address" is not a correctly formatted protocol address.


Specify the correct IP address.

Revise the specification.



Error Code

KAIC04100-E

KAIC04211-E

KAIC04212-E

KAIC04213-E

Description

An internal error occurred. An incorrect format for the IP address "IP-address" was detected.

An exception occurred when

Storage Navigator Modular was invoked. (exception="stack-

trace")

An exception occurred while

Storage Navigator Modular event history information was being acquired.

(exception="stack-trace")


Storage Navigator Modular.

(error code = "error code from

Storage Navigator Modular

Server", error message =

"error message for Storage

Navigator Modular error code")



Table 1-7 KAIC05000-KAIC05999: Transport Errors

Error Code

KAIC05000-E

KAIC05001-E

KAIC05002-E

KAIC05003-E

KAIC05004-E

KAIC05005-E

Description

An unspecified transport error was encountered.

Device Manager does not support the operation

"operation" for the storage array type.

An internal server error occurred. The transport connection is not valid for the storage array.

The storage subsystem is currently locked by "user-

name".



Device Manager Server does not support requests on the specified storage device.


An attempt to acquire the lock for the subsystem has failed.

An attempt to release the SNMP lock has failed after "number-

of-trials" attempts.

The storage array is locked by another management application. Check whether anyone is accessing the storage array from another management application on the network. If this problem persists, contact the

Support Center.

Check whether anyone is accessing the storage array from another management application on the network. If this problem persists, contact the Support Center.



1-25

1-26

Error Code

KAIC05008-E

KAIC05009-E

KAIC05011-E

KAIC05012-E

KAIC05013-E

KAIC05014-E

KAIC05015-E

KAIC05016-E

KAIC05018-E

KAIC05019-E

KAIC05020-E

KAIC05022-E

KAIC05023-E

KAIC05024-E

KAIC05026-E

KAIC05027-E

Description

An SNMP error occurred during an internal refresh of the subsystem.

An attempt to retrieve info via

SNMP has failed.


DeviceIdentificationService was not found.

No default service is registered for identification of the array family "array-family".

An error occurred during acquisition of configuration information from the device at

IP Address "IP-address".

Device Manager does not support the specified operation

"operation" on the subsystem.

The minimum microcode version is "version".

The specified array group

"array-group" is out of range.


"array-group" already exists.

The specified PDEV "PDEV-ID" is already in use.

The specified LDEV "device-

number" is out of range.


number" already exists.

The specified host mode is invalid for the storage subsystem. The setting for the storage subsystem type does not match the actual value.

The specified host mode is unsupported on the subsystem.

The function "Function-name" on the subsystem does not exist.

Device Manager does not support the specified subsystem, or a configuration error might exist in the subsystem.

The number of devNums required to create the specified

LU in the current configuration do not exist.


Center.



This is an internal server error indicating an invalid configuration in the transport layer.


An error was encountered during polling for device configuration information. Check the storage array for possible problems. If this problem persists, contact the Support

Center.

To perform this operation, the microcode version must be updated.

Perform a refresh on the storage subsystem.

Specifying the correct model, add the storage subsystem again. If there is a serious impact on your system, contact the

Support Center.

Check that the subsystem supports this host mode.

Check the subsystem functionality.

Revise the subsystem specifications. If there is no problem in the specifications, contact the Support Center.

Delete any unnecessary LUs, and then retry.



Error Code

KAIC05028-E

KAIC05030-E

KAIC05031-E

KAIC05032-E

KAIC05034-E

KAIC05035-E

KAIC05036-E

KAIC05040-E

KAIC05041-E

KAIC05042-E

KAIC05043-E

KAIC05044-E

KAIC05045-E

Description

The PP Name(Dynamic

Provisioning) ArrayGroup has been specified. A PP

Name(Dynamic Provisioning) volume cannot be created in

Device Manager.

Cannot create the LDEV with the specified emulation type under present storage configuration.

The specified emulation type is invalid for the array group.

An LDEV cannot be created for an array group of the emulation type "emulation-type".

The subsystem type is invalid.

An LDEV that has the emulation type "emulation-type" cannot be created for the specified device number

(devNum="device-number").

The specified device number

(devNum="device-number") cannot be used.

Operations for command device security are not supported on the microcode version of this subsystem.

The specified SMI-S Enabled subsystem was not found.

An SMI-S Enabled subsystem was not found. The specified

SMI-S provider does not manage any SMI-S Enabled subsystems supported by

Device Manager.

The specified virtualizationserver management program or virtualization server was not found.

No virtualization servers were found. The specified virtualization-server management program is not managing any virtualization servers supported by Device

Manager.

The information acquired from the specified virtualization server does not match the information in the database.


Revise the ArrayGroup specification.

Delete any unnecessary LUs, and then retry.

Correct the specified emulation type and/or array group, and then retry.

Check the specified emulation type.

Revise the specified subsystem type.

Revise the specified devNum or emulation type.

Revise the specified devNum.

To perform command device security operations, you will need to upgrade.


Revise the specification of the SMI-S Enabled subsystem.

Revise the SMI-S provider specification.

Revise the specification for the virtualizationserver management program or virtualization server.

Revise the specification for the virtualizationserver management program.

Delete the virtualization server from the

Device Manager server, and then re-register the virtualization server information.



1-27

1-28

Error Code

KAIC05054-E

KAIC05056-E

KAIC05057-E

KAIC05060-E

KAIC05090-E

KAIC05100-E

KAIC05101-E


The parameter (IP address or communication protocol) used to connect to the storage subsystem has been changed in

Storage Navigator Modular 2.

Make sure the IP address and communication protocol are correct, and then refresh the storage subsystem.

An attempt to connect to the storage subsystem failed. Check the specified storage subsystem type, IP address, microcode version, and network port settings, as well as the network status.

An attempt to connect to the storage subsystem failed. Check the specified storage subsystem type, IP address, communication protocol, microcode version, and network port settings, as well as the network status.

The IP address and communication protocol used to connect to the storage subsystem must be the same as those set in Storage

Navigator Modular 2. Check the network environment and the IP address and communication protocol used to connect to the storage subsystem. If necessary, specify the correct IP address or communication protocol, and then refresh the storage subsystem to obtain the most up-to-date configuration information.

Check the following items related to the storage subsystem:







Type

IP Address

Microprogram version



The ports that will be used. (Check from both Device Manager and the storage subsystem.)

The network status



If there is no problem with any of the above items, there is a hardware problem with the network or the storage subsystem.

Check the following items related to the storage subsystem:





Type

IP Address







Communication protocol

Microprogram version

The ports that will be used. (Check from both Device Manager and the storage subsystem.)



The network status

If there is no problem with any of the above items, there is a hardware problem with the network or the storage subsystem.

Revise the host specification. The host agent does not support the operation

"operation".

The specified operation is not supported by the microcode version of this storage subsystem.

An internal server error occurred. An attempt to execute the transport service failed due to a missing parameter

"parameter".

An internal server error occurred. An attempt to initialize the transport connection has failed.

To perform the specified operation, you will need to upgrade the microcode version.





Error Code

KAIC05102-E

KAIC05103-E

KAIC05200-E

KAIC05251-E

KAIC05252-E

KAIC05254-E

KAIC05255-E

KAIC05300-E

KAIC05302-E

KAIC05303-E

KAIC05304-E

KAIC05305-E

KAIC05306-E

Description

The subsystem or SMI-S provider is currently performing other processing. Wait a while, and then try again.

The virtualization-server management program or the virtualization server is currently processing. Wait a while, and then try again.

Initialization of the SNMP connection at IP-address "IP-

address" has failed.


Center.



Center.

The specified volume is already being used by another PP Name

(VolumeMigration) migration plan.

The specified PP Name

(VolumeMigration) migration plan was not found in the storage subsystem.


(VolumeMigration) migration plan cannot be deleted because migration has not finished.

The specified PP name

(VolumeMigration) migration plan cannot be canceled because it is not running.


An attempt to load a storage array connection library has failed.

An attempt to log in to the storage array has failed. Check the validity of the user ID and password. Moreover, please confirm whether the account registered in the storage subsystem is effective.

Permissions necessary to manage the subsystem are not allocated.

Another management application on the network is changing the subsystem configuration.

Specified PDEV are not continuous.

An error occurred during the initialization of the SNMP for the specified IP Address. This indicates a network connection or SNMP configuration error on the device.

Revise the volume specification.

Check and, if necessary, revise the specification.


Make sure the user ID and password are valid, and then retry the operation. If

Advanced Security mode is changed in the

Hitachi AMS or SMS series, all accounts registered in the storage subsystem are initialized. If this happens, create an account in Hitachi Storage Navigator Modular 2, and then retry the operation.

Make sure that the permissions to manage the subsystem are allocated. If this problem continues to occur, contact the Support

Center.

Make sure that the subsystem configuration is not being changed by another management application. If this problem continues to occur, contact the Support

Center.

Specify continuous PDEV. If the problem persists, contact the Support Center.



1-29

1-30

Error Code

KAIC05307-E

KAIC05308-E

KAIC05310-E

KAIC05311-E

KAIC05312-E

KAIC05313-E

KAIC05314-E

KAIC05315-E

KAIC05350-E

KAIC05381-E

KAIC05390-E

KAIC05391-E

KAIC05392-E

KAIC05393-E

Description

The number of PDEVs

("number-of-PDEVs") does not match the type "RAID-type".

You cannot delete the LU. You can only delete the last logical unit created. The last LU created was "device-number".

An attempt to connect to the storage array has failed. Check the validity of the storage type, and IP address, and DAMP connection port number, and network connectivity.

No more spare drives can be added on the subsystem.

No more command devices can be added to the specified subsystem.

An API function that was executed by the storage subsystem microcode is not supported.

The specified RAID type is invalid.

The Device Manager server does not support the specified subsystem.

The name of the virtualization server (host-name) detected for the specified IP address (IP-

address) is the same as a host name already registered in

Device Manager.

This Device Manager does not support the LUN Management option.

The port "port-name" was not found on the storage array.

The controller "controller-ID" was not found on the storage array.

HostStorageDomain "host-

storage-domain-ID" was not found on the storage array.

The specified Port Option "port-

option-name" is not supported on the microcode version of this subsystem.


A valid PDEV number needs to be assigned.

You can only delete the last logical unit created. The last LU created was "device-

number".

Confirm the storage subsystem type and IP address and subsystem connection port number are correct. If these are correct, there is a network or storage subsystem problem.

Remove other spare drives, and then retry.

Up to 2 LUs of command devices can be specified. Delete unnecessary command devices, and then retry.

Check the version of the storage subsystem microcode.

Check the request.

Make sure that the specified subsystem is supported by the Device Manager.

Revise the host name, and then try again.

Check this subsystem's option list.

Make sure that the port name is correct, and then retry. If this problem persists, contact the Support Center.

Make sure that the controller number is correct, and then retry. If this problem persists, contact the Support Center.

Make sure that the HostStorageDomain is correct, and then retry. If this problem persists, contact the Support Center.

A microcode upgrade is required to use the specified port option. Contact the Support

Center.



Error Code

KAIC05394-E

KAIC05395-E

KAIC05396-E

KAIC05400-E

KAIC05401-E

KAIC05402-E

KAIC05409-E

KAIC05420-E

KAIC05421-E

KAIC05422-E

KAIC05423-E

KAIC05424-E


An attempt to log in to the storage subsystem failed because another user is already logged in. Wait a while, and then retry the operation. If

Physical View, Storage

Navigator Modular or Storage

Navigator Modular 2 is open, close the window, and then retry the operation.

An attempt to register a user failed because the maximum number of users is already registered.

An attempt to register a user failed because the specified user ID is already registered.

An attempt to connect to the storage array at IP Address "IP-

address" has failed. Check the validity of the user ID and password, storage type, and IP address, as well as any network connections.

An attempt to retrieve data for the storage array has failed.

Check the validity of the user ID and password, as well as any network connections.

An attempt to execute the operation on the storage array has failed.

Wait a while, and then retry the operation. If

Physical View, Storage Navigator Modular or

Storage Navigator Modular 2 is open, close the window, and then retry the operation.

Delete unnecessary users from storage subsystem, and then retry the operation.

Revise the user ID or password specifications, and then retry the operation.

The HTTP connection command has failed.

Check the validity of the user ID, password, storage type, IP address, and network connections.

The HTTP GET command has failed to retrieve the desired data. Check the network connection and the user ID and password used to access the device. The Device

Manager Server may need to be refreshed to obtain the latest configuration information.

The HTTP POST command failed. Check the network connection and the user ID and password used to access the device. The

Device Manager Server may need to be refreshed to obtain the latest configuration information.

Perform a refresh on the storage subsystem, and then retry.

The chassis referenced in the request is not valid for the storage array.


There is no external array groups that Device Manager can assign.

An attempt to create the external array group "External

Array Group" has failed.

There is no path groups that

Device Manager can assign.

The specified LU cannot be created because the total capacity of that LU exceeds the capacity of the external volume.


Delete any unnecessary external array groups, and then try again.

Revise the external array group specification.

Delete any unnecessary path groups, and then retry the operation.

Revise the LU specification.



1-31

1-32

Error Code

KAIC05425-E

KAIC05500-E

KAIC05520-E

KAIC05521-E

KAIC05522-E

KAIC05523-E

KAIC05600-E

KAIC05601-E

KAIC05607-E

KAIC05609-E

KAIC05700-E

KAIC05701-E

KAIC05702-E

KAIC05703-E


An internal server error occurred. Execution of the transport service failed due to an invalid parameter value.

There is no response from the device at IP address "IP-

address".

The specified ISCSIName

"ISCSIName" does not exist.


"ISCSIName" already exists.

An attempt to execute a request has failed. Only some of the configuration changes may have been applied to the storage subsystem.

The request was not completed within the time limit. Only some of the configuration changes may have been applied to the storage subsystem.


An RMI connection could not be established using the IP address

IP-address. Check the specified type and IP address, as well as the network status.

The storage array at "IP-

address" is currently locked by another user, or is undergoing reconfiguration.

A RMI Session problem occurred at "IP-address".

Not enough free space exists.

An internal server error occurred. The

HostStorageDomainID is invalid.

The specified port already has the maximum number of LUNs.

The HostStorageDomain specified already has the maximum number of LUNs.


If the IP address of the storage subsystem is correct, there is a network connection error, or an SNMP configuration error in the device.


Refresh the storage subsystem, and make sure the request is correct.

Refresh the subsystem, check the parameter for the specified iSCSI port, and then retry the operation. If this problem persists, contact the Support Center.

Refresh the subsystem, and then check the changed settings. Specify the parameters for settings that have not yet changed, and then retry the operation. If this problem persists, contact the Support Center.


Make sure that the correct storage subsystem type and IP address have been specified. Also, check the settings for the

Device Manager and storage subsystem communication ports. Restart Device

Manager server if you have not done so since changing the storage subsystem microcode version. If there is no problem with the specifications or settings and restarting

Device Manager server does not solve the problem, there is a hardware problem with the network or the storage subsystem.

The storage array is locked by another management application. Wait a while, and then retry. If this problem persists, contact the Support Center.

This indicates a network or storage problem.

Specify the size within the scope of free space available.


No more LUNs can be specified on this port, so select a different port to which to add

LUNs.

No more LUNs can be specified on this

HostStorageDomain. Select a different

HostStorageDomain to which to add LUNs.



Error Code

KAIC05704-E

KAIC05705-E

KAIC05706-E

KAIC05707-E

KAIC05708-E

KAIC05709-E

KAIC05710-E

KAIC05711-E

KAIC05712-E

KAIC05713-E

KAIC05714-E

KAIC05715-E

KAIC05716-E

KAIC05717-E

KAIC05718-E


The LDEV of is a PP Name

(VolumeMigration) reserved volume; it cannot be used in a

LUSE.

The LU is an OnDemand device and cannot be used for an LUN.

The specified LDEV does not exist.

The specified WWN does not exist.

Perform a refresh on the storage subsystem and check the request.

Perform a refresh on the storage subsystem and check the request.

Perform a refresh on the storage subsystem to obtain the latest configuration information.

Perform a refresh on the storage subsystem to obtain the latest configuration information.

Check the request.

The specified port already has the maximum number of

WWNs.

The specified

HostStorageDomain already has the maximum number of

WWNs.

The specified WWN already exists.

The control unit for devNum cannot be used.

Perform a refresh on the storage subsystem to obtain the latest configuration information, and check the specified WWN.

An attempt to add a logical unit has failed.

The cu number is not valid. Perform a refresh on the storage subsystem to obtain the latest configuration information.

LDEV cannot be created because the SSID is not set.

You need to set an appropriate SSID from

SVP. Contact the subsystem administrator, or call maintenance personnel.

The specified capacity is invalid. Specify a valid capacity, and then retry.

The setting value of the security option of Storage array has changed. A refresh of the storage subsystem is recommended. Contact your system administrator if you are a local user.

This API version does not support the LUN Management option.

The Device Manager Server may not contain the most current storage device information.


Check this subsystem's option list.

Alternatively, check the Device Manager

Server XML API manual and make sure the running API version supports the command.

Specify a Fibre Channel port, and then retry. The request cannot be processed because the specified port is not a Fibre Channel port.

The request cannot be processed because the security switch of the specified port is turned off.

Turn on the security switch of the port, and then retry.

The request cannot be processed because the port that the specified

HostStorageDomain belongs to is not a Fibre Channel port.

Specify a HostStorageDomain that belongs to a Fibre Channel port, and then retry.



1-33

1-34

Error Code

KAIC05719-E

KAIC05720-E

KAIC05721-E

KAIC05722-E

KAIC05723-E

KAIC05724-E

KAIC05725-E

KAIC05726-E

KAIC05727-E

KAIC05728-E

KAIC05729-E

KAIC05730-E


The request cannot be processed because the security switch of the port that the specified HostStorageDomain belongs to is turned off.

The specified

HostStorageDomain "HSD-

identifier" already exists on the port "port-identifier".

An inconsistency was detected for the storage array. A refresh of the storage subsystem is recommended. Contact your system administrator if you are a local user.

This operation to the subsystem has failed. Some of the operation may have been applied to the storage subsystem. A refresh of the storage subsystem is recommended. Contact your system administrator if you are a local user.

The LUN "LUN-of-a-path" was not found on the storage array.

The SCSI ID "SCSI-ID-of-a-

path" was not found on the storage array.

The LUN "LUN-of-a-path" is already used on the storage array.

The port "port-identifier" was not found on the storage array.

The HostStorageDomain "HSD-

identifier" does not exist on the port "port-identifier".

PDEV #"PDEV-ID" is not a spare drive.

The specification of nickname

"nickname" is invalid. The maximum length of the nickname is "maximum-length-

of-nickname" bytes.

An attempt to log in to the subsystem has failed. Password authentication is required.

Specify the user ID and password, and then try again.

Turn on the security switch of the port that the specified HostStorageDomain belongs to, and then retry.

Check the combination of the specified

HostStorageDomain and port ID.

The Device Manager Server may not contain the most current storage device information.




Center.

Check the LUN.

Check the SCSI ID.

Check the LUN.

Check the Port.

Check the HostStorageDomain.

Check the PDEV.

Check the specified nickname. Make sure that the nickname is correct, and then retry.

Specify the user ID and password, then retry. If this problem continues to occur, contact the Support Center.



Error Code

KAIC05731-E

KAIC05732-E

KAIC05735-E

KAIC05736-E

KAIC05737-E

KAIC05750-E

KAIC05751-E

KAIC05752-E

KAIC05760-E

KAIC05761-E

KAIC05762-E

KAIC05763-E

KAIC05764-E

KAIC05765-E


A LUSE Volume configuration is not supported when the devNum is specified with emulation type "emulation-

type" and a capacity of

"capacityKB". Specify the creation capacity within the range from "min-ldev-sizeKB" to "max-ldev-sizeKB".

An attempt to change portRole has failed.

An inconsistency was detected in the "type of information" information. Refreshing the storage subsystem is recommended. If you are a local user, contact your system administrator.

An LU cannot be created. The number of LUs that can be created using the specified parameter is "maximum

number of LUs".

An error occurred while deleting an LU. (successfully deleted device(s) : "device number

list")

The devNum cannot be used.

There are no SSIDs that Device

Manager can assign for the LU to be created.

The LUs cannot be created because their total capacity exceeds the free space in the array group.

The subsystem managed by the partitioned storage administrator cannot execute the request.

Make sure that the capacity falls within the valid range for the emulation type.

Confirm the state of the port, and then try again.

The Device Manager Server might not contain the most current storage device information. Refresh the storage subsystem, and then try again.

Make sure that there is sufficient free space at the target, or revise the LU capacity and count. For details, see the manual that corresponds to your storage subsystem.

Revise the devNum (device number) value, and then try again.

The specified operation cannot be executed because the PDEV of the specified disk capacity

"disk-capacity" is not supported.

Revise the specification for devNum of the

LogicalUnit elements and then try again.

Check and, if necessary, specify a different disk capacity, and then retry the operation.

The specified drive type "drive-

type" is invalid.

The specified CLPR "CLPR-

number" does not exist in the storage subsystem.

Check and, if necessary, specify a different drive type, and then retry the operation.

Revise the CLPR specification.

The specified capacity is invalid. Revise the LU or LDEV capacity specification.


"device-number" is not available.

Revise the device number specification.

Revise the "server.properties" value, and then restart the services.

Reduce the total capacity of the LUs to be created, and then retry the operation.

Revise the subsystem settings.



1-35

1-36

Error Code

KAIC05766-E

KAIC05767-E

KAIC05768-E

KAIC05769-E

KAIC05770-E

KAIC05771-E

KAIC05772-E

KAIC05773-E

KAIC05774-E

KAIC05779-E

KAIC05780-E

Description

There is no PP Name (Dynamic

Provisioning) volume group which Device Manager can assign.

There is no CU which Device

Manager can assign.

The pool threshold cannot be modified to the specified value

"threshold" because it is less than or equal to the pool's usage rate "pool's usage rate".

Status in pool (function="PP

Name (Dynamic Provisioning)" pool ID="poolID") is not

"Normal", and threshold of pool cannot be modified.

This API cannot be executed because it has supported it since the microcode version 7.

The retention term of the specified LDEV has not expired.

The protection attributes of the specified LDEV cannot be changed.

Usage rate of pool

(function="PP Name (Dynamic

Provisioning)" pool

ID="poolID") is more than

95%, and threshold of pool cannot be modified.

The pool cannot be created because the maximum number of pools for "PP Name (Quick

Shadow)" or "PP Name

(Dynamic Provisioning)" have been created in the storage subsystem.

Array groups cannot be added because the number of array groups for "PP Name (Dynamic

Provisioning)", "PP Name (Quick

Shadow)" and "PP Name

(Universal Volume Manager)" will exceed the maximum number of array groups in storage subsystem.

An attempt to execute the request failed. The array groups of the source and target volumes do not match in the

Device Manager database and the storage array.

The specified subsystem does not support the host mode

"name-of-host-mode".


Reduce the LUs to be added, and then retry the operation.

Create the volume to the existing CU.

Specify a value that is more than the pool's usage rate, and then retry the operation.

Check the status of specified pool, and then retry the operation.

Check the microcode version of the subsystem.

Check the specification of the LDEV.

Check the usage rate of pool.

Delete any unnecessary pool, and then retry the operation.

Delete any unnecessary array groups for "PP

Name (Dynamic Provisioning)", "PP Name

(Quick Shadow)" or "PP Name (Universal

Volume Manager)", and then retry the operation.

Refresh the storage subsystem, and make sure the request is correct.

Revise the subsystem specifications.



Error Code

KAIC05781-E

KAIC05782-E

KAIC05783-E

KAIC05784-E

KAIC05785-E

KAIC05786-E

KAIC05787-E

KAIC05788-E

KAIC05789-E

KAIC05790-E

KAIC05791-E

KAIC05792-E


The specified host mode "name-

of-host-mode" cannot be specified for the microcode version of this subsystem.

The specified port does not support the channel speed

"channel-speed".

The specified subsystem does not support the host mode 2

"name-of-host-mode-2".

The specified host mode 2

"name-of-host-mode-2" cannot be specified for the microcode version of this subsystem.

The specified subsystem does not support the option "name-

of-port-option".

The specified port option

"name-of-port-option" is not supported on the microcode version of this subsystem.

Storage subsystem information different from that of the actual machine is registered in Storage

Navigator Modular 2. Use

Storage Navigator Modular 2 to delete the following storage subsystem information, and then retry the operation. (array name = "array-name-

registered-in-Storage-

Navigator-Modular-2")

PP-Name functionality must be enabled on the subsystem.

The specified operation cannot be executed because the usage rate of the pool

(poolID="poolID", usage=

"pool-usage-rate") is the pool threshold (attribute-

name="attribute-value") or more.






Use Storage Navigator Modular 2 to delete the storage subsystem information, and then retry the operation.

Enable PP-Name functionality on the subsystem.

Revise the configuration so that the pool usage rate is less than the value of attribute-

name, and then retry the operation.

A pool/journal group cannot be created because the maximum number of PP Name (Universal

Replicator) pools/journal groups has been created in the storage subsystem.

A journal group cannot be shrunk because its status is not

"Initial" or "Stop".

A journal group cannot be expanded because its status is not "Initial", "Active", or "Stop".

Delete any unnecessary pools/journal groups, and then try again.

Change the status of the pairs that use the journal group, and then retry the operation.




1-37

1-38

Error Code

KAIC05793-E

KAIC05794-E

KAIC05795-E

KAIC05796-E

KAIC05798-E

KAIC05799-E

KAIC05800-E

KAIC05850-E

KAIC05851-E

KAIC05852-E

KAIC05853-E

KAIC05854-E


The specified pool cannot be deleted because its used capacity is not 0GB.

The Status of all pairs that use the specified pool must be

"Simplex".

SnapShot or TrueCopy

Extended Distance functionality must be enabled on the subsystem.

The LU "device number" cannot be used for a pool volume/journal volume because it is set for VMA.

The specified journal group cannot be deleted because its status is not the initial status.

An internal server error occurred. An attempt to execute the transport service failed because the parameter

"parameter" or "parameter" is missing.

An internal error occurred during execution of the CIM function.

On the port "port-name", security is not set for the host storage domain "host-storage-

domain-name" or the iSCSI initiator "iscsi-initiator-name".

On the port "port-name", security has already been set for the host storage domain

"host-storage-domain-name" and the iSCSI initiator "iscsi-

initiator-name".

For the specified port "port-

name", the maximum number of iSCSI names "maximum-

number-of-iscsi-initiators" has already been set or might be exceeded when the processing is executed.

The specified nickname

"nickname" is already being used for another iSCSI name on the same port "port-name".

The specified iSCSI name "iscsi-

name" is already being used by another host storage domain on the same port "port-name".

Delete all pairs which use the specified pool.

Change status of pairs which use the pool into "Simlex", and then retry.

Check and, if necessary, revise the subsystem functionality.

Revise the LU specification, and then try again.

Change the status of the journal group to the initial status, and then retry the operation.





Specify a nickname that is not being used by another iSCSI name on the same port, and then retry the operation.

Specify an iSCSI name that is not being used by another host storage domain on the same port, and then retry the operation.



Error Code

KAIC05855-E

KAIC05856-E

KAIC05857-E

KAIC05858-E

KAIC05859-E

KAIC05860-E

KAIC05861-E



"nickname" is already being used by another host storage domain on the same port "portname".

The maximum number of host storage domains "maximum-

number-of-iscsi-targets" for the port "port-name" cannot be exceeded.

The specified iSCSI name

"nickname" is invalid. The maximum length of the iSCSI name is "maximum-length-of-

nickname bytes".

The specified iSCSI name "iscsi-

name" is invalid. Specify the iSCSI name by using the iqn format or the eui format.

Different nickname "iscsi-

nickname1" and "iscsi-

nickname2" are specified for iSCSI name "iscsi-name" on same port "port-name".

An error occurred during access to an SMI-S Enabled subsystem. A specified parameter or the status of the

SMI-S provider or the SMI-S

Enabled subsystem might be invalid. (WBEM error code =

"WBEM-error- code", WBEM method name = "WBEM-

method-name", CIM class name

= "target-CIM-class-name", detailed information =

"detailed-information")

An attempt to access the SMI-S

Enabled provider has failed.

Make sure the following parameters are correct: SMI-S provider IP address, port number, user ID and password.

(WBEM error code = "WBEM-

error- code", WBEM method name = "WBEM-method-name",

CIM class name = "target-CIM-

class-name", detailed information = "detailed-

information")

Specify a nickname that is not being used by another host storage domain on the same port, and then retry the operation.

Revise the specification so the maximum number of host storage domains is not exceeded.

Revise the specified iSCSI name, and then retry the operation.



Check, and if necessary, revise the specified parameters. In addition, make sure the status of the SMI-S provider and the SMI-S

Enabled subsystem are correct. If this problem persists, contact the SMI-S provider administrator.

Make sure the following parameters are correct, and the try again: SMI-S provider IP address, port number, user ID and password.



1-39

1-40

Error Code

KAIC05862-E

KAIC05863-E

KAIC05864-E

KAIC05865-E

KAIC05866-E

KAIC05867-E

KAIC05868-E


The environment for the SMI-S

Enabled subsystem is invalid.





information")

An internal error occurred during access to an SMI-S

Enabled subsystem. (WBEM error code = "WBEM-error-

code", WBEM method name =

"WBEM-method-name", CIM class name = "target-CIM-


information")

An unexpected error occurred during access to an SMI-S





information")


Enabled subsystem. (CIM method name = "CIM-method-

name", return value = "value-

returned-from-the-CIM-

method")


Enabled subsystem. (CIM method name = "CIM-method-



method")

Communication between the

SMI-S provider and SMI-S

Enabled subsystem timed out.

(CIM method name = "CIM-

method-name", return value =

"value-returned-from-the-CIM-

method")

Execution of the access method of the SMI-S Enabled subsystem failed. (CIM method name = "CIM-method-name", return value = "value-returned-

from-the-CIM-method")




Contact the SMI-S provider administrator.






Error Code

KAIC05869-E

KAIC05870-E

KAIC05871-E

KAIC05872-E

KAIC05873-E

KAIC05874-E

KAIC05875-E

KAIC05876-E

KAIC05877-E

KAIC05878-E

KAIC05879-E


A parameter required for accessing an SMI-S Enabled subsystem is invalid. (CIM method name = "CIM-method

name")

An invalid value was returned from an SMI-S provider. (CIM method name = "CIM-method-



method")

The specified volume size is invalid. (CIM method name =

"CIM-method-name")

The specified LU ID (LUN) is invalid. (CIM method name =


The specified initiator port ID

(WWN) is invalid. (CIM method name = "CIM-method-name")

The specified target port ID

(WWN) is invalid. (CIM method name = "CIM-method-name")

The specified permission is invalid. (CIM method name =


The specified initiator port and target port combination is already exists. (CIM method name = "CIM-method-name")

The specified LUN is already in use. (CIM method name =


An internal error occurred in an

SMI-S Enabled subsystem. (CIM method name = "CIM-method-



method")




"WBEM-error-code", WBEM method name = "WBEM-

method-name", detailed information = "detailed-

information")

Revise the parameter specification, and then try again.


Revise the volume size specification, and then try again.

Revise the LU ID (LUN) specification, and then try again.

Revise the initiator port ID (WWN) specification, and then try again.

Revise the target port ID (WWN) specification, and then try again.

Revise the permission specification, and then try again.

Revise the initiator port and target port combination, and then try again.

Revise the LUN specification, and then try again.






1-41

1-42

Error Code

KAIC05880-E

KAIC05881-E

KAIC05882-E

KAIC05883-E

KAIC05884-E

KAIC05885-E

KAIC05886-E


An attempt to access an SMI-S provider has failed. Check the following parameters: SMI-S provider IP address, port number, user ID, and password.

(WBEM error code="WBEM-

error-code", WBEM method name="WBEM-method-name", detailed information =




(WBEM error code="WBEM-

error-code", WBEM method name="WBEM-method-name", detailed information =



Enabled subsystem. (WBEM error code="WBEM-error-code",

WBEM method name="WBEM-


information")


Enabled subsystem. (WBEM error code="WBEM-error-code",

WBEM method name="WBEM-


information")

A job for an SMI-S Enabled subsystem has failed. (job status = "job-status", detailed code = "detailed-code", detailed information = "detailed-

information")



Enabled subsystem might be invalid. (WBEM method name =


class-name")

The SMI-S Enabled subsystem being managed by the specified

SMI-S provider is already managed by another SMI-S provider.

Check the following parameters, and the try the operation again: SMI-S provider IP address, port number, user ID, and password.







Specify settings such that multiple SMI-S providers do not manage the same SMI-S

Enabled subsystem.



Error Code

KAIC05887-E

KAIC05888-E

KAIC05889-E

KAIC05890-E





"WBEM-error- code", WBEM method name = "WBEM-

method-name", CIM class name

= "target-CIM-class-name", detailed information =

"detailed-information", subsystem name = "subsystem-

name")

An attempt to access the SMI-S

Enabled provider has failed.

Make sure the following parameters are correct: SMI-S provider IP address, port number, user ID and password.





information", subsystem name

= "subsystem-name")


















Make sure the following parameters are correct, and the try again: SMI-S provider IP address, port number, user ID and password.





1-43

1-44

Error Code

KAIC05891-E

KAIC05900-E

KAIC05902-E

KAIC05903-E

KAIC05904-E

KAIC05905-E

KAIC05906-E

KAIC05907-E

KAIC05908-E

KAIC05909-E









The option of the specified journal group cannot be modified.

"Inflow Control" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Inflow Control" cannot be modified because the specified journal group is a restore journal group.

A pool volume cannot be added because the status of the pool whose function is "PP Name

(QuickShadow)" and whose pool

ID is "pool ID" is blocked unless the usage rate is 100%.

"Data Overflow Watch" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Data Overflow Watch" cannot be modified because the specified journal group is a restore journal group and has a mirror whose status is "status".

"Path Watch Time" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Path Watch Time" cannot be modified because the specified journal group is a restore journal group and has a mirror whose status is "status".

"Path Watch Time" cannot be modified because the specified journal group is a restore journal group.


Check and, if necessary, revise the journal group type.

Check and, if necessary, revise the journal group type and the mirror status.


Recover from the pool blocked status, and then retry the operation.





Error Code

KAIC05910-E

KAIC05911-E

KAIC05912-E

KAIC05913-E

KAIC05914-E

KAIC05915-E

KAIC05916-E

KAIC05917-E

KAIC05918-E

KAIC05919-E

KAIC05990-E

Description

"Forward Path Watch Time" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Forward Path Watch Time" cannot be modified because the specified journal group is a restore journal group.

"Use of Cache" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Use of Cache" cannot be modified because the specified journal group is a restore journal group and has a mirror whose status is "status".

"Speed of Line" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Speed of Line" cannot be modified because the specified journal group is a restore journal group and has a mirror whose status is "status".

"Delta resync Failure" cannot be modified because the specified journal group is a master journal group and has a mirror whose status is "status".

"Delta resync Failure" cannot be modified because the specified journal group is a restore journal group.

A pool volume cannot be added because the status of the pool whose function is "PP Name

(Dynamic Provisioning)" and whose pool ID is "poolID" is blocked.

Virtual volumes for "PP Name

(Quick Shadow)" virtual volumes cannot be created because the number of virtual volumes for "PP Name (Quick

Shadow)" has already reached the maximum allowed.


(detailed information =











Recover from the pool blocked status, and then retry the operation.

Revise the settings.




1-45

1-46

Error Code

KAIC05991-E

KAIC05992-E

KAIC05993-E

KAIC05994-E

KAIC05995-E

KAIC05996-E

KAIC05997-E

KAIC05998-E

KAIC05999-E

Description

An attempt to create a volume has failed. Check whether a required license for the SMI-S

Enabled subsystem is missing or whether a hardware error has occurred.

The request was not completed within the time limit. Only part of the changes made to the configuration might have been applied to the SMI-S Enabled subsystem.

There is no response from the connection destination (IP-

address).

An error occurred while accessing the virtualizationserver management program or virtualization server. This might be because a specified parameter is invalid, or the virtualization-server management program or virtualization server is not in a normal status.

An attempt to access the virtualization-server management program or virtualization server failed.

Confirm that the IP address, user ID, and password of the connection destination are correct.

The virtualization server environment is invalid.

An internal error occurred while accessing the virtualizationserver management program or virtualization server.

An unexpected error occurred while accessing the virtualization-server management program or virtualization server.

The virtualization servers managed by the specified connection destination are already managed by another virtualization-server management program. The virtualization-server management configuration might have been changed.


If this problem occurs again, contact the

SMI-S provider administrator.

Refresh the SMI-S Enabled subsystem, and then check the changed settings. If this problem occurs again, contact the SMI-S provider administrator.

Make sure that the IP address and connection protocol are correct, and then try again.

Revise the parameters settings, check the status of the virtualization-server management program and virtualization server, and then try again. If this problem persists, contact the Support Center.

Make sure that the IP address, user ID, and password of the connection destination are correct, and then try again.




Revise the virtualization-server management configuration.



Table 1-8 KAIC06000-KAIC06999: Storage Array Errors: SNMP, Etc.

Error Code

KAIC06000-E

KAIC06002-E

KAIC06003-E

KAIC06004-E

KAIC06005-E

KAIC06006-E

KAIC06007-E

KAIC06008-E

KAIC06009-E

KAIC06010-E

KAIC06011-E

KAIC06012-E

KAIC06013-E


An unspecified storage array error was encountered.

An unspecified error occurred while executing SNMP command.

An attempt to create the SNMP session on the device at IP

Address "IP-address or host-

name" has failed.

Error retrieving oid "oid" due to a null oid table.

An attempt to retrieve the object ID "oid" has failed.


An internal server error was encountered due to a failure in the SNMP library. Contact the

Support Center.

An internal server error was encountered due to a failure in the SNMP library. Contact the

Support Center.

An error occurred while accessing the device via SNMP. This indicates a network connection or SNMP configuration error on the device.

A null value for object ID "oid" was retrieved via SNMP.

An SNMP error of status

"status" occurred while waiting for the command "command" to complete.

Communication timed out waiting for a response from the array. Check the network connection.

The SNMP set request has failed to execute the command

"command". Error status =

"error-status", index = "index".

An invalid command status trap was detected.

SNMP authentication has failed for the device at IP Address

"IP-address".

The storage array cannot be accessed. An operation is in progress at the SVP.

The device at IP Address "IP-

address" was not identified as a family storage array. Check the IP address and SNMP agent configuration.

An internal server error was encountered in the command trap specification. Contact the

Support Center.

The Device Manager Server must have read/write permission to perform management functions on the storage device.

Check the SNMP community string and make sure that the read/write permissions are correct.

An attempt to access the storage device failed as the SVP is currently in "Modify" mode.

Device Manager Server must have exclusive access to the device to perform management functions.

Check the IP address and SNMP agent connection.



1-47

1-48

Error Code

KAIC06100-E

KAIC06101-E

KAIC06200-E

KAIC06299-E

KAIC06300-E

KAIC06301-E

KAIC06302-E

KAIC06303-E

KAIC06305-E

KAIC06306-E

KAIC06307-E


The SNMP command has failed

(command status =

"command-status", meaning =

"meaning"). Only part of the configuration change may have been applied. Refresh the subsystem. If you are a local user, contact the system administrator.

The SNMP command has failed.

Information is not available. A refresh of the storage subsystem is recommended.

Contact your system administrator if you are a local user.

The subsystem serial number is invalid.

An error occurred during processing on the subsystem

(DampErrorCode = "error-

code-of-DAMP",

TransErrorCode = "error-code-

of-DampTrans", message =

"error-message"). If the configuration was being changed, refresh the subsystem. If you are a local user, contact the system administrator.

The command has failed on the storage array.

The Target ID mode of the controller is not "M-TID, M-LUN

(mapping mode)".

Refer to the applicable storage subsystem messages and recommended actions in this manual. Follow the recommended actions.

Perform a refresh on the storage array, and then retry.




Device Manager only supports the Target ID mode "M-TID, M-LUN (mapping mode)". For details about the Target ID mode, see the

Disk Array Management Program manual or

Storage Navigator Modular manual.

Contact the Support Center. An attempt to retrieve fibre channel port information for controller "controller-ID" has failed.

An attempt to retrieve the fibre channel port information for port "port-name" has failed.

The LUN security option is not installed on the storage array.

Check the configuration of the storage device.

The LUN security option must be installed to perform this function.

The LUN security option is disabled on the storage array.

The LUN security cannot be modified, because the port is in HP mode.

To change the LUN security, disable the HP mode of the port.



Error Code

KAIC06309-E

KAIC06311-E

KAIC06312-E

KAIC06313-E

KAIC06314-E

KAIC06315-E

KAIC06316-E

KAIC06317-E

KAIC06318-E

KAIC06320-E

KAIC06321-E

KAIC06322-E

KAIC06323-E

KAIC06330-E

Description

The LUN "LUN" of the port

"port-name" is already reserved for a non-existing

LDEV "device-number".

The integrated LU option is disabled on the storage array.

The integrated LU option is not installed on the storage array.


Device Manager does not support management of the specified LUN. Use Disk

Array Management Program or Storage

Navigator Modular to release the LUN.


The integration LU option must be enabled to perform this function.


The integration LU option must be installed to perform this function.

Contact the Support Center. An attempt to retrieve port information for controller

"controller-ID" has failed.

An attempt to retrieve port information for port "port-

name" has failed.

The host mode 2 "name-of-

host-mode-2" for fibre port is invalid.

The host mode 2 "name-of-

host-mode-2" for SCSI port is invalid.

The port option "port-option" for fibre port is invalid.

The port option "port-option" for SCSI port is invalid.

The subsystem does not support the host mode 2

"name-of-host-mode-2".

The target storage device is not in mapping mode.

This may indicate a configuration error on the storage device. Check the configuration of the storage device.


The request for the subsystem cannot be executed. The permission to manage the subsystem might have been acquired by another user.

The request for the subsystem cannot be executed. The login session of the subsystem has expired.

The specified subsystem

"array-family" is a SCSI model.

It is not supported in Device

Manager.

This operation requires that mapping mode be enabled. Check the device configuration. For details about the mapping mode, see the Disk

Array Management Program manual or

Storage Navigator Modular manual.

Make sure the storage array is not being accessed by the built-in account of another application. If it is not being accessed, refresh the subsystem, and then try again.

A forced logout might have been executed because the account was invalidated. Make sure such an operation was not executed performed on the subsystem by another user.

If no such operation was executed, refresh the subsystem, and then try again.

Check the subsystem.



1-49

1-50

Error Code

KAIC06400-E

KAIC06401-E

KAIC06402-E

KAIC06403-E

KAIC06450-E

KAIC06999-E

Description


(error code 1 = "error-code-1", error code 2 = "error-code-2", meaning = "meaning"). If the configuration was being changed, refresh the subsystem. If you are a local user, contact the system administrator.

An error occurred in the format processing of the subsystem.

(Error code = "Error Code")

Remove the cause of the problem, and then refresh the subsystem.

Processing in the subsystem has not finished. Remove the cause of the problem, and then refresh the subsystem.

LDEV (devNum="Device

number") is not in a formattable state.


(error code 1 = "error-code-1", error code 2 = "error-code-2", meaning = "meaning"). If the configuration was being changed, refresh both the subsystem and external subsystem. If you are a local user, contact the system administrator.

The SNMP command was cancelled after repeated failures.



Remove the cause of the problem, and then refresh the subsystem.

Refresh the subsystem, and then revise the

LDEV state.

Take action based on the applicable storage subsystem messages and recommended actions in the Device Manager error manual.


Table 1-9 KAIC07000-KAIC08999: Command (Agent) Errors

Error Code

KAIC07000-E

KAIC07001-E

KAIC07002-E

KAIC07003-E

KAIC07004-E

Description

Unspecified agent error was encountered.

Device Manager does not support the operation

"operation" for the storage array type.

The license key required for the operation is not installed.

The license key required for the operation is not active.

Invalid "LU" parameter.

Integer expected.



Device Manager Server does not support requests on the specified storage device.

Install the required license key.

Activate the required license key.

Make sure the "LU" is an integer value, and then retry. If this problem persists, contact the Support Center.



Error Code

KAIC07005-E

KAIC07006-E

KAIC07007-E

KAIC07008-E

KAIC07009-E

KAIC07010-E

KAIC07011-E

KAIC07012-E

KAIC07013-E

KAIC07014-E

KAIC07015-E

KAIC07016-E

KAIC07017-E

KAIC07018-E

KAIC07019-E

KAIC07020-E invalid.

Description

Missing parameter: Storage

Array "objectID".

Missing parameter: Port

"objectID".

Missing parameter: Path

"objectID".

Missing parameter: "WWN".

The value for the "scsiID" parameter is incorrect.

The specified WWN "WWN" is

Missing parameter:

WWNGroup "objectID".

Missing parameter: LUNGroup

"objectID".

The objectID references an incorrect object type for the request.

Missing parameter: Logical

Group "objectID".


The ObjectID parameter of Storage Array is required. Provide the missing parameter, and then retry.

The ObjectID parameter of the port is required. Provide the missing parameter, and then retry.

The ObjectID parameter of Path is required.

Provide the missing parameter, and then retry.

The WWN parameter is required. Provide the missing parameter, and then retry.

Check the SCSI ID. Make sure that the SCSI

ID is correct, and then retry. If this problem persists, contact the Support Center.

Make sure that the WWN parameter has the proper format.

ObjectID parameter of the WWNGroup is required. Provide the missing parameter, and then retry.

The ObjectID parameter of the LUNGroup is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

Check the type of the specified object.

Missing parameter: Host

"objectID".

Missing parameter: Logical

Group Element "objectID".

Missing parameter:

"objectID".

The specified logical group

("Logical-group-path") does not exist.

Missing parameter: Host

"name".

The ObjectID parameter of the Logical Group is required. Provide the missing parameter, and then retry.

The ObjectID parameter of the Host is required. Provide the missing parameter, and then retry.

The ObjectID parameter to be registered for the logical group as a logicalGroup element is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

The ObjectID parameter is required. Provide the missing parameter, and then retry.

Revise the parameter specifications.

A required element is missing from the request. "element"

The Name parameter of the Host is required.


Make sure that all of the required elements of a request are in place. Provide the missing element, and then retry. If this problem persists, contact the Support Center.



1-51

1-52

Error Code

KAIC07021-E

KAIC07022-E

KAIC07023-E

KAIC07024-E

KAIC07025-E

KAIC07026-E

KAIC07027-E

KAIC07028-E

KAIC07029-E

KAIC07030-E

KAIC07031-E

KAIC07032-E

KAIC07033-E

KAIC07034-E

KAIC07035-E

KAIC07036-E


There is more than one instance of the logical group

("Logical-group-path").

Specify the object ID.

Missing parameter: Host Info

"unspecified-parameter".

The logical group parent is invalid. A group cannot be its own parent.

The logical group parent is invalid. The request creates a circular group dependency.

The logical group parent was not found in the Device

Manager database.

The logical group was not found in the Device Manager database.

The storage array was not found in the Device Manager database.

The specified LDEV (devnum =

"Device number") cannot be found in the Device Manager database.

The specified path (port ID =

"Port ID", domain ID =

"Domain ID", devNum =

"Device number") cannot be found in the Device Manager database.

The host was not found in the


The host info was not found in the Device Manager database.

The "parameter-name" and

"parameter-name" parameters cannot be specified at the same time.

The number of elements specified in the request is invalid. (element = "element-

name")

Missing parameter: User

"loginID".

This operation cannot be executed because the maximum number of registerable RCUs or SSIDs has already been created.

Missing parameter: Rule

"ruleID".


Specify the object name not registered in the

Host Info.

Specify a logical group that is not also its own parent group.

The relationship between the logical group parent and logical group child is invalid. Check the specified group.

Check the logical group parent.

Check the logical group.

Check the coding of storage array.

Make sure that the specified LDEV is in the


Check and, if necessary, revise the path specification.

Check the host.

Check the host info.


Revise the number of elements in the request, and then try the operation again.

The User "loginID" is required. Provide the missing parameter, and then retry.

Delete any unnecessary RCUs or SSIDs, and then try again.

The Rule "ruleID" is required. Provide the missing parameter, and then retry.



Error Code

KAIC07037-E

KAIC07038-E

KAIC07039-E

KAIC07040-E

KAIC07041-E

KAIC07042-E

KAIC07043-E

KAIC07044-E

KAIC07045-E

KAIC07046-E

KAIC07047-E

KAIC07048-E

KAIC07049-E

KAIC07050-E

KAIC07051-E

Description

This operation cannot be executed because the maximum number of registerable logical paths has been exceeded.

Missing parameter: UserGroup

"name".

The user group was not found in the Device Manager database.


"password".


"groupName".

The user group name is invalid. Specify no more than

25 characters for the name, using only the following characters: a-z A-Z 0-9 - =

\ ` , . _

The user ID is invalid. Specify a user ID by using the following rules. Input rules :

"input-rules-for-user-ID"

The password is invalid.

Specify a password by using the following rules. Input rules: "input-rules-for-

passwords"

The specified group "specified-

logical-group-name" is not available because a child group with that name already exists under the group

"target-parent-logical-group-

name".

The specified group "specified-

logical-group-name" is not available because a top-level group with that name already exists.

A zero-length name is not permitted.

The file named "file-name" was not found.

The file named "file-name" cannot be read.

The MCU-RCU or remote path cannot be created between the specified storage subsystems.

Missing parameter: Debug level "value".


Delete any unnecessary logical paths, and then try again.

The UserGroup "name" is required. Provide the missing parameter, and then retry.

Check the user group.

The User "password" is required. Provide the missing parameter, and then retry.

The user "groupName" is required. Provide the missing parameter, and then retry.

Revise the entered user group name.

Revise the entered password.

Change the name of the child group, and then retry.

Change the group name, and then retry.

Revise the request, and then try again.


Revise the specification of the storage subsystem, and then try again.

The debug level "value" is required. Provide the missing parameter, and then retry.



1-53

1-54

Error Code

KAIC07052-E

KAIC07053-E

KAIC07054-E

KAIC07055-E

KAIC07056-E

KAIC07057-E

KAIC07058-E

KAIC07059-E

KAIC07060-E

KAIC07061-E

KAIC07062-E

KAIC07063-E

KAIC07064-E

KAIC07065-E

KAIC07066-E


The specified MCU port is not the Initiator.

The debug level value "debug-

level-value" is not valid.

An attempt to unregister

Subscriber "Subscriber-ID" has failed.

Missing parameter: Subscriber

"topic".

An attempt to register

Subscriber "Subscriber-ID" has failed.

Missing parameter: Network resource "IP Address".

The operation cannot be performed because the MCU-

RCU or remote path has already been created between the specified storage subsystems.

The "count" parameter is invalid, and needs to be a positive integer. This attribute should only be specified once.

This operation cannot be performed because the specified port is not in a modifiable combination.

The "start" parameter is invalid, and needs to be a date. This attribute should only be specified once.

Missing parameter: Object

"name".

Invalid parameter: Alert

"number" or "source" required.

The parent storage array could not be found.

Missing parameter: Storage device "arrayFamily".

This operation cannot be performed because the specified logical path is already registered for the

RCU.

Revise the specification of the logical path, and then try again.

Valid debug levels are 0 (All information) 1

(Informational messages and above) 2

(Warnings and above) 3 (Errors and above) 4

(Fatal errors only). Make sure that the "value" is valid, and then retry.

The specified Subscriber "Subscriber-ID" does not exist. Make sure that the "Subscriber-ID" is valid.

The topic of Subscriber is required. Provide the missing parameter, and then retry.


The "IP Address" is required. Provide the missing parameter, and then retry.

Revise the MCU-RCU or the remote path specification, and then try again.

Check the specified "count". Make sure that it is a positive integer, and then retry.

Revise the specification of the port, and then try again.

Check the specified "start". Make sure that it is a valid date, and then retry.

The object "name" is required. Provide the missing parameter, and then retry.

Both Alert "number" and "source" are required. Provide the missing parameters, and then retry. If this problem persists, contact the Support Center.

Check the description of storage array.

The "arrayFamily" of the storage device is required. Provide the missing parameter, and then retry.

Revise the specification of the path, and then try again.



Error Code

KAIC07067-E

KAIC07068-E

KAIC07069-E

KAIC07070-E

KAIC07071-E

KAIC07072-E

KAIC07073-E

KAIC07074-E

KAIC07075-E

KAIC07076-E

KAIC07077-E

KAIC07078-E

KAIC07079-E

KAIC07080-E

KAIC07081-E

KAIC07082-E

KAIC07083-E

Description

Missing parameter: Storage device "searchCommunity".

The "objectID" parameter is invalid.

The logical group can only contain objects from a single storage array.

The "Topic" parameter is invalid.

The parameter "name" exceeds the maximum possible length.

The specified logical paths are not set.

Invalid request target parameter: Expected

"expected-class-name"; found

"specified-class-name".


Controller "ID".


Controller "Mode".


Parameter "searchCommunity" of storage array is required. Provide the missing parameter, and then retry.

Make sure that the specified "objectID" is correct, and then retry.

An attempt was made to add an object to a logical group. However, a group can only contain objects from a single array.

Make sure that the specified "Topic" is correct, and then retry.

Make sure that the length of "name" does not exceed the maximum length, and then retry.



The value for Port Controller

Mode is invalid.

The requested mode cannot be set on a non-Fibre Channel

Port Controller.

The ports for the requested

Port Controller could not be found.

High Speed mode cannot be set because port "port1-ID" and port "port2-ID" have different host modes.

High Speed mode cannot be set because port "port1-ID" and port "port2-ID" have different topologies.

High Speed mode cannot be set because port "port1-ID" and port "port2-ID" have the same fibre address.

High Speed mode cannot be set because port "port-ID" topology is Point-To-Point.

The high speed mode cannot be set because LDEV "device-

number" is assigned to both port "port1-ID" and port

"port2-ID".

The Port Controller "ID" is required. Provide the missing parameter, and then retry.

The "Mode" of Port Controller is required.


Valid Port Controller value is required. See the

Device Manager Server XML API manual.

This request can only be attempted for a Fibre

Channel port.


High Speed mode requires that port "port1-

ID" and "port2-ID" have the same host mode.


ID" and "port2-ID" have the same topology.


ID" and "port2-ID" have the same fibre address.

High Speed mode requires that the topology of port "port-ID" be FC-AL.

Release the LDEV from one of the ports, and then retry the operation.



1-55

1-56

Error Code

KAIC07084-E

KAIC07085-E

KAIC07086-E

KAIC07087-E

KAIC07088-E

KAIC07089-E

KAIC07090-E

KAIC07091-E

KAIC07092-E

KAIC07093-E

KAIC07094-E

KAIC07095-E

KAIC07096-E

KAIC07097-E

KAIC07099-E

KAIC07100-E

KAIC07101-E

KAIC07102-E

KAIC07103-E

KAIC07104-E


The requested port has no

WWN.

Insufficient number of physical devices for array group.

The requested host mode is not available on this storage array.


"operation".


"ruleType".


"target".

Check the WWN of port.

The creation of an array group requires at least two physical devices.

Check the host mode or storage array.

Rule "operation" is required. Provide the missing parameter, and then retry.

Rule "ruleType" is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

Rule "target" is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

"group name" is required. Specify the missing parameter, and then retry.

A parameter is missing:

"group name" must be specified.


"role".

The role is invalid.

An invalid cluster number has been specified for the Port

Controller.

High speed mode is unavailable.

Invalid CHA number.

Invalid topology number.

Invalid fibre address.

Invalid channel speed.

The parameter "portID" is out of range. The valid range is

"minimum-port-ID" to

"maximum-port-ID".

The parameter "LU" is out of range. The valid range is

"minimum-LU" to "maximum-

LU".

The parameter "lun" is out of range. The valid range is

"minimum-lun(hex)

(minimum-lun)" to

"maximum-lun(hex)

(maximum-lun)".

The port was not found on the storage array.

The LU "device-number" was not found on the storage array.

User "role" is required. Provide the missing parameter, and then retry.

Check the role of user.

Check the number of the Port Controller.

High Speed mode is unsupported with the specified Port Controller.

Assign a valid card number.

Assign a valid topology.

Assign a valid fibre address.

Assign a valid channel speed.

Specify a valid value.

Check the specified port and storage array.

Check the specified LU and storage array.



Error Code

KAIC07105-E

KAIC07106-E

KAIC07107-E

KAIC07108-E

KAIC07109-E

KAIC07110-E

KAIC07111-E

KAIC07112-E

KAIC07113-E

KAIC07114-E

KAIC07115-E

KAIC07116-E

KAIC07117-E

KAIC07118-E

KAIC07119-E

Description

The LUN "LUN" was not found on the storage array.

The LU "device-number" is already in use on port "port-

name".

The LUN "LUN" is already in use on port "port-name".

The LU "device-number" is an

OnDemand device and cannot be used for an LUN.

This command cannot be processed, since both a

"devNum" attribute of a Path element and LDEV elements are not specified.

The LUN cannot be deleted, because one or more hosts are using it. LUN Security must be removed for this LUN before the path can be deleted.

The WWN "WWN" cannot be deleted. The WWN was not found on the port.

The port (portID = "Port ID") cannot be found in the storage subsystem.

The number of logical paths cannot go below the set minimum number of paths.

The security for this LUN cannot be changed, since it is part of LUNGroup "LUN-group-

nickname".

The LUN cannot be deleted, since it is part of LUNGroup

"LUN-group-nickname".

The specified remote paths are invalid. One port from both controller0 and controller1 must be specified.

The command cannot be executed because the specified WWN group is not on the port "port-name".

The command cannot be executed because the specified LUN group is not on the port "port-name".

The LUN referenced by the

HostInfo was not found in the storage array.


Check the specified LUN and storage array.

Check the LU.

Check the specified LUN.

Check the specified LU.

Check the request.

Clear the LUN security for this LUN, and then retry.

Make sure that the WWN and LUN are specified correctly. Otherwise, no action is required.

Check and, if necessary, revise the port or storage subsystem specification.


Delete the LUNGroup, and reissue the secure

LUN command.

Delete the LUNGroup, and then retry.

Revise the specification of the remote path, and then try again.

Make sure that the correct WWN group and port are specified, and then try again.

Make sure that the correct LUN group and port are specified.

Check the LUN.



1-57

1-58

Error Code

KAIC07120-E

KAIC07121-E

KAIC07122-E

KAIC07123-E

KAIC07124-E

KAIC07125-E

KAIC07126-E

KAIC07127-E

KAIC07128-E

KAIC07129-E

KAIC07130-E

KAIC07131-E

KAIC07132-E

KAIC07133-E

KAIC07134-E

Description

The specified host ("host-

name-or-objectID") does not exist.

The logical group element cannot be deleted, because the element is not part of the

Logical group.

The host name "host-name" is already used by an existing host.

The host info record is already contained in the Device

Manager database.

The storage array with serial number "serial-number" was not found in the Device

Manager database.

Cannot delete host "host-

name", because one of the

WWNs is securing an LUN.

The LDEV "device-number" is a "PP Name

(VolumeMigration)" reserved volume and cannot be used for an LUN.

Invalid parameter: Filter

"Condition volumeKind"



Check the specified objectID.

Specify a new host name.

Check the HostInfo.

Check the specified objectID of the storage array.

Clear the LUN before deleting the host.

Check the LDEV.

The logical unit with LU

"device-number" is a command device. The LUN cannot be deleted.

The WWN

"00.00.00.00.00.00.00.00" is invalid, and cannot be used to secure an LUN.

An LUN cannot be added to a port of type "port-type".

The SCSI ID "SCSI-ID" was not found on the storage array.

This operation cannot be performed for a port of the port type "port-type".

The maximum number of

WWNs ("maximum-number-

of-WWNs") cannot be exceeded.

The WWN "WWN" is already in use by host "host-name".

Make sure that the "Condition volumeKind" is valid. The valid Condition volumeKinds are

"MAINFRAME", "INTERMEDIATE", "OPEN" or combinations of these.

Check the LU.

Make sure that the WWN is correct.

Check the port.

Check the SCSI ID.

Check the port.

No more WWNs can be added to the port.

Delete WWNs that are not used, and then retry.

Check the specified WWN.



Error Code

KAIC07135-E

KAIC07136-E

KAIC07137-E

KAIC07138-E

KAIC07139-E

KAIC07140-E

KAIC07141-E

KAIC07142-E

KAIC07143-E

KAIC07144-E

KAIC07145-E

KAIC07146-E

KAIC07147-E

KAIC07148-E

Description

Physical device #"PDEV-ID" is already in use (role = "role").

Physical device #"PDEV-ID" is not on the proper chassis for the array group.

A logical unit that has an LUN defined cannot be deleted.

An array group that has an

LUN defined cannot be deleted.

Parameter "chassis" is out of range. The valid range is

"minimum-number-of-chassis" to "maximum-number-of-

chassis".

The Port Controller was not found in the Device Manager database.


LDEVs ("maximum-number-

of-LDEVs") for the array group cannot be exceeded.

An attempt to delete a spare drive has failed. The physical device #"PDEV-ID" is not a spare drive or is a spare drive which is currently being used.

The spare physical device

#"spare-physical-device-ID" must be deleted from the array group.

An invalid emulation type was specified.

An invalid capacity was specified for the desired emulation type.

Insufficient free space on the specified array group.


Check the PDEV "pdevID".

A PDEV with chassis specified as array groups is required.

The LUN must be deleted prior to deleting the logical unit.

The LUN must be deleted prior to deleting the array group.

Specify a valid "chassis" range in within the range "minimum-number-of-chassis" to

"maximum-number-of-chassis", and then retry.

Check the specified Port Controller.

Ensure that the number of LDEVs in the array group does not exceed the maximum, and then retry.

Check the specified PDEV.

Delete this array group to delete this spare physical device.

The emulation type specified is not supported by the operation. Device Manager Server can only create logical units using OPEN emulation.


Specify the size within the scope of free space.

For details, see the manual that corresponds to your storage subsystem.

Check the specified chassis. The maximum number of array groups ("maximum-

number-of-array-groups") for the chassis cannot be exceeded.

The parameter

"defaultPortController" is out of range. The valid range is

"minimum-controller-number" to "maximum-controller-

number".

Specify a "defaultPortController" within the range "minimum-controller-number" to

"maximum-controller-number", and then retry.



1-59

1-60

Error Code

KAIC07149-E

KAIC07150-E

KAIC07151-E

KAIC07152-E

KAIC07153-E

KAIC07154-E

KAIC07155-E

KAIC07156-E

KAIC07157-E

KAIC07158-E

KAIC07159-E

KAIC07160-E

KAIC07161-E

KAIC07162-E

Missing parameter: "host mode" in the ModifyPort request.

Description

Device Manager does not manage the specified Port

Controller "port-controller-ID".

Device Manager does not manage the specified port

"port-name".

Cannot find the specified storage array.

The parameter "domainID" is out of range. The valid range is "minimum-number-of-

domainID" to "maximum-

number-of-domainID".

The domainID "domainID" is already in use on port "port-

ID".


HostStorageDomains

("maximum-number-of-host-

storage-domains") for the port

"port-number" cannot be exceeded.

The host storage domain (port

ID = "Port ID", domainID =

"Domain ID") cannot be found in the Device Manager database.

Missing parameter:

HostStorageDomain

"objectID".


Check the specified Port Controller.

Check the specified port.

Check the specified storage array.

Specify a "domainID" within the range

"minimum-number-of-domainID" to

"maximum-number-of-domainID", and then retry.

Change the domainID.


Check and, if necessary, revise the host storage domain specification.

The HostStorageDomain "objectID" is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

The HostStorageDomain "host mode" is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

Check the specified objectID. "name" of the specified object cannot be deleted.

The partitioned storage administrator who manages this subsystem cannot modify the configuration of the port

(port ID = "Port ID") that belongs to SLPR: "SLPR-

Number".

The security for the LUN cannot be changed, because the WWN is part of

WWNGroup "WWNGroup".


"Condition type"

Missing parameter: "Port".

Check and, if necessary, revise the port specification.

Delete the WWNGroup, and reissue the secure/unsecure LUN command.

Revise the value you specified in Condition type. Valid values are ALL, FREE, ASSIGNED,

UNASSIGNED and RESERVED.

Port parameter required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.



Error Code

KAIC07163-E

KAIC07164-E

KAIC07165-E

KAIC07166-E

KAIC07167-E

KAIC07168-E

KAIC07169-E

KAIC07170-E

KAIC07171-E

KAIC07172-E

KAIC07173-E

KAIC07174-E

KAIC07175-E

KAIC07176-E


The specified port option is invalid.

The specified host mode 2 is invalid.

Inconsistent combinations of host modes are specified for the same port.

Inconsistent combinations of host mode 2 are specified for the same port.

XML Message has no API

Version for the URLLink.

The specified WWN does not exist on the target "target-

element".

This operation cannot be performed for a Port Controller of E-NAS.

The specified user ID is invalid.

The specified LU used by PP

Name (TrueCopy)/PP Name

(ShadowImage) cannot be deleted.

No more command devices can be added to the specified subsystem.

This operation cannot be performed for a system volume (devNum = "Device

number") of E-NAS.

For the specified emulation type "emulation-type", the creation capacity automatically computed from the specified size "specified-

size-in-KBKB" is "creation-

size-in-KBKB". Re-specify this value so that the creation capacity is within the range of

"lower-limit-size-in-KBKB" to

"upper-limit-size-in-KBKB".

Free space is insufficient on the specified array group.

Specify the size within the range of the free space. The automatically computed capacity for creation is

"creation-size-in-KBKB".

A Command Device without an

LUN defined cannot be added.


The specified storage subsystem does not support different combinations of host modes for the same port. Revise the settings.

The specified storage subsystem does not support different combinations of host mode 2 for the same port. Revise the settings.


Check the specified WWN, and then retry.

The operation is not supported for a Port

Controller of E-NAS.

Specify an effective user ID.

Check and, if necessary, revise the LU specification.

Up to 2 command devices can be specified.

Delete any unnecessary command device, and then retry.

The operation is not supported for an E-NAS system volume.


Specify the size within the range of free space.

Perform this operation after the definition of an LUN.



1-61

1-62

Error Code

KAIC07177-E

KAIC07178-E

KAIC07179-E

KAIC07180-E

KAIC07181-E

KAIC07182-E

KAIC07183-E

KAIC07184-E

KAIC07185-E

KAIC07186-E

KAIC07187-E

KAIC07188-E

KAIC07189-E


The last path of an LU

(devNum = "Device number") set for a command device cannot be deleted.

The specified command option is invalid.

Invalid parameters: domainID and WWN cannot be specified at the same time.

In LUSE creation, LDEV

"device-number" overlaps and is specified.

Missing parameter: LogicalUnit

"commandDevice".

Delete the command device, and then the path.

An invalid command option is specified.

Make sure that the request is correct.

Check the specification of LDEV.

The commandDevice parameter of LogicalUnit is required. Provide the missing parameter, and then retry. If this problem persists, contact the Support Center.

Check the LU. The LU "device-number" is a

PP Name (VolumeMigration) reserved volume, and cannot be used for a command device.

The LU "device-number" is a

LUSE device, and cannot be used for a command device.

The specified LU "device-

number" cannot be used as a

Command Device because it is being used by PP Name

(TrueCopy)/PP Name

(ShadowImage).


(devNum = "Device number") used by PP Name



To create a command device, the size of specified LU must be "minimum size of LU which

can create a command device"

KB or more.

If the specified path is not a representative LDEV configuring a LUSE, the path cannot be deleted.



Check the LU.

Use Disk Array Management Program or

Storage Navigator Modular to delete the path that is not a representative LDEV configuring a

LUSE, and then use Device Manager to refresh the storage subsystem.


The path for an LU used by PP



Device Manager Server does not support the operation

"operation" for the specified

LDEV.

Device Manager Server supports the operation for only open volumes. Check the specified

LDEV.



Error Code

KAIC07190-E

KAIC07191-E

KAIC07192-E

KAIC07193-E

KAIC07194-E

KAIC07195-E

KAIC07196-E

KAIC07197-E

KAIC07198-E

KAIC07199-E

KAIC07200-E

KAIC07201-E

KAIC07202-E


This command cannot be processed, since the specified

LU is a command device.

This command cannot be processed, since the specified

LU in not a command device.

The parameter "element-

name" is insufficient. Either

"attribute-name-1" or

"attribute-name-2" must be specified.

This command cannot be processed, since command device security is already set for the specified LU.

This command cannot be processed, since command device security is not set for the specified LU.

A non-OPEN emulation

LogicalUnit cannot be set as a command device.

The LU "device-number" is already being used for "PP

Name (QuickShadow)"

"volume type of QuickShadow"

.

An array group cannot consist of PDEVs with different drive types.

A RAID0 array group cannot consist of PDEVs with specified drive types.

The specified object already exists in the logical group

"LogicalGroup name".

The request has failed: empty messageID in request.

Check the LU.

Check the parameter.

Check the LU.

Make sure that the PDEV specification is valid.

Revise the object specifications.

GetRequestStatus requires a valid messageID attribute. Add a valid messageID attribute to the request, and then retry.


An attempt to create an external array group has failed. The specified external storage subsystem is in the same storage subsystem.

The request has failed: messageID "message-ID" not found.

No data was found for message ID. This is most likely because the data was already retrieved. See if the Device Manager database has been updated with the results of the request (i.e. Add Storage Array).



1-63

1-64

Error Code

KAIC07203-E

KAIC07204-E

KAIC07205-E

KAIC07206-E

KAIC07207-E

KAIC07208-E

KAIC07209-E

KAIC07210-E

KAIC07211-E

KAIC07212-E

KAIC07213-E

KAIC07214-E


This command cannot be executed because a normal volume and a V-VOL of "PP

Name (QuickShadow)" are mixed in the specified LU

(devNum = "Device number" and devNum = "Device

number").

This command does not support the specified emulation type.

An invalid combination of path group IDs is specified.

For a remote command device, the parameter

"number of LU" cannot be specified for numOfLUs.

An attempt to create an external array group has failed because the combination of the specified port "port-name" and external storage subsystem port (WWN =

"port-WWN") is invalid.

An attempt to create an external array group has failed because the combination of the specified port "port-name" and external storage subsystem volume (LUN =

"LUN") is invalid.

The external volumes for alternate paths are different.

The replication group is already registered in the


The request failed, since a null objectID exists in

ReplicationGroup.

An attempt to execute the request has failed. The object specified in ReplicationGroup was not found in the database.

The request failed, since a null objectID exists in

ReplicationInfo.

An attempt to execute the request has failed. The object specified in ReplicationInfo was not found in the database.


Specifiy "OPEN-V" as the emulation type.


Revise the specifications for the port and external storage subsystem port.

Revise the specifications for the port and external storage subsystem volume.

Revise the alternate paths specification.

Check the ReplicationGroup.

"api-name" requires a valid objectID attribute in the ReplicationGroup. Add an objectID to the request, and then retry.


"api-name" requires a valid objectID attribute in the ReplicationInfo. Add an objectID to the request, and then retry.




Error Code

KAIC07215-E

KAIC07216-E

KAIC07217-E

KAIC07218-E

KAIC07219-E

KAIC07220-E

KAIC07221-E

KAIC07222-E

KAIC07223-E

KAIC07224-E

KAIC07225-E

KAIC07226-E


The request failed, since the specified ReplicationGroup is not handled by Device

Manager.

The request failed, since the specified ReplicationInfo is not in the specified

ReplicationGroup.

The specified command option is invalid. The number of specified command option items is "number-of-specified-

option-items", but the API requires at least "minimum-

items-api-requires".

The specified command option is invalid. The number of specified command option items is "number-of-specified-

option-items", but the API requires at most "maximum-

items-api-demands".

The request failed, since the specified copyTrackSize "copy-

track-size" is invalid.

The replication controller pair was not found in the Device

Manager database.

The specified logical unit

(array type = "type-of-LU", serial number = "LU-serial-

number", device number =

"LU-device-number") cannot be used in a pair because the host's I/O suppression mode is enabled.

The specified LU "device

number" cannot be used for a

LUSE device because it is being used by PP Name


(ShadowImage).

The LUSE cannot be deleted because the specified LU

"device number" is used by PP


(ShadowImage).

The specified host mode option is invalid.

The object ID of the host is not specified.

The specified object ID of the host is invalid.

Check the property file of the corresponding host agent.

Check the request, and then retry.

Check what is specifies for the replication controller pair.

Revise the logical unit specification.


Revise the host mode option specification.

Revise the request, and then retry.

Specify the object ID of a host that batchmanages pairs.



1-65

1-66

Error Code

KAIC07227-E

KAIC07228-E

KAIC07229-E

KAIC07230-E

KAIC07231-E

KAIC07232-E

KAIC07233-E

KAIC07234-E

KAIC07235-E

KAIC07236-E

KAIC07237-E

KAIC07238-E

KAIC07239-E

KAIC07240-E


The object ID of "Element-

name" cannot be specified.

The specified

"replicationOwnerHost" was not found in the Device

Manager database.

The "Element-name" element is not specified.

The command cannot be executed because the specified LDEV "Device

number" is protected.

The command cannot be executed because a path is set for the specified LDEV "Device

number".


number" is set to a PP Name

(VolumeMigration) reserved volume.


number" is not a representative LDEV making up a LUSE Volume.


number" is a pair device.

The LDEV "Device number" specification is duplicated.


"Condition host"


Revise the LDEV specification.



Make sure that the "Condition host" is valid.

The valid Condition hosts are "ASSIGNED" and

"UNASSIGNED".

Revise the specifications for the logical unit. Multiple instances of the same logical unit "Device number" have been specified.

It is not possible to create an unformatted logical unit in the specified subsystem.

A Quick Format cannot be executed because there is no

System Disk area.

This command cannot be executed, because the specified LU is being used as a remote command device in another subsystem.

Revise the subsystem specification.

Create the System Disk area, and then try again.




Error Code

KAIC07241-E

KAIC07242-E

KAIC07243-E

KAIC07244-E

KAIC07245-E

KAIC07246-E

KAIC07247-E

KAIC07248-E

KAIC07249-E

KAIC07250-E

KAIC07251-E

KAIC07252-E

KAIC07253-E



number" was being used for

PP Name (Dynamic

Provisioning).

The LDEV "device-number" is a command device. The LDEV cannot be deleted.

The LU "device-number" cannot be formatted because it is an external volume, pool volume, or journal volume.

The wait option and quickformat option cannot be specified at the same time.

The specified external volume is a command device. When specifying the capacity of the

LU, you need to specify the same capacity as the external volume.

An attempt to create an external array group has failed because two or more combinations of the port

"port-name" and external storage subsystem port (WWN

= "port-WWN") are specified.

This operation cannot be performed for a port whose port role is "port-role".

The specified external volume is a command device. Mapping to an internal volume is required.

The cache mode cannot be set for a remote command device.

The LDEV related to the specified PP Name

(VolumeMigration) migration plan was not found in the


The specified "parameter-

name" was not found in the


LUSE is set for the specified

LDEV. The LDEV cannot be used for a PP Name


The specified VolumeMigration element objectID is invalid.


Check the LDEV.

Check the specified LU, and then try again.

Check the request, and then try again.


Revise the specifications for the port and external storage subsystem port.

Revise the port specification.




Revise the parameter specification.


Revise the objectID specification.



1-67

1-68

Error Code

KAIC07254-E

KAIC07255-E

KAIC07256-E

KAIC07257-E

KAIC07258-E

KAIC07259-E

KAIC07260-E

KAIC07261-E

KAIC07262-E

KAIC07263-E

KAIC07264-E

Description

A path is set for the specified

LDEV. The LDEV cannot be used for a PP Name


The specified LDEV is a command device. It cannot be used for a PP Name


The specified LDEV is already set as a PP Name


The specified LDEV is not PP

Name (VolumeMigration) reserved volume.

An attempt to execute the request has failed. A set or release operation for the PP

Name (VolumeMigration) reserved volume cannot be specified simultaneously.


(VolumeMigration) migration plan is not in the subsystem

("Array type", "Serial

number").

An attempt to execute the request has failed. The same ownerID must be specified for all VolumeMigration elements.

Invalid parameters were specified. The same sourceDevNum

"sourceDevNum of volume

migration" was specified for two or more VolumeMigration elements in the request.

Invalid parameters were specified. The same targetDevNum "targetDevNum

of volume migration" was specified for two or more

VolumeMigration elements in the request.

The owner ID specified in the request does not match the owner ID of the target volume.

An attempt to execute the request has failed. The ownerID must be specified in the VolumeMigration element.



Unify the specification of the reserved volume.

Check and, if necessary, revise the request.

Revise the ownerID specification, and then retry.

Revise the sourceDevNum specification for the

VolumeMigration elements, and then retry.

Revise the targetDevNum specification for the

VolumeMigration elements, and then retry.

Check the owner ID specifications.

Specify the same value as the ownerID of the target volume related to the VolumeMigration element.



Error Code

KAIC07265-E

KAIC07266-E

KAIC07267-E

KAIC07268-E

KAIC07269-E

KAIC07270-E

KAIC07271-E

KAIC07272-E

KAIC07273-E

KAIC07274-E

KAIC07275-E

Description

An attempt to execute the request has failed. The emulation types of the specified source and target volumes do not match.

An attempt to execute the request has failed. The size of the specified source and target volumes do not match.

An attempt to execute the request has failed. The specified volume is a pair consisting of a standard volume and a CVS volume.

An attempt to execute the request has failed. Specify the same hihsmOwnerID for all

LDEVs.

The specified LDEV is protected. It cannot be used for a PP Name


An attempt to execute the request has failed. The specified LDEV is a pair device. It cannot be used for a

PP Name (VolumeMigration) reserved volume.

An attempt to execute the request has failed. The parameter "Attribute name" is outside the valid range. The valid range is from "Min.

parameter value" to "Max.

parameter value".

The specified LDEV cannot be used because it is set for

ChacheResidency.

The parameter is invalid.

(Filter "Condition hostType")

The object ID of the host or the host name cannot be specified at the same time as the filter used for selecting the host.

The specified LDEV is being used for PP Name (Dynamic

Provisioning), and cannot be used for PP Name

(VolumeMigration).


For the source and target volumes, specify volumes that have the same emulation type.

For the source and target volumes, specify volumes that are of the same size.

Specify standard volumes or CVS volumes for the source and target volumes.

Revise the hihsmOwnerID specification, and then retry.




Revise the specification, then retry.




1-69

1-70

Error Code

KAIC07276-E

KAIC07277-E

KAIC07278-E

KAIC07279-E

KAIC07280-E

KAIC07281-E

KAIC07282-E

KAIC07283-E

KAIC07284-E

KAIC07285-E

KAIC07286-E

KAIC07288-E

KAIC07289-E

Description

The path cannot be set because the specified LDEV

"Device number" is being used in the pool of PP Name

(Dynamic Provisioning).

A PP Name (Dynamic

Provisioning) volume cannot be deleted in Device Manager.

A parameter is not specified.

("parameter")

The specified user ID or password is too long. This user ID and password cannot be used to access the SMI-S provider from Device

Manager. Specify a user ID and password by using 1024 bytes or fewer, and then try again.

The specified LDEV has a different logical DKC. The system cannot create the

LUSE. (devNum = "Device

number")

A parameter is invalid. (Filter:

"Condition portType")

The P-VOL's pool ID does not match the S-VOL's pool ID.

The specified pool does not exist in the Device Manager database.

An attempt to execute the request has failed. All replication pairs in the same replication group must use the same Pool.

A parameter is invalid.

(parameter = "parameter")

This operation cannot be performed because the command device is not specified.

This operation cannot be performed because the specified ports are not Fibre

Channel ports.

This operation cannot be performed because the specified ports are not SLPR:0 ports.


Make sure the LDEV specifications are correct.

Revise the LogicalUnit specification.

Revise the specification, and then try again.

Specify a valid user ID and password, and then try again.


Revise the specification, and then retry the operation.

Revise the pool ID specification.

Revise the pool specification.



Specify the command device, and then try again.

Revise the specification of the ports



Error Code

KAIC07290-E

KAIC07291-E

KAIC07292-E

KAIC07293-E

KAIC07294-E

KAIC07295-E

KAIC07296-E

KAIC07297-E

KAIC07298-E

KAIC07299-E


This command cannot be executed because the specified LDEV "device-

number" is being used by a pool of "PP-name (Dynamic

Provisioning)".

No more DM-LUs can be added to the specified subsystem.

This operation cannot be performed because the specified LU size, "LU-size"

GB, is insufficient.

This operation cannot be performed because the specified LU is not set as a

DM-LU.

The specified LU is not in the


This operation cannot be performed because the specified remote path does not use a Fibre Channel connection.

The executed command cannot use the specified volume "Device number".


Delete any unnecessary DM-LUs

Revise the specification of the LU

Revise the remote path specification, and then try again.

Device Manager cannot be used to perform operations on the specified pair or pairs.

This operation cannot be performed because the specified LU is already set as a

DM-LU.

The serial number of the specified subsystem (IP address = "IP-address") does not match the serial number registered in Device Manager.

The serial number might have been changed during maintenance work. (registered serial number = "registered-

serial-number", current serial number = "current-serial-

number")

Device Manager does not support operations on High Availability Manager volumes or

External Storage Availability Manager volumes. Release the High Availability

Manager or External Storage Availability

Manager configuration for the selected volume or select a different volume, and then retry the operation.

Device Manager does not support operations on High Availability Manager copy pairs or

External Storage Availability Manager copy pairs. Release the High Availability Manager or

External Storage Availability Manager configuration for the selected copy pair or select a different copy pair, and then retry the operation.

Revise the specification of the LU

Delete the target subsystem information from

Device Manager, and then re-add it.



1-71

1-72

Error Code

KAIC07300-E

KAIC07301-E

KAIC07302-E

KAIC07303-E

KAIC07304-E

KAIC07305-E

KAIC07306-E

KAIC07307-E

KAIC07308-E

KAIC07310-E

KAIC07311-E

KAIC07312-E

KAIC07313-E

KAIC07314-E

KAIC07315-E


A negative value is specified for the Messages timeToWait attribute.

The Subscriber is not registered.

Missing parameter in the

URLLink request.

The URLLink in the request does not exist.

The URLLink request contains both the objectID and linkedID parameters.

The objectID in the URLLink request does not reference a known storage array.

URLLink acquired from an

SMI-S Enabled subsystem cannot be deleted.

The object specified for linkedID cannot be found.

Device Manager does not support URLLink operations for specified Device Manager objects.

The host is not specified for performance data acquisition.

Specify the host for the property "server.cim.agent" in the "server.properties" file, restart Device Manager

Server, and the retry the operation.

Device Manager does not manage the specified host

"Host name".

The Port parameter and

LogicalUnit parameter cannot be specified at the same time.

Neither the Port parameter nor the LogicalUnit parameter is specified.

The specified storage subsystem does not support performance data acquisition, or the necessary microcode version is not installed.

The specified range of

LogicalUnit (from "Lower value

for LU range" to "Upper value

for LU range") is invalid.


Register the Subscriber by using

AddSubscriber in the XML-API.

Check the specified URLLink.

Revise the option and objectID specification.

Either objectID or linkedID must be specified, but not both.

Check the specified storage array.

Check the specified URLLink.

Revise the option and linkedID specification.

Revise the URLLink specification.

None.

Add the specified Host, and the retry.




Revise the specified parameters, and then retry the operation.



Error Code

KAIC07320-E

KAIC07321-E

KAIC07322-E

KAIC07323-E

KAIC07324-E

KAIC07325-E

KAIC07326-E

KAIC07327-E

KAIC07328-E

KAIC07331-E

KAIC07332-E

KAIC07333-E

KAIC07334-E

KAIC07335-E

KAIC07336-E


The specified subsystem is not supported the DF series

Performance retrieval function.

The specified label "label" is invalid because the maximum length for a label is maximum

label length bytes.

The specified label "label" is invalid because an empty string cannot be specified as a label.

The specified label "label" is invalid because it contains an invalid character.

The same LDEV is specified by more than one element.

The specified LDEV already has a label.

The targetID parameter of

ObjectLabel is missing.

Check the specified Parameter, and then retry.

Revise the label specification, and then try again.

The label parameter of

ObjectLabel is missing.

The specified LDEVs belong to more than one storage subsystem.

The host storage domain

(portID = " port ID", domainNickname = " domain

nickname") cannot be found in the Device Manager database.

Invalid parameters: domainID and domainNickname cannot be specified at the same time.

Invalid parameters: domainNickname and WWN cannot be specified at the same time.

Invalid parameters: parameter and parameter cannot be specified at the same time.(element = element)

A required parameter is not specified. (element = element, parameter = parameter)

Invalid parameters were specified. The attribute

"parameter" of the element

"element" and element

"element" cannot be specified at the same time.

Revise the LDEV specification, and then try again.


The targetID parameter of ObjectLabel is required. Specify the missing parameter, and then try again.

The label parameter of ObjectLabel is required. Specify the missing parameter, and then try again.


Revise the host storage domain specification.

Check and, if necessary, revise the parameters.

Check and, if necessary, revise the parameters.



1-73

1-74

Error Code

KAIC07337-E

KAIC07350-E

KAIC07351-E

KAIC07352-E

KAIC07353-E

KAIC07354-E

KAIC07356-E

KAIC07357-E

KAIC07358-E

KAIC07359-E

KAIC07360-E

KAIC07361-E


The command option option-

name cannot be specified for hosts of the type host-type.

The LUSE Feature is not available for the storage array.

All the LDEVs that make up a

LUSE must have the same

"attribute-name". The requested "attribute-name" of the LDEVs is "value1"

(devNum = "Device number") and "value2" (devNum =

"Device number").

In this API version, LDEVs that constitute a LUSE cannot be specified in LUSE creation.

The specified LDEV "LDEV-

identifier (devNum)" is a reserved volume of PP Name

(VolumeMigration). This LDEV cannot be used in a LUSE.

The LDEV "LDEV-identifier

(devNum)" currently exists as an LUN. This LDEV cannot be used in a LUSE.

The number of LDEVs for the

LUSE (devNum = "Device

number") must be between

"minimum-number-of-LDEVs" and "maximum-number-of-

LDEVs".

Response data not found for

Transport Layer.

The specified LDEV "LDEV-

identifier (devNum)" is a RAID

0 LDEV. RAID 0 LDEVs cannot be used to create a LUSE.

The microcode version of the storage array is insufficient for the requested LUSE operation.

The microcode version is

"microcode-version".

The LUSE cannot be created because the specified LDEVs

(devNum = "Device number" and devNum = "Device

number") have different default controllers.

For Device Manager, the LDEV

"devNum-of-LDEV" must be the representative LDEV in

LUSE operations using the microcode "microcode-

version" of this subsystem.

Revise the specified host.

The storage array does not support LUSE functionality. Check the specified storage array.

For the LDEVs that make up a LUSE, specify

LDEVs that have the same "type".


Revise the specifications for the LDEVs that make up the LUSE, and then try again.

Revise the specifications for the LDEVs that make up the LUSE.

Revise the specified number of LDEVs to be created for the LUSE.



Check the version of the software contained in the storage subsystem.

Check and, if necessary, revise the specifications of the LDEVs that make up the

LUSE.




Error Code

KAIC07362-E

KAIC07363-E

KAIC07364-E

KAIC07365-E

KAIC07366-E

KAIC07367-E

KAIC07370-E

KAIC07380-E

KAIC07381-E

KAIC07390-E

KAIC07391-E

KAIC07400-E


The size of a created LUSE

(devNum = "Device number") must be less than "max-size-

of-LUSETB". The specified size is "size-of-LUSEKB".

A logical unit that has a LUSE defined cannot be deleted.

The LUSE must be deleted before deleting the logical unit.

The LUSE cannot be created because the emulation type of a specified LDEV (devNum =

"Device number") is not OPEN.

An attempt to delete pairs has failed.

The LUSE cannot be created because the drive types of the specified LDEVs (devNum =

"Device number"and devNum

= "Device number") are different.

The specified LDEV "Device

number" is being used for PP

Name (Dynamic Provisioning), and cannot be used for a

LUSE.

The specified subsystem

("array-type", "serial-number

(Secret)") is not an object of

Device Manager management.

Invalid parameter: "element",

"invalid-parameter"

Check and, if necessary, revise the specifications of the LDEVs that make up the

LUSE.

LUSE must be deleted before deleting LDEV.

Check and, if necessary, revise the LDEV specification.


Center.

Check and, if necessary, revise the specifications of the LDEVs.


This is an information message only. No additional action is required.

Check that all of the required parameters of the element are specified. If a parameter is missing, specify the missing parameter, and then retry. If this problem persists, contact the Support Center.

Check the value of the ConfigurationChange element's type attribute.

An invalid value was specified in the ConfigurationChange element's type attribute. "type

attribute"

The specified storage subsystem does not support secure communication.

An attempt to execute a request has failed. The specified communication protocol is invalid.

HiScan SetHostVolume agent encountered an error : "error-

details".






1-75

1-76

Error Code

KAIC07401-E

KAIC07410-E

KAIC07411-E

KAIC07412-E

KAIC07413-E

KAIC07414-E

KAIC07415-E

KAIC07416-E

KAIC07417-E

KAIC07420-E

KAIC07421-E

KAIC07422-E

KAIC07423-E

KAIC07424-E

Description

The host IP address could not be resolved.

The specified host "host-

name" cannot be deleted because the host type of that host is "External port".

The WWNs of the specified host "host-name" cannot be changed because the host type of that host is "External port".

The AddHostRefresh operation is not supported for a host whose host type is "host-

type".

The file server information

"the-information-attempted-

to-be-changed" cannot be changed.

WWNs cannot be added to a mainframe host.

The specified host type "host-

type" is invalid.

This API cannot modify information of the specified host "host-name".

The host "host-name" cannot be merged because its host type is host-type.

The host "host-name" does not have a WWN or iSCSI name.


Revise the host agent settings and the host environment. If the problem persists, contact the Support Center.

Retry. If this problem persists, contact the

Support Center.

An attempt to update the host information has failed.

Another operation that updates the host information is already being executed.


Another operation that sets up the host is being executed.


Another operation is accessing the host information.

The updating of the host information was interrupted.

Device Manager Server may be shutting down.

Check the Device Manager Server status, and then retry.

Revise the host specification.


Revise the host type specification.






Error Code

KAIC07425-E

KAIC07426-E

KAIC07433-E

KAIC07434-E

KAIC07435-E

KAIC07436-E

KAIC07440-E

KAIC07441-E

KAIC07450-E

KAIC07452-E

KAIC07453-E

KAIC07454-E

KAIC07456-E

Description

The host "host-name-or-

objectID" is specified more than once.

The same host is specified for the target and source hosts.

A host that is not a virtualization server was detected for the specified IP address (IP-address).

The AddHostRefresh command cannot be executed for virtualization servers in this

API version.

The information regarding the specified virtualization server is inconsistent. Refresh the virtualization server, and then retry the operation.

The specified virtualization server is currently being refreshed. Wait a while, and then retry the operation.

An internal server error was encountered. An attempt to create the replication information has failed.

An internal server error was encountered. The LogicalUnit that the host agent specifies was not found in the database.

An internal server error was encountered. An attempt to acquire LogicalUnit information that is P-VOL or

S-VOL has failed.

An internal server error was encountered. An attempt to acquire information to access the host agent has failed.

An internal server error was encountered. An error occurred during the search for host agent(s) that will be accessed. Port "port-number" does not exist.


An attempt to operate "open-

or-close" on host agent server

"URL-of-host-agent" has failed. The response from the host agent was "response-

from-host-agent".




Revise the host specification, and then try again.

Use a version of the API that supports the command.

Refresh the virtualization server, and then retry the operation.

Wait a while, and then retry the operation.


Perform a refresh on subsystem ("array-type",

"serial-number") or check the status of host agent.



Confirm the status of host agent. If there are no problems with the host agent, contact the

Support Center.



1-77

1-78

Error Code

KAIC07457-E

KAIC07458-E

KAIC07459-E

KAIC07460-E

KAIC07461-E

KAIC07462-E

KAIC07470-E

KAIC07471-E

KAIC07472-E

KAIC07473-E

KAIC07474-E

KAIC07475-E

Description

An error occurred during communicating with the host agent "URL-of-host-agent".


Check the host agent and the status of the network connection between Device Manager

Server and host agent. If this problem persists, contact the Support Center.

Contact the Support Center. An internal server error was encountered. An attempt to create a request to the host agent has failed. The POST request of HTTP cannot be performed.

An attempt to resolve the IP address of host agent Server has failed.

The accessed host "host-

name" is different from the host "host-name" registered in

Device Manager.

An attempt to execute a request for the host agent has failed. (error details = "error-

message")

The version of the host agent on host "host-name" is

"installed-version-host-agent".

However, version "required-

version" or later of the host agent is required to execute the service.

An attempt to execute the request has failed. Execute the request again.

An attempt to update the information for the displayed list has failed.

The storage subsystem information ("Subsystem-

name") is inconsistent.

Refresh the subsystem, and then try again.

The storage subsystem information ("Subsystem-

name") is being updated. Wait a while, and then perform the operation again.

The value of the "attribute-

name" parameter is outside the valid range from

"minimum-value" to

"maximum-value".

The sum of startElementNum and numOfElements is outside the valid range from


"maximum-value".

Check that the IP address of host agent is valid.

Check that the host name and the IP address of the host agent in Device Manager are valid.

Check the host agent and the status of the network connection between Device Manager

Server and host agent. If this problem persists, contact the Support Center.

Check the host agent on the host.


Center.


Wait a while, and then perform the operation again.




Error Code

KAIC07476-E

KAIC07477-E

KAIC07478-E

KAIC07479-E

KAIC07480-E

KAIC07481-E

KAIC07482-E

KAIC07483-E

Description

The "attribute-name" parameter is missing in the requested "element-name" element.

Memory for the Device

Manager server became insufficient while this operation was being performed.


Check whether the requested element has all the necessary parameters. If there are any missing parameters, specify them and then re-execute the command.

If the command you executed is Add, Modify, or Delete, take the following action:

(1) Use the following procedure to check the status of the operation:

1. Increase the memory heap size for the

Device Manager server.

2. If the command was executed for a storage subsystem or host, refresh the information of the storage subsystem or host.

3. Check the status of the operation.

(2) If necessary, perform the operation again.

If the command you executed is Get, take the following action:

(1) Use the following procedure to perform the operation again:

1. Restart the Device Manager server.

2. Do either of the following:

- Increase the memory heap size for the

Device Manager server, and then perform the operation again.

- Reduce the amount of information to be collected, and then perform the operation again.

Contact the Support Center. An internal error occurred while registering a temporary user for the storage subsystem.

The value of Over Provisioning

Percent Alert Notice is outside the valid range from


"maximum-value".

ISCSINames cannot be added to a mainframe host.


"ISCSIName" is invalid because it exceeds the maximum length maximum-

length-of-ISCSIName bytes.


"ISCSIName" is invalid because it contains an invalid character.

The portWWN and portISCSIName parameters are both specified in the request.



Revise the specified ISCSIName, and then retry the operation.

Specify either the portWWN or the portISCSIName parameter, but not both.



1-79

1-80

Error Code

KAIC07484-E

KAIC07485-E

KAIC07486-E

KAIC07487-E

KAIC07488-E

KAIC07489-E

KAIC07490-E

KAIC07491-E

KAIC07492-E

KAIC07493-E

KAIC07494-E

KAIC07496-E

KAIC07497-E

KAIC07498-E

Description

ISCSINames cannot be specified for this

HostStorageDomain because the port to which this

HostStorageDomain belongs is a Fibre Channel port.

The specified ISCSIName is invalid.

WorldWideNames cannot be specified for this

HostStorageDomain because the port to which this

HostStorageDomain belongs is an iSCSI port.

The specified domain type

"domain-type" is invalid.

ISCSINames are invalid on this storage subsystem.

The following parameter is not specified: ISCSIName

"iSCSIName".

The ISCSIName "ISCSIName" does not exist in the Device

Manager database.


"ISCSIName" cannot be used because it is already being used for another ISCSIName on the same

HostStorageDomain.

The Fibre Channel port attribute and the iSCSI port attribute cannot be specified at the same time.

The iSCSI port attribute cannot be specified for a Fibre

Channel port.

The Fibre Channel port attribute cannot be specified for an iSCSI port.

The ISCSIName of the specified host "host-name" cannot be changed because the host is on an external port.


"nickname" is invalid for the specified ISCSIName

"ISCSIName".

The ISCSIName "ISCSIName" is already being used by the host "host-name".


Specify a HostStorageDomain that belongs to an iSCSI port, and then retry the operation.


Specify a HostStorageDomain that belongs to a Fibre Channel port, and then retry the operation.

Revise the domain type specification.

Revise the storage subsystem specification.

Specify the ISCSIName, and then retry the operation.


Specify an ISCSIName that is not already being used on the same HostStorageDomain, and then retry the operation.




Revise the ISCSIName specification.



Error Code

KAIC07499-E

Description

The host "host-name" cannot be deleted because it includes an ISCSIName used for an

LUN.


Delete the LUN security, and then delete the host.



1-81

1-82

Error Code

KAIC07501-E

KAIC07502-E

KAIC07503-E

KAIC07504-E

KAIC07505-E

KAIC07506-E

KAIC07507-E

KAIC07510-E

KAIC07511-E

KAIC07512-E

KAIC07513-E

KAIC07514-E

KAIC07515-E

Description

An error occurred while the fabric information was being acquired.

An error occurred while the fabric information was being acquired.

Only one instance of this command can be executed at one time.

The LUN Management option of the specified storage subsystem is not enabled.

The host information in the

Device Manager database has been updated. Other update processing might have been executed while Host Scan was executing.

Host Scan was not executed because no target storage subsystem was found.

The host information in the

Device Manager database has been updated. Other update processing might have been executed while hosts were being merged.

The configuration of purchasable optional features on the storage subsystem might have changed.

No more users can be registered because the maximum number of users has already been registered in the specified storage subsystem.

A user ID that is the same as the temporary user ID is already registered in the storage subsystem.

The element-name (attribute-

name="attribute-value") is specified more than once.

The poolID "poolID" is already being used in the subsystem.

The element-name (attribute-

name="attribute-value") was not found in the Device

Manager database.



Wait a while, and then try again.

Check the option list of the storage subsystem.

Make sure that other update processing is not executing, and then retry Host Scan. If this problem persists, contact the Support Center.


Make sure that no other update processing is being executed, and then try to merge the hosts again. If this problem persists, contact the Support Center.


Delete unnecessary users from the storage subsystem, and then retry the operation.

Delete the already registered user ID from the storage subsystem, and then retry the operation.

Revise the element-name specification.

Revise the poolID specification, and then retry the operation.

Revise the element-name specification.



Error Code

KAIC07516-E

KAIC07517-E

KAIC07518-E

KAIC07519-E

KAIC07520-E

KAIC07521-E

KAIC07522-E

KAIC07523-E

KAIC07524-E

KAIC07525-E

KAIC07526-E

KAIC07527-E

KAIC07528-E


The specified operation cannot be executed because the value of the attribute attribute-name

(attribute-value) is the value of the attribute attribute-name

(attribute-value) or more.

The element-name specification is invalid. The drive types of all element-

names in one pool must be the same.

The specified operation cannot be executed because the status of the element-name

(attribute-name="attribute-

value") is status.

The capacity "capacity" is invalid. Specify a value from

minimum-value to maximum-

value.

The specified operation cannot be executed for an array group that consists of PP-

Name pool.

The RAID level "RAID-level" cannot be specified for this operation.

The combination of RAID level and the number of PDEVs is invalid.

The selected number of PDEVs does not match the pool combination (function="PP-

name", poolID = "poolID").

The command option "option-

name" has not been specified.

The specified command option

"option-name" is invalid.

Revise the attribute-name and attribute-name specifications, and then retry the operation.

Revise the element-name specification, and then retry the operation.

Recover the status of element-name, and then retry the operation.

Revise the capacity specification, and then retry the operation.

Revise the array group specification.

Revise the RAID level specification, and then retry the operation.

Revise the RAID level and the number of

PDEVs, and then retry the operation.

Revise the PDEV specification, and then retry the operation.

Specify the command option "option-name".

Check and, if necessary, specify a different command option, and then retry the operation.

Check and, if necessary, specify a different capacity, and then retry the operation.

The specified capacity of

element-name (attribute-

name="attribute-value") is invalid. Specify the capacity more than the current capacity.

The specified operation cannot be executed because the pool

(poolID="pool-ID") is blocked.

"option-name" has not been specified for command option

2.

Unblock the pool, and then retry the operation.

Specify "option-name" for command option 2.



1-83

1-84

Error Code

KAIC07529-E

KAIC07530-E

KAIC07531-E

KAIC07532-E

KAIC07533-E

KAIC07534-E

KAIC07550-E

KAIC07551-E

KAIC07552-E

KAIC07553-E

KAIC07554-E

KAIC07555-E


The specified operation cannot be executed because status in pool (poolID="pool-ID") is not

"Normal".

The Over Provisioning Warning

Threshold is outside the valid range. The valid range is from


value.

The Over Provisioning Limit

Threshold is outside the valid range. The valid range is from


value.

The Over Provisioning Percent of the specified pool "pool-ID" has already exceeded the

Over Provisioning Limit

Threshold.

Upon executing this command, the Over

Provisioning Percent of the specified pool "pool-ID" will exceed the Over Provisioning

Limit Threshold.

The specified operation cannot be executed because the Over

Provisioning Warning

Threshold (attribute-value) is greater than or equal to the

Over Provisioning Limit

Threshold (attribute-value).

The specified IPAddress

"IPAddress" cannot be used because it is already being used by another port.

The format of the specified

IPAddress "IPAddress" is invalid.


SubnetMask "SubnetMask" is invalid.


DefaultGateway

"DefaultGateway" is invalid.

The PortNumber specified for the port is invalid.

The keepAliveTime specified for the port is invalid.

Recover from the pool status, and then retry the operation.

Revise the Over Provisioning Warning

Threshold, and then try again.

Revise the Over Provisioning Limit Threshold, and then try again.

Revise the pool specification, and then retry the operation.

Revise the size and number of virtual volumes that will be created or changed, and then retry the operation.

Revise the Over Provisioning Warning

Threshold and the Over Provisioning Limit

Threshold, and then try again.

Specify an IPAddress that is not being used by another port, and then retry the operation.

Specify the IPAddress by using a valid format.

Specify the SubnetMask by using a valid format.

Specify the DefaultGateway by using a valid format.

Specify a valid PortNumber.

Specify a valid keepAliveTime.



Error Code

KAIC07556-E

KAIC07557-E

KAIC07558-E

KAIC07559-E

KAIC07560-E

KAIC07561-E

Description


"ISCSIName" cannot be used because it is already being used by another

HostStorageDomain on the same port.


ISCSINames ("maximum-

number-of-ISCSINames") has been exceeded.


"nickname" cannot be used because it is already being used by another ISCSIName on the same port.

Device Manager does not support operations on this storage subsystem. The minimum microcode version is

"version".

The iSCSI attribute cannot be specified for the Fibre Channel

HostInfo.

The Fibre Channel attribute cannot be specified for the iSCSI HostInfo.


Specify an ISCSIName that is not being used by another HostStorageDomains on the same port, and then retry the operation.

No more ISCSINames can be added to the specified port. Delete any unnecessary

ISCSINames, and then retry the operation.

Specify a nickname that is not being used by another ISCSIName on the same port, and then retry the operation.

To perform this operation, the microcode version must be updated.




1-85

1-86

Error Code

KAIC07570-E

KAIC07571-E

KAIC07572-E

KAIC07573-E

KAIC07574-E

KAIC07575-E

KAIC07577-E

KAIC07578-E

KAIC07579-E

KAIC07581-E

KAIC07582-E

KAIC07583-E

KAIC07584-E

KAIC07585-E


The LU "device number" cannot be used for a pool volume because it is an

OnDemand device.

The drive type of all LUs that make up the specified pool must be same.

A pool cannot be deleted because one or more V-VOLs exist.

The pool volumes of specified pool cannot be deleted.

A journal group cannot be changed or deleted, because it is used by Universal Replicator for Mainframe.

The specified LU is not a volume of the specified journal group.

"Data Overflow Watch Time" could not be set, because the value for Inflow Control is

"No".

The combination of values specified for "Path Watch

Time" and "Unit of Path Watch

Time" is invalid.

A journal volume cannot be deleted when the delta of the master journal group is

"Hold".

The LU "device number" cannot be used as a pool volume/journal volume because the I/O suppression mode is active.

The LU "device number" cannot be used as a pool volume/journal volume because it is a system volume.

Journal volumes cannot be emptied during journal volume deletion.

The specified journal group ID

"journal group ID" is already used on the storage subsystem by PP Name

(Universal Replicator).

Operations cannot be performed for the specified journal group because it does not have any volumes.


Revise the drive types of pool volumes, and then try again.

Delete all V-VOLs used by the specified pool, and then try again.

Check the subsystem functionality.

Specify a journal group that is not used by

Universal Replicator for Mainframe, and then try again.


Revise the journal group options, and then try again.

Revise the values of "Unit of Path Watch Time" and "Path Watch Time", and then try again.




Revise the LU specification, and then retry the operation.

Revise the journal group ID specification, and then try again.

Revise the journal group ID specification, and then try again.



Error Code

KAIC07586-E

KAIC07588-E

KAIC07589-E

KAIC07590-E

KAIC07591-E

KAIC07592-E

KAIC07593-E

KAIC07595-E

KAIC07596-E

KAIC07600-E

KAIC07601-E

Description

The specified pool ID "poolID" is an invalid value. The pool

ID must be "value 1" or "value

2".

When modifying a journal group, either a journal group option or an LU to be modified must be specified.

The specified pool/journal group cannot be added in this

API version.

The specified pool/journal group cannot be deleted in this API version.

The specified pool/journal group cannot be modified in this API version.

A parameter is invalid. If you specify "Path Watch Time" or

"Unit of Path Watch Time", you must specify both of them at the same time.

The specified pool is invalid.

An attempt to execute the request has failed. The emulation types of the specified volumes are a combination of "emulation

type1" and "emulation type2".

The storage subsystem information ("subsystem-

name") is incomplete. Refresh the subsystem, and then try again.

The "microcode-version" microcode version of the storage subsystem cannot be used for the "PP Name

(Dynamic Provisioning)" configuration.

Device Manager does not support the "operation" operation except for the "PP

Name (Dynamic Provisioning)" function. again.

Revise the function type, and then retry the operation.


Revise the pool ID specification, and then try


Make sure that the operation is supported in the specified API version.



Specify both "Path Watch Time" and "Unit of

Path Watch Time".

Revise the pool ID specification, and then try again.

For the source and target volumes, specify volumes that have the same emulation type.


Make sure the microcode version of the storage subsystem is correct.



1-87

1-88

Error Code

KAIC07602-E

KAIC07603-E

KAIC07604-E

KAIC07605-E

KAIC07606-E

KAIC07607-E

KAIC07608-E

KAIC07609-E

KAIC07610-E

KAIC07611-E


The LU cannot be used for a pool volume because the capacity of the LU "device-

number" is outside the valid range. The capacity of a pool volume must be "minimum-

value(KB)KB(minimum-

value(LBA)LBA)" or more.

The LU "device-number" cannot be used for a pool volume/journal volume because the LU is a LUSE devise.

The LU "device-number" cannot be used for a pool volume/journal volume because the LU has a path set.

The LU "device-number" cannot be used for a pool volume/journal volume because it is a reserved volume of "PP Name (Volume

Migration)".

The LU "device-number" cannot be used for a pool volume/journal volume because it is a "volume-

attribute" of "PP Name".

The LDEV "device-number" cannot be used for a pool volume/journal volume because its status is not

"Normal".

The LDEV "device-number" cannot be used for a pool volume/journal volume because it is protected.

All LDEVs that make up a pool/journal group for "PP

Name (Dynamic Provisioning)" must have the same CLPR.

LU "device-number", whose emulation type is "emulationtype", cannot be used for a pool volume/journal volume of

"PP Name (Dynamic

Provisioning)".

The LU "device-number" cannot be used for a pool volume/journal volume because it is a command devise.


Check the status of the LDEV, and then retry the operation.




Error Code

KAIC07612-E

KAIC07613-E

KAIC07614-E

KAIC07615-E

KAIC07616-E

KAIC07618-E

KAIC07620-E

KAIC07621-E

KAIC07622-E

KAIC07623-E

KAIC07624-E

KAIC07625-E

Description

The LU "device-number" cannot be used for a pool volume/journal volume because it is set for "PP Name

(Cache Residency)".

The pool volume/journal volume cannot be added because the number of LUs will exceed the maximum number of pool volume/journal volume that make up a pool for "PP Name

(Dynamic Provisioning)".

The specified threshold

"threshold" is invalid.

The specified pool ID "poolID" is already being used on the storage subsystem, for "PP

Name (Quick Shadow)" or "PP

Name (Dynamic

Provisioning)".

The specified poolID/journal group ID "pool ID/journal

group ID" is invalid. A pool ID

/journal group ID must be in the range from "minimum-

value" to "maximum-value".

The specified pool cannot be deleted because an LU is assigned to it.

The LU "device-number" is already assigned to a pool.

"volume-attribute" and the pool must have the same

CLPR.

An attempt to execute the request failed because the LU

"device-number" is unassigned to pool.

The LU "device-number" cannot be released from the pool because the LU has a path.

The LU "device-number" cannot be released from the pool because the LU is a LUSE volume.

The array group

(chassis="chassis" number="array-group-

number") already exists in the storage subsystem.



Reduce the number of specified LUs, and then retry the operation.

Specify a valid value, and then retry the operation.

Revise the pool ID specification, and then retry the operation.

Revise the pool ID/journal group ID specification, and then retry the operation.

Remove any assigned LUs from the pool, and then retry.


Revise the pool and volume combination, and then retry the operation.


Release any paths for the LU, and then retry the operation.

Release the LUSE, and then retry the operation.




1-89

1-90

Error Code

KAIC07626-E

KAIC07627-E

KAIC07629-E

KAIC07630-E

KAIC07631-E

KAIC07632-E

KAIC07633-E

KAIC07634-E

KAIC07635-E

KAIC07636-E

KAIC07637-E

KAIC07638-E

KAIC07639-E



"device-number" is already in use.

The LDEV cannot be added, because the number of LDEVs will exceed the maximum number of LDEVs in the array group.

An LU whose emulation type is

"emulation-type" cannot be added to "PP Name (Dynamic

Provisioning)".

The specified array group was not found in the Device

Manager database.



number") cannot be deleted because it contains at least one LDEV that is assigned to a pool.



number") cannot be deleted because it contains at least one LU that has a path.



number") cannot be deleted because it contains a LUSE volume.



number") cannot be deleted because it contains at least one protected LDEV.


"device-number" is invalid.

The LU "device-number" cannot be deleted because it is assigned to a pool.

The LU "device-number" cannot be deleted because it has a path.

The LU "device-number" cannot be deleted because it is a LUSE volume.

The LU "device-number" cannot be deleted because it is protected.

Revise the device number specification, and then retry the operation.

Reduce the number of specified volumes, and then retry the operation.

Correct the specified emulation type, and then retry the operation.

Revise the array group specification, and then retry the operation.

Specify the option "force", and then retry the operation.

Release the paths set for the LU, and then retry the operation.



Specify another device number, and then retry the operation.

Specify the option "force", and then retry the operation.

Release the paths set for the LU, and then retry the operation.





Error Code

KAIC07640-E

KAIC07641-E

KAIC07642-E

KAIC07643-E

KAIC07644-E

KAIC07647-E

KAIC07648-E

KAIC07649-E

KAIC07650-E

KAIC07651-E

KAIC07700-E

KAIC07701-E

KAIC07702-E

KAIC07703-E

Description

A parameter is not specified :

LU "emulation"


LU "dpPoolID"


LU "threshold"

All LUs that make up a pool for "PP Name (Dynamic

Provisioning)" must have the same volume classes (internal or external).

All LUs that make up a pool for "PP Name (Dynamic

Provisioning)" must have the same cache mode.

The objectID of the array group is not specified. If you specify "exist" option, you must also specify the objectID of the array group.



number") is not used for "PP

Name (Dynamic

Provisioning)".

Specified LU

(devNum="device-number") is not "volume-attribute" of "PP

Name".

An error occurred in

Provisioning Manager Server.

(Message ID:Message-ID)

An error occurred when

Provisioning Manager Server was invoked.

In the "operation" operation, an array group and LU cannot be specified at the same time.

"option-name" cannot be specified for command option

2.

The value specified for

"option-name" of command option 2 is invalid.

The array group


number") have been specified more than once.


Specify the LU emulation type.

Specify the pool ID.

Specify the LU threshold.


Specify the objectID of the array group, and then retry the operation.

Specify an array group that is used for "PP

Name (Dynamic Provisioning)".

Specify volume-attribute of PP Name.

Refer to the Provisioning Manager Server log.

Specify either an array group or an LU, and then retry the operation.





1-91

1-92

Error Code

KAIC07704-E

KAIC07705-E

KAIC07706-E

KAIC07707-E

KAIC07708-E

KAIC07709-E

KAIC07710-E

KAIC07711-E

KAIC07712-E

KAIC07713-E

KAIC07714-E

KAIC07715-E

KAIC07716-E


The specified pool

(function="PP Name (Dynamic

Provisioning)" pool

ID="poolID") was not found in the Device Manager database.


ArrayGroup "chassis" or

"number".

In the specified request, the

"chassis" and "number" attributes of the ArrayGroup element cannot be specified.

In the specified request, the number of requested

ArrayGroup element must be one.

All "dpPoolID" attributes of

LogicalUnit element must have the same value.

The number of elements specified in the request is invalid. In the specified request, one child element

"child-element-name" must be specified for the "parent-

element-name" element.

A required element is missing from the request. "element-

name" or "element-name"

The array group


number") was not found in the storage subysystem.

The device number "device-

number" is specified more than once.

The drive types of all LDEVs that make up a single pool of

"PP Name (Dynamic

Provisioning)" must match.

A element "element-name" or attribute "attribute-name" is missing from the request.

The request contains both the capacityInKB parameter of the logical unit and the lba parameter of the LDEV.

An attempt to execute a request has failed. If option

"option-name" is specified, the

element-name element cannot be specified.

Revise the pool specification, and then retry the operation.

Specify both "chassis" and "number" for

ArrayGroup.


Revise the number of elements in the request, and then retry the operation.

Revise the specification of the elements in the request.

Revise the specification of the array group and storage subsystem.

Revise the device number specification.

Revise the specification of the LUs, and then retry the operation.


Specify either the capacityInKB parameter of the logical unit or the lba parameter of the

LDEV, but not both.




Error Code

KAIC07717-E

KAIC07720-E

KAIC07721-E

KAIC07722-E

KAIC07723-E

KAIC07724-E

KAIC07725-E

KAIC07726-E

KAIC07727-E

KAIC07728-E

KAIC07729-E


An attempt to execute a request has failed. If option

"option-name" is specified, the

attribute-name attribute in a

element-name element cannot be specified.

An attempt to create a

TrueCopy pair has failed. The

LDEV "LUSE" is a LUSE device.

The number of LDEVs in the

LUSE must be less than "max-

number-of-LDEVs-in-LUSE".


TrueCopy pair has failed. The


The RAID type and the number of data disks must be identical for all LDEVs in the

LUSE.


TrueCopy pair has failed. To create a TrueCopy pair using the V-VOL of a QuickShadow pair, the QuickShadow pair must be created beforehand.

An attempt to create a "pair-

name" pair has failed. The


The number of LDEVs in the

LUSE must be less than "max-

number-of-LDEVs-in-LUSE".


TrueCopy Async pair has failed because the size of the LDEV that makes up the LUSE was smaller than 1 GB.

In this API version, the

TrueCopyAsync pair operation for the specified storage subsystem is not supported.

The data pool for the specified storage subsystem is not in the same default controller as the LU that will make up the pair.


TrueCopy Async pair has failed because the default controller of the LU to be defined in S-

VOL was not the same as the current controller.

Error occurred while parsing response from host agent.

An error occurred while encoding the message.


Make sure that the request is valid, and then retry.

Check the size of the LDEV that makes up the

LUSE.

Check the API versions supported by this storage subsystem.

Create a data pool, and then try again.

Check the default controller and a current controller of the LU.




1-93

1-94

Error Code

KAIC07730-E

KAIC07731-E

KAIC07734-E

KAIC07735-E

KAIC07736-E

KAIC07737-E

KAIC07738-E

KAIC07739-E

KAIC07740-E

KAIC07741-E

KAIC07742-E


If you used Disk Array

Management Program or

Storage Navigator Modular to create an expanded LU from two or more volumes assign to an LUN, the expanded LU cannot be deleted.

Creation of an LDEV in the specified array group is not supported.

Invalid information was sent from host agent. Serial number of the subsystem that has the replication volume was not specified.

An attempt to get the information of the pair configuration on host "host-

name" has failed. Error detail :

"error-detail".

The configuration file specified by instance number "instance-

number" already exists on the host "host-name".


number" on Host "host-name" is not managed by Device

Manager.


number" on Host "host-name" does not exist on the host

"host-name".

The specified group "group-

name" exists in the configuration file (instance number "instance-number" on host "host-name").

This API version does not support the LUN Management option.

A value for the attribute

"priority" is not specified for all "ExternalPathInfo" elements.

The same value has been specified for the attribute

"priority" in multiple

"ExternalPathInfo" elements.

Use Disk Array Management Program or

Storage Navigator Modular to delete the LUN that cannot be used, and then use Device

Manager to refresh the subsystem.




Center.

Specify another instance number, and then retry.

Specify another group name, and then retry.

Check this subsystem's option list. You can also check the Device Manager Server XML

API manual and make sure that the running

API version supports the command.

Specify a value for the attribute "priority" either for all "ExternalPathInfo" elements or for no "ExternalPathInfo" elements.

Specify different values for the attribute

"priority" in multiple "ExternalPathInfo" elements.



Error Code

KAIC07743-E

KAIC07750-E

KAIC07751-E

KAIC07752-E

KAIC07753-E

KAIC07754-E

KAIC07755-E

KAIC07756-E

KAIC07757-E

KAIC07758-E


The value specified for the attribute "priority" in the element "ExternalPathInfo" differs from that specified for the specified path group.

The specified device name

"device-name" exists in the configuration file (instance number "instance-number" on host "host-name").

The specified group "group-

name" does not exist in the configuration file (instance number "instance-number" on host "host-name").

The host agent (URL = "url-of-

host-agent") does not support the "function-name" function.

An error occurred during a pair operation.

An attempt to delete the information for a pair configuration (instance number "instance-number" on host "host-name" and instance number "instance-number" on host "host-name") has failed.

Error detail, host "host-name"

: "error-detail"

An attempt to create a pair has failed. The specified pair configuration may remain in the configuration file (instance number "instance-number" on host "host-name" and instance number "instance-number" on host "host-name"). Error details: "error-detail"

An error occurred during processing of the service by the host agent. Host agent

Error Message : "host-agent-

message" Command Error

Message : "command-error-

message"

An error was detected in the host agent. Details: "error-

detail"

The specified configuration file with instance number is

"instance-number" does not exist on host "host-name".

For the attribute "priority", specify the same value as the attribute "priority" set for the specified path group.



Use a host agent of version "necessary-

version" or later.


Center.

Check that the configuration file exists on the host "host-name", and then retry.



1-95

1-96

Error Code

KAIC07759-E

KAIC07760-E

KAIC07761-E

KAIC07762-E

KAIC07763-E

KAIC07764-E

KAIC07765-E

KAIC07766-E

KAIC07767-E

KAIC07768-E

KAIC07769-E

KAIC07770-E


The specified configuration file

(instance number "instance-

number" on host "host-name") is not valid. The configuration file is changed, or, the specification of Command

Device is invalid.

The content of the specified configuration file (instance number "instance-number") is not the same as that on the host "host-name".

The specified device name does not exist in the configuration file (instance number "instance-number" on host "host-name").

An attempt to delete a pair has failed. Error detail, host

"host-name" : "error-detail".

Device Manager Server timed out.

An internal server error occurred, because the parameter "parameter" was not specified.

An attempt to create a pair has failed. The specified pair configurations may remain in the configuration files


number" on host "host-name" and instance number

"instance-number" on host

"host-name").

An attempt to start a HORCM instance (instance number

"instance-number") on host

"host-name" failed.

Some pairs may be not deleted.

An attempt to restart the

HORCM instance (instance number "instance-number" on host "host-name") has failed.

Error detail: "error-detail"

An internal server error occurred. An attempt to execute a service for the host agent has failed.

An attempt to shut down the

HORCM instance (instance number "instance-number" on host "host-name") has failed.

Error detail: "error-detail"

Check the configuration file (instance number

"instance-number" on host "host-name"), and correct it if necessary.

Perform a refresh.


Center.



Center.

Contact the administrator of the host, and then restart the HORCM instance on the host.


Center.



Error Code

KAIC07771-E

KAIC07772-E

KAIC07773-E

KAIC07774-E

KAIC07775-E

KAIC07776-E

KAIC07777-E

KAIC07778-E

KAIC07779-E


An attempt to get the result of

"operation" has failed.

An internal server error occurred. An attempt to create a request for the host agent was failed.

An attempt to create a pair has failed. Error details, host

"host-name1" : "error-detail", host "host-name2" : "error-

detail"

An attempt to create a pair has failed. Error detail, host

"host-name" : "error-detail"

An attempt to create a pair has failed. The specified pair configurations may remain in the configuration files


number" on host "host-

name1" and instance number

"instance-number" on host

"host-name2"). Error details, host "host-name1" : "error-

detail", host "host-name2" :

"error-detail"

An attempt to create a pair has failed. The specified pair configurations may remain in the configuration file (instance number "instance-number" on host "host-name"). Error details of Host "host-name" :

"error-detail"

An attempt to create a pair has failed. The specified pair configurations may remain in the configuration file (instance number "instance-number" on host "host-name1"). Error details, Host "host-name1" :

"error-detail", Host "host-

name2" : "error-detail"

An attempt to execute a request has failed. The host agent returned an invalid response.

An attempt to delete the configuration file (instance number "instance-number" on host"host-name") has failed.

Error detail : "error-detail"


Center.



1-97

1-98

Error Code

KAIC07780-E

KAIC07781-E

KAIC07782-E

KAIC07783-E

KAIC07784-E

KAIC07785-E

KAIC07786-E

KAIC07787-E

KAIC07788-E

KAIC07789-E

KAIC07790-E


An attempt to delete a pair has failed. Error details, host


detail"

An attempt to delete information for a pair configuration (instance number "instance-number" on host "host-name1" and instance number "instance-

number" on host "host-

name2") has failed. Error details, host "host-name1" :

"error-detail", host "host-

name2" : "error-detail"

An attempt to delete information for a pair configuration (instance number "instance-number" on host "host-name") was failed.

Error details : "error-detail".

An attempt to modify a pair has failed. Error details, host

"host-name" : "error-detail".

An attempt to modify a pair has failed. Error details, host


detail".

An attempt to restart a

HORCM instance (instance number "instance-number") on host "host-name" failed.

An internal error occurred in host agent ("agent-url").

The host agent (host-name

"host-name") cannot support the "function-name" function.

Use "PP on Host" of version

"necessary-version" or later on this host.

Device Manager Server cannot operate the host agent service

"operation".

An error occurred during processing of the service by the host agent. (error message from the host agent

= "error-message-from-host-

agent")

An attempt to get volume information on host "host-

name" has failed. Error detail :

"error-detail".

Check the configuration file, and then correct it if necessary.


Center.

Check the host agent environment.


Center.

Check the host agent status. If this problem persists, contact the Support Center.



Error Code

KAIC07791-E

KAIC07792-E

KAIC07793-E

KAIC07794-E

KAIC07795-E

KAIC07796-E

KAIC07797-E

KAIC07798-E

KAIC07799-E

KAIC07800-E

KAIC07801-E

Description

An attempt to get program product information on host

"host-name" has failed. Error detail: "error-detail".

An attempt to acquire pair volume information on the host "host-name" has failed.

Error details: "error-detail".

An attempt to execute the request has failed. The specified LU "device-number" is being used by PP Name

(UniversalReplicator).

Creation, modification, or deletion of UniversalReplicator or Continuous Access XP

Journal pairs is not supported.


(devNum = "Device number") used by PP Name

(UniversalReplicator) cannot be deleted.

An attempt to execute the request has failed. The specified LU "device-number" is being used as a journal volume.

LDEV of device number

"device-number" cannot be used to make up a LUSE because the device number is smaller than the maximum device number of the LDEVs that make up the first specified LUSE.

The microcode version of the storage array is insufficient for the requested an LUSE operation using a path defined

LDEV. The microcode version is "microcode-version"

An attempt to execute the request has failed. The specified LU "device-number" is being used as a system disk.

There are too many elements in the request. The maximum number of "element-name-in-

XML-API" elements which can be specified is "maximum-

number-of-elements".

A required element is missing from the request. Specify

"element-name" elements.


Center.


Revise the LU specifications, and then try again.




To create a LUSE based on a LUSE that has already been configured, specify an LDEV with a device number larger than the maximum device number of the LDEVs that make up the first LUSE.




Check that all of the required elements of a request are present. Provide the missing element, and then retry.



1-99

1-100

Error Code

KAIC07802-E

KAIC07803-E

KAIC07804-E

KAIC07805-E

KAIC07806-E

KAIC07807-E

KAIC07808-E

KAIC07809-E


The number of elements specified in the request is insufficient. To execute this command, "minimum-

number-of-elements" or more

"element-name" elements are required.

Missing parameter: "element-

name" "attribute-name-of-

element".

A parameter is invalid. The same object is specified for at least two "Path" elements in the request.

Some parameters are incorrect. The same WWN

"WWN

(xx.xx.xx.xx.xx.xx.xx.xx)" is specified for two or more

"WorldWideName" elements in the request.

The command cannot be executed because the security switch for the specified port

"port-name" is OFF. To execute this command, the security switch for the port must be ON.

An LUN group cannot be created because there are no paths on the specified port

"port-name". To create an

LUN group, there must be at least one path on the port at the creation destination.

The command cannot be executed because executing it will cause the number of LUN groups on the specified port

"port-name" to exceed the maximum number of LUN groups "maximum-number-of-

LUN-groups-that-can-be-

created-on-a-port" that can be created on a port.

The command cannot be executed because executing it will cause the number of WWN groups on the specified port

"port-name" to exceed the maximum number of WWN groups "maximum-number-of-

WWN-groups-that-can-be-

created-on-a-port" that can be created on a port.

Check the number of elements, then retry.

Specify the required parameter, and then retry.

Revise the specifications for the object of the path element, and then retry.

Check the WWN specifications of the

WorldWideName elements, and then retry.

Turn the security switch ON for the specified port, and then retry.

Create at least one path on the specified port, and then retry.

Revise the specifications for the ports and LUN groups so they do not exceed the maximum number, and then retry.

Revise the specifications for the ports and

WWN groups so they do not exceed the maximum number, and then retry.



Error Code

KAIC07810-E

KAIC07811-E

KAIC07812-E

KAIC07813-E

KAIC07814-E

KAIC07815-E

KAIC07816-E

KAIC07817-E

KAIC07818-E

KAIC07819-E

KAIC07820-E



"nickname" is invalid, since the maximum length for a nickname is "maximum-

length-of-nickname" bytes.


"nickname" is invalid, since it contains a forbidden character.


"nickname" is not available.

This nickname is already used by the other LUNGroup on the same port.



This nickname is already used by another WWN/WWNGroup on the same port.

The specified path cannot be used because it belongs to another LUN group on the same port.

The specified WWN "WWN" is not available. This WWN already belongs to the other

WWNGroup on the same port.

It is not possible to group paths that have different WWN securities each other. Paths that have same WWN securities or no WWN security must be specified.

It is not possible to group

WWNs used by different paths. WWNs that are used by the same path(s), or are not used, must be specified.

The specified path is not a path on the port "port-name".

A path that is on the specified port must be specified.

The specified WWN is a member of WWNGroup. In order to perform secure/unsecure by

WWNGroup, specify all WWNs that are members of the

WWNGroup.

The specified

HostStorageDomain includes a path belonging to an

LUNGroup. This command does not support secure/unsecure with paths belonging to an LUNGroup.

Check the nickname, and then retry.

Specify a nickname that is not used by other

LUNGroups on the same port, and then retry.


WWN/WWNGroups on the same port, and then retry.

Specify a path that does not belong to another

LUN group on the same port, and then retry.

Specify the WWN which does not belong to other WWNGroups on the same port, and then retry.

Check the specification of paths, and then retry.

Check the specification of WWNs, and then retry.

Revise the relationship between the specified port and path, and then retry.

Specify all members of the WWNGroup or specify WWN that does not belong to the

WWNGroup, and then retry.

Check that there is no path belonging to the

LUNGroup in the HostStorageDomain to specify, and then retry.



1-101

1-102

Error Code

KAIC07821-E

KAIC07822-E

KAIC07823-E

KAIC07824-E

KAIC07825-E

KAIC07826-E

KAIC07827-E

KAIC07828-E

KAIC07829-E

KAIC07830-E


This operation for the WWN comprising a WWNGroup is not supported by the specified

API version.

The specified WWN "WWN" is not available. This WWN already belongs to

HostStorageDomain

"HostStorageDomain" on the same port.

A non-representative LDEV

(devNum = "Device number") that is making up a LUSE was specified. A LUSE cannot be created by specifying a nonrepresentative LDEV.

A non-representative LDEV

(devNum = "Device number") that is making up a LUSE was specified. A path cannot be set to a non-representative LDEV.



This nickname is already used by another

WWN/HostStorageDomain on the same port.



This nickname is already used by another




This nickname is already used by another WWN on the same port.

The specified Host Storage

Domain

(nickname="Nickname for

Host Storage Domain", portID="Port ID") does not exist.

The specified WorldWideName

(nickname="Nickname for

WorldWideName") does not exist in the Host Storage

Domain (portID="Port ID", domainID="Domain ID").


(devNum = "Device number") set for PP Name

(QuickShadow) cannot be deleted.


Specify the WWN which does not belong to other HostStorageDomain on the same port, and then retry.



WWN/HostStorageDomain on the same port, and then retry.


HostStorageDomain on the same port, and then retry.


WWN on the same port, and then retry.

Revise the parameter specifications

Delete the settings, then delete the path.



Error Code

KAIC07831-E

KAIC07832-E

KAIC07833-E

KAIC07834-E

KAIC07835-E

KAIC07840-E

KAIC07841-E

KAIC07842-E

KAIC07843-E

KAIC07844-E

KAIC07845-E

KAIC07846-E


In this API version, creation, modification, and deletion of

"PP Name (QuickShadow)" pairs on the specified device is not supported.


(nickname = Nickname for

ISCSIName) does not exist in the host storage domain

(portID = Port ID, domainID =

Domain ID).

The specified host storage domain does not exist in the


There is no communication protocol by which host "host-

name" and host "host-name" can communicate with each other.

The IP address necessary to perform the specified operation is not registered with the host "host-name".

The specified port already has the maximum number of

LUNs.

The specified

HostStorageDomain already has the maximum number of

LUNs.

The specified LDEV (devNum

= "Device number") is not a

LUSE.

The specified LUSE (devNum

= "Device number") has an

LUN. LUSEs that have LUNs cannot be deleted with the

"DeleteLUSE" command.

Some parameters are incorrect. The same ruleID

"ruleID" is specified with two or more "Rule" elements in the request.

An attempt is being made to set multiple volumes for the same port, group, or LUN group (portID = "Port ID", domainID = "Domain ID", lun

= "LUN").

The LDEV (devnum = "Device

number") you are attempting to use, to make up the LUSE, is a command device.



Revise the host storage domain specification.

Revise the host settings.

Revise the host agent version, the RAID

Manager version, and/or the host settings.

No more LUNs can be specified on this port, select a different port on which to add LUNs.

No more LUNs can be specified on this

HostStorageDomain. Select a different

HostStorageDomain on which to add LUNs.

Make sure the specified LDEV is correct.

Make sure the LUSE specification is correct.

Check the specification of the ruleID of Rule elements, and then retry.

Check and, if necessary, revise the specifications.



1-103

1-104

Error Code

KAIC07847-E

KAIC07848-E

KAIC07849-E

KAIC07850-E

KAIC07851-E

KAIC07852-E

KAIC07853-E

KAIC07854-E

KAIC07855-E

KAIC07856-E

KAIC07857-E

Description

An attempt is being made to set multiple volumes for the same port, group, or LUN group (portID = "Port ID", lun

= "LUN").

The first specified LDEV

(devNum = "Device number") must have the lowest number from among the LDEVs in the list.

For the specified request, if

(type="array-group type") is specified in the ArrayGroup element, the dpPoolID or threshold attribute in a

LogicalUnit element cannot be specified.

In the specified request,

"type" attributes in more than one ArrayGroup element differ. All "type" attributes within the ArrayGroup elements must be the same.

The "force" option cannot be specified for this ArrayGroup element.

A specified ArrayGroup element (chassis="chassis", number="array-group

number") cannot be deleted because the LU "device

Number" in the array group is a pair device.

The specified LU "device

Number" cannot be deleted because it is a pair device.

This "API or CLI" version does not support deletion of "PP

name (QuickShadow)" virtual volumes.

This "API or CLI" version does not support creation of "PP

name (QuickShadow)" virtual volumes.

This request cannot specify an

ArrayGroup element that has the attribute

(chassis="chassis").

This request cannot specify a

LogicalUnit element that has the attribute

(chassis="chassis").


Revise the specification, and then retry.


Revise the specification of the ArrayGroup element "type" attributes, and then retry the operation.


Revise the specification of the ArrayGroup element, and then retry the operation.

Revise the specification of the LogicalUnit element, and then retry the operation.

Check what "API or CLI" versions support deletion of "PP name (QuickShadow)" virtual volumes.

Check what "API or CLI" versions support creation of "PP name (QuickShadow)" virtual volumes.

Revise the specification of the ArrayGroup element.

Revise the specification of the LogicalUnit element.



Error Code

KAIC07858-E

KAIC07860-E

KAIC07861-E

KAIC07862-E

KAIC07863-E

KAIC07864-E

KAIC07866-E

KAIC07867-E

KAIC07869-E

KAIC07870-E

KAIC07871-E

KAIC07872-E

Description

In the specified request,

"type" attributes in more than one LogicalUnit element differ.

All "type" attributes within the

LogicalUnit elements must be the same.

Missing parameter:

DataRetention "parameter-

name". At least one of these parameters is required to change the protection attributes.

The value for "parameter-

name" is invalid.

The specified LDEV is not an open volume. The protection attributes of the specified

LDEV cannot be changed.

The specified LDEV is not a representative-LDEV. The protection attributes of the specified LDEV cannot be changed.

The specified LDEV is an

OnDemand device. The protection attributes of the specified LDEV cannot be changed.

The specified LDEV is a PP

Name (VolumeMigration) reserved volume. The protection attributes of the specified LDEV cannot be changed.

The specified LDEV is a command device. The protection attributes of the specified LDEV cannot be changed.

The specified LDEV is not protected. The retention term cannot be set for an LDEV that is not protected.

The specified LDEV is a pool volume. The protection attributes of the specified

LDEV cannot be changed.

When the ioAccess value is changed to a value other than

Read/Write, replication cannot be set.

The ioAccess value is set to a value other than Read/Write, so replication cannot be set.

Revise the specification of the LogicalUnit elements.


Specify the required parameter, and then retry.

Specify a valid value, and then retry.



Revise the ioAccess and replication specifications.



1-105

1-106

Error Code

KAIC07880-E

KAIC07881-E

KAIC07882-E

KAIC07883-E

KAIC07884-E

KAIC07885-E

KAIC07886-E

KAIC07890-E

KAIC07891-E

KAIC07892-E

KAIC07893-E

KAIC07894-E

Description

The LUSE cannot be created because the CLPRs of the specified LDEVs (devnum =

"Device number" and devnum

= "Device number") are different.

An attempt to execute the request has failed. The specified LU cannot be used for a Delta Resync pair.

An attempt to execute the request has failed. The specified journal group cannot be used for a Delta Resync pair.

Execution of the request failed. At least one storage subsystem that makes up 3DC is not registered in the Device

Manager database.

An attempt to execute the request has failed. Some storage subsystems that make up the 3DC do not support

Delta Resync pair creation.

An attempt to execute the request has failed. The specified operation is not supported for the Delta

Resync pair.

An attempt to execute the request has failed. The specified pair cannot be deleted because a Delta

Resync pair exists.


number" is protected. It cannot be deleted.


number" is protected. It cannot be used for LUSE.

The specified LUSE volume

"device-number" is protected.

It cannot be released.


number" is protected. It cannot be used for a command device.


number" is protected. It cannot be used for S-VOL.




Add all the storage subsystems that make up

3DC, and then try again.

Check the microcode version of all storage subsystems that make up the 3DC.


Check the specification of the LU.


Check the specification of the LU.



Error Code

KAIC07895-E

KAIC07896-E

KAIC07897-E

KAIC07898-E

KAIC07899-E

KAIC07901-E

KAIC07902-E

KAIC07903-E

KAIC07904-E

KAIC07905-E

KAIC07906-E

KAIC07907-E

KAIC07908-E

KAIC07909-E

Description

The LU "device-number" that is P-VOL of the specified replication pair is protected.

Restore operation cannot be performed.

The LU "devNum" that is S-

VOL of the specified replication pair is protected.

Resync operation cannot be performed.

The specified array group contains protected LDEV(s).

The array group cannot be deleted.

The LU "device-number" that is S-VOL of the specified replication pair is protected.

The restore operation cannot be performed.


An agent service failed to execute because a proper method could not be found for the class-name class.

The request has failed. The attribute "attribute-name" was not specified.

The request has failed. The specified Host (name="host-

name", hostID="host-id") was unable to handle replication.

The request has failed. The specified Host ID "specified-

host-id" was not found in the database.

The request has failed. No

ReplicationInfo was specified.

The request has failed. An invalid value was specified for

"attribute-name".


"attribute-name".

The request has failed.

"attribute-name" was not specified.


"attribute-name".


"replicationFunction".


Check the specification of the replication pair.

Check the specification of the array group.

Check the specification of the replication pair.


The API requires "attribute-name" when the objectID is not specified. Add "attribute-name" to the request, and then retry.

Select a valid host, and then retry.


AddReplication requires at least one

ReplicationInfo. Add a ReplicationInfo to the request, and then retry.

Valid names must have length 1 to 31, and must not include whitespace(' '). Check the request, and then retry.

Valid values are 0 to 4094. Check the request, and then retry.

When creating new Configuration File, network port number is necessary. Check the request, and then retry.

Valid values are 0 to 65535. Check the request, and then retry.




1-107

1-108

Error Code

KAIC07910-E

KAIC07911-E

KAIC07912-E

KAIC07913-E

KAIC07914-E

KAIC07915-E

KAIC07916-E

KAIC07917-E

KAIC07918-E

KAIC07919-E

KAIC07920-E

KAIC07921-E

Description

The request has failed. An invalid value was specified for fenceLevel.







An attempt to execute the request has failed. The specified logical unit (serial number = "serial-number", device number = "device-

number") was not found in the database.

An attempt to execute the request has failed. The specified logical unit (serial number = "serial-number", device number = "device-

number") cannot be used for replication because it is

"cause".

An attempt to execute the request has failed. For the specified logical unit (serial number = "serial-number", device number = "device-

number"), security for the host has not been set.

An attempt to execute the request has failed. An invalid value has been specified for muNumber.

An attempt to execute the request has failed. The specified subsystem (serial number = "serial-number") was not found in the database.

An attempt to execute the request failed. No host agents were found for the specified host "host-name".

AddReplication requires the array type. Check the request, and then retry.

AddReplication requires a serial number.


AddReplication requires a device number.



Set the security for the host, and then perform a refresh.

Revise the muNumber specification.


Confirm that host agents have been installed for the host "host-name", and then restart the agents. If the host is a mainframe host, confirm that a valid URLLink has been specified.

Contact the Support Center. No more ReplicationGroups may be created.

No more ConfigFiles may be created.


Valid values are Never, Data or Status. Check the request, and then retry.



Error Code

KAIC07922-E

KAIC07923-E

KAIC07924-E

KAIC07925-E

KAIC07926-E

KAIC07927-E

KAIC07928-E

KAIC07929-E

KAIC07930-E

KAIC07931-E

KAIC07932-E

KAIC07933-E

KAIC07934-E

KAIC07935-E


The request has failed. Fence

Level 'Status' was not used for the specified subsystem.

The license key for "license-

name" has not been installed.

The license key for "license-

name" is disabled.


Duplicated pairNames "pair-

name" are specified.

The request has failed. The specified pairName "pair-

name" is already being used.

No more ReplicationInfo may be created.

The specified subsystem has just one port controller.

An attempt to execute the request has failed. A remote path or the MCU-RCU path between the local subsystem and the remote subsystem is not correctly set.

An attempt to execute the request has failed. The host

"host-name" does not recognize the specified logical unit (serial number = "serial-


"device-number").

The request has failed. The size of the specified

LogicalUnits pair does not match.

The request has failed. No pair could be created with the specified logical units by the specified replication function.

The request has failed. The emulation type of the specified

LogicalUnits pair does not match.

The request has failed. The default port controller of the specified LogicalUnits pair does not match.

An attempt to execute the request has failed. The specified array group (serial number = "serial-number", chassis = "chassis", number =

"array-group-number") was not found in the database.

Check the parameter, and then retry.

Contact the Support Center. Install the license key.

Contact the Support Center. Enable the license key.

Specify pair names which are unique in a

HORCM instance.


Dual-port-controller is necessary.

Revise the remote path or the MCU-RCU path.

Make sure that the host can recognize the logical unit, and then execute the host agent command "HiScan".

Specify the LogicalUnits whose size are same for P-VOL and S-VOL.


Specify the LogicalUnits whose emulation type are same for P-VOL and S-VOL.

Specify the LogicalUnits whose default port controller are same for P-VOL and S-VOL.




1-109

1-110

Error Code

KAIC07936-E

KAIC07937-E

KAIC07938-E

KAIC07939-E

KAIC07940-E

KAIC07941-E

KAIC07942-E

KAIC07943-E

KAIC07944-E

KAIC07945-E

KAIC07946-E

KAIC07947-E

KAIC07948-E

KAIC07949-E

KAIC07950-E

Description

The request has failed. The specified LogicalUnits pair does not match. RAID type does not meet the conditions.

The request has failed. The specified LogicalUnit was

LUSE.

The request has failed. The specified port number "port-

number" was already used in another configuration file.


Replication pairs in the same replication group must have the same replication function.


Replication pairs in the same replication group must have the same fence level.


Subsystems in the same replication group must be all

RAID or All DF.

The request has failed. The specified replication group cannot be operated on per group. The configuration file contains an unknown definition.

An unexpected response was returned from the host agent transport.

Some of the requests of "api-

name" has failed.

This GetHost request is invalid. "element-name" do not have a objectID.

The same object is included in a single request.

The specified storage subsystem does not support

TrueCopyAsync.

Reverse resynchronization cannot be performed for the specified pair.

An invalid replication configuration was specified.

The request has failed. The specified MU number is already in use.


Specify the LogicalUnits whose number of data disks are the same for P-VOL and S-VOL. If the pair is TrueCopy, RAID type of the

LogicalUnits must be "RAID5".

Specify the LogicalUnits which are not LUSE.

Specify the port number other than "port-

number".


Operate per pair.



Center.





Confirm that a replication configuration is valid.

Specify another MU number.



Error Code

KAIC07951-E

KAIC07952-E

KAIC07953-E

KAIC07954-E

KAIC07955-E

KAIC07956-E

KAIC07957-E

KAIC07958-E

KAIC07959-E

KAIC07960-E

KAIC07961-E


An attempt to execute the request has failed. The storage subsystem "storage-

array-name" can have a maximum of "max-number-of-

pairs" "replication-function" pairs.

An attempt to execute the request has failed. The specified subsystem

(sequence number =

"sequence-number") was not found in the database.

The request has failed. The specified logical unit pair is invalid. The number of configured LDEVs is different.

The request has failed. The specified host (name="host-

name", hostID="host-id") cannot handle replication.

"agent-or-raidmanager" is not installed.

The request has failed. The specified Host (name="host-

name", hostID="host-id") cannot handle replication. The host does not recognize the logical units.

The request has failed. The specified Host (name="name", hostID="host-id") cannot handle replication. The host does not recognize the command device.

The request has failed. The specified LogicalUnits are not open volumes.

An attempt to execute the request has failed. The combination of the pair that configures the group is invalid.

The request has failed. In the case of QuickShadow,

ReplicationInfo's status must be 'Simplex'.

The request has failed. In the case of QuickShadow, S-VOL must be QuickShadow V-VOL.

The request has failed. The specified P-VOL is not paired with selected V-VOL when

QuickShadow pair was made.

Delete an existing pair.


Specify the LogicalUnits whose number of

LDEVs are same for P-VOL and S-VOL.

Install "agent-or-raidmanager", and then retry.

Make sure that the host "host-name" recognizes the logical units, and then perform

"HiScan" command from the host agent.

Make sure that the host "name" recognizes the command device, and then perform

"HiScan" command from the host agent.

Specify open-volume-LogicalUnits for P-VOL and S-VOL.


Alternatively, specify a different group, and then retry.

Specify another LU, and then retry.

Specify QuickShadow V-Vol for S-VOL.

Specify another LU, and then retry.



1-111

1-112

Error Code

KAIC07962-E

KAIC07963-E

KAIC07964-E

KAIC07965-E

KAIC07966-E

KAIC07967-E

KAIC07968-E

KAIC07969-E

KAIC07970-E

KAIC07971-E

KAIC07972-E

Description

The request has failed. The

QuickShadow pair could not be created in the specified array system.

The request has failed. The port ID "port-id" is invalid.

An attempt to execute the request has failed. For the specified logical unit (serial number = "serial-number", device number = "device-

number"), security for the host has not been set on the specified port "port-ID".

An attempt to execute the request has failed. The host

"host-name" does not recognize the specified logical unit (serial number = "serial-


"device-number") on the specified port "port-ID".

An attempt to execute the request has failed. There are no paths on the specified port

"port-ID" for the specified logical unit (serial number =

"serial-number", device number = "device-number").

An attempt to execute the request has failed. There are no paths for the specified logical unit (serial number =

"serial-number", device number = "device-number").

The request has failed. No port was found.

In this API version,

QuickShadow is not supported.

The specified icon "icon" is invalid.

An attempt to execute the request has failed. Multiple pairs for one P-VOL of

QuickShadow cannot be restored at the same time.

The request has failed. The specified instance number

"instance-number" is already in use.



Specify another port ID, and then retry.

Set the security for the host, and then perform a refresh.

Make sure that the host can recognize the logical unit, and then execute the host agent command "HiScan".

Set a path for the logical unit on the specified port.

Set a path for the logical unit.

Confirm the port status.


Check the specified icon file.


Specify another instance number.



Error Code

KAIC07973-E

KAIC07974-E

KAIC07975-E

KAIC07976-E

KAIC07977-E

KAIC07978-E

KAIC07979-E

KAIC07980-E

KAIC07981-E

KAIC07982-E

KAIC07983-E

KAIC07984-E

Description

The LUSE could not be created because the types or attributes of the specified

LDEVs (devnum = "Device

number" and devnum =

"Device number") are not identical.

The paths cannot be create to the external port "port name".

Creating or deleting external volumes is not supported.

The specified DevNum "Device

number" already exists in the


An attempt to execute the request has failed. There are no Differential Management

LUs in the specified device.

The specified parameter is invalid. The value that can be specified for a pattern attribute of the WritingPattern element is a hexadecimal number from "Min. parameter

value" to "Max. parameter

value" bytes.

The specified last

WritingPatterns element parameter is invalid.

The specified parameter is invalid. "element-name"

"attribute-name-of-element" :

"attribute-value-of-element"

The stripe sizes of the LDEVs do not match. The LUSE

(devNum = "Device number") cannot be created.

The specified stripeSizeInKB is invalid.

An attempt to execute the request has failed. The specified replication function is not supported in this subsystem.

An attempt to execute the request has failed. The specified replication operation is not supported for this subsystem.




Make sure that all of the LDEVs making up the

LUSE satisfy the following conditions:



The volume classes (internal or external) are identical.





The disk types are identical.

The host's I/O suppression modes are identical.

The cache modes are identical.

Check and, if necessary, revise the port specification.

Check and, if necessary, revise the specification of the LDEV or ArrayGroup.

Revise the specification for devNum of the

LogicalUnit elements, and then retry.

Create a Differential Management LU, and then retry.



Make sure that the specified parameter is valid, and then retry.

Make sure the LDEV specifications are correct.






1-113

Error Code

KAIC07985-E

KAIC07986-E

Description

An attempt to execute the request has failed. The specified replication operation cannot be performed for this emulation type of this volume.

An attempt to execute the request has failed. There is no specified journal group.





Error Code

KAIC07987-E

KAIC07988-E

KAIC07989-E

KAIC07990-E

KAIC07991-E

KAIC07992-E

KAIC07993-E

KAIC07994-E

KAIC07995-E

Description

An attempt to execute the request has failed. The journal group cannot be used because the journal volume is not registered.

An attempt to execute the request has failed. The specified journal group is already being used by the mainframe function.

An attempt to execute the request has failed. The specified journal group is already used as a primary journal group or secondary journal group.

An attempt to execute the request has failed. The specified MU number cannot be used.

An attempt to execute the request has failed. The combination of the journal groups is invalid.

An attempt to execute the request has failed. The CLPR of the pair volume does not match the CLPR of the journal volume that configures the journal group.

An attempt to execute the request has failed. The combination of the journal group and the replication group is invalid.

An attempt to execute the request has failed. All replication pairs in the same replication group must use the same journal group.

The requested operation could not be performed. The specified LU is being used for a PP Name (Dynamic

Provisioning) pool, and cannot be used as the P-VOL or S-

VOL.


Revise the specification, and then retry.





1-115

1-116

Error Code

KAIC07996-E

KAIC07997-E

KAIC07998-E

KAIC08000-E

KAIC08001-E

KAIC08002-E

KAIC08003-E

KAIC08004-E

KAIC08005-E


The requested operation could not be performed. A PP Name

(Dynamic Provisioning) volume cannot be used as the

P-VOL or S-VOL for the following replication function.

Replication function: PP Name

(TrueCopy, TrueCopyAsync,

QuickShadow,

UniversalReplicator)

The requested operation could not be performed. If you use a

PP Name (Dynamic

Provisioning) volume as the S-

VOL for PP Name

(ShadowImage), you must also use a PP Name (Dynamic

Provisioning) volume as the P-

VOL.

An attempt to execute the request has failed. The CLPR of the pair volume does not match the CLPR of the pair volume that belongs to the journal group.

A part that differs from the actual machine was found in the subsystem information.

Refresh the subsystem. If you are a local user, contact the system administrator.

A part that differs from the actual machine was found in the subsystem information.

Refresh the subsystem. If you are a local user, contact the system administrator. (error =

"error")

"FreeSpace" cannot be specified. Revise the "

" bulk

"," dividebycap

", and

" dividebynum then retry.

" options, and

This API version does not support batch operations on

Lus.

An attempt to execute a request has failed. The combination of options "option

name" and "option name" is invalid.

The number of LUs that can be deleted cannot exceed

"maximum number of LUs".


The Device Manager server might not contain the latest storage subsystem information.

Refresh the information by using the GUI refresh function, or by executing

AddStorageArray of the API.

Revise the option specification.

Make sure that the API version supports the command.

Revise the option specification.




Error Code

KAIC08006-E

KAIC08007-E

KAIC08008-E

KAIC08009-E

KAIC08010-E

KAIC08011-E

KAIC08012-E

KAIC08013-E

KAIC08014-E

KAIC08015-E

KAIC08016-E

KAIC08017-E

KAIC08018-E


Batch deletion is not possible for LUs whose emulation is not

OPEN-V. (devNum = device

number)

An LDEV (devNum = device

number) that has a path defined cannot be deleted.

An LDEV (devNum = device

number) that has a LUSE defined cannot be deleted.

The specified array group does not exist in the Device

Manager database.

The specified array group does not have sufficient free space.

The Device Manager database does not have sufficient free space.

A "PP Name (Dynamic

Provisioning)" volume

(devNum = "device number") cannot be deleted in Device

Manager.

An attempt to execute a request has failed. When

"option name" is specified,

"option name" must also be specified.

This subsystem does not support batch operations on

LUs.

Batch creation is not possible for LUs whose emulation is not

OPEN-V.

The request syntax is incorrect. The attribute

"attribute-name" is not specified in the element

"element-name".

The request syntax is incorrect. The value

"attribute-value" (specified for the attribute "attribute-name" in the element "element-

name") is duplicated.

The request syntax is incorrect. The attribute

"attribute-name" is not specified in the element

"param" (name = "element-

name").


Defined paths must be deleted before deleting

LDEVs.

LUSEs must be deleted before deleting LDEVs.



Revise the free space specification.



Check the subsystem.

Revise the emulation type specification.

Revise the request syntax, and then try again.





1-117

1-118

Error Code

KAIC08019-E

KAIC08020-E

KAIC08021-E

KAIC08022-E

KAIC08023-E

KAIC08024-E

KAIC08025-E

KAIC08026-E

KAIC08027-E


Execution of the request failed. The value "attribute-

value" (specified for "Type" in the parameter "parameter-

name") is invalid.


value" (specified for "value" in the parameter "parameter-

name") is invalid. Specify the value as "valid-values (only

"2")".


value" (for "value" in the parameter "parameter-name") is invalid. Specify a value that is no more than "max-

character-string-length" characters.


value" (for attribute

"attribute-name" in element

"element-name") is invalid.

Execution of the request failed. If the parameter

"parameter-name" is specified, the parameter

"parameter-name" must also be specified.


value" (for "value" in the parameter "parameter-name") is invalid. Specify a size that is within the free-disk space of

"InPool".

The request syntax is incorrect. The invalid attribute

"attribute-name" is specified in the element "parameter-

name".

The request syntax is incorrect. The child element

"ArrayValue" must be specified for the parameter

"parameter-name".


value" (for the attribute

"value" of the child element

"ArrayValue" in the parameter

"parameter-name") is invalid.












Error Code

KAIC08028-E

KAIC08030-E

KAIC08100-E

KAIC08101-E

KAIC08102-E

KAIC08103-E

KAIC08104-E

KAIC08105-E

KAIC08106-E

KAIC08107-E

KAIC08108-E

KAIC08110-E

KAIC08111-E


An attempt to execute a request has failed. The number of child elements for parameters "parameter-name" and "parameter-name" are not the same.

The specification method

("method-name") cannot be executed. Wait a while, and then try again. (object path =

"object-path")

You have already selected another subsystem

("subsystem-name"). You can reserve only one subsystem at a time.

The subsystem has been reserved by user "user-name".

A reserved subsystem cannot be deleted.

The properties, except for the name of the reserved subsystem, cannot be changed.

Another application has already reserved the specified subsystem. Only the reserving application can perform operations now.

The subsystem is not reserved, or the reservation was released because the time limit was exceeded.

The specified command is not available for reserved subsystems.

The reservation status has been changed.

The specified command cannot be executed using the storage subsystem microcode version

"microcode-version".

This command cannot be executed because, for the specified storage subsystem, only one "PP Name (Dynamic

Provisioning)" volume can be added to an array group.

This command cannot be executed because, for the specified storage subsystem, the array group must be specified.



Center.

Release the reservation on the other subsystem, then retry the operation.

After the subsystem reservation has been released, retry the operation.

Retry the operation from the reserving application.

Check whether the reservation has been released.

After the subsystem reservation has been released, retry the operation.

Check the reservation status.

Make sure the microcode version of the storage subsystem is correct.





1-119

1-120

Error Code

KAIC08112-E

KAIC08113-E

KAIC08114-E

Description

The specified external array group "external array group

name" cannot be deleted because Device Manager does not contain any externally mapped volume information for the external array group.

The specified external array group "external array group

name" cannot be deleted because the emulation type is not OPEN-V.

External array groups can only be deleted from the CLI.


Revise the external array group information.

Revise the external array group information.

Use the CLI to execute the request.

Table 1-10 KAIC09000-KAIC09999: CIM/WBEM Errors

Error Code

KAIC09000-E

KAIC09001-E

KAIC09002-E

KAIC09003-E

KAIC09004-E

KAIC09005-E

KAIC09006-E

KAIC09007-E

KAIC09008-E

KAIC09009-E

Description

An unidentifiable CIM Wbem service error was encountered.

"CIM-class-name" class does not support the "method-

name" method.


An attempt to find the "CIM-

class-name" class has failed.


"stack-trace"


The ACL users table is empty.


The ACL rules table is empty.

Authentication has failed. username: "user-name"

The operation was denied. username: "user-name", write request: "whether-request-

needs-write-permission"

The operation was not authorized. username: "user-

name", write request:

"whether-request-needs-write-

permission"

The "requested-operation-

name" operation has failed.



Use another operation. If the used operation should be supported, contact the Support

Center.


Check the server condition ACL users.

Check the server condition ACL rules.

Check the username and password, and then retry.

Check the username, password and user permissions, and then retry.

Follow the last related message. If there is no related message, contact the Support Center.



Error Code

KAIC09011-E

KAIC09012-E

KAIC09013-E

KAIC09014-E

KAIC09015-E

KAIC09016-E

KAIC09017-E

KAIC09018-E

KAIC09019-E

KAIC09020-E

KAIC09021-E

KAIC09022-E

KAIC09023-E

KAIC09024-E

KAIC09025-E


An attempt to create a CIM-

Instance failed. Class:"CIM-

class-name", Key:"key-

properties", "stack-trace"


An attempt to create a CIM-

ObjectPath has failed.

Class:"CIM-class-name",

Key:"key-properties", "stack-

trace"

The WQL is invalid.

Property:"property-name",

Operator:"operator(number)",

Value:"value"

The WQL is unsupported.

Property:"property-name",

Operator:"operator(number)",

Value:"value"

This association cannot be associated.

Source(Class:"source-CIM-

class-name",Role:"source-

role") and Result(Class:"result-

CIM-class-name",Role:"result-

role")

Check the specified WQL or ObjectPath, and then retry.


This association is not supported as a result class of this Association class. "class-

name"

An invalid key property exists in the ObjectPath. "key-name"


Check the specified ObjectPath, and then retry.

An attempt to obtain a class name from ObjectPath has failed. ObjectPath:

"ObjectPath"

The WQL is invalid. wql:"WQL" Check the specified WQL or ObjectPath, and then retry.

The class is invalid. class:

"class-name"

Check the specified ObjectPath, and then retry.

The property is invalid.

Property: "property-name" value: "value"

Check the specified WQL or ObjectPath, and then retry.

The role parameter is invalid.

"role"

The parameter is invalid. When

ResultClass is not specified,

PropertyList cannot be specified.

The argument type is invalid.

"type"


"object-name" is null.

Check the specified role or resultRole, and then retry.

Specify the ResultClass, or do not specify the

PropertyList.

Check the specified argument type, and then retry.




1-121

1-122

Error Code

KAIC09026-E

KAIC09027-E

KAIC09028-E

KAIC09029-E

KAIC09100-E

KAIC09101-E

KAIC09114-E

KAIC09501-E

Description

The instance does not exist.

Object path:"Object path"

In the "requested-operation-

name" operation, An attempt to retrieve data for the storage array has failed.

An attempt to execute a request failed. Check and, if necessary, revise the request, and then try again.

An attempt to execute a request failed. Check and, if necessary, revise the operating environment, and then try again.

CIM-WBEM Service initialization error: an invalid

HTTP port number "port-

number" has been specified.

CIM-WBEM Service initialization error: an invalid

HTTPS port number "port-

number" has been specified.

An attempt to start the CIM-

WBEM Service on port "port-

number" failed.

An error occurred within SLP

API processing. SLP error number: "SLP-error-number", error details: "error-detail"


Check the object path, and then re-execute.

Follow the last related message. If there is no related message, contact the Support Center.

Check and, if necessary, revise the request, and then try again.

Check the operating environment. If the error persists, contact the Support Center.

Confirm the value of "server.properties" and restart the services.

Stop any service that uses a port having a port number used by the CIM-WBEM Service, and restart the Device Manager Server.

Check if the SLP daemon is running. If it is not running, then start it and restart the

Device Manager Server. If this error occurs even the SLP daemon is already running, then contact the Support Center.

Table 1-11 KAIC30000-KAIC39999: Trace messages

Error Code

KAIC30004-I

KAIC30005-I

KAIC30017-I

KAIC32006-I

KAIC32007-I

KAIC32101-I

KAIC32102-I

KAIC33020-W

KAIC33025-W

KAIC33026-I

KAIC35435-I

Description

Device Manager Server has started.

Device Manager Server has stopped.

Device Manager Server has started in Secure mode.

Device Manager HiKeyTool has started.

Device Manager HiKeyTool has stopped.

Device Manager "client-name" has started.

Device Manager "client-name" has finished.

An inconsistency was detected from the database information. The database will now be initialized.

An inconsistency was detected from the database information. Restore the database from the backup.

The database will now be initialized.

The version of the "library-name" is "version (additional-information)".



Error Code

KAIC35436-W

KAIC39004-I

KAIC39005-I

Description

An attempt to get the version of "library-name" has failed (Error code "error-

code").

The CIM-WBEM Service has started.

The CIM-WBEM Service has stopped.



1-123

Device Manager Web Client Messages

The Device Manager Web Client error messages are output to the following log files:



For Windows systems:

Device-Manager-installation-

destination\DeviceManager\HiCommandServer\logs\HDvMGuiTracen.log



For Solaris and Linux systems:

/opt/HiCommand/HiCommandServer/logs/HDvMGuiTrace

n.log where n is a numerical value that indicates the file number.

The Web Client error messages are output to the log files in the following

format (see Table 1-12):

serial-number date time program-name process-ID thread-ID ID type message

Table 1-13 lists the Hitachi Device Manager Web Client GUI error messages,

and provides recommended actions for resolving the error conditions. The error messages are listed in numerical order by error code. For errors whose recommended action is "Contact the Support Center.", first collect maintenance information by executing the hcmdsgetlogs command, and then

contact the Hitachi Data Systems Support Center (see Calling the Hitachi Data

Systems Support Center for contact information).

Table 1-12 Format of Messages Output to Log Files

Item

Serial number

Date

Time

Program name

Process ID

Thread ID

ID

Description

Serial number of the message.

Date the error occurred, in yyyy/mm/dd format.

Time the error occurred, in hh:mm:ss:xxx format (xxx indicates milliseconds).

Component name or command name of Device Manager.

Process ID of the program that requested the log output.

Thread ID of the program that requested the log output.

Message ID. Device Manager messages are output in KAICmmmmm-X format.

KAIC: Character strings that indicate the message is output from

Device Manager.

mmmmm: Error code.

X: Indicates the error level. One of the following is displayed:

I

(nonerror information),

W

(warning), or

E

(error).

1-124

Message Message.



Table 1-13 KAIC10000-KAIC11999: Hitachi Device Manager Web Client

GUI Errors

Error Code

KAIC10001-W

KAIC10002-W

KAIC10003-W

KAIC10004-W

KAIC10005-W

KAIC10006-W

KAIC10010-W

KAIC10011-W

KAIC10012-W

KAIC10013-W

KAIC10015-W

KAIC10016-W

KAIC10017-W

Description

Currently, there are commands being processed for subsystem <subsystem-

name>.

Cannot Move Storage to a

LogicalGroup which has different subsystem.


name>.

There are processing tasks still running on logical group "<logical-

group-name>".

There are processing tasks still running on storage subsystem

"<subsystem-name>".


name>.

Subsystem is busy. Please retry this action after the previous action is completed.


Please retry this action after the active commands are completed.

Please move storage to a Logical

Group which contains storage in same storage subsystem.

Please retry this action after the active commands are completed.

An attempt to add the storage has failed.

Please retry this action after the previous action is completed.







An attempt to move same LUN has failed.


An attempt to delete the LUN security has failed.


An attempt to remove the Port has failed.


An attempt to delete the group has failed.




1-125

1-126

Error Code

KAIC10018-W

KAIC10019-W

KAIC10024-W

KAIC10025-W

KAIC10026-W

KAIC10027-W

KAIC10028-W

KAIC10029-W

KAIC10030-W

KAIC10031-W

KAIC10032-W

KAIC10033-E

KAIC10034-W

Description












The server is returning a Message ID that is used by a previous command.

Delete alerts is in process. Please retry this action after the previous action is completed.


An attempt to delete the storage has failed.


An attempt to delete the storage array has failed.


An attempt to scan LUN has failed.


An attempt to delete the storage from multi groups has failed.


An attempt to add the Logical Unit has failed.


An attempt to delete the Logical Unit has failed.


An attempt to add the array group has failed.


An attempt to define spares has failed.


An attempt to delete the array group has failed.


An attempt to modify the port controller has failed.


An attempt to add HostStorageDomain has failed.


If this error persists, please contact the Support Center.

Please retry this action after the active action is completed.



KAIC10039-E

KAIC10040-E

KAIC10041-E

KAIC10042-E

KAIC10043-E

KAIC10044-E

KAIC10045-E

KAIC10046-E

KAIC10047-E

KAIC10048-E

KAIC10049-E

Error Code

KAIC10035-E

KAIC10036-E

KAIC10037-E

KAIC10038-E

Description

Device Manager Web Client was unable to communicate with the



Check the network status and whether the Device Manager server is running correctly.

If a network problem exists, remove its cause.

If the Device Manager server has stopped, start it. If you cannot start the server, contact the Support

Center.

Even if the Device Manager server is running correctly, this message might be output if the Device Manager server takes an unusually long time to start because of its status when it last stopped. In this case, wait a while and then retry starting the server.

Please contact the Support Center.

Device Manager Web Client internal error has occurred.

A problem was encountered trying to download and install the server certificate. Device Manager Web Client is unable to access the Device

Manager Server through the secure channel. Please contact your system administrator for assistance.

A file required for a secure socket connection cannot be downloaded.

Click OK to exit the system.












Please ask the system administrator if the Keystore file is located in correct location on the server machine.

Please check the network configuration.




1-127

1-128

KAIC10058-E

KAIC10059-E

KAIC10060-E

KAIC10061-E

KAIC10062-E

KAIC10063-E

KAIC10064-E

KAIC10065-E

KAIC10066-E

KAIC10067-E

Error Code

KAIC10050-E

KAIC10051-E

KAIC10052-E

KAIC10053-E

KAIC10054-E

KAIC10055-E

KAIC10056-E

KAIC10057-E

KAIC10068-E

KAIC10069-E

KAIC10070-E

KAIC10071-E

KAIC10072-E

Description




























Error Code

KAIC10073-E

KAIC10074-E

KAIC10075-E

KAIC10078-E

KAIC10079-W

KAIC10081-W

KAIC10082-W

KAIC10083-W

KAIC10084-W

KAIC10085-W

KAIC10086-E

KAIC10087-W

KAIC10088-W

KAIC10089-E

KAIC10091-W

KAIC10092-W

KAIC10093-W


A user is not permitted to log in as

Peer.

Since the version of JRE is old,WebClient cannot be started. The version of JRE which is operating now is <JRE-version>.

The Logical Group that you have selected no longer exists.

Cannot parse "<value>" into a floating point number.

No LU is selected.

Please log in not as Peer.

Confirm that you are using a JRE version that is supported for use with

Web Client.

Please open another window, then come back to the original window. If this error persists, please contact the

Support Center.

If this error persists, please contact the Support Center.

Please continue process after selecting the storage.

Please check the network configuration. If you want to launch

Storage Navigator or Dynamic Link

Manager, please check if the selected application is working properly.

Please continue operation after a logical group is selected.

Device Manager cannot modify the logical group because no logical group has been selected.

A logical group cannot be deleted if it or a child group has already been allocated to a resource group. The resource group must be deleted first.

Please retry operation after deleting the resource group.

Device Manager cannot delete the logical group because no logical group has been selected.

Storage cannot be moved to a logical group assigned to the resource group

<resource-group-name>.


Please move the storage to a logical group that is not assigned to the resource group.

Device Manager cannot proceed to the next step because no logical group is selected.


There was an error adding a new host. Contact the Support Center.

Currently, there are commands being processed for subsystem <name>.

Please continue operation after the active process is finished.

Currently, there are commands being processed for subsystem <name>.



All of the disks in an array group must be in the same row and chassis.

You must select at least two (2) disks to create an array group.

All of the disks in an array group must be next to one another.

Please select disks which are located in the same row and chassis.

Please select at least two disks.

Please select disks located next to each other (contiguous).



1-129

1-130

Error Code

KAIC10094-W

KAIC10095-W

KAIC10096-E

KAIC10097-E

KAIC10098-E

KAIC10099-W

KAIC10100-W

KAIC10101-W

KAIC10103-W

KAIC10104-E

KAIC10105-E

KAIC10106-E

KAIC10108-E

Description

You cannot delete the user who is currently logged on.


To delete the specified user, first log on as another system administrator or local system administrator.

Please delete the specified user after creating one or more users.

You have asked to permanently delete the last <resource-group-name> user. There must always be at least one user of this type for Device

Manager to work.



Inconsistent properties found in the logical group "<name>".

No storage is selected.


The Storage Array is not selected!

This resource group name already exists. Select a different name.

Your user ID or password is invalid, please check with the Administrator.

Device Manager Web Client has lost the network connection to the Device

Manager Server. This might be due to a network problem or the server may be down. Device Manager Web Client will now exit. Please check your network connection and try again later.

Please retry operation after the storage is selected.

Please retry operation after the storage subsystem is selected.

Please select a resource group name which is not duplicated.

Please select a user name which is not duplicated.

Please confirm your user ID and password with the Administrator.

Please check if Device Manager is running properly. Please also check network condition.

Also confirm that the number of LDEVs specified for a single operation does not exceed the maximum specifiable number. This maximum number is approximately 200 if each LDEV has one volume path, or 100 if each LDEV has two volume paths.

Please check if Device Manager Agent is running properly. Please also check network condition.

Device Manager has lost the network connection to the Device Manager

Agent. This might be due to a network problem or the agent may be down.

The Device Manager Server Certificate has expired. Device Manager Web

Client will now exit. Please contact your system administrator for assistance.

The requested service is not currently implemented on the Device Manager

Server.

Please contact the system administrator.

Please go to the Help, Index in menu bar to check if the versions of server and Web client match.



KAIC10113-E

KAIC10114-E

KAIC10123-E

KAIC10124-E

KAIC10125-E

KAIC10126-E

KAIC10127-E

KAIC10128-E

KAIC10129-E

KAIC10130-E

Error Code

KAIC10109-E

KAIC10110-E

KAIC10111-E

KAIC10112-E

KAIC10131-E

KAIC10132-E

KAIC10133-E

Description

An unexpected error occurred in the

Device Manager Web Client.

An unexpected error occurred in the


Device Manager Server received bad request.

Device Manager Server received too large request.



Device Manager Server is shutting down now.

Device Manager Server cannot find files to be downloaded.

Missing host in message response.

Missing HostInfo in message response.

Parent Group "<logical-group-name>" was deleted in a previous command.

The new parent group already contains storage.

Group Name is duplicated!

The Group Name "<logical-group-

name>" is reserved!

The parent group is busy.

Please contact the System administrator to resize the maximum size of acceptable request for Device

Manager Server.



Please select another logical group for the parent group.

Please select another group name.

Login process to Device Manager

Server is failed. Web Client is shutting down now since there is a possibility of having network problem. Please login after checking network connectivity.

Failed to receive messages from

Device Manager Server. Web Client is shutting down now since there is a possibility of having network problem.

Please check your network connection and try again later.

Failed to receive messages from



Failed to receive command result from



Please retry this action after the active action is completed.

Please check if Device Manager is running properly. Please also check network condition.



1-131

1-132

Error Code

KAIC10134-W

KAIC10135-W

KAIC10136-W

KAIC10137-W

KAIC10139-E

KAIC10140-E

KAIC10141-W

KAIC10142-W

KAIC10143-W

KAIC10144-W

KAIC10145-W

KAIC10146-W

KAIC10147-W

KAIC10148-E

KAIC10149-W

KAIC10150-W

Description

The password you entered was not correct. You will not be permitted to continue this operation.

More than <number> of disks cannot be defined as spare disks of this subsystem.

The subsystem is busy.


Please check the password.

Please select fewer spare disks than specified.

The subsystem is busy.

Device Manager Server internal error has occurred.

<program-name> cannot be started up.



One or no WWNs exist in the WWN group <WWN-group-name>. Make sure that two or more WWNs exist in the WWN group.

No LUNs exist in the LUN Group

<LUN-group-name>. Make sure that more than one LUN exists in the LUN

Group.

A WWN group of the same name already exists in either the dropdown list or storage subsystem.

An LUN group of the same name already exists in either the dropdown list or storage subsystem.

The subsystem is busy. Try this action again once the previous action has completed.

The specified WWN is being used with a different LUN/LUN Group, and cannot be registered.

WWN group names must be less than eight characters, and more than one character.

LUN group names must be less than eight characters, and more than one character.

Wait until the processing finishes, and then retry the operation.




Add two or more WWNs to the WWN group.

Add one or more LUNs to the LUN group.

Change the name of the WWN group to one which does not exist.

Change the name of the LUN group to one which does not exist.


Change the security of the LUN of the corresponding WWN, or de-allocate the WWN.

Change the name.



Error Code

KAIC10151-W

KAIC10152-W

KAIC10153-E

KAIC10154-E

KAIC10155-E

KAIC10156-E

KAIC10157-E

KAIC10158-W

KAIC10159-W

KAIC10160-W

KAIC10161-W

KAIC10162-W

KAIC10163-W

Description

Only the following characters can be used in group names:

ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz

0123456789

_-+=.@!#$%&'^~`[](){}

Only the following characters can be used in group names:

ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz

0123456789

_-+=.@!#$%&'^~`[](){}


The LDEV "<DevNum>" can not be used as a command device.

The capacity of the LDEV is not sufficient.




A duplicate nickname is specified.

The specified nickname "<nickname>" is not available. This nickname is already used by another


The specified nickname "<nickname>" is not available. This nickname is already used by another

WWN/HostStorageDomain on the same port.

The WWN Group could not be registered, because LUN security is disabled. Please enable LUN security.

The LUN Group could not be registered, because LUN security is disabled. Please enable LUN security.

The cascading copy pairs by

ShadowImage / BusinessCopy exist in the group <group-name> (Host:

<host-name> HORCM: <instance-

number>). Cascading copy pairs cannot be specified in the same group. Please select different groups.


Change the name.


Check the capacity of the LDEV/LU and choose another.


Specify a unique nickname, then retry.

Change the name of the

HostStorageDomain to one which does not exist.

Change the name of the

WWN/HostStorageDomain to one which does not exist.

Enable LUN security for this port.

Select another group, or create a new group.



1-133

1-134

KAIC10170-E

KAIC10171-E

KAIC10172-E

KAIC10173-E

KAIC10174-E

KAIC10175-E

KAIC10176-E

KAIC10177-E

KAIC10178-E

KAIC10179-E

KAIC10180-E

KAIC10181-E

KAIC10182-E

Error Code

KAIC10164-W

KAIC10165-W

KAIC10166-W

KAIC10167-W

KAIC10168-W

Description

The specified copy pair name <copy-

pair-name> already exists in Host:


number>. Please enter a different copy pair name.

The specified copy pair name <copy-

pair-name> is duplicated in Host:


number>. Please enter a different copy pair name.

The group <group-name> (Host:


number>) cannot register this combination of copy pairs, since the subsystem type that the copy pairs are using is different.



number>) cannot register this combination of copy pairs, since the fence level that the copy pairs are using is different.



number>) cannot register this combination of copy pairs, since the different combination of P-VOL and S-

VOL subsystem are existed in this group.

Select the storage to be deleted.

Select the storage to be moved.

Select the storage for which you want to modify security.

Select multiple storage for which you want to create a LUSE.

Select the storage for which you want to delete a LUSE.

Select the storage to be allocated.

Select the storage to be unallocated.

Select the storage for which you want to create a copy pair.

Select storage belonging to a single subsystem.

The group name is not specified.

The group name "<group-name>" is a reserved name.

The host name is not specified

The specified World Wide Name is invalid.


Specify another copy pair name.

Select another group, or create a new group.

Only one combination of P-VOL and S-

VOL storage subsystem copy pair can be specified in one group. Select another group, or create a new group.

Select the storage to be deleted.

Select the storage to be moved.

Select the storage for which you want to modify the security.

Select multiple storage to create a

LUSE.

Select the storage for which the LUSE will be deleted.

Select the storage to be allocated.

Select the storage to be unallocated.

Select the storage for which a copy pair will be created.

Select storage belonging to a single storage subsystem.

Enter a group name.

Enter another group name.

Enter a host name.

Enter a valid World Wide Name.



Error Code

KAIC10183-E

KAIC10184-E

KAIC10185-E

KAIC10186-E

KAIC10187-E

KAIC10188-E

KAIC10189-E

KAIC10190-E

KAIC10191-E

KAIC10192-E

KAIC10193-E

KAIC10194-E

KAIC10195-E

KAIC10196-E

KAIC10197-E

KAIC10198-E

KAIC10199-E

KAIC10201-E

KAIC10204-E

KAIC10205-E

KAIC10206-E

KAIC10207-E

KAIC10208-E

KAIC10209-E


The World Wide Name must be unique.

The IP address or host name is not specified.

The user ID is not specified.

Enter another World Wide Name.

Enter an IP address or host name.

Enter a user ID.

The SNMP community is not specified. Enter a SNMP community.

The password is invalid. Re-enter a password.

Enter the LDEV in the correct format. The format of the LDEV entry is invalid.

The format of the total capacity entry is invalid. Enter an integer value.

Revise and re-enter the total capacity.

You can enter a value up to a maximum of 2 to the power of 31 minus 1.

Enter the number of storages. The number of storages is invalid.

Enter an integer value.

The find options are invalid. Enter a valid find option.

Enter the LDEVs.

Enter the total capacity.

Enter the number of storages.

Specify another LDEV number.

Enter LDEVs.

Enter the total capacity.

Enter the number of storages.

A device cannot be found with the selected LDEV number <LDEV-

number>.

There are no or not enough LDEVs matching the search criteria.

Select more than one PORT.

Select more than one PORT-

HOST:WWN/iSCSI Name.

Select more than one LU.

Select more than one LU-PORT-

HOST:WWN/iSCSI Name connection.

An LDEV with a path specified cannot be specified for a LUSE.

An LDEV reserved as a Migration LDEV cannot be specified for a LUSE.

If CVS LDEVs are in a LUSE, all LDEVs must be CVS.

All LDEVs in a LUSE must have the same CU.

All LDEVs in a LUSE must have the same emulation type.

All LDEVs in a LUSE must have the same RAID level.

Specify another find option.

Select more than one PORT.

Select more than one Port-

Host:WWN/iSCSI Name.

Select more than one LU.

Select more than one LU-Port-

Host:WWN/iSCSI Name connection

Select unallocated LDEVs.

Select LDEVs which are not reserved for Volume Migration (Hitachi USP),

CruiseControl (Hitachi Lightning

9900V), or HIHSM (Hitachi Lightning

9900).

Make all the LDEVs either CVS LDEVs or non-CVS LDEVs.

Select LDEVs from the same CU.

Select LDEVs having the same emulation type.

Select LDEVs having the same RAID level.



1-135

Error Code

KAIC10210-E

KAIC10211-E

KAIC10212-E

KAIC10213-E

KAIC10214-E

KAIC10215-E

KAIC10216-E

KAIC10218-E

KAIC10219-E

KAIC10220-E

KAIC10221-E

KAIC10222-E

Description

All CVS LDEVs in a LUSE must have the same size.

The sum total of the LU size must be less than 2 TB.

The RAID0 LDEV cannot be specified in a LUSE.

All LUs must belong to the same default port controller in a LUSE.

Only a maximum of 36 LDEVs may be configured in a LUSE.

Storage cannot be added to the selected logical group.

No subsystems are registered.

A WWN already assigned to the port is selected. Check the available

HOST:WWN and PORT combinations.

Storage which is not a LUSE volume is selected.

Enter your user ID.

Enter your password.

The user ID or password is invalid.


Select LDEVs having the same size.

Make the sum total of the LU size less than 2 TB.

Select LDEVs except RAID 0 level

LDEVs.

Select LDEVs having the same port controller.

Select no more than 36 LDEVs.

Select another logical group.

Add a storage subsystem.

Check the available combinations of

HOST:WWN and PORT.

Select a LUSE volume.

Enter your user ID.

Enter your password.

Enter your user ID and password.



Error Code

KAIC10224-E

KAIC10225-E

Description

An error occurred in Single Sign On

Service.

Your session is over. Log out, and then log in again.


For LDAP:




4. If you cannot resolve the problem, collect maintenance information, and then contact the Support

Center.

For RADIUS:




Center.

For Kerberos:

1. By using the host and port set in exauth.properties, check whether the authentication server can be accessed, the settings of the external authentication server, and the status of the network.


Center.

For not LDAP, not RADIUS and not

Kerberos:


Log in again.



1-137

1-138

Error Code

KAIC10226-E

KAIC10227-E

KAIC10228-E

KAIC10229-E

KAIC10231-E

KAIC10232-E

KAIC10236-E

KAIC10237-W

KAIC10238-W

KAIC10239-W

KAIC10240-E

KAIC10241-E

KAIC10242-E

KAIC10243-E

KAIC10244-E

KAIC10245-E

KAIC10246-E


The temporary license has expired.

Enter a product license key or a product license key file.

The emergency license has expired.

Enter a product license key or a product license key file.

Enter your license key.

An attempt to get the license information has failed.

This license key is invalid or has already been registered.

Purchase a license.

Enter your license key.


Enter a valid license key.

An attempt to log into Device Manager has failed. Enter the user ID and password.

Log in again.

The host has no copy pair information. Select a host that has one or more copy pairs.

If this operation is performed during

I/O processing on the primary volume, the data of the secondary volume may be corrupted. Make sure that no I/O processing is being performed on the primary volume before you proceed.

Are you sure you want to continue?

An un-recommended value is specified for the copy pace. Make sure the value is correct. Are you sure you want to continue?

Confirm that hosts are not issuing I/Os on any primary volume (P-VOL), and then continue the operation.

For AMS/WMS, Thunder 9500V or

Thunder 9200, set the copy pace for

ShadowImage, TrueCopy and

QuickShadow / COW Snapshot to

Faster 15.

The data in the volume specified to be the secondary volume will be lost as a result of this operation. Please confirm.

World Wide Name or iSCSI Name is not specified.

The name of the storage subsystem is not specified.

Select more than one WWN or iSCSI

Name or WWN group.

The specified parent logical group is invalid.

The host name must be unique.

World Wide Name(s) or iSCSI

Name(s) <World-Wide-Name/iSCSI

Name> is/are already in use by host(s) <host-name>.

<host-name> HORCM <instance-

number> cannot be specified, since it is not set to be managed.

Continuing this operation will delete the data of a volume specified to be a secondary volume. Back up the data if necessary, and then continue the operation.

Enter a World Wide Name or iSCSI

Name.

Enter the name of the storage subsystem.

Select a WWN or iSCSI Name or a

WWN group.

For a parent logical group, do not specify a logical group that will be updated or a child logical group of a logical group that will be updated.

Enter another host name.

Enter another World Wide Name or iSCSI Name.

Enter another instance number.



Error Code

KAIC10247-E

KAIC10248-E

KAIC10249-E

KAIC10250-E

KAIC10251-E

KAIC10252-E

KAIC10253-E

KAIC10254-E

KAIC10255-E

KAIC10256-E

KAIC10257-E

KAIC10258-E

KAIC10260-E

KAIC10263-E

KAIC10264-E

Description

The port number does not match the one already specified for <host-

name> HORCM <instance-number>.

The combination of the HORCM instance and the HORCM port number cannot be changed.

This group name already exists in the host <host-name> HORCM <instance-

number>.

The port number <port-number> is already used in the host <host-

name>.

The same HORCM cannot be specified for both P-VOL and S-VOL.

The same HORCM port cannot be specified for both P-VOL and S-VOL.

The LU <DevNum> cannot be deleted, because it is set as a command device.

The LU <DevNum> cannot be deleted, because it is set as a copy pair.

The LU <DevNum> cannot be deleted from Device Manager.

The LU <DevNum> cannot have a logical group moved.

The storage of another storage subsystem is assigned to the group

<group-name>.

You cannot assign the same security for all the LDEVs that you selected.

The LU <DevNum> cannot be secured with Device Manager.

A request cannot be received. Close the dialog box, and retry the operation. If the problem re-occurs, log in again and retry the operation.

Use numeric characters for the

HORCM instance number.

Use numeric characters for the port number

Secure the LUN from the application attached to the storage subsystem.

Close the dialog and try the operation again.


Select another combination, or create a new combination.

Enter another group name.

Enter another port number.

Enter another HORCM.

Enter another HORCM port.

Cancel the setup of the command device.

Delete a copy pair.

Delete from the application attached to the storage subsystem.

When an expanded LU is made by Disk

Array Management Program 2 with multiple LUs that have been allocated for an LUN, or when LUNs are assigned to LUs except for a MainLU after making the LU expansion, the

LUNs except for the LUNs allocated to the MainLU are also displayed by

Device Manager. In this case Device

Manager cannot operate this type of

LU.

Select another logical group.

Secure the security individually.

Enter a valid instance number.

Enter a valid port number.



1-139

1-140

Error Code

KAIC10265-E

KAIC10266-W

KAIC10267-E

KAIC10268-E

KAIC10269-E

KAIC10270-W

KAIC10271-W

KAIC10272-W

KAIC10273-W

KAIC10274-W


Only alphanumeric characters and symbols can be used in copy pair names and copy group names. Also, '-

' cannot be used at the beginning of a name.

Because LUNs are already assigned to the following combinations of LDEVs and Ports, this operation does NOT assign LUNs to them and does NOT register them to the storage group.

Are you sure you want to continue?

The selected WWN Group is not registered in the selected port. Check the available combinations of

HOST:WWN and PORT.

The selected LU is already allocated to the selected port. Check the available combinations of LU and Port-Host

WWN.

The selected LU is already allocated to the selected Port/HSD(iSCSI Target).


LU and Port-Host WWN/iSCSI Name.

As a result of this operation, data on these volumes will be lost. Are you sure you want to continue?

Confirm that no host and External port is performing I/O processing on any of the LUNs with the PORTs. If I/O processing is being performed, the processing might terminate abnormally. Are you sure you want to continue?

Confirm that no host and External port is performing I/O processing on any of the LUNs with the HSD/iSCSI Target.

If I/O processing is being performed, the processing might terminate abnormally. Are you sure you want to continue?

Confirm that no host and External port is performing I/O processing on any of the LUNs. If I/O processing is being performed, the processing might terminate abnormally. Are you sure you want to continue?

This operation will change the port's

LUN security, which may prevent other hosts and External ports from accessing LUNs with the following ports. Are you sure you want to continue?

Enter a valid pair name.

Enter a valid character string.


HOST:WWN and PORT, and use an available combination.


LU and Port-Host WWN, and use an available combination.


LU and Port-Host WWN/iSCSI, and use an available combination.

Check the contents of the warning and check whether there is an error in the operation.




Error Code

KAIC10275-W

KAIC10276-E

KAIC10277-E

KAIC10278-E

KAIC10279-E

KAIC10281-E

KAIC10282-E

KAIC10284-E

KAIC10285-E

KAIC10286-E

KAIC10287-W

KAIC10288-E

KAIC10289-E

KAIC10290-E

Description

Deleting copy pair volumes or command devices may disable later modification of the copy pair volume settings. Are you sure you want to continue?

The host <host-name> is not a host that can operate copy pairs.


A selected LDEV does not satisfy requirements for the copy pair.

Possible reasons for this error are as follows:

1. A requirement for making a copy pair was not satisfied.

2. An LDEV that meets the requirements for making a copy pair has not been selected.

See "Requirements for copy pairs", and make sure that the copy pair satisfies the necessary requirements for making a copy pair.

Specify a group name.

Specify the <P-VOL or S-VOL> <Item

Name>.

<Name> can only contain numeric characters.

Specify the <name> using a number between <number> and <number>.

A device already allocated to all ports is included.

A WWN group and WWN registered to a WWN group cannot be selected.

The selected WWN is registered to the

WWN group in the selected port.


HOST:WWN and PORT.

The LDEV cannot be specified because an invalid LDEV is selected or multiple

LDEVs are selected. The initial window of Dynamic Link Manager is displayed.

Add a subsystem.

Check the contents of the warning.

A resource group is registered in the specified logical group.

Check the following items:

1. The version of the RAID Manager installed on the host.

2. The version of the host agent installed on the host.

3. A command device is accessible by the host.

Select an LDEV that meets the requirements and execute the process again.

Enter valid characters.

Use numeric characters.

Enter another number.

Select a device that can be allocated.

Select a WWN that is not registered to the selected WWN group.


HOST:WWN and PORT, and use an available combination.

Re-select the LDEV, or select an LDEV in Dynamic Link Manager.

Add a storage subsystem before displaying the report window.

Check the contents of the warning, then select the check box.

Create a new logical group, then add a path in the logical group.



1-141

1-142

Error Code

KAIC10291-E

KAIC10292-E

KAIC10293-E

KAIC10294-E

KAIC10295-E

KAIC10296-E

KAIC10298-E

KAIC10299-E

KAIC10300-E

KAIC10301-E

KAIC10302-E

KAIC10303-E

KAIC10304-E

KAIC10305-E

KAIC10306-W

KAIC10307-E


The operation cannot be continued because no host is registered.

An attempt to perform authentication has failed.

An attempt to start has failed.

Register a host.

Contact the system administrator.

No path is selected.

An LDEV in pool cannot be used for storage allocation.

The LDEV device specified by the

LDEV number <LDEV-number> is part of a pool.

A communication error has occurred.

Open the Tasks menu, and confirm that the operation has finished.

Confirm that you are using a JRE version that is supported for use with

Web Client.

If the error occurs again, contact the system administrator.

Select a path.


Specify the LDEV number of an allocatable device.

An illegal transition was done by user operation.

The session is over. Log out, and then log in again.

The session is invalid. Log out, and then log in again.

All the paths that you have specified already exist. Specify other LDEVs and ports.

In QuickShadow / COW Snapshot, a

Restore operation cannot be performed in a batch for multiple copy pairs with the same P-VOL.

Select the alert to be deleted.

No logical groups are registered. Add a logical group, and then execute the operation.

The storage subsystem "<subsystem-

name>" has two controllers, but only one IP Address was specified. We recommend that you specify another

IP Address by modifying the properties in the Subsystem

Management window.

Enter the appropriate characters as follows: <string>. The maximum text length is <number> characters.

Open the Tasks menu to check if the operation has finished. If this error occurs frequently, contact the system administrator.

Retry the operation.

Log out, and then log in again.

Specify other LDEVs and ports.

Select one copy pair from the copy pairs with the same P-VOL to perform the restore operation.

Select the alert to be deleted.

Add a logical group before executing the operation.

Specify another IP Address by modifying the properties in the

Storage Subsystem Management window.

Check valid characters and text length.



KAIC10319-E

KAIC10320-E

KAIC10321-E

KAIC10322-E

KAIC10323-E

KAIC10324-E

KAIC10325-E

KAIC10326-E

KAIC10327-E

Error Code

KAIC10309-W

KAIC10310-E

KAIC10311-E

KAIC10312-E

KAIC10313-E

KAIC10314-E

KAIC10315-E

KAIC10316-W

KAIC10317-W

KAIC10318-W

Description

Update the current Javascript to the latest version.

Select one or more World Wide

Names.

The selected storage is deleted.

The group name "LUN SCAN" is reserved. Change the group name to execute this operation.

A LUSE cannot be created by mixing an internal volume with an assigned volume of <pp-name>.

All LDEVs in a LUSE must be the same

IO Suppression mode.

All LDEVs in a LUSE must be the same

Cache mode.

A host that corresponds to the

External port of a subsystem cannot be removed.

An assigned volume of <pp-name> may be invalid. Are you sure you want to continue?

An attempt was made to create a

LUSE with multiple external subsystems or an unknown external subsystem. (LDEV = <LDEV-

number>)

Provisioning Manager failed to invoke

Device Manager. (info: <info>)

Provisioning Manager sent an invalid request. (info: <info>)

The license key file that was entered is invalid.

Enter your license key file.

Failed to delete the file.

One or more application files are corrupt.

The license key file exceeds the maximum size.

This license key file is invalid or has already been registered.

All the LU types in a LUSE must be the same.


Install Internet Explorer 6.0 or later version, or you can download the latest JScript from the site below and install it. http://www.microsoft.com/downloads/ details.aspx?displaylang=en&FamilyID

=c717d943-7e4b-4622-86eb-

95a22b832caa

Specify the World Wide Names to delete.

Select another storage.

Change the group name using "Modify

Properties".

Select internal volumes only, or assigned volumes only.

Select LDEVs with the same IO

Suppression mode.

Select LDEVs with the same Cache mode.

A host that corresponds to the

External port of a storage subsystem cannot be removed from the system.

A volume assigned by Universal

Volume Manager may be invalid.

Check the changes.

A LUSE with multiple external subsystems is not recommended.

Select LDEVs with the same external subsystem.


Enter the correct license key file, then retry.

Enter your license key file.

No action is required.

Contact the support center.


Make sure that all the LDEV types are the same.



1-143

1-144

Error Code

KAIC10328-W

KAIC10329-E

KAIC10331-E

KAIC10332-E

KAIC10333-W

KAIC10334-W

KAIC10335-W

KAIC10336-E

KAIC10337-E

KAIC10338-W

KAIC10339-E


Confirm that all hosts have been added into the host view before running a LUN Scan. After LUN Scan,

Device Manager creates new hosts that have WWNs/iSCSI Names associated with the LUNs and have not been added into the Host View. You will need to clean up these hosts after the attributes of them are updated when the Device Manager Agent reports information about them. Are you sure you want to continue?


The formats specified for LDEV attribute condition values do not match.

For >=, specify a value that is less than or equal to the value specified for

<=.

If a storage resource is associated with a different storage resource, a partitioned storage administrator will not be able to manage the storage resource.

If volumes from different cache resources are used to create a LUSE volume, the effectiveness of the cache partition might be reduced.

A LUSE volume that consists of volumes in different cache resources has been selected. This might reduce the effectiveness of the cache partition.

Device Manager has failed to open the

Web browser.

Make sure that the Web browser is running normally.

Make sure that the link to the Web browser is set up correctly.

Device Manager has failed to open the

Web browser.

Make sure that the Web browser is running normally.

Make sure that the path to Internet

Explorer is set up correctly.

An operation was performed while the subsystem was being updated.

The displayed information might not be the latest information.

The subsystem is being updated. After this update processing finishes, retry the operation.

Check all hosts in host view.


Specify the same format for LDEV attribute condition values.

For >=, specify a value that is less than or equal to the value specified for

<=.

Your setting might prevent a partitioned storage administrator from managing the storage resource. Make sure that this setting is appropriate.

Your setting might reduce the effectiveness of the cache partition.

Make sure that this setting is appropriate.

Your setting might reduce the effectiveness of the cache partition.

Make sure that this setting is appropriate.

Make sure that the link to the Web browser is set up correctly.

Make sure that the path to Internet

Explorer is set up correctly.

If a subsystem operation is executed during update processing, the operation might fail. After the update processing finishes, retry the operation.

After the update processing finishes, retry the operation.



Error Code

KAIC10340-E

KAIC10341-E

KAIC10342-E

KAIC10343-E

KAIC10344-E

KAIC10361-E

KAIC10362-E

KAIC10363-E

KAIC10364-E

KAIC10365-E

KAIC10366-E

KAIC10367-E

KAIC10368-E

KAIC10369-W


An attempt to execute license management has failed.

All the LU CLPRs in a LUSE must be the same.

An LDEV in a DM-LU cannot be used for storage allocation.

The LDEV device specified by the

LDEV number <LDEV-number> is part of a DM-LU.

Only a maximum of 128 LDEVs may be configured in a LUSE.

Memory for executing license management may be insufficient on the system running Device Manager.

Please confirm whether the memory is insufficient on the system. If this problem persists, contact customer support.

Make sure that all the LDEV CLPRs are the same.


Specify the LDEV number of an allocatable device.

Select no more than 128 LDEVs.

Enter the host storage domain name. Enter the host storage domain name.

The specified host storage domain name "<host-storage-domain-name>" is not available. This host storage domain name is already used by another host storage domain on the same port.

Change the name of the host storage domain to one that does not exist.

Close the Host Storage Domain Info panel. After the screen has been refreshed, retry the operation.

The operation is not possible because the Host Storage Domain Info panel is open or in the process of closing.

Close the Host Storage Domain Info panel. After the screen has been refreshed, retry the operation.

Link and launch for Storage Navigator

Modular is required for this operation.

Please manually install and configure it according to the instructions in the manual.

To use PhysicalView, a setting for linking with Storage Navigator Modular is necessary. Confirm that the corresponding storage subsystem is correctly registered in Storage

Navigator Modular.

If V-VOL LDEVs are in a LUSE, all

LDEVs must be V-VOL.

Make all the LDEVs either V-VOL

LDEVs or non-V-VOL LDEVs.

Log out, and then log in again. Authentication was refused when logging into the common component.

Log out, and then log in again.


The license that corresponds to the subsystem has not been registered.

Data on the array group <array-

group-number>, which is the target of this operation, will be lost. Make sure that the data is not necessary.


Register the license in the Version

Information of Device Manager panel.

Data on the array group that is the target of this operation will be lost.

Check the data and, if necessary, take a backup, and then continue the operation.



1-145

1-146

Error Code

KAIC10370-W

KAIC10371-W

KAIC10372-W

KAIC10373-I

KAIC10374-I

KAIC10375-I

KAIC10376-I

KAIC10377-E

KAIC10379-E

KAIC10380-E

KAIC10381-E

KAIC10382-E

KAIC10383-E

KAIC10385-E

KAIC10386-E

Description

If the settings for this port are changed, the storage might become inaccessible to the hosts and external ports that are currently accessing the storage.

The system will now be rebooted to apply the settings. I/O requests cannot be received during the reboot.

If the system is being used as an external subsystem, make sure that you execute the Disconnect

Subsystem operation on Storage

Navigator.

Make sure that I/O processing is not being performed from hosts or external ports that are using the port targeted for this operation. Performing this operation while I/O processing is being performed might damage the file system. Also, as a result of this operation, only the hosts and external ports that are set in the host storage domain <name-of-the-host-storage-

domain-ID0> will be able to gain access.

Register the license key.

License registration has finished.

The temporary license will expire in

<n> days on <date>.

The emergency license will expire in

<n> days on <date>.

An attempt to log into Device Manager has failed. For the user, allocate a resource group, and assign a Device

Manager permission other than Peer or assign a user management permission. Then log in again.

All LDEVs in a LUSE must have the same stripe size.

A JavaScript-enabled browser is required.

The temporary license has expired.

The emergency license has expired.

The combination of filter conditions is invalid.

Duplicate resource group names are not allowed.

The resource group was not found in the Device Manager database.


Thoroughly check the settings.

The system will now be rebooted to apply the settings. I/O requests cannot be received during the reboot.

If the system is being used as an external subsystem, make sure that you execute the Disconnect

Subsystem operation on Storage

Navigator.

Make sure that I/O processing is not being performed from hosts or external ports.

Register the license key.


Register the license before the expiration date.

For the user, allocate a resource group, and assign a Device Manager permission other than Peer, or assign a user management permission. Then, log in again.

Make sure all the LDEVs have the same stripe size.


Purchase a license.

If you filter using AND, you can specify no more than 2 LDEV attribute conditions. Each condition must have a different operator. You cannot specify multiple non-LDEV attributes.

Make sure that the resource group name is not a duplicate, then retry.

Make sure that the resource group name exists in the Device Manager database, then retry.



KAIC10391-E

KAIC10392-E

KAIC10393-E

KAIC10394-E

KAIC10395-E

KAIC10396-E

KAIC10397-E

KAIC10398-E

KAIC10399-E

KAIC10400-E

KAIC10401-E

Error Code

KAIC10387-E

KAIC10388-E

KAIC10389-E

KAIC10390-E

KAIC10402-E

KAIC10403-E

KAIC10404-E

KAIC10405-E

KAIC10406-E


The specified resource group cannot be added under this API version.

The specified user cannot be added under this API version.

The specified logical group is already being used by another resource group.

The specified resource group is already associated with another logical group.

A user is already registered in the specified resource group.

A resource group is registered under the specified logical group.

A resource group is registered in the specified logical group.

The logon user cannot modify own resource group and user role.

The resource group name is invalid.

Use name less than 25 bytes.

The built-in resource group cannot be deleted.

The own resource group cannot be deleted.

The built-in resource group cannot be modified.

The own resource group cannot be modified.

The specified group name is reserved.

It cannot be used.

The logon user who does not belong to any resource groups cannot use the function of the Device Manager.

An inconsistency with the common user information about resource group was detected.


Specify another logical group, then retry.

Remove the old association, then retry.

Remove all resource groups under the specified logical group, then retry.

Create a new logical group, and then add a path in the logical group.

Check the logon user authorization, then retry.

The resource group name is invalid.

Use name less than 25 bytes.

Check the resource group.

Try again with the user who can use the function of the Device Manager.

The Common Component may not contain the most current resource group information. Restart the Device

Manager Server.


The specified resource group is not registered in the common user information.

The specified resource group has already been registered in the common user information.

Missing parameter: Resource Group

<name>.

The resource group was not found in the Device Manager database.

The Resource Group "name" is required. Provide the missing parameter, then retry. If this problem persists, contact the Support Center.




1-147

1-148

Error Code

KAIC10407-E

KAIC10408-E

KAIC10410-E

KAIC10411-E

KAIC10412-E

KAIC10413-E

KAIC10414-E

KAIC10415-E

KAIC10416-E

KAIC10417-E

KAIC10418-E

KAIC10419-E

KAIC10420-E


The "group name" is invalid. Specify within 25 characters. Only alphanumeric characters and '-', '=',

'\', '`', ',', '.', '_' are permitted.

The license key that should be entered does not exist in the license key file.

The entered license key file is for another product. Please verify the license key file.

The operation is not possible because the Select WWN/iSCSI Name panel is open or in the process of closing.

Close the Select WWN/iSCSI Name panel and, after the window has been refreshed, retry the operation.

An LDEV selection is invalid. The LDEV

(LDEV number <dev-number>) is reserved as an OnDemand LDEV.

An LDEV selection is invalid. The LDEV

(LDEV number <ldev-number>) is reserved as a Migration LDEV.

An LDEV reserved as an OnDemand

LDEV cannot be used for storage allocation.

An LDEV reserved as a Migration LDEV cannot be used for storage allocation.

An LDEV reserved as an OnDemand

LDEV cannot be specified for a LUSE.

This host name is already used by a mainframe host.

Not all of the selected LDEV paths belong to the same logical group.

Select LDEV paths that belong to the same logical group.

Check the group name.


After the window has been refreshed, retry the operation.

Select a valid LDEV.

Please select an unused host name.

Use the CLI to check which mainframe host names are being used. For details about how to do this, see the CLI manual.

Clear the selection or use the Move

Storage function for the necessary

LDEV paths, so that all selected LDEV paths belong to the same logical group, and then retry the operation.

Some of the selected LDEV paths do not belong to a logical group. Select

LDEV paths that belong to the same logical group.

<number-of-selected-LDEV-paths>

LDEV paths are selected. A maximum of <maximum-number-of-selectable-

LDEV-paths> LDEV paths can be selected for the Add Like Storage function.

<number-of-selected-hosts> hosts are selected. A maximum of

<maximum-number-of-hosts> hosts can be removed.

Select a number of LDEV paths that does not exceed the maximum number of selectable LDEV paths, and then retry the operation.

Select a number of hosts that does not exceed the maximum number of hosts that can be removed, and then retry the operation.



Error Code

KAIC10421-W

KAIC10422-W

KAIC10423-W

KAIC10424-E

KAIC10425-W

KAIC10426-W

KAIC10427-I

KAIC10428-W


The temporary license will expire in

<n> days on <date>. Enter a product license key or a product license key file.

The emergency license will expire in

<n> days on <date>. Enter a product license key or a product license key file.

The copy pair cannot be created because the copy status of multiple copy pairs that use the same P-VOL cannot be specified as "Pair" in this subsystem.

"Restore" or "Resync" cannot be specified for an operation on multiple copy pairs, because the copy status of multiple copy pairs that use the same

P-VOL cannot be specified as "Pair" in the subsystem <subsystem-name>.

The value of the table.ldev.rowsperpage

property could not be acquired because an attempt to read the client.properties

file failed. In this case, the default values (25, 300) will be used for the number of rows displayed for a sortable table.

The value (<set-value>) specified for the table.ldev.rowsperpage

property in the client.properties

file is invalid. In this case, the default values

(25, 300) will be used for the number of rows displayed for a sortable table.

A value (<set-value>) has been specified for table.ldev.rowsperpage


file. <set-value> rows will be displayed for a sortable table.

The table.ldev.rowsperpage

property has not been specified in the client.properties

file. In this case, the default values (25, 300) will be used for the number of rows displayed for a sortable table.

Register the license before the expiration date.

When creating a copy pair, return to the Choose Pair(s) window, and then change the copy pair settings so that the same P-VOL is not used, or change the copy status of the existing copy pair to "Split" or "Simplex".

If changing the copy status for multiple copy pairs that use the same

P-VOL, use only one copy pair for which "Restore" or "Resync" is specified.

Confirm the following to make sure the application program can read the client.properties

file:





The client.properties

file exists.

You have permission to read the client.properties

file.




corrupted.

file is not

For details on the table.ldev.rowsperpage


file, see the

Configuration and Operation Guide.

Specify a valid value for the table.ldev.rowsperpage


file.

For details on this property, see the



Specify a valid value for the table.ldev.rowsperpage


file.





1-149

1-150

Error Code

KAIC10429-E

KAIC10430-E

KAIC10431-W

KAIC10432-W

KAIC10433-W

KAIC10434-I

KAIC10435-I

KAIC10438-E


An attempt was made to allocate

<number-of-LU-Port-Host:WWN-

combinations> LU - Port - Host:

WWN/iSCSI Name combinations. The upper limit for LUNs allocatable in one operation is 100 LUNs.

If you want to allocate more than the upper limit, execute multiple operations.

The user ID or the password is incorrect.

The value of the client.assignlun.upperlimit.enable

d

property could not be acquired because an attempt to read the client.properties

file failed. The default value (true) will be used.

The client.assignlun.upperlimit.enable

d

property has not been specified in the client.properties

file. The default value (true) will be used.

The value (<specified value>) specified for the client.assignlun.upperlimit.enable

d

property in client.properties

is invalid. The default value (true) will be used.


The upper limit can be set or released using the client.assignlun.upperlimit.enable

d


file.



Make sure that the user ID and the password exist.

Confirm the following to make sure the application program can read the client.properties

file:






file exists.

You have permission to read the client.properties

file.




corrupted.

file is not

For details on the client.assignlun.upperlimit.enable

d


file, see the Configuration and

Operation Guide.

Specify a valid value for the client.assignlun.upperlimit.enable

d


file.



Specify a valid value for the client.assignlun.upperlimit.enable

d


file.



No action is required. The client.assignlun.upperlimit.enable

d

property is set to true.

The client.assignlun.upperlimit.enable

d

property is set to false.

An attempt was made to allocate more than <number-of-LU-Port-

Host:WWN-combinations> LU - Port -

Host: WWN/iSCSI Name combinations. The upper limit for

LUNs allocatable in one operation is

100 LUNs.



The upper limit can be set or released using the client.assignlun.upperlimit.enable

d


file.





Error Code

KAIC10439-E

KAIC10440-E

KAIC10441-W

KAIC10442-W

KAIC10443-W

KAIC10444-I

KAIC10445-I

KAIC10446-E

KAIC10447-E

KAIC10448-E

KAIC10449-E

KAIC10450-W

KAIC10451-E

Description

This license key is either invalid or may be for another product.

The last path of an LU of the copy pair volume cannot be released.

The format of the entered capacity is invalid.

The length of the value specified for the capacity is invalid. Specify a character string from 1 to 9 characters.

The value (<specified-value>) specified for the property client.report.csv.format.escaped in the file client.properties is invalid. The default value (<true>) will be used.

The property client.report.csv.format.escaped in the file client.properties is set to true.

The property client.report.csv.format.escaped in the file client.properties is set to false.

The operation is not possible because the Select Journal Group panel is open or in the process of closing. Close the

Select Journal Group panel. After the screen has been refreshed, retry the operation.

The LUN IDs available after the specified first LUN ID are insufficient.

Change the first LUN ID to a smaller number, and try again. (Port (HSD) =

<Port-(HSD)-name>)

The LDEV (number <LDEV-number>) has the <VolumeAttr> attribute.

A path cannot be set for an LDEV that has the <VolumeAttr> attribute.

The search condition specified in [Find

Storage] might not execute correctly because the specified number of

LDEVs exceeds the maximum

(<Number of LDEVs> ) that can be processed at one time. Using [Enter

LDEVs] or [Browse LDEVs], please select a lower number of storage subsystems for the operation.

The number of specified LDEV(s) exceeds the maximum (<maximum-

number-of LDEVs>) that can be specified at once. Divide the operation into two or more operations so that the specified number of LDEVs for each operation does not exceed the above maximum.


Enter a valid license key.

Cancel a copy pair volume and delete a path. For V-VOL, delete the path from Physical View.

Enter the capacity in the correct format.

Specify a valid value for the property client.report.csv.format.escaped in the file client.properties.




Close the Select Journal Group panel.

After the screen refreshes, retry the operation.

The LUN IDs available after the specified first LUN ID are insufficient.

Change the first LUN ID to a smaller number, then retry.

Please select a valid LDEV.

Select a device that can be assigned.

Please select the storage subsystems by using Enter LDEVs or Browse

LDEVs.

If you need to specify a number of

LDEVs that exceeds the maximum for a single operation, divide the operation into several operations.



1-151

1-152

Error Code

KAIC10452-W

KAIC10453-E

KAIC10454-E

KAIC10455-E

KAIC10456-E

KAIC10457-W

KAIC10460-E

KAIC10461-E

KAIC10462-W

KAIC10463-E

KAIC10465-E

KAIC10466-I

KAIC10467-E

KAIC10468-E


The maximum number of search data items that can be displayed has been reached (2048). If required data is not displayed, please divide the operation into several smaller operations.

The storage subsystem information might not be up-to-date. Refresh the storage subsystem information, and then re-execute the operation.

(subsystem: <subsystem-name>)

Enter the iSCSI Target.

The specified iSCSI Target "<iSCSI-

Target>" is not available. This iSCSI

Target is already used by another iSCSI Target on the same port.

If required data is not displayed, please divide the operation into several smaller operations.


If you do not refresh the storage subsystem, you might not be able to operate storage subsystems.

The storage subsystem information might not be up-to-date. Restart the

Device Manager server, and then reexecute the operation.

The format of the entered Consumed

Capacity is invalid.

The length of the value specified for the Consumed Capacity is invalid.

Specify a character string from 1 to 9 characters.

The specified operation cannot be performed because the storage subsystem is not supported by Device

Manager.

The execution for start command of

<command-name> failed.

The execution for stop command of

<command-name> failed.

Restart the Device Manager server, then retry.

If you do not restart the Device

Manager server, the contents displayed in sortable tables might become incorrect.

Enter the Consumed Capacity in the correct format.

Unsupported storage subsystems can only be deleted. Other operations are not supported.

Start the Device Manager Server.

Stop the Device Manager Server.

The number of LDEVs exceeds the maximum (Number of LDEVs) that can be processed at one time. Please change and rerun a search option, or using [Enter LDEVs] or [Browse

LDEVs] and choose storage to operate other LDEV(s).

The operation is not possible because the iSCSI Target Info panel is open or in the process of closing. Close the iSCSI Target Info panel. After the screen has been refreshed, retry the operation.

Please change and rerun a search option, or using Enter LDEVs or

Browse LDEVs and choose storage to operate other LDEV(s).

Close the iSCSI Target Info panel.

After the screen has been refreshed, retry the operation.

The length of the value specified for the array group is invalid. Specify a character string from 1 to 20 characters.

Enter the array group in the correct format.

Core License registration has finished. No action is required.

Enter the iSCSI Target.

Change the name of the iSCSI Target to one that does not exist.



Error Code

KAIC10469-E

KAIC10470-E

KAIC10471-E

KAIC10472-E

KAIC10473-E

KAIC10474-E

KAIC10475-W

KAIC10476-E

KAIC10477-E

KAIC10478-W

KAIC10479-E

KAIC10480-E

KAIC10481-E

KAIC10482-E

KAIC10483-E

KAIC10484-E

KAIC10485-E

KAIC10486-E


Select one or more iSCSI Names.

The specified iSCSI Name is invalid.

The iSCSI Name must be unique.

License registration of Web Client has finished, but there is a possibility that licensing info acquisition handling of

Device Manager Server failed.

There is a possibility that licensing info acquisition handling of Device

Manager Server failed.

An error was encountered during task execution. Please see error code and message below for details. Click the

Back button to modify task parameters, if needed, and re-submit the task for execution.

A LUN exists whose security does not match the security of the host storage domain/iSCSI target.

Different type of A WWN/iSCSI Name and port are selected. Check the available HOST:WWN/iSCSI Name and

PORT combinations.

Paths that have different port types are selected. Select paths that have the same port type.

A path cannot be added because the type of an entered WWN or iSCSI

Name is different from the type of a

WWN or iSCSI Name already set for the host. To add a path to a WWN or iSCSI name, use the Add Storage function.


Specify the iSCSI Names to delete.

Enter a valid iSCSI Name.

Enter another iSCSI Name.

Log in again. If this problem persists, contact the Support Center.

Log in again. If this problem persists, contact the Support Center.

Please see error code and message below for details. Click the Back button to modify task parameters, if needed, and re-submit the task for execution.


Make sure that the combination of

WWN (or iSCSI name) and port is valid.

Select paths that have the same port type.

To add a path to a WWN or iSCSI name, use the Add Storage function.

An error occurred in the Storage

Navigator Modular 2. (error code =

"<error code>")

No usable pools are registered.

The length of the value specified for the host is invalid. Specify a character string by using to 50 characters.

Collect maintenance information, and then contact customer support.


Register a pool.

Enter the host in the correct format.

The format of the host entry is invalid.

The format of the array group entry is invalid.


No mapping path is selected.

No LDEV number is entered. Enter the

LDEV number.

Select at least one mapping path.

Enter the LDEV number.



1-153

1-154

Error Code

KAIC10487-E

KAIC10488-E

KAIC10489-E

KAIC10490-E

KAIC10491-E

KAIC10494-E

KAIC10495-E

KAIC10496-E

KAIC10497-W

KAIC10498-E

KAIC10500-E

KAIC10501-E

KAIC10502-E


The format of the entered LDEV number is invalid. Enter either "Auto" or an LDEV number.

No array group is entered. Enter the array group.

The format of the entered array group is invalid. Enter either "Auto" or a value from 1 to 16384.

Enter the CLPR number.

The format of the entered CLPR number is invalid. Enter a numeric value from 0 to 2147483647.

Duplicate LDEV numbers exist. Please specify a unique LDEV number.

The number of specified LDEVs exceeds 100, the maximum number that can be specified at once. If you want to perform an operation using more than the maximum number of

LDEVs, perform the operation a number of times, specifying a valid number of LDEVs each time.

The number of items selected for the mapping path has exceeded the maximum number of selectable items.

You can specify a maximum of 8 items.

You can combine from 1 to 8 external array nodes and ports. Click the appropriate LDEV number, and then change the number of combinations.

External storage settings cannot be specified for this storage subsystem.

(microcode version = version-number)

An attempt to connect to the database has failed. Make sure the database has been started.

Enter the LDEV number in the correct format.

Enter the array group.


Enter the CLPR number.

Enter the CLPR number in the correct format.

Specify a unique LDEV number.

If you want to perform an operation using more than the maximum number of LDEVs, perform the operation a number of times, specifying a valid number of LDEVs each time.

Change the number of items selected for the mapping path to 8 or fewer.

Click the appropriate LDEV number, and then change the number of combinations.

Select a storage subsystem for which the settings can be specified.

If the database has not been started, re-start it, then retry.

If the database has been started, there might be an internal error.


An attempt to acquire data from the database has failed. Make sure the database has been started. SQL statement: SQL statement

The file could not be opened. Make sure the file/directory access permissions and path name are correct, and that there is enough free space in the filesystem. File name: file

name

Make sure the file/directory access permissions and path name are correct, and that there is enough free space in the filesystem.

If there is not enough free space in the file system, delete any unnecessary files, then retry.



Error Code

KAIC10503-E

KAIC10504-E

KAIC10505-E

KAIC10506-E

KAIC10507-E

KAIC10508-W

KAIC10509-W

KAIC10510-W

KAIC10511-E

KAIC10512-E

KAIC10513-E

KAIC10514-E

KAIC10515-E

KAIC10516-E


An attempt to write the file has failed.

Make sure the file/directory access permissions are correct, and that there is enough free space in the filesystem. File name:file name

An attempt to read the file has failed.

Make sure the file/directory access permissions are correct, and that there is enough free space in the filesystem. File name: file name

An attempt to delete the file has failed. Make sure the file/directory access permissions are correct. File name: file name

The size of the detailed array report is more than 2 gigabytes. Reduce the number of selected storage subsystems, and then try again.

An attempt to perform a cancellation has failed. The status of the detailed array report has already changed to

"error" or "incomplete", or else the detailed array report has already been deleted.

Another request to create a detailed array report is currently being executed. Please wait for a while.

There are too many LDEVs, so it might not be possible to display reports. If they cannot be displayed, use the detailed array report.

After downloading the detailed array report, delete it from the server.

The status of the detailed array report is "incomplete". File name: file name

The detailed array report was deleted.

File name: file name


An attempt to acquire the Storage

Navigator Modular tree information has failed.

There are no available LDEVs.

The specified pool cannot be deleted because a virtual volume is assigned to it.

Make sure the file/directory access permissions are correct to enable the user executing the operation to write the file, then retry.

If there is not enough free space in the file system, delete any unnecessary files, then retry.

Make sure the file/directory access permissions are correct to enable the user executing the operation to read the file, then retry.

Make sure the file/directory access permissions are correct to enable the user executing the operation to delete the file, then retry.

Reduce the number of selected storage subsystems, then retry.

Cancellation can only be performed when the status is "processing". If the status is any other status, cancellation cannot be performed. Close the window, by clicking the close button.

Wait until the status of the detailed array report being processed changes to another status, then retry.

Sometimes HTML output cannot be performed if there are too many

LDEVs. From the report list, use the detailed array report.

The detailed array report is retained on the server even after it is downloaded. We recommend deleting it from the server as soon as possible.

There is a possibility of an internal error. Please contact the Support

Center.

If you need a detailed array report, try the operation again.

Click the [Refresh Tree] button, and then display the navigation area again.


Provide LDEVs which can be registered to the pool.

Delete any virtual volumes assigned to the specified pool.



1-155

1-156

Error Code

KAIC10517-E

KAIC10520-E

KAIC10521-E

KAIC10522-E

KAIC10525-E

KAIC10526-E

KAIC10527-E

KAIC10528-E

KAIC10551-E

KAIC10560-E

KAIC10561-E

KAIC10562-E

KAIC10563-E

KAIC10564-E

KAIC10565-E

KAIC10566-E

Description

A virtual volume cannot be deleted because a path is set to a <PP-name> virtual volume (LDEV number =

<LDEV-number>).

A license for <PP-name> is not registered in the storage subsystem.

There are no available pool IDs.


Check the virtual volume, and then retry the operation.

Install the license for <PP name> into the storage subsystem.

Delete any unnecessary pools, and then retry the operation.

If you want to delete more than the maximum number of pools, execute multiple operations.

An attempt was made to delete

<number-of-pools-selected> pools. A maximum of <set-maximum> pools can be deleted in one operation. If you want to delete more than the maximum number of pools, execute multiple operations.

An attempt was made to delete

<number-of-virtual-volumes-

selected> <PP-name> virtual volumes. A maximum of <set-

maximum> virtual volumes can be deleted in one operation. If you want to delete more than the maximum number of virtual volumes, execute multiple operations

An operation is not possible because the editing window is open or in the process of closing. Close the editing window, wait for the window to be refreshed, and then retry the operation.

Multiple virtual volumes are specified.

Specify only one virtual volume.

All LDEVs registered to a pool must have the same CLPR.

The subsystem managed by the partitioned storage administrator cannot execute the operation.

Two or more LDEVs are selected.

Please select only one LDEV.

Select an LDEV for which you want to create a LUSE.

The total LU size must be less than 60

TB.

A command device LDEV cannot be specified for a LUSE.

An LDEV whose access attribute is guarded cannot be specified for a

LUSE.

An LDEV used as a Pool Volume cannot be specified for a LUSE.

An LDEV used as a Journal Volume cannot be specified for a LUSE.

If you want to delete more than the maximum number of virtual volumes, execute multiple operations.

Close the editing window, wait for the main window to be refreshed, and then retry the operation.

Specify only one virtual volume.

Revise the LDEV specification, and then retry the operation.

Revise the subsystem settings.

More than two LDEVs are selected.

Please select only single LDEV.

Select single LDEV for which you want to create a LUSE.

Specify less than 60 TB for the total

LU size.

Select an LDEV that is not a command device.

Select an LDEV whose access attribute is not guarded.

Select an LDEV that is not a pool volume.

Select an LDEV that is not a journal volume.



Error Code

KAIC10567-E

KAIC10568-E

KAIC10569-E

KAIC10570-E

KAIC10571-E

KAIC10572-E

KAIC10573-W

KAIC10574-E

KAIC10575-E

KAIC10576-E

KAIC10577-W

KAIC10601-E

KAIC10602-E


An LDEV used as a <PP name> virtual volume cannot be specified for a

LUSE.

An LDEV used as a Pair Volume cannot be specified for a LUSE.

An LDEV assigned to a host storage domain whose host mode is "VMware" cannot be specified for a LUSE.

An LDEV assigned to a host storage domain whose host mode is

"Windows" cannot be specified for a

LUSE.

There are no LDEVs that can be used to make a LUSE.

Not all of the selected LDEV paths belong to the same storage subsystem. Select LDEV paths that belong to the same storage subsystem.

As a result of this operation, data on volumes that do not have paths specified (volumes marked with "*" in the Object List) will be lost. Are you sure you want to continue?

Some of the selected LDEV paths are allocated to the same ports,

HSD/iSCSI targets, or hosts. Check the ports, HSD/iSCSI targets, and hosts of these paths.

The microcode version of this storage subsystem does not support LUSE operations on LDEVs that have paths specified.

Some of the selected LDEV paths are allocated to the same ports, WWN, or hosts. Check the ports, WWN, and hosts of these paths.

Before performing this operation, check the settings of the host and host storage domain of the target path. The host might not recognize the expansion of the volume by this operation.

The number of specified LDEVs exceeds (<maximum-number-of-

LDEVs>), the maximum number that can be specified at once. If you want to perform an operation using more than the maximum number of LDEVs, perform the operation a number of times, specifying a valid number of

LDEVs each time.

Use any of the following characters for a label: <string>

Select an LDEV that is not a virtual volume.

Select an LDEV that is not a pair volume.

Select an LDEV that is assigned to a host storage domain whose host mode is not "VMware".

Select an LDEV that is assigned to a host storage domain whose host mode is not "Windows".

Please select an LDEV that can be used to make a LUSE.

Select LDEV paths that belong to the same storage subsystem.


Check the ports, HSD/iSCSI targets, and hosts of these paths.


Check the ports, WWN, and hosts of these paths.

To perform this operation, check the restriction of the host OS and host storage domain of the target path.

For details, see the LUN Expansion manual that corresponds to your storage subsystem.

If you want to perform an operation using more than the maximum number of LDEVs, perform the operation a number of times, specifying a valid number of LDEVs each time.

Enter only valid characters.



1-157

1-158

Error Code

KAIC10603-E

KAIC10604-E

KAIC10607-W

KAIC10608-W

KAIC10609-W

KAIC10610-E

KAIC10611-E

KAIC10612-E

KAIC10613-E

KAIC10614-E

KAIC10615-E

KAIC10616-W

KAIC10617-W

KAIC10618-E

KAIC10619-E

KAIC10620-E

Description

Use no more than <number> characters for a label.

A filter condition that is not compatible with LDEVs has been restored. Change "Not applicable" displayed in the list box to a valid value.

Are you sure you want to add the label to the selected volume(s)?


Enter no more than the allowed maximum number of characters.

Select a correct value from the list.

Are you sure you want to modify the labels for the selected volume(s)?

Are you sure you want to delete the labels from the selected volume(s)?

The storage subsystem configuration information might not be up-to-date.

Check the status of the storage subsystem information.


<Database name>. Call server administrator.

Available storage subsystems do not exist.

Before continuing, make sure that you want to add the label to the selected volume(s).

Before continuing, make sure that you want to modify the labels for the selected volume(s).

Before continuing, make sure that you want to delete the labels from the selected volume(s).

Close this dialog box, and then retry the operation.

A selected LDEV was not found. Close this dialog box, and then retry the operation.

Tiered Storage Manager failed to invoke Device Manager. (info: <info>)

Tiered Storage Manager sent an invalid request. (info: <info>)

Device Manager faild to invoke Tiered

Storage Manager. (info: <info>)

The length of the value specified for the label is invalid. Specify a character string by using to 64 characters.

The length of the value specified for the HSD/iSCSI Target is invalid.

Specify a character string by using to

32 characters.

The storage subsystem configuration information might have been updated.



Enter the label in the correct format.

Enter the HSD/iSCSI Target in the correct format.

Refresh the storage subsystem. If you do not refresh the storage subsystem, you might not be able to perform some operations on it.

Check the status of the storage subsystem.


Software registration managed by the

SMI-S provider might be invalid.

Please retry this action after adding a storage subsystem available for Host

Scan.

Revise the

CIM_RemoteServiceAccessPoint class on the SMI-S provider, refresh the storage subsystem, and then retry the operation.



Error Code

KAIC10621-E

KAIC10622-E

KAIC10623-W

KAIC10624-W

KAIC10625-I

KAIC10626-E

KAIC10627-E

KAIC10628-E

KAIC10629-E

KAIC10630-E

KAIC10631-E

KAIC10633-E

KAIC10634-E

KAIC10635-E

KAIC10637-E


The port number has not been specified.

Specify a valid port number.

The password has not been specified. Specify a valid password.

The client.addstorage.block.per.storage property has not been specified in the client.properties file. The default value

(true) will be used.

The value "specified-value" specified for the client.addstorage.block.per.storage property in the client.properties file is invalid. The default value (true) will be used.

The value "specified-value" has been specified for the client.addstorage.block.per.storage property in the client.properties file.

Specify a valid value for the client.addstorage.block.per.storage property in the client.properties file.

For details on this property, see the "

Configuration and Operation Guide".

Specify a valid value for the client.addstorage.block.per.storage property in the client.properties file.

For details on this property, see the "

Configuration and Operation Guide".


Wait for the user to finish, or for the user to cancel the processing.

This wizard, which is used for adding storage from a selected subsystem, is currently in use by another user. Wait for the user to finish, or for the user to cancel the processing.

All LDEVs registered in a pool must be of the same type.

The port number is invalid. Specify a number from 1 to 65,535.

All LDEVs registered in a pool must be of the same volume class (internal or external).

An attempt to acquire the storage subsystem information has failed.


Specify a number from 1 to 65,535.


Click the [Refresh Tree] button, and then display the screen again. If this problem persists, contact customer support.

Choose a valid WWN/iSCSI name for the host/port.

The HSD/iSCSI target might have been deleted from the selected host/port. Choose a valid WWN/iSCSI name for the host/port.

The license that corresponds to the subsystem has not been registered.

The valid Full License is not registered in Device Manager.

An invalid URL was detected. Confirm that the URL is correct.

{number-of-hosts-selected} hosts are selected. A maximum of {specified-

maximum} hosts can be selected.

Register the license in the dialog box for Device Manager License

Information.

Register the valid Full License in

Device Manager.

Confirm that the URL is correct.

Select no more than <set-maximum> hosts.



1-159

1-160

Error Code

KAIC10639-E

KAIC10640-E

KAIC10641-W

KAIC10642-W

KAIC10643-I

KAIC10647-I

KAIC10650-W

KAIC10651-E

KAIC10652-W

KAIC10657-E

KAIC10659-W


{number of WWNs/iSCSI names

selected} WWNs/iSCSI names are selected. A maximum of {specified-

maximum} WWNs/iSCSI names can be selected.

There are no hosts available to be merged.

The client.ldev.rowsperpage.retain.enabled property has not been specified in the client.properties file. The default value

(true) will be used.

The value (<specified-value>) specified for the client.ldev.rowsperpage.retain.enabled property in the client.properties file is invalid. The default value (true) will be used.

Select no more than <specified-

maximum> WWNs/iSCSI names.

Register the hosts that you want to merge, and then retry the operation.

Specify a valid value for the client.ldev.rowsperpage.retain.enabled property in the client.properties file.


Hitachi Device Manager and

Provisioning Manager Server

Installation and Configuration Guide.

Specify a valid value for the client.ldev.rowsperpage.retain.enabled property in the client.properties file.


Hitachi Device Manager and

Provisioning Manager Server

Installation and Configuration Guide.

No action is required. The value (<spedified-value>) has been specified for the <property-key> property in the client.properties file.

The capacity is currently within the licensed limit.

The capacity has exceeded the licensed limit.

An attempt to read properties in the

<property-file> file has failed. The default value (<default-value>) for

<property-key> will be used.



An attempt to read properties in the

<property-file> file has failed. The default value (<default-value>) for

<property-key> will be used.

A parameter for connecting to the specified storage subsystem (the IP address or the communication protocol) has been changed in Storage

Navigator Modular 2. From Storage

Navigator Modular 2, note the IP address and communication protocol, and then add the storage subsystem.

One or more host mode options supported by the storage subsystem could not be acquired.

Confirm the following to make sure the application program can read the file:







The file exists.

You have permission to read the file.

The file is not corrupted.

Confirm the following to make sure the application program can read the file:







The file exists.

You have permission to read the file.

The file is not corrupted.

From Storage Navigator Modular 2, note the IP address and communication protocol of the specified storage subsystem. After that, from the [Add Subsystem] dialog box in Device Manager, specify the same IP address and communication protocol, and then add the subsystem.




Error Code

KAIC10660-W

KAIC10661-E

KAIC10662-E

KAIC10663-E

KAIC10664-E

KAIC10665-E

KAIC10666-W

KAIC10667-E

KAIC10668-E


An operation was performed while the host was being updated.

The displayed information might not be the latest.

The host information might not be the latest. Check the status of the host.

An error occurred during a task. For details, see the error code and message below. Close the window, and then retry the operation.

The virtualization server or the virtualization-server management program could not be detected. The wrong IP address or protocol might have been specified, or the virtualization server or the virtualization-server management program might not be in a normal state.

The format of the IP address is invalid. Enter an IP address in one of the following formats:

- xxx.xxx.xxx.xxx (where xxx is a decimal integer from 0 to 255)

- yyyy:yyyy:yyyy:yyyy:yyyy:yyyy:yyyy

:yyyy (where yyyy is a hexadecimal integer from 0 to ffff).

The total LU size must be less than

128 TB.

Some virtual machine names could not be displayed because information on some virtual machines could not be acquired. Check the status of the virtual machines.

An error occurred in the processing of the Storage Navigator Modular 2 session. (Process status code from

<Process status code0> to <Process

status code1>.)

The pool (pool ID: pool number) might not be in the Normal status.

Threshold1 can be modified only when the pool is in the Normal status.

Refresh the storage subsystem information, and then check the status of the pool.

An operation might fail if it is executed on a host that is being updated. Wait until the update has finished, and then retry the operation.

Refresh the host, and then try again.

If you do not refresh the host, you might not be able to execute operations on the host.

For details, see the error code and message below. Close the window, and then retry the operation.

Depending on the cause, take either or both of the following actions:





Revise the IP address or protocol specification.

Correct the state of the virtualization server or the virtualization-server management program.

Enter an IP address in one of the following formats:

- xxx.xxx.xxx.xxx (where xxx is a decimal integer from 0 to 255)

- yyyy:yyyy:yyyy:yyyy:yyyy:yyyy:yyyy

:yyyy (where yyyy is a hexadecimal integer from 0 to ffff).

Specify less than 128 TB for the total

LU size.

Some virtual machine names could not be displayed because information on some virtual machines could not be acquired. Check the status of the virtual machines.


If you cannot resolve the problem, collect maintenance information, and then contact the Support Center.

Refresh the storage subsystem information, and then check the status of the pool.



1-161

Error Code

KAIC11999-E

Description

Memory might be insufficient or a network error might have occurred.

(details: <info>)


If the details or log contains the character string "Out Of Memory", memory is insufficient. In this case, set the memory heap size for HBase

Storage Mgmt Web Service.

If the details or log contains the character string "Connection", a network error might have occurred. In this case, check the network status.

If the problem is other than the above, contact the Support Center.



Device Manager Agent Messages

When an error occurs, Device Manager Agent produces one or more error messages. An error message consists of a message number, a level code indicating the severity of the error, and the error message text. Message numbers are grouped by error type. If you run Device Manager Agent in an

English environment, some messages are output in English, using the same meaning and error codes as for Japanese messages.

Device Manager Agent messages are written to a secondary output device in the following format:

revision-level / timestamp / message-text

revision-level indicates an internal revision number of the program. This information is required when an error is reported to the Hitachi Data

Systems Support Center.

timestamp, although subject to the local time zone, is always in the same format in other respects. In other words, there are no locality-specific format differences in a timestamp.

message-text begins with a message number followed by one of the following message levels indicating the severity:

–

I: Non-error information

–

W: Warning

– E: Error

Table 1-14 and Table 1-15 list the Hitachi Device Manager Agent error

messages and provide the recommended action for resolving the error conditions. The error messages are listed in numerical order by error code.

Table 1-14 KAIC20000-KAIC23999, KAIC25000-KAIC29999: Hitachi

Device Manager Agent Errors

Error Code

KAIC21901-E

KAIC21902-E

Description

server.properties was not found. server.properties could not be read.


The server.properties

does not exist.

file

Make sure that server.properties

exists, and that it is well-formed.

The server.properties

could not be read.

file

Make sure that server.properties

exists, and then re-execute the operation as a user with

Administrator permissions.



1-163

1-164

Error Code

KAIC21907-E

KAIC21908-E

KAIC21909-E

KAIC21910-E

KAIC22001-E

KAIC22003-E


server.properties could not be saved.

An attempt to save the server.properties

file has failed.

Make sure that the installation of Device Manager agent terminated correctly, and that the disk is not full.

The configuration of HiScan event could not be saved. The registration command returned exit code {code}.

Too many arguments have been specified.

Attempt to save the configuration of the HiScan event has failed.

Check the system configuration.

The hdvmagt_account arguments. command was executed with

Execute this command with no parameters.

Unable to change server.properties because Add-On module is currently running.

This usage is incorrect:

{<explanation > <summary of

correct usage>}

The hdvmagt_account command was executed while an add-on module on a

Device Manager agent was running.

After the add-on module processing finishes, reexecute the hdvamgt_account command.

An attempt was made to execute

HiScan parameters.

with invalid

Execute

HiScan

with the correct parameters.

An error occurred while executing the

HiScan command.

Respond as indicated in the message following

DoScan:

.

DoScan: Disk drive not found on this host


HiScan command.

Consult your system administrator. Ensure that all

Hitachi or Sun disks are online.


HiScan command.

Respond as indicated in the message following

DoEmit:

.



Error Code

KAIC22005-E

KAIC22006-E

KAIC22007-E

KAIC22008-E

KAIC22009-E

Description

The output file could not be opened.({Exception information})

The IPAddress [{IPAddress}] could not be resolved.

The server socket could not be opened. ({Exception information})

A connection could not be established.

An HTTP/XML message could not be sent. ({Exception

information},Content-

Length=Transmission length)


An attempt to create a log file that was specified with the

-t parameter has failed.

Ensure that the path used in the

-t

parameter exists, the filename is valid for this operating system, and that there is sufficient space on the disk.

An attempt to resolve the IP address of the Device

Manager server has failed.

Make sure that the IP address of the Device Manager server is correct.

An attempt to communicate with the Device Manager server has failed.

Make sure that the Windows

OS and TCP/IP protocol stack are correctly installed.


Make sure that the

-s parameter is specified correctly (both the server address and port number are correct), and the specified

Device Manager server is active.


Make sure that the network connection is operating reliably.

Make sure that the server.http.entity.maxLeng

th

property in the server.properties

file of the

Device Manager server is larger than Content-Length.



1-165

1-166

Error Code

KAIC22010-E

KAIC22011-E

KAIC22012-E

KAIC22013-E

Description

The server response could not be received. ({Exception




There was no response from the Device Manager server.

The Device Manager server is probably not working correctly.

Make sure that the value of the

-s

parameter indicates a

Device Manager server, and not another network server type.

Make sure that the network connection is operating reliably.


th


file of the


A connection to the Device Manager server was established, but no response was detected. ({Exception



The correct response header could not be acquired: HTTP/1.0.

Received:({Received contents})

The status code of the HTTP response is not "OK": ({Response contents})

Make sure that the value of IP

Address of the Device

Manager server specified in -s parameter or server.server.serverIPAddr

ess

property is correct, and the port of the Device

Manager server specified in

-s parameter or server.server.serverPort

property is correct (It is corresponding to server.server.serverPort

property of the Device

Manager server), the Device

Manager server works normally, and the network is normal.


The details portion of this message should indicate the nature of the problem. This kind of condition may be due to an invalid combination of

u

userid and

-p

password parameters.



Error Code

KAIC22014-E

KAIC22018-E

KAIC22019-E

KAIC22020-E

KAIC22047-E


HiScan could not connect to Device

Manager server because of a connection timeout.

Information about the installed plugin could not be acquired.({Exception

information})

The "hldutil" response timeout.

The executable program "hldutil" does not exist.({Exception information})

An attempt to authenticate a user ID and password has failed. : {status

code}

Communication with the

Device Manager server terminated because of a timeout monitored by Device

Manager agent.

Revise the server.http.server.timeOut

value in the Device Manager agent properties.


th


file of the


The installation status is incorrect.

The installation of Device

Manager agent or Dynamic

Link Manager may have terminated abnormally.

Consult your system administrator.

An abnormal situation may have occurred during execution of the hldutil command, or a timeout may have occurred in the hldutil command due to an excessive number of LUs.

Make sure that the host is detecting LUs correctly. If necessary, revise the value of server.util.processTimeOut

property.

If the problem cannot be resolved, consult your system administrator.

An attempt to execute the hldutil

command has failed.

The installation of Device

Manager agent may have terminated abnormally.

Consult your system administrator.

The specified user ID and password are invalid.

Execute the hdvmagt_account command to check the user

ID and password.



1-167

1-168

Error Code

KAIC22048-E

KAIC22049-E

KAIC22050-E

KAIC22051-E

KAIC22401-W

KAIC22801-I

KAIC22802-I

KAIC22803-I

KAIC22804-I

KAIC22805-I

KAIC22806-I


The data in the request was rejected because the data is too large. :

{status code}

The value of an argument in the specified option is invalid. : {option}

A site-local address or link-local address cannot be specified.

({address})

An attempt to resolve the host IP address failed.

The command prompt was not started by the administrator.

Although processing is executing properly, the started command prompt will be closed after processing ends.

The HiScan command will now start to send an XML document to the

Device Manager server at {IP-

ADDRESS}:{PORT-

NUMBER}(Content-


The HiScan command has finished sending an XML document to the


ADDRESS}:{PORT-NUMBER}

The HiScan command is receiving an

XML document from the Device

Manager server at { IP-ADDRESS }:{

PORT-NUMBER }

The HiScan command has finished receiving an XML document from the


ADDRESS}:{PORT-NUMBER}

The HiScan command will now start to acquire HostVolume information.

The HiScan command has finished acquiring HostVolume information.

No additional action is required.

The Device Manager server's processing capacity was exceeded because the data in the request is too large.

Revise the value of the Device

Manager server property server.http.entity.maxLeng

th

.

The character that cannot be used for the argument of the option is specified.

Specify the character string that can be used for the argument of the option.

A site-local address or linklocal address is specified in an option. To use IPv6 addresses, you must specify a global address.

Check, and if necessary, revise the value set for server.http.socket.agentAddre

ss in server.properties.

If this error occurs repeatedly, contact the

Support Center.

Execute this command as the administrator.



Error Code Description Recommended Action

KAIC25105-W

You can not select this destination folder. Recommended folder is under

"Program Files (x86)".

KAIC25107-W You cannot cancel this installation operation: [type of installation]

KAIC25111-W (Windows)

The Device Manager agent installation has been suspended due to requests received from a management server.

Please wait a moment and then click

Retry to attempt the installation again, or click Cancel to end the

Device Manager agent installation.

(UNIX)

The Device Manager agent installation has been suspended due to requests received from a management server.

Please wait a moment and enter (Y)es to attempt the installation again or enter (N)o to end the Device Manager agent installation.


The Device Manager agent installation has been suspended due to the execution of the one of the following commands:

(hbsasrv, hdvmagt_account, hdvmagt_schedule, hdvmagt_setting,

TIC, hldutil).


Retry to attempt the installation again, or click Cancel to end the

Device Manager agent installation.

(UNIX)

The Device Manager agent installation has been suspended due to the execution of the one of the following commands:


TIC, hldutil).


You have specified "

Program

Files

" folder to install Device

Manager agent when you try to install it to the IA64 platform.

Please install it under

"

Program File (x86)

" folder as far as possible.


The installation was canceled because the Device Manager agent was being accessed from outside.

Wait a while, and then retry the installation. If you want to immediately stop the Device

Manager agent, see the explanation of the hbsasrv command in the Device

Manager agent manual.

The installation was canceled because the Device Manager agent command is executing.



1-169



The Device Manager agent installation has been suspended because the

HiScan command is executing.

Please wait a moment and click Retry to attempt the installation again, or click Cancel to end the Device

Manager agent installation.

(UNIX)

The Device Manager agent installation has been suspended because the

HiScan command is executing.



The Device Manager agent uninstallation has been suspended due to requests received from a management server.


Retry to attempt the uninstallation again, or click Cancel to end the

Device Manager agent uninstallation.

(UNIX)

The Device Manager agent uninstallation has been suspended due to requests received from a management server.


The installation was canceled because the HiScan command is executing.

The uninstallation was canceled because the Device

Manager agent was being accessed from outside.

Wait a while, and then retry the uninstallation. If you want to immediately stop the

Device Manager agent, see the explanation of the hbsasrv command in the Device






The Device Manager agent uninstallation has been suspended because one of the following commands is executing:


TIC, hldutil)




(UNIX)

The Device Manager agent uninstallation has been suspended because one of the following commands is executing:


TIC, hldutil)



The Device Manager agent uninstallation has been suspended because the HiScan command is executing.




(UNIX)

The Device Manager agent uninstallation has been suspended because the HiScan command is executing.


The uninstallation was canceled because the Device

Manager agent command is executing.

Wait a while, then retry the uninstallation.

The uninstallation was canceled because the HiScan command is executing.

Wait a while, and then retry the uninstallation.



1-171

Error Code

KAIC25120-W

KAIC25121-W

KAIC25122-W

Description

User account authentication has failed. Revise the user account information.

The specified user account does not have Administrators permissions.

Revise the user account information.

The specified user account does not have the User Rights Assignment setting "Log on as a service". Make sure the user account has this setting.


Possible causes are as follows:



The specified user account

(user ID) does not exist.



The password for the user account was specified incorrectly.

Check the following points, and then click the [Next] button in the Setting Up the

Agent Service Account window:



Make sure that the specified user account exists.



Make sure that the password for the user account is specified correctly.

The specified user account does not have Administrators permissions.

Make sure that the user performing the installation has Administrators permissions, and then click the [Next] button in the

Setting Up the Agent Service

Account window.

The User Rights Assignment setting "Log on as a service" has not been specified for the specified user account.

Make sure that the User

Rights Assignment setting

"Log on as a service" has been specified for the user performing the installation, and then again click the

[Next] button in the Setting

Up the Agent Service Account window.



Error Code

KAIC25123-W

KAIC25156-E

KAIC25157-E

KAIC25163-E

KAIC25172-E

Description

An error occurred during setup of the agent service account.


An unexpected error occurred during user account authentication.

In the Setting Up the Agent

Service Account window, click the [Next] button again.

If you cannot resolve the problem, do not set up the agent service account (select

[NO] in the Setting Up the

Agent Service Account window), and then click the

[Next] button in that window.

After the installation, open the Services window from

[Administrative Tools], and then change the account for

[HBsA Service].

Install Device Manager agent to execute the setup.exe.

Installation FAILED. Please execute setup.exe to install Device Manager agent.

There is not enough free disk space for installation. Make sure that there is enough free space on the system drive and installation drive.

Installation will now stop.

A newer version of Device Manager agent is already installed on this system. You cannot downgrade

Device Manager agent.

Installation or uninstallation was stopped because an error occurred in the JVM.

Make sure that there is enough free space, and then try installing again.


A prerequisite patch might not have been applied.

Alternatively, if you are using

Unix, the Java information in the properties file used by the

Device Manager agent might not be valid.



Make sure that all prerequisite patches have been applied.For details on the prerequisite patches, see the Device Manager agent manual.



If you are using Unix, make sure the Java information specified in the properties file used by the

Device Manager agent is valid.

If the Java information is invalid, specify the correct

Java information in the properties file, and then reinstall the Device Manager agent.For details on the properties file, see the Device




1-173

1-174

Error Code

KAIC25173-E

KAIC25174-E

KAIC25176-E

KAIC25177-E

KAIC25178-E

KAIC25179-E

KAIC25180-E

KAIC25181-E

KAIC25183-E


Program aborted. Wait a while, and restart this procedure.

This environment is a non-global zone. Installation in a non-global zone is not supported.

An unexpected error occurred during setup processing of the Device

Manager agent.

The installation or uninstallation was executed while the Device Manager agent was running.

Wait a while, and then reexecute.

Please execute the installation in a global zone.

An illegal option is specified.

{specified option}

The mistake is found in the number of arguments. {specified number}

The installation path of the Device

Manager agent cannot be acquired.

It failed in the installation of add-on module. {add-on module name}

It failed in the installation of

Protection Manager.

The user is not the root user.

The setup program could not be executed.

Collect maintenance information and contact the

Support Center.

An invalid option is specified in the installation command or uninstallation command.

Check the syntax, specify the option correctly, and then execute the installation command or uninstallation command again.

The number of arguments in the installation command or uninstallation command is invalid.

Check the syntax, specify the arguments correctly, and then execute the installation command or uninstallation command again.

An attempt to acquire the installation path of the Device

Manager agent has failed.


Support Center.

An unexpected error occurred during installation of the addon module.


Support Center.

An attempt to copy the

Protection Manager files has failed.

Execute hptmguiinst.exe or hptmguiinst.sh, and then take action based on the output error message.

Perform the installation as the root user.



Error Code

KAIC25184-E

KAIC25185-E

KAIC25186-E

KAIC25188-E

Description

A file required for installation of the

Device Manager agent is missing.

No usable JDK or JRE exists. Install a

JDK or JRE, and then retry the operation.

Your user group permissions are not

Administrators permissions.

A fatal error occurred during the installation of the Device Manager agent. Installation will now stop.


A file required for the installation is missing.

Make sure that all files required for the installation exist.

No prerequisite Java version is installed in the system.

Install a prerequisite Java version, and then retry the operation.

Perform installation as a user who has Administrators permissions.




Installation files of the

Device Manager agent could not be copied to a working directory.





Installation files of the

Device Manager agent could not be deleted from a working directory

Collect maintenance information, and then contact the Support

Center.



1-175

Error Code

KAIC25189-E

Description

Installation of the Device Manager agent has FAILED.


Installation of the Device

Manager agent has failed.

Possible causes include the following:





Installation information of a past Device Manager agent or of a past Dynamic

Link Manager still remains.

There is not enough space at the specified installation destination.

Check the following and, if necessary, carry out the recommended action. Then try to install the Device

Manager agent again. If you cannot resolve the problem, collect maintenance information, and then contact the Support Center.



HBase Agent is displayed twice in the Add or

Remove Programs window on a computer where the

Device Manager agent or

Dynamic Link Manager is installed. Alternatively,

HBase Agent is displayed in the Add or Remove

Programs window on a computer where both the

Device Manager agent and

Dynamic Link Manager have been uninstalled. In either of the above cases, execute the hbsa_util command, and then delete the Device Manager agent registry and files. For details on this command, see the Device Manager agent manual.



Make sure that there is enough free space on the disk where the Device

Manager agent is to be installed.



Error Code

KAIC25190-E

KAIC25193-E

KAIC25194-E

KAIC25197-E

KAIC25198-E


Installation of the Device Manager agent was completed, but the setup of the Device Manager agent or a related program has FAILED.

If you want to use the related program for which setup did not finish, reinstall the Device Manager agent.

If you will not use the related program for which setup did not finish, no additional action is required.

The execute permission for the installation files could not be changed.

An attempt to open the

'HDVMAgent_conf file name' file has

FAILED.

The format of line %d in the

'HDVMAgent_conf file name' is invalid.

A property in the 'HDVMAgent_conf

file name' has been incorrectly specified(line %d).




Setup of the Device

Manager agent failed.









Setup of the Protection

Manager linkage function failed.

Setup of the Dynamic Link

Manager linkage function failed.

Setup of the account information for the Device

Manager agent service

(HBsA Service) failed.

Installation of the Global

Link Manager agent failed.

If you want to use the related program for which setup did not finish, reinstall the Device

Manager agent.

If you will not use the related program for which setup did not finish, no additional action is required.

The execute permission for the installation files could not be changed.

Put the installation files into a directory that can be written to.

An attempt to open the

'HDVMAgent_conf file name' file has failed.

The HDVMAgent.conf file was not found in the directory that contains the installer. Make sure that the file is there, and then try to install the Device

Manager Agent again.

The format of the

HDVMAgent.conf file is invalid.

The HDVMAgent.conf file might be corrupted. Check the file, and then try to install the Device Manager Agent again.

A property in the

HDVMAgent.conf file has been incorrectly specified(line %d).

The HDVMAgent.conf file might be corrupted. Check the file, and then try to install the Device Manager Agent again.



1-177

1-178

Error Code

KAIC25208-E

KAIC28201-W

KAIC28202-W

KAIC28203-W

KAIC28204-W


Setup of the Device Manager agent has FAILED.

The IP address could not be resolved from the specified hostname.

Access to the server has failed. (detail

= "Verify network connectivity and that the Device Manager server is running")

The setup program could not be executed.

Follow the instructions in the following messages:

KAIC25029-I, KAIC25033-I.







Make sure that the entered value is correct.

Make sure that the hostname is defined in the hosts file.

To specify an IPv6 address, server.agent.JRE.location must be specified. Make sure that the specified value is correct.












Check the firewall settings on the machines on both the host side and the server side.

If a firewall is configured between the host and the server, make sure that the settings are correct.

If you want to install the

Device Manager server later, click No in the confirmation window, and then continue setup.



Access to the server has failed. (detail

= "Unauthorized user ID or password is invalid")

Access to the server has failed.

(details = "A normal response could not be recieved from the Device

Manager server.")









Check the status of the

Device Manager server. If the server is in the process of starting, wait a while, and then retry the operation.

If the problem cannot be solved, collect maintenance information and contact the

Support Center.



Error Code Description


RAID Manager is not installed on the selected drive. (specified drive:

\HORCM)

(UNIX)

RAID Manager is not installed in the selected directory.


If you want to install RAID

Manager later, click [NO] in the confirmation window, and then continue setup.

(Windows)

Make sure that RAID

Manager is installed on the specified drive.

(UNIX)

Make sure that RAID

Manager is installed in the specified directory.



1-179

Error Code

KAIC28305-E

KAIC28306-E

KAIC28307-E

KAIC28308-E

KAIC28309-E

KAIC28310-E

KAIC28311-E

KAIC28312-E

KAIC28313-E

KAIC28314-E

Description

The specified IP address or hostname is invalid.

The specified port number is invalid.

The specified User ID is invalid.

The specified password is invalid.

The IP address or hostname contains invalid characters.

Check the value and enter again.

Refer to the Device Manager agent manual for characters you can use.

The user ID contains invalid characters.



The password contains invalid characters.



An unexpected error occurred when the Device Manager server information was being specified.

The server information cannot be specified.

An I/O error occurred when the

Device Manager server information was being specified.

The server information cannot be specified.

An unexpected error occurred when the execution period of the HiScan command was being specified.

The execution period of the HiScan command cannot be specified.


Enter a valid value.


Support Center.





Make sure that the server.properties file exists, and you have write permissions for the file.

Make sure that there is enough free space on the disk.


Support Center.



Error Code

KAIC28315-E

KAIC28316-E

KAIC28317-E

KAIC28318-E

KAIC28319-E

KAIC28353-E

KAIC28615-W

Description

An I/O error occurred when the execution period of the HiScan command was being specified.

The execution period of the HiScan command cannot be specified.

An unexpected error occurred when

RAID Manager settings were being specified.

These RAID Manager settings cannot be specified.

An I/O error occurred when RAID

Manager settings were being specified.

These RAID Manager settings cannot be specified.





Make sure that the server.properties file exists, and that you have write permissions for the file.



Support Center.

A fatal error occurred during the setup processing of the Device

Manager agent.

Setup processing has stopped.

A site-local address or link-local address is specified for the IP address. To use IPv6 addresses, you must specify a global address.

Setup processing has stopped because the Add-On module is currently running.

The host does not recognize the defined command device.








Make sure that the directories shown below exist, and you have write permissions for the files.

Windows:

Device-Manager-agentinstallation-

directory\mod\hdvm\config

UNIX platforms except

AIX:

/opt/HDVM/HBaseAgent/m od/hdvm/config

AIX:

/usr/HDVM/HBaseAgent/m od/hdvm/config


Make sure that the crontab or at command can be used.


Support Center.

Please specify a global address.

Wait a while, then retry the operation.





Make sure that the description of the command device is correct.

Make sure that the connection status between the host and the storage subsystem is correct.



1-181

1-182

Error Code

KAIC28616-W

KAIC28804-E

KAIC28805-E

KAIC28807-E

KAIC28809-E

KAIC28810-E

Description

No command device recognized by the host is defined.

No command device is defined in the configuration file.

An I/O error occurred while reading the configuration file.

The processing was interrupted because no handle could be acquired from RMLIB.

The file perf_cmddev.properties was not found.

An I/O error occurred. <filename>

(Error details: errno = error-code, msg = error-message)






Add the specified command device to the properties file.

Update the file perf_cmddev.properties by using the following command: perf_findcmdev write

Define the command devices by using the perf_findcmddev command.

An I/O error occurred while reading the perf_cmddev.properties file.

Make sure of the following:





The perf_cmddev.properties file exists.

The perf_cmddev.properties file is readable.

If the perf_cmddev.properties file does not exist, create the file by using the perf_findcmddev command.

The RMILIB API became unusable during request processing.

If the problem occurs frequently, collect maintenance information and contact the support center.

Make sure that the file perf_cmddev.properties exists and is valid.







Make sure that the file perf_cmddev.properties exists and is not writeprotected.


Make sure that the directory to which the file will be written exists.



Table 1-15 KAIE00000-KAIE69999: Agent Errors (used by all Hitachi

Storage Command Suite products)

Error Code

KAIE10401-E

KAIE10403-E

KAIE10404-E

KAIE10502-E

KAIE10602-E

KAIE10606-E

KAIE10610-E

KAIE16002-I

KAIE16605-I

KAIE16606-I

Error Message

A serious error was detected during one of the following processes:



Installation or uninstallation



Addon-module loading



Request reception

There might be a memory shortage or an internal error.

An error occurred when loading a module. There might be a memory shortage or an internal error.

An I/O error occurred.

An attempt to access the following files has failed:





Device Manager agentinstallation-

directory/agent/mod/*


directory/agent/mod/*/var

The service might not have permission to access these files or directories.

The environment is invalid. An attempt to read the product information file (Device Manager

agent-installation-

directory/etc/amc_iid) has failed.

The installation might not have finished correctly.

The environment is invalid.


Make sure that there are no memory shortages, and then restart the service. If this does not resolve the problem, collect maintenance information and contact the Support Center.

Make sure that the user who is executing the service has permission to access these files or directories. If the user does not have permission, grant permission, or change to a user who has permission.

Re-install. If this does not resolve the problem collect maintenance information and contact the

Support Center.

An I/O error occurred. An attempt to generate the product information file

(Device Manager agent-installation-

directory/etc/amc_iid) has failed.

The installation might not have finished correctly.

An attempt to uninstall failed. The module has been used.

The detail of the error information is output.

There are no registered add-on modules or there are no usable registered add-on modules.

The specified add-on module is not registered, or it is registered but is currently disabled.

For appropriate action, see the past operating log message containing details about the problem.

Re-install. If this does not resolve the problem collect maintenance information and contact the

Support Center.

Re-uninstall after a while.

For appropriate action, see the content of exception information.


When using a specified add-on module, make sure that the specified add-on module is installed and is supported on this platform.



1-183

1-184

Error Code

KAIE20001-E

KAIE20002-E

KAIE20101-E

KAIE20102-E

KAIE20303-E

KAIE20402-E

KAIE20403-E

KAIE20601-E

KAIE20701-E


A serious error was detected during one of the following processes:





Addon-module loading

Request reception


A serious error was detected during service execution. There might be a memory shortage or an internal error.

An unexpected error occurred during processing of the request. There might be a memory shortage or an internal error.



A serious error was detected during service execution. There might be a network error or a memory shortage.


Make sure that there are no network errors or memory shortages, and then restart the service. If this does not resolve the problem, collect maintenance information and contact the

Support Center.

An unexpected error occurred during

HTTP connection processing. There might be a network error or a memory shortage.

An I/O error occurred while communicating with the remote host. The remote host might have severed the connection, or there might be a network error or memory shortage.

An unexpected error occurred during processing of the service request.


An error occurred while creating the log output destination directory. The service might not have write permissions for the following directory:

Device Manager agent-installation-

directory/agent

If it was not a normal disconnection by the remote host, make sure that there are no network errors or memory shortages, and then restart the service. If this does not resolve the problem, collect maintenance information and contact the Support Center.


Make sure that the user who is executing the service has permission to access these files or directories. If the user does not have permission, grant permission, or change to a user who has permission.



Error Code

KAIE20702-E

KAIE20703-E

KAIE20704-E

KAIE20705-E

KAIE20706-E

Error Message

An error occurred while creating the log output destination directory. A file which has the same name


directory/agent/logs) already exists.

The log output destination directory


directory/agent/logs) is read-only.

An attempt to access the log property file (Device Manager agent-

installation-

directory/agent/config/logger.propert

ies) has failed. Possible causes are:





The file does not exist.

The user has the file open.





The user lacks access permissions.

The settings are invalid.


Delete the file which has the same name as the directory.

Make the log output destination directory writable.









Make sure that the logger.properties file exists.

If the logger.properties file is open, close it.

Grant access permissions for the logger.properties file, or change to a user who has access permissions and restart the service.

Check the settings of the logger.properties file. If they are invalid, correct them.

Delete the directory which has the same name as the log output file.

The log output file cannot be created. A directory which has the same name as a log output file

(below) exists in the log output destination directory.




directory/agent/logs/trace.log




directory/agent/logs/access.log






directory/agent/logs/error.log


directory/agent/logs/service.log

One of the following log output files is not writable because the user who is executing the service does not have write permissions for that file:




directory/agent/logs/trace.log




directory/agent/logs/access.log






directory/agent/logs/error.log


directory/agent/logs/service.log

Grant write permissions for the log output file, or change to a user who has write permissions and restart the service.



1-185

1-186

Error Code

KAIE20707-E

KAIE20901-E

KAIE20902-E

KAIE20903-E

KAIE20904-E

KAIE21701-W

KAIE21702-W

KAIE21703-W

Error Message

There is an error in the settings of the property file

( server.properties

).

An unrecoverable error occurred in the service execution process. There might be a memory shortage or an internal error.

A network error occurred while waiting for a connection. There might be a network error or a memory shortage.

An unexpected error occurred in the service execution process. There might be a memory shortage or an internal error.

An error occurred during shutdown of the service execution process.


Check each value of the server.properties

property and correct them if necessary.



If the following properties are specified in the properties file, revise the specification: server.http.socket.agentAddr

ess

 server.http.socket.bindAddre

ss


Make sure that there are no network errors or memory shortages. If the problem occurs frequently, collect maintenance information and contact the

Support Center.

Make sure that there are no network errors or memory shortages, and then restart the service. If this does not resolve the problem, collect maintenance information and contact the

Support Center.

Make sure that there are no network errors or memory shortages. If this does not resolve the problem, collect maintenance information and contact the

Support Center.

Correct the value for logger.MaxBackupIndex, then restart the service.

The value for the property logger.MaxBackupIndex in logger.properties is outside the range from 1 to 20, or it is not a number.

The value for the property logger.MaxFileSize in logger.properties is outside the range from 512 KB to 32 MB, or it is not a number.

There is an error in the settings of the property file

( server.properties

).

Correct the value for logger.MaxFileSize, then restart the service.

Check each value of the server.properties

property and correct them if necessary.



Error Code

KAIE30101-E

KAIE30201-E

KAIE30504-E

KAIE30505-E

KAIE30506-E

KAIE30507-E

Error Message





An unexpected error occurred during execution of the service control process stop command. There might be a memory shortage or an internal error.

The service execution process could not start because the environment is invalid.

The service execution process detected an unexpected error. There might be a memory shortage or an internal error.

A communication error occurred during the execution of "hbsasrv stop". Possible causes are:





The service control process cannot receive commands because of a problem such as a system resource shortage.

The service control process is not working correctly.

Make sure that there are no memory shortages, and then retry a forced termination of the service.

If this does not resolve the problem, collect maintenance information and contact the

Support Center.

For details on the appropriate action, see the preceding message that gives details about the problem.


Re-execute "hbsasrv stop".

If the above actions do not resolve the problem, collect maintenance information and contact the

Support Center.



1-187

1-188

Error Code

KAIE60607-E

KAIE62001-I

KAIE62601-E

KAIE62602-E

KAIE62604-E

KAIE62605-E

Error Message

Processing has stopped because the current user is different from the previous installer.

HBsA Service is already running.

Permission of HBsA Service was denied.

The directory structure is invalid.

Unable to stop HBsA Service because

Add-On module is currently running.

The connection error of HBsA Service has occurred.


Processing can no longer continue because the current user ID is different than the user ID who last installed Dynamic Link Manager or

Device Manage agent.

Follow steps 1-3 of the procedure written below. If this problem persists, contact the Support

Center.

1. If Dynamic Link Manager 5.8.0-

00 to earlier than 5.9.4-00 has been installed:Retry as the same user ID who previously installed

Dynamic Link Manager.

2. If Device Manager agent 5.0.0-

00 to earlier than 5.9.0-00 has been installed:Retry as the same user ID who previously installed

Device Manager agent.

3. In situations other than the above:First retry installation as the user ID who previously installed Dynamic Link Manager

5.8.0-00 to earlier than 5.9.4-00 and Device Manager agent

5.0.0-00 to earlier than 5.9.0-

00.

Only one instance of HBsA Service can run on a system at any given time.

A user without Administrator permissions executed the command. Execute this command as a user with Administrator permissions.

Device Manager agent was not installed correctly. Make sure that installation of Device Manager agent was performed correctly.

Wait a while, and then retry the operation. For details on how to stop the service, see the explanation of the hbsasrv command.

Make sure that the TCP/IP environment on the host is normal.

To do this, use the standard OS commands for network monitoring

(such as netstat or ping.).

If there is no problem, restart the system and then re-install the program. If the problem persists, collect the maintenance information and contact the Support Center.



Error Code

KAIE62606-E

KAIE62607-E

KAIE62608-E

KAIE62638-E

KAIE62639-E

KAIE65601-E

Error Message

An error occurred while starting

HBsA Service.

The HBsA service could not start normally.

The Java path is invalid. [{path}]


Re-install the program. If the problem persists, collect the maintenance information and contact the Support Center.

Make sure that the prerequisite patches have been applied, and then re-install the program.

Revise the value specified for server.agent.JRE.location in server.properties, and then retry the operation.

Correct the value for server.agent.maxMemorySize, and then restart the HBsA service.

The value specified for server.agent.maxMemorySize in the server.properties file is not numeric.

The value specified for server.agent.maxMemorySize in the server.properties file is outside the valid range.

The command was executed by a user other than the administrator.





1-189

Device Manager Agent's Provisioning Manager Messages

This section describes the messages output by the Provisioning Manager support functionality of the Device Manager agent and the actions to take in response to these messages.

Table 1-16 lists the error messages related to the Provisioning Manager

support functionality of the Device manager agent, and provides recommended actions sfor resolving the error conditions. The error messages are listed in numerical order by error code. For details on the Provisioning

Manager messages (error codes starting with KARF) that are not listed in Table

1-16, see the Provisioning Manager message manual.

Table 1-16 Device Manager Agent's Provisioning Manager Messages

Error Code

KARF62001-E

KARF62002-E

KARF62003-E

KARF62004-E

Error Message

The specified volume manager type is not supported.

The specified device file does not exist.

The specified device file is not mounted.

A file or directory (folder) exists in the specified mount point directory.

Cause and Action

Cause:

The Agent information recognized by the Provisioning Manager server has not been updated.

Action:

Refresh the host information, and then retry the operation.

Cause:

The host information recognized by the

Provisioning Manager server has not been updated.

Action:


Cause:



Action:


Cause:

The Agent information recognized by the Provisioning Manager server has not been updated, or the requested operation is invalid in the host's system configuration.

Action:

Refresh the host information, and then retry the operation. Alternatively, depending on the contents of the error message, revise the host status, remove the cause of the error, and then retry the operation.



Error Code

KARF62007-E

KARF62008-E

KARF62010-E

KARF62011-E

KARF62012-E

Error Message

The specified device file is already being used.

A mount point exists in the specified mount point.

The specified extension size is invalid.

The specified logical volume does not exist.

The specified mount point is already in use.


Cause:



Action:


Cause:


Action:

Depending on the contents of the error message, revise the host status, remove the cause of the error, and then retry the operation.

Cause:


Provisioning Manager server has not been updated, or processing might have been performed for the same resource.

Action:


Cause:



Action:


Cause:


Action:




1-191

1-192

Error Code

KARF62014-E

KARF62015-E

KARF62018-E

KARF62023-E

KARF62024-E

Error Message

The specified mount point does not exist.

The specified mount point is a file.

A mount point cannot be created.

The logical volume name is invalid.

A process using the specified file system exists.


Cause:



Action:


Cause:

The requested operation is invalid in the host's system configuration.

Action:


Cause:

The directory specified as the mount point might be in one of the following states:

A file that has the same name as the specified directory exists.

The specified directory already exists and a file exists under that directory.

The specified directory already exists and that directory is mounted.

Action:

Update the host information. Search for and delete the device files that were generated while the file system was being added, remove the cause of the error, and then retry the operation to add the file system.

Cause:

The request was made with an invalid value.

Action:

Acquire the error information for

Provisioning Manager and Device

Manager, and then contact the Support

Center.

Cause:


Action:




Error Code

KARF62025-E

KARF62026-E

KARF62027-E

KARF62028-E

KARF62029-E

KARF63002-E

Error Message

2 or more logical volumes are on the specified disk.

A file system that has multiple device files mounted cannot be modified or deleted.

There is a snapshot volume for the specified logical volume.

The specified logical volume is a snapshot.

A file system that has been mounted on multiple mount points cannot be modified or deleted.



Cause:



Action:


Cause:

Multiple device files have been mounted on the specified mount point.

Action:

Check the host status, revise the mount setting to the specified mount point, and then retry the operation.

Cause:


Provisioning Manager server has not been updated. The operation cannot be executed because there is a snapshot volume for the specified logical volume.

Action:

Refresh the host information.

Cause:


Provisioning Manager server has not been updated. The operation cannot be executed because the specified logical volume is a snapshot.

Action:


Cause:

There are mount points, other than the specified mount point, that the same device file has been mounted on.

Action:

Check the host status, revise the mount setting to the specified mount point, and then retry the operation.

Cause:



Action:




1-193

1-194

Error Code

KARF63003-E

KARF64001-E

KARF64003-E

KARF64004-E

KARF64005-I

KARF64006-E

Error Message

The specified physical volume does not exist.

A logical volume already exists on the specified physical volume.

Logical volumes or physical volumes exist in the specified volume group.

A mount point exists on the specified drive.

The logical volume name will be handled as '*'.

The physical volume name is invalid.


Cause:



Action:


Cause:



Action:


Cause:


Provisioning Manager server has not been updated, or there is an unnecessary logical volume or physical volume in the specified volume group.

Action:

No action is required because recovery is performed internally in Provisioning

Manager.

Cause:



Action:


Cause:

-

Action:


Cause:


Action:




Center.



Error Code

KARF64007-E

KARF64008-E

KARF64009-E

KARF64010-E

KARF64011-E

KARF64012-E

Error Message

The specified logical volume already exists.


The specified logical volume size is invalid.

The specified physical volume is already in use.


The specified volume group already exists.


Cause:



Action:


Manager.

Cause:



Action:


Cause:



Action:


Cause:


Provisioning Manager server has not been updated. Or the requested operation is invalid to a host's system configuration.

Action:


Cause:



Action:


Cause:


Provisioning Manager server has not been updated, or the requested operation is invalid in the host's system configuration.

Action:


Manager.



1-195

1-196

Error Code

KARF64013-E

KARF64014-E

KARF64015-E

KARF64017-W

KARF64018-W

KARF64019-W

Error Message

The specified volume group does not exist.

A logical volume cannot be created on the specified device file.

The information relating to the volume group cannot be acquired.

Importing to the specified disk was unnecessary.

The specified disk was already

Basic.

The specified disk was already

Dynamic.


Cause:



Action:


Cause:


Provisioning Manager server has not been updated. Or the device may not be correctly recognized on the host.

Action:


Cause:

The host's application (VxVM) settings are incorrect.

Action:

Revise the host's application (VxVM) settings, remove the cause of the error, and then retry the operation.

Cause:

The disk was already recognized by the host.

Action:

There is no problem in operation, so processing will continue. No action is required.

Cause:

The disk was already a Basic disk.

Action:


Cause:

The disk was already a Dynamic disk.

Action:




Error Code

KARF64020-E

KARF64021-E

KARF64022-E

KARF64023-E

KARF64024-W

KARF64025-E

Error Message

The logical volume name is invalid.

The specified logical volume is still being used.

You cannot use the

DeleteVolumeGroup API to delete a volume group that contains 2 or more physical volumes.

You cannot use the

DeletePhysicalVolume API to delete a physical volume from a volume group that contains only 1 physical volume.

The logical volume Logical

volume name journal log cannot be deleted because it is being used.

The specified disk has an error status.


Cause:


Action:




Center.

Cause:



Action:


Cause:


Provisioning Manager server has not been updated. Or processing may have been performed to the same resource.

Action:


Cause:


Provisioning Manager server has not been updated. Or processing may have been performed to the same resource.

Action:


Cause:

The logical volume was not deleted because it is being used as a journal log.

Action:


Cause:

A setup of a host's application (VxVM or

Dynamic Link Manager) is inaccurate.

Or the requested operation is invalid to a host's system configuration.

Action:

Depending on the contents of the error message, revise the host status and application (VxVM or Dynamic Link

Manager) settings, remove the cause of the error, and then retry the operation.



1-197

1-198

Error Code

KARF64026-E

KARF64027-E

KARF64028-E

KARF64029-E

KARF64031-E

KARF64032-E

KARF64033-E

Error Message

2 or more logical volumes are on the specified disk.

The specified logical volume has a snapshot.

The specified logical volume is a snapshot.

A partition cannot be specified for the device file.

One or more physical volumes other than an md device exist in the specified volume group.

The md device has been created with multiple device files.

The specified HDLM path is not in the Online status.


Cause:



Action:


Cause:


Provisioning Manager server has not been updated. The operation cannot be executed because there is a snapshot volume for the specified logical volume.

Action:


Cause:


Provisioning Manager server has not been updated. The operation cannot be executed because the specified logical volume is a snapshot.

Action:


Cause:


Action:


Cause:



Action:


Cause:



Action:


Cause:

An error might have occurred in the

HDLM path.

Action:

See the Dynamic Link Manager manual, remove the cause of the error, and then retry the operation.



Error Code

KARF64034-E

KARF64035-E

KARF64036-E

KARF64037-E

Error Message

An attempt to create a directory for the volume group has failed. (directory =

directory)

A group file cannot be created because the maximum value of the minor number exceeds the system limit.

The specified logical volume is being used by the cluster software.

The specified logical volume has been marked as part of a high-availability cluster.


Cause:


Provisioning Manager server has not been updated, or the requested operation is invalid in the host's system configuration.

Action:


Cause:

The maximum value of the minor number exceeds the system limit (FF).

Action:

Delete any unnecessary group files, and then retry the operation.

Cause:

Provisioning Manager cannot be used to operate a logical volume that is being used by the cluster software.

Action:

Manually perform the following procedure, and then retry the operation:

Edit the cluster configuration file.

Execute cmapplyconf

.

Cause:

Provisioning Manager cannot be used to operate a logical volume that is being used by the cluster software.

Action:

Manually perform the following procedure, and then retry the operation:

Execute the vgchange -a n

command to deactivate the volume group.

Execute the vgchange -c n

command to remove the high-availability cluster mark.

Execute the vgchange -a y

command to activate the volume group.




1-199

1-200

Error Code

KARF64038-E

KARF64039-E

KARF64040-E

KARF65001-E

KARF65002-E

Error Message

The cluster configuration of the host is invalid.

An attempt to delete the directory for the created volume group has failed.

(directory name = directory)

A partitioned disk cannot be used.

The specified raw device does not exist.

An HDLM device corresponding to the specified device does not exist.


Cause:

There is an inconsistency between the host cluster configuration and cluster configuration file.

Action:

Refer to the Serviceguard manual to check the contents of the cluster configuration file. If necessary, check the cluster system status, remove the inconsistency between the host cluster configuration and cluster configuration file, and then retry the operation.

Cause:

Rollback processing has failed.

Action:

Delete the directory that was output in the message.

Cause:

The specified disk includes one or more partitions.

Action:

If the partitions are not in use, unpartition the disk, and then retry the operation.

Cause:

The specified raw device is not correctly recognized as a device file on the host.

Action:

Make the specified raw device recognizable as a device file, and then resume processing.

Cause:

An attempt to create an HDLM device might have failed. Alternatively, an attempt to either recognize the LU specified by the request or create a device file might have failed.

Action:

Refresh the host information to check whether the specified LU appears. If it does not appear, make the host recognize the LU, create an HDLM device, and then retry the operation.

For details on how to make a host recognize an HDLM device, see the

Dynamic Link Manager manual.



Error Code

KARF65003-E

KARF65011-W

KARF65012-I

KARF65013-E

KARF65014-E

KARF66001-E

KARF66002-E

Error Message

The HDLM path is invalid.


The cfgmgr command will be executed number of command

execution times.

The specified raw device still exists.

An unnecessary device file exists.

VolumeManagerAdmin execution error.

FileSystemAdmin execution error.


Cause:

The host's application (Dynamic Link

Manager) settings are incorrect, or the requested operation is invalid in the host's system configuration.

Action:

Depending on the contents of the error message, revise the host status and application (Dynamic Link Manager) settings, remove the cause of the error, and then retry the operation.

Cause:



Action:


Cause:

-

Action:


Cause:

The specified raw device was not correctly deleted from the host.

Action:

Delete the specified raw device from the host, and then resume processing.

Cause:

The specified raw device was not correctly deleted from the host.

Action:

Delete the specified raw device from the host, and then resume processing.

Cause:

An unexpected internal error occurred.

Action:




Center.

Cause:


Action:




Center.



1-201

1-202

Error Code

KARF66003-E

KARF66004-E

KARF66005-E

KARF66006-E

KARF66007-E

KARF66008-E

KARF66009-E

Error Message

RawDeviceAdmin execution error.

The specified volume manager type is not supported.

The specified file system type is not supported.


The raw device cannot be deleted because there is a partition in the raw device.

The specified mount point

(mount-point) is invalid.

An md device already exists on the specified device file.


Cause:


Action:




Center.

Cause:


Action:


Cause:


Action:


Cause:

The specified raw device is not correctly recognized as a device file on the host.

Action:

Make the specified raw device recognizable as a device file, and then resume processing.

Cause:

Partitions exist on the specified raw device.

Action:

Delete all partitions in the raw device if they are not being used, and then retry the operation.

Cause:

The mount point included at least one invalid character.

Action:

You cannot use Provisioning Manager to add, expand or delete the specified file system. Manually add, expand or delete it, and then refresh the host information.

Cause:

An unsupported device file was specified.

Action:

Delete the md device, and then retry the operation.



Error Code

KARF66010-E

KARF66011-E

KARF66012-E

KARF67001-E

KARF67002-E

KARF70001-E

Error Message Cause and Action

The specified logical volume cannot be deleted because its path length exceeds 32 characters.

An attempt to create a device file for the specified volume group has failed. (volume group = Volume group name)

An attempt to create a device file for the specified logical volume has failed. (volume group = Volume group name, logical volume = Logical

volume name)

The md device cannot be created because a system limit was exceeded.

Cause:

The path length of the specified logical volume exceeds 32 characters.

Action:

The specified logical volume cannot be deleted.

Cause:

A device file already exists for the specified volume group, or a file with the same name already exists.

Action:

Specify a different volume group name, and then retry the operation.

Cause:

A device file already exists for the specified logical volume, or a file with the same name already exists.

Action:

After manually deleting the created volume group, specify a different logical volume name, and then retry the operation.

Cause:

The number of md devices exceeded a system limit.

Action:

Delete an unnecessary md device, and then retry the operation.


Cause:



Action:

Refresh the host information, and then retry the operation. processing Cause:


Action:




Center.

Exception occurred = class

name

Cause:


Action:




Center.



1-203

1-204

Error Code

KARF70002-E

KARF70003-I

Error Message

The specified parameter is invalid.

Execution command =

command, startTime =

command start time.

KARF70004-E Command execution error =

command

KARF70005-E Program Product is not installed.

KARF70006-E Program Product is not supported.

KARF70007-W An attempt to delete the file has failed. (file name = file

name)

KARF70008-E The specified parameter is invalid.


Cause:


Action:




Center.

Cause:

-

Action:


Cause:

A command execution error occurred.

Action:

Depending on the contents of the error message, revise the host status and application settings, remove the cause of the error, and then retry the operation.

Cause:


Action:


Cause:


Action:


Cause:

An attempt to delete the file indicated in this message has failed.

Action:


Cause:

The hldutil command returned an unexpected execution result.

Action:




Center.



Error Code

KARF70009-E

KARF70010-W

KARF70012-I

KARF70013-I

KARF70014-E

KARF70015-E

KARF70016-E

Error Message

The specified parameter length is invalid.

Command execution error =

Command execution result

Waiting wait time seconds before starting the next command.

Command execution result =

command execution result, endTime = command end

time.

The execution result of the command is invalid.

The specified entry already exists in Definition file.

The specified mount point does not exist in Definition file.


Cause:

The hldutil command returned an unexpected execution result.

Action:




Center.

Cause:

A nonfatal error occurred during command execution.

Action:


Cause:

-

Action:


Cause:

-

Action:


Cause:

The command returned an unexpected execution result.

Action:




Center.

Cause:


Action:


Cause:


Action:




1-205

1-206

Error Code

KARF70017-E

KARF70018-E

KARF70019-E

KARF70020-E

KARF70021-E

KARF70022-W

Error Message Cause and Action

Definition file cannot be backed up.

Definition file cannot be read.

The entry cannot be removed from Definition file.

Definition file cannot be updated.

The system environment is invalid. (value = An unjust

value)

An attempt to set the value for

Key Name has failed. The default value default Value will be used.

Cause:


Action:


Cause:


Action:


Cause:


Action:


Cause:


Action:


Cause:

The host's configuration system or the application (whole) settings are incorrect. Alternatively, the requested operation is invalid in the host's system configuration.

Action:

Depending on the contents of the error message, revise the host status and application settings, remove the cause of the error, and then retry the operation.

Cause:

An invalid value exists in the settings file.

Action:

Revise the settings file.



Error Code

KARF70023-E

KARF70024-E

KARF70025-E

KARF70026-W

KARF70027-W

KARF70028-W

KARF70029-E

Error Message

The specified entry does not exist in Definition file.

An error occurred because an invalid value was detected.

(attribute = method name, value = Invalid value)

The command results do not contain a value that matches

missing Value.

The default value default Value will be used because the value

specified Value is invalid.

The number value value that corresponds to Header Name could not be acquired from the command execution results.

The object object does not exist. new object will now be created.

A directory exists that has the same name as the backup file.

(directory = directory)


Cause:

The system configuration of the host is incorrect, or the requested operation is invalid in the system configuration of the host.

Action:


Cause:


Action:




Center.

Cause:


Action:


Cause:

Processing will continue, ignoring the invalid value that was returned.

Action:


Cause:

Processing will continue, ignoring the unexpected value returned as the command execution result.

Action:


Cause:

A nonfatal error occurred.

Action:


Cause:

Processing could not continue because a directory that has the same name exists.

Action:




1-207

Error Code

KARF70030-I

KARF70031-E

Error Message

The value that corresponds to

Header name is acquired.

(value = value)

Command output message (

message )


Cause:

-

Action:


Cause:

The cause depends on the error that occurred.

Action:

Depending on the contents of the message, revise the host status and application settings, remove the cause of the error, and then retry the operation.



Device Manager Agent's Replication Manager Messages

This section describes the messages output by the Replication Manager support functionality of the Device Manager agent and the actions to take in response to these messages.

Table 1-17 lists the error messages related to the Replication Manager support

functionality of the Device Manager agent, and provides recommended actions for resolving the error conditions. The error messages are listed in numerical order by error code.

Table 1-17 Error Codes KAVN01800-KAVN01813: Device Manager Agent's

Replication Manager Messages

Error Code

KAVN01800-I

KAVN01801-I

KAVN01802-I

KAVN01803-I

KAVN01804-E


The CCI instance has stopped successfully.

Cause:

The CCI instance (HORCM instance) has stopped successfully.

Action:


The CCI instance has started. Cause:


Action:


The CCI instance has already stopped.

The CCI instance has stopped.

An error occurred while acquiring the status of the

CCI instance.

Cause:


Action:


Cause:

The CCI instance (HORCM instance) has stopped.

Action:


Cause:

An attempt to acquire the CCI instance

(HORCM instance) status has failed.

Action:

Check the status of CCI, and then correct the problem. Then, retry the operation.



1-209

1-210

Error Code

KAVN01805-E

KAVN01806-E

KAVN01807-E

KAVN01808-I

KAVN01809-I

KAVN01810-E

KAVN01811-E


A supported version of CCI was not found.

CCI was not found.

An argument other than "stop" has been specified.

Collection of maintenance information from the

Replication Manager agent will now start.

Collection of maintenance information from the

Replication Manager agent has ended.

Cause:

The prerequisite version of CCI for

Replication Manager was not found.

Action:

Install the prerequisite version of CCI for Replication Manager, and then retry the operation.

Cause:

CCI is not installed.

Action:

Install the prerequisite version of CCI for Replication Manager, and then retry the operation.

Cause:

An argument other than the -stop is specified on the command line.

Action:

Check the argument, and then reexecute the command.

Cause:

The collection of maintenance information from the Replication

Manager agent has started.

Action:


Cause:

The collection of maintenance information from the Replication

Manager agent has ended.


An argument is not specified. Cause:

The hrpm_getras command was executed without specifying an argument (the output directory).

Action:

Specify an argument (the output directory), and then execute the hrpm_getras command.

The directory specified as an argument of the

TIC command of the Device

Manager agent cannot be accessed

Cause:

The directory specified as an argument of the hrpm_getras command cannot be accessed.

Action:

Check whether the directory specified as an argument exists and whether access permission is granted for the user, and then retry the operation.



Error Code

KAVN01812-E

KAVN01813-E

Description

An error occurred during collection of maintenance information from the

Replication Manager agent.

The specified parameter value is invalid.


Cause:


TIC

command of the Device Manager agent during the collection of maintenance information from the Replication Manager agent.

Action:

Re-execute the

TIC

command of the

Device Manager agent. If the error occurs again, change the value of the argument, and then re-execute the command. If the problem cannot be corrected, contact the Support Center.

Cause:

Multiple arguments are specified, or the argument is specified incorrectly.

Action:

Specify a single argument, and then reexecute the

TIC

command of the Device

Manager agent. If the error still occurs, change the value of the argument, and then re-execute the command. If the problem cannot be corrected, contact the Support Center.



1-211

Device Manager VDS Provider Messages

When an error occurs, Device Manager VDS Provider produces one or more error messages. An error message consists of a message number, a level code indicating the severity of the error, and the error message text. Message numbers are grouped by error type. If you run Device Manager Agent in an

English environment, some messages are output in English, although they share the same meaning, as well as the same error codes, as the Japanese messages.

Device Manager VDS Provider messages are written to a secondary output device in the following format:

revision-level / timestamp / message-text

revision-level indicates an internal revision number of the program. This information is required when an error is reported to the Hitachi Data Systems

Support Center.

timestamp, although subject to the local time zone, is always in the same format in other respects. In other words, there are no locality-specific format differences in a timestamp.

message-text begins with a message number followed by one of the following message levels indicating the severity:

–

–

I

: non-error information

W

: warning

–

E

: error

Table 1-18 lists the Hitachi Device Manager VDS Provider error messages, and

provides recommended actions for resolving the error conditions. The error messages are listed in numerical order by error code.

Table 1-18 KAIC24000-KAIC24999: Hitachi Device Manager VDS Provider

Errors

Error Code

KAIC24001-E

KAIC24017-E

KAIC24054-E

Description

An attempt to create a thread has failed.

An attempt to allocate a buffer for

CHdvmComm failed due to lack of memory.

The CIM operation failed.

(<detailed-message>)



Please add more memory.

An attempt to communicate with the

Device Manager server has failed. The details portion of this message should indicate the nature of the problem. Revise the Device Manager VDS provider properties.



Error Code

KAIC24063-E

KAIC24065-E

KAIC24123-E

KAIC24124-E

KAIC24125-E

KAIC24126-E

KAIC24132-E

KAIC24133-E

KAIC24140-E

KAIC24141-E

KAIC24142-E

KAIC24805-E

Description

Communication with the Device

Manager server failed.

This application runs on Windows

Server 2003 only. Installation will now stop.

Please enter the IP address <IP-

address>.





Device Manager server has failed. Revise the server.ipaddress

value in the file vds.properties

.

The Device Manager VDS provider can run on Windows Server 2003 only. Please install it on Windows Server 2003.

The IP address is incorrect. Specify the correct IP address.

The user ID contains an invalid character or is too long. Specify the correct user ID.

The password contains an invalid character or is too long. Specify the correct password.

The port number is incorrect. Enter the port address of the CIM HTTP protocol, set for the Device Manager server.

The Device Manager VDS provider cannot be started from the command line. Start

Device Manager VDS Provider as a

Windows service.

Please enter the Device Manager server port address <port-

address>.

You cannot start the file hdvmprovider.exe from the command line. Device Manager VDS

Provider must be started as the service.

You cannot start the file xxxx from the command line. The file yyyy must be executed.

xxxx: Internal file

yyyy: Error information batch collection tool ( hdvmgetlogs.bat)

An attempt to open a log file has failed.

An attempt to write to the log file has failed.

An attempt to back up a log file has failed.

You do not have the permissions required to run this program.

This command cannot be started alone.

Execute the command shown by yyyy.

If the log directory (

<

installationdirectory

>\logs

) does not exist, re-install the VDS provider.

Make sure the Read-only check box is not selected for the log file and the log directory.

Free up disk space by deleting any unnecessary files.

Make sure the Read-only check box is not selected for the backup file.

Execute the command as a user who has

OS Administrator permissions.



1-213

Device Manager CLI Messages

When an error occurs, Device Manager CLI produces one or more error messages. An error message consists of a message number and the error message text.

For details on the log files to which the CLI error messages are output, see the

Device Manager CLI manual.

Table 1-19 lists the Device Manager CLI error messages, and provides

recommended actions for resolving the error conditions. The error messages are listed in numerical order by error code.

Table 1-19 Device Manager CLI Errors

Error Code

KAIC00000-E

KAIC90000-E

KAIC90001-E

KAIC90002-E

KAIC90003-E

KAIC90004-E

KAIC90005-E

KAIC90006-E

KAIC90007-E

KAIC90008-E

KAIC90009-E

KAIC90010-E

Description

Unknown

An internal error occurred in CLI.

Malformed key/value pair: specified-

key-value (must be in the form key=value)

Malformed parameter key:

specified-key-value (must be in the form key=value)

Malformed parameter value:

specified-key-value (must be in the form key=value)

An argument is required for the option specified-option

The option "specified-option" is not valid

Value of key-name must be an integer; could not parse specified-

value

An invalid value "parameter-value" has been specified for parameter

"parameter-name".


"parameter-name".

"LogicalUnit" must be specified in parameter "error-parameter-name" before using parameter "related-

parameter-name".


"parameter-name".










Error Code

KAIC90011-E

KAIC90012-E

KAIC90013-E

KAIC90014-E

KAIC90015-E

KAIC90016-E

KAIC90017-E

KAIC90018-E

KAIC90019-E

KAIC90020-E

KAIC90021-E

KAIC90022-E

KAIC90023-E

KAIC90024-E

KAIC90025-E

KAIC90026-E

KAIC90027-E

KAIC90028-E


Value of channelspeed must be an integer. You entered "specified-

value".

Cannot query Logical Group for contained elements of type

"element-type"

Model = model-name not supported.

Parameter "wwn" must have at least two WWNs.

The list element element-name could not be added to the Host as a

WWN

If either serial number or model is specified for an array, both must be specified

Value of devnums must be a positive integer. You entered

"specified-devnums-value".

Value of devnum must be a positive integer. You entered "specified-

devnum-value".

Could not translate to a WWN from

wwn-string: detail-message

There is no way to make a WWN for

"management-object".

The object type cannot be determined.

The specified object is not a path.


"parameter-name".

"parameter-name" must be specified in parameter "relation-

paramater-name(1)" before using parameter "relation-paramater-

name(2)".

Cannot query parameter-name without relation-paramater-name(1) in relation-paramater-name(2)

"model-name" is not a model name recognized by Device Manager CLI.

The model does not support the command "specified-command".

Modifying Option Definitions while parsing is illegal






If the problem persists, contact the

Support Center.



1-215

1-216

Error Code

KAIC90029-E

KAIC90030-E

KAIC90031-E

KAIC90032-E

KAIC90033-E

KAIC90034-E

KAIC90035-E

KAIC90036-E

KAIC90037-E

KAIC90038-E

KAIC90039-E

KAIC90040-E

KAIC90041-E

KAIC90042-E

KAIC90046-E

KAIC90047-E

KAIC90048-E

KAIC90049-E

KAIC90050-E

KAIC90051-E


Option already defined using character "define-option-character"

- existing-option-name; cannot define option define-option-name

Option already defined long option

"define-option-name" - existing-

option-character; cannot define

define-option-character

Could not correctly parse xml to determine service


Revise the specified XML.

Bad URL

Invalid response received

Could not correctly parse response xml

An error occurred while receiving a response. Make sure the URL is correct, and the server is usable.

Cause: URL

Unexpected error

Invalid Virtual List String - String is null or length is zero

Invalid Virtual List String - length must be even

Invalid Virtual List String - string not in hex format

Revise the specified URL.


Revise the options, URL, and server settings. Make sure that the URL host name is the same as the host name set on the server. If an error still occurs, contact the Support Center.


Failed to add the WWN : error-WWN Revise the specification.

The same WWN "WWN" has existed in the same parameter. invalid parameter value: specified-

parameter-value

Invalid WWN : specified-WWN,

WWN should be "*.*.*.*.*.*.*.*" format. "*" is one or two hexadecimal numbers.

The Alerts element cannot contain that element.

The value: long-value of attribute

attribute-name could not be read as a long value

Illegal value for attribute-name:

specified-date; must be in the form:

required-date-format

The method for reading the XML data cannot be initialized.

An unexpected type or value was detected in the XML response.






Error Code

KAIC90052-E

KAIC90053-E

KAIC90054-E

KAIC90055-E

KAIC90056-E

KAIC90057-E

KAIC90058-E

KAIC90059-E

KAIC90060-E

KAIC90061-E

KAIC90062-E

KAIC90063-E

KAIC90064-E

KAIC90065-E

KAIC90066-E

KAIC90067-E

KAIC90068-E

KAIC90069-E

KAIC90070-E

KAIC90071-E

KAIC90072-E

KAIC90073-E

KAIC90074-E

Description

CommParameters elements cannot contain element-name elements

Parameters elements must have a

"name" and a "value" attribute

An unexpected element was detected in the XML response.

Program Error: Could not read file contents

An unexpected element was detected in the XML response.

The object cannot be created.

An unexpected object has been specified.

An unexpected type or value was detected in the XML response.

Malformed XML HTTP Request

Device Manager does not recognize

root-element-name root element

All Device Manager messages must have an <APIInfo> element

All Device Manager Requests must be in <Request> elements

All Device Manager Requests elements must contain a Module

Element

Device Manager module element must contain a command element

Command element must contain a target attribute

All Device Manager Responses must be in <Response> elements

All Device Manager Responses elements must contain an

EchoCommand Element

Status value of: status-value is not one of the allowed values (FAILED |

PROCESSING | COMPLETED)

Service Module must be specified before writing XML

Command must be specified before writing XML

Command target must be specified before writing XML

Attribute " attribute-name of

Element <element-name> has value= attribute-value; integer value is required

Malformed XML HTTP Response






1-217

1-218

Error Code

KAIC90075-E

KAIC90076-E

KAIC90077-E

KAIC90078-E

KAIC90079-E

KAIC90080-E

KAIC90081-E

KAIC90082-E

KAIC90083-E

KAIC90084-E

KAIC90085-E

KAIC90086-E

KAIC90087-E

KAIC90088-E

KAIC90089-E

KAIC90090-E

KAIC90091-E

KAIC90092-E

KAIC90093-E

KAIC90094-E


All Device Manager Responses must been <Response> elements

XML Conversion Unavailable: missing class file

Cannot interpret the element

<element-name>

The object cannot be converted to

XML.

Contact the Support Center. requires concurrence on date format

The value has an unexpected type.

Revise the specification. The value: attribute-value of attribute attribute-name could not be read as a value of type type-

name

Device Manager Exception, code=

result-code, level= error-level, source= error-source, description=error-description

Device Manager Server Exception:

error code= result-code

error level= error-level

error source= error-source

description=error-description


Refer to the error code in the "Device

Manager Server Messages" section in the

Hitachi Device Manager Software Error

Codes manual, and then perform the corresponding Recommended Action.

Refer to the troubleshooting in the CLI manual.

Server returned the following HTTP

Response: "response"; no additional information available

No Response Returned from the

Device Manager Server

For any-command the option option must be specified

For the command-name command, the option option must be specified

Could not open the file trace-file-

name for writing the message trace

Could not open the file input-

redirect-file-name for reading the input

Could not open file log-file-name for

Logging; will log to console

Must supply a URL from the command line or in the properties file



Could not read password from file

password-file-name

Could not find the password file

password-file-name

Error reading the password file

password-file-name: cause

Revise the contents of the password file.

Revise the password file specification.

Make sure the status of the password file is correct.



Error Code

KAIC90095-E

KAIC90096-E

KAIC90097-E

KAIC90099-E

KAIC90100-E

KAIC90101-E

KAIC90102-E

KAIC90103-E

KAIC90104-E

KAIC90105-E

KAIC90106-E

KAIC90107-E

KAIC90108-E

KAIC90109-E

KAIC90112-E

KAIC90113-E

KAIC90114-E

KAIC90115-E

Description

Certificate from Server shows a hostname of cert-host-name, but the response is actually from url-

host-name

Could not open the file output-

redirect-file-name for writing the output

An attempt to read the property file

"property-file-name" has failed.

Error reading property-file-name from executing directory



Make sure the user has permission to access the specified file.

Revise the file specification, then retry.

An attempt to read the property file

"property-file-name" has failed.

Executing with no property-file-

name Property File

Unrecognized command: command-

name

For the command-name command, the key value must be specified

For the command-name command, the item-option-name(1) or the

item-option-name(2) must be specified

For the command-name command, both the item-option-name(1) and the item-option-name(2) can not be specified together.

Specified parameters not appropriate for the command: family = model-name not recognized;

Subtarget specified-subtarget not recognized; currently supporting:

storage-array-subtarget-names

PDEV devnum from the key-name was not an integer: specified-

pdevnums

In the command-name command, when specifying specified-operand, you have to specify not-specified-

operand

The "attribute-name(channel-

speed)" command is not supported on this subsystem.

Value of key must be either true or false; the value specified-value is neither

The object type cannot be determined.

Check and, if necessary, revise the specified path setting and the status of the file, and then make sure the file can be accessed.

Revise the file specification, then retry.




Revise the specified groupelements, then retry.



1-219

1-220

Error Code

KAIC90116-E

KAIC90117-E

KAIC90118-E

KAIC90119-E

KAIC90120-E

KAIC90121-E

KAIC90122-E

KAIC90123-E

KAIC90124-E

KAIC90128-E

KAIC90129-E

KAIC90130-E

KAIC90131-E

KAIC90132-E

KAIC90133-E

KAIC90134-E

KAIC90135-E


Parameters wwn and domain cannot both be specified.

Either devnum or lusedevnums must be specified

Parameter option-name(1) ignored, using option-name(2) for LUSE definition

"option-name(1)" and "option-

name(2)" can not be specified together.

When "option-name(1)", "option-

name(2)", "option-name(3)"(or

"option-name(4)") and "option-

name(5)" are specified, they must be specified together.

When "option-name(1)", "option-

name(2)", "option-name(3)" and

"option-name(4)" are specified, they must be specified together.

The objectid is required when either

"option-name(1)" or "option-

name(1)" is specified with "option-

name(2)".

Date-Time entered (specified-value) not in the required format:

YYYY/MM/DD HH:MM:SS

Duplicate execution is not allowed:

RefreshStorageArrays



Wait until the executing command finishes, then retry.

Option option-name requires an argument option Revise the specification.

Contact the Support Center. option-name is in the longOptionMap. but not in the charOptionMap under option-

character

option-name is in the charOptionMap. but not in the longOptionMap problem accessing the Device

Manager datatype

Value of key-name must be a long; could not parse specified-value

The CLI initialization information is invalid.

Invalid character was detected in the specified userid or password.

The number of values of

"parameter-name" and "parameter-

name" must be same.






Error Code

KAIC90136-E

KAIC90137-E

KAIC90138-E

KAIC90139-E

KAIC90140-E

KAIC90141-E

KAIC90142-E

KAIC90143-E

KAIC90144-E

KAIC90145-E

KAIC90146-E

KAIC90147-E

KAIC90148-E

KAIC90149-E

KAIC90150-E

KAIC90151-E

Description

The certificate file ("specified

certificate file path") does not exist in the specified path, or the certificate file is invalid.

The certificate file ("default

certificate file path") does not exist in the default path, or the certificate file is invalid.

When the -s option is used, URLs must start with https.

A connection cannot be established.

(reason = "reason why the

connection cannot be established")


Make sure the certificate file is in the specified path and is valid. If you cannot identify the cause of the problem, download the certificate file again.

Make sure the certificate file is in the default path and is valid. If you cannot identify the cause of the problem, download the certificate file again.

Make sure the specified option and URL are correct.

Take action based on the information contained in the message and make sure that the Device Manager Server is running.

Make sure the objectID is correct. The specified objectID "specified

objectID" is invalid.

The API version "specified-API-

version" specified in the XML request is invalid.

An internal error occurred. The CLI

API version "CLI-API-version" is invalid.

The API version "specified-API-

version" specified in the XML request exceeds the highest usable version "highest-usable-version".

Both "Parameter name (1)" and

"Parameter name (2)" must be specified.

The model of the subsystem must be specified when the parameter

"Parameter name" is specified.


parameter-name.


parameter-name. Specify the value by using an integer, CU:LDEV syntax or LDKC:CU:LDEV syntax.


parameter-name. Specify the value by using an integer (decimal or hexadecimal).

Specify either "arraygroupname" or

"chassis" and "groupnum".

"arraygroup" cannot be specified together with "chassis" and

"groupnum".

Specify either "Parameter name (1)" or "Parameter name (2)".

Revise the API version specification.


Revise the API version specification.




1-221

1-222

Error Code

KAIC90152-E

KAIC90153-E

KAIC90154-E

KAIC90155-E

KAIC90156-E

KAIC90157-E

KAIC90158-E

KAIC90159-E

KAIC90160-E

KAIC90161-E

KAIC90162-E

KAIC90163-E

KAIC90164-E

KAIC90165-E

KAIC90167-E

KAIC90168-E


Information in the message was omitted because the message is too long. The original message is as follows:

The object ID of the host or the host name cannot be specified at the same time as the filter used for selecting the host.


parameter-name.

When "parameter-value" is specified for "parameter-name", you must specify the value for "parameter-

name".

When "parameter-value" is specified for "parameter-name", you cannot specify the value for "parameter-

name".

For this model, parameter-value cannot be specified for parameter-

name.

If "parameter-name" is omitted,

"parameter-name" cannot be used.

The user ID or password is not specified. Specify a user ID and password to discover the specified subsystem.

The parameter param0 cannot be specified for this model.

The parameter param0 must be specified for this model

If the parameter param0 is omitted, the parameter param1 must be specified.

Specify one of the following:

parameter-name, parameter-name,


parameter-name, or parameter-

name.

The "command-name" command is not supported on this model.

Specify one of the following:


parameter-name, or parameter-

name.

"hostname" is not recognized as a virtualization server.

This command is not supported on virtualization server.





Revise the specified values.








Use RefreshVirtualizationServer to refresh the virtualization server.



Error Code

KAIC90169-E

KAIC90170-E

KAIC90171-E

KAIC90180-E

KAIC90181-E

KAIC90182-E

KAIC90200-E

KAIC90201-E

KAIC90202-E

KAIC90203-E

KAIC90204-E

KAIC90500-E

KAIC90501-E

KAIC90503-E

KAIC90504-E

KAIC90505-E

Description

No virtualization server or the management software mananging the virtualization servers could be detected.

The parameter "parameter-name" cannot be specified for this Host.

The "specified-command" command is not supported on this Host.

The length of the "parameter-name" parameter is outside the valid range from "minimum-value" to

"maximum-value".

When "option-name(1)","option-

name(2)" and "option-name(3)" are specified, they must be specified together.

The specified parameter

"Parameter-Name" is not appropriate.

The number of "iscsiname" values must match the number of

"iscsinickname" values.

The string "element-name" could not be added to the host as an iSCSIName.

An attempt to add the iSCSIName

"error-iSCSIName" has failed.

The same iSCSIName "iSCSIName" is already specified in the parameter.

The iSCSIName cannot be specified for the instance "management-

object".

Options "-b" and "-i" cannot be specified at the same time.

A command or parameter cannot be specified when option "-b" is specified.

Both "Command name" and

"Command name" are included in the command specifications in the specified batch file. Only one of these commands can be included in the batch file.

The number of commands that can be included in the batch file is

"Number".

A command "Command-Name" that cannot be executed by batch execution has been coded in the batch file.


Revise the parameter settings and the virtualization software settings.








Revise the contents of the batch file.



1-223

1-224

Error Code

KAIC90506-E

KAIC90507-E

KAIC90508-E

KAIC90509-E

KAIC90510-E

KAIC90511-E

KAIC90512-E

KAIC90513-E

KAIC90550-E

KAIC90551-E

KAIC90552-E

KAIC90553-E

KAIC90556-E

KAIC90557-E

KAIC90559-E

KAIC90560-E

KAIC90562-E

KAIC90563-E

Description

The specified batch file cannot be found.

An attempt to read the specified batch file has failed. Remove the cause of the problem, and then reexecute the batch file. Cause:

"Message"

No command has been coded in the batch file.

The commands coded in the batch file must be for a single subsystem.

The batch file contains invalid coding in line Line-Number.

An error occurred while reading the batch file. Revise the coding in the batch file, and then re-execute the batch file. Line:Line-Number Cause:

Message

The specified parameter

"Parameter-Name" is not appropriate for the command

"Command-Name".

The specification of parameter

"Parameter-Name" is duplicated in the command.

There is an error in the syntax of the batch file coding.

The coding that follows the endbatch line is invalid.

The beginbatch line is not coded.

A command or endbatch line is not specified.

The coding in the beginbatch line is invalid.

The coding in the endbatch line is invalid.

A space character is required before the command name.

Characters other than alphanumeric characters cannot be used in a command name.

The batch file contains invalid coding.

Characters other than alphanumeric characters cannot be used in a parameter name.


Revise the batch file specification.

Remove the cause of the problem, and then re-execute the batch file.


Revise the contents of the batch file, then retry.






Error Code

KAIC90564-E

KAIC90565-E

KAIC90566-E

KAIC90569-E

KAIC90570-E

KAIC90571-E

KAIC90572-E

KAIC90573-E

KAIC90574-E

KAIC90575-E

KAIC90576-E

Description

The parameter specification is invalid. The parameter name is incorrect or the parameter has not been specified using the

"parameter-name=value" syntax.

An invalid character is being used in the parameter value. Only ASCII characters can be used. Escaping by

"\" is required for spaces and symbols, except for: ",", "-", ".",

"/", ":", "=", "_", ";".

Characters other than symbol characters cannot be escaped. The characters that can be escaped are:

" ", "!", """, "#", "$", "%", "&", "'",

"(", ")", "*", "+", "<", ">", "?", "@",

"[", "\", "]", "^", "`", "{", "|", "}",

"~".

A new line is required at the end of a statement.

The maximum number of characters that can be specified for a name, such as a parameter name, is

"Length".

This is an invalid line. A line feed is required after a carriage return.

If you specify "parameter-key-

name", you must also specify

"parameter-key-name". If you specify "parameter-key-name", you must also specify "parameter-key-

name".

If you specify "parameter-key-

name" and "parameter-key-name", you must also specify "parameter-

key-name" and "parameter-key-

name".

The memory for the CLI became insufficient while this operation was being performed.


Revise the command parameters, then reexecute the command.

Take either of the following actions:





Increase the memory heap size for the

CLI, and then perform the operation again.

Decrease the amount of information to be collected, and then perform the operation again.

Specify a valid value. The value of the "parameter-key-

name" parameter is outside the valid range from "minimum-value" to "maximum-value".

The sum of startElementNumFilter and numOfElementsFilter is outside the valid range from "minimum-

value" to "maximum-value".



1-225

1-226

Error Code

KAIC90577-E

KAIC90600-E

KAIC90601-E

KAIC90602-E

KAIC90603-E

KAIC90701-E

KAIC90702-E

KAIC90703-E

KAIC90704-E

KAIC90705-E

KAIC90706-E

KAIC90707-E

KAIC90708-E

KAIC90709-E

Description

The "parameter-name-list" and

"parameter-name-list" parameters cannot be specified at the same time.

An invalid value "specified-value" has been specified for the option

"specified-option".

The options "specified-option" and

"specified-option" cannot be specified at the same time.

The option "specified-option" and the command "specified-command" cannot be specified at the same time.

The option "specified-option" and the parameter "specified-

parameter" cannot be specified at the same time.

The user ID specified for the option

-u does not match the user ID in the property file property-file-name.

The password specified for [Old password] does not match the password in the property file

property-file-name.

The passwords specified for [New password] and [Re-enter new password] are not the same.

An attempt to encode the password has failed.



Specify the correct user ID at the command line.

Specify the correct password at the command line. If the password in the property file cannot be specified correctly at the command line, delete the password from the property file, and then execute the command again.

Specify the correct password at the command line.

An attempt to decode the password has failed.

Revise the execution environment, and then execute the command again. If the problem persists, please contact the

Support Center.

Specify the correct user ID that corresponds to the password set in the password2 option. If the problem persists, please contact the Support Center.

Delete the password in the property file, and then execute the command again.

An attempt to decode the password failed because the current environment is different from the environment in which the password was encoded.

Command execution failed because the environment does not support the specific encoding algorithm.

I/O processing for a file failed or was interrupted. (cause = Message)

An invalid password was specified.


Support Center.

Remove the cause of error by referring to the error information in the message, and then execute the command again.

Check which characters are valid and the maximum number of characters for a password, and then specify a valid password.



Error Code

KAIC90710-E

KAIC90711-E

KAIC90712-E

Description

An attempt to encode or decode the password failed because the execution environment was invalid.

An attempt to encode or decode the password failed because the execution environment was invalid.

The password file password-file-

name could not be written to.




Support Center.

If the password file exists, grant write access for it. If it does not exist, grant write access so that a password file can be made.



1-227

Device Manager CLIEX Messages

When an error occurs, Device Manager CLIEX produces one or more error messages. An error message consists of a message number and the error message text.

For details on the log files to which the CLIEX error messages are output, see the Device Manager CLI manual.

Table 1-20 lists the Device Manager CLIEX error messages, and provides

recommended actions for resolving the error conditions. The error messages are listed in numerical order by error code.

Table 1-20 Device Manager CLIEX Errors

Error Code

KAIC40001-E

KAIC40002-E

KAIC40003-E

~ KAIC40699-

E

KAIC41000-E

Description

An unknown failure occurred in the target storage array.

The command device has failed.

command device error message

RAID Manager error message



Support Center.

See the CCI/RAID Manager manual.

See the Troubleshooting Device Manager

CLIEX Problems and the CCI/RAID

Manager manual.


KAIC41001-E

An internal error occurred. (file =

"file name", line = "line number").

Memory allocation error. Out of memory.

KAIC41002-E

There might not be enough memory to execute Device Manager CLIEX.

Make sure there is enough memory in the system. If the problem persists, contact the Support Center.


KAIC41003-E

KAIC41004-E

KAIC42000-E

KAIC42001-E

KAIC42002-E

This command has not been supported for the target storage array.

An attempt to load the command device has failed.

An attempt to acquire the device information has failed. (device special file: "device file name")

Check the status of the device associated with the device special file.

The storage-array parameter must be one of the following: "-c", "-cmddev", "-a", or "--array"

The storage-array parameter must be one of the following: "-c", "-cmddev", "-a", or "--array"

The specified storage array name

"alias name" is invalid. Check the property file.

Make sure that the host is recognizing the command device correctly.

Check the status of the device associated with the device special file.


Support Center.


Make sure the contents of the property file are correct, then revise the storage subsystem specification.



Error Code

KAIC42003-E

KAIC42004-E

KAIC42005-E

KAIC42006-E

KAIC42007-E

KAIC42008-E

KAIC42009-E

KAIC42010-E

KAIC42011-E

KAIC42012-E

KAIC42013-E

KAIC42014-E

KAIC42015-E

KAIC42016-E

KAIC42017-E

KAIC42018-E

KAIC42019-E

KAIC42020-E


A command argument is missing or invalid.

The command must contain only one of the following: command list

The value "parameter value" for the parameter "parameter name" is invalid.

The value for the parameter

"parameter name" must be between

minimum value and maximum

value.

The parameter "parameter name" is required.

The parameter "parameter identifier

or parameter name" is invalid.

The parameter must be either

"parameter name" or "parameter

name".

The LUN "path LUN" has already been assigned to a LUN group or is not assigned to this port.

The specified LDEV "device number" is invalid.

The specified LDEV "device number" is part of the LU joined by the LUSE.

The LU "device number" is not assigned to the port "port number".

Revise the command specification.


Collect the storage subsystem information, and then make sure the parameter specification is correct.


The LUN "path LUN" is already being used.

To perform this operation,

"LUNSecurity=On" must be set for the port.

The LU "device number" is already assigned to this port.


Revise the LUN specification.

Turn on the security switch for the specified port, then retry.


The LU "device number" is not assigned to "port-number - host

storage domain ID" (port -

HostStorageDomain).

The LUN "path LUN" is not assigned to the LUN group "LUN group ID".

The host storage domain "host

storage domain ID" already exists on this port.

The WWN "WWN" has not been registered in "LUNGroup or

HSDOMAIN": "LUN group ID or host

storage domain ID".



1-229

1-230

Error Code

KAIC42021-E

KAIC42022-E

KAIC42023-E

KAIC42024-E

KAIC42025-E

KAIC42026-E

KAIC42027-E

KAIC42028-E

KAIC42029-E

KAIC42030-E

KAIC42031-E

KAIC42100-E

KAIC42996-E

KAIC42997-E

KAIC42998-E

Description

The WWN "WWN" has already been defined in the host storage domain

"host storage domain ID".

The maximum LUN number

("maximum value") on the port has been reached.

The host storage domain "host

storage domain ID" has not been defined for the port "port number".

The LU "path LUN" has already been assigned to a port.

target volume is not available for this operation.

The usual volume and the V-VOL can not be specified together.

At least one LUN is necessary for the pair volume.

Duplicated value "parameter value" for parameter name is specified.

The LU "device number" is already assigned to this host storage domain.

ARRAY: "array name" is not attached this host or doesn't have valid CMDDEV.

The Command Device

(devNum="device number", devFile="device file name") is not attached this host. Or, the storage array that has the Command Device is not supported. Revise devFile or devNum in the property file.

Permission denied with the Virtual

Partition Manager, "parameter

name": "parameter value".

Device Manager CLIEX cannot be started because the installation directory in the registry is invalid.

Re-install Device Manager CLIEX. If this problem cannot be solved, contact the Support Center.

Device Manager CLIEX cannot be started because a registry entry is invalid. Re-install Device Manager

CLIEX. If this problem cannot be solved, contact the Support Center.

Device Manager CLIEX cannot be started because the registry key is invalid. Re-install Device Manager

CLIEX. If this problem cannot be solved, contact the Support Center.


Make sure that the host is recognizing the command device correctly.

Make sure that the host is recognizing the command device correctly, and that the storage subsystem for the command device is supported by Device Manager

CLIEX.




Make sure the host storage domain is correct.


Revise the volume specification.

Revise the LUN specification.



If the problem cannot be solved, contact the Support Center.



Error Code

KAIC42999-E

KAIC43300-E

KAIC43301-E

KAIC43302-E

KAIC43303-E

KAIC43500-E

KAIC43502-E

KAIC43503-E

KAIC43504-E

KAIC43505-E

KAIC43506-E

KAIC43550-E

KAIC43551-E

KAIC43552-E

KAIC43553-E


The specified value "specified value" does not exist on the target "target

element".

An attempt to load "file name" has failed.

The filename cannot contain any directories.

The file "file name" cannot be loaded.

The file cannot be opened. ("file

name")



Revise the property file specification.


There are too many or too few elements in the message file. (file =

"file name", line = "line number", string = "line string")

The log level in the message file is invalid. (file = "file name", line =

"line number", string = "line string")

The message ID in the message file is invalid. (file = "file name", line =

"line number", string = "line string")

A definition is duplicated in the message file. (file = "file name", line = "line number", string = "line

string")

The number of sections in the message file is invalid. (file = "file

name", line = "line number", string

= "line string")

The message file "file name" is missing the message "message ID".

The file cannot be opened. ("file

name")

The file cannot be written to. ("file

name")

An attempt to open the event log has failed. Check the event log settings or change the Device

Manager CLIEX settings so that event logs are not output to the event log.

An attempt to output to the event log has failed. Check the event log settings or change the Device


Revise the configuration of the property file. If the problem persists, contact the

Support Center.


Revise the event log settings.



1-231

Error Code

KAIC43554-E

KAIC44300-E

KAIC44301-E

KAIC44302-E

KAIC44303-E

KAIC44304-E

KAIC44305-E

KAIC44306-E

KAIC44400-E

Description

An attempt to close the event log has failed. Check the event log settings or change the Device


The XML is invalid. (file = "file

name", line = "line number", column = "column number",

"message")

The XML is not well formed. (file =

"file name", line = "line number", column = "column number",

"message")

An error occurred during XML parser initialization. (file = "file name")

An error occurred during parsing.

("error message")

A DOM error occurred during parsing. ("error message")

An error occurred during parsing.

("error message")

An error occurred during XML processing. ("error message")

An error occurred while parsing "file

name". This file does not conform to the DTD.


Revise the event log settings.

Make sure the contents of the property file are correct.


Support Center.



Support Center.




Universal Storage Platform V/VM

Messages

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Universal Storage Platform V/VM.



Details About Universal Storage Platform V/VM Messages

Universal Storage Platform V/VM Messages


2-1

Details About Universal Storage Platform V/VM Messages

Some messages displayed by Device Manager contain, as a part of the message, a message output from the storage subsystem. This section lists and describes the error messages from Universal Storage Platform V/VM that are contained in Hitachi Device Manager messages.

If you are unable to resolve the conditions of an error, see

Calling the Hitachi

Data Systems Support Center for instructions on calling the Hitachi Data


When a Device Manager message contains a message from Universal Storage

Platform V/VM, Device Manager displays two types of error code identifying the Universal Storage Platform V/VM messages.

Table 2-1 lists and describes the Universal Storage Platform V/VM messages

that are displayed by Hitachi Device Manager. For details on the Universal

Storage Platform V/VM error messages that are not listed in Table 2-1, see the

Storage Navigator message manual. In those messages, %s indicates a string variable and %d indicates a numerical variable.

Messages whose first error code (error code 1) is 60xx (where xx is a two-digit number) are TrueCopy for z/OS or TrueCopy messages. This manual contains

TrueCopy for z/OS messages only. If you are a TrueCopy user, note that:



The word M-VOL in TrueCopy for z/OS messages is equivalent to P-VOL in

TrueCopy messages.



The word R-VOL in TrueCopy for z/OS messages is equivalent to S-VOL in

TrueCopy messages.

Note:

 The list of messages below shows error codes 1 and 2, separated by a comma. The asterisk ("*") indicates that the error code output varies. If a displayed error code does not match any of the codes listed below, see the explanation for the message labeled *,*.

 In some cases, the Recommended Action column may be blank. In these circumstances, the user should take actions based on instructions provided in the error message and based on what the user is trying to accomplish.

2-2 Universal Storage Platform V/VM Messages


Table 2-1 Universal Storage Platform V/VM Messages

Error Code

*,*

2,5510

2,56525

2,58578

3,2003

3,2033

3,2100

5,66101

305,56525

405,5047

Description

An error has occurred in the subsystem. If you cannot solve this problem, contact the Support Center.

The disk subsystem is in internal process, or some other user is changing the configuration. Wait a while, then click

[Refresh] on the File menu, or wait a while and login again.

Because the settings across the multiple

SLPRs are contained, the authority has been shifted to the storage administrator from the storage partition administrator.

To continue the operation, please contact the storage administrator. To perform other operations, select a function button.

An error occurred in the disk subsystem.

The configuration may be inconsistent.

Please select [All Refresh] and refresh the configuration.

Volume migration, QuickRestore, etc. are in process. After you reply to this message, a window that shows only the

Refresh button will be displayed. Please wait for a while, and then select

[Refresh].

Wait a while, then click [Refresh] on the

File menu, or wait a while and login again.

See the Storage Navigator message manual.


After you reply to this message, a window that shows only [Refresh] will be displayed. Wait a while, then click

[Refresh].If this problem persists, inconsistency of configuration may have occurred. Please call the Support Center.

If the problem occurred when starting

SVP, check the version number of the microprogram and the configuration information.


The SVP is not ready yet, or an internal processing is being executed. Wait for a while, and then click [Refresh] on the File menu. When an error occurs during login, wait for a while and login again.

An error occurred while connecting to the disk subsystem. The configuration may be inconsistent. Please select [All Refresh] and refresh the configuration.

This function could not be used because a function failed to start during SVP initialization.Click [All Refresh] and refresh the configuration. If this problem persists, please call the Support Center.




An error occurred when installing or uninstalling the program product. Please select the program product and select







Support Center.



2-3

2-4

Error Code

405,5503

605,8971

605,66501

605,66502

605,66503

605,66504

605,66505

605,66506

605,66507

605,66508

605,66509

605,66512

605,66514

605,66515

605,66517

605,66518

605,66675

605,66693

Description

[Detail] to check the details of the error.

You have attempted to install an

Emergency key to the option for which a

Permanent key has been installed. If you want to install the Emergency key forcibly by using the license key file, please specify Only Normal & Warning and retry this operation. If you want to install the

Emergency key forcibly by using the license key code, please select [OK].

An error occurred while connecting to the disk subsystem. The configuration may be inconsistent. Click [Refresh All] on the File menu and refresh the configuration.

The number of LDEVs that can be defined in an external volume has exceeded the maximum value.

Specified ExG has already been used.

It is not set within the range where LDKC,

CU, and LDEV can be used.

Specified LDKC:CU:LDEV has already been used.

It is allocated in other emulation groups within the delimited range of each

32LDEV number.

Specified SSID has already been used.









The target external volume is blocked or not set within the range where capacity can be used.

The specified LDEV capacity is invalid.



The total of the LDEV capacity defined in the external volume exceeds the external volume size.

Specified CLPR is not mounted.



LDKC: CU that cannot be used by the

SLPR is specified.

SSID that cannot be used by the SLPR is specified.

The target external volume has already been mapped or set.

The cross-subsystem path configuration of the external volume is not corresponding to the cross-subsystem path configuration defined in PathGroup.

The syntax of the parameter is invalid.






A correct parameter is not set as a data


See the Storage Navigator message



Error Code

605,66694

605,66695

605,66698

605,66702

605,66705

605,66710

605,66713

605,66718

605,66720

605,66722

605,66736

605,66739

605,66742

605,66744

605,66747

605,66797

605,66798

605,66799

1005,1128

1005,2100

Description

transfer volume.

A correct parameter is not set as

RemoteCommandDevice.

Specified port is not external port.


manual.




The number of alternate Path definitions that can be set to the external volume has exceeded the maximum.

It is not set within the range where

PathGroup can be used.

It is not Port number that can be specified.

It is not set within the range where LUN can be used.

It is not set within the range where ExG can be used.

It is not set within the range where CLPR can be used.

It is not emulation type that can be specified.

CacheMode is invalid.

It is not set within the range where LDKC can be used.

It is not set within the range where CU can be used.

It is not set within the range where LDEV can be used.

It is not set within the range where LDEV capacity can be used.

It is not set within the range where SSID can be used.

There is an error in the parameter of the subordinate position hierarchy.

Specified WWN was not found.

















Specified external volume was not found. See the Storage Navigator message manual.

Review the Channel Package. You have requested to change the channel speed, but the version of Fiber

PCB is not supported.

An error occurred while connecting to the disk subsystem. The configuration may be inconsistent. Please select [All Refresh]




2-5

2-6


and refresh the configuration.

1005,56525 Because the settings across the multiple


1305,66572 Declaration is invalid.

1305,66573 The number of lines or the number of characters in one line exceeds the maximum number.

1305,66574 There is a line that cannot be interpreted as an element of the spreadsheet.

1305,66575 It is not corresponding to the serial number of the device that executes the spreadsheet.

1305,66576 Any operation tag to the program product is not set.

1305,66577 Version number or program product of the declaration is not correct.

1305,66578 There was an error while executing the spreadsheet. Please confirm the result of each parameter.

1305,66675 The syntax of parameter is invalid.










3005,8971 An error occurred while connecting to the disk subsystem. The configuration may be inconsistent. Click [Refresh All] on the File menu and refresh the configuration.




3005,58572 An error occurred during the communication with the storage system.

Please wait a while, and retry the operation.If the error occurred in the operation of the pool, please refresh the configuration by clicking [Refresh All] on the File menu, then retry the operation.




5105,56525



To continue the operation, please contact










the storage administrator. To perform other operations, select a function button.







8005,5510 The disk subsystem is in internal process, or some other user is changing configuration. After you reply to this message, a window that shows only the

Refresh button will be displayed. Please wait for a while, and then select

[Refresh].




8105,2033 The SVP is not ready yet, or an internal processing is being executed.

8105,6999 There is a possibility that composition information has been changed.

9605,56525














2-7

2-8 Universal Storage Platform V/VM Messages


Hitachi USP Messages

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Hitachi USP.



Details About Hitachi USP Messages



3-1

Details About Hitachi USP Messages

Some messages displayed by Device Manager contain, as a part of the message, a message output from the storage subsystem. This section lists and describes the error messages from Hitachi USP that are contained in Hitachi

Device Manager messages.


Calling the Hitachi



When a Device Manager message contains a message from Hitachi USP,

Device Manager displays two types of error code identifying the Hitachi USP messages.

Table 3-1 lists and describes the Hitachi USP messages that are displayed by

Hitachi Device Manager.

Note: The list of messages below shows error codes 1 and 2, separated by a comma. The asterisk ("*") indicates that the error code output varies. If a displayed error code does not match any of the codes listed below, see the explanation for the message labeled *,*.

Table 3-1 Hitachi USP Messages

*,*

Error Code

1,1001

3,1002

1005,1002

Description

An error has occurred in the subsystem. If you cannot solve this problem, contact the Support

Center.

A timeout has occurred. The SVP will reboot. Try again later.



Support Center.

The SVP reboots automatically. After the reboot, re-execute. If the same result occurs, contact the Support

Center.

None. The specified volume cannot be set as a command device or a component of a LUSE volume, because it is being used as a

Remote Copy, ShadowImage,

Cross-system Copy, Volume

Migration, or COW Snapshot volume. Select another volume.

The specified volume cannot be set as a command device or a component of a LUSE volume, because it is being used as a


Cross-system Copy, Volume

Migration, or COW Snapshot volume. Select another volume.

3-2 Hitachi USP Messages


Error Code

3,1003

1005,1003

3,1004

1005,1004

3,1005

1005,1005

3,1007

1005,1007

3,1009

1005,1009

3,1010

Description

An attempt is being made to set multiple paths from one group to the same volume.

An attempt is being made to set multiple paths from one group to the same volume.

An attempt is being made to set multiple volumes for one combination of port, group, and

LUN group.

An attempt is being made to set multiple volumes for one combination of port, group, and

LUN group.

An attempt is being made to set paths to an uninstalled volume, a volume other than the top of an expanded LU, a reserve volume of

Volume Migration, or a Just-in-

Time volume.

An attempt is being made to set paths to an uninstalled volume, a volume other than the top of an expanded LU, a reserve volume of

Volume Migration, or a Just-in-

Time volume.

The last path connected to a volume of one of the following could not be deleted: Remote

Copy, ShadowImage, Crosssystem Copy, Volume Migration, or COW Snapshot.

The last path connected to a volume of one of the following could not be deleted: Remote

Copy, ShadowImage, Crosssystem Copy, Volume Migration, or COW Snapshot.

The emulation type of the volume to be connected as an expanded

LU is not an open-systems volume.

The emulation type of the volume to be connected as an expanded

LU is not an open-systems volume.

You are trying to specify an expanded LU that includes an already expanded LU.


The configuration might be already changed. Revise the settings.


None.





3-3

3-4

Error Code

3,1011

1005,1011

3,1012

1005,1012

3,1013

1005,1013

3,1015

1005,1015

3,1018

1005,1018

3,1020

1005,1020

3,1021

1005,1021

3,1022

1005,1022

3,1023

1005,1023

Description

The volumes to be connected as an expanded LU extend across different CU numbers.

The volumes to be connected as an expanded LU extend across different CU numbers.

An LU path is set for the volumes to be connected as an expanded

LU.

An LU path is set for the volumes to be connected as an expanded

LU.

The emulation types of the volumes to be connected as an expanded LU are not the same.



The emulation types of the volumes to be connected as an expanded LU are not the same.

An LU path is set for the LUSE to be released.

An LU path is set for the LUSE to be released.

A port specified as an element in the configuration change does not exist.

A LUN is invalid. (The specified value is outside the valid range.)

A LUN is invalid. (The specified value is outside the valid range.)

The specified volume does not exist.

When specifying volumes in a LUSE, you must use volumes with the same emulation type, size, and attributes

(you cannot specify Normal Volume and Customized Volume together.).

Remove the path for the target volume before releasing the LUSE.

A port specified as an element in the configuration change does not exist.

The specified port does not exist. You might have specified a port that has not been implemented, or an exclusive port for a mainframe.

Revise the specified port.

The specified port does not exist. You might have specified a port that has not been implemented, or an exclusive port for a mainframe.

Revise the specified port.


The specified volume (CU number :

LDEV number) does not exist. You might have specified a volume that has not been implemented, or an exclusive volume for a mainframe.

Revise the specified volume.


The host mode is invalid.

The host mode is invalid.

The fibre address is incorrect.

The fibre address is incorrect.



None.



3,1031

3,1032

3,1033

3,1034

Error Code

3,1024

1005,1024

3,1025

1005,1025

3,1027

3,1028

1005,1028

3,1029

3,1035

3,1036

Description

Invalid fiber topology information has been specified. (The specified value is outside the valid range.)

Invalid fiber topology information has been specified. (The specified value is outside the valid range.)

The specified LU path does not exist.

The specified LU path does not exist.

The specified value in the command device settings is invalid. (The specified value is outside the valid range.)

The number of volumes to be connected as an expanded LU exceeded the maximum value 36.

The number of volumes to be connected as an expanded LU exceeded the maximum value 36.

The size of the volumes to be connected as an expanded LU are not the same. Alternatively, you have tried to connect the combination of a customized volume and normal volume.

The area specified in Cache

Residency exceeds the volume size.

The specified extent exceeds the size that can be specified.

A mainframe volume is specified in an instruction for the entire

Cache Residency volume.

The method of specifying the

Cache Residency setting area and the volume type do not match.

(An LBA number is specified for a mainframe volume. Alternatively, a cylinder number and header number are specified for an opensystems volume.)

The SSIDs are not defined. If this problem persists, call the Support

Center.

The specified size of the CV is outside the valid range. (It is smaller than the minimum size, or is larger than the maximum.)






When specifying volumes in a LUSE, you must use volumes with the same emulation type, size, and attributes

(you cannot specify Normal Volume and Customized Volume together.).


Specify a smaller extent, and then respecify the setting.


None.

The size of the CV is outside the valid range. (It is smaller than the minimum size, or is larger than the maximum.) If this problem persists, contact the Support Center.



3-5

3-6

Error Code

3,1037

3,1038

3,1039

3,1040

3,1041

3,1042

3,1043

3,1044

3,1045

3,1048

3,1049

3,1050

There is not enough space left in the logical parity group to create a CV.

Description

The specified emulation types for the CV cannot be used together, or are not supported.

A VLL operation is being attempted for a volume with an

LU path specified, an LU expanded volume, or a volume with LDEV Security specified.

When executing VLL (Volume

Initialize), only Deleted Normal

Volume information was specified.

An internal logic error has occurred.

The CU number and LDEV number that were specified in the VLL operation have duplicated those of another volume.

An error occurred in the subsystem. If this problem persists, contact the Support

Center.

An instruction was issued to a logical parity group not installed by a VLL operation. Contact the

Support Center.

When executing a VLL operation

(Volume Initialize), the number of volumes that should be returned to Normal Volume and the number of volumes requested in

Volume Initialize were different.

The specified subsystem ID already exists. Specify another

SSID.

The specified volume does not exist, or a delete request was issued to a volume without Cache

Residency specified.

When executing a VLL operation

(Volume Initialize), a CV was not set in the target logical parity group.

A reserve volume of Volume

Migration or Just-in-Time volume is included in the volumes to be combined into an expanded LU.

None.


Specify the value considering that the number of LDEVs that can be stored in a logical parity group varies depending on the drive type and RAID type. For more details, contact the

Support Center.

Since each emulation type has a different definition, contact the

Support Center for more details.

Revise the target volume.

Contact the Support Center for more details.

The Cache Residency pre-staging command was accepted, but the

Cache Residency setting has not been made. Alternatively, the Cache

Residency setting was made, but prestaging is not set. Contact the

Support Center.





Error Code

1005,1050

3,1051

*,1059

3,1059

*,1061

3,1061

3,1062

3,1063

3,1064

1005,1064

5305,1064

3,1065

1005,1065

3,1066

1005,1066

3,1067

Description

A reserve volume of Volume

Migration or Just-in-Time volume is included in the volumes to be combined into an expanded LU.

The emulation type is specified incorrectly in the VLL operation.

A LUN Manager operation is being attempted for a non-Fibre port.

A LUN Manager operation is being attempted for a non-Fibre port.

A LUN Manager operation is being attempted on a port for which the

LUN Manager function is disabled.

A LUN Manager operation is being attempted on a port for which the

LUN Manager function is disabled.

A invalid volume emulation type or emulation type size was specified in the VLL operation

(Install CV). The specified size of the volume does not correspond to the emulation type.

The specified WWN is already in use. Specify another WWN.

An attempt is being made to register an existing WWN.

An attempt is being made to register an existing WWN.

The specified WWN is already in use. Specify another WWN.

An attempt is being made to register an existing WWN nickname or an existing host group nickname. The WWN nickname or host group nickname must be unique.

An attempt is being made to register an existing WWN nickname or an existing host group nickname. The WWN nickname or host group nickname must be unique.

An unregistered WWN number was specified at the time of deletion or modification.

An unregistered WWN number was specified at the time of deletion or modification.

An attempt is being made to register an existing host group number.


Switch on the security.

Specify the number of user-defined cylinders for mainframe volumes, and specify the user-defined size for open-systems volumes.







3-7

3-8

5205,1076

5205,1077

5205,1078

5205,1079

5205,1080

5205,1081

5205,1082

5205,1083

5205,1084

5205,1085

5205,1086

5205,1087

5205,1088

Error Code

1005,1067

3,1068

1005,1068

3,1074

3,1075

Description

An attempt is being made to register an existing host group number.

An unregistered host group was specified at the time of deletion or modification.

An unregistered host group was specified at the time of deletion or modification.

The CU specified in the VLL operation (Install CV) is invalid.

Different types of VLL operations

(Volume Initialize, Install CV, or

Volume to Space) have been specified in a single request to set the configuration information.

The specified volume is already being used by ShadowImage or

FlashCopy Mirror.


FlashCopy Mirror.

The specified volume is a LUSE volume, so you cannot change it to a reserve volume.

The volume specified as a reserve volume has the Cache Residency setting.

The specified volume is not available.

The specified volume is a command device.

The specified volume is not implemented.

The specified volume is already specified as a reserve volume.

There is no allocatable reserved volume.

The specified volume is already being used by Volume Migration.

The RAID level of the target volume is not supported.

The HDEV specified as a reserve volume is a NAS system volume.

The specified destination volume is a NAS system volume.



Specify one type of VLL operation in a single request.

Check the status of the specified volume.

Release the Cache Residency setting from the specified volume.

Re-execute. If the same result occurs, contact the Support Center.

Release the command device, or select another volume.


Set the reserve volume, and then reexecute.


Check the microcode version, and contact the Support Center.

Check the status of the selected volume.




3,1103

3,1104

3,1105

3,1108

Error Code

5205,1094

5205,1095

5205,1096

3,1101

3,1102

1005,1108

5205,1109


The volume is not a reserved volume.

The number of volumes exceeds the maximum.

The specified volume is already in use by a host or remote copy.

A VLL operation was requested for a volume that has not been implemented.

A volume initialization operation cannot include the last LDEV in a parity group.


Further reduction is not possible because at least one LDEV is required in a parity group. Revise the specified contents.

Revise the settings. A VLL operation has been specified on a parity group that has not been implemented.

You are trying to set a subsystem

ID without a VLL operation.


Issue a request to change the subsystem ID when a VLL operation is performed.

To create an LDEV, first delete an unnecessary LDEV, or specify another array group.

Revise the volume for which the command device is set.

The maximum number of LDEVs that can be created in an array group has been reached.

A command device setting cannot be requested for the following volumes: 1. Reserved volume of

Volume Migration 2. Just-in-Time volumes 3. Volumes other than open-systems volumes (including uninstalled volumes).

A command device setting cannot be requested for the following volumes: 1. Reserved volume of

Volume Migration 2. Just-in-Time volumes 3. Volumes other than open-systems volumes (including uninstalled volumes).

The selected volume or combination is not supported by

Volume Migration.




3-9

3-10

3,1116

1005,1116

5205,1117

5205,1118

5205,1119

5205,1120

5205,1121

5205,1122

3,1123

Error Code

3,1110

1005,1110

*,1111

3,1113

1005,1123


Unusable characters were specified in the nickname to be used in HOST GROUP and WWN.

A nickname must not start or end with a space character, and must not contain the following characters:

\ / : , ; * ? " < >

| .

Unusable characters were specified in the nickname to be used in HOST GROUP and WWN.

A nickname must not start or end with a space character, and must not contain the following characters:

\ / : , ; * ? " < >

| .

A nickname is not specified when the configuration change of LUN

Manager is requested.

The selected CU:LDEV in the VLL operation to create a volume cannot be applied because it is being used by HPAV.

A value was not registered at

WWN registration, or 0 was set for the WWN value.

A value was not registered at

WWN registration, or 0 was set for the WWN value.

The specified volume is already being used in concurrent copying.



The specified volume is already being used by HXRC.



You have requested to set the command device security, but the command device has not been set for the target volume.

You have requested to set the command device security, but the command device has not been set for the target volume.

None.

Make sure to specify a host group nickname.

Change the specified volume ID, or release the HPAV settings.

Make sure to specify the WWN value before issuing a request to change the configuration.


The configuration might be already changed. Revise the settings. You need to set the command device for the volume before or at the same time you set the command device security.



3,1125

1005,1125

3,1126

1005,1126

3,1127

1005,1127

3,1128

1005,1128

3,1129

Error Code

3,1124

*,1130

3,1131

1005,1131

3,1132


The setting method of the command device/command device security is incorrect. The following settings are invalid. 1.

Set command device + Release command device security 2.

Release command device + Set command device security

No host groups are available to register the WWN.

No host groups are available to register the WWN.

The command device cannot be set within a LUSE volume. Select another volume.

The command device cannot be set within a LUSE volume. Select another volume.

The CHA high-speed mode is specified for an unmounted CHA.

The CHA high-speed mode is specified for an unmounted CHA.

Channel speed change was requested, but the specified CHA does not support Fibre PCB.

Channel speed change was requested, but the specified CHA does not support Fibre PCB.

When registering the WWN in the

LUN Manager operation, the number of WWNs exceeded the maximum value of 255.

When registering the host group nickname and the WWN nickname, you specified an invalid nickname. (xx-G00: xx is a port name, such as 1A, 1B.)

When setting the host group in an add, change, or delete operation, you specified a value larger than the maximum value (0 to 127) allowed for the port.

When setting the host group in an add, change, or delete operation, you specified a value larger than the maximum value (0 to 127) allowed for the port.

When setting the WWN in an add or change operation, you specified a value larger than the maximum value (0 to 254) allowed for the port.




Revise the channel package.

Revise the channel package.


A default nickname cannot be specified in a LUN Manager operation.





3-11

3-12

Error Code

1005,1132

3,1133

1005,1133

3,1134

1005,1134

3,1135

1005,1135

3,1136

1005,1136

3,1137

1005,1137


When setting the WWN in an add or change operation, you specified a value larger than the maximum value (0 to 254) allowed for the port.

When setting the host mode, you specified a value for the host group ID larger than the maximum value allowed for the port.

When setting the host mode, you specified a value for the host group ID larger than the maximum value allowed for the port.

When setting the path in an add or change operation, you specified a value larger than the maximum value allowed for the port. (When

Security Switch is OFF: 256,

When Security Switch is ON: 512)

When setting the path in an add or change operation, you specified a value larger than the maximum value allowed for the port. (When

Security Switch is OFF: 256,

When Security Switch is ON: 512)

When setting port information

(Fibre Address, Fibre Topology, or

Channel Speed), you specified more than one instruction to make changes to the same port.

When setting port information

(Fibre Address, Fibre Topology, or

Channel Speed), you specified more than one instruction to make changes to the same port.

When setting the CHA high-speed mode, you specified more than one instruction to make changes to the same port.

When setting the CHA high-speed mode, you specified more than one instruction to make changes to the same port.

When setting LUSE, the maximum number of instructions that can be set by the DKC was exceeded.

When setting LUSE, the maximum number of instructions that can be set by the DKC was exceeded.

Multiple configurations are specified for the port for which you attempted to change the configurations. Revise the settings.

Multiple configurations are specified for the port for which you attempted to change the configurations. Revise the settings.





Error Code

3,1138

1005,1138

3,1140

100,1140

3,1141

3,1145

1005,1145

3,1146

1005,1146

3,1147

1005,1147

3,1148

1005,1148

3,1149


The same setting exists for the

LUNM function.

The same setting exists for the

LUNM function.

Changes cannot be made because the port group settings are already made. Delete the port group settings.

Changes cannot be made because the port group settings are already made. Delete the port group settings.

Now processing. Wait a while, and then re-execute.

None.

Release the port group setting.

Wait a while, and then log in again.

Retry the same operation several times. If the same result occurs, contact the Support Center.

None. An attempt was made to change the setting of the fibre address, the topology, the channel speed, the security switch, or the port attribute (the initiator or the target) of a NAS port. Check the setting.

An attempt was made to change the setting of the fibre address, the topology, the channel speed, the security switch, or the port attribute (the initiator or the target) of a NAS port. Check the setting.

You cannot add the path to the

NAS system user group because system LU is not set. Set system

LU in SVP.

You cannot add the path to the

NAS system user group because system LU is not set. Set system

LU in SVP.

An attempt was made to add a path to the LDEV defined for the

NAS system LU.

An attempt was made to add a path to the LDEV defined for the

NAS system LU.

The intermediate volume was specified as the user LU for NAS system.

The intermediate volume was specified as the user LU for NAS system.

An attempt was made to set

(add/delete) a path to the NAS system LU group.

None.



3-13

3-14

Error Code

1005,1149

3,1150

1005,1150

3,1151

1005,1151

3,1170

1005,1170

3,1171

1005,1171

3,1172

Description

An attempt was made to set

(add/delete) a path to the NAS system LU group.

The CMDDEV for the LDEV defined for the NAS system LU was specified.

The CMDDEV for the LDEV defined for the NAS system LU was specified.

An attempt was made to change the speed mode by specifying the package (CHA) for NAS.

An attempt was made to change the speed mode by specifying the package (CHA) for NAS.

When you configure a volume as a command device, the volume must meet the following conditions:



The volume has the

Read/Write attribute.



The volume is usable as an S-

VOL (secondary volume).

When you configure a volume as a command device, the volume must meet the following conditions:





The volume has the


The volume is usable as an S-

VOL (secondary volume).

This LU cannot be combined into or released from a LUSE volume because it is not a Read/Writeenabled volume that is also usable as an S-VOL (secondary volume).

This LU cannot be combined into or released from a LUSE volume because it is not a Read/Writeenabled volume that is also usable as an S-VOL (secondary volume).

The LUs cannot be combined or released because the volumes do not have the Read/Write attribute.


Correct the settings, then re-execute.



1005,1181

3,1182

1005,1182

3,1183

4,1183

1005,1183

3,1173

3,1174

1005,1174

3,1175

3,1176

3,1177

1005,1177

3,1178

1005,1178

3,1179

3,1180

1005,1180

3,1181

Error Code

1005,1172



The maximum number of hosts that can be set for a port was exceeded.

The specified host ID is already registered.

The specified host ID is already registered.

Fibre port settings cannot be made for an iSCSI port.

The high-speed mode cannot be set for iSCSI packages.

The specified host is already registered.

The specified host is already registered.

An invalid host name was specified.

An invalid host name was specified.

A non-registered host was specified.

The system LU specification and another LU specification was executed in a single PDU.

The system LU specification and another LU specification was executed in a single PDU.

The specified path cannot be added because the volume is used by a Remote Copy pair.

The specified path cannot be added because the volume is used by a Remote Copy pair.

An attempt was made to set at least 60TB for the LUSE setting.

Revise the setting.

An attempt was made to set at least 60TB for the LUSE setting.

Revise the setting.

The port information does not match the PCB mode.





None.


None.



3-15

3-16

Error Code

1005,1184

3,1185

1005,1185

3,1186

1005,1186

3,1187

1005,1187

3,1188

1005,1188

3,1189

1005,1189

3,1190

Description


In a connection operation that includes a LUSE, an attempt was made to insert an LDEV number.

(The LDEV number was specified in a format that inserted it in the numbers of the LDEVs included in the LUSE.)

In a connection operation that includes a LUSE, an attempt was made to insert an LDEV number.

(The LDEV number was specified in a format that inserted it in the numbers of the LDEVs included in the LUSE.)

A path setting other than top path was made in a connection operation including a LUSE.

A path setting other than top path was made in a connection operation including a LUSE.

Expansion of the LU is not possible because the host mode of the host group having the path to the target LU is "LUSE On".

Expansion of the LU is not possible because the host mode of the host group having the path to the target LU is "LUSE On".

You cannot delete the LU because

NAS OS is currently using the

System LU. Check the setting.

You cannot delete the LU because

NAS OS is currently using the

System LU. Check the setting.

The specified user LU cannot be deleted because the user LU is being used by the NAS system package. To delete the user LU, delete the file system configured in the LU.

The specified user LU cannot be deleted because the user LU is being used by the NAS system package. To delete the user LU, delete the file system configured in the LU.

When you define a path from a

NAS system port or an iSCSI port to a volume, the volume must meet the following conditions: 1)

The volume has the Read/Write attribute, 2) The volume is usable as an S-VOL (secondary volume).


If this problem persists contact the

Support Center.

None.

Delete the file system configured on the LU set for the user LUN to be deleted, and then re-execute.




3,1193

3,1194

1005,1194

3,1195

1005,1195

3,1196

1005,1196

3,1197

1005,1197

3,1198

Error Code

1005,1190

3,1192

1005,1198

3,1199

1005,1199

Description

When you define a path from a

NAS system port or an iSCSI port to a volume, the volume must meet the following conditions: 1)

The volume has the Read/Write attribute, 2) The volume is usable as an S-VOL (secondary volume).

Command device settings cannot be made for a volume to which a path from an iSCSI port is defined. Also, you cannot define paths from iSCSI ports to command devices.

Paths cannot be added to

TrueCopy, ShadowImage, or

Cross-system Copy pair volumes.

Port information about external ports cannot be changed.

Port information about external ports cannot be changed.

Cross-system Copy LUs cannot be used as command devices.

Cross-system Copy LUs cannot be used as command devices.

A LUSE volume cannot be created by concatenating LUs and Crosssystem Copy LUs.

A LUSE volume cannot be created by concatenating LUs and Crosssystem Copy LUs.

The high-speed mode cannot be specified for a package including an external port.

The high-speed mode cannot be specified for a package including an external port.

The high-speed mode cannot be specified because a path is defined for a Cross-system Copy

LU.

The high-speed mode cannot be specified because a path is defined for a Cross-system Copy

LU.

When defining paths from iSCSI ports, you can only define paths to open-systems volumes.

The path cannot be set for the specified volume because the volume is not an open-systems volume.

None.





3-17

3-18

5205,1207

5205,1208

5205,1209

5205,1210

5205,1211

5205,1212

5205,1213

5205,1214

Error Code

3,1201

1005,1201

3,1203

1005,1203

3,1204

1005,1204

Description

The selection of High Speed mode/MIX mode is invalid. The specified port cannot be changed to High Speed mode/MIX mode.

The selection of High Speed mode/MIX mode is invalid. The specified port cannot be changed to High Speed mode/MIX mode.

High Speed mode/MIX mode was specified. However, there are addresses to which High Speed mode/MIX mode cannot be set in the Fibre Addresses of the specified ports.

High Speed mode/MIX mode was specified. However, there are addresses to which High Speed mode/MIX mode cannot be set in the Fibre Addresses of the specified ports.

High Speed mode/MIX mode was specified. However, there are topologies to which High Speed mode/MIX mode cannot be set in the topologies of the specified ports.

High Speed mode/MIX mode was specified. However, there are topologies to which High Speed mode/MIX mode cannot be set in the topologies of the specified ports.

The volume types do not match. Re-execute the same operation. If the same result occurs, contact the

Support Center.


The selected volume or combination is not supported by

Volume Migration.

The specified volume or combination is not supported by

Volume Migration.

The number of target volumes that could be executed at one time exceeds the maximum.

The number of volume pairs exceeds the maximum.


The specified volume cannot be used.

The specified volume is being formatted.





5205,1223

5205,1224

5205,1225

5205,1226

5205,1227

5205,1228

5205,1229

5205,1230

5205,1231

5205,1232

5205,1233

5205,1234

Error Code

5205,1215

5205,1216

5205,1217

5205,1218

5205,1219

5205,1220

5205,1221

5205,1222

Description



The specified volume cannot be used.

The specified volume is being formatted.


The specified volume is not a reserved volume.


The number of ShadowImage,

ShadowImage z/OS, or FlashCopy

Mirror pair volumes reached the maximum.



The selected source volume and destination volumes are the same volume.

The specified volume is already being used by Remote Copy.


The RAID level of the target volume is not supported.


FlashCopy Mirror.


FlashCopy Mirror.

The specified volume is already being used by data migration.


FlashCopy Mirror.


FlashCopy Mirror.

The specified volume is already in use by a host or remote copy.



None.



Release the data migration settings.


None.



3-19

3-20

5205,1243

5205,1246

5205,1247

5205,1248

5205,1249

5205,1250

5205,1251

5205,1252

5205,1253

5205,1254

5205,1255

Error Code

5205,1235

5205,1236

5205,1237

5205,1238

5205,1239

5205,1240

5205,1241

5205,1242

Description


The RAID level of the specified volume is not supported.


FlashCopy Mirror.


FlashCopy Mirror.

The specified volume is already being used by data migration.


FlashCopy Mirror.

The specified migration source volume has a Cache Residency setting.

The specified migration destination volume has a Cache

Residency setting.

The specified volume is not the source volume.

The number of plans that can be executed simultaneously exceeds the maximum.

The specified volume is already a source volume.

The specified source or target volume is used as a Cross-system

Copy volume.

The volume specified as a reserved volume is used as a

Cross-system Copy volume.

The specified source volume is connected to an iSCSI port.

The specified target volume is connected to an iSCSI port.

The volume specified as a reserved volume is connected to an iSCSI port.

The specified source volume is used as a Cross-system Copy volume.

The specified target volume is used as a Cross-system Copy volume.

The volume specified as a reserved volume is used as a

Cross-system Copy volume.




Release the data migration settings.





Error Code

5305,1258

3,1350

1005,1350

3,1351

1005,1351

3,1352

1005,1352

3,1353

1005,1353

3,1354

1005,1354

Description

This port is not properly implemented.

The path to the initiator or external port cannot be added.

The path to the initiator or external port cannot be added.

The high-speed or initiator/external mix mode cannot be set to the specified port because of a port attribute.

The high-speed or initiator/external mix mode cannot be set to the specified port because of a port attribute.

Logical paths remain on the Fibre-

MCU port. This operation may cause fatal damage to the logical paths. Stop this operation. If you want to continue this operation, remove the logical paths from the

MCU port first.

Logical paths remain on the Fibre-

MCU port. This operation may cause fatal damage to the logical paths. Stop this operation. If you want to continue this operation, remove the logical paths from the

MCU port first.

S-VOLs remain on the Fibre-RCU port. This operation may cause fatal damage to S-VOLs. Stop this operation. If you want to continue this operation, remove the S-

VOLs from the RCU port first.

S-VOLs remain on the Fibre-RCU port. This operation may cause fatal damage to S-VOLs. Stop this operation. If you want to continue this operation, remove the S-

VOLs from the RCU port first.

The WWN to the initiator or external port cannot be registered.

The WWN to the initiator or external port cannot be registered.


To add a path, change the attribute of the specified port to Target or RCU

Target.

None.

Since the port you are trying to set up is for Fibre TrueCopy, you need to delete the logical path, and then perform setup.

Since the port you are trying to set up is for Fibre TrueCopy, you need to delete the S-VOL logical path set for

RCU Target, and then perform setup.

To register the WWN, change the attribute of the specified port to

Target or RCU Target.



3-21

3-22

Error Code

3,1355

1005,1355

3,1356

1005,1356

3,1357

1005,1357

3,1358

3,1359

3,1360

1005,1360

3,1361

1005,1361

3,1362

1005,1362

3,1363

1005,1363

3,1364

1005,1364


The host mode of the host group that you connected to the initiator or external port cannot be changed.

The host mode of the host group that you connected to the initiator or external port cannot be changed.

The host group cannot be added to the initiator or external port.

To change the host mode, change the attribute of the specified port to


The host group cannot be added to the initiator or external port.

Change is not possible because logical paths remain on the RCU target port.

Change is not possible because logical paths remain on the RCU target port.

Cache Residency cannot be set for this volume because the IO

Suppression mode is set to

Enable.

Cache Residency cannot be set for this volume because the Cache mode is set to Disable.

The system LU cannot be defined for a cross-system copy volume.

The system LU cannot be defined for a cross-system copy volume.

The number of user LU settings exceeded the maximum.

The number of user LU settings exceeded the maximum.

The LUSE volume cannot be set because the cross-system copy volumes do not have the same

I/O suppression mode and the same cache mode.

The LUSE volume cannot be set because the cross-system copy volumes do not have the same

I/O suppression mode and the same cache mode.

Paths cannot be added to Journal volumes.

Paths cannot be added to Journal volumes.

The port type is incorrect.


To add the host group, change the attribute of the specified port to


The specified port is for Fibre

TrueCopy. Delete the logical path, and then set up the port.

Change the IO Suppression mode of this volume to Disable, and then retry the operation.

Change the Cache mode of this volume to Enable, and then retry the operation.

None.



Error Code

3,1365

1005,1365

3,1367

1005,1367

3,1368

1005,1368

3,1600

1005,1600

3,1601

1005,1601

3,1602

3,1603

Description

The LUSE volume cannot be configured because external volumes of different drive types

(normal, SATA) cannot be mixed.

The LUSE volume cannot be configured because external volumes of different drive types

(normal, SATA) cannot be mixed.

The host mode "4C" is specified for a host group connected to a volume that cannot be used for

Universal Volume Manager.

The host mode "4C" is specified for a host group connected to a volume that cannot be used for

Universal Volume Manager.

The host mode "4C" can only be used with Universal Volume

Manager volumes.

The host mode "4C" can only be used with Universal Volume

Manager volumes.

The PP (program product) cannot be installed because LUN Manager functionality is required.

Alternatively, the PP cannot be used because it has expired.

The PP (program product) cannot be installed because LUN Manager functionality is required.


The PP (program product) has not been installed to use OPEN

Volume Management functionality. Alternatively, the PP cannot be used because it has expired.

The PP (program product) has not been installed to use OPEN

Volume Management functionality. Alternatively, the PP cannot be used because it has expired.

The PP (program product) has not been installed to use VLL functionality. Alternatively, the PP cannot be used because it has expired.

The PP (program product) has not been installed to use Cache

Residency functionality.



Install the required PP (Program

Product). (Since there are 3 types of

PP licenses, a different type of license might not be able to be installed after a given license expires).


Product). (Since there are 3 types of




3-23

3-24

Error Code

3,1604

5205,1606

5205,1607

5205,1608

5205,1609

5205,1610

5205,1611

5205,1612

3,1900

3,1901

3,1904

105,1904

605,1904

1005,1904

Description

This functionality is not available.

Cache Residency z/OS is required.

The program product Volume

Migration has not been installed.

Volume Security is already set for the specified volume.

Volume Security is already set for the specified volume.

Volume Retention Manager is already set for the specified volume.

Volume Retention Manager is already set for the specified volume.

Read Only, Protect, or S-VOL

Disable has been set for the Data

Retention of the specified volume.

Read Only, Protect, or S-VOL

Disable has been set for the Data

Retention of the specified volume.

Maintenance operations by the

SVP are being performed. Wait for the maintenance to finish, and then retry the operation.

You cannot make Cache

Residency settings for Crosssystem Copy LUs.

The specified volume cannot be assigned as a LUSE volume or a command device and the path cannot be set, because the specified volume is being used as a data pool volume




None.



Product).

None.

Wait a while, and then re-execute.


None.



3,1906

105,1906

605,1906

1005,1906

3,1910

105,1910

3,1911

105,1911

3,1912

Error Code

3,1905

105,1905

605,1905

1005,1905

1005,1912

3,1913

Description

There are both V-VOLs and non-

V-VOLs among the volumes specified to configure the LUSE volume.







The specified volume cannot be set as a command device because it is being used as a V-VOL.




The specified volume contains a

COW Snapshot pair.

The specified volume contains a

COW Snapshot pair.

The specified volume contains a data pool volume.

The specified volume contains a data pool volume.

A command device setting or command device security setting cannot be set or released because the specified volume is a remote command device.

A command device setting or command device security setting cannot be set or released because the specified volume is a remote command device.

The setting cannot be made because the specified LDEV is a remote command device.

None.




3-25

3-26

Error Code

3,1914

3,1915

3,1916

3,1917

1005,1918

3,1919

1005,1920

1005,1921

1005,1922

*,2002

3,2003

5205,2003

3,2004


The number of virtual volumes has exceeded the maximum number that can be set in a disk subsystem.

The specified LDEV number is incorrect. An LDEV number of a

CU group that is not set in CHA cannot be specified.

Volumes in the same parity group cannot be set across multiple CU groups.

Volumes in CLPR cannot be set across multiple CU groups.

An external volume is mapped to the target external port. Delete the external volume that is mapped to the target external port, and then retry the operation.

The newly added LDEV has not been formatted. The LDEV remains blocked. If you continue this operation, the LDEV cannot be referred from the host. Be sure to format the LDEV.

The path definition between a

NAS cluster and LDEV is incorrect.

- The same LDEV is specified in different NAS clusters. - In the

CHN pair of the same NAS cluster, different LUNs are specified for the same LDEV.

The specified volume is not an

LUSE volume.

LDEVs that are not normal are included in the component of a

LUSE volume.

An attempt to connect the communication between DKCs

(SVP) has failed.

An attempt to retrieve the configuration information from the

DKC (SVP) has failed.

An internal process is being executed, or maintenance is in progress. Wait a while, and then re-execute.

An attempt to load files necessary for application execution has failed. (Memory is insufficient or the necessary files do not exist.)

None.

Revise the LAN settings. If the same problem occurs after revising the settings, contact the Support Center.

From the SVP, make sure that the status of the DKC is normal. If the problem persists after checking the status, contact the Support Center.

Make sure that a maintenance operation is not in progress, wait a while, and then re-execute.

Since it is likely that there is insufficient memory, reboot the SVP, then retry. If the problem persists after revising the settings, contact the

Support Center.



Error Code

3,2005

3,2009

3,2010

1005,2010

*,2011

2,2011

3,2011

3005,2011

3205,2011

5205,2011

3,2012

3,2013

3,2014

Description

The memory required for execution could not be reserved.

The SVP or DKC microcode cannot execute the request. (The version cannot execute the request.) If the same error occurs despite retrying, contact the Support

Center.

The LDEV is being used by the host, or an error occurred in the subsystem. Recovery processing may take about one minute. Wait a while, and then try again.

The LDEV is being used by the host, or an error occurred in the subsystem. Recovery processing may take about one minute. Wait a while, and then try again.

There may be a blocked component. Contact the Support

Center.

The subsystem configuration is invalid. Contact the Support

Center.

Some of volumes may be blocked, or there may be a module in a status that requires maintenance

(for example, a module is blocked, the shared memory is inconsistent, or some other factor). Check the status of the volumes. If the volumes are not blocked, call the Support Center.

The subsystem requires maintenance (for a problem such as a blocked state, or inconsistent shared memory). Contact the

Support Center.

The disk subsystem requires maintenance (due to a problem such as a blockage or shared memory inconsistency). Contact the support center.

The specified volume is already being used by remote copy.

A port blockage error has occurred. Contact the Support

Center.

A download error has occurred.


A port recovery error has occurred. Contact the Support

Center.


Revise the versions of microcode in the SVP and DKC. If you cannot solve this problem, contact the Support

Center.

Check if the host is performing I/O operations on the target path or volume.

Check the DKC status (for blockage).

If this problem persists, contact the

Support Center.


None.

None.

Release the Remote Copy Pair.




3-27

3-28

3205,2015

2,2016

3,2017

3,2022

5205,2024

5205,2025

5205,2026

5205,2027

5205,2028

5205,2029

5205,2030

3,2032

1005,2032

3,2033

Error Code

*,2015

2,2015

3005,2015

3,2016


A communication error occurred.

If the same error occurs despite retrying, contact the Support

Center.


Center.

An error occurred during communication with the subsystem. Wait for a while, and then retry the operation.

An error occurred while connecting to the subsystem.


The subsystem is refreshing, or some other user is changing the configuration. Wait a while, and then re-execute.

An SNMP user or maintenance person is accessing the system in

Modify mode. Wait a while, and then re-execute.

A network error was detected.

The exclusive lock has been released.

The SVP and DKC are running VLL processing. Wait a while, and then re-issue the request to set the configuration information.

The controller detected blocked hardware.





A data transfer failure was detected.

A data transfer failure was detected.

Communication is busy. Wait a while, and then re-execute.


Initial startup is being performed, or an internal refresh operation is in progress.


Revise the LAN settings. If the same result occurs despite retrying, contact the Support Center.


None.

None.


Re-execute the request for starting an exclusive lock.

Wait a while, and then issue a request to change the configuration again.



Wait a while, and then reissue the request to change the configuration.



Error Code

3,2080

3,2081

3,2082

1005,2082

3,2083

3,2084

3,2085

105,2085

605,2085

3005,2085


An attempt at pre-stage processing has failed.

An error occurred during custom volume installation or uninstallation. Retry the operation.

Processing is disabled because the host is mounted or the device is reserved.

The host is mounted or the device is reserved. Unmount the host and cancel reservation of the device. If the host is an AIX host, unmount the host, and then execute the varyoffvg command.

Processing is disabled because the host is mounted or the device is reserved.

An error occurred during the process to change the configuration on the DKC.

The result of changing the configuration is unknown.

An error was detected in the precheck of the VLL operation.

Copying is in progress for the

TrueCopy, ShadowImage,

FlashCopy Mirror, or Cross-system

Copy pairs. Wait a while, and then re-execute.






Copying is in progress for Crosssystem Copy pairs. Wait a while, and then re-execute.






Wait a while, click the Refresh button, and then make the same configuration change again.

Alternatively, check the DKC status (if it is blocked). If the same result occurs, contact the Support Center.


Support Center.

Check the DKC status and current configuration settings. If necessary, re-execute the setup operation.




3-29

3-30

Error Code

3205,2085

3,2086

105,2086

605,2086

3005,2086

3205,2086

*,2087


Copying is in progress for Remote

Copy, ShadowImage,

ShadowImage z/OS, Volume

Migration, FlashCopy Mirror, COW

SnapShot, or Cross-system Copy pairs. Wait a while, and then retry the operation.

The configuration of Remote

Copy, ShadowImage,



SnapShot, or Cross-system Copy has been defined. Reset the configuration definition, and then retry the operation.


Copy, ShadowImage,




The configuration of Cross-system

Copy is defined. Reset the configuration definition, and then retry the operation.


Copy, ShadowImage,







SnapShot, or Cross-system Copy pair is defined. Release the pair definition, and then retry the operation.

An error was detected in the precheck of the VLL operation. Vary

Online has been issued from the mainframe host to the DKC subsystem. Make the DKC subsystem offline from the mainframe host.

None.

Release the configuration definition, and then re-execute.

None.

None.

Make the DKC subsystem offline from the mainframe host.



Error Code

605,2087

3005,2087

3205,2087

*,2088

3005,2088

3205,2088

*,2089

3005,2089

3205,2089

3,2090

105,2090

605,2090

Description

The subsystem is online to the mainframe host. Take the subsystem offline from the host.

The subsystem is online to the mainframe host. Take the subsystem offline from the host.

The system is varied online from the mainframe host. Perform a

Vary Offline operation on the connected mainframe host.


TrueCopy is suspended. Add an alternative path.

The Remote Copy pair is suspended. Add an alternative path.

The Remote Copy pair is suspended. Add an alternate path.

An error was detected in the precheck of the VLL operation. The corresponding CHA might contain the last path between the MCU and RCU of remote copy. Make sure that there is an alternative path from the MCU.

The target CHA might contain the last path between the MCU and

RCU of Remote Copy. Make sure that there is an alternative path from the MCU.

The corresponding CHA might contain the last path between the

MCU and RCU of Remote Copy.

Make sure that there is an alternative path from the MCU.

An error was detected in the precheck of the VLL operation. The

ShadowImage, FlashCopy Mirror, or Cross-system Copy settings exist. Either reset the settings or stop the I/O operations, and then retry the operation.

An error was detected in the precheck of the VLL operation. The

ShadowImage, FlashCopy Mirror, or Cross-system Copy settings exist. Either reset the settings or stop the I/O operations, and then retry the operation.

The Cross-system Copy settings exist. Either reset the settings or stop the I/O operations, and then retry the operation.

None.


Add an alternative path.

None.

Make sure that there is an alternative path from the MCU.

None.

Release the ShadowImage, FlashCopy

Mirror, or Cross-system Copy settings. Alternatively, stop the I/O operations, and then re-execute.

Release the ShadowImage, FlashCopy

Mirror, or Cross-system Copy settings. Alternatively, stop the I/O operations, and then re-execute.

Either reset the settings or stop the

I/O operations, and then re-execute.



3-31

3-32

Error Code

3005,2090

*,2091

3,2091

605,2091

3005,2091

3205,2091

3,2092

105,2092

605,2092

3005,2092

3,2093

105,2093


ShadowImage, ShadowImage

Mainframe, FlashCopy Mirror, or

Cross-system Copy settings exist.

Release the settings or stop the

I/Os, and then retry the operation.

An error was detected in the precheck of the VLL operation. The backup server of ShadowImage or

FlashCopy Mirror is running. Stop the backup server, and then retry.

The backup server of

ShadowImage, ShadowImage z/OS, or FlashCopy Mirror is running. Stop the backup server, and then retry the operation.







Some ShadowImage, FlashCopy

Mirror, or Cross-system Copy pairs are included. Separate them.

Some ShadowImage, FlashCopy

Mirror, or Cross-system Copy pairs are included. Separate them.

Some Cross-system Copy pairs are included. Separate them.

Some ShadowImage,

ShadowImage Mainframe,


Copy pairs exist. Split these pairs.

An error was detected in the precheck of the VLL operation. Some

ShadowImage, FlashCopy Mirror,

Cross-system Copy pairs are included. Resynchronize them.


ShadowImage, FlashCopy Mirror,

Cross-system Copy pairs are included. Resynchronize them.

None.

Stop the backup server and then reexecute.

None.

Separate ShadowImage, FlashCopy

Mirror, or Cross-system Copy pairs.

Split the Cross-system Copy pairs.

None.

Resynchronize the age,

ShadowImage, FlashCopy Mirror, or

Cross-system Copy pairs.

Resynchronize the age,


Cross-system Copy pairs.



Error Code

605,2093

3005,2093

3,2094

105,2094

605,2094

3005,2094

*,2095

3,2095


Some Cross-system Copy pairs are included. Resynchronize them.

Some ShadowImage,



Copy pairs exist. Resynchronize these pairs.


ShadowImage, FlashCopy Mirror, and Cross-system Copy pairs are included. Change the status of their volumes to Simplex.


ShadowImage, FlashCopy Mirror, and Cross-system Copy pairs are included. Change the status of their volumes to Simplex.

Some Cross-system Copy pairs are included. Change the status of their volumes to Simplex.

Some ShadowImage,



Copy pairs exist. Change their volumes to Simplex.

An error was detected during the pre-check of the VLL operation. A maintenance operation is in progress (for example: 1) LDEV formatting is in progress, 2) correction copy is in progress, 3) drive copying is in progress, 4) the channel status is changing, 5) the cache status is changing, or

6) OEM drive micro conversion is in progress).

A maintenance operation is in progress. For example: LDEV formatting is in progress.

Correction Copy is in progress.

Drive Copy is in progress. The

CHA/DKA status is changing. The cache status is changing.

Replacement of an OEM drive microprogram is in progress.

LDEV Shredding is in progress.

Extent Shredding is in progress.

Therefore the specified operation cannot be executed.

Resynchronize the Cross-system Copy pairs.

None.

Change the status of the


Cross-system Copy volumes to

Simplex.

Change the status of the Crosssystem Copy volumes to Simplex.

None.


None.



3-33

3-34

Error Code

105,2095

3005,2095

3205,2095

3,2096

3,2097

1005,2097

3,2098

1005,2098

3,2099

1005,2099

Description

















Other maintenance processing or error processing is executing.

An error was detected during the pre-check of the VLL operation.

The currently running microcode version does not support the specified operation.

The host specified by the WWN is performing I/O operations.

The host specified by the WWN is performing I/O operations.

The operation cannot be performed because the SVP microcode version does not match the DKCMAIN (subsystem) microcode version.

The operation cannot be performed because the SVP microcode version does not match the DKCMAIN (subsystem) microcode version.

The operation cannot be performed because an inoperative

MP exists.

The operation cannot be performed because an inoperative

MP exists.

None.



Stop executing the I/O operations from the host, and then re-execute.

If this problem occurs no matter how many times the operation is retried, contact the Support Center.

Wait a while, and then re-execute. If the same result occurs, contact the

Support Center.



Error Code

3,2100

1005,2100

3,2106

*,2145

3,2170

1005,2170

*,2200

3005,2200

3205,2200

*,2201


An error occurred during communication with the disk subsystem. The configuration may be inconsistent. Click [Refresh All] and refresh the configuration.


Maintenance personnel are accessing in the Modify mode.

A connection error has occurred.

None.



Stop the host I/O operations. Extended Copy Manager is running, but I/O operations might be in progress. Stop the I/O operations from the host.

Extended Copy Manager is running, but I/O operations might be in progress. Stop the I/O operations from the host.

Concurrent copying or the

Extended Remote Copy operation is in progress on the target volumes. Cancel the Concurrent copy job or delete a Extended

Remote Copy pair via the host.

If a concurrent copy or Extended

Remote Copy operation is in progress in the maintenance-target volume, cancel the concurrent copy job or delete the Extended Remote Copy pair via the host. If a concurrent copy or Extended Remote Copy operation is not in progress, issue the LISTSESS or LISTDVCS command to all the maintenance-target volumes, check the session ID number, and then use the TERMSESS command to end the session.

None. Concurrent Copy or XRC

Replication is executing on the volumes to be maintained.

Terminate the Concurrent Copy job or delete the XRC Replication pair from the host.

Concurrent Copy or XRC

Replication is currently executing on the maintenance-target volume. Cancel the Concurrent

Copy job or delete the XRC

Replication pair from the host.

Processing cannot be performed because of the Data Retention settings.

Correct the settings, and then reexecute.



3-35

3-36

Error Code

3005,2201

3005,2202

3005,2203

3,2204

3005,2204

3,2205

105,2205

605,2205

3005,2205

3,2500

1005,2500

3,2501

1005,2501


Processing cannot be performed because there are Data Retention settings.

The specified volume cannot be processed due to the effect of the access attribute assigned by

Volume Retention z/OS.

Processing cannot be performed because of Volume Security settings.

Devices to be maintained include journal volumes. Delete or suspend all pairs belonging to journal volumes to be maintained.

Devices to be maintained include journal volumes. Delete or suspend all pairs belonging to journal volumes to be maintained.

Devices to be maintained include journal volumes. Delete all pairs belonging to journal volumes to be maintained.

The devices to be maintained include journal volumes. Delete all the pairs that belong to the journal files to be maintained.

Journal volumes are included in the external volumes to be maintained. Delete the journal volumes to be maintained, and all the pairs that are using these journal volumes.

Devices to be maintained include journal volumes. Delete all pairs belonging to journal volumes to be maintained.

Paths from NAS system or iSCSI ports to volumes that do not have the Read/Write attribute cannot be set.

Paths from NAS system or iSCSI ports to volumes that do not have the Read/Write attribute cannot be set.

The volume cannot be configured as a command device because the volume does not have the


The volume cannot be configured as a command device because the volume does not have the


None.




Error Code

3,2502

1005,2502

3,2503

1005,2503

3,2504

1005,2504

105,2511

105,2512

3,2515

105,2515

Description





No settings can be made because there is a volume reserved for

RAID Manager.

No settings can be made because there is a volume reserved for

RAID Manager.

The restore operation failed because an LDEV format operation or shredding was not implemented for the specified

LDEV.

The restore operation failed because the specified LDEV could not be accessed. Contact the

Support Center.

One of the following is defined: a

Remote Copy pair, a Universal

Replicator pair, or a Universal

Replicator z/OS pair.

Alternatively, command devices defined by BC Manager are included. Cancel the pair definition or delete command devices defined by BC Manager, and then retry the operation.






None.




3-37

3-38

Error Code

605,2515

3,2516

105,2516

605,2516

3,2517

105,2517

605,2517

Description









Replicator z/OS pair. Cancel the pair definition or suspend the pair, and then retry the operation.










ShadowImage pair, a

ShadowImage z/OS pair, a

FlashCopy Mirror pair, or a Crosssystem Copy pair. Cancel the pair definition, and then retry the operation. If the high-speed split mode is on, suspend the pair and then cancel the pair definition.


ShadowImage pair, a


FlashCopy Mirror pair, or a Crosssystem Copy pair. Cancel the pair definition, and then retry the operation. If the high-speed split mode is on, suspend the pair and then cancel the pair definition.

A ShadowImage, ShadowImage z/OS, FlashCopy Mirror, Crosssystem Copy, or COW SnapShot pair is defined. Cancel the pair definition, and then retry the operation. If the high-speed split mode is on, suspend the pair and then cancel the pair definition.

None.




Error Code

3,2518

105,2518

605,2518

3,2519

105,2519

605,2519

3,2520

105,2520

Description


ShadowImage pair, a


FlashCopy Mirror pair, or a Crosssystem Copy pair. Cancel the pair definition, and then retry the operation. If a reserve volume is defined, cancel the definition of the reserve volume. If the highspeed split mode is on, suspend the pair and then cancel the pair definition.


ShadowImage pair, a




ShadowImage pair, a



The volume is reserved by

ShadowImage or ShadowImage z/OS. Cancel the definition of the reserve volume, and then retry the operation.





A Volume Migration pair is defined. Delete the pair definition, and then try again.





3-39

3-40

Error Code

605,2520

3,2521

105,2521

605,2521

3,2522

105,2522

605,2522

1,3000

3,3000

1,3001

Description


A Volume Migration pair is defined. Delete the pair definition.

Also, if a reserved-volume is defined, delete the reservedvolume definition, and then try again.





The volume is defined as a

Volume Migration reservedvolume. Delete the reservedvolume definition, and then try again.






Center.

An attempt to acquire an external function pointer required by the application has failed. Contact the

Support Center.

The number of set operations exceeds the maximum (20000).

None.


This error status might remain internally in the health check function log after a forced release of the

Modify mode, but this is not a problem. In other cases, contact the

Support Center.

Reboot the SVP, then retry. If the problem persists, contact the Support

Center.

Reduce the number of Set operations, and then re-execute.



6,4000

6,4002

1,4003

1,4004

1,4005

1,4011

1,4012

1,4013

Error Code

3,3001

*,3002

1,3002

3205,3003

3,3004

3,3005

3,3006

3,3007

Description

An attempt to acquire the external function pointer for obtaining trace information has failed. Contact the Support

Center.

An invalid interface was detected in the applications. Contact the

Support Center.


Center.

An error occurred during processing on the SVP. If it happens again, contact the support center.

The process to manage the configuration information has failed. Contact the Support

Center.

The process to manage the configuration information has failed. Contact the Support

Center.

A file access error occurred for the file required by the application. Contact the Support

Center.

An interface logical error was detected in the agent, or a nonregistered error occurred. Contact the Support Center.


Center.

There is no data in the authentication file, so login failed.

Login failed. The entered user ID is invalid.

Login failed. The entered password is invalid.

The user name is already logged in.

There is no RMI object or forced logoff was carried out.


Reboot the SVP, then retry. If the problem persists, contact the Support

Center.

Reduce the number of set characters.

None.

The directory for MIB management information does not exist. Contact the Support Center.

An attempt to write the MIB management information has failed.



The authentication data must be registered. Contact the Support

Center.

Enter the correct user ID, and then log on again.

Enter the correct password, and then log on again.


Log on again. If this problem persists, increase the value of the RMI timeout period.

Wait a while, and then log on again. The number of connections exceeds the maximum (32).


Center.

An attempt to access the config file has failed. Contact the Support

Center.



3-41

3-42

405,5047

405,5070

405,5071

405,5072

6007,5074

405,5075

405,5076

405,5079

405,5080

405,5087

Error Code

1,4020

5305,5000

3205,5013

5305,5018

2,5040

6505,5040

9505,5041 group.

Description

A network error was detected, so the exclusive lock was forcibly released.

A character in the WWN is invalid.

Use 0-9, A-F, hyphens (-), and spaces.


The entered value is invalid. Enter a valid value (0-65535).

The number of requests exceeds the maximum number that can be processed. Reduce the number of requests, and then retry the operation.

Too many objects are specified.

The maximum number of the initiators and the host groups is respectively 32 and 64 per port

An error occurred during installation/uninstallation.

The product name is different.

Select the correct program product name.

The license key cannot be installed. A Temporary key is installed.

The existing capacity of the licensed program product is invalid.

TrueCopy or TrueCopy Mainframe is not installed.

This key code is invalid.


The lock was released. If necessary, re-execute the request for applying the exclusive lock.


None.

Enter a correct value.

None.

Reduce the number of specified objects, and then retry the operation.

Check the number of initiators and the host groups registered in the port group.

If the same error occurs despite reexecuting many times, contact the

Support Center.

Review the program product code, and then re-set.

Obtain the official license to use this software.

Obtain the appropriate license.

Install TrueCopy or TrueCopy

Mainframe.

Make sure that the key code is correct.

Check the DKC Serial Number. The serial number is invalid.

Correct it.

This program product needs another DKC type.

This program product cannot be changed.

This PP (program product) cannot be processed because an error occurred in another PP.


Specify a setting other than ALL

Normal.



5305,5101

*,5102

5305,5104

5305,5105

5305,5106

5305,5107

5305,5108

5305,5109

5305,5110

5305,5111

5305,5112

5305,5113

5305,5114

5307,5128

2,5130

Error Code

507,5099

1,5132

Description


The specified WWN is not registered.

The specified PPC group is not registered.

The specified PPC group is already registered.

The specified port does not implement the WWN subject to monitoring.

The target WWN is already registered as a target of monitoring in the specified port.

The specified nickname is already used.

The specified nickname is already used.

The specified ports exceed the maximum number of WWN's subject to monitoring.

The number of WWNs exceeds the max. that can be registered as monitoring targets.

The number of WWNs that can be registered in the PPC group exceeds the maximum.

The specified WWN belongs to the

PPC group.

The specified WWN belongs to the

PPC group.

The selected WWNs have different operating modes specified.

The number of PPC groups that can be registered exceeds the maximum.

A sequence error occurred.


A user with the same user ID is already logged on.

None.


Check the settings, and then reexecute.

Check the specified contents, and then re-execute.

Connection was terminated from the subsystem because of a network failure. Log on again. This error might remain internally in the unlock function log when the Exit button is clicked in View mode, but this should not be a problem. If it is a problem, contact the Support Center.

Log on with a different user ID. Also, there is a possibility that the previous termination process was performed incorrectly. After the RMI timeout

(default = 1 min.), log on again.



3-43

3-44

Error Code

5,5200

5,5201

5,5202

5,5203

5,5204

1,5400

405,5501

405,5502

5205,5504

5205,5505

5205,5506

5205,5507

1,5508

1,5509

2,5510

8005,5510

*,5511


This function cannot be used.

SNMP API is required.


Compatible PAV is required.

Install the program product.

Install the program product. When releasing, install the emergency key first, and then release.

Install the program product. This function cannot be used.

Performance Monitor is required.


Volume Migration is required.


Performance Monitor is required.

Monitoring data cannot be acquired because the subsystem is busy.

The extended time for the trial period has been exceeded.

The licensed capacity is insufficient. The program product will not be installed.

The specified volume is being used by Data Migration.

The specified volume is being used by Remote Copy.

The volume specified as the copy source is a Remote Copy P-VOL, and is already being used in a pair whose status is not Suspend.

The specified destination volume is not a Volume Migration destination volume.

An administrator is changing the system environment file. Wait a while, and then log on.

You do not have lock permissions.

Switch to the lock mode and then operate.

This subsystem is internally processing, otherwise another user is changing the configuration or performing maintenance. Wait a while, and then re-execute.

This subsystem is internally processing, otherwise another user is changing the configuration or performing maintenance. Wait a while, and then re-execute.

The PP (program product) is not installed. Install the PP, and then re-execute.


Alternatively, if other users have the

Performance Monitor window open, or the Export Tool is executing, then:

Check the program product installation status.

Increase the licensed capacity.

Release the Data Migration settings.

Release the Remote Copy pair.

Re-execute. If the execution result is the same, contact the Support

Center.

Wait a while, and then log on.

When setting up, change to Modify mode.



Install the required program for this function, and then re-execute.



9105,5600

9105,5601

9105,5602

9105,5603

9105,5604

9105,5605

9105,5606

9105,5607

9105,5608

*,5624

*,5625

Error Code

405,5524

405,5525

1,5550

1,5551

1,5552

1,5554


This license key cannot be installed because a usable environment has not been prepared.

The S-Vol Disable setting of the

Data Retention still remains.

The same user ID is already registered. Check the setting, and then retry the operation.

NULL characters or blank spaces are used in the user ID. Check the setting, and then retry the operation.

A character used for the user ID or the number of the characters of the user ID is invalid. Check the setting, and then retry the operation.

The storage device Administrator user (built in-account) cannot be added or deleted. Revise the setting, and then retry the operation.

The security group settings are incorrect.

The host group settings are incorrect.

The string length is incorrect.


Release the S-Vol Disable setting.

None.

The host type has been specified as DKC emulation.

The specified vendor information is incorrect.

The number of hosts that can be registered has been exceeded.

The target LDEV is not implemented.

The LDEV group settings are incorrect.

The pool group cannot contain volumes that have defined LU paths or are not implemented.

The specified volume cannot be set because it is being used as a

NAS system volume.

Another pair cannot be created because the number of pairs defined in the group exceeds the maximum.

Correct the security group settings, and then re-execute.

Correct the host group settings, and then re-execute.

Correct the number of characters of the entered title, and then reexecute.

Specify a different host, and then reexecute.

Correct the specified vendor information, and then re-execute.

Delete any unnecessary hosts, and then re-execute.

Delete the unimplemented LDEV, and then re-execute.

Correct the LDEV group settings, and then re-execute.

Check the attributes of the specified volumes, and then re-execute.


Decrease the number of pairs, and then re-execute.



3-45

3-46

Error Code

*,5626

7005,5655

9607,5804

9605,5809

9105,5819

9105,5820

*,5821

3205,5827

3205,5828

3005,5872

3005,5874

3005,5875

4,6001

507,6012

1205,6012


The specified volume cannot be used because the write protection is set by Volume Retention z/OS.

You cannot set a pair because the

LBA number is different for the specified volume.

The format of the pattern file is invalid.

The number of requests for combining LUs was not set for the

LU-combined volumes.

The specified port is not supported by this function.

When a host group contains a host to which ports are set, the hosts in that host group cannot be registered in a different host group.

The operation was rejected. The specified volume is set with an attribute that prevents S-VOL specification for Volume Retention z/OS.



The first volume of the expanded

LU volumes has not been specified.

A program product required for using the shredding function has not been installed.

The specified volume is being formatted or shredding.

A timeout occurred. The SVP will reboot. After rebooting finishes, re-execute.

Change the Volume Retention z/OS settings.

Select another volume which has a matching LBA number.

None.

Check the logical devices, and then re-execute.

Specify a port supported by this function.

Check the specified host and port.

Change the Volume Retention z/OS settings so that an S-VOL can be specified.

None.

The SVP will automatically reboot. If the same result occurs after starting and re-executing, contact the Support

Center.

None. An error occurred during processing on the SVP. If it happens again, contact the support center.


Center.

The necessary memory for the settings cannot be secured. Reexecute. If the same result occurs, contact the Support Center.



5305,6023

6005,6023

6007,6023

6805,6023

7005,6023

9105,6023

6007,6024

4,6037

9605,6038

Error Code

3205,6012

1,6022

405,6022

3205,6022

5205,6022

5305,6022

6007,6022

6505,6022

3205,6023

Description

An error occurred during processing on the SVP side. If this problem persists, contact the support center.

A file open error has occurred.

The SVP is busy. Wait a while, and then re-execute.


File access has failed. Wait a while, and then re-execute.

A file open error occurred.


A file open error has occurred.


A file access error occurred.

None.


Retry the operation. If the same result occurs, contact the Support

Center.

None.

If this problem occurs no matter how many times the operation is retried, contact the Support Center.



Center.

None.




Center.


The SVP is busy. Wait for a while, and then retry the operation.


None.

File operation has failed.

An error occurred. If this problem persists, contact the Support

Center.

The DKC status is incorrect.


The set parameter is incorrect.


Center.





Support Center.



3-47

3-48

7,6091

7,6092

7,6093

*,6501

*,6502

2,6502

*,6510

4105,6510

5205,6511

5205,6512

*,6513

1205,6515

9505,6515

Error Code

3005,6050

505,6502

9005,6502

*,6503

505,6506

505,6507



An error occurred while compressing a file.

An error occurred while reading a file.

The file to be downloaded was not found.

There is no monitoring data.



A timeout error occurred. Wait a while, and then re-execute. If processing still cannot execute, contact the Support Center.

This key code is invalid.

The target volume is changing to

SMPL.

Communication is busy. Reexecute later.

The maximum allowable capacity of the program product became insufficient.

None.

None.

Wait a while, and then re-execute. If the problem persists, contact the

Support Center.

Wait a while, and then log on again.

If the same result occurs after retrying the same operation many times, contact the Support Center.


Check the controller status, and then re-execute.

If you use the Just In Time function, the permitted capacity of the PP

(program product) might become insufficient. Install any PP for which permitted capacity might be insufficient, and then execute.


Support Center.


An internal lock time-over has been detected. Wait a while, and then re-execute.

The disk subsystem is busy. Wait a while, and then re-execute.

Check the pair status.


Another request was received during processing.

The specified host is performing

I/O operations.

Extended Copy Manager is operating, but host I/O operations might be in progress. Stop the host I/O operations.



Stop the host I/O operations.



105,6534

605,6534

105,6535

605,6535

3205,6535

105,6536

605,6536

3205,6536

1,6540

Error Code

405,6517

*,6531

5205,6532

105,6533

3205,6533

1,7003

3005,7060

Description

Serverless Backup is running, but the host I/O operations might not have stopped. Stop the host I/O.



The subsystem is now acquiring the latest data. Wait a while, and then re-execute.



The number of external volumes that can be set to the subsystem exceeds the maximum.

The number of external volumes that can be set to the subsystem exceeds the maximum.

You cannot make changes because a logical path to the volume still remains.



The target volume cannot be changed due to its LUSE configuration.



No more users can be registered because the number of registered users has reached the maximum.

Reduce the number of users, and then retry the operation.

The content of the management file of the audit log is invalid.



Center.


Support Center.

None.



3-49

3-50

Error Code

507,7070

405,7101

9607,7118

9607,7119

9607,7120

405,7202

505,7202

405,7203

405,7205

*,7310

1205,7310

3005,7310

Description



Center.

A parameter error occurred. If this problem persists, contact the

Support Center.


Support Center.


Support Center.


Center.

Some of volumes may be blocked, or there may be a module in a status that requires maintenance

(for example, a module is blocked, the shared memory is inconsistent, or some other factor). Check the status of the volumes. If the volumes are not blocked, call the Support Center.


Center.


Center.

An unregistered error code occurred.

This error code is not registered.


None.




Support Center.

Order a license that has the appropriate capacity.

None.


Check the name of the program product that is to be installed.


Support Center.

None.

Check the setting contents, and then re-execute.



Error Code

5205,7400

5205,7401

5205,7402

5205,7403

5205,7404

5205,7405

5205,7406

5205,7407

5205,7408

5205,7409

5205,7410

5205,7411

5205,7412

5205,7413

5205,7414

5205,7415

5205,7416

5205,7417

5205,7418

5205,7419

5205,7420

5205,7421

5205,7422

5205,7423

5205,7424

Description

The file might not be in the designated directory.







A correct migration plan cannot be created for this function.

There is not enough Volume

Migration data to create a plan.

An attempt to write to the plan file has failed.



The file contents are incorrect.






The configuration information is incorrect.

The reserved volume information is incorrect.

There is not enough Volume

Migration data to create a plan.

The proper plan cannot be created. Check the following: 1.

Reserved volume location 2.

Maximum disk usage rate

Memory allocation has failed.


An attempt to delete all the plans has failed.


Retry the operation several times. If the same result occurs, contact the

Support Center.



3-51

3-52

Error Code

5205,7426

9505,7430

9505,7431

9505,7432

4105,7441

*,8000

2,8000

605,8000

3205,8000

*,8001

2,8001

505,8001

3005,8001

3205,8001

5205,8001

An attempt to delete the plan has failed.

Description

The specified ports cannot be set to Extended Copy Manager.

External ports for the high-speed

PCB are not specified. When specifying the external ports for the high-speed PCB, perform setup at the same time.

The high-speed PCB has been setup, but the parameter settings of the external ports do not match.

A specified value is outside the cache capacity range.

A timeout error occurred.



Support Center.

Specify the ports which support

Extended Copy Manager.

When setting up external ports for a high-speed PCB, set up the highspeed PCB at the same time.

Set the same parameters to all the high-speed PCB external ports.

Correct the specified value, and then re-execute.

Make sure that the DKC status is normal, wait a while, and then retry the operation. If the occurrence does not change, contact the Support

Center.

None. An error occurred while connecting to the DKC. Wait a while, and then try again.

An error occurred while connecting to the DKC. Wait a while, and then re-execute.


A timeout error occurred while connecting to the DKC.


Center.

None.

Make sure that the DKC status is normal, wait a while, and then retry the operation. If the occurrence does not change, contact the Support

Center.

None. A communication timeout error occurred.



A communication timeout error occurred on the disk subsystem.





Support Center.

None.


Support Center.



4105,8002

5305,8002

6805,8002

9105,8002

405,8003

4,8010

*,8100

Error Code

6805,8001

9005,8001

9505,8001

9605,8001

*,8002

1205,8002

3205,8002

2,8100

505,8100

3005,8100

Description

A communication timeout error occurred on the DKC. Wait for a while, and then retry the operation.




A connection timeout error occurred in the DKC. Wait a while, and then re-execute.

A timeout error occurred while connecting to the subsystem.






None.


Retry the operation. If you get the same message again, contact the

Support Center.



Support Center.

None.



Support Center.

None. Communication busy. Wait for a while, and then retry the operation.








A timeout error occurred.


Support Center.

Make sure that the DKC status is normal, wait a while, and then retry the operation. If the same result occurs, contact the Support Center.

None. An error occurred while connecting to the subsystem.





Wait for a while, and then retry the operation.

None.



3-53

3-54

*,8102

605,8102

3005,8102

4105,8102

9105,8102

9005,8103

6005,8104

6805,8110

9105,8110

9605,8120

9605,8122

9605,8123

9605,8124

9605,8125

9605,8126

9605,8127

9605,8128

9605,8129

Error Code

5205,8100

9005,8100


This function is not supported.





Support Center.

Check the SSB LOG. Report the output error code and message to the

Support Center.



The SVP and DKC versions do not match.

The SVP and DKC versions do not match.




Support Center.

None.


The pair status has not finished changing yet. Check the configuration and connection-line status of the MCU and RCU, and make sure that the Remote Copy pair status has changed.

Check the version of the DKC-MAIN microcode, and then contact the

Support Center.

The configuration and connection-line status of the MCU and RCU might not satisfy the operating conditions.

Check the configuration and connection-line status of the MCU and

RCU, and make sure that the Remote

Copy pair status has changed.

None. An attempt to change the configuration has failed.

An attempt to change the configuration has failed.

The specified logical device does not exist.

This logical device is busy.



Specify an open-systems volume.

This logical device is a mainframe volume.

Attribute of the logical volume has been changed by RAID Manager.

This logical device is setup as a command device.

This logical device is a NAS system volume.

A parameter error occurred.

This logical device is a Just in

Time volume.


The DKCMAIN and SVP microcode version numbers might not match.

Check each version number.

Specify an open-systems volume.

Check the LDEV information, and then re-execute.

Check the logical device, and then reexecute.


Support Center.




9605,8142

405,8202

405,8203

405,8204

405,8205

405,8206

405,8301

505,8310

Error Code

9605,8130

9605,8131

9605,8132

9605,8133

9605,8134

9605,8135

9605,8136

605,8140

9605,8141

9205,8142


This logical device is a volume for

Cross-system Copy.

This logical device is a NAS system user volume.

The error code is not registered.


This logical device is an iSCSI volume.

You cannot change an attribute of this logical device to Read/Write.

Contact the Support Center if you want to change an attribute.

This logical device is an S-VOL for either TrueCopy or ShadowImage.

The command was rejected because the license capacity was exceeded.

This logical volume cannot be selected because it is used as a

FlashCopy Mirror Version 2 volume.

This logical volume cannot be selected because it is used as a reserve volume for Volume

Migration.


Universal Replicator Mainframe volume.


Universal Replicator volume.

This program product requires a newer microprogram version.


This program product requires a newer hardware version. Contact the Support Center.

This program product requires a different configuration. Contact the Support Center.



This program product is in use, so it cannot be uninstalled.






Support Center.


A logical device attribute cannot be changed to Read/Write. If you want to change the attribute, contact the

Support Center.


The current license capacity is insufficient. To increase the licensed capacity, order a new license key.

None.


Stop using this program product function.


Support Center.



3-55

3-56

*,8500

*,8501

*,8502

*,8503

*,8504

*,8505

605,8505

*,8506

*,8507

605,8507

*,8508

*,8509

*,8511

*,8512

*,8513

Error Code

6805,8310

*,8401

505,8401

Description

The DKC status is invalid. Contact the Support Center.



None.



Support Center.

Contact the Support Center. The disk subsystem requires the maintenance(for a reason such as a blockage or shared memory inconsistency).

The program product is not installed.

The command was rejected because a status transition was in progress.

The reserved volume cannot be set because a Remote Copy pair exists in the same frame.

A new pair cannot be created because a Remote Copy pair exists in the same frame.

The command was rejected.

Re-install the program product.


Delete the Remote Copy pair.

The command cannot execute due to one of the following conditions:

Contact the Support Center. The requested command is incorrect.

The requested command is incorrect.

The command was rejected. The specified S-VOL is being used by the host or a TrueCopy volume.

The Pairsplit command was issued to a pair in a PSUS state.


Center.

Change the specified S-VOL to another volume, or stop using the S-

VOL in the host or TrueCopy, and then re-execute.

The Pairsplit operation cannot be performed because the pair is already in a PSUS state.

None. The Pairsplit command was issued to the pairs in PSUS status.

The Paircreate command was issued to a pair in a PSUS state.

The Split command with the

QUIESCE specification was issued to a secondary startup device.

The volume cannot be reserved because a path group is set.

The Resync or Suspend operations cannot be performed because a path group is set.

The command was rejected. The specified P-VOL is being used by the host or Remote Copy.

The Paircreate operation cannot be performed for pairs in a PSUS state.

Check the contents, and then reexecute.

Detach the S-VOL from the host, or delete the Remote Copy path.

Change the specified P-VOL to another volume, or stop using the P-

VOL in the host or Remote Copy, and then re-execute.



*,8520

*,8521

*,8522

*,8523

*,8524

Error Code

*,8514

*,8515

*,8516

605,8517

7005,8517

*,8518

*,8519


There is no allocatable reserved volume.

The number of cylinders in the reserved volume exceeds the maximum.

The number of P-VOL cylinders exceeds the maximum.

The number of S-VOL cylinders exceeds the maximum.

The number of S-VOL cylinders exceeds the maximum.

Delete the reserved volume.



This pair cannot be created because the track format is different for each.

This pair cannot be set because the number of cylinders is different for each.

Check the emulation type.

Check the volume capacity.

This pair cannot be set because the volume type is different for each.

The number of multiple copy jobs exceeds the maximum.

The P-VOL emulation type is not supported.

Specify the same emulation type, and then re-execute.


Specify an emulation type supported in ShadowImage.

The S-VOL emulation type is not supported.

The emulation type is not supported. error. Retry the operation. If the same result occurs, contact the Support

Center.

*,8532

605,8532

*,8533

605,8534

The P-VOL and S-VOL are being used by the host or Remote Copy.

The P-VOL and S-VOL are being used by the host or by Remote

Copy.

The emulation type of the specified reserved volume is not supported.

An internal logical contradiction occurred.

Check the target volume, or stop using it in Remote Copy.

None.

Specify a volume of a supported emulation type.


Center.



3-57

3-58

*,8551

*,8552

*,8553

*,8554

*,8555

*,8540

*,8542

*,8543

*,8544

*,8545

*,8546

*,8547

*,8548

*,8549

*,8550

Error Code

3205,8534

*,8535

*,8536

*,8537

*,8538

*,8539


An internal logic error occurred. None.

A processor failure was detected. Retry the operation. If the same result occurs, contact the Support

Center.

A cache failure was detected.

The cache capacities do not match.

An SM (shared memory) failure was detected.

There is insufficient shared memory to create 4096 pairs.


Center.

There is sufficient shared memory for 4096 pairs, but the initial settings are not set.

An attempt to complete the initial shared memory setup has failed.

The shared memory capacity does not match.

There is 16 MB of shared memory.

A power supply failure was detected.

Revise the settings, and then reexecute.


Center.

The command was rejected. The

PS OFF is in progress.

A data transfer failure was detected (CHA).

Re-execute the operation with the power on.


Center.

A data transfer failure was detected (DKA).

The P-VOL is not implemented.

The P-VOL cannot be used.

The P-VOL is being formatted.

The P-VOL is a command device.

The S-VOL is not implemented.

The S-VOL cannot be used.

The S-VOL is being formatted.

This operation cannot be performed for unimplemented volumes.


Center.

Wait until the volume finishes formatting, and then re-execute the operation.

Check the target volume.



Center.




*,8570

*,8571

*,8572

*,8573

*,8574

*,8575

*,8576

*,8577

*,8560

*,8561

*,8562

*,8563

*,8564

*,8565

*,8566

*,8567

*,8568

*,8569

Error Code

*,8556

*,8557

*,8558

*,8559

Description

The S-VOL is a command device.

The target volume is not implemented.

The target volume cannot be used.

The target volume is being formatted.


Check the target volume.



Center.


Check the target volume. The target volume is a command device.

The command code is incorrect.

The command code sender is incorrect.

The volume type is incorrect.

The volume type is incorrect.

The command code sender is incorrect.

A reserved volume attribute is incorrect.

The number of valid lists is incorrect.

The emulation type is incorrect.

Check the contents, then re-execute.


The number of multiple jobs exceeds the maximum.

The selected volume does not exist.

The volume is already defined as reserved.

The volume is already defined as a P-VOL.


Volume Migration source volume.


Volume Migration destination volume.

The selected volume is not a reserved volume.

There are no reserved volumes that can be set.

The maximum number of reserved volumes that can be defined has been exceeded.

Specify a volume of a supported emulation type.


Center.

Check the settings, then re-execute.

Check the corresponding conditions.


Stop the reserved volume setting operation, or delete the reserved volume.



3-59

3-60

*,8586

*,8587

*,8588

*,8589

*,8590

*,8591

*,8592

*,8593

*,8594

*,8595

*,8596

*,8597

*,8598

*,8579

*,8580

*,8581

*,8582

*,8583

*,8584

*,8585

Error Code

*,8578

Description

This P-VOL cannot be paired with the targeted volume, because this

P-VOL is already paired with a backup volume.

The reserved volume is not defined.

The specified volume is only for backup servers.

The specified volume is not only for backup servers.

The emulation type of the target volume is being changed.


The reserved volume is not defined.

The number of reserved volumes exceeds the maximum.



Define the reserved volume, then reexecute.

This volume cannot be used. Specify another volume, then re-execute.


Wait a while, then re-execute.

Specify a volume of a supported RAID level.


The number of groups that can be set in the same subsystem is incorrect.

The number of pairs that can be set in the same group is incorrect.

The specified group number is not set.

The specified group name is incorrect.

The group name and number do not match.

The specified pair is already set in another group.

The command was rejected because the license capacity was exceeded.

The P-VOL is a Volume Migration source volume.

The P-VOL is a Volume Migration destination volume.

The specified P-VOL does not exist.

The specified volume is a reserved volume.

The specified P-VOL contains the maximum allowable number of pairs.

The specified volume is not a P-

VOL.

Stop the reserved volume setting operation, or delete the reserved volume.



Check the capacity of the installed license key.


Refresh, then re-execute.


More pairs cannot be created for this

P-VOL. Delete an existing pair.




Error Code

*,8599

*,8600

*,8601

*,8602

*,8603

7005,8603

*,8604

*,8605

*,8606

605,8606

*,8608

*,8609

*,8610

605,8610

*,8611

*,8612

*,8613

*,8614

*,8615

*,8616

*,8617

*,8618


The specified volume is already a

P-VOL.


Specify another P-VOL, and then reexecute, or delete the specified volume pair, and then re-execute.

Check the RAID level, specify a supported RAID level volume, and then re-execute.


The target P-VOL cannot be paired with a backup server volume.

The target volume is already set as a reserved volume.

Specify another volume, or release the specified volume reserved attributes, and then re-execute.

Delete the Data Migration pair.

The target volume is set as a Data

Migration P-VOL.


Migration S-VOL.


Migration S-VOL.

The Resync command was issued to a device in an SMPL state.

A new pair was created by using an S-VOL that was created in the

Remote Copy cooperation pattern.


Rectify the volume number for pair creation, or delete the Remote Copy pair.

A new pair was created with an S-

VOL forming the Remote Copy cooperation pattern.

The specified S-VOL does not exist.

The specified volume is not set as a reserved volume.

The S-VOL is a Volume Migration source volume.

The S-VOL is a target volume for

Volume Migration.


None.

The specified volume is an S-VOL. Check the contents, then re-execute.

The specified volume is not an S-

VOL.

The RAID level of the specified S-

VOL is not supported.

This S-VOL is used as a Remote

Copy P-VOL.

This S-VOL is used as a Remote

Copy S-VOL.

This S-VOL is used as a Data

Migration P-VOL.

None.

Check the settings, then re-execute.

Specify the supported RAID level volume number.



This S-VOL is used as a Data

Migration S-VOL.

This S-VOL is defined as a P-VOL. Check the volume number.



3-61

3-62

*,8623

*,8624

*,8625

*,8626

*,8627

*,8628

*,8629

*,8630

*,8631

*,8632

*,8633

*,8634

*,8635

*,8636

*,8637

Error Code

*,8619

*,8620

*,8621

*,8622


This S-VOL is defined as a Volume

Migration destination volume.

The volume specified as reserved is defined as a Data Migration P-

VOL.

The volume specified as reserved is defined as a Data Migration S-

VOL.

The volume specified as reserved is defined as a Remote Copy M-

VOL.




The volume specified as reserved is defined as a Remote Copy R-

VOL.

The selected volume is not a pair. Check the specified volume number.

The P-VOL (S-VOL) and S-VOL (T-

VOL) have the same number.

The SMPL command was rejected because a high-speed Split was in progress.

The Reverse Resync command was rejected because a highspeed Split was in progress.

After the high-speed Split finishes, reexecute.

The L1 pair Resync command cannot be performed because the

L2 pair is in an SP-Pend state.

The status mode specification is incorrect.

Change the L2 pair to PSUS, and then execute the L1 pair Resync command.


The status mode type is incorrect.

The specified CU number is incorrect.

The timing of issuing the command is incorrect.


Center.

The abnormal status is incorrect.

The volume specified as reserved is defined as a Volume Migration reserved volume.

Change the volume number in order to specify a reserved volume.

The specified P-VOL is defined as a Volume Migration reserved volume.

The specified S-VOL is defined as a Volume Migration reserved volume.

The specified P-VOL is used as a

Volume Migration destination volume.



*,8639

*,8640

*,8641

*,8642

*,8643

*,8647

*,8648

*,8649

*,8650

*,8651

*,8652

*,8653

*,8654

Error Code

*,8638

*,8644

*,8645

*,8646

Description

The command was rejected because this P-VOL has Cache

Residency settings.


The specified operation cannot be executed. Release the Cache

Residency settings in order to execute.

The command was rejected because this S-VOL has Cache

Residency settings.

The command was rejected because a pair sharing the P-VOL was in a Reverse Copy state.

The L1 pairs contain a pair in a

Reverse Copy state.

The L2 pairs contain a pair in a

Reverse Copy state.

The request was rejected because the Reverse Copy request was made to a pair in a non-Split state.

The request was rejected because the pair is not in a Split or

Suspend state.

The Reverse Copy request was rejected because the P-VOL was shared with a secondary volume of a Remote Copy pair.

The Reverse Copy request was rejected because the P-VOL was shared with a Remote Copy pair in a non-Suspend state.

The Reverse Copy request was rejected because the S-VOL was shared with a Remote Copy pair.

The boot device and the P-VOL do not match in the Paircreate command.

The flag does not match because the boot device is the S-VOL in the Pairsplit-S command.

The boot device and the P-VOL do not match in the Paircreate,

Resync, or Pairsplit-S commands.

The SSID is incorrect.

The boot device is not a P-VOL or

S-VOL.

The flag does not match because the boot device is the P-VOL in the Pairsplit-S command.

The boot device and the T-VOL do not match in the Paircreate,

Resync, or Pairsplit-S commands.

The specified operation cannot be executed. Release the reserved copy in order to execute.

The specified operation cannot be executed. Release the reserved copy in order to execute.


The specified operation cannot be executed. Release the reserved copy pair in order to execute.


Check the number of the volume that is the target of the operation.






3-63

3-64

Error Code

*,8655

*,8656

*,8657

*,8659

6805,8659

605,8670

605,8671

605,8672

605,8673

605,8674

605,8675

605,8676

605,8677

605,8678

605,8679

605,8680

605,8681

605,8682

605,8683

605,8684


An incorrect secondary SSID is specified for the Paircreate or

Resync command.

An incorrect secondary SSID is specified for the DeletePair or

Split command.

Swap&Freeze was specified, but the mode is incorrect.

No PCBs for iSCSI are installed.

Attach the required PCBs.

The number of LDEVs configured in the LUSE volume for the P-VOL and S-VOL are not the same.

The pair cannot be set because the number of LBAs.is different for each volume.

The specified combination of

Cross-system Copy LDEVs is incorrect.

The emulation type of the Crosssystem Copy LDEV is not OPEN-V.

The specified volume is not an

LUSE volume.

An I/O operation to the Crosssystem Copy LDEV is executing.


Cross-system Copy target volume.

The specified volume is already used as a Cross-system Copy

LDEV.

The volume defined as the source is an iSCSI volume.

The volume defined as the destination is an iSCSI volume.

The specified volume is already an iSCSI LDEV.

The volume defined as the source is the volume being used by

Cross-system Copy.

The volume defined as the destination is the volume being used by Cross-system Copy.

The specified consistency group is being used as the mainframe consistency group.

The microcode used for processing CTG setting does not support the At-TimeSplit function.



Check the contents of the specified option.

Implement a PCB for an iSCSI.

None.

Check the settings, and make configuration changes.

Check the volume, then re-set.

None.

Stop the I/O operations, and make configuration changes.



Install the microcode that supports the At-TimeSplit function.



Error Code

605,8687

605,8689

605,8690

605,8691

605,8692

605,8694

605,8695

7105,8696

7105,8697

7105,8698

7105,8699

6005,8700 Re-execute.

6005,8701

6005,8703

Description

The specified consistency group number is outside the range from

0x00 to 0x7F.

The volume specified by Crosssystem Copy is the Remote Copy

P-VOL.

The volume specified by Crosssystem Copy is the Remote Copy

S-VOL.

The volume specified by Crosssystem Copy is the ShadowImage

P-VOL.

The volume specified by Crosssystem Copy is the ShadowImage

S-VOL.


Cross-system Copy target volume.

The specified MU number is not less than or equal to 2.

The command was rejected because the specified S-VOL is being used as a T-VOL for

ShadowImage, FlashCopy

Version2.

The command was rejected because the specified T-VOL is being used as a volume for


Version2.

The command was rejected because the specified volume is being used by ShadowImage,

FlashCopy Version2.

The Reverse Copy or Quick

Restore command was rejected because the specified S-VOL is sharing a relation with


Version2.

The logical path between the MCU and RCU is not active.

The specified number of paths is less than the minimum number of paths in the RCU option.



None.

Re-execute.

Check the path status in the RCU

Status window, and then use Edit

Path to re-establish the path.

Check the number of paths.



3-65

3-66

6005,8713

6005,8714

6005,8715

6005,8716

6005,8717

6005,8718

6005,8719

6005,8705

6005,8706

6005,8707

6005,8709

6005,8710

6005,8711

6005,8712

Error Code

6005,8704

6005,8720


An MCU-RCU communication problem has caused the number of specified paths to be less than the minimum in the RCU option, or remote copying via a serial path does not support R-VOL device emulation.

The path cannot be deleted because of a communication error between the MCU and RCU.

A parameter entered in the

Remote Copy operation is incorrect.

Check the path status in the RCU

Status window, and then re-establish the path. Refer to the open-systems section of the maintenance manual, and make sure that R-VOL device emulation is supported.

Check the CHA status on the MCU status window. If the CHA is blocked, change it, then re-execute.

Enter the correct data.

The Data Migration operation setting is incorrect.

The Remote Copy operation was rejected.

The pair status of the specified volume is incorrect.


Change the CHA, and then reexecute.

Check the settings. If permissible, reexecute.

An entered parameter is incorrect. Check the RCU port number, ID, and

LUN.

The operation was rejected because of a Freeze state.

1. If this was a path-related Freeze status recovery operation, reexecute.

2. If this was a pair-related operation, refer to the RCU status, and then after the time set for SCP

Time elapses, re-execute.

A port group is already set on the specified port.


Incorrect number of paths.

Delete the group settings, and then change the port type.


Check the number of specified paths, and then re-execute. If the problem persists, contact the Support Center.

The specified port is not an RCP.

The connection-destination address is incorrect.

The specified logical path already exists.

The RCU serial number, link address, controller ID, or SSID is incorrect.

There are already 4 (the maximum) registered RCUs.

Check the configuration of the LCP and RCP, and then specify the correct port, or change the port to RCP.

Check the logical address, and then set the correct address.

Check all of the logical addresses, and then specify a different address or

RCP.

Check the RCU's serial number, SSID, link address and controller ID, and then set the correct value. If the values are correct, check the RCU cable connection, and then reexecute. If the problem still persists, contact the Support Center.

Re-check the entered values, and then execute.



6005,8727

6005,8728

6005,8729

6005,8730

6005,8731

6005,8732

6005,8733

Error Code

6005,8721

6005,8722

6005,8723

6005,8724

6005,8725

6005,8726

6005,8734


Path creation was incomplete.

Path creation has failed.

The Edit Path operation was rejected because the specified path is the last path of a Remote

Copy pair.

The specified number of paths is less than the minimum number of paths in the RCU option. Check the number of paths.

The specified operation is not supported by the current microcode version.

Check the path connections between the MCU and RCU, and then reexecute.

Create another path or delete all the pairs on the RCU, and then retry.

Check the number of paths.

Check the microcode version. If the target version is an edition that supports Remote Copy, try to change the LCP microcode again.

The multiplatform function is already installed on the MCU.

The minimum number of paths exceeds the normal number of paths.

The minimum number of paths exceeds the normal number of paths.


TrueCopy and Data Migration has an exclusive connection with the multiplatform function. Reduce the

MCU's CHS PCB, and then execute the

TrueCopy and Data Migration function.

Recover the minimum number of paths. If this problem persists, contact the Support Center.

The Fibre-Remote Copy function is not installed on the RCU.

See the SSB log, and then obtain TSC support.

The specified logical address is incorrect.

Execute the correct logical address recovery process. If this problem persists, contact the Support Center.

A logical address does not match. Delete the RCU, and then re-add it.

Specify the same logical address.

There are already 4 (the maximum) registered SSIDs.

Check the RCU SSID values. If an incorrect SSID is registered, delete it and then re-execute.

The Fibre-Remote Copy function is not installed on the MCU.

When creating a Fibre-Remote Copy path or pair, the Fibre-Remote Copy function must already be installed on the MCU and RCU. Install the Fibre-

Remote Copy function on the MCU.

When creating a Fibre-Remote Copy path or pair, the Fibre-Remote Copy function must already be installed on the MCU and RCU. Install the Fibre-

Remote Copy function on the RCU.



3-67

3-68

6005,8736

6005,8737

6005,8738

6005,8739

6005,8740

6005,8741

6005,8747

6005,8748

Error Code

6005,8735

6005,8750

6005,8751

6005,8752

6005,8753

6005,8754

6005,8755



Check the serial number, SSID and link address registered to the RCU, and then set the correct value. If the values are correct, check the RCU cable connection, and then reexecute. If the problem still persists, contact the Support Center.

Delete all pairs specified in the RCU and SSID, and then re-execute.

The specified RCU or SSID contains a Remote Copy volume pair.

An internal error occurred. See the SSB log and contact the

Support Center.

Check the controller emulation type. Remote Copy is not supported by the MCU controller emulation type.

The NVS of the MCU connecting the host is not active.

The NVS of the RCU connecting the host is not active.

The logical paths between the

MCU and RCU are not established.

The specified operation is not supported by this microversion.

Check the NVS status, and then reset. If it cannot be re-set, contact the

Support Center.

Check the path status between the

MCU and RCU.

Check the microcode version. If it is the Remote Copy support edition, try to change the LCP microcode again.

Check whether the specified volume is online. If it is, change it to offline, and then re-execute. Also, if the specified volume is connected to the

VM system, change the VM system connection to offline.

The specified volume might be online. Check whether it is online.

If it is, change it to offline, and then re-execute. Also, if the specified volume is connected to the VM system, change the VM system connection to offline.

Data Migration is not supported by the MCU controller emulation type.

Pair registration has failed. 1.

Remote Copy is not supported by the RCU DKC emulation. 2. When the RCU is A/H-6593, only a number from 0 to F can be used for the asynchronous copy's consistency group number.

Data Migration is not supported by the RCU controller emulation type.


Check the controller emulation type.

Check the RCU's DKC emulation type and the consistency group number.

Check the controller emulation type.

The MCU serial number or SSID is incorrect.

The RCU serial number

See the SSB log and contact the

Support Center.

Check the MCU serial number and

SSID, and then re-execute.

CU number or SSID is incorrect.



Error Code

6005,8756

6005,8757

6005,8758

6005,8759

6005,8768

6005,8769

6005,8770

6005,8774

6005,8775

6005,8777

6005,8778

6005,8779

6005,8782

6005,8783

6005,8784

The MCU disk array cache is not active.

Description

One side of the MCU cache is blocked.

The TrueCopy E function is not installed on the specified DKC.

Install the TrueCopy E function.

The TrueCopy E function is not installed on the specified DKC.

Install the TrueCopy E function.


Check the subsystem cache status of the MCU connected to the host. If it is off, re-set it. If it still cannot be set, contact the Support Center.

Check the MCU cache status and perform recovery. After recovery finishes, re-execute.

Contact the Support Center. An unexpected error occurred on the MCU.

The RCU cache status is not active.

The RCU is still in another Remote

Copy state.

The multiplatform function is already installed on the RCU.

Check the subsystem cache status of the RCU connected to the host. If it is off, re-set it. If it still cannot be set, contact the Support Center.

Check whether this RCU is busy using another Remote Copy. If it is, delete the RCU, and then re-execute.

The RCU is still in another Remote

Copy state.

The MCU cache is automatically restoring. Wait for a few minutes, and then re-execute.

The multiplatform function is already installed on the MCU.

Wait for the cache to recover, and then re-execute.

TrueCopy and Data Migration have an exclusive relation with the multiplatform function. Reduce the

MCU's CHS PCB, and then execute the


TrueCopy and Data Migration has an exclusive relation with the multiplatform function. Reduce the

RCU's CHS PCB, and then execute the


Check the controller type of the MCU and RCU.

The combination of the RCU with the MCU controller type is not supported.

One side of the RCU cache is blocked.

TrueCopy is not supported by the

RCU controller emulation type.

The Data Migration function is not installed on the specified DKC.

Check the RCU cache status, and then restore the cache.

Check the RCU controller emulation type.

Install the required PP (program product). (Since there are 3 types of


Install the TrueCopy Semi-Sync function, and then re-execute.



3-69

3-70

Error Code

6005,8787

6005,8788

6005,8789

6005,8790

6005,8792

6005,8793

6005,8794

6005,8802

6005,8803

6005,8804

6005,8805

Description

The RCU does not support the expansion volume's Remote Copy.

The specified S-VOL expansion volume is not defined, or the S-

VOL's device emulation is not supported by Remote Copy when using serial interface.

The defined combination of the P-

VOL's expanded LU and the S-

VOL's expanded LU is incorrect.

Check the selected expansion volume combination.

The specified RCU expansion volume (Port/ID/LUN) cannot be used.

Pair registration is not possible because the Volume Retention z/OS function is not installed on the RCU. Install Volume Retention z/OS, and then re-execute.

The Add Pair operation cannot be performed because the TrueCopy function is not installed on the

MCU (or RCU).

The Add Pair operation cannot be performed because the TrueCopy function is not installed on the

MCU (or RCU).

The Add Pair operation failed because it is not registered on the specified consistency group.

Pair registration has failed. If the timer type is None, 4 RCUs are already registered. If the timer type is Local or System, 1 RCU has already been registered.

The Resume Pair operation failed.

1. The pair is asynchronous, even though the pair is specified not to be asynchronous in copy mode. 2.

The pair is not asynchronous, even though the pair is specified to be asynchronous in copy mode.

The Resume Pair operation failed.

The specified consistency group on the RCU side is not registered.


Check the RCU controller type and microcode version.

Check the RCU Port, ID, and LUN.

Refer to the open-systems section of the maintenance manual to make sure that the S-VOL device emulation is supported.

Check the selected expansion volume combination.

Refer to the RCU expansion volume status and microcode version.

Install Volume Retention z/OS on the

MCU and RCU, and then re-execute.

Install the TrueCopy function, and then re-execute.

Register the consistency group, and then re-execute.

Register a new consistency group.

Check the settings of the target pair, then re-execute.

Check the MCU and RCU consistency groups. If the M-VOL exists, delete it, and then re-execute the pair registration operation.



Error Code

6005,8806

6005,8807

6005,8808

6005,8809

6005,8811

6005,8815

6005,8817

6005,8818

6005,8825

6005,8826

6005,8827

6005,8828

Description

Pair registration or the resume operation has failed. A consistency group already exists in the RCU. The consistency group option (timer type, timeout interval) cannot be changed unless all asynchronous pairs in the consistency group have been deleted or suspended.

Pair registration has failed. If the timer type is System, 4 MCUs are already registered. If the timer type is Local or None, 1 MCU has already been registered.

Pair registration or the resume operation has failed. The MCU volume or another volume from the same group is changing to a

Simplex or Suspend state.

Pair registration or the resume operation has failed. The RCU volume or another volume from the same group is changing to a

Simplex or Suspend state.

Pair registration has failed.

Multiple consistency group registration is not supported by the RCU.

The asynchronous pair cannot be formatted because TrueCopy asynchronous extension program product function is not installed on the RCU.

The Add Pair operation cannot be performed because the suspend instruction by the NCFREEZE command is enabled.

The Resume operation cannot be performed because the suspend instruction by the NCFREEZE command is enabled.

Pair registration has failed. A pair that uses a Fibre path and a pair that uses a serial path cannot be combined in the same consistency group.


Pair registration or the resume operation has failed.

This microcode version does not support mixing, within a DKC, pairs that use Fibre paths with pairs that use serial paths.


Check the RCU consistency group options, and then set to the same options as the MCU.

Register a new consistency group.

Wait a while, and check the settings.

If the pair is in a state that allows pair registration or resumption, reexecute.

Wait a while, and check the settings.

If the specified volume is in a state that allows the operation to be performed, re-execute the operation.

Check the RCU consistency group.

Install TrueCopy asynchronous extension program product function in the RCU.

Cancel the suspend instruction by the

NCFREEZE command on the target consistency group.

Check the MCU and RCU settings, and then check the pair's paths.


Support Center.

Wait a few minutes, then retry.

In the RCU Status window, check the type of path specified in the

Paircreate operation.



3-71

3-72

Error Code

6005,8832

6005,8833

6005,8834

6005,8835

6005,8836

6005,8837

6005,8838

6005,8839

6005,8843

6005,8844

6005,8845

6005,8846

6005,8847

6005,8848


Wait a few minutes, and then reexecute.


Pair registration has failed because an attempt was made to register a pair that exceeded the permission capacity.

Pair registration has failed because an attempt was made to register a pair that exceeded the permission capacity of the RCU.


Refer to the license key and check the licensed capacity. If more pairs need to be created, obtain a license key that can use a larger capacity.

Refer to the RCU license key and check the licensed capacity. If more pairs need to be created, obtain a license key that can use a larger capacity.

No pairs are waiting to be copied. Check the pair registration contents, and then retry.

An internal error occurred. See the SSB log and contact the

Support Center.

Check the specified volume. The specified volume is not a

Remote Copy pair.


Check the serial number, SSID, link address and controller ID of this RCU, and then set the correct value. If the values are correct, check the RCU cable connection, and then reexecute. If the problem still persists, contact the Support Center.

The pair state of the specified volume or another volume in the same group, is not in a permissible state for this operation. For a group option operation: 1. The specified volume is Simplex. 2. There is no

Duplex or Pending-Duplex volume in the group. For a pair option operation: 1. The specified volume is Simplex.

Check the settings, and if a pair in either the specified volume or another volume in the same group is in a permissible state, re-execute.

The status of the specified volume, or another volume from the same group, is now changing.

For group or pair option operations: 1. The specified volume status is Deleting. 2. The specified volume status is

Suspending.

The Suspend operation cannot be performed because the suspend instruction by the NCFREEZE command is enabled.


Wait a while, and then if the volume is in a request receivable state, reexecute.

Cancel the suspend instruction by the

NCFREEZE command on the target consistency group.


Support Center.


The Suspend Pair operation failed. Wait a few minutes, and then retry.



Error Code

6005,8849

6005,8850

6005,8853

6005,8855

6005,8856

6005,8857

6005,8858

6005,8860

6005,8861

6005,8862

6005,8863

6005,8864

6005,8865

6005,8866

6005,8867

The specified volume is not a

Remote Copy pair (not in a

Duplex (PAIR), Pending (COPY), or Suspend (PSUS) state).


Description


The pair termination operation failed.

An unregistered error occurred.



Check the specified volume.

The Data Migration volume pair cannot be terminated. Migration copy is executing, or the specified volume might be online.

The status of the specified volume, or another volume from the same group, is now changing.

For group or pair option operations: 1. The specified volume status is Deleting. 2. The specified volume status is

Suspending.

The Pair Delete operation for which consistency was specified in the deletion range has failed. The consistency group status is

SEQCHK.

The volume is in an SEQCHK state, or the volume consistency does not match the group.

The Pair Delete operation has failed. The volume is in an

SEQCHK state, or the volume consistency does not match the group.


Check the serial number, SSID, link address and controller ID of this RCU, and then set the correct value. If the values are correct, check the RCU cable connection, and then reexecute. If the problem still persists, contact the Support Center.

Make sure that the migration copy is in progress, and that the volume is in an online state.

Wait a while, and then if the volume is in a request receivable state, reexecute.

Re-execute the Pair Delete operation for which Volume or Group was specified in the deletion range.

Check the volume that had a Pair

Delete failure. If necessary, specify

Volume or Group in the deletion range, and then re-execute the Pair

Delete operation.

Re-execute the Pair Delete operation for which Volume or Group was specified in the deletion range.


Support Center.

Wait a few minutes, and then retry.






Support Center.



3-73

3-74

Error Code

6005,8868

6005,8869

6005,8870

6005,8872

6005,8873

6005,8874

6005,8875

6005,8876

6005,8877

6005,8878

6005,8879

6005,8880

6005,8881

6005,8882

6005,8883

6005,8884

6005,8885

6005,8886

6005,8887

Description

The group registration operation has failed because the specified consistency group number is already being used by the MCU.

This consistency group is not registered.

An attempt to change a group option has failed, because an asynchronous pair is in the specified consistency group.

Group registration failed. This version does not support multi consistency group registration in the MCU.

The consistency group cannot be registered because TrueCopy

Async function is not installed on the MCU.

Invalid timer type option.


Check the MCU consistency group.

Check the settings.


Install TrueCopy asynchronous extension program product on the

MCU, and then re-execute.





Specify Local or None for the timer type.

Check the settings. An attempt to change the timer type has failed, because an asynchronous copy pair is in the specified consistency group.

No PCBs correspond to the specified port type.


This consistency group is not registered.

A request to delete the consistency group was rejected, because there is at least one asynchronous pair.

Group deletion failed. A pair from this group is changing to Simplex.


The asynchronous option (Current

Pending Update Data Rate) cannot be changed, because registration by the TrueCopy consistency group has finished.


Check the implemented package type, and then retry using the correct parameters.


Support Center.


Check the settings.



Support Center.

Delete all the consistency groups registered by TrueCopy.


Support Center.



Error Code

6005,8888

6005,8889

6005,8890

6005,8891

6005,8893

6005,8894

6005,8895

6005,8896

6005,8897

6005,8898

6005,8899

6005,8900

6005,8901

6005,8902

6005,8904

6005,8905

6005,8906



The specified port is not implemented.

The specified port is still being initialized.

A logical path remains on the MCU port.



Support Center.

Check the settings, and then reexecute. If the same result occurs, contact the Support Center.

After the specified port finishes initializing, retry the operation.

Delete the logical paths on the related port, and then retry.


Support Center.

A job remains on the target MCU port.

Stop the jobs from the host, then retry.

A job remains on the target RCU port.

A parameter error occurred.

Check the settings, and then reexecute. If the same result occurs, contact the Support Center.

An LU remains on the target port. Delete the LU defined on the related port, then retry.

Pending data is on the port.


Re-execute.


Support Center.

Contact the Support Center. An error occurred during the port change.

An error occurred during the port change.

An error occurred during the port change.

The differential management areas in the MCU are full.

Extended shared memory is not implemented in the MCU.

The differential management areas in the RCU are full.

If extended SM #2 is not implemented in the MCU, implement the SM by using the implementation instruction for remote copy extended

SM (Shared Memory Size

Configuration), and then re-create the pairs. If extended SM #2 is implemented in the MCU, more pairs.

Install the SM (shared memory) on the MCU by using the Remote Copy expansion function SM installation instructions (Install Remote Copy

Function).

If extended SM #2 is not implemented in the RCU, implement the SM by using the implementation instruction for remote copy extended

SM (Shared Memory Size

Configuration), and then re-create the pairs. If extended SM #2 is implemented in the RCU, more pairs.



3-75

3-76

Error Code

6005,8907

6005,8910

6005,8911

6005,8912

6005,8913

6005,8914

6005,8915

6005,8917

5305,8919

*,8920

6005,8922

6005,8923

6005,8924

6005,8929

6005,8930

6005,8931

6005,8932

Description

Extended shared memory is not implemented in the RCU.


Install the SM (shared memory) on the RCU by using the Remote Copy expansion function SM installation instructions (Install Remote Copy

Function).

Check the entered value, and then reexecute.

Replace the CHA. An error occurred during port exchange.

A logical path is on the port.

A logical path is on the port.


Delete the path, and then re-execute.

Check the port status, and then reexecute.

Check the subsystem configuration. The multiplatform function is already installed on the subsystem.

The port type exchange operation from the SVP (RMC) was rejected, because the host is already processing a port type exchange.

There are too many pairs in this consistency group.

Check the port status, and then reexecute the port type exchange operation.



Operations on L2 are not possible because the L1 pair is not in the

PSUS state.

The specified MCU does not support the Serial Path Link

Remote Copy function.

The specified RCU does not support the Serial Path Link

Remote Copy function.

A logical path remains on the RCU port.

Invalid port type. Check the port type, and then re-execute.



The path between the MCU and

RCU cannot be established, because the configuration definition of the specified CU number is not defined.

Register a new consistency group, and then register the asynchronous pair.


Support Center.

Wait until the L1 pair changes to a

PSUS state, and then execute the operation to the L2 pair.

Make sure that the MCU supports

Serial Path Link Remote Copy. Install the microcode version that supports

Serial Path Link Remote Copy, or execute Serial Path Link Remote

Copy.

Delete the logical paths of the specified port, then re-execute.

Check the port type of the specified port, then re-execute.

Delete the logical paths of the specified port, then re-execute.

Make sure that the configuration information of the specified CU number is defined.



6005,8945

6005,8947

6005,8948

6005,8949

6005,8950

3205,8951

3205,8952

3205,8953

Error Code

6005,8933

6005,8934

6005,8935

6005,8936

6005,8937

6005,8938

6005,8939

605,8941

6005,8943


Pair registration has failed because the specified P-VOL is a

NAS system volume.

Pair registration has failed because the specified S-VOL is a

NAS system volume.

Pair registration has failed because the specified P-VOL is a

NAS system volume.

Pair registration has failed. The specified RCU version does not support a Remote Copy that has used a NAS system volume.

Pair registration using a fiber path has failed, because a pair using a serial path is in the same MCU.

Pair registration using a serial path has failed, because a pair using a fiber path is in the same

MCU.

The specified P-VOL cannot be used.

The LU for Cross-system Copy is connected to the port.

An I/O operation is occurring at the specified port.


Check the configuration of the specified P-VOL.

Check the configuration of the specified S-VOL.

Check the configuration of the specified P-VOL.

Check the RCU microcode version.

Delete all the pairs with the serial remote copy connection in the specified MCU, and then re-execute.

The command was rejected because the selected CT Group is already used.

In the RCU, the specified volume, or another volume from the same group, is being changed to a

Simplex or Suspend status. Wait a few minutes, and then reexecute.

Check the RCU's SSID

Check the P-VOL's LUN by using RAID

Manager. Specify a LUN with a value less than 256 for P-VOL.

None.

Wait a few minutes, and check the settings. In the RCU, check the status of the specified volume, or another volume from the same group. If it is in an operational state, re-execute.

CU number and the S-VOL Port-

Group-LUN. Re-execute using the correct parameters.

Release the settings of the LU for

Cross-system Copy, and then reexecute.

Stop the I/O operations, then reexecute.

See the SSB log, and contact the

Support Center.

None.


An error occurred on the DKC side. If this problem persists, contact the support center.





3-77

3-78

3205,8960

3205,8961

3205,8962

3205,8963

3205,8964

3205,8965

3205,8966

3205,8967

Error Code

3205,8954

3205,8955

3205,8956

3205,8957

3205,8958

3205,8959

3205,8968

3205,8969

3205,8970

Description




















None.


6005,8972

6005,8973

6005,8974

6005,8975

6005,8976

6005,8977

3205,8978

105,8979

Error Code

605,8971

605,8979

6005,8980

605,8981

2,9000



A pair cannot be created because the specified P-VOL is already in use by Cross-system Copy.

A pair cannot be created because the specified S-VOL is already in use by Cross-system Copy.

A pair cannot be created because the path is defined from an iSCSI port to the specified P-VOL.

A pair cannot be created because the path is defined from an iSCSI port to the specified S-VOL.

A pair cannot be created because the specified P-VOL is a Crosssystem Copy volume.

A pair cannot be created because the specified S-VOL is a Crosssystem Copy volume.


The operation on the external volume failed because the external volume was disconnecte. or all the paths to the external volume were blocked.

The operation of the external volume has been failed because all the paths to the external volume are blocked.

The pair operation failed because the licensed capacity of Volume

Retention z/OS on the RCU was exceeded.

The copy processing of Crosssystem Copy is in progress.

Another user is accessing by using modifier mode. Wait a while, and then re-execute.

None.

Check the status of the specified P-

VOL.

Check the status of the specified S-

VOL.


VOL.


VOL.


VOL.


VOL.

None.

Recover the path that is connecting the external LU, and then follow the

LDEV recovery instructions.

Check the licensed capacity of Volume

Retention z/OS on the RCU. If executing this operation, obtain a license key that can use a larger capacity.

The copy processing of Cross-system

Copy is in progress.

Wait a while, then re-execute.



3-79

3-80

8505,55019

8505,55021

8505,55025

8505,55026

8505,55029

8505,55030

8505,55031

8505,55032

8505,55033

1,55044

Error Code

8505,55008

6805,55009

6805,55010

8505,55016

8505,55017

Description

The current micro-code does not support the partitioning of the resources used by the program product (SLPR Key, Serverless

Backup, Volume Security,

Universal Replicator,

ShadowImage, and TrueCopy).

Check the micro-program version and the supported specifications, and then correct the settings.

An invalid cache resource number

(CLPR number) was detected.

An invalid storage resource number (SLPR number) was detected.

The value for the maximum number of logins exceeds the value set for the maximum number of logins for each SLPR.

The total number of logins registered for each SLPR exceeds the value set for the maximum number of logins to the subsystem.

The SSID is invalid.

The specified CU number is invalid.

The parity group settings are invalid.

None.


Check the SLPR information, then reset the correct information.

The specified port name (port number) is invalid.

The total cache size is invalid.

The SLPR to which the CU belongs does not match the SLPR to which the LDEV belongs.

A LUN cannot be set across multiple SLPRs.

A LUSE volume cannot be set across multiple SLPRs.

This port is already registered on a different SLPR.

At setup, contact maintenance personnel.

Check the SLPR and CLPR information, then re-set the correct information.

Check the settings, and retry the operation.



6805,55209

6805,55210

6805,55211

6805,55212

6805,55213

6805,55214

6805,55215

6805,55216

6805,55217

6805,55218

6805,55219

6805,55220

6805,55221

Error Code

5205,55059

5205,55060

2,55206

1005,55206

Description

The specified volumes cannot be used for migration. The specified source volume is a TrueCopy volume or a TrueCopy z/OS volume, but the specified destination volume is an external volume.

The specified volume migration plan cannot be executed because the pair consists of a volume for which VMA is set for the data retention function, and a volume for which VMA is not set.

The set configuration information does not match the current configuration information. Revise the settings, and then retry the operation.

The set configuration information does not match the current configuration information. Revise the settings, and then retry the operation.

The specified volume is already reserved with a different owner ID by Volume Migration.

The Block Option setting is incorrect.

The Donot Block (Volume Level) option setting is incorrect.

The options "Block Option" and

"Donot Block (Volume Level)" cannot be specified at the same time.

The Level 1 Threshold setting is incorrect.

The Level 2 Threshold setting is incorrect.

The Level 1 SIM setting is incorrect.

The Level 2 Suspend setting is incorrect.

The maximum number of valid

SLPRs has been exceeded.

The Level 1 Sleep setting is incorrect.

The Sleep Time setting is incorrect.

The SLPR number has been duplicated.

The SLPR number has been duplicated.

None.




3-81

3-82

Error Code

5205,55223

5205,55224

5205,55225

5205,55226

5205,55227

8505,55228

6005,55230

1,55231

8005,55243

8005,55244

8005,55245

8005,55246

8005,55247

8005,55248

Description

The owner ID of the disk subsystem being used by the user does not match the owner ID of the volume specified as the switch destination.

The owner ID of the disk subsystem being used by the user does not match the owner ID of the specified reserve volume.

The specified plan cannot be released.

The specified migration plan cannot be canceled.

The volume specified as the reserve volume has already been set as the reserve volume for

Volume Migration by a different owner ID.

This function is not available.

Virtual Partition Manager is required to create an SLPR or

CLPR.

Port attributes assigned to SLPRs

(except SLPR0) can only be changed to Target or LCP.

Application processing (processing to change the configuration) is executing on a different SLPR.

Application processing (processing to change the configuration) cannot be executed simultaneously on multiple SLPRs.

The total of Cache Residency size of the CLPRs and the total of all

Cache Residency size in the subsystem are not equal.

The cache residency size set for the CLPR exceeds the maximum settable size.

The number of cache residency areas set for the CLPR exceeds the maximum number of settable cache residency areas.

The total number of Cache

Residency areas set for the CLPRs and the maximum number of the

Cache Residency areas in the subsystem are not equal.

The cache residency size set for the CLPR is not a multiple of 512

MB.

Some NAS ports in the same CHN have different SLPR numbers set.

None.




Error Code

8005,55249

8005,55250

8005,55251

5205,55252

5205,55253

5205,55254

5205,55255

5205,55256

5205,55257

5205,55258

Description

The SLPR number set for LUN

0000 or LUN 0001 in the NAS system group is different from the

SLPR number set for the port.

LUN 0005 to LUN 000A in the NAS system group are set to an SLPR other than SLPR 0.

The mainframe volume is set to an SLPR other than SLPR 0.

The specified source volume is an internal volume. The specified target volume is an external volume that belongs to a Crosssystem Copy pair. Therefore, the specified volumes cannot be used for migration.

The specified source volume is an external volume that does not belong to a Cross-system Copy pair. The specified target volume is an external volume that belongs to a Cross-system Copy pair. Therefore, the specified volumes cannot be used for migration.

The specified source volume is an external volume that belongs to a

Cross-system Copy pair. The specified target volume is an internal volume. Therefore, the specified volumes cannot be used for migration.

The specified source volume is an external volume that belongs to a

Cross-system Copy pair. The specified target volume is an external volume that does not belong to a Cross-system Copy pair. Therefore, the specified volumes cannot be used for migration.

Both the specified source volume and the specified target volume are external volumes that form a

Cross-system Copy pair.

Therefore, the specified volumes cannot be used for migration.

The specified volume(s) are already being used as data volume(s) by Universal Replicator or Universal Replicator z/OS.


None.




3-83

3-84

Error Code

5205,55259

1,55260

405,55263

7005,55264

8005,55265

605,55284

605,55285

605,55286

605,55287

605,55288

605,55289

605,55290

Description


A user who is currently logged in cannot be deleted.

The specified program product cannot be uninstalled because a license has not been allocated to the SLPR.

The command was rejected because an attempt was made to create a pair consisting of a volume for which VMA is set for the data retention function, and a volume for which VMA is not set.

The parity group containing the volume(s) for which Cache

Residency is set cannot be migrated to another CLPR.

Release the Cache Residency settings from the volumes, and then migrate the parity group.








None.




Error Code

605,55291

605,55292

605,55293

605,55294

605,55295

605,55296

605,55297

605,55298

605,55299

605,55300

7005,55301

605,55309

605,55310

605,55311

605,55312

Description











A pair cannot be created because the license capacity for the data retention function is insufficient.

An incompatible emulation type is defined for the specified external volume.

The declaration statement of the spreadsheet is duplicated.

The version number entered in the spreadsheet is invalid.

The function name entered in the spreadsheet is invalid (the name is not External).

None.




3-85

3-86

605,55317

605,55318

605,55319

605,55340

605,55341

605,55342

605,55343

605,55344

605,55345

605,55346

605,55347

605,55348

605,55349

605,55370

605,55371

Error Code

605,55313

605,55314

605,55315

605,55316

Description

The processing mode entered in the spreadsheet is invalid (the mode is not New).

The function tag (AddLU-PATH,

AddLU-LDEV, or SetSSID) for executing processing is not in the spreadsheet.

The function tag (AddLU-PATH,

AddLU-LDEV, or SetSSID) for executing processing is duplicated in the spreadsheet.

The function tag (AddLU-PATH or

AddLU-LDEV) for executing processing is not in the spreadsheet.

The data length is invalid.

The number of data items entered in the spreadsheet has exceeded the limit.

The number of data items is invalid (there is no definition statement).

There is no entry for an item that requires an entry.

The number of digits is invalid.

The number of path settings specified in the spreadsheet is invalid.

A value specified in the spreadsheet is invalid.

An spreadsheet entry is duplicated.

There are no contents set to be shared by AddLU-PATH and

AddLU-LDEV.

The path settings specified in

AddLU-PATH are duplicated.

The LDEV information specified in

AddLU-LDEV is duplicated

The format of the function tag is invalid.

The number of LDEVs specified in the AddLU-LDEV tag does not match the number of LDEV IDs.

The name for the emulation type is invalid.

An unsupported emulation type has been specified.

None.




Error Code

605,55372

605,55373

605,55374

605,55375

605,55376

605,55377

605,55378

605,55379

605,55380

605,55381

605,55382

605,55383

605,55384

605,55385

605,55386

605,55387

605,55388

605,55389

605,55390

605,55391

605,55392

605,55393

Description

The combination of the IO suppression mode and Cache mode is invalid.

The SLPR number cannot be acquired correctly.

The SSID number cannot be acquired correctly.

The specified external volume group number is duplicated in the spreadsheet.

The specified external volume group number is already being used.

An unset CLPR number has been specified.

The specified SSID value is already being used.

The capacity of the specified volume is outside the set range.

The position of the specified volume has already been set.

The position of the specified volume cannot be set.

The position of the specified volume cannot be set.

The specified device has already been defined.

The capacity of the specified LDEV does not match the capacity of the external volume.

The SSID value is not set.

The number of paths registered for one of the ports has reached the maximum.

A CU number that cannot be used by the subsystem was specified.

The program product has not been installed.

The specified external path was not found.

There is an error in the method for specifying the SSID.

An unsupported device was specified.

The specified SSID value is already being used.

There is an error in the path settings.

None.




3-87

3-88

Error Code

605,55430

5205,55431

5205,55432

5205,55433

3005,55505

3005,55506

3005,55507

3005,55508

3005,55509

3005,55510

3005,55511

3005,55512

3005,55513

3005,55514

Description


The specified volume is already being used by FlashCopy Mirror

Version 2.


Version 2.


Version 2.

The specified operation cannot be performed because data pool volumes in the same pool have been specified to migrate to different CLPRs.










None.




5205,55521

5205,55522

5205,55523

5205,55524

5205,55525

5205,55526

5205,55527

5205,55528

5205,55529

9105,55548

5205,55549

Error Code

3005,55516

3005,55517

3005,55519

5205,55550

5205,55551

5205,55552

Description

The specified function is not available because the program product COW Snapshot has not been installed.



The specified volume is already being used as a COW Snapshot volume.

The specified volume is already being used as a V-VOL.

The specified volume is already being used as a data pool volume.







The specified LDEV cannot be set because of the journal volume.

The volume(s) are already being used as a JNL Volume by

Universal Replicator or Universal

Replicator z/OS.



Replicator z/OS.



Replicator z/OS.

The specified plan is set across an internal volume and an external volume, and the volume is used by Universal Replicator or

Universal Replicator z/OS.

None.




3-89

3-90

1005,55562

1005,55563

1005,55565

1005,55567

1005,55568

1005,55569

1005,55570

Error Code

1005,55553

1005,55554

1005,55555

1005,55556

1005,55557

1005,55558

1005,55559

1005,55560

1005,55571

1005,55572

1005,55573

Description

The specified port is not a fibre port.

The specified WWN is not registered.

The WWN value is not specified or is set to zero.

The specified port is not an iSCSI port.

The specified iSCSI name is not registered.

The value of the iSCSI name is not specified or is set to zero.

The specified package cannot be set because the package is for iSCSI.

The fibre address, topology, channel speed, and initiator/target cannot be changed because the specified port is an iSCSI port.

The specified LU cannot be used as a NAS system LU or is already being used as one.

The specified LDEV cannot be defined as a NAS system LU.

The specified system LU cannot be deleted because a NAS user LU exists.

No NAS path can be set because the specified volume is a V-VOL.

The nickname of the specified target name or iSCSI name is already registered.

The specified group ID is already registered.

One or more invalid characters were specified in the target name, target alias, iSCSI name, or nickname of the iSCSI name.

The target cannot be set because the number of targets exceeds the maximum that can be set in a port.

The iSCSI name cannot be set because the number of iSCSI names exceeds the maximum that can be set in a port.

The default nickname cannot be specified in the nickname set for the iSCSI name.

None.




Error Code

1005,55574

8505,55577

8505,55578

8505,55579

8505,55580

8505,55581

9605,55584

5205,55586

1,55589

1005,55591

5205,55598

5205,55599

5205,55600

1205,56298

1205,56299

1205,56300

3005,56301

3005,56302

Description

The setting cannot be changed because the specified port's attribute is Initiator or External.

You cannot assign the CU number to the SLPR across multiple CU groups.

You cannot assign the port to the

SLPR across multiple CU groups.

You cannot assign the SSID to the


You cannot assign the CLPR to the


You cannot assign the parity group to the CLPR across multiple

CU groups.

The specified LDEV does not belong to the selected CU group.

The specified volume cannot be migrated because an extent in the volume is being shredded.

The specified CU group is invalid.

The specified iSCSI target name cannot be registered because the name is reserved for Target#00.

The specified volume is used as a

Delta resync volume for Universal

Replicator or Universal Replicator z/OS.







The SVP is busy. Wait a while, and then retry the operation.

I/O requests are being transmitted from the host connected via iSCSI.

The SVP is busy. Wait a while, and then retry the operation.

An error occurred during SVP processing. If this problem persists, contact the Support

Center.


Center.

None.




3-91

3-92

Error Code

3005,56303

105,56507

605,56507

3205,56513

3205,56514

605,56515

3205,56516

605,56517

3205,56517

605,56519

Description


Center.

The licensed capacity for a program product will become insufficient because of a configuration change. Add licensed capacity from the License

Key panel. If you do not add licensed capacity in 10 days, the program product will be unavailable.

The licensed capacity for a program product will become insufficient because of a configuration change. Add licensed capacity from the License

Key panel. If you do not add licensed capacity in 10 days, the program product will be unavailable.

The specified emulation type does not permit LDEVs to be added. If you want to set the specified emulation type, contact the support center because the cache segment size must be changed.

The operation to add an LU cannot be performed because the capacity of the specified volume is less than the required minimum.

The Disconnect Subsystem or

Disconnect Volume operation must be executed for the target volume.

Settings for Remote Copy exist.

Cancel the settings for Remote

Copy, and then try again.

Settings of ShadowImage,

ShadowImage z/OS, FlashCopy

Mirror, or COW SnapShot are defined. Cancel these settings, and then retry the operation.

Settings of ShadowImage,

ShadowImage z/OS or FlashCopy

Mirror, COW SnapShot are defined. Cancel these settings, and then retry the operation.

Reservation settings of

ShadowImage, ShadowImage z/OS, or FlashCopy Mirror are defined. Cancel these settings, and then retry the operation.

None.




1,56524

2,56524

305,56524

405,56524

505,56524

605,56524

3005,56524

5205,56524

6005,56524

6505,56524

6805,56524

Error Code

3205,56519

3205,56520

105,56521

605,56521

Description

Reservation settings of

ShadowImage, ShadowImage z/OS, FlashCopy Mirror, or COW

SnapShot are defined. Cancel these settings, and then retry the operation.

A reserved volume setting for

Volume Migration exists. Cancel the reserved volume setting for

Volume Migration, and then try again.

The licensed capacity of some program products will be insufficient because of the Add LU operation.

The licensed capacity of some program products will be insufficient because of the Add LU operation.

The partitioned storage administrator cannot use this function.











None.




3-93

3-94

Error Code

7005,56524

7105,56524

8005,56524

8305,56524

8505,56524

9005,56524

2,56525

305,56525

3005,56525

4105,56525

5105,56525

5205,56525

Description







Usage permissions have been switched from the partitioned storage administrator to the storage administrator, because there are settings across multiple

SLPRs.


SLPRs.


SLPRs.


SLPRs.


SLPRs.


SLPRs.

None.


To continue the operation, contact the storage administrator. To perform a different operation, push the Function button.



Error Code

5305,56525

8005,56525

9605,56525

*,56526

8505,56527

9605,56528

1,56529

605,56536

8505,56536

2,56543

1005,56543

5105,56543

1,56545

7,56546

Description


SLPRs.


SLPRs.


SLPRs.

The resources of another SLPR cannot be accessed.

The SLPR information owned by that user cannot be modified while another user is logged into

Storage Navigator.

The operation cannot be performed because the storage administrator is currently performing operations.

The SLPR that is available does not exist.

To continue the operation, contact the storage administrator. To perform a different operation, push the Function button.

None.


The licensed capacity was exceeded because the configuration was changed.

The licensed capacity was exceeded because the configuration was changed.

Resources of another CU group cannot be accessed.



The operation failed because the audit log is being processed. Wait a while, and then retry the operation.

Another user is downloading the file or transferring the file to the

FTP server. Wait for a while, and then retry the operation.

Contact the storage administrator and have the SLPR set.

Wait for a while, and then retry the operation.

Correct the permission capacity for the license in the License Key

Partition Definition window.

None.



3-95

3-96

1,56552

1,56553

1,56554

1,56555

1,56556

Error Code

1,56548

1,56549

1,56550

1,56551

1,56557

505,57004

8005,57004

4105,57010

1205,57099

1205,57100

Description

The SVP is transferring the file to the FTP server. Wait for a while, then retry the operation.

Another user is downloading the file or transferring the file to the

FTP server. Wait for a while, and then retry the operation.

Transfer to the FTP server is disabled. Check the setting.

Failed to connect to the FTP server. Check the IP address, or the connection between the SVP and the FTP server.

The file transfer to the FTP server failed. Check the user ID and the password.

The file transfer to the FTP server failed. Check the output folder and the status of the FTP server.

The file transfer to the FTP server failed. If this problem persists, call the Support Center.

The complete operation is performed to all SIMs related to

Audit Log.

Complete operation of SIMs failed because the number of audit logs that had not been transferred exceeded the threshold.

The complete operation of the

SIM may not have completed since the SVP is busy.

A contradiction was detected in the CLPR information in the subsystem. Correct the CLPR information.

A contradiction was detected in the CLPR information in the subsystem. Correct the CLPR information.

The CLPR with the PCR definition differs from the SLPR of the NAS port.

The request includes an unexpected parameter.

An internal logic error was detected in the specified request.

None.

None.

None.

None.

None.

None.

None.

None.

None.

None.




Error Code

3005,57101

3005,57102

1,57106

605,58246

605,58247

605,58248

605,58249

605,58299

7005,58299

7105,58299

605,58300

7005,58300

7105,58300

605,58301

7005,58301

Description


Center.


Center.

An invalid value is included in the management file of the audit log.



VMA is set for the specified primary volume.

VMA is set for the specified secondary volume.

The specified volume is being used as a NAS user volume.

The command was rejected because the specified P-VOL contains Universal Replicator settings.

The operation failed because the specified P-VOL was a data volume of Universal Replicator.

Check the requirements for joint use with Universal Replicator.

The command was rejected because the specified S-VOL contains Universal Replicator

Mainframe settings.

The command was rejected because the specified S-VOL contains Universal Replicator settings.

The operation failed because the specified S-VOL was a data volume of Universal Replicator.

The command was rejected because the specified T-VOL contains Universal Replicator

Mainframe settings.

The command was rejected because the specified volume contains Universal Replicator settings.

The reservation setting failed because the specified volume was a data volume of Universal

Replicator.

None.




3-97

3-98

Error Code

7105,58301

8505,58310

8505,58311

8505,58312

8505,58313

8505,58314

8505,58315

8505,58316

8505,58317

Description

The command was rejected because the specified volume contains Universal Replicator

Mainframe settings.

Some of the shared memory of the disk subsystem may be blocked, or maintenance operations are being performed for the disk subsystem. Check the status of the disk subsystem. If this problem persists, call the

Support Center.

Some of the cache memory of the disk subsystem may be blocked, or maintenance operations are being performed for the disk subsystem. Check the status of the disk subsystem. If this problem persists, call the Support

Center.

The configuration cannot be changed because the write pending rate of the target CLPR is too high.

The configuration cannot be changed because the available

Cache Residency size or the number of Cache Residency areas in the intended CLPR is insufficient.

The configuration cannot be changed because the available

Partial Cache Residence size in the intended CLPR is insufficient.

A maintenance job (Correction

Copy, Drive Copy, LDEV formatting, LDEV shredding, or

Extent shredding) is running in the disk subsystem. Retry the operation after the maintenance job finishes.

Parity groups in a CLPR are being migrated in the disk subsystem.


CLPR capacity is being changed in the disk subsystem. Wait for a while, and then retry the operation.

None.


Wait until the write pending rate falls, then retry the operation.

Check the Cache Residency size and the number of Cache Residency areas.

Check the Partial Cache Residence size.


Wait for a while, then retry the operation.



Error Code

8505,58318

6005,58319

6005,58320

6005,58321

6005,58322

8505,58323

605,58330

605,58331

605,58332

8505,58339

7005,58351


An error occurred on the DKC, while obtaining information about the progress of the CLPR process.

If this problem persists, call the

Support Center.

The pair cannot be created because the specified P-VOL is being used by Universal Replicator or Universal Replicator z/OS.

The pair cannot be created because the specified S-VOL is being used by Universal Replicator or Universal Replicator z/OS.

The pair cannot be created because the specified M-VOL is a

LUSE volume that is set across the multiple CLPRs.

The pair cannot be created because the specified R-VOL is a

LUSE volume that is set across the multiple CLPRs.

The CLPR that the parity groups belong to cannot be changed because the specified parity groups include only a part of the

TrueCopy Async or TrueCopy

Async Mainframe pair volumes in a CT group.

After executing an operation to disconnect a subsystem or volume, the operation to disconnect or check a path cannot be executed.

The path in the operation to disconnect or check a path was not found.

The external volume is blocked.

The CLPR that the parity groups belong to cannot be changed because the specified parity groups contain only part of one of the following: a Universal

Replicator volume of a journal group, a Universal Replicator z/OS volume of a journal group, or a journal volume. Make sure that you specify parity groups that contain all the volumes associated with the journal group.

The Quick Restore command has been rejected, because the specified pair is composed of internal and external volumes, and also used as a Universal

Replicator pair.

None.

Specify the parity group so that all the pair volumes in CT group are contained.

None.



3-99

3-100

Error Code

7105,58351

7005,58356

6005,58357

6005,58358

6005,58359

1205,58387

1205,58388

1205,58389

1205,58390

1205,58391

1205,58392

1205,58393

1205,58394

1205,58395

1205,58396

605,58397

Description

The Quick Restore command has been rejected, because the specified pair is composed of internal and external volumes, and also used as a Universal

Replicator pair.

The command was rejected because the specified volume is shared by Universal Replicator and TrueCopy.

This pair cannot be created because an attempt was made to combine a volume for which VMA is set for the data retention function, and a volume for which

VMA is not set.

This pair cannot be created because processing to set VMA for

Data Retention has not finished for the specified primary volume.

This pair cannot be created because processing to set VMA for

Data Retention has not finished for the specified secondary volume.

A communication error occurred while executing the setting contents.

PCB for iSCSI is not mounted.

The specified function is not supported.

The microprogram is being replaced in the disk subsystem.

Wait until it has been replaced, and then retry the operation.

The specified port is blocked.

The port is in Link Down status.

A communication error occurred while communicating with the iSNS server.

An error occurred in registration processing in the iSNS server.

An error occurred in deletion processing in the iSNS server.

There is no object to be deleted in the iSNS server.


None.




Error Code

605,58398

605,58399

605,58400

9605,58404

605,58406

605,58407

605,58408

605,58409

605,58410

605,58411

9605,58412

9605,58413

9605,58414

9605,58415

Description




The specified operation cannot be executed because LDEV shredding, extent shredding, or

LDEV formatting is being executed. Wait until processing has completed, and then retry the operation.

The operation to delete an LU cannot be performed on a volume being used by Universal Replicator or Universal Replicator z/OS.

The operation to delete an LU cannot be performed on a journal volume of Universal Replicator.

The operation to disconnect a subsystem or volume cannot be performed because the status of the specified external volume is

"Cache Cleanup".

The cache mode cannot be changed during an operation to disconnect a subsystem or volume.

The cache mode cannot be changed because bind mode is set for the specified volume.

The cache modes of the volumes that compose the LUSE volume are different. Set the same cache mode for the volumes that compose the LUSE volume.

Data pool volume attributes cannot be changed.

V-VOL attributes cannot be changed.

Attributes for primary volumes and secondary volumes of COW

Snapshot cannot be changed.

VMA cannot be changed for the data pool volume.

None.




3-101

3-102

Error Code

9605,58416

9605,58417

9605,58418

9605,58419

9605,58420

9605,58421

9605,58422

9605,58423

9605,58424

9605,58425

9605,58426

9605,58427

9605,58428

9605,58429

9605,58430

9605,58431

Description

VMA cannot be changed for the V-

VOL.

VMA cannot be changed for primary volumes and secondary volumes of COW Snapshot.

The access attribute of the specified volume cannot be changed because it is Universal

Replicator volume where copying is in progress, or is a pair volume.

The access attribute of a primary or secondary volume for remote copy cannot be changed when

VMA is set.

VMA cannot be set for the specified logical volume because the specified logical volume is a

LUSE volume.

The VMA cannot be set because the volume is being used by

Cross-system Copy.



The specified logical volume is blocked.

The VMA cannot be set for this logical volume because the logical volume is being used as a journal volume of Universal Replicator.

An extent has already been made for this LDEV.

The VMA is not set for this logical volume.

An extent is not set for this LDEV.

A protection period is set for this logical volume.

VMA cannot be set to the specified logical volume because the volume is used as a logical volume for iSCSI.

The VMA cannot be set for this logical volume because the logical volume is being used by Crosssystem Copy.

None.




Error Code

9605,58432

9605,58433

9605,58434

9605,58435

9605,58436

9605,58437

9605,58438

9605,58439

9605,58440

9605,58441

9605,58442

9605,58443

9605,58444

9605,58445

9605,58446

9605,58447

9605,58448

9605,58449

9605,58450

Description

VMA cannot be set for this logical volume because Volume Migration is using this logical volume.

The access attribute is set for this extent.

This logical volume is busy.

This logical volume is busy.

The access attribute for this logical volume has already been changed.

VMA has been set for this logical volume.

This logical volume has been configured as a command device.

This logical volume is a NAS system volume.

This logical volume is a NAS user volume.

This logical volume is an iSCSI volume.

The emulation type of this logical volume is not OPEN-V.

This logical volume is a mainframe volume.

The VMA cannot be set for this logical volume because the logical volume is being used by Remote

Copy, ShadowImage, or Universal

Replicator.

The VMA cannot be set for this logical volume because the logical volume is being used by

ShadowImage.

VMA was set for a secondary volume of Universal Replicator.

The command was rejected because an attempt was made to set VMA to a logical volume for which a path was set.

The specified logical volume is blocked, or the LDEV is being formatted or shredded.

The capacity of this logical volume is different from that of the external volume to which the logical volume is mapped.


None.




3-103

3-104

Error Code

6005,58452

605,58453

6005,58454

3005,58460

6005,58460

3005,58461

3005,58462

3005,58463

3005,58464

3005,58465

3005,58466

3005,58467

Description

The operation failed because the licensed capacity of Data

Retention on the RCU side was insufficient or Data Retention was not installed on the RCU.

The command was rejected because the licensed capacity for

Data Retention was exceeded.

The operation failed because the licensed capacity of Data

Retention on the MCU side was insufficient or Data Retention was not installed on the MCU.

This logical volume cannot be registered because it is not installed.

The specified P-VOL is already used as a primary data volume of


Replicator z/OS. If you want to use the P-VOL in conjunction with one of these program products, recreate the Universal Replicator pair or the Universal Replicator z/OS pair by using a mirror ID other than 0, and then retry the operation.

The specified operation cannot be performed because the logical volume is blocked.

This logical volume cannot be registered because it is defined as a data pool volume.

The specified logical volume cannot be registered because the

CLPR number of the volume does not match the number for the logical volume already registered for the pool.

The specified logical volume cannot be registered because it is a V-VOL.

A volume set as a Command

Device cannot be set as a component of a data pool volume.

The specified logical volume cannot be registered because a

SCSI path is set to this logical volume.

The specified volume cannot be set as a data pool volume because the specified volume exceeds the licensed capacity.

None.




Error Code

3005,58468

3005,58469

3005,58470

3005,58471

3005,58472

3005,58473

3005,58474

3005,58475

605,58476

Description

The emulation type of the logical volume is invalid.

The specified logical volume is being used by another program product.

The specified operation cannot be performed because the pool usage is 100% (full).

The shared memory for the V-VOL management area is insufficient.

An attempt to perform an operation on the pool has failed.

The pool cannot be registered when:







 the V-VOL management area is not initialized. the V-VOL management area is not installed. there is no space left in the V-

VOL management area. the pool is blocked.

 the state of shared memory is abnormal.

The pool cannot be deleted when:



 the V-VOL management area is not initialized. the V-VOL management area is not installed.

 a COW Snapshot pair still remains in the pool. a P-VOL remains in the pool.



 the pool is blocked.

The threshold of pool cannot be changed when:

 the threshold is set below the usage rate of the pool.

An error occurred while setting the pool. Check the error message of the logical volume set for the pool.

Shared memory is insufficient or an error occurred during SVP processing.

The PCB for a fibre port or iSCSI port is not installed.

The operation cannot be performed because the specified primary volume is a primary volume for COW Snapshot.

None.




3-105

3-106

Error Code

7005,58476

605,58477

7005,58477

605,58478

7005,58478

605,58479

7005,58479

605,58480

7005,58480

605,58481

7005,58481

605,58482

7005,58482

605,58483

Description

The operation cannot be performed because the specified primary volume is a primary volume for COW Snapshot.

The operation cannot be performed because the specified primary volume is a V-VOL.

The operation cannot be performed because the specified primary volume is a V-VOL.

The operation cannot be performed because the specified primary volume is a data pool volume.

The operation cannot be performed because the specified primary volume is a data pool volume.

The operation cannot be performed because the specified secondary volume is a primary volume for COW Snapshot.

The operation cannot be performed because the specified secondary volume is a primary volume for COW Snapshot.

The operation cannot be performed because the specified secondary volume is a V-VOL.

The operation cannot be performed because the specified secondary volume is a V-VOL.

The operation cannot be performed because the specified secondary volume is a data pool volume.

The operation cannot be performed because the specified secondary volume is a data pool volume.

The operation cannot be performed because the specified reserved volume is a primary volume for COW Snapshot.

The operation cannot be performed because the specified reserved volume is a primary volume for COW Snapshot.

The operation cannot be performed because the specified reserved volume is a V-VOL.

None.




3005,58491

7005,58492

7005,58493

6005,58494

6005,58495

6005,58496

6005,58497

6005,58498

Error Code

7005,58483

605,58484

7005,58484

6005,58499

6005,58509

6005,58515

Description

The operation cannot be performed because the specified reserved volume is a V-VOL.

The operation cannot be performed because the specified reserved volume is a data pool volume.

The operation cannot be performed because the specified reserved volume is a data pool volume.

A communication timeout error occurred on the disk subsystem.


The Pairsplit-S operation has failed. Check the configuration.

The PCB required for this operation is not mounted. Check the subsystem configuration.

This pair cannot be created because COW Snapshot is using the specified primary volume.

This pair cannot be created because COW Snapshot is using the specified secondary volume.

This pair cannot be created because the specified primary volume is a V-VOL.

This pair cannot be created because the specified secondary volume is a V-VOL.

This pair cannot be created because the specified primary volume is being used as a data pool volume.

This pair cannot be created because the specified secondary volume is being used as a data pool volume.

A communication timeout error occurred between MCU and RCU.


An inconsistency was detected during checking of the amount of copied migration data. Refer to the chapter describing checking of the amount of copied data in the data migration operation manual.

None.




3-107

3-108

Error Code

6005,58516

7005,58520

7005,58533

7005,58534

7005,58535

7005,58536

6005,58568

6005,58569

3005,58570

3005,58571

3005,58572

*,58573

Description

An inconsistency was detected during checking of the amount of copied migration data. Refer to the chapter describing checking of the amount of copied data in the data migration operation manual.

The operation failed because different versions of microprograms coexisted in the disk subsystem.

The operation failed because the specified P-VOL was a journal volume.

The operation failed because the specified S-VOL was a journal volume.

The reserve volume setting failed because the specified volume was a journal volume.

The operation failed because the specified S-VOL was a data volume of Universal Replicator.

Check the requirements for using the volume jointly with Universal

Replicator.

A pair cannot be created because the specified P-VOL is being shredded by Data Retention. Wait until shredding finishes, and then retry the operation.

A pair cannot be created because the specified S-VOL is being shredded by Data Retention. Wait until shredding finishes, and then retry the operation.

The virtual volume management area is being used. Delete the

COW SnapShot pair(s), and then retry the operation.

The specified operation cannot be executed because the pool volume is not mounted.

An error occurred during communication with the disk subsystem. Wait a while, and then retry the operation. If the error occurred in a pool operation, initialize the V-VOL management area, and click [Refresh All] to refresh the configuration.


None.




Error Code

3005,58574

3005,58575

3005,58576

6005,58577

2,58578

7005,58579

1205,58581

7005,58582

7005,58583

7005,58584

605,58585

7005,58585

6005,58586

605,58622

Description

An error occurred while connecting to the disk subsystem.


An error occurred while connecting to the disk subsystem.


A communication timeout error occurred in the disk subsystem.


The operation to erase an S-VOL cannot be performed. Delete the pair.

An error occurred in the disk subsystem. The configuration may be inconsistent. Click [All Refresh] and refresh the configuration.

The operation failed because the specified volume is being shredded by Data Retention. Wait until shredding finishes, and then retry the operation.

The iSNS server could not be registered or deleted because the target port has not been created.

The operation failed because the specified S-VOL was used by COW

Snapshot.

The operation failed because the volume was shared by a COW

Snapshot pair.

The operation failed because the volume was shared by a COW

Snapshot pair in COPY (RS-R) status.

The operation failed because the

CU group of the specified volume is not supported.

The operation failed because the

CU group of the specified volume is not supported.

The operation failed because the host did not allow the specified R-

VOL to be used as an R-VOL.

The LU cannot be deleted from the external volumes which include pool volumes. Release the pool volume setting and then retry the operation.

None.




3-109

3-110

Error Code

105,58623

605,58623

105,58626

605,58626

605,58630

7005,58630

605,58631

7005,58631

7005,58632

6005,58640

6505,58641

Description

The specified operation cannot be performed, because the COW

Snapshot pair using the pool volumes to be maintained is in

PSUS status or being restored.

Resynchronize the pair or release the pair definition, and then retry the operation.

The specified operation cannot be performed, because the COW

Snapshot pair using the pool volumes to be maintained is in

PSUS status or being restored.

Resynchronize the pair or release the pair definition, and then retry the operation.

A COW Snapshot pair is defined.

Cancel the pair definition, and then retry the operation.

A COW Snapshot pair is defined.

Cancel the pair definition, and then retry the operation.

The operation failed because the specified P-VOL was used by Delta resync of Universal Replicator.


The operation failed because the specified S-VOL was used by

Delta resync of Universal

Replicator.


The reserve volume setting failed because the specified volume was used by Delta resync of

Continuous Access XP - Journal.

The Add Pair operation failed. The volume pair cannot be created with Time Stamp set, because

RCU does not support 4x4x4 cascade function.

The specified volume cannot be used as a journal volume because the volume is set by Cache

Residency or Cache Residency z/OS.

None.




Error Code

105,58710

605,58710

7005,58711

6005,58712

6005,58713

6005,58714

Description

The specified volumes include remote command devices registered in the extended consistency group of Universal

Replicator z/OS(R). Delete all journal groups registered in the extended consistency group to delete the remote command devices.

The specified volumes include remote command devices registered in the extended consistency group of Universal

Replicator z/OS(R). Delete all journal groups registered in the extended consistency group to delete the remote command devices.

The operation failed because the specified MU number was already used. Specify other MU numbers.

The licensed capacity of TrueCopy or TrueCopy z/OS on the RCU is insufficient. Check the licensed capacity of this program product and the related program products.

The related program products are:





TrueCopy or TrueCopy z/OS(R)

TrueCopy Async or True Copy

Async z/OS(R).

The licensed capacity of TrueCopy

Async or True Copy Async z/OS on the RCU is insufficient. Check the licensed capacity of this program product and the related program products. The related program products are:







Async z/OS(R).

The licensed capacity of TrueCopy or TrueCopy z/OS on the MCU is insufficient. Check the licensed capacity of this program product and the related program products.

The related program products are:







Async z/OS(R).

None.




3-111

Error Code

6005,58715

605,58905

Description

The licensed capacity of TrueCopy

Async or True Copy Async z/OS on the MCU is insufficient. Check the licensed capacity of this program product and the related program products. The related program products are:







Async z/OS(R.)

Extended shared memory for

Universal Volume Manager is not installed.

None.


3-112 Hitachi USP Messages


Lightning 9900V series Messages

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for the Lightning 9900V series.



Details About Lightning 9900V series Messages

Lightning 9900V series Messages


4-1

Details About Lightning 9900V series Messages

Some messages displayed by Device Manager contain, as a part of the message, a message output from the storage subsystem. This section lists and describes the error messages from the Lightning 9900V series that are contained in Hitachi Device Manager messages.


Calling the Hitachi



When a Device Manager message contains a message from the Lightning

9900V series, the Device Manager displays two types of error code identifying

the Lightning 9900V messages and the message text. Table 4-1 lists and

describes the Lightning 9900V messages that are displayed by Hitachi Device

Manager.

Note: The list of messages below shows error codes 1 and 2, separated by a comma. The asterisk ("*") indicates that the error code output varies. If a displayed error code does not match any of the codes listed below, see the explanation for the message labeled *,*.

Table 4-1 Lightning 9900V Messages

Error Code

*,*

3,1002

3,1003

3,1004

3,1005

3,1007


An error has occurred in the subsystem. If you cannot solve this problem, contact the

Support Center.

You have set the Command Device for the volume to be used by TrueCopy or

ShadowImage.

You have attempted to specify more than one Path from one Group to the same volume.

You have attempted to set more than one volume for one Port/GroupID/LUN combination.

When you change the Path configuration, you cannot specify for the following volumes. 1. The volumes that have not been implemented. 2. The volumes other than the top volume of the LUSE. 3.

HIHSM Reserve Volumes 4."On-Demand" volumes.

You have attempted to delete the last

Path to TrueCopy volume or

ShadowImage volume.

If the problem persists, contact the Support Center.

Review the settings.

Correct the LU Path settings, and issue a request to set the configuration information again.

4-2 Lightning 9900V series Messages



3,1009

3,1010

3,1011

3,1012

The emulation type of the volume to be connected as a part of a LUSE is not Open volume.

You have attempted to set a LUSE that includes a LU that has already been extended.

The volumes to be connected as a LUSE extend across CU#.

A LU Path is set for the volumes to be connected as a LUSE.

The emulation types of the volumes to be connected as a LUSE are not the same.


3,1013

3,1015

3,1018

3,1020

3,1021

A LU Path is set for the LUSE to be released.

The Port for which you have specified to change the configuration does not exist.

An invalid LUN has been specified.


When specifying volumes as a

LUSE, you must use volumes with the same emulation types, sizes, and attributes (you cannot specify Normal Volume and

Customized Volume together.).

Remove the Path for the target volume before releasing the

LUSE.

You may have specified a Port that has not been implemented, or a Mainframe Port. Review the specified Port.


You may have specified a volume that has not been implemented, or a Mainframe volume. Review the specified volume.

Review the settings. 3,1022

3,1024

An invalid Host Mode has been specified.

1010,1023 An invalid Fibre Address has been specified.

Invalid Fibre Topology information has been specified.

3,1025

3,1027

The specified LU Path does not exist.

You have specified an invalid value in the

Command Device settings.

3,1028 The maximum number of volumes that can be connected as a LUSE has been exceeded. (MAX 36).

3,1029

3,1035

The volumes you have tried to connect as a LUSE do not have the same volume size. Or, you have tried to connect a

Customized Volume and a Normal Volume together.

You did not set the required Subsystem ID when you performed a CVS operation.

(INSTALL CV/Volume Initialize)

When specifying volumes as a

LUSE, you must use volumes with the same emulation types, sizes, and attributes (you cannot specify Normal Volume and

Customized Volume together.).

Set the Subsystem ID required for adding a volume, and issue a request to change the configuration again. (Note that you can either specify Boundary with 64 or 256.) For more details, contact the Support Center.



4-3

4-4

Error Code

3,1036

3,1037

3,1038

3,1039

3,1040

3,1041

3,1043

3,1044

3,1045

3,1049

3,1050

3,1051

3,1059

3,1061

Description

When specifying the Customized Volume, you have specified the size that is outside the legal value range. (The value specified is either less than the minimum value or greater than the maximum value.)

There is not enough space left in the

Logical Parity Group to create a CV.


Note that the legal value range may differ depending on the emulation type of the target volume.

You have specified emulation types for CV that cannot be used together. Or, you have specified the emulation types that are not supported.

When you perform CVS operations, you cannot specify for the following volumes.

1. The volumes to which LU Path is set. 2.

The volumes which are connected as an expanded LU. 3. The volumes where LDEV

Security is set.

An internal logical error has occurred.

The CU number or the LDEV number specified in the CVS operation is already used by other volumes.

You have instructed to perform an CVS operation on a Logical Parity Group which has not been implemented.

When you performed a CVS operation

(Volume Initialize), the number of volumes to be returned to Normal

Volumes and the number of volumes requested by Volume Initialize were not the same.

The specified Subsystem ID already exists.

When you performed a CVS operation

(Volume Initialize), you did not specify a

CV within the Logical Parity Group.

When you change the configuration for a

LUSE, you cannot specify for the following volumes. 1. HIHSM (hierarchy control function) Reserve volumes 2. "On-

Demand" volumes

You have specified an incorrect emulation type in the CVS operation.

You have set LUN Management Function

(LUN Security) for a Port that is not a

Fibre Port.

You have attempted to perform a LUN

Security operation on the Port for which

LUN Security Function is disabled.

When you specify the value, consider the fact that the number of LDEVs that can be stored in a

Parity Group may vary depending on a Drive Type and a RAID Type.

For more details, contact the

Support Center.

Since each emulation type has a different definition, contact the

Support Center for more details.

Review the target volume.



Switch on the Security.




3,1062

When you performed a CVS operation, you specified a wrong emulation type of a volume, and the way in which the size of the volume is specified does not correspond to its emulation type.

3,1063 You have attempted to register an existing WWN number.

1110,1064 You have attempted to register an existing WWN.

3,1065 You have attempted to register an existing WWN nickname or an existing

Host Group nickname.

1110,1065

You have attempted to register an existing WWN nickname or an existing

Host Group nickname.

3,1066 You have specified a WWN number that has not been registered (at the time of deletion or modification)

3,1067

3,1068

You have attempted to register an existing Host Group number.

You have specified an unregistered Host

Group.

3,1074

3,1075

3,1101

3,1102

The CU you have specified when performing the CVS operation (Install CV) is invalid.

You have specified different types of CVS operations (Volume Initialize, Install CV,

Volume to Space) in a single request to set the configuration information.

You have requested a CVS operation for a volume that has not been implemented.

At least one LDEV is required in a Parity

Group, so further reduction is impossible.

3,1103

3,1104

You have instructed to perform a CVS operation on the Parity Group, which has not been implemented.

You have tried to specify a SubSystem ID without performing a CVS operation.


Specify the user-defined Cylinder number for Mainframe volumes, and specify user-defined size for

Open volumes.


Specify one of the operation types when performing a CVS operation.


Issue a request to change the

SubSystem ID when you perform a CVS operation.

Review the volume to which the

Command Device is set.

3,1108 When you change the configuration for

Command Device, you cannot specify for the following volumes. 1. HIHSM Reserve volumes 2. "On-Demand" volumes 3.

Volumes other than Open volumes

(including the volumes not yet implemented)

1110,1110 You have specified invalid characters in the Host Group nickname or the WWN nickname.

3,1111 You did not specify a nickname when you issued a request to change the configuration for LUN-Security.

You cannot use

\/:,;*?"<>|

, and you cannot place a blank at the top or at the end of the string.

Make sure to specify a Host

Group nickname.



4-5

4-6

Error Code

3,1113

3,1116

3,1123

3,1124

3,1125

3,1126

3,1127

3,1128

3,1129

3,1130

3,1131

3,1132

3,1133

3,1134


The volume you have tried to create in the CVS operation is currently used to provide the HPAV function.

You did not specify a value when you registered the WWN. Or, you specified 0 for the WWN value.

You have requested to set the Command

Device Security, but the Command Device has not been set to the volume.

There is an error in the Command

Device/Command Device Security settings. You cannot do the following on the same volume. 1.Setting the Command

Device + Releasing the Command Device

Security 2.Releasing the Command Device

+ Setting the Command Device Security

There are no Host Groups to which the

WWN is registered.

Some volumes, which you have tried to connect as a LUSE, have the Command

Device settings.

You have specified CHA high speed mode, but the CHA has not been implemented.

You have requested to change the channel speed, but the version of Fiber PCB is not supported.

When you registered the WWN in the

LUN-Security operation, the maximum number of WWN that can be registered

(MAX 255) was exceeded.

When registering the Host Group nickname and the WWN nickname, you specified an invalid nickname. (xx-G00: xx is a Port name, such as 1A, 1B)

When setting the Host Group

(add/change/delete), you specified a value larger than the maximum value (0 to 127) allowed for the Port.

When setting the WWN (add/change), you specified a value larger than the maximum value (0 to 254) allowed for the

Port.

When setting the Host Mode, you specified a value for Host Group ID that is larger than the maximum value allowed for the

Port.

When setting the Path (add/change), you specified a value larger than the maximum value allowed for the Port.

(When Security Switch is OFF:256 / When

Security Switch is ON: 512)

Change the specified volume ID, or release the HPAV settings.

Make sure to specify the WWN value before issuing a request to change the configuration.

You need to set the Command

Device to the volume before or at the same time you set the

Command Device Security.


Review the Channel Package.




Error Code

3,1135

3,1136

3,1137

3,1140

3,1142

3,1143

3,1144

3,1145

3,1146

3,1147

3,1148

3,1149

3,1150

3,1151

3,1154

3,1156

3,1159

Description

When setting the Port Information (Fibre

Address/Fibre Topology/Channel Speed), you provided more than one instruction to make changes to the same Port.

When setting CHA high speed mode, you provided more than one instruction to make changes to the same Port.

When setting LUSE, you specified a value larger than the maximum value allowed in

DKC (MAX. 4096).

You cannot change it as it has the settings for Port Group.

The specified LDEV cannot be changed as it has LDEV Security Settings.

This error normally does not occur.

Contact the party who created the program.

The LDEV on which you have specified to perform a CVS operation is specified to be a LUSE.


Multiple configurations are specified for the port for which you attempted to change the configurations.


Release the settings for Port

Group.

Release the LDEV Security settings for the LDEV, and then specify the LDEV again.

This error normally does not occur. Contact the party who created the program.

Release the LUSE settings for the

LDEV, and then respecify the

LDEV on which the CVS operation is performed.

Review the settings. You have attempted to change Fibre

Address, Topology, Channel Speed,

Security Switch, Initiator/Target of a Port on E-NAS.

You attempted to add a Path to a User group in E-NAS, but you failed because the status of the System LU has not been defined.

You have attempted to add a Path to an

LDEV that has been defined to be used for

System LU in E-NAS.

You have specified the Intermediate volume as User LU of E-NAS.

You have attempted to set (add/delete) a

Path to the System LU Group in E-NAS.

You have specified CMDDEV for the LDEV that is defined for System LU in E-NAS.

You have attempted to change the speed mode by specifying a package for E-NAS

(CHA).

When specifying OPEN-V, you specified a volume with a different size including

LUSE.

When specifying OPEN-V, you specified a volume with different CU including LUSE.

When specifying OPEN-V, you specified more than 2[TB] of size of a volume including LUSE.

Set the System LU in SVP.






4-7

4-8

Error Code

3,1169

3,1175

3,1176

3,1180

3,1181

3,1182

3,1183

3,1184

3,1192

3,1201

3,1203

3,1204

3,1350

3,1351

3,1352

3,1353


You have specified the same Logical PG for the old settings and the new settings where both settings exist.

Fibre port settings cannot be made for an iSCSI port.

High-speed mode cannot be set for iSCSI packages.

You have specified System-LU and other

LUs with 1 PDU.

You have specified to add a Path to a volume with a Remote Copy Pair, but the

Path cannot be added.

You have attempted to set more than 2TB for LUSE.

You have attempted to set Point to Point for a high speed mode PCB port.

In the high speed mode, you have attempted to set a Fiber Address that already exists.

A command device setting cannot be made for a volume for which a path from an iSCSI port is defined.

You have specified CHA high speed mode, but some Paths you have specified cannot be set to high speed mode. (CHA SPEED is not always the same)

You have specified CHA high speed mode, but some Fiber Addresses of the Port you have specified cannot be set to high speed mode. (Fibre Address is always the same)

You have specified CHA high speed mode, but some Fibre Topologies of the Port you have specified cannot be set to high speed mode. (not all are specified to use FC-AL)

Since the Port to which you have tried to set the Path is a Port for Fibre TrueCopy, you cannot use it.




Some Ports to which you have tried to set the CHA high speed mode have different attributes.

Since the logical Path for Fibre TrueCopy is set to the port you have tried to specify, you cannot change it.

Since the S-VOL logical Path is set to the

Port you have tried to specify, you cannot change it.

In order to be able to set the path, change the attribute of the port. (Change the attribute to

Target or RCU Target.)

When specifying CHA high speed mode, set the same attribute to all the Ports.

Release the logical Path, and then issue a request to change the configuration again.

Delete the S-VOL logical Path that is set to RCU Target Port, and then specify the settings. Issue a request to change the configuration again.



Error Code

3,1354

3,1355

3,1356

3,1357

3,2003

3,2004

3,2005

Description

Since the Port you have tried to set has an Initiator attribute, you cannot change it.



Since the Port you have tried to set is a port used for Fibre TrueCopy, you cannot set it.

The program that allows you to use the functions of LUN Management is not installed. Alternatively, the program is no longer available as it has expired.

You have failed to retrieve the configuration information.

The files required by the application cannot be loaded.

The amount of memory required by the application cannot be secured.


Change the attribute of the Port.

(Change the attribute to Target or

RCU Target.)

After deleting the logical Path, set it again.

3,1600

3,1601

3,1602

The program that allows you to use the functions of Open Volume Management is not installed. Alternatively, the program is no longer available as it has expired.

The program that allows you to use the functions of Volume Management is not installed. Alternatively, the program is no longer available as it has expired.

3,1603

4105,1603 The program that allows you to use the functions of Open Cache Management is not installed. Alternatively, the program is no longer available as it has expired.

3,1604

The program that allows you to use the functions of Open Cache Management is not installed. Alternatively, the program is no longer available as it has expired.

The program that allows you to use the functions of Cache Management is not installed. Alternatively, the program is no longer available as it has expired.

3,2002 You have failed to establish a communicating connection between the

DKCs (SVPs).

Install the required program.

(Since there are three different series of programs, after the program has expired, you may not be able to install another one.)

Review the LAN settings. If the problem persists after reviewing the settings, contact the Support

Center.

Check for SVP if the status of DKC is normal. If the problem persists after checking the status, contact the Support Center.

Since it is likely that there is not sufficient memory, reboot SVP and try again. If the problem persists after reviewing the settings, contact the Support

Center.



4-9

4-10

Error Code

3,2009

3,2010

3,2011

3,2012

2,2013

3,2013

3,2014

3,2015

2,2016

3,2016

3,2017

3,2022

3,2033

3,2081

3,2082

3,2083

3,2084

3,2085

3,2086


The version of microcode in SVP and the version of microcode in DKC are not the same.

The host for the target Path/volume may be generating I/O.

Check the status of DKC (if it is blocked or not).

A Port blockage error has occurred.

Requests to change the configuration for different P.P.s have been received at the same time.

A download error has occurred.

Review the versions of microcode in SVP and DKC.

Check if the host for the target

Path/volume is generating I/O.

If the problem persists after reviewing the settings, contact the Support Center.


Review the settings, then retry.


A Port recovery error has occurred.

A communication error occurred between

SVP and DKC.

Revise the LAN settings. If the problem persists after revising the settings, contact the Support

Center.

Wait for a while, then retry. Another user is changing the configuration, or the configuration is being changed.

A SNMP user or maintenance staff is accessing the system in Modify mode.

Lock has been released.

A CVS process is being performed in DKC. Wait for a while and issue a request to change the configuration again.

The system is in the process of initial start-up, or internal refresh.

After obtaining Lock, change the configuration again.

Contact the Support Center. An error has occurred during the CVS increase/decrease process.

It is being mounted by a host, or the cluster configuration option has been selected.

An error has occurred during the process to change the configuration on the DKC.

Since it is being mounted by a host, or the cluster configuration option is being selected, cancel these states.

Check the status of DKC for the current configuration settings. If necessary, perform the set up operation again.

The result of changing the configuration is unknown.

An error has occurred during the precheck of a CVS operation. (While performing

COPY of TrueCopy/ShadowImage)

An error has occurred during the precheck of a CVS operation. (The configuration for

TrueCopy/ShadowImage has been defined.)

Wait a while, then retry.

Release the configuration definition of

TrueCopy/ShadowImage, then retry.



Error Code

3,2087

3,2088

3,2089

3,2090

3,2091

3,2092

3,2093

3,2094

3,2095

3,2096

3,2097

3,2170

3,2201

3,3000

3,3001

3,3002

Description

An error has occurred during the precheck of a CVS operation. (Vary Online has been issued from Mainframe host.)

An error has occurred during the precheck of a CVS operation. (TrueCopy is being suspended.)

An error has occurred during the precheck of a CVS operation. (The specified CHA may include the last path between MCU and RCU of TrueCopy.)

An error has occurred during the precheck of a CVS operation. (The ShadowImage option has been set.)

An error has occurred during the precheck of a CVS operation. (The back up server for ShadowImage is running.)

An error has occurred during the precheck of a CVS operation. (A ShadowImage Pair is included.)



An error has occurred during the precheck of a CVS operation. (A maintenance related operation is being performed.)

An error has occurred during the precheck of a CVS operation. (The function is not supported on the main side. The specified function is not supported.)

The specified WWN is doing I/O, or you have issued a request to an unregistered

WWN or a WWN used by a group.


Issue Vary Offline from the

Mainframe host you are connected to.

Add an alternative Path.

Check that there is an alternative path from MCU first.

Release the settings for

ShadowImage, or stop the I/O, then retry.

Stop the backup server, then retry.

Separate the ShadowImage Pair.

Resynchronize the ShadowImage

Pair.

Change the ShadowImage volume to Simplex.

Wait for a while, then retry.


The I/O during running Extended Copy

Manager may not have been stopped.

Processing cannot be performed because of the Open LDEV Guard settings.

The system has failed to retrieve a pointer from an external function that is required within the application.

The system has failed to retrieve a pointer from an external function that is required within the application.

The interfaces between the applications are inconsistent.

Review the specified WWN and check if it has been registered or not, release from the Host Group, or stop the I/O from the host.

Then, retry.

Stop the I/O during running

Extended Copy Manager.

Review the settings, then retry.

Try again after rebooting SVP. If the problem persists, contact the

Support Center.



4-11

4-12


3,3003

3,3004

3,3005

3,3006

3,3007

1,4002

1,4003

1,4004

*,4005

*,4011

*,4012

*,4020

An unexpected error has occurred.

Login failed. The inputted user ID is incorrect.

Login failed. The inputted password is incorrect.

The user ID is already logged in.

There is no RMI object or forcible logoff was carried out.

The maximum number of RMI connections was exceeded.

Try again after rebooting SVP. If the problem persists, contact the

Support Center.

The process to manage the configuration information has failed.

The process to manage the configuration information has failed.

An error occurred in accessing the file that is required within the application.

An interface logical error within the application has been detected. Or, an unregistered error has occurred.

There is no data in the authorization file, so login failed.


It is necessary to register the authorization data. Contact the

Support Center.

Input a correct user ID, then retry.

Input a correct password, then retry.


Attempt to login again.

The lock was canceled by force.

The maximum number of users are logged on. Wait for a while, then retry.

The lock was cancelled. You need to re-lock.


Check the P.P. code, then retry.

Login again using the other user name.

Wait for a while, then retry.

405,5047

405,5070

An error has occurred during

INSTALL/DEINSTALL operation.

P.P. code is not matching.

*,5132

*,5510

*,5511

The user of a same name has already logged in.

This subsystem is under configuring or maintenance. Wait for a while, and then retry.

P.P. required for this function is not installed.

*,5626 The specified volume cannot be used because write protection is set by LDEV

Guard.

7010,5653

The Command was rejected because a path is defined from an iSCSI port for the specified volume.

8105,5789 The intermediate volume cannot be specified as a command device.

4,6001 A timeout has occurred. The SVP will reboot. Wait a while, and then retry.

2,6502 The subsystem is busy.

Install P.P. required for this function, and then retry.

Change the LDEV Guard settings.

Select a volume for which a path from an iSCSI port does not exist.

Check the specified LDEV.






1010,6509 The specified host mode is invalid.

6005,8940 The operation failed because the specified

R-VOL is Read Only by LDEV Guard.

6005,8944 The specified S-VOL is not available because an attribute of the S-VOL was changed by Open LDEV Guard.

6005,8974 You cannot create a pair because a path is defined from an iSCSI port to the specified P-VOL.

6005,8975 You cannot create a pair because a path is defined from an iSCSI port to the specified S-VOL.

2,9000 Another user has locked.

Check the specified host mode.

Check if the attribute of the specified R-VOL is Read Only in

LDEV Guard.

Check the status of the specified

S-VOL.


P-VOL.


S-VOL.




4-13

4-14 Lightning 9900V series Messages


Lightning 9900 Messages

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Lightning 9900.



Details About Lightning 9900 Messages



5-1

Details About Lightning 9900 Messages

Some messages displayed by Device Manager contain, as a part of the message, a message output from the storage subsystem. This section lists and describes the error messages from Lightning 9900 that are contained in

Hitachi Device Manager messages.


Calling the Hitachi



The following table lists and describes the Lightning 9900 messages that are displayed by Hitachi Device Manager.

Note: The asterisk ("*") indicates that the error code output varies. If a displayed error code does not match any of the codes listed below, see the explanation for the message labeled *.

Table 5-1 Lightning 9900 Messages

Error

Code

Error Message

*

1000

1002

1003

1004

1005

1007


An error has occurred in the subsystem. If you cannot solve this problem, contact the

Support Center.


Support Center.

The setting requests for Host Modes 0xN1 and

0xN2 (N: the four high-order bits can be any value) are not identical on the corresponding

Ports of cluster-1 and cluster-2. (The corresponding Ports of both clusters were not set at the same time.)

An attempt was made to set the TrueCopy volume or ShadowImage volume as the command device.

An attempt was made to set multiple Paths from a single Port to the same volume.

None.

Correct the Host Mode specification and issue the configuration information setting request again.

Correct the command device specification and issue the configuration information setting request again.

Correct the LU Path specification and issue the configuration information setting request again.

An attempt was made to set multiple volumes for a single Port/SCSI ID/LUN combination.

An attempt was made to define a Path to a volume other than the top volume of the

LUSE.

An attempt was made to delete the last Path to the TrueCopy volume or ShadowImage volume.

5-2 Lightning 9900 Messages


Error

Code

1008

1009

1010

1011

1012

1013

1014

1015

1018

1019

1020

1021

1022

1023

1024

1025

1027


An attempt was made to set a volume for which no LU Path is defined, as the command device. Or, an attempt was made to delete the last Path to the command device.

The emulation type of the volume to be linked as an LUSE is not Open volume.

An attempt was made to set an LUSE that contains an LU that has already been extended.

The volume to be linked as an LUSE extends over CU#.

An LU Path was set for the volume to be linked as an LUSE.

The emulation types of volumes to be linked as an LUSE are not the same.

No LU Path was set for the LUSE. (No Path was set for the LUSE to be added. Or, the

Path for the LUSE no longer exists because it was deleted.)

An LU Path was set for the LUSE to be freed.

(The Path must be freed at the same time as the LUSE is freed.)

The specified Port does not exist (specified

Port number is incorrect) or is a type (for

Mainframes only) that cannot be processed by the agent.

The SCSI ID is invalid. (The specified value is outside the specifications.)

The LUN is invalid. (The specified value is outside the specifications.)

The specified volume does not exist (specified

CU#:LDEV# is incorrect) or is a logical device of a type (for Mainframes only) that cannot be processed by the agent.

The Host Mode is invalid. (The specified value is outside the specifications.)

The Fibre Address is invalid. (The specified value is outside the specifications.)

The Fibre Topology information is invalid.

(The specified value is outside the specifications.)

The specified LU Path does not exist. (The specified Path control index is incorrect.)

The command device specification is invalid.

(The specified value is outside the specifications.)

Correct the LU Path specification and issue the configuration information setting request again.

Correct the LUSE specification and issue a configuration information setting request.

Correct the LUSE specification and issue a configuration information setting request.

Correct the specification and issue the request again.



5-3

5-4

Error

Code

1028

1029

1035

1036

1037

1038

1039

1041

1044

1045

1047

1049

1050

1051

1052

1053

1055


The number of volumes to be linked as an

LUSE is outside the specifiable range. Or, not all LDEVs that make up the LUSE to be freed were specified.

The sizes of the CVs to be linked as an LUSE are not the same. Or, an attempt was made to link a CV and Normal Volume.

The Subsystem ID required for CVS operation was not set.

The CV size is outside the specifiable range

(smaller than the minimum value or larger than the maximum value).

There is no capacity for creating the CV remaining in the Parity Group.

Objects that cannot be mixed were specified as the emulation type of CV.

An attempt was made to operate CVS for a volume for which a LU Path is set, a volume for which the LU is extended, or a volume for which LDEV Security is set.

The CU number or LDEV number specified for

CVS operation is the same as that for another volume.

At CVS operation (Volume Initialize), the number of volumes to be reset to Normal

Volume is different from the number of volumes requested for Volume Initialize.

The specified Subsystem ID is the same as an existing Subsystem ID.

An error occurred during CVS expansion or reduction.

At CVS operation (Volume Initialize), CV was not set in the target Parity Group.

Confirm the number of Normal Volumes to be reset and issue the request again.


Issue the same CVS specification again.

The volume to be linked as an LUSE contains a reserve volume of HIHSM (hierarchy control function).

The emulation type specified for CVS operation is incorrect.

An attempt was made to include a WWN which is already included in a group in another WWN group.

An attempt was made to group together

WWNs that have different access permission set.

An attempt was made to set access permission for a LUN included in a LUN group.

Correct the specification and issue the configuration information setting request again.


Correct the WWN group specification and issue the configuration information setting request again.

Correct the access permission for the

LUN and issue the configuration information setting request again.



Error

Code

1056

1057

1058

1059

1060

1061

1062

1063

1064

1065

1066

1067

1068

1069

1070

1071

1072


An attempt was made to set access permission for WWN included in a WWN group.

An attempt was made to include a LUN which is already included in a group in another LUN group.

An attempt was made to group together LUNs that have different access permission set.

An attempt was made to operate LUN

Security for a Port that is not a Fibre Port.

Correct the access permission for the

WWN and issue the configuration information setting request again.

Correct the LUN group specification and issue the configuration information setting request again.



Security for a LUN that has no LU Path.


Security for a Port on which the LUN Security function has no effect.

The emulation type and a size appropriate to the emulation type specified when setting

Install CV are incorrect. (Specify a userspecified capacity for a Mainframe volume.

Specify a user-specified number of cylinders for an Open volume.)

An attempt was made to register the same

WWN number as one that is already registered.


WWN as one that is already registered.


WWN nickname or WWN group nickname as one that is already registered. (The WWN nickname and WWN group nickname must not duplicate each other.)

The specified WWN number is not registered.

(At deletion or modification)





WWN group number as one that is already registered.

The WWN Group number was not found.


LUN group number as one that is already registered.

The specified LUN group number is not registered. (At deletion or modification)

A setting request having the same contents as those already set was issued for the same

Port.


LUN group nickname as one that is already registered.



5-5

5-6

Error

Code

1073

1074

1075

1100

1101

1102

1103

1104

1105

1108

1110

1111

1113

1114

1115

1116


There is no volume that can be set at CVS operation (Install CV).

The CU specified at CVS operation (Install CV) cannot be set.

Review the set CV and issue the configuration information setting request again.


Different CVS operations (Volume Initialize,

Install CV, Volume to Space) were specified together in a single configuration information setting request.

There are less than two WWNs that belong to the WWN group.

The CVS operation was requested for a volume that is not mounted.

The LDEV to be reduced by the CVS operation could not be deleted. (The target LDEV is the last in the Parity Group.)

In CVS operation, an operation instruction was issued for a Parity Group that is not mounted.

An attempt was made to set a SubSystem ID without the CVS operation.

There must be at least one LDEV in a

Parity Group, so further reduction is impossible.


The number of LDEV IDs that can be set in the CVS operation was exceeded.

A request was made to set a command device for a HIHSM Reserve volume.

Match the required CVS setting and

SubSystem ID and issue the configuration modification request again.

Review the LDEV IDs, delete an existing

LDEV if necessary, and issue the request again.


Review the specified characters and issue the configuration modification request again.

The character string specified as the nickname when requesting modification of the configuration of LUN-Security contains a character that cannot be used.

No nickname was specified when requesting modification of the configuration of LUN-

Security.

The volume to be created by the CVS operation is being used as the MAV function.

Specify a nickname and issue the configuration modification request again.

No value was set for WWN information that belongs to WWN group information when the

LUN-Security operation was executed.

No value was set for LUN information that belongs to LUN group information when the

LUN-Security operation was executed.

No value was set when registering WWN. Or,

0 is set as the WWN value.

Change the volume for which the CVS operation is to create a CV and execute the CVS operation again.

Review WWN information for grouping

WWNs and issue the configuration modification request again.

Review LUN information for grouping

LUNs and issue the configuration modification request again.

Review WWN to be registered and issue the configuration modification request again.



Error

Code

1123

1124

1201

1202

1203

1204

1205

1206

1261

1262

1263

1269

1290


A request was made to set command device security, but a command device has already been set.

The method of setting command device security is incorrect. (To set command device security, set it when setting the command device. And, to free command device security, set it when freeing the command device. However, freeing the command device also frees command device security at the same time.)

The CHA high-speed mode was specified, but the specified Path contains a Path for which the high-speed mode cannot be set.

The CHA high-speed mode was specified, but the specified Port contains a Host Mode for which the high-speed mode cannot be set.

The CHA high-speed mode was specified, but the Fiber Address of the specified Port contains a path for which the high-speed mode cannot be set.

The CHA high-speed mode was specified, but the topology in the specified Port contains a path for which the high-speed mode cannot be set.

The CHA high-speed mode was specified, but a Fiber PCB for which the high-speed mode cannot be set is specified.

The operating mode contains an undefined

CHA, so the specified setting is impossible.

A request was made to modify the configuration of the Path setting for a volume controlled by OnDemand.

A request was made to modify the configuration of the command device setting for a volume controlled by OnDemand.

A request was made to modify the configuration of the LUSE setting for a volume controlled by OnDemand.

The operating mode of the target PCB cannot be modified because I/Os from the host are being executed. (If multiple PCBs are specified at the same time, the operating mode may be partially modified.)

A temporary key was used before when requesting modification of the configuration of a license key, so it cannot be used again.

If you want to specify command device security for the target volume, free the command device setting and issue a configuration modification request. Or, assign processing to a different volume.

Review the specification and issue the configuration modification request again.

Change the parameter to a Path for which the high-speed mode can be set and execute the request again.

Specify a Host Mode for which the highspeed mode can be set and execute the request again.

Specify the Port of a Fiber Address for which the high-speed mode can be set and execute the request again.

Specify a Port whose topology setting allows the high-speed mode to be set and execute the request again.

Specify the Port of a Fiber PCB for which the high-speed mode can be set and execute the request again.

Set the operating mode for CHA and issue the request again.

Correct the specification and issue the request again. Or, free the Parity Group controlled by OnDemand.

First, confirm the operating mode for

PCB. Stop I/Os for the unmodified PCB, and execute the modification again.

To use the license key, take the following measures:

1. Obtain a permanent key and register the license key again.

2. After 180 days, input the same license key again.



5-7

5-8

Error

Code

1291

1292

1293

1294

1295

1296

1297

1298

1299

1350

1351

1352


The capacity for registering licenses when requesting modification of the configuration of a license key is insufficient.

The capacity for prerequisite program products was insufficient when requesting modification of the configuration of a license key.

Obtain the license key again. Or, expand the capacity.

Review the size of the program products already set and, when you have obtained a license key appropriate to the size of the program products, issue the configuration modification request again.

Review the license key and issue the configuration modification request again.

The program product was already installed when requesting modification of the configuration of a license key.

An error occurred when checking whether a program product can be installed when requesting modification of the configuration of a license key.

The license key that you tried to install or uninstall may not be able to be accepted due to RAID configuration information.

Also, the program product may already be set, so free the setting and issue the configuration modification request again.

The key code that was input is invalid. The key code was invalid when requesting modification of the configuration of a license key.

AA prerequisite program product was not installed when requesting modification of the configuration of a license key. Alternatively, the prerequisite program product was already uninstalled.

Prerequisite program products are required for inputting a license key for which a request is issued. After setting the prerequisite program products, request modification of the configuration again. Or, first uninstall program products that share a parent-child relationship with the prerequisite program product.

Obtain the license key and issue the configuration modification request again.

The program product specified when requesting modification of the configuration of a license key does not exist.

Requests having the same product ID for

INSTALL/DEINSTALL were issued when requesting modification of the configuration of a license key.

Multiple DEINSTALL were requested within a single PDU when requesting modification of the configuration of a license key.

An attempt was made to add a Path to an initiator Port.

You cannot change to high-speed mode because the Port attributes (such as initiator) within the package are mixed.

You cannot change because a logical Path remains in the initiator Port.

Separate INSTALL/DEINSTALL having the same product ID before issuing a configuration modification request.

Separate the DEINSTALL requests before issuing a configuration modification request.

The Port to be set is a Fibre TrueCopy

Port, so the attribute must be changed before a Path is added. Attribute (TarGet or RCU TarGet)


Port, so all attributes of the Port must be changed to initiator before switching to high-speed mode.


Port, so the logical Path must be erased before the Port is set.



1401

1402

1403

1404

1406

1407

1408

1410

1411

1412

Error

Code

1353

1354

1400

1405

1415

1416

1417

1418


You cannot change because S-VOL remains in the RCU target.

An attempt was made to register WWN for an initiator Port.

An input parameter is invalid. (RCU Port number/ID/LUN)(MCU/RCU serial number, or

SSID)(too many Paths specified).

The Port type is invalid "Serial"/"Fibre".

The specified volume is not a TrueCopy Pair.

The target CU cannot be found.

The specified Port is not "Serial"-

"RCP"/"Fibre"-"Initiator".

Correct the Port type and issue the request again.

Review the LDEV to be specified and issue the request again.

Review the CU to be specified and issue the request again.

Confirm the specified Port and specify the correct Port, or change the Port to

RCP/Initiator and issue the request again.

The connection destination address is invalid. Confirm the logical address, set the correct address and issue the request again.

The same Path already exists.

The number of Paths exceeds the limit.

(Serial:4 Fibre:8)

The Path does not exist.

Review the Path to be specified and issue the request again.

Review the input parameters and issue the request again.

The specified RCU extension volume

(Port/ID/LUN) cannot be used.

Four RCUs are already registered.

Four SSIDs are already registered in the target CU.

Confirm the SSID values of the RCU. If invalid SSIDs were registered, delete them and issue the request again.

Review the SSID setting and issue the configuration modification request again.

The SSID setting contained an error when requesting modification of the configuration of

TrueCopy.

An attempt was made to set a value higher than the upper limit (4) for the SSID setting when requesting modification of the configuration of TrueCopy.

Multiple operation instructions were set within the same PDU when requesting modification of the configuration of TrueCopy.

The specified RCU was already registered when registering RCU.


Port, so the S-VOL logical Path set to

RCU TarGet must be erased before the

Port is set.


Port, so the attribute must be changed before WWN is added. Attribute (TarGet or RCU TarGet)

Review the parameters and issue the request again.

Review the set SSIDs and issue the configuration modification request again.

Separate the operation requests before requesting modification of the configuration.

Review the set RCU and issue the configuration modification request again.



5-9

5-10

1421

1422

1423

1424

1433

1434

1435

1438

1439

1440

1500

1501

1429

1430

1431

1432

Error

Code

1419

1420

1425

1426

1427


The requested operation is impossible because detailed Path information is not given.

Review the command to be issued and issue the modification request again.

The requested operation is impossible because a summary of Path information is not given.

A logical Path remains in the target MCU Port. Delete the logical Path that remains and execute a retry.

A logical Path remains in the target RCU Port. Delete the logical Path that remains and execute a retry.

A LU definition remains in the target RCU

Port.

Delete the LU definition and execute a retry.

"RCP" of a "Serial" Port was specified in the

MCU Port specification, but no link address to be set for "Serial" was set.

"Initiator" of a "Fibre" Port was specified in the MCU Port specification, but no receive

Port to be set for "Fibre" was set.

A "Fibre" Port was specified in the MCU Port specification in a CU image for which "Serial" was set.

A "Serial" Port was specified in the MCU Port specification in a CU image for which "Fibre" was set.

Confirm the parameters or Port specification.

Confirm the existing setting or MCU Port specification.

The Port mode of a closed Port was changed. Confirm the specified Port.

A setting was input for a Port that is not mounted.

No option ("RIOMIH timer"/"PathBlockadeWatch") was specified.

An unnecessary specification was made.

("RIOMIH timer"/"PathBlockadeWatch")


A setting was input for a Port that is not targeted.

A LU remains in the target Port.

Confirm the specified Port. (It may be a

Port not targeted by TrueCopy.)

Delete the LU and execute the operation again.

"Fibre" Ports and "Serial" Ports are mixed in the 1CU image on the MCU side.

ESCON connection is used when setting RCU, but a target FLAG is set.

The connection destination CU when setting

RCU is outside the specifiable range.

Confirm the send Port specified on the

MCU side.


The connection destination Port number when setting a Path is outside the specifiable range.

The requested operation is impossible because encryption is disabled.

The requested operation is impossible because encryption is already enabled.

Enable encryption or review the operation.

Review the operation.



1519

1520

1521

1522

1505

1506

1507

1508

1509

Error

Code

1502

1503

1504

1510

1511

1512

1513

1514

1515

1516

1517

1518


Encryption alone cannot be enabled.

The specified server is not registered.

The password cannot be disabled while encryption remains enabled.

The maximum number of servers that can be registered was exceeded.

The maximum number of servers that can be registered is already specified.

The specified server is already registered.

A combination of operations that is not permitted is contained.

You cannot lock because the passwords are different. (The password managed on the SVP side and the password that was sent are different.)

The requested operation is impossible because the password was not enabled at locking.

A lock method that requires a password is already enabled.

The specified password is incorrect. (The password contains a character that cannot be used.)

The conventional lock method is already enabled.

No password was given when specifying a lock operation.

Multiple operations were executed for the same IP address.

Enable the password before enabling encryption.

Review the server to be specified.

Disable the password before disabling encryption.

If any obsolete servers are registered, delete them.

None.

Review the server to be specified.

Review the combination of operations.

Review the passwords.

Change to a lock mode that requires a password or review the operation.

It is not necessary to change to a new lock method.

Review the password, specify a correct password and execute the operation again.

It is not necessary to change to the conventional lock method.

Specify a password when executing the lock operation.

Review the specified IP address and eliminate multiple operations for the same IP address.

Review the IP address to be registered.

The instruction registers an IP address that cannot be defined.

A new password was specified but the specified instruction does not change the password.

The specified password is already being used.

(Another vendor/user is using the same password.)

The specified password is reserved and cannot be used.

No password is specified in the password modification instruction.

No IP address is specified in the IP address addition instruction.

The password cannot be modified.

Review the selected operation.

Modify the password again using a different password.

Specify a new password and modify the password again.

Specify an IP address and add the IP address again.

Unlock and then execute the operation again.



5-11

5-12

Error

Code

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011

2012

2013

2014

2015

2016

2017


A configuration information acquisition request or configuration information setting request was issued without issuing a refresh request.

An attempt to connect during communication between Remote Console and DKC (SVP) failed.

An attempt to read configuration information from DKC (SVP) failed.

An attempt to load the file required for execution failed. (Memory is insufficient or the required file does not exist.)

Memory required for execution could not be acquired.

LUN Manager (PP name: LUNM or LUN

Configuration Manager) required for executing the request has not been installed.

LUSE (PP name: LUNM/LUSE or LUN

Configuration Manager) required for executing the configuration information setting request has not been installed.

LUN Security (PP name: LUN Security or

Secure Manager) required for executing the configuration information setting request has not been installed.

The SVP or DKC microcode cannot execute the request. (The version cannot execute the request.)

An error occurred while checking for a blockage.

A maintenance pre-check error occurred.

Expand memory. Also, confirm that installation of the agent did not fail and that the required files have not been mistakenly deleted.

Quit other programs operating on a SVP

PC or expand memory.

Install the required program product.


Install a version of the microcode that can execute the request.

A Port blockage error occurred.

A download error occurred.

A Port recovery error occurred.


DKC (SVP) or Remote Console is setting configuration information. (Error due to exclusive operation)

Exclusive lock was freed forcibly due to the detection of a timeout during a health check.

Issue a refresh request and then issue a configuration information acquisition request or configuration information setting request.

Contact and consult the maintenance service center.

Confirm that no I/O was generated from a host to the Path/volume.

Confirm the status (not blocked) of DKC.

If the error occurs again, call maintenance personnel.

Confirm the connection status of SVP and

DKC. If the error occurs again, call maintenance personnel.

Wait a while and issue the request again.

Issue the request again. (Execute again from the request for starting the exclusive lock.)



Error Message Error

Code

2018

2019

2020

2021

2031

2032

2033

2034

2037

2082

2100

2101

2102

2103

2104


The open DCR (PP name: Open DCR or Cache

Lun) required for executing the configuration information setting request has not been installed.

The open CVS (PP name: Open CVS or Lun

Manager3) required for executing the configuration information setting request has not been installed.

The Mainframe DCR (PP name: DCR or D.C.R) required for executing the configuration information setting request has not been installed.

The Mainframe CVS (PP name: CVS or C.V.S) required for executing the configuration information setting request has not been installed.


SVP or DKC is under CVS processing.

Wait a while and issue the configuration information setting request again.

Install matching versions of RMC and

DKC or SVP.

Wait a while and issue a refresh request.

The versions of RMC and DKC or SVP do not match.

Busy between DKCs (SVPs).

The configuration inside SVP is being changed.

Port Control (PP name: Prioritized Port

Control) required for executing the configuration information setting request has not been installed.

The size of the mounted cache is different on

CL1 and CL2.

You cannot change because of the host reserve status.

M-VOL or R-VOL contains an error.


The pair status is ineffective.

The pair status of the LUSE is invalid.

The logical Path between MCU and RCU is ineffective.

The pair status does not allow the specified operation.

Confirm the status of DKC. If the error occurs again, call maintenance personnel.

Free the host reserve status and execute the operation again.

1. Issue a refresh request and then confirm the status of M-VOL/R-VOL.

(Check SSB of R-VOL.)

2. M-VOL or R-VOL has a PIN. Confirm the status of the PIN slot and recover the PIN.

3. Confirm that M-VOL is in the following status. (Data copying/accessing collection/blocked/maintenance in progress/READ ONLY)

Issue a refresh request and obtain the information again.

Confirm the pair.

Issue a refresh request and then confirm the status of the Path between the specified MCU and RCU.

Confirm the pair status.



5-13

5-14

2107

2108

2109

2110

2112

2113

Error

Code

2105

2106

2114

2115

2116

2117

2119

2120

2121

2122

2123

2124


The specified volume or another volume in the same group as the specified volume is changing status.

The specified RCU/SSID contains a TrueCopy

Pair. Delete all pairs and execute the operation again.

An error occurred while switching Ports.

Wait a while and execute the operation again.

None.

The specified operation is impossible because the Port type is being changed.

The Port is being initialized.

A logical Path remains in the Port on the MCU or RCU side.

A job remains in the target Port.

Call maintenance personnel (replace

CHA).

Wait a while and execute the operation again.

None.

Issue a refresh request and then issue the request again.

None. An attempt to register a pair/operate pair resume failed. R-VOL must not be T-VOL of

ShadowImage or a Reserve VOL.

An attempt to change a pair option failed. The fence level is not supported on the RCU side/M-VOL is in suspend status.

An attempt to delete a pair failed. (1) C/T group is in CHK status. (2) Volume is in CHK status.

An attempt to terminate the pair operation failed.

The Pair suspend operation failed. Issue a refresh request, confirm the pair status and then issue the request again.

None.

The TrueCopy C/T group is already registered.

The Async option cannot be changed.

The timer type cannot be changed because the specified C/T group also contains an asynchronous pair.

The C/T group is not registered.

An attempt to register the C/T group failed.

The specified C/T group is using MCU. One or more asynchronous pairs exist. A pair in the group is migrating to SIMPLEX.

Operation for changing the C/T group option failed. A pair exists.

R-VOL is being used elsewhere. The operation is impossible.

None.

Confirm the following about R-VOL:

1. Dual copy being used

2. Being used by XRC

3. Being used by PPRC or TC-MF

4. Being used by concurrent copy

5. Reserved



2138

2139

2140

2141

2142

2143

2144

2145

2146

2147

2128

2129

2130

2131

2132

2133

2134

2135

Error

Code

2125

2126

2127

2137

2148


MCU is being used by ShadowImage. The operation is impossible.

M-VOL is being used by XRC. The operation is impossible.

RCU is already being used. The operation is impossible.

The operation was rejected due to the

FREEZE status.

The NCFREEZE command suspended processing. The operation is impossible.

M-VOL is being used by HIHSM. The operation is impossible.

TC-MF and TC both exist in the same C/T group.

The specified R-VOL cannot be recognized from the connection Port.

R-VOL is in intervention request status.

An attempt to change the status of R-VOL failed.

The current number of Paths between MCU and RCU is lower than the specified minimum number of Paths.

The program product TrueCopy, HORCA, or

HORCE is not installed.

None.

Issue a refresh request and confirm the status of R-VOL.

Issue a refresh request and confirm the number of Paths.

The program product Fibre-TrueCopy is not installed in MCU or RCU.

TrueCopy and the multi-platform function have an exclusive relationship.

The controller type of MCU or RCU does not support TrueCopy.

The combination of controller types of MCU and RCU are not supported.

1. Install the required program product.

2. Replace with a supported CHA.


Reduce CHS PCB of MCU before executing the TrueCopy function.

Confirm the device emulation type.

None.

The device emulation type of M-VOL or R-VOL does not support TrueCopy.

RCU does not support remote copy of the extension VOL.

A portion is blocked.

Confirm the device emulation type.

Confirm the control type of RCU and the version of the microcode.

Call maintenance personnel.

DKC contains an error.

The DFW status of R-VOL is invalid.

The cache status of MCU or RCU is ineffective. Issue a refresh request and then confirm the cache status.

Confirm the DFW status of R-VOL. If it is off, set it again. If you cannot set it, call maintenance personnel.

NVS of MCU cannot operate. Confirm the NVS status and issue the request again. If you cannot set it, call maintenance personnel.



5-15

5-16

2154

2155

2156

2157

2158

2159

2160

2161

2162

2163

2164

3000

3001

3002

3003

3004

3005

3006

Error

Code

2149

2150

2151

2152

2153


The serial number or the link address on the

RCU is invalid.

The function is not supported.

The cache of MCU is automatically resetting.

Click [OK] to terminate processing, then wait several minutes and execute the operation again.

The status of M-VOL does not allow operations to be accepted.

An attempt to generate a Path failed.

Review the specification.

Confirm the version of the microcode.

Wait a while and issue the request again.

None.

An error occurred in the target MP.

Initializing during the pre-check.

FOP (Port) is blocked.

A logical Path and R-Vol remain in the target

RCU mixed Port.

An error occurred during the referencing of the remaining R-Vol at the target RCU mixed

Port.

An attempt to switch configuration information for the initiator failed.

An attempt to switch configuration information for the target failed.

An attempt to switch configuration information for the RCU target.

A job remains in the target MCU Port.

A job remains in the target RCU Port.

An attempt to change the Port with the FOP

Path configuration information modification function failed.

An attempt to obtain an external function pointer required by the agent failed.

An attempt to obtain an external function pointer for obtaining trace information failed.

An invalid inter-function interface was detected in the agent.

An internal logical error was detected.

No directory for MIB management information exists.

An attempt to write MIB management information failed.

An error occurred during the accessing of a file required by the agent.

Specify a different Path or delete all pairs on the RCU side and then issue the request again.

Call maintenance personnel. (You must confirm CHA.)

Wait a while and execute a retry.


Execute a retry after the job stops.


Contact and consult the maintenance service center (with trace information).



Error

Code

3007

Error Message

An interface logical error was detected in the agent.




5-17

5-18 Lightning 9900 Messages


Hitachi AMS2000/AMS/WMS/SMS,

Thunder 9500V series, and Thunder

9200 series Messages

This chapter lists and describes the Hitachi Device Manager storage subsystem error messages for Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V, and

Thunder 9200.



Details About Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V, and

Thunder 9200 Messages

Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V series, and Thunder 9200 series Messages 6-1


Details About Hitachi AMS2000/AMS/WMS/SMS, Thunder

9500V, and Thunder 9200 Messages

Some messages displayed by Device Manager contain, as a part of the message, a message output from the storage subsystem. This section lists and describes the error messages from Hitachi AMS2000/AMS/WMS/SMS, Thunder

9500V, and Thunder 9200 that are contained in Hitachi Device Manager messages.

For details on the message IDs that begin with DMEG, see the Storage

Navigator Modular 2 message manual.


Calling the Hitachi



The following table lists and describes the Hitachi AMS2000/AMS/WMS/SMS,

Thunder 9500V, and Thunder 9200 messages that are displayed by Hitachi

Device Manager.

Note: The asterisk "*" indicates that the error code output varies. If a displayed error code does not match any of the codes listed below, see the explanation for the message labeled *.

4

5

Table 6-1 Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V and 9200

Messages

Error

Code

Description

*

1

2

3

6

7

An error has occurred in the subsystem. If you cannot solve this problem, contact the Support Center.

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 retry.

DMEA001005: The number of registered subsystems reached the maximum. Delete unnecessary information, and then retry.

DMEA001021: The number of groups reached the maximum. Specify an already registered group or delete an unnecessary group.

6-2 Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V series, and Thunder 9200 series Messages


105

106

107

108

109

10a

10b

18

101

102

103

104

10c

10d

10e

10f

110

111

112

113

115

116

117

8

Error

Code

10

11

12

Description

DMEA001026: The specified information does not match the configuration of the subsystem. Confirm the configuration information.

DMEA000010: An error occurred while communicating with the subsystem. Confirm the subsystem status and the LAN environment, and then try again.

DMEA000011: An error occurred while communicating with the subsystem. Confirm the subsystem status and the LAN environment, and then try again.

DMEA000012: An error occurred in the secure communication with the subsystem.

Please confirm the certificate, subsystem status and the LAN environment. Then try again.

DMEA001071: The function cannot be executed because the LU has already been reserved.

DMEA001019: The process cannot be performed because the firmware on the subsystem does not support the function.

DMEA001006: Invalid parameter.

DMEA001007: The specified controller is incorrect.

DMEA001008: An attempt to open the file has failed. Confirm the file name, and then try again.

DMEA001009: The contents of the file are invalid. Confirm the file contents, and then try again.

DMEA00100A: An attempt to connect with the server failed. Confirm the registered information and the LAN environment, and then retry.

DMEA00100B: The password is not specified.

DMEA00100C: The password is corrupted. Delete the password file, and then retry.

DMEA001017: An error occurred during the file I/O. Check the permissions and available space.

DMEA001022: A hardware error occurred. Confirm the subsystem.

DMEA001023: Processing is not possible because the current subsystem does not support the function.

DMEA001024: The 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 retry.

DMEA001027: The JRE version in use is not supported. Confirm the JRE version.

DMEA001029: Environment variable: STONAVM_HOME is not set correctly. Check the STONAVM_HOME.

DMEA00104E: Processing failed because the function is disabled.

DMEA00104D: The password length is invalid. Use 12 or fewer characters.

DMEA00104F: An attempt to obtain the controller failure dump information failed.

Retry after 10 minutes.

DMEA001070: This program is not installed correctly.

DMEA001073: An attempt to create a log directory failed. Confirm the execution environment.

DMEA001078: The specified key was not found. Confirm the file, and then retry.

DMEA001079: This function cannot be used for the specified device.



11e

11f

130

201

301

302

303

304

305

Error

Code

118

119

11a

11b

11c

11d

306

307

308

400

401

402

403

404

405

406

407

408

409

40a

Description

DMEA001080: The LU mapping cannot be set when the mapping mode is off.

DMEA001081: An attempt to obtain drive information failed.

DMEA001092: An illegal option is set.

DMEA001093: The function cannot be used because it is not installed, locked, or disabled.

DMEA001132: An attempt to create a file has failed. Confirm the execution environment.

DMEA001133: The file cannot be output because the attempt to acquire performance statistics has failed.

DMEA00102A: The JRE (Java Runtime Environment) version in use is not supported.

Check the JRE version.

DMEA00102B: Processing is not possible because the current controller in charge of the specified LU is different. Retry from the current controller of the LU.

DMEA00112B: The specified port is not available because it has not been physically installed. Confirm the port status, and then retry the operation.

DMEA000201: The specified user ID or password is incorrect.

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 retry.

DMEA001130: The specified RAID group is already defined. Specify an undefined

RAID group.

DMEA001131: The specified RAID group is undefined. Specify a defined RAID group.

DMEA00115E: Processing is not possible because there is no free area in the specified RAID group.

DMEA001160: The logical unit cannot be defined in the specified area.

DMEA001161: Processing is not possible because the logical unit is already defined in the first area of the specified RAID group.

DMEA001162: Processing cannot be performed because the specified area is not available.

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.



415

416

417

418

419

41a

41b

41c

41d

41e

411

412

413

414

Error

Code

40b

40c

40d

40e

40f

410

425

426

427

428

429

440

420

421

422

423

424

Description

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.

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.

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 CommonInformation or the item name is invalid.

DMEA001089: Failed to set up a Mapping Mode. Confirm the setting file, and then retry.

DMEA001090: The CTL Header is invalid.

DMEA001091: The PORT Header is invalid.

DMEA001082: The parameter for Additional Battery Unit Mode or the item name is invalid.

DMEA00119F: There is no file version.



50a

50b

50c

50d

50e

510

504

505

506

507

508

509

Error

Code

446

447

448

449

44a

501

441

442

443

444

445

502

503

511

512

Description

DMEA0011A0: There is no start separator.

DMEA0011A1: The user name is invalid.

DMEA0011A2: The secret is invalid.

DMEA0011A3: The alias is invalid.

DMEA0011A4: The target number is invalid.

DMEA0011A5: There is no end separator.

DMEA0011A6: There is no port separator.

DMEA0011AC: The file version is invalid.

DMEA0011AD: The user name reach the maximum.

DMEA0011AE: The target is undefined.

DMEA001094: The specified host group is already defined. Confirm the name or number, and specify a undefined 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 to disable. Set the host group security to enable, and then retry.

DMEA001097: The function cannot be executed because host group 0 is specified.

Specify other than host group 0, and then retry.

DMEA001098: The specified host group name or WWN name is invalid. Confirm the name and then retry.

DMEA001099: The specified host group number is invalid. Confirm the number, and then retry.

DMEA001100: The specified node name is invalid. Confirm the name, and then retry.

DMEA001101: The specified port name is invalid. Confirm the name, and then retry.

DMEA001102: The parameter for LUNManagementInformation or the item name is invalid.

DMEA001103: The same host group name exists in a port. Confirm the setting file, and then retry.

DMEA001104: The same WWN name exists in a port. Confirm the setting file, and then retry.

DMEA001105: The same port name exists in a port. Confirm the setting file, and then retry.

DMEA001106: The same host group number exists in a port. Confirm the setting file, and then retry.

DMEA001107: The information on 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 retry.

DMEA001109: In the installed firmware revision, a setup of the Read Frame Min 128

Byte Mode cannot be performed. Please update to the firmware which can set up the

Read Frame Min 128 Byte Mode.

DMEA00110D: A parameter for Options or item name is invalid.

DMEA00110E: Processing cannot be performed because the specified RAID level is not supported.



532

533

534

535

536

540

51d

51e

51f

520

521

522

523

530

Error

Code

513

514

515

516

517

518

519

51a

51b

51c

541

542

Description

DMEA00110F: The configuration data of the system LU is invalid.

DMEA001110: The configuration data of the user LU is invalid.

DMEA001195: The parameter or item name for the port is invalid.

DMEA001197: The parameter or item name for iSCSIPortInformation is invalid.

DMEA001196: The KeepAliveTimer value is invalid. Check the KeepAliveTimer value, and then try again.

DMEA001198: The parameter or item name for iSNSInformation is invalid.

DMEA001199: The port number is invalid. Check the port number, and then try again.

DMEA00119B: The parameter or item name for TargetInformation is invalid.

DMEA00119A: The target number is invalid. Check the target number, and then try again.

DMEA00119C: The same target number already exists in the port. Check the settings file, and then try again.

DMEA00119D: The parameter or item name for Target Security is invalid.

DMEA00119E: The parameter or item name for Initiator is invalid.

DMEA0011A7: There is no target information for target number 0 in the settings file.

Check the information for target number 0 on each port, and then try again.

DMEA001108: The specified Web Title is invalid. Confirm the Web Title, and then retry.

DMEA00110A: The process cannot be performed because the firmware 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 types are different.

DMEA00112A: The hardware configuration of the subsystem differs from the configuration in the input file. Confirm the subsystem status, and then retry the operation.

DMEA0011A8: The same alias already exists in the port. Check the settings file, and then try again.

DMEA0011A9: The same iSCSI name already exists in the port. Check the settings file, and then try again.

DMEA0011AA: The same initiator name already exists in the port. Check the settings file, and then try again.

DMEA0011AB: The MTU value is invalid. Check the MTU value, and then try again.

DMEA0011AF: The parameter or item name for TargetOption is invalid.

DMEA00112C: In the installed firmware revision, a setup of the

HostSystemConfiguration cannot be performed. Please update to the firmware which can set up the HostSystemConfiguration.

DMEA00112D: The parameter for HostSystemConfiguration or the item name is invalid.

DMEA00112E: Processing is not possible because the attribute is not Read/Write.

Change the attribute to Read/Write, and then retry.



55e

55f

560

562

563

564

565

559

55a

55c

55d

555

556

557

558

Error

Code

543

544

551

552

554

561

Description

DMEA00112F: The retention period cannot be set for the specified LU. Make sure that the LU status is appropriate.

DMEA001134: The validation period cannot be shortened. Specify a value equal to or greater than the current value, and then try again.

DMEA001146: Either the specified path name of the directory for storing the management file is longer than 250 characters, or sufficient memory could not be allocated. Specify the path name using no more than 250 characters, or terminate other programs and then try again.

DMEA001147: An attempt to create the directory for storing the management file has failed. Check the permissions for the directory, as well as its available capacity.

DMEA001148: The specified path name for output of the management file is longer than 250 characters. Specify the path name using no more than 250 characters, and then try again.

DMEA001149: An attempt to write the management file has failed. Check the permissions for the directory, as well as its available capacity.

DMEA00114A: An attempt to open the management file has failed. Check the file name, and then try again.

DMEA00114B: The contents of the management file are invalid. Check the contents of the file, and then try again.

DMEA00114C: The specified path name for the file is longer than 250 characters.

Specify the path name using no more than 250 characters, and then try again.

DMEA00114D: An attempt to write the file has failed. Check the permissions for the directory, as well as its available capacity.

DMEA00114E: An attempt to open the file has failed. Check the file name, and then try again.

DMEA001150: The output time specified for the CSV file is incorrect.

DMEA001151: The specified path name for the CSV file is longer than 250 characters. Specify the path name using no more than 250 characters, and then try again.

DMEA001152: An attempt to write the CSV file has failed. Check the permissions for the directory, as well as its available capacity.

DMEA001153: An attempt to open the CSV file has failed. Check the file name, and then try again.

DMEA001154: Either the specified path name of the directory for storing the CSV file is longer than 250 characters, or sufficient memory could not be allocated. Specify the path name using no more than 250 characters, or terminate other programs and then try again.

DMEA001155: The specified path name for the management file is longer than 250 characters. Specify the path name using no more than 250 characters, and then try again.

DMEA001156: The path name of the file to be deleted exceeds 250 characters.

Specify a path name of 250 characters or less, 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 output number specified for the CSV file is incorrect.

DMEA00115A: An attempt to open the management file has failed. Check the file name, and then try again.



590

591

593

594

600 a01 a02 a03 a04 a05

572

580

581

582

583

584

585

586

587

588

589

Error

Code

567

570

571

58a

58b

Description

DMEA00115B: The contents of the management file are invalid. Check the contents of the file, and then try again.

DMEA00115C: An attempt to connect has failed. Confirm the connection, and then try again.

DMEA00115D: A response was received from a non-array device. Confirm the connection, and then try again.

DMEA001163: The value received from the array device is invalid.

DMEA001164: The specified IP address is invalid. Specify a valid IP address.

DMEA001165: The specified subnet mask is invalid. Specify a valid subnet mask.

DMEA001166: The specified default gateway address is invalid. Specify a valid default gateway address.

DMEA0011B5: The User LAN Parameter header is invalid.

DMEA0011B6: The CTL Parameter header is invalid.

DMEA0011B7: The parameter or item name for User LAN Parameter is invalid.

DMEA0011B8: The Maintenance LAN Parameter header is invalid.

DMEA0011B9: The parameter or the item name for Maintenance LAN Parameter is invalid.

DMEA0011BA: The process cannot be performed because NNC is equipped. Confirm the port type, and then retry the operation.

DMEA0011BB: The process cannot be performed because the DHCP setting is different between the subsystem and input file. Confirm the DHCP setting, and then retry the operation.

DMEA0011BC: The process cannot be performed because the DHCP is enabled.

Disable the DHCP, and then retry the operation.

DMEA0011BD: The process cannot be performed because the User LAN port of subsystem is being used by other applications. Refer to [netstat.X.Y.inf](X:Serial

Number, Y:Date) file in the directory where Navigator is installed, close applications using User LAN port of subsystem, and then try again.

DMEA0011B1: The specified path name for storing the log file is over 255 characters. Specify the path name in 255 characters or fewer, and then try again.

DMEA0011B2: The path name for storing the log file is over 255 characters. Specify the path name in 255 characters or fewer, and then try again.

DMEA0011B3: An attempt to write the log file has failed. Check the permissions and available capacity of the directory.

DMEA0011B4: The internal log is empty.

DMEA001159: The processing cannot be performed because a mapping-guarded LU exists.

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 retry.

DMEA001016: An attempt to start the specified application program failed. Confirm the path to the specified application and the operation environment.



1011

1012

1013

1014

100b

100c

100d

100e

100f

1010

1003

1004

1005

1006

1007

1008

1009

100a a0a b01 b02

1002

Error

Code

a06 a07 a08 a09

Description

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 items reached the maximum. Delete unnecessary information, and then retry.

DMEA001056: E-mail information cannot be saved. Check the permission and available capacity of the install directory.

DMEA001013: An internal program error occurred. Wait for a while and then retry.

If the problem cannot be solved, contact the maintenance personnel.

DMEA001014: The connection type is invalid.

DMEA00000B: An attempt to transfer data failed. Confirm the subsystem status and the LAN environment, and then retry.

DMEA00000C: An attempt to issue the SCSI command failed. Confirm the subsystem status and the LAN environment, and then retry.

DMEA001015: The firmware revision is not supported. Confirm the subsystem status.

DMEA001018: The file in the specified path is incorrect. Specify the correct file path.

DMEA001020: Could not finish replacing the firmware. Please see if there are any alarms or warnings in the subsystem.

DMEA001028: An attempt to restart the subsystem failed.

DMEA001072: The specified path name is over 250 characters.

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 firmware in the specified path does not exist. Please confirm whether the firmware is stored in the path or the specified path is right.

DMEA001077: Failed to create a firmware file directory. Confirm the execution environment.

DMEA00107A: The firmware replacement of the specified controller cannot be performed. Please replace the firmware of the other controller first.

DMEA00107B: The firmware cannot be read. Please check the permission and available capacity of the install directory.

DMEA00107C: The firmware is not read.

DMEA001135: The ENC firmware download and replacement cannot be performed in the single-controller system.

DMEA001136: The directory for storing the ENC firmware cannot be created. Please check the permission of the install directory.

DMEA001137: The ENC firmware cannot be read. Please check the permission and available capacity of the install directory.

DMEA001138: The ENC firmware is not read.

DMEA001139: The ENC firmware of the specified subsystem is not read.



1030

1040

1041

1042

1043

1044

1045

1018

1019

101a

101b

1020

1021

Error

Code

1015

1016

1017

1046

1047

1056

1057

1058

1059

105a

Description

DMEA001140: The ENC firmware in the specified path does not exist. Please confirm whether the ENC firmware is stored in the path or the specified path is right.

DMEA001141: The ENC firmware cannot be read. Please confirm the file and then try again.

DMEA001142: The contents of the ENC firmware are invalid. Please confirm the file and then try again.

DMEA001143: An invalid character was used 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.

DMEA001170: The character length of the serial number is invalid.

DMEA001167: The information cannot be set because the execution environment setting file exceeds 4096 bytes. Check 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: Processing is not possible because the term of the temporary key or emergency key has expired.

DMEA001171: The contents of the license key file are invalid. Check the contents of the file, and then try again.

DMEA001172: The definition line in the license key file is invalid. Check the contents of the file, and then try again.

DMEA001173: Processing cannot be performed because the number of license keys has exceeded 50. Check the contents of the file, and then try again.

DMEA001175: Could not finish replacing the firmware. Please see if there are any alarms or warnings in the subsystem.

DMEA001176: Processing cannot be performed because the NNC has not been installed. Check the NNC status, and then try again.

DMEA001177: The specified NNC cannot perform processing because it is not physically installed or it cannot be connected. Please check the NNC status, and then try again.

DMEA00117F: Processing cannot be performed because a fibre channel port is not physically installed. Check the state of the subsystem, and then try again.

DMEA001180: Processing cannot be performed because the same address has been specified for NTP server 1 and NTP server 2. Specify different addresses, and then try again.

DMEA00117E: The NNC BIOS firmware could not be read. Check whether the installation directory has write permissions and whether there is enough free space.

DMEA00117D: NNC BIOS firmware does not exist in the specified path. Check whether the specified path is correct and whether NNC BIOS firmware is stored in that path.

DMEA00117C: An attempt to create a directory for storing the NNC BIOS firmware has failed. Check whether the installation directory has write permissions.

DMEA00117B: The NNC BIOS firmware has not been read.

DMEA00117A: The contents of the NNC BIOS firmware are invalid. Check the file, and then try again.



1060

1061

1065

1070

1075

1076

1077

1078

1079

1080

1081

1082

1083

1084

2000

2001

2002

2003

2004

Error

Code

105b

105c

1071

1072

Description

DMEA001181: Processing cannot be performed because the controller for the specified NNC has not been registered. Register the controller for the NNC, and then try again.

DMEA001182: Processing cannot be performed because an attempt to connect with the controller for the specified NNC failed. Check the array device status and the connection environment, and then try again.

DMEA001178: The specified external program does not exist. Check whether the external program has been stored.

DMEA001179: An attempt to call the specified external program has failed. Check the set contents and execution environment.

DMEA001183: Processing cannot be performed because a port is invalid or is not physically installed. Check the array device.

DMEA001184: Processing cannot be performed because a connection is not established with the maintenance port. Check the port connection, and then try again.

DMEA001185: Processing cannot be performed because a connection is not established with the management port. Check the port connection, and then try again.

DMEA0011B0: Processing cannot be performed because a fibre channel port and an iSCSI port are not physically installed. Check the port type and the status of the array device, and then try again.

DMEA001186: Processing cannot be performed because the iSCSI port is not physically installed. Check the status of the array device, and then try again.

DMEA001187: The specified target is already defined. Please confirm the name or number, and specify a new target.

DMEA001188: The specified target is not defined. Please confirm the name or number, and specify a defined target.

DMEA001189: The specified processing cannot be performed for Target 0. Specify a target other than Target 0.

DMEA001190: The alias is invalid. Check the alias, and then try again.

DMEA001191: The initiator name is invalid. Check the initiator name, and then try again.

DMEA001192: The iSCSI name is invalid. Check the iSCSI name, and then try again.

DMEA001193: The user name is invalid. Check the user name, and then try again.

DMEA001194: The secret is invalid. Check the secret, and then try again.

DMEA0011BE: Processing cannot be performed because the owner ID is invalid.

Split the pair by using the application that created the pair.

DMEA002000: Rebooting might have failed, because an error occurred while communicating with the subsystem. Please reboot once again.

DMEA002001: The specified password is invalid. Check and, if necessary, revise the password, and then try again.

DMEA002002: Processing cannot be performed because the account is disabled.

Check and, if necessary, revise the account status, and then try again.

DMEA002003: The process cannot be performed because the number of mapping for this port will reach the maximum. Delete unnecessary mapping and try again.

DMEA002004: The specified group does not exist. Specify a exist group.



200f

2010

2011

2012

2013

2009

200a

200b

200c

Error

Code

2005

2006

2007

2008

200d

200e

2014

2015

2016

2017

2018

2019

201a

Description

DMEA002005: The specified pair is not defined. Specify a defined pair.

DMEA002006: The specified pair is not defined in the specified group. Please confirm the pair definition and try again.

DMEA002007: The specified pair is not defined or is not P-VOL in the self subsystem. When a pair is defined, please try again by connected subsystem.

DMEA002008: The invalid character is specified in group name. Confirm the group name.

DMEA002009: The invalid character is specified in pair name. Confirm the pair name.

DMEA00200A: The invalid character is specified in split string. Confirm the split string.

DMEA00200B: The specified group does not have the pair. Specify a exist group.

DMEA00200C: The requested operation cannot be finished. Confirm the subsystem status and the LAN environment, and then try again.

DMEA00200D: The specified pair is not defined or is not S-VOL in the self subsystem. When a pair is defined, please try again by connected subsystem.

DMEA00200E: Could not finish replacing the firmware. Confirm the subsystem status and the LAN environment, and then try again only the updating. Please try it again at least three times until complete it normally. If you cannot totally complete it normally, power OFF and then power ON the subsystem.

DMEA00200F: The process cannot be performed because the pair attribute that cannot operate. Please confirm the pair definition and try again.

DMEA002010: The process cannot be performed because the pair attribute that cannot operate. Please confirm the pair definition and try again.

DMEA002011: The process cannot be performed because the certificate file size is invalid. Please confirm the certificate file size and try again.

DMEA002012: The process cannot be performed because the specified battery count is outside the effective range. Please confirm the battery count.

DMEA002013: The initialization of configuration information might have failed, because an error occurred in the communication with the subsystem. Please initialize configuration information once again.

DMEA002014: Failed to initialization of configuration information.

DMEA002015: The subsystem cannot initialize configuration information.

DMEA002016: The process cannot be performed because the connection with controller 0 failed. Confirm the subsystem status and the LAN environment, and then try again.

DMEA002017: The process cannot be performed because the connection with controller 1 failed. Confirm the subsystem status and the LAN environment, and then try again.

DMEA002018: The registered information does not match the status of the subsystem. Correct the information to match the status of the subsystem and then try again.

DMEA002019: The specified IP address is incorrect, or it failed in the name resolution of the host name. Please confirm the connection and then try again.

DMEA00201A: The protocol version of IP address or the host name specified for controller 0 and controller 1 do not match. Please confirm the connection and then try again.



201f

2020

2021

2022

2023

2024

2025

202c

202d fffe ffff

10000

2026

2027

2028

2029

202a

202b

Error

Code

201b

201c

201d

201e

Description

DMEA00201B: The automatic split immediately after the pair creation and the copying from the S-VOL to the P-VOL after the pair creation cannot be specified at a time. Please confirm the operation and try again.

DMEA00201C: The specified IP address is incorrect. Please specify a right IP address.

DMEA00201D: The specified default gateway address is incorrect. Please specify a right default gateway address.

DMEA00201E: The automatic split immediately after the pair creation cannot be specified to the pair which belongs to the group. Please confirm the operation and try again.

DMEA00201F: Two or more remote array ID cannot be changed. Please confirm the operation and try again.

DMEA002020: The specified remote path name is not defined. Please specify a defined remote path name.

DMEA002021: The invalid character is specified in remote path name. Please confirm the remote path name.

DMEA002022: The specified serial number or array ID does not exist. Please specify a right serial number or array ID.

DMEA002023: There is no remote array ID for change. Please confirm the operation and try again.

DMEA002024: The process cannot be performed because DC power supply is physically unequipped. Please confirm the subsystem status and try again.

DMEA002025: The process cannot be performed because the number of registered subsystems is over the maximum. Please delete unnecessary information and then try again.

DMEA002026: The process cannot be performed because the specified parameter is not supported. Please confirm the operation and try again.

DMEA002027: The specified file name for storing the CSV file is over 50 characters.

Please specify the file name of 50 or less characters and then try again.

DMEA002028: The specified RAID group is already defined or used by DP pool.

Please specify a new RAID group.

DMEA002029: Built-in account could not be set as an account for error monitoring.

Please specify another user ID.

DMEA00202A: The specified Shared Secret is incorrect. Please confirm the Shared

Secret and try again.

DMEA00202B: The DM-LU cannot be mapped. Confirm the setting file and then try again.

DMEA00202C: The directory does not exist. Please confirm the directory and then try again.

DMEA00202D: The shutdown might have failed, because an error occurred while communicating with the subsystem. Please try again.

DMEA00000E: An internal program error occurred. Wait for a while, and then retry.

If the problem cannot be solved, contact maintenance personnel.

DMEA00000D: Insufficient memory. Terminate other programs, and then retry.

DMEA000001: The Busy status was reported from the subsystem. Retry after waiting for a while.



Error

Code

20000

30000

40000

50000

60000

70000

80000

90000

900001

900002

900003

900004

900005

900006

900007

900008

900009

90000a

90000b

90000c

90000d

90000e

90000f

900010

900011

900012

900013

900014

900015

900016

Description

DMEA000002: The Queue Full status was reported from the array device. Wait a while, and then try again.

DMEA000003: LU0 is reserved by another host. 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 retry.

DMEA000005: An error occurred while communicating with the subsystem. Confirm the subsystem status and the LAN environment, and then retry.

DMEA000006: Failed to connect with the subsystem. Confirm the subsystem status and the LAN environment, and then retry.

DMEA000007: An invalid response was received from the subsystem. Confirm the subsystem status and the LAN environment, and then retry.

DMEA000008: An unexpected error was reported from the subsystem. Retry after waiting for a while.

DMEA00000A: The CHECK CONDITION status was reported from the subsystem, but the details could not be acquired. Retry after waiting for a while.

DMEA900001: There is no file header.

DMEA900002: The contents of the file are invalid. Confirm the file and then try again.

DMEA900003: The file cannot be read. Please confirm the file and then try again.

DMEA900004: The tape group configuration data is invalid. Please confirm the file and then try again.

DMEA900005: The tape group number is invalid.

DMEA900006: The tape group is already defined.

DMEA900007: The same tape group number exists.

DMEA900008: The number of tape groups and the number of generations are different.

DMEA900009: The tape cartridge type is invalid.

DMEA90000A: The specified tape cartridge type is not supported.

DMEA90000B: The number of tape cartridges is invalid.

DMEA90000C: The redundancy is invalid.

DMEA90000D: The node name or the port name is invalid.

DMEA90000E: The specified library does not exist.

DMEA90000F: The secondary library is invalid.

DMEA900010: There is no effective information.

DMEA900011: The process cannot be performed because the current subsystem does not support the function.

DMEA900012: The file path is too long.

DMEA900013: The specified directory does not exist.

DMEA900014: There is no key information.

DMEA900015: This file is not TR constitution backup file.

DMEA900016: The file version is unmatch.



Error

Code

900017

900018

900019

900020

900021

900022

900023

900024

900025

900026

900027

900028

900029

900030

900031

Description

DMEA900017: There is no tape group information.

DMEA900018: The tape group information is invalid.

DMEA900019: The format of strings is invalid.

DMEA900020: The tape group number is doubled.

DMEA900021: The tape group detail information is invalid.

DMEA900022: There is no tape information.

DMEA900023: The tape information is invalid.

DMEA900024: The tape group information is unmatch.

DMEA900025: The value of information is too large.

DMEA900026: The specified file does not exist.

DMEA900027: The file is not specified. Please specify the file and try again.

DMEA900028: There is no LU information.

DMEA900029: The LU information is invalid.

DMEA900030: The value of information is too small.

DMEA900031: The TR constitution information is invalid.



Description Error

Code

1019621

1019625

1019626

1019627

1019628

10196f2

101ea05

1020400

DMES019621: Rebooting is required to apply the setup.

DMES019625: The Account Authentication function was enabled successfully.

DMES019626: The Account Authentication function was disabled successfully.

DMES019627: The Account Authentication function was unlocked successfully.

DMES019628: The Account Authentication function was locked successfully.

DMES0196F2: TR constitution backup or restoration is requested.

DMES01EA05: The firmware has been downloaded to the system drives, but some system drives could not be used. The subsystem can be used.

DMES020400: Processing cannot be performed because the LU is unformatted or currently being formatted. Check the LU status, and then try again.

1020404

1020484

DMES020404: Processing is not possible because it is now formatting. Retry after formatting completes.

DMES020484: Power off in process. Retry when the subsystem is in Ready status.

1029500

1029501

DMES029500: Processing is not possible because the subsystem is being shut down.

Wait a moment and restart the subsystem, and then retry.

DMES029501: The process cannot be performed because the subsystem is in a shutdown state. Please restart the subsystem and then try again.

10296f3

10296f4

1029704

DMES0296F3: The process cannot be performed because the MT library is connecting or not connected. Please confirm the MT library and then try again.

DMES0296F4: The process cannot be performed because the path for the MT library connection is detached. Please confirm the path status and then try again.

DMES029704: The processing cannot be performed because some RAID groups are in low-power mode. Spin up the RAID groups, and then try again.




Code

1033101

1033180

DMES033101: Formatting ended abnormally. Retry after waiting for a while.

DMES033180: The specified LU is unformatted. Specify a formatted LU, and then retry.



Error

Code

1049502

Description

1049504

DMES049502: The requested operation cannot be performed. Confirm that there are no abnormalities in the subsystem.

DMES049504: The process cannot be performed because Switch Array failed. Please confirm the subsystem status and then try again.

1049903

DMES049903: The elimination of PIN data is not completed. Please wait for a while and then try again.

104ea10

104ea11

104eb00

104eb01

104eb02

104eb03

DMES04EA10: An error was detected in firmware downgrade check. Please retry by using another firmware.

DMES04EA11: The specified firmware could not be installed on to the RKL type because the firmware 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.

DMES04EB02: An error occurred during the writing to the floppy disk.

DMES04EB03: The SCSI ID could not be set online due to other controller blockage.



Error

Code

Description

1052500

1052580

1052581

1052583

1052584

1052590

DMES052500: The processing cannot be performed because the LU is either undefined or cannot be recognized from the host.

DMES052580: An attempt to allocate the LU failed. Confirm the specified value.

DMES052581: The RAID group is not defined. Specify an existing RAID group.

DMES052583: The setting is not possible because the setting does not match the conditions of the LU cache resident settings.

DMES052584: The last LBA in the RAID group defined with 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).

1052600 DMES052600: Processing failed due to an invalid parameter. Confirm the specified value.



Error

Code

1052601

Description

1052602

1052604

1055504

DMES052601: Processing failed due to an unsupported parameter. Confirm the specified value.

DMES052602: Processing failed due to an invalid parameter. Confirm the specified value.

DMES052604: Release of Persistent Reservation failed because the type of the

Persistent Reserve command was different.

DMES055504: It is impossible to register over 32 Reservation Keys in an LU.

1059503

1059505

1059510

1059511

1059520

1059521

1059530

1059531

1059532

1059533

1059534

1059535

1059536

1059537

1059540

1059541

1059542

1059543

1059544

1059545

1059546

1059547

1059548

DMES059503: The process cannot be performed because Switch Array failed. Please confirm the subsystem status and then try again.

DMES059505: The process cannot be performed because the controller is detached.

Please recover the controller status and then try again.

DMES059510: The process cannot be performed because the firmware is being replaced.

DMES059511: Processing is not possible because the SVP is being replaced.

DMES059520: The specified function cannot be performed because the subsystem is in an incorrect status for execution. Confirm there are no alarms/warnings in the subsystem, or the configuration is changed.

DMES059521: The change from Dual Active mode to Hot Standby mode and the change from Hot Standby mode to Dual Active mode cannot be performed because of an excessive PIN state. Restore the PIN data, and then retry.

DMES059530: The specified user ID is not registered.

DMES059531: Execution failed because another user is logged in.

DMES059532: The specified user ID is already registered.

DMES059533: Registration failed because 20 users are already registered.

DMES059534: The 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 have not logged in.

DMES059540: A spare disk is defined within the range of the specified RAID group.

Specify the range which does not contain a spare disk.

DMES059541: The drive capacity of the 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 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.



Error

Code

1059549

105954a

105954b

105954c

105954d

105954e

1059550

1059551

1059552

1059554

1059555

1059557

1059558

1059559

105955a

105955b

105955c

105955d

105955e

1059560

1059561

1059562

1059563

1059564

Description

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: Processing is not possible because the target mode is not M-TID,M-

LUN.

DMES05954E: Processing is not possible because the addition of target information is required but changed or deleted information exist.

DMES059550: The function cannot be executed because of write prohibition.

DMES059551: The function cannot be executed because the 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.

DMES059557: LU capacities of the P-VOL and S-VOL are not the same. Check the capacity of the LU.

DMES059558: Processing is not possible because the specified LU is a unified LU, or unified LUs exist.

DMES059559: Processing is not possible because the specified LU is a cache resident 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 the LU is reserved to be changed. Cancel the reservation, and then retry.

DMES05955C: The LU of RAID0 cannot be unified. Specify a LU with a RAID level that is not RAID0.

DMES05955D: The unification cannot be performed because the size of the unified

LU will exceed the maximum.

DMES05955E: The separation cannot be performed because the specified LU is not a unified LU. Specify a unified LU and then retry.

DMES059560: Processing is not possible because the target mode is not M-TID,M-

LUN.

DMES059561: Processing is not possible because the target mode is M-TID,M-LUN, but the target information has already been set.

DMES059562: The unification cannot be performed because the specified subLU is a unified LU. Specify a non-unified LU for subLU, and then retry.

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 subLU. Specify an LU other than LU0 for subLU, and then retry.



Error

Code

1059565

Description

1059566

1059568

1059569

105956a

105956b

1059571

1059572

1059573

1059574

1059575

1059577

105957a

105957b

105957c

105957d

105957e

105957f

1059580

1059590

1059591

DMES059565: The unification cannot be performed because the status of the LU is not normal or degenerated. Specify a LU with a status that is normal or degenerated, and then retry.

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 exist in other RAID groups.

DMES059569: The specified LU cannot be deleted because it is not the last defined

LU.

DMES05956A: The specified LU cannot be defined because LU0 is not yet defined.

Define LU0 first, and then retry.

DMES05956B: The capacity is beyond the limits of supported. Split the unnecessary pairs.

DMES059571: An attempt to set the path failed. Confirm the subsystem and then retry.

DMES059572: An attempt to delete the path failed. Confirm the subsystem and then retry.

DMES059573: An option that cannot be specified at the same time is effective unlocked.

DMES059574: The process cannot be performed because Remote Replication is in progress.

DMES059575: The option cannot be locked or disabled because the path has already been set.

DMES059577: Processing is not possible because the pair creation is in progress.

DMES05957A: The process cannot be performed because the status of pair is suspend. Retry after solving the error.

DMES05957B: The process cannot be performed under 'pair' status. Retry after splitting the pair.

DMES05957C: Processing is not possible because the pair has been created in another subsystem.

DMES05957D: Processing is not possible because the subsystem is in a condition of 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 used in the Fibre Channel subsystem.

DMES059580: The process cannot be performed because the RAID Manager is doing a conflicting process. Wait a moment and then try again.

DMES059590: Processing is not possible because the subsystem is for the exclusive use of 128 LUs.

DMES059591: Processing is not possible because the number of ShadowImage pairs reached the maximum.

1059600

1059601

DMES059600: Processing is not possible. Wait for a while, and then retry.

DMES059601: The specified host group number is valid.



Error

Code

1059602

Description

1059603

1059606

1059607

105960a

1059612

1059615

1059617

105961a

105961d

105961e

105961f

10596f5

10596f6

10596f7

10596f8

10596f9

10596fa

10596fb

10596fc

105ea03

105ea04

105ea10

DMES059602: Processing is not possible because the specified option is not a feebasis option.

DMES059603: Processing is not possible because the specified size of the LU exceeds the maximum LU size.

DMES059606: The specified LU is invalid. Specify a valid LU and then retry.

DMES059607: The function cannot be executed because the pair LU or SnapShot logical unit already exists.

DMES05960A: The function cannot be executed because a logical unit already added to the data pool exists.

DMES059612: Processing is not possible because the specified LU is being quick formatted. Wait until the quick format finishes, and then retry.

DMES059615: Processing is not possible because the specified logical unit is part of a COW Snapshot pair. Cancel the COW Snapshot pair, and then try again.

DMES059617: Processing is not possible because the specified RAID level is not supported. Specify a supported RAID level, and then retry.

DMES05961A: Processing is not possible because parity correction has not finished.

Wait until it finishes, and then retry.

DMES05961D: The RAID group cannot be created because different types of drives are specified. Check the drive types, and then retry.

DMES05961E: One internal LUN cannot be mapped to two or more host LUNs in a port. Check the specified mapping information, and then try again.

DMES05961F: The function cannot be executed because the Hi-Copy pair LU already exists. Cancel the Hi-Copy pair, and then try again.

DMES0596F5: Could not start replacing the micro program because the process is in progress in the MT library. Please retry after process completes.

DMES0596F6: The process cannot be performed because other process is in progress in the MT library. Please retry after process completes.

DMES0596F7: The micro program cannot be downgraded because the LTO4 tape drive exists. Please retry after romoving it or by using another micro program.

DMES0596F8: The micro program cannot be downgraded because LUN Expansion are unlocked. Please retry after locking option or by using another micro program.

DMES0596F9: The micro program cannot be downgraded because ShadowImage are unlocked. Please retry after locking option or by using another micro program.

DMES0596FA: The micro program cannot be downgraded because the LTO4 tape or the LTO4 tape group exists. Please retry after executing the inventory after exporting the tape and deleting the tape group or by using another micro program.

DMES0596FB: The micro program cannot be downgraded because Cartridge Cell

License are unlocked. Please retry after locking option or by using another micro program.

DMES0596FC: The micro program cannot be downgraded because the nonsupported MT library is connected. Please retry after deleting the MT library or by using another micro program.

DMES05EA03: Failed to download the firmware. Please confirm the combination of the specified firmware and the subsystem.

DMES05EA04: Failed to replace the firmware. Confirm the subsystem.

DMES05EA10: An error was detected in firmware downgrade check. Please retry by using another firmware.



Error

Code

105ea12

105ea14

105ea15

105ea16

105ea17

105ea18

105ea19

105ea1a

105ea1b

105ea1c

105ea1d

105ea1e

105ea1f

105ea20

105ea30

105ea31

105ea32

105ea33

105ea34

105ea35

105ea36

Description

DMES05EA12: It is impossible to change from the 128LU version firmware to the

64LU version firmware.

DMES05EA14: The firmware cannot be downgraded because the High-speed

Sequential Write Mode is enabled. Please set the High-speed Sequential Write Mode to disable then try again.

DMES05EA15: The firmware 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 firmware cannot be downgraded on this current spare drive configuration. Please release all spare drives then try again.

DMES05EA17: The firmware cannot be downgraded because the units are intermixed. Please remove the AT units then try again.

DMES05EA18: The firmware 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 firmware 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 firmware does not match to this subsystem. Please retry by using another firmware.

DMES05EA1B: The firmware cannot be downgraded because the RAID group of

RAID6 exists. Please retry after deleting it or by using another firmware.

DMES05EA1C: The firmware cannot be downgraded because the non-supported units are connected. Please retry after removing the units or by using another firmware.

DMES05EA1D: The firmware cannot be downgraded because the non-supported cache is connected. Please retry after removing the cache or by using another firmware.

DMES05EA1E: Execution is not possible because the NNC connected to the specified controller is not shut down. Shut down the NNC, and then retry the operation.

DMES05EA1F: Execution is not possible because the NNC is not shut down. Shut down the NNC, and then retry the operation.

DMES05EA20: The subsystem cannot be restarted.

DMES05EA30: The ENC firmware 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 firmware is being replaced. Please retry after replacement completes.

DMES05EA32: Failed to download the ENC firmware. Please confirm the combination of the specified ENC firmware and the subsystem.

DMES05EA33: The ENC firmware of this revision cannot be downloaded. Please retry by using another ENC firmware.

DMES05EA34: The sum check error of the ENC firmware occurred. Please retry by using another ENC firmware.

DMES05EA35: The ENC firmware is not downloaded. Please try again after downloading.

DMES05EA36: Failed to replace the ENC firmware. Please confirm the subsystem.



Error

Code

105ea40

105ea41

105ea42

105ea43

105ea44

105ea45

105ea46

105ea49

105eb04

Description

DMES05EA40: Processing is not possible because the automatic download is enabled. Disable automatic download, and then try again.

DMES05EA41: The process cannot be performed because the ENC firmware is being replaced. Please retry after replacement completes.

DMES05EA42: The process cannot be performed because the subsystem is under diagnosis process. Please retry after a while.

DMES05EA43: The process cannot be performed because the controller is detached.

Recover the controller status and then try again.

DMES05EA44: The process cannot be performed because the ENC is detached.

Recover the ENC status and then try again.

DMES05EA45: The process cannot be performed in the single-controller system.

Confirm the system configuration.

DMES05EA46: The ENC firmware of this revision cannot be replaced. Please retry by using another ENC firmware.

DMES05EA49: The firmware replacement cannot be performed because the CPU is heavily-loaded. Please wait a moment and then try again.

DMES05EB04: The FDD on the subsystem could not be diagnosed because the FDD is in use.

1062a03

1062a04

1062a05

DMES062A03: For the LU, all Reservation Keys and Persistent Reservations were cleared by the Clear service action of the Persistent Reserve command.

DMES062A04: The registration of the Persistent Reserve command or Register &

Ignore Key service action cleared the Reservation Key and released the Persistent

Reservation.

DMES062A05: Preempt of the Persistent Reserve command or a Preempt & Abort service action cleared the Reservation Key.

1063f01 DMES063F01: The firmware is downloaded.




Code

1079578 DMES079578: Processing is not possible because the data is being copied.

10b9531 DMES0B9531: The execution could not be performed because another user is logged in.

10bda00

10bfd00

10bfd01

3010001

3010002

3010003

3010004

3010005

DMES0BDA00: The process cannot be performed because the drive recovery is in progress. Retry after waiting for a while.

DMES0BFD00: Processing is not possible due to LU replacement. Connect to the controller with owner permission, and then retry.

DMES0BFD01: Processing is suspended due to LU replacement. Retry after waiting for a while.

DMED010001: The same host group name exists in a port. Confirm the host group name, and then retry.

DMED010002: The same WWN name exists in a port. Confirm the WWN name, and then retry.

DMED010003: WWNs cannot be assigned to undefined host groups. Specify a defined host group, and then try again.

DMED010004: The function cannot be executed because the host group security on all ports is set to enabled. Set the host group security to disabled on all ports, and then retry.

DMED010005: Processing cannot be performed because the target security for a port is enabled. Disable the target security for all ports, and then try again.



Error

Code

3010006

Description

3020001

3020002

3020003

3020004

3020005

3020006

3020007

3020008

3020009

302000a

302000b

3020010

3020011

3020012

3020013

3020014

3020015

3030001

3030002

3030003

3030004

3030006

DMED010006: Processing cannot be performed because the specified name is the default name for host group 0. Check the name, and then try again.

DMED020001: The value of the Dirty Data Opportunity is outside the valid range.

Specify a value in the valid range, and then retry.

DMED020002: The value of the Dirty Data Stop Opportunity is outside the valid range. Specify a value in the valid range, and then retry.

DMED020003: The value of the Dirty Data Stop Opportunity is less than or equal to the value of the Dirty Data Opportunity. Specify the value, and then retry.

DMED020004: The value of the Prefetch Starting Opportunity is outside the valid range. Specify a value in the valid range, and then retry.

DMED020005: The LU number is outside the valid range. Specify a LU number in the valid range, and then retry.

DMED020006: The reserved random simple buffer size is outside the valid range.

Specify a value within the effective range, and then retry.

DMED020007: The specification of the Random Simple Buffer Size 0% is incorrect.


DMED020008: Prefetch Count is outside the valid range. Specify a value in the valid range, and then retry.

DMED020009: Prefetch Size is outside the valid range. Specify a value in the valid range, and then retry.

DMED02000A: The specification of the Next Prefetch Opportunity Mode is incorrect.


DMED02000B: Setup is not possible because the Multiple Stream Mode of the system parameters is disabled. Enable the Multiple Stream Mode, and then retry.

DMED020010: The number of sequential judgments is outside the valid range.

Specify a value in the valid range, and then try again.

DMED020011: The base Prefetch size is outside the valid range. Specify a value in the valid range, and then try again.

DMED020012: The fixed Prefetch size is outside the valid range. Specify a value in the valid range, and then try again.

DMED020013: The value of Dirty Data Opportunity is equal to or less than value of

Dirty Data Stop Opportunity. Specify the value and try again.

DMED020014: The process cannot be performed because the specified Load

Balancing value is outside the effective range. Set up an effective value.

DMED020015: The process cannot be performed because the specified Load

Balancing Monitoring Time is outside the effective range. Please set up an effective value.

DMED030001: The specified LU is already invalid. Confirm the LU status, and then retry.

DMED030002: The number of LUs exceeds the maximum number of LUs. Delete unnecessary LUs, and then retry.

DMED030003: The specified LU is not invalid. Specify a invalid LU, and then retry.

DMED030004: The specified LU capacity has exceeded the capacity of the original

LU. Confirm the LU capacity, and then retry.

DMED030006: The specified LU is invalid. Specify a valid LU, and then retry.



Error

Code

3030007

Description

3030008

3030009

303000a

303000b

3040001

3040003

3040004

3040005

3040006

3040007

3040008

3040009

3050001

3050002

3050003

3050004

3050005

3050006

3050007

3050008

3050009

DMED030007: The specified LU is unformatted. Specify a formatted LU, and then retry.

DMED030008: The number of LUs exceeds the maximum. Delete any unnecessary

LUs, and then retry.

DMED030009: Processing is not possible because the specified LU is a cache resident LU or a reserved one. Disable the LU, and then try again.

DMED03000A: The specified LU capacity is less than or equal to the minimum capacity of the LU. Specify a capacity larger than the minimum of the LU, and retry.

DMED03000B: Processing cannot be performed because the access level has been set. Change the attribute to Read/Write, enable the S-VOL mode, and then try again.

DMED040001: The specified LUs contain a subLU. Confirm the LU status, and then retry.

DMED040003: The specified LUs contain a regressed or detached LU. Confirm the LU status, and then retry.

DMED040004: The specified LUs contain an un-mounted drive. Confirm the drive status, and then retry.

DMED040005: The specified LUs contain an invalid LU. Confirm the LU status, and then retry.

DMED040006: Someone is already logged in. Set the password protection function to disabled, and then retry.

DMED040007: There is no LU with an entry of format.

DMED040008: Format of the logical unit cannot be performed under drive blockage mode. Turn off the drive blockade mode system parameter.

DMED040009: Processing cannot be performed because the access level has been set. Change the attribute to Read/Write, enable the S-VOL mode, and then try again.

DMED050001: Processing cannot be executed because the specified LU has a PIN or there are too many PINs. Restore the PIN data, and then try again.

DMED050002: Processing is not possible because the cache segment is insufficient.

Wait for a while, and then try again.

DMED050003: Processing cannot be performed because the specified LU is continuously receiving write commands from the host, or the subsystem is running under a high load. Please wait a while, and then try again.


DMED050005: Processing is not possible because a partition with the necessary conditions for LU switching does not exist. Confirm the partition definition, and then try again.

DMED050006: Processing cannot be performed because the specified logical unit is reserved for cache partition modification. Change the cache partition, and then try again.

DMED050007: Processing is not possible because the LU is being switched. Wait for a while, and then try again.

DMED050008: Processing is not possible because the LU is being switched. Wait for a while, and then try again.

DMED050009: The LU switching could not be performed.



Error

Code

305000a

Description

305000b

305000c

305000d

305000e

305000f

3050010

3050011

3050012

3070001

3070002

3070004

3070005

3070006

3070007

3070008

3070009

DMED05000A: Processing is not possible because the controller is blocked. Recover the controller status, and then try again.

DMED05000B: The process cannot be performed because the controller of LU partition does not match or the partition number of LU is not same. Specify the LU which uses the same controller's partition, or the same partition. When the partition of a LU is set as 0 or 1, set a pair partition as auto.

DMED05000C: An internal program error occurred. Wait for a while and then try again. If the problem cannot be solved, contact the maintenance personnel.

DMED05000D: The time out occurred by the LU changing during controller recovery.

Please wait for a while and then try again.

DMED05000E: The process cannot be performed because Remote Replication is in progress. Please retry after replacement completes.

DMED05000F: The operation to change the controllers that control logical unit cannot be performed because the status of the ShadowImage pair that the specified logical unit is a part of or the ShadowImage pairs that share the same P-VOL is

Synchronizing or Reverse Synchronizing. Please execute the operation when the status of all the pairs is changed to Split, Paired or Failure.

DMED050010: The operation to change the controllers that controls logical unit cannot be performed because the specified logical unit is a part of a Volume

Migration pair and its pair status is Synchronizing. Please execute the operation when the pair status is not Synchronizing.

DMED050011: The operation to change the controllers that controls logical unit cannot be performed because Auto Migration is in progress. Please execute the operation after Auto Migration is completed.

DMED050012: The operation to change the controllers that control logical unit cannot be performed because the status of the ShadowImage pair that the specified logical unit is a part of or the ShadowImage pairs that share the same P-VOL is

Synchronizing, Reverse Synchronizing, Split Pending or Paired Internally

Synchronizing. Please execute the operation when the status of all the pairs is changed to Split, Paired or Failure.

DMED070001: The dual ID success cannot be set because either the number of host interface boards or interface board types are different between the controllers.

Confirm the interface boards status, and then retry.

DMED070002: The specified IP address is incorrect. Specify a correct IP address.

DMED070004: The High-speed Sequential Write Mode cannot be disabled because process of Write command from the hosts is not completed. Wait for a while and then try again, or use the system parameter setting with reboot.

DMED070005: The Multiple Stream Mode and the High-speed Sequential Write Mode cannot be specified at the same time.

DMED070006: When a ShadowImage pair with the S-VOL Switch status exists, the

ShadowImage I/O Switch Mode cannot be disabled. Resolve the problem with the pair status, and then try again.

DMED070007: The configuration of the single or dual controller system cannot be changed because Cache Partition Manager is enabled. Lock or disable Cache

Partition Manager, and then try again.

DMED070008: Processing cannot be performed because the specified port number is outside the valid range. Check the port number.

DMED070009: The port number of another controller cannot be set. Check the controller to be set up.



Error

Code

3070010

Description

3070011

3070012

3070013

3070014

3070015

3070016

3080001

3080002

3080003

3080004

3080005

3080006

3080007

3080008

3080009

308000a

308000b

308000c

308000d

308000e

DMED070010: The process cannot be performed because the specified secure port number is outside the effective range. Please confirm the secure port number.

DMED070011: The secure port number of other controller cannot be set up. Please confirm the controller number.

DMED070012: The process cannot be performed because the non-secure port and secure port are same port number. Please set the different port number.

DMED070013: The process cannot be performed because the non-secure port status is changed by the non-secure port. Please retry by the secure port.

DMED070014: The process cannot be performed because the port number and the non-secure port status are changed at the same time. Please confirm the operation and try again.

DMED070015: The process cannot be performed because the non-secure port status of other controller is changed. Please confirm the controller number.

DMED070016: The process cannot be performed because the specified port number is reserved. Please set the unreserved port number.

DMED080001: The data pool cannot be used. Restart the subsystem.

DMED080002: Processing is not possible because a logical unit is being restored.

Wait for a while, and then retry.

DMED080003: Processing is not possible because a logical unit to be added to the data pool is not specified.

DMED080004: Processing is not possible because the same logical unit number has been specified more than twice. Confirm the logical unit number, and then retry.

DMED080005: The specified logical unit number is outside the valid range. Specify a logical unit number within the range, and then retry.

DMED080006: This process cannot be performed. The status of the specified logical unit must be in either normal or regressed state. Please verify the status of the logical unit and try again.

DMED080007: Processing is not possible because the RAID level or HDU combination of the specified logical unit is not supported. Confirm the currently supported RAID levels and the HDU combinations, and then retry.

DMED080008: Processing cannot be performed because the number of LUs in the data pool has reached the maximum. Delete some LUs from the data pool, and then try again.

DMED080009: Processing is not possible because the specified logical unit is a unified LU. Separate the unified LU, and then retry.

DMED08000A: Processing is not possible because the specified logical unit is a part of a ShadowImage pair. Cancel the ShadowImage pair, and then retry.

DMED08000B: The process cannot be performed because the specified logical unit is a part of Remote Replication pair. Cancel the Remote Replication pair and try again.

DMED08000C: Processing is not possible because the specified logical unit is a command device. Cancel the command device, and then retry.

DMED08000D: Processing is not possible because the specified logical unit has been invalidated. Restore the logical unit, and then retry.

DMED08000E: The process cannot be performed because the specified logical unit is a part of SnapShot pair or a SnapShot logical unit. Cancel the SnapShot pair or specify another logical unit and try again.



Error

Code

308000f

Description

3080010

3080012

3080013

3080014

3080015

3080016

3080017

3080018

3080019

308001a

308001b

308001c

308001d

308001e

308001f

3080020

3080021

3080022

3080023

3080024

DMED08000F: The process cannot be performed because the specified logical unit is defined as a SnapShot logical unit. Specify another logical unit and try again.

DMED080010: Processing is not possible because the specified logical unit is added to a data pool. Specify another logical unit, and then retry.

DMED080012: Processing is not possible because the owner controller is different between the specified logical unit and the data pool. Confirm the logical unit owner controller, and then retry.

DMED080013: Processing is not possible because the specified logical unit has been receiving the Write command continuously from the hosts. Wait for a while, and then retry.

DMED080014: Processing is not possible because other logical unit is changing the

Default Controller. Wait for a while, and then retry.

DMED080015: Processing is not possible because the specified logical unit is in the

PIN exceeded state. Restore PIN data, and then retry.

DMED080016: Processing is not possible because the specified logical unit is not enough for sufficient cache blocks. Specify another logical unit, and then retry.

DMED080017: Processing is not possible because no logical unit exists in the data pool.

DMED080018: Processing is not possible because the COW Snapshot pair exists in the specified data pool. Cancel the COW Snapshot pair, and then try again.

DMED080019: Processing is not possible because the data pool to be deleted is not specified.

DMED08001A: Processing is not possible because the threshold of the usage rate in the data pool is not specified.

DMED08001B: The specified threshold is outside the valid range. Specify a value in the valid range, and then retry.

DMED08001C: Processing is not possible because the specified logical unit has capacity equal to or less than 2GB. Specify the logical unit with a capacity larger than 2GB, and then retry.

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.

DMED08001E: Processing is not possible because quick formatting is now running.

Retry after the quick formatting is completed.

DMED08001F: The number of specified logical units is over 64. Specify 64 or fewer logical units.

DMED080020: Processing is not possible because the drive types of the specified logical unit and data pool are different. Check the drive types, and then retry.



DMED080023: The logical units Unit0 and Unit1, as well as those thereafter, cannot be mixed into the data pool.

DMED080024: Processing is not possible because a DM-LU is not defined. Define a

DM-LU, and then try again.



Error

Code

3080025

Description

3080026

3080027

3090001

3090003

3090004

3090005

3090006

3090007

3090008

3090009

309000a

309000b

309000c

309000d

309000e

309000f

3090010

3090011

3090012

DMED080025: Processing is not possible because the specified logical unit is reserved for cache partition modification. Specify another logical unit, and then try again.

DMED080026: The process cannot be performed because the number of logical units reached the system maximum. Please delete logical units in the data pool and try again.

DMED080027: The process cannot be performed because the number of logical units will reach the system maximum. Please delete logical units in the data pool and try again.

DMED090001: The logical unit number of the specified P-VOL is outside the valid range. Specify a logical unit number within the effective range, and then retry.

DMED090003: The logical unit number of specified SnapShot logical unit 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 logical unit created or deleted is not specified.

DMED090005: The process cannot be performed because the same logical unit number has been specified as a SnapShot logical unit more than twice. Confirm the logical unit number and try again.

DMED090006: Processing is not possible because the specified logical unit of the P-

VOL is neither in normal nor in regressed state. Specify a logical unit in the normal or regressed state, and then retry.

DMED090007: Processing is not possible because no logical unit exists in the data pool of the controller system of the specified P-VOL. Add a logical unit to the data pool, and then retry.

DMED090008: Processing is not possible because the RAID level of the specified P-

VOL or HDU combination is not supported. Confirm the currently supported RAID levels and the HDU combinations, and then retry.

DMED090009: The process cannot be performed because the number of created

SnapShot logical unit for the specified P-VOL has reached its maximum. Delete unnecessary SnapShot logical unit and try again.

DMED09000A: The logical unit number has already been defined. Specify a new number.

DMED09000B: Processing is not possible because the specified P-VOL is a unified

LU. Separate the unified LU, and then retry.

DMED09000C: Processing is not possible because the specified P-VOL is a part of a

ShadowImage pair. Cancel the ShadowImage pair, and then retry.

DMED09000D: The process cannot be performed because the specified P-VOL is a part of Remote Replication pair. Cancel the Remote Replication pair and try again.

DMED09000E: Processing is not possible because the specified P-VOL is part of a

COW Snapshot pair. Cancel the COW Snapshot pair, and then try again.

DMED09000F: Processing is not possible because the specified P-VOL is a command device. Cancel the command device, and then retry.

DMED090010: Processing is not possible because the specified P-VOL is invalid.

Restore the LU, and then retry.

DMED090011: Processing is not possible because the specified P-VOL has already been added to a data pool. Specify another LU number, and then retry.

DMED090012: Processing is not possible because the specified P-VOL cannot get sufficient cache capacity. Make sure there is enough cache capacity, and then retry.



Error

Code

3090013

Description

3090014

3090015

3090016

3090017

3090018

3090019

309001a

309001b

309001c

309001d

309001e

309001f

3090020

3090021

3090022

3090023

3090024

3090025

3090026

30a0001

DMED090013: Processing is not possible because the HDU combination of the specified P-VOL differs from registered logical units in the data pool. Confirm the

HDU combination, and then retry.

DMED090014: Processing is not possible because the specified P-VOL has been receiving the Write command continuously from the hosts. Wait for a while, and then retry.

DMED090015: Processing is not possible because another logical unit is changing the Default Controller. Wait for a while, and then retry.

DMED090016: Processing is not possible because the specified P-VOL is in the PIN exceeded state. Restore the PIN data, and then retry.

DMED090017: Processing is not possible because the specified P-VOL is not defined.

Specify a defined logical unit, and then retry.

DMED090018: The process cannot be performed because the specified SnapShot logical unit has been creating the pair. Cancel the SnapShot pair and try again.

DMED090019: Processing is not possible because P-VOL is being deleted. Wait for a while, and then retry.

DMED09001A: The process cannot be performed because the specified set of P-VOL and SnapShot logical unit is not a pair. Confirm the pair status and try again.

DMED09001B: Processing is not possible because the number of COW Snapshot pairs reached the maximum. Delete unnecessary COW Snapshot pairs, and then try again.

DMED09001C: Processing is not possible because the unified LU is composed of 17 or more sub logical units. Specify another logical unit, and then retry.

DMED09001D: Processing is not possible because the unified LU contains a sub logical unit with a size less than 1GB.

DMED09001E: Processing is not possible because the management area of the COW

Snapshot is insufficient. Delete unnecessary COW Snapshot pair(s), and then try again.

DMED09001F: Processing is not possible because the drive types of the specified logical unit and V-VOL are different. Check the drive types, and then retry.



DMED090022: The process cannot be performed because the specified SnapShot logical unit is a part of Remote Replication pair. Cancel the Remote Replication pair and try again.

DMED090023: The process cannot be performed because the specified SnapShot logical unit 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 logical unit is reserved for cache partition modification. Please retry after cache partition modification is completed.

DMED090025: The process cannot be performed because the specified V-VOL size will exceed the maximum of LU size. Confirm the specified V-VOL size.

DMED090026: The specified LU is not V-VOL. Specify the LU number of V-VOL and try again.

DMED0A0001: Processing is not possible because the specified LU is invalid. Restore the LU, and then retry.



Error

Code

30a0002

Description

30a0003

30a0004

30a0005

30a0006

30a0007

30a0008

30a0009

30a000a

30a000b

30a000c

30a000d

30a000e

30b0001

30c0001

30c0002

30c0003

30c0004

30c0005

30c0006

DMED0A0002: Processing is not possible because the specified LU is a subLU of a unified LU. Separate the unified LU, and then retry.

DMED0A0003: Processing is not possible because the specified LU is a S-VOL of

ShadowImage. Specify another logical unit, and then retry.

DMED0A0004: The process cannot be performed because the specified LU is S-VOL of Remote Replication. Specify another logical unit and try again.

DMED0A0005: The process cannot be performed because the specified LU is

SnapShot logical unit. Specify another logical unit and try again.

DMED0A0006: Processing is not possible during the retention term. Wait for the retention term to expire, and then retry.

DMED0A0007: Processing is not possible because ShadowImage is processing. Wait a moment, and then try again.

DMED0A0008: Processing is not possible because COW Snapshot is processing. 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 permission cannot be changed to Read/Write because an expiration lock is enabled. Disable the expiration lock, and then retry.

DMED0A000B: The process cannot be performed because the status of

ShadowImage pair is not Simplex(SMPL) or Split(PSUS). Please retry after changing the status of pair.

DMED0A000C: The process cannot be performed because the status of Remote

Replication pair is not Simplex(SMPL) or Split(PSUS). Please retry after changing the status of pair.

DMED0A000D: The process cannot be performed because the status of SnapShot pair is not Split(PSUS). Please retry after changing the status of pair.

DMED0A000E: The process cannot be performed because the status of Remote

Replication pair is not Simplex(SMPL) or Split(PSUS). Please retry after changing the status of pair.

DMED0B0001: Processing cannot be executed according to the current access level.

Change the setting to Read/Write, and then enable the S-VOL mode. If the mode has already been set, unlock it by using RAID Manager, and then try again.

DMED0C0001: Processing cannot be executed according to the current access level.


DMED0C0002: Processing cannot be executed according to the current access level.


DMED0C0003: Unification cannot be performed because the drive types are different. Check the drive types, and then retry.

DMED0C0004: The logical units Unit0 and Unit1, as well as those thereafter, cannot be unified.

DMED0C0005: Processing is not possible because the unified LUs reached the maximum.

DMED0C0006: The unification cannot be performed because the cache partition is different. Confirm the cache partition of the specified logical unit.



Error

Code

30c0007

Description

30c0008

30d0001

30d0002

30d0003

30e0001

30e0002

30e0003

30e0004

30e0005

30e0006

30e0007

30e0008

30e0009

30e000a

30e000b

30e000c

30e000d

30e000e

30e000f

30e0010

DMED0C0007: Processing cannot be performed because the specified LU is reserved for cache partition modification. Modify the cache partition, and then try again.

Otherwise, specify a different LU.

DMED0C0008: The total count of Main LU and Sub LU is over the maximum. Please specify 128 or fewer LUs.

DMED0D0001: Processing cannot be executed because ReadOnly or Protect is specified for the access level. Change the setting to Read/Write, and then try again.

DMED0D0002: Processing is not possible because the temporary key cannot be used for the next 180 days after the key is locked or expires.

DMED0D0003: The specified function has already been unlocked.

DMED0E0001: Processing cannot be executed according to the current access level.


DMED0E0002: The process cannot be performed because the unified LU which belongs to two or more RAID groups exists. Please separate the unified LU and try again.

DMED0E0003: The process cannot be performed because the specified LU is a Sub

LU. Specify a Main LU and try again.

DMED0E0004: The process cannot be performed because the LUs number of the specified RAID group reach the maximum. Confirm the RAID group and try again.

DMED0E0005: The process cannot be performed because the specified LU is DM-LU.

Specify another LU and try again.

DMED0E0006: The process cannot be performed because the specified LU is V-VOL of COW Snapshot. Specify the P-VOL and try again.

DMED0E0007: The logical unit number for free area has already been used. Please specify unused logical unit number.

DMED0E0008: The logical unit cannot be created. Please delete unnecessary logical units or specify automatically for free area and then try again.

DMED0E0009: The logical unit of RAID0 cannot be created by multiple free areas.

Please confirm the specified area and then try again.

DMED0E000A: The free area does not exist. Please delete unnecessary logical units and then try again.

DMED0E000B: The capacity of specified area is insufficient or the logical unit number to show the position of the free area is invalid. Please confirm the area and try again.

DMED0E000C: The capacity of specified area is insufficient. Please confirm the capacity and then try again.

DMED0E000D: The logical units are over maximum. Please confirm the specified capacity or area number or delete unnecessary logical units and then try again.

DMED0E000E: The logical units of RAID group are over maximum. Please confirm the specified capacity or area number or delete unnecessary logical units and then try again.

DMED0E000F: The specified area number is outside of the effective range. Please specify the area number within the range and try again.

DMED0E0010: The specified area does not exist. Please confirm the area number and then try again.



Error

Code

30e0011

30e0012

30e0013

30e0014

30e0015

30e0016

30e0017

30e0018

30e0019

30e001a

30e001b

30e001c

30e001d

30e001e

30e001f

30e0020

30e0021

30e0022

30e0023

30e0024

30e0025

Description

DMED0E0011: The logical unit number to show the position of the free area is outside of the effective range. Please specify the logical unit number within the range and then try again.

DMED0E0012: The logical unit number to show the position of the free area is outside of the effective range. Please specify the logical unit number within the range and then try again.

DMED0E0013: The logical unit number to show the position of the free area is not defined. Please specify a defined logical unit and then try again.

DMED0E0014: The logical unit number to show the position of the free area is not defined. Please specify a defined logical unit and then try again.

DMED0E0015: The logical unit number to show the position of the free area is not defined in specified RAID group. Please confirm the logical unit of specified RAID group and then try again.

DMED0E0016: The logical unit number to show the position of the free area is not defined in specified RAID group. Please confirm the logical unit of specified RAID group and then try again.

DMED0E0017: The logical unit number to show the position of the free area is invalid. Please confirm the logical unit and then try again.

DMED0E0018: The specified area is overlapped. Please confirm the area and then try again.

DMED0E0019: The unused area is specified. Please confirm the area and then try again.

DMED0E001A: The unified LU reached the maximum. Please confirm the capacity or area number and then try again.

DMED0E001B: The unified LU reached the maximum. Please confirm the capacity or area number and then try again.

DMED0E001C: The RAID group is invalid. Please confirm the RAID group and then try again.

DMED0E001D: The process cannot be performed because RAID level of specified logical unit is RAID0. Please specify another logical unit and then try again.

DMED0E001E: The capacity of logical unit is over maximum. Please confirm the capacity and then try again.

DMED0E001F: The specified capacity is invalid. Please confirm the capacity and then try again.

DMED0E0020: The unified LU reached the maximum. Please confirm the capacity or area number and then try again.

DMED0E0021: The capacity of specified area is insufficient. Please confirm the capacity and then try again.


DMED0E0023: The quick format size is over maximum value. Please retry after that specified quick format size is decreased or current executed quick format is finished.

DMED0E0024: The logical unit number is not defined. Please specify a defined logical unit and then try again.




Error

Code

30e0026

Description

30e0027

30e0028

30e0029

30e002a

30f0001

30f0002

30f0003

30f0004

30f0005

30f0007

3100001

3100002

3100003

3100004

3100005

3100006

3100007

3100008

DMED0E0026: The specified capacity is over the logical unit capacity. Please confirm the capacity and then try again.

DMED0E0027: The process cannot be performed because the specified logical unit is not normal state. Please recover the status and then try again.

DMED0E0028: The process cannot be performed because the specified logical unit contains an un-mounted drive or a blocked drive. Confirm the drive status and try again.

DMED0E0029: The process cannot be performed because the over provisioning threshold of the specified DP pool is equal to or more than the limit. Please add DP pool capacity and then try again.

DMED0E002A: The process cannot be performed because the over provisioning threshold of the DP pool that has the specified logical unit is equal to or more than the limit. Please add DP pool capacity and then try again.

DMED0F0001: Processing cannot be executed according to the current access level.


DMED0F0002: The processing cannot be performed because the drives of Unit0,

Unit1 and units thereafter are contained within the range of the specified RAID group.

DMED0F0003: The processing cannot be performed because a non-supported drive in this subsystem is contained within the range of the specified RAID group.

DMED0F0004: The specified function cannot be used because the function is locked, disabled or not installed.

DMED0F0005: Processing is not possible because the number of drives is invalid.

Confirm the mounted drive, and then try again.

DMED0F0007: The number of defined RAID groups reached the maximum. Delete unnecessary RAID groups, and then try again.

DMED100001: Processing cannot be executed according to the current access level.


DMED100002: Processing is not possible because the RAID level of the specified logical unit is not supported. Confirm the RAID levels currently supported, and then retry.

DMED100003: Processing is not possible because the specified logical unit is a unified LU. Separate the unified LU, and then retry, or execute online/offline formatting.

DMED100004: Processing is not possible because the specified logical unit is extended and not formatted. Execute online/offline formatting.

DMED100005: The quick format size is over maximum value. Please retry after that specified quick format size is decreased or current executed quick format is finished.

DMED100006: Processing is not possible because the specified logical unit contains an unmounted drive or a blocked drive. Check the drive status, and then retry.

DMED100007: Quick format is not possible when the drive blockage mode is ON in the system parameters. To format, set the drive blockage mode to OFF in the system parameters.

DMED100008: The process cannot be performed because the specified logical unit is not formatted and set the access level other than S-VOL mode. Please change the attribute to Read/Write and try again.



Error

Code

3110001

Description

3110002

3120001

3130001

3130002

3130003

3130004

3130005

3130006

3130007

3130008

3130009

3130010

3130011

3130012

3130013

3130014

3130015

3130016

3130017

3130018

3130019

313001a

DMED110001: The mapping mode cannot be changed because a mapping-guarded

LU exists.

DMED110002: The mapping cannot be changed because a mapping-guarded LU exists.

DMED120001: The specified drive cannot be defined as a spare drive because it is not supported in this subsystem.

DMED130001: The processing cannot be performed because the specified remote path is not set up.

DMED130002: Processing cannot be performed because the specified port is an iSCSI port. Check the port type, and then try again.

DMED130003: Processing cannot be performed because the ports for path0 and path1 are set to the same controller. Please set one of the ports to a different controller, and then try again.

DMED130004: Processing cannot be executed because the specified timeout value is outside the valid range. Revise the value, and then try again.

DMED130005: The process cannot be performed because the specified bandwidth is outside the effective range. Please confirm the bandwidth and try again.

DMED130006: The process cannot be performed because the path status is normal.

Please confirm the status of path.

DMED130007: The process cannot be performed because the path does not exist.

Please setting the path and try again.

DMED130008: The process cannot be performed because the path reconstruction is in progress. Please confirm the status of path and try again.

DMED130009: The process cannot be performed because the path reconstruction is in progress. Please confirm the status of path and try again.

DMED130010: The process cannot be performed because the controller is detached.






DMED130013: The process cannot be performed because the controller is detached.


DMED130014: The process cannot be performed because port are physically unequipped. Please confirm the port type and the subsystem status, and try again.

DMED130015: The process cannot be performed because the specified path is already defined. Please confirm the status of path and try again.

DMED130016: The process cannot be performed because the Hosts is logging out.

Please wait a moment and try again.

DMED130017: The same array ID as a self subsystem is specified. Please specify the array ID of connected subsystem.

DMED130018: The process cannot be performed because the fibre channel port is not equipped. Please confirm the port type and try again.

DMED130019: The process cannot be performed because Remote Replication pair of

Synchronizing or Paired exists. Please confirm the status of pair and try again.

DMED13001A: The process cannot be performed because iSCSI port is physically unequipped. Please confirm the port type and try again.



Error

Code

313001b

Description

313001c

313001d

313001e

313001f

3130020

3130021

3130022

3130023

3130024

3130025

3130026

3130027

3130028

3130029

313002a

313002b

313002c

3140001

3140002

DMED13001B: The process cannot be performed because Distributed Mode is Hub.

Please change Distributed Mode to Edge and try again.

DMED13001C: The process cannot be performed because the remote path or remote port CHAP information (Target information) is defined. Please change Distributed

Mode to Hub and try again.

DMED13001D: The specified array ID is already set. Please specify another array ID.

DMED13001E: The number of defined remote port CHAP information (Target information) reached the maximum. Please delete unnecessary remote port CHAP information (Target information) and try again.

DMED13001F: The number of defined remote path reached the maximum. Please delete unnecessary remote path and try again.

DMED130020: The specified remote path name is already registered. Please specify another remote path name and then try again.

DMED130021: The specified remote array ID cannot be set because Distributed

Mode is Hub. Please change Distributed Mode to Edge, or specify array ID of remote subsystem that Distributed mode is Edge and try again.

DMED130022: The specified array ID does not exist. Please specify a right array ID.

DMED130023: The process cannot be performed because Distributed Mode is not supported. Please confirm the subsystem and try again.

DMED130024: The process cannot be performed because the remote path to two or more are defined. Please delete unnecessary remote path and try again.

DMED130025: The process cannot be performed because the remote port CHAP information (Target information) to two or more is defined. Please delete unnecessary remote port CHAP information (Target information) and try again.

DMED130026: The process cannot be performed because the Remote Replication pair exists to two or more subsystems. Please cancel the Remote Replication pair and try again.

DMED130027: The process cannot be performed because the remote path is defined on the subsystem whose Distributed Mode is not supported. Please delete unnecessary remote path and try again.

DMED130028: The process cannot be performed because the remote port CHAP information (Target information) is defined on the subsystem whose Distributed

Mode is not supported. Please delete unnecessary remote port CHAP information

(Target information) and try again.

DMED130029: The process cannot be performed because Remote Replication pair exists on the subsystem whose Distributed Mode is not supported. Please cancel unnecessary Remote Replication pair and try again.

DMED13002A: The process cannot be performed because the remote path is defined. Please delete remote path and try again.

DMED13002B: The process cannot be performed because the remote port CHAP information (Target information) is defined. Please delete unnecessary remote port

CHAP information (Target information) and try again.

DMED13002C: The process cannot be performed because Distributed Mode is Hub.

Please change Distributed Mode to Edge and try again.

DMED140001: Processing is not possible because the term of the temporary key or emergency key has expired.

DMED140002: Processing is not possible because the DM-LU has already been set.

Cancel the DM-LU, and then try again.



Error

Code

3140003

Description

3140004

3140005

3140006

3140007

3150001

3150004

3150005

3150006

3150007

3150009

315000b

315000c

315000d

315000e

315000f

3150010

3150011

3150012

3150013

3150014

3150015

DMED140003: The process cannot be performed because the specified operation mode is outside the effective range or two or more operation is specified at the same time. Please confirm the operation mode and try again.

DMED140004: The process cannot be performed because DC power supply is physically unequipped. Please confirm the subsystem status and try again.

DMED140005: The function cannot be executed for this subsystem. Please confirm the subsystem.

DMED140006: The process cannot be performed because cache memory size is insufficient. Please increase a larger cache memory and then try again.

DMED140007: The specified value is outside the effective range. Please specify the value in the effective range and try again.

DMED150001: Processing is not possible because the cache partition is not in the initial status. Change the cache partition to the initial status, and then try again.

DMED150004: Processing is not possible because the cache partition is less than the minimum size. Confirm the cache partition size, and then try again.

DMED150005: Processing is not possible because the PIN has overflowed. Restore the PIN data, and then try again.

DMED150006: The segment size of the cache partition (0 or 1) cannot be changed.

DMED150007: The process cannot be performed because ShadowImage is in use.

Cancel the ShadowImage pair and try again.

DMED150009: The process cannot be performed because COW Snapshot is in use.

Cancel the COW Snapshot pair and try again.

DMED15000B: Processing cannot be performed because a segment that is writeincomplete exists. Perform a recovery, and then try again.

DMED15000C: The function cannot be executed because a cache resident LU or a reserved one exists. Disable the LU, and then try again.

DMED15000D: The specified segment size is invalid. Confirm the segment size, and then try again.

DMED15000E: Processing is not possible because the LU is being switched. Wait a moment, and then try again.

DMED15000F: The specified cache partition number is invalid. Confirm the cache partition number, and then try again.

DMED150010: The controller of the current cache partition cannot be changed.

Delete the cache partition, and set up again.

DMED150011: Processing is not possible because the total size of the cache partition exceeds the cache capacity. Confirm the cache partition size, and then try again.

DMED150012: A cache partition for which a LU is set up, or a cache partition of 0 or

1 cannot be deleted. Confirm the cache partition number.

DMED150013: Processing is not possible because the specified cache partition is not defined. Specify a defined cache partition, and then try again.

DMED150014: Processing cannot be performed because the stripe size is not a 64

KB LU. Delete the corresponding LU, and then try again.

DMED150015: The process cannot be performed because the specified logical unit is a part of Remote Replication pair. Please cancel the Remote Replication pair and try again.



Error

Code

3150016

Description

3160002

3160011

3160012

3160013

3160014

3160015

3160016

3160017

3160018

3160019

316001e

316001f

3160020

3160021

3160022

3170001

3170002

3170003

3170004

3170005

DMED150016: The process cannot be performed because the total cache partition capacity using the segment size of 4KB or 8KB is over the system limit. Please confirm the cache partition size or the segment size and try again.

DMED160002: Processing is not possible because the specified logical unit is a sub

LU of the unified LUs. Separate the unified LUs, and then try again.

DMED160011: The logical unit cannot be allocated to the specified cache partition.

Specify another cache partition number, and then try again.

DMED160012: Processing is not possible because the Cache Partition Manager is locked, disabled, or not installed.

DMED160013: The process cannot be performed because the specified logical unit is

SnapShot logical unit. Please specify another logical unit number and try again.

DMED160014: Processing cannot be performed because the specified cache partition is undefined. Check the cache partition, and then try again.

DMED160015: Processing cannot be performed because Cache Partition Manager is locked or disabled. Enable Cache Partition Manager, and then try again.

DMED160016: Processing cannot be performed because the specified cache partition is undefined. Check the cache partition, and then try again.

DMED160017: Processing cannot be performed because the specified cache partition has been set to another controller. Check the cache partition, and then try again.

DMED160018: Processing cannot be performed because the combination of stripe size and segment size is not applicable. Check the stripe size or the cache partition, and then try again.

DMED160019: Processing cannot be performed because the size of the specified cache partition is insufficient. Check the cache partition, and then try again.

DMED16001E: Processing cannot be performed because the pair cache partition and the cache partition are set to the same controller. Check the cache partition, and then try again.

DMED16001F: Processing cannot be performed because the segment sizes are different. Check the segment size of the cache partition, and then try again.

DMED160020: Processing cannot be performed because the size of the specified cache partition is insufficient. Check the cache partition, and then try again.

DMED160021: Processing cannot be performed because the LU is being switched.


DMED160022: Processing cannot be performed because PIN data exists. Restore the

PIN data, and then try again.

DMED170001: Processing is not possible because the specified logical unit is less than 5 GB. Specify a logical unit equal to or more than 5 GB, and then try again.

DMED170002: Processing is not possible because the specified logical unit is RAID level 0. Specify another logical unit, and then try again.

DMED170003: This process cannot be performed. The status of the specified logical unit must be in either normal or regressed state. Please verify the status of the logical unit and try again.

DMED170004: Processing is not possible because the specified logical unit is a unified LU. Separate the unified LU, and then try again.




Error

Code

3170006

Description

3170007

3170008

3170009

3180001

3190001

3190002

3190003

3190004

3190005

3190006

3190007

3190008

3190009

319000b

319000c

319000d

319000e

319000f

3190010

DMED170006: Processing is not possible because the specified logical unit is a command device. Cancel the command device, and then try again.

DMED170007: The process cannot be performed because the specified LU is capacity less than 10GB. Specify the LU is equal to or more than 10GB and try again.

DMED170008: The process cannot be performed because the capacity of DP pool is insufficient. Please wait a moment and then try again. If you cannot set up again, please grow the capacity of DP pool.

DMED170009: The process cannot be set to DM-LU because specified logical unit is mapped. Please delete mapping and then try again.

DMED180001: The specified LU cannot be set as a cache resident LU because the cache partition is not 0 or 1. Try again after changing the cache partition to 0 or 1, or specify a LU with a cache partition of 0 or 1.

DMED190001: An invalid IP address was specified. Specify a correct IP address.

DMED190002: The same IP address as that for the management port cannot be set.

Specify a correct IP address.

DMED190003: Processing cannot be performed because the NNC or array device is processing. Wait a while, and then try again.

DMED190004: The same IP address as that for the maintenance port cannot be set.

Specify a correct IP address.

DMED190005: Processing could not be performed because the controller is blocked.

Recover the controller status, and then try again.

DMED190006: The process cannot be performed because NNC or subsystem is in progress. Please wait a moment and then try again.

DMED190007: Processing cannot be performed because the array device is processing. Wait a while, and then try again.

DMED190008: The same IP address as the NNC management port cannot be set.

Specify a valid IP address.

DMED190009: The maintenance port cannot be changed automatically because the specified network address was the same as the maintenance port while the NNC was connected. Please make sure the specified network address is correct, and then try again.

DMED19000B: The specified host address of the maintenance port is incorrect.

Please specify a correct IP address.

DMED19000C: Processing cannot be performed because the subnet mask set for the management port is incorrect. Please set up a correct subnet mask, and then try again.

DMED19000D: Processing cannot be performed because the default gateway set for the management port is incorrect. Please set up the correct default gateway, and then try again.

DMED19000E: Automatic changing of the DHCP and the maintenance port cannot be specified at the same time. Please make sure the settings are correct, and then try again.

DMED19000F: The specified host address of the management port is incorrect.

Please specify a correct IP address.

DMED190010: Processing cannot be performed because the segments for the management LAN and the default gateway are different. Please specify a correct IP address.



Error

Code

3190011

Description

3190012

3190013

31a0001

31a0002

31a0003

31a0004

31a0005

31a0006

31a0007

31a0008

31a0009

31a000a

31a000b

31a000c

31a000d

31a000e

31a000f

31a0010

31a0020

31a0021

31a0022

31a0023

DMED190011: The process cannot be performed because the maintenance LAN automatic change mode is enabled. Set this mode to disable, and then retry the operation.

DMED190012: The process cannot be performed because subsystem is in progress.

Wait a moment and then try again.

DMED190013: The specified IP address is incorrect. Specify a correct IP address.

DMED1A0001: Processing cannot be performed because the NNC is not connected.

Connect the NNC, and then try again.

DMED1A0002: The specified logical unit is undefined. Specify a defined logical unit.

DMED1A0003: Processing cannot be performed because the specified LU is less than the minimum size required for the system LU. Check the LU size, and then try again.

DMED1A0004: Processing cannot be performed because the specified logical unit is already assigned. Specify a logical unit that is not assigned, and then retry the operation.

DMED1A0005: logical unit is an S-VOL of ShadowImage. Specify another logical unit, and then try again.

DMED1A0006: The process cannot be performed because the specified logical unit is

S-VOL of Remote Replication. Please specify another logical unit and try again.

DMED1A0007: The process cannot be performed because the specified logical unit is defined as a SnapShot logical unit. Please specify another logical unit and try again.

DMED1A0008: Processing cannot be performed because the specified logical unit has been added to a data pool. Specify another logical unit, and then try again.

DMED1A0009: Processing cannot be performed because the specified logical unit is the sub LU of an integrated LU. Specify another logical unit, and then try again.

DMED1A000A: Processing cannot be performed because the specified logical unit is the mapping guard LU. Specify another logical unit, and then retry the operation.

DMED1A000B: Processing cannot be performed because the specified logical unit is a command device. Specify another logical unit, and then try again.

DMED1A000C: The specified logical unit has not been set as a command device.

Specify a logical unit that has already been set as a command device.

DMED1A000D: Processing cannot be performed because the NAS OS is operating.

Check the NAS OS status, and then try again.

DMED1A000E: Processing cannot be performed because the specified logical unit has been set to DM-LU. Specify another logical unit, and then try again.

DMED1A000F: Processing cannot be executed according to the current access level.


DMED1A0010: Processing cannot be performed because all ports are being used by

NAS. Check the port type.

DMED1A0020: Processing cannot be performed because a system LU still exists.

DMED1A0021: Processing cannot be performed because a user LU exists.

DMED1A0022: Processing cannot be performed because the specified LU is a system

LU. Release the system LU, and then try again.

DMED1A0023: Processing cannot be performed because the specified LU is a user

LU. Specify a different LU, and then try again.



Error

Code

31a0024

Description

31a0025

31a0026

31a0027

31a0028

31a0029

31a002a

31a0030

31a0031

31a0032

31a0033

31a0034

31a0070

31a0071

31a0072

31a0073

31a0074

31a0075

31a0076

31a0077

31b0001

31b0002

31b0003

DMED1A0024: Processing cannot be performed because the NAS OS is operating.


DMED1A0025: Processing cannot be performed because the NAS OS is operating.


DMED1A0026: The specified port is being used by NAS. Specify another port.

DMED1A0027: Integration cannot be performed because the stripe sizes are different. Check the stripe size of the LU, and then try again.

DMED1A0028: Processing cannot be performed because the specified LU is a snapshot P-VOL or V-VOL. Specify a different LU, and then try again.

DMED1A0029: The process cannot be performed because the access level is set up.

Change the attribute to Read/Write. When the mode is set up, please reset the mode using RAID Manager. And try again.

DMED1A002A: The process cannot be performed because the specified LU is being used in a ShadowImage pair with more than 2 S-VOLs. Delete all but one S-VOL to make a one-to-one pair, or cancel the pair and then retry the operation.

DMED1A0030: A secondary command device cannot be set for NNCtype1.

DMED1A0031: Work to be stored as dump edit results cannot be set for NNCtype2.

DMED1A0032: A secondary command device cannot be set because a primary command device has not been set. Set the primary command device, and then try again.

DMED1A0033: Command device mapping cannot be released because a secondary command device has been set. Release the secondary command device, and then try again.

DMED1A0034: The processing cannot be performed because the equipped NNC is unknown or because there are multiple NNCs.

DMED1A0070: The backup operation cannot be performed because the NNC is

NNCtype2.

DMED1A0071: The backup operation cannot be performed because the NAS OS is not installed. Install the NAS OS, and then try again.

DMED1A0072: The backup, restore, or clear operation cannot be performed because the controller is blocked. Restore the controller status, and then try again.

DMED1A0073: The backup operation cannot be performed because the NNC has not stopped. Stop the NNC, and then try again.

DMED1A0074: The clear operation cannot be performed because the NNC is

NNCtype1.

DMED1A0075: The restore operation cannot be performed because the system LU has not been backed up.

DMED1A0076: The restore operation cannot be performed because the NNC has not been stopped or blocked.

DMED1A0077: The clear operation cannot be performed because the system LU has not been backed up.

DMED1B0001: An invalid IP address has been specified. Specify a valid IP address.

DMED1B0002: The IP address cannot be changed to the specified IP address.

Specify a valid IP address.

DMED1B0003: Processing cannot be performed because the array device is currently processing. Wait a while, and then try again.



Error

Code

31b0004

Description

31b0005

31b0006

31b0008

31b0009

31b000a

31c0001

31c0002

31c0003

31c0004

31c0005

31c0006

31c0007

31c0008

31c0009

31c000a

31c000b

31c000c

31c000d

31c000e

31c000f

31c0010

DMED1B0004: Processing cannot be performed because the controller is blocked.


DMED1B0005: The specified operation cannot be performed because the DHCP is enabled. Disable the DHCP, and then try again.

DMED1B0006: Processing cannot be performed because the maintenance port is being set. Wait a while, and then try again.

DMED1B0008: The process cannot be performed because the DHCP is enabled.

Disable the DHCP, and then retry the operation.

DMED1B0009: The process cannot be performed because NNC is installed. Confirm the port type, and then retry the operation.

DMED1B000A: The process cannot be performed because the same address is specified as the maintenance LAN and the management LAN. Specify separate addresses, and then retry the operation.

DMED1C0001: Processing cannot be performed because the iSCSI port is not physically installed. Check the port type, and then try again.

DMED1C0002: Processing cannot be performed because the authentication method has not been specified. Specify the authentication method, and then try again.

DMED1C0003: Processing cannot be performed because the alias format is invalid.

Check the alias, and then try again.

DMED1C0004: Processing cannot be performed because the same alias already exists in the port. Check the alias, and then try again.

DMED1C0005: Processing cannot be performed because the format for the iSCSI name is invalid. Check the iSCSI name, and then try again.

DMED1C0006: Processing cannot be performed because the same iSCSI name already exists in the port. Check the iSCSI name, and then try again.

DMED1C0007: Processing cannot be performed because the specified target is undefined. Check the target, and then try again.

DMED1C0008: Processing cannot be performed because the format for the name is invalid. Check the name, and then try again.

DMED1C0009: Processing cannot be performed because the same name already exists in the port. Check the name, and then try again.

DMED1C000A: Processing cannot be performed because the format for the iSCSI name is invalid. Check the iSCSI name, and then try again.

DMED1C000B: Processing cannot be performed because the same iSCSI name already exists in the port. Check the iSCSI name, and then try again.

DMED1C000C: Processing cannot be performed because the valid period for the temporary key or emergency key has expired.

DMED1C000D: Processing cannot be performed because an invalid character has been specified. Check the user name, and then try again.

DMED1C000E: Processing cannot be performed because an invalid character has been specified. Check the secret, and then try again.

DMED1C000F: Processing cannot be performed because the number of characters specified for the user name is outside the valid range. Check the user name, and then try again.

DMED1C0010: Processing cannot be performed because the number of characters specified for the secret is outside the valid range. Specify the secret using 12 to 32 characters, and then try again.



Error

Code

31c0011

31c0012

31c0013

31c0014

31c0015

31c0017

31c0018

31c0019

31c001a

31c001b

31c001c

31c001d

31c001e

31c001f

31c0020

31c0021

31c0022

31c0023

31c0024

31c0025

31c0026

Description

DMED1C0011: Processing cannot be performed because an invalid IP address has been specified. Specify a valid IP address.

DMED1C0012: Processing cannot be performed because an invalid port number has been specified. Specify a valid port number.

DMED1C0013: Processing cannot be performed because the KeepAliveTimer value is outside the valid range. Specify a value from 30 to 64800 for the KeepAliveTimer value, and then try again.

DMED1C0014: Processing cannot be performed because the port number is invalid.

Specify a valid port number.

DMED1C0015: Processing cannot be performed because the array device is currently processing. Wait a while, and then try again.

DMED1C0017: Processing cannot be performed because the number of characters specified for the iSCSI name is outside the valid range. Check the iSCSI name, and then try again.

DMED1C0018: Processing cannot be performed because an invalid character has been specified. Check the iSCSI name, and then try again.

DMED1C0019: Processing cannot be performed because the number of characters specified for the iSCSI name is outside the valid range. Check the iSCSI name, and then try again.

DMED1C001A: The process cannot be performed because the invalid character is specified. Confirm iSCSI Name and try again.

DMED1C001B: Processing cannot be performed because the controller is blocked.


DMED1C001C: Processing cannot be performed because an invalid IP address has been specified. Specify a valid IP address.

DMED1C001D: Processing cannot be performed because a ping command is currently executing. Wait for it to finish, and then try again.

DMED1C001E: Processing cannot be performed because the an invalid CHAP algorithm has been specified. Specify a valid CHAP algorithm, and then try again.

DMED1C001F: Processing cannot be performed because the number of characters specified for the secret is outside the valid range. Specify the secret using 12 to 32 characters, and then try again.

DMED1C0020: Processing cannot be performed because an invalid character has been specified. Check the secret, and then try again.

DMED1C0021: Processing cannot be performed because an invalid character has been specified. Check the user name, and then try again.

DMED1C0022: Processing cannot be performed because the same user name already exists in the port. Check the user name, and then try again.

DMED1C0023: Processing cannot be performed because the LUN manager is locked or disabled. Enable the LUN manager, and then try again.

DMED1C0024: Processing cannot be performed because the target security is disabled. Enable the target security, and then try again.

DMED1C0025: Processing cannot be performed because the number of characters specified for the alias is outside the valid range. Check the alias, and then try again.

DMED1C0026: Processing cannot be performed because an invalid character has been specified. Check the alias, and then try again.



Error

Code

31c0027

Description

31c0028

31c0029

31c002a

31c002b

31c003a

31c003b

31c003c

31c003d

31c003e

31c003f

31c0040

31c0041

31d0001

31e0001

31e0002

31e0003

31e0010

31e0011

31e0012

31e0013

DMED1C0027: Processing cannot be performed because the number of characters specified for the name is outside the valid range. Check the name, and then try again.

DMED1C0028: Processing cannot be performed because an invalid character has been specified. Check the name, and then try again.

DMED1C0029: Processing cannot be performed because the same user name already exists in the port. Check the user name, and then try again.

DMED1C002A: Processing cannot be performed because the specified target is undefined. Check the target, and then try again.

DMED1C002B: Processing cannot be performed because the target security is disabled. Enable the target security, and then try again.

DMED1C003A: Processing cannot be performed because the target security is disabled. Enable the target security, and then try again.

DMED1C003B: Processing cannot be performed because the specified alias is the default name for Target0. Check the alias, and then try again.

DMED1C003C: Processing cannot be performed because the specified iSCSI name is the default name for Target 0. Check the iSCSI name, and then try again.

DMED1C003D: Processing cannot be performed because the same alias already exists in the port. Check the alias, and then try again.

DMED1C003E: Processing cannot be performed because the same iSCSI name already exists in the port. Check the iSCSI name, and then try again.

DMED1C003F: Processing cannot be performed because the same user name already exists in the port. Check the user name, and then try again.

DMED1C0040: The process cannot be performed because the specified host group or target is outside the valid range. Confirm the host group or target, and then retry the operation.

DMED1C0041: The information cannot be acquired because the iSCSI port is not connected. Connect the port, and then try again.

DMED1D0001: Processing cannot be performed during the SNMP is being changed.


DMED1E0001: Processing cannot be performed because the specified cycle time is outside the valid range. Please specify a time from 30 to 3600, and then try again.

DMED1E0002: The setting cannot be performed because the specified cycle time is less than the minimum value. Please make sure the cycle time is correct, and then try again.

DMED1E0003: The process cannot be performed because the specified Queuing

Inhibition Time is outside the effective range. Please confirm the Queuing Inhibition

Time and try again.

DMED1E0010: The process cannot be performed because the Remote Replication pair exists. Please cancel the Remote Replication pair and try again.

DMED1E0011: The process cannot be performed during the Remote Replication pair deleting. Please wait a moment and then try again.

DMED1E0012: The process cannot be performed because the specified logical unit is a part of Remote Replication pair. Please specify another logical unit and try again.

DMED1E0013: The process cannot be performed because the de-allocation of cache blocks for a COW Snapshot is in progress. Wait a while, and then retry the operation.



Error

Code

31e0014

31e0015

31e0016

31e0017

31f0001

31f0010

31f0011

31f0012

31f0013

31f0014

31f0015

31f0017

31f0018

31f0019

31f001a

31f001b

31f0020

31f0021

31f0022

31f0023

31f0024

Description

DMED1E0014: The process cannot be performed because the subsystem is not restarted after Remote Replication is installed. Please restart the subsystem and then try again.

DMED1E0015: The process cannot be performed because the subsystem is not restarted after Remote Replication or SnapShot is installed. Please restart the subsystem and then try again.

DMED1E0016: The process cannot be performed because the subsystem is not restarted after Remote Replication or SnapShot is de-installed. Please restart the subsystem and then try again.

DMED1E0017: The process cannot be performed because the status of Remote

Replication pair is improper. Please confirm the status of pair and try again.

DMED1F0001: The Spare Drive Operation Mode is fixed and the Applying No Copy

Back Mode on All the Units is enabled. This combination is not possible to specify.

Please confirm the operation and try again.

DMED1F0010: Processing failed due to an invalid parameter. Check and, if necessary, revise the specified value.

DMED1F0011: Processing cannot be performed because the specified IP address is invalid. Check and, if necessary, revise the IP address, and then try again.

DMED1F0012: Processing cannot be performed because the same IP address is specified for Syslog Server 1 and Syslog Server 2. Check and, if necessary, revise the IP addresses, and then try again.


DMED1F0014: Processing cannot be performed because the internal log is disabled.

Enable the internal log, and then try again.

DMED1F0015: Processing cannot be performed because the internal log is being exported. Wait a while, and then try again.

DMED1F0017: Processing cannot be performed because exporting of the log failed.



DMED1F0019: Processing cannot be performed because the internal log is being used. Check and, if necessary, revise the internal log status, and then try again.

DMED1F001A: The process cannot be performed because the same IP address is specified to Syslog Server 1 and Syslog Server 2. Please confirm the IP address and try again.

DMED1F001B: The process cannot be performed because the IPv6 address is specified to Syslog Server. Please confirm the version of the navigator.

DMED1F0020: The number of characters in the user ID does not reach the minimum. Please revise the user ID.

DMED1F0021: An invalid character is specified in the user ID. Check and, if necessary, revise the user ID.

DMED1F0022: The current login session has timed out. Please log in again.

DMED1F0023: You do not have a necessary permission. Contact the Account

Administrator, and make sure you have all necessary permissions.

DMED1F0024: The specified user ID has already been registered. Please specify another user ID.



Error

Code

31f0025

31f0026

31f0027

31f0028

31f0029

31f002a

31f002b

31f002c

31f002d

31f002e

31f002f

31f0030

31f0031

31f0040

31f0041

31f0042

31f0043

31f0044

31f0045

31f0048

Description

31f0032

31f0033

31f0034

DMED1F0025: The specified user ID is not registered. Check and, if necessary, revise the user ID.

DMED1F0026: A role is not assigned. Please assign one or more roles.

DMED1F0027: The process cannot be performed for logged in user.

DMED1F0028: The process cannot be performed for built-in account.

DMED1F0029: You do not have modification permission. Contact the Account

Administrator, and check your permission.

DMED1F002A: The number of concurrently logged-in users has reached the maximum. Wait a while, and then log in.

DMED1F002B: The specified password is incorrect. Please specify the password again.

DMED1F002C: You cannot login because your account is disabled. Contact the account administrator, and confirm your account status.

DMED1F002D: The specified password is incorrect. Check and, if necessary, revise the password.

DMED1F002E: The number of account registrations has reached the maximum.

Delete unnecessary accounts, and then register the account.

DMED1F002F: The length of the specified password is below the minimum. Revise the password.

DMED1F0030: Password protection and Account Authentication cannot be used together.

DMED1F0031: The Account Authentication function cannot be unlocked or enabled because NNC is installed. Change the subsystem into a Fibre or iSCSI configuration, and then try again.

DMED1F0032: The process cannot be performed because the specified session timeout value is outside the effective range. Confirm the session timeout value.

DMED1F0033: The process cannot be performed because TrueCopy Modular

Distributed is installed. Please de-install the option and try again.

DMED1F0034: The specified function can not be installed because the function does not meet a requirement. Please retry after installing or enabling the TrueCopy function.

DMED1F0040: The processing cannot be performed because the temporary or emergency key has expired.

DMED1F0041: The processing cannot be performed because there is a

ShadowImage pair in the specified RAID group.

DMED1F0042: The process cannot be performed because the Remote Replication pair is contained.

DMED1F0043: The process cannot be performed because the Remote Replication pair is contained.

DMED1F0044: The processing cannot be performed because there is a COW

Snapshot pair or a V-VOL in the specified RAID group.

DMED1F0045: The processing cannot be performed because there is a Volume

Migration pair in the specified RAID group.

DMED1F0048: The process cannot be performed because formatting is now occurring. Please try again, after it is completed.



Error

Code

31f0049

31f004a

31f004b

31f004c

31f004d

31f004e

31f0051

31f0052

31f0053

31f0054

31f0055

31f0056

31f0057

31f0058

31f0059

31f005a

31f005b

31f005c

31f0080

Description

31f0081

31f0082

DMED1F0049: The process cannot be performed because parity correction is not completed. Please try again, after it is completed.

DMED1F004A: The processing cannot be performed because there is a data pool in the specified RAID group. Delete the data pool, and then try again.

DMED1F004B: The processing cannot be performed because there is a DM-LU in the specified RAID group. Cancel the DM-LU, and then try again.

DMED1F004C: The processing cannot be performed because there is a command device in the specified RAID group. Cancel the command device, and then try again.

DMED1F004D: The processing cannot be performed because there is a system LU in the specified RAID group. Cancel the system LU, and then try again.

DMED1F004E: The process cannot be performed because the LU change is in progress. Please try again, after it is completed.

DMED1F0051: The processing cannot be performed because there is a system drive in the specified RAID group.

DMED1F0052: The processing cannot be performed because there is an LU in the specified RAID group for which write processing has not completed. Wait until the processing has completed, and then try again.

DMED1F0053: The process cannot be performed because the RAID groups in state of Command Monitoring are existing. Spin up the RAID groups and try again.

DMED1F0054: The processing cannot be performed because RAID groups are in lowpower mode. Spin up the RAID groups, and then try again.

DMED1F0055: The processing cannot be performed because RAID groups are in lowpower mode. Spin up the RAID groups, and then try again.

DMED1F0056: The processing cannot be performed because RAID groups are in lowpower mode. Wait for a while, and then try again.

DMED1F0057: The specified RAID group is not defined. Specify a defined RAID group.

DMED1F0058: The processing cannot be performed because processing to restore the RAID groups is executing. Spin up the RAID groups, and then try again.

DMED1F0059: The processing cannot be performed because the health of the RAID groups is being checked. Spin up the RAID groups, and then try again.

DMED1F005A: The processing cannot be performed because there is a user LU in the specified RAID group. Remove the user LU, and then try again.

DMED1F005B: The processing cannot be performed because there is an SES drive in the specified RAID group.

DMED1F005C: The process cannot be performed because state of Power Saving is in progress. Please retry after progress is completed.

DMED1F0080: The process cannot be performed because the external authentication server 1 is not defined. Please confirm the external authentication server 1 and try again.

DMED1F0081: The process cannot be performed because the external authentication server 2 is not defined and the IP address of the external authentication server 1 is disabled. Please confirm the external authentication server 1 and try again.

DMED1F0082: The process cannot be performed because the external authentication server 1 is not defined and The user whose user authentication is RADIUS exists.

Please change the user authentication to Internal and try again.



Error

Code

31f0083

Description

31f0084

31f0085

31f0086

31f0087

31f0088

31f0089

31f008a

31f008b

31f008c

31f008d

31f008e

31f008f

31f00a0

3200001

3200002

3200003

3200004

3200005

DMED1F0083: The specified IP address is incorrect. Please specify a correct IP address.

DMED1F0084: The authentication classification cannot be RADIUS because the user authentication server 1 is not defined. Please setting the external authentication server 1 as RADIUS and try again.

DMED1F0085: The process cannot be performed because the authentication test with the external authentication server 1 failed. Please confirm the external authentication server 1 setting and the LAN environment, and try again.

DMED1F0086: The process cannot be performed because the character length of password is outside the effective range. Please confirm password and try again.

DMED1F0087: The process cannot be performed because the authentication test with the external authentication server 1 failed. Please confirm the user ID and password, and try again.

DMED1F0088: The process cannot be performed because the authentication test with the external authentication server 2 failed. Please confirm the external authentication server 2 setting and the LAN environment, and try again.

DMED1F0089: The password cannot be changed because the user authentication is

RADIUS. Please change the password of RADIUS server.

DMED1F008A: Cannot login because the user authentication with an external authentication server was time-out. Please confirm the external authentication server setting and the LAN environment, and try again.

DMED1F008B: Cannot login because the user authentication with an external authentication server was time-out. Or the process cannot be performed because the authentication test failed. Please confirm the external authentication server setting and the LAN environment, and try again.

DMED1F008C: Cannot login because the user authentication with an external authentication server was failed. Please confirm the user ID and password, and try again.

DMED1F008D: The process cannot be performed because the authentication test with the external authentication server 2 failed. Please confirm the user ID and password, and try again.

DMED1F008E: The process cannot be performed because the character length of user ID is outside the effective range. Please confirm user ID and try again.

DMED1F008F: The process cannot be performed because the password is not set.

Please specify the password, and try again.

DMED1F00A0: The process cannot be performed because the user is not Built-in account. Please login by Built-in account and try again.

DMED200001: Processing is not possible because cache memory size is 1GB or less.

Increase the cache memory, and then retry.

DMED200002: This function is unsupported in a single-controller configuration. Use the function in a dual-controller configuration.

DMED200003: COW Snapshot cannot be unlocked because Cache Partition Manager is enabled. Unlock or disable Cache Partition Manager, and then try again.

DMED200004: Cache Partition Manager cannot be unlocked because the subsystem was not restarted after COW Snapshot was unlocked. Restart the subsystem, and then try again.

DMED200005: The unlocking or enabling cannot be executed because the cache memory size is too low. Increase the size to above 512MB, and then try again.



Error

Code

3200006

Description

3200011

3200012

3200013

3200014

3200015

3200016

3200017

3200018

3200019

320001a

320001b

320001c

320001d

320001e

320001f

3200020

3200021

3200022

3200023

3200024

DMED200006: The option cannot be installed or enabled because cache memory size is 2GB or less. Please increase the cache memory and then try again.

DMED200011: Processing cannot be executed because the specified LU is not a reserved LU. Specify a reserved LU, and then try again.

DMED200012: Processing cannot be executed because the specified LU is a reserved

LU. Delete the reserved LU or specify another LU, and then try again.

DMED200013: Processing cannot be performed because the specified P-VOL and S-

VOL have different capacities. Specify LUs with the same capacity, and then try again.


VOL have different owner controllers. Specify LUs with the same owner controller, and then try again.

DMED200015: Processing cannot be performed the specified P-VOL and S-VOL have the same LU number. Specify different LU numbers.

DMED200016: The process cannot be performed because the pair reached the maximum. Cancel or split the unnecessary Volume Migration pair, or split the unnecessary ShadowImage pair. And try again.


VOL belong to the same RAID group. Specify LUs that belong to different RAID groups.

DMED200018: The specified pair cannot be cancelled because the pair status is not

"wait" or "copy".

DMED200019: The specified pair cannot be split because the pair status is not

"completed" or "error".

DMED20001A: Processing cannot be performed because the specified P-VOL and S-

VOL are not part of the same pair. Specify a P-VOL and S-VOL that are a pair, and then try again.

DMED20001B: The reserved LU cannot be set because the maximum number of reserved LUs has been reached. Delete any unnecessary reserved LUs, and then try again.

DMED20001C: The specified LU is the S-VOL for a volume migration pair. Specify another LU, and then try again.

DMED20001D: The specified LU is not a reserved LU. Specify a reserved LU, and then try again.

DMED20001E: Processing cannot be executed because the P-VOL or S-VOL of the volume migration pair is included. Cancel the pair, and then try again.

DMED20001F: Processing cannot be executed because the reserved LU is included.

Cancel the reserved LU, and then try again.

DMED200020: The process cannot be performed because the P-VOL or S-VOL of the

Volume Migration pair or the reserve LU is contained. Split the Volume Migration pair or delete the reserve LU and try again.

DMED200021: Processing cannot be performed because the owner ID is invalid.

Cancel the pair by using the application that created the pair.

DMED200022: Processing cannot be performed because the owner ID is invalid.

Split the pair by using the application that created the pair.

DMED200023: The specified owner ID is not supported.

DMED200024: A reserved LU already exists. Delete it, and then try again.



Error

Code

3200025

Description

3200026

3200027

3200028

3200029

320002a

320002b

320002c

320002d

320002e

3200030

3210001

3210010

3210011

3220001

3220002

3220003

3220004

3220005

3220006

3220007

3220008

3220009

DMED200025: A volume migration pair already exists. Stop or cancel the pair, and then try again.

DMED200026: Processing cannot be performed because the specified LU is reserved for cache partition modification. Restart the subsystem and then try again.

DMED200027: Processing cannot be performed because the management area is insufficient. Delete any unnecessary pairs, and then try again.

DMED200028: The specified LU is not the volume migration pair. Specify another

LU, and then try again.

DMED200029: The specified LU is the volume migration pair, and it is currently being copied. Wait until the copying has finished, and then try again.

DMED20002A: The copy speed of the specified pair cannot be changed because the pair is not currently waiting or being copied.

DMED20002B: The specified owner ID is not supported.

DMED20002C: The process cannot be performed because the specified LU is not the

P-VOL or S-VOL of the Volume Migration pair. Specify the P-VOL or S-VOL of the

Volume Migration pair and try again.

DMED20002D: The specified P-VOL and S-VOL belong to same DP pool. Please specify a different DP pool and then try again.

DMED20002E: The capacity of DP pool to which the specified S-VOL belongs is insufficient. Please add DP pool capacity and then try again.

DMED200030: The number of iSCSI connecting hosts exceeds the maximum value that can be unlocked or enabled fee-basis option. Please delete unnecessary hosts and try again.

DMED210001: The process cannot be performed because the mapping information is overlapped within the same host group. Confirm the mapping information.

DMED210010: The process cannot be performed because subsystem is in progress.

Wait a moment and then try again.

DMED210011: The process cannot be performed because E-mail Error Report is enabled. Please set E-mail Error Report to disable and try again.

DMED220001: The process cannot be performed because the specified battery count is outside the effective range. Please confirm the battery count.

DMED220002: The battery count cannot be increased. Please specify the count equal to or less than the current battery count.

DMED220003: The process cannot be performed in the single-controller system.

Please confirm the system configuration.

DMED220004: The new unit cannot be added because the number of units reached the maximum. Please confirm the system configuration.

DMED220005: The process cannot be performed because the controller or ENC is detached. Please recover the status and then try again.

DMED220006: The process cannot be performed because the ENC firmware is being replaced. Please retry after the replacement completes.

DMED220007: The process cannot be performed because the subsystem is under diagnosis process. Please retry after a while.

DMED220008: The process cannot be performed because the unit is being added.

Please retry after the addition of unit completes.

DMED220009: The specified battery count cannot be set. Please specify a right battery count.



Error

Code

3230001

Description

3230002

3230003

3230004

3230005

3230006

3230007

3230008

3230009

3230010

3230011

3230012

3230013

3230014

3230015

3230016

3230017

3230018

3230019

3230020

3230021

3231000

3231001

DMED230001: The process cannot be performed because the migration guard is set up. Please clear the migration guard and try again.

DMED230002: The process cannot be performed because the Migration Status is

Checking. Please confirm the Migration Status and try again.


Preparing to Create Copy. Please confirm the Migration Status and try again.


Creating Copy. Please confirm the Migration Status and try again.


Auto Migration Failed. Please confirm the Migration Status and try again.

DMED230006: The process cannot be performed because the subsystem is executing Auto Migration. Please confirm the Migration Status and try again.





Copy Created. Please confirm the Migration Status and try again.


Switching Array. Please confirm the Migration Status and try again.


Auto Migration Completed. Please confirm the Migration Status and try again.


Switching Array Failed. Please confirm the Migration Status and try again.

DMED230014: The process cannot be performed because the Migration Status is In

Progress. Please confirm the Migration Status and try again.


Completed. Please confirm the Migration Status and try again.


Failed. Please confirm the Migration Status and try again.

DMED230017: The process cannot be performed because the Migration Status is Not

Started. Please confirm the Migration Status and try again.


Creating Copy Failed to Start. Please confirm the Migration Status and try again.

DMED230019: The process cannot be performed because the ENC firmware is being replaced. Please retry after replacement completes.


Preparing. Please confirm the Migration Status and try again.

DMED230021: The process cannot be performed because ShadowImage pair of Split

Pending exists. Please try again when the pair status is not Split Pending.

DMED231000: The process cannot be performed because the subsystem is executing the Auto Migration. Please confirm the Migration Status and try again.

DMED231001: The process cannot be performed because the subsystem is executing the Auto Migration or the addition of unit. Please confirm the Migration

Status while executing Auto Migration and try again.



Error

Code

3231002

3231003

3231004

3231005

3231006

3231007

3231008

3240001

3240002

3240003

3241001

3241002

3241003

3241004

3241005

3241006

3241007

3241008

3241009

324100a

Description

DMED231002: The specified array ID is incorrect. Please specify a right array ID.

DMED231003: The process cannot be performed because formatting is now occurring. Please retry after formatting completes.

DMED231004: The process cannot be performed because the specified interface board type is not equipped. Please confirm the interface board type.

DMED231005: The process cannot be performed because the PIN exceeded state.

Please restore PIN data and try again.

DMED231006: The process cannot be performed because the write uncompleted LU exists. Please recover and then try again.

DMED231007: The process cannot be performed because the DM-LU is not defined.

Please define DM-LU and try again.

DMED231008: The process cannot be performed because the Auto Migration is executing or is failed. Please confirm the Migration Status and try again.

DMED240001: The certificate and the secret key cannot be checked. Please restart the subsystem and then try again.

DMED240002: The process cannot be performed because the certificate is invalid.

Please confirm the certificate and try again.

DMED240003: The process cannot be performed because the secret key is invalid.

Please confirm the certificate and try again.

DMED241001: The process cannot be performed because the RAID group expansion is now occurring. Please retry after expansion is completed. And, the specified operation may not be performed even if the RAID group expansion is completed.

When the RAID group expansion is completed, please retry after waiting 2 minutes or more.

DMED241002: The 'cancel' operation cannot be performed because the RAID group does not execute the expansion. Please confirm the RAID group and then try again.

DMED241003: The 'cancel' operation cannot be performed because the RAID group is executing expansion or has been executed the expansion and waiting. Please confirm the RAID group status and try again.

DMED241004: The 'forcibly cancel' operation cannot be performed because the RAID group does not execute the expansion and waiting. Please specify a 'cancel' operation.

DMED241005: The process cannot be performed because RAID group is RAID0.

Please confirm RAID level and then try again.

DMED241006: The process cannot be performed because the number of parity groups is not 1. Please confirm the RAID group and try again.

DMED241007: The process cannot be performed because the specified drives contain an un-mounted drive or a blocked drive. Please confirm the drive status and try again.

DMED241008: The specified drive is already defined as a spare drive, or is already being used in the RAID group. Please confirm the drive status and try again.

DMED241009: The process cannot be performed because the number of drive is incorrect. Please specify it by an even number, when RAID level is RAID1 or

RAID1+0.

DMED24100A: The process cannot be performed because the number of drive is incorrect. Please specify the number of drives within the range of the combination at the RAID level.



Error

Code

324100b

Description

324100c

324100d

324100e

324100f

3241010

3241011

3241012

3241013

3241014

3241015

3241016

3241017

3241018

3241019

324101a

324101b

3241050

3241051

3250001

3250002

DMED24100B: The process cannot be performed because the drive type of the RAID group is different. Please confirm the drive type and try again.

DMED24100C: The process cannot be performed because the capacity of specified drive is less than the minimum capacity of the RAID group drives. Please confirm the drive capacity and try again.

DMED24100D: The process cannot be performed because ShadowImage pair or

Remote Replication pair is not Simplex or Split, or SnapShot pair is not Simplex or

Paired. Please retry after copy is completed.

DMED24100E: The process cannot be performed because SnapShot pair is not

Paired or Remote Replication pair is not Split. Please retry after copy is completed.

DMED24100F: The process cannot be performed because some logical unit are under quick formatting. Please retry after quick formatting is completed.

DMED241010: The process cannot be performed because some logical unit is under parity correction. Please retry after parity correction is completed.

DMED241011: The process cannot be performed because the write uncompleted LU is contained. Please recover and then try again.

DMED241012: The process cannot be performed because the Volume Migration pair is contained. Please split the pair and try again.

DMED241013: The process cannot be performed because the reserve LU of the

Volume Migration is contained. Please delete the reserve LU and try again.

DMED241014: The process cannot be performed because the Cache Residency LU or a reserved one exists. Please delete the Cache Residency LU and then try again.

DMED241015: The process cannot be performed because the state of Power Saving in RAID group is existing. Please spin up the RAID group and try again.

DMED241016: The process cannot be performed because the LU change is in progress. Please wait for a while and then try again.

DMED241017: The process cannot be performed because the size of LU is over

120TB or the unified LU exists. Please shrink the LU capacity and try again.

DMED241018: The process cannot be performed because the specified RAID group is a LU grow. Please confirm the specified LU status.

DMED241019: The process cannot be performed because the subsystem is not restarted, when Cache Partition Manager and SnapShot or Remote Replication is enabled. Or the process cannot be performed because cache partition modification is reserved. Please restart the subsystem and try again.

DMED24101A: The process cannot be performed because ShadowImage pair of Split

Pending exists. Please try again after status is changed to Split.

DMED24101B: The process cannot be performed because the logical unit in regressed state is contained. Please change the state to normal and try again.

DMED241050: The process cannot be performed because the RAID group expansion is now occurring. Please retry after expansion is completed.

DMED241051: The process cannot be performed because the LU changing occurred by the RAID group expansion. Please retry after expansion is completed.

DMED250001: The specified IP address is incorrect. Please specify a correct IP address.

DMED250002: The specified default gateway address is incorrect. Please specify a right default gateway address.



Error

Code

3250003

Description

3250004

3250005

3250006

3250007

3250008

3250009

325000a

325000b

325000c

325000d

325000e

325000f

3260001

3260002

3260003

3260004

3260005

3260006

DMED250003: The process cannot be performed because the segment is different between the management LAN and default gateway. Please specify a correct IP address.

DMED250004: The process cannot be performed because the specified management

LAN is same address as the linklocal management LAN. Please specify the different address and try again.


LAN is same address as the linklocal maintenance LAN. Please specify the different address and try again.


LAN is same address as the maintenance LAN. Please specify the different address and try again.

DMED250007: The process cannot be performed because the specified maintenance

LAN is same address as the management LAN. Please specify the different address and try again.


LAN is same address as the linklocal management LAN. Please specify the different address and try again.


LAN is same address as the linklocal maintenance LAN. Please specify the different address and try again.

DMED25000A: The process cannot be performed because subsystem is in progress.

Please wait a moment and then try again.

DMED25000B: The process cannot be performed because subsystem is in progress.

Please wait a moment and then try again.

DMED25000C: The specified IP address is incorrect. Please specify a correct IP address.

DMED25000D: The specified IP address is incorrect. Please specify a correct IP address.

DMED25000E: The protocol version (IPv4/IPv6) is different between IP address of subsystem and the specified IP address of mail server. Please confirm the protocol version of the subsystem and try again.

DMED25000F: The protocol version (IPv4/IPv6) is different between IP address of subsystem and the set IP address of mail server. Please confirm the protocol version of the subsystem and try again.

DMED260001: The specified drive is already defined as a spare drive, or is already being used in the RAID group or DP pool. Please confirm the drive status and try again.

DMED260002: The process cannot be performed because the DP pool exists. Please delete the DP pool and try again.

DMED260003: The process cannot be performed because the specified logical unit is a logical unit in the DP pool. Please specify another logical unit and try again.

DMED260004: The process cannot be performed because the subsystem is not restarted after Remote Replication, SnapShot or Dynamic Provisioning is installed or is de-installed. Please restart the subsystem and then try again.

DMED260005: The number of defined logical unit reached the maximum. Please delete unnecessary logical unit and try again.

DMED260006: The process cannot be performed because the specified RAID group is a RAID group in the DP pool. Please confirm the RAID group and try again.



Error

Code

3260007

Description

3260008

3260009

326000a

326000b

326000c

326000d

326000e

326000f

3260010

3260011

3260012

3260013

3260014

3260015

3260016

3260017

3260018

3260019

326001a

326001b

DMED260007: The process cannot be performed because the logical unit which belongs to the DP pool is not normal state. Please recover the status and then try again.

DMED260008: The specified DP pool number has already been defined. Please specify a new number.

DMED260009: The process cannot be performed because the specified RAID level is not supported. Please specify the RAID level currently supported and try again.

DMED26000A: The specified RAID group is already used by DP pool. Please specify a new RAID group.

DMED26000B: The process cannot be performed because the specified DP pool is neither in normal nor in regressed state. Please recover the status and then try again.

DMED26000C: The process cannot be performed because the non-supported drive is mounted. Please replace the drive and then try again.

DMED26000D: The process cannot be performed because the capacity of specified drive is not supported. Please replace the drive currently supported and try again.

DMED26000E: The specified DP pool cannot be deleted. Please specify another DP pool.

DMED26000F: The number of defined RAID group reached the maximum. Please delete unnecessary RAID group and try again.

DMED260010: The process cannot be performed because the subsystem is not restarted after Dynamic Provisioning is installed. Please restart the subsystem and then try again.

DMED260011: The process cannot be performed because combination of the RAID level and the number of drive does not match. Please confirm combination of the

RAID level or the number of drive and try again.

DMED260012: The specified DP pool is not defined. Please specify a defined DP pool and then try again.

DMED260013: The process cannot be performed because the specified DP pool is neither in normal state. Please recover the status and then try again.

DMED260014: The number of drives reach the maximum. Please confirm the number of drives.

DMED260015: The process cannot be performed because the logical unit exists in the DP pool. Please delete the logical unit in the DP pool and then try again.

DMED260016: The process cannot be performed because the drive recovery is in progress. Please retry after drive recovery completes.

DMED260017: The process cannot be performed because the drive firmware is being replaced. Please retry after replacement completes.

DMED260018: The early alert of DP pool consumed capacity alert is equal to or more than the depletion alert. Please confirm the values and try again.

DMED260019: The warning of over provisioning threshold is equal to or more than the limit. Please confirm the values and try again.

DMED26001A: The process cannot be performed because the combination of drive type and drive capacity does not match. Please confirm the drive type or the drive capacity, and try again.

DMED26001B: There is no drive which can be used. Please confirm the number of drives and try again.



Error

Code

326001c

Description

326001d

326001e

326001f

3260020

3260021

3260022

3260023

3260024

3260025

3260026

3260027

3260028

3260029

326002a

326002b

326002c

DMED26001C: The process cannot be performed because specified logical unit is not a logical unit in the DP pool. Please specify an logical unit in the DP pool and then try again.

DMED26001D: The process cannot be performed because cache memory size is 2GB or less. Please increase a larger cache memory than 4GB and then try again.

DMED26001E: The process cannot be performed because cache memory size is 2GB or less. Please increase a larger cache memory than 4GB and then try again.

DMED26001F: The process cannot be performed because the status of DP pool consumed capacity is depletion alert over or capacity depleted. Please confirm the

DP pool consumed capacity and then try again.

DMED260020: The process cannot be performed because the DP pool consumed capacity is not normal state. Please confirm the DP pool consumed capacity and then try again.

DMED260021: The process cannot be performed because the combination of RAID level and number of drives does not match. Please confirm the number of drives and then try again.

DMED260022: The process cannot be performed because different drives are specified. Please confirm the drive type and then try again.

DMED260023: The process cannot be performed because there are some logical units that are not normal or skip state of the parity correction. Please retry after changing to normal state.

DMED260024: The process cannot be performed because the drive type of the DP pool is different. Please confirm the drive type and then try again.

DMED260025: The process cannot be performed because the combination of stripe size and segment size does not match. Please confirm the stripe size or the cache partition and then try again.

DMED260026: The process cannot be performed because the combination of the number of drives and the combination does not match. Please confirm the number of drives and the combination and then try again.

DMED260027: The process cannot be performed because the capacity of DP pool will exceed the maximum. Please delete unnecessary DP pools and then try again.

DMED260028: 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. When the mode is set up, please reset the mode using RAID Manager. And try again.

DMED260029: The process cannot be performed because the DP optimization state of the specified logical unit in DP pool or the logical units in DP pool that has specified logical unit is neither in Normal state nor in Failed state. Please wait for completion of DP optimization or cancel DP optimization and then try again.

DMED26002A: The process cannot be performed because the DP optimization state of logical unit in DP pool is not Normal. Please try again, after DP optimization is completed. When the state of DP optimization is failed, cancel DP optimization and then try again.

DMED26002B: The process cannot be performed because the capacity of DP pool for performing DP optimization is insufficient. Please add capacity of DP pool for performing DP optimization and then try again.

DMED26002C: The process cannot be performed because specified logical unit in DP pool or the logical units in DP pool that has specified logical unit contains the write uncompleted logical unit. Please recover and then try again.



Error

Code

326002d

Description

326002e

326002f

3260030

3260031

3260032

3260033

3260034

3260035

3260036

3260037

3260038

3260039

326003a

3300001

3300002

3300005

3300006

3300007

3300008

DMED26002D: It is not necessary to cancel because DP optimization state of the logical unit in specified DP pool or the logical unit in DP pool containing specified logical unit is already optimizing or canceling.

DMED26002E: The process cannot be performed because DP optimization state of the logical unit in DP pool is not normal. Please confirm DP optimization state of the logical unit in DP pool and then try again.

DMED26002F: The process cannot be performed because specified logical unit in DP pool contains the write uncompleted logical unit. Please recover and then try again.

DMED260030: The process cannot be performed because status of the logical unit in specified DP pool or the logical unit in DP pool containing specified logical unit is neither in Normal state nor in Regression state. Please recover the logical unit and then try again.

DMED260031: The process cannot be performed because ShadowImage pair of

Simplex state exists in specified DP pool. Please release the pair and then try again.

DMED260032: The process cannot be performed because specified logical unit in DP pool or the logical units in DP pool that has specified logical unit is in the PIN exceeded state. Please recover and then try again.

DMED260033: The process cannot be performed because state of the DP pool which contains the specified logical unit is Detached. Please recover and then try again.

DMED260034: The process cannot be performed because status the logical unit in the specified DP pool is in Normal state nor in Regression state. Please recover the logical unit and then try again.

DMED260035: The process cannot be performed because specified logical unit in DP pool is in the PIN exceeded state. Please recover and then try again.

DMED260036: The process cannot be performed because the updating of DP management information is in progress. Please wait a moment and then try again.

DMED260037: The capacity of DP pool to which the specified P-VOL belongs is insufficient. Please add DP pool capacity and then try again.

DMED260038: The process cannot be performed because the subsystem is not restarted after DP capacity mode is changed. Please restart the subsystem and then try again.

DMED260039: The process cannot be performed because the capacity of DP pool will exceed the maximum. Please restart the subsystem and then try again.

DMED26003A: The process cannot be performed because the subsystem is not restarted after Remote Replication, SnapShot or Dynamic Provisioning is installed or is de-installed, or Advanced Security Mode is changed. Please restart the subsystem and then try again.

DMED300001: The serial number or equipment ID cannot be changed because the path information and pair information do not exist.

DMED300002: The serial number or equipment ID cannot be changed because the path information and pair information do not exist.

DMED300005: The specified serial number or equipment ID is incorrect. Specify digits (0-9).

DMED300006: The specified serial number or equipment ID is incorrect. Please specify a right serial number or equipment ID.

DMED300007: The specified serial number or equipment ID is incorrect. Please specify a right serial number or equipment ID.

DMED300008: 0 is specified as 6 figures of low order of the serial number or equipment ID. Please specify a right serial number or equipment ID.



Error

Code

3300009

Description

330000a

330000b

330000c

330000d

330000e

33b0011

33b0012

33b0013

33b0014

33b0015

33b0016

33b0018

33b0019

33b001a

33b001b

33b001c

33b001d

33b001e

33b001f

DMED300009: The same serial number or equipment ID as a self subsystem is specified. Please specify the serial number or equipment ID of connected subsystem.

DMED30000A: The same equipment ID as a self subsystem is specified. Specify the equipment ID of connected subsystem.

DMED30000B: Processing cannot be performed because a fibre channel port has not been installed. Check the port type, and then try again.

DMED30000C: A value differs from current value is specified as 1 figures of high order of the serial number or equipment ID. Please specify a right serial number or equipment ID.

DMED30000D: The process cannot be performed because the specified array ID is not set to Remote Replication pair, remote path or remote port CHAP information

(Target information). Please confirm the array ID and try again.

DMED30000E: The array ID before and behind change is the same. Please specify a right array ID.

DMED3B0011: The firmware cannot be downgraded because the non-supported interface board is equipped on the downgraded version. Please retry by using firmware in relation to this interface board.

DMED3B0012: A downgrade cannot be performed because a segment size of 64 KB or more has been set. Check the cache partition, and then try again.

DMED3B0013: A downgrade cannot be performed because a stripe size of 64 KB or more has been set. Check the stripe size of the LU, and then try again.

DMED3B0014: The firmware cannot be downgraded because Remote Replication is installed. Please change Remote Replication to de-installed and try again.

DMED3B0015: The downgrade cannot be performed because the array device was not restarted after the option using the data pool was unlocked or enabled. Please restart the array device, and then try again.

DMED3B0016: The micro program cannot be downgraded because the target(s) or

CHAP user(s) is not initialized. Initialize the target(s) and CHAP user(s), and then retry the operation.

DMED3B0018: The micro program cannot be downgraded because a pair with an MU number other than 0 exists in a ShadowImage S-VOL. Cancel the pair with an MU number other than 0, and then retry the operation.

DMED3B0019: The firmware cannot be downgraded because the pair with MU number of 14 or more exists in SnapShot logical unit. Please cancel the pair with MU number of 14 or more and try again.

DMED3B001A: The firmware cannot be downgraded because P-VOL with 15 or more

SnapShot logical unit exists. Please delete SnapShot logical unit to 14 or less, and try again.

DMED3B001B: The firmware cannot be downgraded because the user LU is being used as the pair of Remote Replication. Please cancel the pair and try again.

DMED3B001C: The micro program cannot be downgraded because a migrated LU exists. Please migrate the LU again.

DMED3B001D: The downgrade cannot be performed because the volume migration function is unlocked. Lock it, and then try again.

DMED3B001E: The firmware cannot be downgraded because Remote Replication is unlocked. Please lock the option and try again.

DMED3B001F: The downgrade cannot be performed because The Account

Authentication function is unlocked. Lock it, and then try again.



Error

Code

33b0020

Description

33b0021

33b0022

33b0023

33b0100

33b0101

33b0102

33b0103

33b0104

33b0201

33c1101

33c1164

33c1211

33c1212

33c1214

33c1215

33c1216

33c1217

33c1218

DMED3B0020: The low-power functionality has been locked. Unlock the function, and then try again.

DMED3B0021: The micro program cannot be downgraded because the NNCtype2 is equipped. Confirm the configuration.

DMED3B0022: The process cannot be performed because the remote path is set up with the array currently connected at the other end. Please delete the remote path and try again.

DMED3B0023: The firmware cannot be downgraded because the 8Gbps fibre interface board is equipped. Please retry by using firmware in relation to this interface board.

DMED3B0100: The process cannot be performed because the firmware is being replaced. Please wait a moment and then try again.

DMED3B0101: The process cannot be performed because the firmware is being replaced. Please wait a moment and then try again.

DMED3B0102: The process cannot be performed because the system drive type is unknown. Replace the system drive with SAS or SATA drive and try again.

DMED3B0103: The firmware replacement cannot be performed because the controller 1 is specified. Please replace the firmware from the controller 0. Or the subsystem may have been rebooted during the firmware replacement. Please replace the firmware again, if the firmware revision is not matched between both controllers.

DMED3B0104: The firmware replacement cannot be performed because firmware replacement of another controller is not completed and the access from hosts is not received. Please perform firmware replacement of this controller again after performing firmware replacement of another controller and completing.

DMED3B0201: The process cannot be performed because Data Retention Utility is installed. Please de-install the option and try again.

DMED3C1101: The firmware cannot be downgraded because Remote Replication is installed. Please change Remote Replication to de-installed and try again.

DMED3C1164: The firmware cannot be downgraded because the non-supported controller is equipped on the downgraded version. Please retry by using firmware in relation to this controller.

DMED3C1211: The firmware cannot be downgraded because the RAID group expansion is now occurring or the RAID group containing unified LU is executed expansion. Please retry after expansion is completed.

DMED3C1212: The firmware cannot be downgraded because ShadowImage pair of

Split Pending or Paired Internally Synchronizing exists. Please retry after status is changed to Split or Paired.

DMED3C1214: The firmware cannot be downgraded because the Dense Units are connected. Please retry after removing the Dense units or by using another firmware.

DMED3C1215: The firmware cannot be downgraded because S-VOL of

ShadowImage pair is under formatting. Please retry after formatting is completed.

DMED3C1216: The firmware cannot be downgraded because Remote Replication is installed. Please change Remote Replication to de-installed and try again.

DMED3C1217: The firmware cannot be downgraded because Distributed Mode is

Hub. Please change the Distributed Mode to Edge and try again.

DMED3C1218: The firmware cannot be downgraded because Dynamic Provisioning is installed. Please change Dynamic Provisioning to de-installed and try again.



Error

Code

33c1219

Description

33c121a

33c121b

33c121c

33c121e

33c121f

33c1220

33c1221

33c1222

33c1223

33c1224

33c1225

33c1227

33c1228

33c12ff

33d0001

3400001

3400002

DMED3C1219: The firmware cannot be downgraded because the user whose user authentication is RADIUS exists. Please delete the user whose user authentication is

RADIUS and try again.

DMED3C121A: The firmware cannot be downgraded because the number of registered account exceeded the maximum value that can be supported on the downgraded version. Please confirm the number of registered account and try again.

DMED3C121B: The firmware cannot be downgraded because the command device that uses the logical unit in the DP pool exists. Please release the command device that uses the logical unit in the DP pool and try again.

DMED3C121C: The firmware cannot be downgraded because the DM-LU that uses the logical unit in the DP pool exists. Please release the DM-LU that uses the logical unit in the DP pool and try again.

DMED3C121E: The firmware cannot be downgraded because Tape Replication is installed. Please change Tape Replication to de-installed and try again.

DMED3C121F: The firmware cannot be downgraded because the number of connected subsystem exceeded the maximum value that can be supported on the downgraded version. Please remove drives or use another firmware and then try again.

DMED3C1220: The firmware cannot be downgraded because the volume migration pair that uses the logical unit in the DP pool exists. Please release the pair and try again.

DMED3C1221: The firmware cannot be downgraded because the state of DP optimization is optimizing. Please try again, after DP optimization is completed.

When the state of DP optimization is failed, cancel DP optimization and then try again.

DMED3C1222: The firmware cannot be downgraded because SSD is mounted.

Please remove SSD or use another firmware and then try again.

DMED3C1223: The firmware cannot be downgraded because the number of connected Dense units exceeded the maximum value that can be supported on the downgraded version. Please remove the Dense units or use another firmware and then try again.

DMED3C1224: The firmware cannot be downgraded because the updating of DP management information is in progress. Please wait a moment and then try again.

DMED3C1225: The firmware cannot be downgraded because Advanced Security

Mode is enabled. Please change Advanced Security Mode to disabled and try again.

DMED3C1227: The firmware cannot be downgraded because the SAS drives are mounted in the Dense Units. Please remove the SAS drives or use another firmware and then try again.

DMED3C1228: The firmware cannot be downgraded because remote paths are set to an array whose H/W revision is 0200. Please delete remote paths and try again.

DMED3C12FF: The firmware cannot be downgraded because tape group targeted differential backup or backed up differential exists. Please delete tape groups, and try again.

DMED3D0001: The process cannot be performed because the drive firmware is being replaced. Please retry after replacement completes.

DMED400001: Processing is not possible because the specified LUs include an unformatted LU. Make sure that the LU status is appropriate, and then retry.

DMED400002: Processing is not possible because the specified logical units contain a V-VOL of COW Snapshot. Confirm the logical unit status, and then try again.



Error

Code

3400003

Description

3400004

3400005

3400006

3400007

3400008

3400009

3400011

3400012

3400013

3400014

3400015

3400021

3400022

3400023

3400024

3400025

3400026

3400027

3400028

DMED400003: Processing is not possible because at least one LU is being quick formatted. Make sure that the LU status is appropriate, and then retry.

DMED400004: Processing is not possible because the specified LUs include a subLU of the combined LUs. Make sure that the LU status is appropriate, and then retry.

DMED400005: Processing is not possible because the specified LUs include a disabled LU. Make sure that the LU status is appropriate, and then retry.

DMED400006: The specified LUs include a degenerating LU. Confirm the LU status, and then try again.

DMED400007: The process cannot be performed because ShadowImage, Remote

Replication, or SnapShot is in progress. Please wait a moment and then try again.

DMED400008: A start or skip operation is specified at the same time as a cancel operation. Make sure that the specification is correct, and then retry.

DMED400009: Processing is not possible because the specified LUs include an undefined LU. Make sure that the LU status is appropriate, and then retry.

DMED400011: Processing is not possible because parity correction has not finished.


DMED400012: Processing is not possible because parity correction is not executed or has aborted. Wait until parity correction finishes, and then retry.





DMED400015: Processing is not possible because parity correction is not available or has aborted. Wait until parity correction has finished, and then retry.

DMED400021: The cancel operation cannot be specified for a parity-uncorrected LU.

Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400022: The start operation cannot be specified for an LU for which parity correction aborted. Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400023: The cancel operation cannot be specified for an LU for which parity correction aborted. Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400024: The start operation cannot be specified for an LU undergoing parity correction. Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400025: The skip operation cannot be specified for an LU undergoing parity correction. Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400026: The start operation cannot be specified for an LU waiting for parity correction. Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400027: The skip operation cannot be specified for an LU waiting for parity correction. Make sure that the parity correction status of the specified LU is appropriate, and then retry.

DMED400028: The cancel operation cannot be specified for an LU for which parity correction was skipped. Make sure that the parity correction status of the specified

LU is appropriate, and then retry.



Error

Code

3400029

Description

340002a

3500001

3600001

3700001

3700002

3800002

3800004

3800005

3800006

3800007

3800008

3800009

3800011

3800013

3800014

3800015

3800016

3800017

3800019

380001a

380001b

3800020

DMED400029: The cancel operation cannot be specified for an LU for which parity correction has finished. Make sure that the parity correction status of the specified

LU is appropriate, and then retry.

DMED40002A: The logical units are under quick formatting. Please the parity correction status and try again.

DMED500001: A command device is not registered. Register the command device, and then retry.


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

Simplex(SMPL). Confirm the LU status and try again.

DMED800002: A parameter error occurred. Check whether the set contents are correct.

DMED800004: The specified NNC number is not a NAS port. Check the port type.

DMED800005: Processing cannot be performed because BIOS is transmitting. Wait for the transmission to finish, and then try again.

DMED800006: Processing cannot be performed because the NAS OS is currently booting, shutting down, or is not ready. Check the status of the NAS OS, and then try again.

DMED800007: Processing cannot be performed because the BIOS is currently being upgraded. Wait for the upgrade to finish, and then try again.

DMED800008: Processing cannot be performed because the NAS OS installation has not finished. Please wait until it has finished, and then try again.

DMED800009: Processing cannot be performed because the other NNC is not active.

Check the NNC status, and then try again.

DMED800011: Process cannot be performed because the NAS OS is running. Stop the NAS OS, and then try again.

DMED800013: Processing cannot be performed because the NAS OS is currently shutting down. Wait until shutdown has finished, and then retry the operation.

DMED800014: Processing cannot be performed because a NAS dump is being collected. Wait for collection to finish, and then try again.

DMED800015: Processing cannot be performed because the system LU is undefined.

Define the system LU, and then try again.

DMED800016: A timeout occurred during installation. Re-insert the NNC breaker, and then try again.

DMED800017: A timeout occurred during installation. Re-insert the NNC breaker, and then try again.

DMED800019: Processing cannot be performed because the NAS OS is not in a stopped state. Stop the NAS OS, and then try again.

DMED80001A: Processing cannot be performed because the BIOS firmware is being updated. Wait for the update of the BIOS firmware to finish, and then try again.

DMED80001B: Processing cannot be performed because the NAS OS is blocked.

Recover the status, and then try again.

DMED800020: An invalid IP address was specified. Specify a correct IP address.



Error

Code

3800021

Description

3800022

3800023

3800024

3800025

3800026

3800027

3800029

3800030

3800099

3900000

3900001

3900002

3900003

3900004

3900005

3900008

3900009

390000a

390000c

390000d

390000e

3900012

DMED800021: A number outside the valid range was specified. Specify a correct number.

DMED800022: An MTU outside the valid range was specified. Specify a correct MTU.

DMED800023: An invalid negotiation has been specified. Specify a correct negotiation.

DMED800024: Processing cannot be performed because the NAS OS is not ready.


DMED800025: Processing cannot be performed because the NNC management port is being set. Check the NAS OS status, and then try again.

DMED800026: The same IP address as that for the management port of the array device cannot be set. Specify a correct IP address.

DMED800027: Daylight savings time is not applicable for the specified time zone.

Check the time zone.

DMED800029: Processing cannot be performed because the MTU values for the NNC are different. Set the same MTU values.

DMED800030: The setting is not possible because the specified IP address is the same as the current IP address of the NNC. Please specify another IP address, and then try again.

DMED800099: An error occurred during installation. Reboot NAS Setup, and then try again.

DMED900000: The process cannot be performed because the MT library is detached or not connected. Please confirm the MT library.

DMED900001: The process cannot be performed because the tape drive is detached or unequipped. Please confirm the tape drive.

DMED900002: The process cannot be performed because the MT library is busy.


DMED900003: The process cannot be performed because the barcode is incorrect.

Please specify a correct barcode.

DMED900004: The process cannot be performed because the slot is detached or unequipped. Please confirm the slot.

DMED900005: The process cannot be performed because the tape group number is not created. Please specify a created tape group number.

DMED900008: The process cannot be performed because the MT library is detached.

Please confirm the status.

DMED900009: The process cannot be performed because there is no tape cartridge in the specified slot or the I/E port. Please confirm the slot or the I/E port.

DMED90000A: The process cannot be performed because the MT library is not connected. Please confirm the MT library.

DMED90000C: The process cannot be performed because the specified slot number is incorrect. Please confirm the slot number and try again.

DMED90000D: The process cannot be performed because there is no tape cartridge in the specified slot. Please confirm the slot.

DMED90000E: The process cannot be performed because the robotics is detached or unequipped. Please confirm the robotics.

DMED900012: The process cannot be performed because the specified tape cartridge cannot be used. Please confirm the status, and select tape cartridges again.



Error

Code

3900013

Description

3900014

3900015

3901000

3901001

3901002

3901003

3901004

3901005

3901006

3901007

3901008

3901009

390100b

390100c

390100e

390100f

3901010

3901100

3901101

DMED900013: The process cannot be performed because differential bit map is insufficient. Please delete unnecessary tape groups or increase the cache memory.



DMED901000: The process cannot be performed because the specified tape group number is being used. Please confirm the tape group number.

DMED901001: The process cannot be performed because the tape cartridge is being used by another tape group. Please confirm the type, and select tape cartridges again.

DMED901002: The process cannot be performed because the tape cartridge is already set as a spare tape cartridge. Please confirm the type, and select tape cartridges again.

DMED901003: The process cannot be performed because the tape cartridge is a cleaning tape cartridge. Please confirm the type, and select tape cartridges again.

DMED901004: The process cannot be performed because the tape cartridge type is different. Please confirm the tape cartridge type, and select tape cartridges again.

DMED901005: The process cannot be performed because the tape cartridge type is not supported. Please confirm the tape cartridge type, and select again.

DMED901006: The process cannot be performed because the number of tape cartridges is insufficient. Please confirm the number of specified tape cartridge type, and select tape cartridges again.

DMED901007: The tape group with mirror cannot be created because there is only one tape drive that can use specified tape cartridge type in the MT library. Please add on a tape drive or select the redundancy without mirror.

DMED901008: The process cannot be performed because the specified tape cartridge cannot be used. Please confirm the status, and select tape cartridges again.

DMED901009: The tape group detail information is invalid.

DMED90100B: The process cannot be performed because there is no tape drive that can use specified tape cartridge type. Please add on a tape drive or select the tape cartridge type again.

DMED90100C: The process cannot be performed because the encryption method is not supported. Please confirm the encryption method, and select again.

DMED90100E: The process cannot be performed because the specified tape cartridge type does not support the encryption.

DMED90100F: The process cannot be performed because the tape cartridge type is not supported. Please confirm the tape cartridge type, and select again.

DMED901010: The process cannot be performed because the filemark interval is not supported.

DMED901100: The process cannot be performed because the copy or restoration of logical unit is in progress. Please try again, after it is completed.

DMED901101: The process cannot be performed because the copy or restoration is in progress in the backup group. Please confirm the status of the tape group in the backup group.



Error

Code

3901102

Description

3902000

3902001

3902002

3902003

3902100

3902101

3902102

3902103

3902104

3902105

3903000

3903001

3903002

3903003

3903004

3903005

3903006

3903007

3903008

DMED901102: The process cannot be performed because the status of another tape group in the backup group is illegal. Please confirm the status of the tape group in the backup group.

DMED902000: The process cannot be performed because the tape cartridge is being used by the tape group. Please confirm the type, and select tape cartridges again.

DMED902001: The process cannot be performed because the tape cartridge is already set as a spare tape cartridge. Please confirm the type, and select tape cartridges again.

DMED902002: The process cannot be performed because the number of spare tape cartridges of the MT library reached the maximum. Please release unnecessary spare tape cartridges.

DMED902003: The process cannot be performed because the tape cartridge is already added in the scratch group. Please confirm the type, and select tape cartridges again.

DMED902100: The process cannot be performed because the tape cartridge is not set as a spare tape cartridge. Please confirm the type, and select tape cartridges again.

DMED902101: The process cannot be performed because the recovery of spare tape cartridge is in progress. Please try again, after it is completed.

DMED902102: The process cannot be performed because the spare tape cartridge is not normal, logically detached, detached. Please confirm the status.

DMED902103: The process cannot be performed because the tape cartridge is not normal. Please confirm the status, and select tape cartridges again.

DMED902104: The process cannot be performed because the tape cartridge type is not undefined. Please confirm the type, and select tape cartridges again.

DMED902105: The process cannot be performed because the tape cartridge is not added in the scratch group. Please confirm the type, and select tape cartridges again.

DMED903000: The process cannot be performed because a different direction of the movement is specified. Please specify the same direction.

DMED903001: The process cannot be performed because the source slot or the I/E port is unequipped. Please confirm the slot or the I/E port.

DMED903002: The process cannot be performed because the destination slot or the

I/E port is unequipped. Please confirm the slot or the I/E port.

DMED903003: The process cannot be performed because the tape cartridge is moving. Please try again, after it is completed.

DMED903004: The process cannot be performed because the MT library is busy.


DMED903005: The process cannot be performed because the number of tape cartridges reached the maximum in one movement.

DMED903006: The process cannot be performed because the tape cartridge is not checked out. Please check out tape cartridges.

DMED903007: The process cannot be performed because the empty I/E port is insufficient. Please confirm the I/E port.

DMED903008: The process cannot be performed because differential bit map is insufficient. Please export unnecessary tape cartridges or delete unnecessary tape groups.



Error

Code

3904000

Description

3904001

3904002

3904003

3905000

3906000

3906001

3906002

3906003

3906004

3906005

3906006

3906007

3906008

3906009

390600a

390600b

390600c

390600d

390600e

3906100

3906101

3906102

DMED904000: The process cannot be performed because the inventory is in progress. Please try again, after it is completed.

DMED904001: The process cannot be performed because the tape cartridge is being exported. Please confirm the status.

DMED904002: The process cannot be performed because the copy or restoration of logical unit is in progress. Please try again, after it is completed.

DMED904003: The process cannot be performed because differential bit map is insufficient. Please export unnecessary tape cartridges or delete unnecessary tape groups.

DMED905000: The process cannot be performed because there is no cleaning tape cartridge. Please import it.

DMED906000: The process cannot be performed because the specified MT library is already added. Please confirm the added MT library.

DMED906001: The process cannot be performed because the number of the MT libraries reached the maximum. Please delete unnecessary MT libraries.

DMED906002: The process cannot be performed because the number of robotics reached the maximum. Please delete unnecessary MT libraries.

DMED906003: The process cannot be performed because the number of tape drives reached the maximum. Please delete unnecessary MT libraries.

DMED906004: The process cannot be performed because the number of slots reached the maximum. Please delete unnecessary MT libraries.

DMED906005: The process cannot be performed because the number of I/E ports on a MT library reached the maximum. Please confirm the MT library.

DMED906006: The process cannot be performed because the specified MT library does not exist. Please confirm the available library to add.

DMED906007: The process cannot be performed because the number of robotics on a MT library reached the maximum. Please confirm the MT library.

DMED906008: The process cannot be performed because the number of tape drives on a MT library reached the maximum. Please confirm the MT library.

DMED906009: The process cannot be performed because the number of slots on a

MT library reached the maximum. Please confirm the MT library.

DMED90600A: The process cannot be performed because the specified MT library number is being used. Please confirm the MT library number.

DMED90600B: The process cannot be performed because the number of robotics on a MT library reached the maximum. Please confirm the MT library.

DMED90600C: The process cannot be performed because the number of tape drives on a MT library reached the maximum. Please confirm the MT library.

DMED90600D: The process cannot be performed because the number of slots on a

MT library reached the maximum. Please confirm the MT library.

DMED90600E: The process cannot be performed because Cartridge Cell License is insufficient. Please install enough Cartridge Cell License and then try again.

DMED906100: The process cannot be performed because the MT library status is waiting connection or connecting. Please confirm the status.





Error

Code

3906103

Description

3906104

3906105

3907000

3908000

3908001

3908002

3909000

3909100

3909101

3909102

3909103

3909104

3909105

3909106

3909107

3909108

3909109

390910a

390910b

390910c

390910d

390910e

390910f

3909110

3909111

3909112

DMED906103: The process cannot be performed because the tape cartridge is being cleaned. Please try again, after it is completed.

DMED906104: The process cannot be performed because the copy is in progress.

Please try again, after it is completed.

DMED906105: The process cannot be performed because the restoration is in progress. Please try again, after it is completed.

DMED907000: The process cannot be performed because the specified port is used by MT library. Please confirm the specification of the port.

DMED908000: The process cannot be performed because the logical unit is copied to the tape cartridge. Please confirm the copy status of the logical unit.

DMED908001: The process cannot be performed because the logical unit is copied to the tape cartridge. Please confirm the copy status of the logical unit.

DMED908002: The process cannot be performed because Tape Replication is installed. Please change Tape Replication to de-installed and then try again.

DMED909000: The process cannot be performed because the tape drive is being used. Please confirm the status.

DMED909100: The process failed due to an invalid parameter. Confirm the specified value.

DMED909101: The process cannot be performed because the tape group is already defined. Please delete the tape group.

DMED909102: The process cannot be performed because the tape cartridge exists in the MT library. Please export the tape cartridge.

DMED909103: The process cannot be performed because other users performed the

TR constitution backup or restoration. Please wait for a while and then try again.

DMED909104: The process cannot be performed because the TR constitution file version is incorrect. Please specify a correct file.

DMED909105: The process cannot be performed because the TR constitution file version is incorrect. Please specify a correct file.





DMED90910A: The tape group detail information is invalid.

DMED90910B: The tape group detail information is invalid.

DMED90910C: The tape group detail information is invalid.

DMED90910D: The tape group detail information is invalid.

DMED90910E: The tape group detail information is invalid.

DMED90910F: The tape group detail information is invalid.



DMED909112: The process cannot be performed because an error occurred in the subsystem. Please confirm the subsystem status, and try again.



Error

Code

3909113

Description

3909114

3909115

3909120

3909121

3909122

3909123

3909124

3909125

3909126

3909127

3909128

3909129

390912a

390912b

390912c

390912d

390912e

390912f

3909132

3909133

3909134

3909135

3909136

3909137

3909138

3909139

39091ff

390a000

390a001

390a002

DMED909113: The process cannot be performed because the version is unmatch between the micro program and the Storage Navigator Modular. Please match the version.


DMED909115: The process cannot be performed because other users changed the

TR constitution information. Please wait for a while and then try again.

DMED909120: The tape information is invalid.










DMED90912A: The tape information is invalid.

DMED90912B: The tape information is invalid.

DMED90912C: The tape information is invalid.

DMED90912D: The tape information is invalid.

DMED90912E: The tape group detail information is invalid. Please specify a correct file.

DMED90912F: The tape information is invalid. Please specify a correct file.

DMED909132: The process cannot be performed because the tape group is already defined. Please delete the tape group.

DMED909133: The process cannot be performed because the tape cartridge exists in the MT library. Please export the tape cartridge.







DMED9091FF: An error occurred in the subsystem.

DMED90A000: The process failed due to an invalid parameter. Confirm the specified value.

DMED90A001: The process failed due to an invalid parameter. Confirm the specified value.

DMED90A002: The process cannot be performed because the number of tape cartridges is incorrect. Please specify a correct number.



Error

Code

390b001

Description

390b002

390b003

390b004

390b005

390b006

390b007

390b00a

390b00b

390b00c

390b00d

390b00e

390b00f

390b010

390b011

390b012

390b013

390b015

390b016

390b017

390b018

390b019

DMED90B001: The process failed due to an invalid parameter. Confirm the specified value.

DMED90B002: The process cannot be performed because the tape group number is not created. Please specify a created tape group number.

DMED90B003: The process cannot be performed because the status of the tape group is illegal. Please confirm the status of the tape group.


DMED90B005: The process cannot be performed because the specified logical unit is reserved for other request. Please confirm the logical unit.

DMED90B006: The process cannot be performed because the tape group cannot be used. Please create the tape group again.

DMED90B007: The process cannot be performed because the specified tape group is not mirror. Please create the tape group with mirror and then try again.

DMED90B00A: The process failed due to an invalid parameter. Confirm the specified value.

DMED90B00B: The process cannot be performed because the logical unit is not defined. Please confirm the logical unit.

DMED90B00C: The process cannot be performed because the logical unit is a logical unit in the DP pool. Please confirm the logical unit.

DMED90B00D: The process cannot be performed because the specified logical unit is

DM-LU. Please specify another logical unit and try again.

DMED90B00E: The process cannot be performed because the specified logical unit is the system LU. Please specify another logical unit and try again.

DMED90B00F: The process cannot be performed because the specified logical unit is a command device. Please specify another logical unit and try again.

DMED90B010: The specified LU is unformatted. Specify a formatted LU and try again.

DMED90B011: The process cannot be performed because the logical unit is neither in normal nor in regressed state. Please confirm the status of the logical unit.

DMED90B012: The process cannot be performed because the specified logical unit is a Sub LU of the unifying LUs. Please specify another logical unit and try again.

DMED90B013: The process cannot be performed because the destination logical unit capacity is smaller than the source logical unit. Please specify the logical unit of the same capacity and try again.

DMED90B015: The process cannot be performed because the logical unit number is doubled. Please specify the different logical unit number.

DMED90B016: The process cannot be performed because the specified logical unit does not exist in the tape group. Please confirm the logical unit in the tape group.

DMED90B017: The process cannot be performed because the destination logical unit capacity is larger than the source logical unit. Please permit Restore to Difference LU

Capacity and then try again.

DMED90B018: The process cannot be performed because the pair status of logical unit is illegal. Please confirm the pair status of logical unit.

DMED90B019: The process cannot be performed because the pair attribute of the logical unit is P-VOL. Please confirm the logical unit.



Error

Code

390b01a

Description

390b01b

390b01c

390b01d

390b01e

390b020

390b021

390b022

390b023

390b024

390b028

390b029

390b02a

390b032

390b047

390b048

390b049

390b04d

390b04e

390b04f

390b050

DMED90B01A: The process cannot be performed because the pair status of the logical unit is Simplex(SMPL). Please confirm the pair status of the logical unit.

DMED90B01B: The process cannot be performed because the logical unit is executing the migration. Please confirm the logical unit.

DMED90B01C: The process cannot be performed because the access level is set to the logical unit. Please confirm the logical unit.

DMED90B01D: The RAID group, to which the specified logical unit belongs, is Power

Saving. Please spin up the RAID groups and then try again.

DMED90B01E: The process failed due to an invalid parameter. Confirm the specified value.

DMED90B020: The process cannot be performed because the segment size of logical unit is too small. Please specify logical unit of a larger segment size than the 8KB and then try again.

DMED90B021: The process cannot be performed because the size of logical unit is too large. Please specify logical unit of a smaller size than the 16TB and then try again.

DMED90B022: The process cannot be performed because the logical unit is the reserve LU. Please delete the reserve LU or specify another logical unit and try again.

DMED90B023: The process cannot be performed because the RAID group that belongs the specified logical unit is executing expansion. Please try again, after it is completed.

DMED90B024: The process cannot be performed because the specified logical unit is a logical unit in the DP pool. Please specify another logical unit and try again.

DMED90B028: The process cannot be performed because the copy or restoration is in progress. Please try again, after it is completed.

DMED90B029: The process cannot be performed because the copy or restoration is in progress. Please try again, after it is completed.

DMED90B02A: The process cannot be performed because the tape group is not backed up. Please specify tape group which is backed up and try again.

DMED90B032: The process cannot be performed because the MT library is busy.





DMED90B04D: The process cannot be performed because the tape group is not encrypted. Please confirm the tape group.

DMED90B04E: The process cannot be performed because the tape group is encrypted.

DMED90B04F: The process cannot be performed because the tape group is encrypted.

DMED90B050: The process cannot be performed because the micro program revision is new. Please update Navigator.



Error

Code

390b051

Description

390b052

390b053

390b054

390b055

390b056

390b05b

390b05c

390b05d

390b05e

390b064

390b065

390b066

390b0c8

390b0c9

390b0cc

390b0d2

390b0d3

390b0d4

390b0d5

390b0d6

390b0d7

390b0d8




DMED90B054: The process cannot be performed because the status of the logical unit is illegal. Please confirm the status of the logical unit.

DMED90B055: The process cannot be performed because the status of the logical unit is illegal. Please confirm the status of the logical unit.

DMED90B056: The process failed due to an invalid parameter. Please confirm the specified value.

DMED90B05B: An error occurred in the subsystem.

DMED90B05C: The process cannot be performed because the cache memory size is insufficient. Please increase the cache memory or delete unnecessary tape group.

DMED90B05D: The process cannot be performed because the tape group is encrypted.

DMED90B05E: The process cannot be performed because the MT library is busy.


DMED90B064: The process cannot be performed because the import is in progress.


DMED90B065: The specified function is not supported. Please confirm the subsystem.

DMED90B066: The process cannot be performed because the TR constitution restoration is in progress. Please try again, after it is completed.

DMED90B0C8: The process failed due to an invalid parameter. Confirm the specified value.

DMED90B0C9: The process cannot be performed because the logical unit is not targeted differential backup. Please confirm the logical unit.

DMED90B0CC: The process cannot be performed because the logical unit is not used by this differential backup. Please confirm the logical unit.

DMED90B0D2: The process cannot be performed because the cache memory size is insufficient. Please increase the cache memory or delete unnecessary tape group.

DMED90B0D3: The process cannot be performed because the pair status of logical unit is illegal. Please confirm the pair status of logical unit.








Error

Code

390b0d9

Description

390b0da

390b0db

390b0e3

390b0e5

390b0e7

390b0ec

390b0ed

390b0ee

390b0f1

390b0f4

390b0f5

390b0f6

390c000

390c001

390d000

390d001

390d002

390d003

390d004

390d100

DMED90B0D9: The process cannot be performed because the number of differential backup to the specified logical unit reached the maximum. Please confirm the backup group.

DMED90B0DA: The process failed due to an invalid parameter. Confirm the specified value.

DMED90B0DB: The process cannot be performed because the logical unit is not used by this differential backup. Please confirm the logical unit.

DMED90B0E3: The process cannot be performed because the full backup tape group does not exist. Please confirm the tape group.

DMED90B0E5: The process cannot be performed because the status of the full backup tape group is illegal. Please confirm the status of differential source tape group.

DMED90B0E7: The process cannot be performed because the restoration of the full backup tape group is in progress. Please try again, after it is completed.

DMED90B0EC: The process failed due to an invalid parameter. Confirm the specified value.

DMED90B0ED: The process cannot be performed because the cache memory size is insufficient. Please try again, after other restoration is completed.

DMED90B0EE: The process cannot be performed because the logical unit at restoring destination is not a part of ShadowImage pair. Please confirm the pair status of the logical unit.

DMED90B0F1: The process cannot be performed because the restoration is in progress in the backup group. Please confirm the status of the tape group in the backup group.

DMED90B0F4: The process cannot be performed because the copy is in progress in the backup group. Please confirm the status of the tape group in the backup group.

DMED90B0F5: The process cannot be performed because the status of another tape group in the backup group is illegal. Please confirm the status of the tape group in the backup group.

DMED90B0F6: The process cannot be performed because the access level is set to the logical unit. Please confirm the logical unit.

DMED90C000: The process cannot be performed because the library port is not set.

Please confirm the library path.

DMED90C001: The process cannot be performed because the recovery of library path is in progress. Please try again, after it is completed.

DMED90D000: The process failed due to an invalid parameter. Confirm the specified value.



DMED90D003: The process cannot be performed because the logging out is in progress. Please wait for a while and then try again.

DMED90D004: The process cannot be performed because the updating information of the port is in progress. Please wait for a while and then try again.

DMED90D100: The process cannot be performed because the port is unequipped.

Please confirm the subsystem status.



Error

Code

390d101

Description

390d102

390d103

390d104

390d105

390d106

390d108

390d10a

390d10b

390d200

390d201

3910000

3910001

3910002

3910003

3910004

3910005

391000f

3910012

3910013

3910014

3910015

3910017

DMED90D101: The process cannot be performed because the port is detached.

Please confirm the port status.

DMED90D102: The process cannot be performed because the specified port type is not fibre channel. Please confirm the port type.

DMED90D103: The process cannot be performed because the port is already set as a library port. Please confirm the port, and select ports again.

DMED90D104: The process cannot be performed because the port is already set as a remote path. Please confirm the port, and select ports again.

DMED90D105: The process cannot be performed because the port is already set the security option. Please confirm the security option of the port.

DMED90D106: The process cannot be performed because the port is already mapped the logical units. Please confirm the mapping information.

DMED90D108: The process cannot be performed because the controller is detached.

Please confirm the subsystem status.

DMED90D10A: The process cannot be performed because the topology of the port is not Point To Point. Please confirm the setting of port.

DMED90D10B: The process cannot be performed because the transfer rate of the specified port is not AUTO. Please confirm the setting of port.

DMED90D200: The process cannot be performed because the specified port is not library port. Please confirm the port status.

DMED90D201: The process cannot be performed because all the library ports cannot be released.





DMED910004: The process cannot be performed because the specified tape group does not exist. Please confirm the condition of the inventory.


DMED91000F: The process cannot be performed because the copy or restoration is in progress. Please try again, after it is completed.


DMED910013: The process cannot be performed because the import is in progress.



DMED910015: The process cannot be performed because the MT library is being added. Please try again, after it is completed.

DMED910017: The process cannot be performed because the micro program is being replaced. Please try again, after it is completed.



Error

Code

3910021

Description

3910022

3910023

3910024

3910025

3910026

3910027

3910028

3910029

3910030

3910031

3910032

3910040

3910050

3910051

3910060

3910070

3910071

3910072

3911000

3911001

3911002

3911003

DMED910021: The process cannot be performed because the import is in progress.



DMED910023: The process cannot be performed because the number of tape cartridges reached the maximum. Please export unnecessary tape cartridges.

DMED910024: The process cannot be performed because the tape cartridge is being exported. Please import it.

DMED910025: The process cannot be performed because the number of the tape groups reached the maximum. Please delete unnecessary tape groups.

DMED910026: The process cannot be performed because the specified tape group number is being used. Please confirm the tape group number.

DMED910027: The process cannot be performed because the specified tape group is already imported. Please confirm the tape group.

DMED910028: The process cannot be performed because the tape cartridge is not normal. Please confirm the status.

DMED910029: The process cannot be performed because the tape cartridge is not undefined. Please confirm the type.




DMED910040: The process cannot be performed because the tape cartridge is already audited. Please export unnecessary tape cartridges.

DMED910050: The process cannot be performed because the inventory is not in progress. Please confirm the condition of the inventory.

DMED910051: The process cannot be performed because the condition of the inventory is incorrect. Please confirm the condition of the inventory.


DMED910070: The option cannot be de-installed or disabled because the import is in progress


DMED910072: The process cannot be performed because the specified tape group is impossible to import. Please confirm the tape group.

DMED911000: The option cannot be installed or enabled because the fibre channel port is not equipped.

DMED911001: The option cannot be installed or enabled because DM-LU is not defined

DMED911002: Tape Replication cannot be installed by emergency key because the options that relate to Tape Replication is already installed by permanent key.

DMED911003: Tape Replication cannot be de-installed because the options that relate to Tape Replication is installed.



Error

Code

3911004

Description

3911005

3911006

3911007

3911008

3911009

391100a

391100b

391100c

3911010

3911020

3911021

3911030

3911031

3911032

3911040

3c00001

3c00002

3c00003

3c00004

3c00005

3c00006

3c00007

3c00008

DMED911004: The option cannot be de-installed because the tape group is already defined. Please delete the tape group.

DMED911005: The option cannot be de-installed because the library port is already defined. Please release the library port.

DMED911006: The process cannot be performed because Tape Replication is deinstalled, or disabled. Please change Tape Replication to installed and then try again.

DMED911007: The option that relate to Tape Replication cannot be installed because

Tape Replication is not installed by permanent key.

DMED911008: The option cannot be installed because differential bit map is insufficient. Please delete unnecessary pairs.

DMED911009: The option cannot be de-installed because differential bit map is used. Please delete all tape groups and release all library ports.

DMED91100A: The option cannot be de-installed because MT library is added. Please delete MT libraries.

DMED91100B: Tape Replication cannot be disabled because the option that relate to

Tape Replication is enabled.

DMED91100C: The process cannot be performed because differential bit map is insufficient. Please delete unnecessary pairs or increase the cache memory.

DMED911010: The option which cannot be specified at the same time is installed.

DMED911020: The option cannot be de-installed or disabled because the copy is in progress.

DMED911021: The option cannot be de-installed or disabled because the restoration is in progress.

DMED911030: The option which cannot be specified at the same time is installed.

DMED911031: The option cannot be installed or enabled because the order is incorrect. Please change Cartridge Cell License to installed or enabled in ascending order.

DMED911032: The option cannot be installed because the previous option is installed by the temporary key or emergency key. Please install the option with the temporary key or emergency key.

DMED911040: The option cannot be de-installed or disabled because the order is incorrect. Please change Cartridge Cell License to de-installed or disabled in descending order.

DMEDC00001: The process cannot be performed because the specified group number is outside the effective range. Confirm the group number.

DMEDC00002: The process cannot be performed because the specified LU number is outside the effective range. Confirm the LU number.

DMEDC00003: The specified group is not used. Confirm the group number.

DMEDC00004: The specified LU is not pair. Confirm the LU number.

DMEDC00005: The specified LU is V-VOL. Specify another LU and try again.

DMEDC00006: The specified LU is not V-VOL. Specify the LU number of V-VOL and try again.

DMEDC00007: The process cannot be performed because the number of pairs reached the maximum. Confirm the settings of pairs.

DMEDC00008: The process cannot be performed because the same Pair Name exists. Please confirm the Pair Name and try again.



Error

Code

3c00009

Description

3c0000a

3c0000b

3c0000c

3c0000d

3c0000e

5010001

5010002

5010003

5010004

5010005

5010006

5010007

5010009

501000a

501000b

5010019

5010065

5010066

5010067

5011001

5011002

5011003

DMEDC00009: The process cannot be performed because the same Pair Name exists. Please confirm the Pair Name and try again.

DMEDC0000A: The process cannot be performed because the same Pair Name exists. Please confirm the Pair Name and try again.

DMEDC0000B: The process cannot be performed because the same Pair Name exists. Please confirm the Pair Name and try again.

DMEDC0000C: The process cannot be performed because the same Group Name exists. Please confirm the Group Name and try again.

DMEDC0000D: The process cannot be performed because the same Group Name exists. Please confirm the Group Name and try again.

DMEDC0000E: The specified logical unit is Volume Migration pair. Please specify another logical unit and try again.

DMER010001: The target LU is undergoing the change of an ownership of LU. Retry after waiting for a while.

DMER010002: The change of a controller that controls the LU cannot be checked because the directory was blocked in the other controller. Retry after waiting for a while.

DMER010003: An instruction to change the controller that controls the LU was issued. Retry after waiting for a while.

DMER010004: The owner controller of the LUs to be paired is detached. Retry.




DMER010009: The owner controller of the LUs to be paired is detached. Retry after waiting for a while.

DMER01000A: The owner controller of the LUs to be paired is detached. Retry after waiting for a while.

DMER01000B: The owner controller of the LUs to be paired is detached. Retry after waiting for a while.

DMER010019: The pair operation command is a time-out. Retry after waiting for a while.

DMER010065: Since the specified P-VOL requires a change of an ownership of LU, it is undergoing the execution of the ownership of LU change. Retry after waiting for a while.

DMER010066: Though the specified P-VOL requires a change of an ownership of LU, the controller to be changed is blocked. Retry after waiting for a while.

DMER010067: Since the specified P-VOL requires a change of an ownership of LU, the execution of the ownership of LU change has been started. Retry after waiting for a while.






Error

Code

5012001

Description

5012002

5012003

5020000

5020001

5020002

5020003

5020004

5020005

5020006

5020007

5020009

502000d

502000e

502000f

5020010

5020011

5020012

5020014

5020016

5020017

5020018

5020020

5020021




DMER020000: The pair status of the P-VOL is other than Simplex. Check the pair status of the LU.

DMER020001: The status of the P-VOL is other than normal and regressive. Check the status of the LU.

DMER020002: The P-VOL is a Cache Residency LU. Check the status of the LU.

DMER020003: The P-VOL is reserved as a Cache Residency LU. Check the status of the LU.

DMER020004: The P-VOL is a command device. Check the status of the LU.

DMER020005: The primary sequence number is different from the own Array ID.

Check the Array ID.

DMER020006: Both of the two paths are abnormal. Check the status of the path.

DMER020007: The P-VOL has been defined as a SubLU of a unified LU. Check the status of the LU.

DMER020009: There exist maximum number of pairs already. Delete the unnecessary pairs.

DMER02000D: The P-VOL is in a status other than Split and Failure. Check the pair status of the LU.

DMER02000E: The status of the P-VOL is other than normal and regressive. Check the pair attribute of the LU.

DMER02000F: The number of the LU to be paired is different. Check the specified

LUN.


Check the Array ID.


DMER020012: The specified P-VOL is in a status other than Synchronizing and

Paired. Check the pair status of the LU.

DMER020014: The current Array ID differs from the number that was set initially.

Check the Array ID.

DMER020016: The number of the LU to be paired is different. Check the specified

LUN.


Check the Array ID.

DMER020018: The S-VOL pair cancellation instructions to a P-VOL or the pair cancellation instructions to an S-VOL was received. Check the pair status of the LU.

DMER020020: The Asynchronous mode is turned on. The Asynchronous mode is not supported.

DMER020021: The fence level is STATUS. Make sure of the specified fence level.



Error

Code

5020023

Description

5020024

5020025

5020026

5020027

5020028

5020029

502002a

502002b

502002c

502002d

502002e

502002f

5020030

5020031

5020032

5020033

5020035

5020036

5020037

5020038

5020039

502003a

DMER020023: The P-VOL is a volume of ShadowImage. It is in the Failure status and cannot accept Read/Write instructions. Check the pair status of the LU.

DMER020024: The P-VOL is undergoing the restoration of ShadowImage pair. Check the pair status of the LU.

DMER020025: The P-VOL received an instruction to swap pair. Check the pair attribute of the LU.

DMER020026: The pair status is not Takeover. Check the pair status.

DMER020027: The S-VOL received an instruction to resynchronize pair. Check the pair attribute of the LU.

DMER020028: The volume is a P-VOL of ShadowImage. It is in the Failure status and cannot accept Read/Write instructions. Place the P-VOL concerned in the

Simplex status and create the pair again.

DMER020029: The volume is a P-VOL of ShadowImage and undergoing a reverse copy. Check the pair status of the LU.

DMER02002A: The P-VOL received an instruction to be taken over. Check the pair status of the LU.

DMER02002B: It is in the Simplex or Synchronizing status. Check the pair status of the LU.

DMER02002C: The secondary sequence number is different from the Array ID.

Check the Array ID.

DMER02002D: The S-VOL received an instruction to be taken over. Check the pair status of the LU.

DMER02002E: The pair status of the P-VOL is Simplex or Synchronizing. Check the pair status of the LU.

DMER02002F: The primary sequence number is different from the Array ID. Check the Array ID.

DMER020030: The S-VOL received the suspension. Check the pair status of the LU.

DMER020031: The capacity is beyond the limits of support. Split the unnecessary pairs.

DMER020032: The P-VOL is configured as RAID 0. Check the RAID level of the specified LU.

DMER020033: The specified LU is an S-VOL of ShadowImage and it is in a pair status other than Split. Check the pair status of the LU.

DMER020035: The volume is an S-VOL of ShadowImage and it is in a pair status other than Split. Check the pair status of the LU.

DMER020036: The volume is a P-VOL of SnapShot and being restored. Check the pair status of the LU.

DMER020037: The volume is a P-VOL of SnapShot It is in the Failure status and cannot accept Read/Write instructions. Change the statuses of all V-VOLs of the P-

VOL concerned to Simplex, and create the pair again.

DMER020038: The volume is a P-VOL of SnapShot and the mate to it has already been paired by Remote Replication. Check the pair status of the LU.

DMER020039: The volume is a V-VOL of SnapShot and it is in a status other than

Split of SnapShot. Check the pair status of the LU.

DMER02003A: The volume is a V-VOL of SnapShot. The related P-VOL of SnapShot is being restored or has been placed in the Failure status during a restoration. Check the pair status of the LU.



Error

Code

502003b

Description

502003c

502003d

502003e

502003f

5020040

5020042

5020043

5020045

5020046

5020047

5020048

502004b

502004d

502004e

502004f

5020052

5020053

5020054

5020055

5020056

DMER02003B: The specified LU is comprised in a SnapShot pair and it has already been cascaded with a Remote Replication pair. Check the pair status of the LU.

DMER02003C: The specified LU is comprised in a SnapShot pair and it has already been cascaded with a Remote Replication pair. Check the pair status of the LU.

DMER02003D: The volume is a P-VOL of SnapShot and being restored. Check the pair status of the LU.

DMER02003E: The volume is a P-VOL of SnapShot. It is in the Failure status and cannot accept Read/Write instructions. Change the statuses of all V-VOLs of the P-

VOL related to Simplex and create the pair again.

DMER02003F: The volume is a V-VOL of SnapShot and it is in a status other than

Split of SnapShot. Check the pair status of the LU.

DMER020040: The volume is a P-VOL of SnapShot. It is being restored or in the

Failure status and cannot accept Read/Write instructions. Check the pair status of the LU.

DMER020042: The RAID level differs between the MainLU and SubLU. Check that the RAID level of the specified LU is the same as that expected.

DMER020043: The number of data disks differs between the MainLU and SubLU.

Check that the number of data disks of the specified LU is the same as that expected.

DMER020045: The specified LU is a V-VOL of SnapShot. The P-VOL of the related

SnapShot pair is a unified LU, whose MainLU and SubLU are different in RAID level.

Check that the RAID level of the SnapShot P-VOL corresponding to the specified LU is the same as that expected.

DMER020046: The specified LU is a V-VOL of SnapShot. The P-VOL of the related

SnapShot pair is a unified LU, whose MainLU and SubLU are different in number of data disks. Check that the number of data disks of the SnapShot P-VOL corresponding to the specified LU is the same as that expected.

DMER020047: Data of the Remote Replication P-VOL is partially destroyed. Issue the SnapShot instruction (to change the status from Paired to Split) to the SnapShot pair again, and then create the pair again.

DMER020048: Data of the Remote Replication P-VOL is partially destroyed. Format the specified LU after getting backup data of it. Then restore the backup data.

DMER02004B: The specified P-VOL is in the Failure (S-VOL Switch) status of

ShadowImage. Request service personnel to replace drives that compose the P-VOL.

Format them after the replacement then resynchronize the pair.

DMER02004D: The DM-LU is not set. Retry after setting the DM-LU.

DMER02004E: The DM-LU cannot be specified as P-VOL. Check the status of the LU.

DMER02004F: Validity of the license expired. Purchase the license.

DMER020052: The remote SnapShot split request was accepted in the Remote

Replication environment. The remote SnapShot split request is not supported in the

Remote Replication environment.

DMER020053: The specified P-VOL is the reserved LU. Check the status of the LU.

DMER020054: The specified P-VOL is undergoing the migration. Check the pair status of the LU.

DMER020055: The disk drives that configure a RAID group, to which the specified P-

VOL belongs have been spun down. Check the status of the RAID group.





Error

Code

5020057

Description

5020058

5020059

502005a

502005b

502005c

502005d

502005e

502005f

5020060

5020061

5020062

5020063

5020064

5020065

5020066

5020067

5020068

5020069

502006a

502006b

DMER020057: The specified function is not supported in a remote array. Check the remote array.

DMER020058: When creating pairs with group is specified, the specified group ID is beyond the limits of supported. Check the specified group ID.

DMER020059: The pair status of the specified S-VOL does not allow you to create a pair. Check the pair status of the specified S-VOL on both local and remote arrays.

DMER02005A: The command was received in unit of group at the time of resynchronization. Check the specified value.

DMER02005B: When the unit of group is specified, the specified S-VOL is not created pair with group. Check the status of the LU.

DMER02005C: When the unit of group is specified, there is a P-VOL in the same group. Check the group ID.

DMER02005D: When the unit of group is specified, there is no pair, which is in the

Paired, Split, or Failure status, in the same group. Check the pair status of LU in the group.

DMER02005E: When the unit of group is specified, the specified P-VOL is not created pair with group. Check the status of the LU.

DMER02005F: When the unit of group is specified, there is an S-VOL in the same group. Check the group ID.

DMER020060: When the unit of group is specified, there is no pair, which is in the

Paired, Split, or Failure status, in the same group. Check the pair status of LU in the group.

DMER020061: When the unit of group is specified, the specified P-VOL is not created pair with group. Check the status of the LU.

DMER020062: When the unit of group is specified, there is an S-VOL in the same group. Check the group ID.


Synchronizing or Paired status, in the same group. Check the pair status of LU in the group.

DMER020064: The pair cancellation instructions was executed for the range that was not supported. Check the specified value.

DMER020065: When the unit of group is specified, the specified P-VOL is not created pair with group. Check the status of the LU.

DMER020066: When the unit of group is specified, there is an S-VOL in the same group. Check the group ID.

DMER020067: When the unit of group is specified, the specified S-VOL is not created pair with group. Check the status of the LU.

DMER020068: When the unit of group is specified, there is a P-VOL in the same group. Check the group ID.

DMER020069: The remote path connected to the specified remote array does not exist. Retry after creating the remote path from the local array to the remote array of the specified remote Array ID.

DMER02006A: The command cannot execute because the Auto Migration is undergoing. Check the Migration status.

DMER02006B: The command cannot execute because the Auto Migration is undergoing. Check the Migration status.



Error

Code

502006c

Description

502006d

502006e

502006f

5020070

5020071

5020072

5020073

5020074

5020075

5020076

5020077

5020078

5020079

502007a

502007b

502303d

502403d

5030000

5030001

DMER02006C: The command cannot execute because the Auto Migration is undergoing. Check the Migration status.

DMER02006D: There are other pairs in the group, whose fence level is not the same as the one specified. Confirm the fence level of the pair you are creating.

DMER02006E: There are other pairs in the group, whose P-VOL and S-VOL are swapped. Confirm the array on which you are executing the command.

DMER02006F: The specified LU is the P-VOL or S-VOL of a ShadowImage pair that the status is Split Pending or Paired Internally Synchronizing. Check the status of the ShadowImage pair.

DMER020070: Migration status indicates a status other than Not Started. Check the

Migration status.

DMER020071: Migration mode indicates Migration. Check the migration mode.

DMER020072: The RAID group to which the specified LU belongs indicates a status other than Normal. Retry after the status becomes Normal.

DMER020073: An LU that belongs to the RAID group that indicates a status other than Normal is included in the data pool that is used by pairs in the specified group.

Retry after the RAID group status becomes Normal.

DMER020074: The specified CTG number has been used into other remote replication pair with the remote array. Retry after specifying the number other than specified CTG number.

DMER020075: The local array can not execute create pair with the specified remote array because the maximum number of the connected arrays is beyond the limits.

Retry after deleting the all remote replication pair with the another remote array.

DMER020076: The local array can not execute create pair with the specified remote array because the maximum number of the connected arrays is beyond the limits.

Retry after deleting the all remote replication pair with the another remote array.

DMER020077: The LU created in DP pool was specified as P-VOL. Specify an LU other than the LU created in DP pool.

DMER020078: The LU that was specified as P-VOL does not exist. Check the specified LUN.

DMER020079: The specified P-VOL is a volume of ShadowImage pair that includes the LU created in DP pool. Confirm the ShadowImage pair that the specified P-VOL is part of.

DMER02007A: The specified P-VOL is a volume of ShadowImage pair that includes the LU created in DP pool. Confirm the ShadowImage pair that the specified P-VOL is part of.

DMER02007B: The specified P-VOL is an S-VOL of ShadowImage pair those P-VOL is part of another ShadowImage pair that S-VOL is the LU created in DP pool. Confirm all the S-VOL of ShadowImage pair that shares the P-VOL with the ShadowImage pair that specified P-VOL is part of.

DMER02303D: Pair status of corresponding LU does not match. Confirm the pair status of LU and the other side's LUN.


DMER030000: The controller that controls the LU cannot be changed because pinned data exists. Retry after eliminating pinned data.

DMER030001: The controller that controls the LU cannot be changed temporarily.

Retry after waiting for a while.



Error

Code

5030002

Description

5030003

5030004

5030005

5030006

5030007

5030008

5030009

503000b

503000d

503000e

5030010

5030011

5030012

5030014

5030015

5030017

5030018

503001a

503001b

503001d

503001e

503001f

5030020

5030021

5030022

5030023

DMER030002: The operation to change LU is in progress. Retry after waiting for a while.

DMER030003: There is no partition to which the current partition is to be changed.


DMER030004: The directory configuration is being changed. Reboot the subsystem.

DMER030005: The change of a controller that controls the LU resulted in a time-out.


DMER030006: The pair status of the P-VOL is other than Simplex, or a V-VOL does not exist. Check the pair status of the LU.

DMER030007: The pair status is other than Simplex. Check the pair status of the

LU.

DMER030008: The specified P-VOL is a V-VOL. Check the pair status of the LU.

DMER030009: The specified V-VOL is a P-VOL. Check the pair status of the LU.

DMER03000B: The group ID is out of appropriate range. Make sure of the specified group ID number.

DMER03000D: The same MU number was specified within the same P-VOL. Make sure of the specified MU number.

DMER03000E: The process is in progress. Retry after waiting for a while.

DMER030010: The pair status is other than Split. Check the pair status of the LU.

DMER030011: The object LUN is not the same as the expected one. Check the specified LU.

DMER030012: The instruction of forced suspension was received. Make sure of the command.

DMER030014: The P-VOL is in a status other than normal and regressive. Check the status of the LU.

DMER030015: The data pool LU being used is in a status other than normal and regressive. Check the status of the pool LU.

DMER030017: The pair attribute of the P-VOL is V-VOL. Check the status of the LU.

DMER030018: The pair attribute of the V-VOL is P-VOL. Check the status of the LU.

DMER03001A: The same MU number was specified within the same P-VOL. Make sure of the specified MU number.

DMER03001B: The process is in progress. Retry after waiting for a while.

DMER03001D: The object LUN is not the same as the expected one. Check the specified LU.

DMER03001E: The specified V-VOL is not specified to be grouped(Group ID suspension). Check the pair attribute of the LU.

DMER03001F: The V-VOL, which is an object of the batch suspension, is in a status other than Paired(Group ID suspension). Check the pair status of the LU.

DMER030020: The process is in progress. Retry after waiting for a while.


DMER030022: The pair status of the V-VOL is illegal. Check the pair status of the

LU.

DMER030023: The object LUN is not the same as the expected one. Check the specified LU.



Error

Code

5030028

Description

5030029

503002a

503002b

503002c

503002e

503002f

5030030

5030031

5030032

5030033

5030034

5030035

5030036

5030037

5030038

5030039

503003a

503003b

503003c

DMER030028: The specified MU number is different from that of the specified V-

VOL. Make sure of the specified MU number.

DMER030029: The specified MU number is different from that of the specified V-


DMER03002A: The specified MU number is different from that of the specified V-


DMER03002B: The pair status was changed to Failure because the process terminated abnormally. Place the pair concerned in the Simplex status once, and then create the pair again.

DMER03002C: The specified P-VOL has excess pinned data (at the time of a restoration only). Retry after eliminating pinned data.

DMER03002E: Navigator was received by the control information on 8-byte form.

Check the environment of Navigator.

DMER03002F: There are 64 or more LUs being restored. Retry after the restoration is completed.

DMER030030: The P-VOL is being restored. Retry after the restoration is completed.

DMER030031: Data of the V-VOL is partially destroyed. Make a backup from the S-

VOL to a tape device, etc. and then restore the data to the P-VOL.


DMER030033: Because the process terminated abnormally, the pair status was changed to Failure and the P-VOL became unable to accept Read/Write instructions.

Change the statuses of all V-VOLs of the P-VOL concerned to Simplex, and create the pair again.

DMER030034: Because the process terminated abnormally, the pair status was changed to Failure and the P-VOL became unable to accept Read/Write instructions.

Change the statuses of all V-VOLs of the P-VOL concerned to Simplex, and create the pair again.

DMER030035: The MU number is other than 0 to 2. Make sure of the specified MU number.

DMER030036: The MU number is other than 0 to 2. Make sure of the specified MU number.

DMER030037: The MU number is other than 0. Make sure of the specified MU number.

DMER030038: The V-VOL is a volume of Remote Replication and in a status other than Simplex. Check the status of the Remote Replication pair.

DMER030039: The P-VOL of SnapShot is a P-VOL of Remote Replication. It is in the

Split status and prohibited from accepting Write instructions. Check the pair status and pair attribute.

DMER03003A: The P-VOL of SnapShot is a S-VOL of Remote Replication. It is in the

Split status and prohibited from accepting Write instructions. Check the pair status and pair attribute.

DMER03003B: The P-VOL of SnapShot is a volume of Remote Replication and it is in a status other than Simplex and Split. Check the status of the Remote Replication pair.

DMER03003C: Among the other V-VOLs of SnapShot, there are LUs of Remote

Replication in a status other than Split and Failure. Check the status of the Remote

Replication pair.



Error

Code

503003d

Description

503003e

5030044

5030045

5030046

5030047

5030048

5030049

503004a

503004b

5030052

5030053

5030054

5030056

5030057

5030058

5030059

503005a

503005b

503005c

503005d

503005e

503005f

DMER03003D: The V-VOL is a volume of Remote Replication and in a status other than Split and Failure. Check the status of the Remote Replication pair.

DMER03003E: The V-VOL is a volume of Remote Replication and in a status other than Simplex. Check the status of the Remote Replication pair.

DMER030044: The DM-LU is not set. Retry after setting the DM-LU.

DMER030045: The DM-LU was specified as P-VOL. Check the status of the LU.

DMER030046: The DM-LU was specified as V-VOL. Check the status of the LU.



DMER030049: The DM-LU was specified as V-VOL. Check the status of the LU.

DMER03004A: Validity of the license expired. Purchase the license.

DMER03004B: Validity of the license expired. Purchase the license.

DMER030052: The specified P-VOL is a P-VOL of Remote Replication and the status of the Remote Replication pair is other than Split (at the time of restoration). Check the status of the LU.

DMER030053: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Split and writing to the S-VOL is prohibited (at the time of restoration). Check the status of the LU.

DMER030054: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Busy (at the time of restoration). Check the status of the LU.

DMER030056: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Split and reading/writing from/to the S-VOL is prohibited (at the time of restoration). Check the status of the LU.

DMER030057: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is other than Simplex or Split (at the time of restoration). Check the status of the LU.

DMER030058: The P-VOL of this SnapShot is the S-VOL of the Remote Replication pair. It cannot be executed because the status of this Remote Replication pair is

Synchronizing or Paired. Check the status of the LU.

DMER030059: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Split and reading/writing from/to the S-VOL is prohibited. Check the status of the LU.

DMER03005A: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Synchronizing or Paired. Check the status of the

LU.

DMER03005B: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Split and reading/writing from/to the S-VOL is prohibited. Check the status of the LU.

DMER03005C: The specified P-VOL is an S-VOL of Remote Replication and the status of the Remote Replication pair is Pool Full (at the time of restoration). Check the status of the LU.

DMER03005D: The specified P-VOL is the reserved LU. Check the status of the LU.

DMER03005E: The specified P-VOL is the reserved LU. Check the status of the LU.

DMER03005F: Though the specified P-VOL requires a change of an ownership of LU, it has the pinned data. Contact the service personnel.



Error

Code

5030060

Description

5030061

5030062

5030063

5030064

5030065

5030066

5030067

5030068

5030069

503006a

503006b

503006c

503006d

503006e

503006f

5030070

5030071

5030072

5030073

5030074

5030075

5030076

DMER030060: The controller that controls the LU that will be P-VOL cannot be changed. Check the status of the LU.


DMER030062: There is no partition to which the current partition to be changed.


DMER030063: Though the specified P-VOL requires a change of an ownership of LU, the directory structure is being changed. Check the status of the LU.

DMER030064: Though the specified P-VOL requires a change of an ownership of LU, a time-out occurred in the ownership of LU changed. Check the status of the LU.


VOL belongs have been spun down (at the time of restoration). Check the status of the RAID group.

DMER030066: The specified POOL ID is beyond the limits of supported. Check the specified POOL ID.

DMER030067: There is no POOL LU at the specified POOL ID. Check the specified

POOL ID.

DMER030068: The specified P-VOL is already paired with one or more V-VOLs, and the specified POOL ID is different from the POOL ID, which is already assigned.

Check the specified POOL ID.

DMER030069: The RAID group, to which the specified P-VOL belongs, is RAID 0.

Check the RAID level of the specified LU.

DMER03006A: The V-VOL has already created the maximum number of pairs for the specified P-VOL. Check the number of V-VOLs which have paired with the P-VOL.

DMER03006B: The specified P-VOL is a SubLU of a unified LU. Check the status of the LU.

DMER03006C: The specified P-VOL is a Volume Migration pair. Check the status of the LU.

DMER03006D: The specified P-VOL is a ShadowImage pair. Check the attribute of the LU.

DMER03006E: The specified P-VOL has been defined to the command device. Check the attribute of the LU.

DMER03006F: The maximum supported capacity is beyond the limits. Delete the unnecessary pairs.

DMER030070: The maximum supported capacity is beyond the limits. Delete the unnecessary pairs.

DMER030071: It is exceeded the total allowable maximum number of Remote

Replication and SnapShot pairs. Delete the unnecessary pairs.

DMER030072: The specified P-VOL is a MainLU of a unified LU, which includes an LU with a capacity smaller than 1 GB. Check the status of the LU.

DMER030073: The specified P-VOL has been set to the current Cache Residency LU.

Check the status of the LU.

DMER030074: The specified P-VOL has been set to the reserved Cache Residency

LU. Check the status of the LU.

DMER030075: The specified P-VOL is the LU, for which a change of the cache partition(s) had been reserved to other directory. Check the status of the LU.

DMER030076: Differential bit map is insufficient. Delete the unnecessary pairs.



Error

Code

5030077

Description

5030078

5030079

503007a

503007b

503007c

503007d

503007e

503007f

5030080

5030081

5030082

5030083

5030084

5030085

5030086

5030087

5030088

5030089

503008a

503008b

DMER030077: When the specified P-VOL is a Remote Replication pair, the specified pool ID and the used pool ID are not the same. Check the specified pool ID.

DMER030078: LU capacities of the P-VOL and V-VOL are different. Check the capacity of the LU.

DMER030079: The specified V-VOL is an S-VOL of a Remote Replication pair.

DMER03007A: Among the other V-VOLs of SnapShot, there are S-VOLs of Remote

Replication. Check the status of the Remote Replication pair.

DMER03007B: An unsupported command option was received. Check the specified value.

DMER03007C: The specified POOL ID is beyond the limits of supported. Check the specified POOL ID.

DMER03007D: There is no POOL LU at the specified POOL ID. Check the specified

POOL ID.

DMER03007E: An instruction to create a pair was issued to a P-VOL, which has one or more pairs, specifying a POOL ID different from that has been assigned. Check the specified POOL ID.

DMER03007F: The RAID group, to which the specified P-VOL belongs, is RAID 0.


DMER030080: The V-VOL has already created the maximum number of pairs for the specified P-VOL. Check the number of V-VOLs which have paired with the P-VOL.

DMER030081: The specified P-VOL is a SubLU of a unified LU. Check the status of the LU.

DMER030082: The specified P-VOL is a Volume Migration pair. Check the RAID level of the specified LU.

DMER030083: The specified P-VOL is a ShadowImage pair. Check the attribute of the LU.

DMER030084: The specified P-VOL has been defined to the command device. Check the attribute of the LU.




Replication and SnapShot pairs. Delete the unnecessary pairs.

DMER030088: The specified P-VOL is a MainLU of a unified LU, which includes an LU with a capacity smaller than 1 GB. Check the status of the LU.


Check the status of the LU.

DMER03008A: The specified P-VOL has been set to the reserved Cache Residency

LU. Check the status of the LU.

DMER03008B: The specified P-VOL is the LU, for which a change of the cache partition(s) had been reserved to other directory. Check the status of the LU.

503008d

DMER03008D: When the specified P-VOL is a Remote Replication pair, the specified pool ID and the used pool ID are not the same. Check the specified pool ID.



Error

Code

503008e

Description

503008f

5030090

5030091

5030092

5030093

5030094

5030095

5030096

5030097

5030098

5030099

503009a

503009b

503009c

503009d

503009e

503009f

50300a0

50300a1

50300a2

DMER03008E: LU capacities of the P-VOL and V-VOL are different. Check the capacity of the LU.

DMER03008F: When creating a pair specifying a group ID, the specified group ID is already used for a ShadowImage pair. Check the specified group ID.

DMER030090: The partition or pair partition to which the target LU belongs is incorrect. Check the partition number.

DMER030091: The firmware internal error occurred. Retry after waiting for a while.

If an error occurred again, contact the service personnel.

DMER030092: The P-VOL is in a status other than normal or regressive. Check the status of the LU.

DMER030093: The used data POOL LU is in the status other than normal or regressive. Check the status of the LU.

DMER030094: The Migration status is other than unexecuted. Check the Migration status.





DMER030099: There exist maximum number of pairs already. Delete the unnecessary pairs.

DMER03009A: There exist maximum number of pairs already. Delete the unnecessary pairs.

DMER03009B: The operation to change LU has become timeout while the controller is recovering. Retry the operation after the controller is recovered.

DMER03009C: The RAID group to which the target LU of changing ownership belongs indicates a status other than Normal. Retry after the status becomes

Normal.

DMER03009D: The LU created in DP pool was specified as P-VOL. Specify an LU other than the LU created in DP pool.

DMER03009E: A P-VOL that belongs to the RAID group that indicates a status other than Normal is included in the specified group. Retry after the RAID group status becomes Normal.

DMER03009F: An LU that belongs to the RAID group that indicates a status other than Normal is included in the data pool that is used by pairs in the specified group.

Retry after the RAID group status becomes Normal.

DMER0300A0: The RAID group to which the specified LU belongs indicates a status other than Normal. Retry after the status becomes Normal.

DMER0300A1: An LU that belongs to the RAID group that indicates a status other than Normal is included in the data pool that is specified when the pair operation or used by specified pair. Retry after the RAID group status becomes Normal.

DMER0300A2: The LU created in DP pool was specified as P-VOL. Specify an LU other than the LU created in DP pool.



Error

Code

50300a3

Description

50300a4

50300a5

50300ef

50300f0

50300fa

50300fb

5031000

5031001

5031002

5031003

5031004

5031005

5031090

5031091

503109b

503109c

5032000

5032001

5032002

5032003

5032004

5032005

DMER0300A3: The LU that was specified as P-VOL does not exist. Check the specified LUN.


DMER0300A5: An LU whose DP optimization status is not Normal is included in the pair and its cascade pairs. Check the DP optimization status of the LUs which are included in the pairs.

DMER0300EF: The partition or pair partition to which the target LU belongs is incorrect. Check the partition number.

DMER0300F0: The firmware internal error occurred. Retry after waiting for a while.


DMER0300FA: The operation to change LU has become timeout while the controller is recovering. Retry the operation after the controller is recovered.

DMER0300FB: The RAID group to which the target LU of changing ownership belongs indicates a status other than Normal. Retry after the status becomes

Normal.














DMER03109C: The RAID group to which the target LU of changing ownership belongs indicates a status other than Normal. Retry after the status becomes

Normal.












Error

Code

5032090

Description

5032091

503209b

5050001

5050002

5050003

5050004

5050005

5060001

5060002

5060003

5060004

5060005

5060006

5070001

5070002

5070003

5070011

5070012

5070021

5070022

5070023

5080001





DMER050001: The P-VOL or S-VOL is being formatted. Retry after the formatting is completed.





DMER060001: The S-VOL is in the S-VOL Disable mode. Cancel the access attribute.

DMER060002: The P-VOL is in the S-VOL Disable mode (at the time of restoration).

Check the attribute of the LU.

DMER060003: The S-VOL Disable is specified for the P-VOL (at the time of a restoration only). Cancel the access attribute.

DMER060004: The S-VOL Disable is specified for the S-VOL. Cancel the access attribute.

DMER060005: Resynchronization is directed to the ShadowImage pair whose S-VOL is specified as S-VOL Disable. Check the pair attribute of the LU.

DMER060006: The S-VOL Disable is specified for the S-VOL (at the time of a restoration only). Check the pair attribute of the LU.

DMER070001: The P-VOL or S-VOL has not undergone the forced restoration by means of parity. Retry after making the restoration by means of parity.

DMER070002: The P-VOL is undergoing the forced restoration by means of parity

(at the time of restoration). Retry after the restoration by means of parity is completed.

DMER070003: The S-VOL is undergoing the forced restoration by means of parity.

Retry after making the restoration by means of parity.

DMER070011: The P-VOL has not undergone the forced restoration by means of parity. Retry after making the restoration by means of parity.

DMER070012: The P-VOL is undergoing the forced restoration by means of parity.

Retry after the restoration by means of parity is completed.

DMER070021: The P-VOL or data pool LU has not undergone the forced restoration by means of parity. Retry after making the restoration by means of parity.

DMER070022: The P-VOL is undergoing the forced restoration by means of parity

(at the time of a restoration). Retry after parity correction is completed.

DMER070023: The data pool LU is undergoing the forced restoration by means of parity. Retry after the restoration by means of parity is completed.

DMER080001: More LUs than supportable ones were specified for LUNs of the P-

VOL. Make sure of the number of the specified paired LU.



Error

Code

5080002

Description

5080003

5080004

5080005

5080006

5080007

5080008

5080009

508000a

508000b

508000c

508000e

508000f

5080010

5080011

5080012

5080013

5080014

5080016

5080017

5080018

5080019

508001a

508001b

508001c

DMER080002: More LUs than supportable ones were specified for LUNs of the S-

VOL. Make sure of the number of the specified paired LU.

DMER080003: The P-VOL is in the status other than normal and regressive. Check the status of the LU.

DMER080004: The S-VOL is in the status other than normal and regressive. Check the status of the LU.


Check the Array ID.

DMER080006: The secondary sequence number is different from the own Array ID.

Check the Array ID.

DMER080007: The primary port number is not supported. Check the specified port number.

DMER080008: The secondary port number is not supported. Check the specified port number.

DMER080009: The P-VOL is a volume of ShadowImage and in the status other than

Simplex. Check the pair status of the LU.

DMER08000A: The S-VOL is a volume of ShadowImage and in the status other than

Simplex. Check the pair status of the LU.

DMER08000B: The P-VOL is a Sub LU of a unified LU. Check the status of the LU.

DMER08000C: The S-VOL is a Sub LU of a unified LU. Check the status of the LU.

DMER08000E: The P-VOL is a Cache Residency LU. Check the status of the LU.

DMER08000F: The S-VOL is a Cache Residency LU. Check the status of the LU.


DMER080011: The S-VOL is reserved as a Cache Residency LU. Check the status of the LU.

DMER080012: The P-VOL is a command device. Check the status of the LU.

DMER080013: The S-VOL is a command device. Check the status of the LU.

DMER080014: The LUNs of the P-VOL and S-VOL are the same. Check the specified

LU.

DMER080016: The specified pair is in a status other than Split, Split Pending and

Failure. Check the pair status.

DMER080017: The LU to be paired with the P-VOL is not an S-VOL. Check the specified LU.

DMER080018: The LUN of the P-VOL is higher than 512 (1,023). Make sure of the number of the specified paired LU.

DMER080019: The LUN of the S-VOL is higher than 512 (1,023). Make sure of the number of the specified paired LU.

DMER08001A: The primary sequence number is different from the own Array ID.

Check the Array ID.

DMER08001B: The secondary sequence number is different from the own Array ID.

Check the Array ID.

DMER08001C: The primary port number is not supported. Check the specified port number.



Error

Code

508001d

Description

508001f

5080020

5080021

5080022

5080023

5080024

5080026

5080027

5080028

5080029

508002a

508002b

508002c

508002d

508002e

508002f

5080030

5080031

5080032

5080033

5080034

5080035

5080036

DMER08001D: The secondary port number is not supported. Check the specified port number.

DMER08001F: The S-VOL is a volume of ShadowImage and in the pair status of

Simplex or Failure. Check the pair status of the LU.

DMER080020: The LU to be paired with the P-VOL is not an S-VOL. Check the specified LU.

DMER080021: The status of the P-VOL is other than normal and regressive. Check the status of the LU.

DMER080022: The status of the S-VOL is other than normal and regressive. Check the status of the LU.

DMER080023: The P-VOL is a Sub LU of a unified LU. Check the status of the LU.

DMER080024: The S-VOL is a Sub LU of a unified LU. Check the status of the LU.

DMER080026: The P-VOL has been set to the current Cache Residency LU. Check the status of the LU.

DMER080027: The S-VOL has been set to the current Cache Residency LU. Check the status of the LU.


DMER080029: The S-VOL is reserved as a Cache Residency LU. Check the status of the LU.

DMER08002A: The P-VOL is defined as a command device. Check the status of the

LU.

DMER08002B: The S-VOL is defined as a command device. Check the status of the

LU.

DMER08002C: The LUNs of the P-VOL and S-VOL are the same. Check the specified

LU.

DMER08002D: The number of the LU to be paired is different. Check the specified

LUN.

DMER08002E: The number of the LU to be paired is different. Check the specified

LUN.

DMER08002F: The pair status of the P-VOL/S-VOL is other than Simplex, Paired,

Paired Internally Synchronizing and Synchronizing. Check the pair status of the LU.

DMER080030: The LUN of the P-VOL is beyond the limits of support. Check the specified LUN.

DMER080031: The LUN of the S-VOL is beyond the limits of support. Check the specified LUN.

DMER080032: The pair attribute of the LU specified for a P-VOL is not a P-VOL.

Check the specified LUN.

DMER080033: The number of the LU to be paired is different. Check the specified

LUN.

DMER080034: The primary sequence number is different from the Array ID. Check the specified primary sequence number.

DMER080035: The secondary sequence number is different from the Array ID.

Check the specified secondary sequence number.

DMER080036: The primary port number is beyond the limits of support. Check the specified primary port number.



Error

Code

5080037

Description

5080038

5080039

508003a

508003b

508003c

508003d

508003e

508003f

5080046

5080047

5080048

508004b

508004c

508004d

508004e

508004f

5080050

5080051

5080052

5080053

508005e

508005f

5080060

5080061

DMER080037: The secondary port number is beyond the limits of support. Check the specified secondary port number.

DMER080038: A pair in the Failure (S-VOL Switch) status received an instruction to restore. Request that service personnel replace the drives that compose the P-VOL.

Format them after the replacement then resynchronize them.

DMER080039: The specified pair is in the Failure (S-VOL Switch) status. Request that service personnel replace the drives that compose the P-VOL. Format them after the replacement and then resynchronize them.

DMER08003A: The pair in the Failure (S-VOL Switch) status is undergoing resynchronization. Wait until the resynchronization is completed.

DMER08003B: The pair in the Failure (S-VOL Switch) status is undergoing resynchronization. Wait until the resynchronization is completed.

DMER08003C: The group ID is out of appropriate range. Make sure of the specified group ID number.

DMER08003D: The number of pairs having the same group ID exceeded 32. Make sure of the specified group ID number.

DMER08003E: The specified P-VOL/S-VOL is not specified to be grouped(Group ID suspension). Check the pair status of the LU.

DMER08003F: A pair that is in a status other than Paired or Paired Internally

Synchronizing is included in the specified group. Check the pair status of LU in the group.



DMER080048: The DM-LU was specified as S-VOL. Check the status of the LU.

DMER08004B: The DM-LU is not set. Retry after setting the DM-LU.

DMER08004C: The DM-LU was specified as P-VOL. Check the status of the LU.

DMER08004D: The DM-LU was specified as S-VOL. Check the status of the LU.

DMER08004E: Validity of the license expired. Purchase the license.


DMER080050: An LU, for which a change of the cache partition(s) had been reserved, was specified as a P-VOL. Check the status of the LU.

DMER080051: An LU, for which a change of the cache partition(s) had been reserved, was specified as a S-VOL. Check the status of the LU.

DMER080052: An LU, for which a change of the cache partition(s) had been reserved, was specified as a P-VOL. Check the status of the LU.

DMER080053: An LU, for which a change of the cache partition(s) had been reserved, was specified as a S-VOL. Check the status of the LU.

DMER08005E: The specified P-VOL is a Remote Replication pair. Check the status of the LU.

DMER08005F: The specified S-VOL is a Remote Replication pair. Check the status of the LU.

DMER080060: The specified P-VOL is a Remote Replication pair. Check the status of the LU.

DMER080061: The specified S-VOL is a Remote Replication pair. Check the status of the LU.



Error

Code

5080064

Description

5080065

5080066

5080067

5080068

5080069

508006a

508006b

508006c

508006d

508006e

508006f

5080070

5080071

5080072

5080073

5080074

5080075

5080077

5080078

5080079

5080080

DMER080064: The specified MU# is used within the specified P-VOL. Check the specified MU number.

DMER080065: One or more volumes of Paired/Synchronizing/Reverse Synchronizing are under the specified P-VOL. Check the pair status of the LU.

DMER080066: One or more volumes of special Failure are under the specified P-

VOL. Check the pair status of the LU.

DMER080067: One or more Failure pairs that are not readable/writable (Failure transition due to a failure during restoration) under the specified P-VOL. Check the pair status of the LU.

DMER080068: The group ID overlaps within the specified P-VOL at the time of creating the pair of which the group is specified. Make sure of the specified group ID number.

DMER080069: The pair attribute of the specified P-VOL is not a P-VOL or the pair attribute of the specified S-VOL is not a S-VOL. Check the pair attribute of the LU.

DMER08006A: The specified MU# and the MU# of the specified S-VOL are mismatched. Check the specified MU number.

DMER08006B: One or more volumes of Paired/Synchronizing/Reverse Synchronizing are under the specified P-VOL. Check the pair status of the LU.

DMER08006C: One or more Failure pairs that are not readable/writable (Failure transition due to a failure during the restoration) under the specified P-VOL. Check the pair status of the LU.

DMER08006D: The pair attribute of the specified P-VOL is not a P-VOL or the pair attribute of the specified S-VOL is not a S-VOL. Check the pair attribute of the LU.

DMER08006E: The specified MU# and the MU# of the specified S-VOL are mismatched. Check the specified MU number.

DMER08006F: The specified MU# and the MU# of the specified S-VOL are mismatched. Check the specified MU number.

DMER080070: The specified MU# is used within the specified P-VOL. Check the specified MU number.

DMER080071: One or more volumes of Paired/Synchronizing/Reverse Synchronizing are under the specified P-VOL. Check the pair status of the LU.

DMER080072: One or more volumes of special Failure are under the specified P-

VOL. Check the pair status of the LU.

DMER080073: One or more Failure pairs that are not readable/writable (Failure transition due to a failure during the restoration) under the specified P-VOL. Check the pair status of the LU.

DMER080074: The specified MU# and the MU# of the specified S-VOL are mismatched. Check the specified MU number.




DMER080078: The specified S-VOL is the reserved LU. Check the status of the LU.

DMER080079: The specified S-VOL is undergoing the migration and its status is Split or Failure. Check the pair status of the LU.

DMER080080: The specified S-VOL is undergoing the migration and its status is

Synchronizing or Split. Check the pair status of the LU.



Error

Code

5080081

Description

5080082

5080083

5080084

5080085

5080086

5080087

5080088

5080089

508008a

508008b

508008c

508008d

508008e

508008f

5080090

5080091

5080092

5080093

5080094

5080095

5080096

5080097

DMER080081: The specified P-VOL is the reserved LU. Check the pair status of the

LU.

DMER080082: The specified S-VOL is the reserved LU. Check the pair status of the

LU.

DMER080083: The specified S-VOL is undergoing the migration and its status is

Synchronizing. Check the pair status of the LU.

DMER080084: The specified volume is undergoing the migration. Check the pair status of the LU.




DMER080087: The disk drives that configure a RAID group, to which the specified S-




DMER080089: The disk drives that configure a RAID group, to which the specified S-


DMER08008A: The disk drives that configure a RAID group, to which the specified P-


DMER08008B: The disk drives that configure a RAID group, to which the specified S-


DMER08008C: When creating a pair specifying a group ID, the specified group ID is already used for a SnapShot pair. Check the specified group ID.

DMER08008D: The S-VOL is a volume of Remote Replication and in a status other than Split and Failure. Check the status of the Remote Replication pair.

DMER08008E: The S-VOL is a volume of another Remote Replication pair. Check the status of the Remote Replication pair.

DMER08008F: An unsupported command option was received. Check the specified value.

DMER080090: The specified P-VOL has been set to a ShadowImage S-VOL. Check the status of the LU.

DMER080091: The specified P-VOL has been set to a ShadowImage S-VOL. Check the status of the LU.









Error

Code

5080098

Description

5080099

508009a

508009b

508009c

508009d

508009e

508009f

50800a0

50800a1

50800a2

50800a3

50800a4

50800a5

50800a6

50800a7

50800a8

50800a9

50800aa

50800ab

DMER080098: An invalid array ID is received when INQUIRY serial number conversion mode is on in the host group where a command device is mapped. Check the type of the remote array.

DMER080099: An invalid array ID is received when INQUIRY serial number conversion mode is on in the host group where a command device is mapped. Check the type of the remote array.

DMER08009A: The Migration status is other than unexecuted. Check the Migration status.

DMER08009B: One or more volumes of Split Pending/Paired Internally

Synchronizing are under the specified P-VOL. Check the pair status of the LU.

DMER08009C: The S-VOL of the specified pair is a part of another Remote

Replication pair. Check the status of the Remote Replication pair.

DMER08009D: One or more volumes of Split Pending/Paired Internally

Synchronizing are under the specified P-VOL. Check the pair status of the LU.

DMER08009E: The specified pair is in the Split Pending status. Retry after the status becomes Split.

DMER08009F: A pair in the Failure (S-VOL Switch) status received an instruction to resynchronize with Quick mode. Request that service personnel to replace the drives that compose the P-VOL. Format them after the replacement then resynchronize them.

DMER0800A0: One or more Failure pairs that are not readable/writable under the specified P-VOL. Check the pair status of the LU.

DMER0800A1: The capacity is beyond the limits of support. Split the unnecessary pairs.

DMER0800A2: The S-VOL of the specified pair is a part of another Remote

Replication pair. Check the status of the Remote Replication pair.

DMER0800A3: The P-VOL or the S-VOL has not undergone the forced restoration by means of parity. Retry after making the restoration by means of parity.

DMER0800A4: The S-VOL is undergoing the forced restoration by means of parity.

Retry after making the restoration by means of parity.

DMER0800A5: The disk drives that configure a RAID group to which the specified P-


DMER0800A6: The disk drives that configure a RAID group to which the specified S-


DMER0800A7: A pair that is in a status other than Paired, Paired Internally

Synchronizing or Synchronizing is included in the specified group. Check the pair status of LU in the group.

DMER0800A8: A pair that shares the P-VOL with another pair that is in Failure status that are not readable/writable is included in the specified group. Check the pair status of LU in the group.

DMER0800A9: The capacity is beyond the limits of support. Split the unnecessary pairs.

DMER0800AA: A pair that the S-VOL has been cascaded with a Remote Replication pair is included in the specified group. Check the status of the Remote Replication pair.

DMER0800AB: A pair that the P-VOL or the S-VOL has not undergone the forced restoration by means of parity is included in the specified group. Retry after making the restoration by means of parity.



Error

Code

50800ac

Description

50800ad

50800ae

50800af

50800b0

50800b1

50800b2

50800b3

50800b4

50800b5

50800b6

50800b7

50800b8

50800b9

50800ba

50800bb

50800bc

50800bd

50800be

50800bf

50800c0

DMER0800AC: A pair that the S-VOL is undergoing the forced restoration by means of parity is included in the specified group. Retry after making the restoration by means of parity.

DMER0800AD: A pair that the P-VOL belongs a RAID group configured by the disk drives that have been spun down is in the specified group. Check the status of the

RAID group.

DMER0800AE: A pair that the S-VOL belongs a RAID group configured by the disk drives that have been spun down is in the specified group. Check the status of the

RAID group.

DMER0800AF: One or more volumes of Split Pending/Paired Internally Synchronizing are under the specified P-VOL. Check the pair status of the LU.

DMER0800B0: The P-VOL or the S-VOL of the specified pair is a volume of another

Remote Replication pair. Check the status of the Remote Replication pair.

DMER0800B1: The specified pair is in the Split Pending status. Check the pair status of the LU.

DMER0800B2: The RAID group to which the specified LU belongs indicates a status other than Normal. Retry after the status becomes Normal.

DMER0800B3: An LU that belongs to the RAID group that indicates a status other than Normal is included in the specified group. Retry after the RAID group status becomes Normal.

DMER0800B4: The specified pair is in a status other than Split and Failure. Check the pair status.

DMER0800B5: The LU that was specified as P-VOL does not exist. Check the specified LUN.

DMER0800B6: The LU that was specified as P-VOL does not exist. Check the specified LUN.

DMER0800B7: The LU that was specified as S-VOL does not exist. Check the specified LUN.

DMER0800B8: The LU that was specified as S-VOL does not exist. Check the specified LUN.

DMER0800B9: DP pool is insufficient. Confirm the capacity of DP pool.

DMER0800BA: DP pool is insufficient. Confirm the capacity of DP pool.

DMER0800BB: DP pool is insufficient. Confirm the capacity of DP pool.

DMER0800BC: DP pool is insufficient. Confirm the capacity of DP pool.

DMER0800BD: The specified P-VOL is a volume of Remote Replication pair and the specified S-VOL is an LU created in DP pool. Specify an LU other than the LU created in DP pool to S-VOL.

DMER0800BE: The specified P-VOL is a volume of Remote Replication pair and the specified S-VOL is an LU created in DP pool. Specify an LU other than the LU created in DP pool to S-VOL.

DMER0800BF: The specified S-VOL is an LU created in DP pool and the specified P-

VOL already has a pair whose S-VOL is a part of remote replication pair. Retry after deleting the remote replication pair.

DMER0800C0: The specified S-VOL is an LU created in DP pool and the specified P-

VOL already has a pair whose S-VOL is a part of remote replication pair. Retry after deleting the remote replication pair.



Error

Code

50800c1

Description

50800c2

50800c3

50800c4

50800c5

50800c6

50800c7

50800c8

50800c9

50800ca

50800cb

50800cc

5090001

5090002

5090003

5090004

5090005

5090006

5090007

5090009

509000a

509000b

509000c

509000d

DMER0800C1: The DP optimization status of the specified P-VOL is not Normal.

Check the DP optimization status of the P-VOL.

DMER0800C2: The DP optimization status of the specified S-VOL is not Normal.

Check the DP optimization status of the S-VOL.

DMER0800C3: The DP optimization status of the specified P-VOL is not Normal.

Check the DP optimization status of the P-VOL.

DMER0800C4: The DP optimization status of the specified S-VOL is not Normal.

Check the DP optimization status of the S-VOL.

DMER0800C5: Management information regarding DP is being updated. Retry after waiting for a while.




DMER0800C9: The specified P-VOL can not be read due to insufficient capacity of its

DP pool. Check the capacity of the DP pool.

DMER0800CA: The specified P-VOL can not be read due to insufficient capacity of its


DMER0800CB: The specified S-VOL can not be read due to insufficient capacity of its


DMER0800CC: The specified P-VOL can not be read due to insufficient capacity of its


DMER090001: The specified P-VOL is normal or other than regressed. Check the status of the LU.


Check the attribute of the LU.

DMER090003: The specified P-VOL has been set to the reserved Cache Residency

LU. Check the attribute of the LU.

DMER090004: The specified P-VOL has been defined to the command device. Check the attribute of the LU.

DMER090005: The accepted sequence number is different from the Array ID. Check the Array ID.


DMER090007: The specified P-VOL is a Sub LU of a unified LU. Check the attribute of the LU.

DMER090009: The status of the Remote Replication pair of the specified P-VOL is other than Simplex. Check the pair status of the LU.

DMER09000A: The specified P-VOL is a ShadowImage pair. Check the attribute of the LU.

DMER09000B: The specified P-VOL is a SnapShot V-VOL. Check the attribute of the

LU.

DMER09000C: The group ID is beyond the limits of support. Check the group ID.

DMER09000D: The pair status of the specified P-VOL is other than Split or Failure.

Check the pair status of the LU.



Error

Code

509000e

Description

509000f

5090010

5090011

5090012

5090013

5090014

5090015

5090016

5090017

5090018

5090019

5090020

5090021

5090022

5090023

5090025

5090026

5090027

5090029

509002a

509002b

509002c

509002d

5090030

DMER09000E: The specified P-VOL status is normal or other than regressed. Check the status of the LU.

DMER09000F: The specified S-VOL is not a pair target LUN. Check the LUN of the S-

VOL.



DMER090012: When the unit of pair is specified, the pair status of the specified P-

VOL is other than Synchronizing and Paired. Check the pair status of the LU.




DMER090016: When the unit of pair is specified, the specified S-VOL is not a pair target LUN. Check the LUN of the specified S-VOL.


DMER090018: The S-VOL pair cancellation instructions was issued to the P-VOL or pair cancellation instructions was issued to the S-VOL. Check the pair attribute of the LU.

DMER090019: The internal transaction which are splitting or deleting for SnapShot is working now. Retry after waiting for a while.

DMER090020: The pool LU is not defined. Define the pool LU and retry.

DMER090021: The specified fence level is STATUS. Make sure of the specified fence level.


DMER090023: The internal pair status of the specified P-VOL is [under pair deletion]. Check the pair status of the LU.

DMER090025: The forced blockade of a P-VOL was accepted. The forced blockade of a P-VOL is not supported.

DMER090026: The type of the side file release is other than ordinary splitting. Check the specified value.

DMER090027: The S-VOL received an instruction. Check the pair attribute of the LU.


DMER09002A: The P-VOL received an instruction. Check the pair attribute of the LU.

DMER09002B: When the unit of pair is specified, the pair status of the specified S-

VOL is Simplex or Synchronizing. Check the pair status of the LU.

DMER09002C: The accepted sequence number is different from the Array ID. Check the Array ID.

DMER09002D: The specified MU number is beyond the limits (0 to13) of support.

Check the specified MU number.




Error

Code

5090032

Description

5090036

5090037

5090038

5090039

509003a

509003c

509003d

509003e

509003f

5090042

5090044

5090045

5090046

5090047

5090048

5090049

509004b

509004c

509004d

DMER090032: The RAID group, to which the specified P-VOL belongs, is RAID 0.


DMER090036: The specified P-VOL is a SnapShot P-VOL and it is being restored.

Check the pair status of the SnapShot.

DMER090037: The specified P-VOL is a SnapShot P-VOL and its status was changed to Failure during restoration. Check the pair status of the SnapShot.

DMER090038: There is no vacancy in the generation bits. Retry after waiting for a while.

DMER090039: There is one or more pair(s) in the status of [under execution of remote SnapShot split] in the target group. Check the pair status of each LU in the target group. It is required to wait until the process is completed.

DMER09003A: There is one or more pair(s) in the status of [under pair splitting] in the target group. Check the pair status of each LU in the target group. It is required to wait until the process is completed.

DMER09003C: There is one or more pair(s) in the status of [under pair deletion] in the target group. Check the pair status of each LU in the target group. It is required to wait until the process is completed.

DMER09003D: The specified P-VOL is a SnapShot P-VOL and it is being restored.

Check the pair status of the SnapShot.

DMER09003E: The specified P-VOL is a SnapShot P-VOL and its status was changed to Failure during restoration. Check the pair status of the SnapShot.

DMER09003F: There is no pair, which is in the Paired status, in the target group.

Check the pair status of each LU in the target group.

DMER090042: When the unit of pair is specified, the pair status of the specified pair is Split (no reading/writing allowed). Check the pair status.

DMER090044: When the unit of group is specified, there is one or more pair(s) placed in the Split status (no reading/writing allowed) in the group. Check the pair status of each LU in the target group.

DMER090045: When the unit of group is specified, there is no pair that is in the

Paired, Split, or Failure status in the group. Check the pair status of each LU in the target group.

DMER090046: When the unit of pair is specified, the internal status of the pair of the specified P-VOL is [under pair splitting]. Check the pair status of the LU. It is required to wait until the process is completed.

DMER090047: The specified P-VOL has the incomplete DDCB. Check the status of the LU.

DMER090048: The specified P-VOL has unwritten data. Contact the service personnel.

DMER090049: When the unit of pair is specified, the internal status of the pair of the specified P-VOL is [under pair deletion]. Check the pair status of the LU. It is required to wait until the process is completed.

DMER09004B: When the unit of pair is specified, the internal status of the pair of the specified P-VOL is [under execution of remote SnapShot split]. Check the pair status of the LU. It is required to wait until the process is completed.

DMER09004C: When the unit of group is specified, there is one or more pair(s) that is in the status of [under pair splitting] in the group. Check the pair status of each

LU in the target group.

DMER09004D: The DM-LU is not defined. Define the DM-LU.



Error

Code

509004e

Description

509004f

5090050

5090052

5090053

5090054

5090055

5090057

5090059

509005a

509005c

509005e

5090068

5090069

509006b

509006c

509006d

509006e

509006f

5090070

5090071

DMER09004E: The specified P-VOL has been set to the DM-LU. Check the attribute of the LU.


DMER090050: When the unit of group is specified, there is one or more pair(s) that is in the status of [under pair deletion] in the group. Check the pair status of each


DMER090052: When the unit of group is specified, there is one or more pair(s) that is in the status of [under execution of remote SnapShot split] in the group. Check the pair status of each LU in the target group.


Synchronizing or Paired status, in the target group. Check the pair status of each LU in the target group.

DMER090054: The pair cancellation instructions was executed for the range that was not supported. Check the specified value.

DMER090055: When the unit of pair is specified, the internal status of the pair of the specified P-VOL is [under pair splitting]. Check the pair status of the LU. It is required to wait until the process is completed.

DMER090057: When the unit of pair is specified, the internal status of the pair of the specified P-VOL is [under execution of remote SnapShot split]. Check the pair status of the LU. It is required to wait until the process is completed.

DMER090059: When the unit of pair is specified, the internal status of the pair of the specified S-VOL is Busy. Check the pair status of the LU.

DMER09005A: When the unit of group is specified, there is one or more pair(s) that is in the status of [under pair splitting] in the group. Check the pair status of each


DMER09005C: When the unit of group is specified, there is one or more pair(s) that is in the status of [under execution of remote SnapShot split] in the group. Check the pair status of each LU in the target group.

DMER09005E: When the unit of group is specified, there is one or more pair(s) placed in the Busy status in the group. Check the pair status of each LU in the target group.

DMER090068: There is the S-VOL pair whose direction is not correct in the indicated group. Check the group ID.

DMER090069: The partition to which the LU belongs is being changed to the other directory. Retry after waiting for a while.

DMER09006B: There is no pair, which is in the Paired status, in the target group.


DMER09006C: The subsystem has not been rebooted after the Remote Replication option was unlocked. Reboot the subsystem.

DMER09006D: The specified P-VOL is a unified LU including an LU with a capacity less than 1 GB. Check the attribute of the LU.

DMER09006E: The specified P-VOL is the pool LU. Check the attribute of the LU.

DMER09006F: The pool LU status is normal or other than regressed. Check the status of the pool LU.

DMER090070: The pool LU is undergoing the forced parity correction. Check the status of the pool LU.


Replication and SnapShot pairs. Delete unnecessary pairs.



Error

Code

5090072

Description

5090073

5090074

5090075

5090076

5090077

5090078

509007b

509007c

509007d

509007e

509007f

5090080

5090081

5090082

5090083

5090084

5090085

5090086

5090087

5090088

DMER090072: The remote SnapShot split request was accepted. Check the firmware version.

DMER090073: The pair status of the specified S-VOL does not allow you to create a pair. Check the pair status of the specified S-VOL on both local and remote arrays.

DMER090074: The suspension command was accepted with a specification of the unit of pair. The specification of the unit of pair is not supported.

DMER090075: The specified P-VOL is a unified LU whose component LUs include an

LU for which the format operation is being performed. Check the attribute of the LU.

DMER090076: The specified P-VOL is being formatted. Check the attribute of the LU.

DMER090077: The state of the forced parity correction for the specified P-VOL is

Uncorrected or Uncorrected 2. Check the status of the LU.

DMER090078: The specified P-VOL has not undergone the forced parity correction.

Retry it after executing the forced parity correction.

DMER09007B: There is one or more pair(s) in the status of Split or Failure of [under pair deletion] in the target group. Check the pair status of the LU. It is required to wait until the process is completed.

DMER09007C: The internal transaction which are splitting or deleting for SnapShot is working now. Retry after waiting for a while.

DMER09007D: The pool LU status is normal or other than regressed. Check the status of the pool LU.

DMER09007E: The pool LU is undergoing the forced parity correction. Retry after waiting for a while.

DMER09007F: There is one or more P-VOL(s), the status of the forced parity correction for which is Uncorrected or Uncorrected 2, in the target group. Check the status of each LU in the target group.

DMER090080: There is one or more P-VOL(s), status is normal or other than regressed, in the target group. Check the status of each LU in the target group.

DMER090081: There is one or more Remote Replication P-VOL(s), which is cascaded with a SnapShot P-VOL being restored, in the target group. Check the status of each


DMER090082: There is one or more Remote Replication P-VOL(s), which is cascaded with a SnapShot P-VOL that was placed in the Failure status during restoration, in the target group. Check the status of each LU in the target group.

DMER090083: There is no pair, which is in the Split or Failure status, in the target group. Check the pair status of each LU in the target group.

DMER090084: When a pair is created in the new group, the cycle time that has been set is less than [30 x number of groups] seconds. Check the cycle time that has been set.

DMER090085: When the unit of pair is specified, the S-VOL of the target pair has not completed the resynchronization after it accepted the resynchronization command. Check the Remote Replication pair status of the remote array.

DMER090086: When the unit of group is specified, there is one or more S-VOL(s), which has not completed the resynchronization after it accepted the resynchronization command, in the target group. Check the Remote Replication pair status of the remote array.

DMER090087: There are one or more pairs in the status of [under pair splitting] or

[under pair competing] in the group. Retry after waiting for a while.




Error

Code

5090089

Description

509008a

509008b

509008c

509008d

509008e

509008f

5090090

5090091

5090092

5090093

5090094

5090095

5090096

5090097

5090098

5090099

509009a

509009b

509009c

509009d


DMER09008A: The disk drives that configure a RAID group, to which the specified P-


DMER09008B: The disk drives that configure a RAID group, to which the specified P-


DMER09008C: There are one or more Remote Replication P-VOLs corresponding to a

RAID group that belongs to the group concerned and the disk drives that configure the RAID group have been spun down. Check the status of the RAID group.

DMER09008D: The primary pool ID is beyond the limits of supported. Check the pool ID.

DMER09008E: The secondary pool ID is beyond the limits of supported. Check the pool ID.

DMER09008F: The specified pool ID differs from the pool ID in use. Check the pool

ID.

DMER090090: Swap pair has been issued to the Remote Replication pair with

AMS500 or AMS1000. The swap command is not supported in this configuration.

DMER090091: The Swap operation was received in the P-VOL. Check the pair attribute of the LU.

DMER090092: The Swap operation was received by specifying the pair unit. Please confirm the operation and try again.

DMER090093: The LU whose pair status is not Takeover exists in the target group.


DMER090094: The LU whose pair status is Busy exists in the target group. Check the pair status of each LU in the target group.

DMER090095: There is a pair that is a status of Takeover and also deleted just in the Local Array in the group. Delete the pair, that is a status of Takeover in the group, not only in the Local Array but also in the Remote Array. Then execute again.

DMER090096: The internal transaction which are splitting or deleting for SnapShot is working now. Retry after waiting for a while.

DMER090097: The pool LU status is normal or other than regressed. Check the status of the pool LU.

DMER090098: The pool LU is undergoing the forced parity correction. Check the status of the pool LU.

DMER090099: There is one or more S-VOL(s), the status of the forced parity correction for which is Uncorrected or Uncorrected 2, in the target group. Check the status of each LU in the target group.

DMER09009A: There is one or more S-VOL(s), status is normal or other than regressed, in the target group. Check the status of each LU in the target group.

DMER09009B: There is one or more Remote Replication S-VOL(s), which is cascaded with a SnapShot P-VOL being restored, in the target group. Check the status of each


DMER09009C: There is one or more Remote Replication S-VOL(s), which is cascaded with a SnapShot P-VOL that was placed in the Failure status during restoration, in the target group. Check the status of each LU in the target group.

DMER09009D: There exists an S-VOL of a Remote Replication pair, the RAID group which belongs to is in Power Saving mode. Check the status of LUs in the group.



Error

Code

509009e

509009f

50900a0

50900a1

50900a2

50900a3

50900a4

50900a5

50900a6

50900a7

50900a8

50a0001

50a0002

50a0003

50a0004

50a0005

50a0006

50a0007

50a0008

50a0009

Description

DMER09009E: The firmware internal error occurred. Retry after waiting for a while.


DMER09009F: The specified secondary sequence number does not match with the remote side subsystem serial number. Check the specified command device number.

DMER0900A0: The command cannot execute because the Auto Migration is undergoing. Check the Migration status.




DMER0900A4: An LU that belongs to the RAID group that indicates a status other than Normal is included in the data pool that is specified when the pair operation or used by specified pair. Retry after the RAID group status becomes Normal.

DMER0900A5: An LU that belongs to the RAID group that indicates a status other than Normal is included in the group to which the specified pair belongs. Retry after the RAID group status becomes Normal.

DMER0900A6: An LU that belongs to the RAID group that indicates a status other than Normal is included in the data pool that is used by pairs that belong to the same group as the specified pair. Retry after the RAID group status becomes

Normal.

DMER0900A7: The LU created in DP pool was specified as P-VOL. Specify an LU other than the LU created in DP pool.


DMER0A0001: The Volume Migration optional feature is invalid. Install the Volume

Migration optional feature.

DMER0A0002: The temporary key of the Volume Migration was expired. Purchase the license.

DMER0A0003: The status of the specified P-VOL is other than normal and regressive. Check the status of the LU.

DMER0A0004: The status of the specified S-VOL is other than normal and regressive. Check the status of the LU.

DMER0A0005: The status of the parity correction of the specified P-VOL is

Uncorrected or Uncorrected 2. Skip the parity correction or execute the parity correction, and wait for the completion of the correction. Re-execute it after performing the operation.

DMER0A0006: The status of the parity correction of the specified S-VOL is correcting, waiting correction, Uncorrected, or Uncorrected 2. Skip the parity correction or execute the parity correction, and wait for the completion of the correction. Re-execute it after performing the operation.

DMER0A0007: The specified P-VOL has created a Volume Migration pair. Check the pair status of the LU.

DMER0A0008: The specified S-VOL has created a Volume Migration pair. Check the pair status of the LU.

DMER0A0009: The specified P-VOL has created a ShadowImage pair. Check the pair status of the LU.



Error

Code

50a000a

50a000b

50a000c

50a000d

50a000e

50a000f

50a0010

50a0011

50a0012

50a0013

50a0014

50a0015

50a0016

50a0017

50a0018

50a0019

50a001a

50a001b

50a001c

50a001d

50a001e

50a001f

50a0020

50a0021

50a0022

Description

DMER0A000A: The specified S-VOL has created a ShadowImage pair. Check the pair status of the LU.

DMER0A000B: The specified P-VOL is a command device. Check the status of the

LU.

DMER0A000C: The specified S-VOL is a command device. Check the status of the

LU.

DMER0A000D: The specified P-VOL has created a Remote Replication pair. Check the pair status of the LU.

DMER0A000E: The specified S-VOL has created a Remote Replication pair. Check the pair status of the LU.

DMER0A000F: The specified P-VOL has created a Remote Replication pair. Check the pair status of the LU.

DMER0A0010: The specified S-VOL has created a Remote Replication pair. Check the pair status of the LU.

DMER0A0011: The P-VOL is a Cache Residency LU or has been set to the reserved

Cache Residency LU. Check the status of the LU.

DMER0A0012: The S-VOL is a Cache Residency LU or has been set to the reserved


DMER0A0013: The specified P-VOL has created a SnapShot pair. Check the pair status of the LU.

DMER0A0014: The specified S-VOL has created a SnapShot pair. Check the pair status of the LU.

DMER0A0015: The specified P-VOL is the pool LU. Check the pair status of the LU.

DMER0A0016: The specified S-VOL is the pool LU. Check the pair status of the LU.

DMER0A0017: The specified P-VOL is being formatted. Retry after the formatting is completed.

DMER0A0018: The specified S-VOL is being formatted. Retry after the formatting is completed.

DMER0A0019: The specified P-VOL is the DM-LU. Check the status of the LU.

DMER0A001A: The specified S-VOL is the DM-LU. Check the status of the LU.

DMER0A001B: The DM-LU is not set. Retry after setting the DM-LU.

DMER0A001C: The specified P-VOL has unwritten data. Check the status of the LU.

DMER0A001D: The pair cannot be allocated the differential bit map. Split the unnecessary pairs.

DMER0A001E: The specified P-VOL is a SubLU of a unified LU. Check the status of the LU.

DMER0A001F: The specified S-VOL is a SubLU of a unified LU. Check the status of the LU.

DMER0A0020: The size of the specified P-VOL and the S-VOL are not the same.

Specify an LU that the same size.

DMER0A0021: The DIRs in charge of the specified P-VOL and the S-VOL are not the same. Specify an LU that belongs to the same DIR.

DMER0A0022: The LUNs of the specified P-VOL and S-VOL are the same. Check the specified LUN.



Error

Code

50a0023

Description

50a0024

50a0025

50a0026

50a0027

50a0028

50a0029

50a002c

50a002d

50a002e

50a002f

50a0030

50a0031

50a0032

50a0033

50a0034

50a0035

50a0036

5810001

5810002

5810003

5810004

581000a

581000f

581002c

DMER0A0023: There exist maximum number of pairs already (included

ShadowImage pairs). Split the unnecessary pairs.

DMER0A0024: The specified P-VOL is the LU, for which a change of the cache partition(s) had been reserved. Retry after releasing the reserved status.

DMER0A0025: The specified S-VOL is the LU, for which a change of the cache partition(s) had been reserved. Retry after releasing the reserved status.

DMER0A0026: The RAID group of the specified P-VOL and S-VOL are the same.

Specify a different RAID group.

DMER0A0027: The specified P-VOL is the reserved LU. Check the status of the LU.

DMER0A0028: The specified S-VOL is the reserved LU. Check the status of the LU.

DMER0A0029: The access level of the specified S-VOL is other than the ordinary one. Check the access revel of the LU.

DMER0A002C: The specified MU number is 8 or higher. Make sure of the specified

MU number.

DMER0A002D: The specified primary port number is beyond the limits of support.

Check the specified primary port number.

DMER0A002E: The specified secondary port number is beyond the limits of support.

Check the specified secondary port number.

DMER0A002F: The specified primary sequence number is different from the own

Array ID. Check the specified primary sequence number.

DMER0A0030: The specified secondary sequence number is different from the own

Array ID. Check the specified secondary sequence number.

DMER0A0031: The pair concerned is the one that the instruction to start the migration was issued by Navigator etc. Check the owner ID of the specified pair.

DMER0A0032: The disk drives that configure a RAID group, to which the specified P-


DMER0A0033: The disk drives that configure a RAID group, to which the specified S-


DMER0A0034: The Migration status is [data is being copied], [data copy fails], or

[data copy is completed]. Check the Migration status.

DMER0A0035: The Migration status is [access path is being switched] or [access path switching fails]. Check the Migration status.


DMER810001: Both of the two paths of the remote array were detached. Check the status of the path.




DMER81000A: The remote array is receiving a command. Retry after waiting for a while.

DMER81000F: The path of the remote array was detached. Check the status of the path.

DMER81002C: The process is in progress. Retry after waiting for a while.



Error

Code

581002d

Description

581002e

581002f

5810030

5810031

5810033

5810034

5810035

5810036

5810037

5810038

5810039

581003a

581003e

5810042

5810058

5810060

5810061

5810062

5810063

58100d4

58100d9

58100e0

DMER81002D: The S-VOL of the remote array is being formatted. Retry after waiting for a while.

DMER81002E: The remote array is undergoing the pseudo deliberate shutdown.

Retry after the pseudo deliberate shutdown is completed.

DMER81002F: The remote array has undergone the pseudo deliberate shutdown.


DMER810030: The S-VOL is undefined. Check the attribute of the LU.

DMER810031: The WWN of the remote array is illegal. Check the equipment WWN.

DMER810033: The remote array is undergoing hot replacement of the firmware.


DMER810034: A command error occurred. Retry after waiting for a while.

DMER810035: The optional feature of Remote Replication of the remote array is invalid. Unlock and validate the optional feature.

DMER810036: The process is in progress. Retry after waiting for a while. In case that the RAID group to which the LU that will be S-VOL belongs indicate a status other than Normal, retry after the status becomes Normal.

DMER810037: The remote array is busy. Retry after checking the pair status of the

LU, Array ID, number of the connected arrays, and CTG number.



DMER81003A: The remote array is busy. Retry after waiting for a while.

DMER81003E: The S-VOL command is receiving a command. Retry after waiting.

DMER810042: The capacity is beyond the limits of support. Eliminate unnecessary pairs of the remote array.

DMER810058: The ShadowImage P-VOL of the remote array is in the Failure (S-VOL

Switch) status. Contact the service personnel.

DMER810060: The path of the local subsystem is abnormal. Check the status of the path.




DMER8100D4: The LU which has been indicated as S-VOL in the remote subsystem is P-VOL now. Confirm the LU status in the remote subsystem.

DMER8100D9: The status of the remote array is in an inappropriate condition to operate the Remote Replication pair. Confirm the Array ID, pair status of Local and

Remote Replication and the status of the RAID group to which the target LU belongs. Retry after waiting the RAID group status becomes Normal in case that the

RAID group indicate a status other than Normal.

DMER8100E0: Auto Migration is being executed in the remote array. Execute again after the Migration is completed.



Error

Code

58100e5

Description

58100e8

5811001

5811002

5811003

5811004

581100a

581100f

581102c

581102d

581102e

581102f

5811030

5811031

5811033

5811034

5811035

5811036

5811037

5811038

5811039

581103a

581103e

5811042

5811058

DMER8100E5: The RAID group to which the LU that will be specified to S-VOL of the remote array belongs indicates a status other than Normal. Retry after the status becomes Normal.

DMER8100E8: The remote array is executing a pair operation with another array.

Retry after the pair operation is completed with another array.














DMER811031: The WWN of the remote array is illegal. Check the remote array

WWN.





DMER811036: The process is in progress. Retry after waiting for a while. In case that the RAID group to which the LU that will be S-VOL belongs indicate a status other than Normal, retry after the status becomes Normal.






DMER81103E: The S-VOL command is receiving a command. Retry after waiting for a while.

DMER811042: The capacity is beyond the limits of support. Delete unnecessary pairs of the remote array.





Error

Code

58110d4

Description

58110e0

58110e5

58110e8

5812001

5812002

5812003

5812004

581200a

581200f

581202c

581202d

581202e

581202f

5812030

5812031

5812033

5812034

5812035

5812036

5812037

5812038

5812039

581203a

581203e




















WWN.





DMER812036: The process is in progress. Retry after waiting for a while. In case that the RAID group to which the S-VOL belongs indicate a status other than

Normal, retry after the status becomes Normal.









Error

Code

58120d4

Description

58120e0

58120e5

58120e8

5813001

5813002

5813003

5813004

581300a

581300f

581301e

581302c

581302d

581302e

581302f

5813030

5813031

5813033

5813034

5813035

5813036

5813037

5813038

5813039



DMER8120E5: The RAID group to which the S-VOL of the remote array belongs indicates a status other than Normal. Retry after the status becomes Normal.









DMER81301E: The object LU has been organized into a Remote Replication pair or the RAID group to which the object LU belongs indicates a status other than Normal.

Check the pair status of the LU and the RAID group status. Retry after the RAID group status becomes Normal in case that the RAID group indicate a status other than Normal.









WWN.













Error

Code

581303a

581303e

58130d4

58130d9

58130de

58130e0

58130e2

58130e3

58130e5

58130e8

5814001

5814002

5814003

5814004

581400a

581400f

581401e

581402c

581402d

581402e

581402f

5814030

5814031

Description





Remote Replication and the status of the RAID group to which the target LU belongs. Retry after waiting the RAID group status becomes Normal in case that the

RAID group indicate a status other than Normal.

DMER8130DE: Auto Migration is being executed in the remote array. Execute again after the Migration is completed.


DMER8130E2: The remote array is executing Auto Migration. Retry after the Auto

Migration is completed.












Check the pair status of the LU and the RAID group status. Retry after the RAID group status









WWN.



Error

Code

5814033

Description

5814034

5814035

5814036

5814037

5814038

5814039

581403a

581403e

58140d4

58140d9

58140de

58140e0

58140e2

58140e3

58140e5

58140e8

5815001

5815002

5815003

5815004

581500a

581500f

581502c















Remote Replication and the status of the RAID group to which the target LU belongs. Retry af


















Error

Code

581502d

Description

581502e

581502f

5815030

5815031

5815033

5815034

5815035

5815036

5815037

5815038

5815039

581503a

581503e

58150d4

58150e0

58150e5

58150e8

5816022

5816023

5816024

5816025

5816026

5816027

5816028

5816029


DMER81502E: The remote arrayis undergoing the pseudo deliberate shutdown.






WWN.







DMER815037: The remote array is busy. Retry after waiting for a while.













DMER816025: The S-VOL of the remote subsystem is being formatted. Retry after waiting for a while.

DMER816026: The remote subsystem is undergoing the pseudo deliberate shutdown. Retry after the pseudo deliberate shutdown is completed.

DMER816027: The remote subsystem has undergone the pseudo deliberate shutdown. Retry after waiting for a while.

DMER816028: The pair operation commands are being executed in the remote subsystem. Wait a while and execute again.




Error

Code

581602a

Description

581602b

581602c

581602d

581602e

581602f

5816030

5816031

5816032

5816033

5816035

5816038

5816041

5816042

5816086

5816087

5816088

5816089

581608a

581608b

581608c

581608d

DMER81602A: The optional feature of Remote Replication of the remote subsystem is invalid. Unlock and validate the optional feature.

DMER81602B: Both of the two paths of the remote subsystem were detached.

Check the status of the path.


DMER81602D: The S-VOL of the remote subsystem is being formatted. Retry after waiting for a while.

DMER81602E: The remote subsystem is undergoing the pseudo deliberate shutdown. Retry after the pseudo deliberate shutdown is completed.

DMER81602F: The remote subsystem has undergone the pseudo deliberate shutdown. Retry after waiting for a while.


DMER816031: The WWN of the remote subsystem is illegal. Check the remote subsystem WWN.


DMER816033: The remote subsystem is undergoing hot replacement of the firmware. Retry after waiting for a while.

DMER816035: The optional feature of Remote Replication of the remote array is locked. Unlock and enable the optional feature.

DMER816038: Both of the two paths of the remote subsystem were detached. Check the status of the path.

DMER816041: The S-VOL of the remote subsystem is doing a duplicate writing.


DMER816042: The capacity is beyond the limits of support. Delete unnecessary pairs of the remote subsystem.

DMER816086: The S-VOL of the remote subsystem is specified as a command device. Specify a volume other than a command device of the remote subsystem as the S-VOL.

DMER816087: The S-VOL of the remote subsystem is executing format. Check the status of the remote subsystem and retry after waiting for a while.

DMER816088: The S-VOL of the remote subsystem is specified as the DM-LU.

Specify a volume other than the DM-LU of the remote subsystem as the S-VOL.

DMER816089: The S-VOL of the remote subsystem is in the status of S-VOL Disable.

Check the status of the remote subsystem and cancel the access attribute.

DMER81608A: The S-VOL in the remote array cannot allocate the differential bit of remote replication pair because the capacity is beyond the supported limit. Check the status of the remote array. In addition delete unnecessary pairs of the remote array.

DMER81608B: The S-VOL in the remote subsystem has no vacancy of the SnapShot cache block. Check the pool LU status of the remote subsystem. In addition delete unnecessary pairs of the remote subsystem.

DMER81608C: The SnapShot cache block for the S-VOL in the remote subsystem is being deleted. Check the pool LU status of the remote subsystem and retry after waiting for a while.

DMER81608D: The S-VOL of the remote subsystem does not meet the conditions of cascading with a SnapShot pair. Check the status of the LU in the remote array.



Error

Code

581608e

Description

5816091

5816094

5816095

5816096

5816097

581609a

581609b

581609c

581609d

581609e

581609f

58160a0

58160a1

58160a2

58160a3

58160a4

DMER81608E: The S-VOL in the remote subsystem has created a ShadowImage pair. The Remote Replication and ShadowImage volumes cannot be cascaded with each other. Check the LU status of the remote subsystem.

DMER816091: The Array ID of the S-VOL in the remote subsystem is wrong. Check the Array ID of the remote subsystem.

DMER816094: The RAID level of the S-VOL in the remote array is RAID 0. Set the

RAID level other than RAID 0 in the remote array.

DMER816095: The S-VOL in the remote subsystem is undergoing the forced parity correction. Check the status of the remote subsystem and retry after waiting for a while.

DMER816096: The S-VOL in the remote subsystem is a SnapShot V-VOL. The

Remote Replication and SnapShot V-VOLs cannot be cascaded with each other.

Check the LU status of the remote subsystem.

DMER816097: The S-VOL in the remote subsystem received an illegal command.

Check the status of the remote subsystem.

DMER81609A: The status of the LU that will be S-VOL in the remote array is normal or other than regressed or the RAID group to which the LU is belongs indicates a status other than Normal or the LU is a virtual LU. Check the LU status of the remote array. Retry after the RAID group status becomes Normal in case that the

RAID group indicates a status other than Normal. Specify an LU other than an LU created in DP pool to S-VOL.

DMER81609B: The S-VOL in the remote subsystem is a unified LU consists of 17 or more LUs. Make the number of the unified LUs that constitute the unified LU of the remote subsystem 16 or less.

DMER81609C: The LU capacity of the S-VOL in the remote subsystem is not the same as the P-VOL capacity. Make the LU capacity of the remote subsystem the same as that of the P-VOL.

DMER81609D: The S-VOL in the remote array is set to a Cache Residency LU.

Specify an LU other than a Cache Residency LU of the remote array.

DMER81609E: An LU with a capacity less than 1 GB is included in the LUs in which the S-VOL is unified in the remote subsystem. Check the status of the unified LU of the remote subsystem.

DMER81609F: The internal transaction which are splitting or deleting for SnapShot is working now. Retry after waiting for a while.

DMER8160A0: The remote subsystem has no pool LU. Make a pool LU for the remote subsystem.

DMER8160A1: The LU specified as the S-VOL in the remote subsystem is a pool LU.

The pool LU cannot be set to an S-VOL. Check the pool LU status of the remote subsystem.

DMER8160A2: The LU status of the pool LU in the remote subsystem is normal or other than regressed. Check the pool LU status of the remote subsystem.

DMER8160A3: The pool LU in the remote subsystem is undergoing the forced parity correction. Check the pool LU status of the remote subsystem and retry after waiting for a while.

DMER8160A4: The S-VOL in the remote subsystem exceeded the total allowable maximum number of Remote Replication and SnapShot pairs. Check the status of the remote subsystem. In addition, delete unnecessary pairs of the remote subsystem.



Error

Code

58160a5

Description

58160a6

58160a7

58160a8

58160a9

58160aa

58160ab

58160b4

58160b5

58160b6

58160b7

58160b8

58160b9

58160ba

58160bb

58160bc

58160bd

DMER8160A5: The Remote Replication pair status of the S-VOL in the remote subsystem is Failure. Check the Remote Replication pair status of the remote subsystem.

DMER8160A6: The Remote Replication pair status of the S-VOL in the remote subsystem is Threshold Over. Check the Remote Replication pair status of the remote subsystem.

DMER8160A7: The Remote Replication pair status of the S-VOL in the remote subsystem is Split (no reading/writing allowed). Check the Remote Replication pair status of the remote subsystem.

DMER8160A8: The Remote Replication pair status of the S-VOL in the remote subsystem is Takeover (including Busy). Check the Remote Replication pair status of the remote subsystem.

DMER8160A9: The Remote Replication pair status of the S-VOL in the remote subsystem is Simplex. Check the Remote Replication pair status of the remote subsystem.

DMER8160AA: The Remote Replication pair status of the S-VOL in the remote subsystem is Split. Check the Remote Replication pair status of the remote subsystem.

DMER8160AB: The Remote Replication pair status of the S-VOL in the remote subsystem is not Simplex. Check the Remote Replication pair status of the remote subsystem.

DMER8160B4: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, the special processing cannot be continued.

Check the status of the remote subsystem and retry after waiting for a while.

DMER8160B5: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, an ownership of LU change for it has been started. Check the status of the remote subsystem and retry after waiting for a while.

DMER8160B6: The S-VOL in the remote subsystem does not exist on the default owner controller and it has started an ownership of LU change. Check the status of the remote subsystem and retry after waiting for a while.

DMER8160B7: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, an ownership of LU to be changed is blocked. Check the status of the remote subsystem and retry after waiting for a while.

DMER8160B8: The S-VOL in the remote subsystem cannot change an ownership of

LU and, at the same time, it is using the sequential buffer. Check the status of the remote subsystem and retry after waiting for a while.


LU temporarily. Retry after waiting for a while.

DMER8160BA: The S-VOL in the remote subsystem cannot change an ownership of

LU and, at the same time, it has pinned data. Contact the service personnel.

DMER8160BB: The S-VOL in the remote subsystem cannot change an ownership of


DMER8160BC: The S-VOL in the remote subsystem cannot change an ownership of


DMER8160BD: The S-VOL in the remote subsystem cannot change an ownership of

LU and a time-out occurred. Check the status of the remote subsystem and retry after waiting for a while.



Error

Code

58160be

Description

58160c0

58160c1

58160c2

58160c5

58160d2

58160dd

58160e0

58160e5

58160ea

5817022

5817023

5817024

5817025

5817026

5817027

5817028

5817029

581702a

581702b

581702c

581702d

DMER8160BE: The S-VOL in the remote subsystem cannot change an ownership of

LU and, at the same time, the group# is illegal. Check the status of the remote subsystem.

DMER8160C0: The S-VOL in the remote array does not exist on the default owner controller, and its disk drives are being spun up. Check the status of the remote array and retry after waiting for a while.

DMER8160C1: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, it is making the system copy. Check the status of the remote subsystem and retry after waiting for a while.

DMER8160C2: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, it is writing the takeover information. Check the status of the remote subsystem and retry after waiting for a while.

DMER8160C5: The cycle time that has been set for the remote subsystem is less than the minimum interval. Check the cycle time that has been set for the remote subsystem.

DMER8160D2: The S-VOL pool number in the remote subsystem is not same as the one that is being used for SnapShot. Confirm the indicated pool number in the remote subsystem.

DMER8160DD: The firmware internal error occurred. Retry after waiting for a while.


DMER8160E0: Auto Migration is being executed in the remote subsystem just now.

Execute again after the Migration is completed.


DMER8160EA: The LU created in DP pool was specified as S-VOL. Specify an LU other than the LU created in DP pool.









DMER81702A: The optional feature of Remote Replication of the remote subsystem is invalid. Unlock and enable the optional feature.




DMER81702D: The S-VOL of the remote subsystem is being formatted. Retry after waiting for a while.



Error

Code

581702e

Description

581702f

5817030

5817031

5817032

5817033

5817035

5817038

5817041

5817042

5817086

5817087

5817088

5817089

581708a

581708b

581708c

581708d

581708e

5817091

5817094

DMER81702E: The remote subsystem is undergoing the pseudo deliberate shutdown. Retry after the pseudo deliberate shutdown is completed.

DMER81702F: The remote subsystem has undergone the pseudo deliberate shutdown. Retry after waiting for a while.


DMER817031: The WWN of the remote subsystem is illegal. Check the remote subsystem WWN.


DMER817033: The remote subsystem is undergoing hot replacement of the firmware. Retry after waiting for a while.

DMER817035: The optional feature of Remote Replication of the remote array is invalid. Unlock and enable the optional feature.

DMER817038: Both of the two paths of the remote subsystem were detached. Check the status of the path.

DMER817041: The S-VOL of the remote subsystem is doing a duplicate writing.


DMER817042: The capacity is beyond the limits of support. Delete unnecessary pairs of the remote subsystem.

DMER817086: The S-VOL of the remote subsystem is specified as a command device. Specify a volume other than a command device of the remote subsystem as the S-VOL.

DMER817087: The S-VOL of the remote subsystem is executing format. Check the status of the remote subsystem and retry after waiting for a while.

DMER817088: The S-VOL of the remote subsystem is specified as the DM-LU.

Specify a volume other than the DM-LU of the remote subsystem as the S-VOL.

DMER817089: The S-VOL of the remote subsystem is in the status of S-VOL Disable.

Check the status of the remote subsystem and cancel the access attribute.

DMER81708A: The S-VOL in the remote subsystem cannot be allocated the differential bit of Remote Replication. Check the status of the remote subsystem. In addition, delete unnecessary pairs of the remote subsystem.

DMER81708B: The S-VOL in the remote subsystem has no vacancy of the SnapShot cache block. Check the pool LU status of the remote subsystem. In addition delete unnecessary pairs of the remote subsystem.

DMER81708C: The SnapShot cache block for the S-VOL in the remote subsystem is being deleted. Check the pool LU status of the remote subsystem and retry after waiting for a while.

DMER81708D: The S-VOL of the remote subsystem does not meet the conditions of cascading with a SnapShot pair. Check the status of the LU in the remote array.

DMER81708E: The S-VOL in the remote subsystem has created a ShadowImage pair. The Remote Replication and ShadowImage volumes cannot be cascaded with each other. Check the LU status of the remote subsystem.

DMER817091: The Array ID of the S-VOL in the remote subsystem is wrong. Check the Array ID of the remote subsystem.

DMER817094: The RAID level of the S-VOL in the remote array is RAID 0. Make the

RAID level of the remote array other than RAID 0.



Error

Code

5817095

Description

5817096

5817097

5817098

581709a

581709b

581709c

581709d

581709e

581709f

58170a0

58170a1

58170a2

58170a3

58170a4

58170a5

58170a6

DMER817095: The S-VOL in the remote subsystem is undergoing the forced parity correction. Check the status of the remote subsystem and retry after waiting for a while.

DMER817096: The S-VOL in the remote subsystem is a SnapShot V-VOL. The

Remote Replication and SnapShot V-VOLs cannot be cascaded with each other.

Check the LU status of the remote subsystem.

DMER817097: The S-VOL in the remote subsystem received an illegal command.


DMER817098: The S-VOL in the remote array is changing the cache partition. Check the status of the remote array and retry after waiting for a while.

DMER81709A: The status of the LU that will be S-VOL in the remote array is normal or other than regressed or the RAID group to which the LU is belongs indicates a status other than Normal or the LU is a virtual LU. Check the LU status of the remote array. Retry after the RAID group status becomes Normal in case that the

RAID group indicates a status other than Normal. Specify an LU other than an LU created in DP pool to S-VOL.

DMER81709B: The S-VOL in the remote subsystem is a unified LU consists of 17 or more LUs. Make the number of the unified LUs that constitute the unified LU of the remote subsystem 16 or less.

DMER81709C: The LU capacity of the S-VOL in the remote subsystem is not the same as the P-VOL capacity. Make the LU capacity of the remote subsystem the same as that of the P-VOL.

DMER81709D: The S-VOL in the remote array is set to a Cache Residency LU.

Specify an LU other than a Cache Residency LU of the remote array.

DMER81709E: An LU with a capacity less than 1 GB is included in the LUs in which the S-VOL is unified in the remote subsystem. Check the status of the unified LU of the remote subsystem.

DMER81709F: The internal transaction which are splitting or deleting for SnapShot is working now. Retry after waiting for a while.

DMER8170A0: The remote subsystem has no pool LU. Make a pool LU for the remote subsystem.

DMER8170A1: The LU specified as the S-VOL in the remote subsystem is a pool LU.


DMER8170A2: The LU status of the pool LU in the remote subsystem is normal or other than regressed. Check the pool LU status of the remote subsystem.

DMER8170A3: The pool LU in the remote subsystem is undergoing the forced parity correction. Check the pool LU status of the remote subsystem and retry after waiting for a while.

DMER8170A4: The S-VOL in the remote subsystem exceeded the total allowable maximum number of Remote Replication and SnapShot pairs. Check the status of the remote subsystem. In addition, delete unnecessary pairs of the remote subsystem.

DMER8170A5: The Remote Replication pair status of the S-VOL in the remote subsystem is Failure. Check the Remote Replication pair status of the remote subsystem.

DMER8170A6: The Remote Replication pair status of the S-VOL in the remote subsystem is Threshold Over. Check the Remote Replication pair status of the remote subsystem.



Error

Code

58170a7

Description

58170a8

58170a9

58170aa

58170ab

58170b4

58170b5

58170b6

58170b7

58170b8

58170b9

58170ba

58170bb

58170bc

58170bd

58170be

58170c0

DMER8170A7: The Remote Replication pair status of the S-VOL in the remote subsystem is Split (no reading/writing allowed). Check the Remote Replication pair status of the remote subsystem.

DMER8170A8: The Remote Replication pair status of the S-VOL in the remote subsystem is Takeover (including Busy). Check the Remote Replication pair status of the remote subsystem.

DMER8170A9: The Remote Replication pair status of the S-VOL in the remote subsystem is Simplex. Check the Remote Replication pair status of the remote subsystem.

DMER8170AA: The Remote Replication pair status of the S-VOL in the remote subsystem is Split. Check the Remote Replication pair status of the remote subsystem.

DMER8170AB: The Remote Replication pair status of the S-VOL in the remote subsystem is not Simplex. Check the Remote Replication pair status of the remote subsystem.

DMER8170B4: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, the special processing cannot be continued.


DMER8170B5: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, an ownership of LU change for it has been started. Check the status of the remote subsystem and retry after waiting for a while.

DMER8170B6: The S-VOL in the remote subsystem does not exist on the default owner controller and it has started an ownership of LU change. Check the status of the remote subsystem and retry after waiting for a while.

DMER8170B7: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, an ownership of LU to be changed is blocked. Check the status of the remote subsystem and retry after waiting for a while.





DMER8170BA: The S-VOL in the remote subsystem cannot change an ownership of


DMER8170BB: The S-VOL in the remote subsystem cannot change an ownership of


DMER8170BC: The S-VOL in the remote subsystem cannot change an ownership of


DMER8170BD: The S-VOL in the remote subsystem cannot change an ownership of


DMER8170BE: The S-VOL in the remote subsystem cannot change an ownership of


DMER8170C0: The S-VOL in the remote array does not exist on the default owner controller and, at the same time, its disk drives are being spun up. Check the status of the remote array and retry after waiting for a while.



Error

Code

58170c1

Description

58170c2

58170c5

58170d2

58170dd

58170e0

58170e5

58170ea

5819022

5819023

5819024

5819025

5819026

5819027

5819028

5819029

581902a

581902b

58190de

581a022

581a023

581a024

581a025

581a026

DMER8170C1: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, it is making the system copy. Check the status of the remote subsystem and retry after waiting for a while.

DMER8170C2: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, it is writing the takeover information. Check the status of the remote subsystem and retry after waiting for a while.

DMER8170C5: The cycle time that has been set for the remote subsystem is less than the minimum interval. Check the cycle time that has been set for the remote subsystem.

DMER8170D2: The S-VOL pool number in the remote subsystem is not same as the one that is being used for SnapShot. Confirm the indicated pool number in the remote subsystem.



DMER8170E0: Auto Migration is being executed in the remote subsystem just now.



DMER8170EA: The LU created in DP pool was specified as S-VOL. Specify an LU other than the LU created in DP pool.












DMER8190DE: Auto Migration is being executed in the remote subsystem just now.


DMER81A022: Now executing. Wait a while and execute again.



DMER81A025: The S-VOL in the remote subsystem is being formatted now. Wait a while and execute again.

DMER81A026: The remote subsystem is undergoing the pseudo deliberate shutdown. Execute again after the pseudo deliberate shutdown.



Error

Code

581a027

Description

581a028

581a029

581a02a

581a02b

581a02c

581a02d

581a02e

581a02f

581a030

581a032

581a033

581a035

581a038

581a041

581a089

581a08b

581a08c

581a08d

581a090

581a091

581a095

581a097

DMER81A027: The remote subsystem is after the pseudo deliberate shutdown. Wait a while and execute again.

DMER81A028: The pair operation commands are being executed in the remote subsystem. Wait a while and execute again.

DMER81A029: Command error was occurred. Wait a while and execute again.

DMER81A02A: The optional feature of Remote Replication of the remote subsystem is invalid. Unlock and validate the optional feature.

DMER81A02B: Both of the two paths of the remote subsystem were detached.


DMER81A02C: Now executing. Wait a while and execute again.

DMER81A02D: The S-VOL in the remote subsystem is being formatted now. Wait a while and execute again.

DMER81A02E: The remote subsystem is undergoing the pseudo deliberate shutdown. Execute again after the pseudo deliberate shutdown.

DMER81A02F: The remote subsystem is undergoing the pseudo deliberate shutdown. Wait a while and execute again.

DMER81A030: The S-VOL is undefined. Check the attribute of the LU.

DMER81A032: The pair operation commands are being executed in the remote subsystem. Wait a while and execute again.

DMER81A033: The remote subsystem is undergoing hot replacement of the firmware. Wait a while and execute again.

DMER81A035: The optional feature of Remote Replication of the remote subsystem is invalid. Unlock and validate the optional feature.

DMER81A038: Both of the two paths of the remote subsystem were detached.



DMER81A089: The S-VOL of the remote subsystem is in the status of S-VOL

Disable. Check the status of the remote subsystem and cancel the access attribute.

DMER81A08B: The S-VOL in the remote subsystem has no vacancy of the SnapShot cache block. Check the pool LU status of the remote subsystem. In addition, delete unnecessary pairs of the remote subsystem.

DMER81A08C: The SnapShot cache block for the S-VOL in the remote subsystem is being deleted. Check the pool LU status of the remote subsystem and retry after waiting for a while.

DMER81A08D: The S-VOL of the remote subsystem does not meet the conditions of cascading with a SnapShot pair. Retry after checking the LU status of the remote subsystem and satisfying the conditions stated in the User's Guide.


DMER81A091: The indicated Array ID is not same as the actual one for remote subsystem. Confirm the Array ID for the remote subsystem.

DMER81A095: The S-VOL in the remote subsystem is undergoing the forced parity correction. Check the status of the remote subsystem and retry after waiting for a while.

DMER81A097: The S-VOL in the remote subsystem received an illegal command.




Error

Code

581a099

581a09a

581a09f

581a0a0

581a0a1

581a0a2

581a0a3

581a0a4

581a0a5

581a0a6

581a0a7

581a0a8

581a0a9

581a0aa

581a0ab

581a0b4

Description

DMER81A099: The array can not execute the operation because the target P-VOL of the specified LU does not exist. Delete the pair regarding the P-VOL in the remote array and create a remote replication pair.

DMER81A09A: The LU status of the S-VOL in the remote array is normal or other than regressed or the RAID group to which the LU is belongs indicates a status other than Normal. Check the LU status of the remote array. Retry after the RAID group status becomes Normal in case that the RAID group indicates a status other than

Normal.

DMER81A09F: The internal transaction which are splitting or deleting for SnapShot is working now. Retry after waiting for a while.

DMER81A0A0: The remote subsystem has no pool LU. Make a pool LU for the remote subsystem.

DMER81A0A1: The LU specified as the S-VOL in the remote subsystem is a pool LU.


DMER81A0A2: The LU status of the S-VOL in the remote subsystem is normal or other than regressed. Check the pool LU status of the remote subsystem.

DMER81A0A3: The pool LU in the remote subsystem is undergoing the forced parity correction. Check the pool LU status of the remote subsystem and retry after waiting for a while.

DMER81A0A4: The S-VOL in the remote subsystem exceeded the total allowable maximum number of Remote Replication and SnapShot pairs. Check the status of the remote subsystem. In addition, delete unnecessary pairs of the remote subsystem.

DMER81A0A5: The Remote Replication pair status of the S-VOL in the remote subsystem is Failure. Check the Remote Replication pair status of the remote subsystem.

DMER81A0A6: The Remote Replication pair status of the S-VOL in the remote subsystem is Threshold Over. Check the Remote Replication pair status of the remote subsystem.

DMER81A0A7: The Remote Replication pair status of the S-VOL in the remote subsystem is Split (no reading/writing allowed). Check the Remote Replication pair status of the remote subsystem.

DMER81A0A8: The Remote Replication pair status of the S-VOL in the remote subsystem is Takeover (including Busy). Check the Remote Replication pair status of the remote subsystem.

DMER81A0A9: The Remote Replication pair status of the S-VOL in the remote subsystem is Simplex. Check the Remote Replication pair status of the remote subsystem.

DMER81A0AA: The Remote Replication pair status of the S-VOL in the remote subsystem is Split. Check the Remote Replication pair status of the remote subsystem.

DMER81A0AB: The Remote Replication pair status of the S-VOL in the remote subsystem is not Simplex. Check the Remote Replication pair status of the remote subsystem.

DMER81A0B4: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, the special processing cannot be continued.




Error

Code

581a0b5

Description

581a0b6

581a0b7

581a0b8

581a0b9

581a0ba

581a0bb

581a0bc

581a0bd

581a0be

581a0c1

581a0c2

581a0d2

581a0d3

581a0dd

581a0e0

581a0e5

5820005

5820006

DMER81A0B5: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, an ownership of LU change for it has been started. Check the status of the remote subsystem and retry after waiting for a while.

DMER81A0B6: The S-VOL in the remote subsystem does not exist on the default owner controller and it has started an ownership of LU change. Check the status of the remote subsystem and retry after waiting for a while.

DMER81A0B7: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, an ownership of LU to be changed is blocked. Check the status of the remote subsystem and retry after waiting for a while.

DMER81A0B8: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0B9: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0BA: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0BB: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0BC: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0BD: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0BE: The S-VOL in the remote subsystem cannot change an ownership of


DMER81A0C1: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, it is making the system copy. Check the status of the remote subsystem and retry after waiting for a while.

DMER81A0C2: The S-VOL in the remote subsystem does not exist on the default owner controller and, at the same time, it is writing the takeover information. Check the status of the remote subsystem and retry after waiting for a while.

DMER81A0D2: The S-VOL pool number in the remote subsystem is not same as the one that is being used for SnapShot. Confirm the indicated pool number in the remote subsystem.

DMER81A0D3: The license validity of the remote subsystem is expired. Purchase the license.

DMER81A0DD: The firmware internal error occurred. Retry after waiting for a while.


DMER81A0E0: Auto Migration is being executed in the remote subsystem just now.


DMER81A0E5: The RAID group to which the S-VOL of the remote array belongs indicates a status other than Normal. Retry after the status becomes Normal.

DMER820005: The LU of the remote array is being formatted. Retry after waiting for a while.

DMER820006: The remote array is undergoing the pseudo deliberate shutdown.




Error

Code

5820007

Description

5820008

5820009

582000b

582000c

582000d

582000e

5820011

5820012

5820015

5820017

5820019

582001a

582001c

582001d

582001e

5820021

5820032

582003d

582003f

5820040

DMER820007: The remote array has undergone the pseudo deliberate shutdown.


DMER820008: The S-VOL is undefined. Check the status of the LU.


DMER82000B: The remote array is undergoing hot replacement of the firmware.


DMER82000C: A command error occurred. Retry after waiting for a while.

DMER82000D: The optional feature of Remote Replication of the remote array is invalid. Unlock and validate the optional feature.

DMER82000E: The status of the S-VOL cannot be changed. Retry after waiting for a while.

DMER820011: The object LU has already been organized into a Remote Replication pair. Besides, the Array ID differs between the local and remote arrays or the maximum number of the connected arrays is beyond the limits. Check the pair status of the LU and Array ID or number of the connected arrays.

DMER820012: The number of Remote Replication pairs exceeded the maximum value that can be supported. Check the number of Remote Replication pairs.

DMER820015: The status of the object LU is other than normal and regressive or the specified S-VOL is a volume of ShadowImage pair that includes the LU created in

DP pool. Make the status of the LU normal or regressive and confirm the

ShadowImage pair that the specified S-VOL is part of.

DMER820017: The S-VOL is configured as RAID 0. Check the RAID level of the specified LU.

DMER820019: The capacity differs between the P-VOL and S-VOL. Equalize the capacities of the P-VOL and S-VOL.

DMER82001A: The S-VOL is a Cache Residency LU or has been set to the reserved


DMER82001C: The object LU is a command device. Specify an LU other than a command device.

DMER82001D: The change of the default owner controller is reserved for the object

LU. Cancel the reservation for changing the default owner controller or specify the

LU for which the change of the default owner controller is not reserved.



DMER820021: The object LU has already been cascaded with a ShadowImage pair.

Check the pair status of the LU and check that its pair attribute is P-VOL.

DMER820032: The remote array is receiving a command. Retry after waiting.


DMER82003F: The LU assigned to a Remote Replication pair has already been paired by ShadowImage. Check the pair status of the LU.

DMER820040: The S-VOL of the specified pair cannot accept Read/Write instructions or is a part of ShadowImage whose status is Reverse Synchronizing. Check the status of the S-VOL or the pair status of the ShadowImage pair.



Error

Code

5820041

5820045

5820046

5820048

5820049

582004a

5820050

5820053

5820054

5820055

5820058

5820059

582005a

582005b

582005c

58200c6

58200c7

58200cf

58200d4

58200d9

58200de

Description

DMER820041: The process is in progress. Retrying after waiting.

DMER820045: The stripe size of the object LU of the remote array is other than

64KB. Make the stripe size of the LU of the remote array 64KB.

DMER820046: The object LU of the remote array is being restored as a volume of

SnapShot or cannot accept Read/Write instructions. Place the SnapShot pair which comprises the LU of the remote array in the Simplex status once and then operate the pair.

DMER820048: The specified LU is an S-VOL of ShadowImage. Split the

ShadowImage pair that comprises an LU of the remote array.

DMER820049: The object LU of the remote array is being formatted. Create the pair again after the formatting is completed.

DMER82004A: The S-VOL is in the S-VOL Disable mode. Cancel the S-VOL Disable specified for the LU of the remote array.

DMER820050: The object LU of the remote array has not undergone the forced restoration by means of parity or it is undergoing the restoration above. Make the status which concerns the forced restoration by means of parity of the LU of the remote array to Restored or Skip.

DMER820053: The number of unified LUs of the remote array is 17 or more. Make the number of unified LUs of the remote array 16 or less.

DMER820054: The V-VOL which is paired with a SnapShot P-VOL of the remote array has already been organized into a Remote Replication pair. Split the Remote

Replication pair comprising a SnapShot V-VOL that is an LU of the remote array.

DMER820055: The object LU of the remote array is a V-VOL of SnapShot (at the time of a pair formation). Specify the LU of the remote array to a volume other than a V-VOL of SnapShot.



DMER820059: The license validity of the remote array is expired. Purchase the license.

DMER82005A: The DM-LU is not set of the remote array or the DM-LU was specified as S-VOL. Retry after setting the DM-LU or check the status of the LU.

DMER82005B: The specified S-VOL is the pool LU. Check the status of the LU.

DMER82005C: The specified S-VOL is the NAS LU. Check the status of the LU.

DMER8200C6: The specified S-VOL is undergoing the migration. Perform the migration after deleting the pair.

DMER8200C7: The specified S-VOL is the reserved LU. Re-execute the migration specifying an LU other than the reserved LU for the S-VOL.

DMER8200CF: The disk drives that configure a RAID group to which a target LU in the remote array belongs have been spun down. Perform the operation again after spinning up the disk drives that configure the RAID group.

DMER8200D4: The LU which has been indicated as S-VOL in the remote array is P-

VOL now. Confirm the LU status in the remote array.

DMER8200D9: The status of the remote array is in an inappropriate condition to create or resynchronize the Remote Replication pair. Confirm the Array ID, pair status of Local and Remote Replication. See the User's Guide for their detail information.




Error

Code

58200e2

Description

58200e3

58200e9

5821005

5821006

5821007

5821008

5821009

582100b

582100c

582100d

582100e

5821011

5821012

5821015

5821017

5821019

582101a

582101c

582101d

582101e




DMER8200E9: The specified S-VOL is a volume of ShadowImage pair that includes the LU created in DP pool. Confirm the ShadowImage pair that the specified S-VOL is part of.













DMER821011: The object LU has already been organized into a Remote Replication pair. Besides, the Array ID differs between the local and remote arrays or the maximum number of the connected arrays is beyond the limits. Check the pair status of the LU and Array ID or number of the connected Array.


DMER821015: The status of the object LU is other than normal and regressive or the specified S-VOL is a volume of ShadowImage pair that includes the LU created in

DP pool. Make the status of the LU normal or regressive and confirm the

ShadowImage pair that the specified S-VOL is part of.






DMER82101D: The change of the default owner controller is reserved for the object

LU. Cancel the reservation for changing the default owner controller or specify the

LU for which the change of the default owner controller is not reserved.


Check the pair status of the LU and the RAID group status. Retry after the RAID group status



Error

Code

5821021

Description

5821032

582103f

5821040

5821041

5821045

5821046

5821048

5821049

582104a

5821050

5821053

5821054

5821055

5821058

582105a

582105b

582105c

58210c6

58210c7

58210cf

DMER821021: The object LU has already been cascaded with a ShadowImage pair.

Check the pair status of the LU and check that its pair attribute is P-VOL.

DMER821032: The remote array is receiving a command. Retry after waiting for a while.

DMER82103F: The LU assigned to a Remote Replication pair has already been paired by ShadowImage. Check the pair status of the LU.


ShadowImage or cannot accept Read/Write instructions. Check the pair status of the

LU.


DMER821045: The stripe size of the object LU of the remote array is other than

64KB. Make the stripe size of the LU of the remote array 64KB.


SnapShot or cannot accept Read/Write instructions. Place the SnapShot pair, which comprises the LU of the remote array in the Simplex status once and then operate the pair.

DMER821048: The specified LU is an S-VOL of ShadowImage. Split the

ShadowImage pair that comprises an LU of the remote array.

DMER821049: The object LU of the remote array is being quick formatted. Create the pair again after the quick formatting is completed.


DMER821050: The object LU of the remote array has not undergone the forced restoration by means of parity or it is undergoing the restoration above. Make the status, which concerns the forced restoration by means of parity, of the LU of the remote array to Restored or Skip.

DMER821053: The number of unified LUs of the remote array is 17 or more. Make the number of unified LUs of the remote array 16 or less.

DMER821054: The V-VOL, which is paired with a SnapShot P-VOL of the remote array has already been organized into a Remote Replication pair. Split the Remote

Replication pair comprising a SnapShot V-VOL that is an LU of the remote array.

DMER821055: The object LU of the remote array is a V-VOL of SnapShot (at the time of a pair formation). Specify the LU of the remote array to a volume other than a V-VOL of SnapShot.



DMER82105A: The DM-LU is not set of the remote array or the DM-LU was specified as S-VOL. Retry after setting the DM-LU or check the status of the LU.


DMER82105C: The specified S-VOL is the NAS LU. Check the status of the LU.


DMER8210C7: The specified S-VOL is the reserved LU. Re-execute the migration specifying an LU other than the reserved LU for the S-VOL.

DMER8210CF: The disk drives that configure a RAID group, to which a target LU in the remote array belongs have been spun down. Perform the operation again after spinning up the disk drives that configure the RAID group.



Error

Code

58210d4

Description

58210de

58210e2

58210e3

58210e9

5822005

5822006

5822007

5822008

5822009

582200b

582200c

582200d

582200e

5822011

5822014

5822015

582201e

5822020

5822032

582203d

5822041







DMER8210E9: The specified S-VOL is a volume of ShadowImage pair that includes the LU created in DP pool. Confirm the ShadowImage pair that the specified S-VOL is part of.













DMER822011: The object LU has already been organized into a Remote Replication pair. Besides, the Array ID differs between the local and remote arrays. Check the pair status of the LU and Array ID.


Check the Array ID.

DMER822015: The status of the object LU is other than normal and regressive. Make the status of the LU normal or regressive.





LU.






Error

Code

5822046

Description

582204a

5822050

5822059

58220cf

58220d4

58220d7

58220d8

58220de

58220e2

58220e3

5823005

5823006

5823007

5823008

5823009

582300b

582300c

582300d

582300e

5823011


SnapShot or cannot accept Read/Write instructions. Place the SnapShot pair, which comprises the LU of the remote array, in the Simplex status once and then operate the pair.


DMER822050: The object LU of the remote array has not undergone the forced restoration by means of parity or it is undergoing the restoration above. Make the status, which concerns the forced restoration by means of parity, of the LU of the remote array to Restored or Skip.





DMER8220D7: The indicated S-VOL is not Split status in the SnapShot pair. Execute again after having the SnapShot pair status in the remote array be Split or Simplex.

DMER8220D8: The indicated S-VOL is not Split status in the ShadowImage pair.

Execute again after having the ShadowImage pair status in the remote array be

Split or Simplex.




















Error

Code

582301e

Description

5823032

5823041

5823046

58230d4

58230d7

58230d8

58230d9

5824005

5824006

5824007

5824008

5824009

582400b

582400c

582400d

582400e

5824011

582401e

5824032

5824041

5824046

DMER82301E: The object LU has been organized into a Remote Replication pair.





SnapShot or cannot accept Read/Write instructions. Place the SnapShot pair, which comprises the LU of the remote array, in the Simplex status once and then operate the pair.






Split or Simplex.

DMER8230D9: The status of the remote array is in an inappropriate condition to create or resynchronize the Remote Replication pair. Confirm the Array ID, pair status of Local and Remote Replication. See the User's Guide for their detail information.






















Error

Code

58240d4

Description

58240d7

58240d8

58240d9

5825005

5825006

5825007

5825008

5825009

582500b

582500c

582500d

582500e

5825011

5825014

5825015

582501e

5825020

5825032

582503d

5825041






Split or Simplex.

DMER8240D9: The status the remote array is in an inappropriate condition to create the Remote Replication pair. Confirm the Array ID, pair status of Remote Replication and status of SnapShot and ShadowImage. See the User's Guide for their detail information.







DMER825009: The WWN of the array array is illegal. Check the equipment WWN.








Check the Array ID.

DMER825015: The status of the object LU is other than normal and regressive. Make the status of the LU normal or regressive.





LU.






Error

Code

5825046

Description

5825047

582504b

5825050

5825056

5825059

58250cf

58250d4

58250d7

58250d8

58250de

58250e2

58250e3

5826011

5826012

5826015

5826017

5826019

582601a

582601c



DMER825047: The specified LU is an S-VOL of ShadowImage. Specify an LU other than a ShadowImage S-VOL that comprises the LU of the remote array.

DMER82504B: Check the pair status of the LU. Cancel the S-VOL Disable specified for the LU of the remote array (at the time of a swap).

DMER825050: The object LU of the remote array has not undergone the forced restoration by means of parity or it is undergoing the restoration above. Make the status which concerns the forced restoration by means of parity of the LU of the remote array to Restored or Skip.

DMER825056: The target LU of the remote array is a V-VOL of SnapShot (at the time of swap). Specify the LU of the remote array other than a V-VOL of SnapShot.





DMER8250D7: The indicated S-VOL is not Split status in the SnapShot pair. Execute again after having the SnapShot pair status Split or Simplex.


Execute again after having the ShadowImage pair status Split or Simplex.





DMER826011: The object LU has already been organized into a Remote Replication pair. Besides, the Array ID differs between the local and remote subsystems. Check the pair status of the LU and Array ID.


DMER826015: The status of the object LU is other than normal and regressive or the specified S-VOL is an LU created in DP pool. Make the status of the LU normal or regressive and specify an LU other than an LU created in DP pool to S-VOL.

DMER826017: The S-VOL resides in the RAID group of RAID 0. Choose a RAID group of RAID level other than RAID 0.







Error

Code

582601e

Description

5826026

5826027

582602a

5826040

5826045

5826046

5826049

582604a

5826050

5826053

5826055

5826059

582605a

582605b

58260b3

58260c4

58260c6

58260c7





DMER82602A: The optional feature of Remote Replication of the remote subsystem is invalid. Unlock and validate the optional feature.

DMER826040: The S-VOL in the remote subsystem has created a ShadowImage pair. The Remote Replication and ShadowImage volumes cannot be cascaded with each other. Check the LU status of the remote subsystem.

DMER826045: The stripe size of the object LU of the remote subsystem is other than 64KB. Make the stripe size of the LU of the remote subsystem 64KB.

DMER826046: The object LU of the remote subsystem is being restored as a volume of SnapShot or cannot accept Read/Write instructions. Place the SnapShot pair, which comprises the LU of the remote subsystem, in the Simplex status once and then operate the pair.

DMER826049: The object LU of the remote subsystem is being formatted. Create the pair again after the formatting is completed.

DMER82604A: The S-VOL is in the S-VOL Disable mode. Cancel the S-VOL Disable specified for the LU of the remote subsystem.

DMER826050: The object LU of the remote subsystem has not undergone the forced restoration by means of parity or it is undergoing the restoration above. Make the status, which concerns the forced restoration by means of parity, of the LU of the remote subsystem to Restored or Skip.

DMER826053: The number of unified LUs of the remote subsystem is 17 or more.

Make the number of unified LUs of the remote subsystem 16 or less.

DMER826055: The object LU of the remote subsystem is a V-VOL of SnapShot (at the time of a pair formation). Specify the LU of the remote subsystem to a volume other than a V-VOL of SnapShot.

DMER826059: The license validity of the remote subsystem is expired. Purchase the license.

DMER82605A: The DM-LU is not set of the remote subsystem or the DM-LU was specified as S-VOL. Retry after setting the DM-LU or check the status of the LU.


DMER8260B3: The specified S-VOL is a unified LU including a SubLU with a capacity less than 1 GB. Check whether the LU with a capacity less than 1 GB is included in each LU of the specified unified LU.

DMER8260C4: When a new pair of a group is created, the cycle time that has been set for the local and remote array is less than the minimum interval. Check the cycle time that has been set for the local and remote array.


DMER8260C7: The specified S-VOL is the reserved LU. Perform the migration specifying an LU other than the reserved LU for the S-VOL.



Error

Code

58260ca

Description

58260cb

58260cf

58260d1

58260d2

58260db

58260dd

58260de

58260e1

58260e3

58260e9

5827011

5827012

5827015

5827017

5827019

582701a

582701c

582701e

DMER8260CA: The specified S-VOL is undergoing the migration. Perform the migration after deleting the pair.

DMER8260CB: The specified S-VOL is the reserved LU. Perform the migration specifying an LU other than the reserved LU for the S-VOL.


DMER8260D1: The disk drives that configure a RAID group, to which a target LU in the remote array belongs have been spun down. Perform the operation again after spinning up the disk drives that configure the RAID group.

DMER8260D2: The specified data pool number in the remote array is not same as the one that is being used for SnapShot. Confirm the indicated data pool number in the remote array.

DMER8260DB: The partition or pair partition to which the target LU belongs is incorrect. Check the partition number.





DMER8260E1: The operation to change LU has become timeout while the controller in the remote array is recovering. Retry the operation after the controller is recovered.


DMER8260E9: The LU created in DP pool was specified as S-VOL. Specify an LU other than the LU created in DP pool.

DMER827011: The object LU has already been organized into a Remote Replication pair. Besides, the Array ID differs between the local and remote subsystems. Check the pair status of the LU and Array ID.


DMER827015: The status of the object LU is other than normal and regressive or the specified S-VOL is an LU created in DP pool. Make the status of the LU normal or regressive and specify an LU other than an LU created in DP pool to S-VOL.










Error

Code

5827026

Description

5827027

582702a

5827040

5827045

5827046

5827049

582704a

5827050

5827053

5827055

5827059

582705a

582705b

58270b3

58270c4

58270c6

58270c7

58270ca

58270cb




DMER827040: The S-VOL in the remote subsystem has created a ShadowImage pair. The Remote Replication and ShadowImage volumes cannot be cascaded with each other. Check the LU status of the remote subsystem.

DMER827045: The stripe size of the object LU of the remote subsystem is other than 64KB. Make the stripe size of the LU of the remote subsystem 64KB.

DMER827046: The object LU of the remote subsystem is being restored as a volume of SnapShot or cannot accept Read/Write instructions. Place the SnapShot pair, which comprises the LU of the remote subsystem, in the Simplex status once and then operate the pair.

DMER827049: The object LU of the remote subsystem is being formatted. Create the pair again after the formatting is completed.

DMER82704A: The S-VOL is in the S-VOL Disable mode. Cancel the S-VOL Disable specified for the LU of the remote subsystem.

DMER827050: The object LU of the remote subsystem has not undergone the forced restoration by means of parity or it is undergoing the restoration above. Make the status, which concerns the forced restoration by means of parity, of the LU of the remote subsystem to Restored or Skip.

DMER827053: The number of unified LUs of the remote subsystem is 17 or more.

Make the number of unified LUs of the remote subsystem 16 or less.

DMER827055: The object LU of the remote subsystem is a V-VOL of SnapShot (at the time of a pair formation). Specify the LU of the remote subsystem to a volume other than a V-VOL of SnapShot.

DMER827059: The license validity of the remote subsystem is expired. Purchase the license.

DMER82705A: The DM-LU is not set of the remote subsystem or the DM-LU was specified as S-VOL. Retry after setting the DM-LU or check the status of the LU.


DMER8270B3: The specified S-VOL is a unified LU including a SubLU with a capacity less than 1 GB. Check whether the LU with a capacity less than 1 GB is included in each LU of the specified unified LU.

DMER8270C4: When a new pair of a group is created, the cycle time that has been set for the local and remote array is less than the minimum interval. Check the cycle time that has been set for the local and remote array.


DMER8270C7: The specified S-VOL is the reserved LU. Perform the migration specifying an LU other than the reserved LU for the S-VOL.

DMER8270CA: The specified S-VOL is undergoing the migration. Perform the migration after deleting the pair.

DMER8270CB: The specified S-VOL is the reserved LU. Perform the migration specifying an LU other than the reserved LU for the S-VOL.



Error

Code

58270cf

Description

58270d1

58270d2

58270db

58270dd

58270de

58270e1

58270e3

58270e9

582901e

5829026

5829027

582902a

582903d

582905e

582905f

58290de

582a011

582a015


DMER8270D1: The disk drives that configure a RAID group, to which a target LU in the remote array belongs have been spun down. Perform the operation again after spinning up the disk drives that configure the RAID group.

DMER8270D2: The specified data pool number in the remote array is not same as the one that is being used for SnapShot. Confirm the indicated data pool number in the remote array.

DMER8270DB: The partition or pair partition to which the target LU belongs is incorrect. Check the partition number.





DMER8270E1: The operation to change LU has become timeout while the controller in the remote array is recovering. Retry the operation after the controller is recovered.


DMER8270E9: The LU created in DP pool was specified as S-VOL. Specify an LU other than the LU created in DP pool.







DMER82905E: There is a SnapShot pair, which has an MU number specified for a

SnapShot P-VOL, has not been placed in the Paired or Split status, and whose S-VOL is one of the S-VOLs with the specified group numbers. Check the pair status of the

SnapShot.

DMER82905F: There is no pair, which is in the Paired status, in the target group.


DMER8290DE: Auto Migration is being executed in the remote array just now.


DMER82A011: The indicated LU is in the Remote Replication pair for another subsystem. Confirm the pair status for the LU and also the Array ID.

DMER82A015: The status of the object LU is other than normal and regressive.

Make the LU status be normal or regressive.



Error

Code

582a01e

582a026

582a027

582a02a

582a02b

582a030

582a031

582a035

582a038

582a046

582a04a

582a050

582a059

582a05d

582a089

582a08b

582a08c

582a08d

582a090

582a091

582a095

Description

DMER82A01E: The object LU has been organized into a Remote Replication pair or the RAID group to which the object LU belongs indicates a status other than Normal.


DMER82A026: The remote subsystem is undergoing the pseudo deliberate shutdown. Execute again after the pseudo deliberate shutdown.

DMER82A027: The remote subsystem is after the pseudo deliberate shutdown. Wait a while and execute again.

DMER82A02A: The optional feature of Remote Replication of the remote array is disabled. Unlock and enable the optional feature.

DMER82A02B: Both of the two remote paths of the local array were detached. Check the status of the path.

DMER82A030: The S-VOL is undefined. Check the attribute of the LU.

DMER82A031: The WWN of the remote array is illegal. Check the equipment WWN.

DMER82A035: The optional feature of Remote Replication of the remote array is locked. Unlock and enable the optional feature.

DMER82A038: Both of the two paths of the remote array were detached. Check the status of the path.

DMER82A046: The indicated LU in the remote subsystem is being restored for

SnapShot or can not be executed the Read and Write command for the SnapShot pair. Execute again after having the SnapShot pair status in the remote subsystem be Simplex.

DMER82A04A: The S-VOL is 'S-VOL Disable' status. Release the indication for the 'S-

VOL Disable' in the remote subsystem.

DMER82A050: The indicated LU in the remote subsystem is in the forced parity correction, or has not executed the forced parity correction yet. Make the LU status for the forced parity correction in remote subsystem be Restored or Skip.

DMER82A059: The license of the remote subsystem expires. Purchase the license.

DMER82A05D: Now executing. Wait a while and execute again.

DMER82A089: The S-VOL of the remote array is in the status of S-VOL Disable.

Check the status of the remote array and cancel the access attribute.

DMER82A08B: The S-VOL in the remote array has no SnapShot cache block available. Check the data pool LU status of the remote array. In addition, delete unnecessary pairs of the remote array.

DMER82A08C: The SnapShot cache block for the S-VOL in the remote array is being deleted. Check the data pool LU status of the remote array and retry after waiting for a while.

DMER82A08D: The status of S-VOL in the remote array does not satisfy the condition to cascade with SnapShot pair. Check the status of the LU in the remote array.

DMER82A090: The status of S-VOL in the remote array does not satisfy the condition to cascade with SnapShot pair. Check the status of the LU in the remote array.

DMER82A091: The indicated Array ID is not same as the actual one for remote array. Confirm the Array ID for the remote array.

DMER82A095: The S-VOL in the remote array is undergoing the forced parity correction. Check the status of the remote array and retry after waiting for a while.



Error

Code

582a097

Description

582a09a

582a09f

582a0a0

582a0a1

582a0a2

582a0a3

582a0a4

582a0a5

582a0a6

582a0a7

582a0a8

582a0a9

582a0aa

582a0ab

582a0b4

582a0b5

582a0b6

582a0b7

DMER82A097: The S-VOL in the remote array received an illegal command. Check the status of the remote array.

DMER82A09A: The LU status of the S-VOL in the remote array is normal or other than regressed. Check the LU status of the remote array.

DMER82A09F: Splitting or deleting SnapShot pair is in progress. Retry after waiting for a while.

DMER82A0A0: The remote array has no data pool. Create a data pool in the remote array.

DMER82A0A1: The LU specified as the S-VOL in the remote array is a data pool LU.

The data pool LU cannot be set to an S-VOL. Check the data pool LU status of the remote array.

DMER82A0A2: The LU status of the S-VOL in the remote array is normal or other than regressed. Check the pool LU status of the remote array.

DMER82A0A3: The data pool LU in the remote array is undergoing the forced parity correction. Check the pool LU status of the remote array and retry after waiting for a while.

DMER82A0A4: The S-VOL in the remote array exceeded the total allowable maximum number of Remote Replication and SnapShot pairs. Check the status of the remote array. In addition, delete unnecessary pairs of the remote array.

DMER82A0A5: The Remote Replication pair status of the S-VOL in the remote array is Failure. Check the Remote Replication pair status of the remote array.

DMER82A0A6: The Remote Replication pair status of the S-VOL in the remote array is Pool Full. Check the Remote Replication pair status of the remote array.

DMER82A0A7: The Remote Replication pair status of the S-VOL in the remote array is Split (no read/write allowed). Check the Remote Replication pair status of the remote array.

DMER82A0A8: The Remote Replication pair status of the S-VOL in the remote array is Takeover (including Busy). Check the Remote Replication pair status of the remote array.

DMER82A0A9: The Remote Replication pair status of the S-VOL in the remote array is Simplex. Check the Remote Replication pair status of the remote array.

DMER82A0AA: The Remote Replication pair status of the S-VOL in the remote array is Split. Check the Remote Replication pair status of the remote array.

DMER82A0AB: The Remote Replication pair status of the S-VOL in the remote array is not Simplex. Check the Remote Replication pair status of the remote array.

DMER82A0B4: The S-VOL in the remote array does not exist on the default owner controller and, at the same time, the special processing cannot be continued. Check the status of the remote array and retry after waiting for a while.

DMER82A0B5: The S-VOL in the remote array does not exist on the default owner controller and at the same time an ownership of LU change for it has been started.

Check the status of the remote array and retry after waiting for a while.

DMER82A0B6: The S-VOL in the remote array does not exist on the default owner controller and it has started an ownership of LU change. Check the status of the remote array and retry after waiting for a while.

DMER82A0B7: The S-VOL in the remote array does not exist on the default owner controller and at the same time an ownership of LU to be changed is blocked. Check the status of the remote array and retry after waiting for a while.



Error

Code

582a0b8

582a0b9

582a0ba

582a0bb

582a0bc

582a0bd

582a0be

582a0c0

582a0c1

582a0c2

582a0d1

582a0d2

582a0d3

582a0db

582a0dd

582a0de

582a0e1

582a0e3

Description

DMER82A0B8: The S-VOL in the remote array cannot change an ownership of LU and at the same time it is using the sequential buffer. Check the status of the remote array and retry after waiting for a while.

DMER82A0B9: The S-VOL in the remote array cannot change an ownership of LU temporarily. Retry after waiting for a while.

DMER82A0BA: The S-VOL in the remote array cannot change an ownership of LU and at the same time it has pinned data. Contact the service personnel.

DMER82A0BB: The S-VOL in the remote array cannot change an ownership of LU temporarily. Retry after waiting for a while.

DMER82A0BC: The S-VOL in the remote array cannot change an ownership of LU temporarily. Retry after waiting for a while.

DMER82A0BD: The S-VOL in the remote array cannot change an ownership of LU and a time-out occurred. Check the status of the remote array and retry after waiting for a while.

DMER82A0BE: The S-VOL in the remote array cannot change an ownership of LU, and the group number is illegal. Check the status of the remote array.

DMER82A0C0: The S-VOL in the remote array does not exist on the default owner controller, and its disk drives are being spun up. Check the status of the remote array and retry after waiting for a while.

DMER82A0C1: The S-VOL in the remote array does not exist on the default owner controller, and the array is performing the system copy. Check the status of the remote array and retry after waiting for a while.

DMER82A0C2: The S-VOL in the remote array does not exist on the default owner controller, and the array is writing the configuration information. Check the status of the remote array and retry after waiting for a while.

DMER82A0D1: The disk drives that configure a RAID group, to which a target LU in the remote array belongs have been spun down. Perform the operation again after spinning up the disk drives that configure the RAID group.

DMER82A0D2: The S-VOL pool number in the remote array is not same as the one that is being used for SnapShot. Confirm the indicated data pool number in the remote array.

DMER82A0D3: The license has expired. Purchase the license.

DMER82A0DB: The partition or pair partition to which the target LU belongs is incorrect. Check the partition number.

DMER82A0DD: The firmware internal error occurred. Retry after waiting for a while.


DMER82A0DE: Auto Migration is being executed in the remote subsystem just now.


DMER82A0E1: The operation to change LU has become timeout while the controller in the remote array is recovering. Retry the operation after the controller is recovered.

DMER82A0E3: The RAID group to which the S-VOL of the remote array belongs indicates a status other than Normal. Retry after the status becomes Normal.





Alerts Produced by Hitachi Device

Manager Software

Hitachi Device Manager outputs alerts to the event log or to the syslog file on the Device Manager Server. This chapter lists and describes those alerts.



Alerts Output by Hitachi Device Manager



Trap Information Output by Storage Subsystems



Alerts about Storage Subsystem Components

Alerts Produced by Hitachi Device Manager Software


7-1

Alerts Output by Hitachi Device Manager

The Hitachi Device Manager outputs alerts to the event log or to the syslog file on the Device Manager Server. These alerts are categorized into the following seven types:



Trap information output by storage subsystems (see Trap Information

Output by Storage Subsystems ):

–

Trap information output by both the Lightning 9900V and 9900 subsystems:

Alert IDs KAID00001 to KAID00372 (see Table 7-1).

–

Trap information output for only the Lightning 9900:


– Trap information output for only the Lightning 9900V:


–

Trap information output for the Hitachi USP:


– Trap information output for the Universal Storage Platform V/VM:




Alerts about storage subsystem components (see Alerts about

Storage Subsystem Components

):

–

Alerts about components for the Universal Storage Platform V/VM,

Hitachi USP, Lightning 9900V and Lightning 9900 subsystems:


–

Alerts about components for the Hitachi AMS2000/AMS/WMS/SMS,

Thunder 9500V, and Thunder 9200 subsystems:


An alert level is added to each alert ID as follows:



I (Informational): Normal.



W (Warning): Moderate or Service.



E (Error): Acute or Serious.

7-2 Alerts Produced by Hitachi Device Manager Software


Trap Information Output by Storage Subsystems

This section contains:



Trap Information output by both the Lightning 9900V and 9900 subsystems:

Alert IDs KAID00001 to KAID00372 (Table 7-1)



Trap information output for only the Lightning 9900:




Trap information output for only the Lightning 9900V:




Trap information output for only the Hitachi USP:




Trap information output for only the Universal Storage Platform V/VM:


Table 7-1 KAID00001 to KAID00399: Trap Information Output by

Lightning 9900V and 9900 Subsystems

Alert ID Error Contents

KAID00001 LCP ERROR

KAID00002 LCP ERROR

KAID00003 FCP ERROR

KAID00004 PROCESSOR(CHA)

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

Information Displayed in DESCRIPTION Field

(all or part of the displayed information)

LCM HARDWARE ERROR

ADP PERMANENT ERROR

AL_PA VALUE CONFLICT

CHK1A THRESHOLD OVER

CHK1B THRESHOLD OVER

CHK3 THRESHOLD OVER

PROCESSOR BLOCKING

FM THRESHOLD OVER

FM ERROR

INCORRECT FM SUM

LDEV BLOCKADE(EFFECT OF PROCESSOR BLOCKADE)

P/S OFF IMPOSSIBLE



7-3

7-4



ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

KAID00030 PROCESSOR(DKA)

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR





P/S OFF IMPOSSIBLE(DEVICE RESERVED)

UNDEFINED PCB IS MOUNTED

V-R OR SERIAL NUMBER IS INCONSISTENT

RAID5 BOOSTER IS INCONSISTENT

REPLACE FAILED

MICROCODE VERSION UP

MICROCODE VERSION UP IMPOSSIBLE

PACKAGE TYPE CHANGED

PACKAGE TYPE EXCHANGE IMPOSSIBLE

PACKAGE TYPE EXCHANGE IMPOSSIBLE


WARNING OF SM DISABLE

SMA SLAVE ERROR

MPA SLAVE ERROR

INJUSTICE DC VOLTAGE CONTROL

INJUSTICE CE MODE

CHT PCB EXCHANGE IMPOSSIBLE (4GL<->4GS)

CHK1A THRESHOLD OVER

CHK1B THRESHOLD OVER

CHK3 THRESHOLD OVER

PROCESSOR BLOCKING

FM THRESHOLD OVER

FM ERROR



ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

KAID00054 SHSN ERROR

KAID00055 SHSN ERROR

KAID00056 CHSN ERROR










INCORRECT FM SUM

LDEV BLOCKADE(EFFECT OF PROCESSOR BLOCKADE)

P/S OFF IMPOSSIBLE

P/S OFF IMPOSSIBLE(DEVICE RESERVED)

UNDEFINED PCB IS MOUNTED

V-R OR SERIAL NUMBER IS INCONSISTENT

RAID5 BOOSTER IS INCONSISTENT

REPLACE FAILED

MICROCODE VERSION UP

MICROCODE VERSION UP IMPOSSIBLE


WARNING OF SM DISABLE

SMA SLAVE ERROR

MPA SLAVE ERROR


INJUSTICE CE MODE

FSW LED BUS TEST ERROR

TACHYON ERROR

LOGICAL PATH BLOCKADE(CHA)

LOGICAL PATH BLOCKADE(DKA)

LOGICAL PATH BLOCKADE(CHA CARB0)

LOGICAL PATH BLOCKADE(CHA CARB1)

LOGICAL PATH BLOCKADE(DKA-DRR CARB0)

LOGICAL PATH BLOCKADE(DKA-DRR CARB1)

LOGICAL PATH BLOCKADE(DKA-FCA CARB0)

LOGICAL PATH BLOCKADE(DKA-FCA CARB1)

7-5

7-6




KAID00064 CHA CHK2

KAID00065 CHA CHK2

KAID00066 DKA CHK2

KAID00067 DKA CHK2

KAID00068 DKA CHK2

KAID00069 DKA CHK2

KAID00070 DKA CHK2

KAID00071 DKA CHK2



LOGICAL PATH BLOCKADE(DKA-SCA1 CARB0)

LOGICAL PATH BLOCKADE(DKA-SCA1 CARB1)

RCHA TEMPORARY ERROR

RCHA BLOCKING

PINNED SLOT

DRR TEMPORARY ERROR

FCA TEMPORARY ERROR

DRR BLOCKING

FCA BLOCKING

FIBRE LOOP BLOCKING(EFFECT OF PATH INLINE FAILED)

KAID00073 CACHE ERROR




CORRECTABLE ERROR

CACHE TEMPORARY ERROR

MODULE GROUP BLOCKING

PACKAGE BLOCKING











KAID00088 SHARED MEMORY

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

PINNED SLOT

BOTH AREA FAILED

COEXISTENCE OF CACHE SIMM SIZES

AREA IS VOLATILED

PACKAGE IS VOLATILED

MODULE GROUP IS VOLATILED


INJUSTICE CE MODE

CORRECTABLE ERROR(2 BITS ERROR)

ON DEMAND FAILURE CMG DETECTED

CORRECTABLE ERROR

UNCORRECTABLE ERROR

AREA BLOCKING

REAL MEMORY SIZE INCONSISTENT

REPLACE FAILED

BOTH SIDE INVALID

CONFIGURATION INFORMATION COMPARE ERROR



Alert ID Error Contents Information Displayed in DESCRIPTION Field


SHARED MEMORY IS VOLATILED KAID00095 SHARED MEMORY

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

KAID00105 DRIVE ERROR(NORMAL

R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)

CONFIGURATION UNMATCH

DKCMAIN MICRO LOST

CHK3 THRESHOLD OVER

ON DEMAND FAILURE CMG DETECTED

AREA TEMPORARY BLOCKING

REBOOTED WITHOUT VOLATILIZATION

CONFIGURATION CHECK

LOSS OF DUPLICATED INFORMATION

ONE SIDE AREA IS VOLATILED

DRIVE PORT TEMPORARY ERROR(PATH 0)

DRIVE PORT TEMPORARY ERROR(PATH 1)

DRIVE TEMPORARY ERROR

DRIVE MEDIA ERROR

DRIVE PORT BLOCKADE(PATH 0)

DRIVE PORT BLOCKADE(PATH 1)

DRIVE BLOCKADE(DRIVE ERROR)

DRIVE BLOCKADE(EFFECT OF DRIVE COPY NORMAL END)

DRIVE BLOCKADE(MEDIA)

LDEV BLOCKADE(EFFECT OF FIBRE BLOCKADE)(PATH 0)

LDEV BLOCKADE(EFFECT OF FIBRE BLOCKADE)(PATH 1)

LDEV BLOCKADE(EFFECT OF DRIVE BLOCKADE)

CORRECTION COPY START



7-7

7-8



CORRECTION COPY NORMAL END KAID00118 DRIVE ERROR(NORMAL

R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)


R/W)

KAID00130 PAIR VOLUME STATUS

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

CORRECTION COPY ABNORMAL END

CORRECTION COPY DISCONTINUED

CORRECTION COPY WARNING END

DYNAMIC SPARING(DRIVE COPY)START

DYNAMIC SPARING(DRIVE COPY)NORMAL END

DYNAMIC SPARING(DRIVE COPY)ABNORMAL END

DYNAMIC SPARING(DRIVE COPY)DISCONTINUED

DYNAMIC SPARING(DRIVE COPY)WARNING END

INCORRECT SERIAL NUMBER IN MICRO EXCHANGE

PINNED SLOT

LDEV READ ONLY

REMOTE COPY START

REMOTE COPY START

REMOTE COPY START

REMOTE COPY NORMAL END



PAIR END

PAIR END

PAIR END

PAIR STATUS CHANGED

PAIR STATUS CHANGED





PAIR STATUS CHANGED KAID00141 PAIR VOLUME STATUS

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

PAIR END

PAIR END

PAIR END

SUSPEND END

SUSPEND END

SUSPEND END

HRC PAIR STATUS CHANGE(MCU COMMAND)



HRC PAIR SUSPEND(HOST COMMAND)


HRC PAIR SUSPEND(HOST COMMAND)

HRC PAIR STATUS CHANGE(HOST COMMAND)






PAIR SUSPEND END(HOST COMMAND)

PAIR SUSPEND END(HOST COMMAND)

PAIR END(HOST COMMAND)

PAIR END(HOST COMMAND)



7-9

7-10



MIGRATION COPY START KAID00164 PAIR VOLUME STATUS

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

MIGRATION COPY NORMAL END

PAIR END(HODM)

ERASE START(HODM)

ERASE END(HODM)

PAIR SUSPEND(RIO PATH CLOSED)



PAIR SUSPEND(M-VOL ERROR)



PAIR SUSPEND(R-VOL ERROR)



PAIR SUSPEND(DFW/DRV CACHE OFF)



PAIR SUSPEND(SUSPEND REPORT)



PAIR SUSPEND(SIMPLEX REPORT)







PAIR SUSPEND(PATH CLOSED) KAID00187 PAIR VOLUME STATUS

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

KAID00208 HMRCF/HOMRCF

ERROR


ERROR

PAIR SUSPEND(PATH CLOSED)

PAIR SUSPEND(PATH CLOSED)

PAIR SUSPEND(ERROR)

PAIR SUSPEND(ERROR)

PAIR SUSPEND(ERROR)

ERASE FAIL(HODM)

PAIR SUSPEND(MCU P/S OFF)

PAIR SUSPEND(MCU P/S OFF)

SIM REPORT(SERVICE)

SIM REPORT(SERVICE)

SIM REPORT(SERVICE)

SIM REPORT(MODERATE)



SIM REPORT(ACUTE/SERIOUS)



PAIR STATUS INCORRECT



COPY START

COPY COMPLETE



7-11

7-12



ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

KAID00232 HIHSM





SPLIT START

SPLIT COMPLETE

PAIR RESYNC START

PAIR RESYNC END

BACKUP SERVER ERROR(BACKUP FAILED)

BACKUP SERVER ERROR(LACK OF TAPE MEDIA)

BACKUP SERVER ERROR(LACK OF TAPE DEVICE)

BACKUP SERVER ERROR(MULTIPLE PROCESS ERROR)

PAIR COMPLETE

PAIR SUSPEND

PAIR SUSPEND

COPY WARNING END

COPY ABNORMAL END(S-VOL CLOSED)

COPY ABNORMAL END(T-VOL CLOSED)

COPY ABNORMAL END

RESERVE VOL DECREASE TO 1

(LDEV FAILED)

RESERVE VOL DECREASE TO 0

(LDEV FAILED)

ALL SP-PEND SUSPEND BY SM VOLATILE

IMPOSSIBLE TO CONTINUE HMRCF/HOMRCF COPY

INITIALIZE OF EXTENDED TABLE START

INITIALIZE OF EXTENDED TABLE COMPLETE

INITIALIZE OF EXTENDED TABLE ABEND



KAID00233 HIHSM

KAID00234 HIHSM

KAID00235 HIHSM

KAID00236 HIHSM

KAID00237 HXRC ERROR

KAID00238 DRIVE ERROR(ORM)




KAID00242 POWER ERROR











KAID00253 SVP I/F ERROR (CHA)

KAID00254 SVP I/F ERROR (CHA)

KAID00255 SVP I/F ERROR (DKA)

KAID00256 SVP I/F ERROR (DKA)

KAID00257 CSW ERROR

KAID00258 CSW ERROR

KAID00259 ENVIRONMENTAL

ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR

SIDE FILE 40% OVER

FIBRE TEMPORARY ERROR(PATH 0)

FIBRE TEMPORARY ERROR(PATH 1)

DRIVE TEMPORARY ERROR

DRIVE MEDIA ERROR

HDU POWER-OFF DETECTED

HDU POWER RECOVERY

POWER FAILURE MODE SET

POWER FAILURE MODE RESET

DESTAGING STARTUP NORMAL

DESTAGING STARTUP FAILED

AC LINE OFF

AC LINE OFF RECOVER

UPS BATTERY FAIL

URGENT DESTAGING START

URGENT DESTAGING END

ETHERNET ERROR FOR SVP

SIM TRANSFER FAILURE TO SVP

ETHERNET ERROR FOR SVP

SIM TRANSFER FAILURE TO SVP


INJUSTICE CE MODE

TEMPERATURE(OVER 60 DEGREE)




5 VOLTAGE ALARM

3 VOLTAGE ALARM

VOLTAGE(SM 3V) WARNING



7-13

7-14



ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR





VOLTAGE(CM 3V) WARNING

5/3V PS WARNING

5/3V PS WARNING

3V PS WARNING

3V PS WARNING

3V PS WARNING

3V PS WARNING

SUB PS WARNING

HDD MPS1 WARNING

BATTERY WARNING

BATTERY WARNING

BATTERY WARNING

BATTERY WARNING

BATTERY WARNING

BATTERY WARNING (DIAG)




AC WARNING

FAN ABNORMALITY FLGFAN12B


FAN ABNORMALITY FLGFAN12A




ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR


ERROR









FAN ABNORMALITY RLGFAN11B


FAN ABNORMALITY RLGFAN11A






FAN ABNORMALITY RPSFAN11B


FAN ABNORMALITY RPSFAN11A






JP SETTING FAILURE (DKC ALARM INHIBITION JP)

JP SETTING FAILURE (HDU0-3 ALARM INHIBITION JP)

JP SETTING FAILURE (HDU4-7 ALARM INHIBITION JP)

7-15



ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR


MONITOR ERROR

KAID00329 SVP ERROR

KAID00330 SVP ERROR

KAID00331 SVP ERROR

KAID00332 SVP ERROR



JP SETTING FAILURE (SVP PS OFF/ON INHIBITION JP)

ENVIRONMENT MONITOR ACCESS ERROR

ENVIRONMENT MONITOR ACCESS ERROR DKCMN1

ENVIRONMENT MONITOR ACCESS ERROR DKCMN2

ENVIRONMENT MONITOR BUSY

DIAGNOSTIC MODE SETTING FAILURE

INCORRECT DKCMN TYPE

ALARM DISAGREEMENT ERROR

ALARM DISAGREEMENT ERROR DKCMN1

ALARM DISAGREEMENT ERROR DKCMN2

DISAGREEMENT ERROR OF P/S

DISAGREEMENT ERROR OF P/S DKCMN1

DISAGREEMENT ERROR OF P/S DKCMN2

LOGICAL INCONSISTENCY

HEAP ERROR

FILE ERROR

LAN ERROR

7-16

KAID00335 SVP ERROR

KAID00336 SVP ERROR

KAID00337 SVP ERROR

KAID00338 SVP ERROR

KAID00340 SVP ERROR

KAID00341 PERIODIC CHECK

ERROR

KAID00342 END STATUS OF

REMOTE MICRO

EXCHANGE

CUDG3 DETECTED ERROR

LCDG3 DETECTED ERROR

BOOT DETECTED ERROR(CHA)

BOOT DETECTED ERROR(DKA)

FD REMAINS IN FDD

OVER LIFE SPAN OF BATTERY

NORMAL END






REMOTE MICRO

EXCHANGE


REMOTE MICRO

EXCHANGE


REMOTE MICRO

EXCHANGE


REMOTE MICRO

EXCHANGE


REMOTE MICRO

EXCHANGE


REMOTE MICRO

EXCHANGE


REMOTE MICRO

EXCHANGE

ABNORMAL END(SVP)

ABNORMAL END(MP)

VERSION CHK ERROR

SUM CHK ERROR

LCP PATCH ERROR

WARNING(CONFIGURATION INCONSISTENCY)

WARNING(S-SVP BUSY)


REMOTE MICRO

EXCHANGE

WARNING(LCP BUSY)

KAID00351 DKC INTERNAL ERROR SSB(24 BYTE FORM) REPORTED

KAID00352 DKC INTERNAL ERROR SSB(32 BYTE FORM) REPORTED

KAID00353 HOST I/F ERROR




BUSOUT PARITY ERROR

DATA OVERRUN

OFFLINE SEQUENCE

INCIDENT

KAID00358 TRIAL KEY

KAID00361 DUMP RECEIVED

WARNING OF TRIAL PERIOD

DUMMY

ABEND DUMP(CHA)

KAID00363 DUMP RECEIVED

KAID00364 BACKUP SERVER





ABEND DUMP(DKA)

BACKUP SERVER FAILURE DETECTED BY SVP

ATL FAILURE

MT FAILURE

OS FAILURE

NETWORKER ERROR



7-17

7-18


KAID00370 DRIVE ERROR





PRE STAGING START

PRE STAGING NORMAL END

PRE STAGING ABNORMAL END

Table 7-2 KAID00501 to KAID00599: Trap Information Output by the

Lightning 9900 Subsystem


KAID00501 LCP ERROR


ADP TEMPORARY ERROR

KAID00503 LCP ERROR

KAID00504 LCP ERROR

KAID00505 LCP ERROR

KAID00506 ENVIRONMENTAL ERROR




RIO PATH CLOSED

RIO PATH AUTOMATICALLY RECOVERED

LOGICAL PATH(REMOTE COPY) CLOSED

12 VOLTAGE ALARM

HDD MPS0 WARNING


FAN ABNORMALITY


Lightning 9900V Subsystem


KAID00701 LCP ERROR


ADP TEMPORARY ERROR

KAID00703 LCP ERROR

KAID00704 LCP ERROR

KAID00710 HTP ERROR

KAID00711 HTP ERROR

KAID00712 HTP ERROR

KAID00731 HMRCF/HOMRCF ERROR

KAID00751 ENVIRONMENT ERROR

KAID00752 ENVIRONMENT ERROR

KAID00801 SVP DETECTED ERROR





RIO PATH CLOSED

RIO PATH AUTOMATICALLY RECOVERED

HTP HARD ERROR

HTP PATH BLOCKAGE

HTP BLOCKAGE

ShadowImage ABNORMAL END BY SM VOLATILE

ShadowImage ABNORMAL END

ABNORMAL SVP PS Cluster-1

ABNORMAL SVP PS Cluster-2

ABNORMAL AC

ABNORMAL AC RECOVERING

ABNORMAL UPS BATTERY

EMERGENCY DESTAGE START

EMERGENCY DESTAGE END




KAID00820 PROCESSOR (NAS OS CHA)

ERROR


ERROR


ERROR


ERROR


ERROR

KAID00850 PAIR VOLUME STATUS ERROR



KAID00880 SHARED MEMORY ERROR






PROCESSOR FOR NAS OS ERROR

PROCESSOR FOR NAS OS ENVIRONMENT ERROR

NAS OS ERROR

BUS FOR NAS OS ERROR

NETWORK PORT ERROR

P-VOL SUSPEND (continue)

P-VOL SUSPEND (complete)

SUSPENDED (complete) P-VOL ACCEPT UPDATE IO

HPAV MICRO LOST

12 VOLTAGE ALARM

HDD MPS0 WARNING


FAN ABNORMALITY


Hitachi USP Subsystem


KAID00901 LCP/FCP/HTP error






KAID00907 CHA Processor error


KAID00909 CHA NAS OS Processor failure






KAID00915 DKA Processor error


KAID00917 CHSN error


ADP temporary error

ADP blocking

HTP hardware error

HTP path temporary error

HTP path blockage

HTP blockage

CHA patrol check error

CHA memory correctable error

NAS OS Processor failure

NAS OS Processor Environmental Error

NAS OS failure : Occurrence of a failover or a resource (failure part not reported)

NAS OS failure

NAS OS bus error

Network port failure

DKA patrol check error

DKA memory correctable error

Logical path blockage (CHA-DMA1/CARB0)



7-19

7-20





KAID00921 Shared memory error






KAID00927 Drive error (normal R/W)

KAID00928 Drive microcode exchange (OEM drive)




KAID00932 CSW error

KAID00933 CSW error

KAID00934 SVP interface error (CHA side)


KAID00936 SVP interface error (DKA side)


KAID00938 Server error

KAID00939 LCP/FCP error (Remote Control

Port)


Port)

KAID00941 Pair volume error





KAID00946 Cache error



KAID00949 Drive error(normal R/W)

KAID00950 Drive error(normal R/W)


Logical path blockage (CHA-DMA1/CARB1)

Logical path blockage (CHA-PMA/CARB0)

Logical path blockage (CHA-PMA/CARB1)

SMA patrol check error

Duplicated information lost

One side volatilized

HPAV micro lost

Incorrect DC voltage controller

Incorrect CE MODE

Drive blockage by incompatible DKU type

OEM drive microcode exchange start

OEM drive microcode exchange normal end

OEM drive microcode exchange abnormal end

OEM drive microcode exchange discontinued

CARB patrol check error

CARB memory correctable error

Ethernet error for SVP

SIM transfer failure to SVP



DB validation error

Remote copy logical path blockage (due to error status)

Remote copy logical path recovery

M-VOL has been suspended (continue)

M-VOL has been suspended (complete)

The suspended (complete) M-VOL has accepted the update I/O

Link failure 1

Link failure 2

Cache Module Blockade Processing end

Cache Package Blockade Processing end

Recovery of area blocked temporarily was completed

Drive blockade (drive)(RAID6 1drive blockade)

Drive blockade (media)(RAID6 1drive blockade)





Port)

KAID00952 Pair volume status error


KAID00954 HMRCF error or HOMRCF error




KAID00958 Hi-Copy error

KAID00959 Copy-on Write Snapshot error

KAID00960 Copy-on Write Snapshot error

KAID00961 Pool error


KAID00963 External Subsystem Connection


MCU has received the notification of communication line error detection from extender.

None.

None.

ShadowImage-FlashCopy(R) Option abnormal end

ShadowImage-FlashCopy(R) version2 Option abnormal end

All ShadowImage-FlashCopy(R) version2 Option abnormal end by SM volatile

Forcible suspend by SM volatile

Copy abnormal end


Copy-on Write Snapshot Option abnormal end

Pool utilization threshold excess

Pool blocking

External Subsystem path response time out threshold over

KAID00965 Environmental error



P/S warning DKU-XXX

HDD-PL 56V Voltage fall 56V Voltage fall 1

HDD-PL 56V Voltage fall 56V Voltage fall 2


KAID00975 Virus detected



KAID00978 External Subsystem path blockade

Fan abnormality FAN fuse blow out

Clean virus from file

Quarantine infected file

Leave alone

External Subsystem path blockade



7-21


Universal Storage Platform V/VM Subsystem











KAID01012 CHA CHK2

KAID01013 DKA CHK2

KAID01014 DKA CHK2






ADP permanent error

ADP blocking

Link failure 1

Link failure 2

LCP/FCP/HTP hard error

LCP/FCP/HTP path blocking

LCP/FCP/HTP blocking

Processor blocking

FM error

Processor blocking

FM error

RCHA blocking

DRR blocking

FCA blocking

Cache Module Blockade Processing end

Cache Package Blockade Processing end

Cache temporary error

Module group blocking

7-22













KAID01033 Power error

HPAV micro lost

Recovery of area blocked temporarily was completed

Drive blockade (drive) (with redundancy)

Drive blockade (drive) (without redundancy)

Drive blockade (media) (with redundancy)

Drive blockade (media) (without redundancy)

Correction copy warning end (With blockade LDEV or some error)

Dynamic sparing warning end (With blockade LDEV or some error) (Drive copy)





HDU power off





Port)


Port)


Port)























Logical path(s) on the remote copy connections was logically blocked (Due to an error conditions)

The logical path has been recovered from blocked condition on the remote copy conditions.

MCU has received the notification of communication line error detection from extender.

HRC started the initial copy or out of sync for this volume.

HRC completed the initial copy for this volume.

HRC for this volume was deleted. (Operation from an

SVP/remote console or a host processor)

Pair formation completion by HRC(NO copy suspension)

Status of the R-VOL is changed.

HODM started the migration copy or out of sync for this volume.

HODM completed the migration copy for this volume.

HODM for this volume was deleted. (Operation from an SVP/remote console)

HRC/HODM for this volume was suspended (Due to an unrecoverable failure on the remote copy connections.)

HRC/HODM for this volume was suspended (Due to an unrecoverable failure on the M-VOL or the remote copy connections)

HRC/HODM for this volume was suspended (Due to an unrecoverable failure on the R-VOL)

HRC for this volume was suspended (Caused by DFW to the R-VOL was prohibited)

HRC for this volume was suspended (Due to an internal error condition detected by the RCU)

HRC for this volume was suspended (Caused by

Delete pair operation was issued to the R-VOL)

Erase operation for this volume was not completed.

(Due to error conditions)

MCU detected a Moderate Level SIM for RCU.

MCU detected an Acute or Serious Level SIM for

RCU.

Status of the M-VOL was not consistent with the R-

VOL.

HRC started the initial copy or out of sync for this volume.

HRC completed the initial copy for this volume.

HRC for this volume was accepted delete pair operation. (Operation from an SVP/remote console or a host processor)



7-23

7-24



























HRC for this volume was accepted suspend pair operation. (Operation from an SVP/remote console or a host processor)

Delete pair operation for this HRC volume has completed.

Suspend pair operation for this HRC volume has completed.

Pair formation completion by HRC(NO copy suspension)

The R-VOL status has changed as requested by MCU.

The M-VOL has suspended. (Due to an unrecoverable failure on the remote copy connections.)

The M-VOL has suspended. (Due to an unrecoverable failure on the M-VOL or the remote copy connections)

The M-VOL has suspended. (Due to an unrecoverable failure on the R-VOL)

The M-VOL has suspended. (Caused by DFW to the

R-VOL was prohibited)

The M-VOL has suspended. (Caused by Suspend pair operation was issued to the R-VOL)

The M-VOL has suspended. (Caused by Delete pair operation was issued to the R-VOL)

The R-VOL has suspended. (Due to an unrecoverable failure on the remote copy connections)

The R-VOL has suspended. (Due to an unrecoverable failure on the R-VOL)

MCU detected a Service Level SIM for RCU.

MCU detected a Moderate Level SIM for RCU.

MCU detected an Acute or Serious Level SIM for

RCU.

Status of the M-VOL was not consistent with the R-

VOL.

A volume being used by an M-VOL changed status to suspend (continue).

A volume being used by an M-VOL changed status to suspend (complete).

The volume of suspension (complete) did update I/O acceptance with M-VOL and it suspended it. (Accept in complete update I/O.)

Copy abnormal end

ShadowImage-FlashCopy (R) Option abnormal end

All ShadowImage-FlashCopy (R) Option abnormal end by SM volatile

ShadowImage-FlashCopy (R) version2 Option abnormal end






KAID01084 HXRC/HRCA error

KAID01085 Hi-Copy error

KAID01086 Copy-on-Write Snapshot error

KAID01087 Copy-on-Write Snapshot error






KAID01093 Pair volume failure
















All ShadowImage-FlashCopy (R) version2 Option abnormal end by SM volatile


Sidefile 'sleep wait' threshold over

Copy abnormal end


Copy-on Write Snapshot Option abnormal end

Pool utilization threshold excess

Pool blocking

External Subsystem Connection Path Failure

External Subsystem path response time out threshold over

External Subsystem Device failure

A volume to be used by the UR was defined

The volume being used by the UR began a copying

The volume being used by the UR completed a copying

The volume being used by the UR received a request for suspension

The volume being used by the UR completed a suspension transaction

The volume being used by the UR received a request for deletion

The volume being used by the UR completed the deletion

The volume being used by the UR was defined

(placed in the PSUS status immediately)

A change to an SVOL was received from the MCU

A volume being used by a P-VOL was suspended

(Path recovery was impossible)

A volume being used by a P-VOL was suspended (A failure on the MCU side was detected)


(Suspension of an S-VOL was detected)


(Deletion of an S-VOL pair was detected)

A volume being used by an S-VOL was suspended

(Path recovery was impossible)

A volume being used by an S-VOL was suspended (A failure on the RCU side was detected)

Temperature Abnormal Alarm Front of cabinet Left

Side (TH11 detect)

Temperature Abnormal Alarm Front of cabinet Right

Side (TH12 detect)



7-25

7-26
































Temperature Abnormal Alarm Back of cabinet Left

Side (TH21 detect)

Temperature Abnormal Alarm Back of cabinet Right

Side (TH22 detect)

Temperature Abnormal Warning Front of cabinet Left

Side (TH11 detect)

Temperature Abnormal Warning Front of cabinet

Right Side (TH12 detect)

Temperature Abnormal Warning Back of cabinet Left

Side (TH21 detect)

Temperature Abnormal Warning Back of cabinet

Right Side (TH22 detect)

Voltage alarm (LOGIC) Cluster-1

Voltage alarm (LOGIC) Cluster-2

Voltage alarm (MEMORY) Cluster-1

Voltage alarm (MEMORY) Cluster-2

P/S warning PS11

P/S warning PS21

P/S warning PS12

P/S warning PS22

P/S warning PS13

P/S warning PS23

P/S warning PS14

P/S warning PS24

P/S warning PS15

P/S warning PS25

P/S warning PS16

P/S warning PS26

P/S warning BAT-REG(MN1)

P/S warning BAT-REG(MN2)

P/S warning PS Warning

HDD-PL Voltage fall 56V Voltage fall

HDD-PL Voltage fall 37V Voltage fall

Battery warning BATTERY-11






























KAID01167 SVP failure

KAID01168 SVP failure License key















Battery warning DKUBATTERY

AC warning (3-phase) AC-BOX1




Fan abnormality FFAN1

Fan abnormality RFAN1







Fan abnormality FAN WARNING

Fan abnormality FAN fuse blow out

JP remains PS ON JP

JP remains SVP PS ON/OFF (Basic SVP)

JP remains SVP PS ON/OFF (Optional SVP)

Duplex SVP Setup fail

ISDN Router failure

The term of validity is over

Clean virus from file

Quarantine infected file

Leave alone


(Suspension of an S-VOL failure was detected)

DP Pool utilization threshold excess 1

DP Pool utilization threshold excess 2

DP Pool overflow

DP Pool fail

DP VOL utilization threshold excess



7-27

Alerts about Storage Subsystem Components

This section contains:



Alerts about components for the Universal Storage Platform V/VM, Hitachi

USP, Lightning 9900V, and 9900 subsystems:

Alert IDs KAID10001 to KAID10012 (see Table 7-6)



Alerts about components for the Hitachi AMS2000/AMS/WMS/SMS,

Thunder 9500V, and Thunder 9200 subsystems:

Alert IDs KAID11001 to KAID11023 (see Table 7-7)

Table 7-6 KAID10001 to KAID10099: Alerts about components for

Universal Storage Platform V/VM, Hitachi USP, Lightning

9900V, and Lightning 9900 subsystems

Alert ID Information Displayed in COMPONENT

Field (indicating the alert part of a storage subsystem)


KAID10002 DKC Cache Switch

KAID10004 DKC Shared Memory

KAID10005 DKC Power Supply

KAID10009 DKU Power Supply

The information displayed in the

DESCRIPTION field depends on the alert level.

The information displayed in the

DESCRIPTION field is as follows:



When the alert level has been changed from another level to Normal:



This indicates that the cause of an Acute,

Serious, Moderate, or Service status has been corrected, and the status has returned to normal.

When the alert level is Acute, Serious,

Moderate, or Service:

Any Acute, Serious, Moderate, or Service, the error is reported in

COMPONENT

.



Table 7-7 KAID11001 to KAID11099: Alerts about components for

Hitachi AMS2000/AMS/WMS/SMS, Thunder 9500V, and

Thunder 9200 subsystems

Information displayed in DESCRIPTION field Alert ID Information displayed in the

COMPONENT field

(indicating the alert part of a storage subsystem)

KAID11001 Cache

KAID11003 Fan

KAID11004 AC

KAID11005 Battery

KAID11007 Controller

KAID11008 Enclosure

KAID11009 Loop

The information displayed in the field depends on the alert level.

DESCRIPTION

The information displayed in the field is as follows:

DESCRIPTION



When the alert level has been changed from another level to Normal:



This indicates that the cause of an Acute,

Serious, Moderate, or Service status has been corrected, and the status has returned to normal.

When the alert level is Acute, Serious,

Moderate, or Service:

Any Acute, Serious, Moderate, or Service, the error is reported in

COMPONENT.

KAID11011 CTU Power Supply

KAID11014 Connector

KAID11015 NNC

KAID11017 NNC Power Supply

KAID11023 NNC ExSlot HCT



7-29



Error Messages from the Hitachi

Storage Command Suite Common

Component

This chapter lists and describes the error messages output by the Hitachi

Storage Command Suite Common Component:



Error Messages Output by Hitachi Storage Command Suite Common

Component

Error Messages from the Hitachi Storage Command Suite Common Component


8-1

Error Messages Output by Hitachi Storage Command Suite

Common Component

This chapter lists and describes the error messages output by the Hitachi

Storage Command Suite Common Component. An error message from the

Hitachi Storage Command Suite Common Component consists of a message

ID and the error message text. The format is as follows:



Format:

KAPMmmmmm-z message-text (see Table 8-1)

KDJEmmmmm-z message-text (see Table 8-2)

KEHGmmmmm-z message-text (see Table 8-3)

mmmmm is a message number, and z is one of the following message levels:

–

I: Information

–

W: Warning

–

E: Error



Output destination:

– Output level 0

The error message is output to syslog or the event log, integrated trace, and original log trace.

–

Output level 10

The error message is output to the original log trace.

Some of the error messages might be output to the integrated log trace for UNIX.

Table 8-1, Table 8-2, and Table 8-3 list the Hitachi Storage Command Suite

Common Component error messages, and provide recommended actions for resolving the error conditions. If the problem cannot be resolved, collect maintenance information, and then contact the Hitachi Data Systems Support

Center (see Calling the Hitachi Data Systems Support Center for contact

information).

8-2 Error Messages from the Hitachi Storage Command Suite Common Component


Table 8-1 Hitachi Storage Command Suite Common Component

Messages (KAPM)

Error Code Error Message

KAPM00001-E

KAPM00002-E

ID=aa...aa,LogTraceLibrary error. Trace

START failed. bb...bb

aa...aa: ID of the program using the log

bb...bb: Error message output by the log trace library when the system failed to start the trace

Output destinations: syslog/Eventlog

ID=aa...aa,LogtraceLibrary error. Trace

STOP failed. bb...bb


bb...bb: Error message output by the log trace library when the system failed to stop the trace


KAPM00003-W ID=aa...aa,Trace output error.



KAPM00004-W

ID=aa...aa,Integrated trace output error.



KAPM00005-E File I/O failed.(filename=aa...aa).

aa...aa: Name of the version file


KAPM00006-E ID=aa...aa,Invalid eventlog source.

Eventlog's config not found in the registry(source name="HiCommand

Log")



KAPM00011-E ID=aa...aa,Versionfile name is null.



Description and Action

An attempt to start the log trace has failed.

Collect maintenance information and contact the Support Center.

An attempt to start the log trace has failed.


An attempt to output the log trace has failed.

Check whether the log file is read only.

An attempt to output an integrated log trace has failed.

Check whether the Hitachi Network

Objectplaza Trace Monitor 2 service is running.

An attempt to create a version file has failed.

Check whether the version file specified for aa...aa can be written.

The registry for Eventlog was not found.


KAPM00012-E ID=aa...aa,PP version is null.



KAPM00013-E ID=aa...aa,Trace log file name is null.



The version file name has not been specified.


The version of each PP has not been specified.


The name of the individual log trace has not been specified.




8-3


KAPM00014-E ID=aa...aa,Class name is null.



KAPM00015-E ID=aa...aa,Kind of Event is null.



KAPM00016-E ID=aa...aa,Message-ID is null.



KAPM00017-E

KAPM00018-E

KAPM00019-E

KAPM00020-E

KAPM00021-E

KAPM00022-E

aa...aa

aa...aa: NullPointerException message


aa...aa

aa...aa: Exception message



The class name of the program to be used to output the log has not been specified.


The value that indicates the type of message event for output has not been specified.


The message ID for the message to be output has not been specified.


A NullPointerException occurred in

LogTraceManager.


An unexpected exception occurred in

LogTraceManager.


The ID (bb...bb) length attached to

Eventlog is too long.


ID=aa...aa,SyslogID size error:idEnt=bb...bb


bb...bb: Eventlog ID


ID=aa...aa,Invalid version length:version=bb...bb


bb...bb: Version character string


ID=aa...aa,Invalid log file number:logNum=bb...bb


bb...bb: Number of individual log trace files


ID=aa...aa,Invalid log file size:logSize=bb...bb


bb...bb: File size of the individual log trace


The version character string is too long.


The number of individual log trace files is invalid.


The size of an individual log trace file is invalid.




Error Code

KAPM00023-E

KAPM00024-E

KAPM00025-E

KAPM00090-I

KAPM00091-E

KAPM00092-I

KAPM00102-E

KAPM00103-E

KAPM00104-E

KAPM00105-E

Error Message

ID=aa...aa,Invalid message type:kind=bb...bb


bb...bb: Message type


ID=aa...aa,Invalid output level:level=bb...bb


bb...bb: Output level


The value of the encoding setting

bb...bb of the unique log output of

aa...aa is invalid.

aa...aa: Program name request to output log

bb...bb: Encoding


The SSO server started successfully.


An attempt to start the SSO server has failed.


The SSO server was stopped successfully.



A value indicating the message type is invalid.


An invalid log output level exists in the code.


The value of the encoding setting bb...bb of the unique log output of aa...aa is invalid.






Output destinations: Destinations for output level 10, and windows.

An error occurred during DBMS access processing.

Output destinations: Destinations for output level 10.

The DBMS is not running.


The product name is not specified.


An unexpected value was returned from the integrated authentication server.

(aa...aa)

aa...aa: Unexpected return value


An authentication error occurred.


An error occurred during DBMS access processing.



Make sure the DBMS has started.



An unexpected value was returned from the integrated authentication server.




8-5

Error Code

KAPM00106-E

KAPM00107-E

KAPM00108-E

KAPM00110-E

KAPM00111-I

KAPM00112-I

KAPM00113-I

KAPM00114-I

KAPM00115-E

KAPM00116-E

KAPM00117-E

Error Message

An attempt to update the authentication data has failed.


An attempt to delete the authentication data has failed.


An attempt to print the authentication data has failed.



An attempt to update the authentication data has failed.


An attempt to delete the authentication data has failed.

Retry execution. If the problem cannot be solved, collect maintenance information and contact the Support

Center.

An attempt to print the authentication data has failed.


Center.

The HSSOContext value is invalid.


The authentication data was successfully updated.

The HSSOContext value is invalid.


The authentication data was successfully updated.


The authentication data was successfully deleted. (aa...aa)

aa...aa: Product name


The authentication data is already deleted. (aa...aa)



The authentication data was successfully displayed.



SSO server has failed.


An attempt to update authentication data has failed.


The RD area of HBase is blocked.


The authentication data was successfully deleted.

The authentication data is already deleted.

The authentication data was successfully displayed.

An attempt to communicate with the SSO server has failed.


This message is displayed when an attempt to update authentication data fails.

Please restart the Single Sign On server.


Remove the cause of the HiRDB blockage, and then try again.



Error Code

KAPM00119-E

KAPM00130-E

KAPM00131-E

KAPM00132-E

KAPM00133-E

KAPM00134-E

KAPM00138-E

KAPM00139-I

KAPM00140-I

KAPM00141-E

KAPM00145-E

Error Message

Deletion of the license event data has failed.


There is no value in the request.


A required token is not specified.


The event name is invalid.




An error occurred during a DBMS access.



Deletion of the license event data has failed.

Make sure the DBMS has started, and then retry the operation. If you cannot solve the problem, collect the maintenance information, and then contact the Support Center.

There is no value in the request.


A required token is not specified.


The event name is invalid.




An error occurred during a DBMS access.



Authentication data for delete processing is invalid.


Deletion of authentication data for all products will now start.


Deletion of authentication data will now start.

Application name: aa...aa

Service name: bb...bb

aa...aa: Application name

bb...bb: Service name


An attempt to lock the table has failed.






Authentication data for delete processing is invalid.


Deletion of authentication data for all products will now start.

Deletion of authentication data will now start.







8-7

Error Code

KAPM00162-E

KAPM00163-E

KAPM00192-E

KAPM00199-E

KAPM00203-E

KAPM00204-E

KAPM00205-E

KAPM00206-E

Error Message

There is an error in the protocol.

(element = aa...aa)

aa...aa: Element



(element = aa...aa, attribute = bb...bb, value = cc...cc)

aa...aa: Element

bb...bb: Attribute

cc...cc: Value


An exception was detected.


aa...aa

aa...aa: Name of the exception object and the reason that object was thrown, or the backtrace for that object






An error occurred during access to the

DBMS.


The specified event data has already been registered. (application type =

aa...aa, event type = bb...bb, event code = cc...cc)

aa...aa: Application type

bb...bb: Event type

cc...cc: Event code







An exception was detected.


Detailed information for KAPMxxxxx-E.

This indicates the thrown exception object and the backtrace for that object.

See the message KAPMxxxxx-E.





An error occurred during access to the

DBMS.

Collect maintenance information, and then contact the Support Center.

The specified event data has already been registered.




Error Code

KAPM00207-E

KAPM00208-E

KAPM00210-E

KAPM00211-E

KAPM00212-E

KAPM00213-E

Error Message

Event data cannot be updated because no event data exists. (application type =

aa...aa, event type = bb...bb, event code = cc...cc)





Communication with the SSO server has failed.



A program type specified for

TNB_SoftwareFeature is not registered.

(application type = aa...aa)



Associated data does not exist.

(application type = aa...aa)



An event management object cannot be deleted because the specified parameter is invalid. (application type = aa...aa, event type = bb...bb, event code =

cc...cc)





The value registered in the database is invalid. (application type = aa...aa, event type = bb...bb, event code =

cc...cc)






Event data cannot be updated because no event data exists.


Communication with the SSO server has failed.

Make sure the following have started: the

HBase Storage Mgmt Common Service or

HBase Storage Mgmt Web Service, and the database.

Authentication has failed.


A program type specified for

TNB_SoftwareFeature is not registered.


Associated data does not exist.


An event management object cannot be deleted because the specified parameter is invalid.


The value registered in the database is invalid.




8-9

8-10


KAPM00214-E

KAPM00215-E

The same information is already registered in the database. (application type = aa...aa, event type = bb...bb, event code = cc...cc)





An attribute value is invalid. (attribute =

aa...aa)

aa...aa: Attribute


KAPM00216-W The attribute length exceeds the maximum limit. (attribute = aa...aa, value = bb...bb, maximum limit =

cc...cc)

aa...aa: Attribute

bb...bb: Value

cc...cc: Maximum limit


KAPM00217-E An invalid parameter is specified.


KAPM00252-E

KAPM00253-E

The license information file does not exist. (license information file = aa...aa)

aa...aa: License information file


The license information file might be corrupted. (license information file =

aa...aa)



KAPM00254-E

KAPM00255-E

An attempt to read the license information file has failed. (license information file = aa...aa)



The license information file cannot be accessed. (license information file =

aa...aa) aa...aa: License information file



The same information is already registered in the database.


An attribute value is invalid.


The attribute length exceeds the maximum limit.


An invalid parameter is specified.


The license information file does not exist.


The license information file might be corrupted.


An attempt to read the license information file has failed.


The license information file cannot be accessed.




Error Code

KAPM00900-I

KAPM00901-E

KAPM00902-I

KAPM01001-I

KAPM01002-E

KAPM01003-E

KAPM01004-E

Error Message







Initializing HssoServer configuration.


The system property indicated by hcmds.home

could not be found.


HssoServerRes1_0.dtd was not found. path = aa...aa

aa...aa: Path of file

HssoServerRes1_0.dtd


Can't read DTD files.


KAPM01005-W Failed to close FileStream.






Servlet initialization has started.

The system property indicated by hcmds.home

could not be found.


HssoServerRes1_0.dtd

was not found.


An attempt to read the DTD file has failed.


An attempt to close FileStream has failed.

The IP address of the requesting client.

KAPM01010-E

aa...aa: IP address


Can't get InputStream from Request.


KAPM01013-E

KAPM01017-E

KAPM01019-E

Unsupported command was requested.


Unsupported method was requested.


Unsupported method was requested.


An attempt to acquire an InputStream from a client's request has failed.


The requested command name is invalid.


The requested method name is invalid.


The requested method name is invalid.




8-11

8-12

Error Code

KAPM01024-I

KAPM01025-E

KAPM01026-E

KAPM01028-E

KAPM01034-E

KAPM01036-E

KAPM01040-E

KAPM01042-E

KAPM01046-E

KAPM01051-E

Error Message

Request Information: Version = aa...aa,

Command = bb...bb, ID = cc...cc

aa...aa: Version

bb...bb: Command

cc...cc: ID


A fatal error occurred.


An attempt to initialize the HSSO Server configuration has failed.


The file "aa...aa" could not be read. Path

= bb...bb

aa...aa: File name

bb...bb: File path name


Can't get the required information from request. Request is invalid.


Request XML can't parse to DOM. -

aa...aa



XML version aa...aa for HssoClient is not supported.

aa...aa: Request version


An attempt to parse the request has failed.


The format of the request was invalid.

Cause = aa...aa

aa...aa: Cause


The creation of HSSOContext for authentication has failed. aa...aa




The request information will be displayed.



An attempt to initialize the HSSO server configuration has failed.


The file "aa...aa" could not be read.

Check the specified file path and the permission for reading the specified file.

The request format is invalid (analysis was successful).


The format of the request is invalid.


The version of the specified request is not supported.


An attempt to parse the request has failed.


The format of the request was invalid.


An attempt to create HSSOContext has failed.




Error Code

KAPM01052-I

KAPM01055-E

KAPM01056-E

KAPM01057-E

KAPM01059-E

KAPM01061-E

Error Message

aa...aa accessed.

aa...aa: User ID



Indicates the ID of the accessing user.


The system property specified in hcmds.home cannot be found.


HDVM.user not found at hcmds.home.


HDVM.password not found at hcmds.home.


The specified HSSO session is invalid, or does not exist. Session ID = aa...aa

aa...aa: Session ID


An invalid value is set in the configuration file. Parameter = aa...aa

aa...aa: Parameter name


An attempt at client authentication has failed.


The system property specified in hcmds.home

cannot be found.


HDVM.user

not found at hcmds.home

.


HDVM.password

not found at hcmds.home


.

The specified HSSO session is invalid, or does not exist.

Log in again.

An invalid value is set in the configuration file.

Check the value of the parameter specified for aa...aa in the configuration file.

Windows : Hitachi-Storage-Command-

Suite-Common-Component-installationfolder

\conf\user.conf

Solaris SPARC :

/opt/HiCommand/Base/conf/user.conf

Solaris10(x64) or Linux : Hitachi-

Storage-Command-Suite-Common-

Component-installation-

folder/Base/conf/user.conf



8-13

Error Code

KAPM01062-E

KAPM01063-I

KAPM01065-E

KAPM01066-E

KAPM01067-E

KAPM01068-E

KAPM01073-E

Error Message

A parameter is not set in the configuration file. Parameter = aa...aa




A parameter is not set in the configuration file.

Check the value of the parameter specified for aa...aa in the configuration file.



\conf\user.conf

Solaris SPARC :






The set virtual host name will now be displayed.

HSSO configuration: Virtual Host Name

= aa...aa

aa...aa: Virtual host name


Can't create DOM tree. - aa...aa



A CIM Repository exception occurred.


The status of the response from Device

Manager was FAILED.


aa...aa

aa...aa: Information that is included in the response of HiCommand Device

Manager


The format of the response from Device

Manager was invalid.


An attempt to create a DOM tree from the client request has failed.



When using HiCommand V3.x series, confirm that the InterBase or the

InterClient service is running. If the problem cannot be solved, collect maintenance information, and then contact the Support Center.

When using the HiCommand V4.x series or later, make sure that HiRDB is running. If the problem cannot be solved, collect maintenance information, and then contact the Support Center.

The status of the response from Device

Manager was FAILED. See the following message KAPM01068-E for the cause.


aa...aa: Information that is included in the response of Device Manager.


The format of the response from Device

Manager was invalid.




Error Code

KAPM01081-E

KAPM01084-I

KAPM01088-E

KAPM01089-E

KAPM01090-E

Error Message Description and Action

Authentication has failed. User ID =

aa...aa

aa...aa: User ID


The HSSO session has started. Session

ID = aa...aa



An attempt to load the class failed. Class

= aa...aa

aa...aa: Class name


An attempt to create the instance of the class for authentication failed. Class =

aa...aa



An attempt to create the instance of the class for authorization failed. Class =

aa...aa




Log in again using a valid user ID and password.

The HSSO session has started.

An attempt to load the class failed.

Confirm that the class specified for

aa...aa is the class specified in

HSSO.classpath

.



\conf\user.conf

Solaris SPARC :






An attempt to create the instance of the class for authentication failed.

Check the value of

HSSO.authentication.module

in the configuration file.



\conf\user.conf

Solaris SPARC :






An attempt to create the instance of the class for authorization failed.

Check the value of

HSSO.authorization.module




\conf\user.conf

Solaris SPARC :








8-15

Error Code

KAPM01091-E

KAPM01092-E

KAPM01093-I

KAPM01094-I

KAPM01095-E

KAPM01096-E

KAPM01097-E

KAPM01098-E

Error Message

An attempt to initialize the authentication class failed. Class =

aa...aa



An attempt to initialize the authorization class failed. Class = aa...aa



HSSO configuration: Authentication class = aa...aa



HSSO configuration: Authorization class

= aa...aa



The authenticated user does not have permission. User ID = aa...aa,

Application = bb...bb

aa...aa: User ID

bb...bb: Application


An attempt to authenticate the internal user has failed.


An exception occurred during internal authentication module processing.


An exception occurred during authentication module processing.



An attempt to initialize the authentication class failed.

Take action according to the proceeding message.

An attempt to initialize the authorization class failed.


The authentication class that HSSO uses will now be displayed.

The authorization class that HSSO uses will now be displayed.

The authenticated user does not have permission.

Log in again as a user having the permission.

An attempt to authenticate the internal user has failed.

Confirm that the user specified by the value of

HDVM.user

and

HDVM.password

the following configuration file is registered in Device Manager.

in



\conf\user.conf

Solaris or Linux :


An exception occurred during internal authentication module processing.


An exception occurred during authentication module processing.




Error Code

KAPM01099-E

KAPM01103-I

KAPM01104-I

KAPM01105-E

KAPM01106-E

KAPM01107-E

KAPM01108-E

KAPM01109-E

KAPM01114-E

Error Message

An exception occurred during authorization module processing.


HSSO configuration: Device Manager

Server URL = aa...aa

aa...aa: Device Manager server URL


HSSO configuration: Device Manager

Server Connection Timeout = aa...aa

aa...aa: Device Manager server connection timeout


The JP1 token is invalid.


An attempt to communicate with

JP1/Base has failed.


An error occurred due to a virtual host name. Function Code = aa...aa, Result

Code = bb...bb

aa...aa: Function code

bb...bb: Result code



An exception occurred during authorization module processing.


The URL of the Device Manager server that HSSO uses will now be displayed.

The timeout value for the connection with the Device Manager server that

HSSO uses will now be displayed.

The JP1 token is invalid.

Log in again.

An attempt to communicate with

JP1/Base has failed.

Check the status of JP1/Base.

An attempt to load the library associated with JP1/Base has failed.


An exception occurred during JP1 token authentication processing. Function

Code = aa...aa, Result Code = bb...bb

aa...aa: Function code

bb...bb: Result code


An attempt to acquire the link and launch information failed.


An error occurred due to a virtual host name.

Check the value of hbase.virtualhost

the configuration file.

in



\conf\user.conf

Solaris or Linux :


An attempt to load the associated with

JP1/Base library has failed.


An exception occurred during JP1 token authentication processing.






8-17

8-18


KAPM01115-E

KAPM01116-E

KAPM01119-E

KAPM01123-I

KAPM01124-I

KAPM01125-E

KAPM01152-E

Exception in DeviceManager.

DeviceManager returns FAILED. -

aa...aa

aa...aa: Error message acquired from

Device Manager


No user was returned from

DeviceManager.


No user information is set in the HSSO session.


HSSO configuration: HSSO Session

Timeout = aa...aa

aa...aa: HSSO session timeout


The login process has completed properly.


The login process has failed.


Can't get the application name from request. Request is invalid.


KAPM01154-W aa...aa is not registered.



KAPM01156-E

KAPM01167-I

KAPM01168-E

Exception in Repository. - aa...aa

aa...aa: Message


The database has stopped.




KAPM01205-E No instance of Service associated with

ServiceAccessPoint.



The response status of Device Manager is

"

FAILED

".


The GetUser response does not contain any user information.


No user information is set in the HSSO session.

Log in again.

The timeout value (in seconds) of the

HSSO session will now be displayed.

This audit log data indicates that login was successful.

This audit log data indicates that login failed.

The application name cannot be acquired from the request. The request is invalid.


aa...aa is not registered.

An error occurred when the Common

Repository was accessed.

See the message KAPM02xxx-E.

The database has stopped.



An attempt to acquire the service associated with ServiceAccessPoint has failed.




Error Code

KAPM01206-E

Error Message

No instance of SoftwareFeature associated with Service.


KAPM01208-E Exception in Repository. - aa...aa

aa...aa: Details about the repository access error


KAPM01209-W ServiceAccessPoint is not registered.


KAPM01220-E Communication with the external authentication server has failed.



An attempt to acquire the

SoftwareFeature associated with the

Service has failed.


An error occurred in the access to the repository.


ServiceAccessPoint is not registered.

Communication with the external authentication server has failed.


For LDAP:





For RADIUS:






8-19

Error Code Error Message Description and Action

KAPM01255-E

KAPM01302-E

KAPM01308-E

KAPM01309-E

KAPM01312-E

KAPM01314-E

1. Make sure that the realm name and

KDC specified in exauth.properties are correct.

2. Make sure that the network is connected correctly.

3. Make sure that Kerberos is compatible with the external authentication server.


The response status of Device Manager is

"

FAILED

".


Exception in DeviceManager.

DeviceManager returns FAILED. -

aa...aa

aa...aa: Error message acquired from

Device Manager


Can't get the host name or port number of DeviceManager from configuration.


An attempt to communicate with Device

Manager failed. URL = aa...aa

aa...aa: URL


The host name or port number of Device

Manager cannot be acquired from the configuration.

Confirm that the value of the properties

HDVM.host

and

HDVM.port

are set in init.conf

.

An attempt to communicate with Device

Manager failed.

Check the status of Device Manager, and check the values of

HDVM.protocol,

HDVM.host

and

HDVM.port




\conf\user.conf

Solaris or Linux :


Device Manager server XML API version

aa...aa is not supported.


The Device Manager Server XML API version aa...aa is not supported.

aa...aa: Version


DeviceManager Server version aa...aa is not supported.

aa...aa: Version of Device Manager


The connection to Device Manager timed out.


Device Manager server version aa...aa is not supported.


The connection to Device Manager timed out.

Confirm that Device Manager is running.



Error Code

KAPM01331-I

KAPM01336-E

KAPM01337-E

Error Message

Connecting to DeviceManager Server specified by aa...aa

aa...aa: URL of Device Manager


URL aa...aa is invalid to DeviceManager

Server.

aa...aa: URL of Device Manager


Authentication Failed in DeviceManager.


KAPM01338-E I/O Error regarding connection to

DeviceManager.


KAPM01353-E Can aa...aa.

aa...aa: User permissions



The connection to Device Manager is being established.

The format of the URL aa...aa for Device

Manager server is invalid.

Confirm that the values of the and

HDVM.host

HDVM.port

properties are valid in init.conf

.

An authentication error occurred in

Device Manager.

Confirm that the specified user was registered in Device Manager.

An I/O Error occurred in the communication with Device Manager.

Confirm that Device Manager is running.

User permissions could not be mapped.


CIMClient creation is starting.

KAPM01402-E

KAPM02001-E


Can't create CIMClient. - aa...aa



Can not be found database.


An attempt to create CIMClient has failed.


KAPM02001-W

Some of connection updated the same instance together. So didn't update the instance.


The database could not be found.

Check the value of

DATABASE.path

in the following file.



\conf\user.conf

Solaris or Linux :


Some of connection updated the same instance together. So didn't update the instance.

Confirm that the candidate for updating was updated. If it was not updated, try again.



8-21

Error Code

KAPM02002-E

KAPM02003-E

KAPM02004-E

KAPM02005-E

KAPM02006-E

KAPM02007-E

KAPM02008-E

KAPM02009-E

Error Message

Your user name and password are not defined.


An unknown host exception occurred while trying to open a socket connection to server.


No suitable driver.



The name or password of the user accessing the database is invalid.

Check the value of

DATABASE.user

or

DATABASE.password




\conf\user.conf

Solaris or Linux :


The host name of the database to be accessed is invalid.

Check the value of the following file.

DATABASE.hostname

in



\conf\user.conf

Solaris or Linux :


The driver name for accessing the database is invalid.

Check the value of

DATABASE.type


Windows : HiCommand-Suite-Common-

Component-installationfolder

\conf\user.conf

Solaris or Linux :


A socket exception occurred while trying to establish a socket connection to server.

Make sure that InterClient is running.

A socket exception occurred while trying to establish a socket connection to server.


InterServer is unable to locate the

InterBase application or service.


aa...aa



aa...aa



Failed to unlock a table when inserting a record or records.


InterServer is unable to locate the

InterBase application or service.

Make sure that InterBase is running.

An SQLException has occurred.


Another type of exception occurred.


The table-unlock process that set the connection during the insert has failed.




Error Code

KAPM02010-E

KAPM02011-E

KAPM02012-E

KAPM02013-E

KAPM02014-E

KAPM02015-E

KAPM02016-E

KAPM02017-E

KAPM02018-E

KAPM02019-E

KAPM02021-E

KAPM02023-E

Error Message

Update data doesn't exist.


Delete data doesn't exist.


Search data doesn't exist.


Exception happened when some CIM class was used.


An attempt to load the definition for a class has failed. Class name = aa...aa



A class definition could not be found.

Class name = aa...aa



A RepositoryException occurred.


The parameter is null.




The CIMElement already exists.



The CIMElement could not be found.


The CIMObjectPath is incorrect. A key is required.



The data could not be found.






An error occurred while reading or using the value specified in CIM.


An attempt to load the definition for a class has failed.


A class definition could not be found.

Reboot the single signon service.

A RepositoryException occurred.


The parameter is null.




The CIMElement already exists.


Duplicate data exists.


The CIMElement could not be found.


The CIMObjectPath is incorrect. A key is required.




8-23

8-24

Error Code

KAPM02025-E

KAPM02027-E

KAPM02029-E

Error Message

The CIMObjectPath contains an invalid property.


The key property could not be changed.


The initialize parameter is invalid.


KAPM02030-E

KAPM02031-E

KAPM02032-E

KAPM02033-E

KAPM02034-E

KAPM02035-E

KAPM02036-E

An unsupported data type was used.


The CIMClass is invalid. A KEY property is required.


The CIMClass could not be deleted, because it contains instances.


The CIMClass could not be deleted, because it contains subclasses.


A ClassNotFoundException occurred.


A CIMInConnectionPoolException occurred.


A connection to the database could not be established.


KAPM02038-W A DeadLockException occurred.

Description = aa...aa



KAPM02039-W A CIMInDeadLockException occurred.


KAPM02040-E The CIMInstance is invalid.



The CIMObjectPath contains an invalid property.


The key property could not be changed.


The initialize parameter in init.conf is invalid.


An unsupported data type was used.


The CIMClass is invalid. A KEY property is required.


The CIMClass could not be deleted, because it contains instances.


The CIMClass could not be deleted, because it contains subclasses.




A CIMInConnectionPoolException occurred.


A connection to the database could not be established.


A DeadLockException occurred.


A CIMInDeadLockException occurred.


The CIMInstance is invalid.




Error Code

KAPM02041-E

KAPM02042-E

KAPM02044-E

KAPM02045-E

KAPM02046-E

KAPM02047-E

KAPM02048-E

KAPM02049-E

KAPM02050-E

KAPM02051-E

KAPM02052-E

KAPM02053-E

KAPM02054-E

Error Message

The CIMObjectPath is invalid.


The name of property is invalid.


A DBNotFoundException occurred.


The CIMClass is invalid.


The CIMProperty is invalid. The KEY property must be set.


The type of class is invalid.


Failed to get membership groups.


Not authorized object. ObjectName =

aa...aa

aa...aa: Object name


Host name is invalid.


Cannot connect to InterClient.


Cannot connect to InterBase.


SQLException occurred. Description =

aa...aa

aa...aa: Description


Exception occurred. Description =

aa...aa




The CIMObjectPath is invalid.


The name of property is invalid.


A DBNotFoundException occurred.


The CIMClass is invalid.


The CIMProperty is invalid. The KEY property must be set.


The type of class is invalid.


Failed to get membership groups.


Not authorized object.


Host name is invalid.


Cannot connect to InterClient.


Cannot connect to InterBase.


SQLException occurred.


Exception occurred.




8-25

Error Code

KAPM02055-E

KAPM02056-E

KAPM02057-E

KAPM02058-E

KAPM02059-E

KAPM02060-E

KAPM02061-E

KAPM02062-I

KAPM02063-I

KAPM02069-E


CIMException occurred. Description =

aa...aa



A CIMClassNotFoundException occurred.


IOException occurred. Description =

aa...aa



InterruptedException occurred.

Description = aa...aa



The time limit for establishing a connection is over.


An attempt to establish a connection has failed.


aa...aa



The get method changed the state to the standby state.


The createConnection method changed the state to the standby state.


A time-over error occurred when connecting to the repository.


CIMException occurred.




IOException occurred.


InterruptedException occurred.


The time limit for establishing a connection is over.







The get method changed the state to the standby state.

The createConnection method changed the state to the standby state.

A time-over error occurred when connecting to the repository.

If you are trying to log in, log in again. If you have already logged in, retry the operation.




KAPM02070-E

KAPM02071-E

KAPM02072-E

KAPM02073-E

A CIMUnavailableDatabaseException occurred. Detailed message of exception

= aa...aa

aa...aa: Detailed message of exception


HiRDB is not running.


The password of a user connected to

HiRDB is invalid. (user name = aa...aa)

aa...aa: User name


The user name of a user connected to

HiRDB is invalid. (user name = aa...aa)



KAPM02074-W The table name registered into DBMS is changed. Before= aa...aa After =

bb...bb

aa...aa: Before

bb...bb: After


KAPM02075-E An attempt to set a connection to the factory has failed.


KAPM02076-I

Processing to initialize the connection pool was executed.

aa...aa: Initial value, bb...bb: Increment value, cc...cc: Maximum value, dd...dd:

Keep-alive period, ee...ee: Timeout period, ff...ff: Number of retries,

gg...gg: Retry interval

aa...aa: Initial value

bb...bb: Increment value

cc...cc: Maximum value

dd...dd: Keep-alive period

ee...ee: Timeout period

ff...ff: Number of retries

gg...gg: Retry interval



HiRDB is not running.

Please start HiRDB.

A CIMUnavailableDatabaseException occurred.


The password of a user connected to

HiRDB is invalid.

Check the value of

HiRDB.password

in the user.conf

file. If that is not the problem, contact the Support Center.

The user name of a user connected to

HiRDB is invalid.

Check the value of

HiRDB.user

in the user.conf

file. If that is not the problem, contact the Support Center.

The table name to be registered in the

DBMS will be changed.

An attempt to set a connection to the factory has failed.


Processing to initialize the connection pool was executed.



8-27

Error Code

KAPM02077-E

KAPM02078-E

KAPM02079-E

KAPM02080-E

KAPM02201-I

KAPM02202-I

KAPM02203-I

KAPM02204-I

KAPM02210-E

KAPM02211-E

Error Message

An attempt to release the connection of the connection pool has failed.


A RepositoryException occurred. (details

= aa...aa)

aa...aa: Details


An attempt to release the JDBC connection has failed.


A CIMHeldRepositoryException has occurred. Exception message = aa...aa

aa...aa: detailed message of exception


The method was invoked.


The following arguments were specified:

aa...aa

aa...aa: Arguments


External module processing has started.

(module = aa...aa)

aa...aa: Module


External module processing has terminated. (module = aa...aa)

aa...aa: Module


The specified argument is null.


The password is not set.



This message is displayed when an attempt to release the connection of the connection pool fails.


This message is displayed when a

RepositoryException occurs.


This message is displayed when an attempt to release the JDBC connection fails.


A CIMHeldRepositoryException has occurred.


The method was invoked.

The following arguments were specified:

aa...aa

External module processing has started.

External module processing has terminated.

The specified argument is null.

The password is not set.





Error Code

KAPM02213-E

KAPM02214-E

KAPM02215-E

KAPM02216-E

KAPM02217-E

KAPM02218-E

KAPM02219-E

KAPM02220-E

KAPM02221-E

Error Message

An attempt to read the password file has failed.


An attempt to write to the password file has failed.




Confirm that the following file has read permissions. If it does have read permissions, collect maintenance information, and contact the Support

Center.

Windows: Hitachi-Storage-Command-


\conf\.hbaspass

Solaris or Linux:

/opt/HiCommand/Base/conf/.hbaspass

An attempt to write to the password file has failed.

Confirm that the following file has write permissions. If it does have write permissions, collect maintenance information, and contact the Support

Center.



\conf\.hbaspass

Solaris or Linux:

/opt/HiCommand/Base/conf/.hbaspass

The authenticated user does not have permission to execute the method.

The authenticated user does not have permission to execute the method.


The specified user was not found.


The specified group was not found.


The specified user already exists.


The specified group already exists.


The specified user is already registered in the group.

Output destinations: Destinations for output level 10. hadmin cannot be registered in the group.



The specified group was not found.


The specified group already exists.

The specified user is already registered in the group. hadmin cannot be registered in the group.



8-29

Error Code

KAPM02222-E

KAPM02223-E

KAPM02224-E

KAPM02225-E

KAPM02226-E

KAPM02227-E

KAPM02228-E

KAPM02229-E

KAPM02230-E

KAPM02231-E

KAPM02232-E

KAPM02233-E

KAPM02234-I

Error Message

An error occurred during user database access.


The specified mode is unsupported.




The specified user cannot be deleted.


The specified group cannot be deleted.


The common repository is stopping.


The user ID is not set.






The application type is not set.


The resource group ID is not set.


The specified application is not registered.


The permissions for aa...aa will now be changed. (User ID = aa...aa)

aa...aa: User ID



An error occurred during user database access.

Confirm that DBMS, HBase Storage Mgmt

Web Service and HBase Storage Mgmt

Common Service have started. If they have started, collect maintenance information, and contact the Support

Center.

The specified mode is unsupported.




The specified user cannot be deleted.

The specified group cannot be deleted.

The common repository has stopped.


The user ID is not set.






The application type is not set.


The resource group ID is not set.


The specified application is not registered.


The permissions for aa...aa will now be changed.



Error Code

KAPM02235-I

KAPM02236-I

KAPM02237-I

KAPM02238-I

KAPM02239-I

KAPM02240-I

KAPM02241-I

KAPM02242-I

KAPM02243-I

Error Message

The permissions for aa...aa were changed. (User ID = aa...aa)

aa...aa: User ID


A user account will now be created.

(User ID = aa...aa)

aa...aa: User ID


The user account was created successfully. (User ID = aa...aa)

aa...aa: User ID


The user-account properties will now be changed. (aa...aa)

aa...aa: Properties list before the change


The user-account properties were changed. (aa...aa)

aa...aa: Properties list after the change


The resource-group properties will now be changed. (aa...aa)

aa...aa: Properties list before the change


The resource-group properties were changed. (aa...aa)

aa...aa: Properties list after the change


The allocation status of the resource group will now be changed. (aa...aa)

aa...aa: Allocation status before the change


The allocation status of the resource group was changed. (aa...aa)

aa...aa: Allocation status after the change



The permissions for aa...aa were changed.

A user account will now be created.

The user account was created successfully.

The user account properties will now be changed.

The user account properties were changed.

The resource group properties will now be changed.

The resource group properties were changed.

The allocation status of the resource group will now be changed.

The allocation status of the resource group was changed.



8-31

Error Code

KAPM02244-I

KAPM02245-I

KAPM02246-I

KAPM02247-I

KAPM02248-I

KAPM02249-I

KAPM02250-E

KAPM02251-E

Error Message

The password will now be changed.


aa...aa: User ID


The password was changed. (User ID =

aa...aa)

aa...aa: User ID


The user account will now be deleted.


aa...aa: User ID


The user account was deleted. (User ID

= aa...aa)

aa...aa: User ID


The resource group will now be deleted.

(resource group ID = aa...aa, resource group name = bb...bb)

aa...aa: Resource-group ID

bb...bb: Resource-group name


The resource group was deleted.

(resource group ID = aa...aa, resource group name = bb...bb)

aa...aa: Resource-group ID

bb...bb: Resource-group name


A resource group with the same name has already been registered. (resource group name = aa...aa)

aa...aa: Resource-group name


A user account with the same user ID has already been registered. (User ID =

aa...aa)

aa...aa: User ID




The password was changed.

The user account will now be deleted.

The user account was deleted.

The resource group will now be deleted.

The resource group was deleted.

A resource group with the same name has already been registered.

A user account with the same user ID has already been registered.



Error Code

KAPM02252-E

KAPM02254-I

KAPM02255-E

KAPM02256-E

KAPM02257-E

KAPM02258-I

KAPM02259-I

KAPM02260-E

Error Message

A resource group with the same ID has already been registered. (group ID =

aa...aa)

aa...aa: Group ID


Request information: (API version =

aa...aa, Command name = bb...bb, User

ID or session ID = cc...cc)

aa...aa: API version

bb...bb: Command name

cc...cc: User ID or session ID


The specified version is not supported.

(version = aa...aa)



The specified command is not supported. (command = aa...aa)

aa...aa: Command name


Authentication has failed. (user ID =

aa...aa)

aa...aa: User ID


Response information: (API version =

aa...aa, Command name = bb...bb,

Response status = cc...cc)


bb...bb: Command name

cc...cc: Response status


Response information when an error occurs: (Error code = aa...aa,

Description = bb...bb)

aa...aa: Error code

bb...bb: Description


An attempt to communicate with a server has failed. (URL = aa...aa)

aa...aa: URL of the server



A resource group with the same ID has already been registered.

Request information.

The specified version is not supported.


The specified command is not supported.



Make sure the combination of user ID and password is correct.

Response information.

Response information when an error occurs.

An attempt to communicate with a server has failed.

Make sure the HBase Storage Mgmt

Common Service or the HBase Storage

Mgmt Web Service of the server specified in the URL has started.



8-33

Error Code

KAPM02261-E

KAPM02262-E

KAPM02263-E

KAPM02269-E

KAPM02270-E

KAPM02271-E

KAPM02272-E

KAPM02273-I

KAPM02274-I

KAPM02275-I

Error Message

An attempt to parse the response has failed.


The request parameter is invalid.


This user does not have execution permissions. (ID = aa...aa)




Output destinations: syslog/Eventlog/Destinations for output level 10, and windows.

The same user ID already exists.


An attempt to communicate with a database has failed.


An error occurred within the server.


The user will now be added. (ID =

aa...aa, user ID = bb...bb)


bb...bb: User ID


The user was added successfully. (ID =



bb...bb: User ID


The password will now be changed. (ID

= aa...aa, user ID = bb...bb)


bb...bb: User ID



An attempt to parse the response has failed.


The request parameter is invalid.


This user does not have execution permissions.



Another user might have deleted the specified user.

Refresh the display and make sure the selected user is registered.

The same user ID already exists.

Specify another user ID.

An attempt to communicate with a database has failed.

Make sure that HiRDB has started.



The user will now be added.

The user was added successfully.




Error Code

KAPM02276-I

KAPM02277-I

KAPM02278-I

KAPM02279-I

KAPM02280-I

KAPM02281-I

KAPM02282-I

Error Message

The password was changed successfully.

(ID = aa...aa, user ID = bb...bb)


bb...bb: User ID


The user profile will now be changed.

(ID = aa...aa, user ID = bb...bb)


bb...bb: User ID


The user profile was changed successfully. (ID = aa...aa, user ID =

bb...bb)


bb...bb: User ID


The permissions will now be changed.

(ID = aa...aa, user ID = bb...bb, permissions = cc...cc)


bb...bb: User ID

cc...cc: Permissions after the change


The permissions were changed successfully. (ID = aa...aa, user ID =

bb...bb, permissions = cc...cc)


bb...bb: User ID

cc...cc: Permissions after the change

Output destinations: syslog/Eventlog/Destinations for output level 10.

The user will now be deleted. (ID =



bb...bb: User ID


The user was deleted successfully. (ID =



bb...bb: User ID




The user profile will now be changed.

The user profile was changed successfully.

The permissions will now be changed.

The permissions were changed successfully.

The user will now be deleted.

The user was deleted successfully.



8-35

Error Code

KAPM02283-E

KAPM02284-I

KAPM02285-I

KAPM02286-E

KAPM02287-I

KAPM02288-I

KAPM02289-E

KAPM02290-I


The old password is incorrect. (ID =



bb...bb: User ID


The user will now be locked. (ID =

aa...aa, user ID = bb...bb)


bb...bb: User ID


The user was locked successfully. (ID =



bb...bb: User ID


An attempt to lock the user has failed.

aa...aa

aa...aa: Detailed information


The user will now be unlocked. (ID =



bb...bb: User ID


The user was unlocked successfully. (ID

= aa...aa, user ID = bb...bb)


bb...bb: User ID


An attempt to unlock the user has failed.

aa...aa



Authentication was successful. (user ID

= aa...aa)

aa...aa: User ID


The old password is incorrect.

The user will now be locked.

The user was locked successfully.

An attempt to lock the user has failed.

See the message that follows.

The user will now be unlocked.

The user was unlocked successfully.

An attempt to unlock the user has failed.

See the Message of the next message.

Authentication was successful.







KAPM02292-W Authentication has failed for aa...aa times in a row, so the user (bb...bb) was locked.

aa...aa: Failure times

bb...bb: User ID


KAPM02294-E

KAPM02295-E



A distinguished name has not been set.


KAPM02296-E

KAPM02297-E

KAPM02298-E

A domain name has not been set.


The specified distinguished name already exists. (distinguished name =

aa...aa)

aa...aa: Distinguished name


The specified distinguished name could not be found. (distinguished name =

aa...aa)



KAPM02301-E

KAPM02302-E

KAPM02303-E hcmds.home is not set in the Java system properties.


An error occurred during loading of a library.


An attempt to acquire user information about a HiRDB-connected user has failed. error code = aa...aa



Authentication has failed for aa...aa times in a row, so the user (bb...bb) was locked.



A distinguished name has not been set.


A domain name has not been set.


The specified distinguished name already exists.

Specify a different distinguished name.

The specified distinguished name could not be found.

Another user might have already deleted the specified authorization group.

Refresh the screen, and then check whether the specified authorization group is registered. hcmds.home

is not set in the Java system properties.


An error occurred during loading of a library.


An attempt to acquire user information about a HiRDB-connected user has failed.




8-37

Error Code

KAPM02304-E

KAPM02305-E

KAPM02306-E

KAPM02307-E

KAPM02401-E

Error Message

An attempt to set a system environment variable has failed. error code = aa...aa



Attempts to set the system environment variables PDDIR and PATH have failed. error code = aa...aa



An attempt to clear an HiRDB system environment variable has failed. error code = aa...aa



The application type is required, but is not set.


An attempt to read the file failed. (path

= aa...aa)

aa...aa: Path



An attempt to set a system environment variable has failed.


Attempts to set the system environment variables PDDIR and PATH have failed.


An attempt to clear an HiRDB system environment variable has failed.


The application type is required, but is not set.


An attempt to read the file failed.

Confirm that a file exists in the specified location.



Error Code

KAPM02409-E

Error Message

A communication error occurred in an external authentication server. (error code = aa...aa)

aa...aa: error code


KAPM02410-W Authentication with an external authentication server has failed. (user

ID = aa...aa, host = bb...bb, port =

cc...cc, protocol = dd...dd)

aa...aa: User ID

bb...bb: Host

cc...cc: Port

dd...dd: Protocol



A communication error occurred in an external authentication server.


For LDAP:

1. By using the host, port, and protocol set in "exauth.properties", check whether the authentication server can be accessed, the settings of the external authentication server, and the status of the network.

2. By using the hcmdsldapuser command, check that the information for the server names specified in the "auth.server.name" attribute in "exauth.properties" is registered.



For RADIUS:

1. By using the host, port, and protocol set in "exauth.properties", check whether the authentication server can be accessed, the settings of the external authentication server, and the status of the network.

2. By using the hcmdsradiussecret command, check that the information for the server names specified in the "auth.server.name" attribute in "exauth.properties" is registered.


The login user failed to be authenticated on the external authentication server.




8-39


KAPM02411-W

Authentication with an external authentication server has failed. The specified user was not found in the external authentication server. (user ID

= aa...aa, host = bb...bb)

aa...aa: User ID

bb...bb: Host


KAPM02412-E

A naming exception occurred. (host =

aa...aa, port = bb...bb, protocol =

cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol



The login user was not found in the external authentication server.


A naming exception occurred.


For LDAP:





For RADIUS:






Error Code

KAPM02413-E

KAPM02414-I

Error Message

The negotiation for a TLS session has failed. (host = aa...aa, port = bb...bb, protocol = cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol


Authentication with an external authentication server was successful.

(user ID = aa...aa, host = bb...bb, port

= cc...cc, protocol = dd...dd)

aa...aa: User ID

bb...bb: Host

cc...cc: Port

dd...dd: Protocol



Negotiation for a TLS session has failed.


For LDAP:





For RADIUS:




The login user was successfully authenticated on the external authentication server.



8-41

Error Code

KAPM02416-E

Error Message






For LDAP:





For RADIUS:






Error Code

KAPM02417-E

Error Message

Communication with an external authentication server has failed. (host =

aa...aa, port = bb...bb, protocol =

cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol




LDAP server has failed.


For LDAP:





For RADIUS:






8-43


KAPM02418-E

The LDAP service cannot be used. (host

= aa...aa, port = bb...bb, protocol =

cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol


KAPM02419-W Only local operation is available because the attempt to read the configuration file for the external authentication server has failed.


KAPM02422-W A parameter in the exauth.properties file contains an invalid value (aa...aa =

bb...bb). The default value (cc...cc) will be used.


bb...bb: Parameter value

cc...cc: Default value


The LDAP service cannot be used.


For LDAP:





For RADIUS:




Only local operation is available because the attempt to read the configuration file for the external authentication server has failed.

Review the settings in the configuration file for the external authentication server.

The exauth.properties file (configuration file for the external authentication server) contains an invalid parameter file.




Error Code

KAPM02423-E

KAPM02424-E

KAPM02425-E

KAPM02426-E

KAPM02427-E

KAPM02429-I

KAPM02430-E

Error Message

Authentication of the search user has failed. (host = aa...aa)

aa...aa: Host



Authentication of the search user at the

LDAP server has failed.

Use the hcmdsldapuser command to register the access user in the external authentication server. If the user has already been registered, check the settings for that user.

An error occurred in the LDAP server. An error occurred in the external authentication server.


A parameter was not specified.

(parameter = aa...aa)



Authentication stopped because a setting in the configuration file for the external authentication server was invalid.


An invalid character was specified in the

URL for a host name or a port number.

(host = aa...aa, port = bb...bb)

aa...aa: Host

bb...bb: Port


A RADIUS packet has been received.

(packet information = aa...aa)

aa...aa: Packet information


Verification of a RADIUS packet has failed. (host = aa...aa, port = bb...bb, protocol = cc...cc, cause = dd...dd)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol

dd...dd: Cause of failure


A parameter is not specified in the configuration file for the external authentication server.


Authentication stopped because a setting in the configuration file for the external authentication server was invalid.


A URL for a host name or a port number, specified in the configuration file for the external authentication server, contains invalid characters.


A RADIUS packet has been received.

Verification of a RADIUS packet has failed.



8-45

Error Code

KAPM02431-E

Error Message

The connection to an external authentication server has timed out.

(host = aa...aa, port = bb...bb, protocol

= cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol



The connection to an external authentication server has timed out.


For LDAP:





For RADIUS:






Error Code

KAPM02432-E

Error Message

SSL-encrypted communication with the external authentication server has failed. (host = aa...aa, port = bb...bb, protocol = cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol


KAPM02434-W The lock processing was interrupted.


KAPM02435-W If the selected user accounts are locked, no more users will have the User

Management permission.


KAPM02436-E Determination of whether lock processing was performed has failed.



SSL-encrypted communication with the external authentication server has failed.


For LDAP:





For RADIUS:




The lock processing was interrupted.

Make a selection such that at least one user has the User Management permission.

If the selected user accounts are locked, no more users will have the User


Make a selection such that at least one user has the User Management permission.

Determination of whether lock processing was performed has failed.

Acquire the maintenance information, and then contact the Support Center.



8-47

8-48


KAPM02450-I

KAPM02451-W Authentication by an external authentication server has failed. (server type = aa...aa, host = bb...bb)

aa...aa: Server type

bb...bb: Host


KAPM02452-I

KAPM02453-E

A user's authentication method has been successfully changed. (authentication method = aa...aa, user ID = bb...bb) aa...aa: Authentication method bb...bb: User ID


An attempt to change a user's authentication method has failed.

(authentication method = aa...aa, user

ID = bb...bb)

aa...aa: Authentication method

bb...bb: User ID


KAPM02454-E

KAPM02455-E

Acquisition of SRV records failed.

(domain name = aa...aa, protocol =

bb...bb)

aa...aa: Domain name

bb...bb: Protocol


A domain has been removed from the domain list because the acquisition of

SRV records failed. (domain name =

aa...aa)



KAPM02456-E

KAPM02457-E

Authentication by an external authentication server was successful.

(server type = aa...aa, host = bb...bb)

aa...aa: Server type

bb...bb: Host


A function cannot be used because group mapping is disabled. (function name = aa...aa)

aa...aa: Function name


Acquisition of the password file failed.


This audit log data indicates that login was successful.

This audit log data indicates that login has failed.

This audit log data indicates that a user's authentication method has been successfully changed.

This audit log data indicates that an attempt to change a user's authentication method has failed.

Acquisition of SRV records failed.

Make sure that SRV records have been defined on the DNS server.

A domain has been removed from the domain list because the acquisition of

SRV records failed.

Make sure that SRV records have been defined on the DNS server.

A function cannot be used because group mapping is disabled.

Revise the settings in the configuration file for the external authentication server

( exauth.properties

).

Acquisition of the password file failed.




Error Code

KAPM02458-E

KAPM02459-E

KAPM02502-E

KAPM02503-E

KAPM02504-E

KAPM02505-E

Error Message

A setting in the configuration file for the external authentication server

( exauth.properties

) is invalid.



A setting in the configuration file for the external authentication server

( exauth.properties

) is invalid.


( exauth.properties

).

The domain cannot be linked to.

Use a domain that can be linked to.

The domain cannot be linked to.

(domain name = aa...aa)



Please enter a password that satisfies the following conditions:

A minimum of aa...aa upper-case characters.

A minimum of bb...bb lower-case characters.

A minimum of cc...cc numerals.

A minimum of dd...dd symbols.

Different from the user ID.

aa...aa: the minimum number of characters

bb...bb: the minimum number of characters

cc...cc: the minimum number of characters

dd...dd: the minimum number of characters





A minimum of aa...aa lower-case characters.



A minimum of aa...aa numerals.



Please enter a password that satisfies the following conditions:


A minimum of bb...bb lower-case characters.

A minimum of cc...cc numerals.

A minimum of dd...dd symbols.


Enter an appropriate value according to the error message.



A minimum of aa...aa lower-case characters.


A minimum of aa...aa numerals.




8-49

Error Code

KAPM02506-E

KAPM02507-E

KAPM02508-E

KAPM02509-E

KAPM02510-I

KAPM02511-E

KAPM02512-E

Error Message

A minimum of aa...aa symbols.





Enter a value that is exactly aa...aa characters long.

aa...aa: the maximum number of characters


The following characters can be used for the value:

A-Z a-z 0-9 # + - . @ _


Authentication by using a KDC was successful. (Kerberos principal =

aa...aa, KDC = bb...bb)

aa...aa: Kerberos principal name

bb...bb: KDC


Communication with KDC failed. (KDC =

aa...aa)

aa...aa: KDC


Resolution of the KDC host name failed.

(KDC = aa...aa)

aa...aa: KDC


KAPM02513-W Authentication by using a KDC failed.

(Kerberos principal = aa...aa, KDC =

bb...bb)

aa...aa: Kerberos principal name

bb...bb: KDC



A minimum of aa...aa symbols.




Enter a value that is exactly aa...aa characters long.


The following characters can be used for the value:

A-Z a-z 0-9 # + - . @ _


Authentication by using a KDC was successful.

Communication with KDC failed.

Make sure the specified KDC is correct.

Resolution of the KDC host name failed.




Make sure the specified KDC is correct.



Make sure the specified host name in the KDC is registered in the DNS server.

Authentication by using a KDC failed.




KAPM02514-I

The krb5.conf file, used for internal processing, was successfully deleted.

(file name = aa...aa)



KAPM02515-W Deletion of the krb5.conf file, used for internal processing, failed. (file name =

aa...aa)



KAPM02516-I The krb5.conf file, used for internal processing, was successfully created.




KAPM02517-E

KAPM02518-I

KAPM02519-E

Creation of the krb5.conf file, used for internal processing, failed. (file name =

aa...aa)



A request to acquire SRV records was sent. (record key = aa...aa)

aa...aa: SRV record key


Communication with the DNS server failed.



The krb5.conf file, used for internal processing, was successfully deleted.

Deletion of the krb5.conf file, used for internal processing, was successful.

The krb5.conf file, used for internal processing, was successfully created.

Creation of the krb5.conf file, used for internal processing, failed.

Make sure you have the necessary permissions to create the file on the specified path.

A request to acquire SRV records was sent.

KAPM02520-E The Kerberos authentication settings are invalid.


KAPM02521-E The Kerberos realm or KDC definition is invalid. (realm name = aa...aa)

aa...aa: Realm name


KAPM02522-W The SRV records are undefined. (record key = aa...aa)



Communication with the DNS server failed.

Make sure the DNS server settings in the

OS are correct.

Make sure the status of the network connected with the DNS server is normal.

The Kerberos authentication settings are invalid.

Revise the Kerberos authentication settings in the exauth.properties

file or the search user definition.

The Kerberos realm or KDC definition is invalid.

Check and, if necessary, revise the exauth.properties

file realm or the KDC definition.

The SRV records are undefined.



8-51

8-52

Error Code

KAPM02523-I

KAPM02524-E

KAPM02525-E

KAPM02526-I

KAPM02527-I

KAPM02528-I

KAPM02529-I

KAPM02551-E

Error Message

Acquisition of the SRV records was successful. (SRV record = aa...aa)

aa...aa: SRV record


Acquisition of the SRV records failed.

(record key = aa...aa)



An error occurred on the DNS server.


Processing to identify the user account will now start. (user ID = aa...aa, server type = bb...bb)

aa...aa: User ID

bb...bb: Server type


The user account was found. (user ID =

aa...aa, internal = bb...bb)

aa...aa: User ID

bb...bb: Boolean value that shows whether an external authentication server is used


The user account was not found. (user

ID = aa...aa)

aa...aa: User ID


The user account was identified. (user

ID = aa...aa, external = bb...bb,

Kerberos user = cc...cc, Kerberos realm

= dd...dd)

aa...aa: User ID

bb...bb: Boolean value that shows whether an external authentication server is used

cc...cc: Kerberos user name

dd...dd: Kerberos realm name


The following characters can be used for the value: aa...aa

aa...aa: Value



Acquisition of the SRV records was successful.

Acquisition of the SRV records failed.

Make sure that the SRV records are defined on the DNS server.

An error occurred on the DNS server.

Check the operation status of the DNS server.

Processing to identify the user account will now start.

The user account was found.

The user account was not found.

The user account was identified.

The following characters can be used for the value.




Error Code

KAPM02603-E

KAPM02604-E

KAPM02605-E

KAPM02606-E

KAPM02607-E

KAPM02615-E

KAPM02616-E

KAPM02617-E

KAPM02618-E

KAPM02620-E

KAPM02625-E

Error Message

The resource group already exists.

(resource group name = aa...aa)

aa...aa: Resource group name


An HcmdsInvalidOperationException occurred.


An HcmdsAuthorizationException occurred.


An HcmdsUserManagementException occurred.


Make sure that the users can be added.


An HSSOException occurred.



The resource group aa...aa already exists.

Check the resource group name, and then change it to a name that differs from the others.

Settings for adding a user are invalid.

Make sure that the settings for adding users are valid.

The logged in user does not have the required permissions to add users.

Add users by using an account that has the required permissions.

A problem occurred while adding a user.


Make sure that the users can be added.

An IOException occurred.


A CIMException occurred.





Make sure that the repository is running.

If you cannot, acquire the maintenance information, and then contact the

Support Center.


Make sure that the file input and output are correct. If you cannot, acquire the maintenance information, and then contact the Support Center.


Make sure that the access method for the repository is correct. If you cannot, acquire the maintenance information, and then contact the Support Center.


Make sure that the connection to the repository is correct. If you cannot, acquire the maintenance information, and then contact the Support Center.

The resource group was not found. The resource group was not found.


The specified software definition aa...aa was not found.



The specified software definition aa...aa was not found.



8-53

Error Code

KAPM02630-I

KAPM02631-I

KAPM02632-I

KAPM02633-I

KAPM02634-I

KAPM02635-E


A resource group has been created.

(login ID = aa...aa, resource group name = bb...bb, module name = cc...cc)

aa...aa: Login ID

bb...bb: Resource group name

cc...cc: Module name

Output destinations: Audit Log

A resource group has been deleted.

(login ID = aa...aa, resource group ID =

bb...bb, module name = cc...cc)

aa...aa: Login ID

bb...bb: Resource group ID



A resource has been added. (login ID =

aa...aa, resource group ID = bb...bb, module name = cc...cc)

aa...aa: Login ID




A resource has been removed. (login ID

= aa...aa, resource group ID = bb...bb, module name = cc...cc)

aa...aa: Login ID




A resource group property has been edited. (login ID = aa...aa, resource group ID = bb...bb, module name =

cc...cc)

aa...aa: Login ID




Creation of a resource group has failed.

(login ID = aa...aa, resource group name = bb...bb, module name = cc...cc)

aa...aa: Login ID

bb...bb: Resource group name



A resource group has been created.

(login ID = aa...aa, resource group name

= bb...bb, module name = cc...cc)

A resource group has been deleted.



A resource has been added. (login ID =

aa...aa, resource group ID = bb...bb, module name = cc...cc)

A resource has been removed. (login ID

= aa...aa, resource group ID = bb...bb, module name = cc...cc)

A resource group property has been edited. (login ID = aa...aa, resource group ID = bb...bb, module name =

cc...cc)

Creation of a resource group has failed.

(login ID = aa...aa, resource group ID =




Error Code

KAPM02636-E

KAPM02637-E

KAPM02638-E

KAPM02639-E

KAPM02650-I

KAPM02651-I

KAPM02652-I

Error Message

Deletion of a resource group has failed.



aa...aa: Login ID




Addition of a resource has failed. (login

ID = aa...aa, resource group ID =


aa...aa: Login ID




Removal of a resource has failed. (login



aa...aa: Login ID




An attempt to edit a resource group property has failed. (login ID = aa...aa, resource group ID = bb...bb, module name = cc...cc)

aa...aa: Login ID




A parameter has been sent. (HSSO token = aa...aa, application name =

bb...bb)

aa...aa: HSSO token

bb...bb: Application name


The software definition aa...aa does not exist.



aa...aa is not associated with a resource bundle.




Deletion of a resource group has failed.



Addition of a resource has failed. (login

ID =aa...aa, resource group ID =


Removal of a resource has failed. (login



An attempt to edit a resource group property has failed. (login ID = aa...aa, resource group ID = bb...bb, module name = cc...cc)

A parameter has been sent. (HSSO token

= aa...aa, application name = bb...bb)

The specified software definition aa...aa does not exist in the repository.

aa...aa is not associated with a resource bundle.



8-55


KAPM02654-E

KAPM02656-I

KAPM02659-I

A ResourceTabHandleException occurred.


A parameter has been sent. (HSSO token = aa...aa, application name =

bb...bb, resource group ID = cc...cc, resource group name = dd...dd)

aa...aa: HSSO token

bb...bb: Application name

cc...cc: Resource group ID

dd...dd: Resource group name


No users that can be added exist.


KAPM02660-I

KAPM02661-I

A user has been added successfully.

(resource group name = aa...aa, user name = bb...bb)


bb...bb: User name


A user has been removed successfully.



bb...bb: User name


KAPM02704-W An invalid RUAccessPoint object was created. Addition to the launch list is not performed. Name=aa...aa, URL=bb...bb,

TokenVersion=cc...cc, IconUrl=dd...dd,

IconMsg=ee...ee

aa...aa: Name

bb...bb: URL

cc...cc: Token version

dd...dd: Icon URL

ee...ee: Icon message


KAPM02705-E CIMException occurred. The processing that acquires RUAccessPoint will now be interrupted.


A ResourceTabHandleException occurred.

Check and, if necessary, revise the registered software definitions and resource bundles.

A parameter has been sent. (HSSO token

= aa...aa, application name = bb...bb, resource group ID = cc...cc, resource group name = dd...dd)

No users that can be added exist.

A user has been added successfully.


A user has been removed successfully.


An invalid RUAccessPoint object was created. Addition to the launch list is not performed.

CIMException occurred. The processing that acquires RUAccessPoint will now be interrupted.




Error Code

KAPM02706-E

KAPM02802-E

KAPM02803-E

KAPM02804-E

KAPM02806-E

KAPM02809-E

KAPM02810-E

KAPM02811-E

Error Message

The URL format is failed. URL=aa...aa

aa...aa: URL



The URL format is failed.


aa...aa: Execution SQL statement


A HcmdsExecException occurred.

Message=aa...aa, Reason=bb...bb

aa...aa: Message

bb...bb: Reason


Option is invalid.


A Exception occurred. Message=aa...aa

aa...aa: Message


An SQL statement was executed.


A HcmdsExecException occurred.


Option is invalid.

Check the options.

A Exception occurred.


A stack trace will be output.


aa...aa: Stack trace


A FileNotFoundException occurred.



A SQLException occurred.

Message=aa...aa

aa...aa: Message


An EXECUPDATE statement failed.

Execution SQL statement = aa...aa





A FileNotFoundException occurred.


A IOException occurred.










8-57

8-58

Error Code

KAPM02812-E

KAPM02813-E

KAPM02814-E

KAPM02815-E

Error Message

A SQL statement failed.

Message=aa...aa, Reason=bb...bb

aa...aa: Message

bb...bb: Reason


An EXECQUERY statement failed.






File is not found. file-name = aa...aa



aa...aa: Record number


KAPM02818-I

KAPM02891-E

aa...aa: Number of columns


aa...aa: bb...bb

aa...aa: Column name

bb...bb: Value


DB is not found.



A SQL statement failed.


An EXECQUERY statement failed.




File is not found.


Displays the record number.

Displays the number of columns.

Displays the column name and value.

KAPM02892-E User name or password is invalid.


Database is not found.

Check the value of configuration file.

DATABASE.path

in the



\conf\user.conf

Solaris or Linux :


User name or password is invalid.

Check the value of

DATABASE.user

and

DATABASE.password




\conf\user.conf

Solaris or Linux :




Error Code

KAPM02893-E

KAPM02894-E

KAPM02895-E

KAPM02896-E

KAPM02902-E

Error Message

The host name is invalid.


No suitable driver exists.


A connection to InterClient could not be established.


A connection to InterBase could not be established.



aa...aa: Trace message






Check the value of

DATABASE.hostname




\conf\user.conf

Solaris or Linux :



Check the value of

DATABASE.type


Windows : HiCommand-Suite-Common-


\conf\user.conf

Solaris or Linux :



Confirm that the InterClient service is running.


Confirm that the InterBase service is running.

Processing continuation is impossible.


A trace message will be output.



Read legacy record.



Order of hcmdsID change from x to 0.







Change legacy record.

Update CIMClient From 01-00 to 01-

01.

Already update.















Update DB Version.

Create TNB_Classes.

Create TNB_ClassAttribute.

Drop TNB_SERVICEACCESSBYSAP.

Drop

TNB_SOFTWAREFEATURESERVICEIMP

L.

Drop CIMClasses.

Succeed in update DataBase.





8-59

8-60

Error Code

KAPM02903-E

KAPM02904-E

KAPM02905-E

KAPM02907-E

KAPM02910-E

KAPM02911-E

KAPM02912-E

KAPM02913-E

KAPM02914-E

Error Message

A HcmdsUpdateException occurred.

Message = aa...aa, Reason = bb...bb

aa...aa: Message

bb...bb: Reason


An option is invalid.


An exception occurred. Message =

aa...aa

aa...aa: Message



A HcmdsUpdateException occurred.




An exception occurred.


aa...aa: Stack trace


A SQLException occurred. Message =

aa...aa

aa...aa: Message


A SELECT statement failed. Table name

= aa...aa

aa...aa: Table name


An ALTER statement failed. Table name

= aa...aa



A DROP statement failed. Table name =

aa...aa



An UPDATE statement failed. Table name = aa...aa







A stack trace is output.




A SELECT statement failed.


An ALTER statement failed.


A DROP statement failed.


An UPDATE statement failed.






Error Code

KAPM02980-I

KAPM02981-I

KAPM02982-I

KAPM02991-E

KAPM02992-E

KAPM02993-E

KAPM02994-E

KAPM02995-E

Error Message

Update CIMClient from 01-00 to 01-01.


The database has already been updated.


The database was successfully updated.


DB is not found.











Update CIMClient from 01-00 to 01-01.

The database has already been updated.


Database is not found.


DATABASE.path

in the



\conf\user.conf

Solaris or Linux:



Check the value of

DATABASE.user

and

DATABASE.password




\conf\user.conf

Solaris or Linux:



Check the value of

DATABASE.hostname

the configuration file.

in



\conf\user.conf

Solaris or Linux:



Check the value of

DATABASE.type


Windows: HiCommand-Suite-Common-


\conf\user.conf

Solaris or Linux:



Confirm that the InterClient service is running.



8-61

Error Code

KAPM02996-E

KAPM03001-E

KAPM03004-E

KAPM03005-E

KAPM03006-E

KAPM03007-E

KAPM03026-E

KAPM03050-E

KAPM03051-E

KAPM03052-E

KAPM03053-E

KAPM03054-E

Error Message




Illegal parameters have been specified to create HSSO Context.


An error occurred on the HSSO Server.


An error occurred when CIM Client was created.


An unexpected error occurred.


A frame-enabled browser is required.

Output destinations: In window only.

A CIMException was generated during

Console screen display processing.


The parameter sent from the JP1/IM-

View is invalid.


The Launchurl is invalid.


The JP1user ID is invalid.


The JP1token is invalid.


An acquisition failure occurred in

RequestDispatcher.




Confirm that the InterBase service is running.

Fatal error occurred.



Specify the correct user ID and password.

An error occurred on the HSSO server.


An error occurred when CIM Client was created.





Use Internet Explorer 5.5 later or

Netscape 6 later.




The parameter sent from the JP1/IM-

View is invalid.


The Launchurl is invalid.

The JP1user ID is invalid.

The JP1token is invalid.

An acquisition failure occurred in

RequestDispatcher.



Error Code

KAPM03055-E

KAPM03080-E

KAPM03081-E

KAPM03082-E

KAPM03083-E

KAPM03084-E

KAPM03085-E

KAPM03086-E

KAPM03105-E

KAPM03106-E

KAPM03107-E

Error Message



HSSOIllegalArgumentException:Illegal parameters have been specified to create HSSO Context.


HSSONotRegisteredException: The application is not registered.


HSSOAuthenticationException:

Authentication failed.


HSSOServerException: An error occurred in HSSO Server.


IOException: HSSO SERVER Connection

Error.


HSSOIllegalArgumentException:

"createToken()" was used before authentication.


HSSOIllegalStateException: An unsupported version is specified.


A CIMException was generated during menu bar display processing.


A CIMException was generated during subwindow display processing.


A CIMRepositoryException was generated during menu bar display processing.




Use a browser that can use JavaScript.

Alternatively, change the setting of the browser to use JavaScript if the use of script is disabled.

HSSOIllegalArgumentException:Illegal parameters have been specified to create

HSSO Context.


HSSONotRegisteredException: The application is not registered.


HSSOAuthenticationException:



HSSOServerException: An error occurred in HSSO Server.


IOException: HSSO SERVER Connection

Error.


HSSOIllegalArgumentException:

"createToken()" was used before authentication.


HSSOIllegalStateException: An unsupported version is specified.




A CIMException was generated during subwindow display processing.






8-63

Error Code

KAPM03108-E

KAPM03109-E

KAPM03110-E

KAPM03111-E

KAPM03112-E

KAPM03113-E

KAPM03114-E

KAPM03119-I

KAPM03120-I

KAPM03122-E

KAPM03123-E

Error Message

A CIMRepositoryException was generated during subwindow display processing.


A CIMProviderException was generated during menu bar display processing.


A CIMProviderException was generated during subwindow display processing.


An exception was generated during menu bar display processing.


An exception was generated during subwindow display processing.


A NoSuchElementException was generated during menu bar display processing.


A NoSuchElementException was generated during subwindow display processing.


Are you sure that you want to log out?


Do you want to end the application?


The request parameter for a launch is invalid.


Could not acquire the required parameter. ParmName=aa...aa




A CIMRepositoryException was generated during subwindow display processing.




A CIMProviderException was generated during subwindow display processing.


An exception was generated during menu bar display processing.


An exception was generated during subwindow display processing.




A NoSuchElementException was generated during subwindow display processing.


Are you sure that you want to log out?

Do you want to end the application?

The request parameter for a launch is invalid.


Center.

The required parameter could not be acquired.


Center.



Error Code

KAPM03124-E

KAPM03125-E

Error Message

Failed to changing of token version.

Token=aa...aa

aa...aa: Token


Failed to getting of service information.

Description=aa...aa




An attempt to change the token version has failed.


Center.

The acquisition of the service information has failed.


Center.

An attempt to get the path string failed.

Log in again.

KAPM03304-E An attempt to get the path string failed.


KAPM03354-W

A value is not set because an argument is invalid.


KAPM03355-W A value is not acquired because an argument is invalid.


KAPM03356-W A default is set because an argument is invalid. default = aa...aa

aa...aa: Default


KAPM03357-E A parameter of request is invalid. paramName = aa...aa, value = bb...bb


bb...bb: Value


KAPM03358-E

KAPM03361-E

KAPM03362-E

The tree element is invalid. treeElement

= aa...aa

aa...aa: Tree element


An attempt to get the root element data has failed.


An attempt to get the common repository has failed.


A value is not set because an argument is invalid.

A value is not acquired because an argument is invalid.

A default is set because an argument is invalid.

A parameter of request is invalid.

Log in again.

The tree element is invalid.

Log in again.

An attempt to get the root element data has failed.


An attempt to get the common repository has failed.




8-65


KAPM03363-E

KAPM03364-E

An attempt to get the common resource has failed.


The registered data in the common repository is invalid.


KAPM03366-E An attempt to get the name of default view is invalid. application name =

aa...aa



KAPM03368-W An invalid association definition exists in the repository. instance = aa...aa

aa...aa: Instance


KAPM03370-W

A tree element relation

(TNB_AssocNavigationDef) is invalid. name=aa...aa, associationClass=bb...bb, fromName=cc...cc, toClassName=dd...dd, fromRole=ee...ee, toRole=ff...ff

aa...aa: Related name

bb...bb: Related class name

cc...cc: Class name of a relation place

dd...dd: Class name of a related agency

ee...ee: Attribute of a relation place

ff...ff: Attribute of a related agency


KAPM03371-W A tree element relation

(TNB_AllInstanceNavigationDef) is invalid. name=aa...aa, fromName=bb...bb, toClassName=cc...cc

aa...aa: Related name

bb...bb: Class name of a relation place

cc...cc: Class name of a related


KAPM03375-W An attempt to get the tree element data has failed. element = aa...aa

aa...aa: Element



An attempt to get the common resource has failed.




An attempt to get the name of default view is invalid.


An invalid association definition exists in the repository.



(TNB_AssocNavigationDef) is invalid.


(TNB_AllInstanceNavigationDef) is invalid.

An attempt to get the tree element data has failed.




KAPM03377-W

A tree has not been created in the state where the specification object was opened. objectName = aa...aa



KAPM03378-W The specified object does not exist or is not shown in the tree. pathName =

aa...aa, objectName = bb...bb

aa...aa: Path name

bb...bb: Object name


KAPM03379-E

KAPM03380-W An active object was not found. By default, the root object will be set.


KAPM03381-E

An attempt to create a tree from a request has failed.


An internal error occurred. If you click the Refresh button, the initial object tree will be displayed. If you cannot display the tree, log in again and then retry.


KAPM03382-E

KAPM03383-E

A tree has not been created in the state where the specification object was opened.

The specified object does not exist or is not shown in the tree.

An attempt to create a tree from a request has failed.

Log in again.

An active object was not found. By default, the root object will be set.

An internal error occurred. If you click the Refresh button, the initial object tree will be displayed. If you cannot display the tree, collect maintenance information, and then contact customer support.


An internal error has occurred. Retry the operation. If the problem still cannot be solved, log in again and then retry.



If you click the Refresh button, the initial object tree will be displayed. If you cannot display the tree, log in again and then retry. If the problem cannot be solved, collect maintenance information, and then contact the Support Center.


If you click the Refresh button, the initial object tree will be displayed. If you cannot display the tree, log in again and then retry. If the problem cannot be solved, collect maintenance information, and then contact the Support Center.

An internal error has occurred.

Retry the operation. If the problem still cannot be solved, log in again and then retry.

Do the following:

1. Retry the operation.

2. If the problem still cannot be solved, log in again and then retry.

3. If the problem still cannot be solved, collect maintenance information and contact the Support Center.



8-67


KAPM03384-E

KAPM03501-E

An internal error has occurred. Retry the operation. If the problem still cannot be solved, collect maintenance information, and then contact customer support.


A CIM object name is not available for the selected object.


KAPM03502-W There is no default method.


KAPM03503-W The repository data is invalid, so the localization object acquisition failed.


KAPM03504-W A resource is not found, so the localization object acquisition failed.


KAPM03505-W The selected object is already deleted.


KAPM03702-E A HSSOIllegalStateException occurred during launch.


KAPM03703-E An attempt to get to the URL encoding of a token failed. token = aa...aa

aa...aa: Token


KAPM03708-E

KAPM03709-E

A HSSOAuthenticationException was generated during user profile display processing.


A HSSOIllegalArgumentException was generated during user profile display processing.


KAPM03710-E A HSSOServerException was generated during user profile display processing.



An internal error has occurred.

Retry the operation. If the problem cannot be solved, collect maintenance information, and then contact the

Support Center.

A CIM object name is not available for the selected object.


There is no default method.

The repository data is invalid, so the localization object acquisition failed.


A resource is not found, so the localization object acquisition failed.


The selected object is already deleted.

Click the Refresh in NavigationFrame.

A HSSOIllegalStateException occurred during launch.


An attempt to get to the URL encoding of a token failed.


A HSSOAuthenticationException was generated during user profile display processing.


A HSSOIllegalArgumentException was generated during user profile display processing.


A HSSOServerException was generated during user profile display processing.





KAPM03712-E

KAPM03716-E

KAPM03717-W The resource bb...bb for object aa...aa cannot be accessed.


bb...bb: Resource name


KAPM03718-E The data format of the resource bb...bb for the object aa...aa is invalid.


bb...bb: Resource name


KAPM03721-E The attribute bb...bb for object aa...aa is missing.


bb...bb: Value of attribute


KAPM03722-E

KAPM03723-E

An attempt to get membership groups failed.


The format of the URL bb...bb for the object aa...aa is invalid.


bb...bb: URL


The resource information of bb...bb for object aa...aa is missing.


bb...bb: Related name


Property cc...cc of bb...bb for object

aa...aa is missing.


bb...bb: Related name

cc...cc: Value of attribute


KAPM03931-W Your session is invalid. Logout, and then login again.


KAPM03951-E An internal server error has occurred.


An attempt to get membership groups failed.


The format of the URL bb...bb for the object aa...aa is invalid.


The resource bb...bb for object aa...aa cannot be accessed.

The data format of the resource bb...bb for the object aa...aa is invalid.


The attribute bb...bb for object aa...aa is missing.


The resource information of bb...bb for object aa...aa is missing.


Property cc...cc of bb...bb for object

aa...aa is missing.


Your session is invalid. Logout, and then login again.

An internal server error has occurred.




8-69

Error Code

KAPM03952-E

KAPM03954-E

KAPM03956-E

KAPM03957-E

KAPM03958-E

KAPM03960-E

KAPM03961-E

KAPM03962-E

Error Message

An attempt to get the Session has failed.


An attempt to get the HSSOSubject has failed.


The login process has not completed properly.





The request type is not correct.


An attempt to get the string from the

ResourceBundle failed.


An attempt to get the

RequestDispatcher for "aa...aa" failed.

aa...aa: Unexpected operation


An attempt to get the application name has failed.




An attempt to get the Session has failed.


An attempt to get the HSSOSubject has failed.


The login process has not completed properly.

Specify the correct user ID and password.




The request type is not correct.


An attempt to get the string from the

ResourceBundle failed.


An attempt to get the RequestDispatcher for "aa...aa" failed.


An attempt to get the application name has failed.



Log in again. If the problem cannot be solved, collect maintenance information and contact the Support Center.



Error Code

KAPM03964-E

KAPM03965-E

KAPM03966-E

Error Message

An error occurred on the Single Sign On server.




Communications of the Single Sign On server have failed.




Do the following:

1. When using HiCommand V3.x series, make sure that the InterBase service is running. When using the

HiCommand V4.x series or later, make sure that HiRDB is running.

2. If you are using HiCommand Device

Manager, make sure its services are running.

3. Make sure that the settings and statuses of the Single Sign On server service are appropriate.

4. If the problem cannot be solved, collect maintenance information and contact the Support Center.


Do the following:

1. When using HiCommand V3.x series, make sure that the InterBase service is running. If it is not running, start

InterBase and log in again. If it is running, restart the Single Sign On

Server, and log in again.

When using the HiCommand V4.x series or later, make sure that HiRDB is running. If it is not running, start

HiRDB and log in again. If it is running, restart the Single Sign On

Server, and log in again.

2. If you are using HiCommand Device

Manager, make sure its services are running.

3. Make sure that the settings and statuses of the Single Sign On Server are appropriate.

4. If the problem cannot be solved, collect maintenance information and contact the Support Center.


An error occurred on the web server or proxy server. Do the following:

1. Make sure that the services of the

Single Sign On server are running.




8-71

Error Code

KAPM03967-E

Error Message





An error occurred on the web server or proxy server. Do the following:

1. Make sure that Hitachi Storage

Command Suite Common Web Service is running.


The token is invalid.

Log in again.

KAPM03968-E

KAPM03969-E

KAPM03970-E

KAPM03971-E

The token is invalid. token=aa...aa.

aa...aa: Token


The request is invalid.token=aa...aa.

The name of application=bb...bb.

aa...aa: Token

bb...bb: Name of application


The request is invalid.token=aa...aa.

The name of application=bb...bb.

aa...aa: Token

bb...bb: Name of application


The application is not registered. The name of application=aa...aa.

aa...aa: Name of application


The request is invalid.




The application is not registered.




This message is displayed when the usage output method of the command starts.

This message is displayed when the usage output method of the command ends.

The hcmdssup

command has started.

KAPM04004-I

Output destinations: Destinations for output level 10. hcmdssup is finished.


KAPM04006-W Log initialization has failed.


The hcmdssup

command has stopped.

The process outputting the hcmdssup log has failed.




Error Code

KAPM04007-E

KAPM04008-E

KAPM04009-E

KAPM04010-E

KAPM04011-E

KAPM04012-E

KAPM04013-E

KAPM04014-E

KAPM04022-E

Error Message

File is not found. file-name=aa...aa



The error has occurred in file access. file-name=aa...aa



aa...aa

aa...aa: NumberFormat exception message


aa...aa

aa...aa: IllegalArgument exception message


aa...aa

aa...aa: NullPointerException message


aa...aa

aa...aa: IndexOutOfBounds exception message


aa...aa

aa...aa: SecurityException message


aa...aa



Hostname is too long.





The file could not be found.


An error occurred while the file was being accessed. hsso.conf


A NumberFormatException occurred during the processing of hcmdssup

.


An IllegalArgumentException occurred during the processing of hcmdssup

.


A NullPointerException occurred during the creation of an object, such as a file object.


An IndexOutOfBoundsException occurred during the processing of hcmdssup

.


A SecurityException occurred while a system property was being accessed.


An unexpected exception occurred.


The host name is too long.

Specify a host name less than 64 bytes.

The port number is invalid.

Specify a port number from 1 to 65535.

The port number is invalid.

The specified value is outside the integer range. Check the port number.



8-73

8-74


KAPM04025-I hcmdssup succeeded.


KAPM04027-E

KAPM04028-E

KAPM04034-E

KAPM04035-E

KAPM04036-E

KAPM04038-E

KAPM04040-E

KAPM04042-E

KAPM04050-I

KAPM04051-E

KAPM04052-E

The hcmdssup

was executed successfully.


The SSL port number is invalid.




An attempt to read the file hsso.conf has failed.


An attempt to write to the file hsso.conf has failed.

Output destinations: Destinations for output level 10, and windows. hcmdssup

has failed.



Specify a port number with a value from

1 to 65535.


The type of the port number is not an integer. Check the specified value.

An attempt to read the file hsso.conf has failed.

Make sure that the hsso.conf file exists, that you have access permissions for this file, and that the file is not in use.

An attempt to write to the file hsso.conf has failed.

Make sure that the hsso.conf file exists, that you have access permissions for this file, and that the file is not in use.

The specified command line input is invalid.

Specify a valid option, and then reexecute the command.

The specified command line input is invalid. (input data = aa...aa) aa...aa: input data


The specified host name is invalid.




The specified SSL port number is invalid.


The command hcmdsprmset ended successfully.


The command hcmdsprmset has failed.




The specified host name is invalid.




The specified SSL port number is invalid.


The command ended successfully.

The command failed.


The specified command line input was invalid.

Make sure the command format is correct.



Error Code

KAPM04059-E

KAPM04061-E

KAPM04101-E

KAPM04102-E

KAPM04103-E

KAPM04104-I

KAPM04105-E

KAPM04106-E

KAPM04107-E

KAPM04108-E

KAPM04109-E

KAPM04110-E

Error Message

The specified host name is too long.


The value specified for an option is invalid.


Container server name is invalid.

Server= aa...aa

aa...aa: Container server name


Archive file is not found. file=aa...aa

aa...aa: Archive file name


Program type is invalid. type=aa...aa

aa...aa: Program type


Starting web application registration...


Privilege is invalid.



The specified host name is too long.



Revise the values specified for the options.

Container server name is invalid.


Archive file is not found.


Program type is invalid.


Web Application registration is now starting.

Cannot get tmpjavavm.properties file name.


Failed to get service registration status. service=aa...aa

aa...aa: Service name


Cannot get javavm.properties file name.


Cannot set JavaVM option.


Cannot set Java options.


The user does not have sufficient permissions to execute the command.

Execute the command as a user with

Administrator permission.

Cannot get tmpjavavm.properties file name.


Failed to get service registration status.


Cannot get javavm.properties file name.


Cannot set JavaVM option.


Cannot set Java options.




8-75

Error Code

KAPM04111-E

KAPM04112-E

KAPM04113-E

KAPM04114-E

KAPM04115-E

KAPM04116-I

KAPM04117-I

KAPM04118-E

KAPM04119-E

KAPM04120-E

KAPM04121-I

KAPM04122-E

Error Message

An attempt to check whether a program type exists in the hcmdswebpp.ini

file has failed.


Cannot write hcmdswebpp.ini

file.


Service registration has failed. service=aa...aa



Failed to get service registration status. service=aa...aa



Service registration has failed. service=aa...aa


Output destinations: Destinations for output level 0. hcmdsweb registration has succeeded.


Starting web application deletion...


Program type is not registered. type=aa...aa



Cannot delete service and folder.


Cannot delete hcmdswebpp.ini

file.

Output destinations: Destinations for output level 10. hcmdsweb deletion has succeeded.


Cannot get only a war file name.



An attempt to check whether a program type exists in the hcmdswebpp.ini

file has failed.


Cannot write hcmdswebpp.ini

file.


Service registration has failed.


Failed to get service registration status.


Service registration has failed.

Collect maintenance information and contact the Support Center. hcmdsweb registration was successful.

Web application deletion is now starting.

Program type is not registered.


Cannot delete service and folder.


Cannot delete hcmdswebpp.ini

file.

Collect maintenance information and contact the Support Center. hcmdsweb deletion was successful.

Cannot get only a war file name.




Error Code

KAPM04123-E

KAPM04124-E

KAPM04125-E

KAPM04126-E

KAPM04127-E

KAPM04128-E

KAPM04129-E

KAPM04130-E

KAPM04133-E

KAPM04134-E

KAPM04135-E

Error Message

Cannot get hcmdswebpp.ini

file name.


Cannot get name. tmphcmdswebpp.ini

file


Log initialization has failed.



Cannot get hcmdswebpp.ini

file name.


Cannot get tmphcmdswebpp.ini

file name.


Cannot insert new line character.


An attempt to exchange hcmdswebpp.ini

with tmphcmdswebpp.ini

has failed.

Output destinations: Destinations for output level 10. hcmdsweb

registration has failed.

Output destinations: Destinations for output level 0. hcmdsweb

deletion has failed.


Cannot read hcmdswebpp.ini

file.




The parameter is incorrect.


The database specified does not exist.


An unexpected error occurred. Error code = aa...aa





Cannot insert new line character.


An attempt to exchange hcmdswebpp.ini

with tmphcmdswebpp.ini

has failed.

Collect maintenance information and contact the Support Center. hcmdsweb

registration has failed.

Take action according to the last message. hcmdsweb

deletion has failed.

Take action according to the last message.

Cannot read hcmdswebpp.ini

file.


OpenSCManager

command error.


Access is denied.


The parameter is incorrect.


The database specified does not exist.






8-77

Error Code

KAPM04136-E

KAPM04137-E

KAPM04138-E

KAPM04139-E

KAPM04140-E

KAPM04141-E

KAPM04142-E

KAPM04143-E

KAPM04144-E

KAPM04145-E

KAPM04146-E

Error Message

RegOpenKeyEx command error.ErrorCode(aa...aa)



A duplicate name exists on the network.


The filename, directory name, or volume label syntax is incorrect.


The account name is invalid or does not exist.


Circular service dependency was specified.


Service already exists. service=aa...aa



The handle is invalid.


The specified service has been marked for deletion.


CreateService command error. code=aa...aa



DeleteService command error. code=aa...aa



OpenService command error. code=aa...aa




RegOpenKeyEx command error.


A duplicate name exists on the network.


The filename, directory name, or volume label syntax is incorrect.


The account name is invalid or does not exist.


Circular service dependency was specified.


Service already exists.


The handle is invalid.


The specified service has been marked for deletion.


CreateService

command error.


DeleteService


OpenService

command error.

command error.




Error Code

KAPM04147-E

KAPM04148-E

KAPM04149-E

KAPM04150-E

KAPM04151-E

KAPM04152-E

KAPM04153-E

KAPM04154-E

KAPM04155-E

KAPM04156-E

Error Message

The specified service does not exist as an installed service.


RegQueryValueEx command error. code=aa...aa



The error has occurred in aa...aa command. code=bb...bb

aa...aa: Command

bb...bb: Error code


The directory cannot be removed. directory=aa...aa

aa...aa: Directory name


The directory is not empty. directory=aa...aa



The directory name is invalid. directory=aa...aa



QueryServiceStatus command error. code=aa...aa



Failed to get installation directory.


Failed to get Service name. service=aa...aa



Service is running. service=aa...aa




The specified service does not exist as an installed service.


RegQueryValueEx

command error.


The error has occurred in aa...aa command.


The directory cannot be removed.


The directory is not empty.


The directory name is invalid.


QueryServiceStatus

command error.


Failed to get installation directory.


Failed to get Service name.


Service is running.

Stop the service, and then execute the command again.



8-79

Error Code

KAPM04157-E

KAPM04158-E

KAPM04159-E

Error Message

Failed to get service status. service=aa...aa



File is not found. file=aa...aa



Failed to delete specified file. file=aa...aa




Failed to get service status.


File is not found.


Failed to delete specified file.


KAPM04161-E

aa...aa: Original file name

bb...bb: New file name


Privilege is invalid to access aa...aa file.



KAPM04162-E

KAPM04163-E

Failed to copy from aa...aa to bb...bb.

aa...aa: Name of the source file

bb...bb: Name of the destination file


Failed to delete service. service=aa...aa



KAPM04164-W Failed to delete the war file. file=aa...aa

aa...aa: War file name


KAPM04165-W

Failed to delete the folder. folder=aa...aa

aa...aa: Folder name


KAPM04166-E Failed to delete service. service=aa...aa



Failed to rename aa...aa to bb...bb.


Permission to access the file is insufficient.


Failed to copy from aa...aa to bb...bb.


Failed to delete service.


Failed to delete the war file.


Failed to delete the folder.


Failed to delete service.





KAPM04167-E

Failed to get service folder. servicefolder=aa...aa

aa...aa: Service folder name


KAPM04168-W Failed to delete service folder. servicefolder=aa...aa

aa...aa: Service folder name


KAPM04169-E

KAPM04172-E

KAPM04173-E

File is not found. file=aa...aa



Failed to write usrconf.properties to installation information.


Failed to read usrconf.properties file.


KAPM04174-E Failed to exchange usrconf.properties to tmpusrconf.properties.


KAPM04175-E

KAPM04176-E

KAPM04177-E

KAPM04178-E

KAPM04197-I

Failed to create directory. directory=aa...aa



Failed to get the war file name. file=aa...aa



Failed to read javavm.properties file.


An attempt to exchange javavm.properties

with tmpjavavm.properties

has failed.


Service registration has succeeded. service=aa...aa




Failed to get service folder.


Failed to delete service folder.


File is not found.


Failed to write usrconf.properties

to installation information.


Failed to read usrconf.properties

file.


Failed to exchange usrconf.properties

to tmpusrconf.properties

.


Failed to create directory.


Failed to get the war file name.


Failed to read javavm.properties file.


An attempt to exchange javavm.properties with tmpjavavm.properties has failed.


The service was successfully registered.



8-81

8-82

Error Code

KAPM04198-I

KAPM04202-I

KAPM04205-E

KAPM04206-E

KAPM04207-E

KAPM04208-E

KAPM04209-E

KAPM04211-E

KAPM04212-E

KAPM04213-E

KAPM04214-E

KAPM04215-E

Error Message

Service registration has succeeded. service=aa...aa



Service deletion has succeeded. service=aa...aa



Memory alloc error. code=aa...aa



The system cannot find the file specified.


The system cannot find the path specified.


The system cannot open the file.


The process cannot access the file because it is being used by another process.


Failed to get tmpusrconf.properties file name.


Failed to get usrconf.properties file name.


ExtractionWarFolderPath function error.


Failed to get web-users.xml file name.


Failed to get template usrconf.properties file name.



The service was successfully registered.

The service was successfully deleted.

Memory alloc error.


The system cannot find the file specified.


The system cannot find the path specified.


The system cannot open the file.


The process cannot access the file because it is being used by another process.


Failed to get tmpusrconf.properties file name.


Failed to get usrconf.properties file name.


ExtractionWarFolderPath function error.


Failed to get web-users.xml file name.


Failed to get template usrconf.properties file name.




Error Code

KAPM04216-E

KAPM04217-E

KAPM04218-E

KAPM04219-E

KAPM04220-E

KAPM04221-E

KAPM04222-E

KAPM04223-E

KAPM04224-E

KAPM04225-E

KAPM04226-E

KAPM04227-E

KAPM04228-E

Error Message

Failed to get template web-users.xml file name.


Failed to get template javavm.properties file name.


Failed to get Display name.


Failed to load hntr2t.dll

. code=aa...aa



The file

option is invalid.


The type

option is invalid.


The server

option is invalid.


The classpath

option is invalid.


The librarypath

option is invalid.


The javaoption

option is invalid.


The

Xms

option is invalid.


The

Xmx

option is invalid.


RegCreateKeyEx

command error. code=aa...aa




Failed to get template web-users.xml file name.


Failed to get template javavm.properties file name.


Failed to get Display name.


Failed to load hntr2t.dll.


The file

option is invalid.


The type

option is invalid.


The server

option is invalid.


The classpath

option is invalid.


The librarypath

option is invalid.


The javaoption

option is invalid.


The

Xms

option is invalid.


The

Xmx

option is invalid.


RegCreateKeyEx

command error.




8-83

8-84

Error Code

KAPM04229-E

KAPM04230-I

KAPM04231-E

KAPM04232-E

KAPM04233-E

KAPM04234-E

KAPM04235-E

KAPM04236-E

KAPM04237-E

KAPM04238-E

KAPM04239-E

Error Message

RegSetValueEx

command error. code=aa...aa



Service deletion has succeeded. service=aa...aa





An attempt to register the program type in the registry failed. program type = aa...aa



An attempt to delete the program type in the registry failed. program type = aa...aa



Failed to remake service.


The minimum heap size has exceeded the maximum heap size.


The minimum heap size has exceeded the already set up maximum heap size.


The service name exceeds 256 characters.


The service registration is not possible because the service name exceeds 256 characters.


An attempt to get the service control manager execution file path failed.



RegSetValueEx

command error.


Service deletion has succeeded.



An attempt to register the program type in the registry failed.


An attempt to delete the program type in the registry failed.


Failed to remake service.


The minimum heap size has exceeded the maximum heap size.


The minimum heap size has exceeded the already set up maximum heap size.


The service name exceeds 256 characters.


The service registration is not possible because the service name exceeds 256 characters.


An attempt to get the service control manager execution file path failed.




Error Code

KAPM04240-E

KAPM04241-E

KAPM04242-E

KAPM04243-E

KAPM04244-E

KAPM04245-E

KAPM04246-E

KAPM04247-E

KAPM04248-E

KAPM04249-E

Error Message

An error occurred when the environment settings folder was created.


An error occurred when the environment settings file was set.


An error occurred when the web application archive file was expanded.


An error occurred when a directory expanded with the web application archive file was deleted.


An error occurred when registering and updating the web server.


An error occurred when registering and updating Tomcat.


An error occurred when the usrconf.properties file was merged.


An attempt to acquire the number of file lines has failed.


An attempt to create Map information has failed.


An attempt to read data from a file has failed.



An error occurred when the environment settings folder was created.


An error occurred when the environment settings file was set.


An error occurred when the web application archive file was expanded.


An error occurred when a directory expanded with the web application archive file was deleted.


An error occurred when registering and updating the web server.

If you are using Windows, close the

Services window (in the Control Panel), and then re-install. If the problem cannot be solved, collect maintenance information and contact the Support

Center.

An error occurred when registering and updating Tomcat.

If you are using Windows, close the

Services window (in the Control Panel), and then re-install. If the problem cannot be solved, collect maintenance information and contact the Support

Center.

An error occurred when the usrconf.properties file was merged.


An attempt to acquire the number of file lines has failed.


An attempt to create Map information has failed.


An attempt to read data from a file has failed.




8-85

Error Code

KAPM04250-E

KAPM04251-E

KAPM04252-E

KAPM04253-E

KAPM04254-E

KAPM04255-E

KAPM04256-E

KAPM04257-E

KAPM04258-E

Error Message

An attempt to set the javaVM debug option has failed.


The jvmoption

option is invalid.


An error occurred in an internal function.

(call function = aa...aa, use function =

bb...bb, note = cc...cc, error code =

dd...dd)

aa...aa: Call function

bb...bb: Use function

cc...cc: Note

dd...dd: Error code


A memory allocation error occurred.

(call function = aa...aa, use function =

bb...bb, note = cc...cc, error code =

dd...dd)

aa...aa: Call function

bb...bb: Use function

cc...cc: Note

dd...dd: Error code


An attempt to acquire the daemon shell name has failed.


An attempt to write service registration information to the version file has failed.


An attempt to delete service registration information from the version file has failed.


An attempt to start the hcmdssrv command has failed.


An error occurred during execution of the hcmdssrv command.



An attempt to set the JavaVM debug option has failed.


The jvmoption

option is invalid.






An attempt to acquire the daemon shell name has failed.


An attempt to write service registration information to the version file has failed.


An attempt to delete service registration information from the version file has failed.


An attempt to start the hcmdssrv command has failed.


An error occurred during execution of the hcmdssrv command.





KAPM04259-E

KAPM04260-E

KAPM04261-E

An attempt to create the boot shell has failed.


The startup mode of the service is invalid. (start mode = aa...aa)

aa...aa: Start mode


The starttype

option is invalid.


KAPM04262-E

KAPM04263-E

KAPM04264-E

An attempt to create the usrconf.cfg file has failed.


An attempt to deploy the compiled JSP file has failed.


A path was not found for the Web application folder. (folder path =

aa...aa)

aa...aa: Folder path


KAPM04265-E

KAPM04266-E

A path was not found for the compiled

JSP storage folder. (folder path =

aa...aa)

aa...aa: Folder path


The contents of the directory are invalid.

(Directory path = aa...aa)

aa...aa: Directory path


KAPM04267-W An attempt to delete the hwc directory has failed. (Directory path = aa...aa)

aa...aa: Directory path


KAPM04271-E An attempt to update the web application version has failed.



An attempt to create the boot shell has failed.


The startup mode of the service is invalid.


The starttype

option is invalid.

Confirm the specification of the starttype

option.

An attempt to create the usrconf.cfg file has failed.


An attempt to deploy the compiled JSP file has failed.


A path was not found for the Web application folder.


A path was not found for the compiled

JSP storage folder.


The contents of the directory are invalid.


An attempt to delete the hwc directory has failed.

An attempt to update the Web application version has failed.




8-87


KAPM04272-E

Failed to delete specified directory.

Directory=aa...aa

aa...aa: Directory


KAPM04273-W An attempt to execute the aa...aa function has failed. (error code =

bb...bb, description = cc...cc)

aa...aa: Function name


cc...cc: Error description


KAPM04274-E An attempt to load the DLL has failed.


KAPM04275-E

KAPM04276-E

KAPM04279-E

KAPM04280-E

KAPM04281-E

KAPM04282-E

KAPM04283-E


Failed to delete specified directory.

See the message KAPMxxxxx-W.

This message is displayed if an attempt to add a service description has failed.

The service explanation was not added.

It will be added the next time the hcmdsweb

command is executed.

An attempt to acquire the function address in the DLL has failed.


The file does not exist. (file name =

aa...aa)



An attempt to add a service description has failed.




The specified service is not registered.


An attempt to acquire the installation directory has failed.


The name of the specified service is invalid.


This message is displayed if an attempt to load the DLL has failed.


This message is displayed if an attempt to acquire the function address in the

DLL has failed.


This message is displayed if the file does not exist.


This message is displayed if an attempt to add a service description has failed.

Take the appropriate action based on the preceding message.

This message is displayed if a memory allocation error has occurred.

Please see the message that follows.

This message is displayed if the specified service is not registered.


This message is displayed if an attempt to acquire the path of the Hitachi Storage

Command Suite Common Component installation folder has failed.


This message is displayed if the specified service name is invalid.




Error Code

KAPM04284-E

KAPM04285-E

KAPM04286-E

KAPM04287-E

KAPM04288-E

KAPM04289-E

KAPM04290-E

KAPM04291-I

KAPM04292-I

KAPM04293-E

KAPM04294-I

KAPM04295-I

Error Message

An attempt to access the service explanation definition file has failed.


The service explanation definition file is invalid.


An attempt to change a service configuration parameter has failed.


An attempt to connect the service control manager has failed.


An attempt to open the service handle has failed.


An attempt to access the service explanation definition file has failed.


The service name was not specified.


Registration of the aa...aa Web application will now start.



Deletion of the aa...aa Web application will now start.



An attempt to delete the JSP servlet class file has failed.


The JSP servlet class file was deleted successfully.


Deletion of the JSP servlet class file will now start.



This message is displayed if an attempt to access the service explanation definition file has failed.


This message is displayed if the service explanation definition file is invalid.


This message is displayed if an attempt to change a service configuration parameter has failed.


This message is displayed if an attempt to connect the service control manager has failed.


This message is displayed if an attempt to open the service handle has failed.


This message is displayed if an attempt to access the service explanation definition file has failed.


This message is displayed if the service name is not specified.


Web application registration is now starting.

Web application deletion is now starting.

An attempt to delete the JSP servlet class file has failed.


The JSP servlet class file was deleted successfully.

Deletion of the JSP servlet class file will now start.



8-89

Error Code

KAPM04296-I

KAPM04301-I

KAPM04303-I

KAPM04304-I

KAPM04306-I

KAPM04307-E

KAPM04311-E

KAPM04312-E

Error Message

Deletion of the JSP servlet class file will now end.



Deletion of the JSP servlet class file will now end.

Uninstallation of aa...aa has started.



[All processing has finished.]


All processing has finished.

Uninstallation was successful.


All of the services for aa...aa have been deleted.



Restart the machine, and then execute the program again.


All of the services for aa...aa have been deleted.

Restart the machine, and then execute the program again.

Uninstallation has failed.

Manually perform the deletion. Output destinations: Destinations for output level 10, and windows.

Uninstallation was successful. Restart the machine.


"aa...aa" has not stopped. Stop the service, and then try again.



An attempt to acquire an installation path for aa...aa has failed. Manually delete the installation directory.



An attempt to acquire registry information has failed.


Uninstallation was successful. Restart the machine.

aa...aa has not stopped.

Stop the service, then retry.

An attempt to acquire an installation path for aa...aa has failed.

Manually delete the installation directory.

An attempt to acquire registry information has failed.




KAPM04313-E

KAPM04314-E

An attempt to acquire the registry information has failed. Manually delete the registry information.


Some files remained. Manually delete them.


KAPM04315-W All the files for aa...aa will now be deleted. Is this OK?



KAPM04316-W Are you sure you want to delete all of the files?





An attempt to acquire the registry information has failed. Manually delete the registry information.

Some files remained. Manually delete them.

All the files for aa...aa will now be deleted. Is this OK?

Are you sure you want to delete all of the files?

Uninstallation was interrupted.

KAPM04318-I

KAPM04319-E


The OS setting information was successfully deleted.


An attempt to delete the OS setting information has failed.


KAPM04320-W The resident process "aa...aa" has not stopped.

aa...aa: Process name


KAPM04321-I The OS settings information will now be deleted to stop the resident process.


The OS setting information was successfully deleted.

An attempt to delete the OS setting information has failed. manually perform the deletion.

The resident process aa...aa has not stopped.

The OS settings information will now be deleted to stop the resident process.

A DOMException has occurred.




A RuntimeException has occurred.




8-91

Error Code

KAPM04380-E

Error Message

MalformedURLException occurred.

aa...aa
















A MalformedURLException has occurred.


An IllegalDataException has occurred.


An IllegalOptionException has occurred.

Specify a valid option to execute the command.

An IOException has occurred.


A SAXException has occurred.


An HttpProtocolException has occurred.


A ServerNotStartException has occurred.

Confirm that Device Manager, Hitachi

Storage Command Suite Common Web

Service, and Hitachi Storage Command

Suite Single Sign On Service are running, and that the port numbers used by these services are correct.

An Exception has occurred.


Servlet initialization has started.



Error Code

KAPM04405-E

KAPM04421-E

KAPM04422-E

KAPM04423-E

KAPM04426-E

KAPM04429-E

KAPM04440-E

Error Message

Can't read DTD file.



An attempt to read the DTD file has failed.

Windows: Copy the file hcmdsrepClient.dtd

and hcmdsrepServer.dtd

from Hitachi-



\sample\conf

to Hitachi-Storage-

Command-Suite-Common-Componentinstallation-folder

\conf

Solaris or Linux: Copy the file hcmdsrepClient.dtd


from

/opt/HiCommand/Base/sample/conf

to

/opt/HiCommand/Base/conf

The IP address of the requesting client.

aa...aa: IP address


The error has occurred in Repository process.


The illegal data has detected in Server process.


The error has occurred in Server process.


The version is incorrect. Version aa...aa is required.

aa...aa: Versions supported by the server


An error occurred during server processing.


Token has timed out.


The error has occurred in Repository process.

When using HiCommand V3.x series, make sure that InterBase or InterClient is running. If the problem cannot be solved, contact the Support Center.

When using the HiCommand V4.x series or later, make sure that HiRDB is running. If the problem cannot be solved, contact the Support Center.

The illegal data has detected during server process.




The client version is not 1.0.




Token has timed out.

Execute hcmdsrep again.



8-93


Repository registration is now starting.


KAPM04455-W aa...aa has already registered in

Repository.

aa...aa: Value specified by the type option and the displayname option


KAPM04463-W aa...aa is not found in Repository.



KAPM04464-E aa...aa is associated with more than one

ServiceAccessPoint Instances.



aa...aa was already registered in the repository.

Specify a different combination of the type

option and the displayname

option to execute hcmdsrep

.

aa...aa was not found in the repository.

Specify registered information to execute hcmdsrep

.

aa...aa is associated with more than one

ServiceAccessPoint Instance.

The database may be broken. Collect maintenance information and contact the

Support Center.

Deletion of product information from the repository is now starting.


KAPM04468-W aa...aa is not found in Repository.



aa...aa was not found in the repository.

Specify a valid program type to execute hcmdsrep

.

Acquisition of display information from the repository is now starting.

KAPM04475-W No results were found in Repository.


KAPM04480-E


Type name is too Long.


No results were found in Repository.

KAPM04481-E

KAPM04489-E

Type or URL is not set.


This version does not support the add option.


Type name is too Long.


Support Center.

Type or URL is not set.


Support Center.

This version does not support the add option.

The add option cannot be used.



Error Code

KAPM04499-E

KAPM04510-E

KAPM04511-E

KAPM04512-E

KAPM04513-E

KAPM04514-E

KAPM04515-E

KAPM04516-E

KAPM04517-E

KAPM04518-E

KAPM04519-E

KAPM04520-E

Error Message

Detail of exception: aa...aa

aa...aa: Contents of the exception


Option is invalid. option= aa...aa

aa...aa: Option



aa...aa: Option



aa...aa: Option


Option value is invalid. optionvalue=aa...aa

aa...aa: Option value


Following Option is not supported:

aa...aa

aa...aa: Option



aa...aa: Option



aa...aa: Option


Option is invalid.


Option is invalid.


Option is invalid.


Option is invalid.



Detail of exception.


Specify a valid option.





An option value is invalid.








Option is invalid.


Option is invalid.


Option is invalid.


Option is invalid.




8-95

8-96

Error Code

KAPM04521-E

KAPM04522-E

KAPM04523-E

KAPM04524-E

KAPM04525-E

KAPM04529-E

KAPM04554-E

Error Message

Option is invalid.


Invalid Group or Role.


Username or password is invalid.


Failed to connect to HiCommand Suite

Single Sign On Service.


Failed to connect to HiCommand Device

Manager.



Option is invalid.


Invalid Group or Role.

Specify the name and password of a user who belongs to the GROUP "Global" and

ROLE "Admin".

Username or password is invalid.

Specify a user name and password registered in Device Manager.

Failed to connect to Hitachi Storage

Command Suite Single Sign On Service.

Confirm that Hitachi Storage Command

Suite Single Sign On Service is running.

Failed to connect to Device Manager.

Confirm that the Device Manager service is running.




Option needs value. option=aa...aa

aa...aa: Option


An HSSOException has occurred.


A FileNotFoundException has occurred.

Windows: Copy the file hcmdsrepClient.dtd


from Hitachi-



\sample\conf

Command-Suite-Common-Componentinstallation-folder

to Hitachi-Storage-

\conf

Solaris or Linux: Copy the file hcmdsrepClient.dtd


from

/opt/HiCommand/Base/sample/conf

to

/opt/HiCommand/Base/conf



An option requires a value.

Specify a value for the option.





Not support tag type detected.


An unsupported tag type was detected.




Error Code

KAPM04555-E

KAPM04556-E

KAPM04557-E

KAPM04558-E

KAPM04560-I

KAPM04561-I

KAPM04562-E

KAPM04563-E

KAPM04601-E

KAPM04602-E

KAPM04603-E

Error Message

Value is too long.


Failed to connect to HiCommand Suite

Common Web Service.


A single sign-on server exception has occurred.


An invalid role was detected.

Output destinations: Destinations for output level 10. hcmdsrep

add has succeeded. aa...aa


Output destinations: In window only. hcmdsrep

delete has succeeded. aa...aa



add has failed. aa...aa



delete has failed. aa...aa



Command format is invalid.


Command format is invalid. invalidparam=aa...aa

aa...aa: Invalid parameter


File is not found. file-name=aa...aa




The value is too long.

Enter a string that does not exceed the character limit.

Hitachi Storage Command Suite Common

Web Service could not be connected.

Confirm that Hitachi Storage Command

Suite Common Web Service is running.


Confirm that the Hitachi Storage

Command Suite Server is running.

Confirm that the used database is running.

If the problem cannot be solved, contact the Support Center.

An invalid role was detected.

Specify a user belonging to the group

"Admin" or "Peer" and the user's password. hcmdsrep

add has succeeded. hcmdsrep

delete has succeeded. hcmdsrep

add has failed.

See the message output prior to receiving this message. hcmdsrep

delete has failed.

See the message output prior to receiving this message.

The command format is invalid.


The command format is invalid.


The file could not be found.




8-97

8-98

Error Code

KAPM04604-E

KAPM04605-E

KAPM04606-E

KAPM04608-I

KAPM04609-E

KAPM04613-I

KAPM04614-E

Error Message

Directory is not found. directoryname=aa...aa



Bundle PP Name is invalid. name=aa...aa

aa...aa: Invalid value


Web Container server is invalid. name=aa...aa

aa...aa: Invalid value


Setup completed successfully.


Failed to create file. file-name=aa...aa



Delete completed successfully.


Failed to setup server.


KAPM04615-E Failed to delete server.


KAPM04616-E

KAPM04702-E

KAPM04703-E

KAPM04705-E

Server is running. pid=aa...aa

aa...aa: Process ID


The option(s) specified is insufficient.


The option value specified is invalid.


The option "aa...aa" is not supported.

aa...aa: Option



The directory could not be found.


The value of the type option is invalid.


The value of the server option is invalid.


Setup completed successfully.

An attempt to create a file has failed.


Delete completed successfully.

An attempt to set up the server has failed.


An attempt to delete the server has failed.


The server is running.










Error Code

KAPM04706-E

KAPM04707-E

KAPM04710-E

KAPM04711-E

KAPM04713-E

KAPM04714-E

KAPM04715-E

KAPM04716-E

KAPM04717-E

Error Message

The option "aa...aa" appears 2 times or more.

aa...aa: Option


The combination of options is invalid.









An exception occurred. See the following message KAPM49001-E for details.







The input XML contains a grammar mistake.


Failed to connect to HBase Storage

Mgmt Common Service.


Failed to connect to HBase Storage

Mgmt Web Service.


Failed to connect to the host specified in hsso.conf.


An invalid URL was detected. ( aa...aa )

aa...aa: URL




Failed to connect to HBase Storage Mgmt

Common Service.

Confirm that HBase Storage Mgmt

Common Service is running.

Failed to connect to HBase Storage Mgmt

Web Service.

Confirm that the HBase Storage Mgmt

Web Service has started. If the HBase

Storage Mgmt Web Service has started, confirm that the hostname in hsso.conf is correct.



\conf\hsso.conf

Solaris or Linux:

/opt/HiCommand/Base/conf/hsso.conf

Failed to connect to the host specified in hsso.conf.

Confirm that the host name in hsso.conf is correct.



\conf\hsso.conf

Solaris or Linux:

/opt/HiCommand/Base/conf/hsso.conf

An invalid URL was detected.

Confirm that the URL is correct.



8-99

8-100


KAPM04718-E

KAPM04719-E

The server returned an empty response.


An unsupported element type was detected in the XML.


KAPM04722-W aa...aa error(s) were detected in the response.

aa...aa: Number of errors


KAPM04723-E

KAPM04724-E

KAPM04800-E

Invalid error information was detected.


Invalid server information was detected.


Authentication information is insufficient.







aa...aa error(s) were detected in the response.






Authentication information is insufficient.

Use a SOAP Client that send

Authentication information.

KAPM04802-E

KAPM04803-E

KAPM04805-E


A single sign-on server communication exception has occurred.




An XML parser exception occurred.


Authentication has failed to authenticate the specified user id or password. See the following message KAPM49001-E for details.


Communication between a single sign-on client and the server has failed. See the following message KAPM49001-E for details.


A single sign-on server exception has occurred. See the following message

KAPM49001-E for details.

When using HiCommand V3.x series, confirm that InterServer/InterBase or

Device Manager is running. If the problem cannot be solved, collect maintenance information and contact the

Support Center.

When using the HiCommand V4.x series or later, make sure that HiRDB or Device

Manager are running. If the problem cannot be solved, collect maintenance information and contact the Support

Center.

An XML parser exception occurred.





KAPM04806-E

KAPM04807-E

The received XML element aa...aa contains an unexpected value cc...cc for attribute bb...bb. The expected value is

dd...dd. TARGET=ee...ee

aa...aa: XML tag name including unexpected value

bb...bb: Name of attribute unexpected value is set

cc...cc: Unexpected value of attribute

dd...dd: Value of attribute the server expects

ee...ee: Information for processing


The XML element aa...aa is not allowed as a child of element bb...bb.

TARGET=cc...cc

aa...aa: Tag name of unexpected element

bb...bb: Tag name of element including unexpected element

cc...cc: Information for processing


KAPM04808-W The received XML attribute aa...aa is not allowed as an attribute of bb...bb.

TARGET=cc...cc

aa...aa: Unexpected attribute name

bb...bb: Tag name of element including unexpected attribute



KAPM04809-E Message catalog information is insufficient for the log message.

TARGET=aa...aa

aa...aa: Information for processing


KAPM04810-E

KAPM04812-E


TARGET=aa...aa



Failed to connect to HiCommand Device

Manager.



The received XML element aa...aa contains an unexpected value cc...cc for attribute bb...bb. The expected value is

dd...dd.


The XML element aa...aa is not allowed as a child of element bb...bb.


The XML attribute aa...aa is not allowed as an attribute of bb...bb.


Message catalog information is insufficient for the log message.



See the following message KAPM49001-E for details.


Failed to connect to Device Manager.

Confirm that the service is running and check the value of HDVM.host in the init.conf file.



8-101


KAPM04813-E

KAPM04814-W

The CIM datatype aa...aa is invalid for

bb...bb; it will be handled as a string type.

aa...aa: Specified CIM data type name

bb...bb: Attribute name Specified CIM data type is specified


KAPM04815-E

An exception occurred. TARGET=aa...aa



KAPM04816-E

This operation aa...aa is unknown.

TARGET= bb...bb

aa...aa: Unexpected operation

bb...bb: Information for processing


INSTANCENAME cannot be used for the set operation. TARGET=aa...aa



KAPM04817-E The CIM operation aa...aa is missing required argument bb...bb.

TARGET=cc...cc

aa...aa: CIM operation name

bb...bb: Essential parameter name



KAPM04818-I

KAPM04819-I

Starting CIM access... Method = aa...aa

aa...aa: Name of the method of the repository API


Ending CIM access...


KAPM04820-I

KAPM04821-I

Receiving a request...


Replying to the request...





The CIM datatype aa...aa is invalid for

bb...bb; it will be handled as a string type.

Specify a supported data type.

This operation aa...aa is unknown.


INSTANCENAME cannot be used for the set operation.


The CIM operation aa...aa is missing a required argument bb...bb.


CIM access is starting.

Ending CIM access.

Receiving a SOAP request.

Replying to the SOAP request.



Error Code

KAPM04826-I

KAPM04827-I

KAPM04828-I

KAPM04829-I

KAPM04830-I

KAPM04832-E

KAPM04833-E

KAPM04834-E


The instance has been updated.

TARGET=aa...aa



A new instance has been created.

TARGET=aa...aa



The class is empty. TARGET=aa...aa



The instance could not be found.

TARGET=aa...aa



The instance was deleted.

TARGET=aa...aa



The input data aa...aa is not valid for data type bb...bb. TARGET=cc...cc

aa...aa: Input data value

bb...bb: Input data type



The received XML element bb...bb is missing a required attribute aa...aa.

TARGET=cc...cc

aa...aa: Required attribute name

bb...bb: XML tag name which contains attribute of aa...aa



The received XML element bb...bb is missing a required child element aa...aa.

TARGET=cc...cc

aa...aa: XML tag name of the required element

bb...bb: XML tag name of the parent element



The instance has been updated by the set operation.

A new instance has been created by the set operation.

The result of the enumerate operation shows the class is empty.

The instance could not be found.

The instance was deleted.

The input data aa...aa is not valid for data type bb...bb. See the following message KAPM49001-E for details.


The received XML element bb...bb is missing a required attribute aa...aa.


The received XML element bb...bb is missing a required child element aa...aa.




8-103

8-104


KAPM04835-W

The received XML element bb...bb has no child element aa...aa.

TARGET=cc...cc

aa...aa: Required tag name

bb...bb: Tag name of parent element



KAPM04836-E The received XML element aa...aa with attribute bb...bb=cc...cc is duplicated.

TARGET=dd...dd

aa...aa: Duplicated tag name of XML element

bb...bb: Attribute name

cc...cc: Attribute value

dd...dd: Information for processing


KAPM04837-E

KAPM04838-I

The XML element aa...aa as child of element bb...bb is duplicated.

TARGET=cc...cc

aa...aa: Duplicated tag name of XML element

bb...bb: Tag name of parent element



The class has been created.

TARGET=aa...aa



KAPM04839-I

KAPM04840-I

KAPM04841-I

KAPM04842-E

The class already exist. TARGET=aa...aa



The class could not be found.

TARGET=aa...aa



The class was deleted. TARGET=aa...aa



The class aa...aa of the instance is invalid. TARGET=aa...aa




The received XML element bb...bb has no child element aa...aa.

Specify the bb...bb element for the

aa...aa element in the XML file.

The received XML element aa...aa with attribute bb...bb=cc...cc is duplicated.


The XML element aa...aa as child of element bb...bb is duplicated.


The class has been created.

The class already exists.

The class could not be found.

The class was deleted.

The class aa...aa of the instance is invalid.





KAPM04901-E

KAPM04902-E

KAPM04905-E

KAPM04906-I





An attempt to open the file failed. Path

= aa...aa

aa...aa: File path name


The alias for aa...aa was set.

aa...aa: Program product name


KAPM04907-I

KAPM04908-I

The alias for aa...aa was overwritten.



The alias for aa...aa was deleted.



KAPM04910-W The alias for aa...aa does not exist.



KAPM04909-E

KAPM04933-E

KAPM04950-I

KAPM04951-I

The alias for aa...aa does not exist.





PrintWriter was created. path =

"aa...aa", file = "bb...bb"

aa...aa: Path of file bb...bb

bb...bb: File name


BufferedReader was created. path =

"aa...aa", file = "bb...bb"






Set the valid parameter.



An attempt to open the file failed.

Confirm that a file exists in the specified location or does not in use.

The alias for aa...aa was set.

The alias for aa...aa was overwritten.

The alias for aa...aa was deleted.




PrintWriter was created.

BufferedReader was created.



8-105


KAPM04952-E

KAPM04953-I

KAPM04954-W PrintWriter cannot be closed. PrintWriter is null.


KAPM04955-I

PrintWriter has closed.


BufferedReader has closed.


KAPM04956-W BufferedReader cannot be closed.

BufferedReader is null.


KAPM04957-E The specified application command is not registered. application name =

"aa...aa"

aa...aa: Specified application name


KAPM04958-E

KAPM04959-I

The specified application command is already registered. application name =

"aa...aa"

aa...aa: Specified application name


aa...aa has been added to the file.



KAPM04960-I

The file was not found. path = "aa...aa", file = "bb...bb"




KAPM04970-I

KAPM04971-E

aa...aa has been removed from the file.



Processing ended normally.


The specified command is already registered.



The file was not found.


PrintWriter has closed.

PrintWriter cannot be closed. PrintWriter is null.

BufferedReader has closed.

BufferedReader cannot be closed.

BufferedReader is null.

The specified application command is not registered.

The specified application command is already registered.

aa...aa has been added to the file.

aa...aa has been removed from the file.


The specified command is already registered.



Error Code

KAPM04972-E

KAPM04973-E

KAPM04974-E

KAPM04975-E

KAPM04976-E

KAPM04977-E

KAPM05001-I

KAPM05002-E

KAPM05003-E

KAPM05004-E

KAPM05005-E

Error Message

The specified command is not registered.






The type of OS is unknown.


IllegalOptionException occurred.

Description = "aa...aa"

aa...aa: Error details


InconsistencyException occurred.



Output destinations: Destinations for output level 10. hcmdssrv

was entered.


Command format is invalid.


Option is invalid. option=aa...aa

aa...aa: Invalid option


Server name is invalid. servername=aa...aa

aa...aa: Server name


The Win32API has failed. API name=aa...aa, error code=bb...bb

aa...aa: Name of the WIN32API

bb...bb: Results of GetLastError()



The specified command is not registered.





The type of OS is unknown.


IllegalOptionException occurred.


InconsistencyException occurred.


The hcmdssrv

command was entered.

The option is invalid.




The server name is invalid.


An error has occurred in WIN32API.




8-107

Error Code

KAPM05006-E

KAPM05007-I

KAPM05008-E

KAPM05009-I

KAPM05010-E

KAPM05011-E

Error Message

Failed to start service. servicename=aa...aa



Already started service. servicename=aa...aa



Failed to stop service. servicename=aa...aa



Already stopped service. servicename=aa...aa



Failed to query service. servicename=aa...aa



Failed to control service.


KAPM05012-E Failed to access registry. maintenancecode=aa...aa

aa...aa: Maintenance code


KAPM05013-W Failed to read init.conf. maintenancecode=aa...aa



KAPM05014-W Failed to initialize trace. apiname=aa...aa,reason=bb...bb

aa...aa: Log trace API name

bb...bb: Maintenance code



An attempt to start the service has failed.


The service is already running.

An attempt to stop the service has failed.


The service is already stopped.

An attempt to query the service status has failed.


An attempt to control the service has failed.


An attempt to access the registry has failed.


An attempt to read init.conf has failed.


An attempt to initialize the log has failed.

Make sure that multiple instances of the hcmdssrv

command are not executed concurrently. If the problem occurs frequently, collect maintenance information and contact the Support

Center.




KAPM05015-E

KAPM05016-I

An internal function has failed. Function name=aa...aa, error code=bb...bb

aa...aa: Internal function name



Succeeded in starting of service. service-name=aa...aa



KAPM05017-I

KAPM05018-E

Succeeded in stopping of service. service-name=aa...aa



A system call has failed. API name=aa...aa, error code=bb...bb

aa...aa: System call name



KAPM05019-W Definition is invalid. name=aa...aa

aa...aa: Definition value name


KAPM05020-E Failed to open file. maintenancecode=aa...aa



KAPM05021-E

KAPM05022-W Service does not exist.


KAPM05023-E

Service does not exist.


Could not find executable file. filename=aa...aa

aa...aa: Executable file


KAPM05024-W Failed to initialize trace. Reason=aa...aa

aa...aa: Reason



An internal function has failed.


A request to start the service was accepted.

A request to stop the service was accepted.

A system call has failed.


The definition is invalid.


An attempt to open the file has failed.


The service does not exist.


The service does not exist.


Could not find executable file.


Failed to initialize trace.

Processing is continued without a trace.



8-109


KAPM05025-I

KAPM05026-E

KAPM05027-E

KAPM05028-E

KAPM05029-E

KAPM05030-E

The start type has been successfully changed. service-name = aa...aa



An attempt to change the start type has failed. service-name = aa...aa



An attempt to start the DBMS service has failed.


An attempt to stop the DBMS service has failed.


An attempt to acquire the status of the

DBMS service has failed.


An attempt to query the status of a service has failed. (service name =

aa...aa)



KAPM05035-E

KAPM05036-I

An attempt to execute the command

aa...aa has failed.

aa...aa: executable file name


The command aa...aa was executed successfully. (return code = bb...bb)

aa...aa: executable file name

bb...bb: return code


KAPM05037-E An attempt to query a service has failed.


KAPM05038-W The error has occurred in aa...aa command. code=bb...bb

aa...aa: Command




The start type has been successfully changed.

An attempt to change the start type has failed.


An attempt to start the DBMS service has failed.

Refer to details to the hcmdsdbsrv log.

An attempt to stop the DBMS service has failed.


An attempt to acquire the status of the

DBMS service has failed.


An attempt to query the status of a service failed.

Take action according to the message output before or after this message.

An attempt to execute a command has failed.


A command was executed successfully.

An attempt to query a service has failed.

Take action according to the message output before or after this message.

The error has occurred in aa...aa command.



Error Code

KAPM05201-E

KAPM05202-E

KAPM05203-E

KAPM05204-E

KAPM05205-E

KAPM05206-E

KAPM05207-E

KAPM05208-E

KAPM05209-I

KAPM05210-E

KAPM05211-E

KAPM05212-E

KAPM05213-E option.

Error Message

The memory is insufficient.(aa...aa)

aa...aa: Variable name


The number of options is insufficient.


There is no value following the option.


Option is invalid.


There is only a value though there is no


The error occurred in dispatcher.


The error occurred in the registration of the service controller.


The error occurred in the

HandlerRoutine.


The service_stop_thread is started.


The error occurred in the service_stop_thread.


The error occurred in the Report Status.


The error occurred in create JavaVM.


Failed to set processing of JavaVM.



The memory is insufficient.


The number of options is insufficient.


An option has been specified without a value.


An option contains an error.


Only a value is specified for arguments, and not the corresponding option.


An error occurred in the dispatcher.


An error occurred in the registration of the service controller.


An error occurred during list addition of the process's handler function.


A service stop request thread was opened.


An error occurred in the service stop request thread.


An attempt to report progress to the service control manager has failed.


An error occurred while generating the

JavaVM.


An attempt to set up the JavaVM has failed.




8-111

Error Code

KAPM05214-I

KAPM05215-I

KAPM05216-E

KAPM05217-E

KAPM05218-E

KAPM05219-E

KAPM05220-E

KAPM05221-E

KAPM05222-E

KAPM05223-E

KAPM05224-E

KAPM05225-E

Error Message

aa...aa started.



aa...aa stopped.



The error occurred in the start of service.


Failed to get to the option definition file value.


Failed to change the current directory.


Failed to create JavaVM.


Failed to connect to JavaVM.


The class is not found.


The method is not found.



Getinstpath.(aa...aa)

aa...aa: Registry key or registry path


The error occurred in the LoadLibrary.



GetProcAddress.



The service has started.

The service has stopped.



An attempt to get the value of the option definition file has failed.


An attempt to change the current directory has failed.


An attempt to create the JavaVM has failed.


An attempt to connect to the JavaVM has failed.


The class was not found.


The method was not found.


An error occurred while acquiring a key or path from the registry.


An attempt to load the DLL has failed.


An attempt to get the function address in the DLL has failed.




Error Code

KAPM05226-E

KAPM05227-E

KAPM05228-E

KAPM05229-E

KAPM05230-E

KAPM05231-E

KAPM05232-E

KAPM05250-I

KAPM05251-I

KAPM05252-E

KAPM05253-E

KAPM05255-E

Error Message

The error occurred in the AllocConsole.


The error occurred in the DeleteFile.



GenerateConsoleCtrlEvent.



An error occurred while allocating a new console to a process.


An error occurred while deleting a file.


An error occurred while sending the specified signal to the console process group.


An attempt to execute the command to start the Web container server has failed.


An attempt to execute the command to start the Web container server has failed.


An attempt to execute the command to stop the Web container server has failed.


An attempt to execute the thread-dump acquisition command has failed.


The service stopped abnormally.

(service name = aa...aa)



Registration of the information-search user has finished.


Deletion of the information-search user has finished.




The specified option contains an invalid character.




An attempt to execute the command to stop the Web container server has failed.


An attempt to execute the thread-dump acquisition command has failed.


The service stopped abnormally.


Registration of the information-search user has finished.

Deletion of the information-search user has finished.

An option specified for the command is invalid.

Specify a correct option.

The specified option parameter contains an invalid character.

Specify valid characters for the option parameter.





8-113

8-114


KAPM05256-E

KAPM05257-E

KAPM05258-I

KAPM05259-I





The command has started.


The command has ended.


KAPM05263-W No registered information exists








The command has ended.

KAPM05264-E

KAPM05265-E

KAPM05266-W

KAPM05280-I

KAPM05281-I

KAPM05282-E

KAPM05285-E

KAPM05286-E

The file format is invalid.


An error occurred during file I/O processing.


A server has not been registered.


Registration of a secret has succeeded.


Deletion of a secret has succeeded.








No registered information exists.

Register the user information by using the set option, and then re-execute the command. If the same message is output again, acquire the maintenance information, and then contact the

Support Center.





No information was displayed when the list option was specified.


Support Center.

Registration of a secret has succeeded.

Deletion of a secret has succeeded.










KAPM05288-I

KAPM05289-I



The command has finished.


KAPM05293-W No registered information exists.


The command hcmdsradiussecret has started.

The command hcmdsradiussecret has finished.

KAPM05294-E

KAPM05295-E

KAPM05296-W

KAPM05301-E

KAPM05302-E

KAPM05303-E

KAPM05304-I








Register a secret by using the set option, and then re-execute the command. If the same message is output again, acquire the maintenance information, and then contact the Support Center.





No information was displayed when the list option was specified.

Register a secret by using the set option, and then re-execute the command. If the same message is output again, acquire the maintenance information, and then contact the Support Center.

The license has expired.

Use a license key that has not expired.


Output destinations: Destinations for the log.

The system environment is incorrect.


The entered license key is invalid.







Use a regular license key published by the license server.


The acquiring of aa...aa logs started.



Backup of aa...aa started.

KAPM05310-E



The acquiring of aa...aa logs abnormally ended.







8-115

Error Code

KAPM05311-I

KAPM05314-E

KAPM05315-E

KAPM05316-E

KAPM05317-E

KAPM05318-I

KAPM05319-E

KAPM05320-I

KAPM05321-E

KAPM05322-E


The acquiring of aa...aa logs successfully ended.






Backup of aa...aa abnormally ended.


Backup of aa...aa successfully ended.



The specified directory is not empty.




The specified directory name aa...aa is invalid.

aa...aa: Invalid directory name


aa...aa is not registered. bb...bb is available.

aa...aa: Program product name specified in option

bb...bb: Program product name registered in the command


The acquiring of logs successfully ended.

aa...aa



The acquiring of logs abnormally ended.

aa...aa



Backup successfully ended. (aa...aa)



Backup abnormally ended. (aa...aa)



aa...aa does not exist.




Specify an empty directory.


Check the options of the command.

The specified directory name aa...aa is invalid.

Confirm that the specified directory is correct.

aa...aa is not registered. bb...bb is available.

Specify the registered program product name.




Backup successfully ended.

Backup abnormally ended.


aa...aa does not exist.

Confirm that the file exists in the specified directory.



Error Code

KAPM05323-I

KAPM05324-E

KAPM05325-E

KAPM05326-E

KAPM05328-I

KAPM05329-E

KAPM05330-E

KAPM05331-E

KAPM05332-E

KAPM05333-E

KAPM05334-I

KAPM05335-E


Information for restore:

To restore the HiCommand shared repository, specify the "

/enforce

" option.

Before restoring, you have to stop the services "

InterServer

" and "

InterBase

Server

".

Note that the HiCommand shared repository is overwritten with old backup data after the restore.


The privilege is invalid.


Information for restore:

To restore the Hitachi Storage Command

Suite shared repository, specify the

"

/enforce

" option.

Before restoring, you have to stop the services "

InterServer

" and "

InterBase

Server

".

Note that the Hitachi Storage Command

Suite shared repository is overwritten with old backup data after the restore.

An attempt to execute hcmdsras failed.


An attempt to execute jar has failed.


The privilege is invalid.

Execute as a user with execution privilege.

An attempt to execute hcmdsras failed.


An attempt to execute jar has failed.

Make sure that the file name specified in the arc option does not include the pathname. If that is not the problem, contact the Support Center.

The hcmdsbasebackup processing has succeeded.

The hcmdsbasebackup processing has succeeded.


The hcmdsbasebackup processing has failed.












The license key file that was entered could not be found.


The hcmdsbasebackup processing has failed.



Check the options of the command.


Use a license key that has not expired.




Use a regular license key published by the license server.


The license key file that was entered could not be found.

Confirm that the specified path is valid.



8-117

8-118

Error Code

KAPM05336-E

KAPM05337-I

KAPM05390-I

KAPM05402-E

KAPM05403-E

KAPM05405-E

KAPM05406-E

KAPM05407-E

KAPM05410-E

KAPM05411-E

KAPM05413-E

KAPM05414-E






The hcmdsras processing has succeeded.







The license key file that was input may be damaged. Contact the Support Center and acquire a new license key file.


Confirm that the specified license key file is correct.

The hcmdsras processing has succeeded.


Specify all the necessary options.


Specify the option and specify the necessary proceeding values (user name and password, etc.).


Do not specify an unsupported option.


aa...aa: Option



aa...aa: Option





Check the specification of the option.




Confirm that no option that should be specified exclusively is specified at the same time.




Confirm that the file exists, that the file is not in use, and that the make directory of the file is correct.






A fatal structure error was detected in the input XML.




A fatal structure error was detected in the input XML.





KAPM05415-E

KAPM05417-E

KAPM05418-E

KAPM05419-E An unsupported element type was detected in the XML.


KAPM05422-W aa...aa error(s) were detected in the response.

aa...aa: Number of errors


KAPM05423-E

An error occurred during communication processing. (Detail: aa...aa)



An invalid URL was detected. (aa...aa)

aa...aa: URL




KAPM05424-E

KAPM05425-E





The input file contains a grammar mistake.


KAPM05426-E

KAPM05427-E

KAPM05432-E

KAPM05433-E

An error occurred when inputting the file.


The specified value is invalid. value =

aa...aa

aa...aa: Value


Link registration processing has failed.

Processing is interrupted.


The acquisition as a result of registration processing has failed.



An error occurred during communication processing. See the following message

KAPM49001-E for details.


An invalid URL was detected.

Check the specification of the URL.





aa...aa error(s) were detected in the response.







Correct the syntax error in the specified definition file.



The specified value is invalid.

Confirm the value in the user definition application file.

Link registration processing has failed.

Processing is interrupted.


The acquisition as a result of registration processing has failed.




8-119

8-120


KAPM05434-E

KAPM05435-E

KAPM05436-E

KAPM05437-E

I/O of XML has failed.


An error occurred in the SAX parser.


An attempt to analyze the execution result has failed.


The execution result of the XREP processing was null.


KAPM05438-W The "aa...aa" xrep processing result is

bb...bb.

aa...aa: Result of hcmdsxrep command

bb...bb: Result of the command


KAPM05439-E

KAPM05440-E

An attempt to register a link has failed.


An attempt to delete a link has failed.


KAPM05441-W An attempt to check the result has failed.


KAPM05442-E

KAPM05443-E

The registered information was not found.


The table that registers a link does not exist.


KAPM05444-E An error occurred within the server.


KAPM05445-E

KAPM05446-I

An unexpected error occurred within the server.









An attempt to analyze the execution result has failed.


The execution result of the XREP processing was null.


The "aa...aa" xrep processing result is

bb...bb.


An attempt to register a link has failed.


An attempt to delete a link has failed.


An attempt to check the result has failed.


The registered information was not found.


The table that registers a link does not exist.




An unexpected error occurred within the server.






KAPM05501-I Backing up the database to file aa...aa...



KAPM05502-I INTERBASE_PID=aa...aa.

aa...aa: InterBase process ID


KAPM05503-W

The file aa...aa will be overwritten. Is this OK?



KAPM05504-W The HiCommand Server database will be overwritten by this procedure. Is this

OK?


KAPM05505-E

KAPM05506-E

KAPM05507-I

KAPM05508-E

The aa...aa file does not exist or is not readable. The HiCommand Server database was not altered.



The aa...aa file does not exist or is not readable.The HiCommand Server database was not altered.



Restoring the database from the aa...aa file...



The path of the specified database file is invalid.


Backing up the database to file aa...aa.

INTERBASE_PID=aa...aa.

The file aa...aa will be overwritten. Is this

OK?

The continuation will overwrite the

aa...aa.

The Hitachi Storage Command Suite

Common Component database will be overwritten by this procedure. Is this

OK?

The continuation will overwrite the

Hitachi Storage Command Suite Common

Component database.

The aa...aa file does not exist or is not readable. The Hitachi Storage Command

Suite Common Component database was not altered.

Confirm that aa...aa file exists.

Alternatively, check the permission of the

aa...aa file.

The aa...aa file does not exist or is not readable. The Hitachi Storage Command

Suite Common Component database was not altered.

Confirm that the aa...aa file exists.

Restoring the database from the aa...aa file.

The path of the specified database file is invalid.


DATABASE.path

in the



\conf\user.conf

Solaris or Linux:




8-121

Error Code

KAPM05509-E

Error Message

The specified database file was not found.



The specified database file was not found.

Check the value of

DATABASE.path




\conf\user.conf

Solaris or Linux:


An attempt to read to a file has failed.


KAPM05510-E

KAPM05511-E

An attempt to read to a file has failed. file name=aa...aa.







Backup has succeeded. KAPM05512-I Backup succeeded.


KAPM05513-E An attempt to back up has failed.


An attempt to back up has failed.

Take action according to the message output in the window after command execution.

Restoration has succeeded. KAPM05514-I Restoration succeeded.


KAPM05515-E An attempt to restore has failed.


KAPM05516-E

KAPM05530-I

KAPM05531-I

KAPM05532-I

The setup of the specified database is invalid.


An attempt to restore has failed.

Take action according to the message output in the window after command execution.

The setup of the specified database is invalid.

Make sure the setting for the key that the file

DATABASE

starts is correct.



\conf\user.conf

Solaris or Linux:


Backup of the database has started. Backup of the database has started.


Backup of the database has ended.


Restoration of the database has started.


Backup of the database has ended.

Restoration of the database has started.



Error Code

KAPM05533-I

KAPM05534-I

KAPM05535-I

KAPM05536-I

KAPM05537-I

KAPM05538-I

KAPM05539-I

KAPM05540-I

KAPM05541-I

Error Message

Restoration of the database has ended.


The database will now be backed up to file aa...aa.

aa...aa: Backup file


The system area has been damaged. Do you want to recover the system? [y or n]


Please press the Enter key.


Stop the HiRDB service before restoring the database.


Re-creation of the system area has started.


Re-creation of the system area has ended.


Re-creation of the RD area has started.


Re-creation of the RD area has ended.


An attempt to back up the database has failed.



Restoration of the database has ended.

The database will now be backed up to file aa...aa.

The system area has been damaged.

Please select whether to restore this system. Enter not). y

(for yes) or

Please press the Enter key. n

(for do

Stop the HiRDB service before restoring the database.

Re-creation of the system area has started.

Re-creation of the system area has ended.

Re-creation of the RD area has started.

Re-creation of the RD area has ended.

KAPM05544-E

KAPM05545-E An attempt to restore the database has failed.



Make sure that the directory specification is correct. If you cannot solve the problem, collect maintenance information and contact the Support Center.

An attempt to restore the database has failed.


The backed-up version is different from the version in the current environment.

KAPM05546-W The backed-up version is different from the version in the current environment.


KAPM05547-I Do you want to continue and restore the database?


Do you want to continue and restore the database?



8-123

8-124

Error Code

KAPM05548-I

KAPM05550-E

KAPM05551-E

KAPM05559-E

KAPM05560-E

Error Message

Restoration of the database will continue.


The option(s) specified is invalid.


An attempt to execute the aa...aa command has failed.



KAPM05552-E

KAPM05553-E

KAPM05558-E

HiRDB has not been installed.


The RD area of the specified program type could not be found.


KAPM05554-E The aa...aa could not be deleted.



KAPM05555-E

KAPM05556-E

An attempt to set the environment variable has failed.


An attempt to create the backup file has failed.


KAPM05557-E An I/O error occurred.


An attempt to open the archive file has failed.


The backup file format is invalid.


The database location of the specified program type has not been created.



Restoration of the database will continue.


Specify the option correctly.


Make sure that the command specification is correct. If you cannot solve the problem, collect maintenance information and contact the Support

Center.


Make sure that HiRDB has been installed.


Make sure that HiRDB has been set up.

The file aa...aa could not be deleted.

An attempt to set the environment variable has failed.


An attempt to create the backup file has failed.


An I/O error occurred.


An attempt to open the archive file has failed.

Make sure that the file specification is correct. If it is correct but you still cannot solve the problem, collect maintenance information and contact the Support

Center.

The backup file format is invalid.

Specify a valid backup file.


Make sure that the specified application is installed.



Error Code

KAPM05561-I

KAPM05562-E

KAPM05563-I

KAPM05564-E

KAPM05565-I

KAPM05566-E

KAPM05567-E

KAPM05568-E

KAPM05569-E

KAPM05570-I

KAPM05573-E

KAPM05574-E

KAPM05575-E

Error Message

The database was backed up successfully.




The database was completely restored.


An attempt to completely restore the database has failed.


The database was partially restored.


An attempt to partially restore the database has failed.




aa...aa:bb...bb


bb...bb: Message


aa...aa













The database was backed up successfully.


The database was completely restored.

An attempt to completely restore the database has failed.

The database was partially restored.

An attempt to partially restore the database has failed.



Message for debugging.







Center.


Confirm that HiRDB has already installed.



8-125

8-126

Error Code

KAPM05576-E

KAPM05577-E

KAPM05578-E

KAPM05579-E

KAPM05580-I

KAPM05581-I

KAPM05586-I

KAPM05587-I

KAPM05588-I

KAPM05589-I

Error Message



An attempt to clear an HiRDB environment variable has failed.






Re-creation of the database has started.


Re-creation of the database has ended.




Confirm that HiRDB has already set up.




Make sure that the specified application is installed.



Re-creation of the database has started.

Re-creation of the database has ended.

Unsetup of aa...aa has started.



Unsetup of aa...aa has ended.



Setup of aa...aa has started.



Setup of aa...aa has ended.



Execution of the aa...aa command has started.



Execution of the aa...aa command ended normally.



Backup of the parameter definition file has ended.


The backup file of the parameter definition file has been deleted.


Execution of the aa...aa command has started.


Backup of the parameter definition file has ended.

The backup file of the parameter definition file has been deleted.



Error Code

KAPM05590-E

KAPM05591-E

KAPM05592-E

KAPM05596-E

KAPM05597-E

KAPM05598-E

KAPM05599-E

KAPM05601-I

KAPM05602-I

Error Message











Center.

HiRDB has not been set up.

Confirm that HiRDB has already set up.

HiRDB has not been set up.






The aa...aa file was not found.

Make sure that HiRDB has been set up. If you cannot solve the problem, collect maintenance information and contact the

Support Center.

The aa...aa file could not be read.

Make sure that HiRDB has been set up. If you cannot solve the problem, collect maintenance information and contact the

Support Center.

The aa...aa folder could not be deleted.


aa...aa: Folder name


An SQL exception occurred.


An attempt to clear the HiRDB system environment variables has failed.




aa...aa:bb...bb


bb...bb: Message


The acquisition of HiRDB detail logs has started.


The acquisition of HiRDB detail logs was successful.



Check whether HiRDB is running. If it is, collect maintenance information, and contact the Support Center.

An attempt to clear the HiRDB system environment variables has failed.





The acquisition of HiRDB detail logs has started.

The acquisition of HiRDB detail logs was successful.



8-127

Error Code

KAPM05603-I

KAPM05604-I

KAPM05605-I

KAPM05606-I

KAPM05607-E

KAPM05608-E

KAPM05609-E

KAPM05610-I

KAPM05611-E

KAPM05612-E

Error Message

The acquisition of the HiRDB RDAREA has started.


The acquisition of the HiRDB RDAREA was successful.


The acquisition of the table data has started.


The acquisition of the table data was successful.


The command aa...aa is executing in another process.




The acquisition of the HiRDB RDAREA has started.

The acquisition of the HiRDB RDAREA was successful.

The acquisition of the table data has started.

The acquisition of the table data was successful.

The wait for the end of the command




The command aa...aa timed out and ended.



The command is executing in another process.

After the command executing in the other process finishes, re-execute the command.

The wait for the end of the command executing in another process has failed.

Re-execute the command. If this does not resolve the problem, collect maintenance information, and then contact the Support Center.

The command executing in another process timed out.


The specified product is a version for which registration data can be moved.

(This was determined by comparing the versions of the specified product and the product to be installed.)

The specified product is a version for which registration data can be moved.



The specified product is a version for which registration data cannot be moved. (This was determined by comparing the versions of the specified product and the product to be installed.)


The version of the specified product could not be acquired. (product name =

aa...aa)



The specified product is a version for which registration data cannot be moved.



An attempt to execute the version acquisition function has failed.




Error Code

KAPM05613-E

KAPM05614-E

KAPM05615-E

KAPM05616-E

KAPM05617-E

KAPM05618-I

KAPM05619-I

KAPM05620-I

KAPM05621-E

KAPM05622-E

KAPM05623-E

KAPM05624-E


The format of the version number file for the specified product is invalid.


The specified product is not installed.

(product name = aa...aa)



An internal error occurred: aa...aa

aa...aa: Detailed message


The number of specified options is invalid.


The contents of the version file are invalid.


The hcmdsppcheck started.

command has


The hcmdsppcheck

command has ended.


The hcmdsppvrs successful.

command was


The hcmdsppvrs command failed.


The format of the version number file for the specified product is invalid.


The product specified by the version check command is not installed.


An internal error occurred. A detailed message to pinpoint the cause is displayed in the log.


The number of options to specify in the version check function is invalid.


The version number file contains characters that are not numbers.


The version check function has started.

The version check function has ended.

The version acquisition function was successful.

Initialization of the log failed.


An attempt to assign memory to store the log file path has failed.


An attempt to acquire the installation path has failed.


An attempt to execute the version acquisition function has failed.










8-129

Error Code

KAPM05625-E

KAPM05626-E

KAPM05627-E

Error Message

The product names do not match.




There is no version number file.



The product name specified by the version check function does not match the registered product name.


The product name that must be specified by the version check function is not specified.


There is no version number file in the location specified by the version check function.


Upgrade permission file already exists. KAPM05628-I

KAPM05629-E

KAPM05630-E

A file already exists at the specified output destination.


A folder already exists at the specified output destination.


There is no registry key for HBase.


KAPM05640-I

The user ID and password were changed successfully.


KAPM05641-I

KAPM05642-W Neither the user ID nor the password was changed.


KAPM05643-E

There is no password file to reference.


The format of the password file is invalid.


KAPM05644-E An attempt to change the user ID and password has failed.


A folder already exists at the output destination specified by the version check function.

After deleting the output destination folder, re-execute the command, or specify an empty directory.

There is no registry key for Hitachi

Storage Command Suite Common

Component.


The specified user ID and password were changed successfully.

The password file that writes the user ID and password was not found.

The specified user ID and password are the same as before.

Specify a new (different) ID and password.

The password file might have been corrupted.

Collect the maintenance information, and then contact the Support Center.

An attempt to change the specified user

ID and password failed because an error occurred.

Check the preceding log.



Error Code

KAPM05645-E

KAPM05646-E

KAPM05647-E

KAPM05648-E

KAPM05649-E

KAPM05650-E

KAPM05654-E

KAPM05655-E

KAPM05656-E

KAPM05657-I

KAPM05658-I

KAPM05659-E

Error Message



The specified argument contains an invalid character.


An attempt to acquire the HiCommand


Component installation path has failed.








An attempt to output the password file has failed.


The character string specified by the option is too long.


The character string specified by the option is too short.


The hcmdschangeaccount started.

command has


The hcmdschangeaccount ended.

command has


The program product specified by the type option is invalid.



Please make sure the specification of the option is correct.

Specify the option correctly, and execute the command again.

An invalid character was specified in the option.

Enter valid characters only.

An attempt to acquire the Hitachi


Component installation path has failed.








An error occurred during processing to write to the password file.


The character string specified by the option exceeds the maximum number of characters.

Enter a character string that is within the maximum number of characters.

The length of the character string specified by the option is less than the minimum number of characters. Enter a character string that is at least the minimum number of characters.

The hcmdschangeaccount started.

command has

The hcmdschangeaccount ended.

command has

The value specified for the type option is invalid.




8-131

8-132

Error Code

KAPM05660-E

KAPM05661-E

KAPM05662-E

KAPM05663-E

KAPM05672-I

KAPM05673-E

KAPM05674-E

KAPM05675-E

KAPM05676-E

KAPM05677-E

KAPM05678-I

KAPM05679-E

KAPM05680-E

The user ID specified by the newid option is invalid.


The password specified by the newpass option is invalid.






The memory size was changed successfully.


An attempt to change the memory size has failed.


A fatal error occurred during processing.


The service is running.


In a Windows x32 environment, the memory size cannot be changed to

Large.

Error Message




The current memory size is aa...aa.

aa...aa: Memory size


The current memory size is unknown.





The value specified for the newid option is invalid.


The value specified for the newpass option is invalid.


An error occurred during processing to load the password file.



Please execute it again after changing the user name.

The memory size was changed successfully.

An attempt to change the memory size has failed.

Check the message output before or after this message, and take action appropriate to that message.



The service is running.

Stop the service, and then execute the command again.

In a Windows x32 environment, the memory size cannot be changed to

Large.

Specify a valid option to execute the command.



The current memory size is displayed.

The current memory size is unknown.

Use the hcmdschgheap command to reset the memory size.





Error Code

KAPM05681-E

KAPM05682-E

KAPM05683-E

KAPM05684-E

KAPM05685-E

KAPM05686-E

KAPM05687-I

KAPM05688-E

KAPM05689-E

KAPM05690-E

KAPM05691-E

KAPM05699-E

Error Message

An entered argument is invalid.


The specified options are insufficient.


The value specified for an option is invalid. (option = aa...aa)

aa...aa: Option


The specified value is invalid. (value =

aa...aa)

aa...aa: Value


The hcmds.home value cannot be acquired.


An attempt to load the file has failed.

(file = aa...aa)





Execution of the hcmdsweb command has failed.


Execution of the hcmdsweb2 command has failed.


In Windows x86 version, you cannot specify Large.


Command execution failed because services were running.





An entered argument is invalid.

Specify an appropriate argument.

A necessary option is not specified.

Specify a valid option, and then try again.

The value specified for an option is invalid. (option = aa...aa)

Check the value specified for the option.

The specified value is invalid. (value = aa...aa)

Specify an appropriate value.




(file = aa...aa)



Execution of the hcmdsweb command has failed.


Execution of the hcmdsweb2 command has failed.


In Windows x86 version, you cannot specify Large.


Command execution failed because services were running.

Stop all Suite products, Single Sign On

Server, and Common Web Service, and then re-execute the command.





8-133


KAPM05802-E

KAPM05803-E

KAPM05804-E

KAPM05805-E

KAPM05806-E



The specified arguments are insufficient.


The specified value of option is invalid.

(Option = aa...aa)

aa...aa: Option name


The specified directory cannot be created. (directory = aa...aa)



The specified directory name already existed as a file. (file = aa...aa)



KAPM05807-E


aa...aa)

aa...aa: Specified value


KAPM05808-E The aa...aa does not exist.





KAPM05810-E The aa...aa already exists.



KAPM05811-E

Command aa...aa returns value bb...bb.

The error message is cc...cc.


bb...bb: Return code

cc...cc: Error message







The file aa...aa does not exist.



The specified value of option is invalid.

Check the specified value of the option.

The specified directory cannot be created.

Make sure that you have write permission for the directory.

The specified directory name already existed as a file.

Specify another directory name.

Make sure that the file specification is correct. If you cannot solve the problem, collect maintenance information and contact the Support Center.

The directory aa...aa does not exist.


The file aa...aa already exists.

Delete the file, or move to another directory.

Command aa...aa returns value bb...bb.

The error message is cc...cc.

Check the specified value of the option. If you cannot solve the problem, collect maintenance information and contact the

Support Center.



Error Code

KAPM05812-I

KAPM05813-E

KAPM05814-E

KAPM05815-E

KAPM05816-E

KAPM05817-E

KAPM05818-I

KAPM05819-I

KAPM05820-I

KAPM05821-I

KAPM05822-I

KAPM05823-E




An IOException occurred. (details =

aa...aa)

aa...aa: Exception details


An exception occurred. (details =

aa...aa)



A NullPointerException occurred. (details

= aa...aa)



An error occurred while executing the hcmdsauthmode command.


There is no RD area in the system.







A NullPointerException occurred.


An error occurred while executing the hcmdsauthmode command.



Make sure that the Hitachi Storage

Command Suite product has been installed.

The hcmdsauthmove command has started.

The hcmdsauthmove command has started.


Processing to import data has started.


Processing to import data has ended.


Processing to export data has started.


Processing to export data has ended.


HiRDB has not started.







Start HiRDB.

The directory aa...aa already exists.

Specify another directory. aa...aa: Directory name




8-135

8-136

Error Code

KAPM05825-E

KAPM05826-E

KAPM05827-E

KAPM05828-E

KAPM05829-E

KAPM05830-E

KAPM05831-E

KAPM05832-I

KAPM05833-E

KAPM05834-I

KAPM05835-E

KAPM05836-E


An HSSOException occurred. (details =

aa...aa)



A CIMException occurred. (details =

aa...aa)




(directory name = aa...aa)



An attempt to execute the hcmdsauthmove command has failed.






An attempt to execute SQL has failed.


The authentication data was backed up successfully.


An attempt to back up the authentication data has failed.


The authentication data was restored successfully.


An attempt to restore the authentication data has failed.


An attempt to acquire the physical table name has failed. (table name = aa...aa)








Specify an empty directory.

An attempt to execute the hcmdsauthmove command has failed.








The authentication data was backed up successfully.

An attempt to back up the authentication data has failed.

The authentication data was restored successfully.

An attempt to restore the authentication data has failed.

The physical table name was not requested from the logical table name.

Make sure the DBMS has started, and then re-execute. If you cannot solve the problem, collect the maintenance information, and then contact the

Support Center.




KAPM05837-W

The column data exceeds 80 characters.

(column data = aa...aa)

aa...aa: Column data


KAPM05838-E

KAPM05840-E

An attempt to execute the SQL has failed. (SQL = aa...aa, error code =

bb...bb)

aa...aa: Executed SQL statement





KAPM05841-E

KAPM05842-I

KAPM05843-E

KAPM05844-E

KAPM05845-E

KAPM05846-E

KAPM05850-E


The column data of the TNB_AccountUser table could not be reduced to within 80 characters.

An attempt to execute the SQL has failed.


The option is invalid. Code = [aa...aa],

Data = [bb...bb]

aa...aa: Generated code

bb...bb: Generated option and value

Output destinations: Destinations for output level 10. hcmdsbanner

[aa...aa]{,[bb...bb],......[.....]}

aa...aa: Command line argument

bb...bb: Command line argument


The message file does not exist.



Specify correct options, and then reexecute the command.



The options specified for the command will be displayed.

The path specified for the message file is not a file.


The message exceeded 1000 characters.


The path specified in the aa...aa option is not an absolute path.

aa...aa: Option


An attempt to set the banner message display has failed.


The message file specified in the " file

" option does not exist.

Please specify the correct file, and then execute the command.

The path of the message file specified in the " file

" option is not a file.

Please specify the correct file, and then execute the command.

The message of the message file specified in the "file" option exceeded

1,000 characters.

Please keep the message to 1,000 characters or less.


Specify the absolute path, then retry.

An attempt to set the banner message has failed.




8-137


KAPM05851-E

An attempt to set the banner message display has failed. File = [aa...aa], Code

= [bb...bb]

aa...aa: File or directory

bb...bb: Generated code


KAPM05852-I Setting of the banner message display has been completed.


KAPM05860-W The banner message display has already been cancelled.



An attempt to set the banner message has failed.


The setting of the banner message has been completed.

The banner message has already been deleted.



Error Code

KAPM05861-E

KAPM05862-E

KAPM05863-I

KAPM05876-E

KAPM05879-E

KAPM05880-E

KAPM05881-E

KAPM05882-E

KAPM05883-E

KAPM05884-E

KAPM05885-E


An attempt to cancel the banner message display has failed.


An attempt to cancel the banner message display has failed. File =

[aa...aa], Code = [bb...bb]

aa...aa: File or directory

bb...bb: Generated code


Cancellation of the banner message display has been completed.




aa...aa

aa...aa: Information for debugging


The value of EXCurrentVersion is invalid.


EXCurrentVersion does not exist.


The registry key that must be acquired does not exist.




The version management file is invalid


The version management file that must be acquired does not exist.


An attempt to delete the banner message has failed.


An attempt to delete the banner message has failed.


The banner message has been released.



Information for debugging.

The value of EXCurrentVersion is invalid.


EXCurrentVersion does not exist.






The version management file is invalid


The version management file that must be acquired does not exist.




8-139

Error Code

KAPM05886-E

KAPM05887-I

KAPM05890-I

KAPM05891-E

KAPM05892-I

KAPM05893-I

KAPM05894-E

KAPM05895-E

KAPM05896-E

KAPM05897-E

KAPM05898-E

KAPM05899-E

Error Message

An attempt to acquire the version has failed.




Please make sure the product has been correctly installed.

If it has been correctly installed, acquire the maintenance information, and then contact the Support Center.

The processing of the version acquisition function was succeeded.

The hcmdsvrsutil utility was successful.


The hcmdsbasevrs successful.

command was


The sub-key that shows the version does not exist.


The hcmdsbasevrs started.

command has


The hcmdsbasevrs

command has ended.










An attempt to create the log file path has failed.


There is no registry key for HBase.


The version display function was successful.



The version display function has started.

The version display function has ended.









An attempt to create the log file path has failed.


There is no registry key for Hitachi


Component.




Error Code

KAPM05900-I

KAPM05901-I

KAPM05902-E

KAPM05903-E

KAPM05904-I

KAPM05905-E

KAPM05909-E

KAPM05910-E

Error Message

The hcmdsdbtrans started.

command has


The hcmdsdbtrans normally.

command ended





The hcmdsdbtrans


The hcmdsdbtrans normally.

command ended

An option is invalid. Code=[aa...aa],

Data=[bb...bb]

aa...aa: Code indicating generation location

bb...bb: Generated option and value

Output destinations: Destinations for output level 10. hcmdsdbtrans

[aa...aa]{,[bb...bb],......[.....]}

aa...aa: Command line argument

bb...bb: Command line argument



aa...aa: Option




An attempt to acquire the version of








The options specified for the command are displayed.


Specify the absolute path, then retry.



An attempt to acquire the version of the installed aa...aa failed.

Make sure that the products have been properly installed, and if necessary, take actions to satisfy this condition. If an error still occurs after taking the above actions, collect maintenance information, and then contact Customer Support.



8-141

Error Code

KAPM05911-E

KAPM05912-I

KAPM05913-E

KAPM05914-E

KAPM05915-E

KAPM05916-E

KAPM05920-E

Error Message

aa...aa is a version that cannot be registered.




The aa...aa data in the registration data cannot be registered because the data cannot be used with the installed aa...aa version.

Change the installed aa...aa version to the version used when the registration data was created, or to a version for which the registration data can be moved.

If operation is possible without registering the aa...aa data, exclude this data and register the data for the other products.

aa...aa cannot be registered because it is not installed.

If the aa...aa data is necessary, install

aa...aa, and then re-execute the command.

aa...aa cannot be registered because it is not installed.



Processing to register aa...aa will stop because it is not installed.



Processing to register aa...aa will stop because it is not in the registration data.



Processing to register data will stop because aa...aa, specified in the type option, is not installed.

If registration of aa...aa is necessary, install aa...aa and then re-execute the command.

If operation is possible without registering the aa...aa data, exclude this data and register the data for the other products.

Processing to register data will stop because aa...aa, specified in the type option, is not in the registration data.

Use the type option to specify only the products that are included in the archive file or in the directory specified by the workpath option.

An attempt was made to register primary server data into the secondary server.

Check the data to be imported.

An attempt was made to register primary server data into the secondary server.


An attempt was made to register secondary server data into the primary server.


The archive file specification is incorrect.


An attempt was made to register secondary server data into the primary server.

Check the data to be imported and the setting of the server to which the data is to be imported.

The archive file name specified in the file option is incorrect.

Revise the path specified in the command option.



Error Code

KAPM05921-E

KAPM05922-E

KAPM05923-E

KAPM05924-E

KAPM05925-E

KAPM05926-E

Error Message

An attempt to extract the archive file has failed.


An attempt to create an archive file has failed.


An archive file cannot be created because the data exceeds 2 GB.


The work directory specification is incorrect.


The work directory is not empty.


The format of the registration data in the work directory is incorrect.



An attempt to extract the archive file specified in the file option has failed.

Make sure the following conditions are satisfied, and if necessary, take actions to satisfy them:



The capacity of the disk used for the directory specified by the workpath option is sufficient.



The archive file is for the hcmdsdbtrans

command.

If an error still occurs after taking the above actions, collect maintenance information, and then contact Customer

Support.

An attempt to create an archive file has failed.

Make sure that you secure sufficient space in the disk that is to store the archive file. If an error still occurs even after securing the disk space, collect maintenance information, and then contact Customer Support.

An archive file cannot be created because the data exceeds 2 GB.

Instead of the archive file, transfer the data stored in the directory specified by the workpath option to the migration destination server.

The work directory specification is incorrect.

Revise the path specified in the workpath option.

The work directory is not empty.

Specify an empty directory or uncreated directory as the work directory.

A file or directory required by the hcmdsdbtrans

command is not in the work directory specified by the workpath option.



When the file option is specified

Check whether the specified file is the archive file for the hcmdsdbtrans command.

When the file option is not specified



Check whether all the contents of the directory specified by the workpath option when exporting are stored in the directory specified by the workpath option.

If an error still occurs after taking the above actions, collect maintenance information, and then contact Customer

Support.



8-143

Error Code

KAPM05927-E

KAPM05928-E

Error Message

DBMS is not running.


DBMS is not set up.



Data I/O cannot be performed because the DBMS is not running.

Start the DBMS by using the hcmdsdbsrv command.

Data I/O cannot be performed because the DBMS is not set up.

Make sure the installation status of the product is correct.

An attempt to delete a file or directory made in the work directory has failed.

Please delete the work directory.

KAPM05929-W An attempt to delete the work directory has failed.


KAPM05930-I aa...aa will now be exported.

aa...aa: "The application data" or "The authentication data"


KAPM05931-I

KAPM05932-I

KAPM05933-I

aa...aa has been exported.



aa...aa has been deleted from the authentication data.



The archive file will now be created.


KAPM05934-I

KAPM05935-I

KAPM05936-I

KAPM05937-I

The archive file has been created.


The archive file will now be extracted.


The archive file has been extracted.


aa...aa will now be imported.



aa...aa will now be exported.

aa...aa has been exported.

aa...aa has been deleted from the authentication data.

The archive file will now be created.

The archive file has been created.

The archive file will now be extracted.

The archive file has been extracted.

aa...aa will now be imported.



Error Code

KAPM05938-I

KAPM05939-E

KAPM05950-E

KAPM05951-E

KAPM05952-E

KAPM05953-I

KAPM05954-E

KAPM05955-E

KAPM05956-E

KAPM05957-E

Error Message

aa...aa has been imported.



aa...aa

aa...aa: Details from the time of the error


The specified product is not supported.



aa...aa has been imported.

See the preceding detailed error message.

Take action according to the preceding message.





The product specified by the version acquisition function is not supported.


There is no sub-key that indicates the version.



The product specified by the version acquisition function is not installed.

Please install the product specified by the option.

The processing of the version acquisition function succeeded.

The processing of the hcmdsvrsutil library succeeded.






The processing of the hcmdsvrsutil library failed.


There is no registry key for the specified product.



Please specify the product name, and then re-execute the command.


Please specify the correct product name, and then re-execute the command.

The processing of the version acquisition function failed.


There is no registry key for the product specified by the version acquisition function.





8-145

8-146

Error Code

KAPM05958-E

KAPM05959-E

KAPM05970-I

KAPM05971-E

KAPM05972-E

KAPM05973-I

KAPM05974-I

KAPM05975-E

KAPM05976-E

KAPM05977-E

KAPM05978-E

Error Message

An attempt to acquire the sub-key that shows the version of the specified product has failed.


The file that stores the installation path is invalid.


The hcmdsppvrs successful.

command was



(product name = aa...aa)



An attempt to acquire version information for the specified product has failed.


The hcmdsppvrs



The hcmdsppvrs

command has ended.




Log initialization failed.


Initialization of the installation path has failed.





There is no sub-key that indicates the version of the product specified by the version acquisition function.



The file that stores the installation path is invalid.


The version acquisition function was successful.

The product specified by the version acquisition function is not installed.

Please install the specified product.

The version of the product specified by the version acquisition function could not be acquired.



The version acquisition function started.

The version acquisition function ended.





Initialization of the installation path failed.






Error Code

KAPM05979-E

KAPM05980-E

Error Message

The number of specified options is invalid.


A file already exists at the specified output destination.


KAPM05981-E A folder already exists at the specified output destination.


KAPM05982-E The file-creation function failed.


KAPM05983-E The file-writing function failed.


KAPM05984-I

KAPM05985-E

The version was successfully acquired.

(product name = aa...aa, version =

bb...bb)


bb...bb: Version


An attempt to acquire the version has failed. (product name = aa...aa)



KAPM05986-E A fatal error occurred: aa...aa

aa...aa: Detailed message


KAPM05987-I The processing of the hcmdsvrsutil library succeeded.



The number of options specified by the version acquisition function is invalid.


The file already exists at the output destination specified by the version acquisition function.


The folder already exists at the output destination specified by the version acquisition function.


The function that creates the file for writing the version value failed.


The function that writes the version value to the file failed.


The version acquisition was successful.




A fatal error occurred. A detailed message showing the cause is output.

Make sure the specified product is supported. If it is supported, the specified product name might be incorrect; so enter the correct product name, and then re-execute the command.

The processing of the version acquisition function succeeded.



8-147

8-148

Error Code

KAPM05988-E

Error Message

The processing of the hcmdsvrsutil library failed. (RTN = aa...aa, message

= bb...bb)

aa...aa: Version acquisition function return code

bb...bb: Version acquisition function error message



The processing of the version acquisition function failed.


Fatal error.


Updating of the database has started. KAPM06001-I

KAPM06002-I

KAPM06003-I

KAPM06004-I

KAPM06005-I

KAPM06006-I

KAPM06007-I

KAPM06008-E

KAPM06009-I

KAPM06010-E


Updating of the database has started.


The database was updated from 01-00 to 01-01.


The database need not be updated to

01-01.


The database updating from 01-01 to

03-00 has started.


The database was updated from 01-01 to 03-00.


The database need not be updated to

03-00.


The database is already updated.


Updating of the database abnormally ended.


Updating of the database has ended.


An attempt to backup of the database has failed.


The database was updated from 01-00 to

01-01.

The database does not need to be updated to 01-01.

The database updating from 01-01 to 03-

00 has started.

The database was updated from 01-01 to

03-00.

The database does not need updating to

03-00.

The database is already updated.

Updating of the database has abnormally ended.


Updating of the database has ended.

An attempt to backup the database has failed.




Error Code

KAPM06011-E

KAPM06012-I

KAPM06013-I

KAPM06015-E

KAPM06016-E

KAPM06017-E

KAPM06018-E

KAPM06019-E

KAPM06020-E

Error Message

An attempt to restore of the database has failed.


The database does not need to be updated to aa...aa.

aa...aa: Version


The database has been updated from

aa...aa to bb...bb.

aa...aa: Old version

bb...bb: New version


An attempt to change the database meta definition has failed.





The database does not need to be updated to aa...aa.

The database has been updated from

aa...aa to bb...bb.

The version of the database to be upgraded is unknown.


The current database version could not be obtained.


An attempt to acquire the connection has failed.


An attempt to set up the auto-commit function has failed.


An attempt to create the lock table has failed.


An attempt to change the database meta definition has failed.

Confirm that InterBase has started. If it has started, collect maintenance information, and contact the Support

Center.

The version of the database to be upgraded is unknown.


The current database version could not be obtained.


Center.

An attempt to acquire the connection has failed.


Center.

An attempt to set up the auto-commit function has failed.


Center.

An attempt to create the lock table has failed.


Center.



8-149

Error Code

KAPM06021-E

KAPM06022-E

KAPM06023-E

KAPM06024-E

KAPM06025-E

KAPM06026-E

KAPM06027-I

KAPM06028-E

KAPM06029-E

KAPM06030-E

Error Message





An attempt to update the version of the database version table has failed.


An error occurred during an attempt to read a file.


An attempt to acquire the database version has failed.


An attempt to upgrade the database has failed.




An attempt to set up the environment has failed. (system property name =

aa...aa)

aa...aa: System property name


Database is not running.


Disk capacity is insufficient.





Center.



Center.

An attempt to update the version of the database version table has failed.


Center.

An error occurred during an attempt to read a file.




Center.



Center.


An attempt to set up the environment has failed.



Please start HiRDB.

Disk capacity is insufficient.

Restore the repository from the backup file, increase the database capacity, and then re-execute.



Error Code

KAPM06031-E

KAPM06032-E

KAPM06033-E

KAPM06034-E

KAPM06035-E

KAPM06036-E

KAPM06037-I

KAPM06038-E

KAPM06039-E

KAPM06040-E

KAPM06041-E

Error Message





The current database version is incorrect.


Exclusion control of a TNB_DBVersion table has failed.


The access class of a database could not be found.


Access of a database has failed.


The database has been update from version aa...aa to bb...bb.

aa...aa: version

bb...bb: version


An attempt to acquire the user names of users who access the database has failed.


The version of the target database is unknown.








Restore the repository from the backup file, and then re-execute. If the problem cannot be resolved even after reexecution, collect maintenance information and contact the Support

Center.



The current database version is incorrect.


Exclusion control of a TNB_DBVersion table has failed.


The access class of a database could not be found.


Access of a database has failed.


The database has been update from version aa...aa to bb...bb.

An attempt to acquire the user names of users who access the database has failed.


The version of the target database is unknown.








8-151


KAPM06042-W

The SQL will be disregarded. (SQL =

aa...aa, error code = bb...bb)




KAPM06043-E An attempt to perform a rollback has failed.



This message is displayed when the executed SQL statement is to be disregarded during processing to upgrade the database version.

KAPM06044-E

KAPM06045-I

KAPM06046-I

KAPM06047-I

KAPM06048-E

The version upgrade definition file is invalid.


The SQL will now be executed. (SQL =

aa...aa)

aa...aa: SQL statement


Processing to upgrade the database version started. (version = aa...aa)

aa...aa: Database version


Processing to upgrade the database version ended. (version = aa...aa)

aa...aa: Database version


An attempt to execute the SQL has failed. (SQL = aa...aa, error code =

bb...bb)




KAPM06049-E

KAPM06100-I



The hcmdschgurl command started.


This message is displayed when an attempt to perform a rollback during processing to upgrade the database version has failed.


Support Center.

The version upgrade definition file is invalid.


This message is displayed when the SQL statement is to be executed during processing to upgrade the database version.

Processing to upgrade the database version started.

Processing to upgrade the database version ended.

This message is displayed when an attempt to execute the SQL during processing to upgrade the database version has failed.


Support Center.



The hcmdschgurl command started.



Error Code

KAPM06101-I

KAPM06102-E

KAPM06103-I

KAPM06104-E

KAPM06105-I

KAPM06106-E

KAPM06111-I

KAPM06112-E

KAPM06113-E

KAPM06114-E

KAPM06115-E

Error Message

The hcmdschgurl command successfully ended.


The hcmdschgurl command abnormally ended.


An attempt to back up the database has succeeded.




An attempt to restore the database has succeeded.




The URL was changed from "aa...aa" to

"bb...bb".

aa...aa: Old URL

bb...bb: New URL


The specified URL before the change is invalid. URL = "aa...aa"

aa...aa: URL


The specified URL after the change is invalid. URL = "aa...aa"

aa...aa: URL


An attempt to connect to the database has failed.





The hcmdschgurl command successfully ended.

The hcmdschgurl command abnormally ended.


An attempt to back up the database has succeeded.



An attempt to restore the database has succeeded.



The URL was changed from "aa...aa" to

"bb...bb".

The specified URL before the change is invalid.

Confirm that the URL is valid.

The specified URL after the change is invalid.


An attempt to connect to the database has failed.

Confirm that the InterBase or the

InterClient service is running.


Confirm that the option is valid.



8-153


KAPM06116-E

KAPM06117-E

CIMException occurred. Description =

"aa...aa"







KAPM06118-E The BaseURL column does not exist in the class. class name = "aa...aa"



KAPM06119-W

The specified URL does not exist in the class. URL = "aa...aa"

aa...aa: URL


KAPM06120-I The URL is not registered.


KAPM06121-E IllegalDataException occurred.


aa...aa: Details


KAPM06122-W The specified URL before the change and after the change are same.


KAPM06123-W The program product specified by the type option is invalid.


KAPM06130-I

KAPM06131-I

The hcmdsinitsetup command has started.


The hcmdsinitsetup command was successful.


KAPM06132-E The hcmdsinitsetup command has failed.


CIMException occurred.




The BaseURL column does not exist in the class.


The specified URL does not exist in the class.


The URL is not registered.

IllegalDataException occurred.


The specified URL before the change and after the change are same.


The value specified for the type option is invalid.


The hcmdsinitsetup command has started.

The hcmdsinitsetup command was successful.

The hcmdsinitsetup command has failed.



Error Code

KAPM06138-E

KAPM06139-E

KAPM06140-E

KAPM06141-E

KAPM06142-E

KAPM06143-E

KAPM06144-E

KAPM06146-E

KAPM06147-E

KAPM06149-E

KAPM06153-E

KAPM06154-E

KAPM06159-E


A required database path is missing.


An error occurred during a parameter check.


Memory is insufficient.


The HiRDB environment already exists.


Free disk space is insufficient.


An error occurred in the system definition entry file.


The port is already being used.


A required database path is missing.



Check the memory capacity for the operation environment. If necessary, increase the memory.

The HiRDB environment already exists.



Check the disk capacity for the operation environment. If necessary, free some disk area.





Other errors.


An attempt to create the file has failed.


An attempt to create the file has failed.


An attempt to write to the file has failed.


An attempt to delete the file has failed.


An attempt to execute the command has failed.




An attempt to acquire a cluster configuration file has failed.







An attempt to acquire a cluster configuration file has failed.

Check the cluster configuration file.



8-155

8-156

Error Code

KAPM06160-E

KAPM06161-E

KAPM06162-E

KAPM06163-E

KAPM06164-E

KAPM06165-E

KAPM06166-E

KAPM06169-E

KAPM06170-I

Error Message

The value of hcmds.home cannot be acquired.


The cluster configuration file was not found.


An attempt to acquire the key name has failed.


An attempt to acquire a value has failed.





(file = "aa...aa")



An attempt to register the authentication data has failed.


An attempt to log in as an internal user has failed.


The hcmdsdbstatus started.

command has




The cluster configuration file was not found.









See the next message.

An attempt to register the authentication data has failed.

If this message is displayed following the

KAPM06111-I message when the hcmdschgurl

command is executed, information was successfully registered into the local repository of the distributed environment, but the registered information in the remote machine has not been applied.

To apply the registered information in the remote machine, either start or restart the Single Sign On Server for the remote machine.

If you cannot resolve the problem even by doing this, check the network connection and settings.

If you still cannot resolve the problem, acquire the maintenance information, and then contact the Support Center.

An attempt to log in as an internal user has failed.

See the next message.

The


hcmdsdbstatus started.

command has



Error Code

KAPM06171-I

KAPM06172-I

KAPM06173-E

KAPM06176-I

KAPM06177-I

KAPM06178-I

KAPM06179-E

KAPM06180-E

KAPM06181-E

KAPM06182-E

KAPM06183-I

KAPM06184-E

KAPM06185-E


The hcmdsdbstatus ended.

command has


The hcmdsdbstatus successful.

command was


The hcmdsdbstatus

command has failed.


The DBMS is running.


The DBMS is now starting or shutting down.


The DBMS service has stopped.


The DBMS restart was interrupted.


The DBMS service has stopped or does not exist.


The database has not been set up.




Command execution results: "aa...aa"

aa...aa: Displayed output of the executed command






The hcmdsdbstatus terminated.

command has

The hcmdsdbstatus successful.

command was

The hcmdsdbstatus

command has failed.


The DBMS is running.

The DBMS is now starting or shutting down.

The DBMS stopped.

The restart of the DBMS was interrupted.


The DBMS service has stopped or does not exist.


The database has not been set up.




Execution result of command.

The execution of the command failed.






8-157

Error Code

KAPM06186-E

Error Message

The value of acquired. hcmds.home

could not be


KAPM06187-E

KAPM06203-E

KAPM06206-E

KAPM06207-E

An attempt to judge the DBMS status has failed.


The list of table name is empty.



InterBase processing.


The list of table names is empty.


KAPM06214-E

KAPM06215-E

KAPM06216-E

KAPM06217-E

KAPM06218-E

KAPM06219-E



InterBaseServer is not running.


InterServer is not running.


An argument contains a null value.




The specified directory cannot be created. (directory = aa...aa).



The specified directory name already exists as a file. (file = aa...aa)





cannot be


An attempt to judge the DBMS status has failed.


The list of table name is empty.



InterBase processing.


The list of table names is empty.


A table aa...aa has been created.

InterBaseServer is not running.

Make sure that InterBaseServer is running.

InterServer is not running.

Make sure that InterServer is running.







The specified directory name already exists as a file.




Error Code

KAPM06220-E

KAPM06221-E

KAPM06222-E

KAPM06223-E

KAPM06224-E

KAPM06226-E

KAPM06227-I

KAPM06228-E

KAPM06229-E

KAPM06230-E


The specified file name already exists as a directory. (directory = aa...aa )



The specified database file (aa...aa ) does not exist.

aa...aa: Database file name


The specified XML file (aa...aa) does not exist.

aa...aa: XML file name



aa...aa)

aa...aa: Value




The specified file (aa...aa) does not exist in the argument of the pdload command.

aa...aa: Name of non-existent file


The processing on table aa...aa finished successfully.



The CSV file (aa...aa) contains an invalid line.



An attempt to read the data from table




An unexpected return value (aa...aa) was returned from the pdload command.

aa...aa: Unexpected return value


The specified file name already exists as a directory.


The specified database file (aa...aa ) does not exist.


The specified XML file (aa...aa) does not exist.






The specified file (aa...aa) does not exist in the argument of the pdload command.


The processing on table aa...aa finished successfully.

The CSV file (aa...aa) contains an invalid line.


An attempt to read the data from table



An unexpected return value (aa...aa) was returned from the pdload command.




8-159

Error Code

KAPM06231-E

KAPM06232-E

KAPM06234-E

KAPM06235-E

KAPM06239-E

KAPM06241-E

KAPM06242-E

KAPM06243-E

KAPM06244-E

KAPM06245-E

Error Message

An attempt to upgrade InterBase has failed.




A table name in XML is null or 0 bytes.


An unexpected XML tag (aa...aa) has been detected.

aa...aa: Unexpected XML tag


An error occurred during SAX processing.


A fatal error occurred during SAX processing.


An unexpected data length (aa...aa) was detected.

aa...aa: Unexpected value


A SAXException occurred. (details =

aa...aa)

aa...aa: SAXException detailed information


The length of the data to be moved to

HiRDB exceeds the HiRDB limit. (data type of excessively long data, length) =

(aa...aa, bb...bb)

aa...aa: Data type of the excessively long data

bb...bb: Length of the excessively long data





An attempt to upgrade InterBase has failed.




A table name in XML is null or 0 bytes.


An unexpected XML tag (aa...aa) has been detected.


An error occurred during SAX processing.


A fatal error occurred during SAX processing.


An unexpected data length (aa...aa) was detected.


A SAXException occurred.


The length of the data to be moved to

HiRDB exceeds the HiRDB limit.



Please start HiRDB.



Error Code

KAPM06246-I

KAPM06248-I

KAPM06249-E

KAPM06250-I

KAPM06251-E

KAPM06252-E

KAPM06255-I

KAPM06256-E

Error Message

The table aa...aa was successfully created.




Table aa...aa was successfully created.







The data was registered successfully in table aa...aa.



The data was not registered in table

aa...aa.



Authentication has failed at aa...aa.

aa...aa: Database name


Table aa...aa was not created.





The data was registered successfully in table aa...aa.

The data was not registered in table

aa...aa.


Authentication has failed at aa...aa.




Processing to initialize database conversion is being performed.


The specified file could not be created.

(file = aa...aa)



Databases of application aa...aa are not supported.


Processing to initialize database conversion is being performed.

The specified file could not be created.




8-161


KAPM06257-I

Data is now being read from the old database. (progress = aa...aa/bb...bb)

aa...aa: Number of converted tables

bb...bb: Total number of tables to be converted


KAPM06258-I




KAPM06262-I

The database is now being converted.

(progress = aa...aa/bb...bb)

aa...aa: Number of converted tables

bb...bb: Total number of tables to be converted


The hcmdssslsetup started.

command has


KAPM06263-I

KAPM06264-I

KAPM06266-E

KAPM06267-E

The hcmdssslsetup ended.

command has


The hcmdssslsetup successfully.

command ended




The sslc.cnf file was not found.







This message is output when the hcmdssslsetup

command starts.


command ends.


command ends successfully.

This message is output when an option specified for a command is invalid.

Specify valid options.

This message is output when the sslc.cnf file does not exist at the storage location.

If the file option has been specified, confirm that the sslc.cnf file has been specified in the path for the argument.

If the file option has not been specified, collect the maintenance information, and then contact the Support Center.



Error Code

KAPM06268-E

KAPM06269-E

KAPM06270-I

KAPM06271-I

KAPM06272-E

KAPM06273-I

KAPM06274-I

KAPM06275-E

KAPM06276-I

KAPM06277-I

KAPM06278-E

Error Message

The sslc.cnf file is invalid.


Execution of the sslc command failed.



This message is output when the format of the sslc.cnf file is invalid.

Make sure that the sslc.cnf can be accessed, or that the user who executed the command has the appropriate privileges, and then execute the command again.

If there is still a problem, collect the maintenance information, and then contact the Support Center.

This message is output when execution of the sslc command fails.


This message is output when processing to create a private key starts.

Processing to create a private key has started.


Processing to create a private key has ended.


Processing to create a private key failed.


This message is output when processing to create a private key ends.

This message is output when processing to create a private key fails.


This message is output when processing to create a self-signed certificate starts.

Processing to create a self-signed certificate has started.


Processing to create a self-signed certificate has ended.


Processing to create a self-signed certificate failed.


Processing to create a self-signed certificate in DER format has started.


Processing to create a self-signed certificate in DER format has ended.


Processing to create a self-signed certificate in DER format failed.


This message is output when processing to create a self-signed certificate ends.

This message is output when processing to create a self-signed certificate fails.


This message is output when processing to create a self-signed certificate in DER format starts.

This message is output when processing to create a self-signed certificate in DER format ends.

This message is output when processing to create a self-signed certificate in DER format fails.




8-163

Error Code

KAPM06280-E

KAPM06281-I

KAPM06282-I

KAPM06283-E

KAPM06284-E

KAPM06285-E

KAPM06286-E

KAPM06287-E

KAPM06288-E

KAPM06289-E

KAPM06290-E

Error Message




This message is output when an internal error occurs.


Processing to create a certificate content file started.

Processing to create a certificate content file started.


Processing to create a certificate content file ended.


Processing to create a certificate content file has failed.


The sslc

command was not found.


File deletion has failed.


The private key was not found.


The self-signed certificate was not found.


The DER format self-signed certificate was not found.


The certificate contents file was not found.




Processing to create a certificate content file ended.

Processing to create a certificate content file has failed.


The sslc

command was not found.


Deletion of a private key, self-signed certificate, DER format self-signed certificate, or certificate content file created by the has failed. hcmdssslsetup

command


The private key was not found in the storage destination after it was created.


The self-signed certificate was not found in the storage destination after it was created.


The DER format self-signed certificate was not found in the storage destination after it was created.


After the certificate contents file had been created, it was not found in the storage destination.






Error Code

KAPM06303-E

KAPM06304-E

KAPM06305-E

KAPM06306-E

KAPM06307-E

KAPM06308-E

KAPM06309-E

KAPM06310-E

KAPM06311-E

KAPM06312-E

KAPM06313-E

KAPM06317-E

Error Message







Specify all the necessary options.




















The specified value is invalid. value =

aa...aa

aa...aa: Value





Specify the option and specify the necessary proceeding values. (user name and password, etc.)


Do not specify an unsupported option.


Check the specification of the option.










Correct the syntax error in the specified definition file.









8-165

Error Code

KAPM06318-E

KAPM06319-I

KAPM06321-E

KAPM06322-E

KAPM06323-I

KAPM06324-E

KAPM06325-I

KAPM06326-E

KAPM06327-I

KAPM06328-E

KAPM06330-I

KAPM06331-I

Error Message





The "bb...bb" file to be used by "aa...aa" does not exist.

aa...aa: Command name, class name, etc.

bb...bb: Name of the file that does not exist




Execution of the "aa...aa" command ended normally.



An attempt to execute the "aa...aa" command has failed.



HiRDB was started.


HiRDB was not started.


HiRDB was stopped.


HiRDB was not stopped.


aa...aa processing started.

aa...aa: Method name


aa...aa processing finished.

aa...aa: Method name






The bb...bb file to be used by aa...aa does not exist.

Check whether the file is in the specified location.






HiRDB was started.

HiRDB was not started.


HiRDB was stopped.

HiRDB was not stopped.


aa...aa processing started.

aa...aa processing finished.



Error Code

KAPM06332-E

KAPM06333-E

KAPM06334-E

Error Message

The database of the specified product has not been set up.


HiRDB cannot be stopped because a

Suite product is connected to HiRDB.


InterBase is not running.


KAPM06335-E The DBMS has not started.


KAPM06337-E

KAPM06338-E

KAPM06339-E

KAPM06340-E

KAPM06341-E

KAPM06342-E


Authentication has failed in the DBMS.








The DBMS environment already exists.




KAPM06343-E

KAPM06344-E







Use the hcmdsdbsetup command to set up the database of the specified product.



Stop the Suite product that is connected to HiRDB, then retry.

InterBase is not running.

Check whether InterBaseServer is running. For details, check hcmdsdbconvert[n].log.

The DBMS has not started.

Check whether DBMS is running. For details, check hcmdsdbconvert[n].log.

Authentication has failed at InterBase.

Specify the correct user ID and password. For details, check hcmdsdbconvert[n].log.

Authentication has failed in the DBMS.

Specify the correct user ID and password. For details, check hcmdsdbconvert[n].log.


Check hcmdsdbconvert[n].log.


Check hcmdsdbconvert[n].log.


Check hcmdsdbinitsetup[n].log.

The DBMS environment already exists.



Check the operating environment for the disk capacity. If necessary, free up some disk space. For details, check hcmdsdbinitsetup[n].log.







8-167

8-168

Error Code

KAPM06345-E

KAPM06346-E

Error Message



The file "aa...aa" already exists.



KAPM06347-W The specified file system area "aa...aa" already existed, so it was deleted.

aa...aa: File system area


KAPM06348-I

KAPM06349-E

The database was created successfully.


An attempt to create the database has failed.


KAPM06350-I

KAPM06351-E

KAPM06352-E

The database was deleted successfully.


An attempt to delete the database has failed.


Directory creation has failed. (directory

= aa...aa)

aa...aa: directory name


KAPM06353-I Set up the database again.


KAPM06396-E "aa...aa":"bb...bb"


bb...bb: Message


KAPM06398-E "aa...aa"

aa...aa: Message






If the target file is hcmdsdbsetRDArea.ini, a database might already exist at the specified database creation destination.

If such a database exists, change the database creation destination, and then perform setup again.

If such a database does not exist, delete the file indicated by aa...aa, and then perform setup again.

The specified file system area aa...aa already existed, so it was deleted.

The database was created successfully.

An attempt to create the database has failed.

The database was deleted successfully.

An attempt to delete the database has failed.

Directory creation has failed.

Check the destination where the database will be created. If necessary, revise the destination and set up the database again. If you cannot resolve the problem, collect maintenance information, and then contact the

Support Center.

Set up the database again.





Error Code

KAPM06399-E

KAPM06403-E

KAPM06404-E

KAPM06405-I

KAPM06407-E

KAPM06408-I

KAPM06409-E

KAPM06410-I

KAPM06411-I

KAPM06412-I

KAPM06413-I

KAPM06414-E

Error Message

















The "bb...bb" file to be used by "aa...aa" does not exist.

aa...aa: Command name, class name, etc.

bb...bb: Name of the file that does not exist


Execution of the "aa...aa" command ended normally.






The setup status is "not set up".


The setup status is "stand-alone".


The setup status is "active system".


The setup status is "standby system".


The option specification is incorrect.



The bb...bb file to be used by aa...aa does not exist.




The setup status is "not set up".

The setup status is "stand-alone".

The setup status is "active system".

The setup status is "standby system".

The option specification is incorrect.

Review and, if necessary, revise the option specification.



8-169

Error Code

KAPM06429-E

KAPM06433-E

KAPM06434-I

KAPM06436-E

KAPM06437-E

KAPM06438-I

KAPM06439-I

KAPM06440-I

KAPM06441-I

KAPM06442-E

KAPM06443-E

KAPM06444-E

Error Message










Processing ended normally. Processing ended normally.







The HiRDB service has started.


The HiRDB service has stopped.


The HiRDB service has already started.


The HiRDB service has already stopped.


The HiRDB service has not been set up.


An attempt to start the HiRDB service has failed.


An attempt to stop the HiRDB service has failed.


An attempt to execute the aa...aa command has failed.


Please review the specification of the option.

The HiRDB service has started.

The HiRDB service has stopped.

The HiRDB service has already started.

It is already stopped by HiRDB service.

The HiRDB service has not been set up.

Make sure that the products have been properly installed, and if necessary, take actions to satisfy this condition. If an error still occurs after taking the above actions, collect maintenance information, and then contact Customer Support.

An attempt to start the HiRDB service has failed.


An attempt to stop the HiRDB service has failed.




Error Code

KAPM06445-E

KAPM06459-E

KAPM06501-I

KAPM06502-I

KAPM06503-E

KAPM06504-E

KAPM06505-E

KAPM06506-E

KAPM06507-E

KAPM06508-E

Error Message








Hitachi Storage Command Suite product is connected to HiRDB.

Stop any Hitachi Storage Command Suite products that are connected to HiRDB, and then retry the operation.

If you cannot resolve the problem even by doing this, acquire the maintenance information, and then contact the

Support Center.



The method has started.



The method has started.


The method has finished.




A specified option is insufficient.


The value specified in the option is invalid. (option = aa...aa)



The specified directory cannot be created. (directory = aa...aa)

aa...aa: Directory


The specified directory already exists as a file. (file = aa...aa)




aa...aa)

aa...aa: Specified value


The method has finished.



A specified option is insufficient.


The value specified in the option is invalid.

Check the specified value of the option.


Make sure that you have write permission for the directory.

The specified directory already exists as a file.

Specify another directory name.





8-171

8-172








Make sure that the file specification is correct. If you cannot solve the problem, collect maintenance information and contact the Support Center.

The directory aa...aa does not exist.



Delete the file, or move to another directory.

KAPM06511-E The aa...aa already exists.



KAPM06513-E

KAPM06514-I

KAPM06515-E

KAPM06516-E

KAPM06517-E

KAPM06518-E



Command aa...aa returned the value

bb...bb. The error message is cc...cc.


bb...bb: Return code

cc...cc: Error message




An IOException occurred. (details =

aa...aa)



An exception occurred. (details =

aa...aa)



A NullPointerException occurred. (details

= aa...aa)





The directory aa...aa already exists.

Specify another directory.

Command aa...aa returned the value

bb...bb. The error message is cc...cc.

Check the specified value of the option. If you cannot solve the problem, collect maintenance information and contact the

Support Center.






A NullPointerException occurred.



Make sure that HiRDB is installed. When a product of HiCommand 4.0 or later is installed, HiRDB is automatically installed.



Error Code

KAPM06519-E

KAPM06520-E

KAPM06521-E

KAPM06522-E

KAPM06523-I

KAPM06524-I

KAPM06525-I

KAPM06526-I

KAPM06527-I

KAPM06528-I

KAPM06529-I

KAPM06530-I

KAPM06531-I

Error Message

An error occurred while executing the hcmdsdbmode command.




The RD area for aa...aa has not been set up.





The hcmdsdbmove command has started.


Initialization for moving the database is being performed.


The data for aa...aa will now be moved.





The table definitions of the database are being imported.


The data is being imported.


The database procedures are being imported.







An error occurred while executing the hcmdsdbmode command.



Start HiRDB.

The RD area for aa...aa has not been set up.

In the type option, specify the installed product name.


Make sure that the Hitachi Storage

Command Suite products has been installed.

The hcmdsdbmove command has started.

Initialization for moving the database is being performed.

The data for aa...aa will now be moved.


The table definitions of the database are being imported.


The database procedures are being imported.





8-173

Error Code

KAPM06532-I

KAPM06533-I

KAPM06534-I

KAPM06535-I

KAPM06536-I

KAPM06537-I

KAPM06540-I

KAPM06541-I

KAPM06542-E

KAPM06543-I

Error Message

The table definitions of the database are being exported.


The data is being exported.


The database procedures are being exported.




The data is being imported. (progress =

aa...aa/bb...bb)

aa...aa: Amount of imported data

bb...bb: Total amount of data to be imported


The data is being exported. (progress =

aa...aa/bb...bb)

aa...aa: Amount of exported data

bb...bb: Total amount of data to be exported


The view is being imported.


The view is being exported.


The data to be imported to aa...aa is not in the directory in the datapath option.

aa...aa: The product for which the data to be imported cannot be found.


The database was exported successfully.



The table definitions of the database are being exported.


The database procedures are being exported.




The view is being imported.

The view is being exported.

When the import option was specified in the hcmdsdbmove command, the data to be imported from the product displayed in the message was not in the directory specified by the datapath option.

Please check that the data to be imported exists in the directory specified by the datapath option.

Also, if import data of multiple products exists in different directories, specify the type option, and then import the data for each product one product at a time.

The database was exported successfully.



Error Code

KAPM06544-E

KAPM06545-I

KAPM06546-E

KAPM06570-E

KAPM06571-E

KAPM06572-E

KAPM06573-E

KAPM06574-E

KAPM06575-E

KAPM06576-E

KAPM06577-E

Error Message

An attempt to export the database has failed.


The database was imported successfully.


An attempt to import the database has failed.




The specified options are insufficient.


The specified option value is invalid.


The specified directory name already exists as a file name. (file name =

aa...aa)



The directory name exceeds aa...aa characters.

aa...aa: Length of directory name

(number of characters)


The same value cannot be specified for the databasepath and exportpath parameters.



An attempt to export the database has failed.

The database was imported successfully.

An attempt to import the database has failed.

This message is displayed when the format of the specified option is invalid.

Specify a valid option, then retry.

This message is displayed when a required option is not specified or an unnecessary option is specified.

Specify a valid option, then retry.

This message is displayed when the specified value of the option is invalid.

Specify a valid option value, then retry.

This message is displayed when the directory name specified in the command option already exists as a file.


This message is displayed when the length (number of characters) of the directory name specified in the option exceeds the maximum.






This message is displayed when the character strings specified for the databasepath and exportpath parameters are the same.

Specify a different directory name, then retry.

This message is displayed when a required property has not been set in the cluster settings file.

Make sure the contents of the cluster settings file are correct.

This message is displayed when a value has not been set correctly in the cluster settings file.

Make sure the values in the cluster settings file are correct.



8-175

Error Code

KAPM06578-E

KAPM06579-E

KAPM06580-E

KAPM06581-E

KAPM06582-E

KAPM06583-E

KAPM06584-I

KAPM06585-I

KAPM06586-I

KAPM06587-E

Error Message

The cluster settings file was not found.




An attempt to clear a DBMS environment variable has failed.


The DBMS has not stopped.



This message is displayed when there is no cluster settings file in the conf directory.

Make sure that cluster.conf is in the conf directory.

This message is displayed when hcmds.home has not been set in the system properties.

Make sure that hcmds.home has been set in the system properties.

This message is displayed when an attempt to delete the DBMS client environment variable has failed.


This message is displayed when the

DBMS did not stop when the command was executed.

Before executing a command, stop the

DBMS service.

This message is displayed when an attempt to load the file has failed.



(file = aa...aa)




(file = aa...aa)



Processing to export data was successful.


Re-creation of the database was successful.


Processing to import data was successful.


An attempt to export data has failed.


This message is displayed when an attempt to write to the file has failed.


This message is displayed when data was exported successfully.

This message is displayed when the database was re-created successfully.

This message is displayed when data was imported successfully.

This message is displayed when an attempt to export data has failed.

Remove the cause of the failure, then retry. If the problem still cannot be solved, collect the maintenance information, and contact the Support

Center.



Error Code

KAPM06588-E

KAPM06589-E

KAPM06590-I

KAPM06591-E

KAPM06592-E

KAPM06601-I

KAPM06602-E

Error Message

An attempt to re-create the database has failed.


An attempt to import data has failed.



This message is displayed when an attempt to re-create the database has failed.


Center.

This message is displayed when an attempt to import data has failed.


Center.

This message is displayed when command execution ended normally.



The data to be imported was not found in the specified directory.


The data to be imported to aa...aa is not in the directory specified in the exportpath option.

aa...aa: The product that the import data could not be found.


This message is displayed when the data to be imported could not be found in the specified directory.

Specify the directory to which the data was exported, then retry. If the problem still cannot be solved, collect the maintenance information, and contact the Support Center.

The data to be imported of the product displayed in the message is not in the directory specified for the exportpath option.

Please confirm to exist an import data in the directory specified by the exportpath option.

Entered parameter.

aa...aa: Parameter entered by the user


User ID = aa...aa, application = bb...bb, permissions = cc...cc

aa...aa: User ID of the target user

bb...bb: Target application

cc...cc: Permission set by the target user


A specified parameter is invalid.


User ID = aa...aa, application = bb...bb, permissions = cc...cc

A specified parameter is invalid.

Check the specified parameter.



8-177

Error Code

KAPM06603-E

KAPM06604-E

Error Message


(file = aa...aa)

aa...aa: Absolute path of the file


The database has not started.


An attempt to communicate with the server or database has failed.




Make sure the file exists on the specified path aa...aa.

The database has not started.

Make sure the database has started.

KAPM06605-E

KAPM06606-E

KAPM06609-I

KAPM06610-E

KAPM06611-E

An error has occurred.


The command ended normally.


An option specification is invalid.


An attempt to load the hsso.conf file has failed.



KAPM06613-W Authentication data was not found in the repository.


An attempt to communicate with the server or database has failed.

Make sure the following have started: the

HBase Storage Mgmt Common Service or

HBase Storage Mgmt Web Service, and the database.

An error has occurred.


The command ended normally.

An option specification is invalid.

Specify a valid option as shown in the message, and then execute the command.

An attempt to load the hsso.conf file has failed.

Make sure the host name in hsso.conf is correct.


Make sure that the user name and password are correct.

If this does not resolve the problem, acquire the maintenance information, and then contact the Support Center.

Authentication data was not found in the repository.



Error Code

KAPM06614-E

KAPM06640-E

KAPM06641-E

KAPM06642-E

KAPM06643-E

KAPM06659-E

KAPM06665-I

KAPM06666-I

Error Message

An attempt to communicate with SSO

Server has failed.






An error occurred during file input.


An attempt to acquire file information has failed.


aa...aa



The DBMS has started.


The DBMS has stopped.



An attempt to communicate with SSO

Server has failed.

For a distributed environment:

5. If you executed the command from the primary side:

Make sure that the Single Sign-On server on the primary side is running.

6. If you executed the command from the secondary side:

Make sure that the Single Sign-On server on the primary side is running.

If the Single Sign-On server on the primary side is not running, start it, and restart the Single Sign-On server on the secondary side.

If the Single Sign-On server on the primary side is running, make sure that the Single Sign-On server on the secondary side is running.

For a non-distributed environment:

1. Make sure that the Single Sign-On server is running.

If you cannot solve the problem, collect the maintenance information, and then contact the Support Center.





An error occurred during file input.


An attempt to acquire file information has failed.





The DBMS has started.

The DBMS has stopped.



8-179


KAPM06667-I

KAPM06668-I

KAPM06669-E

KAPM06670-E

KAPM06671-E

KAPM06672-E

KAPM06673-E

aa...aa processing has started.

aa...aa: Processing name


aa...aa processing has finished.








aa...aa)

aa...aa: Value


Execution of the command aa...aa has failed.



The DBMS did not start.


KAPM06674-E

KAPM06675-I

KAPM06676-I

The DBMS did not stop.


The DBMS has not been set up




KAPM06679-E The value of hcmds.home cannot be acquired.


KAPM06683-E "aa...aa":"bb...bb"

aa...aa: command name

bb...bb: message



Processing has started.

Processing has finished.







Execution of the command has failed.


The DBMS did not start.


The DBMS did not stop.


The DBMS has not been set up




Message for debugging:




KAPM06689-E

KAPM06690-E

KAPM06691-E

Processing has terminated abnormally.

(processing name = aa...aa)



The file hcmdsdbsetRDArea.ini does not exist.




KAPM06692-W Execution of the command aa...aa has failed.



KAPM06753-E A property value in the installation information file is invalid. (aa...aa)

aa...aa: Property value


KAPM06760-I A method has started.


KAPM06761-I

KAPM06762-I

KAPM06763-I

KAPM06764-I

KAPM06765-E

KAPM06766-E

A method has finished.


The hcmdsssltool command has started.


The hcmdsssltool command has ended.


The hcmdsssltool command ended successfully.




Creation of a private key failed.



Processing has terminated abnormally.

(processing name = aa...aa)


The file hcmdsdbsetRDArea.ini does not exist.




Execution of the command has failed.


A property value in the installation information file is invalid.

Check the contents of the installation information file.

A method has started.

A method has finished.

The

The

The hcmdsssltool command

has started. hcmdsssltool command

has ended. hcmdsssltool command successfully.


Check the options.

ended

Creation of a private key failed.

Check the file output location and the specified distinguished name, and then re-execute the command.

If this does not resolve the problem, collect maintenance information, and then contact the Support Center.



8-181

Error Code

KAPM06767-E

KAPM06768-E

KAPM06769-E

Error Message

Creation of a self-signed certificate failed.


Creation of a CSR failed.


Creation of a certificate content file failed.



Creation of a self-signed certificate failed.



Creation of a CSR failed.



Creation of a certificate content file failed.





Failed to delete a key store.

KAPM06770-E An internal error occurred.


KAPM06771-W Failed to delete a key store.


KAPM06772-E

KAPM06773-E

KAPM06774-E

KAPM06775-E

No value has been specified for an option.






Analysis of binary data failed.(position =

aa...aa,part = bb...bb)

aa...aa: Position

bb...bb: Part



Check the options.





Analysis of binary data failed.




Error Code

KAPM06776-E

KAPM06777-I

KAPM06780-I

KAPM06782-I

KAPM06783-I

KAPM06784-I

KAPM06785-I

KAPM06787-E

KAPM06790-E

KAPM06791-E

KAPM06792-E

KAPM06793-E

Error Message

The keytool command failed.



The keytool command failed.

Take action according to the content of the following messages:



KAPM06766-E







KAPM06767-E

KAPM06768-E

KAPM06769-E

The keytool command has ended. The keytool command has ended.(Return code = aa...aa)

aa...aa: Return code


Enter Server Name [default=aa...aa]:

aa...aa: Host name


Enter Server Name.

Enter Organizational Unit.


Enter Organization Name

[default=aa...aa]:



Enter your City or Locality:


Enter your State or Province:


Enter your two-character country-code:


Enter Organization Name.

Enter your City or Locality:

Enter your State or Province.

Enter your two-character country-code.

The Distinguished Name is confirmed.



Creation of a distinguished name failed.


An IllegalArgumentException occurred.




A HBaseDeleteFileException occurred.




Creation of a distinguished name failed.


An IllegalArgumentException occurred.




A HBaseDeleteFileException occurred.






8-183

Error Code

KAPM06794-E

KAPM06795-E

KAPM06796-E

Error Message

A KeyStoreException occurred.


A CertificateException occurred.


An UnrecoverableKeyException occurred.


KAPM06799-I aa...aa aa...aa: Debug information


KAPM06900-I


KAPM06901-I

Processing to start the service has started.


The service was started successfully.



A KeyStoreException occurred.


A CertificateException occurred.


An UnrecoverableKeyException occurred.


A NoSuchAlgorithmException occurred.


This message contains debug information.

This message is displayed when processing to start the service starts.

KAPM06902-I

KAPM06903-I

KAPM06904-I

KAPM06905-I

KAPM06906-I

KAPM06907-I

Processing to stop the service has started.


The service was stopped successfully.


Processing to start the DBMS has started.


The DBMS was started successfully.


Processing to stop the DBMS has started.


The DBMS was stopped successfully.


This message is displayed when the service starts successfully. However, if the HiCommand version is earlier than

5.7, you might need to start some of the services manually because they do not start automatically.

This message is displayed when processing to stop the service starts.

This message is displayed when the service stops successfully.

This message is displayed when processing to start the DBMS starts.


DBMS starts successfully.

This message is displayed when processing to stop the DBMS starts.


DBMS stops successfully.



Error Code

KAPM06908-E

KAPM06909-E

KAPM06910-E

KAPM06911-E

KAPM06912-E

KAPM06913-E

KAPM06914-E

KAPM06915-E

Error Message



An attempt to stop the service has failed.


The database has not been initialized.


An attempt to release the connection of the connection pool has failed.


KAPM06920-W Log initialization failed.


KAPM06921-E

An attempt to start the DBMS has failed.


An attempt to stop the DBMS has failed.


An attempt to start the service or the

DBMS has failed.


An attempt to stop the service or the

DBMS has failed.





This message is displayed when an attempt to start the service fails.


This message is displayed when an attempt to stop the service fails.

Stop the Suite product that is connected to the DBMS, then retry. If the problem still cannot be resolved, collect the maintenance information, and contact the Support Center.

This message is displayed when an attempt to start the DBMS fails.


This message is displayed when an attempt to stop the DBMS fails.


This message is displayed when an attempt to start the service or the DBMS fails.


This message is displayed when an attempt to stop the service or the DBMS fails.


The database has not been initialized.


This message is displayed when an attempt to release the connection of the connection pool fails.



If the problem occurs frequently, collect maintenance information, and then contact the Support Center.





8-185


KAPM06922-E

KAPM06923-E

KAPM06924-E

KAPM06925-E

KAPM06926-E

KAPM06927-E

The aa...aa command will stop because setting an environment variable failed.

(details = bb...bb)


bb...bb: Details


The aa...aa command will stop because internal processing failed. (details =

bb...bb)


bb...bb: Details



(function = aa...aa, error code =

bb...bb)

aa...aa: Function



A system environment variable is invalid.


The aa...aa command will stop because setting an environment variable failed.

(details = bb...bb)


bb...bb: Details


The aa...aa command will stop because internal processing failed. (details =

bb...bb)


bb...bb: Details


KAPM07000-W Update the current JavaScript to the latest version.


KAPM07001-E The specified user cannot log in because the user does not have permission to access the manager screen.


The specified command stopped because setting an environment variable failed.

Re-execute the command. If the problem cannot be solved, collect maintenance information, and then contact the

Support Center.

The specified command stopped because internal processing failed.


Support Center.



A system environment variable was invalid.


The specified command stopped because setting an environment variable failed.


Support Center.

The specified command stopped because internal processing failed.


Support Center.

Update the current JavaScript to the latest version.

The specified user cannot log in because the user does not have permission to access the manager screen.

Log in as a user who has Hitachi Storage

Command Suite Common Component

Administrator permissions.



Error Code

KAPM07002-E

KAPM07003-E

KAPM07004-E

KAPM07005-E

KAPM07006-E

KAPM07007-E

KAPM07008-E

KAPM07009-E

KAPM07010-E

KAPM07011-E

KAPM07012-E

KAPM07013-E

KAPM07014-E

Error Message

The application is not registered on the

HSSO Server.


The user ID and/or password are not correct.


The executing user does not have permission to execute the method.


The specified user does not exist.




This user has already been deleted.


A problem occurred during processing.


A communication error occurred during processing.


Null is specified for the argument.




The specified group does not exist.


An attempt to register user information has failed, because a problem occurred during registration processing.


An attempt to update user information has failed, because a problem occurred during update processing.



The application is not registered on the

HSSO Server.


The user ID and/or password are not correct.

Input the correct user ID and password.

The executing user does not have permission to execute the method.


The specified user does not exist.

Confirm the user information.


Input a value other than the specified user name.

This user has already been deleted.

Confirm the user information.

A problem occurred during processing.


A communication error occurred during processing.






The specified group does not exist.

Confirm the group information.

An attempt to register user information has failed, because a problem occurred during registration processing.


An attempt to update user information has failed, because a problem occurred during update processing.




8-187

Error Code

KAPM07015-E

KAPM07016-E

KAPM07017-E

KAPM07018-E

KAPM07019-I

KAPM07021-E

KAPM07022-E

KAPM07023-I

KAPM07024-E

Error Message

An attempt to delete user information has failed, because a problem occurred during deletion processing.


An attempt to change the password has failed, because a problem occurred while processing the change.


A problem occurred during an attempt to acquire user information.


A problem occurred during an attempt to acquire group information.


The user information was successfully deleted.



An attempt to delete user information has failed, because a problem occurred during deletion processing.


An attempt to change the password has failed, because a problem occurred while processing the change.


A problem occurred during an attempt to acquire user information.


A problem occurred during an attempt to acquire group information.


The user information was successfully deleted.

User ID aa...aa will be deleted.

If deleted, this user will not be able to log on. Is this OK?

If deleted, this user will not be able to log on. Is this OK?

aa...aa: User ID


A problem occurred during an attempt to acquire HiCommand application information.


An attempt to update HiCommand application information has failed, because a problem occurred during update processing.


HiCommand application information will now be updated.


A problem occurred during an attempt to acquire user application information.


A problem occurred during an attempt to acquire Hitachi Storage Command Suite application information.


An attempt to update Hitachi Storage

Command Suite application information has failed, because a problem occurred during update processing.


Hitachi Storage Command Suite application information will now be updated.

A problem occurred during an attempt to acquire user application information.





KAPM07025-E

KAPM07026-I

An attempt to update user application information has failed, because a problem occurred during update processing.


User application information will now be updated.


KAPM07027-W The specified user application name already exists. application name =

aa...aa




An attempt to update user application information has failed, because a problem occurred during update processing.


User application information will now be updated.

The specified user application name already exists.

Input a value other than the specified application name.

This entry is required. Enter a value.

Input a value. This entry is required. Enter a value.

aa...aa: Input item


A character that cannot be used for this entry has been entered.



A character that cannot be used for this entry has been entered.

Use only characters that are valid for this item.

KAPM07031-E

The number of characters in this entry exceeds the maximum.



The password entries do not match.


The number of characters in this entry exceeds the maximum.

Input a character string of a length less than or equal to the maximum.

Enter from 4 to 255 characters for this entry.



KAPM07033-W The specified URL does not exist in the class. URL = aa...aa

aa...aa: URL


The password entries do not match.

Make sure that the values for the password and password confirmation input items are identical.

Enter from 4 to 255 characters for this entry.

Input a character string of a length between 4 and 255 characters (inclusive) for this input item.

The specified URL does not exist in the class.




8-189

Error Code

KAPM07034-E

KAPM07035-E

KAPM07036-I

KAPM07037-I

KAPM07230-I

KAPM07231-I

KAPM07232-I


IllegalDataException occurred. (details =

aa...aa)

aa...aa: Details


The format of the specified URL is invalid. URL = aa...aa

aa...aa: URL


The password will change. Is this OK?



After the password changes, you must log in again.


IllegalDataException occurred.


The format of the specified URL is invalid.

Check the entered URL. If necessary, enter the correct URL.



After the password changes, you must log in again.

The same value cannot be specified into these input items.

Please reinput other values in an input item.

The same value cannot be specified into these input items.



The user was registered successfully.

(operator = aa...aa, user ID = bb...bb, function = cc...cc)

aa...aa: Operator name

bb...bb: Processed user ID

cc...cc: Function name


The user was deleted successfully.












This is an audit log showing that the user has been registered successfully.

This is an audit log showing that the user has been deleted successfully.

This is an audit log showing that the password has been changed successfully.



Error Code

KAPM07233-I

KAPM07235-I

KAPM07236-I

KAPM07237-E

KAPM07238-E

KAPM07239-E

Error Message

The user information was modified successfully. (operator = aa...aa, user

ID = bb...bb, function = cc...cc)





The user was locked successfully.






The user was unlocked successfully.






The specified password does not satisfy the entry conditions. (operator =

aa...aa, user ID = bb...bb, function =

cc...cc)





The specified e-mail is too long.






The old password is incorrect. (operator

= aa...aa, user ID = bb...bb, function =

cc...cc)






This is an audit log showing that the user information has been modified successfully.

This is an audit log showing that the user has been locked successfully.

This is an audit log showing that the user has been unlocked successfully.

This is an audit log that shows that the password that doesn't meet the input requirement is specified.

This is an audit log that shows that the e-mail string that is too long is specified.

This is an audit log that shows that the old password is incorrect.



8-191

Error Code

KAPM07240-E

KAPM07241-I

KAPM07242-E

KAPM07243-I

KAPM07244-E

KAPM07245-I

KAPM07246-E

KAPM07247-I

Error Message

An attempt to execute the aa...aa operation has failed. (operator =

bb...bb, user ID = cc...cc, function =

dd...dd)

aa...aa: Operation name

bb...bb: Operator name

cc...cc: Processed user ID

dd...dd: Function name


A user was registered successfully. (user

ID = aa...aa)

aa...aa: User ID


Registration of a user has failed. (user

ID = aa...aa)

aa...aa: User ID


The user information was updated successfully. (user ID = aa...aa)

aa...aa: User ID


An attempt to update the user information has failed. (user ID =

aa...aa)

aa...aa: User ID


A user was deleted successfully. (user

ID = aa...aa)

aa...aa: User ID


Deletion of a user has failed. (user ID =

aa...aa)

aa...aa: User ID


The authorization group was added successfully. (operator = aa...aa, distinguished name = bb...bb, function

= cc...cc)


bb...bb: Distinguished name




This is an audit log that shows that the

aa...aa process has failed.

This audit log data indicates that a user was registered successfully.

This audit log data indicates that registration of a user has failed.

This audit log data indicates that the user information was modified successfully.

This audit log data indicates that an attempt to update the user information has failed.

This audit log data indicates that a user was deleted successfully.

This audit log data indicates that deletion of a user has failed.

This is an audit log that shows all the authorization groups that have been added successfully.



Error Code

KAPM07248-E

KAPM07249-I

KAPM07250-I

KAPM07251-I

KAPM07252-E

KAPM07253-I

KAPM07254-E

Error Message

An attempt to execute the aa...aa operation has failed. (operator =

bb...bb, distinguished name = cc...cc, function = dd...dd)

aa...aa: Operation name

bb...bb: Operator name

cc...cc: Distinguished name

dd...dd: Function name


The authorization group was deleted successfully. (operator = aa...aa, distinguished name = bb...bb, function

= cc...cc)





The permissions were changed successfully. (operator = aa...aa, distinguished name = bb...bb, permissions = cc...cc)



cc...cc: Permissions after they were changed


The authorization group was registered successfully. (distinguished name =

aa...aa)



An attempt to register the authorization group has failed. (distinguished name =

aa...aa)



The authorization group was deleted successfully. (distinguished name =

aa...aa)



An attempt to delete the authorization group has failed. (distinguished name =

aa...aa)




This is an audit log that shows the failed aa...aa processes.

This is an audit log that shows all the authorization groups that have been deleted successfully.

This is an audit log that shows all the permissions that have been changed successfully.

This is an audit log that shows all the authorization groups that have been registered successfully.

This is an audit log that shows all the authorization groups that have failed to be registered.

This is an audit log that shows all the authorization groups that have been deleted successfully.

This is an audit log that shows all the authorization groups that have failed to be deleted.



8-193

Error Code

KAPM07255-I

KAPM07256-E

KAPM07300-I

KAPM07301-I

KAPM07302-I

KAPM07303-E

KAPM07306-E

KAPM07307-E

KAPM07308-E

KAPM07309-E

KAPM07310-I

KAPM07311-I

Error Message

The authorization group's permissions were changed successfully.

(distinguished name = aa...aa)



An attempt to change the authorization group's permissions has failed.




The hcmdshpsimcert started.

command has


The hcmdshpsimcert terminated.

command has


The hcmdshpsimcert successful.

command was


The hcmdshpsimcert failed.

command has



cannot be



This is an audit log that shows all the authorization group permissions that have been changed successfully.

This is an audit log that shows all the authorization group permissions that have failed to be changed.

The hcmdshpsimcert

command started.

The hcmdshpsimcert

command ended.

The hcmdshpsimcert successful.

command was

The hcmdshpsimcert

command failed.








Importing of the certificate has started.


Importing of the certificate has ended.


The hcmds.home

acquired.

value cannot be



Please revise the option specification.





Importing of the certificate started.

Importing of the certificate ended.




KAPM07312-E

KAPM07313-E

KAPM07314-E

KAPM07315-E

The host name or the port number is invalid.



HPSIM server has failed.


The format of the certificate acquired from the HPSIM server is invalid.


An attempt to load the keystore file has failed.


KAPM07316-W The certificate of the specified host is already registered.


KAPM07317-I

KAPM07318-E

The following certificate was imported into the keystore.


An attempt to output the keystore file has failed.


KAPM07319-E

KAPM07320-I

An attempt to input the keystore file has failed.


Host name: "aa...aa"



KAPM07321-I

KAPM07322-I

KAPM07323-I

Processing to display the certificate list has started.


Processing to display the certificate list has ended.


The certificate is not stored.




Please revise the specified host name.

Communication with the HPSIM server failed.

Please confirm whether the HPSIM server running.

The format of the certificate acquired from the HPSIM server is invalid.




The certificate of the specified host has already been registered.

The following certificate was imported to the keystore.



An attempt to input the keystore file has failed.


Host name

Processing to display the certificate list started.

Processing to display the certificate list ended.

The certificate is not stored.



8-195


KAPM07324-E

KAPM07325-I

KAPM07326-I

KAPM07346-I

A problem occurred while displaying the certificate list.


Deletion of the certificate has started.


The certificate has been deleted.


KAPM07327-I

KAPM07328-W The certificate for the aa...aa host is not registered.



KAPM07329-E

The certificate for the aa...aa host was deleted.



KAPM07330-E

An attempt to delete the certificate has failed.


An attempt to renew the keystore has failed.


KAPM07342-E An exception occurred.


KAPM07343-E

KAPM07344-I



GET processing for "

/Proxy/Getkey

" has started.


KAPM07345-I GET processing for " ended.

/Proxy/Getkey

" has


The request from "aa...aa" was accepted.




A problem occurred while displaying the certificate list.


Deletion of the certificate started.

The certificate has been deleted.

The certificate of the specified host was deleted.

The certificate of the specified host name is not registered.

An attempt to delete the certificate has failed.


An attempt to modify the keystore has failed.






The GET processing of " started.

/Proxy/GetKey

"

The GET processing of " ended.

/Proxy/GetKey

"

The request from aa...aa was accepted.




KAPM07347-I

KAPM07348-E

KAPM07349-E

The one-time key was issued. (key =

aa...aa)

aa...aa: Onetimekey


An attempt to issue the one-time key has failed.


An attempt to create the one-time key failed because the number of keys had exceeded the maximum.


KAPM07350-W

The one-time key does not exist. (key =

aa...aa)



KAPM07351-W The expiration date of the one-time key has passed. (key = aa...aa)



KAPM07352-I The one-time key was deleted normally.

(key = aa...aa)



KAPM07355-I

The one-time key that passed the expiration date was deleted. (key =

aa...aa)



KAPM07356-I

KAPM07357-I


/Proxy/SSO

" has started.



/Proxy/SSO

" has ended.


KAPM07358-E An error occurred during a parameter check.



The one-time key was issued. (key =

aa...aa)

An attempt to issue the one-time key has failed.


An attempt to create the one-time key failed because the number of keys exceeded the maximum.

Please check whether a one-time key has been generated illegally.

The one-time key does not exist. (key =

aa...aa)

The one-time key expired. (key =

aa...aa)

The one time key was deleted normally.

(key = aa...aa)

The expired one-time key was deleted.

(key = aa...aa)

The GET processing of " started.

/Proxy/SSO

"

The GET processing of " ended.

/Proxy/SSO

"





8-197


KAPM07359-I

KAPM07360-E

KAPM07363-I

KAPM07364-E

KAPM07367-I

The host name is valid.




The one-time key is valid.


KAPM07368-W The one-time key is invalid.


KAPM07371-I Verification of the request parameter was successful.


KAPM07372-E

KAPM07375-I

An attempt to verify the request parameter has failed.


The URL is a normal value.


KAPM07376-E

Parameter output: "aa...aa" = "bb...bb"

aa...aa: Parameter

bb...bb: Value


An attempt to load the keystore has failed.


KAPM07377-E

The URL is an invalid value.


An attempt to convert the aa...aa permission has failed.

aa...aa: Authority name



Parameter output: aa...aa = bb...bb

An attempt to load the keystore has failed.


The host name is valid.


Please make sure the certificate from the launch-source has been imported.

The one-time key is valid.

The one-time key is invalid.

Verification of the request parameter was successful.

Verification of the request parameter failed.


The URL value is normal.

The URL value is invalid.


An attempt to convert the aa...aa permission has failed.




Error Code

KAPM07378-I

KAPM07379-E

KAPM07380-I

KAPM07381-E

KAPM07382-E

KAPM07383-I

KAPM07384-I

KAPM07385-E

KAPM07386-E

KAPM07387-E

KAPM07388-E

KAPM07389-E

Error Message

A redirection to "aa...aa" will be performed.

aa...aa: redirect URL




The certificate of aa...aa has been imported.

aa...aa: Alias


The certificate of aa...aa has not been imported.

aa...aa: Alias


A server problem occurred.


Data verification has started.


Data verification has ended.


An invalid character string was specified for the token.


"SHA1with RSA" is not supported.


The certificate format is invalid.


The signature object has not been initialized.


"US-ASCII" is not supported.



The user will be redirected to aa...aa.



The aa...aa certificate has been imported.

The aa...aa certificate has not been imported.

Please confirm whether the certificate is importing done.

A problem with the server occurred.


Verification of the data started.

Verification of the data ended.

An invalid character string was specified for the token.


"SHA1withRSA" is not supported.


The format of the certificate is invalid.


The signature object has not been initialized.


"US-ASCII" is not supported.




8-199

8-200

Error Code

KAPM07390-I

KAPM07391-I

KAPM07392-E

KAPM07393-E

KAPM07400-E

KAPM07401-I

KAPM07402-I

KAPM07403-E

KAPM07404-E

KAPM07405-E

KAPM07406-E

KAPM07407-E

Error Message

Generation of the HSSO token has started.


Generation of the HSSO token has ended.


The permission conversion definition file was not found.


An attempt to load the permission conversion definition file has failed.


The definition file was not found.


Generation of the X509 certificate object has started.


Generation of the X509 certificate object has ended.









The format of the certificate acquired from HPSIM is invalid.





Generation of the HSSO token started.

Generation of the HSSO token ended.

The permission conversion definition file was not found.


An attempt to load the permission conversion definition file has failed.


The definition file was not found.


Generation of the X509 certificate object started.

Generation of the X509 certificate object ended.







Please confirm whether the HPSIM server running.

The format of the certificate acquired from HPSIM is invalid.




Authentication succeeded.




Error Code

KAPM07420-E

KAPM07421-E

KAPM07422-E

KAPM07423-E

KAPM07424-E

KAPM08001-E

KAPM08002-E

KAPM08003-E

KAPM08004-E

KAPM08005-E





(aa...aa)

aa...aa: Argument


A specified value is invalid. (aa...aa,

bb...bb)

aa...aa: Parameter

bb...bb: Value




The domain name is invalid.


The user name is invalid.








There is an unusable character in the domain name sent from HPSIM.

Please revise the HPSIM domain name.

There is an unusable character in the user name sent from HPSIM.

Please revise the HPSIM user name.














Please fix the cause of the error. For details on the cause, see the

HpsimSSO[n] log.














8-201

Error Code

KAPM08006-E

KAPM08007-E

KAPM08008-E

KAPM08009-I

KAPM08010-E

KAPM08011-E

KAPM08013-E

KAPM08015-E

KAPM08016-E

KAPM08017-E

KAPM08018-E

KAPM08019-E

KAPM08020-E

Error Message







The logout process has completed.




Your session is invalid.











The logout process has completed.



Your session is invalid.

Logout, then login.


Use a browser supported by the Hitachi

Storage Command Suite products being used.

Now loading.


The registered data in the common repository is invalid.(aa...aa)









An error occurred on the SSO Server.



SSO server has failed.









Logout, then login.

An error occurred on the SSO server.

Logout, then login.

An attempt to communicate with the SSO server has failed.

Logout, then login.



Error Code

KAPM08021-E

KAPM08022-E

KAPM08100-E

KAPM08101-E

KAPM08102-E

KAPM08103-E

KAPM08104-E

KAPM08105-E

KAPM08106-E

KAPM08107-E


The DBMS is stopped.


The Common Component database is blocked.




The specified node was not found. key=(aa...aa)

aa...aa: Node key


The object tree has not been created.


An attempt to create the object tree has failed.


An attempt to add a child node to the object tree has failed. (aa...aa)

aa...aa: Node key


The specified node has already been registered. key=(aa...aa)

aa...aa: Node key


The tree information cannot be acquired. (aa...aa)

aa...aa: Node key


The node information is invalid. (aa...aa,

bb...bb)


bb...bb: Acquired value


The DBMS is stopped.


The Common Component database is blocked.

Please contact the server administrator.



The specified node was not found.


The object tree has not been created.


An attempt to create the object tree has failed.


An attempt to add a child node to the object tree has failed.


The specified node has already been registered.


The tree information cannot be acquired.


The node information is invalid.




8-203


KAPM08108-E

KAPM08109-E

KAPM08110-E

KAPM08111-E

KAPM08112-E

An invalid argument was specified during node creation. (aa...aa, bb...bb)




The tree information is invalid. (aa...aa,

bb...bb)

aa...aa: Route-node key (database)

bb...bb: Route-node key (memory)


The node array cannot be acquired.

(aa...aa, bb...bb)




The hierarchy number of the node array cannot be acquired. (aa...aa, bb...bb)




The node array is invalid. (aa...aa,

bb...bb)




KAPM08113-E The hierarchy number of the node array is invalid. (aa...aa)

aa...aa: Hierarchy number of the node


KAPM08114-W An invalid argument was specified during node creation. (aa...aa, bb...bb)




KAPM08115-E An internal error occurred.



An invalid argument was specified during node creation.


The tree information is invalid.


The node array cannot be acquired.


The hierarchy number of the node array cannot be acquired.


The node array is invalid.


The hierarchy number of the node array is invalid.


An invalid argument was specified during node creation.






Error Code

KAPM08116-E

KAPM08150-E

KAPM08152-E

KAPM08154-E

KAPM08160-E

KAPM08200-E

KAPM08201-E

KAPM08202-E

KAPM08203-E


A value that exceeds the maximum value has been specified. (aa...aa,

bb...bb)




The request is invalid. (aa...aa, bb...bb)

aa...aa: Key

bb...bb: Value


The request is invalid. (aa...aa)

aa...aa: Key


An attempt to display the object tree has failed.


The data registered in the common repository is invalid. (aa...aa, bb...bb)

aa...aa: Key

bb...bb: Value


The request parameter required for the display of the Application Bar area is invalid.



If you click the "Refresh Tree" button, the initial object tree will be displayed. If you cannot display the tree, log out, and then log in again.


The number of elements in the array does not match the other arrays.


The request parameter required for the display of the Summary area is invalid.


A value that exceeds the maximum value has been specified.

Check and, if necessary, revise the settings.





An attempt to display the object tree has failed.


The data registered in the common repository is invalid.


The request parameter required for the display of the Application Bar Area is invalid.



If you click the "Refresh Tree" button, the initial object tree will be displayed. If you cannot display the tree, log out, and then log in again. If you cannot resolve this problem, collect maintenance information, and then contact the

Support Center.

The number of elements in the array does not match the other arrays.


The request parameter required for the display of the Summary area is invalid.




8-205

Error Code

KAPM08302-E

KAPM08303-E

KAPM08304-E

KAPM08308-E

KAPM08309-E

KAPM08311-E

KAPM08402-E

KAPM08403-E

Error Message

An error occurred while acquiring the resource bundle.


An error occurred while reading the resource file.


An attempt to access the resource file has failed.




The URL object cannot be created.


An attempt to access the file has failed.


An unusable HTML tag is included.


The warning banner message exceeded

1000 characters.



An error occurred while acquiring resource bundle.


An error occurred during resource file input.


An attempt to access the resource file has failed.




URL object was not able to be made.


An attempt to access the file has failed.


This message is displayed when the message entered by the user contains an unusable HTML tag.

Please enter supported HTML tags only.

This message is displayed when the warning banner message entered by the user exceeds 1000 characters.

Enter no more than 1000 characters.



Error Code

KAPM08404-E

Error Message

An attempt to register the warning banner message has failed.



This message is displayed when an attempt to register a warning banner message from the security GUI window fails.

Perform the following actions:

1. Check that the following folder exists:

Windows: Hitachi Storage Command

Suite Common Componentinstallation-

directory\Base\ conf\sec\resource

Solaris:

/opt/HiCommand/Base/conf/sec/resou rce

Linux: Hitachi Storage Command

Suite Common Componentinstallation-

directory/Base/conf/sec/resource

2. Please delete the following folder:


Suite Common Component- installation-folder

\ \Base conf\sec\resource\bannerresource.p

roperties

Solaris or Linux:

/opt/HiCommand/Base/conf/sec/resou rce/bannerresource.properties

3. Make sure you have access permissions for the following file.


Suite-Common-Componentinstallationfolder

\conf\sec\resource\bannerreso urce.properties

Solaris:


Linux: Hitachi-Storage-Command-

Suite-Common-Componentinstallationdirectory

/Base/conf/sec/resource/ba nnerresource.properties




8-207

Error Code

KAPM08405-E

KAPM08406-E

KAPM08407-E

KAPM08408-E

Error Message

An attempt to delete the warning banner message has failed.


The specified file name already exists as a directory name. (directory name =

aa...aa)



The specified directory name already exists as a file name. (file name =

aa...aa)



The directory does not exist. (directory name = aa...aa)




This message is displayed when an attempt to delete a warning banner message from the security GUI window fails.

Perform the following actions:

1. Check that the following file exists:


Suite Common Componentinstallationfolder

\Base\conf\sec\resource\banne rresource.properties

Solaris:


Linux: Hitachi Storage Command

Suite Common Componentinstallationdirectory

/Base/conf/sec/resource/ba nnerresource.properties


This message is output to the log when an attempt to register a warning banner message from the security GUI window fails.

The system environment is invalid.



The system environment is invalid.



Please create the following folder, then retry:


Suite Common Component-installationdirectory\Base\

conf\sec

Solaris:

/opt/HiCommand/Base/conf/sec

Linux: Hitachi Storage Command Suite

Common Component-installationdirectory/Base/conf/sec



Error Code

KAPM08409-E

KAPM08410-E

KAPM08411-E

KAPM08412-E

Error Message

An attempt to delete the warning banner message has failed.


The specified node is invalid. (node name = aa...aa)

aa...aa: Node name

Output destinations: Destinations for output level 10. hcmds.home

is not set in the Java system properties.


The bannertaglist.conf

exist.

file does not



This message is output to the log when an attempt to delete a warning banner message from the security GUI window fails.

Check that the following file exists:


Suite Common Component-installationdirectory\Base

\conf\sec\resource\bann erresource.properties

Solaris:

/opt/HiCommand/Base/conf/sec/resourc e/bannerresource.properties


Common Component-installationdirectory/Base/conf/sec/resource/banner resource.properties

This message is displayed when an invalid node is specified in the tree display in the security GUI window.

Collect maintenance information and contact the Support Center. hcmds.home

has not been set in the Java system properties.

Make sure that hcmds.home has been set in the Java system properties.

This message is displayed when no bannertaglist.conf file exists during processing to acquire a supported tag list.

Check that the following file exists:


Suite Common Component-installation-

directory \conf\sec\bannertaglist.conf

Solaris:

/opt/HiCommand/Base/conf/sec/bannertaglist.c

onf


Common Component-installation-

directory/Base/conf/sec/bannertaglist.co

nf



8-209

Error Code

KAPM08431-E

Error Message

An attempt to register the security settings information has failed.


KAPM08910-E An exception occurred.



When failing from security GUI screen to the security configuration registration will be displayed.

Do the following:

1. Confirm the following folder exists.


Suite-Common-Componentinstallationfolder\Base\

conf\sec\resource

Solaris:

/opt/HiCommand/Base/conf/sec/resou rce


Suite-Common-Component-

Installationdirectory

/Base/conf/sec/resource

2. Please delete it when the following folders exist.



\Base\conf\sec\resource\secur ity.conf

Solaris:

/opt/HiCommand/Base/conf/sec/resou rce/security.conf




/Base/conf/sec/resource/se curity.conf

3. Make sure you have access permissions for the following file.



\Base\conf\sec\resource\secur ity.conf

Solaris:

/opt/HiCommand/Base/conf/sec/resou rce/security.conf




/Base/conf/sec/resource/se curity.conf






Error Code

KAPM08911-E

KAPM08912-E

KAPM08913-E

KAPM08914-E

KAPM08915-E

KAPM08980-E

KAPM08999-E

KAPM09062-E

Error Message



Null is specified for the argument.(aa...aa)

aa...aa: Arguments


A value is invalid.(aa...aa, bb...bb)

aa...aa: Key

bb...bb: Value




There is an invalid statement in the configuration file of HBase Storage

Mgmt Web Service.


An attempt to acquire

RequestDispatcher has failed.

aa...aa: Jsp name


aa...aa







Logout, then login.





A value is invalid.


There is an invalid statement in the configuration file of HBase Storage Mgmt

Web Service.

The Listen definition in httpsd.conf, the configuration file of HBase Storage Mgmt

Web Service, is invalid.

Revise httpsd.conf as follows, and then restart all Suite products, Single Sign On

Server, and Common Web Service:

(1) Make sure that the Listen definitions of IPv4 non-SSL ports are written before other Listen definitions.

(2) Make sure that the value specified for the Listen definition of IPv4 non-SSL ports are valid values.

An attempt to acquire RequestDispatcher has failed.


Detailed information for KAPMxxxxx-E.


See the message KAPMxxxxx-E.





8-211

Error Code

KAPM09064-E

Error Message



KAPM09065-E

KAPM09066-E

KAPM09067-E







KAPM09068-E

KAPM09069-E

KAPM09070-E

KAPM10009-E

KAPM10011-E

KAPM10012-E

An attempt to read a file has failed.


An attempt to output a file has failed.




The specified authorization group already exists. (distinguished name =

aa...aa)

aa...aa: distinguished-name




aa...aa: domain-name


The information search user is not registered. (domain name = aa...aa)






Support Center.







Support Center.

An attempt to read a file has failed.


An attempt to output a file has failed.




The specified authorization group already exists.

Revise the name of the external authentication group.


Check the settings for the information search user, the settings of exauth.properties, and the operation of the external authentication server.

Authentication of the information search user has failed.

Register the information search user.




KAPM10013-E

KAPM10014-E

KAPM10015-E

KAPM10016-E

An attempt to search for the specified distinguished name has failed.




DNS communication with the external authentication server has failed.




The SRV record in the LDAP server is not registered. (distinguished name =

aa...aa, domain name = bb...bb)


bb...bb: domain-name


A DNS error has occurred.

(distinguished name = aa...aa, domain name = bb...bb)




KAPM10017-W The length of the specified distinguished name is invalid. (line number = aa...aa, distinguished name = bb...bb)

aa...aa: line number

bb...bb: distinguished-name


KAPM10022-E

The SRV record of the Kerberos server is not registered in DNS. (distinguished name = aa...aa, domain name =

bb...bb)




An attempt to search for the specified distinguished name has failed.

Confirm that the external authentication server is operating normally.

DNS communication with the external authentication server has failed.

Revise the settings and IP address of the external authorization server.

The SRV record in the LDAP server is not registered.

Revise the SRV record settings for the

LDAP server on DNS.

A DNS error has occurred.

Revise the DNS settings.

The length of the specified distinguished name is invalid.

Revise the length of specified distinguished name.

The SRV record of the Kerberos server is not registered in DNS.

Revise the SRV record settings for the

Kerberos server on DNS.



8-213

Error Code

KAPM10029-E

KAPM10034-E

Error Message

The specified Distinguished Name cannot be found. (Distinguished Name =

aa...aa)

aa...aa: Distinguished Name



The specified Distinguished Name cannot be found.

Check that the Distinguished Name for the specified group is correct. If it is correct, confirm that the information search user has been granted the following permissions:





Retrieval permission for the attribute to be retrieved

Reference permission for

Distinguished Names for groups

The specified Distinguished Name already exists.

Check that the specified Distinguished

Name is correct.

KAPM10030-W The specified Distinguished Name already exists. (Distinguished Name =

aa...aa)



KAPM10031-E

KAPM10032-E

The specified Distinguished Name already exists in another domain.

(Distinguished Name = aa...aa)



The operation cannot proceed because the external authentication group linkage function is disabled.


KAPM10033-E No groups that the user belongs to are registered. (user name = aa...aa)



The specified Distinguished Name already exists in another domain.

Check that the specified Distinguished

Name is correct.

The operation cannot proceed because the external authentication group linkage function is disabled.

Enable the external authentication group linkage function.

No groups that the user belongs to are registered.

Register a group that the user belongs to and that is on the external authentication server, and then grant the proper permissions to the group.

No groups that the user belongs to exist.

Add the user to an appropriate group on the external authentication server.

KAPM10100-E

No groups that the user belongs to exist. (user name = aa...aa)



Authentication was canceled because a search user has not been registered.

(domain name = aa...aa, host =

bb...bb, port = cc...cc, protocol =

dd...dd)


bb...bb: Host

cc...cc: Port

dd...dd: Protocol


Authentication was canceled because the search user has not been registered.

Make sure the search user has been registered.



Error Code

KAPM10101-E

KAPM10102-I

KAPM10103-E

KAPM10104-E

KAPM10105-E

Error Message

Authentication was canceled because a setting in the configuration file for the external authentication server

( exauth.properties

) is invalid.



Authentication was canceled because a setting in the configuration file for the external authentication server

( exauth.properties

) is invalid.


( exauth.properties

).

The group information was acquired from an LDAP server.

The group information was acquired from the LDAP server. (domain name =

aa...aa, host = bb...bb, port = cc...cc, protocol = dd...dd, basedn = ee...ee)


bb...bb: Host

cc...cc: Port

dd...dd: Protocol

ee...ee: BaseDN


Acquisition of group information failed.

(userId = aa...aa, domain name =

bb...bb, host = cc...cc, port = dd...dd, protocol = ee...ee, basedn = ff...ff)

aa...aa: User ID

bb...bb: Domain name

cc...cc: Host

dd...dd: Port

ee...ee: Protocol

ff...ff: BaseDN


Confirmation of the existence of a group failed because a setting in the configuration file for the external authentication server

( exauth.properties

) is invalid or a search user setting is invalid.


A search user has not been registered.




Acquisition of group information has failed.


( exauth.properties

).

Confirmation of the existence of a group failed because a setting in the configuration file for the external authentication server

( exauth.properties

) is invalid or a search user setting is invalid.


( exauth.properties

) and the search user settings.

The search user has not been registered.

Make sure the search user has been registered.



8-215

Error Code

KAPM10106-I

KAPM10112-I

KAPM10114-E

KAPM10115-E

KAPM15002-I

KAPM15003-I

KAPM15004-I

Error Message

The existence of a group was successfully confirmed. (groupDN =

aa...aa, domain name = bb...bb, host =

cc...cc, port = dd...dd, protocol =

ee...ee)

aa...aa: GroupDN

bb...bb: Domain name

cc...cc: Host

dd...dd: Port

ee...ee: Protocol


Authentication by a search user was successful. (host=aa...aa, port=bb...bb,protocol=cc...cc)

aa...aa: Host

bb...bb: Port

cc...cc: Protocol


Authentication stopped because a setting in the configuration file for the external authentication server

(exauth.properties) or a search user setting is invalid.


The Kerberos realm, KDC, or a search user definition is invalid. (realm name =

aa...aa)

aa...aa: realm-name


The hcmdscheckauth command will now start.


The configuration check of aa...aa will now start.

aa...aa: Phase number


The result of the configuration check of

aa...aa was normal.




The existence of a group was successfully confirmed.

Authentication by a search user was successful.

Authentication stopped because a setting in the configuration file for the external authentication server

( exauth.properties

setting is invalid.

) or a search user

Revise the exauth.properties

file or the search user definition.

The Kerberos realm, KDC, or a search user definition is invalid.

Check and, if necessary, revise the exauth.properties

file realm, the KDC or a search user definition.

The hcmdscheckauth command will now start.

The configuration check will now start.

The result of the configuration check was normal.



Error Code

KAPM15005-E

KAPM15006-I

KAPM15007-I

KAPM15008-E

KAPM15009-I

KAPM15010-I

KAPM15011-I

KAPM15012-E

Error Message

The result of the configuration check of

aa...aa was abnormal.



The configuration of the server aa...aa will now be checked.



The result of the configuration check of the server aa...aa was normal.



The result of the configuration check of the server aa...aa was abnormal.



The configuration check of aa...aa has finished normally.



The connection to the server aa...aa will now be checked. (host = bb...bb, port number = cc...cc, protocol = dd...dd)


bb...bb: Host name

cc...cc: Port number

dd...dd: Protocol


The server aa...aa can be connected to normally.



The result of checking the connection to the server aa...aa indicated an error. aa...aa: Server name



The result of the configuration check was abnormal.

See the immediately preceding message

KAPMxxxxx-E.

The configuration of the server will now be checked.

The result of the configuration check of the server was normal.

The result of the configuration check of the server was abnormal.

See the immediately preceding message

KAPMxxxxx-E.

The configuration check has finished normally.

The connection to the server will now be checked.

The connection to the server has been checked successfully.

An attempt to check the connection to the server has failed.

Refer to error message KAPM15010-I and the related messages that follow it.



8-217

Error Code

KAPM15013-E

KAPM15015-I

Error Message

A connection error occurred.



The command hcmdscheckauth will now finish.



A connection error occurred.

Make sure that the external authentication server is running correctly, and then perform one of the following procedures:

For LDAP:

If the message KAPM15084-E is displayed after this message, the message KAPM15084-E shows the details of the LDAP connection error. Please refer to the following and correct the problem:

1. Make sure that the host or IP address, along with the port and protocol specified in exauth.properties are correct.

2. Make sure that the network is correctly connected.

3. Check the firewall settings.

4. Make sure that the LDAP directory server is compatible with the LDAPv3 protocol.

5. Check the SSL settings for when

StartTLS is being used. For StartTLS, specify the host, not the IP address.


For RADIUS:

1. Make sure that the host or IP address, port name, and protocol specified in exauth.properties are correct.

2. Check and then respecify the client secret set for the external authentication server and the secret set for the client.





Make sure that the user who made the specification is registered in the external authentication server.

The command hcmdscheckauth will now finish.



Error Code

KAPM15016-E

KAPM15017-E

Error Message

A file was not found. (file name =

aa...aa) aa...aa: File name


A file could not be read. (file name =

aa...aa)



The settings of the external authentication server are invalid.



A file was not found.

Make sure that the file exists in the specified folder.

A file could not be read.


KAPM15018-E

KAPM15019-E

KAPM15020-E

The configuration file contains a syntax error. (line number = aa...aa, value =

bb...bb)

aa...aa: Line number

bb...bb: Value


The same property key already exists.

(line number = aa...aa, key = bb...bb)


bb...bb: Key


KAPM15021-E A required parameter has not been specified. (key = aa...aa)

aa...aa: Key


KAPM15022-W An optional parameter has been omitted. (value = aa...aa)

aa...aa: Value


KAPM15023-W A property key cannot be identified.

(line number = aa...aa)



KAPM15024-E A secret does not exist.


The settings of the external authentication server are invalid.

Check and revise the configuration file, specifying valid settings for the external authentication server.

The configuration file contains a syntax error.

The value bb...bb on line aa...aa caused a syntax error. Check and, if necessary, revise the configuration file, and then retry the operation.

The same property key already exists.

The key bb...bb on line aa...aa is a duplicate. Check and, if necessary, revise the configuration file, and then retry the operation.

A required parameter has not been specified.

Specify all required parameters, and then retry the operation.

An optional parameter has been omitted.

(value = aa...aa)

A property key cannot be identified.

Check and, if necessary, review the settings in the configuration file for the external authentication server.

A secret does not exist.

Specify a secret, and then retry the operation.



8-219

Error Code

KAPM15025-E

KAPM15026-E

KAPM15027-E

KAPM15028-E

KAPM15029-E

KAPM15030-I

KAPM15031-E

KAPM15032-E

Error Message

No connection could be made from the secondary server.








The value of hcmds.home could not be acquired.


Processing has finished normally.



The configuration file was not found.





No connection could be made from the secondary server.

Connect from the primary server.




Check and, if necessary, revise the specified options.


Specify all required options.



Processing has finished normally.



The configuration file was not found.

Confirm that the file exists, that the file is not in use.



Error Code

KAPM15033-E

KAPM15034-E

KAPM15035-I

KAPM15036-E

Error Message

An error occurred on the aa...aa server.



Authentication information cannot be acquired. (server name = aa...aa)




A server error occurred.


For LDAP:





For RADIUS:




Authentication information cannot be acquired.

Use the hcmdsldapuser

or hcmdsradiussecret

command to reset the authentication information. If you cannot resolve the problem, collect maintenance information, and then contact the Support Center.

Authentication information has been acquired.

Authentication information has been acquired.





Use the hcmdsldapuser or hcmdsradiussecret command to reset the authentication information.




8-221

Error Code

KAPM15037-E

KAPM15039-I

KAPM15040-E

KAPM15041-E

Error Message

Specify a value for at least one key.

(key = aa...aa)

aa...aa: Key


A connection was successfully established. (server name = aa...aa)



A connection attempt has failed. (server name = aa...aa)



Authentication has failed. (server name

= aa...aa)




Specify a value for at least one key.

Specify key values, and then retry the operation.

A connection was successfully established.

A connection attempt has failed.


For LDAP:

1. Make sure that the host or IP address, along with the port and protocol specified in exauth.properties are correct.






For RADIUS:

1. Make sure that the host or IP address, port name, and protocol specified in exauth.properties are correct.





See the KAPMxxxxx-E message of the server aa...aa, above.



Error Code

KAPM15042-E

KAPM15043-E

KAPM15044-E

KAPM15045-E

KAPM15046-E

KAPM15047-I

KAPM15049-E unknown.

Error Message

A syntax error occurred. (server name =

aa...aa)



A check cannot be performed because the external authentication server type is unknown.


A check cannot be performed because the server identification name is


A parameter has not been specified.

(key = aa...aa)

aa...aa: Key


An invalid value has been specified for a parameter. (key aa...aa)

aa...aa: Key


The authentication method will now be internal authentication.


The configuration file could not be accessed. (File name = aa...aa)




unknown.

If necessary, revise the value of operation.

A syntax error occurred.

See the KAPMxxxxx-E message of the server aa...aa, above.

A check cannot be performed because the external authentication server type is auth.server.type, and then retry the

A check cannot be performed because the server identification name is unknown.

If necessary, revise the value of auth.server.name, and then retry the operation.

The value for a parameter has not been specified.

Specify the value of the parameter aa...aa, and then retry the operation.

An invalid value has been specified for a parameter.

If necessary, revise the value of the parameter aa...aa, and then retry the operation.

The authentication method will now be internal authentication.

The configuration file could not be accessed.

Make sure that the configuration file exists, that you have access permissions for this file, and that the file is not in use.



8-223

Error Code

KAPM15050-E

KAPM15051-E

Error Message

Authentication of the user account used for information searching has failed.


The DN of the user account used for information searching was not found.



Authentication of the user account used for information searching failed.



For LDAP hierarchical structure model:



Make sure the DN and the password of the user who is used for searching for information are correct, and then re-execute the hcmdsldapuser command.

For LDAP flat model:



Using the hcmdsldapuser

command, confirm that the information for the server name specified to the auth.server.name attribute of exauth.properties is not registered.







Make sure the DN of the user account used for information searching is correct, and then re-execute the command hcmdsldapuser

.









KAPM15052-E

Authentication of the specified user has failed.


Authentication of the specified user failed.


For LDAP:


1. Make sure the user is specified correctly. The user must be specified using only the user name, not the

DN format.

2. Make sure the password for the specified user is correct.

3. Make sure the specified user is registered on the external authentication server and is enabled.

4. Check, and if necessary, revise the values of basedn and attr for the corresponding server in exauth.properties.

5. If an LDAP hierarchical structure model is used, check the following:

- Using the hcmdsldapuser

command, confirm that the information for the server name specified to the auth.server.name attribute of exauth.properties is registered.

- Make sure the user who is used for searching for information has the correct permissions.

6. If an LDAP flat model is used, check the following:



7. If this does not resolve the problem, acquire the maintenance information, and then contact the

Support Center.

For RADIUS:

1. Make sure the user is specified correctly.

2. Make sure the password of the specified user is specified correctly.


4. Make sure that the PAP and CHAP settings are valid.

5. If this does not resolve the problem, acquire the maintenance

Error Messages from the Hitachi Storage Command Suite Common Component 8-225



Error Code

KAPM15053-E

Error Message







1. Make sure the user is specified correctly. The user must be specified using only the user name, not the DN format.

2. Make sure that the specified user is registered in the external authentication server and is enabled.

3. Check, and if necessary, revise the values of basedn and attr for the corresponding server in exauth.properties

.


Use the command hcmdsldapuser to make sure that the server name specified for the attribute auth.server.name

of exauth.properties

is registered.

Make sure that the user account used for information searching has the necessary permissions.


Using the hcmdsldapuser command, confirm that the information for the server name specified to the auth.server.name

attribute of exauth.properties

is not registered.




Error Code

KAPM15054-E

Error Message

The specified user was not found. (error code = aa...aa)








DN format.




- Use the command hcmdsldapuser

to make sure that the server name specified for the attribute auth.server.name of exauth.properties is registered.

- Make sure that the user account used for information searching has the necessary permissions.







8-227

Error Code

KAPM15056-E

KAPM15057-E

KAPM15058-I

KAPM15059-E

KAPM15060-I

KAPM15061-E

Error Message



A dn value is invalid.




Perform the following:

1. Make sure that the specified user is registered in the external authentication server.

2. Check, and if necessary, revise the basedn and attr values for the corresponding server in exauth.properties.




Make sure the user who is used for searching for information has the correct permissions.



1. Check, and if necessary, revise the basedn value for the corresponding server in the file exauth.properties.

2. If you use the hcmdsldapuser command to register the information for the server specified for the attribute auth.server.name in the file exauth.properties make sure you specify a valid value for the dn option.

The message outputs LDAP connection information.

The message outputs LDAP connection information. (aa...aa = bb...bb, aa...aa

= bb...bb, ......)

aa...aa: Key

bb...bb: Value


aa...aa

aa...aa: Error code details


The file targeted for generation management was successfully saved.


No file targeted for generation management exists.


This message displays details of the previous error message.

Take action according to the preceding message.

The file specified by the command was saved successfully.

The file specified by the command does not exist.

Correctly specify the path to the file to be saved.



Error Code

KAPM15062-E

KAPM15063-E

KAPM15064-E

KAPM15065-E

KAPM15066-W The specified number of generations exceeds the maximum (99).


KAPM15067-E

KAPM15068-E

KAPM15069-E

KAPM15070-I

Error Message

There is not enough free space to save the file.


The specified management target is a directory.


The permissions for the file to be managed are invalid.


An attempt to store the managed file has failed.


Creation of the directory has failed.






The hcmdsfilerotate started.

command has

Output destinations: Destinations for the

log.


There is not enough free space where the file is to be saved.

Secure enough disk space where the file is to be saved, and then re-execute the command.


A directory was specified for the argument of the option that specifies the file.

Specify the absolute path to the file to be saved.

The permissions for the file specified by the command are invalid.

Make sure that you have the permissions for the specified file, and then re-execute the command.


An attempt to save the specified file has failed.

Check the permissions and save destination for the specified file, and then re-execute the command. If you cannot resolve the problem, collect maintenance information, and then contact the

Support Center.

The value of the option that specifies the number of generations exceeds the maximum.

Specify a value from 2 to 98 for the number of generations.

Creation of the directory has failed.

Make sure that the location of the directory in which the specified file is to be saved is correct, and then re-execute the command.



Specify valid options.



The hcmdsfilerotate started.

command has



8-229


KAPM15071-I

KAPM15072-I

The hcmdsfilerotate ended.

command has


A file whose file number is 99 has been overwritten.


KAPM15073-W The command log cannot be output.


KAPM15074-E

KAPM15080-E

KAPM15081-E




(server name = aa...aa)







The hcmdsfilerotate ended.

command has

If the hcmdsfilerotate

command executes 99 times or more within one second, all copied files whose file number was equal to or more than 99 (which is the maximum file number) will be saved with the file number "99".

The command log cannot be output because an environment variable needed for the output is invalid.

Revise the values set for the environmental variables needed for the output of the command log. If this does not resolve the problem, acquire the maintenance information, and then contact the Support Center.

This message indicates that the value specified for an option is invalid.

Revise the values specified for the options.






Make sure the DN and the password of the user who is used for searching for information are correct, and then re-execute the command. hcmdsldapuser











Make sure the DN of the user account used for information searching is correct, and then re-execute the command hcmdsldapuser

.




Using the hcmdsldapuser command, confirm that the information for the server name specified to the auth.server.name attribute of exauth.properties is not registered.



Error Code

KAPM15082-E

Error Message

Authentication of the specified user has failed. (server name = aa...aa)





Perform one of the following procedures for LDAP:


DN format.







- Make sure the user who is used for searching for information has the correct permissions.





Support Center.

For RADIUS:






Support Center.



8-231

Error Code

KAPM15083-E

KAPM15084-E

KAPM15085-E

Error Message









DN format.




- Use the command hcmdsldapuser to make sure that the server name specified for the attribute auth.server.name of exauth.properties is registered.

- Make sure that the user account used for information searching has the necessary permissions.


- Using the hcmdsldapuser command, confirm that the information for the server name specified to the auth.server.name attribute of exauth.properties is not registered.


LDAP directory server error is detected.

LDAP directory server error is detected.

(information = aa...aa)

aa...aa: Information


An SSL setting is invalid.


An SSL setting is invalid.

Check and, if necessary, revise the SSL settings.



Error Code

KAPM15086-E

KAPM15087-E

KAPM15088-I

KAPM15089-I

KAPM15090-E

KAPM15091-I

KAPM15092-I

Error Message





A dn value is invalid. (server name =

aa...aa)







2. Check, and if necessary, revise the basedn and attr values for the corresponding server in exauth.properties.







1. Check, and if necessary, revise the basedn value for the corresponding server in the file exauth.properties.

2. If you use the hcmdsldapuser command to register the information for the server specified for the attribute auth.server.name in the file exauth.properties make sure you specify a valid value for the dn option.

The common-items check will now start. The common-items check will now start.


The results of the common-items check were normal.


The results of the common-items check include abnormal values.


The individual-realm check will now start.


The results of the realm identified name

aa...aa check were normal.

aa...aa: Realm identified name


The results of the common-items check were normal.

The results of the common-items check include abnormal values.


The individual-realm check will now start.


aa...aa check were normal.



8-233

Error Code

KAPM15093-E

KAPM15094-I

KAPM15095-E

KAPM15096-E

KAPM15097-E

KAPM15098-I

KAPM15102-I

KAPM15103-I

KAPM15104-E

Error Message


aa...aa check include abnormal values.

aa...aa: Realm identified name


The results of the individual-realm check were normal.


The results of the individual-realm check include abnormal values.


The same value already exists. (line number = aa...aa, value = bb...bb)


bb...bb: Value


There is no auth.kerberos.<realm identification name>.realm that corresponds to auth.kerberos.default_realm.


The server connection will now be checked. (user id = aa...aa, realm name

= bb...bb)

aa...aa: User ID

bb...bb: Realm name


The hcmdsunlockaccount started.

command has


The hcmdsunlockaccount finished.

command has


The hcmdsunlockaccount

command cannot be executed on the secondary server. Execute this command on the primary server.

Output destinations: Destinations for output level 10, and windows. finished.



aa...aa check include abnormal values.


The results of the individual-realm check were normal.

The results of the individual-realm check include abnormal values.


The same value already exists.

There are duplicate bb...bb values on line

aa...aa. Check and, if necessary, revise the configuration file, and then retry the operation.

There is no auth.kerberos.<realm identification name>.realm that corresponds to auth.kerberos.default_realm.

Specify auth.kerberos.<realm identification name>.realm as the realm that corresponds to auth.kerberos.default_realm in exauth.properties.

The server connection will now be checked.

The hcmdsunlockaccount started.

The

The hcmdsunlockaccount hcmdsunlockaccount

command has

command has

command cannot be executed on the secondary server. Execute this command on the primary server.

Execute the hcmdsunlockaccount command on the primary server.



Error Code

KAPM15105-E

KAPM15108-I

KAPM15109-I

KAPM15110-E

KAPM15111-E

KAPM15112-E

KAPM15113-E

KAPM15114-E

KAPM15115-E

KAPM15116-E

KAPM15117-E

KAPM15118-E

Error Message

The user account to be unlocked does not have the User Management permission.


The user account was unlocked successfully.


The user account "aa...aa" will now be unlocked.





A command option is invalid.






Communication with the authentication server has failed.


The user ID or password is incorrect.






An HcmdsIllegalArgumentException occurred.



The user account to be unlocked does not have the User Management permission.

Specify a user who has the User


The user account was unlocked successfully.

The user account "aa...aa" will now be unlocked.



A command option is invalid.

Check the options.


Check the options.



Communication with the authentication server has failed.

Make sure the HBase Storage Mgmt

Common Service or the HBase Storage

Mgmt Web Service on the server has started.

The user ID or password is incorrect.

Make sure that the user ID and password are correct.





An HcmdsIllegalArgumentException occurred.




8-235


KAPM15119-E

KAPM15120-E

KAPM15170-E





Acquisition of the installation path has failed.


KAPM15171-E The command aa...aa will stop because internal processing failed. (details =

bb...bb)


bb...bb: Details


KAPM15172-W Log initialization failed.


KAPM15173-E

KAPM15174-E

KAPM15175-E

KAPM15200-I





Acquisition of the installation path has failed.


The specified command will stop because internal processing failed.




The command aa...aa will stop because setting of an environment variable failed. (details = bb...bb)


bb...bb: Details



(function = aa...aa, error code =

bb...bb)

aa...aa: Function



A connection was successfully established. (KDC = aa...aa)

aa...aa: KDC



If the problem occurs frequently, collect maintenance information, and then contact the Support Center.



The command will stop because setting of an environment variable failed.







Error Code

KAPM15201-E

KAPM15202-E

KAPM15203-E

KAPM15204-E

KAPM15205-E


An attempt to connect failed. (KDC =

aa...aa)

aa...aa: KDC


An attempt to connect to the DNS server failed.


On the DNS server,the SRV record corresponding to the realm name is not defined. (realm name = aa...aa)



An unexpected error occurred on the

DNS server.


The KDC resolution failed. (KDC =

aa...aa)

aa...aa: KDC


An attempt to connect failed.

Make sure that the external authentication server is running correctly, and then perform one of the following:

1. Make sure that the realm name and

KDC specified in exauth.properties are correct.

2. Make sure that the network is connected correctly.


4. Make sure that Kerberos is compatible with the external authentication server.



Check and, if necessary, revise the DNS server settings.

On the DNS server,the SRV record corresponding to the realm name is not defined.




Make sure that the realm name is correct.



On the DNS server, define the SRV record corresponding to the realm name.


DNS server.


The KDC resolution failed.




8-237

Error Code

KAPM15206-E

KAPM15207-E

KAPM15208-E

KAPM15209-E

KAPM15210-E

KAPM15211-E

KAPM15212-I

KAPM15213-I

Error Message

An attempt to authenticate failed. (KDC

= aa...aa)

aa...aa: KDC



An attempt to authenticate failed.






Make sure the specified user is registered on the external authentication server.

Check the password of the specified user.







Make sure the time difference between servers not exceeds the specified value in the exauth.properties

.

Make sure the authentication user password has not expired.

Make sure the authentication user account is not invalid.


Make sure the specified user is registered on the external authentication server.

The specified user was not found. (KDC

= aa...aa)

aa...aa: KDC


The specified password is invalid. (KDC

= aa...aa)

aa...aa: KDC


The time difference between servers exceeds the specified value in the exauth.properties. (KDC = aa...aa)

aa...aa: KDC


The authentication user password has expired. (KDC = aa...aa)

aa...aa: KDC


The authentication user account is invalid. (KDC = aa...aa)

aa...aa: KDC


Check the DNS server to confirm the connection status.


Use the default realm to confirm the connection status.



Check the password of the specified user.

The time difference between servers exceeds the specified value in the exauth.properties.

Make sure that the server times are synchronized.

The authentication user password has expired.

Change the password of the specified user.

The authentication user account is invalid.

Validate the registered user on the external authentication server.

Check the DNS server to confirm the connection status.

Use the default realm to confirm the connection status.



Error Code

KAPM15214-E

KAPM15215-E

KAPM15216-E

Error Message

The command cannot be executed on the secondary server.


Creation of the file failed. (file name =

aa...aa)

aa...aa: File name




KAPM15217-W The DBMS is not running.


KAPM15218-W The DBMS is blocked.


KAPM15219-W An error occurred while the DBMS was being accessed.



The command cannot be executed on the secondary server.

Creation of the file failed.








Make sure the file path is correct.

Make sure you have permission to create a file on the specified path.

Make sure there are no files that have the same name as the specified file.




Make sure that the DBMS is running.

The DBMS is blocked.


An error occurred while the DBMS was being accessed.

Make sure that the DBMS, HBase Storage

Mgmt Web Service, and HBase Storage

Mgmt Common Service are running. If they are running, collect maintenance information, and then contact the

Support Center.

The user to be authenticated was not found in the DBMS. (user id = aa...aa)

Make sure aa...aa is registered in the

DBMS.

KAPM15220-W The user to be authenticated was not found in the DBMS. (user id = aa...aa)

aa...aa: User ID


KAPM15221-W An unexpected error occurred on the

DBMS.


KAPM15222-E Acquisition of the KDC from aa...aa failed.




DBMS.

Retry. If you cannot resolve the problem, collect maintenance information, and then contact the Support Center.

Acquisition of the KDC from aa...aa failed.




Make sure that the realm name is correct.



Make sure that there is a KDC corresponding to the realm name.



8-239

Error Code

KAPM15223-E

KAPM15229-I

An unexpected error occurred. (KDC =

aa...aa)

aa...aa: KDC


KAPM15224-W The specified user is not registered in the DBMS as a user of the Kerberos authentication method. (user id =

aa...aa)

Error Message

aa...aa: User ID


KAPM15225-W The configuration file contains a syntax error. (line number = aa...aa, value =

bb...bb)


bb...bb: Value


KAPM15226-E An information search user is not registered. (aa...aa = bb...bb)

aa...aa: Property name

bb...bb: Property value


KAPM15227-I Group linkage is enabled.


KAPM15228-W The external authentication group was not linked to because an authentication user was found on the DBMS.



An unexpected error occurred. (KDC =

aa...aa)

Retry. If you cannot resolve the problem, collect maintenance information, and then contact the Support Center.

The specified user is not registered in the

DBMS as a user of the Kerberos authentication method. (user id =

aa...aa)






Change the specified user authentication method to Kerberos.

Create a new user of the Kerberos authentication method.

The configuration file contains a syntax error.

The value bb...bb on line aa...aa caused a syntax error. Check and, if necessary, revise the configuration file, and then retry the operation.

An information search user is not registered.

Register an information search user for

bb...bb.

Group linkage is enabled.

Group acquisition for the server will now be checked. (aa...aa = bb...bb, host =

cc...cc, port = dd...dd, protocol =

ee...ee)



cc...cc: Host name

dd...dd: Port number

ee...ee: Protocol


The external authentication group was not linked to because an authentication user was found on the DBMS.

When linking to an external authentication group, specify a user not registered in Hitachi Storage Command

Suite.

Group acquisition for the server will now be checked.



Error Code

KAPM15230-I

KAPM15231-E

Error Message

Group acquisition was successful.


Group acquisition failed.




KAPM15232-E The group was not registered.


KAPM15233-E On the DNS server, the SRV record corresponding to the domain name is not defined. (domain name = aa...aa)




Perform one of the following actions:





Make sure that the specified user is registered in a group.

Check, and if necessary, revise the values of basedn for the corresponding server in exauth.properties

.

The group was not registered.

Register the group to the specified user.

Alternatively, specify the user to whom the group is registered.

On the DNS server, the SRV record corresponding to the domain name is not defined.




On the DNS server, define the SRV record corresponding to the domain name.



Make sure that the domain name is correct.

The DNS server has been referenced. KAPM15234-I

KAPM15235-E

The DNS server has been referenced.

(aa...aa = bb...bb, domain name =

cc...cc)



cc...cc: Domain name


A server error occurred. (aa...aa =

bb...bb)




A server error occurred.


1. By using the host, port, and protocol set in " exauth.properties

", check whether the authentication server can be accessed, the settings of the external authentication server, and the status of the network.

2. By using the hcmdsldapuser command, check that the information for the server names specified in the

" auth.server.name

" attribute in

"exauth.properties" is registered.





8-241

8-242

Error Code

KAPM15236-E

KAPM15237-I

KAPM15238-E

KAPM15239-E

KAPM15240-E

KAPM15241-E

KAPM15242-E

KAPM15243-E


A check cannot be performed because the group definition is invalid.



(aa...aa = bb...bb)




Group acquisition failed. (aa...aa =

bb...bb)




The group was not registered. (aa...aa =

bb...bb)




On the DNS server,the SRV record corresponding to the domain name is not defined. (aa...aa = bb...bb)




A check cannot be performed because the group definition is invalid.

Revise the auth.group.mapping value, and then retry the operation.








Make sure that the specified user is registered in a group.

Check, and if necessary, revise the values of basedn for the corresponding server in exauth.properties

.

The group was not registered.

Register the group to the specified user.

Alternatively, specify the user to whom the group is registered.

On the DNS server,the SRV record corresponding to the domain name is not defined.




On the DNS server, define the SRV record corresponding to the domain name.



Make sure that the domain name is correct.



An attempt to connect to the DNS server failed. (aa...aa = bb...bb)





DNS server. (aa...aa = bb...bb)




The common items cannot be checked because they are not set correctly.



DNS server.


The common items cannot be checked because they are not set correctly.

Revise the settings for the common items, and then retry the operation.



Error Code

KAPM15244-I

KAPM15245-I

KAPM15246-E


The connection for realm aa...aa was checked.



A connection was successfully established. (aa...aa = bb...bb)




A connection attempt has failed. (aa...aa

= bb...bb)




The connection for realm aa...aa was checked.


A connection attempt has failed.


For LDAP:

1. Make sure that the host or IP address, along with the port and protocol specified in exauth.properties

are correct.






For RADIUS:

1. Make sure that the host or IP address, port name, and protocol specified in exauth.properties

are correct.






8-243

Error Code

KAPM15247-E

KAPM15248-E

Error Message


(aa...aa = bb...bb)





(aa...aa = bb...bb)










Make sure the DN and the password of the user who is used for searching for information are correct, and then re-execute the hcmdsldapuser command.






is not registered.






Make sure the DN of the user account used for information searching is correct, and then re-execute the command

hcmdsldapuser

.





command, confirm that the information for the server name specified to the auth.server.name


is not registered.



Error Code

KAPM15249-E

Error Message

Authentication of the specified user has failed. (aa...aa = bb...bb)






Perform one of the following procedures for LDAP:





.





is registered.






is not registered.

7. If this does not resolve the problem, acquire the maintenance information, and then contact the Support Center.

For RADIUS:





5. If this does not resolve the problem, acquire the maintenance information, and then contact the Support Center.



8-245

Error Code

KAPM15250-E

Error Message


(aa...aa = bb...bb)




KAPM15251-E The specified user was not found.

(aa...aa = bb...bb)










.


Use the command hcmdsldapuser to make sure that the server name specified for the attribute auth.server.name

of exauth.properties

is registered.

Make sure that the user account used for information searching has the necessary permissions.




is not registered.





2. Check, and if necessary, revise the basedn and attr values for the corresponding server in exauth.properties

.




is registered.




Error Code

KAPM15252-E

KAPM49001-E

Error Message

A dn value is invalid. (aa...aa = bb...bb) aa...aa: Property name bb...bb: Property value


aa...aa






1. Check, and if necessary, revise the basedn value for the corresponding server in the file exauth.properties

.

2. If you use the hcmdsldapuser command to register the information for the server specified for the attribute a uth.server.name

in the file exauth.properties

make sure you specify a valid value for the dn option.

Detailed information for KAPMxxxxx-E.


See the message KAPMxxxxx-E.



8-247


Messages (KDJE)


KDJE41000-E Failed to connect to web container. errno=aa...aa, bb...bb, cc...cc

aa...aa: System-specific error number

bb...bb: Web container IP address used to communicate with the web server

cc...cc: Web container port number used to communicate with the web server


aa...aa: Worker name


KDJE41002-E Could not redirect the request to worker.

Because redirector could not access the definition file : aa...aa



KDJE41003-

W

Invalid parameter value is specified in

aa...aa file : (bb...bb=cc...cc). Default parameter value is used : dd...dd


bb...bb: Parameter name

cc...cc: Value

dd...dd: Default value


KDJE41004-E Could not redirect the request to a worker because request header was too long.



An attempt to connect to the web container has failed.

Make sure that:

1. The worker port number is correct.

2. The worker host name or IP address is correct.

3. The queue for web container execution does not exceed the maximum limit.

4. The web container has started.

Remove the cause of the error by following the error's system-specific error number (this is a value defined in errno.h in a UNIX system, and the return value of WSAGetLastError() in a

Windows system).

An error occurred while communicating with the worker.

An error occurred while communicating to worker aa...aa. Follow the message last output (such as KDJE41000) to solve the problem.

The request could not be redirected to the worker because the redirector could not access the definition file.

The definition file of aa...aa could not be accessed. Check the access permissions and whether the definition file exists, and restart the web server.

The value specified in the parameter is invalid. The default value will be used.

To change the value of the bb...bb parameter of aa...aa file from the default value to an appropriate value, and restart the web server.

The redirector could not make a request to the worker, because the header size of the HTTP request is too large.

Remove the cause of the overly large

HTTP request header, and re-access the worker. A possible cause is that the

HTTP GET method is being used instead of the POST method.




KDJE41005-E Could not redirect the request to a worker because worker name which is specified in the mapping definition file was not defined to worker.list parameter in the workers definition file. (worker name=aa...aa)

aa...aa: Worker name


KDJE41006-E Could not redirect the request to a worker because a required parameter was not specified in the workers definition file.

(parameter=aa...aa)



KDJE41007-E Could not redirect the request to a worker because invalid value was specified in the workers definition file.

(parameter=aa...aa,value=bb...bb)


bb...bb: Value


KDJE41008-

W

Invalid parameter value is specified in the workers definition file

(parameter=aa...aa,value=bb...bb).

Default parameter value is used : cc...cc


bb...bb: Value

cc...cc: Default value


KDJE41009-E Could not create worker because it is out of memory.



The redirector cannot redirect the request to the worker because the worker specified in the mapping definition file is not defined in the worker.list parameters.

Specify the worker name (aa...aa) defined in the mapping definition file

(default name: uriworkermap.properties

) in the worker.list parameters of the worker definition file (default name: uriworkermap.properties

), and restart the web server.

The redirector cannot redirect the request to the worker because a required parameter has not been specified in the worker definition file.

Specify the aa...aa parameter in the worker definition file (default name: workers.properties), and restart the web server.

The redirector could not redirect the request to the worker because the parameter value specified in the worker definition file is invalid.

Specify an appropriate value for the worker definition file (default name: workers.properties

) parameter

(aa...aa), and restart the web server.

The parameter value specified in the worker definition file is invalid. The default value will be used.

To change the worker definition file

(default name: workers.properties

) parameter (aa...aa) from the default value, specify an appropriate value in the aa...aa parameter, and restart the web server.

The worker could not be created because memory is insufficient.

Memory has become insufficient. Secure more memory for the system, and restart the web server. This happens when a value specified in the worker definition file parameter

( worker.

worker-name

.cachesize

) is too large. The worker.

workername

.cachesize

value consumes memory as per the following formula:

Memory consumption =

( worker.

worker-name

.cachesize

value) * 10 kilobytes



8-249


KDJE41010-E Failed to connect to web client. errno=aa...aa

aa...aa: System-specific error number


KDJE41012-E The uri pattern that does not start with '/' was specified in the aa...aa file. This parameter is ignored(bb...bb to cc...cc).


bb...bb: URI pattern

cc...cc: Worker name


KDJE41016-E Could not redirect the request because it is out of memory.


No message

ID

The service named aa...aa reported the following error:>>> bb...bb <<<before the error.log file could be opened.More information may be available in the error.log file.

aa...aa: Name of the executable file of

HBase Storage Mgmt Web Service

bb...bb: Message text

Output to event log


An attempt to communicate with the client that submitted the requested has failed.

The client who submitted the request may have stopped during communication. Remove the cause of the error by following the error's system-specific error number (this is the definition value of errno.h in a UNIX system, and the return value of

WSAGetLastError() in a Windows system).

The URI pattern specified in the definition file does not start with the "

/

" character. This parameter will be ignored.

To validate the specified URI pattern and worker name, start the bb...bb URI pattern of the aa...aa file with a "

/

" character, and restart the web server.

The redirector cannot transfer the request because memory is insufficient.

Memory has become insufficient. Secure more memory for the system, and restart the web server.

The error described in bb...bb occurred before the log file (error.log) was opened.

Remove the error cause indicated by the message text, and restart the

HBase Storage Mgmt Web Service.




Messages (KEHG)

Error Code

KEHG00101-E

KEHG00102-E

KEHG00103-E

KEHG00104-E

KEHG00105-E

KEHG05710-E

KEHG05711-E

KEHG05712-E

KEHG05713-E

KEHG05714-E

KEHG05715-E


An empty string or null was specified for the element name.


An empty string or null was specified for the attribute name.


An object in PageContext

(aa...aa) is invalid.

aa...aa: Name of the invalid object


The specified application name is invalid.


The parts initialization has not been performed.


The first column cannot be a value.


Values cannot be used for two consecutive columns.


The last column cannot be a label.


The first line cannot be a value line.


Value lines cannot be used for two consecutive lines.


The last line cannot be a label line.






An object in PageContext (aa...aa) is invalid.


The specified application name is invalid.


The parts initialization has not been performed.


The first column cannot be a value.


Values cannot be used for two consecutive columns.


The last column cannot be a label.


The first line cannot be a value line.


Value lines cannot be used for two consecutive lines.


The last line cannot be a label line.




8-251

8-252


KEHG05901-E

KEHG05902-E

KEHG06500-E

Neither postName nor url has been specified.

Output destinations: Destinations for output level 10. postValue was specified without postName being specified.


Neither postName nor the URL parameter have been specified.


KEHG07501-W The file "aa...aa" could not be read. Path = bb...bb Detail:

cc...cc


bb...bb: Path

cc...cc: Error information


KEHG07502-E Authentication failed.


KEHG07504-E

KEHG08301-E

KEHG08302-E

KEHG08303-E

KEHG08304-E

An attempt to acquire the link and launch information failed. PP Type

= aa...aa

aa...aa: PP type


An attempt to read the file

(aa...aa) has failed.

aa...aa: Name of the file that could not be read


The specified application name is not registered in HiCommand

Suite Common Component.


An attempt to authenticate

HiCommand Suite Common



An attempt to communicate with the HiCommand Suite Common




Neither postName nor url has been specified.

Check the JPS coding. postValue was specified without postName being specified.

Check the JPS coding.

Neither postName nor the URL parameter have been specified.








An attempt to read the file (aa...aa) has failed.


The specified application name is not registered in Hitachi Storage Command Suite

Common Component.


An attempt to authenticate Hitachi Storage

Command Suite Common Component has failed.


An attempt to communicate with Hitachi

Storage Command Suite Common Component has failed.




Error Code

KEHG08305-E

KEHG20101-E

KEHG20102-E

KEHG90003-E

KEHG90004-E

KEHG90005-E

KEHG90006-E

Error Message

An error occurred in the H

HiCommand Suite Common

Component.






An unexpected tag was detected.

(tag name: aa...aa, attribute value: bb...bb = cc...cc, ... expected tag name: dd...dd, ...)

aa...aa: Unexpected tag name

bb...bb: Attribute name of aa...aa

cc...cc: Value of the attribute name bb...bb

dd...dd: Expected tag name


An unexpected value was detected for a variable. (variable name = aa...aa, value = bb...bb)

aa...aa: Variable containing the unexpected value

bb...bb: Value of the unexpected variable



(aa...aa)

aa...aa: Error information


A resource file corresponding to the specified locale (aa...aa) was not found.

aa...aa: Locale name



An error occurred in Hitachi Storage

Command Suite Common Component.






An unexpected tag was detected.


An unexpected value was detected for a variable.




A resource file corresponding to the specified locale (aa...aa) was not found.




8-253



Error Messages from HiRDB

This chapter lists and describes the error messages output by the HiRDB:



Error Messages Output by HiRDB



9-1

Error Messages Output by HiRDB

This section lists and describes the error messages output by HiRDB. Table 9-1

shows a description of the messages and the corresponding table title.

Table 9-1 Description of Error Messages Output by HiRDB

Table Table Title

Table 9-2

Table 9-3

Table 9-4

Table 9-5

Table 9-6

Table 9-7

Table 9-8

HiRDB Messages (KFPH)

HiRDB Messages (KFPO)

HiRDB Messages (KFPR)

HiRDB Messages (KFPS)

HiRDB Messages

(which require no action)

HiRDB Messages (which require collection of maintenance information, and contact to customer support)

HiRDB Messages (which require re-execution of the operation)

Table Contents

Messages are classified by prefix and described in each table.

Messages that are not output frequently are classified according to the required action, and listed in each table.

Message Description and

Action

Follow the instructions in the Description and Action column for each message.

No action is required for the message.


Table 9-9

Table 9-10

HiRDB Messages (which require restoration of the database)

HiRDB Messages (which require the system to be restarted, and re-execution of the operation)

Re-execute the operation in which an error occurred. If the same message is output, collect maintenance information, and then contact customer support.

Use the hcmdsdb

command to restore the database by using the backup obtained by the hcmdsbackups command.

Stop the service programs of the Hitachi program products, restart the system, and then reexecute the operation. If the same message is output, collect maintenance information, and then contact customer support.

9-2 Error Messages from HiRDB


A HiRDB error message consists of a message ID and the error message text.

The format is as follows:



Format:

KFPA

mmmmm-z message-text (see Table 9-7)

KFPC

mmmmm-z message-text (see Table 9-6 and Table 9-7)

KFPD


KFPH

mmmmm-z message-text (see Table 9-2, and Table 9-6 to Table 9-9)

KFPI


KFPK

mmmmm-z message-text (see Table 9-7)

KFPL

mmmmm-z message-text (see Table 9-6 to Table 9-10)

KFPO


KFPR

mmmmm-z message-text (see Table 9-4, and Table 9-6 to Table 9-9)

KFPS


KFPU


KFPX

mmmmm-z message-text (see Table 9-6 to Table 9-9)

mmmmm is the message number, and z is one of the following message levels:

I: Information

Q: Question

W: Warning

E: Error



Output destination:

The error message is output to syslog or the event log.

Table 9-2 HiRDB Messages (KFPH)

Error Code

KFPH00135-E

Error Message

aa....aa command failed, server =

SDS01

aa....aa: Command name

Output destination: original log trace and either syslog or the event log


The server SDS01 could not execute the operation command aa....aa. The system cancels the operation from the server

SDS01, and continues processing.

Re-execute the operation executed immediately before this message was output. If the same message is output, collect maintenance information, and then contact customer support.



9-3

9-4

Error Code

KFPH20004-E

KFPH23006-E

Error Message

Server SDS01 termination failed, function=aa....aa, return code=bbbb

aa....aa: Function resulting in the error

bbbb: Return code

Output destination: syslog or the event log

Failed to allocate semaphore, errno=aa....aa

aa....aa: Error cause code

4

: The semaphore count per semaphore identifier exceeded the maximum value of the system.

8

: The number of semaphores used by the entire system or the number of semaphore identifiers exceeded the maximum value of the system.



During termination of the server SDS01, a

bbbb error occurred in aa....aa. The system stops termination of the server

SDS01.

An operation submitted before termination of the server was submitted has not finished. Wait until the executing operation finishes, and then re-execute termination of the server. If the same message is output, collect maintenance information, and then contact customer support.

An attempt to allocate the semaphore resource has failed. The system terminates abnormally.

Restart the system. If the same message is output, collect maintenance information, and then contact customer support.

Table 9-3 HiRDB Messages (KFPO)

Error Code

KFPO00113-E

Error Message

"shmget(manager)" failed. size=aa....aa, errno=bbb

aa....aa: Size of the shared memory to be obtained (in bytes)

bbb: Value of system call errno

for the shmget


KFPO00114-E "shmget(aa....aa)" failed. size=bb....bb, errno=ccc

aa....aa: Server identifier

bb....bb Size of the shared memory to be obtained (in bytes)

ccc: Value of system call errno

for the shmget



The shmget

system call that was issued in order to obtain shared memory resulted in an error. The system terminates abnormally.

Stop the service programs of the Hitachi

Storage Command Suite program products, restart the system, and then reexecute the operation. If the same message is output, take appropriate actions according to the value of errno

for the shmget

system call (see Note).

When obtaining the shared memory used by the server aa....aa, the shmget

system call resulted in an error. The system terminates processing.


Storage Command Suite program products, restart the system, and then reexecute the operation. If the same message is output, take appropriate actions according to the value of errno

for the shmget

system call (see Note).

Note: The table below shows the cause of the error and actions to be taken for each errno.



Errno Cause

12

Windows

Systems

Solaris, Linux

Systems

Resources are insufficient.

The size of the shared memory to be obtained exceeds the memory size of the machine.

22

28

A work file in the

HiRDB installation directory might have been deleted while

HiRDB was operating.

The size of the shared memory to be obtained exceeds the value specified in the OS kernel parameter shmmax

.

The capacity of the installation drive is insufficient.

Others ---

The number of identifiers for the shared memory exceeds the maximum for the

OS.

---

Windows Systems

Action

Solaris, Linux Systems

Check whether the performance of the system in which the Hitachi Storage Command Suite program products are set up satisfies the requirements.

If the system does not satisfy the requirements, tune it appropriately.

If the system satisfies the requirements, collect maintenance information, and then contact customer support.

Use the hcmdssrv

/stop

command to stop the Hitachi

Storage Command

Suite Common

Component service, and then use the hcmdssrv /start command to restart the Hitachi Storage

Command Suite

Component service.

In the installation drive, reserve a space larger than the shared memory.

Solaris:

Specify a larger value in the kernel parameter shmsys:shminfo_shmma x

, and then restart the corresponding server.

Linux:

Specify a larger value in the kernel parameter kernel.shmmax

, and then restart the corresponding server.


- Reduce the number of shared memory segments in a single machine

- Increase the value specified in the kernel parameter shmmni

.




9-5

Table 9-4 HiRDB Messages (KFPR)

Error Code

KFPR26032-E

KFPR26243-E

Error Message

Unable to remove temporary file, host=aa....aa, file=bb....bb

aa....aa: Name of the host where the file that cannot be deleted is located

bb....bb: Name of the file that cannot be deleted


Unable to remove temporary file, host= aa

....

aa

, file= bb

....

bb

aa....aa: Name of the host where the file that cannot be deleted is located

bb....bb: Name of the file that cannot be deleted



A temporary file cannot be deleted. The system continues processing.

After the operation finishes, delete the file

bb....bb. If the same message is output, collect maintenance information, and then contact customer support.

A temporary file cannot be deleted. The system continues processing.

After the operation finishes, delete the file

bb....bb. If the same message is output, collect maintenance information, and then contact customer support.

Table 9-5 HiRDB Messages (KFPS)

Error Code

KFPS00719-E

Error Message

Message output error. message ID=

aaa

aaa: Message ID of the message to be output

Output destination: original log trace and either syslog or the event log


Memory was insufficient when a message was output. The system continues processing.


Storage Command Suite program products, and then restart the system. Follow the instructions described in the Description and

Action column for the message with the ID

aaa.

9-6 Error Messages from HiRDB


Table 9-6 HiRDB Messages (No Action Required)

Prefix Message ID

KFPC KFPC00101-I

KFPD KFPD00029-W

KFPH KFPH00035-W, KFPH00110-I, KFPH00115-I, KFPH00130-I, KFPH00134-I, KFPH00157-W,

KFPH00210-I, KFPH00211-I, KFPH00212-I, KFPH00213-W, KFPH00372-I, KFPH20006-W,

KFPH20007-W, KFPH20008-W, KFPH20009-W, KFPH20010-W, KFPH20015-I, KFPH22004-

W, KFPH22012-W, KFPH22017-I, KFPH22019-I, KFPH22020-W, KFPH22021-W, KFPH22022-

E, KFPH22023-W, KFPH22024-I, KFPH22030-W, KFPH22031-W, KFPH22034-W,

KFPH23008-W, KFPH23013-W, KFPH23014-W, KFPH23017-W, KFPH23018-W, KFPH23024-

I, KFPH23030-I, KFPH23201-W, KFPH23202-W, KFPH24004-I, KFPH26001-I, KFPH26010-I,

KFPH29005-W, KFPH29006-W, KFPH29008-I

KFPL KFPL00700-I, KFPL00701-I, KFPL00702-I, KFPL00703-I, KFPL00704-I, KFPL00705-I,

KFPL00707-I, KFPL00708-I, KFPL00709-I, KFPL00710-I, KFPL00712-I, KFPL00713-I,






KFPL50001-I

KFPR

KFPR00754-I, KFPR00756-I, KFPR00757-I, KFPR00758-I, KFPR00764-I, KFPR00765-I,



KFPR26058-I, KFPR26060-I, KFPR26061-W, KFPR26062-W, KFPR26063-I, KFPR26109-I,

KFPR26222-I, KFPR26233-I, KFPR26241-W, KFPR26257-I, KFPR26258-I, KFPR26262-W,

KFPR26264-I, KFPR26265-I, KFPR26270-W, KFPR26272-W, KFPR26275-I, KFPR26276-I

KFPS KFPS00056-I, KFPS00354-W, KFPS00441-I, KFPS00444-I, KFPS00446-W, KFPS00447-I,

KFPS00450-W, KFPS00451-I, KFPS00610-I, KFPS00611-I, KFPS00847-W, KFPS00860-W,

KFPS00958-I, KFPS00971-I, KFPS00972-I, KFPS00973-I, KFPS00980-W, KFPS00983-I,

KFPS00985-I, KFPS00986-W, KFPS00988-I, KFPS00990-I, KFPS00991-I, KFPS00993-I,

KFPS01001-I, KFPS01008-I, KFPS01011-I, KFPS01012-I, KFPS01041-I, KFPS01043-I,


KFPS01104-W, KFPS01108-W, KFPS01109-W, KFPS01114-W, KFPS01116-W, KFPS01128-

W, KFPS01130-W, KFPS01151-I, KFPS01152-W, KFPS01153-I, KFPS01154-I, KFPS01155-

W, KFPS01156-I, KFPS01157-W, KFPS01161-I, KFPS01162-W, KFPS01163-W, KFPS01175-

W, KFPS01182-I, KFPS01206-W, KFPS01211-I, KFPS01212-I, KFPS01213-W, KFPS01215-I,


KFPS01225-I, KFPS01227-W, KFPS01228-W, KFPS01229-I, KFPS01234-I, KFPS01250-I,

KFPS01252-I, KFPS01253-I, KFPS01255-W, KFPS01258-W, KFPS01262-I, KFPS01263-I,

KFPS01265-I, KFPS01266-I, KFPS01269-I, KFPS01271-I, KFPS01278-W, KFPS01279-W,


KFPS01830-I, KFPS01831-I, KFPS01832-I, KFPS01833-I, KFPS01836-W, KFPS01837-I,

KFPS01838-W, KFPS01840-I, KFPS01842-I, KFPS01843-I, KFPS01849-W, KFPS01872-I,

KFPS01877-I, KFPS01878-I, KFPS01888-W, KFPS01890-I, KFPS01894-I, KFPS01900-I,

KFPS02101-I, KFPS02104-W, KFPS02105-W, KFPS02112-W, KFPS02118-I, KFPS02119-I,

KFPS02122-W, KFPS02123-W, KFPS02124-W, KFPS02125-W, KFPS02127-W, KFPS02176-I,

KFPS02177-I, KFPS02179-I, KFPS02181-I, KFPS02183-I, KFPS02185-I, KFPS02186-W,

KFPS02187-I, KFPS02188-I, KFPS02189-W, KFPS02194-I, KFPS02195-W, KFPS02196-W,

KFPS02240-W, KFPS04320-W, KFPS04321-W, KFPS04322-W, KFPS04323-W, KFPS04370-

W, KFPS04371-W, KFPS04372-I, KFPS04373-I, KFPS04605-W, KFPS04620-I, KFPS04624-I,

KFPS04629-I, KFPS04643-I, KFPS04644-I, KFPS04650-I, KFPS04651-W, KFPS04654-W,

KFPS04660-I, KFPS04661-I, KFPS04663-W, KFPS04664-I, KFPS05024-I, KFPS05025-I,

KFPS05048-Q, KFPS05072-W, KFPS05078-I, KFPS05110-I, KFPS05753-W

KFPU KFPU00210-W, KFPU00211-W, KFPU00212-W



9-7

9-8


KFPX KFPX14045-W, KFPX14046-W, KFPX14047-W, KFPX14078-W, KFPX14245-W, KFPX14246-

W, KFPX14247-W, KFPX14250-I, KFPX18507-W, KFPX24012-I, KFPX24013-I, KFPX24212-I,

KFPX24213-I, KFPX24225-I, KFPX24226-I, KFPX24237-I, KFPX24239-I, KFPX24261-I,

KFPX24402-E, KFPX24404-I, KFPX28400-I, KFPX28401-I, KFPX28402-I

Table 9-7 HiRDB Messages (Require Collecting Maintenance Information and Contacting Customer Support)


KFPC KFPC00102-E, KFPC00103-I, KFPC00104-E

KFPD KFPD00011-E, KFPD00013-E, KFPD00014-E, KFPD00024-W, KFPD00030-W

KFPH KFPH00131-E, KFPH00133-E, KFPH00141-E, KFPH00142-E, KFPH00153-E, KFPH00154-E,

KFPH00155-W, KFPH00156-E, KFPH20001-E, KFPH20011-E, KFPH20012-E, KFPH20013-E,

KFPH20016-E, KFPH22005-E, KFPH22006-E, KFPH22007-E, KFPH22008-E, KFPH22009-E,


KFPH23002-E, KFPH23009-E, KFPH23010-E, KFPH23011-W, KFPH23012-E, KFPH23015-E,



KFPH27010-E, KFPH27011-E, KFPH27030-E, KFPH27032-E, KFPH28001-E

KFPK KFPK00204-E

KFPL KFPL10000-E, KFPL10001-E, KFPL10002-E, KFPL10003-E, KFPL10004-E, KFPL10005-E,

KFPL10006-E, KFPL11111-E, KFPL15010-E, KFPL15030-E, KFPL15036-E, KFPL15046-E,










KFPL15341-E, KFPL15342-E, KFPL15343-E, KFPL15344-W, KFPL15346-W, KFPL15347-E,


KFPL16322-E, KFPL16323-E, KFPL16324-E, KFPL16325-W, KFPL16327-E, KFPL17000-E,




KFPL25213-E, KFPL25222-W, KFPL25338-E, KFPL25339-E, KFPL25340-E, KFPL25342-E,





KFPL51203-E

KFPO KFPO00100-E, KFPO00109-E, KFPO00111-E, KFPO00112-E, KFPO00115-E




KFPR KFPR16003-E, KFPR16014-E, KFPR16101-E, KFPR16102-E, KFPR16108-E, KFPR16126-E,

KFPR16127-E, KFPR16128-E, KFPR16203-E, KFPR16214-E, KFPR16301-E, KFPR16302-E,












KFPR26244-E, KFPR26254-E, KFPR26255-E, KFPR26273-E, KFPR26277-E, KFPR26280-E

KFPS KFPS00345-W, KFPS00346-E, KFPS00347-E, KFPS00348-E, KFPS00349-E, KFPS00412-E,

KFPS00440-W, KFPS00442-E, KFPS00448-E, KFPS00452-E, KFPS00612-E, KFPS00700-E,

KFPS00701-E, KFPS00707-E, KFPS00709-E, KFPS00710-E, KFPS00712-E, KFPS00713-E,















KFPS05236-E

KFPU KFPU00215-E, KFPU00216-E, KFPU00217-E, KFPU00218-E, KFPU00219-E, KFPU00220-E,

KFPU00222-E, KFPU00223-E, KFPU00240-E, KFPU00241-E, KFPU00242-E, KFPU00243-E,

KFPU00244-E, KFPU00245-E, KFPU00246-E, KFPU00247-E, KFPU00248-E, KFPU00249-E,

KFPU00250-E, KFPU00251-E

KFPX KFPX14004-E, KFPX14017-E, KFPX14018-E, KFPX14019-E, KFPX14020-E, KFPX14023-E,

KFPX14024-E, KFPX14025-E, KFPX14026-E, KFPX14027-E, KFPX14029-E, KFPX14030-E,




KFPX14255-W, KFPX14259-E, KFPX14262-E, KFPX14268-W, KFPX14280-E, KFPX14302-W,



KFPX24006-E, KFPX24007-E, KFPX24009-W, KFPX24011-W, KFPX24018-E, KFPX24019-E,

KFPX24020-E, KFPX24022-E, KFPX24025-W, KFPX24026-E, KFPX24028-W, KFPX24029-W,


KFPX24211-W, KFPX24218-E, KFPX24219-E, KFPX24220-E, KFPX24222-E, KFPX24223-E,

KFPX24227-E, KFPX24228-E, KFPX24229-E, KFPX24230-E, KFPX24231-W, KFPX24232-E,

KFPX24233-E, KFPX24234-E, KFPX24235-E, KFPX24236-E, KFPX24238-W, KFPX24240-W,

KFPX24241-E, KFPX24242-W, KFPX24243-E, KFPX24244-I , KFPX24246-W, KFPX24262-E,




KFPX28407-E, KFPX28502-E, KFPX28503-E, KFPX28504-W



9-9

9-10

Table 9-8 HiRDB Messages (Require Re-executing the Operation)


KFPD KFPD00012-E, KFPD00020-E, KFPD00021-E



KFPH27005-E, KFPH29009-W

KFPI KFPI21582-E

KFPL KFPL15040-E, KFPL15048-E, KFPL15240-E, KFPL20001-E, KFPL20003-E, KFPL20200-E,

KFPL22000-E, KFPL25341-E

KFPR KFPR16005-E, KFPR16205-E, KFPR26001-E, KFPR26002-E, KFPR26017-E, KFPR26201-E,

KFPR26202-E, KFPR26217-E

KFPS KFPS00430-E, KFPS00443-I, KFPS00460-E, KFPS00609-E, KFPS00703-E, KFPS00836-E,

KFPS00854-W, KFPS00855-W, KFPS00888-W, KFPS00889-E, KFPS00900-I, KFPS00955-E,





KFPS04652-E

KFPU KFPU00221-E

KFPX KFPX18410-E, KFPX24001-E, KFPX24015-E, KFPX24024-E, KFPX24201-E, KFPX24208-E,

KFPX24215-E, KFPX24405-E

Table 9-9 HiRDB Messages (Require Restoring the Database)



KFPH22003-E, KFPH22018-W, KFPH22025-E, KFPH22026-E, KFPH23007-E, KFPH23023-I,


KFPH27008-E

KFPL KFPL20020-E

KFPR KFPR26072-E

KFPS KFPS01180-E, KFPS01181-E, KFPS01183-E, KFPS01184-E, KFPS01185-E, KFPS01202-E,



KFPS01302-E, KFPS02174-E, KFPS02220-E

Table 9-10 HiRDB Messages (Require Restarting the System and Reexecuting the Operation)


KFPL KFPL20000-E, KFPL23000-E, KFPL23001-E

KFPS KFPS00403-E, KFPS00705-E, KFPS00830-E, KFPS01821-E, KFPS01845-E, KFPS01846-E,


KFPS02254-E, KFPS04655-E



Troubleshooting

This chapter provides resources for troubleshooting Hitachi Device Manager.



General Troubleshooting



Calling the Hitachi Data Systems Support Center


General Troubleshooting

For troubleshooting information, please refer to the appropriate documentation as follows:



Hitachi Device Manager client operations - the Device Manager online Help and the Hitachi Device Manager Command Line Interface (CLI) User's

Guide.



Hitachi Device Manager Server operations - Hitachi Device Manager and

Provisioning Manager Server Installation and Configuration Guide.



Hitachi Storage Command Suite Common Component - Hitachi Device

Manager and Provisioning Manager Server Installation and Configuration

Guide.



Hitachi Device Manager Agent operations - Hitachi Device Manager Agent

Installation Guide.



Hitachi Device Manager CLI or Device Manager CLIEX operations - Hitachi

Device Manager Command Line Interface (CLI) User's Guide.



Disk array subsystem operations - The applicable document for the array and feature, for example, the Hitachi Lightning 9900 V Series LUN Manager

User's Guide and the Hitachi Thunder 9500 V Series ShadowImage User's

Guide.

10-2 Troubleshooting


Calling the Hitachi Data Systems Support Center

If you need to call the Hitachi Data Systems Support Center, make sure to provide as much information about the problem as possible, including the circumstances surrounding the error or failure and the exact content of any error messages displayed by Hitachi Device Manager and/or the host system.

Refer to the troubleshooting section of the applicable user document (e.g.,

Hitachi Device Manager Agent Installation Guide) for specific information to be collected before calling the Support Center.

The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, please call:



United States: (800) 446-0744



Outside of the United States: (858) 547-4526


10-4 Troubleshooting


Acronyms and Abbreviations

ACL

AL arbitrated

API array control library loop application program interface

CCI Command Control Interface (also called RAID

Manager)

CHA channel

CIM common information model

CLI command line interface

CMDDEV command switch

C/T consistency

CTG consistency

CTL, ctl controller unit

CV custom

CVS custom volume size (also called Virtual

LVI/LUN)

DAMP

DASD

Disk Array Management Program direct-access storage device for 9900V) dev device fast array controller unit

ESCON Enterprise Systems Connection disk

FDD floppy

FTP port drive

File Transfer Protocol

GB gigabyte



Acronyms-1

GUI

HIHSM

HMRCF

HOMRCF

HORCA

HORCE

HORCM

HPAV

HSN

HTTP graphical user interface

Hitachi Internal Hierarchical Storage Manager

(called Volume Migration for Universal Storage

Platform, called CruiseControl for 9900V)

Hitachi Multiple Raid Coupling Feature (also called ShadowImage for z/OS)

Hitachi Open Multiple Raid Coupling Feature

(also called ShadowImage)

Hitachi Open Remote Copy Asynchronous (also called TrueCopy Async)

Hitachi Open Remote Copy Extended

Hitachi Open Remote Copy Manager

Hitachi Parallel Access Volume

Hierarchical Star Network hypertext transfer protocol

I/F interface protocol

JDBC Java

JDK Java Developers Kit

JRE

JVM

Java Runtime Environment

Java Virtual Machine

KB kilobyte

LAN local area network

LBA

LCP

LU logical

LUN logical block address local control port device unit logical unit number, logical unit

LUSE LUN

LVI

Manager

Expansion logical volume image

MB megabyte

M-VOL

MCU main volume (TrueCopy-S/390) main control unit

MIB message information block

MIH missing

MRCF Multi-RAID Coupling Feature (also called

ShadowImage)

Acronyms-2

PA port

PCB printed circuit board

PDEV physical



PPRC

PS power

P-VOL

Peer-to-Peer Remote Copy supply primary volume (TrueCopy, ShadowImage)

RAID

RCP redundant array of independent disks remote control port

RCU remote control unit

I/O

RMC Remote

R-VOL remote volume (TrueCopy-S/390)

R/W read/write

SAN storage area network

SCSI small computer system interface

SM shared

SNMP simple

SSB sense

SSID management protocol byte storage system ID

SSL

S-VOL secure sockets layer secondary volume (TrueCopy), source volume

(ShadowImage-S/390) processor

TB terabyte

TC TrueCopy

TCP/IP transmission

TC-MF TrueCopy for z/OS and/or TrueCopy-S/390

(MF=mainframe)

TC390 TrueCopy-S/390

TID target

T-VOL target volume (ShadowImage-S/390)

URL uniform resource locator

WBEM Web-Based Enterprise Management name

XML

XRC extended markup language

Extended Remote Copy



Acronyms-3

Acronyms-4 Acronyms and Abbreviations



Hitachi Data Systems

Corporate Headquarters

750 Central Expressway

Santa Clara, California 95050-2627

U.S.A.

Phone: 1 408 970 1000 www.hds.com

[email protected]

Asia Pacific and Americas

750 Central Expressway

Santa Clara, California 95050-2627

U.S.A.

Phone: 1 408 970 1000 [email protected]

Europe Headquarters

Sefton Park

Stoke Poges

Buckinghamshire SL2 4HD

United Kingdom

Phone: + 44 (0)1753 618000 [email protected]

MK-92HC016-23

HiCommand® Device Manager Error Codes

Hitachi Device Manager Software

Error Codes

Document Organization

Software Version

Getting Help

Contents

Contents

Preface

Intended Audience

Software Version

Release Notes

Document Revision Level

Document Organization

Referenced Documents

Document Conventions

Convention for Storage Capacity Values

Getting Help

Comments

Hitachi Device Manager Messages

Device Manager Server Messages

Device Manager Web Client Messages

Device Manager Agent Messages

Device Manager Agent's Provisioning Manager Messages

Device Manager Agent's Replication Manager Messages

Device Manager VDS Provider Messages

Device Manager CLI Messages

Device Manager CLIEX Messages

Universal Storage Platform V/VM

Messages

Details About Universal Storage Platform V/VM Messages

Hitachi USP Messages

Details About Hitachi USP Messages

Lightning 9900V series Messages

Details About Lightning 9900V series Messages

Lightning 9900 Messages

Details About Lightning 9900 Messages

Hitachi AMS2000/AMS/WMS/SMS,

Thunder 9500V series, and Thunder

9200 series Messages

Details About Hitachi AMS2000/AMS/WMS/SMS, Thunder

9500V, and Thunder 9200 Messages

Alerts Produced by Hitachi Device

Manager Software

Alerts Output by Hitachi Device Manager

Trap Information Output by Storage Subsystems

Alerts about Storage Subsystem Components

Error Messages from the Hitachi

Storage Command Suite Common

Component

Error Messages Output by Hitachi Storage Command Suite

Common Component

Error Messages from HiRDB

Error Messages Output by HiRDB

Troubleshooting

General Troubleshooting

Calling the Hitachi Data Systems Support Center

Acronyms and Abbreviations

Key Features

Frequently Answers and Questions

What is the Hitachi Device Manager?

What are the main functions of the Hitachi Device Manager?

What types of storage devices can be managed by the Hitachi Device Manager?

How can I access the Hitachi Device Manager?

Table of contents