Removing a node is not something you would normally need to do unless aliases for different machines have gotten so mixed up that you face the choice of pruning nodes or reinstalling the system. Under most circumstances (bad hosts file corrected, DNS alias changed to point to a different machine), removing an alias from one node and adding it back to a different node should be all that you need to do.
btmcli removeNode -n nodeName -alias aliasName -s sphereUrl -l username:password
|-n||-name||The canonical name of the network node. Typically a fully-qualified domain name. For example, jbujes-myPC.edgility.com|
|-f||-force||Forces the node to be removed even if it is still referenced by containers or entry points.
If you assign this node's aliases to another network node before you remove this node, you can enable a container to associate itself with a different node.
|-s||-sphereUrl||The URL of the sphere.
This flag is not required if you have set the AP_SPHERE_URL environment variable for your sphere.
|-l||-userLogin||The username and password associated with the sphere, in the format: username:password. This set of credentials must belong to a user in the btmadmin role.
See Security Options in Accessing CLI Commands for information on furnishing login credentials.
You can encrypt passwords using the
The following example shows the
btmcli removeNode -n jbujes.edge.com -s http://localhost:8080/btmcentral/sphere/ -l username:password