Reference Guide

264 | Content Addressable Memory (CAM)
www.dell.com | support.dell.com
There is a default microcode, and several other microcodes are available, so that you can adjust packet
handling according to your application. Specifying a microcode is mandatory when selecting a CAM
profile (though you are not required to change it).
CAM Profiling for ACLs
CAM Profiling for ACLs is supported on platform e
t
only.
The default CAM profile has 1K Layer 2 ingress ACL entries. If you need more memory for Layer 2
ingress ACLs, select the profile
l2-ipv4-inacl.
When budgeting your CAM allocations for ACLs and QoS configurations, remember that ACL and QoS
rules might consume more than one CAM entry depending on complexity. For example, TCP and UDP
rules with port range options might require more than one CAM entry.
The Layer 2 ACL CAM partition has sub-partitions for several types of information. Table 11-4 lists the
sub-partition and the percentage of the Layer 2 ACL CAM partition that FTOS allocates to each by default.
Note: Not all CAM profiles and microcodes are available for all systems. Refer to the Command Line
Interface Reference Guide for details regarding available profiles for each system.
Table 11-3. Microcode Descriptions
Microcode Description
default Distributes CAM space for a typical deployment
lag-hash-align
For applications that require the same hashing for bi-directional traffic (for
example, VoIP call or P2P file sharing). For port-channels, this microcode maps
both directions of a bi-directional flow to the same output link.
lag-hash-mpls For hashing based on MPLS labels (up to five labels deep). With the default microcode, MPLS
packets are distributed over a port-channel based on the MAC source and destination address. With
the lag-hash-mpls microcode, MPLS packets are distributed across the port-channel based on IP
source and destination address and IP protocol. This is applicable for MPLS packets with up to five
labels. When the IP header is not available after the 5th label, hashing for default load-balance is
based on MPLS labels. For packets with more than 5 labels, hashing is always based on the MAC
source and destination address.
ipv6-extacl Use this microcode when IPv6 is enabled.
acl-group For applications that need 16k egress IPv4 ACLs (for example, the VLAN ACL Group feature,
which permits group VLANs IP egress ACLs.
Table 11-4. Layer 2 ACL CAM Sub-partition Sizes
Partition % Allocated
Sysflow 6