HP 6125XLG R2306-HP 6125XLG Blade Switch ACL and QoS Configuration Guide - Page 59

ECN, Configuring and applying a WRED table

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 59 highlights

ECN By dropping packets, WRED alleviates the influence of congestion on the network. However, the network resources for transmitting packets from the sender to the device which drops the packets are wasted. When congestion occurs, it is a better idea to inform the sender of the congestion status and have the sender proactively slow down the packet sending rate or decrease the window size of packets. This better utilizes the network resources. RFC 2482 defined an end-to-end congestion notification mechanism named Explicit Congestion Notification (ECN). ECN uses the DS field in the IP header to mark the congestion status along the packet transmission path. A ECN-capable terminal can determine whether congestion occurs on the transmission path according to the packet contents, and then adjusts the packet sending speed to avoid deteriorating congestion. ECN defines the last 2 bits (ECN field) in the DS field of the IP header as follows: • Bit 6 indicates whether the sending terminal device supports ECN, and is called the "ECN-Capable Transport (ECT)" bit. • Bit 7 indicates whether the packet has experienced congestion along the transmission path, and is called the "Congestion Experienced (CE)" bit. For more information about the DS field, see "Appendix." In actual applications, the packets with ECT set to 1 and CE set to 0 and the packets with ECT set to 0 and CE set to 1 are considered as packets that an ECN-capable endpoint transmits. After you enable ECN on a device, congestion management processes packets as follows: • When the average queue size is below the lower threshold, no packet is dropped, and the ECN fields of packets are not identified or marked. • When the average queue size exceeds the lower threshold and is below the upper threshold, before the device drops a packet which should be dropped according to the drop probability, the device examines the ECN field of the packet. { If the ECN field shows that the packet is sent out of ECN-capable terminal, the device sets both the ECT bit and the CE bit to 1 and forwards the packet. { If the ECN field shows that the packet has experienced congestion along the transmission path (both the ECT bit and the CE bit are 1), the device forwards the packet without modifying the ECN field. { If both the ECT bit and the CE bit is 0, the device drops the packet. • When the average queue size exceeds the upper threshold, the device drops the packet, no matter whether the packet is sent out of an ECN-capable terminal. ECN is enabled on a per-queue basis. That is, you can configure the switch to identify and mark the ECN fields of packets for a specific queue. Configuring and applying a WRED table The switch supports the queue-based WRED table. That is, you can configure separate drop parameters for different queues. When congestion occurs, packets of a queue are randomly dropped based on drop parameters of the queue. Determine the following parameters before configuring WRED: 53

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
53
ECN
By dropping packets, WRED alleviates the influence of congestion on the network. However, the network
resources for transmitting packets from the sender to the device which drops the packets are wasted.
When congestion occurs, it is a better idea to inform the sender of the congestion status and have the
sender proactively slow down the packet sending rate or decrease the window size of packets. This better
utilizes the network resources.
RFC 2482 defined an end-to-end congestion notification mechanism named Explicit Congestion
Notification (ECN). ECN uses the DS field in the IP header to mark the congestion status along the packet
transmission path. A ECN-capable terminal can determine whether congestion occurs on the
transmission path according to the packet contents, and then adjusts the packet sending speed to avoid
deteriorating congestion. ECN defines the last 2 bits (ECN field) in the DS field of the IP header as
follows:
•
Bit 6 indicates whether the sending terminal device supports ECN, and is called the "ECN-Capable
Transport (ECT)" bit.
•
Bit 7 indicates whether the packet has experienced congestion along the transmission path, and is
called the "Congestion Experienced (CE)" bit.
For more information about the DS field, see "
Appendix
."
In actual applications, the packets with ECT set to 1 and CE set to 0 and the packets with ECT set to 0
and CE set to 1 are considered as packets that an ECN-capable endpoint transmits.
After you enable ECN on a device, congestion management processes packets as follows:
•
When the average queue size is below the lower threshold, no packet is dropped, and the ECN
fields of packets are not identified or marked.
•
When the average queue size exceeds the lower threshold and is below the upper threshold, before
the device drops a packet which should be dropped according to the drop probability, the device
examines the ECN field of the packet.
{
If the ECN field shows that the packet is sent out of ECN-capable terminal, the device sets both
the ECT bit and the CE bit to 1 and forwards the packet.
{
If the ECN field shows that the packet has experienced congestion along the transmission path
(both the ECT bit and the CE bit are 1), the device forwards the packet without modifying the
ECN field.
{
If both the ECT bit and the CE bit is 0, the device drops the packet.
•
When the average queue size exceeds the upper threshold, the device drops the packet, no matter
whether the packet is sent out of an ECN-capable terminal.
ECN is enabled on a per-queue basis. That is, you can configure the switch to identify and mark the ECN
fields of packets for a specific queue.
Configuring and applying a WRED table
The switch supports the queue-based WRED table. That is, you can configure separate drop parameters
for different queues. When congestion occurs, packets of a queue are randomly dropped based on drop
parameters of the queue.
Determine the following parameters before configuring WRED: