Named Pools QoS Policy Command Reference
742 Quality of Service Guide
Parameters pool-name — The specified pool-name identifies a named pool where the policy will be applied.
Each queue created within the system is tied to a physical port. When the policy is applied
and the queue is created, the system will scan the named pools associated with the port to find
the specified pool name. If the pool is not found on the port, the system will then look at
named pools defined at the ports XMA or MDA level. If the pool name is not found on either
the port, XMA, or MDA, the queue will be marked as ‘pool-orphaned’ and will be mapped to
the appropriate default pool. If the pool comes into existence, the queue will be moved from
the default pool to the new named pool and the ‘pool-orphaned’ state will be cleared. The
specified name must be an ASCII name string up to 32 characters long.
sap-egress
Syntax [no] sap-egress policy-id
Context config>qos
Description This command is used to create or edit a Service Egress QoS policy. The egress policy defines the
Service Level Agreement (SLA) for service packets as they egress on the SAP.
Policies in effect are templates that can be applied to multiple services as long as the scope of the policy
is template. The queues defined in the policy are not instantiated until a policy is applied to a service.
A sap-egress policy differs from sap-ingress policies in the complexity of the QoS parameters that can
be defined. At ingress, policies determine queue mappings based on ingress DSCP, Dot1P and IP or
MAC match criteria. Multiple queues can be created per forwarding class and each queue can have
different CIR or PIR parameters.
At egress, the policies are much simpler, as the forwarding class and in or out of profile determination
happened way back at the original service ingress SAP. Egress SAP QoS policies allow the definition
of queues and the mapping of forwarding classes to those queues. Each queue needs to have a relative
CIR for determining its allocation of QoS resources during periods of congestion. A PIR can also be
defined that forces a hard limit on the packets transmitted through the queue. When the forwarding
class is mapped to the queue, a Dot1p value can optionally be specified. If specified and the SAP has
a Dot1q encapsulation type, the Dot1p value will be used for all packets that egress on that forwarding
class. If the Dot1p value is not specified, a Dot1p value of zero will be used. If the SAP is null
encapsulated, or on a SONET/SDH interface, the Dot1p value has no meaning.
Any unmapped traffic or FC will go to queue 1 (or 11 in case of B/U/M traffic).
The sap-egress policy with policy-id 1 is the default sap-egress QoS policy and is applied to service
egress SAPs when an explicit policy is not specified or removed. The system sap-egress policy can be
modified but not deleted. Using the no sap-egress command on policy-id 1 causes it to revert to its
factory default parameters.
The factory default settings for sap-egress policy-id 1 define a single queue with PIR set to the
maximum value and a CIR set to 25. The single queue is the default queue and all forwarding classes
will map to it. Packets being tagged according to the SAP encapsulation defined will have the Dot1p
bits set to zero.
To Next Page
Loading...
