...
| Code Block |
|---|
./node_admin.pl act=delete node=ripnode confirm=YES deletedata=1 Successfully deleted ripnode |
A backup will be created by default from NMIS 9.1.1 based in the configuration options:
| Code Block |
|---|
backup_node_on_delete => true by default.
keeprrds_on_delete_node => false by default.
node_dumps_dir => Delete backup dir, by default in var/node_dumps
purge_node_dumps_after => 30 by default |
Background Operations
From NMIS 9.1.1, the basic operations can be run in the background with new jobs for the scheduler. It is so simple as adding schedule=1 for create, update, remove and set operations.
As an example:
| Code Block |
|---|
./node_admin.pl file=node1.json act=create schedule=1
Job 5f6492872b1813263276fda1 created for type create_nodes and 1 nodes. |
update and create operations were improved allowing an array of nodes in the json file.
Remote Nodes Operations
From NMIS 9.1.1, NMIS accepts operations with remote nodes. It is so simple as adding server=server_name|server_id for create, update, remove and set operations.
As an example:
| Code Block |
|---|
./node_admin.pl node=asgard1234 confirm=YES act=delete server=285b0b31-dfa5-4a46-a55b-a66384727dc8
Successfully marked for delete node (2). |
opHA will process later these operations and will update the changes in the remote nodes.
Please note, for delete operation, the node will be marked for delete, but won't be removed until opHA will process that node.
Poller Server
From NMIS 9.1.1, if a node is marked as as Poller, the actions in the node_admin tool will be limited to list/show/dump/restore.
Node Properties
NMIS uses a subset of the node properties of the commercial Opmantek tools. node_admin.pl act=mktemplate includes a very brief listing of the most essential ones from NMIS' perspective, and the Common Node Properties wiki page describes most of the important ones in greater detail.
...