Table of Contents
Advertisement
Overview
•
•
The SAP ingress resource chunks referred to in this section is different from the resources
specified using the command 'num-qos-classifiers'. num-qos-classifiers set the limit on the
resources needed per SAP ingress QoS policy. 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,
a SAP specifies the amount of QoS resources it needs, using the 'num-qos-resources' CLI
command (in the SAP ingress policy) and the software allocates the resources required by a SAP
Page 210
7210 SAS-X and 7210 SAS-R6 OS Quality of Service Guide
entries available.
IPv4(any) and MAC(any) match - User needs to allocate resources from the SAP
ingress QoS resource pool to use both IP-criteria (any) and MAC-criteria (any) in a single
policy by using the command "configure> system> resource-profile> ingress-internal-
tcam> qos-sap-ingress-resource> ipv4-mac-match-enable" before using the capability.
Every ipv4 criteria match entry or MAC criteria match entry configured in the QoS policy
uses two (2) entries from the chunks allocated. Software allocates entries from the ipv4-
mac-match-enable pool if the SAP ingress QoS policy uses both ip-criteria (any) and ipv6-
criteria (any).
It also allocates entries for all other criteria if there are no resources available to use in the
pool allocated to those resources (that is, only mac-criteria any, only ip-criteria any, mac-
criteria dot1p-only, ip-criteria dscp-only, ipv4-criteria dscp-only are allocated resources
from this pool if there are no resources available in other pools). Note resources are not
allocated to ipv6-criteria (any) from this pool.
dot1p-only, IPv4 dscp-only, IPv6 dscp-only and Default SAP Ingress QoS policies -
User can use the option 'dot1p-only' or dscp-only', if they plan to use only dot1p bits or
only IP DSCP bits or only IP precedence bits for SAP ingress classification. This typically
allows for efficient use of available hardware resources and better scaling. SAP ingress
policies that use only Dot1p bits or only IPv4/IPv6 DSCP or IPv4/IPv6 precedence or
Default SAP ingress QoS policies bits can use the resources from chunks currently
allocated for use by either IP-criteria or MAC-criteria or IPv6 criteria. There are some
special cases noted below for allocation of resources for default, dot1p-only and dscp-only
SAP ingress policies:
→ If there are no chunks available for accommodating a SAP that is associated with
default or dot1p-only or a dscp-only SAP ingress policy, the software allocates
resources against mac-criteria if the SAP is configured in a VLL or VPLS service. The
software uses the required number of entries for this policy. The remaining entries is
available for SAPs that use mac-criteria or that use only dot1p or only ipv4/ipv6
DSCP or that use default policy.
→ If there are no chunks available for accommodating a SAP that is associated with
default, dot1p-only or a dscp-only SAP ingress policy, the software allocates
resources against ipv4-criteria if the SAP is configured in an IES, R-VPLS or a VPRN
service. The software uses the required number of entries for this policy. The
remaining entries is available for SAPs that use ipv4-criteria or that use only ipv4/ipv6
DSCP or only dot1p criteria or that use default policy.
Advertisement
Table of Contents
