Command Reference Guide

422 | Content Addressable Memory (CAM)
www.dell.com | support.dell.com
Defaults
cam-profile default microcode default
Command Modes
CONFIGURATION
Command
History
Usage
Information
You must save the running configuration using the command copy running-config startup-config
after changing the CAM profile from CONFIGURATION mode. CAM profile changes take
effect after the next chassis reboot.
show cam-acl
c s
Display the details of the CAM profiles on the chassis and all line cards.
microcode microcode
Choose a microcode based on the CAM profile you chose. Not all
microcodes are available to be paired with a CAM profile.
• Enter the keyword default to select the microcode that distributes
CAM space for a typical deployment.
• Enter the keyword
lag-hash-align to select the microcode for
applications that require the same hashing for bi-directional traffic.
• Enter the keyword
lag-hash-mpls to select the microcode for hashing
based on MPLS labels (up to five labels deep).
• Enter the keyword ipv6-extacl to select the microcode for IPv6.
• Enter the keyword acl-group to select the microcode for applications
that need 16k egress IPv4 ACLs.
• Enter the keyword
ipv4-vrf to select the microcode for IPv4 VRF
applications.
• Enter the keyword
ipv4-v6-vrf to select the microcode for IPv4 and
IPv6 VRF applications.
• E-Series TeraScale only: Select l2-switched-pbr microcode if you
apply a PBR redirect list to a VLAN interface and want to prevent
Layer 2 traffic from being redirected and dropped. l2-switched-pbr
(IPv4-LDA) microcode allows only Layer 3 traffic to be redirected
while Layer 2 traffic is switched within the VLAN.
Version 8.4.1.0 Added support for l2-switched-pbr microcode.
Version 8.2.1.0 Added support for the ipv4-64k-ipv6 profile.
Version 7.9.1.0 Added support for VRF protocols.
Version 7.5.1.0 Added the l2-ipv4-inacl CAM profile
Version 7.4.2.0 Added the unified-default CAM profile and lag-hash-align microcode
Version 7.4.1.0 Added the lag-hash-mpls microcode
Version 6.5.1.0 Added the eg-default and ipv4-320k CAM profiles
Version 6.3.1.0 Introduced on E-Series
Note: Do not use the ipv4-egacl-16 CAM profile for Layer 2 egress ACLs.
Note: Do not make any changes to the CAM profile after you change the profile to
ipv4-320K and save the configuration until after you reload the chassis; any changes
lead to unexpected behavior. After you reload the chassis, you may make changes to
the IPv4 Flow partition.