Node Decommissioned But Did Not Reboot

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:

Visibility:: not set

Votes:: 0

Category:: not set

Specialty:: not set

Last Updated:

Applies to

ONTAP 9

Issue

After decommissioning node from cluster, the node was removed from the cluster
but did not reboot. The node continued to show configuration data and network
connectivity when accessed directly, despite being absent from the cluster
management interface.

Attempts to run cluster remove-node and cluster unjoin commands from both the
remaining cluster nodes and the affected node failed, returning errors such as:

Error: "node_name" is an invalid value for field "-node "_x000D_
Valid choices in this command's context: (available nodes)_x000D_
_x000D_
Error: command failed: Cannot remove a node on which the remove-node command is invoked. Please connect to any other node in the cluster to remove this node._x000D_

Console output from the affected node also showed:

The management gateway server restarted. Waiting to see if the connection can be reestablished..._x000D_
:spm.mgwd.process.exit:EMERGENCY]: ManagementGateway (mgwd) subsystem with ID 3378 exited as a result of signal normal exit (0). The subsystem will attempt to restart._x000D_
The connection with the management gateway server could not be reestablished._x000D_
The most recent coredump file is: /mroot/etc/crash/mgwd