Table of Contents
Advertisement
•
•
•
7210 SAS-X and 7210 SAS-R6 OS Quality of Service Guide
mac-criteria (any) - User needs to allocate resources for a SAP ingress policy using mac-
criteria (any or dot1p-only) or a SAP ingress policy that specifies both IP and MAC
criteria (any, dot1p-only) 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.
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> mac-match-enable 1", to configure one chunk for use by mac-criteria
(allowing a total of 512 entries for use by policies using mac-criteria). In this case, the user
can have 10 SAPs using mac-criteria SAP ingress policy and consumes 500 entries.
ipv4-criteria (any) - The usage is same as the mac-criteria. Resources need to be
allocated using the command "configure> system> resource-profile> ingress-internal-
tcam> qos-sap-ingress-resource> ipv4-match-enable". Additionally,IPv4 criteria can share
the entries allocated for IPv6 criteria. The software automatically allocates entries from an
IPv6 criteria slice to IPv4 criteria policies, if there are no entries available in the allocated
IPv4 criteria chunks and there are no chunks available for allocation to IPv4 criteria from
the SAP ingress QoS resource pool. The number of hardware entries taken up by an IPv4
criteria entry when using the IPv6 criteria chunks is the same as required by an entry using
IPv6 criteria (see below for details).
ipv6-criteria (any) - User needs to allocate resources from the SAP ingress QoS resource
pool for ipv6-criteria by using the command "configure> system> resource-profile>
ingress-internal-tcam> qos-sap-ingress-resource> ipv6-ipv4-match-enable" before using
IPv6 criteria and num-qos-classifiers must specify the ipv6 keyword. Every ipv4 criteria
match entry or ipv6 criteria match entry configured in the QoS policy using ipv6-criteria
uses two (2) entries from the chunks allocated for use by ipv6-criteria (128-bit) in the
hardware. Software allocates entries from the ipv6-criteria pool if the SAP ingress QoS
policy uses both ipv6-criteria (any or IPv6 DSCP) entries and ipv4-criteria (any or IPv4
DSCP) entries or if the SAP ingress QoS policy uses only IPv6 criteria (any or IPv6
DSCP) or if the SAP ingress QoS policy uses ipv4 criteria any and there are no resources
available in the IPv4 criteria (as explained above).
For example: Assume a QoS policy is configured to use ipv6-criteria with 50 entries and
using "configure>system> resource-profile> ingress-internal-tcam> qos-sap-ingress-
resource> ipv4-ipv6-128-match-enable 1", user configures one chunk for use by ipv6-
criteria. This allows for a total of 256 entries for use by SAPs using SAP ingress QoS
policies with ipv6-critiera (as each IPv6 entry uses 2 entries in hardware). In this example,
user can have five (5) SAPs using this policy and consuming 250 entries in total. These
resources can be shared with policies that use IPv4 criteria, though it consumes 2 entries in
hardware consumed per IPv4 criteria entry. It allows user to make use of spare IPv6
resources for IPv4 criteria policies, though if user plans to have a larger number of IPv4
criteria policies they are better off allocating more resources for use with IPv4 criteria.
NOTE: When a chunk/slice is allocated for IPv6 criteria, software automatically adjusts
the number of available classification entries in that chunk to half the number of total
Service Ingress QoS Policies
Page 209
Advertisement
Table of Contents
