HiCommand® Device Manager Error Codes

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

Hitachi Device Manager Error Codes

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.

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

Systems Support Center.

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.

Revise the specification.

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.

Revise the specification.

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.

Wait a while, and then try again.

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.





HiCommand® Device Manager Error Codes

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

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