26.1.2 Migrating in phases

For some organizations, their system might function better if phased migration is used rather than building an entirely new system. For such organizations, it will be necessary to completely replicate the existing NNM system to a new NNMi system, thus replacing the old system. Although many migration methods are available, we recommend the following phases:

• 26.2 Phase 1: Migrating the SNMP information

  Configure NNMi using the SNMP information of the environment currently being used.

• 26.3 Phase 2: Migrating discovery

  Configure NNMi to discover objects in a manner similar to the way discovery worked under NNM (automatically).

• 26.4 Phase 3: Migrating status monitoring

  Configure a state polling interval and protocol most appropriate to the environment being used.

• 26.5 Phase 4: Migrating event configuration and event reduction

  Configure NNMi to display event severity, category, and messages and to run automatic actions as NNM was configured to. You might also need to configure deduplication, rate counting, and pairwise cancellation.

• Phase 5: Migrating graphical visualization

  Migrate the hierarchical structures of the NNM location map, Internet submap, and segment submap as NNMi node group configurations. For details about the migration method, see the Release Notes.

Table 26‒1: Migration range provides an overview of the simplest method and the most detailed and thorough method with respect to the migration range.

• With the simplest method, you import the information unique to your NNM environment and use the NNMi default values for other configurations, which have been improved from NNM.

• With the most detailed and thorough method, carefully check the NNM configurations and replicate them to NNMi.

The remainder of this chapter explains one by one the processes of migrating an NNM configuration to NNMi. The following headings, such as Collect from NNM and Replicate to NNMi, indicate where in the migration process that portion of the procedure is applied.

• Collect from NNM indicates a task that is performed at the NNM management station.

• Replicate to NNMi indicates a task that is performed at the NNMi management station.

• NNMi enhancement indicates an additional task that is performed at the NNMi management station. You can make enhancements at any time, either during or after migration.

At some points, multiple methods are provided, depending on the degree of task difficulty.

Table 26‒1: Migration range

Phase	Simplest method	Most detailed and thorough method
SNMP information	Export all community strings currently being used. Import these community strings into NNMi. NNMi determines the node each community string matches.	Export all community strings currently being used. Correct the exported data file and import it into NNMi as the community strings of specific nodes.
Discovery	Export a list of all discovered nodes. Modify the data file and import into NNMi the file content as seeds without any automatic discovery rule.	Identify the methods (seeds, load hosts, filters, and other tools) NNM and netmon used to discover nodes. Use the seeds and the auto-discovery tool to replicate these methods on NNMi as closely as possible.
Status monitoring	The NNMi default values are improved to suit most user requirements. Because there is no need to significantly change these default values, begin operation using the improved default values.	For each group of nodes, carefully examine which polling interval and polling policy are being used by NNM and netmon. Create NNMi node groups and interface groups so as to replicate the polling interval and polling policy.
Event configuration and event reduction	Start with the NNMi default configuration. Add custom trap definitions for managed devices. If necessary, add automatic processing.	For each type of trap and event, examine what NNM customization was performed. On the NNMi system, customize the matching traps and event types.

To Page Top