Nec Storage Manager Is010 12E Users Manual Messages Handbook
IS010-12E to the manual cb4f0167-b500-4465-8307-9000958f813f
2015-01-24
: Nec Nec-Storage-Manager-Is010-12E-Users-Manual-331203 nec-storage-manager-is010-12e-users-manual-331203 nec pdf
Open the PDF directly: View PDF .
Page Count: 710
Download | |
Open PDF In Browser | View PDF |
NEC Storage Manager Messages Handbook IS010-12E © 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. Preface This manual explains messages handled by NEC Storage Manager. IDs. The messages are listed in the order of message Refer to the “NEC Storage Manager Manual Guide” (IS901) for the overview of the NEC Storage and the related manuals. Remarks 1. This manual explains functions implemented by the following program products: • NEC Storage Manager and NEC Storage BaseProduct • NEC Storage AccessControl • NEC Storage PerformanceMonitor • NEC Storage PerformanceOptimizer • NEC Storage ReallocationControl • NEC Storage ReplicationControl • NEC Storage ReplicationControl/DisasterRecovery • NEC Storage ReplicationControl SQL Option 2. This manual is applicable to the program products of the following versions: • NEC Storage Manager Ver3.3 • NEC Storage BaseProduct Ver3.3 • NEC Storage ReplicationControl Ver3.3 • NEC Storage ReplicationControl/DisasterRecovery Ver3.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. 4. The following descriptions in the text of this manual refer to the corresponding products. Description Corresponding Product Storage Manager NEC Storage Manager BaseProduct NEC Storage BaseProduct ReplicationControl SQL Option NEC Storage ReplicationControl SQL Option AccessControl NEC Storage AccessControl DynamicDataReplication NEC Storage DynamicDataReplication PerformanceMonitor NEC Storage PerformanceMonitor RemoteDataReplication NEC Storage RemoteDataReplication NEC Storage RemoteDataReplication/DisasterRecovery ReplicationControl NEC Storage ReplicationControl SnapControl NEC Storage SnapControl NEC Storage ReplicationControl/DisasterRecovery 5. The following descriptions in the text of this manual refer to the corresponding manuals. Description Corresponding Manual User's Manual (UNIX) NEC Storage Manager User's Manual (UNIX) (IS001) User's Manual NEC Storage Manager User's Manual (IS004) Data Replication User's Manual NEC Storage Data Replication User's Manual (Function Guide) (IS015) (Function Guide) Data Replication User's Manual (Installation and Operation Guide for Windows) (IS016) Data Replication Command Reference NEC Storage Data Replication User's Manual (Installation and Operation Guide for Windows) (IS016) 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. 7. Trademarks and registered trademarks • HP-UX is a registered trademark of Hewlett-Packard Co. in the United States. • UNIX is a registered trademark of The Open Group in the United States and other countries. • Microsoft® and Windows® are trademarks or registered trademarks of Microsoft Corporation in the United States and other countries. • Solaris is a trademark or a registered trademark of Sun Microsystems, Inc. in the United States and other countries. • Linux is a trademark or registered trademark of Mr. Linus Torvalds in the United States and other countries. Other product names and company names, etc. are registered trademarks or trademarks of the associated companies. The First Edition in May 2002 The Twelfth Edition in November 2004 Contents Chapter 1 Messages and Output Destinations ..................................................................................................................1 1.1 Message Classification ................................................................................................................................................3 1.2 Message Output Destinations ......................................................................................................................................4 1.3 Message Output Format ..............................................................................................................................................6 Chapter 2 Message List .......................................................................................................................................................8 2.1 Interpretation of Message List.....................................................................................................................................8 2.2 Message List................................................................................................................................................................9 Appendix A Message Output Destination List .................................................................................................................634 Appendix B Changed Message List...................................................................................................................................673 i This page is intentionally left blank. ii Chapter 1 Messages and Output Destinations 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. The ReplicationControl outputs the operation information of data replication in a message format, to the log files of the console/terminal and the business server. The message is output to syslog, event log, and operation log. The message describes the information for checking operating conditions, such as command execution results, and fault and error detection information, etc. If ESMPRO Agent has been installed in the management server on which the Storage Manager has started, messages are output to ESMPRO Manager. Figure 1-1 shows an overview of message output. 1 Chapter 1 Messages and Output Destinations Management server Output to syslog (UNIX) or event log (Windows) Storage Manager Syslog or event log Operation log Output to console/terminal Disk array Console/Terminal Output to ESMPRO Manager when ESMPRO Business server Agent installed (only for Windows) Output to console/terminal Output to syslog (UNIX) or event log (Windows) ReplicationControl Syslog or event log Operation log Figure 1-1 Overview of Message Output 2 Chapter 1 Messages and Output Destinations 11..11 M Meessssaag gee C Cllaassssiiffiiccaattiio on n 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: y ERROR: Error message This message indicates an error that has a critical effect to the functions, and prompt recovery by an administrator is required. An administrator must troubleshoot and recover the system promptly. y WARNING: Warning message This message indicates an event that requires attention regarding the system operations, though the event does not necessarily lead to the system down immediately. An administrator must remove the cause of the event and take measures to operate the system normally. y NOTICE: Notifying message This message notifies the state of internal processes. Although the event notified by the message does not have any effect on the main functions of disk arrays, an administrator must take appropriate measures as necessary. y INFO: Information message This message indicates operating information. No measures are required. 3 Chapter 1 Messages and Output Destinations 11..22 M Meessssaag gee O Ou uttp pu utt D Deessttiin naattiio on nss The output destinations of messages depend on functions and OS to be used. the console/terminal, operation log, syslog, event log, and ESMPRO Manager. Output destinations are Message output destinations are described as follows: y Console/Terminal A console is a monitoring terminal that is directly connected to the monitoring server of the iSM. On the other hand, a terminal is a client terminal that is connected to the monitoring server via telnet, etc. When a command is issued from the iSM or the ReplicationControl, a message indicating execution result is displayed on the console or the terminal where the command is executed. y Operation log Operation log, which is output on UNIX and Windows, records the messages output from the iSM or the 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. logs are output as the following directory/file names by default. (1) Storage Manager operation log UNIX system: /opt/iSMsvr/etc/log/iSM_Log.log Windows system:\iSMsvr\etc\log\iSM_Log.log (2) ReplicationControl operation log HP-UX system: /opt/iSMrpl/etc/*.log /opt/iSMvol/etc/*.log Solaris system: /opt/NECiSMrpl/etc/*.log /opt/NECiSMvol/etc/*.log Windows system: \iSMrpl\etc\trace\*.log \iSMvol\etc\trace\*.log 4 Operation Chapter 1 Messages and Output Destinations y syslog This is output on UNIX system. Together with the messages output by UNIX, the messages output from iSM and ReplicationControl are recorded. The output format depends on the OS (HP-UX or Solaris). Output/no output or output destinations of messages, which is output to syslog, can be specified by modifying descriptions for type (level) and function (facility) in OS settings file (/etc/syslog.conf). Note 1: On Solaris system, a message, of which function is “daemon” and classification is “INFO”, is not output as the default value. Also, a message, of which function is “user” and classification is “WARNING”, “NOTICE”, or “INFO” is not output as the default value. To output these kinds of messages, modify the OS settings file. Note 2: The function of messages output from the iSM to syslog is “Daemon”. However, the function of the messages output by the ReplicationControl command is “user”. Messages are output being affixed the following directory/file name as the default value: HP-UX system: /var/adm/syslog/syslog.log Solaris system: /var/adm/messages y Event log This is output on Windows system. Together with the messages output by windows, the messages output from the iSM and the ReplicationControl are recorded. The messages are output to application log in the event log. The event log has the functions similar to those of UNIX syslog, however, the content of the log are different. in the Management Tool. The event log can be viewed using the [Event Viewer] A message classification and an event log type correspond as follows. ERROR: Error WARNING: Warning NOTICE/ INFO: Information y ESMPRO Manager Messages are output to ESMPRO Manager in the Windows environment. If ESMPRO Agent has been installed in the management server on which the 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. The notification function provided by ESMPRO is also available. 5 Chapter 1 Messages and Output Destinations 11..33 M Meessssaag gee O Ou uttp pu utt F Fo orrm maatt This section describes the message output format and the errno output rule. For details on the message text, refer to Chapter 2 “Message List”. The following shows the output format of a message: Mon Date hh:mm:ss hhhhhh ffffffff :mmmmmm cccccccc : iSMyyyyy : Message body Mon Date : Month and date hh:mm:ss : Time hhhhhh : Host name ffffffff : Function identifier mmmmmm : Message classification cccccccc : Command name and function name yyyyy : Message number The message, which is output to application log in the event log, includes the following values specified for each item: y Classification ERROR : Error WARNING : Warning NOTICE : Information INFO : Information y Source Storage Manager : (fixed) y Classification None (fixed) y Event ID Number part in the message ID output to the operation log. The following describes output rules for errno: y Windows system 1. Routine in C Runtime library: errno value is defined by the library. 2. WIN32 API: The value returned by GetLastError with 20000 added is output. 3. Socket API: The value returned by WSGetLastError with 20000 added is output. 6 Chapter 1 Messages and Output Destinations y UNIX system 1. A defined value is output as is. 7 Chapter 2 Message List Chapter 2 Message List 22..11 IIn ntteerrp prreettaattiio on no off M Meessssaag gee L Liisstt 2.2 “Message List” describes the messages in the order of message IDs. The message are described in the following format: iSMxxxxx: AAAAA , Message ID (iSMxxxxx) and message body (AAAAA , ) are described. Descriptions using parentheses such as and indicate that parameter values are not fixed. (The parentheses “<” and “>” are not displayed in the actual message.) For details of parameter values, refer to [Explanation]. Messages subject to ALIVE report (including ALIVE report from a disk array) are followed by the keyword [_ALERT_] and output to each destination. For messages subject to ALIVE report excluding ALIVE report from a disk array, refer to Appendix A “Message Output Destination List”. [Classification] Message classification (ERROR, WARNING, NOTICE, or INFO) is described. A message that is not output to syslog, event log, or operation log is output without a message classification. This field is blank for such a message that is output without a message classification. [Explanation] This field describes the causes of the message output, etc. Parameters in the message are also described in this field. If a message is output on a specific OS (UNIX or Windows), applicable OS names are described in this field. Unless otherwise noted, the message is a common message that is independent of OS. [Measure] This field describes measures to be taken by an administrator. An administrator must follow the instructions to take measures. Note: For output destination of a message, refer to Appendix A “Message Output Destination List”. 8 Chapter 2 Message List 22..22 M Meessssaag gee L Liisstt 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. For Windows, this message is target of ESMPRO Manager Report. [Measures] Unnecessary iSM01003: Storage Manager has terminated normally [Classification] INFO [Explanation] It shows that iSM server has normally terminated. For Windows, this message is target of ESMPRO Manager Report. [Measures] Unnecessary 9 Chapter 2 Message List iSM01004: Storage Manager has terminated emergency [Classification] WARNING [Explanation] Emergency shutdown of iSM server. This message is output in the iSM server abort processing when iSMsvr stop -e is executed or the system is shut down. This message is output on UNIX system. [Measures] Unnecessary iSM01005: Command is entered.command= [Classification] INFO [Explanation] 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. [Measures] Unnecessary 10 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: has restarted [Classification] INFO [Explanation] It shows that a process indicated with aaa...a is restarted. For Windows, this message is target of ESMPRO Manager Report. aaa...a : Process name [Measures] Unnecessary 11 Chapter 2 Message List iSM01101: The function is not available. function= [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 : Configuration setting GUI function ALIVEmail : ALIVEmail function PerformanceOptimizer : Performance optimization function [Measures] iSMcmd : Configuration setting GUI function FileTransfer : File transfer function SnapShot : Snapshot function Examine the cause by studying iSM server’s syslog or iSM operation log. To use a function indicated with aaa...a, the iSM server must be restarted. iSM01102: Command failed [Classification] NOTICE [Explanation] It shows that iSMsvr stop/update/prf_start/prf_stop/prf_update command execution is failed. The entered command is ignored. A message indicating the error cause is displayed before this message is output. This error may occur when the linkage function or performance monitoring function is terminated. This message is output on UNIX system. [Measures] Investigate and remove the cause of error by referencing the message that is displayed before this message. Restart the iSM server if necessary. 12 Chapter 2 Message List iSM01103: Socket access failed. process= func= [errno= |error= ] detail= [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. aaa...a : Process name bbb...b : Socket system function name ccc : Error number ddd...d : Error contents timeout : Time out socket close : Socket is closed ee-fff : Detail code (This code is not disorder reason but a value for maintenance.) [Measures] If an error number is output, check the function name and the error number to take measures, and restart the iSM server if necessary. When an error contents is output, examine the cause through the previous message output before this message and restart the iSM server if necessary. 13 Chapter 2 Message List iSM01105: File access failed. file= func= errno= detail= [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. aaa...a : File path name bbb...b : File system function name ccc : Error number dd-eee : Detail code (This code is not disorder reason but a value for maintenance.) [Measures] Resolve the problem by checking the file path name, function name and error number, and restart the iSM server. iSM01106: System call error occurred. process= func= errno= detail= [Classification] NOTICE [Explanation] It shows that an error has occurred in the system function except the access of socket/file. The following hindrance is likely as an example. y In case of syslog: The shared memory has been deleted incorrectly with the ipcrm command. (Access error of shared memory) y In case of operation log: System overloading occurred by requests of iSM server. Some resources have been lost. aaa...a : Process name bbb...b : System function name ccc : Error number dd-eee : Detail code (This code is not disorder reason but a value for maintenance.) [Measures] Check the function name and error number to take measures, and restart the iSM server if necessary. 14 Chapter 2 Message List iSM01107: process has terminated abnormally [Classification] WARNING [Explanation] It shows that the process indicated with aaa...a has been abnormally terminated. A message of the cause has been reported from the abnormally terminated process right before this message. For Windows, this message is target of ESMPRO Manager Report. aaa...a [Measures] : Process name 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. This message is output on UNIX system. [Measures] Unnecessary iSM01109: Internal error occurred. detail= [Classification] WARNING [Explanation] It shows that an internal error has occurred in the main process of iSM server. iSM server will be terminated. aa-bbb : Detail code (This code is not disorder reason but a value for maintenance.) [Measures] Acquire the information and restart the iSM server if necessary. For the acquiring method of the information, refer to 6.1.9 “Information Gathering Method when Server Fault with Unknown Cause” of the “User’s Manual”. 15 Chapter 2 Message List iSM01110: Illegal configuration. file= line= [section= ] [keyword= ] [value= ] [token= ] [detail= ] [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 : Section name or words wherein illegal configuration was found ddd...d : Parameter name or words wherein illegal configuration was found eee...e : Parameter value or words wherein illegal configuration was found [Measures] fff...f : Words wherein illegal configuration was found ggg...g : Detailed information Find out incorrect description in the file through the output message, correct it and then restart the iSM server. Probable causes of detail information output are as follows: Detail Information Content Duplicate section The same section name has been specified more than once. Duplicate keyword The same keyword has been specified more than once. Too many diskarray The number of disk arrays exceeds the limitation. Too many diskarray The disk array number exceeds the value n of number diskarray[n]. Too many ip The number of IP addresses exceeds the limitation. Too many special The number of specified special files exceeds the file limitation. Too many disk The specified disk number exceeds the limitation. Too may login The number of user information items exceeds the limitation. Too many login The user number exceeds the value n of login[n]. number 16 Chapter 2 Message List iSM01111: User definition does not exist, Client cannot be connected. file= [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. aaa...a [Measures] : Environment definition file name Specify the login parameter of the client section in the environment definition file and restart the iSM server. iSM01113: iSMadm cannot use UDP port 162. file= line= [section= ] [keyword= ] [value= ] [Classification] NOTICE [Explanation] It shows that the port 162 specified by iSMadm user cannot be used. iSM Server will be abnormally terminated. This message is output on UNIX system. aaa...a : Environment definition file name bbb...b : Line number with illegal configuration ccc...c : Section name or words wherein illegal configuration was found ddd...d : Parameter name or words wherein illegal configuration was found eee...e : Parameter value or words wherein illegal configuration was found [Measures] Restart the iSM server with Super User to receive SNMP trap while the iSM server uses the port 162. If the iSM server does not use the port 162 for receiving SNMP trap, restart the iSM server after deleting the parameter for snmp_port. 17 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. [Measures] Examine the cause through the previous message output before this message and restart the iSM server if necessary. iSM01232: Storage Manager has terminated abnormally by signal.signo= [Classification] ERROR [Explanation] It shows that iSM server has terminated abnormally due to the signal. The user may send the kill signal. This message is output on UNIX system. aa…a: Signal number [Measures] Restart the iSM server. iSM01400: This function is not supported [Explanation] It indicates that functions other than start, stop, update, or prf_update has been specified by iSMsvr command. This message is output on UNIX system. [Measures] Check command format and retry. 18 Chapter 2 Message List iSM01401: Usage: iSMsvr start [Explanation] It indicates that description of iSMsvr start command is incorrect. A specifiable format is shown in the message. Execute the command in valid format. This message is output on UNIX system. [Measures] Check command format and retry. iSM01402: Usage: iSMsvr stop [-e] [Explanation] It indicates that description of iSMsvr stop command is incorrect. A specifiable format is shown in the message. Execute the command in valid format. This message is output on UNIX system. [Measures] Check command format and retry. iSM01403: Usage: iSMsvr update {-m | -s name | -r name} [Explanation] It indicates that description of iSMsvr update command is incorrect. A specifiable format is shown in the message. 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] Retry command execution when the iSM becomes operative. 19 Chapter 2 Message List iSM01408: Rejected: System function error ( ) [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. [Measures] Check error description and retry command execution. If this message is output on a HP-UX system, the following reason is assumed: iSM01408: Rejected: System function error (execl) errno=13 When the iSM server is operated by the administrator for iSM, the setting of the administrator for iSM may not be deleted before uninstallation of the iSM server. In this case, register the administrator for iSM again (delete and set) using the iSM setting command (iSMmkadm). For details on the administrator for iSM setting command, refer to the “User's Manual (UNIX)”. iSM01409: Rejected: msgdrv is not available [Explanation] It indicates that the event link function is not available. This message is output on UNIX system. [Measures] Restarting the iSM is required to use the event link function. iSM01410: This request is accepted [Explanation] It indicates that a device monitoring stop/restart command request has been received. For actual stop/restart operations, refer to syslog. This message is output on UNIX system. [Measures] Unnecessary 20 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= [Explanation] It indicates that an internal error has occurred. aaaa [Measures] : Internal code Obtain information and restart the iSM. iSM01413: Usage: iSMsvr prf_update -t value [Explanation] It indicates that description of iSMsvr prf_update command is incorrect. A specifiable format is shown in the message. Execute the command in valid format. This message is output on UNIX system. [Measures] Check command format and retry. iSM01901: Function error has occurred. Function name= Error code= Error Message= [Classification] ERROR [Explanation] It is an internal error of iSMmainNT. This seems to be a problem depending on Windows system. This message is output on Windows system. [Measures] aaa...a : Function name bbb : Error number ccc...c : Error message Resolve the problem by checking the function name and the error number, and restart the iSM server. 21 Chapter 2 Message List iSM02000 ∼ iSM02010: In initialization, port setting failed errno= [Classification] NOTICE [Explanation] It shows that port number setting has failed in the initializing process. aaaaa [Measures] : Error number 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 other service, or if the specified port number is correct. To check the port number being used, use netstat command. For Windows: Check the server operation environment and review the port number settings. iSM02011: In initialization, shared memory allocation failed errno= [Classification] NOTICE [Explanation] It shows that the acquisition of shared memory has failed in the initializing process. aaaaa [Measures] : Error number Take the measures below. For UNIX : Check the shared memory status by using ipcs command since there is a shortage of usable memory in the system. For Windows: Check the server operating status including memory usage status. 22 Chapter 2 Message List iSM02020: Function Error has occurred name= code= errno= [Classification] NOTICE [Explanation] It shows that a function error has occurred. This message is output on UNIX system. [Measures] aaa...a : Function name bbbbb : Internal code ccccc : Error number Check the settings relevant to the applicable function. Example: iSMclcomm iSM02020:Function Error has occurred name=recv code=417 errno=232 In this case, recv function has error-returned in the errno=232(ECONNRESET:Connection reset by peer) and it is thought that the socket has been disconnected from a client. iSM02021: Internal Error has occurred code= errno= [Classification] NOTICE [Explanation] It shows that an internal error has occurred. This message is output on UNIX system. [Measures] aaaaa : Internal code bbbbb : Error number Check the connection status of iSM client, the environment of server operation and various settings. This message is usually output together with iSM02020. For the specific cause, refer to iSM02020. Example: iSMclcomm iSM02020:Function Error has occurred name=recv code=417 errno=232 iSMclmaind iSM02021:Internal Error has occurred code=1366 errno=* This case shows that the socket has been disconnected from a client in iSM02020 and the communication process for the client has ended. 23 Chapter 2 Message List iSM02040: iSM/Client connected user= client= ip= [Classification] INFO [Explanation] It shows that an iSM client is connected. [Measures] aaa...a : User name bbbbbbbb : iSM client name ccc...c : iSM client’s IP address Unnecessary (This message indicates that the operation is completed as required.) iSM02041: iSM/Client terminated user= client= ip= [Classification] INFO [Explanation] It shows that an iSM client has exited. [Measures] aaa...a : User name bbbbbbbb : iSM client name ccc...c : iSM client’s IP address Unnecessary (This message indicates that the operation is completed as required.) 24 Chapter 2 Message List iSM02042: iSM/Client disconnected user= client= ip= reason= [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 ddd : Reason of the disconnection 001 : Hindrance generated in the client 002 : Time out generated in the client 003 : Others [Measures] Connect the client again if necessary. iSM02043: iSM/Client connect failed user= client= ip= reason= [Classification] NOTICE [Explanation] It shows that iSM client has failed to connect. aaa...a : User name bbbbbbbb : iSM client name ccc...c : iSM client’s IP address ddd : Reason of the disconnection 001 : Incorrect user’s name 002 : Incorrect password 003 : Incorrect IP address 004 : Excessive connection of clients 005 : Resource shortage 006 : Reconnection demand during the process of disconnection of the client 007 : Start terminating iSM server 008 : Internal error generated 009 : Others 010 : Time out generated in the iSM server [Measures] Resolve the problem from the reason of disconnection and reconnect the client. 25 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. [Measures] Unnecessary (This message indicates that the operation is completed as required.) iSM02052: iSM/Client Management Service termination started [Classification] INFO [Explanation] It shows that termination of iSM/Client Management Service has started. [Measures] Unnecessary (This message indicates that the operation is completed as required.) 26 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. To terminate the iSM server, the disconnection from the L3 user client is necessary. iSM02060: Data lost detected client= ip= [Classification] NOTICE [Explanation] It shows that lost of received and transmitted data during process occurred. This message is output on UNIX system. [Measures] aaaaaaaa : iSM client name bbb...b : iSM client’s IP address (Output only to syslog) Remove the status that hinders data transmission in the client’s operation environment or server’s operation environment etc. In this case, the response to operation demand from iSM client may possibly be lost and the information display in the iSM client may not be shown completely. 27 Chapter 2 Message List iSM02061: Data lost recovered client= ip= [Classification] NOTICE [Explanation] It shows that the received and transmitted data lost during process has been recovered. This message is output on UNIX system. [Measures] aaaaaaaa : iSM client name bbb...b : iSM client’s IP address (Output only to syslog) Check if the data loss has an influence on operation or not. Check if a message indicating a trouble on operation has been output or not between the iSM02060 message and this message. 28 Chapter 2 Message List iSM03000 ∼ iSM03100: Disk Array is not specified in the config file. detail= [Classification] [Explanation] WARNING 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] Check description of agent section (disk array or auto_find_spf) in the environment definition file. If no problem is found, check disk connection environment and restart the iSM server. On Windows system, check environment settings (disk array information). If no problem is found, check disk connection environment and restart the iSM server. iSM03101: Object Disk Array does not exist. detail= [Classification] WARNING [Explanation] It shows that the iSM server is started with no disk arrays to be controlled, because no disk arrays to be controlled are found. aa-bbbb : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check description of agent section (diskarray or auto_find_spf) in the environment definition file. If no problem is found, check disk connection environment and restart the iSM server. On Windows system, check environment settings (disk array information). no problem is found, check disk connection environment and restart the iSM server. 29 If Chapter 2 Message List iSM03102: Diskarray[] and diskarray[] are the same disk. detail= [Classification] ERROR [Explanation] It indicates that disk arrays specified by diskarray [a] and diskarray [b] overlap with each other. The iSM server terminates abnormally. a : Disk array specifying number in environment definition file b : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) (UNIX system: 1 to 64, Windows system: 1 to 32) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Describe agent section (diskarray [a] and diskarray [b]) in environment definition file correctly, and restart the iSM server. On Windows system, correctly specify diskarray [a] and diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. iSM03103: IP address ( ) in diskarray[] is invalid description. detail= [Classification] ERROR [Explanation] IP address specified by diskarray [b] is incorrect. The iSM server terminates abnormally. aaa...a : IP address b : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Describe agent section (diskarray [b]) in environment definition file correctly, and restart the iSM server. On Windows system, correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. 30 Chapter 2 Message List iSM03104: IP address ( ) in diskarray[] is not control path to the management object. detail= [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 b : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Describe agent section (diskarray [b]) in environment definition file correctly, and restart the iSM server. On Windows system, correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. iSM03105: IP address ( ) in diskarray[] is defined in the other specification. detail= [Classification] ERROR [Explanation] IP address specified by diskarray [b] is overlapping with others. The iSM server terminates abnormally. aaa...a : IP address b : Disk array specifying number in environment definition file cc-dddd : Detail information (UNIX system: 1 to 64, Windows system: 1 to 32) (This code is not disorder reason but a value for maintenance.) [Measures] Describe agent section (diskarray [b]) in environment definition file correctly, and restart the iSM server. On Windows system, correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. 31 Chapter 2 Message List iSM03106: IP address ( ) in diskarray[] is same as one in diskarray[ ]. detail= [Classification] ERROR [Explanation] The same IP address is specified in diskarray [b] and diskarray [c]. The iSM server terminates abnormally. aaa...a : IP address b : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) c : Disk array specifying number in environment definition file dd-eeee : Detail information (UNIX system: 1 to 64, Windows system: 1 to 32) (This code is not disorder reason but a value for maintenance.) [Measures] Describe agent section (diskarray [b] and diskarray [c]) in environment definition file correctly, and restart the iSM server. On Windows system, correctly specify diskarray [b] and diskarray [c] in environment settings (specifying disk array information) and restart the iSM server. iSM03107: IP address ( ) in diskarray[] contradicts the other specification. detail= [Classification] ERROR [Explanation] The IP addresses specified in diskarray [b] indicates different disk arrays. iSM server terminates abnormally. aaa...a : IP address b : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Describe agent section (diskarray [b]) in environment definition file correctly, and restart the iSM server. On Windows system, correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. 32 Chapter 2 Message List iSM03108: File ( ) in diskarray[] is invalid description. detail= [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. This message is output on UNIX system. aaa...a : Special file name b : Disk array specification number (1 to 64) in the environment definition file (agent section) cc-dddd [Measures] : Detail information Correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. iSM03108: Disk (disk (Port Bus Target Lun )) in diskarray[ ] is invalid description. detail= [Classification] ERROR [Explanation] The disk specified for diskarray[f] in the environment definition file (agent section) is erroneous. The disk may be nonexistent. The iSM server terminates abnormally This message is output on Windows system. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information f : Disk array specification number (1 to 32) in the environment definition file (agent section) gg-hhhh [Measures] : Detail information Correctly specify diskarray [f] in environment settings (specifying disk array information) and restart the iSM server. 33 Chapter 2 Message List iSM03109: File ( ) in diskarray[] is not control path to the management object. detail= [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. aaa...a : Special file name b : Disk array specification number (1 to 64) in the environment definition file (agent section) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. iSM03109: Disk (disk (Port Bus Target Lun )) in diskarray[ ] is not control path to the management object. detail= [Classification] ERROR [Explanation] A disk specified by environment setting (setting of disk array) is not a control path for the monitoring target disk array. The iSM server terminates abnormally. This message is output on Windows system. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information f : Disk array specification number (1 to 32) in the environment definition file (setting of disk array information) gg-hhhh : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [f] in environment settings (specifying disk array information) and restart the iSM server. 34 Chapter 2 Message List iSM03110: File ( ) in diskarray[] is defined in the other specification. detail= [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 b : Disk array specification number (1 to 64) in the environment definition file (agent section) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. iSM03110: Disk (disk (Port Bus Target Lun )) in diskarray[ ] is defined in the other specification. detail= [Classification] ERROR [Explanation] Disks specified in environment setting (setting of disk arrays) overlap with each other. The iSM server terminates abnormally. This message is output on Windows system. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information f : Disk array specification number (1-32) of environment setting (setting of disk array information) gg-hhhh : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [f] in environment settings (specifying disk array information) and restart the iSM server. 35 Chapter 2 Message List iSM03111: File ( ) in diskarray[] is same as one in diskarray[ ]. detail= [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 b : Disk array specification number (1 to 64) in the environment definition file (agent section) c : Disk array specification number (1 to 64) in the environment definition file (agent section) dd-eeee : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [b] and diskarray [c] in environment settings (specifying disk array information) and restart the iSM server. iSM03111: Disk (disk (Port Bus Target Lun )) in diskarray[ ] is same as one in diskarray[ ]. detail= [Classification] ERROR [Explanation] The same disk is specified in diskarray [f] and diskarray [g]. The iSM server terminates abnormally. This message is output on Windows system. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information f : Disk array specification number (1 to 32) of environment setting (setting of disk array information) g : Disk array specification number (1 to 32) in the environment definition file (agent section) hh-iiii : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [f] and diskarray [g] in environment settings (specifying disk array information) and restart the iSM server. 36 Chapter 2 Message List iSM03112: File ( ) in diskarray[] contradicts the other specification. detail= [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 b : Disk array specification number (1 to 64) in the environment definition file (agent section) cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [b] in environment settings (specifying disk array information) and restart the iSM server. iSM03112: Disk (disk (Port Bus Target Lun )) in diskarray[ ] contradicts the other specification. detail= [Classification] ERROR [Explanation] The disks specified in disk array in environment definition indicate different disk arrays. The iSM server terminates abnormally. This message is output on Windows system. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information f : Disk array specification number (1-32) of environment setting (setting of disk array information) gg-hhhh : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Correctly specify diskarray [f] in environment settings (specifying disk array information) and restart the iSM server. 37 Chapter 2 Message List iSM03113: All control paths of diskarray[] are not available. detail= [Classification] WARNING [Explanation] All control paths of diskarray [a] have been blocked. Monitoring to the disk array is disabled. a : 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 for maintenance.) [Measures] Check connection to the disk, and restart the iSM server. iSM03114: Diskarray[] is already managed by autofind. detail= [Classification] WARNING [Explanation] The diskarray [a] has already been incorporated by automatic detecting function. This message is displayed when incorporating by an IP address specified by diskarray [a] failed upon iSM server startup, and the disk array has been incorporated by the automatic detection function. Access to the disk array is not made via the IP address (Ethernet) specified for diskarray[a] but via FC a : 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 for maintenance.) [Measures] Check IP connection to the disk array, and restart the iSM server and select IP connection if necessary. 38 Chapter 2 Message List iSM03120: Management of diskarray[] succeeded. name=( ) detail= [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. a : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : Disk array name cc-dddd : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Unnecessary iSM03121: Management of diskarray[] failed. detail= [Classification] WARNING [Explanation] Failed 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 failed in incorporating. The reason for failure of management is indicated in the preceding message. After that, the disk array may be automatically managed during operation of iSM. a : 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 for maintenance.) [Measures] Check the message preceding this message, and take measures. 39 Chapter 2 Message List iSM03122: Management of diskarray succeeded by autofind. name=( ) detail= [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 iSM03130: Management of control path in diskarray[] failed.ip= port= func= errno= detail= [Classification] NOTICE [Explanation] Failed in building the control path. a : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address ccccc : Port number ddd...d : Function name eee : Error number ff-gggg : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the network connection state to the disk array and the disk array state, and remove the failure. 40 Chapter 2 Message List iSM03131: Management of control path in diskarray[] failed. ip= port= func= reason=(timeout sec.) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path due to time out. a : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address ccccc : Port number ddd...d : Function name eee : Seconds of the time out ff-gggg : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the network connection state to the disk array, and remove the failure. iSM03132: Management of control path in diskarray[] failed. ip= port= reason=(invalid sequence) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. a : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address ccccc : Port number dd-eeee : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Settings of disk array may be incorrect (monitoring by the node running iSM server via LAN may not be allowed). fault. 41 Check settings of disk array and remove Chapter 2 Message List iSM03133: Management of control path in diskarray[] failed. ip= port= reason=(invalid receive data) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. a : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address ccccc : Port number dd-eeee : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the disk array state, and remove the failure. iSM03134: Management of control path in diskarray[] failed. ip= port= command=( ) status=( / / / ) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. a : Disk array specifying number in environment definition file (UNIX system: 1 to 64, Windows system: 1 to 32) bbb...b : IP address ccccc : Port number ddd...d : Command Descriptor Block of the issued command ee : Status Byte ff : Sense Key gg : Additional Sense Code hh : Additional Sense Code Qualifier ii-jjjj : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the disk array state, and remove the failure. 42 Chapter 2 Message List iSM03140: Management of control path in diskarray[] failed. file= func= errno= detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on UNIX system. a : Disk array specification number (1 to 64) in the environment definition file (agent section) bbb...b : Special file name ccc...c : Function number ddd : Error number ee-ffff : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the FC connection state to the disk array and the disk array state, and remove the failure. iSM03140: Management of control path in diskarray[] failed. Disk=(disk (Port Bus Target Lun )) func= errno= detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on Windows system. a : Disk array specification number (1 to 32) in the environment definition file (agent section) diskbbb (Portccc Busddd Targeteee Lunfff): Disk information ggg...g : Function number hhh : Error number ii-jjjj : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the FC connection state to the disk array and the disk array state, and remove the failure. 43 Chapter 2 Message List iSM03141: Management of control path in diskarray[] failed. file= command=( ) status= ( / / / ) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on UNIX system. a : Disk array specification number (1 to 64) in the environment definition file (agent section) bbb...b : Special file name ccc...c : Command Descriptor Block of the issued command dd : Status Byte ee : Sense Key ff : Additional Sense Code gg : Additional Sense Code Qualifier hh-iiii : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the disk array state, and remove the failure. iSM03141: Management of control path in diskarray[] failed. Disk=(disk (Port Bus Target Lun )) command=( ) status=( / / / ) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on Windows system. a : Disk array specification number (1 to 32) in the environment definition file (agent section) diskbbb (Portccc Busddd Targeteee Lunfff): Disk information ggg...g : Command Descriptor Block of the issued command hh : Status Byte ii : Sense Key jj : Additional Sense Code kk : Additional Sense Code Qualifier ll-mmmm : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the disk array state, and remove the failure. 44 Chapter 2 Message List iSM03142: Management of control path in diskarray[] failed.file= command=( ) status=( ) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on UNIX system. a : Disk array specification number (1 to 64) in the environment definition file (agent section) bbb...b : Special file name ccc...c : Command Descriptor Block of the issued command dddddddd : Status Byte ee-ffff : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the disk array state, and remove the failure. iSM03142: Management of control path in diskarray[] failed. Disk=(disk (Port Bus Target Lun )) command=( ) status=( ) detail= [Classification] NOTICE [Explanation] Failed in the inclusion of the control path. This message is output on Windows system. a : Disk array specification number (1 to 32) in the environment definition file (agent section) diskbbb (Portccc Busddd Targeteee Lunfff): Disk information ggg...g : Command Descriptor Block of the issued command hhhhhhhh : Status Byte ii-jjjj : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the disk array state, and remove the failure. 45 Chapter 2 Message List iSM03150: Management of control path by autofind failed. file= func= errno= detail= [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. This message is output on UNIX system. aaa...a : Special file name bbb...b : Function number ccc : Error number dd-eeee : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the FC connection state to the disk array and the disk array state, and remove the failure. Restart iSM server if necessary. iSM03150: Management of control path by autofind failed. Disk=(disk (Port Bus Target Lun )) func= errno= detail= [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. This message is output on Windows system. diskaaa (Portbbb Busccc Targetddd Luneee): Disk information fff...f : Function number ggg : Error number hh-iiii : Detail information (This code is not disorder reason but a value for maintenance.) [Measures] Check the FC connection state to the disk array and the disk array state, and remove the failure. Restart iSM server if necessary. 46 Chapter 2 Message List iSM03151: Management of control path by autofind failed. file= command=( ) status=( / / / ) detail=