Table of Contents
Advertisement
queue-group
Syntax
queue-group queue-group-name [create]
no queue-group queue-group-name
Context
config>port>ethernet>access>egr
config>port>ethernet>access>ing
config>port>ethernet>network>egr
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 are used as an alternative queue destination for SAPs or
egress IP interfaces. Queue groups are not supported on HSMDA Ethernet ports.
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.
Within a network IP interface, an egress forwarding class may be redirected from the port network queue
(created by the network-queue policy applied to the network port) to an egress port queue group. The egress
queue groups may be used to create queues per egress IP interface. In this case, each IP interface would be
mapped to a different queue group and the network QoS policy applied to the IP interface will dictate which
forwarding classes are redirected to the queue group. As an alternative, multiple IP interfaces may share the
same queue group.
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. Queue groups on network mode ports are
created within the network node.
Within the access and network nodes, 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 supported. Multiple access egress queue groups may be created on a single port and are used by
egress SAP forwarding classes. On network mode ports, queue groups are only supported on the egress side
and are used by forwarding classes on egress IP interfaces.
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 cannot be created on the same port with the same name.
The queues defined in the template are created on the queue group. The queue parameters within the
template are used as the default queue parameters for each queue in the queue group. The default queue
parameters 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-limit 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
collecting statistics. The statistics are derived from the queue counters on each queue within the queue
7710 SR OS Interface Configuration Guide
Interface Configuration
Page 207
Advertisement
Table of Contents
