Copying and moving SAPs

Overview

You can copy and move SAPs between physical Ethernet ports, logical ports, or ports and LAGs.

You can also copy and move SAPs between endpoints configured with ATM encapsulation. For example, you can move a SAP on an IMA bundle to another bundle or to a TDM channel configured with ATM encapsulation. The function is typically used in redundancy scenarios, or to recover from a hardware failure.

Consider the following before you attempt to copy or move a SAP:

• Ports:

  • The source and destination ports can be on the same or on a different chassis. Inter-chassis copy or move is supported only when both NEs are of the same type, in the same chassis mode or from a lower chassis mode (source NE) to a higher chassis mode (destination NE), and at the same major software release.

  • The source and destination ports can be the same. This configuration allows you to change the encapsulation values for a group of SAPs on the same port using outer and inner encapsulation offset values. These values can be positive or negative, depending on whether the encapsulation values must increase or decrease.

  • The physical Ethernet ports can be of different types; for example, Fast Ethernet (10/100/1000 Base-T), Gigabit Ethernet (1000 Base-T), and 10 Gigabit Ethernet (10 GBase-T).

  • The source and destination ports must be configured as access ports.

  • The encapsulation type must be the same on the source and destination ports.

  • You cannot copy or move a SAP between an HSMDA port and a non-HSMDA port.

  • The copy and move operations fail if the encapsulation value for a SAP on the source port is used by a SAP on the destination port. You can modify the SAP encapsulation values used on the destination port, if required.

  • The selected L2 access interface SAPs on the source port can be moved only to another service, and not within the same service.

  • If a SAP on the source port belongs to a service not supported on the destination port, the SAP is not copied or moved.

  • The maximum number of SAPs varies for ports and MDAs. The SAP copy or move operation fails if the SAP capacity is exceeded for the destination port.

  • For L2 and L3 access interfaces, you can move all SAPs or a subset of the SAPs on a port. You can also copy all SAPs or a subset of the SAPs on a port for L2 access interfaces.

  • All SAPs associated with a specific port within a group interface contained in an L3 subscriber interface can be moved at the same time.

• LAGs:

  • LAG to SAP copy and move works on all services that support SAP to SAP copy and move. There are no restrictions.

  • LAG specific attributes such as lag-per-link-has are dropped during the copy or move.

  • The target can be a port or a LAG. The target LAG or port can be on the same or a different NE for L2 Services. For L3 Services the target must be the same NE.

  • Both the mode and the encap-type must match to be copied. The NFM-P only displays LAGs or ports that have matching mode and encap-type. You can copy from an Access LAG or port to a Hybrid LAG or port and vice versa.

  • Port speed is not checked. You must verify that the target of the copy or move has enough capacity.

• SAPs:

  • SAPs can be associated with either L2 access interfaces on services such as Apipes, Cpipes, Epipes, Hpipes, Fpipes, Ipipes, VPLS, and MVPLS, or L3 access interfaces or subscriber interfaces that are associated with services such as IES and VPRN.

  • L2 access interface SAPs can be copied or moved from one service to another service of the same service type. The source and target service must be on the same site, and the source and destination service site types must be the same, for example B-site, I-site.

  • MEPs are copied or moved with the L2 SAP copy/move operation only if the Follow Service Topology Changes parameter is not enabled on the global MEG service. If the Follow Service Topology Changes parameter is enabled, the MEPs are automatically created by the OAM framework when the new SAP is created. See To configure an Ethernet CFM MD policy and subordinate objects.

  • For an L2 SAP copy/move operation, only MEP CFM tests that are manually created are moved to the new SAP. MEP CFM tests created by Test Suite are not moved to the new SAP.

  • For a SAP copy, the MEP ID is auto-assigned. For a SAP move, the MEP ID is copied only if the Node Wide MEP ID is not set on the destination NE. Otherwise the MEP ID will be auto-assigned based on the configured MEP ID. See To configure an automatic MEP ID assignment on an NE.

  • Endpoints associated with the specified SAPs are copied during an L2 SAP copy/move operation, but other objects associated with the endpoints such as other SAPs or spokes are not copied/moved. If the destination already has an endpoint with the same name, the endpoint associated with the source SAP will not be copied/moved with the source SAP.

  • You cannot change SAP encapsulation from bridged to routed if ARP and DHCP options have been configured.

• SAP attributes:

  • VPLS and MVPLS dynamic FIB entries that are associated with copied or moved SAPs are discarded. Static FIB entries are transferred to the destination port after a successful SAP copy or move.

  • All SAP redundancy relationships at the source port, such as those provided by an MVPLS, are discarded during a copy or move operation.

  • All alarms, statistics, or OAM test results that are associated with a copied or moved SAP are discarded.

  • When a source SAP belongs to an SHG, the NFM-P attempts to preserve the SHG membership. The destination SHG must have the same name as the source SHG, and must have the same residential SHG status. If an SHG with the same name does not exist on the destination service site, the NFM-P creates it.

  • When a source SAP uses an aggregation scheduler, the scheduler is copied to the destination. The aggregation scheduler must be unique to the destination NE and must have the same scope, for example, MDA or port.

• MEPs

  • MEPs and associated CFM tests are included in SAP copy/move operations for L3 Access Interface and Subscriber Interface SAPs.

See To copy or move L2 SAPs between ports , To copy or move L2 access interface SAPs between services , To move L3 SAPs within or between ports or LAGs on the same NE , and To move L3 subscriber interface SAPs between ports on the same NE to move access interface SAPs between services or ports.