Description
The
event log show command displays
the contents of the event log, which lists significant occurrences within the cluster.
Events are categorized by type.
Use the
event route show command
to display general information about each type of event.
By default,
the command displays non-DEBUG severity level events with the following information,
with the most recent events listed first:
- The time at which the event occurred
- The node on which the event occurred
- The severity of the event
- The event's message
To display detailed information about events,
use one or more of the optional parameters that affect
how the command output is displayed and the amount of
detail that is included.
For example, to display all detailed event information,
use the -detail parameter.
To display DEBUG severity level events,
use the -severity parameter.
At the advanced privilege level and higher, the command displays the
following additional information:
- The internal EMS severity of the event
- The event's kernel generation number, if applicable
- The event's kernel sequence number, if applicable
Parameters
{
[-fields <fieldname>, ...]
If you specify the -fields <fieldname>, ... parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.
|
[-detail ]
Displays
all detailed event information.
|
[-detailtime ]
Displays
detailed event information in chronological order.
|
[-instance ]
}
If you specify the -instance parameter, the command displays detailed information about all fields.
[-node {<nodename>|local}] - Node
Displays
a list of events for the node you specify.
Use this parameter with the -seqnum parameter
to display detailed information.
[-seqnum <Sequence Number>] - Sequence#
Selects the events that match this parameter value.
Use with the -node parameter
to display detailed information.
[-time <MM/DD/YYYY HH:MM:SS>] - Time
Selects the events that match this parameter value. Use the format:
MM/DD/YYYY HH:MM:SS [+- HH:MM].
You can specify a time range
by using the ".." operator between two time statements.
show -time "08/13/2010 05:55:00".."08/13/2010 06:10:00"
Comparative time values are relative to "now".
For example, to display only events that occurred within
the last minute:
show -time >1m
[-severity {EMERGENCY|ALERT|CRITICAL|ERROR|WARNING|NOTICE|INFORMATIONAL|DEBUG}] - Severity
Selects the events that match this parameter value. Severity levels:
- EMERGENCY - The system is unusable
- ALERT - Action must be taken immediately
- CRITICAL - Critical condition
- ERROR - Error condition
- WARNING - Warning condition
- NOTICE - Normal but significant condition
- INFORMATIONAL - Information message
- DEBUG - Debugging message
To display all events, including ones with a severity of DEBUG, specify severity as follows:
show -severity <=DEBUG
[-ems-severity {NODE_FAULT|SVC_FAULT|NODE_ERROR|SVC_ERROR|WARNING|NOTICE|INFO|DEBUG|VAR}] - EMS Severity (privilege: advanced)
Selects the events that match this parameter value. Severity levels:
- NODE_FAULT - Data corruption has been detected or the node is
unable to provide client service
- SVC_FAULT - A temporary loss of service, typically a transient
software fault, has been detected
- NODE_ERROR - A hardware error that is not immediately fatal has
been detected
- SVC_ERROR - A software error that is not immediately fatal has
been detected
- WARNING - A high-priority message that does not indicate a fault
- NOTICE - A normal-priority message that does not indicate a fault
- INFO - A low-priority message that does not indicate a fault
- DEBUG - A debugging message
- VAR - A message with variable severity, selected at runtime.
[-source <text>] - Source
Selects the events that match this parameter value
(typically a software module).
[-messagename <Message Name>] - Message Name
Selects the events that match this parameter value (string).
Message names are descriptive, so filtering output by message name
displays messages of a specific type.
[-event <text>] - Event
Selects the events that match this parameter value.
This parameter is most useful when entered with wildcards.
The "event" field contains the full text of the event,
including any parameters.
For example, a wafl.vol.offline event will contain
the name of the volume taken offline.
[-kernelgen <integer>] - Kernel Generation Number (privilege: advanced)
Selects the events that match this parameter value. Only events that emanate from the kernel
have kernel generation numbers.
[-kernelseqnum <integer>] - Kernel Sequence Number (privilege: advanced)
Selects the events that match this parameter value. Only events that emanate from the kernel
have kernel sequence numbers.
[-action <text>] - Corrective Action
Selects the events that match this parameter value.
This parameter is most useful when entered with wildcards.
The "action" field describes what steps, if any, you must take to
remedy the situation.
[-description <text>] - Description
Selects the events that match this parameter value.
This parameter is most useful when entered with wildcards.
The "description" field describes why the event was encountered and what it means.
Examples
The following example displays the event log:
cluster1::> event log show
Time Node Severity Event
------------------- ---------------- ------------- ------------------------
11/9/2010 13:54:19 node1 INFORMATIONAL vifmgr.portup: A link up event was received on node node1, port e0a.
11/9/2010 13:54:19 node1 INFORMATIONAL vifmgr.portup: A link up event was received on node node1, port e0d.
11/9/2010 13:54:19 node1 INFORMATIONAL vifmgr.portup: A link up event was received on node node1, port e0c.
11/9/2010 13:54:19 node1 INFORMATIONAL vifmgr.portup: A link up event was received on node node1, port e0b.
...
This example demonstrates how to use a range with the -time parameter to display all events that occurred during an extended time period. It displays all events that occurred between 1:45pm and 1:50pm on November 9, 2010.
cluster1::> event log show -time "11/9/2010 13:45:00".."11/9/2010 13:50:0"
The -time parameter also accepts values that are relative to "now". The following example displays events that occurred more than one hour ago.
cluster1::event log> show -time <1h
Time Node Severity Event
------------------- ---------------- ------------- ------------------------
11/9/2010 13:02:03 node1 INFORMATIONAL monitor.globalStatus.ok: The system's global status is normal.
11/9/2010 13:02:03 node2 INFORMATIONAL monitor.globalStatus.ok: The system's global status is normal.
...
Severity levels sort in the order opposite to what you might expect. The following example displays all events that have a severity level of CRITICAL or more severe.
cluster1::> event log show -severity <CRITICAL
