Describing the fields in the error event log

The error event log includes fields with information that you can use to diagnose problems.

Table 1 describes the fields that you see when you use the command-line interface to produce an error event log.

Table 1. Description of data fields for the error event log
Data field	Description
Node identifier	The name of the node that the error or event occurred on. If the event applies to a specific node, for example, it indicates that the fibre-channel port of the node is not working, then the node identifier is indicated here. If the event applies to the cluster rather than to a node, for example, a license limit is exceeded, then this field is set to 0.
Object type	The object type to which the error event log relates. See Table 2.
Object ID	A number that uniquely identifies the instance of the object.
Sequence number	A number that identifies the event. Where appropriate, sense data is returned to host systems references the sequence number.
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 this error event was reported. If events of a similar type are being coalesced together, so one error event log record represents more than one event, this is the time the first error event was logged.
Last error timestamp	The time when the last instance of this error event was recorded in the log.
Error count	The number of error events coalesced into this error event log record.
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 on the status flag, see Table 3.
Type flag	For details on the type flag, see Table 5.
Additional sense data	Data specific to this error or event code. This is a binary data record. When the error event log is viewed using the command line tools, this data is shown in hex. When the data is viewed using the Web interface, this data is translated to ASCII characters on the right side of the page. You are not normally required to interpret this data as part of the service procedures. However, any procedures that do refer to the data describe the ASCII format.

Table 2 describes the types of error-event log objects.

Table 2. Description of object types and object IDs for the error event log
Object type	Object ID
mdisk	Managed disk number
mdiskgrp	Managed disk group number
vdisk	Virtual disk
node	Node ID
host	Host identifier
iogroup	I/O group identifer
fcgrp	FlashCopy® consistency group number
rcgrp	Metro or Global Mirror consistency group number
fcmap	FlashCopy mapping number
rcmap	Metro or Global Mirror mapping number
wwpn	Worldwide port name
cluster	Cluster ID (shown in decimal)
device	Device number
SCSI lun	SCSI logical unit number (LUN) identifier
quorum	Quorum identifier
clusterip	Cluster IP
fc_adapter	Fibre-channel adapter
Emailuser	E-mail user
Syslog	Syslog server
Snmp	SNMP server
Smtp	E-mail server
Auth_Group	User group
SAS_Adapter	SAS adapter

Table 3 shows the types of error-event log flags.

Note: Informational events only have the SNMP trap-raised flag on when configured to do so.

Table 3. Description of flags for the error-event log
Flag	Description
Unfixed	This log entry requires a service action.
Fixed	This entry is marked as fixed. It remains in the error event log until it becomes the oldest record in the log, at which point it is overwritten by the next log entry.
Expired	Some events require a certain number of occurrences in 25 hours before they are shown as unfixed. If they do not reach this threshold in 25 hours, they are flagged as expired. Any further events of this type are then placed in a new event log entry.

Table 4 shows the various combinations of flags that might be logged and the resulting status that is reported by the user interfaces. The Analyze Error Log panel in the SAN Volume Controller Console summarizes the status flags in the error event log record. The following table lists the status values shown, and the status flag combination that value represents.

Table 4. Reported status for combinations of error-log status flags
Reported Status	UNFIXED	ERROR_FIXED	ERROR EXPIRED
BELOW_THRESHOLD	0	0	0
EXPIRED	0	0	1
UNFIXED	1	0	0
FIXED	x¹	1	0
Note: ¹ This flag has no effect on the status.

Table 5 shows the error-event types.

Table 5. Description error-event types
Type	Description
Error Cat 1	These errors require a service action. A Cat 1 error normally indicates a problem with a hardware component. A FRU or list of FRUs are included with the trap data sent with the error record.
Error Cat 2	These errors require a service action. A Cat 2 error normally indicates a configuration or environment problem rather than a hardware problem.
Transient error	Errors of type 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.
Informational	This type indicates that the log entry is an informational event. Information events can be used to warn the user about an unexpected configuration result or prompt a user to initiate further configuration actions.