This section provides information to configure slope QoS policies using the command line interface.
Topics in this section include:
Default buffer pools exist (logically) at the port, FP or MDA and node levels. Each physical port has three associated pool objects:
Each MDA on FP1 hardware has four associated pool objects:
Each FP on FP2 or higher based hardware 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 MDA pools:
For the MC Path Mgmt, the slope policy is configured within a multicast management bandwidth policy which is then applied under the MDA ingress multicast-path-management.
The following CLI syntax example configures the PPP multilink pool:
The following CLI syntax examples may be used to apply slope policies to FP pools:
Although these commands are applied under the MDA CLI tree, the policy is applied to the FP. If different policies are applied to each MDA, the last policy applied take precedence.For the MC Path Mgmt, the slope policy is configured within a multicast management bandwidth policy which 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. The following displays default policy parameters:
Field | Default | |
description | “Default slope policy” | |
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:
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 MDAs:
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 MDA ingress multicast-path-management.
The following CLI syntax example configures the PPP multilink pool:
The following CLI syntax examples can be used to remove slope policies from FP pools:
Although some commands are applied under the MDA CLI tree, the policy is applied to the FP. If different policies are applied to each MDA, the last policy applied take precedence.
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:
You can copy an existing slope policy, rename it with a new policy ID value, or overwrite an existing policy ID. The overwrite option must be specified or an error occurs if the destination policy ID exists.
The following output displays the copied policies:
You can change existing policies and entries in the CLI or NMS. 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, and then write over the original policy.