nnmincidentcfgdump.sh

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

Name

nnmincidentcfgdump.sh — copies incident configuration data from the database into a tag formatted file.

SYNOPSIS

nnmincidentcfgdump.sh { -dump <filename> [-authorKey <author(s)> | -name <names(s)> | -oid <oid pattern(s)> | -mib <mib name(s)>] [-type <type(s)>] [-timeout <timeout>] [-memory <memory>] [-u <user name> -p <password>] [-jdniHost <host name> -jdniPort <port>] } { -listAuthors [-u <user name> -p <password>] [-jdniHost <host name> -jdniPort <port>] }

DESCRIPTION

nnmincidentcfgdump.sh is used to copy incident configurations from the database into a tag formatted file. These configuration files can be edited and loaded back into the database by using nnmincidentcfgload.sh.

Valid configuration types include the following:

*MgmtEventConfig
*PairwiseConfig
*SnmpTrapConfig
*SyslogMessageConfig]

Incident configurations must first have been created using the NNMi console or be loaded into the database using the nnmincidentcfg.sh command.

Parameters

nnmincidentcfgdump.sh supports the following options:

-dump <filename>

Specifies the destination file to which the incident configurations will be copied. If this file exists on the filesystem before the configuration is copied, the user will be notified to delete it.

-authorKey <author(s)>

Specifies the author keys to include in the formatted configuration file. All configurations which are tied to the specified author keys are included. If this argument is not provided all author keys are included.

Cannot be used with the -name, -oid, or -mib parameters

-name <name(s)>

Specifies one or more incident configuration names to include in the formatted configuration file. All configurations with matching names will be included. If this argument is not provided all incident configurations for the specified type are included.

Cannot be used with the -authorKey, -oid, or -mib parameters

-oid <oid pattern(s)>

Specifies one or more Object Identifier (OID) patterns to be included in the formatted configuration file. The OID Pattern must follow these syntax requirement:

*Can contain one wild card "*". 
*Must start with ".".
*Can contain only numbers or wild card separated by "."

Cannot be used with the -name, -authorKey, -mib, or -type parameters

-mib <mib names(s)>

Specifies the MIB module that must be contained in an incident configuration to be included in the formatted configuration file. Note the following requirements for the MIB module name:

*Must already exist in the NNMi database.
*Must already have traps loaded in the NNMi database.

Cannot be used with the -name, -authorKey, -oid, or -type parameters

-type <type(s)>

Specifies one or more configuration types to include in the formatted configuration file. Only the configuration types that are specified are included. If this argument is not provided all configuration types are included.

Valid configuration types include the following:

NOTE: Configuration types are not case sensitive.

*MgmtEventConfig
*PairwiseConfig
*SnmpTrapConfig
*SyslogMessageConfig

Cannot be used with the -oid, or -mib parameters

-timeout <timeout>

Specifies the transaction time out in seconds that NNMi should use for the nnmincidentdump.sh command.

-memory <memory>

Specifies the maximum heap size in Megabytes (MB). The minimum <memory> value is 512 MB. The default <memory> value is 1536 MB.

-u <username>

You must supply the root (UNIX) username to run the script.

-p <password>

You must supply the root (UNIX) password to run the script.

-jndiHost <host name>

The server JNDI host. The default value is localhost.

-jndiPort <port>

The server JNDI port. The default value is 1099.

EXAMPLES

Include the entire Events configuration:

nnmincidentcfgdump.sh -dump full-dump.tag

Include all Management and Snmp Trap configurations:

nnmincidentcfgdump.sh -dump type-dump.tag -type MgmtEventConfig SnmpTrapConfig

Include all NNMi and Customer Event configurations:

nnmincidentcfgdump.sh -dump nnm-and-customer-author-dump.tag -authorKey com.hp.nms.author.nnm com.customer.author

Include all NNMi Management Event configurations:

nnmincidentcfgdump.sh -dump author-type-dump.tag -authorKey com.hp.nms.author.nnm -type MgmtEventConfig

Include the following named configurations, NodeDown and DuplicateCorrelation:

nnmincidentcfgdump.sh -dump names-dump.tag -name NodeDown DuplicateCorrelation

Include all trap configurations that were loaded by the CISCO-VTP-MIB to a tag file named ciscoVtpMib.tag:

nnmincidentcfgdump.sh -dump ciscoVtpMib.tag -mib CISCO-VTP-MIB

Include the SnmpLinkDown/Up trap configurations:

nnmincidentcfgdump.sh -dump snmpLinkDownAndUp.tag -oid .1.3.6.1.6.3.1.1.5.3 .1.3.6.1.6.3.1.1.5.4

Include all LinkDown trap configurations (This includes CiscoLinkDown):

nnmincidentcfgdump.sh -dump linkDownTraps.tag -oid .1.3.6.1.6.3.1.1.5.3.*

Include all CiscoSNMPTrap configurations:

nnmincidentcfgdump.sh -dump ciscoSnmpTraps.tag -oid .1.3.6.1.6.3.1.1.5.*.1.3.6.1.4.1.9

List all available author key / label pairs

nnmincidentcfgdump.sh -listAuthors

AUTHOR

nnmincidentcfgdumpshwas developed by Hewlett Packard Enterprise.

FILES

Configuration formats, and example configuration files for each configuration type are provided under the following directory.

 /opt/OV/examples/nnm/incidentcfg