Token bucket limits and bandwidth limits are together known as performance limits. These performance limits help guarantee packet delivery in outbound bandwidth policies, both integrated and differentiated service.
The token bucket size determines the amount of information your server can process at any given time. If an application is sending your server information faster than the server can send the data out of the network, the buffer fills up. Any data packets exceeding this limit are treated as out-of-profile. Integrated service policies are the exception to this rule. You can select do not limit, which will allow a ReSerVation Protocol (RSVP) connection request. For all other policies, you can determine how to handle out-of-profile traffic. The maximum token bucket size is 1 GB.
The rate limit specifies the long term data rate or the number of bits per second allowed into a network. The quality of service (QoS0 policy looks at the requested bandwidth and compares it with the rate and flow limits for this policy. If the request causes the server to exceed its limits, the server denies the request. The token rate limit is only used for admission control within integrated service policies. This value can vary between 10 Kbps to 1 Gbps. You can also set this to do not limit. When you assign do not limit to the rate, you are making the available resources the limit.
To view real-time monitor data instead of a particular data collection, just open the monitor. The monitor gives real-time statistics on all active policies.