Alcatel-Lucent 7210 SAS-X - Page 779

Virtual Private Routed Network Services
7210 SAS-X OS Services Guide Page 779
queue
Syntax queue queue-id [create]
no queue queue-id
Context config>service>vprn>if>sap>egress>hsmda-queue-overider
config>service>vprn>if>sap>ingress>hsmda-queue-overider
Description This command configures overrides for a HSMDA queue. The actual valid values are those defined in
the given SAP QoS policy.
Parameters queue-id — Specifies the queue ID to override.
Values 1 — 8
create — This keyword is mandatory while creating a new queue override.
packet-byte-offset
Syntax packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context config>service>vprn>if>sap>egress>hsmda-queue-overider
config>service>vprn>if>sap>ingress>hsmda-queue-overider
Description This command adds or subtracts the specified number of bytes to the accounting function for each
packet handled by the HSMDA queue. Normally, the accounting and leaky bucket functions are based
on the Ethernet DLC header, payload and the 4 byte CRC (everything except the preamble and inter-
frame gap). As an example, the packet-byte-offset command can be used to add the frame
encapsulation overhead (20 bytes) to the queues accounting functions.
The accounting functions affected include:
• Offered High Priority / In-Profile Octet Counter
• Offered Low Priority / Out-of-Profile Octet Counter
• Discarded High Priority / In-Profile Octet Counter
• Discarded Low Priority / Out-of-Profile Octet Counter
• Forwarded In-Profile Octet Counter
• Forwarded Out-of-Profile Octet Counter
• Peak Information Rate (PIR) Leaky Bucket Updates
• Committed Information Rate (CIR) Leaky Bucket Updates
• Queue Group Aggregate Rate Limit Leaky Bucket Updates
The secondary shaper leaky bucket, scheduler priority level leaky bucket and the port maximum rate
updates are not affected by the configured packet-byte-offset. Each of these accounting functions are
frame based and always include the preamble, DLC header, payload and the CRC regardless of the
configured byte offset.
The packet-byte-offset command accepts either add or subtract as valid keywords which define
whether bytes are being added or removed from each packet traversing the queue. Up to 31 bytes may