Hierarchical Ingress Policing; Access Egress Qos Policies - Alcatel-Lucent 7210 SAS M OS Quality Of Service Manual

QoS Overview

Hierarchical Ingress Policing

Hierarchical ingress policing allows the users to specify the amount of traffic admitted into the
system per SAP. It also allows the user to share the available bandwidth per SAP among the
different FCs of the SAP. For example, user can allow the packets classified as Internet data to use
the entire SAP bandwidth when other forwarding classes do not have traffic.
It provides an option to configure SAP aggregate policer per SAP on SAP ingress. The user should
configure the PIR rate of the aggregate policer. The user can optionally configure the burst size of
the aggregate policer.
The aggregate policer monitors the traffic on different FCs and determines if the packet has to be
forwarded to an identified profile or dropped. The final disposition of the packet is based on the
operating rate of the following:
•
•
For more information on the final color assigned of the packet, refer to the command description
of "aggregate-meter-rate" command in the 7210 SAS M Services Guide.
A new meter mode "trtcm2" (RFC 4115) is introduced for use only on SAP ingress. When the
SAP aggregate policer is configured, the per FC policer can be only configured in "trtcm2" mode.
The existing meter mode "trtcm" is re-named as "trtcm1" (RFC 2698). The meter modes "srtCM"
and "trtcm1" are used in the absence of aggregate meter.
NOTE: Before use of per SAP aggregate policer/meter, meter resources must be allocated using
the CLI command config> system> resource-profile> ingress-internal-tcam> sap-aggregate-meter.
Change to the amount of resources allocated for SAP aggregate meter requires a reboot of the node
to take effect. For more information, see the 7210 Basic System Guide.

Access Egress QoS Policies

An access egress policy defines the queue and marking characteristics for the traffic egressing
towards the customer on the access ports. There are 8 queues always available at the access port
and FCs are mapped into these 8 Queues. By configuring appropriate queue shape rates the
individual FC traffic can be managed so that each FC traffic is well within SLA limits and does not
impact the serviceability of other FCs.
Access egress QoS policies define access queues and map forwarding class flows to queues.
There are 8 queues always available per access port and all forwarding classes traffic is mapped
into these separate 8 queue as per
define a basic access egress QoS policy, the following are required:
Page 54
Per FC policer
Per SAP aggregate policer
Table 32, Forwarding Class to Queue-ID Map, on page
7210 SAS M OS Quality of Service Guide
82. To