HP StorageWorks XPath OS 7.4.X System Error Messages Reference Guide (AA-RVHGC-TE, September 2005)

XPath OS 7.4.x system error messages reference guide 15
Error log tasks
These procedures explain error log management.
Viewing the error log
The error log is a collection of all daemon-related errors (such as memory allocation errors), as well as
events from the event log. To view the MP Router error log:
1. Log in to the MP Router as admin.
2. Issue the errShow command with the following options:
errShow [-a]
where -a displays all the messages without page breaks.
The following command displays all the messages in the error log, one at a time:
The following command displays all the messages in the error log without page breaks:
Table 5 Message severity levels
Event level Description
0 = Panic Panic messages indicate that a specific software subsystem has detected a fatal or
unrecoverable error condition. Examples are memory allocation failure, system call
failure, and software detection of problems with the ASIC or with hardware subsystems.
These errors usually indicate partial or complete failure of a subsystem.
1 = Critical Critical messages indicate that the software has detected serious problems that
eventually cause a partial or complete failure of a subsystem if not corrected
immediately. A power supply failure, for example, or a rise in temperature must receive
immediate attention. Some of the critical errors might overlap in severity with the panic
messages.
2 = Error Error messages indicate error conditions that do not significantly affect overall system
functionality. For example, error messages might indicate time-outs on certain
operations, failures of certain operations after retries, invalid parameters, or failures to
perform requested operations.
3 = Warning Warning messages highlight current operating conditions that should be checked before
they cause failures. For example, a power supply failure in a redundant system relays a
warning that the system is no longer operating in redundant mode, and that the failed
power supply should be replaced or fixed.
4 = Info Info messages report the current status of the system components other than error status,
for example, detecting on and off line status of a fabric port.
5 = Debug Debug messages are for debugging use only. They are produced by code inserted by
the vendor to inform the user that a suspected problem has occurred.
fabricAP:admin> errShow
fabricAP:admin> errShow -a