The following QoS policies can be applied to an Epipe service:
traffic management
Traffic management of Ethernet VLLs is achieved through the application of ingress QoS policies to SAPs and access egress QoS policies applied to the port. All traffic management is forwarding-class aware, and the SAP ingress QoS policy identifies the forwarding class based on the rules configured to isolate and match the traffic ingressing on the SAP. Forwarding classes are determined based on the Layer 2 (dot1p, MAC) or Layer 3 (IP, DSCP) fields of contained packets, and this association of forwarding class at ingress will determine both the queuing and the Dot1P bit setting of packets on the Ethernet VLL on the egress.
SAP ingress classification and policing
The traffic at the SAP ingress is classified and metered according to the SLA parameters. All the traffic ingressing on the SAP is classified to a particular forwarding class. All the forwarding class is metered through and marked in-profile or out-of-profile, based on the meter parameters.
When applied to 7210 SAS Epipe services, service ingress QoS policies only create the unicast queues defined in the policy. The multipoint queues are not created on the service. Both Layer 2 or Layer 3 criteria can be used in the QoS policies for traffic classification in a service.
egress network dot1p marking
Marking of IEEE dot1p bits in VLAN tags is as per the FC-to-dot1p map. Refer to the default network QoS policy in the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information. This marking is applied at the port level on access ports and access-uplink ports.
Ingress network classification
Ingress network classification is based on the dot1p bits in the outer VLAN tag received on the access-uplink port. Dot1p-to-FC mapping is based on the network ingress QoS policy.