Service Egress QoS Policy Forwarding Class Commands
Page 262
7950 XRS Quality of Service Guide
second
value must be expressed as an integer and defines the rate in kilobits-per-second. The integer
value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the
maximum policer rate used will be equal to the maximum capacity of the card on which the policer is
configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then
the PIR used is equivalent to max.
Values
max
or 1—2000000000
Values
max
or 0—2000000000
cir
{
max
|
kilobits-per-second
}
—
The optional
cir
keyword is used to override the default CIR rate of the
policer. Specifying the keyword max or an explicit
kilobits-per-second
parameter directly following the
cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the
policer is first created, the profiling rate defaults to 0 Kbps. The
kilobits-per-second
value must be
expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by
1,000 to derive the actual rate in bits-per-second.
Values
max
or 0—20,000,000
stat-mode
Syntax
stat-mode
{
no-stats
|
minimal
|
offered-profile-no-cir
|
offered-profile-cir
|
offered-total-cir |
offered-profile-capped-cir | offered-limited-capped-cir
}
no stat mode
Context
config>qos>sap-egress>policer
config>qos>queue-group-templates>egress>queue-group
Description
The
sap-egress
QoS policy's policer
stat-mode
command is used to configure the forwarding plane
counters that allow offered, output and discard accounting to occur for the policer. An egress policer has
multiple types of offered packets (soft in-profile and out-of-profile from ingress and hard in-profile and out-
of-profile due to egress profile overides) and each of these offered types is interacting with the policer’s
metering and profiling functions resulting in colored output packets (green, yellow and red). Due to the
potential large number of egress policers, it is not economical to allocate counters in the forwarding plane
for all possible offered packet types and output conditions. Many policers will not be configured with a CIR
profiling rate and not all policers will receive explicitly re-profiled offered packets. The
stat-mode
command allows provisioning of the number of counters each policer requires and how the offered packet
types and output conditions should be mapped to the counters.
While a
no-stats
mode is supported which prevents any packet accounting, the use of the policer's
parent
command requires at the policer’s
stat-mode
to be set at least to the
minimal
setting so that offered stats are
available for the policer’s Fair Information Rate (FIR) to be calculated. Once a policer has been made a child
to a parent policer, the
stat-mode
cannot be changed to
no-stats
unless the policer parenting is first
removed.
Each time the policer's
stat-mode
is changed, any previous counter values are lost and any new counters are
set to zero.
Each mode uses a certain number of counters per policer instance that are allocated from the forwarding
plane's policer counter resources. You can view the the total/allocated/free stats by using the
tools dump
system-resources
command. If insufficient counters exist to implement a mode on any policer instance, the
stat-mode
change will fail and the previous mode will continue unaffected for all instances of the policer.
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 ...