Transfer Specific Configuration Settings to Another NNMi Management Server

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

To move configuration settings to another NNMi management server:

1. 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.

2. 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>

3. Check whether the configuration settings you want to export have dependencies, see Export/Import Behavior and Dependencies.

   • If no dependencies, export only the configuration settings you are planning to change.
   • If yes, decide if you need a copy of the dependencies (only if you plan to make changes to those configuration settings, as well). Then export all the required files.

4. To export only the configuration settings for either the Device Profiles, Incident, or URL ActionsExport/Import Behavior and Dependenciesworkspace by author, use the export command with the workspace and author key as shown in the following example.

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

   nnmconfigexport.ovpl -c device -a <authorUniqueKey> -f <directory>

   Repeat the export command for each configuration item modified by that author that you want to export. Add the -a <authorUniqueKey> attribute to the command and provide the Unique Key.

   Tip Find the Unique Keys for all authors by exporting an author.xml file, then open the file in a text editor and locate the Key attribute values.

   Find the Unique Key for a particular Author, in the NNMi console:

   1. Open one of these Configuration workspaces in the NNMi console: Device Profiles Configuration, Incidents, or URL Actions.
   2. Select an object created by the Author of interest.
   3. Display the Author form, and copy the value of the Unique Key attribute.

5. Verify that all required xml files are in the specified directory.

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

1. 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.

2. 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>

3. Verify that all required xml files are in the specified directory.

4. At the command line of the NNMi management server, type the appropriate command to import the configuration files that you gathered for transfer:

   nnmconfigimport.ovpl -f <filename>

   nnmconfigimport.ovpl -f <directory>

   Note Note the following:

   • When importing multiple XML files at once using -f <directory>, the NNMi nnmconfigimport.ovpl command takes care of ordering issues.

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

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

   • You cannot use the -sync option when configuration settings have been exported by specifying -a <authorUniqueKey>.

5. 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

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