Alcatel-Lucent 7210 SAS-D User Manual

System Management
7210 SAS D, E, K OS Basic System Configuration Guide Page 399
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.
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:
• 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.
Please see the 7210 QoS user guide, 7210 Systems Basic Guide and the 7210 SAS Router
Configuration Guide for more information about use of SAP aggregate feature, ingress CAM
resource allocation and use of ACLs policies respectively.
With the no form of the command, the software does not allocate any resources for use by SAP
ingress aggregate meter. If no resources are allocated for use, then 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.
Platforms Min value
(per node)
Max value
(per node)
Default Values
7210 SAS-D (per node) 0 1 0

Alcatel-Lucent 7210 SAS-D Specifications

General

Brand	Alcatel-Lucent
Model	7210 SAS-D
Category	Switch
Language	English