
xStack
Example usage:
To display the current 802.1p default priority configuration on the Switch:
Command: show 802.1p default_priority
Port | Priority |
1:1 | 0 |
1:2 | 0 |
1:3 | 0 |
1:4 | 0 |
1:5 | 0 |
1:6 | 0 |
1:7 | 0 |
1:8 | 0 |
1:9 | 0 |
1:10 | 0 |
1:11 | 0 |
1:12 | 0 |
1:13 | 0 |
1:14 | 0 |
1:15 | 0 |
1:16 | 0 |
1:17 | 0 |
1:18 | 0 |
1:19 | 0 |
1:20 | 0 |
1:21 | 0 |
1:22 | 0 |
1:23 | 0 |
1:24 | 0 |
config scheduling_mechanism
Purpose | Used to configure the scheduling mechanism for the QoS function |
Syntax | config scheduling mechanism [strict weight_fair] |
Description | The config scheduling_mechanism command allows the user to |
| select between a Weight Fair (WRR) and a Strict mechanism for |
| emptying the priority classes of service of the QoS function. The |
| Switch contains seven hardware priority classes of service. |
| Incoming packets must be mapped to one of these seven |
| hardware priority classes of service. This command is used to |
| specify the rotation by which these seven hardware priority classes |
| of service are emptied. |
| The Switch’s default is to empty the seven priority classes of |
| service in order − from the highest priority class of service (queue |
| 6) to the lowest priority class of service (queue 0). Each queue will |
| transmit all of the packets in its buffer before allowing the next |
| lower priority class of service to transmit its packets. Lower classes |
| of service will be |
| received on a higher class of service. The packet that was |
| received on the higher class of service will transmit its packet |
| before allowing the lower class to resume clearing its queue. |
110