Skip Headers
Oracle® Communications Network Intelligence User's Guide
Release 7.2.2

E36059-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

16 Migrating Network Entities

This section describes the Migration Manager in Oracle Communications Network Intelligence. The Migration Manager is used to create a migration plan to generate network requirements changes to your network.

Creating a Migration Plan

To create a migration plan:

  1. Perform one of the following to display the Migration Manager wizard:

    • Select Tools - Migration Manager from the main menu on the Network Intelligence GUI.

    • Click the Migration Manager icon under the main menu on the Network Intelligence GUI:

      Migration Manager icon
  2. Enter a date on which the migration takes place in the Migration Project Date field. The date must be in the future.

    Enter a name for the migration in the Migration Project Name field. The name must be unique within Network Intelligence.

    Click Next to display the Select Network Entities window.

  3. Find the network entity type to migrate. Selecting this type enables you to perform a search on network entities of this type in Network Intelligence.

    From the Entity Type list, select the required network entity type:

    • Card

      Tip:

      See "Migrating Cards" for further information on card migration using Migration Manager.
    • Trail

    • Customer

    • Equipment

    • Route

    • Service

    • Shelf

    • Site

    • Topology.

    Click Search to display the (Entity Type) Search window; for example: Trail Search.

  4. Click the Search tab to display a list of identifiers to help you to find the entities for the migration.

    Select the Case Sensitive check box to enforce case sensitivity in the search fields.

    For example: in the Trail Search window, the following identifiers are provided:

    • Name: Enter the name of the trail.

    • Trail Group: Select from the list of supported trail groups.

    • Trail Definitions: Select from the list of supported trail definitions.

    • Service: Select from the list of supported services.

    • Capacity: Select from the list of supported capacities.

    • A Site: Enter the name of the A site, or click the ellipsis button to open a Site Search window to find the originating site.

    • Z Site: Enter the name of the Z site, or click the ellipsis button to open a Site Search window to find the terminating site.

    • A Equipment: Enter the name of the A equipment, or click the ellipsis button to open an Equipment Search window to find the originating equipment. The equipment values in the window are disabled by default until a site is selected.

    • Z Equipment: Enter the name of the Z equipment, or click the ellipsis button to open an Equipment Search window to find the terminating equipment. The equipment values in the window are disabled by default until a site is selected.

    • A Port: Enter the name of the A port.

    • Z Port: Enter the name of the Z port.

    • Customer: Select from the list of supported customers.

    • Protection: Select the protection status for the service demand: Protected, Protection, Unprotected.

    • Presentation: Select the presentation type for the service demand: CHS, CSH, ISH, ISI, or Normal.

    • Route: Select the name of the route.

    • SequenceNo: Select the sequence number of the trail.

    • Supplier: Select from the list of supported suppliers; for example: Alcatel, Ericsson.

    • Media Type: Select from the list of supported media types; for example: Coax, Dark Fibre, Fibre.

    • Status: Select from the list of statuses; for example: Ceased, Faulty, Free, In Service, ONI Planned (where ONI signifies Oracle Network Intelligence).

    • Routed Status: Select from the list of routed statuses; for example: Routed, Partially Routed, Unrouted.

    • Direction: Select from the list of directions; for example: BothWays, Incoming, Outgoing.

    • InService Date: Use the calendar window to select the date on which the selected trail came into service.

    • OutService Date: Use the calendar window to select the date on which the selected trail is due to be exhausted.

    To further refine the trail search, use the Searchable Site Fields, or the Custom Fields.

    Click Search to return the required entities, or click Reset to clear all the search fields.

    Tip:

    Leaving all search fields blank returns all network entities of that particular type.
  5. Verify the entities to be migrated, and click Next.

    Migration Manager processes each selected entity in turn to find both terminating and transiting trails relating to each migration object. It can take some time to complete.

    To change the list, click Previous.

    To remove entities from the table, right-click the selection and select Remove Selections.

  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.

    Note:

    The Next button is disabled until at least one trail has been selected for migration.

    To migrate all trails, select the Select All check box and click Next.

    To migrate a specific customer, or a particular service, click the Services tab, or the Customers tab, and select the required entity.

    To change this selection, click Previous.

    To remove entities from the table, right-click the selection and select Remove Selections.

    Note:

    Selecting a row under either the Services or 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 by clicking Add.

    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. You can select from the following network attributes:

    • Customer

    • Service

    • Capacity

    • Quantity. The Quantity values in the window are disabled by default until a capacity is selected.

    • Start site (A Site)

    • End site (Z Site)

    • Start node (A Node). The node values in the window are disabled by default until a site is selected.

    • End node (Z Node). The node values in the window are disabled by default until a site is selected.

      When you specify a new value, it is applied to all service demands that currently have that value. For example, if you change capacity from VC-12 to VC-4, all service demands that use VC-12 are changed to VC-4.

      Note:

      The From and To values must not be the same.

    Click Create to generate the new rule, or click Close to exit the window without committing the new rule.

    Click Add to create further migration rules, or click Remove to delete the selected rule.

    Tip:

    When migrating from a site or node, you should set migration rules for both the start and end site, or node, because in some cases the traffic may be ingress or egress at that site or node.

    Click Next to display the service demands that are used for the new trail routing plan.

  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, RemoteOffice, the service demands listed in the Plan view display RemoteOffice 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, RemoteOffice is listed as an excluded site.

    If the service demands are incorrect, click Previous 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.

    Click Next to save, and display, the migration plan.

  10. Select one of the following:

    • Save and Display Plan

    • Save and Close Plan

    Click Finish to complete the migration.

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

Viewing Migration Plans

To view a migration plan:

  1. Click the Plans tab in the context tool bar to view all plans within Network Intelligence: forecast plans, migration plans, and outage plans.

  2. Expand the Migration folder to view the migration plans.

  3. Double-click the required plan to view it.

Making Changes to a Migration Plan

You can share plans, modify the name of a plan, or delete the plan from Network Intelligence.

Sharing the Plan

By sharing a plan, multiple Network Intelligence users can modify a plan. This feature might be useful where network planners are working on different elements of the same plan, or working at different locations.

To share a plan with other users of Network Intelligence:

  1. Open the plan as outlined in "Viewing Migration Plans".

  2. Click Edit to enable changes to the plan.

  3. In the Shared field, select Yes.

  4. Click Save.

    The plan is visible to other users, who can edit and re-commit the plan as required.

Changing the Name of the Plan

To modify the name of a plan:

  1. Open the plan as outlined in "Viewing Migration Plans".

  2. Click Edit, and change the name of the plan.

  3. Click Save.

Deleting the Plan

To delete a plan:

  1. Open the plan as outlined in "Viewing Migration Plans".

  2. Click Delete, and confirm the deletion.

    The plan is deleted from the list of plans.

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 in one go.

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