QoS Queue Group Template Command Reference
440 Quality of Service Guide
Besides the default mappings within the templates, the egress queue group template forwarding class
queue mappings operate the same as the forwarding class mappings in a sap-egress QoS policy.
The template forwarding class mappings are the default mechanism for mapping egress policed traffic
to a queue within an egress port queue group associated with the template. If a queue-id is explicitly
specified in the QoS policy forwarding class policer mapping, and that queue exists within the queue
group, the template forwarding class mapping is ignored.
On the 7450 ESS and 7750 SR, egress policed subscriber traffic works in a slightly different way. The
subscriber and subscriber host support destination and organization strings which when exist are used
to identify the egress port queue group. In this instance, the forwarding class mappings are always used
and any queue overrides in the QoS policy are ignored. If neither string exists for the subscriber host,
the egress queue group queue-id can be derived from either the QoS policy policer mapping or the
template forwarding class queue mappings.
The no form of this command is used to return the specified forwarding class to its default template
queue mapping.
Parameters fc-name — A valid forwarding class must be specified as fc-name when the fc command is
executed. When the fc fc-name command is successfully executed, the system will enter the
specified forwarding class context where the queue queue-id command may be executed.
Values be, l1, af, l2, h1, ef, h2 or nc
Default None
policer
Syntax policer policer-id
no policer
Context config>qos>queue-group-templates>ingress>queue-group
config>qos>queue-group-templates>egress>queue-group
Description This command is used in ingress and egress queue-group templates to create, modify or delete a
policer.
Policers are created and used in a similar manner to queues. The policer ID space is separate from the
queue ID space, allowing both a queue and a policer to share the same ID. The ingress queue-group
template may have up to 32 policers (numbered 1 through 32) may be defined while the egress queue-
group template supports a maximum of 8 (numbered 1 through 8). While a policer may be defined in
a queue-group template, it is not actually created until the queue-group template is instantiated on
ingress context of a forwarding plane or on the egress context of a port.
Once a policer is created, the policer's metering rate and profiling rates may be defined as well as the
policer's maximum and committed burst sizes (MBS and CBS respectively). Unlike queues which
have dedicated counters, policers allow various stat-mode settings that define the counters that will be
associated with the policer. Another supported feature—packet-byte-offset—provides a policer with
the ability to modify the size of each packet based on a defined number of bytes.
To Next Page
Loading...
