Each subscriber service type is configured with at least one SAP. A SAP identifies the customer interface point for a service on a 7210 SAS router (Figure: Multiple SAPs for 7210 SAS configured with MPLS uplinks). The SAP configuration requires that slot, MDA, and port information be specified. The slot, MDA, and port parameters must be configured before provisioning a service (refer to the Cards, MDAs, and Ports sections of the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Interface Configuration Guide).
A SAP is a local entity to the router and is uniquely identified by:
physical Ethernet port
encapsulation type
encapsulation identifier (ID)
Depending on the encapsulation, a physical port can have more than one SAP associated with it. SAPs can only be created on ports designated as ‟access” in the physical port configuration.
The preceding figure shows SAPs used for customer service delivery, with SDP used for service transport on 7210 SAS devices that support MPLS uplinks.
SAPs can be created on ports designated as core facing ‟access uplink” ports when using QinQ uplinks. Access-uplink ports have a different set of features enabled in software.
The following figure shows SAPs used for customer service delivery with access-uplink SAPs (also known as QinQ SAPs) used for service transport on 7210 SAS devices when using Layer 2 uplinks.
