Table of Contents
Advertisement
from the chunks depending on whether the SAP ingress policy uses ip-criteria or mac-criteria or
ipv6-criteria.
The users can use "tools> dump> system-resources" command to know the current usage and
availability. One or more entries per chunk are reserved for system use.
Computation of resources used per SAP ingress policy
The user is allowed to configure the number of classification entries the SAP requires (for
example: TQ).
To calculate the number of SAPs allowed, assume all configured to use 'TQ' QoS resources per
SAP.
Number of SAPs allowed = maximum classification entries / TQ.
NOTE: The number of SAPs arrived at using the equation above is subject to system limits. The
above equation is used to derive the limit on the number of SAPs due to QoS resources only.
The user is allowed to mix and match SAPs with different QoS resources (that is, using different
values of TQ).
The following determines the number of QoS resources to be allocated for an SAP:
•
•
•
Only those FCs that are in use by the match-criteria classification entries are considered for the
number of FCs. Therefore, these FCs are referred to as 'FC in use'.
Given the number of traffic types to use per 'FC in use', the following rules apply for a SAP in a
VPLS service to arrive at number of classification entries per FC in use:
•
7210 SAS-X and 7210 SAS-R6 OS Quality of Service Guide
Number of meters allocated automatically by system = TQ / 2 (up to a maximum of 32
meters).
Number of match-criteria entries used to identify the FC.
Number of FCs to use and number of traffic-types to be policed per FC.
The amount of hardware classification resources needed per entry configured by the user
(refer to the section
"Resource Allocation for Service Ingress QoS policies on page
to know about resources needed per match entry. It varies based on different match criteria
in use).
If a FC is in use and is created without explicit meters, use default meter #1 for unicast
traffic and for all other traffic types (that is, broadcast, multicast and unknown-unicast).
This requires one classification entry in hardware. This assumes default mulitpoint meter
#11 is not created by the user.
Service Ingress QoS Policies
Page 211
208"
Advertisement
Table of Contents
