lseventlog

Use the lseventlog command to display a concise view of the system event log, or a detailed view of one entry from the log.

Syntax

lseventlog [ -filtervalueattribute_value ] [ -filtervalue? ] [ -alert { yes | no } ] [ -message { yes | no } ] [ -monitoring { yes | no } ] [ -expired { yes | no } ] [ -fixed { yes | no } ] [ -config { yes | no } ] [ -count entry_limit ] [ -order { date | severity } ] [ sequence_number ]

Parameters

-filtervalueattribute=value
(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter attribute value are returned. If a capacity is specified, the units must also be included.
Note: Some filters allow the use of a wildcard when you enter the command. The following rules apply to the use of wildcards when using the CLI:
  • The wildcard character is an asterisk (*).
  • The command can contain a maximum of one wildcard.
  • When using a wildcard, you must enclose the filter entry within double quotation marks (""), as follows:
    lseventlog -filtervalue "object_name=ob*"
-filtervalue?
(Optional) Displays a list of valid filter attributes for the -filtervalueattribute=value parameter:
  • copy_id
  • error_code
  • event_count
  • event_id
  • fixed
  • last_timestamp
  • object_id
  • object_name
  • object_type
  • report_node
  • reporting_node_name
  • root_sequence_number
  • sequence_number status
-alertyes | no
(Optional) Includes (or excludes) events with alert status.
-messageyes | no
(Optional) Includes events with message status.
-monitoringyes | no
(Optional) Includes events with monitoring status.
-expiredyes | no
(Optional) Includes (or excludes) events with expired status.
-fixedyes | no
(Optional) Includes (or excludes) events with fixed status.
-configyes | no
(Optional) Includes (or excludes) events with config status.
-countentry_limit
(Optional) Indicates the maximum number of events to display.
-order date | severity
(Optional) Indicates what order the events should be in. Ordering by date displays the oldest events first. Ordering by severity displays the events with the highest severity first. If multiple events have the same severity, then they are ordered by date, with the oldest event being displayed first.
The following list shows the order of severity, starting with the most severe:
  1. Unfixed alerts (sorted by error code; the lowest error code has the highest severity)
  2. Unfixed messages
  3. Monitoring events (sorted by error code; the lowest error code has the highest severity)
  4. Expired events
  5. Fixed alerts and messages
sequence_number
(Optional) Indicates if the command should display a full view of the event.

Description

This command displays a concise view of the system event log, or a detailed view of one entry from the log. You can sort the events and entries by severity or age.

The default values for included events are:
  • alert=yes
  • config=no
  • expired=no
  • fixed=no
  • message=yes
  • monitoring=no
Table 1 provides the attribute values that can be displayed as output view data.
Table 1. lseventlog output
Attribute Description Value
machine_type Node machine type and model number The value is an alphanumeric string up to 7 characters long.
serial number Node serial number The value is an alphanumeric string up to 7 characters long.
sequence_number Sequence number of the event The value is numeric from 0 to 8000000.
first_timestamp When the event was added to the log The value is in the format YYMMDDHHMMSS.
first_timestamp_epoch When the event was added to the log (in seconds) after the epoch occurs This is a numeric 32-bit value.
last_timestamp When the event was most recently updated The value is in the format YYMMDDHHMMSS.
last_timestamp_epoch Most recent update (in seconds) after an epoch for an event This is a numeric 32-bit value.
fixed_timestamp Time stamp when event is fixed The value is in the format YYMMDDHHMMSS.
fixed_timestamp_epoch Time stamp (in seconds) when an event is fixed after an epoch occurs The value is a numeric string.
fru Field-replaceable unit (FRU) for error or event; this field contains probable FRUs (separated by commas) The value is an ASCII string up to 255 characters long.
object_type The type of the object the event is logged against The values are:
  • mdisk
  • mdiskgrp
  • volume (or volume copy)
  • node
  • host
  • io_grp (iogroup in dumperrlog)
  • fc_consist_grp (fcgrpin dumperrlog)
  • rc_consist_grp(rcgrp in dumperrlog)
  • fc_map (fcmap in dumperrlog; flash in caterrlog)
  • rc_relationship (rcmapin dumperrlog; remote in caterrlog)
  • cluster
  • controller (devicein caterrlog and dumperrlog)
  • quorum
  • migrate
  • email_server (emailserver in caterrlog and dumperrlog)
  • enclosure
  • drive
object_id ID of the object the event is logged against This is a numeric 64-bit value. It is displayed in decimal for all object types other than clustered systems.

For a clustered system, this value is hexadecimal but is blank for events with cluster object types.

object_name Name of the object the event is logged against. This value is the object name format and is blank if the object was deleted or does not have a name
copy_id Volume copy ID the event is logged against This is a numeric value 0 to 1; it is blank if not a vdiskcopy event
reporting_node_id ID of the node that reported the event This is a numeric 64-bit value that is blank if the event is reported by the clustered system
reporting_node_name Name of the node that reported the event. This value is the object name format and is blank if node is deleted or event is reported by the clustered system
root_sequence_number Sequence number of the root or causal event
Important: If the event is directly caused by another event then the sequence_number of the related event is shown here.
 This is a numeric value from 1 to 8000000; blank if there is no root or if the event is not directly caused by another event
event_count Number of reported events that have been combined into this event This is a numeric 32-bit value.
status Event category The values are:
  • alert
  • message
  • monitoring
  • expired
fixed Indicates whether the event was marked fixed (for an alert) or read (for a message) The values are:
  • yes
  • no (for events that cannot be fixed, or are not fixed)
auto_fixed Indicates if event is marked fixed by the code The values are:
  • yes
  • no (for events that cannot be fixed, or are not fixed)
notification_type Type of event notification The values are:
  • error
  • warning
  • informational
  • none
event_id Event ID This is a 6-digit numeric value.
event_id_text Description associated with the event ID This is a text value with a maximum of 200 bytes.

This appears in CLI requested language.
error_code Error code associated with this event This is a 4-digit numeric value but is blank if there is no error code.
error_code_text Description associated with the error code This is a text value with a maximum of 200 bytes that is blank if there is no error code.

This appears in CLI requested language.
description Description associated with the event

If the event has an error code, this value is the same as the error_code_text field; otherwise, it is the same as the event_id_text field

 Text (maximum of 200 bytes).
sense1 Sixteen bytes of hex-encoded sense data; least significant byte is on the left The value is sixteen two-character hexadecimal numbers separated by spaces.
sense2
sense3
sense4
sense5
sense6
sense7
sense8

Invocation examples

This example shows events in January 2010: 
lseventlog -filtervalue 'last_timestamp>=100101000000:last_timestamp<100201000000'
This example shows all unfixed 1065 errors, in order of occurrence: 
lseventlog -filtervalue error_code=1065:fixed=no
This example lists the most critical event: 
lseventlog -order severity -count 1
This example shows the concise view: 
lseventlog

sequence_number:last_timestamp:object_type:object_id:object_name:copy_id:status:fixed:event_id:error_code:description

400:100106132413:vdisk:2:my_vdisk:1:alert:no:060001:1865:Space Efficient Virtual Disk Copy offline due to insufficient space
401:100106140000:cluster::ldcluster-2::message:no:981001::Cluster Fabric View updated by fabric discovery
This example shows the full view: 
lseventlog 120

sequence_number 120
first_timestamp 111130100419
first_timestamp_epoch 1322647459
last_timestamp 111130100419
last_timestamp_epoch 1322647459
object_type node
object_id 1
object_name node1
copy_id 
reporting_node_id 1
reporting_node_name node1
root_sequence_number 
event_count 1
status alert
fixed yes
auto_fixed no
notification_type error
event_id 073003
event_id_text More/Less fibre channel ports operational
error_code 1060
error_code_text Fibre Channel ports not operational
machine_type 21458F4
serial_number 75BZPMA
fru none
fixed_timestamp 111202141004
fixed_timestamp_epoch 1322835004

sense1 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
sense8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Parent topic: Clustered system diagnostic and service-aid commands