Alcatel-Lucent 7210 SAS M - Filter Policies; Qos Policies

VLL Service Considerations
Page 166 7210 SAS M Services Guide
connection profile is not available. No support for Egress SAP statistics and accounting is
available.
• Mirroring is supported. In network mode, the use of service resiliency mechanisms such
as MC-LAG and Epipe PW redundancy is supported.
QoS Policies
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 the 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 put-profile
based on the Meter parameters.
When applied to 7210 SAS M Epipe services, service ingress QoS policies only create the unicast
queues defined in the policy. The multipoint queues are not created on the service. Note that 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 tag is as per the FC-
to-Dot1p map. For details see the default network QoS policy in the QoS user guide. 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.
Filter Policies
7210 SAS M Epipe services can have a single filter policy associated on both ingress and egress.
Both MAC and IP filter policies can be used on Epipe services.
Note: In the IES service in access-uplink mode, ipv6 filter can be applied on access uplink SAP.