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):

• This service is available only in network mode.

• Epipe service created with the parameter svc-sap-type set to qinq-inner-tag-preserve allows for only one QinQ SAP and only one SDP of vc-type vc-vlan. The system does not allow the user to use 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 vc-ether.

• User can configure 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 (example: if the SAP is 1/1/10:Q1.Q2, then 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 QinQ SAP's inner tag is configured for vlan-vc-tag or dot1q SAP VLAN value, or for the inner tag of the QinQ SAP then it is 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 mis-configuration.

• Existing QoS and ACL functionality for the Epipe service entities continues 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 (that is, Q1 VLAN tag, if the SAP is 1/1/10:Q1.Q2) are used for SAP ingress classification. Dot1p bits of the outermost tag are marked on egress, if marking is enabled on the egress port. The Dot1p bit value of the vlan-vc-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 and VCCV trace are supported for the SDPs

  • Accounting and Statistics for the service entities (for example, SAP and SDP) are 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 new service type (along with use PW redundancy)

*A:7210SAS>config>service# info
----------------------------------------------
epipe 10 svc-sap-type qinq-inner-tag-preserve customer 1 create
       sap 1/1/3:10.45 create
    exit
    spoke-sdp 111:69 vc-type vlan create
         vlan-vc-tag 45
    exit
    no shutdown
----------------------------------------------

*A:7210>config>service# info
----------------------------------------------
epipe 10 svc-sap-type qinq-inner-tag-preserve customer 1 create
       sap 1/1/3:10.45 create
no shutdown
    exit
    sap 1/1/4:45 create
         no shutdown
    exit
    no shutdown
exit
----------------------------------------------

*A:7210>config>service# info
------------------------------------------------------------------------------------
epipe 10 svc-sap-type qinq-inner-tag-preserve customer 1 create
sap 1/1/3:10.45 create
no shutdown
exit
sap 1/1/4:200.45 create
no shutdown
exit
no shutdown
exit
-----------------------------------------------------------------------------------