Command Reference Guide

Specified as the month (mm or month_name) and day (dd), where the year (yy) can be optionally
specified. Acceptable formats are mm/dd/yy, month_name dd, dd month_name yy, or
yy–mm–dd. If the syntax yy–mm–dd is used, the year must be specified.
NOTE: The pattern argument in the following options is a regular expression pattern that is used
to match against the events each option produces. For each option, the pattern argument can be
specified multiple times. For example: showeventlog –type Disk.* –type <Tpdtcl client> –sev Major
displays all events of severity Major and with a type that matches either the regular expression
Disk.* or <Tpdtcl client> .
–sev <pattern>
Specifies that only events with severities that match the specified pattern(s) are displayed.
–nsev <pattern>
Specifies that only events with severities that do not match the specified pattern(s) are displayed.
–class <pattern>
Specifies that only events with classes that match the specified pattern(s) are displayed.
–nclass <pattern>
Specifies that only events with classes that do not match the specified pattern(s) are displayed.
–node <pattern>
Specifies that only events from nodes that match the specified pattern(s) are displayed.
–nnode <pattern>
Specifies that only events from nodes that do not match the specified pattern(s) are displayed.
–type <pattern>
Specifies that only events with types that match the specified pattern(s) are displayed.
–ntype <pattern>
Specifies that only events with types that do not match the specified pattern(s) are displayed.
–msg <pattern>
Specifies that only events, whose messages match the specified patttern(s), are displayed.
–nmsg <pattern>
Specifies that only events, whose messages do not match the specified pattern(s), are displayed.
–comp <pattern>
Specifies that only events, whose components match the specified pattern(s), are displayed.
–ncomp <pattern>
Specifies that only events, whose components do not match the specified pattern(s), are displayed.
SPECIFIERS
None.
RESTRICTIONS
The HP 3PAR OS stores 30 MB of event logs in segments of 3 MB each. When one 3 MB segment
is filled, events are written to the next segment. When all ten segments are filled, they are overwritten
beginning with the oldest segment.
382 Show Commands