
Service Egress QoS Policy Forwarding Class Commands
Page 254
7950 XRS Quality of Service Guide
time the QoS policy is applied to the SAP, using the forwarding class map from the queue group
template.
•
If the
policer
policer-id
port-redirect-group
queue
queue-id
command is successfully executed,
the system will map the forwarding class to the configured
queue-id
within the egress queue group
instance that is specified at the time the QoS policy is applied to the SAP (ignoring using the
forwarding class map from the queue group template).
•
If the
policer
policer-id
group
queue-group-name
instance
instance-id
command is successfully
executed, the system will map the forwarding class to the queue within the specified egress queue
group instance using the forwarding class map from the group template.
•
If the
policer
policer-id
group
queue-group-name
instance
instance-id
queue
queue-id
command
is successfully executed, the system will map the forwarding class to the specified
queue-id
within
the specified egress queue group instance (ignoring the forwarding class map in the group
template).
If the specified
group
queue-group-name
is not defined as an egress queue-group-template, the
policer
command will fail. Further, if the specified group does not exist on the port for the SAPs or subscribers
associated with the
sap-egress
QoS policy, the policer command will fail. While a group queue-group-name
is specified in a
sap-egress
QoS policy, the groups corresponding egress template cannot be deleted. While
a port egress queue group is associated with a policer instance, the port queue group cannot be deleted.
If the specified queue group-queue-id is not defined in the egress queue-group-template queue-group- name,
the policer command will fail. While a
queue-id
within an egress queue group template is referenced by a
sap-egress
QoS policy forwarding class policer command, the queue cannot be deleted from the queue
group template.
If an egress policed packet is discarded by the egress port queue group queue, the source policer discard stats
are incremented. This means that the discard counters for the policer represent both the policer discard
events and the destination queue drop tail events associated with the policer.
The
no
form of this command is used to restore the mapping of the forwarding class to the default queue. If
all forwarding classes have been removed from the default queue, the queue will not exist on the SAPs or
subscribers associated with the QoS policy and the no policer command will cause the system to attempt to
create the default queue on each object. If the system cannot create the default queue in each instance, the no
policer command will fail and the forwarding class will continue its mapping to the existing
policer-id
. If the
no policer command results in a policer without any current mappings, the policer will be removed from the
SAPs and subscribers associated with the QoS policy. All statistics associated with the policer on each SAP
and subscribers will be lost.
Default
none
Parameters
policer-id —
When the forwarding class
policer
command is executed, a valid
policer-id
must be specified.
The parameter
policer-id
references a
policer-id
that has already been created within the
sap-egress
QoS policy.
Values
1—63
Default
none
port-redirect-group-queue —
Used to override the forwarding class default egress queue destination to an
egress port queue group. The specific egress queue group instance to use is specified at the time that the
QoS policy is applied to the SAP. Therefore, this parameter os only valid if SAP based redirection is
required.
Summary of Contents for 7950
Page 12: ...Page 12 7950 XRS Quality of Service Guide List of Figures ...
Page 16: ...Preface Page 16 7950 XRS Quality of Service Guide ...
Page 82: ...Editing QoS Policies Page 82 7950 XRS Quality of Service Guide ...
Page 90: ...Applying Network Queue Policies Page 90 7950 XRS Quality of Service Guide ...
Page 96: ...Editing QoS Policies Page 96 7950 XRS Quality of Service Guide ...
Page 98: ...Command Hierarchies Page 98 7950 XRS Quality of Service Guide ...
Page 108: ...Command Hierarchies Page 108 7950 XRS Quality of Service Guide ...
Page 156: ...Basic Configurations Page 156 7950 XRS Quality of Service Guide exit exit ...
Page 164: ...Queue Depth Monitoring Page 164 7950 XRS Quality of Service Guide ...
Page 304: ...Service Queue QoS Policy Commands Page 304 7950 XRS Quality of Service Guide ...
Page 368: ...Command Hierarchies Page 368 7950 XRS Quality of Service Guide ...
Page 430: ...Configuration Commands Page 430 7950 XRS Quality of Service Guide ...
Page 532: ...Editing QoS Policies Page 532 7950 XRS Quality of Service Guide ...
Page 552: ...Editing Advanced Policies Page 552 7950 XRS Quality of Service Guide ...
Page 600: ...Command Hierarchies Page 600 7950 XRS Quality of Service Guide ...
Page 602: ...QoS Commands Page 602 7950 XRS Quality of Service Guide ...
Page 610: ...Standards and Protocols Page 610 7950 XRS Quality of Service Guide ...
Page 612: ... 2015 Alcatel Lucent All rights reserved 3HE 09868 AAAA TQZZA 01 ...