Interface Configuration
7750 SR Interface Configuration Guide Page 379
queue-group
Syntax queue-group queue-group-name [instance instance-id] [create]
no queue-group queue-group-name [instance instance-id]
Context config>port>ethernet>access>egress
config>port>ethernet>access>ingress
Description This command creates an ingress or egress queue group on an Ethernet port. A queue group is a collection of
queues identified by a group name. Queue groups created on access ports are used as an alternative queue
destination for SAPs.
Within a SAP, a forwarding class may be redirected from the local SAP queue to a port queue group queue.
The forwarding classes from multiple SAPs may be redirected to the same queue group which can be used to
minimize the number of per-SAP queues.
Queue groups may be created on both access and network oriented ports. When the port is in access mode,
the queue groups must be created within the port access node.
Within the access node, queue groups are also configured as ingress or egress. Access ingress queue groups
can only be used by ingress SAP forwarding classes and only a single ingress queue group per port is sup-
ported. Multiple access egress queue groups may be created on a single port and are used by egress SAP for-
warding classes. The instance-id parameter identifies different instances of the same queue group template.
Creating multiple queue groups with a different instance ID but the same queue group name results in sepa-
rate queue groups being created on the port. The instance-id parameter is only valid for egress queue groups
on access ports.
When the queue group is created in an ingress port context, the group-name must be an existing ingress
queue group template. Similarly, queue groups created in an egress port context must have a group-name of
an existing egress queue group template. Two ingress queue groups with the same name cannot be created
on the same port. Two egress queue groups can only be created on the same port with the same queue group
template name if they have different instance-id values.
The queues defined in the template are created on the queue group. The queue parameters within the tem-
plate are used as the default queue parameters for each queue in the queue group. The default queue param-
eters for each queue may be overridden on the queue group with specific queue parameters.
Each queue group supports the application of a scheduler-policy for the purpose of managing the queues
within the group into an aggregate SLA. The queues defined within the template may be configured with
parent scheduler defining the mapping of a queue to one of the schedulers within the scheduler policy.
Egress queue groups also support the agg-rate parameter and the queues in the egress template support the
port-parent command. Each command is used for configuring egress port virtual scheduling behavior.
Each queue group allows the application of an accounting policy and the ability to enable and disable col-
lecting statistics. The statistics are derived from the queue counters on each queue within the queue group.
The accounting policy defines which queue counters are collected and to which accounting file they will be
written.
A queue group does not have an administrative shutdown or no shutdown command. A queue group is con-
sidered to be always on once created.
When creating a queue group, the system will attempt to allocate queue resources based on the queues
defined in the queue group template. If the appropriate queue resources do not currently exist, the queue
group will not be created. Ingress port queue groups do not support the shared-queuing or multipoint-shared
queuing behavior.
To Next Page
Loading...
