Administer > Configure Incidents > Manage Incidents Using Incident Configurations > Using the Command Line to Manage Incident Configurations > Load Incident Configurations Using the Command Line

Load Incident Configurations Using the Command Line

Tip If you do not want to enter an NNMi User Name attribute value and an NNMi Password attribute value at the command line, you can use the nnmsetcmduserpw.ovpl command to specify the valid user name and password (instead of -u and -p). The credentials set using the nnmsetcmduserpw.ovpl command are valid for command execution by the same user. See Set Up Command Line Access to NNMi for more information.

The NNMi nnmincidentcfgload.ovpl script provides a way for you to load Incident Configurations into the NNMi database from a formatted configuration file.

Tip Use the nnmincidentcfgdump.ovpl script to create a configuration file of existing Incident Configurations in a non-xml format. You can then edit this file if desired before loading them into the NNMi database.

See the following directory for the required format (see Manage environment variables):

Windows 

%NnmInstallDir%/examples/nnm/incidentcfg 

Linux 

$NnmInstallDir/examples/nnm/incidentcfg 

To validate an Incident Configuration file before it is loaded into the NNMi database, use the following example syntax:

nnmincidentcfgload.ovpl -validate <file_name> -u <NNMiadminUsername> -p <NNMiadminPassword>

To load Incident Configurations, use the following example syntax:

nnmincidentcfgload.ovpl -load <file_name> -u <NNMiadminUsername> -p <NNMiadminPassword>

Note the following: 

  • NNMi updates all configurations that have matching names or other matching key identifiers.

    Caution NNMi also overwrites the values of any codes associated with these configurations (for example, incident Family).

  • NNMi adds all incident configurations with key identifiers that do not exist in the NNMi database.
  • NNMi does not change existing incident configurations with key identifiers that do not match any in the exported file.
  • NNMi resolves Universally Unique Object Identifiers (UUIDs) if they are not provided in the configuration file.
  • If NNMi is unable to resolve a UUID, a UUID is created.

See nnmincidentcfgload.ovpl for more information, including a complete list of the valid script arguments.

nnmincidentcfg.ovpl Arguments
Argument Description
-load <file_name>

Use to load the Incident Configurations generated using either the nnmincidentcfgdump.ovpl script or created from a template file provided by NNMi.

To create an Incident Configuration file without using existing Incident Configurations, start with one of the template files and required formats provided in the following directory (see Manage environment variables):

Windows

%NnmInstallDir%/examples/nnm/incidentcfg 

Linux

$NnmInstallDir/examples/nnm/incidentcfg

-validate <file_name>

Optional. Use to validate the contents of the Incident Configuration file generated using nnmincidentcfgdump.ovpl.
-expression <expression> Specifies the filter expression you want to validate.
-u

Optional. The NNMi user name. This User Account must be assigned to the NNMi Administrators User Group.
-p

Optional. The password associated with the NNMi user name.

Send Help Center feedback