| Table of Contents |
|---|
...
Storage cluster nodes are controlled through the SNMP action commands. The following OIDs allow disabling nodes and volumes with nodes from a storage cluster:
castorShutdownAction. Disable nodes and volumes within nodes for servicing.
castorRetireAction. Disable nodes and volumes within nodes for retirement.
Shutdown Action for Nodes
| Info |
|---|
RequiredIf you permanently remove a storage node's IP address from a storage cluster, you must also remove the reference to the storage node from the
|
To gracefully shut down a Swarm node, the string shutdown is written to the castorShutdownAction OID. Writing the string reboot to this OID causes a Swarm node to reboot.
...
Retire Action for Nodes and Volumes
| Info |
|---|
RequiredIf you permanently remove a storage node's IP address from a storage cluster, you must also remove the reference to the storage node from the
|
The Retire action is used to permanently remove a node or a volume within a node from the cluster. This action is intended for retiring legacy hardware or preemptively pushing content away from a volume with a history of I/O errors. Retired volumes and nodes are visible in the Swarm Admin Console until the cluster is rebooted.
...
Each volume is given a unique name within the node – the device string from the vols line in the configuration file. To retire a volume, the name is written as a string to the castorRetireAction OID. The volume retirement process is initiated immediately upon receipt and the action cannot be aborted after it starts.
To manually retire a volume,
Open the Swarm UI (or legacy Admin Console).
Click the targeted chassis/node (IP address).
For the targeted disk/volume, select Retire.
Entire node
Retiring a node means all volumes on the node are retired at the same time. After all volumes in the node are retired and the node data is copied elsewhere in the cluster, the node is permanently out of service and does not respond to further requests.
To retire a node and all volumes, the all string is written to the castorRetireAction OID. The node retirement process is initiated immediately upon receipt and the action cannot be aborted after it starts.
...