Understanding The Error Codes; Event Ids; Informational Events - IBM Storwize V7000 Troubleshooting And Maintenance Manual

Hide thumbs Also See for Storwize V7000:
Table of Contents

Advertisement

When the code is loaded, additional testing takes place, which ensures that all of
the required hardware and code components are installed and functioning
correctly.

Understanding the error codes

Error codes are generated by the event-log analysis and system configuration code.
Error codes help you to identify the cause of a problem, the failing
field-replaceable units (FRUs), and the service actions that might be needed to
solve the problem.

Event IDs

The Storwize V7000 software generates events, such as informational events and
error events. An event ID or number is associated with the event and indicates the
reason for the event.
Informational events provide information about the status of an operation.
Informational events are recorded in the event log, and depending on the
configuration, can be notified through email, SNMP, or syslog.
Error events are generated when a service action is required. An error event maps
to an alert with an associated error code. Depending on the configuration, error
events can be notified through email, SNMP, or syslog.

Informational events

The informational events provide information about the status of an operation.
Informational events are recorded in the event log and, based on notification type,
can be notified through email, SNMP, or syslog.
Informational events can be either notification type I (information) or notification
type W (warning). An informational event report of type (W) might require user
attention. Table 27 provides a list of informational events, the notification type, and
the reason for the event.
124
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide
Table 27. Informational events
Notification
Event ID
type
980221
I
980230
I
980231
I
980301
I
980310
I
980320
I
980321
W
980330
I
980340
I
980341
W
980342
W
Description
The error log is cleared.
The SSH key was discarded for the service login user.
User name has changed.
Degraded or offline managed disk is now online.
A degraded or offline storage pool is now online.
Offline volume is now online.
Volume is offline because of degraded or offline
storage pool.
All nodes can see the port.
All ports in this host are now logged in.
One or more ports in this host is now degraded.
One or more ports in this host is now offline.

Advertisement

Table of Contents
loading

Table of Contents