Power-On Self-Test; Understanding Events; Understanding The Error Codes; Notification Types - IBM Storwize V7000 Unified Series Problem Determination Manual

Power-on self-test

Understanding events

Understanding the error codes

|
184
Storwize V7000 Unified: Problem Determination Guide Version
Table 39. Notification types (continued)
Notification type Description
Warning A warning notification is sent to indicate a problem or unexpected
condition with the Storwize V7000 Unified. Always immediately
investigate this type of notification to determine the effect that it
might have on your operation, and make any necessary corrections.
A warning notification does not require any replacement parts and
therefore should not require IBM Support Center involvement. The
allocation of notification type Warning does not imply that the
event is less serious than one that has notification type Error.
Information An informational notification is sent to indicate that an expected
event has occurred: for example, a FlashCopy operation has
completed. No remedial action is required when these notifications
are sent.
When you turn on the system, the file modules and the control enclosure node
canisters perform self-tests.
A series of tests is performed to check the operation of components and some of
the options that have been installed when the units are first turned on. This series
of tests is called the power-on self-test (POST).
If a critical failure is detected during the POST, the software is not loaded and the
fault LED is illuminated. To determine if there is a POST error on a file module or
a node canister, go to "Procedure: Understanding the system status using the
LEDs" on page 198.
When the software is loaded, additional testing takes place, which ensures that all
of the required hardware and software components are installed and functioning
correctly.
The Storwize V7000 Unified software generates events, such as informational
events and configuration events. An event ID or number is associated with the
event and indicates the reason for the event.
There are different types of events:
v Informational events provide information on the status of an operation.
Information events are recorded in the error event log, and depending on the
configuration, can be notified through email, SNMP, and syslog.
v 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.
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.