A. Event IDs Used by HA Monitor
You can link HA Monitor to JP1 products to achieve system automation. If events such as HA Monitor startup or server abnormal termination occur, HA Monitor issues events to notify JP1.
The events issued by HA Monitor are managed by JP1/Base. For details about event management, see the JP1/Base User's Guide.
This section explains the JP1 events that are issued by HA Monitor. You can use a program such as the integrated JP1 management window to check the items listed below.
- Event ID
-
Displays the JP1 event ID assigned to HA Monitor.
- Corresponding HA Monitor message
-
Displays the HA Monitor message ID and message text that correspond to the event.
- Severity
-
Displays the severity level of the event in JP1. One of the following strings is displayed:
-
Error
Error
-
Warning
Warning
-
Information
Information
-
- User name
-
Displays a superuser name.
- Product name
-
Displays /HITACHI/HAmon.
- Object type
-
Displays the type of the HA Monitor object that caused the JP1 event to be issued. One of the following strings is displayed:
-
HAHOST
Event related to HA Monitor itself
-
HASERV
Event related to a server
-
HARESET
Event related to a reset path
-
HAPATH
Event related to a monitoring path
-
HASERVPATH
Event related to a server path error
-
- Object name
-
Displays the object name that corresponds to the object type. One of the following strings is displayed:
-
HA Monitor's host name
This is an object that corresponds to HAHOST.
-
Server alias name or server path name
This is an object that corresponds to HASERV.
-
HA Monitor's host name at the reset target
This is an object that corresponds to HARESET.
-
Host name of the monitoring path
This is an object that corresponds to HAPATH.
-
Server path name
This is an object that corresponds to HASERVPATH.
-
- Registration name type
-
Displays HAmon.
- Registration name
-
Displays the host name for the HA Monitor that issued the event.
- Event type
-
Displays the status of the object set by the object type in which the event is issued. One of the following strings is displayed:
-
START
The object was started.
-
END
The object was terminated
-
NOTSTART
The object could not be started.
-
RESTART
Re-execution of the object was started.
-
SWITCH
Hot standby processing occurred.
-
NOTICE
The user is being notified of the event.
-
EXCEPTION
Other error occurred.
-
- Start time
-
Displays the time the event occurred.
The following table lists the event items whose contents depend on the event.
Event issuance timing |
Event ID |
Corresponding HA Monitor message |
Severity |
Object type |
Object name |
Event type |
---|---|---|---|---|---|---|
When HA Monitor starts |
00010200 |
KAMN002-I |
Information |
HAHOST |
HA Monitor's host name |
START |
When HA Monitor terminates normally |
00010201 |
KAMN050-I |
Information |
END |
||
KAMN056-I |
||||||
When HA Monitor terminates abnormally |
00010202 |
KAMN003-E#1 |
Error |
NOTSTART |
||
KAMN205-E |
||||||
KAMN207-E |
||||||
KAMN208-E |
||||||
KAMN617-E |
EXCEPTION |
|||||
When a server starts |
00010203 |
KAMN241-I |
Information |
HASERV |
Server alias name |
START |
KAMN251-I |
||||||
KAMN254-I |
RESTART |
|||||
KAMN274-I |
||||||
KAMN310-I |
SWITCH |
|||||
KAMN311-I |
||||||
When a server terminates normally |
00010204 |
KAMN280-I |
Information |
END |
||
KAMN281-I |
||||||
KAMN290-I |
||||||
When a server error has occurred or a server terminates abnormally |
00010205 |
KAMN253-E |
Error |
EXCEPTION |
||
KAMN266-I |
||||||
KAMN272-E |
||||||
KAMN273-E#2 |
||||||
KAMN275-E |
||||||
KAMN276-E |
||||||
KAMN295-I |
||||||
KAMN300-E |
||||||
KAMN301-E |
||||||
KAMN517-E |
||||||
KAMN305-E |
NOTSTART |
|||||
KAMN306-E |
||||||
KAMN307-E |
||||||
KAMN312-E |
||||||
KAMN315-E |
||||||
KAMN316-E |
||||||
KAMN384-E |
||||||
KAMN423-E |
||||||
KAMN237-E |
HASERVPATH |
Server path name |
||||
When a failure is detected on the remote host |
00010206 |
KAMN340-E |
Error |
HAHOST |
HA Monitor's host name on the host resulting in the failure |
EXCEPTION |
When a reset path failure or a reset error has occurred |
00010207 |
KAMN347-E |
Error |
HARESET |
HA Monitor's host name at the reset target |
|
KAMN399-E |
||||||
When a monitoring path failure has occurred |
00010208 |
KAMN177-E |
Error |
HAPATH |
Host name of the monitoring path |
|
KAMN607-E |
||||||
KAMN640-E |
||||||
KAMN174-W |
Warning |
|||||
KAMN641-W |
||||||
When HA Monitor is waiting for operator intervention#3 |
00010209 |
KAMN238-D |
Warning |
HASERV |
Server alias name |
WAIT |
KAMN258-D |
||||||
KAMN368-D |
#1: This event is not issued at the following times: when HA Monitor starts, before the KAMN001-I message is issued, when HA Monitor fails to start due to an analysis error in the HA Monitor definition file.
#2: If the KAMN273-E message is output together with the KAMN300-E, KAMN305-E, KAMN312-E, or KAMN315-E message, the KAMN273-E message is not issued as an event. Only the messages that are output together with that message are issued as events.
#3: An operator intervention event might occur multiple times. In such a case, only the first such event that occurs is issued.
- Organization of this section
A.2 Event issuance timing when HA Monitor terminates normally
A.3 Event issuance timing when HA Monitor terminates abnormally
A.7 Event issuance timing when a server failure has occurred
A.8 Event issuance timing when a failure is detected on the remote host
A.9 Event issuance timing when a reset path failure has occurred
A.11 Event issuance timing when a monitoring path failure has occurred
A.12 Event issuance timing when HA Monitor is waiting for operator intervention