Event Log; Managing The Event Log - IBM Storwize V5010 Manual

12.7 Event log

Whenever a significant change in the status of the IBM Storwize V5000 Gen2 is detected, an
event is submitted to the
An alert is logged when the event requires action. Certain alerts have an associated error
code that defines the service action that is required. The service actions are automated
through the fix procedures. If the alert does not have an error code, the alert represents an
unexpected change in the state. This situation must be investigated to see whether it is
expected or represents a failure. Investigate an alert and resolve it when it is reported.
A message is logged when a change that is expected is reported, for instance, an IBM
FlashCopy operation completes.
To check the event log, browse to Monitoring → Events, as shown in Figure 12-74.
Figure 12-74 Event log

12.7.1 Managing the event log

The event log features a size limit. After the event log is full, newer entries replace the older
entries, which are not required. To avoid a repeated event that fills the event log, certain
records in the event log refer to multiple occurrences of the same event. When event log
entries are coalesced in this way, the time stamp of the first occurrence of the problem and
the time stamp the last occurrence of the problem are saved in the log entry. A count of the
number of times that the error condition occurred is also saved in the log entry. Other data
refers to the last occurrence of the event.
Event log panel columns
Right-clicking any column header opens the option menu in which you can select columns
that are shown or hidden. It is also possible to click the Column icon on the far right of the
column headers to open the option menu.
event log
. All events are classified as
Chapter 12. RAS, monitoring, and troubleshooting
alerts messages
or .
709