nnmincidentcfgdump.ovpl — copies incident configuration data from the database into a tag formatted file.
nnmincidentcfgdump.ovpl {
-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>]
}
nnmincidentcfgdump.ovpl 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.ovpl.
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.ovpl
command.
nnmincidentcfgdump.ovpl 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.ovpl 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 administrator (Windows) or root (UNIX) username to run the script. Required unless a nnm.properties(4) file exists.
-p <password>
You must supply the administrator (Windows) or root (UNIX) password to run the script. Required unless a nnm.properties(4) file exists.
-jndiHost <host name>
The server JNDI host. The default value is localhost.
-jndiPort <port>
The server JNDI port. The default value is 1099.
Include the entire Events configuration:
nnmincidentcfgdump.ovpl -dump full-dump.tagInclude all Management and Snmp Trap configurations:
nnmincidentcfgdump.ovpl -dump type-dump.tag -type MgmtEventConfig SnmpTrapConfigInclude all NNMi and Customer Event configurations:
nnmincidentcfgdump.ovpl -dump nnm-and-customer-author-dump.tag -authorKey com.hp.nms.author.nnm com.customer.authorInclude all NNMi Management Event configurations:
nnmincidentcfgdump.ovpl -dump author-type-dump.tag -authorKey com.hp.nms.author.nnm -type MgmtEventConfigInclude the following named configurations, NodeDown and DuplicateCorrelation:
nnmincidentcfgdump.ovpl -dump names-dump.tag -name NodeDown DuplicateCorrelationInclude all trap configurations that were loaded by the CISCO-VTP-MIB to a tag file named ciscoVtpMib.tag:
nnmincidentcfgdump.ovpl -dump ciscoVtpMib.tag -mib CISCO-VTP-MIBInclude the SnmpLinkDown/Up trap configurations:
nnmincidentcfgdump.ovpl -dump snmpLinkDownAndUp.tag -oid .1.3.6.1.6.3.1.1.5.3 .1.3.6.1.6.3.1.1.5.4Include all LinkDown trap configurations (This includes CiscoLinkDown):
nnmincidentcfgdump.ovpl -dump linkDownTraps.tag -oid .1.3.6.1.6.3.1.1.5.3.*Include all CiscoSNMPTrap configurations:
nnmincidentcfgdump.ovpl -dump ciscoSnmpTraps.tag -oid .1.3.6.1.6.3.1.1.5.*.1.3.6.1.4.1.9List all available author key / label pairs
nnmincidentcfgdump.ovpl -listAuthors