Service Egress and Ingress QoS Policies
Quality of Service Guide 233
overwrite — Specifies to replace the existing destination policy. Everything in the existing
destination policy will be overwritten with the contents of the source policy. If overwrite is
not specified, an error will occur if the destination policy ID exists.
SR>config>qos# copy sap-egress 1 1010
MINOR: CLI Destination "1010" exists use {overwrite}.
SR>config>qos# copy sap-egress 1 1010 overwrite
Service Ingress QoS Policy Commands
sap-ingress
Syntax [no] sap-ingress {policy-id | policy-name}
Context config>qos
Description This command is used to create or edit the ingress policy. The ingress policy defines the Service Level
Agreement (SLA) enforcement service packets receive as they ingress a SAP. SLA enforcement is
accomplished through the definition of queues that have Forwarding Class (FC), Committed
Information Rate (CIR), Peak Information Rate (PIR), Committed Burst Size (CBS), and Maximum
Burst Size (MBS) characteristics. The simplest policy defines a single queue that all ingress traffic
flows through. Complex policies have multiple queues combined with specific IP or MAC match
criteria that indicate which queue a packet will flow though.
Policies in effect are templates that can be applied to multiple services as long as the scope of the policy
is template. Queues defined in the policy are not instantiated until a policy is applied to a service SAP.
A SAP ingress policy is considered incomplete if it does not include definition of at least one queue
and does not specify the default action. The OS does not allow incomplete SAP ingress policies to be
applied to services.
SAP ingress policies can be defined with either IP headers as the match criteria or MAC headers as the
match criteria. The IP and MAC criteria are mutually exclusive and cannot be part of the same SAP
ingress policy.
It is possible that a SAP ingress policy will include the dscp map command, the dot1p map command
and an IP or MAC match criteria. When multiple matches occur for the traffic, the order of precedence
will be used to arrive at the final action. The order of precedence is as follows:
1. 802.1p bits
2. DSCP
3. IP Quintuple or MAC headers
To Next Page
Loading...
