Overview

NFM-P Card Migration Event Manager

You can use an NFM-P GUI utility called the Card Migration Event Manager to facilitate the transition to an IOM 3 on one or more 7450 ESS or 7750 SR NEs. The Card Migration Event Manager transfers the existing IOM and MDA configurations to new modules with minimal service interruption.

The NFM-P Card Migration Event Manager can do the following:

• Upgrade from an IOM 1 or IOM 2 to an IOM3 while retaining the same MDAs.

• Upgrade from one MDA type to a newer MDA type that has compatible features.

• Upgrade an IOM and the associated MDAs in one operation.

You can perform an immediate migration, or preconfigure one or more migration events for later execution. A migration event can include an NE reboot to put the new hardware configuration into effect immediately after the migration. You can upgrade multiple IOMs and MDAs in one operation to limit the number of required NE reboots to one.

During a migration event, the NFM-P identifies the configured objects that are bound to the IOM or MDA, deletes the objects, and then creates the objects on the new IOM or MDA. The old and new configurations are saved in the NFM-P database until the migration completes successfully. The NFM-P preserves the statistics data and alarm information that is associated with each object.

Restrictions

The following restrictions apply to NFM-P card migration event management:

• General

  • Only the NFM-P admin user, or a user with an assigned administrator scope of command role, can create, modify, or execute a migration event.

  • The migration functions are not available to NFM-P OSS clients.

  • You may need to re-enable SNMP on an NE after the NE reboots following a migration event.

  • The description of a SAP associated with the card cannot contain a numerical value.

• IOM-specific

  • An IOM downgrade, for example, a migration from an IOM 3 to an IOM 2, is not supported.

• MDA-specific:

  • You cannot migrate an empty MDA slot to an MDA.

  • MDA migration is limited to MDAs of the same physical transmission type; for example, migration from a SONET MDA to an Ethernet MDA is not supported.

  • You cannot upgrade an MDA that is integrated with an IOM, for example, an IMM.

  • For MDAs, you can migrate only to an MDA of similar capacity that has the same or a greater number of ports.

The NFM-P raises an alarm during a migration event if a target NE is unreachable. After a migration event, the NFM-P raises an alarm to indicate migration success or failure.

Table 18-1: Supported MDA migration types

Current MDA	MDAs supported by migration
10 x 1-Gig Ethernet SFP	10 x 1Gig Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
5 x 1-Gig Ethernet SFP	10 x 1Gig Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
1 x 10-Gig Ethernet	4 x 10Gig Extended Performance XFP 2 x 10Gig Extended Performance XFP 1 x 10Gig Extended Performance SFP
20 x 100 Ethernet Fx	20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
20 x 10/100/1000 Ethernet Tx	20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
2 x 10-Gig Ethernet XFP	2 x 10Gig Extended Performance XFP 4 x 10Gig Extended Performance XFP
20 x 10/100/1000 Ethernet SFP	20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
1 x 10-gig Ethernet XFP	4 x 10GigExtended Performance XFP 2 x 10Gig Extended Performance XFP 1 x 10Gig Extended Performance XFP
5 x 10/100/1000	10 x 1Gig Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
10 x 10/100/1000 Ethernet SFP	10 x 1Gig Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance SFP 20 x 10/100/1000 Ethernet Extended Performance TX
60 x 10/100 Ethernet	48 x 10/100/1000 Ethernet Extended Performance TX