Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Configure Incidents > Manage Incidents Using Incident Configurations > Using the Command Line to Manage Incident Configurations > Generate a File of Your Incident Configurations

Generate a File of Your Incident Configurations

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 nnmincidentcfgdump.ovpl script provides a way for you to create or update an Incident Configuration to subsequently load into the NNMi database using the nnmincidentcfgload.ovpl script. The file is generated in a non-xml format.

You can edit the file using the format descriptions provided in the following directory (see Manage environment variables):

Windows

%NnmInstallDir%/examples/nnm/incidentcfg

Linux

$NnmInstallDir/examples/nnm/incidentcfg

To generate a file of your Incident Configurations, use the following example syntax:

nnmincidentcfgdump.ovpl -dump <file_name> -u <NNMiadminUsername> -p <NNMiadminPassword>

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

nnmincidentcfg.ovpl Arguments
Argument	Description
-dump <file_name>	Used to create a file of your Incident Configurations. Tip Incident Configurations can be loaded into the NNMi database using the `nnmincidentcfgload.ovpl` script. To create an Incident Configuration file without using existing Incident Configurations, start with one of the template files provided in the following directory (see Manage environment variables): Windows `%NnmInstallDir%/examples/nnm/incidentcfg` Linux `$NnmInstallDir/examples/nnm/incidentcfg`
-uuid	Recommended. Specifies the Universally Unique Object Identifier (UUID) for each configuration entry. Note Configuration files that do not contain the UUID value take longer to load. See `nnmincidentcfgload.ovpl` for more information.
-authorKey <author or authors>	Optional. Generates an Incident Configuration file that contains the settings created by one or more authors. Note the following: You can include one or more <author> values. If you do not specify any configuration authors, NNMi includes all of the incident configurations. You cannot use this argument with the `-name` argument. To find a Unique Key for a particular author using the command line, execute: `nnmicidentcfgdump.ovpl -ListAuthors` To find the Unique Key for a particular Author in the NNMi console: Open one of the Incident Configuration workspace in the NNMi console. Select an object created by the Author of interest. Display the Author form, and copy the value of the Unique Key attribute.
-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.
-name <name or names>	Optional. Specifies the name of each configuration that should be included in the configuration file you are creating. Note the following: If you do not specify any configuration Names, NNM includes all of the configurations. You cannot use this argument with the `-authorKey` argument.
-type <config_type>	Optional. Specifies the type of configurations you want to include. Valid configuration types include: MgmtEventConfig PairwiseConfig SnmpTrapConfig SyslogMessageConfig
-mib <module_name> or <module_names>	Specifies the MIB module or modules that must be contained in an incident configuration to be included in the formatted configuration file. NNMi includes any SNMP Trap Configurations that contain the specified MIB module. Tip MIB modules are loaded from MIB files using the nnmloadmib.ovpl script. To see what MIB modules are loaded, use the nnmloadmib.ovpl script with the -list option.
-oid <oid_pattern or oid_patterns>	Specifies the Object Identifier (OID) pattern or patterns that must be contained in an incident configuration to be included in the formatted configuration file. NNMi includes any SNMP Trap Configurations that match a specified OID pattern. Each OID pattern can contain one wildcard character (*). See `nnmincidentcfgload.ovpl`for more information.

Send Help Center feedback