Nokia 7210 Configuration Manual page 559

7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
This command allocates meter resources from the available global ingress CAM resource
pool. By default, when resources are allocated to SAP ingress QoS policy, along with the
CAM classification entries, meter resources are also allocated. Hence, if the user needs to
use SAP aggregate meter functionality they cannot allocate all the available resources in the
global resource pool to SAP ingress QoS policies and ETH-CFM UP MEP. They need to
allocate some resources for use by SAP aggregate meter (or SAP ingress ACLs or G8032-
fast-flood feature).
By default, when resources are allocated for ingress ACLs (and G8032 in 7210 SAS-M
network mode only), only classification entries are used and meters resources are not used.
SAP aggregate meter resources can use meters from this pool of meter resources. In other
words, SAP aggregate meters are stolen from the unused meters in the resources allocated
to ingress ACLs.
If the user allocates resources for ingress ACLs (or for G8032-fast-flood feature in
7210 SAS-M network mode only) and configures resources for SAP aggregate meter using
this command, the software does the following.
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.
3HE 17358 AAAB TQZZA
• 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.
• 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.
Use subject to Terms available at: www.nokia.com
© 2021 Nokia.
System Management
559