xStack
config scheduling
|
| combination of strict and |
|
| scheduling. Priority classes that have a 0 in the max_packet field |
|
| will forward packets with strict priority scheduling. The remaining |
|
| classes, that do not have a 0 in their max_packet field, will follow a |
|
| weighted |
|
| long as the priority classes with a 0 in their max_packet field are |
|
| empty. When a packet arrives in a priority class with a 0 in its |
|
| max_packet field, this class will automatically begin forwarding |
|
| packets until it is empty. Once a priority class with a 0 in its |
|
| max_packet field is empty, the remaining priority classes will reset |
|
| the weighted |
|
| starting with the highest available priority class. Priority classes |
|
| with an equal level of priority and equal entries in their |
|
| max_packet field will empty their fields based on hardware priority |
|
| scheduling. |
| Parameters | <class_id |
|
| classes the config scheduling command will be applied. The |
|
| seven priority classes are identified by number − from 0 to 6 − with |
|
| queue 6 being the highest priority. |
|
| max_packet <value |
|
| packets the above specified priority class will be allowed to |
|
| transmit per weighted |
|
| 0 and 15 packets can be specified. A zero (0) denotes strict |
|
| priority scheduling for that priority class. |
| Restrictions | Only |
|
|
|
|
| NOTICE: The default QoS scheduling arrangement is a strict priority |
|
| schedule. To customize scheduling to set up weighted or |
|
| clearing, the max_packets values need to be changed. |
Example usage: |
| |
To configure traffic scheduling:
Command: config scheduling 0 max_packet 15
Success.
Example usage:
To configure a Combination Queue with a Class 6 priority class with strict priority and the remaining classes as weighted round robin (WRR) scheduling:
Command: config scheduling 6 max_packet 0
Success.
106
