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
Parameters
- -filtervalue attribute=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.
- -nohdr
- (Optional) By default, headings are displayed for each column of data in a concise style
view, and for each item of data in a detailed style view. The -nohdr
parameter suppresses the display of these headings.Note: If there is no data to be displayed, headings are not displayed.
- -delim delimiter
- (Optional) By default in a concise view, all columns of data are space-separated. The width
of each column is set to the maximum width of each item of data. In a detailed view, each item
of data has its own row, and if the headers are displayed, the data is separated from the
header by a space. The -delim parameter overrides this behavior. Valid
input for the -delim parameter is a 1-byte character. If you enter
-delim :on the command line, the colon character (:) separates all items of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is separated from its header by the specified delimiter. - -alert yes | no
- (Optional) Includes (or excludes) events with alert status.
- -message yes | no
- (Optional) Includes events with message status.
- -monitoring yes | no
- (Optional) Includes events with monitoring status.
- -expired yes | no
- (Optional) Includes (or excludes) events with expired status.
- -fixed yes | no
- (Optional) Includes (or excludes) events with fixed status.
- -count entry_limit
- (Optional) Indicates the maximum number of events to display.
- -order date | severity
- (Optional) Indicates what order the events must 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 displayed first. The following list shows the order of severity, starting with the most severe:
- Unfixed alerts (sorted by error code; the lowest error code has the highest severity)
- Unfixed messages
- Monitoring events (sorted by error code; the lowest error code has the highest severity)
- Expired events
- Fixed alerts and messages
- -filtervalue?
- (Optional) Displays a list of valid filter attributes for the
-filtervalue
attribute=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
- sequence_number
- (Optional) Indicates whether the command must 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
- expired=no
- fixed=no
- message=yes
- monitoring=no
Table 1 provides the attribute values that can be
displayed as output view data.
| Attribute | Description | Value |
|---|---|---|
| machine_type | Indicates the node machine type and model number. | The value is an alphanumeric string up to 7 characters long. |
| serial number | Indicates the node serial number. | The value is an alphanumeric string up to 7 characters long. |
| sequence_number | Indicates the sequence number of the event. | The value is numeric from 0 to
8000000. |
| first_timestamp | Indicates when the event was added to the log. | The value is in the format YYMMDDHHMMSS. |
| first_timestamp_epoch | Indicates when the event was added to the log (in seconds) after the epoch occurs. | The value is a numeric 32-bit value. |
| last_timestamp | Indicates when the event was most recently updated. | The value is in the format YYMMDDHHMMSS. |
| last_timestamp_epoch | Indicates the most recent update (in seconds) after an epoch for an event. | The value is a numeric 32-bit value. |
| fixed_timestamp | Indicates the time stamp when event is fixed. | The value is in the format YYMMDDHHMMSS. |
| fixed_timestamp_epoch | Indicates the time stamp (in seconds) when an event is fixed after an epoch occurs. | The value is a numeric string. |
| fru | Indicates the 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 | Indicates the type of the object the event is logged against. | The values are:
|
| object_id | Indicates the ID of the object the event is logged against. | The value 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 |
| object_name | Indicates the 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 | Indicates the volume copy ID the event is logged against. | The value is a numeric value 0 to 1;
it is blank if not a vdiskcopy event. |
| reporting_node_id | Indicates the ID of the node that reported the event. | The value is a numeric 64-bit value that is blank if the event is reported by the clustered system. |
| reporting_node_name | Indicates the 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 | Indicates the sequence number of the root or causal event Important: If the event is directly caused by another event, the sequence_number of
the related event is shown here.
|
The value 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 | Indicates the number of reported events that are combined into this event | The value is a numeric 32-bit value. |
| status | Indicates the event category. | The values are:
|
| fixed | Indicates whether the event was marked fixed (for an alert) or read (for a message). | The values are:
|
| auto_fixed | Indicates whether event is marked fixed by the code. | The values are:
|
| notification_type | Indicates the type of event notification. | The values are:
|
| event_id | Indicates the event ID. | The value is a 6-digit numeric value. |
| event_id_text | Indicates the description that is associated with the event ID. | The value is a text value with a maximum of 200 bytes. This appears in CLI requested language. |
| error_code | Indicates the error code that is associated with this event. | The value is a 4-digit numeric value but is blank if there is no error code. |
| error_code_text | Indicates the description that is associated with the error code. | The value is a text value with a maximum of 200 bytes that is blank if
there is no error code. This value appears in the language that is requested by the CLI. |
| description | Indicates the description that is associated with the event. If the
event has an error code, this value is the same as the |
Text (maximum of 200 bytes). |
| sense1 | Indicates the sixteen bytes of hex-encoded sense data; least significant byte is on the left. | The value is 16 2-character hexadecimal numbers that are 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=noThis example lists
the most critical event:
lseventlog -order severity -count 1This
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 discoveryThis
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
