HP StorageWorks 8/80 Brocade Converged Enhanced Ethernet Administrator's Guide - Page 126

Congestion control, Tail drop

Page 126 highlights

9 Congestion control switch(conf-if-te-0/2)#exit switch(config)#end switch# 4. Enter the copy command to save the running-config file to the startup-config file. switch#copy running-config startup-config Verifying a mapping CoS-to-Traffic-Class Perform the following steps from Privileged EXEC mode to verify a CoS-to-Traffic-Class mapping. 1. Enter global configuration mode. switch#configure terminal 2. Verify the CoS-Traffic-Class mapping specifying a name and the mapping. switch(config)#show qos map cos-traffic-class test Congestion control Queues can begin filling up due to a number of reasons, such as over subscription of a link or backpressure from a downstream device. Sustained, large queue buildups generally indicate congestion in the network and can affect application performance through increased queueing delays and frame loss. Congestion control covers features that define how the system responds when congestion occurs or active measures taken to prevent the network from entering a congested state. Tail drop Tail drop queueing is the most basic form of congestion control. Frames are queued in FIFO order and queue buildup can continue until all buffer memory is exhausted. This is the default behavior when no additional QoS has been configured. The basic tail drop algorithm does not have any knowledge of multiple priorities and per traffic class drop thresholds can be associated with a queue to address this. When the queue depth breaches a threshold, then any frame arriving with the associated priority value will be dropped. Figure 13 shows how you can utilize this feature to ensure that lower priority traffic cannot totally 106 Converged Enhanced Ethernet Administrator's Guide 53-1001346-01

  • 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
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162

106
Converged Enhanced Ethernet Administrator’s Guide
53-1001346-01
Congestion control
9
switch(conf-if-te-0/2)#
exit
switch(config)#end
switch#
4.
Enter the copy command to save the running-config file to the startup-config file.
switch#
copy running-config startup-config
Verifying a mapping CoS-to-Traffic-Class
Perform the following steps from Privileged EXEC mode to verify a CoS-to-Traffic-Class mapping.
1.
Enter global configuration mode.
switch#
configure terminal
2.
Verify the CoS-Traffic-Class mapping specifying a name and the mapping.
switch(config)#
show qos map cos-traffic-class test
Congestion control
Queues can begin filling up due to a number of reasons, such as over subscription of a link or
backpressure from a downstream device. Sustained, large queue buildups generally indicate
congestion in the network and can affect application performance through increased queueing
delays and frame loss.
Congestion control covers features that define how the system responds when congestion occurs
or active measures taken to prevent the network from entering a congested state.
Tail drop
Tail drop queueing is the most basic form of congestion control. Frames are queued in FIFO order
and queue buildup can continue until all buffer memory is exhausted. This is the default behavior
when no additional QoS has been configured.
The basic tail drop algorithm does not have any knowledge of multiple priorities and per traffic
class drop thresholds can be associated with a queue to address this. When the queue depth
breaches a threshold, then any frame arriving with the associated priority value will be dropped.
Figure 13
shows how you can utilize this feature to ensure that lower priority traffic cannot totally