QoS Scheduler Policies
Quality of Service Guide 535
Bandwidth distribution from an egress port scheduler to a VPORT configured with a
scheduler policy can be performed based on the level/cir-level and weight/cir-weight
configured under the scheduler’s port parent. The result is in allowing multiple VPORTs, for
example representing different DSLAMs, to share the port bandwidth capacity in a flexible
way that is under the control of the user.
The configuration of a scheduler policy under a VPORT is mutually exclusive with the
configuration of a port scheduler policy or an aggregate rate limit.
A scheduler policy is configured under a VPORT as follows:
CLI Syntax: config>port>ethernet>access>egress>vport# scheduler-
policy scheduler-policy-name
When using this model, a tier 1 scheduler in a scheduling policy applied to a subscriber profile
or SLA profiles must be configured as follows:
CLI Syntax: config>qos>scheduler-policy>tier# parent-location vport
If the VPORT exists, but the port does not have a port scheduler policy applied, then its
schedulers will be orphaned and no port level QOS control can be enforced.
The following show/clear commands are available related to the VPORT scheduler:
show qos scheduler-hierarchy port port-id vport name
[scheduler scheduler-name] [detail]
show qos scheduler-stats port port-id vport name
[scheduler scheduler-name] [detail]
clear qos scheduler-stats port port-id vport name
[scheduler scheduler-name] [detail]
HQoS adjustment and host tracking are not supported on schedulers that are configured in a
scheduler policy on a VPORT, so the configuration of a scheduler policy under a VPORT is
mutually exclusive with the configuration of the egress-rate-modify parameter.
ESM over MPLS pseudowires are not supported when a scheduler policy is configured on a
VPORT.
To Next Page
Loading...
