Skip Headers
Oracle® Communications Network Intelligence Concepts
Release 7.2.2

E17891-03
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

10 Managing Network Migrations

This chapter describes how Oracle Communications Network Intelligence carries out network migrations.

About Network Migration

Network Intelligence uses migration planning to generate network requirements changes to your network. For example, if you plan to upgrade bandwidth capacity, you can assess the impact such an upgrade has on the trails in the network.

You create a migration plan using multiple network elements of the same type, such as trails, and with entities of different types (for example, site and equipment). It can also be used to find the migration impact based on supported network elements:

  • Card

  • Trail

  • Customer

  • Equipment

  • Route

  • Service

  • Shelf

  • Site

  • Topology

You can create migration demands based on changes to the following network attributes:

  • Customer

  • Service

  • Capacity

  • Quantity

  • Start site

  • End site

  • Start node

  • End node

Network Intelligence provides a wizard to guide you through the process of creating a migration plan. Each step helps you to refine the information used to generate the plan.

If you use Migration Manager to search for circuits, the search returns direct children of the circuit, if the selected circuit is a protecting circuit, and children of the protected circuit.

Creating a Migration Plan

To create a migration plan:

  1. Select Tools, then Migration Manager.

  2. Enter a date on which the migration takes place, and give the plan a name.

  3. Select the type of the entities that you want to migrate.

    Selecting the entity type enables you to perform a search on network elements of this type in Network Intelligence.

  4. Refine the search by using case sensitivity, or by utilizing the searchable site, or custom fields.

  5. Verify the entities to be migrated.

    You can include other entities, or remove entities from the table.

    Each entity is processed in turn to find both terminating and transiting trails relating to each migration entity. It can take some time to complete.

  6. Inspect the list of services, customers, and trails that are affected by the entities to be migrated.

    The Services tab groups the trails referenced by the service. Selecting a service selects all of the trails that reference the service.

    The Customers tab groups the trails by customer. Selecting a customer selects all of the trails belonging to that customer.

    The Trails tab presents the full list of the trails for selection.

    You can migrate all trails or migrate a specific customer, or a particular service by selecting the required entity.

    You can include other entities, or remove entities from the table.

    Note:

    Selecting a row under either the Services tab or the Customers tab automatically selects the trails related to those services or customers in the Trails tab.
  7. Generate the migration rules for the new service demand.

    Create a migration rule by entering the current attributes, and the planned attributes. For example, to migrate a capacity, enter the capacity you want to migrate, and the capacity you want to migrate to.

    Tip:

    When migrating from a site or equipment, set migration rules for both the start and end site, or equipment, because the traffic may be ingress or egress at that site or equipment.
  8. Verify the service demands.

    Service demands are used by Forecast Manager to find rerouting path solutions for the migration traffic. To know, for example, only the customers and circuits affected by the migration, the service demands may not be of interest. Service demands do not include links.

    The suggested path solutions exclude the entity being migrated (for example, if you migrate a site, the service demands listed in the Plan view display that site as an excluded site).

    To verify that an entity has been excluded after a migration plan has been completed for that entity, right-click a service demand, and select View Selected Service Demand Policy. In the Consolidated Rules Overview section, the selected site is listed as an excluded site.

    If the service demands are incorrect, revert to the previous step to change the migration input.

  9. Click Next to generate reports on:

    • Affected services

    • Affected customers

    • Affected trails

    • Trail decommissioning

    • Equipment hardware migration

    All reports are selected by default.

  10. Save, and display, the migration plan.

    If you chose to display the migration plan, it is opened in a tab with the name of the plan. Use the Plan, Impact, Migration, and Planned Entities views to display the migration requirements.

    See the Network Intelligence Help for instructions about creating migration plans, or carrying out tasks such as:

    • Viewing plans

    • Sharing plans

    • Editing the name of a plan

    • Deleting plans

About Migrating Cards

The requirements for migrating a significant number of cards using Migration Manager are significant, and must be taken into account before attempting any such migration.

For example, attempting to migrate all of the cards in a network may take some time, and the performance and memory requirements may also be significant. As a result, Migration Manager is not generally suitable for migrating all the cards in the network at once.

Typically, card migration on this scale should be carried out on a site-by-site basis, using several migration plans.