Default buffer pools exist (logically) at the port, FP or MDA, and node levels. Each physical port has three associated pool objects:
Each FP has five associated pool objects:
By default, each pool is associated with slope-policy default, which has the slopes within the pool shutdown.
Slope policies are also applied when WRED is applied per queue and to the associated megapools; see WRED Per Queue.
A basic slope QoS policy must conform to the following:
Configuring and applying slope policies is optional. If no slope policy is explicitly applied to a pool, a default slope policy is applied.
To create a new slope policy, define the following:
Use the following CLI syntax to configure a slope policy:
The following displays the slope policy configuration:
Apply slope policies to the following entities:
The following CLI syntax examples may be used to apply slope policies to port pools:
The following CLI syntax examples may be used to apply slope policies to FP ingress network pools:
For the MC Path Mgmt, the slope policy is configured within a multicast management bandwidth policy that is then applied under the FP ingress multicast-path-management.
The default access ingress and egress policies are identified as policy-id 1. The default policies cannot be edited or deleted. Table 93 lists default policy parameters.
Parameter | Default | |
Description | “Default slope policy” | |
Highplus-slope | ||
shutdown | shutdown | |
start-avg | 85 | |
max-avg | 100 | |
max-prob | 80 | |
High-slope | ||
shutdown | shutdown | |
start-avg | 70 | |
max-avg | 90 | |
max-prob | 80 | |
Low-slope | ||
shutdown | shutdown | |
start-avg | 50 | |
max-avg | 75 | |
max-prob | 80 | |
Exceed-slope | ||
shutdown | shutdown | |
start-avg | 30 | |
max-avg | 55 | |
max-prob | 80 | |
Time-average-factor | 7 | |
The following output displays the default configuration:
This section discusses slope QoS policy service management tasks:
A slope policy is associated by default with XMAs and MDAs and port access and network egress pools. A default policy may be replaced with a non-default policy, but a policy cannot be entirely removed from the configuration. When a non-default policy is removed, the policy association reverts to the default slope policy policy-id default. A QoS policy cannot be deleted until it is removed from all of the places where it is applied.
The following CLI syntax examples can be used to remove slope policies from port pools:
The following CLI syntax examples can be used to remove slope policies from FP pools:
For the MC Path Mgmt, the mcast-pool can be removed from the bandwidth policy or the bandwidth-policy can be removed from under the FP ingress multicast-path-management.
To delete a slope policy, enter the following command:
An existing slope 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 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.