What data is migrated

Edit online

Network Manager migrates most files, and highlights files that you must migrate manually.

Files that have been changed can be classified in the following two ways.

Configuration changes

Standard settings for processes, discovery and monitoring configuration, and topology views can be migrated by following the directions in this document. The person who performs the migration must be the administrator or have a similar level of understanding of Network Manager. Configuration files are fully or partially migrated by the migration process. Any files that must be migrated manually are highlighted.

Customization changes

Network Manager can be extensively customized to add new capability or integrate with your existing environment. The following are some examples of configuration changes:

  • Additional device support
  • Additional data from devices and customer proprietary data sources for visualization and monitoring
  • Modified logic for building connections within and between network devices, and collections for grouping devices
  • Building sets of network views using the dynamic template API
  • Event enrichment via the Event Gateway and nco_p_ncpmonitor probe rules file
  • Right-click topology map tools using Webtools and other technologies
  • Extending the Service Affecting Events system for other collections
  • Integrations with other products, including LDAP and TADDM

All customization changes require some level of knowledge of the product data flow and APIs, plus programming skills. These same skills are required to successfully migrate the same customizations. You must also take account of any new logic changes that might require changes to the existing custom code.

Customization changes are not migrated automatically. The upgrade process highlights files that have changed and must be migrated manually.

Types of data that are not migrated

The following kinds of data can not be migrated:

  • NCIM cache files are not migrated between different versions of Network Manager. NCIM cache files are copied from one installation to another only if you copy an existing V4.2 installation to another V4.2 installation.
  • Discovery cache files
  • Network topology is not migrated. You must run a new discovery on the target installation.

Types of data that are migrated

The following kinds of data are migrated.

  • Configuration files.
  • Network views.
  • Discovery configuration data.
  • Multiple domains. Your domains are automatically recreated, and the network views and monitoring policies are imported.
  • Passwords and SNMP community names. This data is unencrypted, imported, and re-encrypted automatically.
  • Poll policies and poll definitions.
  • MIBs. The SNMP MIBs have been moved from the GUI server to the core components server in Network Manager 4.2.
  • New or customized discovery collectors