QoS Queue Group Template Command Reference
450 Quality of Service Guide
Parameters add bytes — The add keyword is mutually exclusive to the subtract keyword. Either add or
subtract must be specified. When add is defined the corresponding bytes parameter specifies
the number of bytes that is added to the size each packet associated with the queue for
scheduling, profiling and accounting purposes. From the queue’s perspective, the packet size
is increased by the amount being added to the size of each packet.
Values 0 to 30, in steps of 2
Default None
subtract bytes — The subtract keyword is mutually exclusive to the add keyword. Either add or
subtract must be specified. When subtract is defined the corresponding bytes parameter
specifies the number of bytes that is subtracted from the size of each packet associated with
the queue for scheduling, profiling and accounting purposes. From the queue’s perspective,
the packet size is reduced by the amount being subtracted from the size of each packet. The
minimum resulting packet size used by the system is 1 byte.
Values Values 0 to 64, in steps of 2
Default None
parent
Syntax parent scheduler-name [weight weight] [level level] [cir-weight cir-weight] [cir-level cir-
level]
no parent
Context config>qos>qgrps>egr>qgrp>queue
config>qos>qgrpid>ing>qgrp>queue
Description This command defines an optional parent scheduler that further governs the available bandwidth given
the queue aside from the queue’s PIR setting. When multiple schedulers and/or queues share a child
status with the parent scheduler, the weight or level parameters define how this queue contends with
the other children for the parent’s bandwidth.
Checks are not performed to see if a scheduler-name exists when the parent command is defined on
the queue. Scheduler names are configured in the config>qos>scheduler-policy>tier level context.
Multiple schedulers can exist with the scheduler-name and the association pertains to a scheduler that
should exist on the egress SAP as the policy is applied and the queue created. When the queue is
created on the egress SAP, the existence of the scheduler-name is dependent on a scheduler policy
containing the scheduler-name being directly or indirectly applied (through a multi-service customer
site) to the egress SAP. If the scheduler-name does not exist, the queue is placed in the orphaned
operational state. The queue will accept packets but will not be bandwidth limited by a virtual
scheduler or the scheduler hierarchy applied to the SAP. The orphaned state must generate a log entry
and a trap message. The SAP which the queue belongs to must also depict an orphan queue status. The
orphaned state of the queue is automatically cleared when the scheduler-name becomes available on
the egress SAP.
To Next Page
Loading...
