Network Queue QoS Policy Command Reference
168 Quality of Service Guide
Every HSMDA Queue Supports Profile Mode Implicitly
Unlike standard service queues, the HSMDA queues do not need to be placed into the special mode
profile at create time in order to support ingress color aware policing. Each queue may handle in-
profile, out-of-profile and profile undefined packets simultaneously. As with standard queues, the
explicit profile of a packet is dependent on ingress sub-forwarding class to which the packet is mapped.
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.
This command only applies to the 7450 ESS and 7750 SR.
Parameters queue-id — Defines the context of which of the eight egress queues will be entered for editing
purposes.
packet-byte-offset
Syntax packet-byte-offset {add add-bytes | subtract sub-bytes}
no packet-byte-offset
Context config>qos>network-queue>egress-hsmda
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 14-byte Ethernet DLC header, 4-byte or 8-byte VLAN tag (optional), 20-byte IP header, IP
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.
To Next Page
Loading...
