7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
System Management
Edition: 01 3HE 16132 AAAB TQZZA 313
1. Configuring the system resource-profile internal-ingress-tcam qos-sap-
ingress-resource no mac-match-enable command deallocates all the
resources allocated to SAP ingress QoS classification MAC match criteria. After
this command is run, users cannot associate a SAP ingress policy with MAC
match criteria defined to a SAP. Resources allocated to other criteria are
unaffected and can continue to be used.
2. Configuring the system resource-profile internal-ingress-tcam eth-cfm no
up-mep command deallocates all the resources allocated to CFM UP MEP.
After this command is run, user cannot configure UP MEP.
If the system successfully runs the no command, it frees up resources used by the
chunk or slice and make the resources, or the entire chunk/slice, available for use by
other features. Before deallocating resources, the software checks if a service object
is using the resource and fails the command if the object is in use. If resources are
in use, they can be freed up by deleting a SAP, removing a policy association with a
SAP, deleting a MEP, and so on. Some commands under the system resource-
profile context do not take effect immediately and require a system reboot before the
change occurs and resources are freed. The following is the handling of freed
resources.
• If some entries in a slice are freed, they are made available for use by other
SAPs using the same feature to which the chunk is allocated.
• If an entire chunk is freed, it is returned to the system free pool for possible use
by other features.
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.