Reference Guide

| | IN-L3 ACL | 12288 | 2 | 12286
| | IN-L3 FIB | 262141 | 14 | 262127
| | IN-L3-SysFlow | 2878 | 44 | 2834
--More--
Return to the Default CAM Configuration
Return to the default CAM Profile, microcode, IPv4Flow, or Layer 2 ACL configuration using the keyword default from
EXEC Privilege mode or CONFIGURATION mode, as shown in the following example.
Example of the cam-profile default Command
FTOS(conf)#cam-profile ?
default Enable default CAM profile
eg-default Enable eg-default CAM profile
ipv4-320k Enable 320K CAM profile
ipv4-egacl-16k Enable CAM profile with 16K IPv4 egress ACL
ipv6-extacl Enable CAM profile with extended ACL
l2-ipv4-inacl Enable CAM profile with 32K L2 and 28K IPv4 ingress ACL
unified-default Enable default unified CAM profile
FTOS(conf)#cam-profile default microcode ?
default Enable default microcode
lag-hash-align Enable microcode with LAG hash align
lag-hash-mpls Enable microcode with LAG hash MPLS
FTOS(conf)#cam-profile default microcode default
FTOS(conf)#cam-ipv4flow ?
default Reset IPv4flow CAM entries to default setting
multicast-fib Set multicast FIB entries
FTOS(conf)#cam-l2acl ?
default Reset L2-ACL CAM entries to default setting
system-flow Set system flow entries
CAM Optimization
CAM optimization is supported on the S4820T platform.
When you enable this command, 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 single copy of the policy is written (only 1 FP
entry is used). When you disable this command, the system behaves as described in this chapter.
Applications for CAM Profiling
The following describes link aggregation group (LAG) hashing.
LAG Hashing
FTOS 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 can base LAG hashing for MPLS packets
on source and destination IP addresses. This type of hashing is allowed for MPLS packets with five labels or less.
MPLS packets are treated as follows:
• When MPLS IP packets are received, FTOS looks up to five labels deep for the IP header.
• When an IP header is present, hashing is based on IP three tuples (source IP address, destination IP address,
and IP protocol).
• If an IP header is not found after the fifth label, hashing is based on the MPLS labels.
226