Difference between revisions of "Removing a Node From the Registry"
From Internet Computer Wiki
Katie.peters (talk | contribs) (Creating the page) |
Katie.peters (talk | contribs) |
||
Line 21: | Line 21: | ||
* If it was healthy, has had no problems, and does not need firmware or anything else updated, then simply re-insert the HSM and reboot the server, and it will rejoin with the same node ID principal it was deployed with. | * If it was healthy, has had no problems, and does not need firmware or anything else updated, then simply re-insert the HSM and reboot the server, and it will rejoin with the same node ID principal it was deployed with. | ||
* If it had problems, had hardware replaced, had firmware updated, etc., then please do a fresh redeployment. | * If it had problems, had hardware replaced, had firmware updated, etc., then please do a fresh redeployment. | ||
+ | |||
[[Node Provider Documentation|Return to Node Provider Documentation]] | [[Node Provider Documentation|Return to Node Provider Documentation]] | ||
+ | |||
[[Node Provider Troubleshooting|Return to Node Provider Troubleshooting]] | [[Node Provider Troubleshooting|Return to Node Provider Troubleshooting]] |
Revision as of 18:39, 15 November 2023
Removing a node from the registry via DFX
- Ensure that the node does not exist in any subnet.
- Get the HSM (NodeOperator Key) from the data center.
- Insert it into a computer that has DFX installed and has internet access.
- Using the terminal, execute the following command (Where NODE_ID is the principal as shown on the dashboard of the node to remove):
IF USING PHYSICAL HSM:
$ dfx identity new node-operator-hsm --hsm-key-id 01 --hsm-pkcs11-lib-path /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
$ dfx canister --network ic --identity node-operator-hsm call rwlgt-iiaaa-aaaaa-aaaaa-cai remove_node_directly '(record { node_id = principal "NODE_ID" })'
IF USING NO HSM:
$ dfx identity import node_operator node_operator_private_key.pem --storage-mode=plaintext
$ dfx canister --network ic --identity node_operator call rwlgt-iiaaa-aaaaa-aaaaa-cai remove_node_directly '(record { node_id = principal "NODE_ID" })'
When the node is ready to be re-registered:
- If it was healthy, has had no problems, and does not need firmware or anything else updated, then simply re-insert the HSM and reboot the server, and it will rejoin with the same node ID principal it was deployed with.
- If it had problems, had hardware replaced, had firmware updated, etc., then please do a fresh redeployment.