CANOGA PERKINS 9145EMP NID Software Version 4.0 - Manual (Page 215)

9145EMP NID Software User’s Manual Bandwidth Profiling
Policers
200
• Excess Information Parameters:
• Excess Information Rate (EIR) is expressed in kbits per second. It defines the
average rate in kbits of service frames up to which the network may deliver ser-
vice frames, but without any performance objectives. EIR must be greater than or
equal to 0.
• Excess Burst Size (EBS) is expressed in kbytes. It limits the maximum number of
kbytes available for a burst of Service Frames sent at the line speed to conform to
EIR. This represents the maximum amount of tokens in the EIR token bucket.
• a Coupling Flag (CF), which allows the choice between two modes of operation of the
rate enforcement algorithm. It determines whether excess tokens from the CIR bucket
can be put into the EIR bucket. It must have only one of two possible values, 0 or 1. For
the 9145EMP, the value of the coupling flag is 0.
• The Color Mode parameter, which indicates whether the color-aware or color-blind prop-
erty is employed by the Bandwidth Profile. It takes a value of color-blind or color-aware
only. In the case of the 9145EMP, this value is color-blind for the policers and color-aware
for the shapers. This is read-only attribute.
• A reference counter, indicating the number of policers or shapers using the profile. Only
profiles that are not in use can be deleted or modified.
Up to 2048 policer bandwidth profile records can be stored on a 9145EMP system.
Note that you cannot delete the default "best effort" shaping profile (CIR = EIR = 0).
13.2 Policers
Policers limit the ingress traffic on user ports, according to an associated bandwidth profile.
There are a maximum of 128 policers per user port.
A policer is created and destroyed by the system and has the following attributes:
• a unique numerical policer ID
• a textual name
• a policing bandwidth profile record attached to the policer. Several policers may share the
same bandwidth profile.
• the attached traffic flow type. A policer may be attached to:
• A user port - If a policer is associated with an user port, no other policers (service
multiplexing level or CoS flow level policers) can be enabled on that port. For
more information, see the section “Port-level Policing” on page 60.
• A service multiplexing record
• A CoS flow, identified by a service multiplexing value and a PCP value. Every ser-
vice multiplexing record can have up to 8 policers associated. If a service multi-
plexing record has associated CoS-level granularity of bandwidth profiles, a
default policer is associated with the record. All PCP values not explicitly associ-
ated with different policers are associated with the default policer.
• an administrative state of the policer, which allows you to enable and disable traffic polic-
ing, without the need to re-provision the policer.