Reference Guide

NOTE: Not all CAM profiles and microcodes are available for all systems. For details regarding available profiles for
each system, refer to the Command Line Interface Reference Guide .
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 multi-protocol label switching (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 fifth label, hashing for default load-balance is based on MPLS labels. For
packets with more than five 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 access control lists (ACLs) (for example, the VLAN
ACL Group feature, which permits group virtual local area networks [VLANs] IP egress ACLs.
Boot Behavior
The profile and microcode loaded on the primary route processor module (RPM) determines the profile and microcode
that is required on all other chassis components and is called the “chassis profile.”
A profile mismatch condition exists if either the CAM profile or the microcode does not match. The following points
describe line card boot behavior when the line card profile does not match the chassis profile.
• A microcode mismatch constitutes a profile mismatch.
• When the line card profile and chassis profile are of the same type (single-CAM or dual-CAM), but their CAM
profiles do not match, the line card must load a new profile and therefore takes longer to come online.
• If you insert a single-CAM line card into a chassis with a dual-CAM profile, the system displays Message 1. The
line card boots with the default (single-CAM) profile and remains in a problem state as shown in the following
command output example. The line card cannot forward traffic in a problem state.
• If you insert a dual-CAM line card into a chassis with a single-CAM profile, the line card boots with a matching
profile, but operates with a lower capability.
Message 1: EF Line Card with EG Chassis Profile Error
# Before reload:
01:09:56: %RPM0-P:CP %CHMGR-4-EG_PROFILE_WARN: If EG CAM profile is
selected, non-EG
cards will be in problem state after reload
# After reload:
00:04:46: %RPM0-P:CP %CHMGR-3-PROFILE_MISMATCH: Mismatch: line card 1 has
mismatch CAM
profile or microcode
Message 2: EH Line Card with EG Chassis Profile Error
# Before reload:
01:09:56: %RPM0-P:CP %CHMGR-4-EH_PROFILE_WARN: If EH CAM profile is
205