•
Because this functionality forcibly marks all the packets matching the specific match criteria as ‘yellow’, Dell Networking OS does not
support Policer based coloring and this feature concurrently.
•
If single rate two color policer is configured along with this feature, then by default all packets less than PIR would be considered as
“Green” But ‘Green’ packets matching the specific match criteria for which ‘color-marking’ is configured will be over-written and
marked as “Yellow”.
•
If two rate three color policer is configured along with this feature then,
•
x < CIR – will be marked as “Green”
•
CIR < x< PIR – will be marked as “Yellow”
•
PIR < x – will be marked as “Red”
But ‘Green’ packets matching the specific match criteria for which ‘color-marking’ is configured will be over-written and marked as “Yellow”.
Sample configuration to mark non-ecn packets as “yellow”
with Multiple traffic class
Consider the example where there are no different traffic classes that is all the packets are egressing on the default ‘queue0’.
Dell Networking OS can be configured as below to mark the non-ecn packets as yellow packets.
!
ip access-list standard ecn_0
seq 5 permit any ecn 0
class-map match-any ecn_0_cmap
match ip access-group ecn_0 set-color yellow
!
policy-map-input ecn_0_pmap
service-queue 0 class-map ecn_0_cmap
Applying this policy-map “ecn_0_pmap” will mark all the packets with ‘ecn == 0’ as yellow packets on queue0 (default queue).
Classifying Incoming Packets Using ECN and Color-Marking
Explicit Congestion Notification (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 this functionality of ECN to mark the packets and
reduce the rate of sending packets in a congested, heavily-loaded network.
ECN is a mechanism using which network switches indicate congestion to end hosts for initiating appropriate action. End hosts uses two
least significant bits of ToS to indicate that it is ECT. When intermediate network node encounters congestion, remarks ECT to CE for end
host to take appropriate action. During congestion, ECN enabled packets are not subject to any kind of drops like WRED except tail drops.
Though ECN & WRED are independent technologies, BRCM has made WRED a mandatory for ECN to work.
On ECN deployment, the non-ECN packets that are transmitted on the ECN-WRED enabled interface will be considered as Green packets
and will be subject to the early WRED drops. Typically the TCP-acks, OAM, ICMP ping packets will be non-ECN in nature and it is not
desirable for this packets getting WRED dropped.
In such a condition, it is necessary that the switch is capable to take differentiated actions for ECN/Non-ECN packets. After classifying
packets to ECN/Non-ECN, marking ECN and Non-ECN packets to different color packets is performed.
Policy based ingress QOS involves the following three steps to achieve QOS:
1
Classification of incoming traffic.
2
Specify the differentiated actions for different traffic class.
754
Quality of Service (QoS)
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...