Export/Import Behavior and Dependencies
Your configuration settings can be exported to make a copy, and then imported onto the same NNMi management server or another NNMi management server. 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.
You need to understand the behavior and dependencies (see the table). The choices that you make when exporting NNMi configuration settings determine how that configuration information can be used:
click here for more information).
- 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.
Note
- To implement the Replaces all behavior for all configuration workspaces so that you can replicate the NNMi configuration from one NNMi management server to another, use the nnmconfigexport.ovpl command with the -c all option and then use nnmconfigimport.ovpl command with the -sync option. See Transfer Specific Configuration Settings to Another NNMi Management Server for more information.
- If you are exporting a customized subset of a configuration workspace using the -a option (for example. -c device -a <authorUniqueKey>), do not use the nnmconfigimport.ovpl command with the -sync option.
click here for more information).
-
NNMi updates all object instances with matching key identifiers (see Troubleshooting Imports of Configuration Files for information about key identifiers).
Caution NNMi also overwrites the values of any codes associated with these object instances (for example, incident family).
- NNMi adds all object instances with key identifiers that do not exist in the NNMi database.
- NNMi does not touch existing object instances with key identifiers that do not match any in the exported file.
click here for more information).
-
NNMi updates all object instances with matching key identifiers (see Troubleshooting Imports of Configuration Files for information about key identifiers).
Caution NNMi also overwrites the values of any codes associated with these object instances (for example, incident family).
- NNMi adds all object instances with key identifiers that do not exist in the NNMi database.
- NNMi does not touch existing object instances with key identifiers that do not match any in the exported file.
To export all of the configuration settings for all of the configuration workspaces, use the -all export option as shown in the following syntax:
nnmconfigexport.ovpl –c -all -f <directory>
See the nnmconfigexport.ovpl and nnmconfigimport.ovpl Reference Pages for more information, including the complete list of the command line arguments for each command.
| Configuration Workspace's View Name | Export Option | Import Behavior |
Dependencies |
|---|---|---|---|
| Author * | -c author | Incremental |
No dependencies. Import requires one Export file (author.xml). * Not a workspace, but an important data object. |
| -c author -a <authorUniqueKey> |
Incremental (subset) | No dependencies. Import requires one Export file (author.xml). | |
| Communication | -c comm | Replaces all |
No dependencies. Import requires one Export file (comm.xml). Caution SNMPv3 configuration settings cannot be exported because SNMPv3 data is encrypted based on the NNMi encryption key (generated during NNMi installation). Therefore, the SNMPv3 encrypted data cannot be imported into another installed version of NNMi because the encryption key is different. |
| Custom Correlations | -c customCorrelation | Incremental or Replaces all |
Import requires two Export files: (1) author.xml and (2) customCorrelation.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c device -a <authorUniqueKey> |
Incremental (subset) |
Import requires one Export file (customCorrelation.xml). The required Author information is embedded in the Export file. |
|
| Custom Poller | -c custpoll | Incremental or Replaces all |
Import requires five Export files: (1) mibexpr.xml, (2) author.xml, (3) device.xml, (4) nodegroup.xml, and (5) custpoll.xml. Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. Note When importing modifications to an existing Custom Poller Collection, NNMi sets the Active State for all associated Policies to Suspended. |
|
Device Profiles |
-c device | Incremental or Replaces all |
Import requires two Export files: (1) author.xml and (2) device.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c device -a <authorUniqueKey> |
Incremental (subset) |
Import requires one Export file (device.xml). The required Author information is embedded in the Export file. |
|
| Discovery | -c disco | Replaces all |
Import requires eight Export files: (1) comm.xml, (2) discoseed.xml, (3) iftype.xml, (4) author.xml, (5) device.xml, (6) ifgroup.xml, (7) nodegroup.xml, and (8) disco.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| Discovery Seeds | -c discoseed | Incremental or Replaces all |
Import requires three Export files: (1) comm.xml, (2) security.xml, and (3) discoseed.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| Global Network Management | No export/import permitted at this time. | ||
| Icons and icon images | -c icons | Incremental or Replaces all |
No dependencies. Import requires one Export file (icons.xml) Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c icons -a <authorUniqueKey> | Incremental (subset) | No dependencies. Import requires one Export file (icons.xml) | |
| Incident | -c incident | Incremental or Replaces all |
Import requires seven Export files: (1) account.xml, (2) author.xml, (3) device.xml, (4) nodegroup.xml, (5) iftype.xml, (6) ifgroup.xml, and (7) incident.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c incident -a <authorUniqueKey> | Incremental (subset) |
Import requires one Export file (incident.xml). The required Author information is embedded in the Export file. |
|
| Interface Groups | -c ifgroup | Incremental or Replaces all |
Import requires five Export files: (1) iftype.xml, (2) author.xml, (3) device.xml, (4) nodegroup.xml, and (5) ifgroup.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| ifTypes | -c iftype | Incremental or Replaces all |
No dependencies. Import requires one Export file (iftype.xml). Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| Menus | -c menu | Incremental or Replaces all |
Import requires two Export files: (1) author.xml and (2) menu.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c menu -a <authorUniqueKey> | Incremental (subset) |
Import requires one Export file (menu.xml). The required Author information is embedded in the Export file. |
|
| Menu items (formally URL Actions) |
-c menuitem (formally -c urlaction) |
Incremental or Replaces all |
Import requires four Export files: (1) author.xml, (2) menu.xml, (3) mibexpr.xml, and (4) menuitem.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
|
-c menuitem -a <authorUniqueKey> (formally -c urlaction -a <authorUniqueKey>) |
Incremental (subset) |
Import requires one Export file (menuitem.xml). The required Author information is embedded in the Export file. |
|
| MIB Expressions | -c mibexpr | Incremental or Replaces all |
Import requires two Export files: (1) author.xml and (2) mibexpr.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c mibexpr -a <authorUniqueKey> | Incremental (subset) |
Import requires one Export file (mibexpr.xml). The required Author information is embedded in the Export file. |
|
| MIB OID Types | -c mibtypes | Incremental or Replaces all |
No dependencies. Import requires one Export file (mibtypes.xml). Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| Monitoring | -c monitoring | Replaces all |
Import requires six Export files: (1) author.xml, (2) device.xml, (3) nodegroup.xml, (4) iftype.xml, (5) ifgroup.xml, and (6) monitoring.xml |
| Node Groups | -c nodegroup | Incremental or Replaces all |
Import requires three Export files: (1) author.xml, (2) device.xml, and (3) nodegroup.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. Caution Island Node Groups are never exported. See Island Node Groups. |
| Node Group Map Settings | -c ngmap | Incremental or Replaces all |
Import requires six Export files: (1) author.xml, (2) device.xml, (3) nodegroup.xml, (4) iftype.xml, (5) ifgroup.xml, and (6) ngmap.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. Note Any time you save a map, NNMi deletes any previous node locations. Therefore, each export contains only the node locations that were last saved. |
| RAMS Servers | -c rams | Incremental or Replaces all |
Router Analytics Management System data from the RAMS Servers view (does not include data from the Integration Module Configuration RAMS MPLS WAN). See RAMS MPLS WAN Configuration (NNMi Advanced) for more information. No dependencies. Import requires one Export file (rams.xml). Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
|
Security Groups Tenants |
-c security | Incremental or Replaces all |
No dependencies. Exports Security Groups and Tenants in one Export file (security.xml). Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| Security Group Mappings | -c securitymappings | Incremental or Replaces all |
No dependencies. Exports Security Group Mappings in one Export file (securitymappings.xml). Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| Status | -c status | Replaces all |
No dependencies. Import requires one Export file (status.xml). Note The imported status applies to all Node Groups in the database. |
| Traps | -c trap | Incremental or Replaces all |
Import requires four Export files: (1) author.xml, (2) incident.xml, (3) nodegroup.xml, and (4) trap.xml Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| -c trap -a <authorUniqueKey> | Incremental (subset) |
Import requires one Export file (trap.xml). The required Author and Node Group information is embedded in the Export file. |
|
|
User Accounts User Account Mappings User Groups NNMi Roles
|
-c account | Incremental or Replaces all |
Exports User Accounts, NNMi Roles, User Groups, and User Account Mappings. This command gathers data from multiple Configuration workspace views. Import requires one Export file (account.xml). The data from all the Configuration workspace views is embedded in the Export file. Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |
| User Interface | -c ui | Incremental or Replaces all |
No dependencies. Import requires one Export file (ui.xml). Note You must use the nnmconfigimport.ovpl command with the -sync option to replace all configuration content for the specified workspace on the second server. Otherwise the import is Incremental. |