show recentevents

Displays event messages in the group, starting with the most recent.

When an event occurs (such as the creation of a volume or the removal of a power supply), a message is generated. These messages enable you to track normal operations and detect problems before they disrupt operations. Event messages can also help you diagnose problems.

The show recentevents command displays output equal to a screen or page at a time, unless paging has been turned off with the cli-settings paging off command. If paging has been turned off, the command displays all events.

Each event is assigned a priority. Table 5: Event Priorities lists event priorities in order from highest (most severe) to lowest (least severe).

Table 5: Event Priorities
Priority	Description
FATAL	Catastrophic failure that requires immediate administrator intervention.
ERROR	Serious failure that should be investigated and may require administrator intervention.
WARNING	Potential problems in the group. An event with this priority may become an event with ERROR priority if administrator intervention does not occur.
INFO	Normal operational and transitional events that are of interest to administrators but do not require intervention.

Each event message shows the following information:

Group member that reported the event
Date and time of the event, in the format mm/dd/yy hh:mm:ss
Event priority level
Message text

Format

show recentevents

Example

The following command shows examples of events:

> show recentevents

170:61:member2:SP:31-Jan-2007 20:08:29.320062:verify.c:338:INFO:14.2.14:0:

Parity verification completed on RAID LUN 0 after 16385 seconds.

312:189:member1:MgmtExec: 1-May-2007 00:00:00.230190:SnapColSchedule.cc:950:WARNING:8.3.11:

Replica collection schedule 'coll1-sched' failed to create a replica collection.

58:52:member1:SP: 4-Apr-2007

13:32:56.470053:emm.c:1371:WARNING:28.3.51:

Warning health conditions currently exist. Investigate these conditions before they affect array operation.

Control modules are initializing. Control module failover cannot occur until the initialization completes.

There are 1 outstanding health conditions. Investigate these conditions before they affect array operation.

4:2:member2:SP:30-Apr-2007 13:11:09.170003:emm.c:920:ERROR:28.4.50:

Control module in slot 1 is not functioning or not installed.