Explanation
On startup, the node was unable to read its state
data. When this happens, it expects to be automatically added back
into a clustered system. However, if it is not joined to a clustered
system in 60 sec, it raises this node error. This error is a critical
node error, and user action is required before the node can become
a candidate to join a clustered system.
User Response
Follow troubleshooting procedures to correct connectivity
issues between the clustered system nodes and the quorum devices.
- Manual intervention is required once the node reports this error.
- Attempt to reestablish the clustered system by using other nodes.
This step might involve fixing hardware issues on other nodes or fixing
connectivity issues between nodes.
- If you are able to reestablish the clustered system, remove the system data from the node that
shows error 578 so it goes to a candidate state. It is then automatically added back to the
clustered system.
- To remove the system data from the node, go to the service assistant, select the radio button
for the node with a 578, click Manage System, and then choose
Remove System Data.
- Or use the CLI command satask leavecluster -force.
If the node does not automatically add back to the clustered system, note the name and I/O
group of the node, and then delete the node from the clustered system configuration (if this has not
already happened). Add the node back to the clustered system using the same name and I/O group.
- If all nodes have either node error 578 or 550, follow the recommended user response for node
error 550.
- Attempt to determine what caused the nodes to shut down.
Possible Cause—FRUs or other: