Alcatel-Lucent 7950 Quality Of Service Manual page 226

Service Ingress QoS Policy Forwarding Class Commands
Redirection to an egress port queue group specified for the HSMDA is possible using the port-redirect-
group parameter. If this is specified, then packets are redirected to the queue-id in the HSMDA queue
group instance named at the the time the egress QoS policy is applied to the SAP.
The no form of the command restores the defined queue-id to its default parameters. All HSMDA queues
having the queue-id and associated with the QoS policy are re-initialized to default parameters.
Parameters
queue-id — Defines the context of which of the eight ingress or egress queues will be entered for editing
purposes.
port-redirect-group — This parameter is used to mark a given forwarding class queue for redirection to an
egress port queue group. This is only used when the specific queue group instance is assigned at the
time the qos policy is applied to the SAP. This redirection model is knowen as SAP based redirection.
packet-byte-offset
Syntax packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context config>qos>sap-egress>hsmda-queues
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 Ether-
net 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:
•
•
•
•
•
•
•
•
•
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 off-
set.
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 20 bytes may be added to the
packet and up to 43 bytes may be removed from the packet. An example use case for subtracting bytes from
each packet is an IP based accounting function. Given a Dot1Q encapsulation, the command packet-byte-
offset subtract 14 would remove the DLC header and the Dot1Q header from the size of each packet for
Page 226
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
7950 XRS Quality of Service Guide