The adv-config-policy contains queue and policer configuration parameters that are not expected to be useful to most users. The policy only contains queue and policer child control parameters within a child-control node.
The parameters within the child-control node are intended to allow more precise control of the method that hierarchical virtual scheduling employs to emulate the effect of a scheduling context upon a member child queue or policer.
When a policy is created, it may be applied to a queue or policer defined within a sap-egress or sap-ingress QoS policy. It may also be applied to a queue or policer defined within an ingress or egress queue-group template. When a policy is currently associated with a QoS policy or template, the policy may be modified but not deleted (even in the event that the QoS policy or template is not in use).
While the system maintains default values for the advanced configuration parameters, no default adv-config-policy exists.
For information about the tasks and commands necessary to access the CLI and to configure and maintain the router, refer to the Entering CLI Commands chapter in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide.
When the H-QoS algorithm within a port scheduler policy is configured to above-offered-allowance-control, it is possible to tune the distribution of unconsumed bandwidth for parented queues. This is achieved by applying an advanced configuration policy to the queue and configuring the following:
When above-offered-allowance-control is enabled, both queues and schedulers use the default values. Table 20 lists the default values for the percentages.
delta-consumed-agg-rate percent | 20 |
delta-consumed-higher-tier-rate percent | 5 |
unconsumed-agg-rate percent | 100 |
unconsumed-higher-tier-rate percent | 100 |
The percentage values can be tuned for parented queues by applying an advanced configuration policy to the queue with modified percent values.
See H-QoS Algorithm Selection, for information about the use of the parameters with the above-offered-allowance-control H-QoS algorithm.
An advanced QoS policy must conform to the following:
Configuring and applying advanced policies is optional. If no advanced policy is explicitly applied to a SAP or IP interface, then no default advanced policy is applied.
To create a new advanced policy, define the following:
The following displays an example of an advanced policy configuration:
Apply advanced policies to the following entities.
Use the following CLI syntax to apply advanced policies to ingress queue groups.
Use the following CLI syntax to apply advanced policies to egress queue groups.
Use the following CLI syntax to apply advanced policies to an ingress SAP.
Use the following CLI syntax to apply advanced policies to an egress SAP.
The default policies cannot be edited or deleted. Table 21 lists default advanced policy parameters.
Field | Default | |
offered-measurement | ||
high-rate-hold-time | 0 | |
time-average-factor | 0 | |
sample-interval | 1 | |
This section discusses advanced QoS policy service management tasks.
Delete advanced policies from the following entities.
Use the following CLI syntax to delete advanced policies from ingress queue groups.
Use the following CLI syntax to delete advanced policies from egress queue groups.
Use the following CLI syntax to delete advanced policies from an ingress SAP.
Use the following CLI syntax to delete advanced policies from an egress SAP.
An existing advanced policy can be copied, renamed with a new policy ID value, or used to overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.
Existing advanced policies and entries in the CLI or NMS can be edited. The changes are applied immediately to all services where this policy is applied. To prevent configuration errors, copy the policy to a work area, make the edits, then write over the original policy.