An 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 needed (for example, epipe 10 svc-sap-type qinq-inner-tag-preserve create):
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 vlan. The system will not allow the use of any other SAP in this new service; that is, null SAP, Q1. * SAP, 0.* SAP, and so on, are not allowed for configuration in this service. The SDP cannot be of vc-type ether.
The user can configure the vlan-vc tag value for the SDP, the dot1q SAP VLAN tag value, and the inner tag VLAN value of a QinQ SAP to match the VLAN ID value of the inner tag specified in the Q1.Q2 SAP configured in the service. For example, if the SAP is 1/1/10:Q1.Q2, the vlan-vc tag must be set to Q2, the dot1q SAP VLAN value must be Q2, and the inner tag of another QinQ SAP must be set to Q2.
If any other value, other than the QinQ SAP inner tag is configured for the vlan-vc tag or dot1q SAP VLAN value, or for the inner tag of the QinQ SAP, it will be errored out by the software. If the 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 are available, with the following exceptions:
If the packet is received with more than two tags, 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 two tags, the 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 (that is, 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.
OAM tools
MPLS OAM tools such as vccv-ping, vccv-trace, and so on, are supported for the SDPs.
Accounting and Statistics for the service entities (for example, SAP and SDP) will be available as before.
CFM/Y.1731 tools are supported. Up and Down MEP is supported on the SAPs and the SDPs configured in the Epipe service.
The following redundancy mechanisms available in Epipe service are supported when using MPLS SDP:
Epipe PW redundancy
MC-LAG based protection for access SAPs using the service type (along with using PW redundancy)