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

System Basics Introduction

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 or on 7210 SAS-R6 devices, issuing the card reset command, 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.
On 7210 SAS-M, 7210 SAS-T and 7210 SAS-X, the system resource profile parameters are
available under config> system> resource-profile and the parameters defined are applicable to the
entire node. On 7210 SAS-R6 devices, the system resource profile parameters are defined as a
policy. User needs to configure the system resource profile policy and associate it with the IMM.
The software reads the configured policy and allocates resources appropriately per IMM. It allows
users to allocate resource to different features per IMM. On 7210 SAS-R6, some of the system
resource profile parameters are applicable to the entire node and not per IMM. For more
information, see the
and 7210 SAS-X on page
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
Page 254
System Resource-Profile Router Commands for 7210 SAS-M, 7210 SAS-T,
334.
7210 SAS M, T, X, R6 Basic System Configuration Guide