Sap Configuration Notes When Operating The 7210-M In Access-Uplink Mode Only; Table 4: Sap And Service Combinations For 7210 Sas M In Access-Uplink Mode - Alcatel-Lucent 7210 SAS M Service Manual

Hide thumbs Also See for 7210 SAS M:
Table of Contents

Advertisement

SAP configuration notes when operating the 7210-M in Access-
Uplink mode only
When provisioned in access-uplink mode, the following SAP configuration guidelines are
applicable.
The
Table 4

Table 4: SAP and Service Combinations for 7210 SAS M in access-uplink mode

svc-sap-type
null-star
dot1q-preserve
any
Dot1q SAP
7210 SAS M Services Guide
provides details of SAP and service combinations allowed in access-uplink mode
Null SAP,dot1q Default 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)
dot1q SAP Null SAP, dot1q SAP,
dot1q explicit null SAP, Q1.Q2
SAP, Q.* SAP, 0.* SAP
(dot1q VLAN tag not stripped on
ingress), Q1.* SAP
'svc-sap-type' parameter value determines the type of SAPs that are allowed to be
provisioned in a service.
A physical port can have only one SAP to be part of one service. Multiple SAPS can be
defined over a physical port but each of these SAPs should belong to a different service.
In the case of a service's 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 access port is not stripped, when svc-sap-type is set to dot1q-preserve.
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 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
Access SAPs
Services
Access Uplink SAPs
Q.* SAP, Default QinQ
SAP (*.* SAP)
Q1.Q2 SAP (Q2 tag
VLAN ID must match the
dot1q SAP
VLAN ID)
Q1.Q2 SAP, Q.* SAP, 0.*
SAP
Q1.* SAP
Page 39

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents