CHAPTER 10. QoS
208
© SAMSUNG Electronics Co., Ltd.
Minth is given a default value of N packets, where N corresponds to ¼ of
maximum of(3 * Ts) msec of buffering(at 100 byte packets) at a rate of
interface bandwidth or 20.(For larger packets, this will result in larger amount
of buffering). This means that, if a interface is receiving not more than it’s
bandwidth, on an average at least ¼xTs msec of traffic will be buffered before
RED starts dropping. Note that these buffering requirements are calculated for
100 byte packets which are conservative. The average internet packet size is
probably between 100-200 bytes, for which the buffering would be up to twice
the amount mentioned above. The minimum permissible value for minth is L,
where L corresponds to ¼xTs msec of buffering(for 100 byte packets) at rate
of interface bandwidth or L = 5, whichever is lower.
Maxth is given a default value of N packets, where N corresponds to ¾ of
maximum of(3 * Ts) msec of buffering(at 100 byte packets) at a rate of
interface bandwidth or 20. However it is recommended to set maxth to at least
2 times the minth. Too small a difference between minth and maxth will reduce
the effectiveness of RED by causing frequent tail drops. The maximum permissible
value for maxth is H, where H corresponds to(3*Ts) msec of buffering(for 100 byte
packets) at the rate interface bandwidth or 20, whichever is higher.
Class Queue RED parameters
The EWF and MPD parameters considerations are same as described in the
section Interface RED parameters.
The minth and maxth, are the configured minimum and maximum thresholds
respectively, represents packet queue depth levels at which RED algorithm
changes its course of action, i.e. no-drop, probabilistic-drop, and tail-drop,
depending on whether the average queue size is below minimum threshold, in
between minimum and maximum thresholds, and at or above maximum
threshold respectively.
Minth is given a default value of N packets, where N corresponds to 2xTs
msec of buffering, for 200 byte packets, at a rate of CR Kbps or Ts msec of
buffering at BR Kbps or N = 5, whichever is greater.(For larger packets, this
will result in larger amount of buffering). This means that, if a class is
receiving not more than it’s CR, on an average at least(2*Ts) msec of traffic
will be buffered before RED starts dropping. Note that these buffering
requirements are calculated for 200 byte packets which are conservative.
Summary of Contents for Ubigate iBG2016
Page 1: ......
Page 16: ...INTRODUCTION XIV SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 34: ......
Page 62: ...CHAPTER 4 System Logging 28 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 70: ......
Page 108: ......
Page 140: ...CHAPTER 4 RIP 104 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 156: ...CHAPTER 6 BGP 120 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 180: ...CHAPTER 8 VRRP 144 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 264: ...CHAPTER 10 QoS 228 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 272: ......
Page 298: ...CHAPTER 3 Firewall NAT 248 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 356: ...CHAPTER 5 IPSEC 306 SAMSUNG Electronics Co Ltd This page is intentionally left blank ...
Page 358: ......
Page 744: ...EQBD 000071 Ed 00 ...