Network Queue QoS Policies
Quality of Service Guide 167
A queue must be created as multipoint. The multipoint designator cannot be defined after the
queue is created. If an attempt is made to modify the command to include the multipoint
keyword, an error is generated and the command will not execute.
The multipoint keyword can be entered in the command line on a preexisting multipoint
queue to edit queue-id parameters.
Values multipoint or not present
Default Present (the queue is created as non-multipoint)
egress-hsmda
Syntax egress-hsmda
Context config>qos>network-queue
Description This command enables the context to configure queue definitions for use on HSMDAs and only
applies to the 7450 ESS and 7750 SR.
queue
Syntax [no] queue queue-id
Context config>qos>network-queue>egress-hsmda
config>qos>network-queue>fc
Description This command is a container for the configuration parameters controlling the behavior of an HSMDA
queue. Unlike the standard QoS policy queue command, this command is not used to actually create
or dynamically assign the queue to the object which the policy is applied. The queue identified by
queue-id always exists whether the command is executed or not. In the case of HSMDA SAPs and
subscribers, all eight queues exist at the moment the system allocates an HSMDA queue group to the
object.
Best-Effort, Expedited and Auto-Expedite Queue Behavior Based on Queue-ID
With standard service queues, the scheduling behavior relative to other queues is based on two items,
the queues Best-Effort or Expedited nature and the dynamic rate of the queue relative to the defined
CIR. HSMDA queues are handled differently. The create time auto-expedite and explicit expedite and
best-effort qualifiers have been eliminated and instead the scheduling behavior is based solely on the
queues identifier. Queues with a queue-id equal to 1 are placed in scheduling class 1. Queues with
queue-id 2 are placed in scheduling class 2. And so on up to scheduling class 8. Each scheduling class
is either mapped directly to a strict scheduling priority level based on the class ID, or the class may be
placed into a weighted scheduling class group providing byte fair weighted round robin scheduling
between the members of the group. Two weighted groups are supported and each may contain up to
three consecutive scheduling classes. The weighed group assumes its highest member class’s inherent
strict scheduling level for scheduling purposes. Strict priority level 8 has the highest priority while
strict level 1 has the lowest. When grouping of scheduling classes is defined, some of the strict levels
will not be in use.
To Next Page
Loading...
