• 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 | 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 them when the threshold value is exceeded. If you configure ECN for WRED, devices employ ECN
to mark the packets and reduce the rate of sending packets in a congested network.
In a best-effort network topology, data packets are transmitted in a manner in which latency or
throughput is not maintained to be at an effective level. Packets are dropped when the network
experiences a large traffic load. This best-effort network deployment is not suitable for applications that
are time-sensitive, such as video on demand (VoD) or voice over IP (VoIP) applications. In such cases, you
can use ECN in conjunction with WRED to resolve the dropping of packets under congested conditions.
Using ECN, the packets are marked for transmission at a later time after the network recovers from the
heavy traffic state to an optimal load. In this manner, enhanced performance and throughput are
achieved. Also, the devices can respond to congestion before a queue overflows and packets are
dropped, enabling improved queue management.
When a packet reaches the device with ECN enabled for WRED, the average queue size is computed. To
measure the average queue size, a weight factor is used. This weight factor is user-configurable. You can
use the
wred weight number
command to configure the weight for the WRED average queue size. The
mark probability value is the number of packets dropped when the average queue size reaches the
maximum threshold value.
The weight factor is set to zero by default, which causes the same behavior as dropping of packets by
WRED during network loads or also called instantaneous ECN marking. In a topology in which congestion
of the network varies over time, you can specify a weight to enable a smooth, seamless averaging of
packets to handle the sudden overload of packets based on the previous time sampling performed. You
can specify the weight parameter for front-end and backplane ports separately in the range of 0 through
15.
812
Quality of Service (QoS)
Содержание S4820T
Страница 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Страница 282: ...Dell 282 Control Plane Policing CoPP ...
Страница 569: ...Figure 62 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 569 ...
Страница 572: ...Figure 64 Inspecting a LAG Port on BRAVO Using the show interface Command 572 Link Aggregation Control Protocol LACP ...
Страница 573: ...Figure 65 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 573 ...
Страница 617: ...mac address table static multicast mac address vlan vlan id output range interface Microsoft Network Load Balancing 617 ...
Страница 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Страница 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Страница 624: ...Figure 83 Configuring PIM in Multiple Routing Domains 624 Multicast Source Discovery Protocol MSDP ...
Страница 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Страница 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Страница 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Страница 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Страница 979: ...6 Member not present 7 Member not present Stacking 979 ...
Страница 981: ...storm control Storm Control 981 ...
Страница 999: ... Te 1 1 0 INCON Root Rootguard Te 1 2 0 LIS Loopguard Te 1 3 0 EDS Shut Bpduguard Spanning Tree Protocol STP 999 ...
Страница 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...