Configuring an FQ Profile in Priority-based 8-CoS Mode
You can configure priorities, scheduling parameters, and traffic shaping parameters for FQs based on network requirements.
Context
In HQoS in priority-based 8-CoS mode, eight queues are assigned different priorities in a priority-based FQ profile. The priorities are 0, 1, 2, and 3 in descending order. You can configure traffic shaping parameters and scheduling weights for the queues based on the priorities.
By default, the default priority values of queues are used.
Procedure
- Run system-view
The system view is displayed.
- (Optional) Run flow-wred wred-name
A flow WRED object is created and its view is displayed.
- (Optional) Run color { green | yellow | red } low-limit low-limit-percentage high-limit high-limit-percentage discard-percentage discard-percentage
Upper and lower drop thresholds as well as a drop probability are configured.
- (Optional) Run queue-depth queue-depth-value
A queue depth is configured.
- Run commit
The configuration is committed.
- Run quit
Return to the system view.
- Run flow-queue flow-queue-name [ priority-mode ]
The priority-based FQ view is displayed.
To display the priority-based FQ view, you must specify priority-mode.
- Run priority priority-value { pq | wfq }
The scheduling mode of priority-based FQs on the same scheduler is set to PQ or WFQ.
- Run queue cos-value { priority priority-value [ weight weight-value ] | { shaping { shaping-value | shaping-percentage shaping-percentage-value } } | flow-wred wred-name } *
The priority, weight, and shaping value of the FQ are changed, and a flow WRED profile is bound.
- Run share-shaping [ shap-id ] { af1 | af2 | af3 | af4 | be | cs6 | cs7 | ef } * [ pq | wfq weight weight-value | lpq ] shaping-value [ pbs pbs-value ]
Share shaping is configured for multiple FQs.
After queues configured with share shaping are shaped, the queues are scheduled together with other user queues. In the priority-based FQ view, if no scheduling mode is specified for share shaping, share shaping uses the same scheduling mode as sub-schedulers.