Traffic policer configuration rules for class maps
A service policy map or class map name must be unique among all maps of that type.
You cannot delete a service policy map or class map if it is active on an interface.
Operational values that are programmed in the hardware are displayed as part of
show policy-map interface ethernetslot/port command.
A policer name must begin with an alphabetic character from a to z or from A to Z. Underscores, hyphens, and numeric characters 0 through 9 are permitted, except as the first character of the name.
The configurable CIR and EIR ranges start from 22,000 bits per second (bps) and are rounded up to the next achievable rate.
Percentage values are not supported as a policer parameter.
Policer actions are not supported.
If a service policy map is applied to an interface and no policer attributes are present in that service policy map, then ingress and egress packets on that interface are marked as green (conforming).
If the configured CBS value is less than 2*(default MTU) value, then 2*(default MTU) is programmed as the CBS in the hardware. For example, if you configure CBS at 2000 bytes and the default MTU on an interface is 1548 bytes, when a policy map is applied on this interface, the CBS programmed in the hardware is 2*MTU (3096 bytes). If you update the MTU value, the CBS value is not be updated.
If CBS and EBS values are not configured, then these values are derived from CIR and EIR values, respectively. Burst size calculation is as follows: Burst size (CBS or EBS) = (1.2 × information rate (CIR or EIR)) ÷ 8.
If you do not configure EIR and EBS, then the single rate, two-color scheme is applied. Packets are marked as either green or red.
You must configure rate limit threshold values on an interface based on interface speed.
No validation is performed for user-configured values against interface speed.
You can configure up to 1024 service policy maps. Broadcast, unknown unicast, and unknown multicast policies are counted separately.
