8.4.2 Using nnmincidentcfgload.ovpl to load the incident configuration
In NNMi, you can use the nnmincidentcfgload.ovpl script to load the incident configuration from a formatted configuration file into the NNMi database.
For details about the required format, see the following directory:
Windows: %NnmInstallDir%examples\nnm\incidentcfg
Linux: /opt/OV/examples/nnm/incidentcfg
To validate the incident configuration file before loading it into the NNMi database, use the following sample syntax:
nnmincidentcfgload.ovpl -validate file-name -u NNMi-admin-user-name -p NNMi-admin-password
To load the incident configuration, use the following sample syntax:
nnmincidentcfgload.ovpl -load file-name -u NNMi-admin-user-name -p NNMi-admin-password
Note the following:
NNMi updates all settings that have a matching name or similar key identifier.
Use the nnmincidentcfgdump.ovpl script to create a non-XML file from the existing incident configuration file. If necessary, you can then edit this file before you load it into the NNMi database.
NNMi also overwrites the code values (such as incident families) associated with these settings.
NNMi adds all incident settings that have key identifiers that are not in the NNMi database.
NNMi does not change any existing incident setting that does not have a matching key identifier in the export file.
NNMi resolves any unique object ID (UUID) if it is not provided in the configuration file.
If NNMi cannot resolve a UUID, that UUID is created.
- Important
If you change a file while the system is operating in High Availability (HA) mode, you must make the change on both nodes in the cluster. When you use NNMi in an HA configuration, if the change requires you to stop and restart the NNMi management server, you must place the nodes in maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.
For details, see the reference page for the nnmincidentcfgload.ovpl command.