Node error code overview
Node error codes describe failures that relate to a specific node.
Connect to the technician port so that you can use the service assistant GUI to view node errors and other error data.
Because node errors are specific to a node, for example, memory failures, the errors might be reported only on that node. However, if the node can communicate with the configuration node, then it is reported in the system event log.
When the node error code indicates that a critical error was detected that prevents the node from becoming a member of a clustered system, the Node fault LED is on.
Node Error
550 000125The additional data is unique for any error code. It provides the necessary information to isolate the problem in an offline environment. Examples of extra data are disk serial numbers and field replaceable unit (FRU) location codes. For more information, refer to the help for the specific three-digit node error.
Node errors can be divided into critical node errors and noncritical node errors.
Critical errors
A critical error means that the node is not able to participate in a clustered system until the issue that is preventing it from joining a clustered system is resolved. This error occurs because part of the hardware fails or the system detects that the software is corrupted. 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. Resolve the errors in priority order. The range of critical errors is 500 - 699.
Noncritical errors
A noncritical error code is logged when a hardware or code failure is related to 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, an alert describes the error condition. The range of errors that are reserved for noncritical errors are 800 - 899.