Chapter 7. Event Reporting; Understanding Events; Viewing The Event Log; Managing The Event Log - IBM Storwize V7000 Troubleshooting And Maintenance Manual

Hide thumbs Also See for Storwize V7000:

Table of Contents

Chapter 7. Event reporting

Events that are detected are saved in an event log. As soon as an entry is made in this event log, the

condition is analyzed. If any service activity is required, a notification is sent.

Event reporting process

The following methods are used to notify you and the IBM Support Center of a new event:

v If you enabled Simple Network Management Protocol (SNMP), an SNMP trap is sent to an SNMP

manager that is configured by the customer.

v If enabled, log messages can be forwarded from a sender to a receiver on an IP network by using the

syslog protocol.

v If enabled, event notifications can be forwarded from a sender to a receiver through Call Home email.

v If you enabled Call Home, critical faults are reported directly to the IBM Support Center by email.

When a significant change in status is detected, an event is logged in the event log.

Error data

Events are classified as either alerts or messages:

v An alert is logged when the event requires some action. Some 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 state.

This situation must be investigated to see if it is expected or represents a failure. Investigate an alert

and resolve it as soon as it is reported.

v A message is logged when a change that is expected is reported, for instance, an IBM FlashCopy

operation completes.

You can view the event log by using the management GUI or the command-line interface (CLI).

You can view the event log by using the Troubleshooting options in the management GUI. The event log

contains many entries. You can, however, select only the type of information that you need.

You can also view the event log by using the command-line interface (svcinfo lseventlog). See the CLI

topic for the command details.

The event log has a limited size. After it is full, newer entries replace entries that are no longer required.

To avoid having a repeated event that fills the event log, some 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 and the last occurrence of the problem is saved in the log entry. A count of the number of

times that the error condition has occurred is also saved in the log entry. Other data refers to the last

occurrence of the event.

Table of Contents