Resource Allocation For Service Ingress Qos Policies - Alcatel-Lucent 7210 SAS M OS Quality Of Service Manual

Please see the section on
more information.

Resource Allocation for Service Ingress QoS policies

The available global pool of ingress internal CAM hardware resources can be allocated as per user
needs for use with different features such as SAP ingress QoS policy, ingress ACLs, etc. SAP
ingress QoS can be allocated classification and meter resources for use from this pool. Further on,
resources can be allocated for different SAP ingress QoS policy classification match criteria, based
on the operator needs. Users can modify the resource allocated to scale the number of entries
available per match criteria or scale the number of SAPs. The resources from the global ingress
internal CAM pool are allocated in chunks with fixed number of entries. For 7210 SAS-M , each
chunk allows for 512 classification entries and 256 meters. The number of chunks to be allotted for
SAP ingress QoS policy is specified using the CLI command configure> system> resource-
profile> ingress-internal-tcam> qos-sap-ingress-resource.
User can specify a limit for the amount of resources required for SAP ingress QoS policies and
also an option to limit the amount of resources used per match criteria supported for SAP ingress
QoS policies. A given chunk can be used for either MAC criteria or IP criteria or IPv6 criteria.
Allocation of classification entries also allocates meter/policer resources, used to implement per
FC per traffic type policing.
By default, the system allocates resources for SAP ingress QoS policies to maintain backward
compatibility with release 4.0 and allocates resources for MAC criteria and IP criteria (by setting it
to 'max'). Setting the value to 'max' allows each match criteria to use the available SAP ingress
QoS resources on first-cum-first-served model. By default, software does not allocate resources
for use by ingress IPv6 filters. Before associating an IPv6 SAP ingress policy to a SAP, resources
must be allocated. Until resources are allocated for use by IPv6 filters, software fails all attempts
to associate an IPv6 filter policy with a SAP.
When the user allocates resources for use by SAP ingress QoS policies using the CLI command
configure> system> resource-profile> qos-sap-ingress-resource, the system allocates resources in
chunks of 512 entries. The usage of these entries by different type of match criteria is given below:
•
For example: Assume a SAP Ingress QoS policy is configured to use mac-criteria with 50 entries
and uses "configure> system> resource-profile> ingress-internal-tcam> qos-sap-ingress-resource>
7210 SAS M OS Quality of Service Guide
user must remove the association and then change the SAP ingress policy to use the new
match criteria. For SAPs configured in VPRN services, the computation of resources is
similar to an SAP configured in an Epipe service.
"Resource Allocation for Service Ingress QoS policies on page
mac-criteria (any) - User needs to allocate resources for mac-criteria from the SAP
ingress QoS resource pool by using the command "configure> system> resource-profile>
ingress-internal-tcam> qos-sap-ingress-resource> mac-match-enable" before using SAP
ingress policies with mac-criteria. Every entry configured in the SAP ingress QoS policy
using the mac-criteria uses one (1) entry from the chunks in the hardware.
Service Ingress QoS Policies
Page 237
237" for