Named Pools QoS Policy Command Reference
738 Quality of Service Guide
The SAP ingress policy with policy-id 1 is a system-defined policy applied to services when no other
policy is explicitly specified. The system SAP ingress policy can be modified but not deleted. The no
sap-ingress command restores the factory default settings when used on policy-id 1. The default SAP
ingress policy defines one queue associated with the best effort (be) forwarding class, with CIR of zero
and PIR of line rate.
Any changes made to the existing policy, using any of the sub-commands are applied immediately to
all services where this policy is applied. For this reason, when many changes are required on a policy,
it is recommended that the policy be copied to a work area policy ID. That work-in-progress policy can
be modified until complete and then written over the original policy-id. Use the config qos copy
command to maintain policies in this manner.
The no sap-ingress policy-id command deletes the SAP ingress policy. A policy cannot be deleted
until it is removed from all services where it is applied. The system default sap-ingress policy is a
special case; the no command restores the factory defaults to policy-id 1.
The no sap-ingress policy-id bw-reserved command removes the bandwidth reservation attribute
from the sap-ingress policy.
Parameters policy-id — The policy-id uniquely identifies the policy.
Values 1 to 65535
queue
Syntax queue queue-id [multipoint] [queue-type] [queue-mode] pool pool-name
queue queue-id [multipoint] [queue-type] pool pool-name
no queue queue-id
Context config>qos>sap-ingress
config>qos>sap-egress
Description This command creates the context to configure an ingress service access point (SAP) QoS policy
queue.
Explicit definition of an ingress queue’s hardware scheduler status is supported. A single ingress queue
allows support for multiple forwarding classes. The default behavior automatically chooses the
expedited or non-expedited nature of the queue based on the forwarding classes mapped to it. As long
as all forwarding classes mapped to the queue are expedited (nc, ef, h1 or h2), the queue is treated as
an expedited queue by the hardware schedulers. When any non-expedited forwarding classes are
mapped to the queue (be, af, l1 or l2), the queue is treated as best effort (be) by the hardware schedulers.
The expedited hardware schedulers are used to enforce expedited access to internal switch fabric
destinations. The hardware status of the queue must be defined at the time of queue creation within the
policy.
To Next Page
Loading...
