Enabling Strict-Priority Queueing
In strict-priority queuing, the system de-queues all packets from the assigned queue before servicing any other queues. You can assign
strict-priority to one unicast queue, using the strict-priority command.
•
Policy-based per-queue rate shaping is not supported on the queue configured for strict-priority queuing. To use queue-based rate-
shaping as well as strict-priority queuing at the same time on a queue, use the Scheduler Strict feature as described in Scheduler
Strict .
•
The
strict-priority
supersedes
bandwidth-percentage
configuration.
•
A queue with strict priority can starve other queues in the same port-pipe.
•
Assign strict priority to one unicast queue.
INTERFACE mode
service-policy output
policy-map-name
Enter the name for the policy map in character format (32 characters maximum).
Weighted Random Early Detection
Weighted random early detection (WRED) is a congestion avoidance mechanism that drops packets to prevent buffering resources from
being consumed.
The WRED congestion avoidance mechanism 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 a few types of traffic, leaving no
space for other types. You can apply a WRED profile to a policy-map so that specified traffic can be prevented from consuming too much
of the BTM resources.
WRED uses a profile to specify minimum and maximum threshold values. The minimum threshold is the allotted buffer space for specified
traffic, for example, 1000KB on egress. If the 1000KB is consumed, packets are dropped randomly at an exponential rate until the maximum
threshold is reached (as shown in the following illustration); this procedure is the “early detection” part of WRED. If the maximum threshold,
for example, 2000KB, is reached, all incoming packets are dropped until the buffer space consumes less than 2000KB of the specified
traffic.
Quality of Service (QoS)
653
Содержание S3048-ON
Страница 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Страница 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Страница 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Страница 241: ...Dell Control Plane Policing CoPP 241 ...
Страница 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Страница 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Страница 429: ...Figure 54 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 429 ...
Страница 432: ...Figure 56 Inspecting a LAG Port on BRAVO Using the show interface Command 432 Link Aggregation Control Protocol LACP ...
Страница 433: ...Figure 57 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 433 ...
Страница 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Страница 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Страница 479: ...Figure 75 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 479 ...
Страница 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Страница 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Страница 634: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 634 Per VLAN Spanning Tree Plus PVST ...
Страница 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Страница 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...