traffic-class at the policy level

Vyatta NOS handles traffic classes in strict priority order, traffic class 0 being the highest priority, 3 being the lowest.

At the policy level, the traffic-class entity controls the bandwidth and queue limit across all queues of all the profiles of a particular traffic class.

Sub-entities

• WRR queues
• random-detect

The profile queues of the traffic class, at the lowest level of the scheduling hierarchy by default, normally operate as simple FIFO queues. However, you can also configure them to operate as WRED queues.

Note: On software platforms you can set up WRED across all the queues and all the profiles.

Attributes

• bandwidth <limit>
• queue-limit <number>
• queue-limit-bytes <limit>
• queue-limit-time <limit>

The queue-limit attributes define how long the profile queues that belong to a particular traffic class are.

• On software platforms, we express queue-limit as the maximum number of packets that can fit on the queue.
• On hardware platforms, we express queue-limit-bytes as the total number of bytes of memory that packets in the queue can consume.
• We express queue-limit-time as the maximum time that a packet can wait on a queue.

traffic-class at the profile level

You can set up bandwidths on a particular traffic class within the profile.

Control bandwidths across all the queues in that traffic class, within the profile.

Vyatta NOS will schedule eight queues within a traffic class in weighted round robin (WRR) order. You can configure queue weights to provide different bandwidth allocations for each queue within a traffic class.