Table of Contents
Advertisement
Service Ingress QoS Policies
ingress QoS can be allocated classification for use from this pool. Further on, resources can be
allocated for SAP ingress QoS policy classification IPv4, IPv6 and MAC 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.
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 has 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.
By default, the system does not allocate any resources for SAP ingress QoS policies to maintain
backward compatibility with previous releases. Before associating an IPv4 criteria or IPv6 criteria
or MAC criteria SAP ingress policy to a SAP, resources must be allocated. Until resources are
allocated for use, software fails all attempts to associate an policy with a SAP. When the user
allocates resources for use by SAP ingress QoS policies using the CLI command configure>
system> resource-profile> ing-internal-tcam> 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.
The above resources set the maximum limit on the resources available for use by all the SAP
ingress policies in use simultaneously on the system. The software manages the resource chunks
allocated to SAP ingress QoS policy pool and allocates the entries in the chunks when a SAP
ingress QoS policy is associated with a SAP. In other words, the software allocates the resources
required by a SAP from the chunks depending on whether the SAP ingress policy uses ip-criteria
or mac-criteria or ipv6-criteria and the number of entries configured in the SAP ingress policy.
When user allocates chunks of resources using the CLI command, configure> system> resource-
profile> ingress-internal-tcam> qos-sap-ingress-resource, the resources are used only towards
classification entries configured under IPv4 criteria or MAC criteria. A single resource is required
for each entry configured using any of these two criteria.
If user needs to use IPv6 criteria, then resources need to be allocated using the CLI command
configure> system> resource-profile> ingress-internal-tcam> qos-sap-ingress-resource> mac-
ipv4-ipv6-128-match-enable. The resources allocated using this command is used by software to
allocate entries for classification entries configured under ipv6-criteria and ipv4-criteria mac-
criteria. Each IPv6 or IPv4 or MAC classification entry consumes 2 resources from this pool,
reducing the number of classification entries that can be accommodated in a single chunk to 256.
The user can choose to allocate all the chunks allocated for SAP ingress QoS classification for
ipv6 criteria or allocate only a portion of it.
7210 SAS D, E, K OS Quality of Service Guide
Page 237
Advertisement
Table of Contents
