To copy or move L2 SAPs between ports

Before you begin

Note: If the source SAP has an MEP configured, and a CFM test is running on the service that has the new MEP, the test must be stopped and executed again to make the new MEP active.

Before you perform a SAP move operation, archive all existing test results associated with the source SAP MEP.

You can also use the NFM-P clipboard to copy or move SAPs. See Chapter 1, NFM-P GUI for information about using the NFM-P clipboard.

Steps
 

For the source NE, disable automatic configuration backup if it is enabled in the backup policy assigned to the NE. Configure the Auto Backup Scheme parameter appropriately. See To configure a backup policy for configuration information.


CAUTION 

CAUTION

Service Disruption

An unsuccessful SAP copy or move may result in the deletion of one or more source SAPs from the source NE. The backed-up configuration file is required to restore the configuration on the source NE if a SAP copy or move operation fails.

On the source NE, use a CLI to back up the device configuration to a file. Ensure that you use a unique name for the backup file to ensure that it is not accidentally overwritten. Enter the following at the CLI prompt:

admin save file_name

where file_name is a name that differs from the existing configuration file names on the NE and identifies this as the configuration in effect before the copy or move operation

See the appropriate device documentation for more information about saving the device configuration to a file.


For the destination NE, disable automatic configuration backup if it is enabled in the backup policy assigned to the NE. Configure the Auto Backup Scheme parameter appropriately. See To configure a backup policy for configuration information.


On the destination NE, use a CLI to back up the device configuration to a file. Ensure that you use a unique name for the backup file to ensure that it is not accidentally overwritten. Enter the following at the CLI prompt:

admin save file_name

where file_name is a name that differs from the existing configuration file names on the NE and identifies this as the configuration in effect before the copy or move operation

See the appropriate device documentation for more information about saving the device configuration to a file.


CAUTION 

CAUTION

Service Disruption

Nokia strongly recommends that you monitor the NE deployments and the alarm window during a SAP copy or move operation to ensure that faults that may arise during the operation are immediately detected.

The Incomplete Deployments tab of the Deployment form notifies the NFM-P operator of configuration changes that are not successfully deployed to the NE, and the NFM-P alarm window alerts the operator to object failures on the NE that are related to the copy or move operation.

Open the Deployment form to monitor deployments as they occur during the SAP copy or move operation. Choose Administration→NE Maintenance→Deployment from the NFM-P main menu. The Incomplete Deployments tab is displayed.


Choose Tools→Copy/Move→SAP. The SAP Copy/Move form opens.


Arrange the forms on the GUI so that the SAP Copy/Move form, the Deployment form, and the alarm window are all shown.


On the SAP Copy/Move form, click on the Result tab and then click Result Export Path. The Result Export Path form opens.


Specify the file name and location in which to save a text file that contains the results of the SAP copy or move operation.


10 

Click Set. The Result Export Path form closes.


11 

On the SAP Copy/Move form, click on the General tab.


12 

Configure the Current Mode parameter as L2 Access Interface.


13 

Configure the Service Type parameter.


14 

Select a source node and a source port in the Source panel.


15 

Configure the Outer Encap Value Start and Outer Encap Value End parameters, and the Inner Encap Value Start and Inner Encap Value End parameters, if applicable.


16 

Select a destination node and a destination port in the Destination panel.


17 

Configure the required parameters in the Execution Details panel.


18 

Click Execute to begin the copy or move operation. The Execution Result panel displays the execution state of the copy or move operation and the number of successful and failed operations based on the input criteria.

Note: When you copy or move a SAP on an L2 interface and there is a non-zero value assigned to the PIM Snooping parameter Maximum Number of Groups, the value is not copied or moved to the new location. You must manually configure the Maximum Number of Groups parameter in the new location.

The Succeeded state only specifies that the SAP copy or move operation is successfully committed to the database. After the SAP copy or move operation is executed, you must monitor the Deployment form for any deployment errors.


19 

Monitor the Deployments form and the alarm window for any deployment failures and faults related to the SAP copy or move operation. Click Refresh on the Deployments form to update the list, if required.


20 

Click on the Result tab to view a list of the successful and failed operations as identified by the NFM-P.

You can double click the result to open it in a new window and view the details.


21 

Click Refresh Result to view the most recent results.


22 

To view the information for an individual SAP copy or move operation, move the mouse pointer over the Message field of the operation.


23 

If a copy or move operation fails, you can restore the previous source NE configuration using the backup configuration file created in Step 2 .

  1. Open a CLI on the source NE.

  2. Enter the following at the command prompt to load the saved configuration file:

    exec file_name ↵

    where file_name is the name of the configuration file that was specified in Step 2

    The SAPs that were deleted during the unsuccessful copy or move operation are restored on the NE.

  3. Enter the following at the command prompt to save the NE configuration:

    admin save ↵


24 

If a copy or move operation partially fails, you can restore the previous destination NE configuration using one of the following methods.

Note: If the copy or move operation fails completely, there is no need to restore the previous configuration because no SAPs are created on the destination NE.

  1. Restore the backed-up configuration file.

    1. Open a CLI on the destination NE.

    2. Enter the following at the command prompt to load the saved configuration file:

      exec file_name ↵

      where file_name is the name of the configuration file specified in Step 4

      The previous configuration is restored on the NE.

    3. Enter the following at the command prompt to save the NE configuration:

      admin save ↵

  2. Manually delete the SAPs that the copy or move operation created on the destination NE.


25 

Restore the previous automatic configuration backup setting in the backup policy of the source NE by configuring the Auto Backup Scheme parameter appropriately. See To configure a backup policy for configuration information.


26 

Restore the previous automatic configuration backup setting in the backup policy of the destination NE by configuring the Auto Backup Scheme parameter appropriately. See To configure a backup policy for configuration information.


27 

Close the form.

End of steps