This chapter provides information to configure slope QoS policies using the command line interface.
For an overview of buffer pools supported on the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, see Buffer Pools.
On the 7210 SAS-K 2F1C2T, slope policies are applied to service ingress queues, service egress queues, access-uplink port ingress queues, and access-uplink port egress queues.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, slope policies are applied to service ingress and egress queues; network port ingress and egress queues; hybrid port ingress and egress queues; and access-uplink port ingress and egress queues.
Each of these queuing points allocates buffers from the buffer pool and implements WRED for congestion management. During congestion WRED is used to evaluate how buffers from the pool are allocated to different FCs and to in-profile and out-of-profile traffic within a given FC. The slope policies define the WRED parameters to use for in-profile/high-priority packets and for out-of-profile/low-priority packets. The high-slope and low-slope define the parameters for in-profile/high-priority packets and for out-of-profile/low-priority packets respectively. In addition, on ring ports the option is available to use separate slopes for ring traffic (that is, traffic coming in on one ring port and going out of another ring port) and non-ring traffic (that is, traffic coming in on access port and going out of another access port or access-uplink port). For more information about ring and non-ring ports, see Buffer Pools.
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 port, a default slope policy is applied.
To create a new slope policy, define the following:
Use the following syntax to configure a slope policy.
The following is a sample default slope policy configuration output, and Table 46 lists the default values.
Description | Default Slope Policy |
high-slope | |
Administrative state | shutdown |
start-avg | 70% utilization |
max-avg | 90% utilization |
max-prob | 80% |
low slope | |
Administrative state | shutdown |
start-threshold | 50% utilization |
max-avg | 75% utilization |
max-prob | 80% |
high-slope-ring | |
Administrative state | shutdown |
start-threshold | 70% utilization |
max-avg | 90% utilization |
max-prob | 80% |
low-slope-ring | |
Administrative state | shutdown |
start-threshold | 50% utilization |
max-avg | 75% utilization |
max-prob | 80% |
On the 7210 SAS-K 2F1C2T, slope policies are associated with service ingress queues, service egress queues, access-uplink port egress queues, and access-uplink port ingress queues.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, slope policies are associated with service ingress and egress queues; network port ingress and egress queues; hybrid port ingress and egress queues; and access-uplink port ingress and egress queues.
The following syntax examples may be used to apply slope policies to service ingress queues, service egress queues, access-uplink port ingress queues, and access-uplink port egress queues on the 7210 SAS-K 2F1C2T.
The following syntax examples may be used to apply slope policies to service ingress and egress queues; network port ingress and egress queues; hybrid port ingress and egress queues; and access-uplink port ingress and egress queues on the 7210 SAS-K 2F6C4T or 7210 SAS-K 3SFP+ 8C.
A slope policy is associated by default with access and access uplink 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. A QoS policy cannot be deleted until it is removed from all ports where it is applied or if the policies are using the slope policy.
The following syntax removes slope policies from ports.
The following shows the command usage to delete a slope policy.
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 is a sample output of 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.