...
Accessing from the menu Views > Configuration, we can see a list of the configured files.
Create a new configuration file
We can create a new configuration file clicking on the button "New Configuration File":
We would need to introduce:
...
- The file type: If NMIS or OMK. It is very important to select the right type, as it is going to be applied on different products.
- The file subtype: We can choose the subtype depending on the type.
- The file name (Cannot be empty and had .nmis extension).
Once we select a type, we would see a template loaded into the editor. A generic templated will be loaded if the file is not opCommon (OMK) or Config (NMIS).
| Status | ||||
|---|---|---|---|---|
|
...
When we update the configuration in NMIS from a master, 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.
Peer
If a peer role is set to be a poller, opHA menu is not going to be available:
Restoring a Backup
By default, two backup files are saved in the poller in the directory <nmis>/backups or <omk/conf/conf.d/backups>. This configuration can be changed in the configuration file:
...
- '<nmis_conf_ext>' => '<nmis_conf>/conf.d'
Known issues
These are the know issues from this version (Will be solved in next releases):
Considerations
Once a peer is edited from opHA, is important to know:
- The configuration files pushed cannot be removed. But you can send the file again to override the necessary configuration.
- Backup files are saved, but it is not possible to rollback from the GUI. By default, configuration files have 2 backup files.
- Once you edit NMIS configuration, it is not possible to edit from the GUI. You will see a message when there are some configuration files overriding the local configuration.
- If the daemon is going to be restarted, it is not going to see the result on the log. But we can be