6. Service Egress and Ingress QoS Policies
This chapter provides information to configure service egress and ingress QoS policies using the command line interface.
Topics in this chapter include:
6.1. Overview
There is one default policy for service ingress and one default policy for service egress and MC-MLPPP SAP egress. Each policy can have up to eight ingress queues and eight egress queues per service. The default policies can be copied and modified but they cannot be deleted. The default policies are identified as policy ID 1.
 | Note: Throughout this guide, the terms service ingress/egress and access ingress/egress are interchangeable. This section (Service Egress and Ingress QoS Policies) uses the term service ingress/egress. |
The eight ingress queues can be designated as a unicast, broadcast, multicast, or unknown queue for the purposes of FC-to-queue mapping.
The default policies are applied to the appropriate interface, by default. For example, the default service ingress policy is applied to access ingress SAPs. The default service egress policy is applied to access egress SAPs and MC-MLPPP egress SAPs. You must explicitly associate other QoS policies.
For information about the tasks and commands necessary to access the command line interface and to configure and maintain the 7705 SAR, refer to the 7705 SAR Basic System Configuration Guide, “CLI Usage”.
6.2. Basic Configuration
This section contains the following topics related to creating and applying service ingress and service egress QoS policies:
A basic service egress QoS policy must conform to the following:
- have a unique service egress QoS policy ID
- have a QoS policy scope of template or exclusive
- have at least one defined default queue
A basic service ingress QoS policy must conform to the following:
- have a unique service ingress QoS policy ID
- have a QoS policy scope of template or exclusive
- have at least one default unicast forwarding class queue
6.2.1. Creating Service Egress and Ingress QoS Policies
Configuring and applying QoS policies is optional. If no QoS policy is explicitly applied to a SAP or IP interface, a default QoS policy is applied. Perform the following to configure a QoS policy:
6.2.1.1. Creating a Service Egress QoS Policy
After the policy is created, the policy’s behavior can be defined. In addition, the behavior of policy’s FC and queue can be changed from their default settings:
Define the following attributes to create a service egress policy:
- a unique policy ID value — the system does not dynamically assign a value. Optionally, a policy name can be configured after the policy has been created.
- a default queue for the service egress policy
- the scope — the service egress policy must be defined as having either an exclusive scope for one-time use or a template scope that enables its use with multiple SAPs
Use the following CLI syntax to create a service egress QoS policy:
The following output displays the service egress policy 600 configuration:
6.2.1.1.1. Creating a Service Egress QoS Forwarding Class
Define the following attributes to create a service egress forwarding class:
- the egress dot1p priority bits value
- the DSCP name and DSCP priority bits mapping
Optionally, you can enter a queue-id value to override the default forwarding class-to-queue mapping for the egress policy. The queue must exist before it can be associated with an FC.
Use the following CLI syntax to create a service egress forwarding class:
The following output displays the forwarding class configuration for service egress policy 600:
6.2.1.1.2. Creating a Service Egress QoS Queue
Define the following attributes to create a service egress queue:
- adaptation-rule —the method used by the system to derive the PIR and CIR for the queue
- cbs — overrides the reserved buffers default for the queue
- high-prio-only — the percentage of buffer space for the queue to be used exclusively by in-profile packets
- mbs — the maximum number of buffers allowed for a specific queue
- rate — the PIR and CIR values for the queue
- slope-policy — the slope policy for the queue
Use the following CLI syntax to configure the service egress QoS queue parameters:
The following output displays the queue configuration for service egress policy 500:
6.2.1.2. Creating a Service Ingress QoS Policy
After the policy is created, the policy’s behavior can be defined. In addition, the behavior of policy’s FC and queue can be changed from their default settings:
To create an service ingress policy, define the following:
- a policy ID value — the system does not dynamically assign a value. Optionally, a policy name can be configured after the policy has been created.
- a description — provides a brief overview of policy features
- a default forwarding class for the policy — all packets received on an ingress SAP using this ingress QoS policy will be classified to the default forwarding class
- a default priority for all packets received on an ingress SAP using this policy
- the dot1p parameters — this configuration creates a mapping between the dot1p bits of the ingress traffic and the forwarding class
- the DSCP parameters — this configuration creates a mapping between the DSCP of the ingress traffic and the forwarding class
- the forwarding class parameters — overrides the default forwarding class for the policy by assigning the forwarding class to one or more of the following queue designations: broadcast-queue, multicast-queue, unknown-queue, or (unicast) queue (see Creating a Service Ingress Forwarding Class)
A service ingress policy is created with a template scope. The scope can be modified to exclusive for a special one-time use policy. Otherwise, the template scope enables the policy to be applied to multiple SAPs.
Use the following CLI syntax to create a service ingress QoS policy:
The following output displays the configuration for service ingress policy 100:
6.2.1.2.1. Creating a Service Ingress Forwarding Class
Use the following syntax to define a service ingress forwarding class that overrides the default forwarding type that is defined by the default-fc command. The queue must exist before it can be associated with an FC.
The following output displays the forwarding class override value configuration for service ingress policy 100:
6.2.1.2.2. Creating a Service Ingress QoS Queue
To create service ingress queue parameters, define the following:
- a new queue ID value — the system does not dynamically assign a value
- the queue parameters — ingress queues support explicit and auto-expedite hardware queue scheduling as well as a configurable queue mode
Use the following CLI syntax to configure SAP ingress QoS queue parameters:
The following output displays the queue configuration for service ingress policy 100:
6.2.1.3. Creating an MC-MLPPP SAP Egress QoS Policy
After the policy is created (syntax below), the policy’s FC and queue behavior can be defined:
Define the following attributes to create an MC-MLPPP SAP egress policy:
- a unique policy ID value — the system does not dynamically assign a value. Optionally, a policy name can be configured after the policy has been created.
- a default queue for the MC-MLPPP SAP egress policy
Use the following CLI syntax to create an MC-MLPPP SAP egress QoS policy:
The following output displays the MC-MLPPP SAP egress policy 300 configuration:
6.2.1.3.1. Creating an MC-MLPPP SAP Egress QoS Forwarding Class
Define the following attributes to create an MC-MLPPP SAP egress forwarding class:
- the DSCP name and DSCP priority bits mapping
Optionally, you can enter a queue-id value to override the default forwarding class-to-queue mapping for the egress policy. The queue must exist before it can be associated with an FC.
Use the following CLI syntax to create an MC-MLPPP SAP egress forwarding class:
The following output displays the forwarding class configuration for MC-MLPPP SAP egress policy 300:
6.2.1.3.2. Creating an MC-MLPPP SAP Egress QoS Queue
Define the following attributes to create an MC-MLPPP SAP egress queue:
- adaptation-rule — the method used by the system to derive the PIR for the queue
- cbs — overrides the reserved buffers default for the queue
- high-prio-only — the percentage of buffer space for the queue to be used exclusively by in-profile packets
- mbs — the maximum amount of buffer space allowed for a specific queue
- rate — the PIR value for the queue
- slope-policy — the slope policy for the queue
Use the following CLI syntax to configure the MC-MLPPP SAP egress QoS queue parameters:
The following output displays the queue configuration for MC-MLPPP SAP egress policy 300:
6.2.2. Applying Service Egress and Ingress Policies
Apply service egress and ingress policies to the following service SAPs:
- VLL services
- Epipe
- Cpipe
- Apipe
- Apipe SAPs that are members of a VCC SAP aggregation group
- Fpipe
- Hpipe
- Ipipe
- VPLS
- IES
- VPRN
Refer to the 7705 SAR Services Guide, “Service Overview”, for information about configuring service parameters.
6.2.2.1. VLL and VPLS Services
Applying QoS policies is done in the same way for service ingress and service egress VPLS and VLL SAPs. The following example shows how to apply QoS policies to Epipe SAPs. Use the policy ID number or name to identify the policy.
The following output displays an Epipe service configuration with service ingress policy 100 and service egress policy 105 applied to the SAP.
6.2.2.2. IES and VPRN Services
Applying QoS policies is done in the same way for service ingress and service egress IES and VPRN SAPs. The following example shows how to apply QoS policies to IES SAPs. Use the policy ID number or name to identify the policy.
The output examples for IES and VPRN services are similar to the example given previously for an Epipe service configuration.
6.2.3. Default Service Egress and Ingress Policy Values
The default service egress and ingress policies are identified as policy-id 1 and have the default policy name “default”. The default policies cannot be edited or deleted. The following sections display default policy parameters:
6.2.3.1. Service Egress Policy Defaults
The following output shows the service egress policy defaults.
Table 44 lists the service egress policy defaults.
Table 44: Service Egress Policy Defaults
Field | Default |
policy-name | “default” |
description | Default SAP egress QoS policy |
scope | template |
queue | id = 1, type = auto-expedite |
adaptation-rule | pir = closest, cir = closest |
rate | pir = max, cir = 0 |
cbs | default (8 kbytes for 512 byte buffer size, 18 kbytes for 2304 byte buffer size) |
mbs | default (180 kbytes) |
high-prio-only | default (10%) |
slope-policy | default |
6.2.3.2. Service Ingress Policy Defaults
The following output shows the service ingress policy defaults.
Table 45 lists the service ingress policy defaults.
Table 45: Service Ingress Policy Defaults
Field | Default |
policy-name | “default” |
description | Default SAP ingress QoS policy |
scope | template |
queue | id = 1, mode = priority-mode, type = auto-expedite |
adaptation-rule | pir = closest, cir = closest |
rate | pir = max, cir = 0 |
cbs | default (8 kbytes for 512 byte buffer size, 18 kbytes for 2304 byte buffer size) |
mbs | default (180 kbytes) |
high-prio-only | default (10%) |
slope-policy | default |
default-fc | be |
default-priority | low |
6.3. Service Management Tasks
This section describes the following service management tasks:
6.3.1. Deleting QoS Policies
Every service SAP is associated, by default, with the appropriate service egress or ingress policy (policy-id 1). You can replace the default policy with a customer-configured policy, but you cannot entirely remove the policy from the SAP configuration. When you remove a non-default service egress or ingress policy, the association reverts to the default policy-id 1.
A QoS policy cannot be deleted until it is removed from all SAPs where it is applied.
6.3.1.1. Removing a QoS Policy from a Service SAP
Use the following syntax to remove a QoS policy from an Epipe service SAP. The syntax for Apipe, Cpipe, Fpipe, Hpipe, and Ipipe service SAPs is similar.
The following Epipe service output shows that the SAP service egress and ingress reverted to policy-id “1” when the non-default policies were removed from the configuration.
6.3.1.2. Removing a Policy from the QoS Configuration
Use the following syntax to remove a QoS policy:
6.3.2. Copying and Overwriting QoS Policies
You can copy an existing service egress or ingress 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.
Use the following syntax to overwrite an existing QoS policy ID:
The following output displays the copied policies:
6.3.3. Editing QoS Policies
You can change existing QoS policies and entries in the CLI. 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.