...
Once opConfig has been installed, we need to set up the nodes. For this, we go to System > Edit Nodes.
All the local and remote nodes (Remote nodes are seen since version 4.1.1) are listed here:
Click in the button "Refresh OS Info all Nodes" for to update the OS Info for all the local nodes. In this case, it would not take into account if the node is active for opConfig or not for a node to be selected.
This button will update the OS information for a node based on the file OS_Rules.nmis, located in the configuration directory by default. This These rules are based, mostly, in on the sysDescr configuration attribute. For this to be set, the community string must be correct and the device should had have been successfull successfully polled from NMIS at least , once. We can check this attribute - information, among others - , in the node information, by clicking in the node name.
...
We can also set up this configuration using the cli tool.
Note that, for remote nodes (Since version 4.1.1):
- The information will be updated in the poller also.
- If the node cannot be edited, the node won't be saved (As the changes will be overwritten by the opHA synchronisation).
- Is important that the poller has installed opConfig version 4.1.1 or higher.
- A remote node cannot be removed from the Primary.
Steps to set up a Node
If a node has been added, these are the steps to perform for this node to be ready to work with opConfig:
...
No nodes match your selections and the config set filters! A config set has a set of filters that has to mach with the selected node properties. For example, the selected Config set has the following filter:
| Code Block |
|---|
"filter" : {
"activated.opConfig" : 1,
"connection_info.transport" : "SSH",
"name" : [
"node1",
"node2",
"node3"
]
}, |
...
The Virtual Operator is used to help create jobs comprised of commands sets to be run on various nodes, reporting to see job results and troubleshooting to diagnoses nodes which raise conditions. You can find a complete Virtual Operator guide in this link.
Nodes Management
From the System > Edit Nodes menu we can see all nodes, a node details and Edit or add a new node. From the node details, we can Test the connection to a Node, or Discover the Node.
From opConfig 4.0.0, nodes information is shared between NMIS and opConfig, so the "Import Nodes from NMIS" option is not available anymore.
Credential Sets
Credentials for all connections made by opConfig are configurable from the opConfig GUI ONLY. Before anything else you need to create sets of credentials to access you devices. At this point in time, opConfig supports only Telnet and SSH, and for SSH password-based authentication and RSA with no passphrase is supported.
...
Only "command" type jobs will be saved in the queue, to better keep track of the operations run.
Related Configuration for Change Notification
See the documentation for What constitutes a change, and when should opConfig create new revisions
Useful Configuration Items
...
- opConfig 4 Getting Started Guide
- opConfig 4 release notes
- opConfig 4 Troubleshooting
- opConfig CLI tool