...
To run the integration, simply invoke the executable and pass it a configuration file as described in the previous section. You can also invoke the tool by itself, which will look for a configuration file at conf/nmisIntegration.nmis by default.
The rest While most of the integration is completely driven by the options set in the configuration file, additional options can be passed at runtime. These options can be seen in the usage instructions for the integration script.
| Code Block | ||
|---|---|---|
| ||
# Calling the tool with a custom-named configuration file
./bin/oa_nmis_integration.pl conf=conf/my_custom_config.nmis
# Calling the tool by itself (uses conf/nmisIntegration.nmis)
./bin/oa_nmis_integration.pl
# Show the usage instructions
./bin/oa_nmis_integration.pl -h |
Special Cases
This section documents the behaviour that can be expected from the integration in special cases such as a node being deleted from one system or another.
| Case | Behaviour |
|---|---|
| Previously integrated node is deleted from NMIS | A new node will be created in NMIS (to avoid this, update the query/device in Open-Audit) |
| Previously integrated device is deleted from Open-AudIT | A If the flag 'delete_missing_nodes' is provided at execution time, a delete operation will run on the matching NMIS node. Note that this will also apply if the |
| Previously integrated node is renamed in NMIS | Similar to a node being deleted in NMIS - the integration cannot find the node it is supposed to be updating and so a new node is created. |