Asynchronous event monitored by keywords
The system message file (/var/adm/messages) is monitored with monitoring keywords. When a message that includes monitoring keywords is output, an asynchronous event is sent to Manager according to the level corresponding to the monitoring keywords. In this case, the detected message containing the monitoring keywords is sent to Manager as is. If asynchronous events corresponding to the same message are detected several times within the message monitoring time (Polling Time in the Correlation.ini parameter), these events are reported to Manager only once.
Multipath asynchronous events
".*" in the monitoring keywords is a regular expression (which indicates that any characters appears 0 times and more).
Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
.*mplb_mod:.*WARNING.*I/O error.* .*MPD.*WARNING.* (*1) | Warning | One-line message including a monitored keyword | See the ETERNUS multipath driver manual and take action. |
*1: Red Hat Enterprise Linux 5 or higher only
Device-Mapper Multipath asynchronous events
".*" in the monitoring keywords is a regular expression (which indicates that any characters appears 0 times and more).
Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
.*multipathd:.*remove.*path.*(uevent).* | Warning | One-line message including a monitored keyword | Refer to the manual for the corresponding middleware product. |
PRIMECLUSTER GDS and GFS Series asynchronous events
".*" in the monitoring keyword is a regular expression (which indicates that any characters appears 0 times and at more).
Failure event | Level | Event display | Troubleshooting |
|---|---|---|---|
NOTICE: sfx | Information | One-line message including monitoring keywords | Refer to the manual for the corresponding middleware product. |
WARNING: sfx | Warning | One-line message including monitoring keywords | Refer to the manual for the corresponding middleware product. Generally, the connection to storage devices and the cable connections must be checked. |
PANIC: sfx | Error | One-line message including monitoring keywords |
Event reporting a changed host name
Manager uses the host name to identify each of the server nodes. However, in cases where server nodes cannot be identified correctly after their host name has changed, the following event is output:
Event | Level | Event display | Troubleshooting |
|---|---|---|---|
The host name of a server node has changed | Warning | hostname of server node (IPaddress) has been changed from Server-A to Server-B | The hostname for the server having the IP address indicated in the event display has been changed to Server-B. Reset the hostname to Server-A. To do so, edit the /etc/hosts file, which contains the definitions of the hostnames. |
The "IPaddress" indicated in the event display is the IP address of the corresponding server node.
"Server-A" is the name set to which the corresponding server node was originally set.
"Server-B" is the name to which the corresponding server node is currently set.
