Feature Support, Configuration Notes And Restrictions - Alcatel-Lucent 7210 SAS M Service Manual

Thus, the device processes packets received with 2 or more tags using the MPLS SDP or a dot1q
SAP while classifying on the QinQ SAP ingress using 2 tags.

Feature Support, Configuration notes and Restrictions

A new svc-sap-type value "qinq-inner-tag-preserve" is available for configuring the service. This
must be used when creating a new Epipe service if this functionality is desired (For example:
epipe 10 svc-sap-type qinq-inner-tag-preserve create).
•
•
•
•
7210 SAS M Services Guide
This service is available only in network mode.
Epipe service created with the parameter svc-sap-type set to qinq-inner-tag-preserve will
allow for only one QinQ SAP and only one SDP of vc-type 'vc-vlan'. The system will not
allow the user to use any other SAP in this new service, that is, NULL SAP, Q1. * SAP,
0.* SAP, etc, are not allowed for configuration in this service. The SDP cannot be of vc-
type 'vc-ether'.
User can configure vlan-vc-tag value for the SDP and the dot1q SAP VLAN tag value to
match the VLAN ID value of the inner tag specified in the Q1.Q2 SAP configured in the
service (example: if the SAP is 1/1/10:Q1.Q2, then vlan-vc-tag must be set to Q2 and the
dot1q SAP VLAN value must be Q2). If any other value, other than QinQ SAP's inner tag
is configured for vlan-vc-tag or dot1q SAP VLAN value, then it will be errored out by the
software. If vlan-vc-tag value is not configured, it defaults to use the inner VLAN tag
value. It is highly recommended that the customer configure the vlan-vc-tag value to
match the VLAN ID value of the inner tag configured for the QinQ SAP, to avoid
misconfiguration.
Existing QoS and ACL functionality for the Epipe service entities will continue to be
available, with the following exceptions:
→ If the packet is received with more than 2 tags, then IP match-criteria cannot be used
with SAP ingress QoS classification and ACLs (both Ingress and Egress ACLs).
→ If the packet is received with more than 2 tags, then Ethertype value in the mac-
criteria cannot be used with SAP ingress QoS classification and ACLs (both Ingress
and Egress ACLs).
→ Dot1p bits from the outermost tag (i.e. Q1 VLAN tag, if the SAP is 1/1/10:Q1.Q2)
will be used for SAP ingress classification. Dot1p bits of the outermost tag will be
marked on egress, if marking is enabled on the egress port. The Dot1p bit value of the
vc-vlan-tag is not used to mark the Dot1p bits of the outermost VLAN tag, when the
packets is exiting the QinQ SAP.
Virtual Leased Line Services
Page 139