Clustered-System Code Overview; Error Code Range - IBM Storwize V7000 Troubleshooting And Maintenance Manual

168
error occurs because part of the hardware has failed or the system detects that the
scode is corrupt. If it is possible to communicate with the canister with a node
error, an alert that describes the error is logged in the event log. If the system
cannot communicate with the node canister, a Node missing alert is reported. If a
node has a critical node error, it is in service state, and the fault LED on the node
is on. The exception is when the node cannot connect to enough resources to form
a clustered system. It shows a critical node error but is in the starting state. The
range of errors that are reserved for critical errors are 500 - 699.
Some critical errors might be accompanied by error codes 1021, 1036, 1188, and
1189.
Noncritical errors
A noncritical error code is logged when there is a hardware or code failure that is
related to just one specific node. These errors do not stop the node from entering
active state and joining a clustered system. If the node is part of a clustered
system, there is also an alert that describes the error condition. The node error is
shown to make it clear which of the node canisters the alert refers to. The range of
errors that are reserved for noncritical errors are 800 - 899.

Clustered-system code overview

Recovery codes for clustered systems indicate that a critical software error has
occurred that might corrupt your system. Each error-code topic includes an error
code number, a description, action, and possible field-replaceable units (FRUs).
Error codes for recovering a clustered system
You must perform software problem analysis before you can perform further
operations to avoid the possibility of corrupting your configuration.

Error code range

This topic shows the number range for each message classification.
Table 29 lists the number range for each message classification.
168 The command cannot be initiated
because authentication credentials for
the current SSH session have expired.
Explanation: Authentication credentials for the current
SSH session have expired, and all authorization for the
140
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide
Table 29. Message classification number range
Message classification
Node errors
Error codes when
recovering a clustered
system
Range
Critical node errors
Noncritical node errors
920, 990
current session has been revoked. A system
administrator may have cleared the authentication
cache.
User response: Begin a new SSH session and re-issue
the command.
500-699
Some critical errors might be
accompanied by error codes
1021, 1036, 1188, and 1189.
700-899