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 > Maintain NNMi > Export and Import Configuration Settings > Replicate Configuration Settings on Another NNMi Management Server

Replicate Configuration Settings on Another NNMi Management Server

You can export configuration settings and import them onto another NNMi management server to save time.

Note You can change the names of the exported files before importing. The import still works the same.

Caution Do not edit the exported file before importing.

To move configuration settings to another NNMi management server:

Import behavior is determined when you generate the Export files. Make sure you understand your Import behavior choices before you begin. See Export/Import Behavior and Dependencies (consider printing that topic for reference).

Caution The locale setting on the NNMi management server at the time of Export must match the locale setting on the NNMi management server at the time of Import. Otherwise, you risk losing data. Also, make sure that both NNMi management servers have the same NNMi version/patch number.
A user name and password are required with the export command:

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.

-u <NNMiadminUserName> -p <NNMiadminPassword>
At the command line of the NNMi management server export all configuration settings. For example:

nnmconfigexport.ovpl –c all -f <directory>
Note Note the following:
- You can use -x <file_prefix> to provide a unique prefix to the set of exported files. For example, use today's date or a clue about the reason you needed the files:
  
  nnmconfigexport.ovpl –c all -f <directory> -x <file_prefix>
- You can change the names of the exported files before importing. The import still works the same.
Verify that all required xml files are in the specified directory.

To import the configuration settings onto the other NNMi management server:

Import behavior is determined when you generate the Export files. Make sure you understand your Import behavior choices before you begin. See Export/Import Behavior and Dependencies (consider printing that topic for reference).

Caution The locale setting on the NNMi management server at the time of Export must match the locale setting on the NNMi management server at the time of Import. Otherwise, you risk losing data. Also, make sure that both NNMi management servers have the same NNMi version/patch number.
A user name and password are required with the import command:

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.

-u <NNMiadminUserName> -p <NNMiadminPassword>
Verify that all required xml files are in the specified directory.
Use the nnmconfigimport.ovpl command with the -sync option to replace the configuration settings on the current server with those that were exported. For example:

nnmconfigimport.ovpl -sync -f <filename>

nnmconfigimport.ovpl -sync -f <directory>

Tip You can use -x <file_prefix> to specify a unique prefix for a set of files:

nnmconfigimport.ovpl -f <directory> -x <file_prefix>

When you use the nnmconfigimport.ovpl -sync option, NNMi does the following:
- NNMi replaces all object instances with matching key identifiers (see Troubleshooting Imports of Configuration Files for information about key identifiers).
- NNMi adds all object instances with key identifiers that do not exist in the NNMi database
- NNMi deletes all existing object instances with key identifiers that do not match any in the exported file.

If you encounter problems, see Troubleshooting Imports of Configuration Files.

Additional import options for timeout or memory issues:

You can append the following options to any import command if you encounter problems:

Option	Description	Default Setting
`-timeout <seconds>`	For larger data imports, you might encounter timeout issues. To increase the number of seconds that NNMi waits (per file) during an import, append the `-timeout` option to the end of your command line.	1800 seconds (minimum)
`-memory <megabytes>`	For larger data imports, you might encounter memory issues. To increase the number of megabytes allotted to memory during an import, append the `-memory` option to the end of your command line.	512 megabytes

After completing the import, open NNMi and verify your configuration settings.

Send Help Center feedback