Diagnosis Guide
The format of these entries is the format of the standard error log
entries, which are viewed using the errpt -a command. These
are hardware errors. An example is an entry that indicates:
Power module - DC power loss..
Entries are logged when the condition appears to be permanent. The
error information can be cleared. Do not clear an entry if an
error has occurred. Entries appear in the language specified by the
current location setting (SP administrative locale) on the control
workstation.
Table 54 shows the error log templates used by the system
monitor. UNKN indicates an unknown error type. PERM indicates a
permanent error type.
Table 54. AIX Error Log templates for the System Monitor
| Label
| Error ID
| Type
| Class
| Description
|
| HM001_TR
| F55FBD1D
| UNKN
| S
| Explanation: Informational System Monitor message.
Details: These are informational messages that primarily
report unrecognized debug flags specified by the hmadm command, or
incorrect arguments to the System Monitor (hardmon) daemon.
|
| HM002_TR
| B463BBF0
| UNKN
| S
| Explanation: Informational System Monitor message.
Details: These are informational messages that report
certain key events on the progress of the System Monitor daemon
process. For example, initiating the main processing loop, or the
opening or closing of a log file.
|
| HM003_ER
| 6CCA6600
| PERM
| S
| Explanation: The System Monitor has encountered an
internal error.
Details: An internal error has occurred. Examples
are system calls that have ended in error or internal program errors.
|
| HM004_ER
| 3A814C25
| PERM
| S
| Explanation: The System Monitor has encountered an
internal error.
Details: An internal error has occurred. Examples
are system calls that have ended in error, or internal program errors.
|
| HM005_ER
| 8D64B0C8
| PERM
| S
| Explanation: The System Monitor has encountered an
internal error.
Details: An internal error has occurred. Examples
are system calls that have ended in error or internal program errors.
This can also be caused by an unexpected signal that killed an external
hardware driver, or the external hardware driver's restart limit being
exceeded.
|
| HM006_ER
| BB9D16B2
| PERM
| S
| Explanation: The System Monitor has encountered a
configuration error.
Details: A configuration file, or the SDR, was found to
contain incorrect data. Examples are: if the
hmthresholds file contains an incorrect card type, or if there is a
duplicate entry in the hmacls file.
|
| HM007_ER
| C70D5E9D
| PERM
| S
| Explanation: A resource is unavailable to the System
Monitor.
Details: The primary reason for this error is that the
System Monitor was unable to establish a session with the SDR.
|
| HM008_ER
| 472C610A
| PERM
| S
| Explanation: The System Monitor has encountered a data
packet error.
Details: There is some error involving the data packet that is
sent from a frame supervisor to the System Monitor daemon. Examples are
a missing data packet or an unexpected supervisor type in the data
packet.
|
| HM009_ER
| 60A89611
| PERM
| S
| Explanation: The System Monitor has received a bad client
command.
Details: A command sent to the System Monitor from a client
such as: hmmon, hmcmds, s1term is bad. For example, the command
is incorrect or the command arguments are incorrect.
|
| HM010_ER
| A7DA9589
| PERM
| S
| Explanation: The System Monitor could not open a
file.
Details: The System Monitor could not open a log file, a
configuration file, or a tty.
|
This file is located in:
/var/adm/SPlogs/spmon/hmlogfile.ddd, where
ddd is the Julian day, on the control workstation. It is not
trimmed. It is created automatically when the System Monitor (hardmon)
is started.
A new system monitor daemon log file can be created by issuing the
command:
hmadm clog
The previous log file is not deleted. A new one (with a different
name) is created.
Entries in the file have this format:
hardmon: message_number message_text
Locate the message number in: PSSP: Messages
Reference.
An example of some data in this file is :
hardmon: 0026-801I Hardware Monitor Daemon started at Wed Dec 22 17:46:06 1999
hardmon: 0026-802I Server port number is 8435, poll rate is 5.000000 seconds
hardmon: 0026-805I 1 frames have been configured.
hardmon: 0026-803I Entered main processing loop
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]