System Resource Allocation; Allocation Of Ingress Internal Tcam Resources - Alcatel-Lucent 7210 SAS-D Configuration Manual

System Resource Allocation

Allocation of Ingress Internal TCAM resources

In current releases, the system statically allocates ingress TCAM resources for use by SAP ingress
QoS classification, SAP ingress access control list (ACLs), Identifying and sending CFM OAM
packets to CPU for local processing, and so on. The resource allocation is not user configurable.
With introduction of new capabilities such as IPv6 classification, UP MEP support, and G8032-
fast-flood, the static allocation of resources by software does not meet requirements of different
customers, who typically want to use different features.
The user can allocate a fixed amount of resources per system to be used for QoS, ACLs, CFM/
Y.1731 MEPs and other features. Some of these parameters are boot-time and others are run-time.
A change in current value of the parameter that is designated 'boot-time' needs a reboot of the
node , before the new value takes effect. Change in current value of the parameter that is
designated 'run-time' takes effect immediately, if the software determines resources are available
for use to accommodate the change.
During system bootup, the system reads all the resource profile parameters and allocates resources
to the features, in the order of which it appears in the configuration file. (NOTE: The order in
which the command appears in the configuration file is important).The resources are shared;
therefore the user has to ensure that the sum total of such resources does not exceed the limit
supported by the IMM/node. If the system determines that it cannot allocate the requested
resources, the system disables the feature from us. For example, if the system determines that it
cannot allocate resources for g8032-fast-flood, it disables the feature from use (that is, G8032 eth-
rings does not use fast-flood mechanisms). Another example is, if the system determines that it
cannot allocate resources for ipv4-based SAP Ingress ACL classification, then the system does not
allow users to use ipv4-based SAP ingress ACL classification feature and fails the configuration
when it comes upon the first SAP in the configuration file which uses an IPv4-based SAP ingress
ACL policy.
For boot-time parameters, such as g8032-fast-flood-enable, it is the user's responsibility to ensure
that configuration of services matches the resource allocated. If the system determines that it
cannot allocate resources to services then it fails the configuration file at the first instance where it
encounters a command to which resources cannot be allocated. The available resources can be
allocated to different features. Please refer to the scaling guide for amount of resources available
per platform and per feature.
For ACL and QoS resources, the user has the option to allocate resources to limit usage per
feature, irrespective of the match criteria used (that is, sum of all resources used for different SAP
ingress classification match-criteria is limited by the amount allocated for SAP ingress
classification) and can further allocate resources for use by specific match criteria. User can
enable any of the match criteria from among those supported and associate a fixed amount of
resources with each of them in are put together of fixed sizes (the chunk size is dependent on the
platform).
7210 SAS D, E, K OS Basic System Configuration Guide
System Management
Page 223