The output of this command, shown in the following example, displays:
• The estimated number of CAM entries the policy-map will consume.
• Whether or not the policy-map can be applied.
• The number of interfaces in a port-pipe to which the policy-map can be applied.
Specifically:
•
Available CAM
— the available number of CAM entries in the specified CAM partition for the specified
line card or stack-unit port-pipe.
•
Estimated CAM
— the estimated number of CAM entries that the policy will consume when it is applied
to an interface.
•
Status
— indicates whether the specified policy-map can be completely applied to an interface in the
port-pipe.
•
Allowed
— indicates that the policy-map can be applied because the estimated number of CAM
entries is less or equal to the available number of CAM entries. The number of interfaces in the
port-pipe to which the policy-map can be applied is given in parentheses.
•
Exception
— indicates that the number of CAM entries required to write the policy-map to the
CAM is greater than the number of available CAM entries, and therefore the policy-map cannot be
applied to an interface in the specified port-pipe.
NOTE:
The
show cam-usage
command provides much of the same information as the
test cam-
usage
command, but whether a policy-map can be successfully applied to an interface cannot be
determined without first measuring how many CAM entries the policy-map would consume; the
test
cam-usage
command is useful because it provides this measurement.
• Verify that there are enough available CAM entries.
test cam-usage
Example of the
test cam-usage
Command
Dell# test cam-usage service-policy input pmap_l2 port-set 0 | port pipe
Port-pipe | CAM Partition | Available CAM | Estimated CAM | Status
=====================================================================
0 L2ACL 500 200 Allowed(2)
Configuring Weights and ECN for
WRED
The WRED congestion avoidance functionality drops packets to prevent buffering resources from being
consumed. Traffic is a mixture of various kinds of packets. The rate at which some types of packets arrive
might be greater than others. In this case, the space on the buffer and traffic manager (BTM) (ingress or
egress) can be consumed by only one or few types of traffic, leaving no space for other types. You can apply
a WRED profile to a policy-map so that the specified traffic can be prevented from consuming too much of
the BTM resources.
WRED drops packets when the average queue length exceeds the configured threshold value to signify
congestion. ECN is a capability that enhances WRED by marking the packets instead of causing WRED to drop
Quality of Service (QoS)
856
Содержание S4048T
Страница 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Страница 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Страница 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Страница 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Страница 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Страница 591: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 591 ...
Страница 594: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 594 ...
Страница 595: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 595 ...
Страница 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Страница 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Страница 648: ...Figure 89 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 648 ...
Страница 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Страница 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Страница 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...
Страница 1179: ...Figure 147 Create Hypervisor Figure 148 Edit Hypervisor Figure 149 Create Transport Connector Virtual Extensible LAN VXLAN 1179 ...