When provisioned in access-uplink mode, the following SAP configuration guidelines are applicable.
The following table describes SAP and service combinations allowed in access-uplink mode.
svc-sap-type |
Access SAPs |
Access uplink SAPs |
|---|---|---|
|
Null SAP, dot1q default SAP, default QinQ SAP (*.* SAP) |
Q.* SAP, default QinQ SAP (*.* SAP) |
|
Dot1q SAP (dot1q VLAN tag is not stripped on ingress), Q1.Q2 SAP (Q2 tag VLAN ID must match the dot1q SAP VLAN ID) |
Q1.Q2 SAP (Q2 tag VLAN ID must match the dot1q SAP VLAN ID) |
|
Null SAP, dot1q SAP, dot1q explicit null SAP, Q1.Q2 SAP, Q.* SAP, 0.* SAP |
Q1.Q2 SAP, Q.* SAP, 0.* SAP |
|
Dot1q SAP (dot1q VLAN tag not stripped on ingress), Q1.* SAP |
Q1.* SAP |
The following guidelines apply to SAPs:
The svc-sap-type parameter value determines the type of SAPs that are allowed to be provisioned in a service.
A physical port can only have one SAP to be part of one service. Multiple SAPS can be defined over a physical port but each of these SAPs must belong to a different service.
If a service sap-type is specified as dot1q-preserve, all the SAPs configured in the service must have the same VLAN ID. The outermost VLAN tag of the packets received on the access port is not stripped, when svc-sap-type is set to dot1q-preserve.
A dot1q default SAP cannot be configured when svc-sap-type is set to any.
When svc-sap-type is set to any for a null SAP, the system processes and forwards only packets with no VLAN tag (that is, untagged). All other packets with one or more VLAN tags (even those with priority tag only) are not processed and are dropped. Users can use the service with svc-sap-type set to null-star, to process and forward packets with one or more tags (including priority tag) on a null SAP.
An ingress QoS policy and accounting policy is assigned per access-uplink port and cannot be assigned per access-uplink SAP.
The default QinQ SAP processes only tagged packets received on a QinQ port. All tagged packets that do not match the specific SAP tags configured on the same port are processed by this SAP. The default QinQ SAP cannot process un-tagged packets, even if 0.* SAP is not configured for use on that port.
The default QinQ SAP is available for use with 0.* SAPs configured on the same port or in the same service. It is available for use with another default QinQ SAP configured in the same service (on a different port). In a VPLS service, the default QinQ SAP is available for use with any other SAP type configured in a service configured with svc-sap-type parameter set to null-star.
SAPs using connection-profile (to specify dot1q VLAN ranges or individual VLAN IDs) can be configured in a service only when svc-sap-type is set to dot1q-range.
When a service is configured to use svc-sap-type dot1q-range, the outermost V-LAN tag of the packets is not stripped when the packet is received on access port ingress. See Epipe services for more information about the processing behavior for this type of service.