See the 7210 SAS Release Notes for information about services supported on different 7210 SAS platforms. The references to services in the following table appear for completeness and do not imply support is available.
This section provides information about the resource consumption per SAP ingress policy. Resources required by the SAP ingress policy are allocated from the ingress-internal-tcam resource pool, based on the amount of resources allocated for SAP ingress classification.
The user can configure the number of classification entries the SAP requires (for example, TQ).
Number of meters allocated automatically by system = TQ / 2
(up to a maximum of 32 meters)
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
The number of SAPs arrived at using the preceding equation is subject to system limits. The preceding 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 allowed values in 7210 SAS-D devices for the num-qos-classifiers command are: 4, 8, 16, 32, 64, 128, and 256. The allowed num-qos-classifiers values for 7210 SAS-Dxp devices are any multiple of 2, between 2 and 256.
The following items determine the number of QoS resources to be allocated for a SAP:
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 (see Resource allocation for service ingress QoS policy classification rules for information about resources needed per match entry; it varies based on different match criteria in use)
Only those FCs that are in use by the match-criteria classification entries are considered for the number of FCs. These FCs are referred to as ‟FCs in use”.