Content Addressable Memory (CAM) | 289Return to the Default CAM ConfigurationReturn to the default CAM Profile, microcode, IPv4Flow, or Layer 2 ACL configuration using thekeyword default from EXEC Privilege mode or from CONFIGURATION mode, as shown in the followingexample.FTOS(conf)#cam-profile ?default Enable default CAM profileeg-default Enable eg-default CAM profileipv4-320k Enable 320K CAM profileipv4-egacl-16k Enable CAM profile with 16K IPv4 egress ACLipv6-extacl Enable CAM profile with extended ACLl2-ipv4-inacl Enable CAM profile with 32K L2 and 28K IPv4 ingress ACLunified-default Enable default unified CAM profileFTOS(conf)#cam-profile default microcode ?default Enable default microcodelag-hash-align Enable microcode with LAG hash alignlag-hash-mpls Enable microcode with LAG hash MPLSFTOS(conf)#cam-profile default microcode defaultFTOS(conf)#cam-ipv4flow ?default Reset IPv4flow CAM entries to default settingmulticast-fib Set multicast FIB entriesFTOS(conf)#cam-l2acl ?default Reset L2-ACL CAM entries to default settingsystem-flow Set system flow entriesCAM OptimizationCAM optimization is supported on platforms c sWhen this command is enabled, if a Policy Map containing classification rules (ACL and/or dscp/ip-precedence rules) is applied to more than one physical interface on the same port-pipe, only a singlecopy of the policy is written (only 1 FP entry will be used). When the command is disabled, the systembehaves as described in this chapter.Applications for CAM ProfilingLAG HashingFTOS includes a CAM profile and microcode that treats MPLS packets as non-IP packets. Normally,switching and LAG hashing is based on source and destination MAC addresses. Alternatively, you canbase LAG hashing for MPLS packets on source and destination IP addresses. This type of hashing isallowed for MPLS packets with 5 labels or less.MPLS packets are treated as follows:
