...
When using an opHA NMIS cluster most node admin is performed on the "Main Primary" server, more details about that @ opHA 3 Redundant Node Polling and Centralised Node Management
Get opConfig working on all my nodes
Use the opAdmin GUI to bulk edit nodes
The opConfig User Manual includes details on this: opConfig 4 User Manual, if you are using an opHA cluster, you will need to activate the nodes on the primary and then do the discovery on the poller.
In summary, on the primary access the Node Admin tool, https://server.domain.com/en/omk/admin/nodes, and select the nodes.
Then activate them for opConfig, and click OK.
This will activate many nodes at once and it will all be sent to the necessary poller.
Automating for many nodes using simple scripts and CLI tools
Scripts are useful when you want things to happen repeatedly, or you have so many things to click on, scripting is faster than clicking.
Get a list of nodes using node_admin.pl
To get a list of nodes is easy, just ask node admin to get you a list.
...
| Code Block |
|---|
/usr/local/nmis9/admin/node_admin.pl act=list group=GROUPNAME |
Using a script to active nodes for opConfig
The following BASH script will let activate opConfig for all nodes on the primary server, opHA will then synchronise this to all the pollers.
...
| Code Block |
|---|
sudo bash enable-opconfig-all-nodes.sh |
opConfig Automation
The following handy BASH script will run an opConfig discovery, which includes OS Info and credential discovery. It will run this for all the nodes and it will only run if the node is enabled in opConfig.
...