To move a VLL service

Purpose

Perform this procedure to move a VLL service from one NE to another NE. The VLL service site and all of the children objects, including SAPs, SDP bindings, MEPs on the SAPs and related CFM tests, are moved to the destination site. MEPs and associated CFM tests are included in VLL move operations for L2 SAPs and SDP bindings (including return SDP bindings). Return SDP bindings (from remote site to the source site) for SDP bindings from the source site to a remote site are moved. Ingress and egress, scheduler, policer, accounting, and IP/MAC filters (ACLs) policies are moved and distributed to the destination NE.

If there are SAPs on different ports within a VLL, you must move the service port by port. When the service does not already exist on the destination NE—that is, before an move operation—the service site and children objects are moved to the destination NE. Only SAPs on the specified port are moved to the destination site. After an initial move, moving the remaining SAPs on other ports is a SAP move operation. See To copy or move L2 SAPs between ports .

Note: Consider the following site limitations when you move a service:

  • Moving services is only supported on 7750 SR, 7450 ESS, and 7950 XRS NEs.

  • The NE type and major software release of the source and destination NEs must be the same.

  • The chassis mode of the destination NE must be the same or higher than the chassis mode of the source NE.

  • The NFM-P copies the source site and children objects and creates them on the destination NE.

  • You cannot move sites that are used in a backbone configuration.

  • You cannot move sites created by a RADIUS script for dynamic service.

Consider the following SAP limitations when you move a service:

  • The source and destination ports must be compatible, for example, have the same encapsulation type, be HSMDA ports or not, or both be access or hybrid.

  • You cannot move SAPs that are configured on PW ports and Ethernet tunnel endpoints.

  • SAPs with connection profiles (ATM/VLAN) can be moved when there is at least one SAP configured on the source port with the encap value in the specified range on the source service site.

  • If the source site only contains SAPs with connection profiles, the site will not be moved.

  • If the source site contains SAPs associated with connection profiles on the specified port, and SAPs on a different port, or SAPs on the specified source port but with encap values out of the range, the site will not be moved.

  • The ranges specified in the connection profiles (ATM/VLAN) on source SAPs must not overlap with SAPs on the destination port or fall in a range where a SAP on the destination port may exist.

    The Encap value ranges specified in the move procedure do not apply to connection profiles.

  • If there is a Ethernet Ring Path Endpoint associated with the source SAP, the association is not be copied to destination SAP.

Take into account the following service tunnel considerations when you move a service:

  • If the spoke SDP bindings on the source NE use an SR-ISIS or SR-OSPF service tunnel, the NFM-P looks for a matching tunnel on the destination NE. If no matching tunnel exist, then the NFM-P creates one.

  • If the spoke SDP bindings on the source NE use an MPLS-TP service tunnel, the copy/move operation is allowed, but an MPLS-TP service tunnel must exist on the destination NE.

  • You cannot move SDP bindings that use L2TPv3 service tunnels.

  • You cannot move spoke SDP bindings if they are not manually created.

Steps
 
1 

Choose Tools→Copy/Move→Service from the NFM-P main menu. The Service Copy/Move form opens.

2 

Set the Action Type parameter to Move.

3 

Set the Service Type parameter to a VLL service or VPLS+VLL.

Note: Only VPLS is supported for the action type Copy.

4 

In the Source panel, choose the NE from which you want to move the service.

5 

In the Source Port panel, choose the source port from which you want to move the service.

6 

Configure required parameters in the Source panel.

7 

In the Destination panel, choose the NE to which you want to move the service.

8 

In the Destination Port panel, choose the port to which you want to move the service.

9 

Configure the required parameters in the Execution Details panel.

The NFM-P creates SAPs on the destination port with the same encapsulation values as the source SAP if you set the Outer Encap Value Offset and Inner Encap Value Offset parameters to 0. Otherwise, the NFM-P creates SAPs on the destination port encapsulation values equal to the source encapsulation value plus the Outer Encap Value Offset or Inner Encap Value Offset parameter.

10 

Click Result Export Path and specify the file name and location in which to save a text file that contains the results of service move operation.

11 

Click Execute.

12 

Click on the Results tab to view the results of the copy or move action.

End of steps

Note:

If the new site is created successfully with all children copied from the source site, the source site is deleted.

A service move searches for all of the SAPs with specified service type on the source NE, within the encapsulation value range that you specified in Step 6 on the specified port. The NFM-P creates the associated service sites on the destination NE with the corresponding SAPs on the destination port, including all children objects, such as SDP bindings, that existed on the source site.

The source site is not deleted if the new site is created successfully with only some of the SAPs from source site, for instance, there are SAPs remaining on the source site on different ports or with outer or inner encapsulation values out of the specified range. The SAPs that are within the specified encapsulation range that you specified in Step 6 will be deleted from the source port after the move, along with all corresponding SDP bindings.

If the corresponding service site exists on the destination NE, only the SAPs within the specified encapsulation range are copied/moved to the destination site. All other children objects, such as SDP bindings, under the source site are not copied or moved to the destination site. In this case, the source site will be deleted along with all other children objects when the last SAP is moved.

If a SAP exists on the destination site with same encapsulation values as the source SAP (the source SAP encapsulation values plus the Outer Encap Value Offset or Inner Encap Value Offset parameters that you specified in Step 9 ), the move action fails.

If there is a failure when moving a site or any of the child objects, the move action for this site fails and nothing from this site is moved to the destination NE.

If there are multiple service sites being copied or moved along with the SAPs as specified by source port and encapsulation range, the copy or move action continues to the next site if there is an individual failure.

The NFM-P reports that the copy or move action is finished when the NFM-P database transaction has completed; deployment operations on the node may continue after the database transaction is complete.