Ethernet Pipe (Epipe) Services
Page 126 7210 SAS-X, R6 OS Services Guide
• 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.
• OAM tools
→ MPLS OAM tools such as vccv-ping, vccv-trace, etc. is supported for the SDPs
→ Accounting and Statistics for the service entities (e.g. 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.
• Following Redundancy mechanisms available in Epipe service is 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)
Configuration of Epipe service for processing of packets
received with more than 2 tags on a QinQ SAP devices
configured
The following is the example when the user configures “vlan-vc-tag” value to
match the inner tag specified in the Q1.Q2 SAP configured in the service :
*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
----------------------------------------------
To Next Page
Loading...
