Name

nnmconfigexport.ovpl — Export the configuration to one or more files that can be imported on another system.

SYNOPSIS

nnmconfigexport.ovpl -? | -c <configuration>[,configuration...] [-a <author_key>] [-u <username> -p <password>] [-x <file_prefix>] [-f <output file or directory>]

DESCRIPTION

nnmconfigexport.ovpl is a Perl script that enables you to export the customized configuration to stdout, or to save it in a file.

Parameters

nnmconfigexport.ovpl supports the following options:

-?

Displays the usage statement.

-u <username>

Supply the NNMi administrator username to run the script. This script requires the NNMi administrator username unless you use an nnm.properties file. See the nnm.properties.4 reference page for more information.

-p <password>

Supply the NNMi administrator password to run the script. This script requires the NNMi administrator password unless you use an nnm.properties file. See the nnm.properties.4 reference page for more information.

-c <configuration>[,configuration...]

Exports the XML schema for the specified configuration. Use a comma separated list for multiple configurations. If there are multiple configurations, you must specify a directory when using the -f option.

Valid configurations:

account

Exports user accounts, user roles, user principals, user groups and user account mappings.

author

Exports authors. Can be optionally filtered using the -a argument.

customCorrelation

Exports custom correlation configuration. Can be optionally filtered using the -a argument.

comm

Exports communication configuration. Does not export SNMPv3 communication configuration and device credentials. The encryption algorithms used with this data rely on an internal key specific to the NNMi installation. It is not possible to import this data, so the data is excluded from the export.

custpoll

Exports custom poller configuration.

device

Exports device profiles. Can be optionally filtered using the -a argument.

disco

Exports discovery configuration (does not include seeds).

discoseed

Exports discovery seeds.

icons

Exports icons.

ifgroup

Exports interface groups.

iftype

Exports interface types (IfTypes). Can be optionally filtered using the -a argument.

incident

Exports incident configuration. Can be optionally filtered using the -a argument.

menu

Exports menus. Can be optionally filtered using the -a argument.

menuitem

Exports all menu items configured for the Actions menu. If you supply the -a argument, the output contains the related parent menus and sub-menus.

mibexpr

Exports MIB expressions. Can be optionally filtered using the -a argument.

mibtypes

Exports MIB OID Types.

monitoring

Exports monitoring configuration.

nodegroup

Exports node groups.

ngmap

Exports node group maps. The node host names must match between both NNMi management servers for the node coordinates to import successfully.

oam

Exports Overlapping Address Mappings.

rams

Exports one or more route analytics management server configurations.

NOTE: The Query Password field of a RAMS configuration will only be valid when you import it into the same NNMi installation on the same system. If you import the Query Password field into a different system, you will have to re-enter the Query Password.

security

Exports security groups and tenants.

securitymappings

Exports security group mappings.

station

Exports NNM 6.x/7.x management stations.

status

Exports the node group status configuration.

trap

Exports the trap logging configuration. Can be optionally filtered using the -a argument.

ui

Exports user interface settings.

all

Exports all of the available configuration areas. If you use this option, you must direct the output to a directory.

-a <author_key>

Export only the configuration items created by author with key author_key in a special XML format used for incremental import. The nnmconfigimport.ovpl script automatically detects this XML format. You do not need to use a special option when using the nnmconfigimport.ovpl script. This option is only available for configurations author, customCorrelation, device, incident, menu, and menuitem. You can find available author keys by doing an export of authors. See the examples shown below.

-f <output file or directory>

Saves the output to the specified file or directory.

-x <file_prefix>

A file name prefix that is used to name files when the specified output is a directory. Files will be named <prefix>-<area>.xml.

EXAMPLES

nnmconfigexport.ovpl -u myusername -p myadminpassword -c comm

Exports the communication configuration to stdout.

nnmconfigexport.ovpl -u myusername -p myadminpassword -c comm,disco -f /tmp -x my

Exports the communication and discovery configurations to files named /tmp/my-comm.xml and /tmp/my-disco.xml.

nnmconfigexport.ovpl -u myusername -p myadminpassword -c author

Exports all authors with author key and label to stdout.

nnmconfigexport.ovpl -u myusername -p myadminpassword -c menuitem -a com.mycorp.nnm.author -f /tmp/mycorpmenuitems.xml

Exports the menuitem configuration created by author with key com.mycorp.nnm.author to the /tmp/mycorpmenuitems.xml file.

AUTHOR

nnmconfigexport.ovpl was developed by Hewlett Packard Enterprise.

SEE ALSO

nnmconfigimport.ovpl(1M), nnm.properties(4).

Return to Reference Pages Index