7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
For more information about specific CLI commands and features that use system
resource allocation, refer to the CLI command and feature descriptions in the
appropriate 7210 SAS software user manual.
6.8.2 Allocation of Egress Internal TCAM Resources
Before the introduction of new capabilities, such as IPv6 match criteria, the system
allocated egress TCAM resources on bootup for use by different criteria in SAP
egress access control lists (ACLs) and other purposes; the resource allocation was
not user configurable. With the introduction of new capabilities, such as IPv6 match
criteria in egress, the static allocation of resources by software may not meet
customer requirements if they want to use different features. Therefore, to facilitate
user configuration and resource allocation in accordance with user needs, the
ingress internal TCAM resource allocation capabilities have been extended to
include the egress internal TCAM resources.
For information about specific CLI commands and features that use system resource
allocation, refer to the CLI command and feature descriptions in the appropriate
7210 SAS software user manuals.
Note: The commands in the config>system>resource-profile context, which require a
reboot to take effect, are read and implemented by the system only during bootup. These
commands do not take effect if the exec command is used to run the configuration file.
6.8.3 System Resource Allocation Examples
This section provides system resource allocation examples.
Example 1:
config> system> resource-profile...
...
...
In the preceding CLI example, the system performs the following actions.
3HE 17358 AAAB TQZZA
acl-sap-ingress 3
mac-match-enable max
ipv4-match-enable 1
no ipv6_128-ipv4-match-enable
no ipv6_64-only-match-enable
exit
• 3 chunks are allocated for use by the SAP ingress ACL entries.
Use subject to Terms available at: www.nokia.com
© 2021 Nokia.
System Management
315