Alcatel-Lucent 7210 SAS M Configuration Manual page 437

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-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 user allocates resources for ingress ACLs (or for G8032-fast-flood feature in 7210-M network
mode only) and then configures resources for SAP aggregate meter using this command, then the
software does the following:
Similar checks as above are performed when 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:
Please see the 7210 SAS-M,T and 7210 SAS-X,R6 QoS user guide, 7210 SAS-M,X,T, and R6
Systems Basic Guide and the 7210 SAS-M, X,T, and R6 Router Configuration Guide for more
information about use of SAP aggregate feature, ingress CAM resource allocation and use of ACLs
policies respectively.
7210 SAS M, T, X, R6 Basic System Configuration Guide
• It does not allocate any additional chunks/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-M network mode only). For example, if 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 aggre-
gate meters, then 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
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, then the software will allocate 1 addi-
tional 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 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, then 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 avail-
able global ingress CAM resource pool. For example, if user has allocated 1 chunk of 512 entries
for SAP aggregate meters and then configures ingress ACLs to use 2 chunks, then 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 alloted for ingress ACLs can be assigned to the SAP aggregate feature, if need be.
System Management
Page 437