Motorola 549478-001-00 User Guide - Page 43

Quality of Service

Page 43 highlights

Quality of Service Once a port has been set to use dynamic or static mode; specify whether T3 will use IP TOS or 802.1P precedence bit for dynamic packet classification. network qos interface queue mode Deprecated commands to set the queuing mechanism on a port. This command is superseded by network qos interface egress which has more configuration options. When using this command, note that WFQ has a fixed percentage for each queue: Critical: High: Medium: Low: strict priority over all other queues 70% of available bitrate 20% of available bitrate 10% of available bitrate In priority mode, strict priority applies to all queues where a higher queue always transmits before a lower queue. Note that when using wfq mode, a low priority queue will use all the available bandwidth if a higher priority queue is not in the transmission buffer. network qos interface egress priority queue Any queue assigned as a Priority queue will transmit using strict priority. A higher level queue will always transmit before a lower level queue. Use priority mode for latency and jitter sensitive applications. network qos interface egress shaping queue peak average burst Set a fixed traffic shaping parameter for each queue. Note that a queue will never exceed the peak rate parameter regardless of other services on the port. Where; Queue: Peak: Average: Burst: the queue where you wish to shape traffic. Valid options are critical, high, medium, or low the maximum rate for the queue, in Mbits/second the average rate for the queue, in Mbits/second the maximum data burst allowed at the peak rate network qos interface egress wfq queue weight Configure the behavior of the WFQ scheduling method. Bitrates are determined as a percentage of the total queue weights. In order to determine the percentage of bandwidth that will be allocated for a particular queue, divide the queue weight by the sum of all the queues "weight". For example; assume the High queue weight is 100 and the Medium queue weight is 50. 100 + 50 = 150. So, the High queue will receive 66% of the bandwidth (100/150=0.667) and the Medium queue will receive 33% of the bandwidth (50/150=0.33). network qos multicast config queue-allocation Multicast packets are allocated a separate set of transmission buffers. Set the multicast queue to be the same queue where the multicast packets will be transmitted. For example, if using video packets with an IP TOS bit, assign the packets to the high queue based on the IP TOS bit, and assign the multicast queue to be also use high. T3 has no way to automatically determine where the multicast packets will be transmitted. network qos wred enable | disable Motorola, Inc. 570510-001-00 rev A Page 43 of 50

  • 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

Quality of Service
Motorola, Inc.
570510-001-00 rev A
Page 43 of 50
Once a port has been set to use dynamic or static mode; specify whether T3 will use IP TOS or 802.1P
precedence bit for dynamic packet classification.
network qos interface queue <interface-id> mode <mode>
Deprecated commands to set the queuing mechanism on a port.
This command is superseded by
network qos
interface egress
which has more configuration options.
When using this command, note that WFQ has a fixed percentage for each queue:
Critical:
strict priority over all other queues
High:
70% of available bitrate
Medium:
20% of available bitrate
Low:
10% of available bitrate
In priority mode, strict priority applies to all queues where a higher queue always transmits before a lower queue.
Note that when using wfq mode, a low priority queue will use all the available bandwidth if a higher priority queue
is not in the transmission buffer.
network qos interface egress priority <interface-id> queue <queue>
Any queue assigned as a Priority queue will transmit using strict priority.
A higher level queue will always transmit
before a lower level queue.
Use priority mode for latency and jitter sensitive applications.
network qos interface egress shaping <interface-id> queue <queue> peak <peak rate> average <avg rate> burst
<burst size>
Set a fixed traffic shaping parameter for each queue.
Note that a queue will never exceed the peak rate
parameter regardless of other services on the port.
Where;
Queue:
the queue where you wish to shape traffic.
Valid options are critical, high, medium, or low
Peak:
the maximum rate for the queue, in Mbits/second
Average:
the average rate for the queue, in Mbits/second
Burst:
the maximum data burst allowed at the peak rate
network qos interface egress wfq <interface-id> queue <queue> weight <0-200>
Configure the behavior of the WFQ scheduling method.
Bitrates are determined as a percentage of the total
queue weights.
In order to determine the percentage of bandwidth that will be allocated for a particular queue, divide the queue
weight by the sum of all the queues “weight”.
For example; assume the
High queue
weight is 100 and the
Medium queue
weight is 50.
100 + 50 = 150.
So,
the High queue will receive 66% of the bandwidth (100/150=0.667) and the Medium queue will receive 33% of the
bandwidth (50/150=0.33).
network qos multicast config queue-allocation <allocation>
Multicast packets are allocated a separate set of transmission buffers.
Set the multicast queue to be the same
queue where the multicast packets will be transmitted.
For example, if using video packets with an IP TOS bit,
assign the packets to the high queue based on the IP TOS bit, and assign the multicast queue to be also use
high.
T3 has no way to automatically determine where the multicast packets will be transmitted.
network qos wred enable | disable