The ipv6acl and vman-dual-qos allocations must be entered as a factor of 2 (2, 4, 6, 8, 10). All other
profile allocations can use either even or odd numbered ranges.
You must save the new CAM settings to the startup-config (write-mem or copy run start) then
reload the system for the new settings to take effect.
1. Select a cam-acl action.
CONFIGURATION mode
cam-acl [default | l2acl]
NOTE: Selecting default resets the CAM entries to the default settings. Select l2acl to allocate
space for the ACLs and QoS regions.
2. Enter the number of FP blocks for each region.
EXEC Privilege mode
l2acl number ipv4acl number ipv6acl number, ipv4qos number l2qos number,
l2pt number ipmacacl number ecfmacl number nlbcluster number[vman-qos |
vman-dual-qos number
3. Reload the system.
EXEC Privilege mode
reload
4. Verify that the new settings will be written to the CAM on the next boot.
EXEC Privilege mode
show cam-acl
Test CAM Usage
This command applies to both IPv4 CAM profiles, but is best used when verifying QoS optimization for
IPv6 ACLs.
Use this command to determine whether sufficient ACL CAM space is available to enable a service-policy.
Create a Class Map with all required ACL rules, then execute the test cam-usage command in Privilege
mode to verify the actual CAM space required. The Status column in the command output indicates
whether or not the policy can be enabled.
Example of the test cam-usage Command
Dell#test cam-usage service-policy input pmap stack-unit all
Stack-Unit | Portpipe | CAM Partition | Available CAM | Estimated CAM per Port
| Status
--------------------------------------------------------------------------------
----------
2 | 0 | L2ACL | 28 | 1
| Allowed (28)
Content Addressable Memory (CAM) 241