NEC Storage Manager Messages Handbook
NEC Storage Manager Messages Handbook

NEC Storage Manager Messages Handbook

Hide thumbs Also See for Storage Manager:

Advertisement

Quick Links

NEC Storage Manager
Messages Handbook
IS010-12E

Advertisement

Table of Contents
loading

Summary of Contents for NEC Storage Manager

  • Page 1 NEC Storage Manager Messages Handbook IS010-12E...
  • Page 2 © NEC Corporation 2001-2004 No part of the contents of this book may be reproduced or transmitted in any form without permission of NEC Corporation. The contents of this book may be modified without notice in the future.
  • Page 3 • NEC Storage ReplicationControl SQL Option Ver3.2 • NEC Storage SnapControl Ver3.3 3. The NEC Storage Manager is referred to as iSM or Storage Manager in the text of this manual. Also, the NEC Storage series disk array subsystem is referred to as a disk array.
  • Page 4 (Installation and Operation Guide for Windows) (IS016) Data Replication Command Reference NEC Storage Data Replication Command Reference (IS021) 6. The term “Microsoft SQL Server 2000” in this text refers to as either Microsoft SQL Server 2000 Enterprise Edition or the Microsoft SQL Server 2000 Standard Edition.
  • Page 5: Table Of Contents

    Contents Chapter 1 Messages and Output Destinations ........................1 Message Classification ..............................3 Message Output Destinations ............................4 Message Output Format ..............................6 Chapter 2 Message List ...............................8 Interpretation of Message List.............................8 Message List................................9 Appendix A Message Output Destination List .........................634 Appendix B Changed Message List...........................673...
  • Page 6 This page is intentionally left blank.
  • Page 7: Chapter 1 Messages And Output Destinations

    The Storage Manager outputs the information, which is required for maintenance and operation of a disk array and the Storage Manager, to log files of the console/terminal and the management server. The log files to which a message is output are syslog, event log, and operation log. The message describes information that indicates events to be reported to an administrator, such as system state transition, fault and error detection, and command input results.
  • Page 8 Chapter 1 Messages and Output Destinations Management server Output to syslog (UNIX) or event log (Windows) Syslog or event log Storage Manager Operation log Output to console/terminal Disk array Console/Terminal Output to ESMPRO Manager when ESMPRO Business Agent installed (only for Windows)
  • Page 9: Message Classification

    Chapter 1 Messages and Output Destinations A message classification is assigned to a message, according to its level of urgency. Messages are classified into the following four classifications, in the order of urgency: “ERROR”, “WARNING”, “NOTICE”, and “INFO”. A message classification is also referred to as a message level. Meanings of the messages are as follows: ERROR: Error message This message indicates an error that has a critical effect to the functions, and prompt recovery by an...
  • Page 10: Message Output Destinations

    ReplicationControl only. During the operation of iSM client, the information output to the operation log is also displayed on the message display area of the state monitor screen. Operation logs are output as the following directory/file names by default. Storage Manager operation log UNIX system: /opt/iSMsvr/etc/log/iSM_Log.log Windows system: <Installation directory>\iSMsvr\etc\log\iSM_Log.log...
  • Page 11 Storage Manager has started, messages to be notified to the ESMPRO manager of all the messages that the Storage Manager server outputs to an event log are automatically set to display on the ESMPRO Manager alert viewer. To change the setting, ESMPRO Agent notification setting must be changed.
  • Page 12: Message Output Format

    : Error WARNING : Warning NOTICE : Information INFO : Information Source Storage Manager : (fixed) Classification None (fixed) Event ID Number part in the message ID output to the operation log. The following describes output rules for errno: Windows system 1.
  • Page 13 Chapter 1 Messages and Output Destinations UNIX system 1. A defined value is output as is.
  • Page 14: Chapter 2 Message List

    Chapter 2 Message List Chapter 2 Message List 2.2 “Message List” describes the messages in the order of message IDs. The message are described in the following format: iSMxxxxx: AAAAA<aaa>,<bbb...b> Message ID (iSMxxxxx) and message body (AAAAA<aaa>,<bbb...b>) are described. Descriptions using parentheses such as <aaa> and <bbb...b> indicate that parameter values are not fixed. (The parentheses “<”...
  • Page 15 Chapter 2 Message List iSM01000 ∼ iSM01001: Storage Manager has started [Classification] INFO [Explanation] It shows that iSM server has started. For Windows, this message is target of ESMPRO Manager Report. [Measures] Unnecessary iSM01002: Storage Manager is ready [Classification] INFO [Explanation] It shows that iSM server has become capable of operation.
  • Page 16 It shows that a command is entered. This message is output on UNIX system. aaa...a: command that is entered [Measures] Unnecessary iSM01006: Termination of Storage Manager is started [Classification] WARNING [Explanation] It shows that abort processing of iSM server is started.
  • Page 17 Chapter 2 Message List iSM01010: Storage Manager has restarted [Classification] INFO [Explanation] It shows that the iSM server is restarted. For Windows, this message is target of ESMPRO Manager Report. [Measures] Unnecessary iSM01011: <aaa...a> has restarted [Classification] INFO [Explanation] It shows that a process indicated with aaa...a is restarted.
  • Page 18 Chapter 2 Message List iSM01101: The function is not available. function=<aaa...a> [Classification] WARNING [Explanation] The function indicated with aaa...a has become unavailable. iSM server will block the function. aaa...a : Unavailable function PerformanceMonitor : Performance monitoring function ReplicationControl : Replication control function msgdrv : Event link function config GUI...
  • Page 19 Chapter 2 Message List iSM01103: Socket access failed. process= <aaa...a> func=<bbb...b> [errno=<ccc>|error=<ddd...d>] detail=<ee-fff> [Classification] NOTICE [Explanation] Error has occurred in the socket communication between the processes indicated with aaa...a and the main process. This error occurs when the process has stopped or the file environment of iSM Server’s socket path (/opt/iSMsvr/etc/sock) is in an incorrect status.
  • Page 20 Chapter 2 Message List iSM01105: File access failed. file=<aaa...a> func=<bbb...b> errno=<ccc> detail=<dd-eee> [Classification] NOTICE [Explanation] It shows that an error has occurred in accessing the file indicated with aaa...a. In this message case, the environment of environment definition file (/etc/iSMsvr/iSMsvr.conf) or control file (files under /opt/iSMsvr/etc.) may be in an incorrect status.
  • Page 21 : Process name [Measures] Resolve the problem through the previous message output before this message, and restart the iSM server if necessary. iSM01108: Storage Manager has already started [Classification] NOTICE [Explanation] It shows that the iSM server has already started.
  • Page 22 Chapter 2 Message List iSM01110: Illegal configuration. file=<aaa...a> line=<bbb...b> [section=<ccc...c>] [keyword=<ddd...d>] [value=<eee...e>] [token=<fff...f>] [detail=<ggg...g>] [Classification] NOTICE [Explanation] It shows that an illegal configuration is detected in the environment definition file. iSM Server will be abnormally terminated. aaa...a : Environment definition file name bbb...b : Line number with illegal configuration ccc...c...
  • Page 23 Chapter 2 Message List iSM01111: User definition does not exist, Client cannot be connected. file=<aaa...a> [Classification] NOTICE [Explanation] It shows that there is no specification of the indispensable parameter of the environment definition file. The indispensable parameter is a login parameter in the client section.
  • Page 24 Chapter 2 Message List iSM01230: Storage Manager has terminated abnormally [Classification] WARNING [Explanation] It shows that iSM server has terminated abnormally. The message of the cause has displayed before this message. For Windows, this message is target of ESMPRO Manager Report.
  • Page 25 Execute the command in valid format. This message is output on UNIX system. [Measures] Check command format and retry. iSM01407: Rejected: Storage Manager is not ready [Explanation] It indicates that a command was not accepted because the iSM is not operative. [Measures]...
  • Page 26: Aaa

    Chapter 2 Message List iSM01408: Rejected: System function error (<aaa...a>) <bbb...b> [Explanation] It indicates that an error occurred in a system function indicated by “aaa...”. aaa...a : System function name bbb...b : Error description errno= zzzz : Error number socket close : Socket with iSM closed timeout : Time-out occurred in socket communication with the iSM.
  • Page 27 Chapter 2 Message List iSM01411: Rejected: PerformanceMonitor is not available [Explanation] It indicates that the performance monitor function is not available. [Measures] Unnecessary iSM01412: Internal error. detail=<aaaa> [Explanation] It indicates that an internal error has occurred. aaaa : Internal code [Measures] Obtain information and restart the iSM.
  • Page 28 Chapter 2 Message List iSM02000 ∼ iSM02010: In initialization, port setting failed errno=<aaaaa> [Classification] NOTICE [Explanation] It shows that port number setting has failed in the initializing process. aaaaa : Error number [Measures] Take the measures below. For UNIX : Check the port number setting in the [client] section of the environment definition file in order to see if the iSM port number which is specified in the iSMsvr_port parameter or the port number of 8020 at the time of an abbreviation is being used in...
  • Page 29 Chapter 2 Message List iSM02020: Function Error has occurred name=<aaa...a> code=<bbbbb> errno=<ccccc> [Classification] NOTICE [Explanation] It shows that a function error has occurred. This message is output on UNIX system. aaa...a : Function name bbbbb : Internal code ccccc : Error number [Measures] Check the settings relevant to the applicable function.
  • Page 30 Chapter 2 Message List iSM02040: iSM/Client connected user=<aaa...a> client=<bbbbbbbb> ip=<ccc...c> [Classification] INFO [Explanation] It shows that an iSM client is connected. aaa...a : User name bbbbbbbb : iSM client name ccc...c : iSM client’s IP address [Measures] Unnecessary (This message indicates that the operation is completed as required.) iSM02041: iSM/Client terminated user=<aaa...a>...
  • Page 31 Chapter 2 Message List iSM02042: iSM/Client disconnected user=<aaa...a> client=<bbbbbbbb> ip=<ccc...c> reason=<ddd> [Classification] NOTICE [Explanation] It shows that the iSM client has been disconnected. aaa...a : User name bbbbbbbb : iSM client name ccc...c : iSM client’s IP address : Reason of the disconnection 001 : Hindrance generated in the client 002 : Time out generated in the client 003 : Others...
  • Page 32 Chapter 2 Message List iSM02050: iSM/Client Management Service started [Classification] INFO [Explanation] It shows that iSM/Client Management Service has started. [Measures] Unnecessary (This message indicates that the operation is completed as required.) iSM02051: iSM/Client Management Service terminated [Classification] INFO [Explanation] It shows that iSM/Client Management Service has terminated.
  • Page 33 Chapter 2 Message List iSM02053: iSM/Client Management Service is waiting for L3 user’s termination [Classification] INFO [Explanation] It shows that iSM/Client Management Service is waiting for the termination of L3 user. This message is output on UNIX system. [Measures] iSM server has become the state of waiting for the disconnection of L3 user who is in the controlling level.
  • Page 34 Chapter 2 Message List iSM02061: Data lost recovered client=<aaaaaaaa> ip=<bbb...b> [Classification] NOTICE [Explanation] It shows that the received and transmitted data lost during process has been recovered. This message is output on UNIX system. (Output only to syslog) aaaaaaaa : iSM client name bbb...b : iSM client’s IP address [Measures]...
  • Page 35 Chapter 2 Message List iSM03000 ∼ iSM03100: Disk Array is not specified in the config file. detail=<aa-bbbb> [Classification] WARNING [Explanation] It indicates that no monitoring disk array exists for the iSM server because disk array has not been specified. aa-bbbb : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures]...
  • Page 36 Chapter 2 Message List iSM03102: Diskarray[<a>] and diskarray[<b>] are the same disk. detail=<cc-dddd> [Classification] ERROR [Explanation] It indicates that disk arrays specified by diskarray [a] and diskarray [b] overlap with each other. The iSM server terminates abnormally. : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32)
  • Page 37 Chapter 2 Message List iSM03104: IP address (<aaa...a>) in diskarray[<b>] is not control path to the management object. detail=<cc-dddd> [Classification] ERROR [Explanation] It indicates that IP address specified by diskarray [b] is not a control path of the monitoring target disk array. The iSM server terminates abnormally. aaa...a : IP address : Disk array specifying number in environment definition file...
  • Page 38 Chapter 2 Message List iSM03106: IP address (<aaa...a>) in diskarray[<b>] is same as one in diskarray[<c>]. detail=<dd-eeee> [Classification] ERROR [Explanation] The same IP address is specified in diskarray [b] and diskarray [c]. The iSM server terminates abnormally. aaa...a : IP address : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) : Disk array specifying number in environment definition file...
  • Page 39 Chapter 2 Message List iSM03108: File (<aaa...a>) in diskarray[<b>] is invalid description. detail=<cc-dddd> [Classification] ERROR [Explanation] A special file specified by diskarray [b] is incorrect. The file may not exist or the file may not be a character-type special file. The iSM server terminates abnormally.
  • Page 40 Chapter 2 Message List iSM03109: File (<aaa...a>) in diskarray[<b>] is not control path to the management object. detail=<cc-dddd> [Classification] ERROR [Explanation] A special file specified by diskarray [b] is not a control path for the monitoring target disk array. The iSM server terminates abnormally. This message is output on UNIX system.
  • Page 41 Chapter 2 Message List iSM03110: File (<aaa...a>) in diskarray[<b>] is defined in the other specification. detail=<cc-dddd> [Classification] ERROR [Explanation] It indicates that disk arrays specified by diskarray [b] overlap with each other. The iSM server terminates abnormally. This message is output on UNIX system. aaa...a : Special file name : Disk array specification number (1 to 64) in the environment...
  • Page 42 Chapter 2 Message List iSM03111: File (<aaa...a>) in diskarray[<b>] is same as one in diskarray[<c>]. detail=<dd-eeee> [Classification] ERROR [Explanation] The same special file is specified in diskarray [b] and diskarray [c]. The iSM server terminates abnormally. This message is output on UNIX system. aaa...a : Special file name : Disk array specification number (1 to 64) in the environment...
  • Page 43 Chapter 2 Message List iSM03112: File (<aaa...a>) in diskarray[<b>] contradicts the other specification. detail=<cc-dddd> [Classification] ERROR [Explanation] The special files specified in diskarray [b] indicates different disk arrays. The iSM server terminates abnormally. This message is output on UNIX system. aaa...a : Special file name : Disk array specification number (1 to 64) in the environment...
  • Page 44 Chapter 2 Message List iSM03113: All control paths of diskarray[<a>] are not available. detail=<bb-cccc> [Classification] WARNING [Explanation] All control paths of diskarray [a] have been blocked. Monitoring to the disk array is disabled. : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bb-cccc : Detail information (This code is not disorder reason but a value...
  • Page 45: Environment Definition File Name

    Chapter 2 Message List iSM03120: Management of diskarray[<a>] succeeded. name=(<bbb...b>) detail=<cc-dddd> [Classification] INFO [Explanation] Succeeded in incorporating disk array specified by agent section (diskarray [a]) in environment definition file. On Windows system, the message indicates that the disk array specified by environment setting (setting of disk array information) diskarray [a] was successfully incorporated.
  • Page 46 Chapter 2 Message List iSM03122: Management of diskarray succeeded by autofind. name=(<aaa...a>) detail=<bb-cccc> [Classification] INFO [Explanation] It shows that management of disk array is successful via automatic detection function. aaa...a : Disk array name bb-cccc : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Unnecessary...
  • Page 47 Chapter 2 Message List iSM03131: Management of control path in diskarray[<a>] failed. ip=<bbb...b> port=<ccccc> func=<ddd...d> reason=(timeout <eee>sec.) detail=<ff-gggg> [Classification] NOTICE [Explanation] Failed in the inclusion of the control path due to time out. : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address...
  • Page 48 Chapter 2 Message List iSM03133: Management of control path in diskarray[<a>] failed. ip=<bbb...b> port=<ccccc> reason=(invalid receive data) detail=<dd-eeee> [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address ccccc...
  • Page 49 Chapter 2 Message List iSM03140: Management of control path in diskarray[<a>] failed. file=<bbb...b> func=<ccc...c> errno=<ddd> detail=<ee-ffff> [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on UNIX system. : Disk array specification number (1 to 64) in the environment definition file (agent section) bbb...b : Special file name...
  • Page 50 Chapter 2 Message List iSM03141: Management of control path in diskarray[<a>] failed. file=<bbb...b> command=(<ccc...c>) status= (<dd>/<ee>/<ff>/<gg>) detail=<hh-iiii> [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on UNIX system. : Disk array specification number (1 to 64) in the environment definition file (agent section) bbb...b : Special file name...
  • Page 51 Chapter 2 Message List iSM03142: Management of control path in diskarray[<a>] failed.file=<bbb...b> command=(<ccc...c>) status=(<dddddddd>) detail=<ee-ffff> [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on UNIX system. : Disk array specification number (1 to 64) in the environment definition file (agent section) bbb...b : Special file name...
  • Page 52 Chapter 2 Message List iSM03150: Management of control path by autofind failed. file=<aaa...a> func=<bbb...b> errno=<ccc> detail=<dd-eeee> [Classification] INFO [Explanation] Failed in the inclusion of the control path by auto find function. The disk with error cannot be included to iSM server. iSM server will ignore error.
  • Page 53 Chapter 2 Message List iSM03151: Management of control path by autofind failed. file=<aaa...a> command=(<bbb...b>) status=(<cc>/<dd>/<ee>/<ff>) detail=<gg-hhhh> [Classification] INFO [Explanation] Failed in the inclusion of the control path by auto find function. The disk with error cannot be included in iSM server. iSM server will ignore the error.
  • Page 54 Chapter 2 Message List iSM03152: Management of control path by autofind failed. file=<aaa...a> command=(<bbb...b>) status=(<cccccccc>) detail=<dd-eeee> [Classification] INFO [Explanation] Failed in the inclusion of the control path by auto find function. The disk information that becomes an error cannot be included in iSM server. iSM server will ignore the error.
  • Page 55 Chapter 2 Message List iSM03200: Control path access failed. ip=<aaa...a> port=<bbbbb> func=<ccc...c> errno=<ddd> detail=<ee-ffff> [Classification] ERROR [Explanation] An error occurred in the socket communication with the disk array. aaa...a : IP address bbbbb : Port number ccc...c : Function number : Error number ee-ffff : Detail information (This code is not disorder reason but a value...
  • Page 56 Chapter 2 Message List iSM03203: Control path access failed. ip=<aaa...a> port=<bbbbb> func=<ccc...c> reason=(timeout <ddd>sec.) detail=<ee-ffff> [Classification] ERROR [Explanation] A timeout occurred in the socket communication with the disk array. aaa...a : IP address bbbbb : Port number ccc...c : Function number : Seconds of time out ee-ffff : Detail information (This code is not disorder reason but a value...
  • Page 57: File=

    Chapter 2 Message List iSM03220: Control path access failed. file=<aaa...a> func=<bbb...b> errno=<ccc> detail=<dd-eeee> [Classification] ERROR [Explanation] Error occurred in the access of the control path (special file). This message is output on UNIX system. aaa...a : Special file name bbb...b : Function number : Error number dd-eeee...
  • Page 58 Chapter 2 Message List iSM03221: Control path access failed. file=<aaa...a> command=(<bbb...b>) status=(<cc>/<dd>/<ee>/<ff>) detail=<gg-hhhh> [Classification] ERROR [Explanation] A command error occurred. A failure may exist in the disk array. This message is output on UNIX system. aaa...a : Special file name bbb...b : Command Descriptor Block of the issued command : Status Byte...
  • Page 59 Chapter 2 Message List iSM03222: Control path access failed. file=<aaa...a> command=(<bbb...b>) status=(<cccccccc>) detail=<dd-eeee> [Classification] ERROR [Explanation] A command error occurred. A failure may exist in the disk array. This message is output on UNIX system. aaa...a : Special file name bbb...b : Command Descriptor Block of the issued command cccccccc...
  • Page 60 Chapter 2 Message List iSM03224: Control path is blockaded. file=(<aaa...a>) func=<bbb...b> errno=<ccccc> status=<ddd...d> (<eee...e> productID=<fffff> SN=<ggggg>) [UC=<hhhhhhhh> FC=<ii>][_ALERT_] [Classification] ERROR [Explanation] The control path (access to special file) was blockaded. This message is output on UNIX system. This message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 61 Chapter 2 Message List iSM03224: Control path is blockaded. disk=(disk<aaa> (Port<bbb> Bus<ccc> Target<ddd> Lun<eee>)) func=<fff...f> errno=<ggggg> status=<hhh...h> (<iii...i> productID=<jjjjj> SN=<kkkkk>) [UC=<llllllll> FC=<mm>][_ALERT_] [Classification] ERROR [Explanation] The control path (access to disk) was blockaded. This message is output on Windows system. This message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 62 Chapter 2 Message List iSM03224: Control path is blockaded. ip=(<aaa...a>) func=<bbb...b> errno=<ccccc> status=<ddddd> (<eee...e> productID=<fffff> SN=<ggggg>) [UC=<hhhhhhhh> FC=<ii>][_ALERT_] [Classification] ERROR [Explanation] The control path (access to SVP) was blockaded. This message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 63 Chapter 2 Message List iSM03225: Data can not be gotten sequentially during split mode.Disk=(disk<aaa> (Port<bbb> Bus<ccc> Target<ddd> Lun<eee>)) reason=(invalid sequence) detail=<ff-gggg> [Classification] ERROR [Explanation] Obtaining data failed in command divided transfer. The message indicates that retry processing could not obtain correct data either. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information ff-gggg : Detail information (This code is not disorder reason but a value...
  • Page 64 Chapter 2 Message List iSM03301: SVP failed. name=(<aaa...a>) ip=<bbb...b> detail=<cc-dddd> [Classification] INFO [Explanation] Service processor(SVP) has become unavailable for use due to a problem. If SVP is in redundant composition, iSM server will continue processing by switching the SVP. aaa...a : Disk array name bbb...b : IP address of service processor (SVP)
  • Page 65 Chapter 2 Message List iSM03303: SNMP trap has been available. detail=<aa-bbbb> [Classification] INFO [Explanation] SNMP TRAP has changed the receiving status from unavailable to available. SNMP TRAP receiving can be done. iSM server has become available to swiftly report trouble information using SNMP TRAP. aa-bbbb : Detail information (This code is not disorder reason but a value for maintenance.)
  • Page 66 Chapter 2 Message List iSM03410: Socket access failed. func=<aaa...a> errno=<bbb> detail=<cc-dddd> [Classification] ERROR [Explanation] Error occurred in the socket access function. iSM server will be terminated abnormally. aaa...a : Function number : Error number cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the function name and error number, and resolve the hindrance.
  • Page 67 Chapter 2 Message List iSM03420: Memory access failed. func=<aaa...a> errno=<bbb> detail=<cc-dddd> [Classification] ERROR [Explanation] Error occurred in the memory access function. iSM server will be terminated abnormally. This message is output on UNIX system. aaa...a : Function number : Error number cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.)
  • Page 68 Chapter 2 Message List iSM03440: iSMmknod is running. detail=<aa-bbbb> [Classification] ERROR [Explanation] iSM server cannot be activated because iSMmknod command is being executed. This message is output on UNIX system. aa-bbbb : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Wait for completion of iSMmknod command and restart the iSM server.
  • Page 69 Chapter 2 Message List iSM03500: Internal error occurred. detail=<aa-bbbb> [Classification] ERROR [Explanation] Internal error has occurred under the agent management. The iSM server terminates abnormally. aa-bbbb : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Save the following information and restart the iSM server.
  • Page 70: Notice

    Chapter 2 Message List iSM04000 ∼ iSM04020: Function Error has occurred name=<aaa...a> code=<bbbbb> errno=<ccccc> [Classification] NOTICE [Explanation] It shows that a function error has occurred. aaa...a : Function name bbbbb : Internal code ccccc : Error number [Measures] Check the settings relevant to the applicable function. iSM04021: Internal Error has occurred code=<aaaaa>...
  • Page 71 Chapter 2 Message List iSM04023: File write error has occurred file=<aaa...a> [Classification] ERROR [Explanation] Failed in writing to the file. aaa...a : File name [Measures] Check the status of applicable file. (Writing down authority, etc.) If a generation management file (iSM_Log.cnt) name is indicated, the generation number managed by the generation management file is invalid, and backup operation for the generation file may not be performed normally.
  • Page 72 Chapter 2 Message List iSM04025: File open error has occurred file=<aaa...a> [Classification] ERROR [Explanation] Failed in opening the file. aaa...a : File name [Measures] Check the existence and the status of the applicable file. If a generation management file (iSM_Log.cnt) name is indicated, the generation number managed by the generation management file is invalid, and backup operation for the generation file may not be performed normally.
  • Page 73 Chapter 2 Message List iSM04060: Log File write started host=<aaa...a> [Classification] INFO [Explanation] It shows that writing into the operation log has started. aaa...a : Host name of the machine running iSM server [Measures] Unnecessary...
  • Page 74 Chapter 2 Message List iSM06000 ∼ iSM06020: Function Error has occurred name=<aaa...a> code=<bbbbb> errno=<ccccc> [Classification] NOTICE [Explanation] It shows that a function error has occurred. aaa...a : Function name bbbbb : Internal code ccccc : Error number [Measures] Check the settings relevant to the applicable function. iSM06021: Internal Error has occurred code=<aaaaa>...
  • Page 75 Chapter 2 Message List iSM06030: Message driven definition file cannot open. errno=<aaaaa> file=<bbb...b> [Classification] WARNING [Explanation] It shows that opening of the message driven definition file has failed. aaaaa : Error number bbb...b : File name [Measures] Check the status of definition file. The definition files are stored in the following: For UNIX : /etc/iSMsvr/msgdrv.conf...
  • Page 76: Aaa

    Chapter 2 Message List iSM06033: Message driven definition file error. <aaa...a> overlaps. line=<bbb> [Classification] WARNING [Explanation] It indicates that “SMTP”, “SMTP_PORT”, “POP”, “POP_PORT”, “AUTH”, “USER”, “PASSWORD”, or “HEADER” overlaps in the message driven definition file. aaa...a : “SMTP”, “SMTP_PORT”, “POP”, “POP_PORT”, “AUTH”, “USER”, “PASSWORD”, or “HEADER”...
  • Page 77 Chapter 2 Message List iSM06035: Message driven definition file error. ‘=’ does not exist. line=<aaa> [Classification] WARNING [Explanation] It indicates that there is no “=” in the applicable line of the message driven definition file. : Error line number [Measures] Take the measures below.
  • Page 78 Chapter 2 Message List iSM06037: Message driven definition file error. <aaa...a> is not defined [Classification] WARNING [Explanation] It indicates that there is no definition of “SMTP”, “POP”, or “USER” in the message driven definition file. aaa...a : “SMTP”, “POP”, or “USER” [Measures] Take the measures below.
  • Page 79 Chapter 2 Message List iSM06039: Message driven definition file error. “shell” and “mail” exceeded 10. line=<aaa> [Classification] WARNING [Explanation] It indicates that definition number of either “shell” or “mail” at the same level exceeded 10 in the applicable line of the message driven definition file. : Error line number [Measures] Take the measures below.
  • Page 80 Chapter 2 Message List iSM06041: Header file cannot read. errno=<aaaaa> [Classification] WARNING [Explanation] It indicates that reading a header file has failed. aaaaa : Error number [Measures] Check header file name (header file name specified in message driven definition file on UNIX system, or mail header file name specified in link information of environment settings on Windows system), and check the state of the file (such as reading authority, etc.).
  • Page 81 Chapter 2 Message List iSM06044: Header file error. No character following “FROM:” [Classification] WARNING [Explanation] It indicates that nothing is written next to first “FROM:” in the header file. [Measures] Check header file name (header file name specified in message driven definition file on UNIX system, or mail header file name specified in link information of environment settings on Windows system), and check the first line of the file.
  • Page 82 Chapter 2 Message List iSM06048: POP address or port number error [Classification] WARNING [Explanation] It indicates that the specified POP address or the port number specified in POP_PORT is incorrect. [Measures] Specify POP by the DNS name of IP address of the POP server and POP_PORT by the port number of the POP server.
  • Page 83 Chapter 2 Message List iSM06062: Mail server connect error. name=<aaa...a> code=<bbbbb> errno=<ccccc> [Classification] WARNING [Explanation] It indicates that the connection to mail server has failed. aaa...a : Function name bbbbb : Internal code ccccc : Error number [Measures] Failed in connection with mail server (mail server specified in message driven definition file on UNIX system, or mail server specified by link information of environment settings on Windows system).
  • Page 84 Chapter 2 Message List iSM06064: Send error (to mail server). name=<aaa...a> code=<bbbbb> errno=<ccccc> [Classification] WARNING [Explanation] It indicates that transmitting to mail server has failed. aaa...a : Function name bbbbb : Internal code ccccc : Error number [Measures] Check the operation of the defined mail server, and resolve the problem. iSM06065: Communication error(mail server).
  • Page 85 Chapter 2 Message List iSM06068: Authentication failed. id=<a> send=<bbb...b> recv=<ccc...c> [Classification] WARNING [Explanation] It indicates that authentication has failed. : Internal code bbb...b : Transmission information ccc...c : Reception information [Measures] Take the measures described below. For UNIX : Check the required information for the specified authentication mode, and describe it correctly.
  • Page 86 Chapter 2 Message List iSM06071: Data lost recovered [Classification] WARNING [Explanation] It indicates that the message lost by the overflow of message buffer has been recovered. This message is output on UNIX system. (Output only to syslog) [Measures] This message is output in pair with iSM06070, which indicates that too many messages to be linked exist, and indicates recovery of the error indicated by iSM06070.
  • Page 87 Chapter 2 Message List iSM06082: Definition change error. Message driven function continues to operate by previous definition [Classification] WARNING [Explanation] The definition change was failed. The driven function operates by the old function before changing. [Measures] While trying to change the definition with iSM server operating, the definition error occurred.
  • Page 88 Chapter 2 Message List iSM06085: Making directory for message file error. name=<aaa...a> path=<bbb...b> errno=<ccccc> [Classification] ERROR [Explanation] It indicates it failed to create the message file directory. aaa...a : Function name bbb...b : Directory name ccccc : Error number [Measures] There is an error in the authority of installation directory and so on.
  • Page 89 Chapter 2 Message List iSM06088: Message driven processing stopped for excess of number of processes was resumed [Classification] WARNING [Explanation] The driving process, which has been cancelled because the processing number of mail transmission and shell start per one minute exceeded the limit, has been released.
  • Page 90 Chapter 2 Message List iSM06092: Message driven definition file error. Number of “,” is not right. line=<aaa> [Classification] WARNING [Explanation] It indicates that “ , ” is not suitable in the applicable line of the message driven definition file. : Error line number [Measures] Take the measures below.
  • Page 91 Chapter 2 Message List iSM06099: Message driven definition file error. id=<a> line=<bbb> [Classification] WARNING [Explanation] It indicates that incorrect description exists in the message driven definition file. : Error Classification Some character follows the [SERVER] or [LEVEL]. A position of “=” is inappropriate or “=” does not exist. No character follows “=”.
  • Page 92 Chapter 2 Message List iSM06902: Message customize function error. reason=<aaa...a> [func=<bbb...b>] [errno=<ccc>] [line=<ddd>] [detail=<eee...e>] [Classification] ERROR [Explanation] It shows that an error occurred in the message customizing function. This message is output on Windows system. aaa...a : error contents system call error : System call error file definition error : File description error internal error...
  • Page 93 Chapter 2 Message List iSM07000 ∼ iSM07011: Resource monitoring started. (<aaa...a> productID=<bbbbb> SN=<ccccc>) [Classification] INFO [Explanation] It indicates that state monitoring to disk array (name: aaa...a) has been started. For Windows, this message is target of ESMPRO Manager Report. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.)
  • Page 94 Chapter 2 Message List iSM07021: Resource monitoring stopped. (<aaa...a> productID=<bbbbb> SN=<ccccc>) [Classification] INFO [Explanation] It indicates that state monitoring to disk array (name: aaa...a) has been stopped. For Windows, this message is target of ESMPRO Manager Report. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 95 Chapter 2 Message List iSM07023: Resource monitoring stopped by control path fault. (<aaa...a> productID=<bbbbb> SN=<ccccc>) [UC=<dddddddddd> FC=<ee>][_ALERT_] [Classification] ERROR [Explanation] It indicates that trouble of control path caused the stop of monitoring to disk array (name: aaa...a). For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 96 Chapter 2 Message List iSM07024: Resource monitoring stopped by information collecting failure. (<aaa...a> productID=<bbbbb> SN=<ccccc>) [UC=<dddddddddd> FC=<ee>][_ALERT_] [Classification] ERROR [Explanation] It indicates that state monitoring to disk array (name: aaa...a) has been stopped by information collecting failure. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 97 Chapter 2 Message List iSM07026: Resource monitoring changes to recovery mode.(<aaa...a> productID=<bbbbb> SN=<ccccc>) [UC=<dddddddddd> FC=<ee>][_ALERT_] [Classification] ERROR [Explanation] It indicates that the monitoring for the disk array (name: aaa...a) became impossible to continue due to disk array failure or control path failure, and the system is turned into the monitoring recovery waiting status.
  • Page 98 Chapter 2 Message List iSM07032: Request to stop monitoring resource is waiting for termination of other request. (<aaa...a>) [Classification] INFO [Explanation] It indicates that a state monitoring stop command to disk array (name: aaa...a) is waiting for the end of other command processing. The monitoring of disk array automatically stops after the end of the processing that has been requested.
  • Page 99 Chapter 2 Message List iSM07035: Retrying to start monitoring resource is started. (<aaa...a>) [Classification] INFO [Explanation] It indicates that an attempt has been made to restart state monitoring to disk array (name: aaa...a) that stopped operation due to failure. aaa...a : Disk array name [Measures] Unnecessary...
  • Page 100 Chapter 2 Message List iSM07093: Monitoring function is blockaded. [Classification] ERROR [Explanation] It indicates that state monitoring to the iSM server is blockaded. [Measures] Collect information and restart the iSM server if necessary. For how to collect the information, refer to “Information Gathering Method when Server Fault with Unknown Cause”...
  • Page 101: Bbb

    Chapter 2 Message List iSM07095: Inconsistency of resources information(<aaaaa>) was detected. (<bbb...b> productID=<ccccc> SN=<ddddd>) [Classification] ERROR [Explanation] It indicates that inconsistency of configuration information is detected in resource (aaaaa) of disk array (name: bbb...b). aaaaa : Resource type (LD, etc.) bbb...b : Disk array name ccccc...
  • Page 102 Chapter 2 Message List iSM07101: State of PD(<aa>h) has become ready. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] INFO [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has become ready. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 103 Chapter 2 Message List iSM07102: State of PD(<aa>h) has become fault. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>)[_ALERT_] [Classification] ERROR [Explanation] It indicates that trouble occurred in the physical disk (number: ee-ff) of disk array (name: bbb...b). For Windows, this message is target of ESMPRO Manager Report. : Internal number indicating physical disk type bbb...b : Disk array name...
  • Page 104 Chapter 2 Message List iSM07104: State of PD(<aa>h) has become attn(rebuilding). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>)[_ALERT_] [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is rebuilding data. For Windows, this message is target of ESMPRO Manager Report. : Internal number indicating physical disk type bbb...b : Disk array name...
  • Page 105 Chapter 2 Message List iSM07105: State of PD(<aa>h) has become attn(powering up). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is starting up. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 106 Chapter 2 Message List iSM07106: State of PD(<aa>h) has become attn(formatting). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is being formatted. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 107 Chapter 2 Message List iSM07108: State of PD(<aa>h) has become offline. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] ERROR [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has been in the off line status. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 108 Chapter 2 Message List iSM07109: State of PD(<aa>h) has become ready. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>)[_ALERT_] [Classification] INFO [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has rebuilt data and its status has changed to “ready”. For Windows, this message is target of ESMPRO Manager Report.
  • Page 109 Chapter 2 Message List iSM07111: State of <aaaaa>(<bb>h[-<cc>h]) has become ready. (<ddd...d> productID=<eeeee> SN=<fffff> No=<gg>h ) [Classification] INFO [Explanation] It indicates that the component* (abbreviated name: aaaaa, number: gg) of disk array (name: ddd...d) has become ready. aaaaa : Abbreviated name of component bb-cc : Internal number indicating component type ddd...d...
  • Page 110 Chapter 2 Message List iSM07113: State of <aaaaa>(<bb>h[-<cc>h]) has become offline. (<ddd...d> productID=<eeeee> SN=<fffff> No=<gg>h ) [Classification] ERROR [Explanation] It indicates that the component* (abbreviated name: aaaaa, number: gg) of disk array (name: ddd...d) has become removed (or not existed). aaaaa : Abbreviated name of component bb-cc...
  • Page 111 Chapter 2 Message List iSM07115: State of CHE(<aa>h[-<bb>h]) has become attn(rebuilding). (<ccc...c> productID=<ddd...d> SN=<eee...e> No=<ff>h ) [Classification] NOTICE [Explanation] It indicates that the cache module (number: ff) of a disk array (name: ccc...c) is rebuilding data. aa-bb : Internal number indicating component type ccc...c : Disk array name ddd...d...
  • Page 112 Chapter 2 Message List iSM07121: State of LD has become ready. (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] INFO [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has become ready. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 113 Chapter 2 Message List iSM07123: State of LD has become fault(media error). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e> [PDN=<ff>h-<gg>h])) [_ALERT_] [Classification] ERROR [Explanation] It indicates that trouble (media error) occurred in the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a). For Windows, this message is target of ESMPRO Manager Report.
  • Page 114 Chapter 2 Message List iSM07124: State of LD has become attn(reduce). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] ERROR [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has become a reduced state*. * RAID composition which lost redundancy by PD trouble. aaa...a : Disk array name bbbbb...
  • Page 115 Chapter 2 Message List iSM07126: State of LD has become attn(preventive copy). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that data in the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has been copied into spare disk. aaa...a : Disk array name bbbbb...
  • Page 116 Chapter 2 Message List iSM07128: State of LD has become attn(unformatted). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has been unformatted logically. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 117 Chapter 2 Message List iSM07130: State of LD has become attn(format-fail). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) failed in formatting logically. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 118 Chapter 2 Message List iSM07132: State of LD has become attn(expand-fail). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) failed in logical expansion. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 119 Chapter 2 Message List iSM07141: State of RANK has become ready. (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h ) [Classification] INFO [Explanation] It indicates that the RANK (number: dd-ee) of disk array (name: aaa...a) has become ready. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc : Serial number of disk array...
  • Page 120 Chapter 2 Message List iSM07143: State of RANK has become attn(reduce). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h ) [Classification] ERROR [Explanation] It indicates that the RANK (number: dd-ee) of disk array (name: aaa...a) has become in reduced state. * RAID composition which lost redundancy by PD trouble. aaa...a : Disk array name bbbbb...
  • Page 121 Chapter 2 Message List iSM07145: State of RANK has become attn(preventive copy). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h ) [Classification] NOTICE [Explanation] It indicates that data in the RANK (number: dd-ee) of disk array (name: aaa...a) has been copied into spare disk. aaa...a : Disk array name bbbbb...
  • Page 122 Chapter 2 Message List iSM07147: State of RANK has become attn(expanding). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h ) [Classification] NOTICE [Explanation] It indicates that the rank (number: dd-ee) of disk array (name: aaa...a) is expanding the logic. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 123 Chapter 2 Message List iSM07151: State of PD(<aa>h) has become ready. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] INFO [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has become ready. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 124 Chapter 2 Message List iSM07152: State of PD(<aa>h) has become fault. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [UC=<hhh...h> FC=<ii>] [_ALERT_] [Classification] ERROR [Explanation] It indicates that a trouble occurred in the physical disk (number: ee-ff) of disk array (name: bbb...b). For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 125 Chapter 2 Message List iSM07154: State of PD(<aa>h) has become attn(rebuilding). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [UC=<hhh...h> FC=<ii>] [_ALERT_] [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is rebuilding data. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 126 Chapter 2 Message List iSM07155: State of PD(<aa>h) has become attn(powering up). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is activated. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 127 Chapter 2 Message List iSM07156: State of PD(<aa>h) has become attn(formatting). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is being formatted. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 128 Chapter 2 Message List iSM07158: State of PD(<aa>h) has become offline. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] ERROR [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has been in the off line status. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 129 Chapter 2 Message List iSM07159: State of PD(<aa>h) has become ready. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [UC=<hhh...h> FC=<ii>] [_ALERT_] [Classification] INFO [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has rebuilt data and its status has changed to “ready”. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 130 Chapter 2 Message List iSM07161: State of <aaaaa>(<bb>h[-<cc>h]) has become ready. (<ddd...d> productID=<eeeee> SN=<fffff> No=<gg>h) [Classification] INFO [Explanation] It indicates that the component* (abbreviated name: aaaaa, number: gg) of disk array (name: ddd...d) has become ready. aaaaa : Abbreviated name of component bb-cc : Internal number indicating component type ddd...d...
  • Page 131 Chapter 2 Message List iSM07162: State of <aaaaa>(<bb>h[-<cc>h]) has become fault. (<ddd...d> productID=<eeeee> SN=<fffff> No=<gg>h) [UC=<hhhhhhhhhh> FC=<ii>][_ALERT_] [Classification] ERROR [Explanation] It indicates that trouble occurred in the component* (abbreviated name: aaaaa, number: gg) of disk array (name: ddd...d). For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 132 Chapter 2 Message List iSM07163: State of <aaaaa>(<bb>h[-<cc>h]) has become offline. (<ddd...d> productID=<eeeee> SN=<fffff> No=<gg>h) [Classification] ERROR [Explanation] It indicates that the component* (abbreviated name: aaaaa, number: gg) of disk array (name: ddd...d) has become removed (or not existed). aaaaa : Abbreviated name of component bb-cc : Internal number indicating component type...
  • Page 133 Chapter 2 Message List iSM07165: State of CHE(<aa>h[-<bb>h]) has become attn(rebuilding). (<ccc...c> productID=<ddd...d> SN=<eee...e> No=<ff>h ) [Classification] NOTICE [Explanation] It indicates that cache module (number: ff) of a disk array (name: ccc...c) is rebuilding data. aa-bb : Internal number indicating component type ccc...c : Disk array name ddd...d...
  • Page 134 Chapter 2 Message List iSM07171: State of LD has become ready. (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] INFO [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has become ready. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 135 Chapter 2 Message List iSM07173: State of LD has become fault(media error). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e> [PDN=<ff>h-<gg>h]) [UC=<hhh...h> FC=<ii>][_ALERT_] [Classification] ERROR [Explanation] It indicates that trouble (media error) occurred in the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a). For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 136 Chapter 2 Message List iSM07174: State of LD has become attn(reduce). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] ERROR [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has become a reduced state*. * RAID composition which lost redundancy by PD trouble. aaa...a : Disk array name bbbbb...
  • Page 137 Chapter 2 Message List iSM07176: State of LD has become attn(preventive copy). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that data in the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has been copied into spare disk. aaa...a : Disk array name bbbbb...
  • Page 138 Chapter 2 Message List iSM07178: State of LD has become attn(unformatted). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) has been unformatted logically. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 139 Chapter 2 Message List iSM07180: State of LD has become attn(format-fail). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) failed in formatting logically. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 140 Chapter 2 Message List iSM07182: State of LD has become attn(expand-fail). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that the logical disk (number: dddd, name: eee...e) of disk array (name: aaa...a) failed in logical expansion. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc...
  • Page 141 Chapter 2 Message List iSM07191: State of RANK has become ready. (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h) [Classification] INFO [Explanation] It indicates that the RANK (number: dd-ee) of disk array (name: aaa...a) has become ready. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc : Serial number of disk array dd-ee...
  • Page 142 Chapter 2 Message List iSM07193: State of RANK has become attn(reduce). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h) [Classification] ERROR [Explanation] It indicates that the RANK (number: dd-ee) of disk array (name: aaa...a) has become in reduced state. * RAID composition which lost redundancy by PD trouble. aaa...a : Disk array name bbbbb...
  • Page 143 Chapter 2 Message List iSM07195: State of RANK has become attn (preventive copy). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h) [Classification] NOTICE [Explanation] It indicates that data in the RANK (number: dd-ee) of disk array (name: aaa...a) has been copied into spare disk. This message is output on UNIX system.
  • Page 144 Chapter 2 Message List iSM07197: State of RANK has become attn(expanding). (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h-<ee>h) [Classification] NOTICE [Explanation] It indicates that the rank (number: dd-ee) of disk array (name: aaa...a) is expanding the logic. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc : Serial number of disk array...
  • Page 145 Chapter 2 Message List iSM07201: Disk Array ,named “<aaa...a>”, has renamed to “<bbb...b>”. (SN=<ccccc>) [Classification] INFO [Explanation] It indicates that the name of disk array (name: aaa...a, serial number: ccccc) has been changed to bbb...b. aaa...a : Disk array name bbb...b : New disk array name ccccc...
  • Page 146: Ccc

    Chapter 2 Message List iSM07203: LD ,named “<aaa...a>”, has renamed to “<bbb...b>”. (<ccc...c>No=<dddd>h) [Classification] INFO [Explanation] It indicates that the logical disk (number: dddd) name of disk array (name: ccc...c)has been changed from aaa...a to bbb...b. aaa...a : Old Logical disk name bbb...b : New Logical disk name ccc...c...
  • Page 147 Chapter 2 Message List iSM07206: CHE-Disk has configured.(<aaa...a>) [Classification] NOTICE [Explanation] It indicates that the cache disk configuration of disk array (name: aaa...a) has been changed. aaa...a : Disk array name [Measures] Unnecessary iSM07207: Attribute of PD has changed from <aaaaa>...
  • Page 148 Chapter 2 Message List iSM07211: Renaming Disk Array,named “<aaa...a>”,is failed. (SN=<bbbbb>) [Classification] INFO [Explanation] It indicates that change of disk array names (name: aaa...a, serial number: bbbbb) failed. aaa...a : Disk array name bbbbb : Serial number [Measures] Check result indicated on client screen (dialog) and remove cause of the failure. Then change the names again.
  • Page 149 Chapter 2 Message List iSM07220: SVP information was updated. (<aaa...a> productID=<bbbbb> SN=<ccccc> No=<dd>h) [Classification] INFO [Explanation] It indicates that service processor information (component number: dd) of disk array (name: aaa...a) has been changed. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc : Serial number of disk array : Component number of service processor.
  • Page 150 Chapter 2 Message List iSM07251: Disk Array name “<aaa...a>” exists in others. (productID=<bbbbb> SN=<ccccc>) [Classification] WARNING [Explanation] It indicates that the disk array name (aaa...a) (product ID: bbbbb, serial number: ccccc) is duplicated. aaa...a : Disk array name bbbbb : Product ID of disk array (S2100 Disk Array etc.) ccccc : Serial number of disk array [Measures]...
  • Page 151 Chapter 2 Message List iSM07301: LD_SET,named “<aaa...a>” was added. (<bbb...b>) [Classification] INFO [Explanation] It indicates that LD_SET (name: aaa...a) is added to disk array (name: bbb...b). aaa...a : LD_SET name bbb...b : Disk array name [Measures] Unnecessary iSM07302: LD_SET,named “<aaa...a>” was deleted.
  • Page 152 Chapter 2 Message List iSM07304: PATH, “<aaa...a>” was deleted from LD_SET. (<bbb...b> LD_SET=<ccc...c>) [Classification] INFO [Explanation] It indicates that the path (aaa...a) is deleted from LD_SET (name: ccc...c) of disk array (name: bbb...b). aaa...a : Path aaaa-aaaa-aaaa-aaaa : WWPN aah-aah : Port number bbb...b : Disk array name...
  • Page 153 Chapter 2 Message List iSM07307: PATH, “<aaa...a>” was changed for “<bbb...b>”. (<ccc...c> LD_SET=<ddd...d>) [Classification] INFO [Explanation] It indicates that the path aaa...a to LD_SET (name: ddd...d) of disk array (name: ccc...c) is changed to bbb...b. aaa...a : Old path aaaa-aaaa-aaaa-aaaa : WWPN aah-aah : Port number...
  • Page 154 Chapter 2 Message List iSM07309: LD,named “<aaa...a>”(<bbbb>h) was added to LD_SET. (<ccc...c> LD_SET=<ddd...d>) [Classification] INFO [Explanation] It indicates that the logical disk (name: aaa...a, number: bbbb) is added to LD_SET (name: ddd...d) of disk array (name: ccc...c). aaa...a : Logical disk name bbbb : Logical disk number ccc...c...
  • Page 155 Chapter 2 Message List iSM07311: LD,named “<aaa...a>”(<bbbb>h) was deleted from LD_SET. (<ccc...c> LD_SET=<ddd...d>) [Classification] INFO [Explanation] It indicates that the logical disk (name: aaa...a, number: bbbb) is deleted from LD_SET (name: ddd...d) of disk array (name: ccc...c). aaa...a : Logical disk name bbbb : Logical disk number ccc...c...
  • Page 156 Chapter 2 Message List iSM07314: ACCESS_CONTROL function was stopped. (<aaa...a>) [Classification] INFO [Explanation] It indicates that access control function on disk array (name: aaa...a) has been stopped. aaa...a : Disk array name [Measures] Unnecessary iSM07315: LD_SET, named “<aaa...a>”, has renamed to “<bbb...b>”. (<ccc...c>) [Classification] INFO [Explanation]...
  • Page 157 Chapter 2 Message List iSM07331: Adding a LD_SET, named “<aaa...a>” was failed. (<bbb...b>) [Classification] INFO [Explanation] It indicates that adding the LD_SET (name: aaa...a) to disk array (name: bbb...b) failed. aaa...a : LD_SET name bbb...b : Disk array name [Measures] Identify a cause of fault on the basis of previous and following messages, remove the cause of fault, and then retry processing.
  • Page 158 Chapter 2 Message List iSM07334: Deleting a PATH, named “<aaa...a>” to LD_SET was failed. (<bbb...b> LD_SET=<ccc...c>) [Classification] INFO [Explanation] It indicates that deleting Path (aaa...a) from LD_SET (name: ccc...c) of disk array (name: bbb...b) failed. aaa...a : Path aaaa-aaaa-aaaa-aaaa : WWPN aah-aah : Port number bbb...b...
  • Page 159 Chapter 2 Message List iSM07336: Assigning some of LDs, to LD_SET was failed. (<aaa...a> LD_SET=<bbb...b>) [Classification] INFO [Explanation] It indicates that assigning Logical Disk to LD_SET (name: bbb...b) of disk array (name: aaa...a) failed. aaa...a : Disk array name bbb...b : LD_SET name [Measures] Identify a cause of fault on the basis of previous and following messages, remove...
  • Page 160 Chapter 2 Message List iSM07338: Adding a LD, named “<aaa...a>” (<bbbb>h), to LD_SET was failed. (<ccc...c> LD_SET=<ddd...d> PATH=<eee...e>) [Classification] INFO [Explanation] It indicates that adding Logical Disk (name: aaa...a, number: bbbb) to LD_SET (name: ddd...d) of disk array (name: ccc...c) , Path (eee...e) failed. aaa...a : Logical disk name bbbb...
  • Page 161 Chapter 2 Message List iSM07340: Deleting a LD, named “<aaa...a>” (<bbbb>h), from LD_SET was failed. (<ccc...c> LD_SET=<ddd...d> PATH=<eee...e>) [Classification] INFO [Explanation] It indicates that deleting Logical Disk (name: aaa...a) from LD_SET (name: ddd...d) of disk array (name: ccc...c), Path (eee...e) was failed. aaa...a : Logical disk name bbbb...
  • Page 162 Chapter 2 Message List iSM07342: Changing ACCESS_CONTROL mode was failed. (<aaa...a> No=<bb>h-<cc>h) [Classification] INFO [Explanation] It indicates that changing Port (number: bb-cc) of disk array (name: aaa...a) failed. aaa...a : Disk array name bb-cc : Port number [Measures] Identify a cause of fault on the basis of previous and following messages, remove the cause of fault, and then retry processing.
  • Page 163 Chapter 2 Message List iSM07345: Renaming LD_SET, named “<aaa...a>” was failed. (<bbb...b>) [Classification] INFO [Explanation] It indicates that renaming the LD_SET (name: aaa...a) to disk array (name: bbb...b) failed. aaa...a : LD_SET name bbb...b : Disk array name [Measures] Identify a cause of fault on the basis of previous and following messages, remove the cause of fault, and then retry processing.
  • Page 164 Chapter 2 Message List iSM07402: State of PD(<aa>h) has become info(inactive). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>)[_ALERT_] [Classification] INFO [Explanation] It indicates that trouble occurred in the physical disk (number: ee-ff) of disk array (name: bbb...b). For Windows, this message is target of ESMPRO Manager Report. : Internal number indicating physical disk type bbb...b : Disk array name...
  • Page 165 Chapter 2 Message List iSM07404: State of PD(<aa>h) has become attn(rebuilding). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is rebuilding data. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 166 Chapter 2 Message List iSM07409: State of PD(<aa>h) has become ready. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [Classification] INFO [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has completed rebuilding and become ready. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 167 Chapter 2 Message List iSM07411: State of POOL has become ready. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>) [Classification] INFO [Explanation] It indicates that the pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) has become ready. aaa...a : Disk array name bbb...b : Product ID of disk array (S2800 Disk Array etc.) ccc…c...
  • Page 168 Chapter 2 Message List iSM07413: State of POOL has become attn(reduce). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>) [Classification] ERROR [Explanation] It indicates that the pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) has become a reduced state. aaa...a : Disk array name bbb...b : Product ID of disk array (S2800 Disk Array etc.)
  • Page 169 Chapter 2 Message List iSM07415: State of POOL has become attn(preventive copy). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation It indicates that data in a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) has been copied into a spare disk. aaa...a : Disk array name bbb...b...
  • Page 170 Chapter 2 Message List iSM07452: State of PD(<aa>h) has become info(inactive). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [UC=<hhh...h> FC=<ii>][_ALERT_] [Classification] INFO [Explanation] It indicates that trouble occurred in the physical disk (number: ee-ff) of disk array (name: bbb...b). For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 171 Chapter 2 Message List iSM07454: State of PD(<aa>h) has become attn(rebuilding). (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [UC=<hhh...h> FC=<ii>] [Classification] NOTICE [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) is rebuilding data. : Internal number indicating physical disk type bbb...b : Disk array name ccc...c...
  • Page 172 Chapter 2 Message List iSM07459: State of PD(<aa>h) has become ready. (<bbb...b> productID=<ccc...c> SN=<ddd...d> No=<ee>h-<ff>h <ggg...g>) [UC=<hhh...h> FC=<ii>] [Classification] INFO [Explanation] It indicates that the physical disk (number: ee-ff) of disk array (name: bbb...b) has rebuilt data and its status has changed to “ready”. : Internal number indicating physical disk type bbb...b : Disk array name...
  • Page 173 Chapter 2 Message List iSM07461: State of POOL has become ready. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>) [Classification] INFO [Explanation] It indicates that the pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) has become ready. aaa...a : Disk array name bbb...b : Product ID of disk array (S2800 Disk Array etc.) ccc...c...
  • Page 174 Chapter 2 Message List iSM07463: State of POOL has become attn(reduce). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>) [Classification] ERROR [Explanation] It indicates that the pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) has become a reduced state. aaa...a : Disk array name bbb...b : Product ID of disk array (S2800 Disk Array etc.)
  • Page 175 Chapter 2 Message List iSM07465: State of POOL has become attn(preventive copy). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>) [Classification] NOTICE [Explanation] It indicates that data in a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) has been copied into a spare disk. aaa...a : Disk array name bbb...b...
  • Page 176 Chapter 2 Message List iSM07501: Request is meaningless(already) [Explanation] It indicates that the request for starting or terminating the disk array monitoring has already executed. This message is output on UNIX system. [Measures] Unnecessary iSM07503: Resource table is re-created [Explanation] It indicates that the request is suspended since the disk array configuration is changed.
  • Page 177 Chapter 2 Message List iSM07506: Request cancel [Explanation] It indicates that the request is cancelled since due to disk array failure, etc. This message is output on UNIX system. [Measures] For disk array failure, retry after recovering the disk array. For other cases, retry after investigating the cause from syslog or iSM operation log.
  • Page 178 Chapter 2 Message List iSM07512: Specified disk array is not managed [Explanation] It indicates that the specified disk array name is not managed by the iSM server. This message is output on UNIX system. [Measures] Retry after checking the disk array name. iSM07513: Disk array is busy(configuration) [Explanation] It indicates that the request cannot be executed since the disk array is in the...
  • Page 179 Chapter 2 Message List iSM07552: Invalid parameter has detected. (code=<aaa...a>) [Classification] NOTICE [Explanation] It indicates that invalid parameter has been detected in state monitoring process. aaa...a : Internal error code [Measures] Execute again. If the same phenomenon recurs, investigate the cause with syslog or iSM operation log.
  • Page 180 Chapter 2 Message List iSM07555: System call error has occurred. [func=<aaa...a> errno=<bbb...b>] (code=<ccc...c>) [Classification] NOTICE [Explanation] It indicates that system error occurred in state monitoring process. aaa...a : Function name bbb...c : Error number ccc...c : Internal error code [Measures] Execute again.
  • Page 181 Chapter 2 Message List iSM07601: Attribute of LD has configured. (<aaa...a>) [Classification] NOTICE [Explanation] It indicates that attribute of LD is configured for the disk array (name: aaa...a). aaa...a : Disk array name [Measures] Unnecessary iSM07602: LD movement terminated. (<aaa...a>) [Classification] NOTICE [Explanation]...
  • Page 182 Chapter 2 Message List iSM07616: The capacity of SRA used is over threshold.(<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e> capacity=<fff...f>GB threshold=<ggg...g>GB) [Classification] WARNING [Explanation] It indicates that the used capacity of snapshot reserve area (number: dddd and name: eee...e) in disk array (name: aaa...a) exceeded specified threshold values. For Windows, this message is target of ESMPRO Manager Report.
  • Page 183 Chapter 2 Message List iSM07617: The capacity of SRA used is under threshold.(<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e> capacity=<fff...f>GB threshold=<ggg...g>GB) [Classification] INFO [Explanation] It indicates that the used capacity of pool (number: dddd and name: eee...e) in disk array (name: aaa...a) fell below specified threshold values. aaa...a : Disk array name bbb...b...
  • Page 184 Chapter 2 Message List iSM07620: Expansion State of POOL has become normal-end. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>)[_ALERT_] [Classification] INFO [Explanation] It indicates that capacity expansion of a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) normally ended. For Windows, this message is target of ESMPRO Manager Report.
  • Page 185 Chapter 2 Message List iSM07622: Expansion State of POOL has become expand-fail. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>)[_ALERT_] [Classification] ERROR [Explanation] It indicates that capacity expansion of a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) failed. For Windows, this message is target of ESMPRO Manager Report. aaa...a : Disk array name bbb...b...
  • Page 186 Chapter 2 Message List iSM07670: Expansion State of POOL has become normal-end. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>)[ UC=<fff...f> FC=<gg>][_ALERT_] [Classification] INFO [Explanation] It indicates that capacity expansion of a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) normally ended. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 187 Chapter 2 Message List iSM07671: Expansion State of POOL has become expanding. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>)[ UC=<fff...f> FC=<gg>][_ALERT_] [Classification] NOTICE [Explanation] It indicates that the capacity of a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) is being expanded. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 188 Chapter 2 Message List iSM07672: Expansion State of POOL has become expand-fail. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e>)[ UC=<fff...f> FC=<gg>][_ALERT_] [Classification ERROR [Explanation] It indicates that capacity expansion of a pool (number: dddd, name: eee...e) of a disk array (name: aaa...a) failed. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 189 Chapter 2 Message List iSM07950: Illegal write data has been detected. (<aaa...a>, LD=<bbb...b>(<cccc>h), host-info=<ddd...d>) [Classification] WARNING [Explanation] It indicates that an invalid write request on disk array was detected by data retention function. aaa...a : Name of disk array that detected invalid write request. bbb...b : Name of logical disk that detected invalid write request.
  • Page 190 Chapter 2 Message List iSM08000∼ iSM08020: Disk array=<aaa...a> logging is started interval=<bb> [Classification] INFO [Explanation] It indicates that data accumulation started on statistic information history file. aaa...a : Disk array name : Accumulation interval (minute) [Measures] Unnecessary iSM08021: Disk array=<aaa...a> logging is stopped [Classification] INFO...
  • Page 191 Chapter 2 Message List iSM08030: Disk array=<aaa...a> logging is already started [Classification] NOTICE [Explanation] It indicates that accumulation into statistics information history file has already been started. aaa...a : Disk array name [Measures] Check whether the specified disk array name is correct. iSM08031: Disk array=<aaa...a>...
  • Page 192 Chapter 2 Message List iSM08033: Disk array=<aaa...a> does not exist [Classification] NOTICE [Explanation] The following status is indicated. (1) The specified disk array does not exist. (2) PerformanceMonitor has not been purchased for specified disk array aaa...a : Disk array name [Measures] Specify the correct disk array name.
  • Page 193 Chapter 2 Message List iSM08036: Disk array=<aaa...a> is overload [Classification] NOTICE [Explanation] It indicates that accumulation of statistics information cannot be started due to the following causes. (1) There are so many disk array components that statistic information cannot be collected by specified logging interval. (2) The disk array is failed.
  • Page 194 Chapter 2 Message List iSM08050: Performance data is over threshold (disk array=<aaa...a> [, type=<bbbb>] [, number=<cccc>] : <dddddddd> <value =<eee...e> (<ffff>), threshold=<ggg...g>(<ffff>)>) [Classification] WARNING [Explanation] Performance data of components in disk array exceeded specified threshold values. aaa...a : Disk array name bbbb : Calculation unit PORT...
  • Page 195 Chapter 2 Message List iSM08052: Threshold monitoring condition has changed interval=<aa>(<bbb>) border=<ccc> [Classification] NOTICE [Explanation] It indicates that threshold monitoring conditions have been changed. : Threshold monitoring interval : Unit of threshold monitoring interval (min or sec) : Minimum number of I/Os [Measures] Unnecessary iSM08053: Condition to reset threshold excess...
  • Page 196 Chapter 2 Message List iSM08054: Threshold excess state has been reset [Disk array=<aaa...a>][type=<bbbb>][numb er=<cccc>][<<dddddddd>>] [Classification] NOTICE [Explanation] Threshold excess status has been released automatically. aaa...a : Disk array name bbbb : Calculation unit PORT : Port CHESEG : Cache segment : Logical Disk : Physical Disk cccc...
  • Page 197 Chapter 2 Message List iSM08056: Restoration of threshold monitoring object failed ([disk array=<aaa...a>] [func=<bbb...b>] [errno=<cccc>] [detcode=<dddddddd>]) [Classification] WARNING [Explanation] It indicates that restoration of threshold value failed. aaa...a : Disk array name bbb...b : Name of function in which an error occurred. cccc : Error number dddddddd...
  • Page 198 Chapter 2 Message List iSM08060: Psl file {open|access|close} error func=<aaa...a> errno=<bbbb> detcode=<cccccccc> file=<ddd...d> [Classification] WARNING [Explanation] It indicates that error occurred in open/access/close of statistics information history file. aaa...a : Function name with error. bbbb : Error number cccccccc : Detail code of error ddd...d : File name The followings are the main reasons for this message output.
  • Page 199 Chapter 2 Message List iSM08062: Psl file name is over max value [Classification] WARNING [Explanation] It indicates that file name of statistics information history file has been over the maximum value. [Measures] Review the file name of statistics information history file or the storage directory.
  • Page 200 Chapter 2 Message List iSM08071: Change directory failed dirname=<aaa...a> errno=<bbbb> detcode=<cccccccc> [Classification] NOTICE [Explanation] It indicates that it failed to change the directory. aaa...a : Directory name bbbb : Error code cccccccc : Detail code [Measures] Remove the cause of trouble and restart the iSM server. iSM08072: Insufficient resource detected func=<aaa...a>...
  • Page 201 Chapter 2 Message List iSM08092: To get performance data failed from disk array=<aaa...a> type=<bbb...b> number=<cccc> detcode=<dddddddd> [Classification] NOTICE [Explanation] It indicates that I/O error occurred in disk array collecting statistics information. aaa...a : Disk array name bbb...b : Type of failed information SYSTEM (MNT) : Maintenance information of disk array SYSTEM (INQ) : Attribute information of disk array : Statistics information of HD...
  • Page 202 Chapter 2 Message List iSM08094: System call error occurred func=<aaa...a> errno=<bbbb> detcode=<cccccccc> [Classification] NOTICE [Explanation] It indicates that abnormalities occurred in iSM server operation. aaa...a : Function name bbbb : Error code cccccccc : Detail code [Measures] Restart iSM server. iSM08099: Program error occurred detcode=<aaaaaaaa>...
  • Page 203 Chapter 2 Message List iSM08181: Specified value is the same as current value(<a> times/minute) [Classification] NOTICE [Explanation] The specified value is same as current display refresh rate. The command will be ignored. : Specified refresh rate [Measures] Unnecessary iSM08182: Can’t change display refresh rate(<aaa...a>:<bbb...b>) [Classification] NOTICE...
  • Page 204 Chapter 2 Message List iSM08183: Specified value is not allowed as display refresh rate(<a> times/minute) [Classification] NOTICE [Explanation] The specified value is not allowed as a display refresh rate. : Specified refresh rate [Measures] Review the specified value. iSM08201: Illegal performance data was received from disk array=<aaa...a>...
  • Page 205 Chapter 2 Message List iSM08900: Process busy when terminate emergency. unexpected error message maybe generated. [Classification] WARNING [Explanation] The performance monitoring instructed emergency stop. However, process could not be stopped immediately. This message is output on Windows system. [Measures] Unnecessary...
  • Page 206 Chapter 2 Message List iSM09000 ∼ iSM09001: System call error occurred func=<aaa...a> errno=<bbbb> detcode=<cccccccc> [Classification] NOTICE [Explanation] It indicates that an error occurred in iSM server operation. aaa...a : Function name bbbb : Error code cccccccc : Detail code [Measures] Restart iSM server.
  • Page 207 Chapter 2 Message List iSM09003: LD movement from <aaaa>(<bbb...b>) to <cccc>(<ddd...d>) in <eee...e> <fff...f> [Classification] NOTICE [Explanation] It indicates that the logical disk movement process has been completed. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc : Logical disk number of work disk for Optimization ddd...d...
  • Page 208 Chapter 2 Message List iSM09004: Changed LD movement speed from <aaaa>(<bbb...b>) to <cccc>(<ddd...d>) in <eee...e> [Classification] NOTICE [Explanation] It indicates that the logical disk movement speed is changed. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc : Logical disk number of work disk for Optimization ddd...d...
  • Page 209 Chapter 2 Message List iSM09006: Failed in communication with <aaaa> func=<bbb...b> errno=<cccc> detcode=<dddddddd> [Classification] NOTICE [Explanation] It indicates that an error has occurred on the internal communication process. aaaa : Communication target bbb...b : Function name cccc : Error code dddddddd : Detail code [Measures]...
  • Page 210 Chapter 2 Message List iSM09008: Make directory failed dirname=<aaa...a> func=<bbb...b> errno=<cccc> detcode=<dddddddd> [Classification] NOTICE [Explanation] It indicates that it has failed to create the directory. aaa...a : Directory name bbb...b : Function name cccc : Error code dddddddd : Detail code [Measures] Remove the cause of the error and restart the iSM server.
  • Page 211 Chapter 2 Message List iSM09010: Request of start LD movement from <aaaa>(<bbb...b>) to <cccc>(<ddd...d>) in <eee...e> is rejected detcode=<ffffffff> [Classification] NOTICE [Explanation] It indicates that the request to move the logical disk was rejected. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc...
  • Page 212 Chapter 2 Message List iSM09012: Request of change LD movement speed from <aaaa>(<bbb...b>) to <cccc>(<ddd...d>) in <eee...e> is rejected detcode=<ffffffff> [Classification] NOTICE [Explanation] It indicates that the request to change the logical disk movement speed was rejected. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc...
  • Page 213 Chapter 2 Message List iSM09014: Failed in termination of LD movement from <aaaa>(<bbb...b>) to <cccc>(<ddd...d>) in <eee...e> detcode=<ffffffff> [Classification] NOTICE [Explanation] It indicates that the attempt to terminate the logical disk movement process failed. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc...
  • Page 214: Ddd

    Chapter 2 Message List iSM09016: The schedule of LD movement from <aaaa>(<bbb...b>) to <cccc> (<ddd...d>) in <eee...e> registered. schedule time=<ffff>/<gg>/<hh> <ii>:<jj> range=<kk> [Classification] NOTICE [Explanation] It indicates that moving schedule of logical disks has been registered. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc...
  • Page 215 Chapter 2 Message List iSM09018: The schedule of LD movement from <aaaa>(<bbb...b>) to <cccc> (<ddd...d>) in <eee...e> deleted. [Classification] NOTICE [Explanation] It indicates that moving schedule of registered logical disks has been canceled. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc...
  • Page 216 Chapter 2 Message List iSM09020: The schedule of LD movement from <aaaa>(<bbb...b>) to <cccc> (<ddd...d>) in <eee...e> changed. schedule time=<ffff>/<gg>/<hh> <ii>:<jj> range=<kk> [Classification] NOTICE [Explanation] It indicates that moving schedule of registered logical disks has been changed. aaaa : Logical disk number of moved material logical disk bbb...b : Logical disk name of moved material logical disk cccc...
  • Page 217 Chapter 2 Message List iSM09022: Failed to start the scheduled LD movement from <aaaa>(<bbb...b>) to <cccc>(<ddd...d>) in <eee...e>. detcode=<ffffffff> [Classification] NOTICE [Explanation] It indicates that a logical disk to which the moving schedule has been registered cannot be started to move within the re-execution continuing time, or that it cannot be started to move because its configuration is changed.
  • Page 218 Chapter 2 Message List iSM09101: Bsl file open failed func=<aaa...a> errno=<bbbb> detcode=<cccccccc> filename=<ddd...d> [Classification] WARNING [Explanation] Failed to open the Bsl file. aaa...a : Function name bbbb : Error code cccccccc : Detail code ddd...d : Bsl file name [Measures] Check the Bsl file and the file system, remove the cause of the error and restart the iSM server.
  • Page 219 Chapter 2 Message List iSM09103: Bsl file rename failed func=<aaa...a> errno=<bbbb> detcode=<cccccccc> filename=<ddd...d> [Classification] WARNING [Explanation] Failed to change the Bsl file name. aaa...a : Function name bbbb : Error code cccccccc : Detail code ddd...d : Bsl file name [Measures] Check the Bsl file and the file system, remove the cause of the error and restart the iSM server.
  • Page 220 Chapter 2 Message List iSM09105: Bsl file seek failed func=<aaa...a> errno=<bbbb> detcode=<cccccccc> [rankno=<dddd>] filename=<eee...e> [Classification] WARNING [Explanation] Seek in the Bsl file failed. aaa...a : Function name bbbb : Error code cccccccc : Detail code dddd : RANK number of the data that could not be positioned eee...e : Bsl file name [Measures]...
  • Page 221 Chapter 2 Message List iSM09107: Bsl file close failed func=<aaa...a> errno=<bbbb> detcode=<cccccccc> filename=<ddd...d> [Classification] WARNING [Explanation] Failed to close the Bsl file. aaa...a : Function name bbbb : Error code cccccccc : Detail code ddd...d : Bsl file name [Measures] Check the Bsl file and the file system, remove the cause of the error and restart the iSM server.
  • Page 222 Chapter 2 Message List iSM10000 ∼ iSM10001: comm error: main sc=<aaa>h ec=<bbb...b>h [Classification] NOTICE [Explanation] It indicates that it failed in connection/disconnection to iSM server. : Code indicating location of error bbb...b : Error code [Measures] Check whether abnormalities have occurred in the configuring process on the iSM server machine and restart the iSM server.
  • Page 223 Chapter 2 Message List iSM10040: func error: main sc=<aaa>h ec=<bbb...b>h [Classification] NOTICE [Explanation] It indicates that abnormal termination occurred in the state monitoring function of replication management. : Code indicating location of error bbb...b : Error code [Measures] Check whether abnormalities have occurred in the configuring process on the iSM server machine and restart the iSM server.
  • Page 224 Chapter 2 Message List iSM10102: comm error: Agent sc=<aaa>h ec=<bbb...b>h [Classification] NOTICE [Explanation] It indicates that it failed to process the telegram receiving from disk array. : Code indicating location of error bbb...b : Error code [Measures] Check whether abnormalities have occurred in the configuring process on the iSM server.
  • Page 225 Chapter 2 Message List iSM10106: DiskArrayName(=<aaa...a>) has changed [Classification] NOTICE [Explanation] Specified disk array name has been changed. aaa...a : Disk array name [Measures] Check whether the disk array name hasn’t been changed. Specify the newest one. iSM10200: comm error: client sc=<aaa>h ec=<bbb...b>h [Classification] NOTICE...
  • Page 226 Chapter 2 Message List iSM10210: comm error: client sc=<aaa>h ec=<bbb...b>h [Classification] NOTICE [Explanation] It indicates that the telegram message contained an abnormality. : Code indicating location of error bbb...b : Error code [Measures] Failed in communication process with iSM client. If it is a transient failure, check whether abnormalities have occurred in the connection environment between iSM server and iSM client and connect again.
  • Page 227 Chapter 2 Message List iSM10302: command: <aaa...a>, <bbb...b>, status=failed (<cc>h/<dd>h/<ee>h) [Classification] INFO [Explanation] It indicates that it failed in accessing the disk array (failure of SCSI protocol). aaa...a : Command name bbb...b : Disk array name : Sense Key defined in SCSI specification : Additional Sense Code defined in SCSI specification : Additional Sense Code Qualifier defined in SCSI specification [Measures]...
  • Page 228: Eee

    Chapter 2 Message List iSM10304: command: <aaa...a>, <bbb...b>=<ccc...c> (<dddd>h) <eee...e>, status=failed (<ff>h/<gg>h/<hh>h) [Classification] INFO [Explanation] It indicates that it failed in accessing the volume expressed in logical disk name (failure of SCSI protocol). aaa...a : Command name bbb...b : Volume classification ccc...c : Logical disk name dddd...
  • Page 229 Chapter 2 Message List iSM10306: command: <aaa...a>, volume=<bbbb>h <ccc...c>, status=failed (ec=<ddd...d>) [Classification] INFO [Explanation] It indicates that it failed in accessing the volume expressed in volume number (failure except for SCSI protocol). aaa...a : Command name bbbb : Logical disk number ccc...c : Disk array name ddd...d...
  • Page 230 Chapter 2 Message List iSM10308: command: <aaa...a>, mv=<bbb...b> (<cccc>h) <ddd...d>, rv=<bbb...b> (<cccc>h) <ddd...d>, status=failed (<ee>h/<ff>h/<gg>h) [Classification] INFO [Explanation] It indicates that it failed in accessing the pair expressed in MV or RV (failure of SCSI protocol). aaa...a : Command name bbb...b : Logical disk name cccc...
  • Page 231 Chapter 2 Message List iSM10310: command: <aaa...a>, <bbb...b>= <ccc...c> (<dddd>h) <eee...e> [Classification] NOTICE [Explanation] It indicates that setting operation to volume expressed in logical disk name has been executed. aaa...a : Command name bbb...b : Volume classification ccc...c : Logical disk name dddd : Logical disk number eee...e...
  • Page 232 Chapter 2 Message List iSM10312: command: <aaa...a>, mv=<bbb...b> (<cccc>h) <ddd...d>, rv=<bbb...b> (<cccc>h) <ddd...d> [Classification] NOTICE [Explanation] It indicates that setting operation to the pair expressed in MV or RV has been executed. aaa...a : Command name bbb...b : Logical disk name cccc : Logical disk number ddd...d...
  • Page 233 Chapter 2 Message List iSM10314: Logical Disks were paired: mv=<aaa...a>(<bbbb>h) <ccc...c> , rv=<aaa...a>(<bbbb>h) <ccc...c> [, several states changed.] [Classification] NOTICE [Explanation] It indicates that paired volumes were detected. If two or more state transitions occurred within a polling interval and the midway states could not be identified, “several states changed”...
  • Page 234 Chapter 2 Message List iSM10316: Replication state of pair was changed: mv=<aaa...a>(<bbbb>h) <ccc...c>, Activity State=<ddd...d>, Sync State=<eee...e>, Copy Control State=<fff...f>, rv=<aaa...a> (<bbbb>h) <ccc...c>[, Activity State= <ddd...d>, Sync State=<eee...e>, Copy Control State=<fff...f>][,several states changed.] [Classification] NOTICE [Explanation] It indicates that change of replication state (Replicate/Restore/Separate, etc.) of paired volume was detected.
  • Page 235 Chapter 2 Message List fff...f : Copy control state normal suspend : Copy suspending abnormal suspend : Copy fault suspending background copy : Background copy foreground(sync) : Foreground copy (synchronous) foreground(semi) : Foreground copy (semi-synchronous) Invalid : Invalid [Measures] Unnecessary iSM10317: command: <aaa...a>, LD=<bbb...b>...
  • Page 236 Chapter 2 Message List iSM10318: Replication state of Logical Disk was changed: LD=<aaa...a>(<bbbb>h) <ccc...c>, Restriction=<ddd...d> [,several states changed.] [Classification] NOTICE [Explanation] It indicates that change of logical disk status was detected. If two or more state transitions occurred within a polling interval and the midway states could not be identified, “several states changed”...
  • Page 237 Chapter 2 Message List iSM10321: command: <aaa...a>, ATgroup=<bbb...b> <ccc...c> [, classification=<ddd...d>][, New ATgroup Name=<eee...e>][, Mode=<fff...f>, Copy Mode=<ggg...g>][, Restriction=<hhh...h>] [Classification] NOTICE [Explanation] It indicates that a command related to AT-group was executed. aaa...a : Name of the executed command create ATgroup AT-group creation delete ATgroup AT-group deletion...
  • Page 238 Chapter 2 Message List hhh...h : RV access restriction <R/W Permit | Read Only> [Measures] Unnecessary iSM10322: command: <aaa...a>, ATgroup=<bbb...b> <ccc...c>, LD=<ddd...d>(<eeee>h) [Classification] NOTICE [Explanation] It indicates that a command related to AT-group was executed. aaa...a : Name of the executed command enter volume for group Add volume (pair) into AT-group.
  • Page 239 Chapter 2 Message List iSM10323: ATgroup created: ATgroup=<aaa...a> <bbb...b>, classification=<ccc...c>, Mode=<ddd...d>, Copy Mode=<eee...e>, ATgroup State =<fff...f>, Sync State=<ggg...g>, Volume Number=<hhhh>[, several states changed.] [Classification] NOTICE [Explanation] It indicates that an AT-group has been newly created. aaa...a : AT-group (concentrator) name bbb...b : Disk array name ccc...c...
  • Page 240 Chapter 2 Message List Rst/suspend Restore suspend state Invalid Invalid hhhh : Number of the registered volumes [Measures] Unnecessary iSM10324: ATgroup deleted: ATgroup=<aaa...a> <bbb...b>, classification=<ccc...c> [Classification] NOTICE [Explanation] It indicates that an AT-group has been deleted. aaa...a : AT-group (concentrator) name bbb...b : Disk array name ccc...c...
  • Page 241 Chapter 2 Message List iSM10325: Replication state of ATgroup was changed: ATgroup=<aaa...a> <bbb...b>, classification=<ccc...c>[, New ATgroup Name =<ddd...d>], Mode=<eee...e>, Copy Mode=<fff...f>, ATgroup State=<ggg...g>, Sync State=<hhh...h>, Volume number=<iiii>[, several states changed.] [Classification] NOTICE [Explanation] It indicates that the state of an AT-group has been changed. If two or more state transitions occurred within a polling interval and the midway states could not be identified, “several states changed”...
  • Page 242 Chapter 2 Message List Separated Separated state Rpl/start Replicate start state Rpl/exec Replicate execution state Rpl/sync Replicate synchronous Rpl/suspend Replicate suspend state Rst/exec Restore execution state Rst/suspend Restore suspend state Invalid Invalid iiii : Number of the registered volumes [Measures] Unnecessary iSM10330: inconsistency of product revision of diskarray: mv=<aaa...a>, rv=<aaa...a>...
  • Page 243 Chapter 2 Message List iSM10331: command: <aaa...a>, ATgroup(concentrator)=<bbbb>h <ccc...c> [<ddd...d>], status=failed(<ee>h/<ff>h/<gg>h) [Classification] INFO [Explanation] It indicates that access to the concentrator indicated by the concentrator number failed (SCSI protocol failure). aaa...a : Command name bbbb : AT-group (concentrator) number ccc...c : Disk array name of AT-group (concentrator) ddd...d : Disk array name of AT-group (distributor) (Output if fixed)
  • Page 244 Chapter 2 Message List iSM10332: command: <aaa...a>, ATgroup(distributor)=<bbbb>h <ccc...c> [<ddd...d>], status=failed(<ee>h/<ff>h/<gg>h) [Classification] INFO [Explanation] It indicates that access to the distributor indicated by the distributor number failed (SCSI protocol failure). aaa...a : Command name bbbb : AT-group (distributor) number ccc...c : Disk array name of AT-group (distributor) ddd...d : Disk array name of AT-group (concentrator)
  • Page 245 Chapter 2 Message List iSM10334: command: <aaa...a>, ATgroup(distributor)=<bbbb>h <ccc...c> [<ddd...d>], status=failed(ec=<eee...e>) [Classification] INFO [Explanation] It indicates that access to the distributor indicated by the distributor number failed (failure except for SCSI protocol). aaa...a : Command name bbbb : AT-group (distributor) number ccc...c : Disk array name of AT-group (distributor) ddd...d...
  • Page 246 Chapter 2 Message List iSM10401: copy error:mv=<aaa...a>(<bbbb>h) <ccc...c>, rv=<aaa...a>(<bbbb>h) <ccc...c>, status=<ddd...d>h [,ATgroup=<eee...e>] [UC=<fff...f> FC=<gg>][_ALERT_] [Classification] ERROR [Explanation] It indicates the information of volume in which copy fault occurred. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 247 Chapter 2 Message List iSM10402: link error:Disk Array=<aaa...a>, linkno=<bbb...b>, portno=<ccc...c>, state=<ddd...d>h [Classification] WARNING [Explanation] It indicates that a fault, freeze, or checking state has occurred in the link between disk arrays. For Windows, this message is target of ESMPRO Manager Report. aaa...a : Disk array name bbb...b...
  • Page 248 Chapter 2 Message List iSM10403: Disk array info (<aaa...a> S/N=<bbb...b> Product-ID=<ccc...c>) [UC=<ddd...d> FC=<ee>][_ALERT_] [Classification] ERROR [Explanation] It indicates additional information of disk array in which copy fault occurred. For the pair composed by RemoteDataReplication, additional information of disk array of each of MV and RV is output. For Windows, this message is target of ESMPRO Manager Report, and also to be target of ALIVE/Express Report via ESMPRO.
  • Page 249 Chapter 2 Message List iSM10411: comm error:report event type=<aaaaaaaa>h, ec=<bbb...b>h [Classification] NOTICE [Explanation] It indicates that it failed in receiving telegram from iSM server. aaaaaaaa : Telegram code which indicates the telegram that occurred abnormality bbb...b : Error code [Measures] Check whether abnormalities have occurred in the configuring process on the iSM server.
  • Page 250 Chapter 2 Message List iSM10440: func error:report sc=<aaa>h, ec=<bbb...b>h [Classification] NOTICE [Explanation] It indicates that it failed in the transmission of trouble report to iSM client. : Code indicating location of error bbb...b : Error code [Measures] Check whether abnormalities have occurred in the configuring process on the iSM server.
  • Page 251 Chapter 2 Message List iSM10503: array state error:status=<aaa...a> [Classification] ERROR [Explanation] It indicates that it failed to refer to information due to the device status. aaa...a : Device status [Measures] Check the device status and re-execute. iSM10504: acquire information error:status=<a> [Classification] ERROR [Explanation]...
  • Page 252 Chapter 2 Message List iSM10900: Process is busy when it terminates emergency. Unexpected error message maybe generated. [Classification] WARNING [Explanation] It indicates that the replication management received a request for emergency stop, but could not terminate the process immediately. [Measures] Unnecessary...
  • Page 253 Chapter 2 Message List iSM11000 ∼ iSM11100: Command completed successfully. [Classification] INFO [Explanation] Command execution succeeded. [Measures] Unnecessary iSM11101: Setup of the Disk Array Subsystem is done according to specified parameter. (<aaa...a>) [Classification] INFO [Explanation] Setting of the disk array is executed according to the specified parameter. aaa...a : Additional information [Measures]...
  • Page 254 Chapter 2 Message List iSM11103: Specified Disk Array Subsystem is monitored by iSM. (Under processing to stop monitoring.. ) [Classification] INFO [Explanation] Specified disk array is being monitored by iSM server though monitoring stop process is being executed. [Measures] Stop monitoring disk array and execute it again. iSM11104: Disk Array Subsystem ‘<aaa...a>’...
  • Page 255 Chapter 2 Message List iSM11106: The start of the configuration operation was notified to Disk Array Subsystem. [Classification] INFO [Explanation] Start of configuration operation was notified to the disk array. [Measures] Unnecessary iSM11107: The end of the configuration operation was notified to Disk Array Subsystem.
  • Page 256 Chapter 2 Message List iSM11109: <aaa...a> was terminated. [Classification] INFO [Explanation] aaa...a (iSMconf,iSMautobind) was terminated. aaa...a : Program name [Measures] Unnecessary iSM11110: Command completed abnormally. [Classification] INFO [Explanation] With “All information” option selected, failed in obtaining (a part of) information about disk array. [Measures] Check the status of the disk array.
  • Page 257 Chapter 2 Message List iSM11153: Cannot establish the communication path. [Classification] INFO [Explanation] Communication pass cannot be established. [Measures] Check whether iSMsvr has started. iSM11154: Failed to request notification for start of <aaa...a>. [Classification] INFO [Explanation] It failed in notifying the request for start of aaa...a. aaa...a : Program name [Measures]...
  • Page 258 Chapter 2 Message List iSM11162: Disk Array Subsystem which can be operated by this program is not found. [Classification] INFO [Explanation] No such disk array as is an object of support of iSM can be found. [Measures] Terminate the program. Check that the iSM server covers the disk array as monitoring target, and also check the environmental definition of the iSM server and the connection with the disk array.
  • Page 259 Chapter 2 Message List iSM11171: PD group doesn’t exist. [Classification] INFO [Explanation] PD group does not exist. [Measures] Check the status of the disk array. iSM11172: RANK doesn’t exist. [Classification] INFO [Explanation] RANK does not exist [Measures] Check the status of the disk array. iSM11173: LD doesn’t exist.
  • Page 260 Chapter 2 Message List iSM11175: PORT doesn’t exist. [Classification] INFO [Explanation] PORT does not exist. [Measures] Check the status of the disk array. iSM11176: Permitted PORT for LD doesn’t exist. [Classification] INFO [Explanation] Port with access permission (to LD) does not exist. [Measures] Check the status of the disk array.
  • Page 261 Chapter 2 Message List iSM11180: Specified option is not supported by specified disk array subsystem. [Classification] INFO [Explanation] The specified option is not supported by the specified disk array. [Measures] Specify a disk array which supports the information of the specified option. iSM11182: Pool doesn’t exist.
  • Page 262 Chapter 2 Message List iSM11220: Port #<aa>h-<bb>h was selected. [Classification] INFO [Explanation] Port aa-bb was selected. aa-bb : Port number [Measures] Unnecessary iSM11221: View Host Permit List was selected. [Classification] INFO [Explanation] View host permit list was selected. [Measures] Unnecessary iSM11222: View LD Assign List was selected.
  • Page 263 Chapter 2 Message List iSM11231: Port configuration is required. [Classification] INFO [Explanation] Port configuration is needed. [Measures] Execute it after selecting the port. iSM11232: Cannot set Access Control function. Cross call function should be working for using Access Control function. It is set up from the main menu.
  • Page 264 Chapter 2 Message List iSM11234: Corresponding LD is not found. [Classification] INFO [Explanation] Corresponding LD cannot be found. [Measures] Check the status of the disk array. iSM11235: Effective LD without being in List. [Classification] INFO [Explanation] A nonexistent logical disk was specified. [Measures] Specify a logical disk that exists.
  • Page 265 Chapter 2 Message List iSM11240: PDG #<aa>h was selected. [Classification] INFO [Explanation] PDG aa was selected. : PDG number [Measures] Unnecessary iSM11241: Cannot set up LD, because number of PD is not sufficient. [Classification] INFO [Explanation] LD cannot be set because the number of PD is insufficient. [Measures] Check the status of the disk array.
  • Page 266 Chapter 2 Message List iSM11251: Failed to open a file. [Classification] INFO [Explanation] It failed in opening a file. [Measures] Check the content of the file. iSM11252: Succeeded in loading a file. [Classification] INFO [Explanation] It succeeded in loading a file. [Measures] Unnecessary iSM11253: Illegal file parameter.
  • Page 267 Chapter 2 Message List iSM11257: Succeeded in saving a file. [Classification] INFO [Explanation] It succeeded in saving a file. [Measures] Unnecessary iSM11258: Failed to save a file. [Classification] INFO [Explanation] It failed in saving a file. [Measures] Check whether the specification of the file name and the save destination are correct.
  • Page 268 Chapter 2 Message List iSM11305: IMPORTANT NOTICE: Stop IO access to this Disk Array Subsystem from the host before executing this command which has parameter of “all” or “High Reliability Mode : off”. Otherwise the data in LD may be destroyed.
  • Page 269 Chapter 2 Message List iSM11308: ATTENTION: PD Recovery History data will be deleted. [Classification] INFO [Explanation] Attention: PD Recovery History data will be deleted. [Measures] Unnecessary iSM11309: ATTENTION: Internal Log data will be deleted. [Classification] INFO [Explanation] ATTENTION: Internal Log data will be deleted. [Measures] Unnecessary iSM11310: ATTENTION: Media Error List data...
  • Page 270 Chapter 2 Message List iSM11320: LD capacity which is bound will be <aa> MB. [Classification] INFO [Explanation] LD capacity which is bound will become aa MB. : LD capacity [Measures] Unnecessary iSM11321: System space of 2MB is added to LD, and LD is bound.
  • Page 271 Chapter 2 Message List iSM11323: Cannot bind LD by specified RANK. (unsupported RAID type/unsupported stripe size) [Classification] INFO [Explanation] LD cannot be bound in the specified RANK (unsupported RAID type/unsupported stripe size). [Measures] Check the status of RANK. iSM11330: Failed to get Disk Array Subsystem information.
  • Page 272 Chapter 2 Message List iSM11361: Specified LD is not found. [Classification] INFO [Explanation] Specified LD cannot be found. [Measures] Check the status of the disk array. iSM11362: Failed to bind RANK. [Classification] INFO [Explanation] It failed in binding RANK. [Measures] Check the status of the disk array.
  • Page 273 Chapter 2 Message List iSM11365: Specified PD doesn’t exist. [Classification] INFO [Explanation] Specified PD does not exist. [Measures] Check the status of the disk array. iSM11366: Specified RANK doesn’t exist. [Classification] INFO [Explanation] Specified RANK does not exist. [Measures] Check the status of the disk array. iSM11367: Specified Hot Spare doesn’t exist.
  • Page 274 Chapter 2 Message List iSM11370: Failed to read F/W file. [Classification] INFO [Explanation] It failed in reading F/W file. [Measures] Check whether the path and name of specified F/W file is normal. iSM11372: Disk Array Subsystem is not found. [Classification] INFO [Explanation] Disk array cannot be found.
  • Page 275 Chapter 2 Message List iSM11375: The directory may have been deleted or changed. Please specify file name by absolute path. [Classification] INFO [Explanation] The directory may have been deleted or changed. Specify the file name by absolute path. [Measures] Unnecessary iSM11376: Cannot bind LD, because number of LD exceeds the range that can be specified.
  • Page 276 Chapter 2 Message List iSM11378: Not enough space to bind LD. [Classification] INFO [Explanation] Space to bind LD is insufficient. [Measures] Check the space of RANK. iSM11379: Not enough space to bind LD. Only <aa> LDs be able to be bound. [Classification] INFO [Explanation]...
  • Page 277 Chapter 2 Message List iSM11382: <aa> LDs was bound successfully. But some LDs failed to bind. [Classification] INFO [Explanation] It succeeded to bind aa number of LDs, but it failed in binding some LDs. : Number of LD which has already been bound [Measures] Check the status of RANK.
  • Page 278 Chapter 2 Message List iSM11385: The following <aaa...a> didn’t download. [Classification] INFO [Explanation] The following aaa...a was not downloaded. aaa...a : Download resource name [Measures] Check the status of the disk array and download only the unexecuted one. iSM11402: Auto assignment was selected. (<aaa...a>) [Classification] INFO...
  • Page 279 Chapter 2 Message List iSM11405: Cannot bind SPARE by specified parameter. (<aaa...a>) [Classification] INFO [Explanation] SPARE cannot be bound by specified parameter. aaa...a : Additional information [Measures] Check whether the input parameter is correct. iSM11406: Cannot bind RANK by specified parameter.
  • Page 280 Chapter 2 Message List iSM11409: Cross call was selected. (<aaa...a>) [Classification] INFO [Explanation] Cross call was selected. aaa...a : Additional information [Measures] Unnecessary iSM11410: Subsystem control mode was selected. (<aaa...a>) [Classification] INFO [Explanation] Subsystem control mode was selected. aaa...a : Additional information [Measures] Unnecessary iSM11412: Expand lun was selected.(<aaa...a>)
  • Page 281 Chapter 2 Message List iSM11414: Cannot open a firmware file. [Classification] INFO [Explanation] Firmware file cannot be opened. [Measures] Check whether the path and name of the firmware file is correct. iSM11415: Illegal resource type was selected. [Classification] INFO [Explanation] Selected resource is incorrect.
  • Page 282 Chapter 2 Message List iSM11419: Target Disk Array Subsystem specified by firmware file is not found. [Classification] INFO [Explanation] Object disk array specified by firmware file is not found. [Measures] Check whether the firmware file belongs to a target disk array. iSM11420: Cannot bind some RANKs that was specified.
  • Page 283 Chapter 2 Message List iSM11423: Hot SPARE bind custom was selected. (<aaa...a>) [Classification] INFO [Explanation] Hot spare bind custom was selected. aaa...a : Additional information [Measures] Unnecessary iSM11424: Hot SPARE bind standard was selected. (<aaa...a>) [Classification] INFO [Explanation] Hot spare bind standard was selected. aaa...a : Additional information [Measures]...
  • Page 284 Chapter 2 Message List iSM11426: LD unbind was selected. (<aaa...a>) [Classification] INFO [Explanation] LD unbind was selected. aaa...a : Additional information [Measures] Unnecessary iSM11429: RANK is not found in specified PDG. (<aaa...a>) [Classification] INFO [Explanation] RANK is not found in the specified PDG. aaa...a : Additional information [Measures]...
  • Page 285 Chapter 2 Message List iSM11439: LD ownership was selected. (<aaa...a>) [Classification] INFO [Explanation] LD ownership was selected. aaa...a : Additional information [Measures] Unnecessary iSM11440: Dynamic capacity expansion was selected. (<aaa...a>) [Classification] INFO [Explanation] Dynamic capacity expansion was selected. aaa...a : Additional information [Measures] Unnecessary iSM11442: RANK bind custom was selected.
  • Page 286 Chapter 2 Message List iSM11443: RANK bind standard was selected. (<aaa...a>) [Classification] INFO [Explanation] RANK bind standard was selected. aaa...a : Additional information [Measures] Unnecessary iSM11444: RANK unbind was selected. (<aaa...a>) [Classification] INFO [Explanation] RANK unbind was selected. aaa...a : Additional information [Measures] Unnecessary iSM11455: Temp.
  • Page 287 Chapter 2 Message List iSM11487: The resource that F/W is downloaded to may be not present. (<aaa...a>) [Classification] INFO [Explanation] The resource of downloading destination may be not mounted. aaa...a : Additional information [Measures] Check the status of the disk array. iSM11501: LD information was selected.
  • Page 288 Chapter 2 Message List iSM11504: RANK/PD information was selected. [Classification] INFO [Explanation] “RANK/PD information” was selected. [Measures] Unnecessary iSM11505: PD information was selected. [Classification] INFO [Explanation] “PD information” was selected. [Measures] Unnecessary iSM11506: RANK map information was selected. [Classification] INFO [Explanation] “RANK map information”...
  • Page 289 Chapter 2 Message List iSM11508: Media error list init. was selected. [Classification] INFO [Explanation] “Median error list init.” was selected. [Measures] Unnecessary iSM11509: Subsystem view current setting was selected. [Classification] INFO [Explanation] “Subsystem view current setting” was selected. [Measures] Unnecessary iSM11510: Maintenance view current setting was selected.
  • Page 290 Chapter 2 Message List iSM11522: Media error list doesn’t exist. [Classification] INFO [Explanation] Media Error List does not exist. [Measures] Unnecessary iSM11531: Disk Array Subsystem list information option was selected. [Classification] INFO [Explanation] “Disk Array Subsystem list information” option was selected. [Measures] Unnecessary iSM11532: Disk Array Subsystem detail...
  • Page 291 Chapter 2 Message List iSM11533: LD list information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “LD list information” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11534: LD detail information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “LD detail information” option was selected. aaa...a : Additional information [Measures]...
  • Page 292 Chapter 2 Message List iSM11536: PD detail information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “PD detail information” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11537: Port information with LD key option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Port information with LD key”...
  • Page 293 Chapter 2 Message List iSM11539: Controller information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Controller information” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11540: Enclosure information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Enclosure information” option was selected. aaa...a : Additional information [Measures]...
  • Page 294 Chapter 2 Message List iSM11543: Port information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Platform information” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11544: Specified Resource does not exist. [Classification] INFO [Explanation] Specified resource does not exist. [Measures] Check input resource name and resource number, and retry processing.
  • Page 295 Chapter 2 Message List iSM11548: Volume list data is not found. [Classification] ERROR [Explanation] A volume list data does not exist or specified volume does not exist in the volume list data. [Measures] Check a volume name with reference to the volume list data, and input the volume name again.
  • Page 296 Chapter 2 Message List iSM11561: Rebuild option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Rebuild” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11562: Spare Rebuild option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Spare Rebuild” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11563: iSMrepair was executed.
  • Page 297 Chapter 2 Message List iSM11565: PD Number was too large. [Classification] INFO [Explanation] PD number exceeds the range that can be specified. [Measures] Check whether the input parameter is correct. iSM11566: RANK Number was too large. [Classification] INFO [Explanation] RANK number exceeds the range that can be specified. [Measures] Check whether the input parameter is correct.
  • Page 298 Chapter 2 Message List iSM11569: RANK detail information option was selected. [Classification] INFO [Explanation] “RANK detail information” option was selected. [Measures] Unnecessary iSM11570: Access Control list information option was selected. [Classification] INFO [Explanation] “Access Control list information” option was selected. [Measures] Unnecessary iSM11571: LD Set information with LD Set key...
  • Page 299 Chapter 2 Message List iSM11572: All information option was selected. [Classification] INFO [Explanation] “All information” option was selected. [Measures] Unnecessary iSM11573: Controller detail information option was selected. (<aaa...a>) [Classification] INFO [Explanation] “Controller detail information” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11574: Enclosure detail information option...
  • Page 300 Chapter 2 Message List iSM11575: LD Set detail information option was selected.(<aaa...a>) [Classification] INFO [Explanation] “LD Set detail information” option was selected. aaa...a : Additional information [Measures] Unnecessary iSM11576: ReallocationControl information option was selected. [Classification] INFO [Explanation] “ReallocationControl information” option was selected. [Measures] Unnecessary iSM11577: Cache segment list information...
  • Page 301 Chapter 2 Message List iSM11578: Cache segment detail information with LDN key option was selected. [Classification] INFO [Explanation] “Cache Segment detail information with LDN key” option was selected. [Measures] Unnecessary iSM11579: Cache segment detail information with LD name key option was selected.
  • Page 302 Chapter 2 Message List iSM11581: Pool detail information with Pool Number key option was selected. [Classification] INFO [Explanation] “Pool detail information with Pool Number key” option was selected. [Measures] Unnecessary iSM11582: Pool detail information with Pool Name key option was selected. [Classification] INFO [Explanation]...
  • Page 303 Chapter 2 Message List iSM11585: Snapshot Pool detail information with Pool Number key option was selected. [Classification] INFO [Explanation] “Snapshot Pool detail information with Pool Number key” option was selected. [Measures] Unnecessary iSM11586: Snapshot LD list information option was selected. [Classification] INFO [Explanation]...
  • Page 304 Chapter 2 Message List iSM11601: Failed to communicate. [Classification] INFO [Explanation] It failed to communicate. [Measures] Check whether iSMsvr has started. iSM11602: Failed to set Log output environment. [Classification] INFO [Explanation] It failed in setting environment for Log output. [Measures] Unnecessary iSM11603: Only an Administrators group can execute.
  • Page 305 Chapter 2 Message List iSM11605: Please wait a minute. [Classification] INFO [Explanation] The configuration information is now being obtained(/output). Please wait for a minute. [Measures] Please wait for a minute. iSM11700: Please wait a minute. [Classification] INFO [Explanation] The volume list is now being created/updated. Please wait for a minute. [Measures] Please wait for a minute.
  • Page 306 Chapter 2 Message List iSM11703: Option is insufficient. [Classification] ERROR [Explanation] It indicates that the required option is not specified or invalid option is specified. [Measures] Specify the correct option. iSM11704: Specified option are duplicated. [Classification] ERROR [Explanation] It indicates that the specified options are duplicated. This message is output on Windows system.
  • Page 307 Chapter 2 Message List iSM11707: Combination of options is illegal. [Classification] ERROR [Explanation] It indicates that combination of options is illegal. This message is output on Windows system. [Measures] Specify the correct option. iSM11708: Form of parameter is illegal. [Classification] ERROR [Explanation] It indicates that the form of parameter is illegal.
  • Page 308 Chapter 2 Message List iSM11711: Volume list data does not exist. [Classification] WARNING [Explanation] Volume list does not exist. [Measures] Create/update the volume list. iSM11712: Volume list data is not created by the command which supports property display. [Classification] WARNING [Explanation] The property of the volume list could not be obtained because it is old.
  • Page 309 Chapter 2 Message List iSM11721: Disk Array does not exist in volume list data. [Classification] ERROR [Explanation] It indicates that the disk array information is not registered in the volume list. [Measures] Check the connection between the host machine and the disk array, and newly create the volume list.
  • Page 310 Chapter 2 Message List iSM11724: Specified ld_name does not exist in volume list data. [Classification] ERROR [Explanation] It indicates that the specified logical disk name is not registered in the volume list. This message is output on Windows system. [Measures] Specify the correct logical disk name.
  • Page 311 Chapter 2 Message List iSM11727: Specified HBT does not exist in volume list data. [Classification] ERROR [Explanation] It indicates that the specified HBT is not registered in the volume list. This message is output on Windows system. [Measures] Specify the correct HBT. iSM11728: Specified HBT or LUN does not exist in volume list data.
  • Page 312 Chapter 2 Message List iSM11730: Failed to get the specified Disk Array information. [Classification] ERROR [Explanation] It indicates that the disk array information collection is failed. This message is output on Windows system. [Measures] Check the connection between the host machine and the disk array, and newly create a volume list.
  • Page 313 Chapter 2 Message List iSM11733: Failed to initialize an ODM session. [Classification] ERROR [Explanation] Failed in initialization of ODM session. [Measures] Check that ODM environment is normal and retry processing. Check that system memory capacity is sufficient and retry processing. iSM11734: Failed to terminate an ODM session.
  • Page 314 Chapter 2 Message List iSM11737: Failed to get control volume definitions. [Classification] ERROR [Explanation] Failed in obtaining control volume definitions. [Measures] Check that control volume definition file is described correctly, and then retry processing. iSM11738: Failed to get target volume definitions.
  • Page 315 Chapter 2 Message List iSM11740: Failed to get property of volume list data. [Classification] ERROR [Explanation] Failed in obtaining the property of volume list data. [Measures] Update the volume list, and then retry processing. iSM11742: Failed to open control volume definition file.
  • Page 316 Chapter 2 Message List iSM11745: Failed to close control volume definition file. [Classification] ERROR [Explanation] Failed in closing control volume definition file. [Measures] Check that control volume definition file exists, and then retry processing. iSM11746: Failed to close target volume definition file.
  • Page 317 Chapter 2 Message List iSM11749: Control volume is not found. [Classification] ERROR [Explanation] Control volume is not found. [Measures] Check that control volume definition file is described correctly, and then create a target-control volume list again. iSM11750: Failed to execute popen. [Classification] ERROR [Explanation]...
  • Page 318 Chapter 2 Message List iSM11751: ReplicationControl or iSMvollist command has already started. iSM11751: iSMvollist command has already started. iSM11751: iSMmknod command has already started. iSM11751: iSM/Server has already started. [Classification] ERROR [Explanation] Reference or update of Volume List was executed during execution of the replication control command.
  • Page 319 Chapter 2 Message List iSM11756: Illegal OS version [Classification] ERROR [Explanation] This version of OS is not supported for ReplicationControl. This message is output on UNIX system. [Measures] ReplicationControl cannot be used. iSM11757: SCSI path-through driver is not installed. [Classification] ERROR [Explanation] The SCSI path-through driver is not installed in the system.
  • Page 320 Chapter 2 Message List iSM11758: System call error (error code=<aaa>) [Classification] ERROR [Explanation] The system call failed when the volume list was created. : Error code 200: fork() fail 201: rename() fail 202: opendir() fail 203: execvp() fail 204: system() fail 205: unlink() fail 206:...
  • Page 321: Diagnostic Mode

    Chapter 2 Message List iSM11759: Failed to open control volume in Diagnostic mode. [Classification] ERROR [Explanation] Control volume cannot be opened in Diagnostic mode. [Measures] Check that LVM has not been activated on control volume and has not been opened by other application in Diagnostic mode. Then retry processing. iSM11760: Volume list data is locked by another process.
  • Page 322 Chapter 2 Message List iSM11783: Failed to read volume list data. [Classification] ERROR [Explanation] It indicates that it failed to read the volume list. [Measures] The volume list may be invalid. Create a new volume list. iSM11784: Failed to write volume list data. [Classification] ERROR [Explanation]...
  • Page 323 Chapter 2 Message List iSM11787: Failed to rename volume list data. [Classification] ERROR [Explanation] It indicates that the file name of the volume list is not changed due to an error. This message is output on Windows system. [Measures] The volume list may be invalid. Create a new volume list. iSM11791: Failed to read directory.
  • Page 324 Chapter 2 Message List iSM11794: Failed to open scsi device. [Classification] ERROR [Explanation] It indicates that SCSI device is not opened due to an error. [Measures] Check the connection between the host machine and the disk array, and newly create a volume list. iSM11795: Failed to get OS version.
  • Page 325 Chapter 2 Message List iSM11799: Failed to execute system function. [Classification] ERROR [Explanation] It indicates that an error occurred in the system function of OS. [Measures] OS may be in instability or invalid. Set the OS in a stable condition by restarting or re-installing the OS.
  • Page 326 Chapter 2 Message List iSM11804: Failed to get ‘<aaa...a>’ log. [Classification] INFO [Explanation] Failed in obtaining log from disk array indicated by “aaa...a”. [Measures] Check status of iSM server and disk array, and then retry processing.
  • Page 327 Chapter 2 Message List iSM13000 ∼ iSM13200: <aaa...a> [Classification] INFO [Explanation] Executed command line. aaa...a : Entered character string [Measures] Unnecessary iSM13201: Replicate Start <aaaa/bb/cc> <dd:ee:ff> MV:<ggg...g> RV:<ggg...g> [Classification] INFO [Explanation] Replicate processing start message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second ggg...g : Volume name [Measures]...
  • Page 328 Chapter 2 Message List iSM13203: Replicate Abnormal End <aaaa/bb/cc> <dd:ee:ff> MV:<ggg...g> RV:<ggg...g> [Classification] INFO [Explanation] Replicate processing abnormal termination message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second ggg...g : Volume name [Measures] Check the message displayed immediately before to handle it. iSM13204: Restore Start <aaaa/bb/cc>...
  • Page 329 Chapter 2 Message List iSM13206: Restore Abnormal End <aaaa/bb/cc> <dd:ee:ff> MV:<ggg...g> RV:<ggg...g> [Classification] INFO [Explanation] Restore processing abnormal termination message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second ggg...g : Volume name [Measures] Check the message displayed immediately before to handle it. iSM13207: Separate Start <aaaa/bb/cc>...
  • Page 330 Chapter 2 Message List iSM13209: Separate Abnormal End <aaaa/bb/cc> <dd:ee:ff> MV:<ggg...g> RV:<ggg...g> [Classification] INFO [Explanation] Separate processing abnormal termination message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second ggg...g : Volume name [Measures] Check the message displayed immediately before to handle it. iSM13210: Change Start <aaaa/bb/cc>...
  • Page 331 Chapter 2 Message List iSM13212: Change Abnormal End <aaaa/bb/cc> <dd:ee:ff> MV:<ggg...g> RV:<ggg...g> [Classification] INFO [Explanation] Copy Control State change processing abnormal termination message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second ggg...g : Volume name [Measures] Check the message displayed immediately before to handle it. iSM13213: Wait Abnormal End <aaaa/bb/cc>...
  • Page 332 Chapter 2 Message List iSM13215: These targets have already separated. (<aaa...a>) MV:<bbb...b> RV:<bbb...b> [Classification] INFO [Explanation] Specified volume has already been separated. Separation condition is not displayed for separation normally ended aaa...a : Separation condition cancel : forced separation fault : fault separation bbb...b : Volume name...
  • Page 333 Chapter 2 Message List iSM13219: <aaa...a> return=<bbb...b> <ccc...c> [Classification] INFO [Explanation] It indicates that processing returned from a function. The name, return value and return information of function are edited and output with arbitrary character strings. aaa...a : Function name bbb...b : Return value of function (decimal) ccc...c...
  • Page 334 Chapter 2 Message List iSM13221: Resetting drive letter (<aaa...a>) has succeeded. iSM13221: Resetting mount point (<bbb...b>) has succeeded. [Classification] INFO [Explanation] The drive letter or the NTFS folder mount point was canceled successfully. This message is output on Windows system. aaa...a : Drive name bbb...b...
  • Page 335 Chapter 2 Message List iSM13224: MV is restored. Volume Name:<aaa...a> Mount Point:<bbb...b> [Classification] INFO [Explanation] The MV is to be restored by the restore command. This message is output on Windows system. aaa...a : Mount point volume name bbb...b : Drive letters or NTFS folder name [Measures] Unnecessary If an error occurs during unmount of MV that is performed at restore start, set the...
  • Page 336 Chapter 2 Message List iSM13227: Flush Abnormal End <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation] Buffer flush processing abnormal termination message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second [Measures] Check the message displayed immediately before to handle it. iSM13228: Scan Start <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation]...
  • Page 337 Chapter 2 Message List iSM13230: Scan Abnormal End <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation] Device scan processing abnormal termination message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second. [Measures] Check the message displayed immediately before to handle it. iSM13231: Writing signature succeeded. volume=<aaa...a> [Classification] INFO [Explanation]...
  • Page 338 Chapter 2 Message List iSM13233: Deleting of signature information from signature map file has succeeded. [Classification] INFO [Explanation] All the disk signature information was deleted from the signature map file successfully. This message is output on Windows system. [Measures] Unnecessary iSM13234: Exporting file succeeded.
  • Page 339 Chapter 2 Message List iSM13238: Freeze of database is started. <aaaa>/<bb>/<cc> <dd>:<ee>:<ff> [Classification] INFO [Explanation] Freeze of database is started. aaaa/bb/cc : System date (year/month/day) when freeze of database started. dd:ee:ff : System time (hour:minute:second) when freeze of database started. [Measures] Unnecessary iSM13239: All of database were thawed.
  • Page 340 Chapter 2 Message List iSM13241: SnapshotBackup Normal End <aaaa>/<bb>/<cc> <dd>:<ee>:<ff> [Classification] INFO [Explanation] Snapshot backup processing has terminated normally. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second [Measures] Unnecessary iSM13242: SnapshotBackup Abnormal End <aaaa>/<bb>/<cc> <dd>:<ee>:<ff> [Classification] INFO [Explanation] Snapshot backup processing has terminated abnormally. aaaa/bb/cc : Year/Month/Day dd:ee:ff...
  • Page 341 Chapter 2 Message List iSM13244: SnapshotRestore Normal End <aaaa>/<bb>/<cc> <dd>:<ee>:<ff> [Classification] INFO [Explanation] Snapshot restore processing has terminated normally. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second [Measures] Unnecessary iSM13245: SnapshotRestore Abnormal End <aaaa>/<bb>/<cc> <dd>:<ee>:<ff> [Classification] INFO [Explanation] Snapshot restore processing has terminated abnormally. aaaa/bb/cc : Year/Month/Day dd:ee:ff...
  • Page 342 Chapter 2 Message List iSM13248: Command has completed successfully.(already) (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] INFO [Explanation] The requested state has already been set up, and command execution was successful. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Unnecessary...
  • Page 343 Chapter 2 Message List iSM13251: Create Start <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation] Snapshot create processing start message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second [Measures] Unnecessary iSM13252: Create Normal End <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation] Snapshot create processing normal end message. aaaa/bb/cc : Year/Month/Day dd:ee:ff...
  • Page 344 Chapter 2 Message List iSM13254: Delete Start <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation] Snapshot delete processing start message. aaaa/bb/cc : Year/Month/Day dd:ee:ff : Hour/Minute/Second [Measures] Unnecessary iSM13255: Delete Normal End <aaaa/bb/cc> <dd:ee:ff> [Classification] INFO [Explanation] Snapshot delete processing normal end message. aaaa/bb/cc : Year/Month/Day dd:ee:ff...
  • Page 345 Chapter 2 Message List iSM13400: Specified volume state has already been set up. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] WARNING [Explanation] Specified volume state has already been set up. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check specified volume state and re-execute.
  • Page 346 Chapter 2 Message List iSM13403: Specified attribute (<aaa...a>) was already set up to the ATgroup. ATG=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] WARNING [Explanation] Specified attribute has already been set up to the AT-group. aaa...a : Specified attribute value bbb…b : AT-group name ccc...c : Process number ddd...d...
  • Page 347 Chapter 2 Message List iSM13406: Specified targets are duplicated. MV=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13406: Specified targets are duplicated. volume=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] WARNING [Explanation] MV or BV is defined repeatedly. aaa...a : Volume name bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check the volume specification.
  • Page 348 Chapter 2 Message List iSM13408: These targets have replicated. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13408: These targets have replicated. MV:<aaa...a> RV:<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] WARNING [Explanation] A command, which must not be executed for volumes or AT-groups with Replicate being completed, was executed. aaa...a : AT-group name or volume name bbb...b...
  • Page 349 Chapter 2 Message List iSM13409: These targets have separated. ATG=<aaa...a>> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13409: These targets have separated. MV:<aaa...a> RV:<aaa...a>> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] WARNING [Explanation] A command, which must not be executed for volumes or AT-groups with Separate being completed, was executed. aaa...a : AT-group name or volume name bbb...b...
  • Page 350 Chapter 2 Message List iSM13410: These targets have restored. MV:<aaa...a> RV:<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] WARNING [Explanation] A command, which must not be executed for volumes with Restore being completed, was executed. aaa...a : Volume name bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures]...
  • Page 351 Chapter 2 Message List iSM13413: Target pair’s copy mode is foreground. [Classification] WARNING [Explanation] A request was made for a pair of volumes to change from the foreground copy state into the synchronous copy mode or semi synchronous copy mode. [Measures] Move the volumes into normal suspend state, and then change the copy mode.
  • Page 352 Chapter 2 Message List iSM13480: Target ATgroup is replicating now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] WARNING [Explanation] The specified AT-group is in the state of replicate start (Rpl/start) or replicate execution (Rpl/exec), and replicate has been already started. aaa...a : AT-group name bbb...b : Process number ccc...c...
  • Page 353 Chapter 2 Message List iSM13482: Target ATgroup is separating now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] WARNING [Explanation] The specified AT-group is in the state of separate start (Sep/start) or separate execution (Sep/exec), separation has been already started. aaa...a : AT-group name bbb...b : Process number ccc...c...
  • Page 354 Chapter 2 Message List iSM13500: Insufficient option. (<aaa...a>) [Classification] ERROR [Explanation] The specified command does not have some required arguments, or invalid arguments are specified. When -file option is specified, an available option is specified for the pair specified by the replication operation file. () may or may not be displayed.
  • Page 355 Chapter 2 Message List iSM13503: Too many options are specified. (<aaa...a>) [Classification] ERROR [Explanation] Too many values are specified in the argument. aaa...a : Specified value [Measures] Check the input format and enter it again. iSM13504: Illegal combination of options. (<aaa...a>) [Classification] ERROR...
  • Page 356 Chapter 2 Message List iSM13507: Illegal rvflg type. (<aaa...a>) [Classification] ERROR [Explanation] The value specified as RV type is invalid. aaa...a : Specified value [Measures] Specify a correct value. iSM13508: Illegal cprange type. (<aaa...a>) [Classification] ERROR [Explanation] The value specified in -cprange is invalid. aaa...a : Specified value [Measures]...
  • Page 357 Chapter 2 Message List iSM13511: Illegal force type. (<aaa...a>) [Classification] ERROR [Explanation] The value specified in -force is invalid. aaa...a : Specified value [Measures] Specify a correct value. iSM13512: Illegal copy mode. [Classification] ERROR [Explanation] A copy mode is not specified. Or, the specified copy mode is not supported as copy control mode for the target pair.
  • Page 358 Chapter 2 Message List iSM13513: Volume (<aaa...a>) does not exist in volume list. [Classification] ERROR [Explanation] Specified volume does not exist in the volume list. If you use the control volume for operation, the specified volume or volume paired with the specified volume should be accessible from the relevant business server with the Access Control or other functions.
  • Page 359 Chapter 2 Message List iSM13514: Volume name is too long. (<aaa...a>) [Classification] ERROR [Explanation] The specified volume name is too long. aaa...a : Specified volume name [Measures] Specify the volume within the following range: Logical disk name: within 24 1-byte characters Special file name: within 32 1-byte characters Volume group name:...
  • Page 360 Chapter 2 Message List iSM13517: Number of LD(MV) is not equal to that of LD(RV). [Classification] ERROR [Explanation] The number of volumes specified for MV and RV are different. This message is output on UNIX system. [Measures] Make the number of MV and RV volumes equal. iSM13518: Illegal value of -wait [second].
  • Page 361 Chapter 2 Message List iSM13519: Illegal value of RPL_WATCHDEV. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The value specified in the environment variable RPL_WATCHDEV is invalid. (UNIX) The value specified in RPL_WATCHDEV of the replication operation option setting file is not allowed. (Windows) aaa...a : Specified value bbb...b...
  • Page 362 Chapter 2 Message List iSM13521: Specified volume group does not exist vg=<aaa...a> iSM13521: Specified disk group does not exist dg=<bbb...b> [Classification] ERROR [Explanation] An invalid volume group or disk group is specified. This message is output on UNIX system. aaa...a : Volume group bbb...b : Disk group...
  • Page 363 Chapter 2 Message List iSM13524: No such file filename=<aaa...a> errno=<bbb> [Classification] ERROR [Explanation] The specified file does not exist. aaa...a : File name : Error number [Measures] Specify a correct file name. iSM13525: Illegal file type filename=<aaa...a> [Classification] ERROR [Explanation] The specified file type cannot be processed.
  • Page 364 Chapter 2 Message List iSM13527: Illegal character is included. filename=<aaa...a> line=<bbb...b> [Classification] ERROR [Explanation] An invalid character exists in the description in the file. aaa...a : File name bbb...b : Number of lines [Measures] Correct the file and execute it again. iSM13528: Line has too many characters.
  • Page 365 Chapter 2 Message List iSM13530: Illegal MV type is specified. filename=<aaa...a> line=<bbb...b> [Classification] ERROR [Explanation] An invalid value was specified in MV Type. aaa...a : File name bbb...b : Number of lines [Measures] Specify a correct value for MV Type.. iSM13531: Illegal iopath type.
  • Page 366 Chapter 2 Message List iSM13533: MV name is too long. error filename=<aaa...a> line=<bbb...b> iSM13533: RV name is too long. error filename=<aaa...a> line=<bbb...b> iSM13533: Specified volume name is too long. error filename=<aaa...a> line=<bbb...b> [Classification] ERROR [Explanation] The specified volume name is too long. aaa...a : File name bbb...b...
  • Page 367 Chapter 2 Message List iSM13535: ATgroup does not exist. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13535: ATgroup does not exist. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified AT-group does not exist. Or, no operational AT-group is found. aaa...a : Specified AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a...
  • Page 368 Chapter 2 Message List iSM13537: Number of LD(MV) is not equal to that of LD(RV). filename=<aaa...a> line=<bbb...b> [Classification] ERROR [Explanation] The number of volumes specified for MV and RV are different. aaa...a : File name bbb...b : Number of lines [Measures] Make the number of volumes of MV and RV equal.
  • Page 369 Chapter 2 Message List iSM13540: Illegal volflg type (<aaa...a>) [Classification] ERROR [Explanation] The value specified in the -vol type is invalid. aaa...a : Specified value [Measures] Specify a correct value. iSM13541: Semi-sync mode is not available to DynamicDataReplication. [Classification] ERROR [Explanation] Semi-sync mode cannot be specified for pairs in the same disk array.
  • Page 370 Chapter 2 Message List iSM13543: Illegal atmode type. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The value specified in the -atmode option is invalid. aaa...a : Specified value bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct value.
  • Page 371 Chapter 2 Message List iSM13545: Illegal site type. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The value specified in the -site option is invalid. aaa...a : Specified value bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct value.
  • Page 372 Chapter 2 Message List iSM13549: Failed to replicate. [Classification] ERROR [Explanation] Replicate failed. [Measures] Check the message displayed immediately before to handle it. iSM13550: Failed to restore. [Classification] ERROR [Explanation] Restore failed. [Measures] Check the message displayed immediately before to handle it. iSM13551: Failed to separate.
  • Page 373 Chapter 2 Message List iSM13553: Illegal value of RPL_LIMWATCHDEV. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified value of an environment variable or RPL_LIMWATCHDEV of the replication operation option setting file is out of the specified range. aaa...a : Specified value bbb...b : Process number ccc...c...
  • Page 374 Chapter 2 Message List iSM13555: Checking status failed. (detail error code=<aaa>) [Classification] ERROR [Explanation] A failure was detected during wait mode process and volume state could not be obtained. : Error code The following show major error codes. : SCSI I/O failure : system error occurred : SCSI open failure : SCSI close failure...
  • Page 375 Chapter 2 Message List iSM13556: SCSI I/O error has occurred. [Classification] ERROR [Explanation] SCSI I/O error has occurred. [Measures] A failure may be occurring in connection with disk array. Check status of FC connection and then retry processing. If no problems are found in status of FC connection, check the following for the specified volume.
  • Page 376 Chapter 2 Message List iSM13559: Parameter error occurred. [Classification] ERROR [Explanation] Parameter error occurred in the internal processing. [Measures] Collect information on operation trace iSM13560: State of the specified ATgroup is unknown. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] State of the specified AT-group is unknown. aaa...a : Process number bbb...b...
  • Page 377 Chapter 2 Message List iSM13562: RV is omitted. [Classification] ERROR [Explanation] RV was omitted for MV with the pair setting of multiple RVs. [Measures] Specify RV and execute it again. iSM13563: System call error (error code=<aaa>) [Classification] ERROR [Explanation] It failed in system calling. : System error number [Measures] If the operation trace is collected, use the information in the operation trace and...
  • Page 378 Chapter 2 Message List iSM13565: Upper pair is not separated. [Classification] ERROR [Explanation] The activity state of the pair of the specified MV and the upper pair is not Separate. [Measures] Make the activity state of the upper pair separate state, and retry processing. To replicate the target pair when the activity state of the upper pair is Replicate, set the copy control mode on the target pair to the background copy mode and replicate it.
  • Page 379 Chapter 2 Message List iSM13568: Target ATgroup is processing Atomic-break now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Request was rejected because atomic-break is operating on the specified AT-group. aaa...a : AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check the state of the AT-group and the state of the pair registered in the...
  • Page 380 Chapter 2 Message List iSM13569: Target ATgroup is replicating now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13569: Target pair is replicating now. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified pair is being replicated. Or, the specified AT-group is in the replicate start (Rpl/start) or replicate execution (Rpl/exec) state. aaa...a : AT-group name bbb...b...
  • Page 381 Chapter 2 Message List iSM13570: Target ATgroup is restoring now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13570: Target pair is restoring now. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified pair is being restored. Or, the specified AT-group is in the restore execution (Rst/exec) state. aaa...a : AT-group name bbb...b...
  • Page 382 Chapter 2 Message List iSM13571: Target ATgroup is separating now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13571: Target pair is separating now. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified pair is being separated. Or the specified AT-group is in the separate start (Sep/start) or separate execution (Sep/exec) state. aaa...a : AT-group name bbb...b...
  • Page 383 Chapter 2 Message List iSM13573: Target ATgroup is not replicated. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13573: Target pair is not replicated or restored. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The activity state of the specified pair is not the Replicate or Restore state. Or, the sync state of the specified AT-group is not replicate synchronous.
  • Page 384 Chapter 2 Message List iSM13575: Unexpected error occurred. [Classification] ERROR [Explanation] Message for an unexpected error. [Measures] Check library version for the replication operation, and check firmware revision of disk array device. iSM13576: Targets may not be a pair, or unexpected error occurred.
  • Page 385 Chapter 2 Message List iSM13578: These targets are separating now. MV:<aaa...a> RV:<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] A non-executable replication operation command was performed for the pair in Separate execution. aaa...a : Volume name bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check the execution conditions of the specified command and execute it again.
  • Page 386 Chapter 2 Message List iSM13580: Target ATgroup is suspended now. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The sync state of the specified AT-group has become replicate suspend (Rpl/suspend) or restore suspend (Rst/suspend). aaa...a : AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 387 Chapter 2 Message List iSM13582: These targets have separated. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13582: These targets have separated. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] A command not allowed for separated volume or AT-group was executed. aaa...a : AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 388 Chapter 2 Message List iSM13584: Not enough memory (<aaa...a>) errno=<bbb> [Classification] ERROR [Explanation] Insufficient memory to execute the process. () and error number may or may not be displayed. aaa...a : Resource name : Error number [Measures] Add more memory to the system. iSM13585: Volume list is missing or unexpected error occurred.
  • Page 389 Chapter 2 Message List iSM13586: Target ATgroup is fault. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The sync state of the specified AT-group has become failure separation (Fault). aaa...a : AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] This AT-group may have been forcibly separated by another process or it may...
  • Page 390 Chapter 2 Message List iSM13588: Specified ATgroup has already existed. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13588: Specified ATgroup has already existed. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified AT-group already exists. aaa...a : AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] A newly created AT-group must have a unique name in the system.
  • Page 391 Chapter 2 Message List iSM13590: Specified ATgroup cannot be operated from this site. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Operation of the specified AT-group cannot be executed from the current position. AT-group binding is enabled on the concentrator side. aaa...a : AT-group name bbb...b : Process number...
  • Page 392 Chapter 2 Message List iSM13592: Target ATgroup is not separated. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13592: Target pair is not separated. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The activity status of the specified pair is not Separate. Or, the specified AT-group sync state is not separated (Separated) or failure separation (Fault). aaa...a : AT-group name bbb...b...
  • Page 393 Chapter 2 Message List iSM13594: License for RemoteDataReplication /DisasterRecovery is locked. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The product of RemoteDataReplication/DisasterRecovery is not purchased. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] To perform the RemoteDataReplication/DisasterRecovery operation, purchase the RemoteDataReplication/DisasterRecovery product.
  • Page 394 Chapter 2 Message List iSM13597: DynamicDataReplication is not supported. [Classification] ERROR [Explanation] The DynamicDataReplication function is not supported. [Measures] ReplicationControl cannot be used. iSM13598: RemoteDataReplication is not supported. [Classification] ERROR [Explanation] The RemoteDataReplication function is not supported. [Measures] ReplicationControl cannot be used. iSM13599: License for this command is locked.
  • Page 395 Chapter 2 Message List iSM13600: Specified drive has multiple partitions/extents. [Classification] ERROR [Explanation] Specified physical disk is configured in multiple partitions, or logical volume in the specified volume disk is configured in multiple extensions (physical disk). This message is output on Windows system. [Measures] Physical disk status can be confirmed by Disk Management (Computer Management) for Windows.
  • Page 396 Chapter 2 Message List iSM13603: Partition that specified drive character assigned has multiple partitions/extents. [Classification] ERROR [Explanation] Specified disk to which the drive letter is allocated is configured in multiple partitions, or volume in the disk is configured in multiple extensions (physical disk).
  • Page 397 Chapter 2 Message List iSM13606: There is no authority to access the specified volume. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) iSM13606: There is no authority to access the specified pair. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The operation could not be executed because access to the specified pair or volume is not permitted.
  • Page 398 Chapter 2 Message List iSM13607: Specified disk type is not supported. iSM13607: Specified drive type is not supported. [Classification] ERROR [Explanation] Specified disk or drive type is not supported. This message is output on Windows system. [Measures] Check the formats of the specified disk and connected device and retry command execution.
  • Page 399 Chapter 2 Message List iSM13610: Illegal drive number is specified. [Classification] ERROR [Explanation] The specified disk number is illegal. This message is output on Windows system. [Measures] Specify a correct value. iSM13611: RemoteDataReplication/Disaster Recovery is not supported. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] RemoteDataReplication/DisasterRecovery function is not supported.
  • Page 400 Chapter 2 Message List iSM13612: Specified ATgroup is empty. ATG=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified AT-group does not have any registered pair. aaa...a : AT-group name bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] For operation of an AT-group, a pair must be registered in advance.
  • Page 401 Chapter 2 Message List iSM13614: Failed to read signature. iSM13614: Failed to read signature. volume=<aaa...a> [Classification] ERROR [Explanation] The disk signature information could not be read. aaa...a : Physical disk number [Measures] If a message is output immediately before this message, take measures according to the message.
  • Page 402 Chapter 2 Message List iSM13616: ATgroup cannot be registered any more. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] No more AT-group can be registered. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] No more AT-group can be registered because the number of registered AT-groups has already reached the maximum number of AT-groups that can be...
  • Page 403 Chapter 2 Message List iSM13618: Specified volume does not exist in signature map file. volume=<aaa...a> [Classification] ERROR [Explanation] The specified disk does not exist in the signature map file. This message is output on Windows system. aaa...a : Physical disk number [Measures] Specify a correct value.
  • Page 404 Chapter 2 Message List iSM13623: Signature file access has failed. filename=<aaa...a> errno=<bbb> [Classification] ERROR [Explanation] Access to the signature map file could not be made. This message is output on Windows system. aaa...a : File name : Error number [Measures] Take measures according to the message output immediately before this message.
  • Page 405 Chapter 2 Message List iSM13625: Specified volume has more than one mount point. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The specified volume has multiple mount points (drive letter or NTFS folder name). aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] The volume should have only one mount point (drive letter or NTFS folder...
  • Page 406 Chapter 2 Message List iSM13627: Specified volume’s signature does not exist in file. filename=<aaa...a> [Classification] ERROR [Explanation] The signature information of the specified disk does not exist in the signature map file. This message is output on Windows system. aaa...a : File name [Measures] Specify a correct value.
  • Page 407 Chapter 2 Message List iSM13631: Failed to mount. [Classification] ERROR [Explanation] Failed to mount. This message is output on Windows system. [Measures] Check the message displayed immediately before to handle it. iSM13632: Failed to umount. [Classification] ERROR [Explanation] Failed to unmount. This message is output on Windows system.
  • Page 408 Chapter 2 Message List iSM13634: Failed to set drive letter. (<aaa...a>) iSM13634: Failed to set mount point. (<bbb...b>) [Classification] ERROR [Explanation] The drive letter or the NTFS folder mount point could not be set. This message is output on Windows system. aaa...a : Drive letters bbb...b...
  • Page 409 Chapter 2 Message List iSM13636: Failed to initialize signature. iSM13636: Failed to initialize signature. volume=<aaa...a> [Classification] ERROR [Explanation] The disk signature information could not be initialized. This message is output on Windows system. aaa...a : Physical disk number [Measures] Take measures according to the message output immediately before this message.
  • Page 410 Chapter 2 Message List iSM13639: Specified path is not normal status. [Classification] ERROR [Explanation] File or directory cannot be read. This message is output on Windows system. [Measures] Check that the file or directory exists or access to the volume is permitted, and retry command execution.
  • Page 411 Chapter 2 Message List iSM13641: Firmware does not support necessary function. iSM13641: Firmware does not support <aaa...a> function. [Classification] ERROR [Explanation] Functions of firmware necessary are not supported. aaa...a : Function name signature : Signature function separate(immediate) : Separate (Quick Replicate) function separate(RDR immediate) : Separate (Quick Replicate) function of RemoteDataReplication restore(rv-protection)
  • Page 412 Chapter 2 Message List iSM13645: Target pair cannot be registered in specified ATgroup. MV=<aaa...a> RV=<aaa...a> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) iSM13645: Target pair cannot be registered in specified ATgroup. ATG=<bbb... b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] The specified pair cannot be registered in the AT-group. To register a pair in an AT-group, the following conditions are required: - The AT-group sync state is separated (Separated), failure separation (Fault), or no pair registered (Invalid).
  • Page 413 Chapter 2 Message List iSM13646: Specified mv volume is mounted. path=<aaa...a> [Classification] ERROR [Explanation] The MV has been mounted. This message is output on UNIX system. aaa...a : Path name of MV (special file name, volume path name, etc.) [Measures] Unmount the MV, and then re-execute the command.
  • Page 414 Chapter 2 Message List iSM13649: These targets are not restoring now. MV:<aaa...a> RV:<aaa...a> [Classification] ERROR [Explanation] Specified pair is not in the restoration status. aaa...a : Volume name [Measures] Check the specified pair operation status and re-execute iSM13650: Target pair is a member of ATgroup. MV=<aaa...a>...
  • Page 415 Chapter 2 Message List iSM13651: Target pair is already registered in other ATgroup. MV=<aaa...a> RV=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) iSM13651: Target pair is already registered in specified ATgroup. MV=<aaa...a> RV=<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The specified pair is already registered in another AT-group. A pair cannot be registered in multiple AT-groups at the same time.
  • Page 416 Chapter 2 Message List iSM13653: Illegal mode type. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The value specified in the mode option of the Restore command is illegal. aaa...a : Specified value bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct value.
  • Page 417 Chapter 2 Message List iSM13655: Illegal condition type. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The value specified in the cond option of the Wait command is illegal. aaa...a : Specified value bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct value.
  • Page 418 Chapter 2 Message List iSM13657: Illegal value of -limit [second]. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The value specified in the limit option of the Wait command is illegal. aaa...a : Specified value bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct value.
  • Page 419 Chapter 2 Message List iSM13659: Specified targets are not ready. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) iSM13659: Specified targets are not available. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Specified volume is unavailable. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] The volume is specified under the Read Only, Not Ready, or Not Available...
  • Page 420 Chapter 2 Message List iSM13660: Replicate command has terminated because “activity status” is changed by other process. iSM13660: Replicate command has terminated because “ATgroup Sync State” is changed by other process. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Activity status of a pair has changed to status other than Replicate during waiting process for completion of replication.
  • Page 421 Chapter 2 Message List iSM13661: Restore command has terminated because “activity status” is changed by other process. iSM13661: Restore command has terminated because “ATgroup Sync State” is changed by other process. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Activity status of a pair has changed to status other than Restore during waiting process for completion of restoration.
  • Page 422 Chapter 2 Message List iSM13662: Separate command has terminated because “activity status” is changed by other process. iSM13662: Separate command has terminated because “ATgroup Sync State” is changed by other process. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Activity status of a pair has changed to status other than Separate during waiting process for completion of separation.
  • Page 423 Chapter 2 Message List iSM13663: The processing of waiting has terminated because “separate diff” or “copy diff” does not decrease in the specified time. (<aaa> sec) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] The waiting process for completion of replication, restoration, or separation has been terminated before completion because the copy difference of the pair or the differential quantity volume of the AT-group did not decrease in the specified time.
  • Page 424 Chapter 2 Message List iSM13664: Wait command has terminated because “ATgroup Sync State” is changed by other process. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The waiting process for completion of synchronization or separation has been terminated before completion because an error in the AT-group sync state as described below has been detected.
  • Page 425 Chapter 2 Message List iSM13669: SnapControl is not installed. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] SnapControl has not been installed. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Install SnapControl. iSM13670: ReplicationControl is not installed.
  • Page 426 Chapter 2 Message List iSM13672: DynamicSnapVolume is not supported. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] DynamicSnapVolume is not supported. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check the support state of the disk array. iSM13673: Specified attribute (<aaa...a>) does not match the attribute of ATgroup.
  • Page 427 Chapter 2 Message List iSM13674: Specified volume is used by snapshot function. <aaa...a>:<bbb...b > (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Snapshot operation is taking place in the specified volume. aaa...a : Character string indicating MV or RV MV : MV volume RV : RV volume bbb...b...
  • Page 428 Chapter 2 Message List iSM13676: Failed to sql server connection. [Classification] ERROR [Explanation] Connection of Microsoft SQL Server 2000 failed. [Measures] Microsoft SQL Server 2000 service may have not started. Check that the service started and retry command execution. Or, if a user ID is specified upon execution of a command, the specified user ID and password are used for connecting to Microsoft SQL Server 2000.
  • Page 429 Chapter 2 Message List iSM13679: Illegal remod type. (<aaa...a>) [Classification] ERROR [Explanation] A value specified for -remod option is invalid. aaa...a : Specified value [Measures] Specify a valid value. iSM13680: Illegal refile name. (<aaa...a>) [Classification] ERROR [Explanation] A value specified for -refile option is invalid. aaa...a : Specified value [Measures]...
  • Page 430 Chapter 2 Message List iSM13682: Failed to VDI initialization. [Classification] ERROR [Explanation] Initial process of VDI failed. [Measures] Check that VDI is available in given environment, and then retry command execution. iSM13683: No authority to access database. [Classification] ERROR [Explanation] No authority to access database is given.
  • Page 431 Chapter 2 Message List iSM13686: Failed to metafile (<aaa...a>) creation. [Classification] ERROR [Explanation] Failed in creating metafile. aaa...a : File name [Measures] Check that specified metafile is correct and retry command execution. iSM13687: Metafile(<aaa...a>) is not found. [Classification] ERROR [Explanation] Specified metafile is not found.
  • Page 432 Chapter 2 Message List iSM13690: Failed to sql command execution. [Classification] ERROR [Explanation] Failed in SQL command. [Measures] Check error log of Microsoft SQL Server 2000, remove cause of fault and then retry command execution. iSM13691: Dbname does not exist in SQL server.
  • Page 433 Chapter 2 Message List iSM13694: Database (<aaa...a>) is being used in another process. [Classification] ERROR [Explanation] Database is used by other process. aaa...a : Database name [Measures] Check that other process is not using the database and then retry command execution.
  • Page 434 Chapter 2 Message List iSM13698: Database filename does not exist in metafile. [Classification] ERROR [Explanation] File name of database does not exist in metafile. [Measures] Check that specified file name indicates a physical file of database and then retry command execution. iSM13699: Number of move files are not equal to metafile’s number.
  • Page 435 Chapter 2 Message List iSM13701: ‘R/W permit’ mode cannot be set when state is ‘rpl/sync’, ‘rpl/exec’, ‘rst/sync’, ‘rst/exec’ or ‘sep/exec’. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] R/W Permit mode cannot be specified because the system is under status of replicated, executing replication, restored, executing restoration, or executing separation.
  • Page 436 Chapter 2 Message List iSM13703: Failed to connect iSM/Server. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] Socket connection failed aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check status of iSM server. iSM13704: The unexpected error has occurred in iSM/Server.
  • Page 437 Chapter 2 Message List iSM13706: No more RV can be paired with specified MV. (code=<aaa...a>- <bbb...b>-<bbb...b>-<bbb...b>) [Classification] ERROR [Explanation] Pair setting is unavailable because the number of pairs in specified MV exceeds upper limit. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check status of specified MV, and then specify pairs correctly.
  • Page 438 Chapter 2 Message List iSM13709: Conflict of volume list data has been detected. (code=<aaa...a>-<bbb...b>- <bbb...b>-<bbb...b>) [Classification] ERROR [Explanation] Inconsistency was found in volume list. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Create a volume list again.
  • Page 439 Chapter 2 Message List iSM13712: Some link paths which belong to specified Disk Array are not normal state. (code=<aaa...a>-<bbb...b>- <bbb...b>-<bbb...b>) [Classification] ERROR [Explanation] An error has been detected in some link paths among disk arrays. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures]...
  • Page 440 Chapter 2 Message List iSM13714: Disk Array includes specified volume is not managed by iSM. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] Necessary information could not be obtained because the disk array including the specified volume is not managed by iSM. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a...
  • Page 441 Chapter 2 Message List iSM13717: Control path is not set to iSM/Server. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] I/O path for disk array is not specified to use iSM server (replication management function). aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specified option is available only when I/O path for disk array is specified to use...
  • Page 442 Chapter 2 Message List iSM13720: License for DynamicDataReplication/ RemoteDataReplication is locked. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] License for DynamicDataReplication or RemoteDataReplication is not unlocked. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Unlock the license of disk array.
  • Page 443 Chapter 2 Message List iSM13723: State of Disk Array includes specified volume is ‘monitoring stop’. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] Monitoring on disk array of specified volume has been stopped. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Start monitoring on disk array.
  • Page 444 Chapter 2 Message List iSM13725: Disk Arrays can be available to replication does not exist. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] Disk array to be monitored does not exist, or disk array applicable to data replication function does not exist. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a...
  • Page 445 Chapter 2 Message List iSM13727: Attribute of specified volume is ‘<aaa...a>’. <bbb...b>:<ccc...c> (code=<ddd...d>-<eee...e>- <eee...e>-<eee...e>) [Classification] ERROR [Explanation] The following attributes are added to the specified volume. aaa...a : Volume attribute reserve: Volume with a reserve attribute (registered in a reserve group) Volume with a BV attribute Volume with an SV attribute...
  • Page 446 Chapter 2 Message List iSM13729: Failed to execute command. (all of targets) [Classification] ERROR [Explanation] Operations on all pairs failed. [Measures] Check status of pairs with failed operation and then retry command execution. iSM13730: RV of specified pair has already forced to be unpaired.
  • Page 447 Chapter 2 Message List iSM13732: Capacity of <aaa...a> license is insufficient. (code=<bbb...b>- <ccc...c>-<ccc...c>-<ccc...c>) [Classification] ERROR [Explanation] Licensed capacity is insufficient. aaa...a : License name in question DynamicDataReplication RemoteDataReplication RemoteDataReplication/DisasterRecovery bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Increase the licensed capacity and then retry command execution.
  • Page 448 Chapter 2 Message List iSM13735: Specified RV has already paired with other volume on same Disk Array as MV. (code=<aaa...a>-<bbb...b>- <bbb...b>-<bbb...b>) [Classification] ERROR [Explanation] Specified RV has already been paired as MV within the same disk. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 449 Chapter 2 Message List iSM13738: Target-control volume list data has invalid data. [Classification] ERROR [Explanation] Target-control list contains invalid information. [Measures] Create a target-control volume list again. iSM13739: Control volume is not found. [Classification] ERROR [Explanation] Control volume is not found. [Measures] Check that control volume definition file is described correctly, and then create a target-control volume list again.
  • Page 450 Chapter 2 Message List iSM13741: Failed to create socket. (code=<aaa...a>-<bbb...b>-<ccc...c>- <ddd...d>) [Classification] ERROR [Explanation] Socked creation failed. aaa...a : Process number bbb...b-ccc…c-ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] With reference to error number indicated by ddd...d in detailed information, remove cause of error and retry command execution.
  • Page 451 Chapter 2 Message List iSM13743: Failed to receive from iSM/Server. (code=<aaa...a>-<bbb...b>-<bbb...b>- <bbb...b>) [Classification] ERROR [Explanation] Message reception from iSM server failed. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check status of communication with iSM server.
  • Page 452 Chapter 2 Message List iSM13745: Illegal value of port number. <aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>- <ccc...c>) [Classification] ERROR [Explanation] Invalid value has been specified for socket port number. aaa...a : Socket port number bbb...b : Process number ccc...c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct socket port number.
  • Page 453 Chapter 2 Message List iSM13748: Failed to <aaa...a>(<bbb...b>). drive letter (<ccc...c>) (code=<eee...e>-<fff...f>-<fff...f>-<fff...f >) iSM13748: Failed to <aaa...a>(<bbb...b>). mount point volume (<ddd...d>) (code=<eee...e>-<fff...f>-<fff...f>-<fff...f >) [Classification] ERROR [Explanation] Operations on volume failed. aaa...a : Executed Operations replicate Replicate restore Restore unmount Unmount bbb...b : Volume Operations mount...
  • Page 454 Chapter 2 Message List iSM13749: Volume list data is locked by another process. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Volume list data has been created/modified by other process. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] After completion of a process, retry command execution.
  • Page 455 Chapter 2 Message List iSM13751: Volume type is not ld. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Specified volume type is not logical disk. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check a specified volume type.
  • Page 456 Chapter 2 Message List iSM13753: Disconnected from iSM/Server. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Connection with iSM server was disconnected. aaa...a : Process number bbb...b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Operations of iSM server may have stopped. Check status of iSM server. iSM13754: Replication function of iSM/Server is not ready.
  • Page 457 Chapter 2 Message List iSM13755: Command issue to <aaa...a> failed. (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Issuing operation command failed. aaa...a : Volume that failed in issuing operation command (MV, RV, or MV/RV) bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Take measures with reference to a message that was output immediately after...
  • Page 458 Chapter 2 Message List iSM13762: Illegal svflg type. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Specified SV type is invalid. aaa...a : Specified value bbb...b : Process number ccc...c : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct value.
  • Page 459 Chapter 2 Message List iSM13765: Replication and snapshot function are mixed in specified pairs. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The data replication function pair and snapshot function pair are both specified. aaa...a : Process number bbb...b : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] The data replication function pair and snapshot function pair cannot be both...
  • Page 460 Chapter 2 Message List iSM13767: Illegal volume type is specified. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Specified volume type is invalid. aaa...a : File name bbb...b : Number of lines ccc...c : Process number ddd...d : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a correct volume type and re-execute.
  • Page 461 Chapter 2 Message List iSM13769: Specified volume does not match the database volume. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The volume specified for MV or BV does not match the volume containing the target database. aaa...a : Process number bbb...b : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check whether the specified volume is correct and whether you have specified...
  • Page 462 Chapter 2 Message List iSM13771: Specified volume is under restoration. [BV:<aaa...a>] (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Specified volume is being restored. aaa...a : BV logical disk name bbb...b : Process number ccc...c : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the pair status and that restore is completed and re-execute.
  • Page 463 Chapter 2 Message List iSM13773: Specified volume is linked from LV. [{BV|SV}:<aaa...a>] (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] BV or SV is linked to LV. aaa...a : BV or SV logical disk name bbb...b : Process number ccc...c : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the pair status, remove the link (unlink), and re-execute.
  • Page 464 Chapter 2 Message List iSM13775: Deleting snapshot has terminated because "Snap State" is changed by other process. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Processing has terminated because the snapshot activity state changed from the deletion state (snap/deleting) during snapshot deletion. aaa...a : Process number bbb...b : Detail information (This code is not disorder reason but a value...
  • Page 465 Chapter 2 Message List iSM13777: The volume linked from LV exists. [BV:<aaa...a>] (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Some SV paired with BV are linked. aaa...a : BV logical disk name bbb...b : Process number ccc...c : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the pair status, remove the link connection to the volume (unlink), and...
  • Page 466 Chapter 2 Message List iSM13779: Function error has occurred. function=<aaa...a> retcode=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] A function error has occurred. aaa...a : Name of function in which an error occurred bbb...b : Code value returned by the function (refer to the table below) Code Explanation value...
  • Page 467 Chapter 2 Message List iSM13780: Specified volume is used by replication function. BV:<aaa...a> (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Replication is taking place in the specified BV. aaa...a : BV logical disk name bbb...b : Process number ccc...c : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the replication status of specified BV and re-execute.
  • Page 468 Chapter 2 Message List iSM13801: Illegal Option type is specified. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Invalid value was specified for option type in database operation file. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 469 Chapter 2 Message List iSM13803: User id is too long. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] User ID specified in database operation file is too long. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 470 Chapter 2 Message List iSM13805: Server name is too long. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] “computer name\instance name” specified in database operation file is too long. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 471 Chapter 2 Message List iSM13807: Description name is too long. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Description for the backup set specified in database operation file is too long. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a...
  • Page 472 Chapter 2 Message List iSM13809: Refile name is too long. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Standby database file name specified in database operation file is too long. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 473 Chapter 2 Message List iSM13811: OS file name is too long. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Physical file name for -move option specified in database operation file is too long. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d...
  • Page 474 Chapter 2 Message List iSM13813: Options “pass” can not be omitted are specified. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Option “pass” has been omitted in file setting of database operation file. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d...
  • Page 475 Chapter 2 Message List iSM13815: Options “uid” can not be omitted are specified. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Option “uid” has been omitted in database operation file. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 476 Chapter 2 Message List iSM13817: Specified database name is duplicated. filename=<aaa...a> line=<bbb...b> (code=<ccc...c>-<ddd...d>-<ddd...d>-< ddd...d>) [Classification] ERROR [Explanation] Specified database overlaps in database operation file. aaa...a : File name bbb...b : Number of lines ccc…c : Process number ddd…d : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a database uniquely.
  • Page 477 Chapter 2 Message List iSM13819: Insufficient database. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Database that has not been specified exists. aaa...a : Specified value bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify all databases in volume.
  • Page 478 Chapter 2 Message List iSM13821: Illegal server name. (<aaa...a>) filename=<bbb...b> line=<ccc...c> (code=<ddd...d>-<eee...e>-<eee...e>-< eee...e>) [Classification] ERROR [Explanation] Value specified by “-server” option is invalid. aaa...a : Server name bbb...b : File name ccc...c : Number of lines ddd...d : Process number eee…e : Detailed information (This code is not disorder reason but a value for maintenance.)
  • Page 479 Chapter 2 Message List iSM13823: No authority to access SQL server. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Access to Microsoft SQL Server 2000 is not authorized. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check that access to Microsoft SQL Server 2000 is authorized.
  • Page 480 Chapter 2 Message List iSM13825: Specified iopath is not supported. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] The requested function is not available under the specified I/O issue control that is currently enabled. I/O issue path control must be specified, or the setting must be changed. aaa...a : Process number bbb...b...
  • Page 481 Chapter 2 Message List iSM13827: User id is too long. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] User ID is too long. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify user ID within 64 characters (1-byte).
  • Page 482 Chapter 2 Message List iSM13829: Server name is too long. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] “computer name\instance name” is too long. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify a computer name within 255 characters (1-byte), and specify an instance name within 16 characters (1-byte).
  • Page 483 Chapter 2 Message List iSM13831: Database already exist. (<aaa...a>) (code=<bbb...b>-<ccc...c>-<ccc...c>-< ccc...c>) [Classification] ERROR [Explanation] Specified database already exists. aaa...a : Database name bbb...b : Process number ccc…c : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Detach specified database, and execute SQL command again.
  • Page 484 Chapter 2 Message List iSM13833: Database operation file name is too long. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Specified database operation file name is too long. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify database operation file name within 128 characters (1-byte).
  • Page 485 Chapter 2 Message List iSM13835: Metafolder name is too long. (code=<aaa...a>-<bbb...b>-<bbb...b>-< bbb...b>) [Classification] ERROR [Explanation] Specified metafile storing folder name is too long. aaa...a : Process number bbb…b : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify metafile storing folder name within 256 characters (1-byte).
  • Page 486 Chapter 2 Message List iSM14000 ∼ iSM14400: Information sense error : info=<aaa...a>, status=failed (<bbb...b>) [Classification] INFO [Explanation] It indicates that it failed in acquiring Disk Array information. aaa...a : Command name bbb...b : Detail of error [Measures] If an error occurred (status=failed was output), configuration or settings of disk array may have been changed.
  • Page 487 Chapter 2 Message List iSM14402: Configuration released. : Disk Array=<aaa...a>, status=<bbb...b> [Classification] INFO [Explanation] It indicates that configuration setting completed. aaa...a : Disk array name bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] An error may have occurred on the disk array or the control path.
  • Page 488 Chapter 2 Message List iSM14404: LD unbind : LDN=<aaaa>h, <aaaa>h..., status=<bbb...b> [Classification] INFO [Explanation] It indicates that the unbinding of Logical Disk was executed. aaaa : Logical disk number bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of the disk array may be changed.
  • Page 489 Chapter 2 Message List iSM14406: RANK unbind : RANK=<aa>h, <aa>h..., PDG=<bb>h, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the unbinding of RANK was executed. : RANK number : PD group number ccc...c : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of...
  • Page 490 Chapter 2 Message List iSM14408: SPARE bind : PDN=<aa>h, <aa>h..., PDG=<bb>h, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the binding of SPARE was executed. : Physical disk number : PD group number ccc...c : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures]...
  • Page 491 Chapter 2 Message List iSM14410: Set ownership : LDN=<aaaa>h, <aaaa>h..., <bbbb>, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the ownership of Logical Disk was set. aaaa : Logical disk number bbbb : Controller on which the ownership to be set (CNT0 or CNT1) ccc...c : Execution state of the command.
  • Page 492 Chapter 2 Message List iSM14412: Set Disk Array time : <aaa...a>, Disk Array=<bbb...b>, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the date and time in the Disk Array was set. aaa...a : date, time. Example (Thu May 24 14:03:01 JST 2001) bbb...b : Target disk array name ccc...c...
  • Page 493 Chapter 2 Message List iSM14414: Forced Reduce(maintenance) : RANK=<aa>h, PDN=<bb>h, PDG=<cc>h, status=<ddd...d> [Classification] INFO [Explanation] It indicates that forced reduce was instructed to specified physical disk. : RANK number : Physical disk number : PD group number ddd...d : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 494 Chapter 2 Message List iSM14416: SPARE Rebuild(maintenance) : RANK=<aa>h, PDN=<bb>h, PDG=<cc>h, Time=<dd>, status=<eee...e> [Classification] INFO [Explanation] It indicates that start of rebuilding using SPARE was instructed to specified physical disk. : RANK number : Physical disk number : PD group number : Rebuild time eee...e : Execution state of the command.
  • Page 495 Chapter 2 Message List iSM14418: Auto repair mode : mode=<aaa>, status=<bbb...b> [Classification] INFO [Explanation] It indicates that ON/OFF of the auto repair was set. : on, off bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of the disk array may be changed.
  • Page 496 Chapter 2 Message List iSM14420: FW download(maintenance) : resource=<aa>, PDG=<bb>h, number=<cc>h, <cc>h..., status=<ddd...d> [Classification] INFO [Explanation] It indicates that firmware downloading was executed. : Subjected resource : Physical disk : Host director : Disk enclosure : Service processor : PD group number (Valid only when the subjected resource is a PD.) : Resource number or all ddd...d...
  • Page 497 Chapter 2 Message List iSM14422: Media error list init(maintenance) : RANK=<aa>h, PDG=<bb>h, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the Media error list within Disk Array was initialized. : RANK number : PD group number ccc...c : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 498 Chapter 2 Message List iSM14424: Set SPARE mode : mode=<aaa>, status=<bbb...b> [Classification] INFO [Explanation] It indicates that ON/OFF of data rewrite at failure recovery was set. : on, off bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of the disk array may be changed.
  • Page 499 Chapter 2 Message List iSM14426: RANK rebuild time : RANK=<aa>h, PDG=<bb>h, Time=<cc>, status=<ddd...d> [Classification] INFO [Explanation] It indicates that RANK rebuild time was changed. : RANK number : PD group number : Rebuild time ddd...d : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 500 Chapter 2 Message List iSM14428: Auto assignment mode: mode=<aaa>, status=<bbb...b> [Classification] INFO [Explanation] It indicates that auto assignment mode was set. : on, off bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of the disk array may be changed.
  • Page 501 Chapter 2 Message List iSM14430: Set LD reserve ( ): LDN=<aaaa>h, <aaaa>h..., status=<bbb...b> [Classification] INFO [Explanation] It indicates that the logical disk was set to the reserve group. aaaa : Logical disk number bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 502 Chapter 2 Message List iSM14432: Start data initialize : LDN=<aaaa>h, <aaaa>h..., status=<bbb...b> [Classification] INFO [Explanation] It indicates that initialization of the logical disk began. aaaa : Logical disk number bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of the disk array may be changed.
  • Page 503 Chapter 2 Message List iSM14434: Change data initialize time : Time=<aa>, status=<bbb...b> [Classification] INFO [Explanation] It indicates that logical disk initialization time was changed. : Initialization time bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs (status=failed was output), the configuration or setting of the disk array may be changed.
  • Page 504 Chapter 2 Message List iSM14436: Cancel LD reserve (optimization) : LDN=<aaaa>h, <aaaa>h..., status=<bbb...b> [Classification] INFO [Explanation] It indicates that the logical disk was released from the work disk for optimization. aaaa : Logical disk number bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 505 Chapter 2 Message List iSM14438: Set Port Platform : Platform=<aa>, HD=<bb>h, Port=<cc>h, status=<ddd...d> [Classification] INFO [Explanation] The OS type of the port has been set. : Set platform : Host director number : Port number ddd...d : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 506 Chapter 2 Message List iSM14440: <aaa> Control Software update : status=failed [Classification] INFO [Explanation] Indicates failure in updating storage control software. : Subjected resource : Host director : Disk director SVP : Service processor [Measures] The configuration or setting of the disk array may be changed. After updating it to the newest information or restarting state monitoring, check current state and execute again.
  • Page 507 Chapter 2 Message List iSM14442: Reset resource : resource=<aaa>, number=<bb>h, status=<ccc...c> [Classification] INFO [Explanation] It indicates that resetting of resource or disk array started. : Subjected resource : Service processor : Whole disk array : Resource number applicable to resetting (all for the whole disk array) ccc...c : Command execution status...
  • Page 508 Chapter 2 Message List iSM14443: Set IP Address : number=<aa>h, (IP Address=<bbb...b>, Subnet Mask=<ccc...c>, Gateway Address=<ddd...d>) -> (IP Address=<eee...e>, Subnet Mask=<fff...f>, Gateway Address=<ggg...g>), status=<hhh...h> [Classification] INFO [Explanation] It indicates that IP address, subnet mask, and gateway address have been specified for the disk array. Information specified here becomes valid after resetting disk array or service processor.
  • Page 509 Chapter 2 Message List iSM14444: Set SCSI Socket permission : number=<aa>h, SCSI Socket Guard Invalid=<bbb>, SCSI Socket Valid IP Address=<ccc...c>,<ccc...c>..., status=<ddd...d> [Classification] INFO [Explanation] Indicates access restriction has been specified on monitoring server. Information specified here becomes valid after resetting disk array or service processor.
  • Page 510 Chapter 2 Message List iSM14445: Set SNMP Request permission : number=<aa>h, SNMP Valid=<bb>, Community Name=“<ccc...c>”, SNMP Valid IP Address=<ddd...d>, <ddd...d>..., status=<eee...e> [Classification] INFO [Explanation] Indicates access restriction has been specified by SNMP request. Information specified here becomes valid after resetting disk array or service processor. : Service processor number : Access restriction status by SNMP request (on or off) ccc...c...
  • Page 511 Chapter 2 Message List iSM14446: LD Bind(maintenance) : LDN=<aaaa>h, <aaaa>h..., RANK=<bb>h, PDG=<cc>h, status=<ddd...d> [Classification] INFO [Explanation] It indicates that logical disks have been configured. After normal operation, iSM14410 message is output also. aaaa : Logical disk number : RANK number : PD group number ddd...d : Command execution status...
  • Page 512 Chapter 2 Message List iSM14448: Set SNMP Trap Transmission : number=<aa>h, Community Name=“<bbb...b>”, SNMP Trap IP Address=<ccc...c>,<ccc...c>,..., status=<ddd...d> [Classification] INFO [Explanation] It indicates that sending destination of SNMP trap was specified. Information specified here becomes valid after resetting disk array or service processor. : Service processor number bbb...b : Community name...
  • Page 513 Chapter 2 Message List iSM14449: Set SNMP Trap Information : number=<aa>h, Trap Sense Interval=<bb>, Unit Contact=“<ccc...c>”, Unit Name=“<ddd...d>”, Unit Location=“<eee...e>”, Unit Info=“<fff...f>”, status=<ggg...g> [Classification] INFO [Explanation] It indicates that SNMP trap information was specified. Information specified here becomes valid after resetting disk array or service processor. : Service processor number : Trap monitoring interval (unit: second) ccc...c...
  • Page 514 Chapter 2 Message List iSM14450: Set CachePartitioning mode: mode=<aaa> initialize=<bbbb>, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the cache partitioning function has started/stopped. : Cache partitioning function starting/termination (on or off) bbbb : Initial status of settings at cache partitioning function starting (on, off, or “----”) ccc...c : Command execution status...
  • Page 515 Chapter 2 Message List iSM14451: Define cache segment : segment number=<aa>h, segment name=“<bbb...b>”, max. capacity=<ccc...c>GB, min. capacity=<ddd...d>GB, status=<eee...e> [Classification] INFO [Explanation] It indicates that the cache segment has been created. : Cache segment number bbb...b : Cache segment name ccc...c : Max.
  • Page 516 Chapter 2 Message List iSM14452: Delete cache segment : segment number=<aa>h, segment name=“<bbb...b>”, status=<ccc...c> [Classification] INFO [Explanation] It indicates that the cache segment has been deleted. : Cache segment number bbb...b : Cache segment name ccc...c : Command execution status good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 517 Chapter 2 Message List iSM14453: Set cache segment information: segment number=<aa>h, segment name=“<bbb...b>”, max. capacity=<ccc...c>GB, min. capacity=<ddd...d>GB, status=<eee...e> [Classification] INFO [Explanation] It indicates that the cache segment information has been changed. : Cache segment number bbb...b : Cache segment name ccc...c : Max.
  • Page 518 Chapter 2 Message List iSM14454: Assign LD to cache segment : segment number=<aa>h, segment name=“<bbb...b>”, LDN=<ccc...c>, <ccc...c>..., status=<ddd...d> [Classification] INFO [Explanation] It indicates that LD assigned to cache segment has been changed. : Number of cache segment to which LD was added bbb...b : Name of cache segment to which LD was added ccc...c...
  • Page 519 Chapter 2 Message List iSM14456: Pool bind : Pool number=<aaaa>h, Type=<bbb...b>, PD count=<cccc>, PDN=<dd>h-<ee>h, <dd>h-<ee>h, ..., Time=<ff>, RAID=<ggg...g>, status=<hhh...h> [Classification] INFO [Explanation] It indicates that pool bind has been executed. aaaa : Pool number bbb...b : Pool type dynamic : Dynamic basic : Basic cccc...
  • Page 520 Chapter 2 Message List iSM14457: Pool unbind : Pool number=<aaaa>h, PD count=<bbbb>, PDN=<cc>h-<dd>h, <cc>h-<dd>h, ..., status=<eee...e> [Classification] INFO [Explanation] It indicates that pool unbind has been executed. aaaa : Pool number bbbb : Number of physical disks : PD group number : Physical disk number eee...e : Execution state of the command...
  • Page 521 Chapter 2 Message List iSM14458: Pool expansion : Pool number=<aaaa>h, PD count=<bbbb>, PDN=<cc>h-<dd>h, <cc>h-<dd>h, ..., restruct=<eee>, Time=<fff>, status=<ggg...g> [Classification] INFO [Explanation] It indicates that pool expansion has been executed. aaaa : Pool number bbbb : Number of physical disks : PD group number : Physical disk number : Rebuilding : With pool rebuilding...
  • Page 522 Chapter 2 Message List iSM14459: Pool rebuild/expansion time : Pool number=<aaaa>h, rebuild time=<bb>, expansion time=<ccc>, status=<ddd...d> [Classification] INFO [Explanation] It indicates that the pool expansion time has been changed. aaaa : Pool number : Rebuild time : Expansion time ddd...d : Execution state of the command good : Normal...
  • Page 523 Chapter 2 Message List iSM14461: LD bind : LDN=<aaaa>h, <aaaa>h..., Pool number=<bbbb>h, LD capacity=<ccc...c>GB, Time=<dd>, status=<eee...e> [Classification] INFO [Explanation] It indicates that LD bind has been executed. aaaa : Logical disk number bbbb : Pool number ccc...c : Logical disk capacity : Binding time eee...e : Execution state of the command...
  • Page 524 Chapter 2 Message List iSM14462: LD expansion : LDN=<aaaa>h, LD capacity=<bbb...b>GB, Time=<cc>, status=<ddd...d> [Classification] INFO [Explanation] It indicates that LD expansion has been executed. aaaa : Logical disk number bbb...b : Logical disk capacity (after expansion) : Expansion time ddd...d : Execution state of the command good : Normal...
  • Page 525 Chapter 2 Message List iSM14467: SRA expansion : LD(SDV) number=<aaaa>h,<aaaa>h..., Pool number=<bbbb>h, SRA capacity=<ccc...c>GB, threshold=<ddd...d>GB(<ee>%), status=<fff...f> [Classification] INFO [Explanation] It indicates that SRA was expanded. aaaa : Logical disk (SDV) number bbbb : Pool number ccc...c : SRA capacity (GB) ddd...d : Threshold (GB) : Threshold (%)
  • Page 526 Chapter 2 Message List iSM14468: SRA bind : LD(SDV) number=<aaaa>h,<aaaa>h..., Pool number=<bbbb>h, SRA capacity=<ccc...c>GB, threshold=<ddd...d>GB(<ee>%), status=<fff...f> [Classification] INFO [Explanation] It indicates that SRA was bound. aaaa : Logical disk (SDV) number bbbb : Pool number ccc...c : SRA capacity (GB) ddd...d : Threshold (GB) : Threshold (%)
  • Page 527 Chapter 2 Message List iSM14469: LV bind : LD(LV) number=<aaaa>h,<aaaa>h...(LD(BV) number=<bbbb>h,<bbbb>h...), Pool number=<cccc>h, status=<ddd...d> [Classification] INFO [Explanation] It indicates that LV was bound. aaaa : Logical disk (LV) number bbbb : Logical disk (BV) number permitted to be linked cccc : Pool number ddd...d : Execution state of the command.
  • Page 528 Chapter 2 Message List iSM14470: SV bind : LD(SV) number=<aaaa>h,<aaaa>h...(LD(BV) number=<bbbb>h), Pool number=<cccc>h, SV count=<dd>, status=<eee...e> [Classification] INFO [Explanation] It indicates that a generation was added (SV was bound). aaaa : Logical disk (SV) number bbbb : Number of logical disk (BV) to which the generation is added cccc : Pool number : Number of generations to be added...
  • Page 529 Chapter 2 Message List iSM14471: SRA unbind : Pool number=<aaaa>h, LD(SDV) number=<bbbb>h,<bbbb>h..., status=<ccc...c> [Classification] INFO [Explanation] It indicates that SRA was unbound. aaaa : Pool number bbbb : Logical disk (SDV) number ccc...c : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description)
  • Page 530 Chapter 2 Message List iSM14472: SV unbind : LD(SV) number=<aaaa>h,<aaaa>h...(LD(BV) number=<bbbb>h), SV count=<cc>, status=<ddd...d> [Classification] INFO [Explanation] It indicates that a generation was removed (SV was unbound). aaaa : Logical disk (SV) number bbbb : Number of logical disk (BV) from which the generation is removed : Number of generations to be removed ddd...d...
  • Page 531 Chapter 2 Message List iSM14474: SRA threshold : Pool number=<aaaa>h, threshold=<bbb...b>GB (<cc>%), status=<ddd...d> [Classification] INFO [Explanation] It indicates that threshold was changed. aaaa : Pool number bbb...b : Threshold (GB) : Threshold (%) ddd...d : Execution state of the command. good : Normal failed(xxxx)
  • Page 532 Chapter 2 Message List iSM14476: Configuration released(reference mode).: Disk Array=<aaa...a>, status=<bbb...b> [Classification] INFO [Explanation] It indicates that the reference mode of configuration setting is ended. aaa...a : Disk array name bbb...b : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures]...
  • Page 533 Chapter 2 Message List iSM14601: Forced termination : status=<aaa...a> [Classification] INFO [Explanation] It indicates that the “Configurating” state was forcefully canceled. aaa...a : Execution state of the command. good : Normal failed(xxxx) : Error occurred (xxxx is error description) [Measures] When an error occurs, check whether any abnormality has occurred in the processes making up the iSM server or in the operation environment, then restart the iSM server.
  • Page 534 Chapter 2 Message List iSM15000 ∼ iSM15600: Internal error : detail=<aaa...a>, code=<bbbb> [Classification] INFO [Explanation] It indicates that such internal error as communication error and system call error occurred. aaa...a : The following output will be provided depending on an error content.
  • Page 535 Chapter 2 Message List iSM16000 ~ iSM16001: iSMalived process has started. function=<aaa...a> AUTH=<bbb...b> [Classification] INFO [Explanation] It indicates that ALIVEmail process has started. aaa...a : Function name that has started SG Error : Process has started, but notification is not executed because of SG setting error (function blockage state).
  • Page 536 Chapter 2 Message List iSM16021: Internal Error has occurred. code=<aaaa> errno=<bbb> [Classification] NOTICE [Explanation] It shows that an internal error has occurred. aaaa : Internal code : Error number [Measures] Check the server operating environment and various settings. iSM16029: File does not exist. file=<aaa...a> [Classification] WARNING [Explanation]...
  • Page 537 Chapter 2 Message List iSM16030: File cannot be opened. errno=<aaa> file= <bbb...b> [Classification] WARNING [Explanation] It shows that opening of the ALIVEmail setting file or message information table file has failed. : Error number bbb...b : File name alived.conf : Setting file alived.tbl : Message information table file alived.hst...
  • Page 538 Chapter 2 Message List iSM16033: Illegal configuration. file=alived.conf Tag overlaps. line=<aa> tag=<bbb...b> [Classification] WARNING [Explanation] It indicates that the tags overlap in the ALIVEmail setting file. : Error line number bbb...b : Tag name [Measures] Check the syntax of the ALIVEmail setting file and correct it. iSM16034: Illegal configuration.
  • Page 539 Chapter 2 Message List iSM16035: Illegal configuration. file=alived.conf id=<a> line=<bb> [Classification] WARNING [Explanation] It indicates that there is Invalid description in the ALIVEmail setting file. : Error classification 1: Improper position of “=”, or no “=” 2: Improper position of “:”, or no “:” 3: Improper position of “,”, or too many “,”...
  • Page 540 Chapter 2 Message List iSM16038: Illegal configuration. file=alived.conf It has exceeded 256 bytes. line=<aa> [Classification] WARNING [Explanation] It indicates that the applicable line of the ALIVEmail setting file exceeds 256 bytes. : Error line number [Measures] Check the applicable line of the ALIVEmail setting file, and correct it 256 bytes or less.
  • Page 541 Chapter 2 Message List iSM16043: Illegal configuration. file=alived.tbl Tag overlaps. line=<aa> tag=<bbb...b> [Classification] WARNING [Explanation] It indicates that the tags overlap in the ALIVEmail message information table file. : Error line number bbb...b : Tag name [Measures] Check the syntax of the ALIVEmail message information table file and correct it. iSM16044: Illegal configuration.
  • Page 542 Chapter 2 Message List iSM16045: Illegal configuration. file=alived.tbl id=<a> line=<bb> [Classification] WARNING [Explanation] It indicates that there is Invalid description in the ALIVEmail message information table file. : Error classification 1: Improper position of “=”, or no “=” 5: Improper position of “,” 8: No description of address : Error line number [Measures]...
  • Page 543 Chapter 2 Message List iSM16048: Illegal configuration. file=alived.tbl It has exceeded 256 bytes. line=<aa> [Classification] WARNING [Explanation] It indicates that the applicable line of the ALIVEmail message information table file exceeds 256 bytes. : Error line number [Measures] Check the applicable line of the ALIVEmail message information table file, and correct it in 256 bytes or less.
  • Page 544 Chapter 2 Message List iSM16062: Mail server cannot be connected. name=<aaa...a> code=<bbbb> errno=<ccc> [Classification] WARNING [Explanation] It indicates that the connection to mail server has failed. aaa...a : Function name bbbb : Internal code : Error number [Measures] Failed in connection with mail server specified in the ALIVEmail setting file. Check the address and operations of the specified mail server.
  • Page 545 Chapter 2 Message List iSM16064: Communication error(send to mail server). name=<aaa...a> code=<bbbb> errno=<ccc> [Classification] WARNING [Explanation] It indicates that transmitting to mail server has failed. aaa...a : Function name bbbb : Internal code : Error number [Measures] Check the operations of the specified mail server, and resolve the problem. iSM16065: Communication error(mail server).
  • Page 546 Chapter 2 Message List iSM16070: Message buffer is full. Data losing is detected. [Classification] WARNING [Explanation] It indicates that messages have been deleted because the message buffer capacity exceeded the limit. [Measures] There are too many messages for link. Definition must be reviewed. iSM16071: Data losing is recovered.
  • Page 547 Chapter 2 Message List iSM16080: Definition change is successful. function=<aaa...a> AUTH=<bbb...b> [Classification] INFO [Explanation] It indicates that the setting information change was successful. aaa...a : Function name that has started Alert : Error report Heartbeat : Heartbeat report Regulary : Periodical error report RunningMainte : Scheduled maintenance report bbb...b : Authentication method for accessing a mail server...
  • Page 548 Chapter 2 Message List iSM16082: Definition change error. ALIVEmail function continues to operate by old one. [Classification] WARNING [Explanation] The setting file change was failed. The driven function operates by the old function before changing. [Measures] While trying to change the setting information with the iSM server running, the definition error occurred.
  • Page 549 Chapter 2 Message List iSM17000 ∼ iSM17001: Ftp environment(user) is not defined. File Transfer function can not be used. detail=<aa-bbbb> [Classification] NOTICE [Explanation] File transfer function cannot be used because FTP user name has not been defined. aa-bbbb : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify correct description of file_transfer section (user) in environment...
  • Page 550 Chapter 2 Message List iSM17003: Ftp environment(temp_directory) is invalid. File Transfer function can not be used. detail=<aa-bbbb> [Classification] NOTICE [Explanation] File transfer function cannot be used because work file storing directory has not been defined correctly. aa-bbbb : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Specify correct description of file_transfer section (temp_directory) in...
  • Page 551 Chapter 2 Message List iSM17010: File access has failed. func=<aaa...a> path=<bbb...b> errno=<ccc> detail=<dd-eeee> [Classification] NOTICE [Explanation] An error occurred in file access function. aaa...a : Function name bbb...b : Path name : Error number dd-eeee : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check function name and error number, take appropriate measures, and restart...
  • Page 552 Chapter 2 Message List iSM17030: Memory access has failed. func=<aaa...a> errno=<bbb> detail=<cc-dddd> [Classification] WARNING [Explanation] An error occurred in memory access function. iSM server terminates abnormally. aaa...a : Function name : Error number cc-dddd : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Check function name and error number, take appropriate measures, and restart...
  • Page 553 Chapter 2 Message List iSM17050: Internal error has occurred. detail=<aa-bbbb> [Classification] WARNING [Explanation] An internal error occurred in file transfer function. iSM server terminates abnormally. aa-bbbb : Detailed information (This code is not disorder reason but a value for maintenance.) [Measures] Save the following information and restart the iSM server.
  • Page 554 Chapter 2 Message List iSM18000 ∼ iSM18001: Snapshot has been created. (<aaa...a>, BV=<bbb...b> (<cccc>h), SV=<ddd...d> (<eeee>h)) [Classification] INFO [Explanation] It indicates that snapshot was created. aaa...a : Disk array name bbb...b : BV logical disk name cccc : BV logical disk number ddd...d : SV logical disk name eeee...
  • Page 555 Chapter 2 Message List iSM18003: Snapshot has been deleted. (<aaa...a>, BV=<bbb...b> (<cccc>h), SV=<ddd...d> (<eeee>h)) [Classification] INFO [Explanation] It indicates that snapshot deletion was completed. aaa...a : Disk array name bbb...b : BV logical disk name cccc : BV logical disk number ddd...d : SV logical disk name eeee...
  • Page 556 Chapter 2 Message List iSM18005: Snapshot has been restored. (<aaa...a>, BV=<bbb...b> (<cccc>h), SV=<ddd...d> (<eeee>h)) [Classification] INFO [Explanation] It indicates that snapshot restoring was completed. aaa...a : Disk array name bbb...b : BV logical disk name cccc : BV logical disk number ddd...d : SV logical disk name eeee...
  • Page 557 Chapter 2 Message List iSM18007: Snapshot was cancelled. (<aaa...a>, BV=<bbb...b> (<cccc>h), SV=<ddd...d> (<eeee>h), generation=<fff>) [Classification] ERROR [Explanation] It indicates that snapshot was cancelled due to insufficient capacity of snapshot reserve area or other cause. Snapshot data is no longer accessible once snapshot is cancelled.
  • Page 558 Chapter 2 Message List iSM18008: Snapshot was nullified. (<aaa...a>, BV=<bbb...b> (<cccc>h), SV=<ddd...d> (<eeee>h), generation=<fff>) [Classification] NOTICE [Explanation] It indicates that snapshot was nullified because an old snapshot is restored. Snapshot data is no longer accessible once snapshot is nullified. aaa...a : Disk array name bbb...b : BV logical disk name...
  • Page 559 Chapter 2 Message List iSM18202: Failed to delete snapshot. (<aaa...a>, BV=<bbb...b> (<cccc>h), SV=<ddd...d> (<eeee>h), generation=<fff>, code=<ggg...g>) [Classification] WARNING [Explanation] It indicates that snapshot deletion failed. aaa...a : Disk array name bbb...b : BV logical disk name cccc : BV logical disk number ddd...d : SV logical disk name eeee...
  • Page 560 Chapter 2 Message List iSM18204: Failed to change SV guard of snapshot-volume. (<aaa...a>, SV=<bbb...b> (<cccc>h), code=<ddd...d>) [Classification] WARNING [Explanation] It indicates that the protection mode of snapshot-volume cannot be changed. aaa...a : Disk array name bbb...b : SV logical disk name cccc : SV logical disk number ddd...d...
  • Page 561 Chapter 2 Message List iSM18301: System call error has occurred. (func=<aaa...a>, code=<bbb...b>, errno=<cccc>) [Classification] ERROR [Explanation] It indicates that a system call error has occurred. aaa...a : Abnormally terminated function name bbb...b : Internal error code indicating the type of abnormal state cccc : Error number [Measures]...
  • Page 562 Chapter 2 Message List iSM18311: Internal communication error has occurred. (code=<aaa...a>) [Classification] ERROR [Explanation] In indicates that an internal communication error has occurred. aaa...a : Internal error code indicating the type of abnormal state [Measures] Collect necessary information according to the iSM error information collection procedure, and restart the iSM server.
  • Page 563 Chapter 2 Message List iSM18501: Access mode was changed. (<aaa...a>, LD=<bbb...b> (<cccc>h), mode from <ddd...d> to <eee...e>) [Classification] INFO [Explanation] It indicates that the volume access mode was changed. aaa...a : Disk array name bbb...b : Logical disk name cccc : Logical disk number ddd...d : Access mode before change...
  • Page 564 Chapter 2 Message List iSM18503: Logical disk was unlinked from link-volume.(<aaa...a>,LV=<bbb...b>(< cccc>h), LD=<ddd...d>(<eeee>h)) [Classification] INFO [Explanation] It indicates that the volume was unlinked from the link-volume. aaa...a : Disk array name bbb...b : Logical disk name of link-volume cccc : Logical disk number of link-volume ddd...d : Logical disk name of destination-volume eeee...
  • Page 565 Chapter 2 Message List iSM18602: Failed to link logical disk to link-volume.(<aaa...a>,LV=<bbb...b>(< cccc>h), LD=<ddd...d>(<eeee>h),code=<fff...f>) [Classification] WARNING [Explanation] It indicates that the volume cannot be linked to the link-volume. aaa...a : Disk array name bbb...b : Logical disk name of link-volume cccc : Logical disk number of link-volume ddd...d...
  • Page 566 Chapter 2 Message List iSM18999: Unexpected error has occurred. (code=<aaa...a>) [Classification] WARNING [Explanation] In indicates that an unexpected error has occurred. aaa...a : Error code indicating the type of abnormal state [Measures] Collect necessary information according to the iSM error information collection procedure, and restart the iSM server.
  • Page 567 Chapter 2 Message List iSM19000 ∼ iSM19000: <aaa...a> [Classification] INFO [Explanation] Executed command line. aaa...a : Entered character string [Measures] Unnecessary iSM19010: iSMsc_create has normally terminated. [Classification] INFO [Explanation] iSMsc_create command normal termination message. [Measures] Unnecessary iSM19011: iSMsc_create has normally terminated. [BV:<aaa...a>] [SV:<bbb...b>] [Classification] INFO...
  • Page 568 Chapter 2 Message List iSM19013: iSMsc_create has abnormally terminated. [BV:<aaa...a>] [SV:<bbb...b>] [Classification] INFO [Explanation] iSMsc_create command abnormal termination message. aaa...a : Volume name bbb...b : Volume name [Measures] Check the message displayed immediately before to handle it. iSM19020: iSMsc_delete has normally terminated.
  • Page 569 Chapter 2 Message List iSM19022: iSMsc_delete has abnormally terminated. [Classification] INFO [Explanation] iSMsc_delete command abnormal termination message. [Measures] Check the message displayed immediately before to handle it. iSM19023: iSMsc_delete has abnormally terminated. [BV:<aaa...a>] [SV:<bbb...b>] [Classification] INFO [Explanation] iSMsc_delete command abnormal termination message. aaa...a : Volume name bbb...b...
  • Page 570 Chapter 2 Message List iSM19031: iSMsc_restore has normally terminated. [BV:<aaa...a>] [SV:<bbb...b>] [Classification] INFO [Explanation] iSMsc_restore command normal termination message. aaa...a : Volume name bbb...b : Volume name [Measures] Unnecessary iSM19032: iSMsc_restore has abnormally terminated. [Classification] INFO [Explanation] iSMsc_Restore command abnormal termination message. [Measures] Check the message displayed immediately before to handle it.
  • Page 571 Chapter 2 Message List iSM19034: iSMsc_restore has accepted the request. [Classification] INFO [Explanation] It indicates that the iSMsc_restore command has accepted the request. [Measures] Unnecessary iSM19035: iSMsc_restore has accepted the request. [BV:<aaa...a>] [SV:<bbb...b>] [Classification] INFO [Explanation] It indicates that the iSMsc_restore command has accepted the request. aaa...a : Volume name bbb...b...
  • Page 572 Chapter 2 Message List iSM19101: The volume linked from LV cannot be specified. [{BV|SV}:<aaa...a>] [Classification] ERROR [Explanation] It indicates that the request cannot be accepted because BV or SV is linked to aaa...a : Volume name [Measures] Remove the link (unlink) with the iSMcc_unlink command and re-execute. iSM19102: The volume mounted cannot be specified.
  • Page 573 Chapter 2 Message List iSM19104: The volume is not paired cannot be specified. [BV:<aaa...a>] [SV:<bbb...b>] [Classification] ERROR [Explanation] It indicates that the request cannot be accepted because the specified volume has no pair setting. aaa...a : Volume name bbb...b : Volume name [Measures] Check the volume and re-execute.
  • Page 574 Chapter 2 Message List iSM19107: State of SV's access mode is invalid. (mode=<aaa...a>) [SV:<bbb...b>] [Classification] ERROR [Explanation] The command cannot be executed because the SV access restriction is not "Not Ready". aaa...a : SV access restriction Input/output allowed Read only Access prohibited bbb...b : Volume name...
  • Page 575 Chapter 2 Message List iSM19110: The volume of SV guard exists. [SV:<aaa...a>] [Classification] ERROR [Explanation] It indicates that the request cannot be accepted because BV contains protected aaa...a : Logical disk name of relevant volume [Measures] Deactivate the protection for relevant volume and re-execute. iSM19111: Version of API is invalid.
  • Page 576 Chapter 2 Message List iSM19113: Volume list does not exist. [Classification] ERROR [Explanation] Volume list is invalid. Or, the volume list version is not correct. [Measures] Re-create the volume list. iSM19114: License for snapshot is locked. [Classification] ERROR [Explanation] The snapshot product has not been purchased. [Measures] Purchase the product to perform snapshot operation.
  • Page 577 Chapter 2 Message List iSM19117: Specified drive type is not supported.(type=<aaa...a>) [Classification] ERROR [Explanation] Specified drive type is not supported. This message is output on Windows system. aaa...a : Drive type Dynamic Disk. Dynamic disk GPT Partition Disk. : GPT partition disk Multi Partition Disk.
  • Page 578 Chapter 2 Message List iSM19120: The operation to the volume specified is forbidden. (type=<aaa...a>) [Classification] ERROR [Explanation] The command was issued to the volume of which OS type is not supported. This message is output on Windows system. aaa...a : OS type [Measures] Check the OS type and re-execute.
  • Page 579 Chapter 2 Message List iSM19123: The volume which is not recognized cannot be specified. [BV:<aaa...a>] [Classification] ERROR [Explanation] It indicates that the request cannot be accepted because the command was issued to the volume invisible to the self host. aaa...a : Volume name [Measures] Check the volume and re-execute.
  • Page 580 Chapter 2 Message List iSM19127: Request has already completed. [Classification] INFO [Explanation] It indicates that the request is already satisfied. [Measures] Unnecessary iSM19200: Mandatory option was not specified. (<aaa...a>) [Classification] ERROR [Explanation] Specified command does not have some required arguments, or invalid arguments are specified.
  • Page 581 Chapter 2 Message List iSM19203: Number of BV and SV was not equal. [Classification] ERROR [Explanation] The number of volumes specified for BV and SV is different. This message is output on UNIX system. [Measures] Make the number of BV and SV volumes equal. iSM19208: Illegal configuration was detected.
  • Page 582 Chapter 2 Message List iSM19210: Number of BV and SV was not equal. (file =<aaa...a>,line=<bbb...b>) [Classification] ERROR [Explanation] The number of volumes specified for BV and SV is different. aaa...a : File name bbb...b : Number of lines [Measures] Make the number of BV and SV volumes equal. iSM19212: Duplicated targets were detected.
  • Page 583 Chapter 2 Message List iSM19301: The unexpected error has occurred in iSM/Server. (code=aaa...a/bb/ccc...c) [Classification] ERROR [Explanation] An unexpected error has occurred. aaa...a : Process number : Detail information (This code is not disorder reason but a value for maintenance.) ccc...c : Error detail code [Measures] Abnormality was found in message from iSM server.
  • Page 584 Chapter 2 Message List iSM19305: The timeout was detected by waiting of communication with iSM/Server. [Classification] ERROR [Explanation] Time-out occurred in socket exclusive control. [Measures] Another process may control the socket. Check status of iSM server and re-execute. iSM19306: Failed to connect iSM/Server.(errno=<aaa...a>, phase=<...
  • Page 585 Chapter 2 Message List iSM19308: Failed to send to iSM/Server.(errno=<aaa...a>, phase=<bbb...b>) [Classification] ERROR [Explanation] Failed in sending messages to iSM server. aaa...a : System call error number bbb...b : Error detail code [Measures] Check connection status of iSM server. iSM19401: System call error has occurred.(func=<aaa...a>, errno=<bbbb>, phase=<ccc...c>) [Classification]...
  • Page 586 Chapter 2 Message List iSM19403: Failed to mount. [Classification] ERROR [Explanation] Mounting failed. This message is output on Windows system. [Measures] Check the message displayed immediately before to handle it. iSM19404: Failed to umount. [Classification] ERROR [Explanation] Unmounting failed. This message is output on Windows system. [Measures] Check the message displayed immediately before to handle it.
  • Page 587 Chapter 2 Message List iSM20000 ∼ iSM20000: <aaa...a> [Classification] INFO [Explanation] Executed command line. aaa...a : Entered character string [Measures] Unnecessary iSM20010: iSMsc_chgmod has normally terminated. [Classification] INFO [Explanation] iSMsc_chgmod command normal termination message. [Measures] Unnecessary iSM20011: iSMsc_chgmod has normally terminated.
  • Page 588 Chapter 2 Message List iSM20013: iSMsc_chgmod has abnormally terminated. [vol:<aaa...a>] [Classification] ERROR [Explanation] iSMsc_chgmod command abnormal termination message. aaa...a : Volume name [Measures] Check the message displayed immediately before to handle it. iSM20020: iSMsc_link has normally terminated. [Classification] INFO [Explanation] iSMsc_link command normal termination message.
  • Page 589 Chapter 2 Message List iSM20023: iSMsc_link has abnormally terminated. [LV:<aaa...a>] [SV:<bbb...b>] [Classification] INFO [Explanation] iSMsc_link command abnormal termination message. aaa...a : Volume name bbb...b : Volume name [Measures] Check the message displayed immediately before to handle it. iSM20030: iSMsc_unlink has normally terminated.
  • Page 590 Chapter 2 Message List iSM20032: iSMsc_unlink has abnormally terminated. [Classification] INFO [Explanation] iSMsc_unlink command abnormal termination message. [Measures] Check the message displayed immediately before to handle it. iSM20033: iSMsc_unlink has abnormally terminated. [LV:<aaa...a>][SV:<bbb...b>] [Classification] INFO [Explanation] iSMsc_unlink command abnormal termination message. aaa...a : Volume name bbb...b...
  • Page 591 Chapter 2 Message List iSM20101: The volume from which capacity is different cannot be specified. [LV:<aaa...a>] [{BV|SV}:<bbb...b>] [Classification] ERROR [Explanation] It indicates that the request cannot be accepted because the capacity of LV is different from that of BV or SV. aaa...a : Volume name bbb...b...
  • Page 592 Chapter 2 Message List iSM20104: State of SV's access mode is invalid. (mode=<aaa...a>) [SV:<bbb...b>] [Classification] ERROR [Explanation] It indicates that the request cannot be accepted because the access restriction of specified volume is not "Not Ready". aaa...a : Access restriction of specified volume Input/output allowed Read only Access prohibited...
  • Page 593 Chapter 2 Message List iSM20108: SV which is not snap/active cannot be specified. [SV:<aaa...a>] [Classification] ERROR [Explanation] Link cannot be set because SV with snapshot inactive is specified as link connection volume. aaa...a : Volume name [Measures] Check the SV status and re-execute. iSM20109: The volume which is not link target volume cannot be specified.
  • Page 594 Chapter 2 Message List iSM20116: Version of API is invalid. [Classification] ERROR [Explanation] API version is invalid. [Measures] Use the API with the correct version. iSM20117: License for snapshot is locked. [Classification] ERROR [Explanation] The snapshot product has not been purchased. [Measures] Purchase the product to perform snapshot operation.
  • Page 595 Chapter 2 Message List iSM20120: Link information does not exist. [VOL:<aaa...a>] [Classification] ERROR [Explanation] The command cannot be executed because the specified volume is neither LV nor link target volume. aaa...a : Volume name [Measures] Check the volume and re-execute. iSM20121: The volume which is not recognized cannot be specified.
  • Page 596 Chapter 2 Message List iSM20123: State of specified diskarray is 'freeze'. [Classification] ERROR [Explanation] The disk array where specified volume is stored is in the freeze state. [Measures] Cancel the freeze state and re-execute. iSM20200: Mandatory option was not specified.(<aaa...a>) [Classification] ERROR [Explanation]...
  • Page 597 Chapter 2 Message List iSM20203: Specified volume group does not exist.(vg=<aaa...a>) [Classification] ERROR [Explanation] Specified volume group is invalid. aaa...a : Volume group [Measures] Specify a correct volume group. iSM20204: Specified disk group does not exist.(dg=<aaa...a>) [Classification] ERROR [Explanation] Specified disk group is invalid. aaa...a : Disk group [Measures]...
  • Page 598 Chapter 2 Message List iSM20206: Specified file does not exist. (file=<aaa...a>) [Classification] ERROR [Explanation] Specified file does not exist. aaa...a : File name [Measures] Specify a correct file name. iSM20207: Specified file is invalid.(illegal file type) (file=<aaa...a>) [Classification] ERROR [Explanation] The specified file type cannot be processed.
  • Page 599 Chapter 2 Message List iSM20209: Illegal option value was detected. (file=<aaa...a>, line=<bbb...b>) [Classification] ERROR [Explanation] Specified file contains invalid options. [Measures] Correct the file and re-execute. iSM20210: Empty file cannot be specified. (file=<aaa...a>) [Classification] ERROR [Explanation] Specified file is empty. aaa...a : File name [Measures]...
  • Page 600 Chapter 2 Message List iSM20301: The unexpected error has occurred in iSM/Server. (code=aaa...a/bb/ccc...c) [Classification] ERROR [Explanation] An unexpected error has occurred. aaa...a : Process number : Detail information (This code is not disorder reason but a value for maintenance.) ccc...c : Error detail code [Measures] Abnormality was found in message from iSM server.
  • Page 601 Chapter 2 Message List iSM20304: Timeout error has occurred in iSM/Server. [Classification] ERROR [Explanation] Time-out occurred in process of iSM server. [Measures] Loads on iSM server may be too heavy. Check status of iSM server and re-execute. iSM20305: The timeout was detected by waiting of communication with iSM/Server.
  • Page 602 Chapter 2 Message List iSM20307: Failed to receive from iSM/Server.(errno=<aaa...a>, phase=<bbb...b>) [Classification] ERROR [Explanation] Failed in receiving messages from iSM server. aaa...a : System call error number bbb...b : Error detail code [Measures] Check connection status with iSM server. iSM20308: Failed to send to iSM/Server.(errno=<aaa...a>, phase=<bbb...b>) [Classification]...
  • Page 603 Chapter 2 Message List iSM20402: Unexpected error occurred. (phase=<aaa...a>) [Classification] ERROR [Explanation] An unexpected error has occurred. aaa...a : Error detail code [Measures] Check the details and re-execute. iSM20403: SCSI I/O error is detected. (device=aaaa, cdb =bbbb,status=cccc/dddd/ee/ff/gg) [Classification] ERROR [Explanation] An error has occurred during SCSI command execution.
  • Page 604 Chapter 2 Message List iSM20404: Control path is blockaded. (device=aaaa, cdb =bbbb,status=cccc/dddd/ee/ff/gg) [Classification] WARNING [Explanation] Paths are switched. aaa...a : Failed device name bbbb : Command Descriptor Block of issued command cccc : SCSI command execution result dddd : SCSI sense result : SCSI sense information SenseKey : SCSI sense information SenseCode : SCSI sense information Qualifier...
  • Page 605 Chapter 2 Message List iSM20406: Failed to umount. [Classification] ERROR [Explanation] Unmounting failed. This message is output on Windows system. [Measures] Check the message displayed immediately before to handle it.
  • Page 606 Chapter 2 Message List iSM99000 ∼ iSM99001: Connected with iSM server (Server=<aaa...a>, Port=<bbb...b>, User=<ccc...c>, Client=<ddd...d>) [Classification] INFO [Explanation] It has connected with the server (internal message of iSM client). aaa...a : Server name bbb...b : Port name ccc...c : User name ddd...d : Client name iSM99002: Disconnected with iSM server...
  • Page 607 Chapter 2 Message List iSMnetconf: 001 ∼ iSMnetconf: 001 Command complete successfully. [Classification] INFO [Explanation] Succeeded in command execution. [Measures] Unnecessary iSMnetconf: 101 Command has failed. (<aaa...a>) [Classification] INFO [Explanation] Failed in SCSI command execution. aaa...a : Additional information [Measures] Service processor was not set correctly.
  • Page 608 Chapter 2 Message List iSMnetconf: 112 Changed to the alternative path. (<aaa...a>) [Classification] INFO [Explanation] Switched to alternative path. aaa...a : Additional information [Measures] Unnecessary iSMnetconf: 201 Resource does not exist. (<aaa...a>) [Classification] INFO [Explanation] Applicable resource does not exist. aaa...a : Additional information [Measures]...
  • Page 609 Chapter 2 Message List iSMnetconf: 211 Specified Disk Array Subsystem is not supported. (<aaa...a>) [Classification] INFO [Explanation] Specified disk array is not supported by this program. aaa...a : Additional information [Measures] Specify a special file that indicates disk array that is applicable to this program. iSMnetconf: 212 Specified Disk Array Subsystem is set by another maintenance tool.
  • Page 610 Chapter 2 Message List iSMnetconf: 222 Specified parameter is illegal. (<aaa...a>) [Classification] INFO [Explanation] Specified parameter is invalid. aaa...a : Additional information [Measures] Specify a valid parameter. iSMnetconf: 223 Specified IP Address is alive. (<aaa...a>) [Classification] INFO [Explanation] Specified IP address is being used by other network device. aaa...a : Additional information [Measures]...
  • Page 611 Chapter 2 Message List iSMnetconf: 225 Specified Subnet Mask is illegal. (<aaa...a>) [Classification] INFO [Explanation] Specified subnet mask is invalid. aaa...a : Additional information [Measures] Specify a valid subnet mask. iSMnetconf: 226 Specified Gateway Address is illegal. (<aaa...a>) [Classification] INFO [Explanation] Specified gateway address is invalid.
  • Page 612 Chapter 2 Message List iSMnetconf: 228 Specified IP Address is already registered. (<aaa...a>) [Classification] INFO [Explanation] Specified IP address has already been registered. aaa...a : Additional information [Measures] Specify an IP address that has not yet been registered. iSMnetconf: 229 Specified IP Address is not registered.
  • Page 613 Chapter 2 Message List iSMnetconf: 241 Specified file cannot be read. [Classification] INFO [Explanation] Specified file cannot be read. [Measures] Check that specified file name is correct and authority to access file is given. iSMnetconf: 242 File format is illegal. (<aaa...a>) [Classification] INFO [Explanation]...
  • Page 614 Chapter 2 Message List iSMprfarc: 101 ∼ iSMprfarc: 101 Not PSL file -- <aaa...a> [Explanation] The specified file is not a statistic info file. aaa...a : Specified file name [Measures] Specify the correct file. iSMprfarc: 102 Can’t open file -- <aaa...a> func=<bbb...b>...
  • Page 615 Chapter 2 Message List iSMprfarc: 105 Can’t input multi-level file [Explanation] Statistic information history files and statistic information primary summarized files cannot be mixed. [Measures] Specify either statistic information history files or statistic information primary summarized files. iSMprfarc: 106 Out of range -- <aaaa> [Explanation] The specified target period of summarizing is erroneous.
  • Page 616 Chapter 2 Message List iSMprfarc: 110 Read error -- <aaa...a> func=<bbb...b> errno=<cccc> [Explanation] Read of the statistic info file failed. aaa...a : Name of the file which was read bbb...b : Name of the function where the error occurred cccc : Error number [Measures] Remove the cause of read failure, or check whether the specified statistic info...
  • Page 617 Chapter 2 Message List iSMprfarc: 120 Illegal file format -- <aaa...a> [Explanation] The specified file is a wrong file that is not the statistic information history file/statistic information summarized file, or a statistic information file of unprocessable version. aaa...a : Name of the wrong file [Measures] Check the specified file.
  • Page 618 Chapter 2 Message List iSMprfctl 011: Illegal option -- <aaa...a> [Explanation] An illegal option was specified. aaa...a : Name of the illegal option [Measures] Specify the correct option, and then re-execute the command. iSMprfctl 012: Missing option value -- <aaa...a> [Explanation] No value has been specified in the option.
  • Page 619 Chapter 2 Message List iSMprfctl 021: Specified Disk Array is invalid [Explanation] The command cannot be executed for the specified disk array because of the following: The specified disk array is not one to be monitored by iSM. The specified disk array is not permitted to use the performance optimization function.
  • Page 620 Chapter 2 Message List iSMprfctl 030: Specified Logical Disk is invalid [Explanation] The specification of the logical disk to be moved is invalid. Check: if the specified logical disk exists in the specified disk array. if the specified logical disk is defined as a work disk for optimization. if the specified logical disk is defined as a cache resident disk.
  • Page 621 Chapter 2 Message List iSMprfctl 033: Specified Logical Disk is multi rank type [Explanation] The specified logical disk to be moved is a multi-RANK disk, and it cannot be moved. [Measures] Review the specification of the logical disk to be moved, and then re-execute the command.
  • Page 622 Chapter 2 Message List iSMprfctl 037: Specified Optimization Work Disk name overlaps [Explanation] The name of the specified work disk for optimization is identical to the name of another disk in the specified disk array. [Measures] Correct the volume format specification of the work disk for optimization, and then re-execute the command.
  • Page 623 Chapter 2 Message List iSMprfctl 043: Specified Optimization Work Disk is not in normal state [Explanation] The specified work disk for optimization is not in normal state, and it cannot be moved. [Measures] Rebuild the work disk for optimization or specify another one, and then re-execute the command.
  • Page 624 Chapter 2 Message List iSMprfctl 050: Failed in communication with iSMsvr func=<aaa...a> errno= <bbbb> detcode=<cccccccc> [Explanation] An error occurred during communication with the iSM server. aaa...a : Function name bbbb : Error code cccccccc : Detail code [Measures] Eliminate the error cause (e.g., restarting the iSM server), and then re-execute the command.
  • Page 625 Chapter 2 Message List iSMprfctl 090: HW error has occurred in start of Logical Disk movement [Explanation] An error occurred in the disk array, and moving of the logical disk failed to start. [Measures] Check the error cause according to the related messages, recover the disk array from the error, and then re-execute the command.
  • Page 626 Chapter 2 Message List iSMprfedit: 001 ∼ iSMprfedit: 001 <aaa...a> > <bbb...b> [Explanation] The performance information of the statistical information history file or statistical information summary file was edited and output as a report normally. aaa...a : Name of the statistical information history file or statistical information summary file (character string) bbb...b : Name of the Performance Report (text format file) (character...
  • Page 627 Chapter 2 Message List iSMprfedit: 103 Missing option - <aaa...a> [Explanation] It indicates that required option is not specified. aaa...a : Option name required to be specified (String) [Measures] Specify the option correctly and execute the command again. iSMprfedit: 110 File open error - <aaa...a> func = <bbb...b>...
  • Page 628 Chapter 2 Message List iSMprfedit: 112 Read error - <aaa...a> func = <bbb...b> errno = <cccc> ds = <dddddddd> [Explanation] It indicates that an error occurred in the input process of the file. aaa...a : Name of the file for which the error occurred in the input process (String) bbb...b : Name of the function where the error occurred (String)
  • Page 629 Chapter 2 Message List iSMprfedit: 115 Memory allocate error - <aaa...a> func = <bbb...b> errno = <cccc> ds = <dddddddd> [Explanation] It indicates that an error occurred in memory allocation process. aaa...a : Name of the file for which the error occurred in the memory allocation process (String) bbb...b : Name of the function where the error occurred (String)
  • Page 630 Chapter 2 Message List iSMprfedit: 122 Since there is no data of <aaa...a>, <aaa...a> performance report has not been created - <bbb...b> [Explanation] It indicates that specified statistic information history file/statistic information summarized file does not contain the statistic information of the performance detail report, and specified performance detail report could not be created.
  • Page 631 Chapter 2 Message List iSMprfedit: 999 Unexpected error - <aaa...a> ds = <bbbbbbbb> [Explanation] It indicates that an error occurred in the internal processing of iSMprfedit. aaa...a : Name of the specified statistic information history file/statistic information summarized file (String) bbbbbbbb : Detailed code of the error (in Hexadecimal) [Measures]...
  • Page 632 Chapter 2 Message List iSMprfext: 001 ∼ iSMprfext: 001 <aaa...a> > <bbb...b> [Explanation] The statistical information of the statistical information history file or statistical information summary file was converted into CSV format and output as a CSV format file normally. aaa...a : Name of the statistical information history file or statistical information summary file (character string)
  • Page 633 Chapter 2 Message List iSMprfext: 004 File open error - <aaa...a> func = <bbb...b> errno = <cccc> [Explanation] It indicates that an error occurred in the open process of the file. aaa...a : Name of the file for which the error occurred in the open process (String) bbb...b : Name of the function where the error occurred (String)
  • Page 634 Chapter 2 Message List iSMprfext: 007 Write error - <aaa...a> func = <bbb...b> errno = <cccc> [Explanation] It indicates that an error occurred in the write process of the file. aaa...a : Name of the file for which the error occurred in the write process (String) bbb...b : Name of the function where the error occurred (String)
  • Page 635 Chapter 2 Message List iSMprfext: 010 Unexpected error - <aaa...a> ds = <bbbbbbbb> [Explanation] It indicates that an error occurred in the internal processing of CSV Conversion Tool. aaa...a : Name of the specified statistic information history file/statistic information summarized file (String) bbbbbbbb : Detailed code of the error (in Hexadecimal) [Measures]...
  • Page 636 Chapter 2 Message List iSMprflog:001 ∼ iSMprflog:001 Disk array=<aaa...a> logging is started interval=<bb> [Explanation] It indicates that data accumulation in statistic information history file has been started. aaa...a : Disk array name : Accumulating interval (minute) [Measures] Unnecessary iSMprflog:002 Disk array=<aaa...a> logging is already started [Explanation] It indicates that data accumulation in statistic information history file has already...
  • Page 637 Chapter 2 Message List iSMprflog:010 Disk array=<aaa...a> logging is stopped [Explanation] It indicates that data accumulation in statistic information history file has been terminated. aaa...a : Disk array name [Measures] Unnecessary iSMprflog:011 Disk array=<aaa...a> logging is already stopped [Explanation] It indicates that data accumulation in statistic information history file has been already terminated.
  • Page 638 Chapter 2 Message List iSMprflog:102 Missing option value - <aaaaa> [Explanation] It indicates that value of -aaaaa option has not been specified. aaaaa : Specified value [Measures] Specify required option value and retry command execution. iSMprflog:103 Illegal option value - <aaaaa> [Explanation] It indicates that an invalid option value has been specified.
  • Page 639 Chapter 2 Message List iSMprflog:122 There is no disk array [Explanation] It indicates that target disk array does not exist when batch operation is executed for all the disk array with -a option specified. [Measures] Check status of disk array, and retry command if necessary. iSMprflog:123 Disk array=<aaa...a>...
  • Page 640 Appendix A Message Output Destination List Appendix A Message Output Destination List This appendix lists the destinations of messages output by iSM. (1/39) Table A-1 Message Output Destination List Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX...
  • Page 641 Appendix A Message Output Destination List Table A-1 Message Output Destination List (2/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM02021 NOTICE iSM02040 INFO ∆ iSM02041 INFO ∆...
  • Page 642 Appendix A Message Output Destination List Table A-1 Message Output Destination List (3/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM03203 ERROR iSM03204 ERROR iSM03220 ERROR iSM03221 ERROR iSM03222 ERROR...
  • Page 643 Appendix A Message Output Destination List Table A-1 Message Output Destination List (4/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM06041 WARNING iSM06042 WARNING iSM06043 WARNING iSM06044 WARNING iSM06045 WARNING...
  • Page 644 Appendix A Message Output Destination List Table A-1 Message Output Destination List (5/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM07031 INFO ∆ iSM07032 INFO ∆ iSM07033 INFO ∆...
  • Page 645 Appendix A Message Output Destination List Table A-1 Message Output Destination List (6/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM07151 INFO ∆ iSM07152 ERROR iSM07154 NOTICE iSM07155 NOTICE iSM07156...
  • Page 646 Appendix A Message Output Destination List Table A-1 Message Output Destination List (7/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM07211 INFO iSM07212 INFO iSM07213 INFO iSM07220 INFO ∆...
  • Page 647 Appendix A Message Output Destination List Table A-1 Message Output Destination List (8/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM07411 INFO ∆ iSM07412 ERROR iSM07413 ERROR iSM07414 NOTICE iSM07415...
  • Page 648 Appendix A Message Output Destination List Table A-1 Message Output Destination List (9/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM07621 NOTICE iSM07622 ERROR iSM07670 INFO ∆ iSM07671 NOTICE iSM07672...
  • Page 649 Appendix A Message Output Destination List Table A-1 Message Output Destination List (10/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM08181 NOTICE iSM08182 NOTICE iSM08183 NOTICE iSM08201 NOTICE iSM08900 WARNING...
  • Page 650 Appendix A Message Output Destination List Table A-1 Message Output Destination List (11/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM10106 NOTICE iSM10200 NOTICE iSM10201 NOTICE iSM10210 NOTICE iSM10220 ERROR...
  • Page 651 Appendix A Message Output Destination List Table A-1 Message Output Destination List (12/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM10501 ERROR iSM10502 ERROR iSM10503 ERROR iSM10504 ERROR iSM10505 ERROR...
  • Page 652 Appendix A Message Output Destination List Table A-1 Message Output Destination List (13/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM11231 INFO iSM11232 INFO iSM11233 INFO iSM11234 INFO iSM11235 INFO...
  • Page 653 Appendix A Message Output Destination List Table A-1 Message Output Destination List (14/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM11372 INFO iSM11373 INFO iSM11374 INFO iSM11375 INFO iSM11376 INFO...
  • Page 654 Appendix A Message Output Destination List Table A-1 Message Output Destination List (15/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM11442 INFO iSM11443 INFO iSM11444 INFO iSM11455 INFO iSM11486 INFO...
  • Page 655 Appendix A Message Output Destination List Table A-1 Message Output Destination List (16/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM11561 INFO iSM11562 INFO iSM11563 INFO iSM11564 INFO iSM11565 INFO...
  • Page 656 Appendix A Message Output Destination List Table A-1 Message Output Destination List (17/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM11711 WARNING iSM11712 WARNING iSM11713 WARNING iSM11714 WARNING iSM11721 ERROR...
  • Page 657 Appendix A Message Output Destination List Table A-1 Message Output Destination List (18/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM11781 ERROR iSM11782 ERROR iSM11783 ERROR iSM11784 ERROR iSM11785 ERROR...
  • Page 658 Appendix A Message Output Destination List Table A-1 Message Output Destination List (19/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13221 INFO ∆ iSM13222 INFO iSM13223 INFO iSM13224 INFO ∆...
  • Page 659 Appendix A Message Output Destination List Table A-1 Message Output Destination List (20/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13411 WARNING iSM13412 WARNING iSM13413 WARNING iSM13414 WARNING iSM13415 WARNING...
  • Page 660 Appendix A Message Output Destination List Table A-1 Message Output Destination List (21/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13531 ERROR iSM13532 ERROR iSM13533 ERROR iSM13535 ERROR iSM13536 ERROR...
  • Page 661 Appendix A Message Output Destination List Table A-1 Message Output Destination List (22/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13571 ERROR iSM13572 ERROR iSM13573 ERROR iSM13574 ERROR iSM13575 ERROR...
  • Page 662 Appendix A Message Output Destination List Table A-1 Message Output Destination List (23/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13611 ERROR iSM13612 ERROR iSM13613 ERROR iSM13614 ERROR iSM13615 ERROR...
  • Page 663 Appendix A Message Output Destination List Table A-1 Message Output Destination List (24/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13661 ERROR iSM13662 ERROR iSM13663 ERROR iSM13664 ERROR iSM13669 ERROR...
  • Page 664 Appendix A Message Output Destination List Table A-1 Message Output Destination List (25/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13701 ERROR iSM13702 ERROR iSM13703 ERROR iSM13704 ERROR iSM13705 ERROR...
  • Page 665 Appendix A Message Output Destination List Table A-1 Message Output Destination List (26/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13741 ERROR iSM13742 ERROR iSM13743 ERROR iSM13744 ERROR iSM13745 ERROR...
  • Page 666 Appendix A Message Output Destination List Table A-1 Message Output Destination List (27/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM13801 ERROR iSM13802 ERROR iSM13803 ERROR iSM13804 ERROR iSM13805 ERROR...
  • Page 667 Appendix A Message Output Destination List Table A-1 Message Output Destination List (28/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM14401 INFO iSM14402 INFO iSM14403 INFO iSM14404 INFO iSM14405 INFO...
  • Page 668 Appendix A Message Output Destination List Table A-1 Message Output Destination List (29/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM14441 INFO iSM14442 INFO iSM14443 INFO iSM14444 INFO iSM14445 INFO...
  • Page 669 Appendix A Message Output Destination List Table A-1 Message Output Destination List (30/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM16033 WARNING iSM16034 WARNING iSM16035 WARNING iSM16037 WARNING iSM16038 WARNING...
  • Page 670 Appendix A Message Output Destination List Table A-1 Message Output Destination List (31/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM18001 INFO ∆ iSM18002 INFO ∆ iSM18003 INFO ∆...
  • Page 671 Appendix A Message Output Destination List Table A-1 Message Output Destination List (32/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM19101 ERROR iSM19102 ERROR iSM19103 ERROR iSM19104 ERROR iSM19105 ERROR...
  • Page 672 Appendix A Message Output Destination List Table A-1 Message Output Destination List (33/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM19401 ERROR iSM19402 ERROR iSM19403 ERROR iSM19404 ERROR iSM19405 ERROR...
  • Page 673 Appendix A Message Output Destination List Table A-1 Message Output Destination List (34/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSM20201 ERROR iSM20202 ERROR iSM20203 ERROR iSM20204 ERROR iSM20205 WARNING...
  • Page 674 Appendix A Message Output Destination List Table A-1 Message Output Destination List (35/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSMnetconf: INFO iSMnetconf INFO :101 iSMnetconf: INFO iSMnetconf: INFO iSMnetconf:...
  • Page 675 Appendix A Message Output Destination List Table A-1 Message Output Destination List (36/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc: iSMprfarc:...
  • Page 676 Appendix A Message Output Destination List Table A-1 Message Output Destination List (37/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSMprfctl iSMprfctl iSMprfctl iSMprfctl iSMprfctl iSMprfctl iSMprfctl iSMprfctl iSMprfctl iSMprfctl...
  • Page 677 Appendix A Message Output Destination List Table A-1 Message Output Destination List (38/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSMprfedit: iSMprfedit: iSMprfedit: iSMprfedit: iSMprfedit: iSMprfedit: iSMprfedit: iSMprfext: iSMprfext: iSMprfext:...
  • Page 678 Appendix A Message Output Destination List Table A-1 Message Output Destination List (39/39) Output destination Classification Operation log Syslog Event log Console ESMPRO link UNIX Windows HP-UX Solaris Windows ALIVE/ Manager express report iSMprflog: iSMprflog: iSMprflog: iSMprflog: iSMprflog: iSMprflog: iSMprflog: iSMprflog: iSMprflog: iSMprflog:...
  • Page 679: Appendix B Changed Message List

    Appendix B Changed Message List Appendix B Changed Message List Table B-1 Message modification list (1/32) Modification Description Message ID version Message body Classification Added Changed Deleted Illegal configuration. file=<aaa...a> line=<bbb...b> [section=<ccc...c>] [keyword=<ddd...d>] [value=<eee...e>] NOTICE [token=<fff...f>] iSM01110 Illegal configuration. file=<aaa...a> line=<bbb...b> [section=<ccc...c>] [keyword=<ddd...d>] [value=<eee...e>] NOTICE [token=<fff...f>] [detail=<ggg...g>]...
  • Page 680 Appendix B Changed Message List Table B-1 Message modification list (2/32) Modification Modification Message ID version Classification Added Changed Deleted Message body Resource monitoring started. (<aaa...a> productID=<bbbbb> INFO SN=<ccccc>) [UC=<dddddddddd> FC=<ee>] iSM07012 Resource monitoring started. (<aaa...a> productID=<bbbbb> SN=<ccccc>) [UC=<dddddddddd> FC=<ee>][_ALERT_] INFO Resource monitoring stopped by control path fault.
  • Page 681 Appendix B Changed Message List Table B-1 Message modification list (3/32) Modification Modification Message ID version Message body Classification Added Changed Deleted State of <aaaaa>(<bb>h[-<cc>h]) has become fault. ERROR (<ddd...d> productID=<eeeee> SN=<fffff> No=<gg>h ) State of <aaaaa>(<bb>h[-<cc>h]) has become fault. iSM07112 (<ddd...d>...
  • Page 682 Appendix B Changed Message List Table B-1 Message modification list (4/32) Modification Modification Message ID version Message body Classification Added Changed Deleted State of LD has become fault(media error). (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h Name=<eee...e> [PDN=<ff>h-<gg>h]) [UC=<hhh...h> ERROR FC=<ii>] iSM07173 State of LD has become fault(media error). (<aaa...a> productID=<bbb...b>...
  • Page 683 Appendix B Changed Message List Table B-1 Message modification list (5/32) Modification Modification Message ID version Message body Classification Added Changed Deleted The capacity of SRA used is over threshold.(<aaa...a> iSM07616 productID=<bbb...b> SN=<ccc...c> No=<dddd>h WARNING Name=<eee...e> capacity=<fff...f>GB threshold=<ggg...g>GB) The capacity of SRA used is under threshold.(<aaa...a> iSM07617 productID=<bbb...b>...
  • Page 684 Appendix B Changed Message List Table B-1 Message modification list (6/32) Modification Description Message ID version Message body Classification Added Changed Deleted Expansion State of POOL has become expand-fail. (<aaa...a> productID=<bbb...b> SN=<ccc...c> No=<dddd>h ERROR Name=<eee...e>) iSM07672 Expansion State of POOL has become expand-fail. (<aaa...a>...
  • Page 685 Appendix B Changed Message List Table B-1 Message modification list (7/32) Modification Description Message ID version Message body Classification Added Changed Deleted copy error:mv=<aaa...a> (<bbb...b>h) <ccc...c>, NOTICE rv=<aaa...a> (<bbb...b>h)<ccc...c>, status=<ddd...d>h copy error:mv=<aaa...a>(<bbbb>h)<ccc...c>, rv=<aaa...a> iSM10400 (<bbbb>h)<ccc...c>, status=<ddd...d>h[,ATgroup=<eee...e>] ERROR [_ALERT_] copy error:mv=<aaa...a>(<bbb...b>h)<ccc...c>, rv=<aaa...a>(<bbb...b>h)<ccc...c>,status=<ddd...d>h ERROR [UC=<eeeeeeee>...
  • Page 686 Appendix B Changed Message List Table B-1 Message modification list (8/32) Modification Description Message ID version Message body Classification Added Changed Deleted The address which can be specified is <aaaa>h or <bbbb>h. INFO iSM11322 The address which can be specified is “<aaaa>h” or INFO “<bbbb>h”.
  • Page 687 Appendix B Changed Message List Table B-1 Message modification list (9/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM11714 Volume list data has no control volume. WARNING iSM11740 Failed to get property of volume list data. ERROR iSM13218 <aaa...a>...
  • Page 688 Appendix B Changed Message List Table B-1 Message modification list (10/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM13252 Create Normal End <aaaa/bb/cc> <dd:ee:ff> INFO iSM13253 Create Abnormal End <aaaa/bb/cc> <dd:ee:ff> INFO iSM13254 Delete Start <aaaa/bb/cc> <dd:ee:ff> INFO iSM13255 Delete Normal End <aaaa/bb/cc>...
  • Page 689 Appendix B Changed Message List Table B-1 Message modification list (11/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM13560 State of the specified ATgroup is unknown. ERROR (code=<aaa...a>-<bbb...b>-<bbb...b>-<bbb...b>) These targets are replicating now. MV:<aaa...a> ERROR RV:<aaa...a> iSM13577 These targets are replicating now.
  • Page 690 Appendix B Changed Message List Table B-1 Message modification list (12/32) Modification Description Message ID version Message body Classification Added Changed Deleted Illegal value of -interval [second]. (<aaa...a>) ERROR iSM13656 Illegal value of -interval [second]. (<aaa...a>) ERROR (code=<bbb...b>-<ccc...c>-<ccc...c>-<ccc...c>) Illegal value of -limit [second]. (<aaa...a>) ERROR iSM13657 Illegal value of -limit [second].
  • Page 691 Appendix B Changed Message List Table B-1 Message modification list (13/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM13678 Description is too long. (<aaa...a>) ERROR (code=<bbb...b>-<ccc...c>-<ccc...c>-<ccc...c>) MV volume differs from database volume. ERROR iSM13681 Specified volume differs from database volume. ERROR code=<aaa...a>-<bbb...b>-<bbb...b>-<bbb...b>) iSM13700...
  • Page 692 Appendix B Changed Message List Table B-1 Message modification list (14/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM13761 Illegal bvflg type. (<aaa...a>) ERROR (code=<bbb...b>-<ccc...c>-<ccc...c>-<ccc...c>) iSM13762 Illegal svflg type. (<aaa...a>) ERROR (code=<bbb...b>-<ccc...c>-<ccc...c>-<ccc...c>) iSM13763 SV is omitted. ERROR (code=<aaa...a>-<bbb...b>-<bbb...b>-<bbb...b>) iSM13764...
  • Page 693 Appendix B Changed Message List Table B-1 Message modification list (15/32) Modification Description Message ID version Message body Classification Added Changed Deleted Deleting snapshot has terminated because iSM13775 "Snap State" is changed by other process. ERROR (code=<aaa...a>-<bbb...b>-<bbb...b>-<bbb...b>) Restoring snapshot has terminated because iSM13776 "Snap State"...
  • Page 694 Appendix B Changed Message List Table B-1 Message modification list (16/32) Modification Description Message ID version Message body Classification Added Changed Deleted Server name is too long.filename=<aaa...a> line=<bbb...b> ERROR Server name is too long.filename=<aaa...a> iSM13805 line=<bbb...b> ERROR (code=<ccc...c>-<ddd...d>-<ddd...d>-<ddd...d>) Back up set name is too long. filename=<aaa...a> iSM13806 line=<bbb...b>...
  • Page 695 Appendix B Changed Message List Table B-1 Message modification list (17/32) Modification Description Message ID version Message body Classification Added Changed Deleted Options "uid" can not be omitted are specified. ERROR filename=<aaa...a> line=<bbb...b> Options "uid" can not be omitted are specified. iSM13815 filename=<aaa...a>...
  • Page 696 Appendix B Changed Message List Table B-1 Message modification list (18/32) Modification Description Message ID version Message body Classification Added Changed Deleted User id is too long. ERROR iSM13827 User id is too long. ERROR (code=<aaa...a>-<bbb...b>-<bbb...b>-<bbb...b>) Password is too long. ERROR iSM13828 Password is too long.
  • Page 697 Appendix B Changed Message List Table B-1 Message modification list (19/32) Modification Description Message ID version Message body Classification Added Changed Deleted SRA bind : LD(SDV) number=<aaaa>h,<aaaa>h..., Pool iSM14468 number=<bbbb>h, SRA capacity=<ccc...c>GB, INFO threshold=<ddd...d>GB(<ee%>), status=<fff...f> LV bind : LD(LV) number=<aaaa>h,<aaaa>h...(LD(BV) iSM14469 number=<bbbb>h,<bbbb>h...), Pool number=<cccc>h, INFO...
  • Page 698 Appendix B Changed Message List Table B-1 Message modification list (20/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM16032 Illegal configuration. file=alived.conf First line is not WARNING [ALIVE]. iSM16033 Illegal configuration. file=alived.conf Tag overlaps. WARNING line=<aa> tag=<bbb...b> iSM16034 Illegal configuration.
  • Page 699 Appendix B Changed Message List Table B-1 Message modification list (21/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM16061 Mail server (<aaa...a>) address is illegal. WARNING iSM16062 Mail server cannot be connected. name=<aaa...a> WARNING code=<bbbb> errno=<ccc> iSM16063 Communication error(receive from mail server).
  • Page 700 Appendix B Changed Message List Table B-1 Message modification list (22/32) Modification Description Message ID Message body version Classification Added Changed Deleted iSM18003 Snapshot has been deleted. (<aaa...a>, BV=<bbb...b> INFO (<cccc>h), SV=<ddd...d>(<eeee>h)) Restoring snapshot has been started. (<aaa...a>, iSM18004 BV=<bbb...b> (<cccc>h), SV=<ddd...d>(<eeee>h), INFO generation=<fff>) iSM18005...
  • Page 701 Appendix B Changed Message List Table B-1 Message modification list (23/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM18311 Internal communication error has occurred. (code=<aaa...a>) ERROR iSM18321 Access to diskarray was failed. (<aaa...a>, code=<bbb...b>, WARNING <ccc...c>) iSM18501 Access mode was changed.
  • Page 702 Appendix B Changed Message List Table B-1 Message modification list (24/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM19012 iSMsc_create has abnormally terminated. INFO iSM19013 iSMsc_create has abnormally terminated. [BV:<aaa...a>] INFO [SV:<bbb...b>] iSM19020 iSMsc_delete has normally terminated. INFO iSM19021 iSMsc_delete has normally terminated.
  • Page 703 Appendix B Changed Message List Table B-1 Message modification list (25/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM19101 The volume linked from LV cannot be specified. ERROR [{BV|SV}:<aaa...a>] iSM19102 The volume mounted cannot be specified. [BV:<aaa...a>] ERROR iSM19103 State of specified diskarray is 'freeze'.
  • Page 704 Appendix B Changed Message List Table B-1 Message modification list (26/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM19114 License for snapshot is locked. ERROR iSM19115 Snapshot function is not supported with this volume. ERROR iSM19116 Specified drive number does not exist.
  • Page 705 Appendix B Changed Message List Table B-1 Message modification list (27/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM19202 Illegal option value was specified. (<aaa...a>) ERROR iSM19203 Number of BV and SV was not equal. ERROR iSM19208 Illegal configuration was detected.
  • Page 706 Appendix B Changed Message List Table B-1 Message modification list (28/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM19307 Failed to receive from iSM/Server.(errno=<aaa...a>, ERROR phase=< bbb...b >) iSM19308 Failed to send to iSM/Server.(errno=<aaa...a>, ERROR phase=<bbb... b>) iSM19401 System call error has occurred.(func=<aaa...a>, ERROR...
  • Page 707 Appendix B Changed Message List Table B-1 Message modification list (29/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM20020 iSMsc_link has normally terminated. INFO iSM20021 iSMsc_link has normally terminated. [LV:<aaa...a>] INFO [SV:<bbb...b>] iSM20022 iSMsc_link has abnormally terminated. INFO iSM20023 iSMsc_link has abnormally terminated.
  • Page 708 Appendix B Changed Message List Table B-1 Message modification list (30/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM20106 Targets volumes are not linked. [LV:<aaa...a>] [{BV|SV}:< ERROR bbb...b>] iSM20107 The volume mounted cannot be specified. [LV:<aaa...a>] ERROR iSM20108 SV which is not snap/active cannot be specified.
  • Page 709 Appendix B Changed Message List Table B-1 Message modification list (31/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM20122 The volume which is not linked cannot be specified. ERROR [VOL:<aaa...a>] iSM20123 State of specified diskarray is 'freeze'. ERROR iSM20200 Mandatory option was not specified.(<aaa...a>)
  • Page 710 Appendix B Changed Message List Table B-1 Message modification list (32/32) Modification Description Message ID version Message body Classification Added Changed Deleted iSM20302 Specified Diskarray does not exist. ERROR iSM20303 State of Diskarray includes specified volume is not ERROR monitoring. iSM20304 Timeout error has occurred in iSM/Server.

Table of Contents