EasyManua.ls Logo

Nokia 7705 - Page 292

Nokia 7705
534 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Service Egress and Ingress QoS Policies
292
Quality of Service Guide
3HE 11014 AAAC TQZZA Edition: 01
Parameters add bytesafter automatic adjustment for internal headers (for example, added FCS or
removal of internal service/overhead), adds the specified number of bytes to each
packet associated with the queue for scheduling and accounting purposes. From the
queue’s perspective, the packet size is increased by the amount being added to each
packet.
Values 2 to 62, in steps of 2
subtract bytesafter automatic adjustment for internal headers (for example, added
FCS or removal of internal service/overhead), subtracts the specified number of
bytes from each packet associated with the queue for scheduling and accounting
purposes. From the queue’s perspective, the packet size is reduced by the amount
being subtracted from each packet.
Values 2 to 62, in steps of 2
none — the packet size is left unchanged
policy-name
Syntax policy-name policy-name
no policy-name
Context config>qos>sap-egress
Description This command configures a policy name for the SAP egress policy.
Parameters policy-name — specifies the name for the policy, up to 64 characters
queue
Syntax queue queue-id [queue-type] [create]
no queue queue-id
Context config>qos>sap-egress
Description This command enables the context to configure a service egress policy queue. Explicit
definition of an egress queue’s hardware scheduler status is supported. A single egress
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
egress ports. The hardware status of the queue must be defined at the time of queue creation
within the policy.

Table of Contents

Other manuals for Nokia 7705

Related product manuals