Describing the fields in the error log
The error log includes fields with
information you can use to diagnose problems.
Table 64 describes the fields you see in Figure 170 and Figure 172.
Table 64. Description of data fields for the error log
| Data field |
Description |
| Node identifier |
The name of the node that created the error
report. |
| Object type |
The object type that error log relates to.
See Table 65. |
| Object ID |
A number that uniquely identifies the object
on this node. |
| Sequence number |
A sequentially assigned number that can be used to provide
a cross reference to sense data returned to host systems. |
| Root Sequence Number |
The sequence number of another log entry
that enables all errors that have a single source to be marked as fixed by
a single action. |
| First Error Timestamp |
The time when the first instance of this error code
was reported by this object type in the last 25 hours. |
| Last error timestamp |
The time when the last instance of this error
code was reported by this object type in the last 25 hours. |
| Error count |
The number of times that this error code
has been reported by this object in the last 25 hours. |
| Error ID |
This number is a unique identifier for the
error or event. |
| Error code |
This number is used as the starting point for service
procedures. |
| Status flag |
For details of the status flag. See Table 66. |
| Type flag |
For details of the type flag. See Table 68. |
| Additional sense data |
Data specific to this error or event code. This is a
binary data record and when the error log is viewed via the command line tools
this data is shown in hex. When the data is viewed via the web interface
this data is translated to ASCII characters on the right hand side of the
page. You will not normally be required to interpret this data as part of
the service procedures. However, any procedures that do refer to the this
data will describe the ASCII format. |
Table 65 describes the types of error log objects.
Table 65. Description of object types and object IDs for the error log
| Object type |
Object ID |
| Node |
The six character node ID |
| Fcgrp |
Flash Copy consistency group number |
| Rcgrp |
Remote Copy consistency group number |
| Fcmap |
Flash Copy map number |
| Rcmap |
Remote Copy Map number |
| Cluster |
Cluster Name as displayed on the front panel. |
| Device |
Device number |
| Mdisk |
Managed disk number |
| Mdiskgrp |
Managed disk group number |
| Uninterruptible power supply |
Uninterruptible power supply serial number |
Table 66 shows the types of error log flags.
 | Note: Configuration Events have nothing in the flag field. Information Events only
have the SNMP trap-raised flag on when configured to do so. |
Table 66. Description of flags for the error log
| Flag |
Description |
| Unfixed |
This log entry requires a service action. |
| Fixed |
This entry has been marked as fixed. It will
remain in the error log until it becomes the oldest record in the log at which
point it will be overwritten by the next log entry. |
| Expired |
The error log entry is over 25 hours old. Any new log
entries of this error/event code for this object type will produce a new log
entry. |
| SNMP trap raised |
An SNMP trap has been raised. SNMP traps are raised
for unfixed errors and for information events. |
Table 67 shows the various combinations of flags that may
be logged and the resulting status that is reported by the user interfaces.
 | Note: SNMP_TRAP_RAISED is independent of the other flags. |
Table 67. Reported status for combinations of error-log status flags
| UNFIXED |
ERROR_FIXED |
ERROR_EXPIRED |
Reported Status |
| 0 |
0 |
0 |
BELOW_THRESHOLD |
| 0 |
0 |
1 |
EXPIRED |
| 0 |
1 |
0 |
FIXED |
| 0 |
1 |
1 |
not possible |
| 1 |
0 |
0 |
UNFIXED |
| 1 |
0 |
1 |
not possible |
| 1 |
1 |
0 |
FIXED |
| 1 |
1 |
1 |
not possible |
Table 68 shows the types of error log flags.
Table 68. Description of types of error log flags
| Flag |
Description |
| Unknown error |
This flag should never be seen. This flag
can only result from a software defect. |
| Error Cat 1 |
These errors require a service action. A
FRU or list of FRUs will be included with the trap data or e-mail sent with
the error record. |
| Error Cat 2 |
These errors require a service action but
more analysis is required before the service action or FRU can be identified. |
| Related error |
These are errors that have a root cause that has been
reported in another log entry. Marking the source error as fixed will also
mark this error as fixed. |
| Transient error |
Errors flagged as transient have been recovered
by an error recovery procedure. |
| Configuration event |
This entry is from the Configuration Event
log. This flag is useful when displaying both logs in a seamless display as
an aid to relating logged error conditions to configuration events. |
| Information |
This entry indicates that the log entry is
an Information Event. Information events can be used to warn the user about
an unexpected configuration result or prompt a user to initiate further configuration
actions. This type of log entry will cause an SNMP trap to be raised if requested
by the user. |