Alcatel-Lucent 7950 Quality Of Service Manual page 191

Extensible routing system
Table of Contents

Advertisement

removed from a SAP ingress policy, the mac-criteria is removed from all services where that policy is
applied.
policer
Syntax
policer policer-id [create]
no policer policer-id
Context
config>qos>sap-ingress
Description
This command is used in the sap-ingress and sap-egress QoS policies 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 sap-ingress policy may have up to
63 policers (numbered 1 through 63) may be defined while the sap-egress QoS policy supports a maximum
of 8 (numbered 1 through 8). While a policer may be defined within a QoS policy, it is not actually created
on SAPs or associated with the policy until a forwarding class is mapped to the policer's ID.
All policers must be created within the QoS policies. A default policer is not created when a sap-ingress or
sap-egress QoS policy is created.
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.
Once a policer is created, it cannot be deleted from the QoS policy unless any forwarding classes that are
mapped to the policer are first moved to other policers or queues.
The system will allow a policer to be created on a SAP QoS policy regardless of the ability to support
policers 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 having 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
succeed. It is not necessary to actually delete the policer ID for the policer instances to be removed from
SAPs or 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
7950 XRS Quality of Service Guide
1—63
Page 191

Advertisement

Table of Contents
loading

Table of Contents