HA Monitor Cluster Software 3000-9-134-O0(E) Messages

HA Monitor Cluster Software
Messages
3000-9-134-O0(E)
■ Relevant program products
For the Red Hat Enterprise Linux AS 4 (x86), Red Hat Enterprise Linux ES 4 (x86), Red Hat Enterprise Linux AS 4 (AMD64 & Intel
EM64T), Red Hat Enterprise Linux ES 4 (AMD64 & Intel EM64T), Red Hat Enterprise Linux 5 (x86), Red Hat Enterprise Linux 5 (AMD/
Intel 64), Red Hat Enterprise Linux 5 Advanced Platform (x86), Red Hat Enterprise Linux 5 Advanced Platform (AMD/Intel 64), Red Hat
Enterprise Linux Server 6 (x86), and Red Hat Enterprise Linux Server 6 (x86_64) operating systems:
P-812C-E112 HA Monitor 01-58
For the Red Hat Enterprise Linux AS 4 (x86), Red Hat Enterprise Linux ES 4 (x86), Red Hat Enterprise Linux AS 4 (AMD64 & Intel
EM64T), Red Hat Enterprise Linux ES 4 (AMD64 & Intel EM64T), Red Hat Enterprise Linux 5 (x86), Red Hat Enterprise Linux 5 (AMD/
Intel 64), Red Hat Enterprise Linux 5 Advanced Platform (x86), Red Hat Enterprise Linux 5 Advanced Platform (AMD/Intel 64), Red Hat
Enterprise Linux server 6 (x86), Red Hat Enterprise Linux server 6 (x86_64) operating systems:
P-9S2C-E211 HA Monitor Extension 01-00
This manual can be used for products other than the product shown above. For details, see the Release Notes.
■ Trademarks
HITACHI, JP1, Job Management Partner 1, HiRDB, HA Monitor are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and
other countries.
AMD, AMD Opteron, and combinations thereof, are trademarks of Advanced Micro Devices, Inc.
Itanium is a trademark of Intel Corporation in the United States and other countries.
Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.
Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.
Other company and product names mentioned in this document may be the trademarks of their respective owners.
Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization
used by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use of a
trademark in this document should not be regarded as affecting the validity of the trademark.
■ Restrictions
Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software
described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and
conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of
warranty.
Material contained in this document may describe Hitachi products not available or features not available in your country.
No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.
Printed in Japan.
■ Edition history
June 2015: 3000-9-134-O0(E)
■ Copyright
All Rights Reserved. Copyright (C) 2012, 2015, Hitachi, Ltd.
Summary of amendments
The following table lists changes in this manual (3000-9-134-O0(E)) and product changes related to this manual.
Changes
The following messages were added:
Location
2.2
KAMN107-I, KAMN108-I
The following messages were changed:
KAMN407-I, KAMN414-E, KAMN624-E (HP-UX (IPF) and Linux (IPF)), KAMN624-E (Linux (x86)),
KAMN725-W, KAMN726-E
In addition to the above changes, minor editorial corrections were made.
2.5, 2.7, 2.8
Preface
This manual describes the messages output by HA Monitor. After reading this manual, the reader can expect to be able to
understand the meanings of the messages output by HA Monitor and, if necessary, take the appropriate corrective action.
This manual covers HA Monitor and HA Monitor Extension. HA Monitor is a product that increases system availability by
providing hot standby operation. HA Monitor Extension is an optional product of HA Monitor.
■ Intended readers
This manual is intended for system administrators, operators, and programmers. The manual assumes that system
administrators will perform system installation, design, and configuration; that operators will perform the day-to-day
operations on a configured system; and that programmers will create user programs.
Readers of this manual must have:
• A basic knowledge of the applicable hardware
• A basic knowledge of the applicable operating system
• A basic knowledge of a program for setting up system switchover configurations
• A basic knowledge of C-language syntax for coding user programs
If you use OpenTP1 or HiRDB to set up your system switchover configuration, we recommend that you first read the relevant
OpenTP1 or HiRDB manuals.
■ Conventions: Fonts and symbols
The following table explains the fonts used in this manual:
Font
Bold
Convention
Bold type indicates text on a window, other than the window title. Such text includes menus, menu
options, buttons, radio box options, or explanatory labels. For example:
• From the File menu, choose Open.
• Click the Cancel button.
• In the Enter name entry box, type your name.
Italics
Italics are used to indicate a placeholder for some actual text to be provided by the user or system. For
example:
• Write the command as follows:
copy source-file target-file
• The following message appears:
A file was not found. (file = file-name)
Italics are also used for emphasis. For example:
• Do not delete the configuration file.
Code font
A code font indicates text that the user enters without change, or text (such as messages) output by the
system. For example:
• At the prompt, enter dir.
• Use the send command to send mail.
• The following message is displayed:
The password is incorrect.
The following table explains the symbols used in this manual:
I
Preface
Symbol
|
Convention
In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For
example:
A|B|C means A, or B, or C.
{}
In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected.
For example:
{A|B|C} means only one of A, or B, or C.
[]
In syntax explanations, square brackets indicate that the enclosed item or items are optional. For
example:
[A] means that you can specify A or nothing.
[B|C] means that you can specify B, or C, or nothing.
...
In coding, an ellipsis (...) indicates that one or more lines of coding are not shown for purposes
of brevity.
In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as
many times as necessary. For example:
A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.
■ Conventions: Version numbers
The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen.
For example:
• Version 1.00 (or 1.0) is written as 01-00.
• Version 2.05 is written as 02-05.
• Version 2.50 (or 2.5) is written as 02-50.
• Version 12.25 is written as 12-25.
The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in
the program as 02-00.
II
Contents
1
2
Overview of Messages
1
1.1 Message format
2
1.1.1 Message output format
2
1.1.2 Message statement format
2
1.2 Setting the message language
4
Messages from KAMN000 to KAMN999
5
2.1 Messages from KAMN000 to KAMN099
6
2.2 Messages from KAMN100 to KAMN199
12
2.3 Messages from KAMN200 to KAMN299
29
2.4 Messages from KAMN300 to KAMN399
51
2.5 Messages from KAMN400 to KAMN499
73
2.6 Messages from KAMN500 to KAMN599
89
2.7 Messages from KAMN600 to KAMN699
94
2.8 Messages from KAMN700 to KAMN799
108
2.9 Messages from KAMN900 to KAMN999
117
Appendixes
A. Version Changes
128
A.1 Changes made to the Linux (x86) edition of HA Monitor 01-57 (3000-9-134-N0(E))
128
A.2 Changes made to the Linux (x86) edition of HA Monitor 01-56 (3000-9-134-M0(E))
128
B. Reference Material for This Manual
130
B.1 Related publications
130
B.2 Conventions: Abbreviations for product names
131
B.3 Conventions: Acronyms
132
B.4 Conventions: KB, MB, GB, and TB
133
C. Glossary
Index
127
134
139
i
1
Overview of Messages
This chapter describes, in general terms, the HA Monitor messages.
1
1. Overview of Messages
1.1 Message format
The section describes the message format.
1.1.1 Message output format
Messages are output in the following format.
KAMNnnn-i xx....xx
• KAMNnnn-i: Message ID
• xx....xx: Message text
1.1.2 Message statement format
(1) Statement format
Messages in this manual are presented using the format shown below.
KAMNnnn-i (X)
Message text
The message's meaning is described in this section.
aa....aa: What the variable refers to is explained on this line.
S:
Indicates what processing the system performs after it outputs the message.
O:
Indicates what the operator is to do after checking the message.
Action:
Indicates the corrective action that the system administrator is to take when checking the message.
If this manual advises the operator or system administrator to contact maintenance personnel, they are
recommended to contact the Hitachi representative noted in the purchase agreement.
(2) Explanation of Message ID Symbols
Message ID symbols are explained below.
KAMN:
Indicates that this is an HA Monitor message.
nnn:
Indicates the serialized message identification number.
i:
Indicates the type of message.
E:
• Indicates that an error is preventing library, command, or server functions from being performed.
• Indicates that the attempted operation cannot be executed because an invalid definition or an invalid
operand was specified for the command.
W:
• Indicates a warning about memory usage by libraries, commands, or servers.
• Indicates that a definition was invalid, or an invalid operand was specified for a command, but operation
continued by using a default value.
2
1. Overview of Messages
D:
• Indicates that an error occurred that prevents library, command, or server functions from functioning
correctly, and the operation is pending. Some kind of action must be taken for the operation to continue.
I:
• These are informational messages not categorized as E, W, or D that simply indicate the status of an
operation.
(X):
Indicates the destination to which the message is output.
(E): Standard error
(S): Standard output
(L): Message log file (syslog)
If a single message is output to multiple destinations, the output destinations are concatenated using plus signs (+).
If the message is output only to the message log file (syslog), the output destination is omitted and this area is left
blank.
3
1. Overview of Messages
1.2 Setting the message language
HA Monitor can output messages in English or Japanese. The language that was specified for the OS is used for
message output. For details about setting or switching the language in which messages are output, see the following
manual:
• HA Monitor Cluster Software Guide (for Linux(R) (x86) systems)
4
2
Messages from KAMN000 to
KAMN999
This chapter describes messages from KAMN000 to KAMN999.
5
2. Messages from KAMN000 to KAMN999
2.1 Messages from KAMN000 to KAMN099
KAMN001-I (S+L)
HAmonitor (vv-rr-ss) is started.
HA Monitor startup has begun.
vv: Version number
rr: Revision number
ss: Sequence code
S:
Continues processing.
KAMN002-I (S+L)
HAmonitor was completed. Processing is started.
HA Monitor started normally.
S:
Continues processing.
KAMN003-E (E+L)
HAmonitor cannot be started.
HA Monitor cannot start because an error was detected in HA Monitor startup processing. A message indicating the
error detail is output prior to this message.
S:
Terminates processing.
O:
Take the corrective action described for the message that indicated the error detail.
If all of the following conditions are satisfied, carefully review the specifications for socket buffer size, which is a
kernel parameter.
• Message KAMN601-W indicates the error detail.
• The detail code indicated in KAMN601-W is 233, and the name of the function that generated the error is
ipc_setsockopt.
• The maximum number of servers that can run simultaneously on a single system is specified using the
servmax operand in the HA Monitor environment settings.
KAMN004-E (E+L)
Because not super user, command cannot be executed.
The HA Monitor command that the user attempted to execute cannot be executed because the user is not currently
logged in as a superuser.
S:
Stops command processing.
O:
Login again as a superuser and re-execute the command.
KAMN005-E (E+L)
HAmonitor does not install correctly.
HA Monitor cannot start because it was not installed correctly.
6
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Check that all files are correctly installed under /opt/hitachi/HAmon. If they are, contact a system
administrator.
Action:
Eliminate the cause of the system call error as indicated by KAMN601-W, which is output before this message.
Do not specify the /etc/fstab file or specify the nosuid option with the mount command for the file
systems on which HA Monitor is installed.
KAMN006-E (E+L)
HAmonitor is already processing.
HA Monitor could not start because it was already running.
S:
Terminates processing.
O:
Terminate the instance of HA Monitor that is running, and then restart HA Monitor.
KAMN007-E (E+L)
The control file of HAmonitor cannot be opened.
HA Monitor cannot start because the HA Monitor control file (/opt/hitachi/HAmon/etc/.CTLFILE) cannot
be opened.
S:
Terminates processing.
O:
Check whether the control file exists. If it does, delete it, and then restart HA Monitor. If the control file does not
exist, contact a system administrator.
Action:
Eliminate the cause of the system call error as indicated by KAMN650-E, which is output before this message.
KAMN008-E (E+L)
Shared memory cannot be gotten.
Cause code:aa....aa Memory size:bb....bb
HA Monitor cannot start because a shared memory area cannot be allocated. For details about cause codes, see the
documentation for the applicable OS.
aa....aa: Cause code (errno returned by the system call when an attempt was made to allocate shared memory, 1 to 3
digits)
bb....bb: Size of memory you attempted to allocate (bytes)
S:
Terminates processing.
O:
Check the amount of memory currently available in the system. If the amount of available system memory is less
than the value shown by bb....bb, change the system value, and then restart HA Monitor. If the value is larger,
report the amount of memory allocated and the cause code to a system administrator.
Action:
Eliminate the cause of the system call error as indicated by KAMN650-E, which is output before this message.
7
2. Messages from KAMN000 to KAMN999
KAMN009-E (E+L)
It cannot be written in the control file of HAmonitor.
Cause code:aa....aa
The HA Monitor control file (/opt/hitachi/HAmon/etc/.CTLFILE) is write-protected. For details about
cause codes, see the documentation for the applicable OS.
aa....aa: Cause code (return code when an attempt is made to write to the control file, 1 or 2 digits)
S:
Terminates processing.
O:
Report the cause code to a system administrator.
Action:
Eliminate the cause of the system call error as indicated by KAMN650-E, which is output before this message.
KAMN010-W (E+L)
The control file of HAmonitor cannot be closed.
HA Monitor control processing cannot close the HA Monitor control file (/opt/hitachi/HAmon/
etc/.CTLFILE).
S:
Continues processing.
O:
Delete the control file.
KAMN011-E (E+L)
A memory that is necessary to execute HAmonitor runs short.Memory size:aa....aa
HA Monitor cannot start because the data space is smaller than the memory required to run HA Monitor.
aa....aa: Size of shared memory allocated (bytes)
S:
Terminates processing.
O:
Check the size of the shared memory being allocated and the size of the data space required to run HA Monitor,
and then restart HA Monitor. If this message is output, even though the required amount of data space has been
allocated, contact a system administrator.
Action:
If checking reveals that there is not enough system memory, increase the amount of memory. If there is enough
system memory, determine what is consuming memory, and then take corrective action accordingly.
KAMN012-E (E+L)
Processing of HAmonitor cannot be started.
The process management daemon of HA Monitor cannot start. A message indicating the error detail is output prior to
this message
S:
Terminates processing.
O:
Take the corrective action described for the message that indicated the error detail.
KAMN013-E (E)
Abnormality occurred in File:aa....aa. Error details:bb....bb.
8
2. Messages from KAMN000 to KAMN999
An error occurred in the file indicated by aa....aa.
aa....aa: File name
bb....bb: Detail code (errno of system call)
S:
Terminates processing.
O:
Eliminate the cause of the system call error as indicated by message KAMN601-W, which is output before this
message. If no KAMN601-W message is output before this message, the error occurred while the file was being
read. Use the detail code to eliminate the cause of the error, and then execute the HA Monitor environment setup
command (monsetup).
KAMN021-E (E)
There are syntax errors in command(aa....aa).
The syntax of an HA Monitor command is incorrect.
aa....aa: Command name
S:
Stops command processing.
O:
Execute the command using the correct syntax.
KAMN050-I (S+L)
HAmonitor is terminated.
HA Monitor was terminated normally by the HA Monitor termination command (monstop).
S:
Continues processing.
KAMN051-E (E+L)
HAmonitor is not processing.
An HA Monitor command cannot be executed for the following reason.
• The HA Monitor process is not running.
• There is an error in the control file (/opt/hitachi/HAmon/etc/.CTLFILE).
• There is an error in shared memory.
S:
Stops command processing.
O:
If this message is output while HA Monitor is running, forcibly stop HA Monitor with the kill command, and
then restart it.
KAMN052-W (E+L)
Shared memory cannot be freed, because command (monstop) cannot have access to shared memory. HAmonitor does not
install correctly.
HA Monitor cannot terminate because the HA Monitor's group ID and the HA Monitor termination command's
(monstop) group ID do not match. HA Monitor was installed incorrectly.
S:
Continues processing.
O:
Reinstall using the correct procedure.
9
2. Messages from KAMN000 to KAMN999
KAMN053-W (E+L)
Shared memory cannot be freed.
An error occurred in a system call to free shared memory allocated for HA Monitor.
S:
Continues processing.
O:
Contact a system administrator.
Action:
Eliminate the cause of the system call error.
KAMN054-E (E+L)
Errors occurred in command(monstop). HAmonitor cannot be terminated.
HA Monitor did not terminate because an error occurred in inter-process communications.
S:
Stops command processing.
O:
Re-execute the HA Monitor termination command (monstop).
KAMN055-E (E+L)
Online server or Standby server exists. HAmonitor cannot be terminated.
An HA Monitor termination request was not accepted because there is still an active server or standby server.
S:
Terminates processing.
O:
Check the server status using the server and host status display command (monshow).
If there is an active server, stop the server using the termination method for that server, and then execute the HA
Monitor termination command (monstop).
If there is a standby server, stop all standby servers using the standby server termination command
(monsbystp), and then execute the HA Monitor termination command (monstop).
KAMN056-I (S+L)
HAmonitor is terminated.
HA Monitor has terminated normally.
S:
Continues processing.
KAMN058-W
The group operand of server:(aa....aa) is invalid.
The server indicated by the server alias name is specified as one of the servers to be grouped by the group operand of
the environment setting for servers (servers), but that operand is invalid because the number of servers specified in
the group exceed the system limit.
aa....aa: Server alias name
S:
Continues processing.
O:
Revise the environment setting for servers (servers) so that the number of servers specified in the group does
not exceed the system limit.
10
2. Messages from KAMN000 to KAMN999
KAMN066-E
The HAmonitor process stopped abnormally. An operating system panic occurred. (details code:aa....aa)
An OS panic occurred because the HA Monitor process terminated abnormally.
aa....aa: Detail code
Detail code
Meaning
PRCMAIN
The prcmain process terminated abnormally.
HAIOD
The haiod process terminated abnormally.
HCMREAD
The hcmread process terminated abnormally.
S:
Terminates processing.
O:
Restart the host.
Action:
Contact maintenance personnel.
11
2. Messages from KAMN000 to KAMN999
2.2 Messages from KAMN100 to KAMN199
KAMN100-I (S)
A check of a definition file is started.
A definition check command (moncheck) was received, and a check of the environment settings definition file has
started.
S:
Continues processing.
KAMN101-I (S)
A check of a definition file was completed perfectly.
No errors were found in the environment settings definition file, and the check terminated normally.
S:
Continues processing.
KAMN102-E (E)
A check of a definition file was stopped abnormally.
An error was found in the environment settings definition file.
S:
Terminates processing.
O:
Correct the environment settings definition file.
KAMN105-I (S)
Definition file:aa....aa, bb....bb [cc....cc]
This is the header part for the device information that is output by the definition check command (moncheck).
aa....aa: Definition file name
bb....bb: 'Host Name' or 'Alias'
cc....cc: Host name, server alias name, or program alias name
S:
Continues processing.
KAMN106-E (E)
It was started the command of [bb....bb] to check [aa....aa].
But abnormality occurred in the command processing.
An error occurred when a device check was run with the definition check command (moncheck). Either a device that
is not in the system was defined, or a device driver has not been installed.
aa....aa: Name of operand that was to be checked
bb....bb: Name of command that was to be executed
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Correct the device definition or install the device driver.
12
2. Messages from KAMN000 to KAMN999
KAMN107-I (S)
Reservation release processing for server:aa....aa will now start.
Device Status
bb....bb cc....cc
Reservation release processing will start for the shared disks used by the server indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Device name of the server
cc....cc: Device status
S:
Continues processing.
KAMN108-I (S)
Reservation release processing for server:aa....aa is complete. Details:bb....bb
Reservation release processing is complete for all shared disks used by the server indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Detail code
Detail code
Meaning
SUCCESS
Reservation release processing was successful for the shared disks used by server aa...aa.
FAILURE
Reservation release processing failed for at least one of the shared disks used by server aa...aa.
S:
Terminates processing.
Action:
Take one of the following actions, as indicated by the detail code:
Detail code
Corrective action
SUCCESS
No action is needed, because reservation release processing was successful for all shared disks.
FAILURE
Take the corrective action described for the error detail indicated in the message that was
output prior to this message.
KAMN112-E (E+L)
This environment cannot specify hab_gid.
The hab_gid operand, a server environment definition, cannot be specified under the current software configuration.
S:
Terminates processing.
O:
Check whether HA Booster has been correctly installed.
KAMN113-E (E)
The setting of specified value bb....bb of the aa....aa operand is wrong. Detailed code:cc....cc.
An invalid value was set for an operand specified in the definition file.
aa....aa: Operand name
bb....bb: Operand specification
cc....cc: Detail code
13
2. Messages from KAMN000 to KAMN999
Detail code
PATH
Meaning
One of the following errors has occurred:
• The specified symbolic link or logical device does not exist.
• A relative path was specified instead of an absolute path.
In addition, one of the following errors might have occurred.
If the operand name is scsi_device and HDLM is being used as the multipath software:
• HDLM is not installed.
• HDLM service has stopped.
If the operand name is dmmp_device and DMMP is being used as the multipath software:
• DMMP is not installed.
• DMMP service has stopped.
DEVICE_TYPE
One of the following errors has occurred.
When the operand name is scsi_device:
• If HDLM is being used as the multipath software:
The specified device is not a logical device for HDLM.
HDLM is not installed.
The HDLM service has stopped.
• If a virtual environment based on VMware ESXi is being used:
The device in the specified symbolic link does not support SCSI reservation.
The specified symbolic link is for a logical device (such as an LVM logical volume or a
logical device for multipath software).
• In all other cases:
Possible errors are the same as when a virtual environment based on VMware ESXi is
being used.
When the operand name is dmmp_device and DMMP is being used as the multipath software:
• The specified device is not a logical device for DMMP.
• DMMP is not installed.
• The DMMP service has stopped.
S:
Continues processing.
O:
Take one of the following actions, as indicated by the detail code:
Detail code
Corrective action
PATH
Check the shared disk symbolic links or the logical device name for HDLM or DMMP, and then
correct the operand specifications as necessary.
DEVICE_TYPE
Check the shared disk symbolic links or the logical device name for HDLM or DMMP, and then
correct the operand specifications as necessary.
If the operand name is scsi_device and HDLM is being used as the multipath software, and
if the specified logical device is correct, check the operating status of the HDLM service.
If the operand name is dmmp_device and the specified logical device is correct, check the
operating status of the DMMP service.
KAMN115-E (E)
In this system, aa....aa cannot be specified.
A definition is invalid.
aa....aa: Operand name
14
2. Messages from KAMN000 to KAMN999
S:
Suspends processing.
O:
Check the HA Monitor environment settings or the server environment definition. Correct the definition as
needed, and then restart HA Monitor.
KAMN116-W (E)
The same shared resource is defined for two or more servers. operand name:aa....aa, specified operand value:bb....bb
A single shared resource is defined for multiple servers in a server environment definition.
aa....aa: Operand name
bb....bb: Operand specification
S:
Continues processing.
O:
Check the operand specifications in the server environment definition and correct them as necessary.
KAMN117-E (E)
The aa....aa of the multicast_lan operand of definition file:sysdef does not exist in the /etc/hosts file, or is not class D
multicast address.
The value specified for the multicast_lan operand in the HA Monitor environment settings is not in the /etc/
hosts file. Or, the value specified in the /etc/hosts file is not a class D multicast address.
aa....aa: Host name corresponding to the multicast group ID (TCP/IP LAN)
S:
Terminates processing.
O:
Carefully review the following specifications, and correct them as necessary.
• Value specified for the multicast_lan operand in the HA Monitor environment settings
• Multicast group ID specified in the /etc/hosts file
KAMN118-W (E)
The same value is specified for the same operand of two or more programs. operand name:aa....aa specified operand
value:bb....bb
The same value is specified for the same operand in multiple program definition statements in the monitor-mode
program environment definition.
aa....aa: Operand name
bb....bb: Operand specification
S:
Terminates processing.
O:
Check the values specified for operands of monitor-mode program environment definition, and correct them as
necessary.
KAMN119-W (E)
Definition file:programs exists, but does not specify to use the function of program.
A value of 1 or more is specified for the pgmmax operand in the HA Monitor environment settings, and a monitormode program environment definition file exists, but it has not been set to allow use of the monitor-mode program
management function.
S:
Continues processing.
15
2. Messages from KAMN000 to KAMN999
O:
Check the following items:
• Is a value of 1 or more specified for the pgmmax operand in the HA Monitor environment settings, even
though the monitor-mode program management function will not be used?
• Is nouse specified for the program operand in the server environment definition even though the monitormode program management function will be used? In addition, check whether definition of the program
operand has been omitted.
KAMN120-E (E)
Definition file :aa....aa, There is not dd....dd in cc....cc operand of the bb....bb definition sentence.
A search was performed for the relevant server definition based on the program name or server alias name when the
program started, but no match was found.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
dd....dd: Operand specification
S:
Terminates processing.
O:
Check the content of the server environment definition.
KAMN130-E (E)
Definition file:aa....aa, Because the file does not exist or the file does not consist for reading, it cannot open.
A definition file in the environment settings cannot be opened.
aa....aa: Definition file name
S:
Terminates processing.
O:
Check whether the environment settings definition file exists, and whether the read attribute is set, and then
correct the definition file as necessary.
If the definition file is programs, check the following:
• Is a value of 1 or more is specified for the pgmmax operand in the HA Monitor environment settings even
though the monitor-mode program management function will not be used?
• Is use specified for the program operand in the server environment definition even though the monitormode program management function will not be used?
KAMN140-E (E)
Definition file:aa....aa, The number of characters of the bb....bb line is too much.
The length of a character string specified in the definition file for the environment settings exceeds 1,024 characters.
aa....aa: Definition file name
bb....bb: Relative line number where the character string is located
S:
Terminates processing.
O:
Check the character string on the line in the definition file that generated the error.
KAMN142-E (E)
Definition file:aa....aa, The method of a definition of the value of the dd....dd operand of the cc....cc definition sentence of the
bb....bb line is incorrect.
16
2. Messages from KAMN000 to KAMN999
The value of an operand in a definition file is specified incorrectly.
aa....aa: Definition file name
bb....bb: Relative line number where the value is specified
cc....cc: Definition statement name
dd....dd: Operand name
S:
Terminates processing.
O:
Check the specification on the line that generated the error in the environment settings definition file, and correct
it as necessary.
KAMN144-E (E)
Definition file:aa....aa, The method of a definition of the cc....cc definition sentence of the bb....bb line is incorrect.
A definition statement in the definition file is defined incorrectly.
aa....aa: Definition file name
bb....bb: Relative line number where the definition statement is located
cc....cc: Definition statement name
S:
Terminates processing.
O:
Check the definition statement in the line that generated the error in the environment settings definition file.
KAMN146-E (E)
Definition file:aa....aa, The method of a definition of the dd....dd operand of the cc....cc definition sentence of the bb....bb line
is incorrect.
An operand in an environment settings definition file is defined incorrectly.
aa....aa: Definition file name
bb....bb: Relative line number where operand is located
cc....cc: Definition statement name
dd....dd: Operand name
S:
Terminates processing.
O:
Check the operand in the line that generated the error in the environment settings definition file, and correct it as
necessary.
KAMN148-W (E+L)
Definition file:aa....aa, Unnecessary end symbol(ff....ff) is defined in the ee....ee of the dd....dd operand of the cc....cc
definition sentence of the bb....bb line.An end symbol is ignored.
An unnecessary delimiter symbol was found for an operand in an environment settings definition file. The delimiter
was ignored.
aa....aa: Definition file name
bb....bb: Relative line number where operand is located
cc....cc: Definition statement name
dd....dd: Operand name
ee....ee: Operand specification
ff....ff: Delimiter symbol
S:
Continues processing.
17
2. Messages from KAMN000 to KAMN999
O:
Check the operand in the line that generated the error in the definition file of the server environment definition,
and correct it as necessary.
KAMN150-E (E)
Definition file:aa....aa, Specification of dd....dd of the cc....cc operand of the bb....bb definition sentence is incorrect.
The value specified for an operand in an environment settings definition file is invalid.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
dd....dd: Operand specification
S:
Terminates processing.
O:
Check the specification in the line that generated the error in the environment settings definition file, and correct it
as necessary.
KAMN151-E (E)
Definition file:aa....aa, The number of the values of the cc....cc operand of the bb....bb definition sentence has exceeded a
maximum value.
The number of operands in the environment settings definition file exceeds the maximum.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
S:
Terminates processing.
O:
Reduce the number of operands in the environment settings definition file.
KAMN152-E (E)
Definition file:aa....aa, Length of a character string in dd....dd of the cc....cc operand of the bb....bb definition sentence is
incorrect.
The length of a character string specified for an operand in an environment settings definition file is outside the
permitted range.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
dd....dd: Operand specification
S:
Terminates processing.
O:
Correct the character string length of the specification of the operand in the environment settings definition file.
KAMN153-E (E)
Definition file:aa....aa, The cc....cc operand cannot be defined to the bb....bb definition sentence.
A disallowed operand was specified in a definition statement in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
18
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Delete the disallowed operand in the definition statement in the environment settings definition file.
KAMN154-E (E)
Definition file:aa....aa, The cc....cc operand of the bb....bb definition sentence does not have a value.
No value was specified for an operand in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
S:
Terminates processing.
O:
Specify a value for the operand in the environment settings definition file.
KAMN155-W (E+L)
Definition file:aa....aa, The dd....dd is defined in several to the cc....cc operand of the bb....bb definition sentence. A value
after the second is ignored.
The same value was specified for an operand multiple times in an environment settings definition file. The second and
all subsequent values were ignored.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
dd....dd: Operand specification
S:
Continues processing.
O:
Delete the redundant specifications for the operand in the environment settings definition file.
KAMN156-W (E+L)
Definition file:aa....aa, The cc....cc operand is defined in several to the bb....bb definition sentence. An operand after the
second is ignored.
A single operand was defined multiple times in the definition statements of an environment settings definition file.
The second and all subsequent operands were ignored.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
S:
Continues processing.
O:
Delete the redundant operands in the definition statement in the environment settings definition file.
KAMN157-E (E)
Definition file:aa....aa, The bb....bb definition sentence cannot be defined.
A disallowed definition statement was specified in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Definition statement name
19
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Delete all content in the environment settings definition file other than HA Monitor definition statements.
KAMN158-E (E)
Definition file:aa....aa, The bb....bb definition sentence is defined in several.
A single definition statement was specified multiple times in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Definition statement name
S:
Terminates processing.
O:
Delete the redundant definition statements in the environment settings definition file.
KAMN159-E (E)
Definition file:aa....aa, There is not a cc....cc operand of the bb....bb definition sentence.
A required operand was not specified in a definition statement of an environment settings definition file.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
S:
Terminates processing.
O:
Add the required operand to the definition statement in the environment settings definition file.
KAMN160-E (E)
Definition file:aa....aa, A memory necessary in the definition analysis ran short.
An error occurred while allocating the work area for definition analysis.
aa....aa: Definition file name
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Remove unnecessary processes, and then retry the operation.
KAMN161-E (E)
Definition file:aa....aa, There is not a bb....bb definition sentence.
A required definition statement was not specified in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Definition statement name
S:
Terminates processing.
O:
Add the required definition statement to the environment settings definition file.
20
2. Messages from KAMN000 to KAMN999
KAMN162-E (E)
Definition file:aa....aa, The dd....dd of the cc....cc operand of the bb....bb definition sentence is outside a range.
The specification of an operand in an environment settings definition file is outside the permitted range.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
dd....dd: Operand specification
S:
Terminates processing.
O:
Check the operand specification in the environment settings definition file, and correct it as necessary.
KAMN163-E (E)
Definition file:aa....aa, There is a mistake in contents specified as the cc....cc operand of the bb....bb definition sentence.
The specification of an operand in an environment settings definition file is incorrect.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
S:
Stops processing.
O:
Check the specification of the operand in the environment settings definition file that generated the error, and
correct it as necessary.
KAMN164-E
The servers:(aa....aa, aa....aa) are specified as a server group with the group name:cc....cc in the definition file:bb....bb, but
the specified value of the dd....dd operand is not in agreement.
A server group definition was specified in the definition file indicated by the definition file name, but the value
specified in the operand indicated by the operand name does not match.
aa....aa: Server alias name or resource server alias name
bb....bb: Definition file name
cc....cc: Group name
dd....dd: Operand name
S:
Terminates processing.
O:
Change the operand indicated by the operand name in the definition file indicated by the definition file name, so
that the server groups are consistent.
KAMN165-E (E)
Definition file:aa....aa, The number of the specification values of the cc....cc operand and the dd....dd operand of the bb....bb
definition sentence does not agree.
The numbers of values specified for two operands in the environment settings definition file do not match.
aa....aa: Definition file name
bb....bb: Definition statement name
cc....cc: Operand name
dd....dd: Operand name
21
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Correct the values specified for the two operands that caused the error in the environment settings definition file,
so that the numbers match.
KAMN166-W (S+L)
Definition file:aa....aa, Because cc....cc operand is not specified in the bb....bb definition sentence, the dd....dd operand is
ignored.
A required operand was not specified in the HA Monitor definition, so the dd....dd operand specification was ignored.
aa....aa: Definition file name
bb....bb: Definition sentence name
cc....cc: Operand name
dd....dd: Operand name
S:
Continues processing.
O:
Add the required operand to the definition file in the environment settings, and restart HA Monitor if needed.
KAMN169-E (E)
Definition file:sysdef, There is a mistake in contents specified as the pathpatrol_retry operand of the function
definition sentence. The product of retry interval and retry times has exceeded the health check interval.
The specification for the pathpatrol_retry operand in the HA Monitor environment settings is incorrect. The
product of the retry interval and retry times specified in the pathpatrol_retry operand exceeds the health check
interval for monitoring paths specified in the pathpatrol operand.
S:
Terminates processing.
O:
Correct the specifications of the pathpatrol and pathpatrol_retry operands in the HA Monitor
environment settings.
KAMN170-W (E)
There are errors of contents:bb....bb for the aa....aa line of definition file:connection.
The connection configuration file contains an error.
aa....aa: Relative line number that generated the error
bb....bb: Description of error
S:
Ignores all information from the erroneous information to the next semicolon (;), and then resumes processing.
O:
Correct the error in the connection configuration file. In addition, execute the server and host status display
command (monshow) with the -c option to check the connection, since the host specified in the erroneous
information might not be connected. If it is not connected, execute the HA Monitors manual connection command
(monlink) and manually connect the missing host.
KAMN172-W (E)
The aa....aa of the lan operand of definition file:sysdef is not exist in the /etc/hosts file.
A value specified in the lan operand of the HA Monitor environment settings is not found in the /etc/hosts file.
Another possibility is that the value specified in the lan operand was entered incorrectly.
aa....aa: Host name of monitoring path (TCP/IP LAN)
22
2. Messages from KAMN000 to KAMN999
S:
Continues processing. Note that the incorrect monitoring path cannot be used.
O:
Correct the error in the HA Monitor environment settings, and then restart HA Monitor.
KAMN173-W (E)
The aa....aa of the lanport operand of definition file:sysdef is not exist in the /etc/services file.
A value specified in the lanport operand of the HA Monitor environment settings is not in the /etc/services
file. Another possibility is that the value specified in the lanport operand was entered incorrectly.
aa....aa: Service name of monitoring path (TCP/IP LAN)
S:
Continues processing. Note that the incorrect monitoring path cannot be used.
O:
Correct the error in the HA Monitor environment settings, and then restart HA Monitor.
KAMN174-W (E+L)
The aa....aa of the lan operand of definition file:sysdef cannot use as the Patrol Path.
The monitoring path for the TCP/IP host name specified in the lan operand of the HA Monitor environment settings
cannot be used. The possible causes are as follows:
• The network interface has not been started.
• The network being used cannot broadcast.
• The IP address of the monitoring path for HA Monitor specified in the /etc/hosts file is incorrect.
aa....aa: Host name of monitoring path (TCP/IP LAN)
S:
Ignores the specification and continues processing. Note that the incorrect monitoring path cannot be used.
O:
If the network interface has not been started, start it, and then restart HA Monitor. If the network being used
cannot broadcast, use another network. Carefully review the IP address specified in the /etc/hosts file. If
there is an error, correct it, and then restart HA Monitor.
KAMN175-I
Definition file:connection is updated.
Host information has been added to the connection configuration file because the connected host was not specified in
the connection configuration file.
S:
Updates the connection configuration file, and then continues processing.
KAMN176-E
It could not be connected with host:aa....aa specified as definition file:connection.
The host specified in the connection configuration file could not be connected to, despite connection processing
reaching its limit. The possible causes are as follows:
• The host is not running.
• The connection configuration file contains an error.
• The attempt to communicate failed because the monitoring path contained an error.
aa....aa: Host name
S:
Ignores the host that cannot be connected, and continues processing.
23
2. Messages from KAMN000 to KAMN999
O:
If the host is running when this message is received, check the connection configuration file. If a TCP/IP LAN is
being used for the monitoring path, check the contents of the HA Monitor environment settings, the /etc/
hosts file, and the /etc/services file. If there is an error in a file, correct the error, and then connect to the
HA Monitor using the HA Monitors manual connection command (monlink). If there is no error, there might be
an error in communications with the host.
If you cannot connect despite executing the monlink command several times, eliminate any monitoring path
errors, and then restart HA Monitor.
KAMN177-E
Because it is already used, Port Number bb....bb of Service Name:aa....aa of TCP/IP cannot be used as a Patrol Path of the
HAmonitor.
The port number specified in the service indicated by the service name in the /etc/services file is being used by
another process. It cannot be used as the monitoring path of the HA Monitor.
aa....aa: Service name of monitoring path (TCP/IP LAN)
bb....bb: Port number of monitoring path (TCP/IP LAN)
S:
Continues processing. Note that the incorrect monitoring path cannot be used.
O:
Terminate the other process that is using the specified port number in the monitoring path of HA Monitor.
Alternatively, change the port number and restart HA Monitor.
KAMN178-W
Value:cc....cc of host:bb....bb specified for the aa....aa line of definition file:connection is wrong.
The host address or IP address specified in the connection configuration file does not match the value for that host.
aa....aa: Relative line number in the connection configuration file
bb....bb: Host name
cc....cc: Host or IP address
S:
Ignores the error and continues processing.
O:
Correct the error in the connection configuration file.
KAMN179-E
The TCP/IP host name for the IP address cannot be acquired. IP address:aa....aa
An attempt to acquire the TCP/IP host name failed for the following reason.
• An attempt to generate a process failed.
Note that the TCP/IP host name is not displayed when the monitoring path status display command (monpath) is
executed with the -i option.
aa....aa: IP address
S:
Continues processing.
O:
If an attempt to generate a process fails, check the reason given in message KAMN601-W, which is output before
this message, and eliminate the cause of the error.
KAMN184-E (E)
Definition file:aa....aa line bb....bb, The number of the values of the cc....cc operand is too much.
The number of operand values specified in the environment settings definition file exceeds the maximum.
24
2. Messages from KAMN000 to KAMN999
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
S:
Terminates processing.
O:
Reduce the number of operands in the environment settings definition file.
KAMN185-E (E)
Definition file:aa....aa line bb....bb, The number of the values of the cc....cc operand is not enough.
The number of operand values specified in the environment settings definition file is smaller than the minimum.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
S:
Terminates processing.
O:
Increase the number of operands in the environment settings definition file.
KAMN186-E (E)
Definition file:aa....aa line bb....bb, There is a mistake in contents:dd....dd as the cc....cc operand.
The value specified for an operand in an environment settings definition file is invalid.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
dd....dd: Operand specification
S:
Terminates processing.
O:
Correct the operand specification in the environment settings definition file.
KAMN187-E (E+L)
Definition file:aa....aa line bb....bb, The number of the values of the cc....cc operand is too much.
The number of operand values specified in the environment settings definition file exceeds the maximum.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
S:
Terminates processing.
O:
Reduce the number of operands in the environment settings definition file.
KAMN188-E (E+L)
Definition file:aa....aa line bb....bb, The number of the values of the cc....cc operand is not enough.
The number of operand values specified in the environment settings definition file is smaller than the minimum.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
25
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Increase the number of operands in the environment settings definition file.
KAMN189-E (E+L)
Definition file:aa....aa line bb....bb, There is a mistake in contents:dd....dd as the cc....cc operand.
The value specified for an operand in an environment settings definition file is invalid.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
dd....dd: Operand specification
S:
Terminates processing.
O:
Correct the operand specification in the environment settings definition file.
KAMN190-E (E+L)
There is not a LAN status setting file:aa....aa.
The status settings file indicated by the LAN status settings file name does not exist.
aa....aa: LAN status settings file name
S:
Terminates processing.
O:
Create the status settings file indicated by the LAN status settings file name, and then restart HA Monitor or the
server.
KAMN191-E (E+L)
The LAN status cannot be set the LAN status setting file:aa....aa. Error details:bb....bb.
The LAN status cannot be set using the status settings file indicated by the LAN status settings file name.
aa....aa: LAN status setting files name
bb....bb: Detail code (sets errno of system call)
S:
Terminates processing.
O:
Check whether the status settings file indicated by the LAN status settings file name has permission to set the
status. If it does not have permission, run the operating system's chmod command to give it permission, and then
restart the HA Monitor or server. If the file does have permission to set the status, contact a system administrator.
For details about the operating system's chmod command, see the documentation for the applicable OS.
Action:
Eliminate the cause of the system call error that is indicated by the detail code.
KAMN192-E
There is not a LAN status setting file:aa....aa.
The status settings file indicated by the LAN status settings file name does not exist.
aa....aa: LAN status settings file name
S:
Continues processing.
26
2. Messages from KAMN000 to KAMN999
O:
Create the status settings file indicated by the LAN status settings file name, and then set the LAN status, if
necessary.
KAMN193-E
The LAN status cannot be set the LAN status setting file:aa....aa. Error details:bb....bb.
The LAN status cannot be set using the status settings file indicated by the LAN status settings file name.
aa....aa: LAN status settings file name
bb....bb: Detail code (sets errno of system call)
S:
Continues processing.
O:
Check whether the status settings file indicated by the LAN status settings file name has permission to set the
status. If it does not have permission, run the operating system's chmod command to give it permission, and then
restart the HA Monitor or server. If the file does have permission to set the status, contact a system administrator.
For details about the operating system's chmod command, see the documentation for the applicable OS.
Action:
Eliminate the cause of the system call error that is indicated by the detail code.
KAMN194-W (E)
The servers:(aa....aa, aa....aa, ...) invalidate specification of exclusive_servers operand of a definition file:servers_opt
between the servers so that there is specification as bb....bb group server in the definition file:servers.
The servers indicated by the server alias names have been specified as one of the servers grouped in the server
environment definition. Servers specified in the same group cannot be made into exclusive servers. Specification of
the exclusive_servers operand in the exclusive server environment definition (servers_opt) is not valid for
those servers.
aa....aa: Server alias name
bb....bb: Group name
S:
Continues processing.
Action:
Correct the definition so that servers within the same group do not become locked servers.
KAMN195-E (E)
Definition file:aa....aa, line bb....bb, The cc....cc operand cannot be defined.
An invalid operand was specified in a definition statement in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
S:
Terminates processing.
O:
Delete the invalid operand in the definition statement in the environment settings definition file.
KAMN196-E (E)
Definition file:aa....aa line bb....bb, The method of a definition of the cc....cc operand is incorrect.
An operand in an environment settings definition file is specified incorrectly.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
27
2. Messages from KAMN000 to KAMN999
cc....cc: Operand name
S:
Terminates processing.
O:
Correct the operand specification in the environment settings definition file.
KAMN197-E (E+L)
Definition file:aa....aa, line bb....bb, The cc....cc operand cannot be defined.
An invalid operand was specified in a definition statement in an environment settings definition file.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
S:
Terminates processing.
O:
Delete the invalid operand in the definition statement in the environment settings definition file.
KAMN198-E (E+L)
Definition file:aa....aa line bb....bb, The method of a definition of the cc....cc operand is incorrect.
An operand in an environment settings definition file is specified incorrectly.
aa....aa: Definition file name
bb....bb: Relative line number in definition file
cc....cc: Operand name
S:
Terminates processing.
O:
Correct the operand specification in the environment settings definition file.
KAMN199-E (E)
Although server:(aa....aa, aa....aa, ...) has specification in definition file:servers as a server group by group name:bb....bb, the
specification value of a standbypri operand is not in agreement.
A server group definition was specified in the server environment definition, but the value specified in the
standbypri operand does not match.
aa....aa: Server alias name, or resource server alias name
bb....bb: Group name
S:
Terminates processing.
O:
Change the standbypri operand in the server environment definition so that the server groups are consistent.
28
2. Messages from KAMN000 to KAMN999
2.3 Messages from KAMN200 to KAMN299
KAMN201-I
It connected with HAmonitor of host:aa....aa.
A connection was made to HA Monitor on the host indicated by the host name.
aa....aa: Host name
S:
Continues processing.
KAMN202-E
A communication error with host:aa....aa occurred. Start answer cannot be sent.
An error occurred when transmitting a start response to HA Monitor on the system indicated by the host name.
aa....aa: Host name
S:
Ignores start messages from the host indicated by the host name.
O:
Contact a system administrator.
Action:
Eliminate the cause of the communication error, and then restart HA Monitor on the host indicated by the host
name.
KAMN203-E
A communication error with host:aa....aa occurred. Start impossibility answer cannot be sent.
An error occurred when transmitting a cannot-start response to HA Monitor on the system indicated by the host name.
aa....aa: Host name
S:
Ignores start messages from the host indicated by the host name.
O:
Contact a system administrator.
Action:
Eliminate the cause of the communication error, and then correct the name and address operands of the
environment settings of HA Monitor on the host indicated by the host name so that their values do not duplicate
values in other systems. Then restart HA Monitor.
If there are no errors in the HA Monitor environment settings, wait a short while, and then restart HA Monitor.
KAMN204-E
Obstacle processing of own host is being done on host:aa....aa. HAmonitor is terminated.
HA Monitor terminates because the host indicated by the host name is processing a system failure. After this message
is output, the host indicated by the host name will reset itself.
aa....aa: Host name
S:
Terminates processing.
O:
After the host finishes processing the system failure, restart HA Monitor.
KAMN205-E
Host name and host address are duplicated with the processing host's. HAmonitor is terminated.
29
2. Messages from KAMN000 to KAMN999
The host name and host address in the HA Monitor environment settings are the same as those of another host that is
currently running.
S:
Terminates processing.
O:
Correct the name and address operands in the HA Monitor environment settings so that their values are not the
same as any other systems, and then restart HA Monitor.
KAMN206-E (E)
An error occurred in command(aa....aa). Command cannot be executed.
A communication error occurred between a command (shell) and HA Monitor.
aa....aa: Command name
S:
Stops command processing.
O:
Re-execute the command. If the communication error occurs again, contact a system administrator. If the
command name that is output is monswap, the server (TP1 or HiRDB) might terminate abnormally during system
switchover and this message might be output. If the system switchover was successful, ignore this message.
Action:
Determine the cause of the error based on the error message that was output before this message.
KAMN207-E
The number of connected hosts exceeded upper limit. HAmonitor is terminated.
A start message was sent to HA Monitor on another system, but the start request could not be accepted because startup
of the current system would have caused the number of running hosts to exceed the maximum.
S:
Terminates HA Monitor in the current system.
O:
Re-evaluate the system configuration.
KAMN208-E
Host name is duplicated with the processing host's. HAmonitor is terminated.
A start message was sent to HA Monitor on another system, but the start request could not be accepted because the
recipient host has the same name as the transmitting host.
S:
Terminates HA Monitor in the current system.
O:
Check the HA Monitor environment settings, and then give the host a name that is unique within the system.
KAMN209-E
Host address is duplicated with host:aa....aa's. HAmonitor is terminated.
A start message was sent to HA Monitor on another system, but the start request could not be accepted because the
recipient host has the same address as the transmitting host.
aa....aa: Host name
S:
Terminates the HA Monitor in the current system.
O:
Check the HA Monitor environment settings, and then give the host an address that is unique within the system.
30
2. Messages from KAMN000 to KAMN999
KAMN210-I
HAmonitor of host:aa....aa is terminated.
A connection to HA Monitor on the host indicated by the host name has been terminated.
aa....aa: Host name
S:
Continues processing.
KAMN211-I (S)
Standby server:aa....aa was terminated normally.
The standby server indicated by the server alias name terminated normally.
aa....aa: Server alias name
S:
Continues processing.
KAMN212-E (E)
Online server:aa....aa was stopped by plan. Because an error occurs in communication with host(bb....bb), Hotstandby cannot
be done.
An attempt was made to perform a planned shutdown of the active server using the planned hot-standby command
(monswap), but the system could not perform a hot standby because of a communication failure with the host
indicated by the host name. If HA Monitor and a standby server are running normally on the host indicated by the host
name, a system reset will now be executed on that host.
aa....aa: Server alias name
bb....bb: Host name
S:
Terminates processing.
O:
If HA Monitor and standby servers are running, first terminate the standby server normally, and then restart the
active server on the paired host. Alternatively, wait for the paired host to detect the communication failure with the
current system's host and perform a hot standby.
If HA Monitor is not running on the host indicated by the host name, restart the active server on the current
system's host. In addition, contact a system administrator.
Action:
Determine the cause of the communication failure.
KAMN213-I (S)
Own host name : aa....aa
Own servers Pair servers
Alias Status Status Host name
bb....bb cc....cc dd....dd ee....ee
This is the server status list that is output by the server and host status display command (monshow).
aa....aa: Name of local system host
bb....bb: Server alias name
cc....cc: Status of local system server
dd....dd: Status of paired system server
ee....ee: Host name of paired system
S:
Continues processing.
31
2. Messages from KAMN000 to KAMN999
KAMN213-I (S)
Own host name : aa....aa
Group name : bb....bb
Alias : cc....cc Status : dd....dd
This is the server status list that is output when the status of a server group is displayed.
aa....aa: Name of local system host
bb....bb: Group name of server group
cc....cc: Server alias name
dd....dd: Server status
S:
Continues processing.
KAMN213-I (S)
Own host name : aa....aa
Server : bb....bb
*** DISK information ***
-NAME---------------------------cc....cc
dd....dd
on_opt="ee....ee"
*** File system information ***
-NAME---------------------------ff....ff
mount dir=gg....gg
mount opt=hh....hh
This is the server status list that is output when shared resource information is displayed.
aa....aa: Name of local system host
bb....bb: Server alias name
cc....cc: Special file name of volume group
dd....dd: Indicates whether to use the function that stops server startup when a connection to a shared resource is lost.
neck: Use the function that stops server startup when a connection to a shared resource is lost.
No display: Do not use the function that stops server startup when a connection to a shared resource is lost.
ee....ee: Option when a volume group goes online
ff....ff: Special file name of file system
gg....gg: Name of directory at mounting destination
hh....hh: Option used with the OS's mount command
S:
Continues processing.
KAMN213-I (S)
Own host name : aa....aa
Own servers Pair servers
Alias Status pri Status pri Host name
bb....bb cc....cc dd....dd ee....ee ff....ff gg....gg
This is the server status list that is output when the multi-standby function is being used and the server priority is
displayed.
32
2. Messages from KAMN000 to KAMN999
aa....aa: Name of local system host
bb....bb: Server alias name
cc....cc: Status of local system server
dd....dd: Priority of local system server (from 1 to 4 digits)
ee....ee: Status of paired system server
ff....ff: Priority of the paired system server (from 1 to 4 digits)
gg....gg: Host name of paired system
S:
Continues processing.
KAMN213-I (S)
Own host name : aa....aa
Alias Patrol time
bb....bb cc....cc
This is the server status list that is output when server failure monitoring time is displayed.
aa....aa: Name of local system host
bb....bb: Server alias name
cc....cc: Server failure monitoring time (from 1 to 3 digits)
S:
Continues processing.
KAMN214-I (S)
Usage:monswap alias
monswap -g group
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the planned hotstandby command (monswap) is incorrect.
S:
Continues processing.
KAMN215-E (E)
Online server:aa....aa is not processing. Command(bb....bb) cannot be executed.
A command was executed, but the specified server is not an active server or its startup processing is not complete.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Check the server alias name and active server status, and then re-execute the command.
KAMN216-E (E)
Standby server:aa....aa that Hotstandby can be able does not exist.
Command(monswap) cannot be executed.
A planned hot-standby command (monswap) was executed, but no standby server exists that is able to perform a hot
standby for the specified server. Another possibility is that no standby server is in standby-complete status.
aa....aa: Server alias name
S:
Stops command processing.
33
2. Messages from KAMN000 to KAMN999
O:
Check the server alias name and the standby server status, and then re-execute the command.
KAMN217-I (S)
Online server:aa....aa was stopped by plan.
Standby server is done into Hotstandby.
Planned shutdown of an active server using the planned hot-standby command (monswap) has been completed. A hot
standby to a standby server will now be performed.
aa....aa: Server alias name
S:
Continues processing.
KAMN219-I (S)
Usage:monact alias
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the wait-state server
start command (monact) is incorrect.
S:
Continues processing.
KAMN220-E
Definition file:aa....aa, The definition of server that the name operand and the alias operand shows does not correspond with
the definition of the server of host(bb....bb).
Either the server alias name or program name does not match. The server terminates with an error.
aa....aa: Definition file name
bb....bb: Host name
S:
Terminates server startup processing.
O:
Correct the environment settings definition file, and then restart the server.
KAMN221-E (E)
Server:aa....aa is Online server.
Command(bb....bb) cannot be executed.
An attempt was made to execute a command, but the command cannot be executed because the specified server is
active.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Check the server alias name and the active server's startup type and status, and then re-execute the command.
KAMN222-I
Online server:aa....aa is already started.
The server indicated by the server alias name is already running.
aa....aa: Server alias name
S:
Terminates processing.
34
2. Messages from KAMN000 to KAMN999
O:
Correct the server environment definition, and then restart the server.
KAMN225-I
Server:aa....aa is started as Online server.
The server indicated by the server alias name has been started as the active server.
aa....aa: Server alias name
S:
Continues processing.
KAMN226-I
Server:aa....aa is started as Standby server.
Online server is on host(bb....bb).
The server indicated by the server alias name has been started as the standby server. The active server for this standby
server is on the host indicated by the host name.
aa....aa: Server alias name
bb....bb: Host name
S:
Continues processing.
KAMN227-E (E)
Standby server:aa....aa is not starting wait state.
Command(monact) cannot be executed.
The wait-state server start command (monact) has been executed, but the server indicated by the server alias name is
either starting up or in stand-by status.
aa....aa: Server alias name
S:
Stops command processing.
O:
Check the server alias name and standby server startup type and status, and then re-execute the command.
KAMN229-E
Definition file:aa....aa, The server specified the alias operand(bb....bb) stops an activation, because it already exists.
A server exists with a server alias name that is the same as the server alias name defined in the server environment
definition.
aa....aa: Definition file name
bb....bb: Server alias name
S:
Terminates processing.
O:
Correct the environment settings definition file, and then restart server.
KAMN230-E
bb....bb of server:aa....aa cannot be made ONLINE.
The device of the server indicated by the server alias name cannot be placed online.
aa....aa: Server alias name
bb....bb: Device name
35
2. Messages from KAMN000 to KAMN999
S:
Continues processing.
O:
Place the device online as needed.
KAMN232-E
bb....bb of server:aa....aa cannot be made STANDBY.
The device of the server indicated by the server alias name cannot be placed in standby state.
aa....aa: Server alias name
bb....bb: Device name
S:
Continues processing.
O:
Place the device in standby state if needed.
KAMN233-E
bb....bb of server:aa....aa cannot be connected.
A device on the server indicated by the server alias name cannot be connected. Processing continues without
connecting.
aa....aa: Server alias name
bb....bb: Device name
S:
Continues processing.
O:
Connect the device, if necessary.
Action:
Determine the cause of the error. If the device name is a file system name, consult the switching log acquired in
the /opt/hitachi/HAmon/spool/server-ID-name.fslog file to determine the cause of the error.
KAMN234-E
bb....bb of server:aa....aa cannot be disconnected.
A device on the server indicated by the server alias name cannot be disconnected. Processing continues with the
device connected.
aa....aa: Server alias name
bb....bb: Device name
S:
Continues processing.
O:
Disconnect the device, if necessary. It is possible that resources have been corrupted, particularly if a file system is
being used; be sure to disconnect the device if a file system is being used.
Action:
Determine the cause of the error. If the device name is a file system name, check the switching log acquired in
the /opt/hitachi/HAmon/spool/server-ID-name.fslog file. If the device name is a volume group
name, check the connection log acquired in the /opt/hitachi/HAmon/spool/volume-group-name.vglog
file.
KAMN235-I
The state of Server:aa....aa changed to the Hotstandby wait state.
36
2. Messages from KAMN000 to KAMN999
The standby server indicated by the server alias name was placed in hot-standby wait-state in order to check the status
of the LAN interface if a failure is detected in the active system.
aa....aa: Server alias name
S:
Continues processing.
KAMN236-I (S)
Standby server:aa....aa of starting wait state is started as Online server.
Forced-start processing of the standby server indicated by the server alias name has finished.
aa....aa: Server alias name
S:
Continues processing.
KAMN237-E
The processing about the server under aa....aa is stopped.
An error occurred in the processing of the server definition analysis. Processing will not be performed for the server
indicated by the program name.
aa....aa: Program name
S:
Terminates processing.
O:
If message KAMN601-W is output before this message, eliminate the cause of the system call error as indicated by
that message, and then restart the server. If message KAMN601-W is not output, execute the definition check
command (moncheck), check the error, correct the server environment definition, and then restart the server.
KAMN238-D
Standby server:aa....aa is starting wait state.
The active server has not started, so the standby server indicated by the server alias name becomes the active server in
a startup wait-state.
This message is output at set intervals to report status to the user.
aa....aa: Server alias name
S:
Continues processing.
O:
Start the intended active server, or execute the wait-state server start command (monact).
KAMN239-I
The bb....bb command was processed cc....cc times by device processing of server:aa....aa.
In device processing of the server indicated by the server alias name, the command indicated by the command name
was executed the number of times indicated by the execution count.
aa....aa: Server alias name
bb....bb: Command name
cc....cc: Execution count
S:
Continues processing.
Action:
If the command was not executed the required number of times, investigate the cause and place the device in the
necessary state.
37
2. Messages from KAMN000 to KAMN999
KAMN241-I
Server:aa....aa was completed as Standby server.
Startup of the standby server indicated by the server alias name has finished.
aa....aa: Server alias name
S:
Continues processing.
KAMN242-D (E+L)
After stopping abnormally, HAmonitor of an own host:aa....aa is a restart. Online server:bb....bb has the possibility that is
starting in other hosts. The initial state was changed to Standby server, and it was made a start wait state.
HA Monitor has restarted after terminating due to an error. Since the active server might have been started by a host
on another system, the startup type of the server indicated by the server alias name has been changed to a standby
server to place it in a wait-state.
aa....aa: Host name
bb....bb: Server alias name
S:
Continues processing.
O:
Determine the reason HA Monitor terminated abnormally, and either use the wait-state server start command
(monact) to make this server, currently in the active server startup wait-state, start as the active server, or make
HA Monitor terminate normally.
KAMN243-D (E+L)
There is a fail of system reset or the Server who stops abnormally in the own host:aa....aa. Online server:bb....bb has the
possibility that is starting in other hosts. The initial state was changed to Standby server, and it was made a start wait state.
The host of the current system cannot perform a system reset. Another possibility is that a server terminated
abnormally. Since the active server might have been started by a host on another system, the startup type of the server
indicated by the server alias name has been changed to a standby server to place it in an active server startup waitstate.
aa....aa: Host name
bb....bb: Server alias name
S:
Continues processing.
O:
Determine the reason the server terminated abnormally, and either use the wait-state server start command
(monact) to make this server, currently in the startup wait-state, start as the active server, or make HA Monitor
terminate normally.
KAMN244-D (E+L)
Own host:aa....aa had abnormality in communication with other hosts. Online server:bb....bb has the possibility that is starting
in other hosts. The initial state was changed to Standby server, and it was made a start wait state.
An error occurred during communication with a host on another system. Since the active server might have been
started by a host on another system, the startup type of the server indicated by the server alias name has been changed
to a standby server to place it in a wait-state.
aa....aa: Host name
bb....bb: Server alias name
S:
Continues processing.
38
2. Messages from KAMN000 to KAMN999
O:
Determine the cause of the communication error, and either use the wait-state server start command (monact) to
make this server, currently in the startup wait-state, start as the active server, or stop it with the wait-state server
stop command (mondeact).
KAMN245-E
Standby server:aa....aa is started in several.
Multiple instances of the standby server indicated by the server alias name are running.
aa....aa: Server alias name
S:
Terminates processing.
O:
Correct the server environment definition, and then restart the server.
KAMN246-W
It connected with HAmonitor of host:aa....aa.
The version of HAmonitor of each host is different.
HA Monitor on the host indicated by the host name was connected to, but it is running a different version of HA
Monitor than the host on the current system.
aa....aa: Host name
S:
Continues processing.
Action:
If you connected two different versions of HA Monitor, stop the HA Monitor of the wrong version, reinstall HA
Monitor of the correct version, and then restart it. There is no problem if you intentionally connected two different
versions of HA Monitor.
KAMN249-E (E+L)
The version of HAmonitor of host:aa....aa and own host is different.
Processing is stopped.
The HA Monitor versions on the host indicated by the host name and the host on the current system are different.
aa....aa: Host name
S:
Stops processing.
O:
Check the HA Monitor version of each host.
KAMN251-I
Server:aa....aa was completed as Online server.
Startup of the active server indicated by the server alias name has finished.
aa....aa: Server alias name
S:
Continues processing.
KAMN252-I
Server:aa....aa, Hotstandby was enabled.
The server on the other system is now able to perform a hot standby.
aa....aa: Server alias name
39
2. Messages from KAMN000 to KAMN999
S:
Continues processing.
KAMN253-E (E+L)
Online server:aa....aa duplicates in host:bb....bb. Make an Online server end immediately so that there is a fear of breaking a
resource used in the server.
The server indicated by the server alias name is running on a connected host. The resources the server is using might
be corrupted. Shut down the active server as soon as possible, and then check the status of the resources.
aa....aa: Server alias name
bb....bb: Host name
S:
Outputs this message once every 30 seconds until the active server is shut down.
O:
Shut down the active server, and then contact a system administrator.
Action:
Investigate the status of the resources that were used by the active server, check the resources, and then restart the
server.
KAMN254-I
Server:aa....aa restart completed as Online server.
The active server indicated by the server alias name has finished restarting.
aa....aa: Server alias name
S:
Continues processing.
KAMN255-D
Server:aa....aa was made a restart wait state.
The active server indicated by the server alias name has been placed in the restart wait-state.
aa....aa: Server alias name
S:
Continues processing.
O:
Start the active server. Alternatively, perform a planned hot standby of the active server currently in the restart
wait-state with the planned hot-standby command (monswap), or stop it with the wait-state server stop command
(mondeact).
KAMN256-I (S)
LAN adaptor status
Pair Interface Status
aa....aa bb....bb cc....cc
dd....dd ee....ee
This is the dual LAN adapter information that is output when the -l option is specified for the server and host status
display command (monshow).
aa....aa: Defined LAN adapter pair (lanX-lanY)
bb....bb: Name of LAN adapter to be used as the primary adapter
cc....cc: Operating status of the LAN adapter to be used as the primary adapter
dd....dd: Name of LAN adapter to be used as the secondary adapter
ee....ee: Operating status of the LAN adapter to be used as the secondary adapter
40
2. Messages from KAMN000 to KAMN999
The operating status of the LAN adapter displays the following information:
OK: The LAN adapter is normal.
NG: The LAN adapter is abnormal.
*: The LAN adapter is currently running as the primary adapter. The other LAN adapter for which * is not
displayed is on standby.
S:
Continues processing.
KAMN257-I
The stop request of the server:aa....aa was accepted.
Termination processing of the server indicated by the server alias name has started. Termination processing of all
corresponding standby servers has also started.
aa....aa: Server alias name
S:
Stops the active server and corresponding standby servers.
KAMN258-D
Online server:aa....aa is restart wait state.
The active server indicated by the server alias name is in the restart wait-state.
This message is output at set intervals to report status to the user.
aa....aa: Server alias name
S:
Continues processing.
O:
Start the active server. Alternatively, perform a planned hot standby of the active server currently in the restart
wait-state with the planned hot-standby command (monswap), or stop the server with the wait-state server stop
command (mondeact).
KAMN259-I
Server:aa....aa, Hotstandby was completed. Host:bb....bb
The server indicated by the server alias name has finished processing a hot standby of the host indicated by the host
name.
aa....aa: Server alias name
bb....bb: Host name
S:
Continues processing.
KAMN260-I
Patrol of server:aa....aa is started.
HA Monitor has started failure monitoring of the server indicated by the server alias name.
aa....aa: Server alias name
S:
Continues processing.
KAMN261-I
Patrol of server:aa....aa is ended.
HA Monitor has terminated failure monitoring of the server indicated by the server alias name.
aa....aa: Server alias name
41
2. Messages from KAMN000 to KAMN999
S:
Continues processing.
KAMN262-E
Slowdown of program:aa....aa was detected. The program is made to stop abnormally. Process ID:bb....bb.
Operation reports stopped coming in while monitoring the program indicated by the program alias name. This was
considered to be a slowdown and the program was terminated abnormally.
aa....aa: Program alias name
bb....bb: Process ID of program that stopped reporting.
S:
Restarts the program based on the settings. If the preset number of restarts is exceeded, the active server is
switched if it is in a state that allows hot standbys.
O:
Contact a system administrator.
Action:
Eliminate the cause of the program slowdown.
KAMN263-E
Program:aa....aa stopped abnormally. Process ID:bb....bb.
An error occurred in the program indicated by the program alias name.
aa....aa: Program alias name
bb....bb: Process ID of program that terminated with an error.
S:
Restarts the program based on the settings. If the preset number of restarts is exceeded, the active server is
switched if it is in a state that allows hot standbys.
O:
Contact a system administrator.
Action:
Eliminate the cause of the error that caused the program to terminate.
KAMN264-I
Program:aa....aa is restarted.
The program indicated by the program alias name has restarted.
aa....aa: Program alias name
S:
Continues processing.
KAMN265-W (E+L)
After stopping abnormally, HAmonitor of an own host:aa....aa is a restart.
HA Monitor has restarted on the current host after terminating in error.
aa....aa: Host name
S:
Continues processing.
O:
If the host does not automatically restart after HA Monitor terminates abnormally, manually restart the host. It is
possible that resources have been corrupted, particularly if a file system is being used. Be sure to restart all devices
if a file system is being used.
42
2. Messages from KAMN000 to KAMN999
KAMN266-I
Server:aa....aa, Hotstandby is started. Because an error of program was detected.
A server hot standby was executed because an error was detected in the program managed by the server indicated by
the server alias name.
aa....aa: Server alias name
S:
Continues processing.
KAMN267-W
Slowdown of program: aa....aa was detected. Patrol of Online server:bb....bb is continued, because there is not Standby
server. Process ID:cc....cc.
Operation reports stopped coming in while monitoring the program indicated by the program alias name. This was
considered to be a slowdown, but processing could not be switched to the standby server because the server indicated
by the server alias name was not running, so the current server will continue status monitoring.
aa....aa: Program alias name
bb....bb: Server alias name
cc....cc: Process ID of program that slowed down.
S:
Continues status monitoring. Performs a hot standby after the standby server corresponding to the active server
completes start-up processing.
O:
If the standby server corresponding to the active server is not running on the host of another system, start the
standby server.
Action:
After the active server finishes performing a hot standby, investigate the cause of the program slowdown.
KAMN268-E
An error of program:aa....aa was detected, but server:bb....bb exchange of system will not start because Standby server is not
ready. Process ID:cc....cc.
An error was detected in the program indicated by the program alias name, but the hot standby was stopped because
the standby server, indicated by the server alias name, is not running.
aa....aa: Program alias name
bb....bb: Server alias name
cc....cc: Process ID of program that terminated with an error.
S:
Continues processing.
O:
Start the standby server, and then manually perform a planned hot standby, if necessary. Alternatively, restart the
active server or the program that failed.
KAMN269-E (E)
Program:aa....aa does not exist in system.
The program specified by the command option is not running.
aa....aa: Program alias name
S:
Terminates processing.
O:
Check the program alias name, and then re-execute the command.
43
2. Messages from KAMN000 to KAMN999
KAMN270-W
Patrol command of server:aa....aa execution was failed. Patrol of server will not be executed.
The server cannot be monitored because the server monitoring command specified in the patrolcommand operand
in the server environment definition did not execute.
aa....aa: Server alias name
S:
Continues processing.
O:
Check whether the specified server monitoring command can be executed.
KAMN271-I
Patrol command of server:aa....aa is started.
Startup processing of the monitor-mode server monitoring command terminated normally.
aa....aa: Server alias name
S:
Continues processing.
KAMN272-E
An error of Online server:aa....aa was detected by patrol command. A planned exchange of system is started.
A planned hot standby is being executed because a server error was detected by the monitor-mode server monitoring
command.
aa....aa: Server alias name
S:
Performs a hot standby to a standby server.
O:
Contact a system administrator.
Action:
Determine the cause of the server error, and then restart the server.
KAMN273-E (E+L)
Server aa....aa is terminated with an error.
reason:bb....bb details:cc....cc
If yes was specified in the waitserv_exec operand of the server environment definition, either the monitor-mode
server start command (monbegin) failed, or the server failed to restart after it terminated abnormally.
aa....aa: Program name
bb....bb: Cause code (unique to HA Monitor, 1 or 2 digits)
Cause code
Meaning
1
System call error when the server start command is executed
2
Server start command error
3
System call error when the server stop command is executed
4
Server stop command error
cc....cc: Detail code
Cause code
If 1 or 3
44
Detail code
errno value
Meaning
Displays the value of the system call errno.
2. Messages from KAMN000 to KAMN999
Cause code
If 2 or 4
Detail code
Meaning
126
Program file does not have permission to execute.
127
The program itself does not exist.
Other value
Displays the value returned by the server start command or server
stop command.
S:
Depending on the environment settings and other circumstances, the active server undergoes system switchover,
restarts, or stops.
O:
Contact a system administrator.
Action:
Take one of the actions listed below, as indicated by the cause code. Restart the active server as needed.
Cause code
Corrective action
1 or 3
Eliminate the cause of the error for the system call.
2 or 4
Check whether the server start command or server stop command can be executed. If it can,
eliminate the cause of the error corresponding to the cause code that is output. If it cannot, correct
the command.
KAMN274-I
Server aa....aa is normally restarted.
The program restarted because a program error was detected and the server environment definition
serveexec_retry operand was specified.
aa....aa: Program name
S:
Continues processing.
KAMN275-E
An error of Online server:aa....aa was detected by patrol command, Server is now restarting.
The program will restart because a program error was detected and the server environment definition
serveexec_retry operand was specified.
aa....aa: Server alias name
S:
Continues processing.
O:
Eliminate the cause of the server's abnormal termination.
KAMN276-E
An error of Online server:aa....aa was detected by patrol command, but exchange of system will not start because Standby
server is not ready.
A hot standby was attempted due to the occurrence of one of the events described below, but hot standby was stopped
because there was no standby server:
• A program error was detected when 0 was specified for the server environment definition servexec_retry
operand.
• A program error was detected when retry was specified for the server environment definition switch_error
operand.
45
2. Messages from KAMN000 to KAMN999
• The program restart limit was reached when a value other than 0 was specified for the server environment
definition servexec_retry operand.
aa....aa: Server alias name
S:
Depending on the environment settings and other circumstances, the active server either restarts or stops.
O:
If the active server is not currently performing operations, start the standby server, and perform a planned hot
standby manually, if necessary.
If the active server has not started, restart it.
KAMN280-I
Online server:aa....aa was terminated normally.
The active server indicated by the server alias name terminated normally.
aa....aa: Server alias name
S:
Continues processing.
KAMN281-I
Standby server:aa....aa was terminated normally.
The standby server indicated by the server alias name terminated normally.
aa....aa: Server alias name
S:
Continues processing.
KAMN283-W
Program:aa....aa, the patrol method is not corresponding to the definition. Signal:bb....bb Process ID:cc....cc.
Operation reports will not be monitored because the UAP indicated by the program alias name does not define the
monitoring method in the same way as the hamon_patrolstart function for one of the following reasons:
• A nonzero value was specified as the signum argument for the hamon_patrolstart function (which
specifies monitoring of operation reports), but the patrol operand was not specified in the monitor-mode
program environment definition.
• 0 was specified as the signum argument for the hamon_patrolstart function (which specifies process
monitoring), but the patrol operand was specified in the monitor-mode program environment definition.
aa....aa: Program alias name
bb....bb: signum value specified in the hamon_patrolstart function
cc....cc: Process ID of the UAP that invoked the hamon_patrolstart function
S:
Monitors the UAP process. Does not monitor UAP operation reports.
O:
Contact a system administrator.
Action:
If monitoring of UAP operation reports is necessary, specify tan appropriate signum value in the
hamon_patrolstart function, and then restart the process. Alternatively, specify the patrol operand in the
monitor-mode program environment definition, and then restart the UAP.
KAMN284-I
Patrol of program:aa....aa is started. Signal:bb....bb Process ID:cc....cc.
HA Monitor will start monitoring the program indicated by the program alias name.
46
2. Messages from KAMN000 to KAMN999
aa....aa: Program alias name
bb....bb: signum value specified in the hamon_patrolstart function
cc....cc: Process ID of the program that HA Monitor will start monitoring
S:
Continues processing.
KAMN285-E
Program:aa....aa is terminated with an error.
Reason:bb....bb Details:cc....cc
Start or restart of the program indicated by the program alias name has failed.
aa....aa: Program alias name
bb....bb: Cause code (unique to HA Monitor, 1 or 2 digits)
cc....cc: Detail code
The detail and cause codes are defined as follows:
Cause code
1
2
Detail code
Meaning
1
The program's restart command did not finish before the timeout period
elapsed.
2
The UAP did not invoke the hamon_patrolstart function before the
timeout period elapsed.
3
The program's restart command did not finish before the timeout period
elapsed, and the UAP did not invoke the hamon_patrolstart
function.
126
The file specified in the restartcommand operand does not have
permission to execute the command.
127
The file specified in the restartcommand operand does not exist.
256
A system call error occurred when the program's restart command was
executed.
Other value
Displays the value returned by the program's restart command.
S:
If the cause code is 1, stops execution of the server start command and begins execution a restarts according to the
settings. If the preset number of restarts is exceeded, a hot standby is executed if the active server is in a state that
allows hot standbys.
If the cause code is 2, stops processing.
O:
Contact a system administrator.
Action:
Take one of the following actions, as indicated by the cause code.
Cause code
Corrective action
1
Determine the reason the program's restart command did not return a value or the reason the program
did not invoke the hamon_patrolstart function, and then eliminate the cause. Manually perform
a planned hot standby, if necessary. Alternatively, restart the active server or the program that failed.
2
Check whether the program restart command can be executed. If it can, eliminate the cause of the
error for the cause code that is output. If it cannot, correct the command. Manually perform a planned
hot standby, if necessary. Alternatively, restart the active server or the program that failed.
KAMN286-I
Patrol of host:aa....aa is started.
47
2. Messages from KAMN000 to KAMN999
Monitoring of the host indicated by the host name has started.
aa....aa: Host name
S:
Continues processing.
KAMN287-I
Patrol of host:aa....aa is ended.
Monitoring of the host indicated by the host name has ended.
aa....aa: Host name
S:
Continues processing.
KAMN288-W
The online server:aa....aa is not in a hot standby state.
A system switchover cannot occur because the active server indicated by the server alias name is not on hot standby.
This message is intended as a status notification for the user and is output at a given interval.
aa....aa: Server alias name
S:
Continues processing.
O:
Start the standby server.
KAMN290-I
Online server:aa....aa was stopped by plan.
The active server indicated by the server alias name stopped as planned.
aa....aa: Server alias name
S:
Continues processing.
KAMN291-W
Disconnection of the volume group:bb....bb of the server:aa....aa was skipped.
Disconnection of the volume group of the server indicated by the server alias name was skipped. The system
continues processing while maintaining the connection.
aa....aa: Server alias name
bb....bb: Volume group name
S:
Continues processing.
O:
Disconnect the device if necessary.
Action:
Eliminate the cause of the error for the system call indicated in the message KAMN234-E, which is output before
this message. If the device name is a file system name, consult the switching log acquired in the /opt/
hitachi/HAmon/spool/server-ID-name.fslog file to determine the cause of the error. If the device name
is a volume group name, consult the connection log acquired in the /opt/hitachi/HAmon/spool/volumegroup-name.vglog file to determine the cause of the error.
KAMN292-E
Processing of a start command of server:aa....aa carried out the timeout.
48
2. Messages from KAMN000 to KAMN999
The start command on the server indicated by the server alias name has timed out. The server start command has
stopped and the server startup failed.
aa....aa: Server alias name
S:
Stops processing.
O:
Eliminate the reason the server's start command did not finish, and then restart the server.
KAMN293-E
Processing of a end command of server:aa....aa carried out the timeout.
The stop command on the server indicated by the server alias name has timed out. The server's stop command and the
monitoring UAP have stopped, and the process of terminating the server will resume.
aa....aa: Server alias name
S:
Continues processing.
O:
Eliminate the reason the server's stop command did not finish.
KAMN294-I
Patrol of program:aa....aa is ended. Process ID:bb....bb.
HA Monitor will stop monitoring the program indicated by the program alias name.
aa....aa: Program alias name
bb....bb: Process ID of the program that HA Monitor will stop monitoring
S:
Continues processing.
KAMN295-I
Program:aa....aa is abnormally. Server:bb....bb is restarted.
An error was detected in the program indicated by the program alias name. The server indicated by the server alias
name will now restart because the restartcommand operand of the monitor-mode program environment definition
has not been specified.
aa....aa: Program alias name
bb....bb: Server alias name
S:
Continues processing.
KAMN296-I
An attempt was made to start server:aa....aa as an online server, but startup was not successful and is now being retried.
(details code:bb....bb)
Startup of the server indicated by the server alias name is being retried.
aa....aa: Server alias name
bb....bb: Detail code
Detail code
Meaning
RESOURCE
Startup of the server is being retried because an attempt to connect to a shared resource failed.
SERVER
Startup of the server is being retried because an attempt to start it failed.
S:
Continues processing.
49
2. Messages from KAMN000 to KAMN999
KAMN298-I
The processing to stop the server:aa....aa is complete.
The server indicated by the server alias name was successfully stopped.
aa....aa: Server alias name
S:
Continues processing.
KAMN299-I
Contact of a halt was received from host:aa....aa. Details:bb....bb
A stop message was received from the host indicated by the host name. The stopped host will now be connected to
and a hot standby performed to a server in the hot-standby wait-state.
aa....aa: Host name
bb...bb: Detail code indicating what caused the host to stop
Detail code
Meaning
29
Power was cut off (host power supply was cut off)
31
Dump processing occurred (host is processing a dump)
S:
Continues processing.
50
2. Messages from KAMN000 to KAMN999
2.4 Messages from KAMN300 to KAMN399
KAMN300-E
Online server:aa....aa stopped abnormally.
A failure has occurred in the active server indicated by the server alias name.
aa....aa: Server alias name
S:
Depending on the environment settings and other circumstances, the active server undergoes system switchover,
restarts, or stops.
O:
Contact a system administrator.
Action:
Investigate the cause of the error and eliminate it. If the active server is stopped, restart it.
KAMN301-E
Slowdown of Online server:aa....aa was detected.
The server is made to stop abnormally.
Operation reports stopped being received during status monitoring of the active server indicated by the server alias
name. This was considered to be a slowdown and the server was forced to terminate, resulting in an error.
aa....aa: Server alias name
S:
Depending on the environment settings and other circumstances, the active server undergoes system switchover,
restarts, or stops.
O:
Contact a system administrator.
Action:
Investigate the cause of server slowdown and eliminate it. If the active server is stopped, restart it.
KAMN302-W
While server:aa....aa abnormal end processing, a device cannot be processed.
A device error occurred because the server indicated by the server alias name terminated abnormally.
aa....aa: Server alias name
S:
Continues processing.
Action:
If a system switchover has not occurred, see Handling shared resource disconnection errors in the manual HA
Monitor Cluster Software (for Linux(R) (x86) systems), and take the corrective action described there.
KAMN303-E
Following an abnormal end of an Online server:aa....aa, the HAmonitor is made to end abnormally.
HA Monitor was forcibly terminated because the server indicated by the server alias name terminated abnormally.
This message is output by the host's pairdown function.
aa....aa: Server alias name
S:
HA Monitor is forcibly terminated, resulting in an error. The host executes a system reset from HA Monitor on
another host. The message KAMN300-E or KAMN301-E is output before this message.
51
2. Messages from KAMN000 to KAMN999
O:
Contact a system administrator.
Action:
Determine the reason the KAMN300-E or KAMN301-E message was output, and then restart the host.
KAMN304-E
Online server:bb....bb of host(aa....aa) stopped abnormally.
An active server on the host indicated by the host name has terminated abnormally.
aa....aa: Host name
bb....bb: Server alias name
S:
If the active server is able to perform a hot standby, a hot standby to a standby server is performed. If the active
host is unable to perform a hot standby, the standby server on the local host terminates abnormally (or fails to
start).
O:
Determine why the active server on the host indicated by the host name terminated abnormally.
KAMN305-E
Online server:aa....aa cannot start.
The active server indicated by the server alias name encountered an error during startup processing. Startup processing
was terminated.
aa....aa: Server alias name
S:
Depending on the environment settings and other circumstances, the active server either restarts or stops.
O:
Contact a system administrator.
Action:
Investigate the cause of the error and eliminate it. If the active server is stopped, restart it.
KAMN306-E
Standby server:aa....aa cannot start.
The standby server indicated by the server alias name encountered an error during startup processing. Startup
processing was terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Determine the cause of the failure, and then restart the server.
KAMN307-E
Standby server:aa....aa stopped abnormally.
The standby server indicated by the server alias name terminated abnormally.
aa....aa: Server alias name
S:
Terminates processing.
52
2. Messages from KAMN000 to KAMN999
O:
Contact a system administrator.
Action:
Determine the cause of the failure, and then restart the server.
KAMN308-E
Standby server:bb....bb of host(aa....aa) stopped abnormally.
The standby server on the host indicated by the host name terminated abnormally.
aa....aa: Host name
bb....bb: Server alias name
S:
Terminates processing.
O:
Determine why the standby server on the host indicated by the host name terminated abnormally.
KAMN309-W
Slowdown of Online server:aa....aa was detected. Patrol is continued according to the definition of the HAmonitor.
Operation reports stopped being received during status monitoring of the active server indicated by the server alias
name. This was considered to be a slowdown and status monitoring was resumed because manual was specified in
the switchtype operand of the server environment definition.
aa....aa: Server alias name
S:
Continues processing.
O:
Perform a planned hot standby with the planned hot-standby command (monswap). Determine the cause of the
slowdown after the planned hot standby, and then restart the server.
KAMN310-I
Server:aa....aa, Hotstandby is started.
A hot standby of the server indicated by the server alias name has started.
aa....aa: Server alias name
S:
Continues processing.
KAMN311-I
Server:aa....aa, Hotstandby was completed.
Processing of a hot standby of the server indicated by the server alias name finished successfully.
aa....aa: Server alias name
S:
Continues processing.
KAMN312-E
Server:aa....aa, Hotstandby is failed.
A hot standby of the server indicated by the server alias name could not be performed.
aa....aa: Server alias name
S:
Depending on the environment settings and other circumstances, the active server either restarts or stops.
53
2. Messages from KAMN000 to KAMN999
O:
Contact a system administrator.
Action:
Investigate the cause of the error and eliminate it. If the active server is stopped, restart it.
KAMN313-E
Server:aa....aa, Hotstandby cannot be done, because Standby server does not exist.
A hot standby cannot be performed because the standby server corresponding to the server indicated by the server
alias name does not exist.
aa....aa: Server alias name
S:
Terminates processing.
O:
Restart the active server.
KAMN314-E
While Hotstandby processing of server:aa....aa, a device cannot be processed.
A device error occurred during hot standby processing for the server indicated by the server alias name. The hot
standby could not be performed.
aa....aa: Server alias name
S:
Continues processing.
O:
Contact a system administrator. After eliminating the failure, restart the server.
Action:
Eliminate the source of the system call error as indicated by message KAMN601-W, which is output before this
message.
KAMN315-E
Online server:aa....aa is the limit of a restart.
The restart limit was reached for an active server, indicated by the server alias name, in the restart wait state, or for a
server for which startup is being retried.
aa....aa: Server alias name
S:
If the server is in the restart wait state, a hot standby to a standby server is performed. The message KAMN319-I
is output before this message.
If startup is being retried for the server, the server is stopped. In this case, the message KAMN296-I is output
before this message.
O:
Contact a system administrator. Eliminate the cause of the error, and then restart the server.
Action:
Investigate the cause of the error based on one of the messages listed below, whichever is output before this
message, and eliminate the cause of the error. If the server mode is being used to start the server, investigate the
cause of the error on the server side.
Server startup method
Server status
Server mode
Restart wait state
54
KAMN300-E
Monitor mode
--
2. Messages from KAMN000 to KAMN999
Server startup method
Server status
Server mode
Startup being
retried
KAMN300-E
Monitor mode
• Connection to a shared resource failed.
KAMN498-E
• Execution of the server startup command failed.
KAMN273-E
• An error was detected by the server monitoring command.
KAMN276-E
KAMN300-E
Legend:
--: No message is output.
KAMN316-E
Online server:bb....bb of host(aa....aa) is the limit of a restart. Standby server was made a start wait state.
The restart limit for the active server on the host indicated by the host name has been reached. The standby server was
placed into the active server start wait-state because manual was specified in the switchtype operand of the
server environment definition.
aa....aa: Host name
bb....bb: Server alias name
S:
Places the standby server into the active server start wait-state.
O:
Determine and eliminate the cause of the active server failure, and then restart the server. Alternatively, restart it as
the active server using the wait-state server start command (monact), or stop it using the wait-state server stop
command (mondeact).
KAMN317-W
It is a memory shortage. Restart patrol of the Online server(aa....aa) cannot be done.
A memory shortage developed during restart monitoring of the active server indicated by the server alias name.
aa....aa: Server alias name
S:
Continues processing.
O:
Determine the cause of the error based on the KAMN601-W message output before this message. If the active
server has not restarted, restart it. Alternatively, perform a planned hot standby of the active server in the restart
wait-state using the planned hot-standby command (monswap), or stop it using the wait-state server stop
command (mondeact).
KAMN318-I
Online server:aa....aa of a restart wait state was stopped by force.
The active server in the restart wait-state, indicated by the server alias name, was forcibly stopped.
aa....aa: Server alias name
S:
Continues processing.
KAMN319-I
Online server:bb....bb of host(aa....aa) became a restart wait state.
The active server on the host indicated by the host name has been placed into the restart wait-state.
55
2. Messages from KAMN000 to KAMN999
aa....aa: Host name
bb....bb: Server alias name
S:
Continues processing.
KAMN320-E (E+L)
The number of executing process exceeded upper limit.
Command(aa....aa) cannot be executed.
Command processing cannot be executed because a new process cannot be initiated.
aa....aa: Command name
S:
Stops command processing.
O:
Wait until fewer processes are executing, and then re-execute the command.
KAMN321-I
Standby server:aa....aa does not exist in system.
It is changed to abnormally termination processing of Standby server.
The standby server indicated by the server alias name does not exist. Abnormal termination processing is performed
for the standby server.
aa....aa: Server alias name
S:
Continues processing.
O:
Determine the reason the standby server terminated.
KAMN322-E (E)
Server:aa....aa does not exist in system.
The server specified in the command option is not running.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check the server alias name, and then re-execute the command.
KAMN323-E (E)
Server:aa....aa, an error occurred on communication with it. Command(bb....bb) cannot be executed.
An error occurred during communication with the server that is processing the command indicated by the command
name. Command processing was terminated.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Re-execute the command. If you receive the message again, contact a system administrator.
Action:
Determine the cause of the error based on the error message that was output before this message.
56
2. Messages from KAMN000 to KAMN999
KAMN324-W (E)
Standby server:aa....aa does not exist in system. Command(bb....bb) processing is continued.
The standby server does not exist. Command processing continues.
aa....aa: Server alias name
bb....bb: Command name
S:
Continues command processing.
Action:
Investigate why the applicable standby server does not exist.
KAMN325-I (S)
Usage:monshow -c
monshow [alias]
monshow -d [alias]
monshow -g [group]
monshow -r
monshow -p [alias]
monshow -t [alias]
monshow -u [alias]
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the server and host
status display command (monshow) is incorrect.
S:
Continues processing.
KAMN326-I (S)
Usage:monsbystp alias
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the standby server
termination command (monsbystp) is incorrect.
S:
Continues processing.
KAMN327-E (E)
The option that cannot be specified in command(aa....aa) is specified.
An option was specified that cannot be specified in the command indicated by the command name.
aa....aa: Command name
S:
Stops command processing.
O:
Check the specified option, and then re-execute the HA Monitor command.
KAMN328-E (E)
Server:aa....aa is Standby server. Command(bb....bb) cannot be executed.
A command could not be accepted because the specified server is currently a standby server.
aa....aa: Server alias name
bb....bb: Command name
57
2. Messages from KAMN000 to KAMN999
S:
Stops command processing.
O:
Execute the HA Monitor command on an active server.
KAMN329-E (E)
Standby server:aa....aa is not on standby. Command(bb....bb) cannot be executed.
A command could not be accepted because the standby server specified by the standby server termination command
(monsbystp) is not in the standby complete state.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Once the standby server is in the standby complete state, execute the standby server termination command
(monsbystp).
KAMN330-E (E)
Online server:aa....aa was stopped by plan. Because Standby server does not exist, Hotstandby cannot be done.
A hot standby cannot be performed after a planned stop of the server indicated by the server alias name was performed
because the standby server does not exist.
If the multi-standby function is being used, this message is output even if the existence of the standby server could not
be confirmed due to a communications error. In this case, if HA Monitor and a standby server on a remote host are
operating normally, the system is reset from that host and a hot standby performed.
aa....aa: Server alias name
S:
Terminates processing.
O:
Restart the active server. If the multi-standby function is being used and a communications failure caused this
error, there is no need to restart the active server if the hot standby is successful.
Action:
Determine the cause.
KAMN331-E
While processing server:aa....aa, system call(bb....bb) error occurred.
A system call error occurred while the server indicated by the server alias name was running.
aa....aa: Server alias name
bb....bb: System call name
S:
Continues processing.
O:
Contact a system administrator.
Action:
Eliminate the source of the system call error as indicated by message KAMN601-W, which is output before this
message.
KAMN332-E
Communication with server:aa....aa cannot be done.
58
2. Messages from KAMN000 to KAMN999
An error occurred during communication with the server indicated by the server alias name (transmission of a
response message).
aa....aa: Server alias name
S:
Continues processing.
O:
Determine the cause of the communication error based on the message that was output before this message, and
then eliminate that cause.
KAMN333-E
Online server:aa....aa does not in system.
The server indicated by the server alias name does not exist in this system.
aa....aa: Server alias name
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Determine the reason the active server is not running.
KAMN334-I
The server:aa....aa was forcibly canceled.
The wait-state server stop command (mondeact) was executed, and therefore the restarting of the active server
indicated by the server alias name, for which startup was being retried, was forcibly canceled.
aa....aa: Server alias name
S:
Continues processing.
KAMN335-I (S)
Connected host information
Host name Host address Patrol time
aa....aa bb....bb cc....cc
This is the header for the status list of connected hosts that is output by the server and host status display command
(monshow). The first line displays information for the current system (local host), while subsequent lines display
information for remote systems that HA Monitor is connected to (remote hosts).
aa....aa: Host name
bb....bb: Host address
cc....cc: System failure monitoring period
S:
Continues processing.
KAMN336-I (S)
Standby server:aa....aa of starting wait state was stopped by force.
A standby server in the start wait-state, as indicated by the server alias name, was forcibly stopped.
aa....aa: Server alias name
S:
Continues processing.
59
2. Messages from KAMN000 to KAMN999
KAMN337-E (E)
Standby server:aa....aa is not starting wait state.
Command(bb....bb) cannot be executed.
An attempt was made to execute the command indicated by the command name, but the command could not be
executed because the standby server indicated by the server alias name is not in the start wait-state.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Execute the command on a standby server that is in the start wait-state.
To stop a server that is in the start wait-state of a resource server, start or stop the resource server. Once the
resource server has finished startup or shutdown processing, re-execute the command.
KAMN338-I (S)
Online server:aa....aa of Hotstandby wait state was stopped by force.
The active server indicated by the server alias name was forcibly stopped.
aa....aa: Server alias name
S:
Continues processing.
KAMN339-E (E)
Online server:aa....aa is not Hotstandby wait state.
Command(bb....bb) cannot be executed.
An attempt was made to execute the HA Monitor command indicated by the command name, but the command could
not be executed because the active server indicated by the server alias name is not in the hot-standby wait-state.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Execute the command on an active server in the hot-standby wait-state.
KAMN340-E
Host:aa....aa down was detected.
alive messages stopped being received during status monitoring of the host indicated by the host name, so a
slowdown is considered to have occurred.
aa....aa: Host name
S:
Terminates host monitoring, and then executes host down processing. If an active server is running on the host
indicated by the host name, resets the system, and then performs a host standby.
O:
Contact a system administrator.
Action:
Determine the cause of the host slowdown, and then restart the host.
60
2. Messages from KAMN000 to KAMN999
KAMN341-W
Slowdown of Online server:aa....aa was detected.
Patrol is continued, because there is not Standby server.
Operation reports stopped being received during status monitoring of the active server aa....aa, so a slowdown is
considered to have occurred. However, no standby server is running, so status monitoring resumes.
aa....aa: Server alias name
S:
Resumes status monitoring. Performs a hot standby after the standby server corresponding to the active server
finishes starting up.
O:
If the standby server corresponding to the active server is not running on the host of a remote system, start the
standby server.
Action:
Determine the cause of the slowdown after the active server hot standby finishes, and then restart the server.
KAMN342-W
Statistical information file cannot be opened.
The statistical information file cannot be opened.
S:
Continues processing. Statistical information will not be acquire.
KAMN343-W
Statistical information file cannot be closed.
The statistical information file cannot be closed.
S:
Continues processing.
Action:
Investigate why the statistical information file cannot be closed.
KAMN344-I
Host:aa....aa is system reset.
The host resets the system because an error was detected on the host indicated by the host name.
aa....aa: Host name
S:
The host resets the system, and then the system resumes processing.
KAMN345-W
While processing Standby server:aa....aa, an error occurred on communication with host(bb....bb). When there is not Standby
server, it judges, and it continues processing.
Communications with the host indicated by the host name was lost while the server indicated by the server alias name
was processing. No standby server is considered to exist, so processing resumes.
aa....aa: Server alias name
bb....bb: Host name
S:
Continues processing.
O:
Determine the reason communication ceased, and the server status.
61
2. Messages from KAMN000 to KAMN999
KAMN346-W
While processing Standby server:aa....aa, an error occurred on communication with host(bb....bb). When there is not Online
server, it judges, and it continues processing.
Communications with the host indicated by the host name was lost while the server indicated by the server alias name
was processing. No active server is considered to exist, so processing resumes.
aa....aa: Server alias name
bb....bb: Host name
S:
Continues processing.
O:
Determine the reason communication ceased, and the server status.
KAMN347-E
Host:aa....aa, system reset is failed.
After an error was detected on the host indicated by the host name and a system reset was initiated, an error occurred
during reset processing. The message KAMN621-E or KAMN624-E is output before this message.
aa....aa: Host name
S:
Stops hot standby processing.
O:
Contact a system administrator.
Action:
Determine the reason the system could not reset based on the error details in the KAMN621-E or KAMN624-E
message.
KAMN348-I
A requirement of system reset was received from the HAmonitor of host:aa....aa.
A system reset request was received from the HA Monitor on the host indicated by the host name. This message is
output when the pairdown function is used and a device connected to a server cannot be disconnected.
aa....aa: Host name
S:
Continues processing.
KAMN350-E
While processing server:aa....aa, system call(bb....bb) error occurred.
A system call error occurred while the server indicated by the server alias name was running.
aa....aa: Server alias name
bb....bb: System call name
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Eliminate the source of the system call error as indicated by KAMN601-W, which is output before this message.
KAMN351-E
While processing Online server:aa....aa, an error occurred on communication with host(bb....bb).
62
2. Messages from KAMN000 to KAMN999
A communications error occurred between a host on a remote system and the active server.
aa....aa: Server alias name
bb....bb: Host name
S:
Terminates processing.
O:
Determine the cause of the communications error and the status of the standby server, and then terminate the
standby server, if necessary.
KAMN352-E
Online server was terminated in the activating of Standby server:aa....aa.
An attempt was made to communicate with a server on a remote host, but the server was either shutting down or had
already terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Determine the server status, and then restart the server, if necessary.
KAMN353-W
While processing Online server:aa....aa, an error occurred on communication with host(bb....bb). When there is not Standby
server, it judges, and it continues processing.
An error occurred while the server indicated by the server alias name was communicating with the host indicated by
the host name. No standby server was considered to exist on the host, so processing resumes.
aa....aa: Server alias name
bb....bb: Host name
S:
Continues processing.
O:
Determine the cause of the communications error and the status of the standby server, and then terminate the
standby server if one exists.
KAMN354-E
Online server:bb....bb of host (aa....aa) was terminated normally.
The standby server cannot start because the active server has terminated.
aa....aa: Host name
bb....bb: Server alias name
S:
Terminates processing.
O:
Determine the server status, and then restart the server, if necessary.
KAMN355-E
While processing server:aa....aa, a device cannot be processed.
An error occurred during an attempt to access a device that was connected to the server indicated by the server alias
name.
aa....aa: Server alias name
S:
Continues processing.
63
2. Messages from KAMN000 to KAMN999
O:
Disconnect the device.
KAMN356-E
Standby server:aa....aa cannot be done Hotstandby, because it is not on standby.
The planned hot-standby command (monswap) was executed on the active server, but the standby server indicated by
the server alias name was not in a state that allows a hot standby to be performed.
aa....aa: Server alias name
S:
Flags the standby server as a server that is not allowed to start.
O:
Start the active server.
KAMN358-I
Standby server:bb....bb of host (aa....aa) was terminated normally.
Processing of the standby server indicated by the server alias name on the host indicated by the host name has
terminated.
aa....aa: Host name
bb....bb: Server alias name
S:
Terminates processing.
KAMN359-E
The state of Online server(bb....bb) of host(aa....aa) is abnormal.
The active server on the host indicated by the host name is in an abnormal status.
aa....aa: Host name
bb....bb: Server alias name
S:
Terminates processing.
O:
Restart the standby server, if necessary.
KAMN360-I (S)
------------------Detailed Information--------------------aa....aa bb....bb
This is the header for the detailed server information list that is output by the server and host status display command
(monshow).
aa....aa: Message ID
bb....bb: Text of the message
S:
Continues processing.
KAMN361-I (S)
Online server:aa....aa of Hotstandby wait state is started.
The active server in a hot-standby wait-state, as indicated by the server alias name, has started.
aa....aa: Server alias name
S:
Continues processing.
64
2. Messages from KAMN000 to KAMN999
KAMN362-I
Standby server:aa....aa of starting wait state was stopped by force.
The standby server in a start wait-state, as indicated by the server alias name, was forcibly stopped.
aa....aa: Server alias name
S:
Continues processing.
KAMN363-I
Online server:aa....aa of Hotstandby wait state was stopped by force.
The active server in a hot-standby wait-state, as indicated by the server alias name, was forcibly stopped.
aa....aa: Server alias name
S:
Continues processing.
KAMN364-D (S+L)
Server:aa....aa is Hotstandby wait state, because system reset is failed.
The active server indicated by the server alias name cannot reset the system, so it is placed in the hot-standby waitstate.
aa....aa: Server alias name
S:
Continues processing.
O:
Start the active server in the hot-standby wait-state as the active server using the wait-state server start command
(monact), or stop it using the wait-state server stop command (mondeact).
KAMN368-D
Online server:aa....aa is system switchover wait state.
The active server indicated by the server alias name is in the hot-standby wait-state.
This message is output at set intervals to report status to the user.
aa....aa: Server alias name
S:
Continues processing.
O:
Start the server in the hot-standby wait-state as the active server using the wait-state server start command
(monact), or stop it using the wait-state server stop command (mondeact).
KAMN369-I
Host:aa....aa is abnormal. A contact was received from the HAmonitor of other host:bb....bb.
A message was received from a host on a remote system stating that it detected a failure in the host indicated by the
host name.
aa....aa: Host name
bb....bb: Remote host name
S:
Continues processing. Corrective action for the host that experienced the failure is implemented by the remote
host that detected the failure.
O:
If you are performing operations involving the host that experienced the failure, check the system status.
65
2. Messages from KAMN000 to KAMN999
KAMN370-E (E)
Online server:aa....aa is already started.
The active server indicated by the server alias name is already running.
aa....aa: Server alias name
S:
Stops command processing.
O:
Correct the server environment definition, and then restart the server.
KAMN371-I (S)
Server:aa....aa is started as Online server.
The server indicated by the server alias name has been started as the active server.
aa....aa: Server alias name
S:
Continues processing.
KAMN372-E (E)
Server:aa....aa is Standby server.
Command(bb....bb) cannot be executed.
An attempt was made to execute the HA Monitor command indicated by the command name, but the specified server
is a standby server; therefore, the command could not be executed.
aa....aa: Server alias name
bb....bb: Command name
S:
Terminates processing.
O:
Check the server alias name and the server's startup type and status, and then re-execute the command.
KAMN373-I (S)
Online server:aa....aa was terminated normally.
HA Monitor has started shutdown processing of the server indicated by the server alias name.
aa....aa: Server alias name
S:
Continues processing.
KAMN374-I (S)
Usage:aa....aa Alias
This message is output when a command's syntax is incorrect.
aa....aa: Command name
S:
Continues processing.
KAMN375-E (E)
Definition file:servers,The method of a definition of the alias(aa....aa) is incorrect. Command processing is stopped.
An error occurred during analysis of the server environment definition. Processing on the server corresponding to the
server alias name specified in the HA Monitor command has stopped.
aa....aa: Server alias name
66
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Correct the server environment definition, and then restart the server.
KAMN376-I (S)
Server:aa....aa is started.
Startup of the server indicated by the server alias name has begun.
aa....aa: Server alias name
S:
Continues processing.
KAMN377-E (E+L)
Errors occurred in the activating or ending of server:aa....aa. Processing is stopped. Cause:bb....bb Details:cc....cc
An error occurred in startup or shutdown processing for the server indicated by the server alias name. Processing for
the server has stopped. For more information about detail codes, see the documentation for the applicable OS.
aa....aa: Server alias name
bb....bb: Cause code (unique to HA Monitor, 1 or 2 digits)
Cause code
3
Meaning
Server stop request
The causes are as follows:
Invalid definition
If the one of the following messages is output before this message, see the description for that
message.
KAMN190-E, KAMN191-E, KAMN220-E, KAMN222-I, KAMN229-E, KAMN245-E, KAMN412-E,
KAMN413-E, KAMN964-E, KAMN970-E
If none of these messages have been output, one of the following applies:
• Startup was stopped because the startup was attempted for multiple resource servers in the same
group.
• Startup of a child server was stopped because a server in a different group was specified as its
parent server.
• Startup of a child server was stopped because its parent server definition contains an error that
stopped analysis.
• Startup was stopped because, even though use is specified for the program operand in the
server environment definition of the server indicated by the server alias name, none of the
programs associated with the server whose server alias name is specified in the server_alias
operand of the monitor-mode program environment definition are defined in the monitor-mode
program environment definition.
• Startup was stopped because one of the programs specified for the server whose server alias is
specified in the server_alias operand is specified more than once in the name or alias
operand.
• Startup was stopped because the value specified in the name or alias operand for the program
that specifies the server whose server alias name is specified in the server_alias operand is
the same as a program that is already running.
Other causes
If the one of the following messages is output before this message, see the description for that
message.
KAMN285-E, KAMN292-E, KAMN445-I, KAMN498-E, KAMN530-E, KAMN933-E, KAMN937-E
If none of these messages has been output, one of the following applies:
• The resource server startup was stopped because a child server terminated in error while the
resource server was starting up.
• The startup of a server in the middle of a grouped system switchover was stopped because another
server involved in the switchover terminated in error.
67
2. Messages from KAMN000 to KAMN999
Cause code
Meaning
• Server startup was stopped because it was starting up during a grouped system switchover.
• Server startup was stopped because an attempt was made to start a server from the same group
during a grouped system switchover.
• The active server of a remote system was stopped when an attempt was made to start it as a
standby server.
4
Restart request
5
System call error
cc....cc: Detail code (sets errno of system call; when 0, there is no detail code)
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Take one of the following actions, as indicated by the cause code:
Cause code
3
Corrective action
For a definition error, carefully review the HA Monitor definition, and then restart the server, if
necessary.
For other causes, check the server status, and then restart the server, if necessary.
4
Re-execute the command.
5
Eliminate the cause of the system call error, and then re-execute the command.
KAMN378-I (S)
Server:aa....aa is started as Standby server.
The server indicated by the server alias name has been started as the standby server.
aa....aa: Server alias name
S:
Continues processing.
KAMN379-E (E)
Server:aa....aa was not completed as Online server.
Termination processing cannot be performed because the server indicated by the server alias name has not completed
startup.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check the server status, and then re-execute the command.
KAMN380-I (S)
Standby server:aa....aa is started as Online server.
The standby server indicated by the server alias name has been started as the active server.
aa....aa: Server alias name
S:
Continues processing.
68
2. Messages from KAMN000 to KAMN999
KAMN381-E (E+L)
Server aa....aa processing is stopped.
An attempt was made to start the server indicated by the program name using the server start command, but the server
could not start.
aa....aa: Program name
S:
Terminates processing.
O:
Eliminate the reason why the server did not start.
KAMN382-I (S)
Server:aa....aa was completed as Online server.
Startup of the active server indicated by the server alias name has finished normally.
aa....aa: Server alias name
S:
Continues processing.
KAMN383-I (S)
Server:aa....aa was completed as Standby server.
Startup of the standby server indicated by the server alias name has finished normally.
aa....aa: Server alias name
S:
Continues processing.
KAMN384-E
Standby server cannot be started automatically.
Host:aa....aa, Server:bb....bb, Cause:cc....cc
The standby server did not automatically start.
aa....aa: Host name of the standby system on which the automatic start was attempted
bb....bb: Server alias name whose automatic start was attempted
cc....cc: Source code
Cause code
Meaning
TIME-OUT
No response from standby system host
MEMORY
Insufficient memory
SEND
Communications failure
SIMULATED
Failure of automatic start in standby system host
S:
Stops processing.
O:
Execute the server and host status display command (monshow), and then check the standby server status. If the
standby server is not in the startup state, execute the monitor-mode server start command (monbegin) from the
standby system.
KAMN385-W (E+L)
Server:aa....aa failed in starting. It is restarted.
69
2. Messages from KAMN000 to KAMN999
An attempt to start the server indicated by the server alias name has failed. The server has been restarted.
aa....aa: Server alias name
S:
Continues processing.
O:
Check whether the server restarted normally.
KAMN386-E (E)
Server:aa....aa is not a server start in the monbegin command. Command cannot be executed.
The command could not be executed because the server indicated by the server alias name is not the server started by
the monitor-mode server start command (monbegin).
aa....aa: Server alias name
S:
Stops processing.
O:
Check the server name, and then re-execute the command.
KAMN388-I (S)
Online server:aa....aa of a restart wait state was stopped by force.
The active server in the restart wait-state, as indicated by the server alias name, was forcibly stopped.
aa....aa: Server alias name
S:
Continues processing.
KAMN390-I (S)
Path status Display
device name host name status
aa....aa bb....bb cc....cc
This is the header for the status list of monitoring paths that is output by the monitoring path status display command
(monpath).
aa....aa: TCP/IP host name of the monitoring path
bb....bb: Error status of the remote host name or the monitoring path
cc....cc: Status of communication with the remote host
S:
Continues processing.
KAMN390-I (S)
Path status Display
device name host name host(IP_address) status
aa....aa bb....bb cc....cc(dd....dd) ee....ee
This is the header for the status list of monitoring paths that is output by the monitoring path status display command
(monpath -i).
aa....aa: TCP/IP host name of the monitoring path
bb....bb: Error status of the remote host name or the monitoring path
cc....cc: TCP/IP host name of the remote system monitoring path (shown for normal monitoring paths)
dd....dd: IP address of the remote system monitoring path (shown for normal monitoring paths)
ee....ee: Status of communication with the remote host
70
2. Messages from KAMN000 to KAMN999
S:
Continues processing.
KAMN391-I (S)
Usage: monpath [-i] [check_time]
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the monitoring path
status display command (monpath) is incorrect.
S:
Continues processing.
KAMN392-E (E)
Option value:bb....bb of the aa....aa command is improper.
The value specified for an option of a command is invalid.
aa....aa: Command name
bb....bb: Option value
S:
Stops command processing.
O:
Specify a valid option value, and then re-execute the command.
KAMN393-E (E)
Because the HAmonitor is checking a Patrol Path, monpath command cannot be accepted.
The monitoring path status display command (monpath) cannot be executed because a monpath command is
already executing or a monitoring path re-check is being executed with the pathpatrol_retry operand specified.
S:
Stops command processing.
O:
Wait 30 to 60 seconds, and the re-execute the command.
KAMN394-I
Devices cannot be disconnected in host : aa....aa.
A server device cannot be disconnected by the host indicated by the host name. A KAMN348-I message is output
following this message.
aa....aa: Host name
S:
Continues processing.
O:
Determine the reason that the device cannot be disconnected by the host indicated by the host name, and then
eliminate the cause of the failure.
KAMN395-I (S)
aa....aa Status Display
host name status
bb....bb cc....cc
Indicates the reset path status list that is output by reset path status display command (monrp).
aa....aa: Hardware used for system resets
Reset Path: Displayed when a reset path is specified for the system reset.
71
2. Messages from KAMN000 to KAMN999
bb....bb: Host name
cc....cc: Status of the reset path (if the physical partition reset function is being used, displays whether a physical
partition can be reset)
OK: Normal
NG: Abnormal
OK(Partition): Physical partition can be reset.
NG(Partition): Physical partition cannot be reset.
S:
Continues processing.
KAMN396-I (S)
Usage: monrp [host_name]
This message is output after message KAMN327-E or KAMN392-E when the syntax of the reset path status display
command (monrp) is incorrect.
S:
Continues processing.
KAMN397-E (E)
Host: aa....aa does not exist in system.
The host specified by the command is not running
aa....aa: Host name
S:
Stops command processing.
O:
Check the host name, and then re-execute the command.
KAMN398-E (E)
Because the HAmonitor is checking a Reset Path, monrp command cannot be accepted.
The reset path status display command (monrp) cannot be accepted either because a monrp command is already
executing, or because HA Monitor is doing a health check of the reset path.
S:
Stops command processing.
O:
Wait 30 to 60 seconds, and the re-execute the command.
KAMN399-E
Abnormality occurred in Reset Path. Other host:aa....aa
An error occurred in the reset path of the host indicated by the host name.
aa....aa: Host name
S:
Continues processing. However, if a system failure is detected while the reset path is in error, the system reset fails
and the system is placed in the hot-standby wait-state without the standby server being able to perform a system
switchover to the active server. (Message KAMN364-D is output.)
O:
Eliminate the cause of the error, and then execute the reset path status display command (monrp).
72
2. Messages from KAMN000 to KAMN999
2.5 Messages from KAMN400 to KAMN499
KAMN400-E
While HAmonitor activated, an error had occurred. Activation is stopped.
An unavoidable error occurred during HA Monitor startup. Another message indicating the error detail is output prior
to this message.
S:
Terminates processing.
O:
Take the corrective action described for the message that indicated the error details.
KAMN402-E
There are errors in definition file:sysdef. Start again in the correct definition file.
HA Monitor cannot start because there is an error in the HA Monitor environment settings.
S:
Terminates processing.
O:
Correct the definition error in the HA Monitor environment settings, and then restart the system.
KAMN404-I
A notification of hostdown was received from host : aa....aa. Name of down host:bb....bb
The system indicated by the notifying host name sent a notification that a failure was detected in the system indicated
by the failed host name.
aa....aa: Name of notifying host
bb....bb: Name of failed host
S:
Continues processing.
KAMN407-I
A system reset will now be performed for the partition because an attempt to perform a system reset of the host:aa....aa has
failed. Error details : bb....bb
A system reset will be performed on the physical partition because an attempt to perform a system reset on the host
indicated by the host name (logical partition) failed.
aa....aa: Host name
bb....bb: Detail code
Detail code
Meaning
RESET-ERR
A reset error occurred in the failure management processor.
CTRLPTH-DOWN
A control line was severed on the reset path.
LPAR-RSP-FAIL
An error occurred in a query to the affected host.
S:
Continues processing.
KAMN408-E
The process which send alive message is stopped abnormally. Error details : aa....aa
The daemon that sends alive messages has terminated abnormally.
73
2. Messages from KAMN000 to KAMN999
aa....aa: Internal error code
S:
Continues processing.
O:
Restart HA Monitor.
Action:
Contact maintenance personnel.
KAMN409-I
Sending errors occurred in Patrol Path:aa....aa.
Host:bb....bb
A system call error occurred during an attempt to transmit a message to the host indicated by the host name.
aa....aa: Failed monitoring path name
bb....bb: Host name
The host name is displayed as ---- if the error occurred during transmission of a message that is part of a multicast.
S:
Continues processing.
Action:
Eliminate the cause of the system call error as indicated by KAMN601-W, which is output before this message.
KAMN410-I
The specified number of suppress_reset operand or more hosts are confirmed to be processing. Name of down
host:aa....aa
The number of hosts currently active has been confirmed to meet or exceed the minimum number of active hosts.
aa....aa: Name of failed host
S:
Resets the system, and then performs a system switchover.
KAMN411-I
A system reset to the host:aa....aa has not been required or has failed.
A reset of the system indicated by the host name is not required, or the system reset has failed.
aa....aa: Name of failed host
S:
Continues processing.
KAMN412-E
The number of connected server exceeded upper limit.
The number of operating servers, or the number of operating grouped servers, has reached the HA Monitor system
limit. The startup request could not be completed.
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Rebuild the system so that the number of servers operating on the HA Monitor system does not exceed the limit.
74
2. Messages from KAMN000 to KAMN999
KAMN413-E
The number of connected program exceeded upper limit.
The number of executing programs has reached the HA Monitor system limit. The startup request could not be
completed.
S:
Stops server startup processing. If a program was started manually, terminates the program.
O:
Contact a system administrator.
Action:
Rebuild the system so that the number of programs executing on the HA Monitor system does not exceed the
limit.
KAMN414-E
The host address is already in use by another HA monitor that shares the reset path. host address : aa....aa, IP address :
bb....bb, details : cc....cc
The host address is the same as that of one of the following:
• HA Monitor indicated by the IP address
• HA Monitor that uses the failure management processor indicated by the IP address
• HA Monitor that uses the hot-standby feature indicated by the IP address
If there is duplication, the following phenomena occur and the database might be damaged by mounting of both hosts:
• When the error occurs in a host, an error also occurs in other unrelated hosts that have a hot standby configuration.
• When a host is restarted, an error also occurs in other unrelated hosts that have a hot standby configuration.
If the local system is running in a virtual environment based on VMware ESXi and the detail code is SVP/HRL, the
host address indicates the machine address.
aa....aa: Host address
bb....bb: IP address
cc....cc: Detail code
Detail code
Meaning
HA MONITOR
The host address is the same as that of the HA Monitor indicated by the IP address.
SVP/HRL
The host address or the machine address is the same as that of one of the following:
• HA Monitor that uses the failure management processor indicated by the IP address
• HA Monitor that uses the hot-standby feature indicated by the IP address
S:
Continues processing.
O:
Stop the local system or the HA Monitor indicated by the detail code, and then take one of the following steps:
• Separate the networks so that no messages are exchanged between hot-standby configurations.
• Assign different reset paths (including failure management processors) and port numbers used for monitoring
paths to each hot-standby configuration so that messages are not transferred between different hot-standby
configurations.
• Change the host addresses of all HA Monitors that share the network to unique values that are also unique
within each hot standby configuration.
If you take the second or third step above, restart the HA Monitors whose settings were changed.
Do not restart the OS until you restart the HA Monitors.
75
2. Messages from KAMN000 to KAMN999
KAMN415-W
The request of HAMON_UAPNAME:aa....aa is not accepted.
Reason:bb....bb. Process ID:cc....cc.
An invalid request was received by the program name indicated by HAMON_UAPNAME. The request is ignored. Note
that the specification for the HAMON_UAPNAME environment variable is a program name.
aa....aa: Program name
bb....bb: Cause code
Cause code
1
Meaning
Invalid program name
The causes are as follows:
Definition error
• The program name specified in the HAMON_UAPNAME environment variable is not specified
in the name operand of the monitor-mode program environment definition.
• The server specified in the server_alias operand of the monitor-mode program
environment definition is not running or is not defined in the server environment definition.
• nouse is specified in the program operand of the server environment definition of the
server specified in the server_alias definition of the monitor-mode program
environment definition.
Operation error
• After the server environment definition or monitor-mode program environment definition
were corrected, a UAP was started manually without restarting the server.
• A UAP was started manually without starting the server specified in the server_alias
operand of the monitor-mode program environment definition.
2
Timing for invoking an API is invalid
An API was invoked at an invalid time, generally as a result of a UAP being operated manually.
3
The hamon_patrolstart function was invoked multiple times
cc....cc: Requesting process ID
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Take one of the following actions, as indicated by the cause code:
Cause code
1
Corrective action
For a definition error, carefully review the definition, and then restart the server.
If the server did not restart after the definition was corrected, restart the server.
If a UAP was manually started without starting the server, start the server. To continue without
starting the server and without monitoring the UAP with HA Monitor, specify nouse as the
HAMON_API_PATROL environment variable, and then start the UAP.
2
Check the server and UAP status, and then start the UAP manually.
3
Check whether the hamon_patrolstart function has been invoked multiple times, and then
correct the UAP, if necessary.
KAMN420-I
Group:aa....aa of grouped exchange of systems are started.
A grouped system switchover involving the group indicated by the group name has started.
76
2. Messages from KAMN000 to KAMN999
aa....aa: Name of group to which grouped system switchover is performed
S:
Continues processing.
KAMN421-I
Server:aa....aa became a state of which a grouped exchange of system is possible in group:bb....bb.
The server indicated by the server alias name is now able to perform a grouped system switchover with the group
indicated by the group name.
aa....aa: Server alias name
bb....bb: Group name
S:
Continues processing.
KAMN423-E (E+L)
Because it is being grouped, Standby server:aa....aa of an own host cannot be exchanged of system.
The active system server terminated abnormally, but, because it is grouped, a grouped system switchover cannot be
performed.
aa....aa: Server alias name
S:
Waits in the standby server startup complete state.
O:
Either start the active server, or use the standby server termination command (monsbystp) to stop the standby
server. Alternatively, use the planned hot-standby command (monswap) with the -g option to force the server
group to perform a grouped system switchover.
KAMN424-W
Slowdown of Online server:aa....aa was detected. Because it is grouped, hotstandby cannot be done. Patrol is continued.
A slowdown was detected while monitoring the status of the active server indicated by the server alias name, but,
because it is grouped, a hot standby cannot be performed. Status monitoring continues.
aa....aa: Server alias name
S:
Continues server status monitoring. If a grouped system switchover of a server group has already been started,
performs a hot standby of all servers together.
O:
Determine the reason the server slowdown occurred.
KAMN426-E (E)
Group:aa....aa are not states that a grouped exchange of system can be done.
The group indicated by the group name is not in a state that allows grouped system switchover.
aa....aa: Group name
S:
Terminates processing.
O:
Execute the server and host status display command (monshow) with the -g option to check the group status, and
then re-execute the command with the correct group name.
KAMN427-I (S+L)
Standby server:aa....aa of a grouped exchange of systemwait state is started as Online server.
77
2. Messages from KAMN000 to KAMN999
A hot standby of a server in the grouped system switchover wait-state has started.
aa....aa: Server alias name
S:
Continues processing.
KAMN428-E (E)
Group:aa....aa does not exist in system.
The group indicated by the group name does not exist.
aa....aa: Group name
S:
Terminates processing.
O:
Check the group name, and then re-execute the command.
KAMN429-I (S)
A planned exchange of system is done for a group:aa....aa.
A planned hot standby involving the group indicated by the group name has started.
aa....aa: Group name
S:
Continues processing.
KAMN430-E
An error occurred in the processing of an exchange of system of group:aa....aa of the server:bb....bb. Confirm the state of the
server.
An error occurred during hot standby processing for the group indicated by the group name.
aa....aa: Group name
bb....bb: Server alias name
S:
Terminates processing.
O:
Check the server status using the server and host status display command (monshow). If the server is stopped,
restart it, and then re-execute the monshow command.
KAMN431-E (E+L)
Because it is grouped, a planned exchange of system cannot be done for the server:aa....aa.
A planned hot standby cannot be done for the server indicated by the server alias name because it is grouped.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check the server status using the server and host status display command (monshow), and then re-execute the
planned hot-standby command (monswap) specifying the -g option.
KAMN432-W
While processing Online server:aa....aa, an error occurred on communication with host(bb....bb).
An error occurred when the server indicated by the server alias name attempted to communicate with the host
indicated by the host name.
aa....aa: Server alias name
78
2. Messages from KAMN000 to KAMN999
bb....bb: Host name
S:
Continues processing.
O:
Determine the reason communications failed, and the server status.
KAMN433-W
Server:aa....aa does not exist in system.
The server specified in the command option is not running.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check the server alias name, and then re-execute the command.
KAMN434-W
Server:aa....aa is not a state that the bb....bb command can be executed. Command processing is stopped.
The server indicated by the server alias name is not in a state that allows the specified command to be executed.
Command processing has stopped.
aa....aa: Server alias name
bb....bb: Command name
S:
Terminates command processing.
O:
Check the server status, wait for it to enter a state that allows the specified command to be executed, and then reexecute the command.
KAMN435-W
Server:aa....aa, The cc....cc is defined in the bb....bb.
The same value is already specified for the indicated operand in the server environment definition of the server
indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Specified value
S:
Terminates command processing.
O:
Check whether the value that you were attempting to add was already defined in the server environment
definition, and then re-execute the HA Monitor command.
KAMN436-W
Server:aa....aa, The cc....cc is not defined in the bb....bb.
The specified value was never defined for the indicated operand in the server environment definition of the server
indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Specified value
79
2. Messages from KAMN000 to KAMN999
S:
Terminates command processing.
O:
Check whether the value you were attempting to delete was defined in the server environment definition, and then
re-execute the HA Monitor command.
KAMN437-W
When the cc....cc is defined to the bb....bb of Server:aa....aa, The number of the values has exceeded a maximum value.
An attempt to add the specified value to the corresponding operand in the server environment definition of the server
indicated by the server alias name has caused the maximum number of values that can be specified to be exceeded.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Specified value
S:
Terminates command processing.
O:
Carefully review the resource configuration to ensure the number of values specified does not exceed the
maximum limit.
KAMN438-W
The value:aa....aa, The method of a definition of the value is incorrect.
The indicated value was not specified correctly.
aa....aa: Specified value
S:
Terminates command processing.
O:
Re-execute the HA Monitor command correctly.
KAMN439-W
Because server:aa....aa is during command processing, Command(bb....bb) cannot be executed.
The specified command could not be executed because the server indicated by the server alias name is already
processing a command.
aa....aa: Server alias name
bb....bb: Command name
S:
Terminates command processing.
O:
After the currently executing command finishes processing, re-execute the command.
KAMN444-E
Online server:aa....aa is already started.Server:bb....bb cannot start.
The server indicated by the server alias name cannot start because the server indicated by the active server alias name
is already running. Start processing is terminated.
aa....aa: Active server alias name
bb....bb: Server alias name
S:
Terminates processing.
80
2. Messages from KAMN000 to KAMN999
O:
Either stop the active server, or perform a planned hot standby and restart the server, as necessary.
KAMN445-I
Server:bb....bb is terminated, because online server:aa....aa is started.
The server indicated by the server alias name was shut down because the active server indicated by the active server
alias name is starting.
aa....aa: Active server alias name
bb....bb: Server alias name
S:
Continues processing.
KAMN446-E (E)
Online server is already started. Server:aa....aa cannot start.
The server indicated by the server alias name could not start because an active server is already running. Startup
processing is terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Either stop the active server, or perform a planned hot standby and restart the server, as necessary.
KAMN447-W
The number of operating hosts is the number specified for the suppress_reset operand or fewer. (number of operating
hosts:aa....aa, number specified for the suppress_reset operand:bb....bb)
Because the number of active hosts is equal to or smaller than the minimum number of active hosts, the host indicated
by the host name is suppressing a reset to another system. If an error occurs in the active system, the active system
might be prevented from being reset and might be placed in the hot-standby wait-state.
aa....aa: Number of active hosts
bb....bb: Minimum number of active hosts
S:
Continues processing.
O:
If you do not want the active system to be placed in the hot-standby wait-state, increase the number of active hosts
to at least the minimum number of active hosts.
KAMN448-W (E+L)
Definition file:servers, Abnormalities occurred during processing of a aa....aa operand. Details:bb....bb
An error occurred during processing of the aa....aa operand of the server environment definition.
aa....aa: Operand name
bb....bb: Detail code (1 or 2 digits)
Detail code
Meaning
1
No value specified for operand.
2
Operand is missing.
S:
Continues processing.
81
2. Messages from KAMN000 to KAMN999
O:
Check the content of the operand specified in the server environment definition, and correct it, if necessary.
KAMN449-I
Server aa....aa, The specification value corresponding to cc....cc of a bb....bb operand was changed.
The value specified for the indicated operand in the server environment definition of the server indicated by the server
alias name has been changed.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Resource name
S:
Continues processing.
KAMN450-I (S)
Usage: mondevice -Q
mondevice alias -a device-type resource-name
mondevice alias -d device-type resource-name
mondevice alias -c device-type resource-name change-type attribute
This message is output after message KAMN021-E when the syntax of the command for dynamically changing a
server's shared resources (mondevice) is incorrect.
S:
Continues processing.
KAMN451-E (E)
Server:aa....aa is not a state that the bb....bb command can be executed. Command processing is stopped.
Command processing was terminated because the server indicated by the server alias name is not is a state that allows
this command to be executed.
aa....aa: Server alias name
bb....bb: Command name
S:
Terminates command processing.
O:
Check the server status, wait for it to enter a state that allows this command to be executed, and then re-execute
the command.
KAMN452-E (E)
Server:aa....aa, The cc....cc is defined in the bb....bb.
The same value is already specified for the indicated operand in the server environment definition of the server
indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Specified value
S:
Terminates command processing.
O:
Check whether the value you are attempting to add was already defined in the server environment definition, and
then re-execute the HA Monitor command.
82
2. Messages from KAMN000 to KAMN999
KAMN453-E (E)
Server:aa....aa, The cc....cc is not defined in the bb....bb.
The value specified for the indicated operand in the server environment definition of the server indicated by the server
alias name could not be found.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Specified value
S:
Terminates command processing.
O:
Check whether the value you are attempting to delete was defined in the server environment definition, and then
re-execute the HA Monitor command.
KAMN454-E (E)
When the cc....cc is defined to the bb....bb of Server:aa....aa, The number of the values has exceeded a maximum value.
Specifying another value for the indicated operand in the server environment definition of the server indicated by the
server alias name has caused the maximum number of values that can be specified to be exceeded.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Specified value
S:
Terminates command processing.
O:
Carefully review the resource configuration to ensure that the number of values specified does not exceed the
limit.
KAMN455-E (E)
The value:aa....aa, The method of a definition of the value is incorrect.
The indicated value was not specified correctly.
aa....aa: Specified value
S:
Stops command processing.
O:
Re-execute the HA Monitor command correctly.
KAMN456-E (E)
An error occurred in command(aa....aa). Command cannot be executed.
An error occurred during processing of the HA Monitor command indicated by the command name. Command
processing is terminated.
aa....aa: Command name
S:
Terminates command processing.
O:
Contact a system administrator.
Action:
Determine the cause of the error based on the error message that was output before this message.
83
2. Messages from KAMN000 to KAMN999
If this message is displayed after executing the command for dynamically changing a server's shared resources
(mondevice), an error message might have been output by a remote system; therefore, you must also consult
error messages output on remote systems to determine the cause.
KAMN457-I
Server:aa....aa, The cc....cc was added to bb....bb.
A resource name has been added to the indicated operand in the server environment definition of the server indicated
by the server alias name.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Resource name
S:
Continues processing.
KAMN458-I
Server:aa....aa, The cc....cc was deleted from bb....bb.
A resource name has been deleted from the indicated operand in the server environment definition of the server
indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Operand name
cc....cc: Resource name
S:
Continues processing.
KAMN459-I (S)
Command:aa....aa was terminated.
Processing of the HA Monitor command indicated by the command name has terminated.
aa....aa: Command name
S:
Terminates command processing.
KAMN460-E (E+L)
An error occurred in command(aa....aa). Command cannot be executed.
An error occurred during processing of the HA Monitor command indicated by the command name. Command
processing is terminated.
aa....aa: Command name
S:
Terminates command processing.
O:
Contact a system administrator.
Action:
Determine the cause of the error based on the error message that was output before this message.
If this message was output after the command for dynamically changing a server's shared resources
(mondevice) was executed, execute the server and host status display command (monshow) with the -d option
to check whether the device status and the content of the server environment definition are correct. If they are not
correct, change the definition, and then re-execute the command for dynamically changing a server's shared
resources (mondevice).
84
2. Messages from KAMN000 to KAMN999
KAMN461-W
Server:aa....aa of other host occurred abnormally during device processing. The server of own host continues device
processing for Online server.
An error has occurred during device processing by a server on the specified remote host. The local server is the active
server, so device processing continues.
aa....aa: Server alias name
S:
Continues processing.
O:
Check the statuses of devices on the active server and the standby server. If the device statuses differ, forcibly
terminate the standby server, change its definition, and then restart it.
KAMN462-E
Server:aa....aa of other host occurred abnormally during device processing. The server of own host stopped device processing
for Standby server.
An error has occurred during device processing by a server on the specified remote host. The local server is the
standby server, so device processing is terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check the statuses of devices on the active server and the standby server. If the device statuses differ, forcibly
terminate the standby server, change its definition, and then restart it.
KAMN463-W
Abnormality had occurred in changing definition file:servers. Confirm the contents of the definition file.
An error occurred while the contents of the server environment definition were being changed by the execution of the
command for dynamically changing a server's shared resources (mondevice).
S:
Continues processing.
O:
Check whether the contents of the server environment definition were changed correctly. If they were not, correct
the server environment definition.
KAMN465-E (E)
Because server:aa....aa is during command processing, Command(bb....bb) cannot be executed.
The indicated command cannot be executed because the server indicated by the server alias name is processing
another command.
aa....aa: Server alias name
bb....bb: Command name
S:
Terminates command processing.
O:
After the currently executing command finishes processing, re-execute the command.
KAMN466-E (E)
Because HAmonitor is during Command(aa....aa) processing, Command(bb....bb) cannot be executed.
The indicated command cannot be executed because HA monitor is processing another command.
85
2. Messages from KAMN000 to KAMN999
aa....aa: Name of the command currently processing
bb....bb: Name of the command whose execution was attempted
S:
Processing of the command whose execution was attempted stops.
O:
After the currently executing command finishes processing, re-execute the command whose execution was
attempted.
KAMN474-E
The control group of server:aa....aa cannot be disconnected. ID:bb....bb code:cc....cc
The control group of the server indicated by the server alias name could not be disconnected. Processing continues
with the control group connected.
aa....aa: Server alias name
bb....bb: Control group ID
cc....cc: Detail code
S:
Continues processing.
O:
Manually disconnect the device, if necessary.
KAMN475-E
The control group of server:aa....aa cannot be connected. ID:bb....bb code:cc....cc
The control group of the server indicated by the server alias name could not be connected. Processing continues with
the control group disconnected.
aa....aa: Server alias name
bb....bb: Control group ID
cc....cc: Detail code
S:
Continues processing.
O:
Manually connect the device, if necessary.
KAMN477-W
Server:bb....bb of other host:aa....aa occurred abnormally during device processing. The server of own host continues device
processing.
An error occurred during device processing on a server of the specified remote host. The local server continues device
processing.
aa....aa: Host name
bb....bb: Server alias name
S:
Continues processing.
O:
Check the statuses of devices on the local server and the remote server. If the device statuses differ, forcibly
terminate the remote server, change its definition, and then restart it.
KAMN478-E (E +L)
The specified function cannot be used in this system. Function:aa....aa
The specified function cannot be used in the current environment.
aa....aa: Function
86
2. Messages from KAMN000 to KAMN999
CPUDOWN-SYSTEM: Shorten the hot standby period in a mutual hot-standby configuration
S:
Suspends processing.
O:
Contact a system administrator.
Action:
Take the following action, depending on the function.
Function
CPUDOWN-SYSTEM
Corrective action
Check the cpudown operand of the HA Monitor environment settings, and the
settings pertaining to the cluster management function of the Switch & Management
Module. Correct definitions and the settings of the Switch & Management Module
as necessary.
KAMN494-E
Abnormalities occurred in execution of the LAN status setting file:aa....aa. Cause code:bb....bb.
An error occurred during processing of the LAN's status settings file.
aa....aa: LAN status settings file name
bb....bb: Cause code (termination code of the LAN's status settings file)
S:
Continues processing.
O:
Eliminate the cause of the error.
KAMN495-E
Abnormalities occurred during execution of a usercommand. Cause code: aa....aa
An error occurred during execution of a user command.
aa....aa: Cause code (termination code of user command)
S:
Continues processing.
O:
Eliminate the cause of the error.
KAMN496-I
The group conversion for the group:aa....aa is complete.
Grouped-system switchover of the group indicated by the group name is complete.
aa....aa: Name of the group for which grouped-system switchover is complete
S:
Continues processing.
KAMN498-E
Starting of a server: aa....aa is stopped.
This message is displayed in the following situations:
• When the same LAN adapter is specified more than once in the lan_neck operand of the server environment
definition and both the current and spare LAN adapters are in the failure state.
• When use is specified in the ip_neck operand of the server environment definition and the LAN status settings
file exited with a value other than 0.
87
2. Messages from KAMN000 to KAMN999
• When a resource that specifies use in the vg_neck or fs_neck operand of the server environment definition
fails to connect.
• When use is specified in the uoc_neck operand of the server environment definition and the user command
exited with a value other than 0.
• When use was specified in the fence_scsi operand of the HA Monitor environment settings, and a SCSI
Reserve failed for a device that was specified in the server environment definition's scsi_device operand or
scsi_dmmp operand.
aa....aa: Server alias name
S:
Continues processing.
O:
Eliminate the cause of the error, and then restart the server.
KAMN499-E
Processing of a shared resource carried out the timeout.
Processing of a shared resource did not complete within the timeout period specified in the definition.
S:
Continues processing.
O:
Check the status of the shared resource, and then restart the server, if necessary.
88
2. Messages from KAMN000 to KAMN999
2.6 Messages from KAMN500 to KAMN599
KAMN511-E
The specified LAN interface:aa....aa cannot be used with this system.
The LAN interface specified in the switchbyfail operand of the server environment definition cannot be used in
this system.
aa....aa: LAN interface name
S:
Suspends processing.
O:
Contact a system administrator.
Action:
Check the switchbyfail operand specification in the server environment definition. Correct the definition if
needed, and then restart HA Monitor.
KAMN512-E (E)
LAN monitor definition file corresponding to LAN interface:aa....aa cannot be used. Details:bb....bb
Either the LAN monitoring definition file corresponding to the specified LAN interface cannot be used, or the LAN
interface specified in the LAN monitoring definition file cannot be used.
aa....aa: LAN interface name
bb....bb: Detail code
Detail code
Meaning
0x00000001
The name of the LAN interface to be monitored, as specified in the LAN monitoring definition
file, exceeds 32 bytes.
0x00000002
The LAN to be monitored, as specified in the LAN monitoring definition file, does not exist in
the system.
0x00000003
The LAN monitoring definition file cannot be read.
0x00000004
A directory was specified for the LAN monitoring definition file.
0x00000007
The IP address or IP label specified in the LAN monitoring definition file has not been specified
in the /etc/hosts file.
0x00000008
The same IP address or IP label was specified in the LAN monitoring definition file more than
once.
0x00000009
A LAN monitoring definition file statement is invalid.
0x0000000A
When monitoring hbonding, the number of IP addresses or IP labels specified in the LAN
monitoring definition file is not 0 or between 2 and 1,024.
When monitoring ethernet or bonding, the number of IP addresses or IP labels specified in
the LAN monitoring definition file is not between 2 and 1,024.
S:
Continues processing.
O:
Contact a system administrator.
Action:
Check the LAN monitoring definition file. Correct the definition, as needed, and then restart HA Monitor.
KAMN513-E (E+L)
Abnormality occurred by internal processing of LAN monitor processing. Details:aa....aa LAN interface: bb....bb
89
2. Messages from KAMN000 to KAMN999
An error has occurred while checking the environment for LAN monitor processing.
aa....aa: Detail code
bb....bb: LAN interface name
S:
Suspends processing.
O:
Contact a system administrator.
Action:
Eliminate the cause of the error based on the message that was output before this message.
KAMN514-E (E)
There are contradiction in a specified value of the bb....bb operand of definition file:aa....aa and a specified value of the
dd....dd operand of definition file:cc....cc.
There is a contradiction in the way corresponding definitions were specified.
aa....aa: Definition file name
bb....bb: Operand name
cc....cc: Definition file name
dd....dd: Operand name
S:
Suspends processing.
O:
Contact a system administrator.
Action:
Take the corrective action described for the applicable displayed item combination in the table below. If you
correct the HA Monitor environment settings, restart HA Monitor.
Displayed item combination
cpudown of sysdef
vmware_env of sysdef
Corrective action
If you are giving reset priority to the active system or standby
system:
Specify online or standby for cpudown of sysdef,
or do not define any value.
If you are not determining reset priority:
• If you are switching systems in a virtual environment
based on VMware ESXi:
Specify online or standby for cpudown of
sysdef, or do not define any value.
• If you are not switching systems in a virtual
environment based on VMware ESXi:
Specify nouse for vmware_env of sysdef, or do
not define any value.
fence_reset of
sysdef
fence_scsi of sysdef
If you are resetting the system as a method of protecting data on
a shared disk:
Specify nouse for fence_scsi of sysdef, or do not
define any value.
If you are using a SCSI Reserve as a method of protecting data
on a shared disk:
Specify nouse for fence_reset of sysdef.
If you are resetting the system as a method of protecting data on
a shared disk:
Specify use for fence_reset of sysdef, or do not
define any value.
90
2. Messages from KAMN000 to KAMN999
Displayed item combination
Corrective action
If you are using SCSI Reserve as a method of protecting data on
a shared disk:
Specify use for fence_scsi of sysdef.
switch_error of
servers
switch_retry of
servers
If you are using the function for retrying startup during a hot
standby:
Specify retry for switch_error of servers.
If you are not using the function for retrying startup during a hot
standby:
Do not define switch_retry of servers.
fence_lan of sysdef
lanfailswitch of
sysdef
If you are using LAN communication enabling/disabling for
controlling server switching:
Specify use for lanfailswitch of sysdef.
If you are not using LAN communication enabling/disabling for
controlling server switching:
Specify nouse for fence_lan of sysdef.
KAMN515-E (E)
The LAN monitoring script:aa....aa does not exist or execution of this script is not permitted.
Either no LAN monitoring script exists, or execution of this script is not permitted.
aa....aa: File name of LAN monitoring script
S:
Suspends processing.
O:
Check whether the LAN monitoring script has been set up and whether its execution is permitted, and then restart
HA Monitor.
KAMN516-E (E)
The value specified (specified value:cc....cc) for the bb....bb operand of the aa....aa definition file is invalid. Details
code:dd....dd
The operand specified in the definition file is invalid.
aa....aa: Definition file name
bb....bb: Operand name
cc....cc: Operand specification value
dd....dd: Detail code
Detail code
Meaning
NOT HBONDING
Because the specified LAN interface is not hbonding, the status of hbonding cannot be
monitored using the LAN monitoring function.
NOT 802.3AD LACP
Because the operating mode of the specified LAN interface is not 802.3AD, errors might not
be detected if the LAN monitoring function is used to monitor the status of hbonding.
NOT FOUND LANMONDEF
Because there is no LAN monitor definition file for the specified LAN interface, the LAN
monitoring function cannot be used.
S:
Continues processing.
O:
Take one of the following actions, as indicated by the detail code:
91
2. Messages from KAMN000 to KAMN999
Detail code
Corrective action
NOT HBONDING
Make sure that the specified LAN interface is hbonding, and then specify hbonding.
NOT 802.3AD LACP
Make sure that the operating mode of the specified LAN interface is 802.3AD, and then
specify hbonding with operating mode 802.3AD.
NOT FOUND LANMONDEF
Make sure that there is a LAN monitor definition file that corresponds to the specified LAN
interface, and then define the settings for using the LAN monitoring function.
KAMN523-E
Abnormality was detected LAN interface: aa....aa. server:bb....bb
An error has occurred in the LAN being monitored.
aa....aa: LAN interface name
bb....bb: Server alias name
S:
Continues processing. If the active server that uses the LAN is in a state able to perform a hot standby, performs a
hot standby.
O:
Check for errors in the LAN monitoring definition file or the LAN monitoring script. If the LAN interface was
specified in the hbond_lacp operand of the HA Monitor environment settings, check whether a channel group
has been set up in the network switch connected to hbonding. If there are no errors, determine the cause of the
failure in the LAN, and then eliminate the cause of the failure.
KAMN524-I
LAN interface:aa....aa was restored. server:bb....bb
The LAN being monitored is ready to be used.
aa....aa: LAN interface name
bb....bb: Server alias name
S:
Continues processing.
KAMN525-E
Server:bb....bb, Hotstandby is started, because it detected abnormality in LAN interface:(aa....aa).
A hot standby is being performed on an active server capable of hot standby because an error was detected in the
LAN.
aa....aa: LAN interface name
bb....bb: Server alias name
S:
Continues processing.
KAMN526-W
LAN interface:aa....aa, abnormality occurred in the monitoring process. The monitoring process is restarted.
The monitoring process was restarted because an error occurred that prevented LAN monitoring from continuing.
aa....aa: LAN interface name
S:
Continues processing.
KAMN528-I
The state of LAN interface:aa....aa will be checked.
92
2. Messages from KAMN000 to KAMN999
The state of the LAN interface specified in the switch_judge operand is being checked so that, if its state is
normal, this interface can be used for the active system in the event that an error is detected in the remote system.
After this message, message KAMN529-I or KAMN530-E is output.
This message is output for each LAN interface in each host in which an error occurred.
aa....aa: LAN interface name
S:
Continues processing.
KAMN529-I
The state of LAN interface:aa....aa is normal.
The state of the LAN interface specified in the switch_judge operand was checked, and it was determined that the
monitored LAN is normal.
The server on which the switch_judge operand is specified, and other servers in the same server group as that
server, behave as follows:
• If a server is in hot-standby wait state, hot standby starts.
This message is output for each LAN interface.
aa....aa: LAN interface name
S:
Continues processing.
KAMN530-E
An abnormal state of LAN interface:aa....aa was detected.
The state of the LAN interface specified in the switch_judge operand was checked, and it was determined that the
monitored LAN is abnormal.
The server in which the switch_judge operand is specified stops, together with other servers in the same server
group as that server.
This message is output for each LAN interface.
aa....aa: LAN interface name
S:
Stops the servers.
O:
Contact a system administrator.
Action:
Investigate the cause of the LAN error, eliminate the cause of the error, and then start the servers as needed.
93
2. Messages from KAMN000 to KAMN999
2.7 Messages from KAMN600 to KAMN699
KAMN601-W (E+L)
An error occurred in the aa....aa system call. Error details:bb....bb Functional name:cc....cc
An error occurred in a system call invoked by an HA Monitor function. For more information about detail codes, see
the documentation for the applicable OS.
aa....aa: Invoked system call
bb....bb: Detail code (1 or 3 digits)
cc....cc: Name of function that generated the error
S:
Continues processing.
O:
Contact a system administrator.
Action:
Determine the cause based on the detail code.
KAMN607-E
Patrol Path cannot be opened. Patrol Path name:aa....aa Error details:bb....bb
An attempt to open a monitoring path failed.
A message indicating the error detail is output prior to this message.
aa....aa: Failed monitoring path name
bb....bb: Detail code (1 or 2 digits)
S:
Continues processing.
O:
Determine the cause as indicated by the message output before this message, and then restart HA Monitor.
KAMN608-W
It cannot be sent to host:aa....aa.
Communications with the host indicated by the host name failed. Data could not be transmitted normally.
aa....aa: Host name
S:
Continues processing.
O:
Execute the monitoring path status display command (monpath), and then determine the status of the monitoring
path that was used. If an error occurred in the monitoring path, eliminate the cause of the error. If NO RESPONSE
is displayed, check the network's connection, and then determine whether equipment has failed.
KAMN609-W
Receiving errors occurred in the Patrol Path. Patrol Path name:aa....aa.
Communication was attempted with a remote host using the monitoring path indicated by the failed monitoring path
name. Data could not be received normally.
aa....aa: Failed monitoring path name
S:
Continues processing.
O:
Execute the monitoring path status display command (monpath), and then check the monitoring path status.
94
2. Messages from KAMN000 to KAMN999
Action:
Determine the cause as indicated by the message output before this message.
KAMN610-W
The following language(s) are not available: LANG=aa....aa
Continuing processing using the language "C".
The value of the message environment variable LANG is incorrect. Processing continues with LANG set to its default
value of C.
aa....aa: Value of LANG environment variable
S:
Continues processing.
O:
Correct the value of the message environment variable LANG.
KAMN611-W
Cannot read "aa....aa" message catalog; proceeding in default language.
The message catalog file specified in the message environment variable cannot be read, so processing resumes using
the HA Monitor default file.
aa....aa: Value of LANG environment variable
S:
Continues processing.
O:
Check whether the value of the LANG environment variable is valid for HA Monitor.
KAMN612-E (E+L)
It errs in the message environment. Message number:aa....aa
A message cannot be output because the message environment is specified incorrectly.
aa....aa: Number of the message that cannot be output
S:
Continues processing.
O:
Eliminate the cause of the message environment error.
KAMN613-E (E+L)
There is not message. Message number:aa....aa
A message cannot be output because the message indicated by the message number does not exist in the message
catalog file.
aa....aa: Number of the message that cannot be output
S:
Continues processing.
O:
Check whether the HA Monitor message catalog file is correctly installed. If it is not, add it to the correct
directory.
If the file is correctly installed, contact a system administrator.
Action:
If an error message is output before this message, determine the cause based on that error message.
95
2. Messages from KAMN000 to KAMN999
KAMN614-E (E)
aa....aa: bb....bb
An error occurred in a message catalog file.
For details about error information, see the documentation for the applicable OS.
aa....aa: Message catalog file name
Message catalog file name
Meaning
/usr/share/locale/C/HAmon.cat
English language messages
/usr/share/locale/ja_JP.eucJP/HAmon.cat
Japanese language
messages (EUC)
/opt/hitachi/HAmon/nls/ja_JP.UTF-8/HAmon.cat
Japanese language
messages (UTF-8)
bb....bb: Error information
S:
Continues processing.
O:
Eliminate the cause of the error in the HA Monitor's message catalog file.
KAMN615-E (E)
It errs in the message environment. Command is stopped.
There is an error in the message environment.
S:
Stops command processing.
O:
Eliminate the cause of the message KAMN614-E, and then re-execute the command.
KAMN616-E (E+L)
Command(aa....aa) of HAmonitor stopped abnormally.
An error occurred in a command invoked as a child process. Either the specified command does not exist or a signal
was received during processing.
aa....aa: Command name
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Determine the cause of the error based on the error message that was output before this message.
KAMN617-E
HAmonitor stopped abnormally. abort-id:aa....aa
HA Monitor terminated abnormally because an unrecoverable error occurred within HA Monitor.
aa....aa: Abort ID
Abort ID
213
96
Meaning
Abort when an attempt to add a host management table failed (due to the address operand in the HA
Monitor environment settings being duplicated in a remote system)
2. Messages from KAMN000 to KAMN999
Abort ID
Meaning
250
Abort when a server failure was detected or a device failed to disconnect (due to a server failure while
using the pairdown function or when a shared resource failed to disconnect during a hot standby)
260
Abort when local system failure is detected or a reset completion is received (due to the address
operand in the HA Monitor environment settings being duplicated in a remote system)
S:
Terminates processing.
O:
Restart the host. It is possible that resources have been corrupted, particularly if a file system is being used; be
sure to restart the file system if one is being used.
Action:
Eliminate the cause of the error based on the abort ID that is output. If the abort ID output is not listed above,
contact maintenance personnel.
KAMN619-E
File:aa....aa cannot be opened. Cause code:bb....bb
A message cannot be output to a file because the file indicated by the file name cannot be opened. For details about
cause codes, see the documentation for the applicable OS.
aa....aa: File name (/dev/console or /dev/null)
bb....bb: Cause code (errno of system call when file is opened)
S:
Continues processing. The message is sent to standard output or standard error.
O:
Contact a system administrator.
Action:
Determine the cause based on the cause code.
KAMN620-E
Slowdown of HAmonitor in the own host was detected.Standby server:aa....aa is started again.
A slowdown was detected in the local system's HA Monitor. The standby server indicated by the server alias name
was restarted and the connection is restored.
aa....aa: Server alias name
S:
Continues processing.
O:
Determine the reason the local HA Monitor slowed down, and then restart HA Monitor, if necessary.
KAMN621-E
Abnormality occurred in Reset Path. Error details:aa....aa
An error occurred in a reset path of a remote host linked by a reset path.
aa....aa: Detail code
Detail code
Meaning
SEND
A communication failure occurred.
NORSTD
A reset path initialization failure occurred.
S:
Continues processing.
97
2. Messages from KAMN000 to KAMN999
O:
Eliminate the cause of the system call error as indicated by message KAMN601-w, which is output before this
message, or the cause of the reset path error as indicated by message KAMN624-E, and then execute the reset path
status display command (monrp).
KAMN624-E
The state of Reset Path of Host : aa....aa is abnormal.
Error details : bb....bb
Reset Path : cc....cc
An error occurred in the reset path.
aa....aa: Host name
bb....bb: Detail code
Detail code
Meaning
SEND
A communications failure occurred.
NO SET ADDRESS
The indicated host has not finished initializing the reset path.
SVP-TIMEOUT
A timeout of the indicated reset path was detected.
RESET-ERR
The failure management processor failed to reset.
LPAR-RSP-FAIL
An error occurred in a query to the indicated host.
SYSNAME-ERR
The managing system name is invalid.
PARTITION-ERR
The partition name is invalid.
HOST-OVER
The number of hosts has exceeded the number that can be controlled.
POWER-FAILURE
A power failure occurred on the indicated host.
CTRLPTH-DOWN
A reset path connection failed.
REQ-TIMEOUT
A request to a reset path timed out.
IMPOSSIBLE
Resetting on the remote host is not possible.
SSH-ERR
Communication with the VMWare ESXi of the host indicated by the host name failed.
SSH-TIMEOUT
The response from the VMWare ESXi of the host indicated by the host name timed out.
VMNAME-ERR
The virtual machine name is invalid.
VMNAME-DBL
The virtual machine name was specified more than once.
NOLRSTD
Reset path initialization failed.
cc....cc: Failed reset path
Primary: Primary reset path
ESXi: Reset path for connecting VMware ESXi
S:
Terminates processing.
O:
Take one of the following actions, as indicated by the detail code:
Detail code
SEND
98
Corrective action
Eliminate the cause of the system call error as indicated by message KAMN601-w,
which is output before this message, and then execute the reset path status display
command (monrp).
2. Messages from KAMN000 to KAMN999
Detail code
• NO SET ADDRESS
• RESET-ERR
Corrective action
These are generally caused by a hardware failure. Eliminate the cause of the error, and
then execute the reset path status display command (monrp).
• LPAR-RSP-FAIL
• POWER-FAILURE
• CTRLPTH-DOWN
SVP-TIMEOUT
If system is specified for the cpudown operand of the HA Monitor environment
settings, carefully review the settings and configuration pertaining to the cluster
management function of the Switch & Management Module. Correct any errors you
find in the settings or configurations.
If you do not find any errors, a hardware failure might be at fault. Eliminate the cause
of the error, and then execute the reset path status display command (monrp).
• SYSNAME-ERR
• PARTITION-ERR
These are generally caused by reset path setting and configuration errors. Carefully
review the reset path settings and configurations, and then restart HA Monitor.
• HOST-OVER
• IMPOSSIBLE
REQ-TIMEOUT
First, carefully review the reset path settings and configurations. For an N+M cold
standby configuration, carefully review the following for all Switch & Management
Modules that belong to the same network as the HA Monitor's reset path.
• Are the N+M cold standby settings correct?
• Is the managing system name duplicated?
If system is specified for the cpudown operand of the HA Monitor environment
settings, also carefully review the settings pertaining to the cluster management
function of the Switch & Management Module.
Correct any errors you find in the reset path settings or configuration, and then restart
HA Monitor.
If you do not find any errors in the reset path settings or configuration, a hardware
failure might be at fault. Eliminate the cause of the error, and then execute the reset
path status display command (monrp).
SSH-ERR
Carefully review the following:
• IP address of VMWare ESXi set in HA Monitor
• Port number for SSH connection to VMWare ESXi set in HA Monitor
• IP address set in VMWare ESXi
• Port number for SSH connection set in VMWare ESXi
Correct any errors you find in the HA Monitor settings, and then restart HA Monitor.
If you find any errors in the VMWare ESXi settings, correct them, and then execute
the reset path status display command (monrp).
If you do not find any errors in any of these settings, a hardware failure or an error in
VMWare ESXi might be at fault. Eliminate the cause of the error, and then execute
the reset path status display command (monrp).
If this still does not resolve the problem, the process might have temporarily slowed
down due to reset processing. Wait a while, and then execute the reset path status
display command (monrp).
If normal status is not restored, contact a system administrator.
SSH-TIMEOUT
Carefully review the following:
• IP address of VMWare ESXi set in HA Monitor
• Port number for SSH connection to VMWare ESXi set in HA Monitor
• IP address set in VMWare ESXi
• Port number for SSH connection set in VMWare ESXi
99
2. Messages from KAMN000 to KAMN999
Detail code
Corrective action
Correct any errors you find in the HA Monitor settings, and then restart HA Monitor.
If you find any errors in the VMWare ESXi settings, correct them, and then execute
the reset path status display command (monrp).
If you do not find any errors in any of these settings, a hardware failure or an error in
VMWare ESXi might be at fault. Eliminate the cause of the error, and then execute
the reset path status display command (monrp).
VMNAME-ERR
Carefully review the following:
• IP address of VMWare ESXi set in HA Monitor
• Virtual machine name set in HA Monitor
• IP address set in VMWare ESXi
• Name of logical partition in which the local system runs, set in VMWare ESXi
Correct any errors you find in the HA Monitor settings, and then restart HA Monitor.
If you find any errors in the VMWare ESXi settings, correct them, and then execute
the reset path status display command (monrp).
VMNAME-DBL
Correct the VMWare ESXi and HA Monitor settings so that no virtual machine names
are duplicated, and then restart HA Monitor.
NOLRSTD
If message KAMN601-W is output before this message, eliminate the cause of the
system call error as indicated by KAMN601-W, and then execute the reset path status
display command (monrp).
If message KAMN601-W is not output before this message, carefully review the
following:
• IP address of VMWare ESXi set in HA Monitor
• Port number for SSH connection to VMWare ESXi set in HA Monitor
• IP address set in VMWare ESXi
• Port number for SSH connection set in VMWare ESXi
• VMWare ESXi settings pertaining to SSH connection
• Password of root user set in VMWare ESXi
Correct any errors you find in the HA Monitor settings, and then restart HA Monitor.
If you find any errors in the VMWare ESXi settings, correct them, and then execute
the reset path status display command (monrp).
If this message is output after message KAMN751-I, execute the reset path status
display command (monrp).
KAMN625-W
The definition of Reset Path was changed.
The reset path setting was changed. The overwriting of this setting might create a conflict.
If, within a system, there are multiple hot standby configurations that do not monitor each other and that share a reset
path, this message is output when values specified for address operands in the HA Monitor environment settings
duplicate each other.
S:
Continues processing.
O:
Check the reset path settings and the address operands of the HA Monitor environment settings for all hosts.
Specify address operands so that they do not duplicate those of any host that shares the reset path. After you
have eliminated any errors, restart HA Monitor on all hosts. This message might also be displayed when HA
Monitor restarts.
KAMN626-E (E+L)
Command(aa....aa) of HAmonitor stopped abnormally. Error details:bb....bb
100
2. Messages from KAMN000 to KAMN999
An error occurred in a command invoked as a child process. The specified command received a signal during
processing.
aa....aa: Command name
bb....bb: Detail code
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Restart HA Monitor.
KAMN635-E
The system call for a Patrol Path:aa....aa ended abnormally. Return code:bb....bb. Error details:cc....cc. System call
name:dd....dd.
A system call error occurred while a monitoring path was in use. For more information about detail codes, see the
documentation for the applicable OS.
aa....aa: Failed monitoring path name
bb....bb: Return code
cc....cc: Detail code
dd....dd: System call name
S:
Continues processing.
O:
Execute the monitoring path status display command (monpath), and then check the monitoring path status.
KAMN639-W
The system name set to Switch and Management Modules overlaps each other. IP address of the Switch and Management
Module:aa....aa : bb....bb system name : cc....cc
Managing system names, set in Switch & Management Modules, are duplicated. A conflict might have been created
because of an error in the reset path setting.
aa....aa: IP address of Switch & Management Module
bb....bb: IP address of Switch & Management Module
cc....cc: Managing system name
S:
Continues processing.
O:
Check all Switch & Management Modules on the same network as the reset path to determine if managing system
names duplicate each other. After errors have been eliminated, restart HA Monitor on all systems.
KAMN640-E
Abnormality occurred in Patrol Path:aa....aa. Details:bb....bb.
An error occurred in the monitoring path.
aa....aa: Failed monitoring path name
bb....bb: Detail code
Detail code
4
Meaning
LAN line failure
S:
Continues processing.
101
2. Messages from KAMN000 to KAMN999
O:
Execute the monitoring path status display command (monpath), and then check the monitoring path status
again. If no problem is found, the situation might be due to a high machine load or a temporary failure of a
monitoring path, which means you can ignore it. If a problem is found, contact a system administrator.
Action:
Determine the cause of the error, and then eliminate it.
KAMN641-W
The answer of the state inquiry message of Patrol Path is not sent from host:aa....aa. Patrol Path name:bb....bb.
A monitoring path status query message was sent via the monitoring path to the host indicated by the host name, but
no response message was received.
aa....aa: Host name
bb....bb: Failed monitoring path name
S:
Continues processing.
O:
Execute the monitoring path status display command (monpath), and then check the monitoring path status
again. If no problem is found, the situation might be due to a high machine load or a temporary failure of a
monitoring path, which means you can ignore it. If a problem is found, contact a system administrator.
Action:
Determine the cause of the error, and then eliminate it.
KAMN642-W
Alive message is not sent from host:aa....aa.
No alive message has been received during status monitoring of the host indicated by the host name, even though
approximately 70% of the monitoring period has elapsed.
aa....aa: Host name
S:
Continues host monitoring. If a preferred monitoring path has been specified in the lan operand of the HA
Monitor environment settings, HA Monitor switches to that monitoring path. If the reason no alive message has
been received is due to the host rather than the monitoring path, HA Monitor outputs a KAMN340-E message
after it outputs this message once the remaining 30% of the monitoring period elapses, and then performs timeout
failure processing.
O:
Execute the monitoring path status display command (monpath), and then check the monitoring path status
again. If no problem is found, the situation might be due to a high machine load or a temporary failure of a
monitoring path, which means you can ignore it. If a problem is found, contact a system administrator.
Action:
Determine the cause of the error, and then eliminate it.
KAMN643-W
The answer of the inquiry message is not sent from host:aa....aa.
A query message was sent to the host indicated by the host name, but no response has been received, even though
approximately 70% of the monitoring period has elapsed.
aa....aa: Host name
S:
Continues host monitoring.
If a preferred monitoring path has been specified in the lan operand of the HA Monitor environment settings, HA
Monitor switches to that monitoring path. If the reason no response message has been received is due to the host
rather than the monitoring path, HA Monitor outputs a KAMN340-E message after it outputs this message once
the remaining 30% of the monitoring period elapses, and then performs timeout failure processing.
102
2. Messages from KAMN000 to KAMN999
O:
Execute the monitoring path status display command (monpath), and then check the monitoring path status
again. If no problem is found, the situation might be due to a high machine load or a temporary failure of a
monitoring path, which means you can ignore it. If a problem is found, contact a system administrator.
Action:
Determine the cause of the error, and then eliminate it.
KAMN644-W
An error occurred in the reset path of the host:aa....aa. (details code:bb....bb, reset path:cc....cc)
An error occurred in the reset path of the host indicated by the host name. The active system might be prevented from
being reset, and might be placed in the hot-standby wait-state. This message is intended as a status notification for the
user and is output at a given interval.
aa....aa: Host name
bb....bb: See the detailed code tables for KAMN621-E and KAMN624-E.
cc....cc: If the detail code is NORSTD, four single-byte hyphens (----) are displayed. If the detail code is not
NORSTD, see the reset path that caused the error indicated by KAMN624-E.
S:
Continues processing.
O:
See the table under O: in KAMN624-E.
KAMN650-E (E)
aa....aa system call error (bb....bb): cc....cc
An error occurred in a system call invoked by an HA Monitor function. For more information about detail codes, see
the documentation for the applicable OS.
aa....aa: System call invoked
bb....bb: Detail code
cc....cc: Message of detail code
S:
Continues processing.
O:
Contact a system administrator.
Action:
Determine the cause based on the detail code.
KAMN651-E (E+L)
The environment check or termination process of the HA monitor was failed.
Error details:aa....aa:bb....bb:cc....cc.
A check of the HA Monitor environment settings or termination processing failed.
aa....aa: Detail code (1 digit)
Detail code
4
Meaning
Linux Tough Dump service could not be used.
bb....bb: Internal error code
cc....cc: errno of system call (from 1 to 3 digits)
If detail code is 4: 0
S:
Terminates processing.
103
2. Messages from KAMN000 to KAMN999
O:
Take one of the following actions, as indicated by the internal error code:
Internal error code
Corrective action
SYSTEM_CALL
Eliminate the cause of the system call error as indicated by message KAMN601-W, which is
output before this message, and then restart HA Monitor.
LTD_STOP
Restart the Linux Tough Dump service and HA Monitor.
LTD_ERROR
Restart the Linux Tough Dump service and HA Monitor.
If a message from the Linux Tough Dump service was output before this message, eliminate
the cause of the error sa indicated by that message, and then restart the Linux Tough Dump
service and HA Monitor.
KAMN660-E
Usercommand:aa....aa cannot start.
A user command could not be executed.
aa....aa: Command name
S:
Continues processing.
O:
Check the usrcommand operand of the HA Monitor environment settings, and then eliminate the cause of the
error in the indicated user command.
KAMN661-I (S)
Usage: moninfo alias -p inheritable information
moninfo alias -g
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the command for
specifying and displaying server inheritance information (moninfo) is incorrect.
S:
Continues processing.
KAMN662-E (E)
The inheritable information of aa....aa command is improper.
The information that the server inherits from the specified command has exceeded a limit or includes an invalid
character.
aa....aa: Command name
S:
Stops command processing.
O:
Specify the information that the server inherits using the correct syntax.
KAMN663-I (S)
Inheritable information was set at server:aa....aa.
The inheritable information, specified by the command for specifying and displaying server inheritance information
(moninfo), was set in the server indicated by the server alias name.
aa....aa: Server alias name
S:
Continues processing.
104
2. Messages from KAMN000 to KAMN999
KAMN666-E
Removal of a shared disk reserve for the server aa....aa was detected.
The reserve status could no longer be detected for the shared disk of the server indicated by the server alias name. The
server was stopped.
Reserve status might have become undetectable for the following reasons:
• A hot standby was triggered by a local system slowdown or monitoring path failure, so a remote system reserved
the disk.
• The shared disk used by the server was illegally reserved by another program or operation.
aa....aa: Server alias name
S:
Resumes processing.
O:
Eliminate the cause of the failure, and then restart the server, if necessary.
KAMN667-I (S)
No reset path is being used.
The reset path status display command (monrp) cannot be used because no reset path is being use.
S:
Resumes processing.
KAMN684-E
Abnormality of HAmonitor in the own host was detected. Own host cannot be system reset.
Error details:aa....aa
The local system cannot perform a reset, nor can it be reset from a remote system, because an error has been detected
on the local HA Monitor, as indicated by the cause code.
aa....aa: Cause code
Cause code
Meaning
ATTACH
A daemon failed to start.
PIPE
A pipe system call error occurred.
FORK
A fork system call error occurred.
CONNECT
A communication error occurred.
NOEXIST
A daemon terminated abnormally.
S:
Continues processing.
O:
If message KAMN601-W is output before this message, eliminate the cause of the system call error as indicated by
that message, and then execute the reset path status display command (monrp).
If message KAMN624-E is output before this message, eliminate the cause of the detail code error as indicated by
that message, and then execute the reset path status display command (monrp).
If the cause code is PIPE, the reset path might not have been set by the HA Monitor environment setup command
(monsetup). Check the setting of the reset path. If the path has not been set, force HA monitor to terminate
normally, set the reset path with monsetup, and then restart HA Monitor.
KAMN685-W
The definition of host(aa....aa)'s Reset Path is different from own host's definition.
105
2. Messages from KAMN000 to KAMN999
The host indicated by the host name was connected. However, a system reset could not be performed on that host
because its reset path configuration is different from that of the local system. If the Switch & Management Module is
used for the reset path, a reset path might not have been set up using the HA Monitor environment setup command
(monsetup).
aa....aa: Host name
S:
Continues processing.
O:
Check the reset path setting and correct it if necessary, and then restart HA Monitor.
KAMN686-W
The function of Switch and Management Module cannot be used. Details : aa....aa
A local Switch & Management module sent a notification that an invalid function was attempted.
aa....aa: Detail code
Detail code
CLUSTER-MANAGER
Meaning
The cluster management function of the Switch & Management Module is in an invalid
state.
S:
Continues processing.
O:
Take the following action, as indicated by the detail code:
Detail code
CLUSTER-MANAGER
Corrective action
Carefully review the cluster management function settings and configuration of the
local Switch & Management Module. If an error is found, correct it.
KAMN690-W
An error occurred in the aa....aa command.
Command output details:'bb....bb'
An error occurred in an OS command issued in an HA Monitor function. For details about the output message, see the
documentation for the applicable OS.
aa....aa: Issued command
bb....bb: Message issued by the command (might be blank in some cases)
S:
Continues processing.
Action:
Investigate the cause of the error based on the output message, and eliminate the cause of the failure.
KAMN695-I
The function that detects Operating System panic of other systems was enabled.
The function that detects OS panics in other systems has been enabled. HA Monitor operates using the function that
detects OS panics in other systems.
S:
Continues processing.
KAMN696-W
The function that detects Operating System panic of other systems was not enabled. Cause code:aa....aa
HA Monitor will operate without using the function that detects OS panics in other systems.
106
2. Messages from KAMN000 to KAMN999
aa....aa: Cause code
Cause code
Meaning
SYSTEM_CALL
System call error
LTD_STOP
Linux Tough Dump service has not started.
LTD_ERROR
Linux Tough Dump service error.
S:
Continues processing.
O:
Contact a system administrator.
Action:
Take one of the following actions, as indicated by the cause code:
Cause code
Corrective action
SYSTEM_CALL
Eliminate the source of the system call error as indicated by message KAMN601-W,
which is output before this message, and then restart HA Monitor.
LTD_STOP
Restart the Linux Tough Dump service and HA Monitor.
LTD_ERROR
Determine the cause of the error based on the OS failure notification function message
that was output before this message. After eliminating the cause of the error, restart the
Linux Tough Dump service and HA Monitor.
For details about the OS failure notification function messages, see the documentation
for the Linux Tough Dump service.
KAMN699-I
The function that Linux Tough Dump Service is used.
The Linux Tough Dump service will be used. A system dump will be generated if a system failure occurs.
If the function that detects OS panics in other systems is available, HA Monitor operates using the function that
detects OS panics in other systems.
S:
Continues processing.
107
2. Messages from KAMN000 to KAMN999
2.8 Messages from KAMN700 to KAMN799
KAMN701-I
Because it is already published, the trb_mtb_malloc function rejects.
The module trace buffer allocation function (trb_mtb_malloc) has already been invoked, and a buffer has been
allocated. Re-invoking this function is not allowed.
S:
Continues processing.
KAMN702-W
Because a module trace buffer cannot be gotten, module trace information stops.
Due to a memory shortage, the work area required to acquire module trace information could not be allocated. Module
trace information will not be collected.
S:
Continues processing.
O:
Contact a system administrator.
Action:
Determine the cause of the error based on the error message that was output before this message.
KAMN717-E
Failed to JP1 event notification. Event-ID=aa....aa Message-ID=bb....bb Function-name=cc....cc Status=dd....dd
An attempt to report a JP1 event has failed. The JP1 event has not been reported.
aa....aa: ID of event that was attemping to post a notification
bb....bb: ID of the HA Monitor message corresponding to the event that was attempting to post a notification
cc....cc: Name of the function that generated the error
dd....dd: Status code
Status code
Meaning
NO_LIBRARY
Library not found.
CONNECT_ERROR
Cannot connect to JP1/Base.
MAXOPEN
The number of open files has exceeded the limit.
NO_MEMORY
Insufficient memory
S:
Continues processing.
O:
Contact a system administrator.
Action:
Eliminate the failure, based on the avoidance strategies in the table below. If the status codes is not found in this
table, collect information as necessary.
Status code
NO_LIBRARY
Corrective action
JP1/Base might not have been installed.
Install it, and then restart HA Monitor.
CONNECT_ERROR
JP1/Base might not have been started.
Start JP1/Base.
108
2. Messages from KAMN000 to KAMN999
Status code
Corrective action
MAXOPEN
Carefully review the kernel parameters, and then restart HA Monitor.
NO_MEMORY
Carefully review whether sufficient memory has been allocated to the system.
KAMN723-E
The data protection method setting for the shared disk is invalid.
Although both the scsi_device and dmmp_device operands have been specified in the server environment
definition, use is not specified in the fence_scsi operand of the HA Monitor environment settings.
S:
Suspends startup processing.
O:
Contact a system administrator.
Action:
Correct the definition, and then restart HA Monitor.
KAMN724-E
0 cannot be set for the address operand of the function statement in the sysdef definition file.
0 cannot be specified in the address operand because use was specified in the fence_scsi operand of the HA
Monitor environment settings.
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Specify 1 or more for the address operand in the HA Monitor environment settings.
KAMN725-W (E+L)
Execution of the SCSI command on the device aa....aa ended abnormally. (details code: bb....bb, server: cc....cc, host address:
dd....dd (0xee....ee))
A SCSI command execution error has occurred for device aa....aa. If bb....bb is OPEN or IOCTL, message
KAMN601-W is output before this message.
aa....aa: Name of the device specified in the server environment definition operand in which the error occurred
For details about the device name, see the following table:
Operand name
scsi_device
Environment
Device name
Multipath software is
HDLM.
HDLM logical device name
Virtual environment
based on VMware ESXi
Symbolic link name
All other cases
dmmp_device
Multipath software is
DMMP.
DMMP logical device name
(/dev/xxx) is output after the DMMP logical device name, where xxx
indicates the name of the path where the error occurred.
bb....bb: Detail code
Detail code
OPEN
Meaning
An attempt to open aa....aa failed. aa....aa does not exist.
109
2. Messages from KAMN000 to KAMN999
Detail code
Meaning
IOCTL
aa....aa does not support SCSI reservations.
ALREADY-RESERVATION
aa....aa is already reserved. Another possibility is that it was reserved by a remote
system in a hot standby.
IO-ERR
An I/O error has occurred on aa....aa.
cc....cc: Server alias name of the server that is using a shared disk on aa....aa.
dd....dd: The following are displayed, listed by detail code.
Detail code
OPEN
Text displayed
*
IOCTL
ALREADY-RESERVATION
Host address of the system that has reserved the disk
IO-ERR
Local system host address (Note: When this message is output by the
monscsiclr command, this value is always 99999999.)
ee....ee: The following are displayed, listed by detail code.
Detail code
OPEN
Text displayed
*
IOCTL
ALREADY-RESERVATION
IO-ERR
Displays, in hexadecimal, the content displayed in dd....dd. This is the
specification key of the sg_persist command that is executed during
corrective actions.
S:
Resumes processing.
O:
Contact a system administrator.
Action:
Take one of the following actions, as indicated by the detail code:
Detail code
Corrective action
OPEN
Specify a symbolic link or HDLM logical device name for the scsi_device
operand. Alternatively, specify the logical device of the multipath software
(DMMP) in the dmmp_device operand.
IOCTL
Specify a symbolic link of a shared disk supporting SCSI Reserve or an
HDLM logical device name for the scsi_device operand. Alternatively,
specify the logical device of the multipath software (DMMP) in the
dmmp_device operand.
ALREADY-RESERVATION
If the active server is started after any of the operations or events listed below,
this detail code is output and the processing to start the active server fails. In
such a case, either execute the reservation release command (monscsiclr
command) or release the reservation by following the procedure described in
the section on handling a server that does not release a reservation in the
manual HA Monitor Cluster Software (for Linux(R) (x86) systems), and then
restart the active server.
• When the active server was stopped, the reservation could not be released,
for example, because of an I/O error (the KAMN726-E message is
displayed).
• A host failure occurred on the active system while hot standby processing
was not possible (for example, because the standby server was inactive).
110
2. Messages from KAMN000 to KAMN999
Detail code
Corrective action
• The OS was shut down while the active server was running.
• When hot standby processing was performed as a result of a host failure,
the active server terminated before the failed host and the standby server
were started.
If none of the above applies, see the sections on handling device failures on a
shared disk in the manual HA Monitor Cluster Software (for Linux(R) (x86)
systems), and take the corrective action described there.
IO-ERR
See the section on handling shared disk device failures in the manual HA
Monitor Cluster Software (for Linux(R) (x86) systems), and take the corrective
action described there.
KAMN726-E (E+L)
Errors occurred on all the paths to the device aa....aa.
Errors have occurred on all paths corresponding to device aa....aa. The KAMN725-W message is output before this
message.
aa....aa: Name of the device specified in the server environment definition operand, in which the error occurred
For details about the device name, see the following table:
Operand name
scsi_device
Environment
Device name
Multipath software is
HDLM.
HDLM logical device name
Virtual environment
based on VMware ESXi
Symbolic link name
All other cases
dmmp_device
Multipath software is
DMMP.
DMMP logical device name
(/dev/xxx) is output after the DMMP logical device name, where xxx
indicates the name of the path where the error occurred. Out of the
physical paths corresponding to the DMMP logical device, the path
name displayed in the message KAMN725-W, which is output before the
message KAMN726-E, is output.
S:
Resumes processing.
O:
Contact a system administrator.
Action:
See message KAMN725-W, which was output before this message, and then eliminate the cause of the error.
KAMN727-I
Recovery of the device aa....aa was detected. (details code: bb....bb, server: cc....cc)
The device aa....aa that failed when the SCSI command was executed has been recovered.
aa....aa: Name of the device specified in the server environment definition operand in which the error occurred
For details about the device name, see the following table:
Operand name
scsi_device
Environment
Device name
Multipath software is
HDLM.
HDLM logical device name
Virtual environment
based on VMware ESXi
Symbolic link name
111
2. Messages from KAMN000 to KAMN999
Operand name
Environment
Device name
All other cases
dmmp_device
Multipath software is
DMMP.
DMMP logical device name
(/dev/xxx) is output after the DMMP logical device name, where xxx
indicates the name of the path where the error occurred.
bb....bb: Detail code
Detail code
Meaning
STANDBY_CHECK
The processing to check the path status of the shared disk, which is executed
periodically by the standby server, detected that the device had been recovered.
ONLINE_CHECK
The processing to check for shared disk reservations, which is executed periodically
while the active server is running, detected that the device had been recovered.
ONLINE_CHECK(NO_KEY)
The processing to check for shared disk reservations, which is executed periodically
while the active server is running, detected that the device had been recovered, but the
restored path is in a state that is unable to update the disk.
cc....cc: Server alias name of the server that is using the shared disk of aa....aa.
S:
Resumes processing.
O:
Take one of the following actions, as indicated by the detail code:
Detail code
STANDBY_CHECK
ONLINE_CHECK
Corrective action
For a multipath configuration, check the path status by executing an HDLM or
DMMP command. If it is not restored to online status (failback), use an HDLM or
DMMP command to restore online status (failback).
No action is required if a multipath configuration is not used.
ONLINE_CHECK(NO_KEY)
As indicated by the content of message KAMN725-W, which is output before this
message, see the section on handling shared disk device failures in the manual HA
Monitor Cluster Software (for Linux(R) (x86) systems), and take the corrective action
described there.
KAMN728-W
A shared disk reserve for the server aa....aa is not released.
A shared disk reservation has not been released, because the status of another system cannot be checked, so releasing
the reservation might lead to corruption of data on the shared disk.
aa....aa: Server alias name
S:
Continues processing.
O:
See the recommended corrective actions to take in response to a server that has not released its reservation to a
shared disk in the manual HA Monitor Cluster Software (for Linux(R) (x86) systems). The above action is not
necessary if an active name with the server alias name is running on another system when the multi-standby
function is being used. In this case, ignore the message.
KAMN729-W
Execution of a SCSI command on the device:aa....aa ended abnormally. (details code:bb....bb, server:cc....cc, host
address:dd....dd (0xee....ee)).
A SCSI command execution error occurred on the standby server indicated by the server alias name. If the active
system fails, an attempt to start the switching-destination standby server might fail. This message is intended as a
status notification for the user and is output at a given interval.
112
2. Messages from KAMN000 to KAMN999
aa....aa: Name of the device specified in the server environment definition operand in which the error occurred
For details about device names, see the table under aa....aa in KAMN725-W.
bb....bb: See the detail codes in KAMN725-W.
cc....cc: Server alias name of the server that uses the shared disk indicated by aa....aa
dd....dd: See the table under dd....dd in KAMN725-W.
ee....ee: See the table under ee....ee in KAMN725-W.
S:
Continues processing.
O:
Contact a system administrator.
Action:
See the message KAMN725-W, which is output before this message, and eliminate the cause of the error.
KAMN730-E (E)
In the function definition statement in the definition file:sysdef, the ph_log_size operand is not specified.
The ph_threshold operand is specified in the HA Monitor environment settings, but the ph_log_size operand
is not.
S:
Terminates processing.
O:
Contact a system administrator.
Action:
To generate a monitoring log, specify the ph_log_size operand in the HA Monitor environment settings.
KAMN731-E (E)
In the function definition statement in the definition file:sysdef, the value specified in the ph_threshold operand is the
same as or more than the value specified in the patrol operand.
A value equal to or greater than the value specified for the patrol operand has been specified in the
ph_threshold operand in the HA Monitor environment settings.
S:
Terminates processing.
O:
Contact a system administrator.
Action:
Correct the HA Monitor environment settings so that the value specified for the ph_threshold operand is less
than the value specified in the patrol operand.
KAMN732-E (E)
For server aa....aa, in the definition file:servers the value specified in the ph_threshold operand is the same as or more
than the value specified in the patrol operand.
A value equal to or greater than the value specified for the patrol operand has been specified in the
ph_threshold operand in the server environment definition.
aa....aa: Server alias name
S:
Terminates processing.
O:
Contact a system administrator.
113
2. Messages from KAMN000 to KAMN999
Action:
Correct the server environment definition so that the value specified for the ph_threshold operand is less than
the value specified in the patrol operand.
KAMN733-E (E)
For server aa....aa, the ph_threshold operand is specified in the definition file:servers, but in the function definition
statement in the definition file:sysdef, the ph_log_size operand is not specified.
The server indicated in the server alias name specifies the ph_threshold operand in the server environment
definition, but does not specify the ph_log_size operand in the HA Monitor environment settings.
aa....aa: Server alias name
S:
Terminates processing.
O:
Contact a system administrator.
Action:
To generate a monitoring log, add the ph_log_size operand to the HA Monitor environment settings.
To not generate a monitoring log, delete the ph_threshold operand from the server environment definition.
KAMN740-I
The patrol history file has been backed up.
The monitoring log file has been backed up. Create a backup of (/opt/hitachi/HAmon/history/
patrol_history_old), if necessary.
S:
Continues processing.
KAMN741-E
The patrol history could not be acquired.
Cause:aa....aa
An attempt to access the monitoring log has failed. Access to the monitoring log is denied.
aa....aa: Cause code
Cause code
Meaning
OPEN
The monitoring log file failed to open.
WRITE
Writing to the monitoring log file failed.
BACKUP
Backup of the monitoring log file failed.
S:
Continues processing.
O:
Contact a system administrator.
Action:
Eliminate the source of the system call error as indicated by message KAMN601-W, which is output before this
message.
After eliminating the cause of the error, restart HA Monitor.
KAMN750-W
HAmonitor in host:aa....aa cannot system reset to own host.
114
2. Messages from KAMN000 to KAMN999
The version of HA Monitor on the host indicated by the host name is old, so a local system running a newer virtual
environment could not be reset.
aa....aa: Host name
S:
Continues processing.
O:
Upgrade the version of HA Monitor on the host indicated by the host name to one that supports the virtual
environment in which the local system is running. Alternatively, operate it in a different hot standby configuration
from that of the host indicated by the host name.
KAMN751-I
Initialization of performing a system reset of a virtual machine was completed.
The virtual machine has been reset.
S:
Continues processing.
KAMN752-E
There is a contradiction in the definition of Reset Path between host:aa....aa and own host. system name of own host:bb....bb
machine address of own host:cc....cc system name of host:aa....aa:dd....dd machine address of host:aa....aa:ee....ee
There is a conflict between the host indicated by the host name and the reset path of the local system. This message is
displayed in either of the following circumstances:
• If the managing system names of the remote and local system are different, but the machine addresses are the
same.
• If the managing system names of the remote and local system are the same, but the machine addresses are
different.
aa....aa: Host name
bb....bb: Local managing system name
cc....cc: Local machine address
dd....dd: Managing system name of the host indicated by the host name
ee....ee: Machine address of the host indicated by the host name
S:
Continues processing.
O:
Contact a system administrator.
Action:
Carefully review the host indicated by the host name and the settings of the local system reset path. After
correcting the managing system name or the machine address settings, restart the HA Monitor of the corrected
system.
KAMN755-I
HAmonitor connected to the VMware ESXi via Secure Shell. IP address of the VMware ESXi:aa....aa
HA Monitor is connected to VMWare ESXi via SSH.
aa....aa: IP address
S:
Continues processing.
KAMN757-W
The virtual machine name set to host:aa....aa overlaps each other. Virtual machine name:bb....bb
115
2. Messages from KAMN000 to KAMN999
The virtual machine name specified in the host indicated by the host name is the same as the local system settings. The
reset path settings are not correct, so the local or remote system might have been reset incorrectly.
aa....aa: Host name
bb....bb: Virtual machine name
S:
Continues processing.
O:
Contact a system administrator.
Action:
Check whether the virtual machine name of the local and remote systems are duplicated for all VMWare ESXi that
HA Monitor can connect to. If you change a virtual machine name, restart HA Monitor.
KAMN761-E
The function of HAmonitor Extension cannot be set. Error details:aa....aa
An error occurred when the HA Monitor Extension function was being initiated, so the function could not be set up.
aa....aa: Detail code (1 digit)
Detail code
Meaning
1
HA Monitor Extension is not installed.
2
HA Monitor is already running.
S:
Suspends processing.
O:
After eliminating the cause of the error based on the detail code, reinitiate the HA Monitor Extension function.
KAMN762-E
HA monitor Extension is not set. The function to specify cannot be used. Definition file: aa....aa bb....bb operand
The specified function cannot be used because the HA Monitor Extension function has not been set up.
aa....aa: Definition file name
bb....bb: Operand name
S:
Suspends processing.
O:
Carefully review the definition and set up the HA Monitor Extension function.
KAMN763-E
HAmonitor Extension is not installed, can not execute the command.
The command cannot be executed because HA Monitor Extension is not installed.
S:
Suspends processing.
O:
Install HA Monitor Extension.
116
2. Messages from KAMN000 to KAMN999
2.9 Messages from KAMN900 to KAMN999
KAMN931-I (S+L)
A server is the waiting for a premise server stop. server:aa....aa premise server:bb....bb group name :cc....cc
The server cannot stop because it is part of a group of servers that are being stopped in a specific sequence, and a
server that must stop earlier in the sequence has not stopped. The server is forced to wait for this parent server to stop.
aa....aa: Server alias name of the server forced to wait before it can be stopped
bb....bb: Server alias name of the server that must be stopped earlier
cc....cc: Server group name
S:
Forces the server to wait for the parent server to stop, and then restarts termination processing of the pending
server after termination of the parent server completes.
KAMN932-I (S+L)
A server is the waiting for premise server starting. server:aa....aa premise server:bb....bb group name:cc....cc
The server cannot start because it is part of a group of servers that are being started in a specific sequence, and a server
that must start earlier in the sequence has not started. The server is forced to wait for this parent server to start.
aa....aa: Server alias name of the server forced to wait before it can be started
bb....bb: Server alias name of the server that must be started earlier
cc....cc: Server group name
S:
Forces the server to wait for the parent server to start, and then restarts startup processing of the pending server
after startup of the parent server completes.
KAMN933-E
All of servers which are waiting for start are stopped, because premise server:aa....aa stopped abnormally.
All servers in the server start wait state are stopped because the parent server has terminated abnormally.
aa....aa: Server alias name of the server that terminated abnormally and must be restarted
S:
Continues processing.
O:
Determine the reason the parent server terminated abnormally.
KAMN934-W
Server: aa....aa would start according to order control although premise server: bb....bb does not meet the condition of order
control.
Server startup processing continues regardless of the status of the server's parent server, because the parent server is
not running.
aa....aa: Server alias name of server
bb....bb: Server alias name of the parent server that must be started earlier
S:
Continues processing.
O:
Start the parent server, if necessary.
KAMN936-I (S)
resource server has not started. server is made the waiting for start. server:aa....aa premise server:bb....bb group name:cc....cc
A resource server has not started before the server to start, so the server must wait for the resource server to start.
117
2. Messages from KAMN000 to KAMN999
aa....aa: Server alias name of the server waiting for the resource server
bb....bb: Server alias name of resource server
cc....cc: Server group name
S:
Forces the server to wait for the resource server to start, and then restarts server startup processing after the
resource server starts.
KAMN937-E
An error occurred in group resource process, server activation is stopped. server:aa....aa group name:bb....bb
A server could not start because processing of the resources being used by the group has failed.
aa....aa: Server alias name of the server that terminated startup processing
bb....bb: Server group name
S:
Terminates server start processing.
O:
Eliminate the cause of the error, and then restart the server.
KAMN944-E (E)
server: aa....aa is not grouped.
The server specified in the command option is not part of the group.
aa....aa: Server alias name
S:
Stops command processing.
O:
The executed command cannot be used on servers that are not part of the group. Check for errors in the command
syntax or server alias name, and then re-execute the command.
KAMN950-I (S)
Order Information
group name: aa....aa
alias: bb....bb parent: cc....cc
This is the information that is displayed by the command for displaying the server order control status (monodrshw).
aa....aa: Group name
bb....bb: Server alias name
cc....cc: The server's parent server
Server alias name: Displayed if a parent server has been specified.
none: Displayed if no parent server has been specified.
S:
Continues processing.
KAMN952-I (S)
Usage: monodrshw -s alias
monodrshw -g group
This message is output after message KAMN021-E or message KAMN327-E when the syntax of the command for
displaying the server order control status (monodrshw) is incorrect.
S:
Stops command processing.
118
2. Messages from KAMN000 to KAMN999
KAMN953-E (E)
server:aa....aa is a resource server. It cannot start in monbegin.
The command could not be executed because the server indicated by the server alias name is a resource server.
aa....aa: Server alias name
S:
Terminates command processing.
O:
Start the resource server using the resource server start command (monresbgn).
KAMN954-E (E)
server:aa....aa is not a resource server. It cannot start in monresbgn.
The command could not be executed because the server indicated by the server alias name is not a resource server.
aa....aa: Server alias name
S:
Terminates command processing.
O:
Start the server using the monitor-mode server start command (monbegin).
KAMN955-E (E)
server:aa....aa is a resource server. It cannot stop in monend.
The command could not be executed because the server indicated by the server alias name is a resource server.
aa....aa: Server alias name
S:
Terminates command processing.
O:
Use the active resource server termination command (monresend) to stop the server.
KAMN956-E (E)
server:aa....aa is not a resource server. It cannot stop in monresend.
The command could not be executed because the server indicated by the server alias name is not a resource server.
aa....aa: Server alias name
S:
Terminates command processing.
O:
Use the monitor-mode server termination command (monend) to stop the server.
KAMN957-E (E)
server:aa....aa is a resource server. It cannot stop in monsbystp.
The command could not be executed because the server indicated by the server alias name is a resource server.
aa....aa: Server alias name
S:
Terminates command processing.
O:
Use the standby resource server termination command (monressbystp) to stop the server.
119
2. Messages from KAMN000 to KAMN999
KAMN958-E (E)
server:aa....aa is not a resource server. It cannot stop in monressbystp.
The command could not be executed because the server indicated by the server alias name is not a resource server.
aa....aa: Server alias name
S:
Terminates command processing.
O:
Use the standby server termination command (monsbystp) to stop the server.
KAMN959-E (E)
The resource server is already defined by the group:bb....bb of server:aa....aa.
A resource server is already defined in the group that includes the resource server indicated by the server alias name.
aa....aa: Server alias name
bb....bb: Server group name
S:
Terminates processing.
O:
Carefully review the server environment definition, and correct any errors as necessary.
KAMN961-E (E)
Order control relation of server:aa....aa is incorrect.
There is an error in the sequencing relationship that includes the server indicated by the server alias name.
aa....aa: Server alias name
S:
Terminates processing.
O:
Carefully review the server environment definition, and correct any errors as necessary.
KAMN963-E (E)
Since a server while using a resource is, server:aa....aa cannot be stopped.
Termination of the server indicated by the server alias name was stopped because a server that uses the resource is
running.
aa....aa: Server alias name
S:
Terminates processing.
O:
Terminate the server that is using the resource, and then terminate the server indicated by the server alias name.
KAMN964-E
The command:cc....cc specified as the bb....bb operand of program:aa....aa does not exist or execution of this command is not
permitted.
The command specified in the operand indicated by the operand name of the program indicated by the program alias
name either does not exist or does not have permission to execute. Another possibility is that a directory was
specified.
aa....aa: Program alias name
bb....bb: Operand name
cc....cc: Path name of command
120
2. Messages from KAMN000 to KAMN999
S:
Terminates processing.
O:
Check the following items, and then restart the server:
• Has the command indicated by the command name been created?
• Does it have permission to execute?
• Has a directory been specified as the path name of the command?
KAMN965-E (E)
The program defining statement to specify the server:aa....aa for server_alias operand doesn't exist though the
server:aa....aa uses the function of program.
The server indicated by the server alias name has specified use in the program operand in the server environment
definition. However, there is no program definition statement that specifies the server indicated by the server alias
name in the server_alias operand of the monitor-mode program environment definition.
aa....aa: Server alias name
S:
Terminates processing.
O:
Carefully review the server environment definition and the monitor-mode program environment definition, and
correct any errors as necessary.
KAMN966-I
For program:aa....aa, the server:bb....bb specified in the program operand is not defined in the server definition sentence or
cannot use the function of program.
The specification of the server set to manage the program indicated by the program alias name has one of the
following errors:
• The server definition statement of the server environment definition has not been defined.
• monitor has not been specified in the acttype operand of the server environment definition.
• The program operand of the server environment definition has not been specified.
aa....aa: Program alias name
bb....bb: Server alias name
S:
Continues processing.
O:
Check for errors in the program operand of the server environment definition or in the server_alias
operand of the monitor-mode program environment definition.
KAMN967-E (E)
The number of program belong the server:aa....aa has exceeded the number of the pgmmax operand.
Processing was terminated, because the number of programs managed by the server indicated by the server alias name
has exceeded the value of the pgmmax operand in the HA Monitor environment settings.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check for errors in the pgmmax operand and the monitor-mode program environment definition.
121
2. Messages from KAMN000 to KAMN999
KAMN968-I (S)
The total number of program belong each servers in definition file:servers has exceeded the number of the pgmmax operand.
The total number of programs managed by all servers defined in the server environment definitions has exceeded the
value of the pgmmax operand in the HA Monitor environment settings.
S:
Continues processing.
O:
Take the follow corrective action, and then restart HA Monitor or the servers:
• Carefully review the definition of the pgmmax operand in the HA Monitor environment definition to ensure
the number of programs managed by servers does not exceed that specified in the pgmmax operand.
• Correct the monitor-mode program environment definition.
KAMN969-E (E)
Definition file:programs, The method of a definition of the server:aa....aa is incorrect. Command processing is stopped.
An error occurred during analysis of the monitor-mode program environment definition. Processing for the server
indicated by the server alias name specified in the HA Monitor command was terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Correct the monitor-mode program environment definition, and then restart the server.
KAMN970-E
Since a server:aa....aa starting priority overlaps other systems, therefore starting of server is stopped.
The switchover priority of the server is the same as that of a remote system. Startup of the server indicated by the
server alias name was terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Correct the server environment definition, and then restart the server.
KAMN971-E
Server:aa....aa online server is executed by two or more of other systems, therefore starting of server is stopped.
It was determined at server startup that the active server is running on multiple systems. Startup of the server indicated
by the server alias name was terminated.
aa....aa: Server alias name
S:
Terminates processing.
O:
Stop the active server on the remote system and contact a system administrator.
Action:
Determine the resources that were being used by the active server, confirm that the resources do not have any
problems, and then restart the server.
KAMN972-D (S+L)
Server:aa....aa non-connected host exists. it was made a start wait state.
122
2. Messages from KAMN000 to KAMN999
An unconnected host was detected at server startup. The server indicated by the server alias name has been placed in
the standby server startup wait-state.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check all the connections between systems of HA Monitor. Connections between systems can be checked with the
server and host status display command (monshow) or the monitoring path status display command (monpath).
If the check shows that no active servers are running on remote systems, the wait-state server startup (the monact
command) can be executed to make this server into an active server. If active servers are running on remote
systems, execute the wait-state server stop command (mondeact) to stop this server.
KAMN973-D (S+L)
Server:aa....aa The host who failed in reset exists. server state is not able to be check. it was made a start wait state.
A host that failed to reset and is waiting to be started as an active server was detected at server startup. The server
indicated by the server alias name has been placed in the standby server startup wait-state.
aa....aa: Server alias name
S:
Terminates processing.
O:
After checking the status of each system, start the server in the startup wait-state as the active server using the
wait-state server start command (monact), or force it to stop using the wait-state server stop command
(mondeact).
KAMN974-E (E)
Online server : aa....aa is started in other systems. Command(bb....bb) cannot be executed.
When active servers are running on remote systems, the wait-state server stop command (mondeact) cannot be
executed.
aa....aa: Server alias name
bb....bb: Command name
S:
Stops command processing.
O:
Check the server statuses of each system.
KAMN975-D
Server : aa....aa is made to stop normally, because system reset is failed.
The standby server indicated by the server alias name was forcibly terminated because a system reset failed to
execute.
aa....aa: Server alias name
S:
Terminates processing.
O:
Check the status of the host on which the error occurred. If the standby server was terminated by the host on
which the error occurred, the standby server can be started, if necessary. Restart the standby server, if necessary.
KAMN977-W
The definition of host:aa....aa is different. Detailed information:bb....bb
123
2. Messages from KAMN000 to KAMN999
The settings for the HA Monitor on the local host differ from the settings for the HA Monitor of the host indicated by
the host name.
aa....aa: Host name
bb....bb: Detailed information
PATROL: The system failure monitoring period is different.
RESETPATH: The hot standby mechanisms specified in the reset path and alternate reset path are different.
MULTICAST: The multicast settings are different.
PATROL_TYPE: Monitor timing interval settings are different.
FENCE_TYPE: The methods set for protecting data on shared disks are different.
S:
Continues processing.
O:
Take one of the following actions, as indicated by the detailed information:
Detailed information
PATROL
Corrective action
Carefully review the definition file, correct definitions as needed, and then restart HA Monitor.
Alternatively, execute the command for changing settings while HA Monitor and servers are
running (monchange), and make the system failure monitoring periods the same for both
systems.
RESETPATH
Make the reset path and alternate reset path the same, and then restart HA Monitor.
MULTICAST
Make the values specified for the hostmax, alive_multicast, and multicast_lan
operands of the HA Monitor environment settings the same for both systems, and then restart
HA Monitor.
PATROL_TYPE
Make the values specified for the patrol_type operand of the HA Monitor environment
settings the same for both systems, and then restart HA Monitor.
FENCE_TYPE
Make the values specified for the fence_reset, fence_scsi, and fence_lan operands
of the HA Monitor environment settings the same for both systems, and then restart HA
Monitor.
KAMN978-I (S)
Usage:monchange -m operand value
monchange -s alias operand value
monchange -p program alias operand value
This message is output after message KAMN021-E or message KAMN392-E when the syntax of the command for
changing settings while HA Monitor and servers are running (monchange) is incorrect.
S:
Continues processing.
KAMN980-W
HAMON_UAPNAME: aa....aa An error occurred in the bb....bb system call. Error details:cc....cc dd....dd
An error occurred in a system call invoked within an API process. For more information about detail codes and detail
messages, see the documentation for the applicable OS.
aa....aa: Program name (Specification for HAMON_UAPNAME environment variable. If more than 32 characters are
specified, only the final 32 are displayed.)
bb....bb: System call invoked
cc....cc: Detail code (errno of system call, 1 to 3 digits. If 0, the detail message is displayed)
dd....dd: Detail message
S:
Continues processing.
124
2. Messages from KAMN000 to KAMN999
O:
Take one of the following actions, as indicated by the system call displayed:
System call
Corrective action
dlopen
Stop the UAP and eliminate the cause of the error displayed in the detail message. If HA
Monitor is not installed, or the installed HA Monitor is a version that cannot monitor UAPs,
install and set up a version that supports such monitoring.
connect
Stop the UAP and eliminate the cause of the error displayed in the detail code.
If the detail code is 2, HA Monitor is not running, or HA Monitor is a version that does not
allow UAP monitoring. Restart the UAP, if necessary.
write
Stop the UAP and eliminate the cause of the error displayed in the detail code.
If the detail code is 2, HA Monitor is not running. Restart the UAP, if necessary.
read
Stop the UAP and eliminate the cause of the error displayed in the detail code.
If the detail code is 2, HA Monitor is not running. Restart the UAP, if necessary.
Other
Stop the UAP and eliminate the cause of the error displayed in the detail code. Restart the
UAP, if necessary.
KAMN981-E
While processing API an error occurred. Cause: aa....aa Details: bb....bb
An error occurred during API processing.
aa....aa: Cause code
Cause code
1
Meaning
One of the following was detected. NO UAP name is output in the detail information.
• The HAMON_UAPNAME environment variable was not specified.
• No value was specified for the HAMON_UAPNAME environment variable.
• The value specified for the HAMON_UAPNAME environment variable exceeds 1,000 characters in
length.
bb....bb: Detailed information
S:
HA Monitor is deactivated.
Action:
Take the following action:
Cause code
1
Corrective action
Enter the program name specified in the name operand of the monitor-mode program
environment definition in the HAMON_UAPNAME environment variable.
125
Appendixes
127
A. Version Changes
A. Version Changes
The following sections describe the changes made to the various versions.
A.1 Changes made to the Linux (x86) edition of HA Monitor 01-57
(3000-9-134-N0(E))
The following table describes the changes made to the Linux (x86) edition of HA Monitor 01-57 (3000-9-134-N0(E)):
Description of additions and changes
Message details were consolidated into Chapter 2.
The following messages were changed:
KAMN194-W, KAMN206-E, KAMN246-W, KAMN302-W, KAMN324-W, KAMN343-W, KAMN377-E, KAMN423-E, KAMN460-E,
KAMN474-E, KAMN475-E, KAMN513-E, KAMN529-I, KAMN530-E, KAMN690-W, KAMN693-W, KAMN694-W, KAMN696-W
The following message was deleted:
KAMN527-W
A.2 Changes made to the Linux (x86) edition of HA Monitor 01-56
(3000-9-134-M0(E))
The following table describes the changes made to the Linux (x86) edition of HA Monitor 01-56 (3000-9-134-M0(E)):
Description of additions and changes
The following messages were added:
KAMN066-E, KAMN164-E, KAMN235-I, KAMN528-I, KAMN529-I, and KAMN530-E
The following messages were changed:
KAMN153-E, KAMN154-E, KAMN157-E, KAMN158-E, KAMN159-E, KAMN161-E, KAMN162-E, KAMN514-E, and KAMN977-W
(Linux (x86))
Because support was added for a function that automatically retries starting a server during a hot standby, the following messages were
added:
KAMN296-I and KAMN334-I
Additionally, the following messages were changed:
KAMN273-E, KAMN276-E, KAMN300-E, KAMN301-E, KAMN305-E, KAMN312-E, KAMN315-E, and KAMN514-E
Because it was made possible to output a message when server stoppage or grouped-system switchover is complete, the following
messages were added:
KAMN298-I and KAMN496-I
Because notification processing for the hot standby disabled state was improved, the messages listed below were added for the Linux
(x86) edition. These messages are warning messages that are output at a set interval.
KAMN288-W, KAMN447-W, KAMN644-W, and KAMN729-W
Because the processing following a failure to disconnect an FS during a hot standby was improved, the message listed below was added
for the Linux (x86) edition. This message is a warning message that is output when a VG disconnection process is skipped.
KAMN291-W
The following message was enhanced with an explanation about a case in which the multi-standby function is being used, and an active
server with a server alias name is running on a remote system:
KAMN728-W
128
A. Version Changes
Description of additions and changes
Because support was added for HDLM as multipath software, the explanation of the following message for the Linux (x86) edition was
changed:
KAMN113-E
Additionally, the explanations of the following messages were changed:
KAMN725-W, KAMN726-E, and KAMN727-I
Because a change was made to enable SCSI Reserve for a shared disk in a virtual environment based on VMware ESXi, the explanation of
the following message was changed:
KAMN165-E
Because a change was made to enable monitoring of hbonding in the 802.3ad mode, the following message was added for the Linux
(x86) edition:
KAMN516-E
Additionally, the explanation of the following message was changed:
KAMN523-E
The explanation of the following message for the Linux (x86) edition was changed:
KAMN624-E
Because a change was made to make it possible to tell whether specification of the address operand is duplicated, the following
message was added for the Linux (x86) edition:
KAMN414-E
129
B. Reference Material for This Manual
B. Reference Material for This Manual
This appendix provides reference information, including various conventions, for this manual.
B.1 Related publications
This manual is part of a related set of manuals. The other manual in the set is listed below (with the manual number):
• HA Monitor Cluster Software Guide (3000-9-140(E)), for Linux(R) (x86) systems
Manuals other than HA Monitor manuals that are related to this manual are listed below (with the manual numbers).
Refer to these manuals as necessary.
If you are using OpenTP1
• OpenTP1 Version 5 Description (3000-3-360(E))
• OpenTP1 Version 5 System Definition (3000-3-362(E))
• OpenTP1 Version 5 Operation (3000-3-363(E))
• OpenTP1 Version 5 TP1/Client User's Guide (3000-3-364(E))
• OpenTP1 Version 5 Messages (3000-3-368(E))
• OpenTP1 Version 6 Description (3000-3-941(E))
• OpenTP1 Version 6 System Definition (3000-3-943(E))
• OpenTP1 Version 6 Operation (3000-3-944(E))
• OpenTP1 Version 6 Messages (3000-3-947(E))
• OpenTP1 Version 6 TP1/Client User's Guide TP1/Client/W.P (3000-3-949(E))
• OpenTP1 Version 6 TP1/Client User's Guide TP1/Client/J (3000-3-950(E))
• OpenTP1 Version 7 Description (3000-3-D50(E))
• OpenTP1 Version 7 System Definition (3000-3-D52(E))
• OpenTP1 Version 7 Operation (3000-3-D53(E))
• OpenTP1 Version 7 Messages (3000-3-D56(E))
• OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/W.P (3000-3-D58(E))
• OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J (3000-3-D59(E))
If you are using HiRDB
• HiRDB Version 6 Description (3000-6-231(E))
• HiRDB Version 6 Installation and Design Guide (3000-6-232(E))
• HiRDB Version 6 System Definition (3000-6-233(E))
• HiRDB Version 6 System Operation Guide (3000-6-234(E))
• HiRDB Version 6 Command Reference (3000-6-235(E))
• HiRDB Version 6 Messages (3000-6-238(E))
• HiRDB Version 7 Description (3000-6-271(E))
• HiRDB Version 7 Installation and Design Guide (3000-6-272(E))
• HiRDB Version 7 System Definition (3000-6-273(E))
• HiRDB Version 7 System Operation Guide (3000-6-274(E))
• HiRDB Version 7 Command Reference (3000-6-275(E))
• HiRDB Version 7 Messages (3000-6-278(E))
• HiRDB Version 8 Description (3000-6-351(E)), for UNIX systems
130
B. Reference Material for This Manual
• HiRDB Version 8 Installation and Design Guide (3000-6-352(E)), for UNIX systems
• HiRDB Version 8 System Definition (3000-6-353(E)), for UNIX systems
• HiRDB Version 8 System Operation Guide (3000-6-354(E)), for UNIX systems
• HiRDB Version 8 Command Reference (3000-6-355(E)), for UNIX systems
• HiRDB Version 8 Messages (3020-6-358(E))
• HiRDB Version 9 Description (3000-6-451(E)), for UNIX systems
• HiRDB Version 9 Installation and Design Guide (3000-6-452(E)), for UNIX systems
• HiRDB Version 9 System Definition (3000-6-453(E)), for UNIX systems
• HiRDB Version 9 System Operation Guide (3000-6-454(E)), for UNIX systems
• HiRDB Version 9 Command Reference (3000-6-455(E)), for UNIX systems
• HiRDB Version 9 Messages (3020-6-458(E))
If you are automating system operation through event management
• JP1 Version 7i JP1/Base (3020-3-F04(E))
• Job Management Partner 1/Base User's Guide (3020-3-K06(E))
• Job Management Partner 1/Base Messages (3020-3-K07(E))
• JP1 V9 Job Management Partner 1/Base User's Guide (3020-3-R71(E))
• JP1 V9 Job Management Partner 1/Base Messages (3020-3-R72(E))
• JP1 V10 Job Management Partner 1/Base User's Guide (3021-3-001(E))
• JP1 V10 Job Management Partner 1/Base Messages (3021-3-002(E))
For disk path redundancy
• Hitachi Dynamic Link Manager Software User's Guide (3000-3-F04(E)), for Linux(R) systems
If hot standby is performed in an N+M cold standby configuration
• ServerConductor/Blade Server Manager Series Administration Guide (3020-3-L52(E))
B.2 Conventions: Abbreviations for product names
This manual uses the following abbreviations for product names:
Abbreviation
Full name or meaning
HCSM
Hitachi Compute Systems Manager
HDLM
Hitachi Dynamic Link Manager Software
JP1/ServerConductor
JP1/ServerConductor/Advanced Agent
JP1/ServerConductor/Agent
JP1/ServerConductor/Blade Server Manager
JP1/ServerConductor/Blade Server Manager Plus
JP1/ServerConductor/Server Manager
Linux
Linux
Linux(R)
Linux (x86)
Red Hat Enterprise Linux AS 3 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux AS 3 (x86)
131
B. Reference Material for This Manual
Abbreviation
Full name or meaning
Red Hat Enterprise Linux AS 4 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux AS 4 (x86)
Red Hat Enterprise Linux ES 3 (x86)
Red Hat Enterprise Linux ES 4 (AMD64 & Intel EM64T)
Red Hat Enterprise Linux ES 4 (x86)
Red Hat Enterprise Linux 5 (x86)
Red Hat Enterprise Linux 5 Advanced Platform (x86)
Red Hat Enterprise Linux 5 (AMD/Intel 64)
Red Hat Enterprise Linux 5 Advanced Platform (AMD/Intel 64)
Red Hat Enterprise Linux Server 6 (x86)
Red Hat Enterprise Linux Server 6 (x86_64)
UNIX
UNIX(R)
VMware ESXi
VMware ESXi
VMware vSphere(R) ESXi(TM)
B.3 Conventions: Acronyms
This manual also uses the following acronyms:
Acronym
Full name or meaning
API
Application Programming Interface
CPU
Central Processing Unit
DB
Database
DMMP
Device Mapper Multipath
EUC
Extended UNIX Code
HA
High Availability
HRA
Health-check and Reset Adaptor
IPF
Itanium(R) Processor Family
LA
Line Adaptor
LAN
Local Area Network
LPAR
Logical Partitioning
LVM
Logical Volume Manager
NLS
National Language Support
OA
Onboard Administrator
OS
Operating System
OSI
Open Systems Interconnection
PA-RISC
Precision Architecture - Reduced Instruction Set Computer
132
B. Reference Material for This Manual
Acronym
Full name or meaning
PV
Physical Volume
SCSI
Small Computer System Interface
SP
Service Processor
SSH
Secure Shell
SVP
Service Processor
TCP/IP
Transmission Control Protocol/Internet Protocol
UTF-8
8-bit UCS Transformation Format
XNF
Extended Hitachi Network Architecture Based Communication Networking Facility
B.4 Conventions: KB, MB, GB, and TB
This manual uses the following conventions:
• 1 KB (kilobyte) is 1, 024 bytes.
• 1 MB (megabyte) is 1, 0242 bytes.
• 1 GB (gigabyte) is 1, 0243 bytes.
• 1 TB (terabyte) is 1, 0244 bytes.
133
C. Glossary
C. Glossary
abort code
Cause code for abnormal termination of a UNIX system.
active server
The server that is currently performing job processing.
active server start wait state
When a standby server is to be started, it might not always be possible for some reason to confirm that the active server has started on the
remote host. In such a case, HA Monitor places the startup processing on the standby server in the wait state until the status of the active
server can be confirmed. Such a standby server is called being in the active server start wait state. A standby server in the start wait state
waits for a user intervention. When the active server startup processing is confirmed to have started, HA Monitor then starts the standby
server.
active system
The system (host) that is performing job processing by running an active server.
alias IP address function
A function that enables multiple IP addresses to be assigned to a single LAN adapter so that the LAN adapter can be shared through the
use of different IP addresses.
alive message
A message that is issued between hosts at a specified interval to determine whether the target host is running normally.
chassis
A rack that houses a computer and its peripheral equipment. When the system being used is BladeSymphony, this rack is called a chassis.
Multiple systems can be configured in one chassis.
child server
A server whose startup processing begins after its parent server has started. This corresponds to a child in the parent-child relationship in
server groups.
client
A machine (node) that uses various services provided by programs.
cluster configuration
A system configuration that is larger than one server system. Multiple server systems are connected via high-speed LANs and processing
is distributed among different server systems. A client can perform processing by treating these server systems as a single server system.
core file
An OS-specific file in which memory information (module trace information) for a process is stored in the event the program terminates
abnormally. Core files might not always be created. If an error occurs in a user-created program and its core file is available, the user can
use OS commands to debug the program.
dual server system
A system that improves reliability and availability of the entire system by providing two sets of machines, programs, and resources for the
system on which a server is run (or by sharing dual resources).
event ID
A number assigned to each event in order to individually manage the events that occur in a UNIX system.
grouped-system switchover
A function that groups multiple servers together in advance, allowing operations to be switched over to a standby server for that group if a
failure occurs on any of the active servers in the group (server group). HA Monitor enables the user to specify hot standby processing for
each server within the server group.
grouped-system switchover wait state
If a server failure occurs on an active server for which no_exchange is specified for the group operand of the server environment
definition, HA Monitor delays hot standby processing on the standby server in the standby system. This status for a standby server is
called the grouped-system switchover wait state. A standby server in the grouped-system switchover wait state waits for a user
134
C. Glossary
intervention. However, if a server failure occurs on an active server for which exchange is specified in the group, grouped-system
switchover is also performed on the standby server in the grouped-system switchover wait state.
HA Monitor Extension
An HA Monitor optional product. When HA Monitor Extension is installed, hot standby control in a large system configuration can be
supported. HA Monitor Extension can be used when the OS is Linux (x86).
host
A unit for a system in which one server is run per CPU. The hardware making up a system and the programs that are run on the system
are referred to collectively as a host.
host slowdown
An event in which the execution time on the entire host becomes longer than usual. Its causes include concurrent execution of too many
programs or a failure in communication between programs.
hot standby
A function for switching jobs to a standby system (host) or server if a failure occurs on the primary system (host) or server.
hot-standby wait-state
If the standby system fails to reset the active system after a failure on the active system, and the active server is started on the standby
system while the status of the active server cannot be verified, two active servers might result. To avoid this, HA Monitor delays startup of
the active server on the standby system. This status at the active server is called the hot-standby wait-state. A server in the hot-standby
wait-state cannot be started as an active server without user intervention.
IP address
An address used with the IP protocol. The IP protocol corresponds to the network layer in the OSI basic reference model. The network
layer manages addresses used to establish data transfer paths and to determine paths.
kernel
The core program of an OS. Its roles include management of tasks, memory, and I/O operations.
LAN adapter
Data conversion hardware used to connect a computer and a LAN.
lock
A control to prevent concurrent updating and deadlock on system resources when multiple requests for the same system resources result
in contention. In HA Monitor, a function that prevents shared disks from being updated concurrently from both the active server and a
standby server is called the lock function.
locked server
If multiple standby servers provide separate services to the standby system, the user can prevent multiple active servers from being run
concurrently after hot standby processing.
When a standby server operates as an active server, HA Monitor stops all other standby servers running on the same host. Such a standby
server that is terminated by HA Monitor is called a locked server.
LVM
Abbreviation for Logical Volume Manager, which is a kernel functions. LVM enables the user to group several physical disk devices
together as a volume group and assign to them any number and size of logical volumes.
message log
An OS function that stores issued messages in a specific file (message log file).
module trace information
A flow of module processing in HA Monitor that is collected in a module trace buffer (core file). The module trace information is first
transferred to a portable medium and then is analyzed.
monitor mode
One of the server operation modes. A server in the monitor mode cannot use some of the HA Monitor functions, such as starting a server
on the standby server beforehand or monitoring for server failures. However, the monitor-mode program management function makes
some of those unavailable HA Monitor functions available.
135
C. Glossary
multi-standby function
A function for providing multiple standby servers for one active server.
This function can protect against a system failure while the primary system is recovering from a failure, in contrast to when only one
standby server is provided per active server.
N+M cold standby configuration
A system configuration for BladeSymphony in which JP1/ServerConductor or HCSM is used to switch from the primary server module to
a standby server module when a hardware failure occurs on the primary server module that was performing job operations. Because one
or more standby server modules are provided, reliability is improved for handling failures.
operation report
Information that is sent from a server to HA Monitor at specific intervals. HA Monitor monitors the server based on this information.
OS panic
An OS kernel panic.
parent server
A server that must be active so that another server can be started or hot standby processing can be started. This corresponds to the parent
in the parent-child relationship in server groups, and it is specified in the server environment definition.
partition
A function that divides a server machine into multiple sections and runs each section as a virtual server is called partitioning. Each such
section is called a partition.
In BladeSymphony, which enables multiple processors to be installed in a single chassis, each processor is sometimes called a partition.
Hitachi server virtualization enables logical partitions (LPARs) to be configured within a processor.
portable medium
A storage medium, such as DAT, that enables programs and data to be recorded and transported.
primary system
The system (host) that performs job processing when it is started.
program
The program (application) that actually executes jobs. HA Monitor improves system reliability by employing hot-standby configurations
to achieve dual programs.
Programs can be classified into two types, programs with an HA Monitor interface and programs without an HA Monitor interface.
program with an HA Monitor interface
A program that has a dedicated HA Monitor interface. When a program with an HA Monitor interface is run in the server mode, HA
Monitor monitors both host failures and server failures.
HA Monitor monitors a program with an HA Monitor interface and performs hot standby processing in the event of a failure that cannot
be detected by the program.
program without an HA Monitor interface
A program that does not have a dedicated HA Monitor interface. Some of the HA Monitor functions are not available, including the
function for starting programs on the standby system in advance and the function for monitoring server failures.
There is no difference in functional limitations between using programs without an HA Monitor interface and running programs with an
HA Monitor interface in the monitor mode.
resource server
A server used only for sharing resources among multiple servers. A resource server does not provide server functions.
Shared resources are controlled for each server when no resource server is used, while shared resources are controlled for each server
group when a resource server is used.
restart wait state
If a server failure occurs on an active server for which restart or manual is specified in the switchtype operand in the server
environment definition, HA Monitor waits until the active server is restarted without terminating it. Such a status for an active server is
called the restart wait state.
secondary system
A system (host) that is placed on standby mode when it is started.
136
C. Glossary
server
A service that processes jobs in accordance with requests. In this manual, a program as a unit of hot standby processing is called a server.
Servers are classified roughly as server-mode servers and monitor-mode servers.
server inheritance information
Information that is inherited from an active server to a standby server when pairing is established between the active server and the
standby server. If information needs to be transmitted between servers within a user command, HA Monitor's moninfo -p command
(command for specifying and displaying server inheritance information) is used to specify the information beforehand, and then the
moninfo -g command is used to reference and display the information.
server mode
A server operation mode that can be selected when the program has an interface with HA Monitor. When a server is run in the server
mode, HA Monitor monitors both host failures and server failures.
server slowdown
An event where the server execution time becomes longer than usual. Its causes include program looping and resource contention.
shared resource
A resource, such as shared disks and LANs, that can be shared between the active and a standby system. The shared resources controlled
by HA Monitor include shared disks, file systems, LANs, and communication lines. HA Monitor controls shared resources for each
server.
A resource server can also be used to share resources among server groups.
standby server
A server currently on standby in the event of a failure on the active server.
standby system
A system (host) that is running a standby server that is on standby ready to take over in the event of a failure.
system dump
An OS function for storing on a portable medium error information that cannot be narrowed down to a specific program. Memory
information, information about swap area (virtual memory), and processor-specific information can be collected in a system dump. In
general, a system dump is used when the cause of an error in the system cannot be identified.
TCP/IP
A standard communication protocol used for connection between UNIX computers. TCP/IP supports both the TCP protocol and the IP
protocol.
UAP
A user's job created as a program. UAPs can be used as programs on a server in the monitor mode. HA Monitor can monitor UAPs by
having the UAPs issue APIs.
user command
A command created by a user. A user command that has been registered into HA Monitor in advance can be issued automatically when
HA Monitor processing is triggered by a change in the server status. User commands enable the user to use as shared resources various
resources that are not controlled by HA Monitor.
137
Index
A
abbreviations for products
acronyms 132
131
C
conventions
abbreviations for products 131
acronyms 132
fonts and symbols I
KB, MB, GB, and TB 133
version numbers II
F
font conventions
I
G
GB meaning
133
K
KB meaning
133
M
MB meaning
133
S
symbol conventions
I
T
TB meaning
133
V
version number conventions
II
139