Administrator Guide

Version Description
9.9(0.0) Introduced on the C9010.
9.2(1.0) Introduced on the Z9500.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
7.8.1.0 Introduced.
Usage
Information
This command applies to both IPv4 and IPv6 CAM Profiles, but is best used when verifying QoS optimization
for IPv6 ACLs.
QoS Optimization for IPv6 ACLs does not impact the CAM usage for applying a policy on a single (or the first
of several) interfaces. It is most useful when a policy is applied across multiple interfaces; it can reduce the
impact to CAM usage across subsequent interfaces.
The following describes the test cam-usage command shown in the following example.
Term Explanation
Linecard Lists the line cards that are checked. Entering all displays the status for line cards in
the chassis.
Portpipe Lists the port pipes (port sets) that are checked. Entering all displays the status for all
line cards and port pipes in the chassis.
CAM Partition Shows the CAM profile of the CAM.
Available CAM Identifies the amount of CAM space remaining for that profile.
Estimated CAM
per Port
Estimates the amount of CAM space the listed policy will require.
Status Indicates whether or not the policy will be allowed in the CAM.
Example
Dell# test cam-usage service-policy input pcam linecard all
linecard |Portpipe|CAM Partition|Available CAM |Estimated CAM per Port|
Status
-----------------------------------------------------------------------------
0 | 0 | IPv4Flow | 408 | 1 | Allowed (408)
0 | 1 | IPv4Flow | 408 | 1 | Allowed (408)
0 | 2 | IPv4Flow | 408 | 1 | Allowed (408)
1 | 0 | IPv4Flow | 408 | 1 | Allowed (408)
1 | 1 | IPv4Flow | 408 | 1 | Allowed (408)
1 | 2 | IPv4Flow | 408 | 1 | Allowed (408)
1 | 3 | IPv4Flow | 408 | 1 | Allowed (408)
2 | 0 | IPv4Flow | 408 | 1 | Allowed (408)
2 | 1 | IPv4Flow | 408 | 1 | Allowed (408)
2 | 2 | IPv4Flow | 408 | 1 | Allowed (408)
2 | 3 | IPv4Flow | 408 | 1 | Allowed (408)
Unified Forwarding Table Modes
Unified Forwarding Table (UFT) consolidates the resources of several search tables (Layer 2, Layer 3 Hosts, and Layer 3 Route
[Longest Prefix Match — LPM]) into a single flexible resource. Trident 2 supports several UFT modes to extract the forwarding
tables, as required. By default, Dell Networking OS initializes the table sizes to UFT mode 2 profile, since it provides a reasonable
shared memory for all the tables. The other supported UFT modes are scaled-l3–hosts (UFT mode 3) and scaled-l3–routes
(UFT mode 4).
Important Points to Remember
● All line cards/Stack Members within a single system must have the same UFT mode profiles. this profile must match the
system UFT mode profile (the profile on the primary route processor module [RPM]/ Master Unit of the Stack).
Content Addressable Memory (CAM)
509