Specifications

White Paper
© 2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 51 of 89
Figure 35. Step 1 and 2 of the Token Bucket Process
Step 3 and 4: The PFC will inspect the number of tokens that are available in the token bucket. If the number of
tokens is greater than or equal to the number of bits in the current packet being inspected, then the packet can be
forwarded. If there are not enough tokens, then the packet will either be marked down (and forwarded) or dropped,
depending on the policer’s configuration.
Figure 36. Steps 3 and 4 of the Token Bucket Process
Step 5: Assuming that there are enough tokens in the bucket, a number of tokens (corresponding to the number of
bits in the packet) will be removed from the token bucket.
Step 6: The packet will then have the “conform-action” as configured in the policing statement applied to it. Normally
the “conform” action is simply to forward the packet, which is performed by the Policy Feature Card. Other packets
that had arrived in that time interval will have the same action applied to them. If enough tokens exist in the bucket
for those packets, the packets will be sent.