Configuring queue scheduler policies for subinterfaces

To configure queue scheduler policies for subinterfaces, use the qos scheduler-policies scheduler-policy command.
Note: By default for scheduler 0 inputs, the committed rate is set to zero, which causes all traffic to be dropped. You must configure meaningful committed rate values for scheduler 0 inputs to prevent packet loss.

Configure queue scheduler policies for subinterfaces

In the following example, strict priority scheduler 0 has queues expedited and nc as inputs with priority levels and committed rates defined. WRR scheduler 1 has queues af1, af2, and best-effort as inputs with committed rates, peak rates, and weights assigned. Both schedulers have output-type defined as interface with a peak-rate-percent value of 100.

--{ candidate shared default }--[  ]--
# info qos scheduler-policies scheduler-policy subinterface-scheduler-policy
    scheduler 0 {
        priority strict
        input 0 {
            input-type queue
            queue-name expedited
            priority-level 4
            committed-rate-kbps 2000
        }
        input 1 {
            input-type queue
            queue-name nc
            priority-level 5
            committed-rate-kbps 500
        }
    }
    scheduler 1 {
        input 1 {
            input-type queue
            queue-name af1
            weight 30
            committed-rate-kbps 5000
            peak-rate-kbps 10000
        }
        input 2 {
            input-type queue
            queue-name af2
            weight 20
            committed-rate-kbps 4000
            peak-rate-kbps 10000
        }
        input 3 {
            input-type queue
            queue-name best-effort
            weight 1
            peak-rate-kbps 10000
        }
        output {
            output-type interface
            peak-rate-percent 100
        }
    }