Opmantek System Configuration is a new admin tool to edit all the NMIS and Opmantek configuration and to manage all nodes from an unified and centralised easy to use GUI.
This is available under the following link:
In a opHA environment, it is also possible to manage remote nodes. Even relocate the nodes from one poller to another.
Custom role types
If we have custom net types, nodes or custom role types in any poller, we also add this types into our nmis configuration file (nmis9/conf/Config.nmis) in the master:
"roletype_list" => "default,core,distribution,access",
"nettype_list" => "default,wan,lan,vpn,man,san,voice",
"nodetype_list" => "default,generic,switch,router,firewall,server",
We can also manage the nodes using the API.
Important: All this methods are authenticated.
We should receive a 200 response and a cookie, that we can reuse for next API calls.
If any operation has a remote cluster id, the API will try to edit in the remote server. If this operation is not possible, it will fail.
In order to succeed:
- opHA needs to be pulling that peer. This is because the peer sends the API url to update the remote in the registry data. And this information should be updated at least once a day.
- The peer has to be online.
If we should edit the remote node locally for some reason, we should use opnode_admin cli tool.