Nokia 7705 - 6.2.1 Creating Service Egress and Ingress QoS Policies; 6.2.1.1 Creating a Service Egress QoS Policy

Service Egress and Ingress QoS Policies
260
Quality of Service Guide
3HE 11014 AAAC TQZZA Edition: 01
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:
• Creating a Service Egress QoS Policy
• Creating a Service Ingress QoS Policy
• Creating an MC-MLPPP SAP Egress 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:
• Creating a Service Egress QoS Forwarding Class
• Creating a Service Egress QoS Queue
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:
CLI Syntax: config>qos
sap-egress policy-id
description description-string
policy-name policy-name
queue queue-id [queue-type]
scope {exclusive|template}
Example: *A:ALU-1>configure qos sap-egress 600 create
config>qos>sap-egress$ fc be create
config>qos>sap-egress>fc$ exit
config>qos>sap-egress$ policy-name “sap_egr_87”
config>qos>sap-egress$ queue 2 expedite create
config>qos>sap-egress>queue$ exit
config>qos>sap-egress# scope exclusive