...
Managing and monitoring a large network of devices requires a scalable, high availability and easy to manage solution. opHA 3.0.5 brings a new feature that allows to centralise the configuration files from the master Primary and send it to the pollers. The configuration files can be applied in NMIS and OMK. This partial configuration files would override the configuration that the poller has.
...
- The first step is create a file from a template (NMIS or OMK)
- Validate and save the file
- Create a group. By default, the following groups are created:
- pollers: With contains all peers
- masterPrimary: With the local machine
- Assign peers to a group
- Assign group to a configuration file
- Push the configuration file: The file will be send to the peers and restart the daemons when needed (You will see a message when it is necessary).
...
Please note that once we change NMIS or OMK configuration from the masterPrimary, it is not intended to be edited from the own poller.
...
When we update the configuration in NMIS from a masterPrimary, we are going to see a message on the NMIS configuration screen, and we are not going to be able to update the configuration from NMIS.
...
- Go to the backup directory in the masterPrimary. By default:
- NMIS: <nmis>/backups
- OMK: <omk/conf/conf.d/backups>.
- The backup file should be file_name.nmis.version. For example, authentication.nmis.3
- Rename the file, removing the version. For example, authentication.nmis.
- Move the file to the external configuration folder. By default:
- NMIS: <nmis>/conf/conf.d
- OMK: <omk>/conf/conf.d
- For some of the changes to take effect, the corresponding daemon should be restarted. For example:
- service nmis9d restart
...
- <omk>/bin> ./opha-cli.pl act=cleanup : The purpose is cleaning master Primary files and metadata. Must be run from the masterPrimary. Will check for:
- Metadata without a file associated in the file system
- Orphan files in the file system
- Backup files
- <omk>/bin> ./opha-cli.pl act=cleanup_poller : The purpose is cleaning poller files. Will check for:
- Orphan backup files from OMK.
- Check for duplicated configuration items in OMK: This means that there is the same configuration item in different configuration external files. This could led us to errors, as the one which is loaded first is going to override the other.
- Check for duplicated configuration items in NMIS.
- <omk>/bin> ./opha-cli.pl act=clean_orphan-nodes : Will remove the nodes with no cluster_id associated. Will ask for confirmation for each node if simulate=f is specified.
...