cam-acl {default | l2acl number ipv4acl number ipv6acl number ipv4qos number l2qosnumber l2pt number ipmacacl number vman-qos | vman-dual-qos number ecfmacl numbernlbcluster number ipv4pbr number openflow number | fcoe number iscsioptacl number[vrfv4acl number]NOTE: If you do not enter the allocation values for the CAM regions, the value is 0.3. Execute write memory and verify that the new settings are written to the CAM on the next boot.EXEC Privilege modeshow cam-acl4. Reload the system.EXEC Privilege modereloadTest CAM UsageTo determine whether sufficient CAM space is available to enable a service-policy, use the test-cam-usage command. To verifythe actual CAM space required, create a Class Map with all required ACL rules, then execute the test cam-usage command inPrivilege mode. The Status column in the command output indicates whether or not you can enable the policy.Example of the test cam-usage CommandDell#test cam-usage service-policy input test-cam-usage stack-unit 2 po 0Stack-Unit| Portpipe|CAM Partition|Available CAM|Estimated CAM per Port|Status------------------------------------------------------------------------------------2 | 0 |IPv4Flow |192 |3 |Allowed (64)Dell#View CAM-ACL SettingsThe show cam-acl command shows the cam-acl setting that will be loaded after the next reload.Example of Viewing CAM-ACL SettingsDell(conf)#do show cam-acl-- Chassis Cam ACL --Current Settings(in block sizes) Next Boot(in block sizes)1 block = 128 entriesL2Acl : 6 4Ipv4Acl : 4 2Ipv6Acl : 0 0Ipv4Qos : 2 2L2Qos : 1 1L2PT : 0 0IpMacAcl : 0 0VmanQos : 0 0VmanDualQos : 0 0EcfmAcl : 0 0FcoeAcl : 0 0iscsiOptAcl : 0 0ipv4pbr : 0 2vrfv4Acl : 0 2Openflow : 0 0fedgovacl : 0 0-- Stack unit 0 --Current Settings(in block sizes) Next Boot(in block sizes)1 block = 128 entriesL2Acl : 6 4Ipv4Acl : 4 2Content Addressable Memory (CAM) 227
