Alcatel-Lucent 7750 Configuration Manual page 568

Service router
Hide thumbs Also See for 7750:
Table of Contents

Advertisement

Interfaces
The system will allow a policer to be created on a SAP QoS policy regardless of the ability to support polic-
ers on objects where the policy is currently applied. The system only scans the current objects for policer
support and sufficient resources to create the policer when a forwarding class is first mapped to the policer
ID. If the policer cannot be created due to one or more instances of the policy not supporting policing or hav-
ing insufficient resources to create the policer, the forwarding class mapping will fail.
The no form of this command is used to delete a policer from a sap-ingress or sap-egress QoS policy. The
specified policer cannot currently have any forwarding class mappings for the removal of the policer to suc-
ceed. It is not necessary to actually delete the policer ID for the policer instances to be removed from SAPs
or subscribers associated with the QoS policy once all forwarding classes have been moved away from the
policer. It is automatically deleted from each policing instance although it still appears in the QoS policy.
Parameters
policer-id — The policer-id must be specified when executing the policer command. If the specified ID
already exists, the system enters that policer's context to allow the policer's parameters to be modified.
If the ID does not exist and is within the allowed range for the QoS policy type, a context for the policer
ID will be created (depending on the system's current create keyword requirements which may require
the create keyword to actually add the new policer ID to the QoS policy) and the system will enter that
new policer's context for possible parameter modification.
Values
stat-mode
Syntax
stat-mode {no-stats | minimal | offered-profile-no-cir | offered-priority-no-cir | offered-
limited-profile-cir | offered-profile-cir | offered-priority-cir | offered-total-cir}
no stat mode
Context
config>card>fp>ingress>access>qgrp>policer-over>plcr
config>card>fp>ingress>network>qgrp>policer-over>plcr
Description
This command is used to configure the forwarding plane counters that allow offered, output and discard
accounting to occur for the policer. An ingress policer has multiple types of offered packets (explicit in-pro-
file, explicit out-of-profile, high priority or low priority) 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 large number of 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 profil-
ing rate and not all policers will receive explicitly 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 total/allocated/free stats by using the tools dump sys-
Page 568
1—32
7750 SR Interface Configuration Guide

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents