Nokia 7210 SAS-M User Manual

7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
System Management
Edition: 01 3HE 16132 AAAB TQZZA 557
• It does not allocate any additional resources from the available global ingress CAM
resource pool to SAP aggregate meter, if it can allocate the required number of meters
from the chunks/resources allocated to ingress ACLs (or from resources allocated to
G8032-fast-flood in 7210 SAS-M network mode only). For example, if the user has
allocated 2 chunks of 512 entries each for ingress ACLs and then configures sap-
aggregate-meter to use 2 chunks to use about 512 aggregate meters, the software will
not allocate any additional entries from the available global resource pool.
• If the number of ingress ACL resources allocated by user is less than the number of
resources assigned by the user to sap-aggregate-meter (or if no resources are allocated
to G8032), then it allocates the difference from the available global ingress CAM
resource pool. For example, if the user has allocated 1 chunk of 512 entries for ingress
ACLs and then configures sap-aggregate-meter to use 2 chunks to use about 512
aggregate meters, the software will allocate 1 additional chunk (2 chunks required for
SAP aggregate - 1 chunk alloted to ingress ACLs) for use with SAP aggregate meter.
The classification entries associated with additional chunk alloted for SAP aggregate-
meter can be used by the ingress ACLs policies. It cannot be used by SAP ingress QoS
policies and eth-cfm UP MEP.
Similar checks as above are performed when the user allocates resources for SAP aggregate
meters using this command and then configures resources for ingress ACLs (or for G8032-
fast-flood feature). That is, the software does the following.
• It does not allocate any additional entries from the available global ingress CAM
resource pool to ingress ACLs, if it can allocate the required number of classification
entries from the chunks allocated to SAP aggregate meter feature. For example, if the
user has allocated 2 chunks of 512 entries each for SAP aggregate meters and then
configures ingress ACLs to use 2 chunks to use about 512 classification entries, the
software will not allocate any additional entries from the available global resource pool.
• If the number of SAP aggregate meter resources allocated by user is less than the
number of resources requested by the user for ingress ACLs, then it allocates the
difference from the available global ingress CAM resource pool. For example, if the user
has allocated 1 chunk of 512 entries for SAP aggregate meters and then configures
ingress ACLs to use 2 chunks, the software will allocate 1 additional chunk (2 chunks
required for ingress ACLs - 1 chunk alloted to SAP aggregate meter) for use with ingress
ACLs. The meter resources associated with additional chunk allo
ted for ingress ACLs
can be assigned to the SAP aggregate feature, if need be.
Refer to the 7210 SAS-M, T, Mxp, Sx, S Quality of Service Guide and the 7210 SAS-M, T,
R6, R12, Mxp, Sx, S Router Configuration Guide for more information about use of SAP
aggregate feature, ingress CAM resource allocation, and use of ACLs policies respectively.
The no form of this command specifies that the software does not allocate any resources for
use by SAP ingress aggregate meter. If no resources are allocated for use, the software fails
all attempts to associate an aggregate-meter with SAP ingress.
Parameters num-resources — Specifies the maximum amount of resources for use by this filter
match criteria.

Nokia 7210 SAS-M Specifications

General

Brand	Nokia
Model	7210 SAS-M
Category	Cell Phone
Language	English