Look at my case:
Customers are connected to service provider (SP) trough a FastEthernet ports on a switch. One vlan per customer. Then that vlans are terminated on access router (subinterfaces). Occasionaly not all customers follow the contract agreement of bandwidth utilization. By contract they are prohibited to, for example, 7 mbps bandwidth, but because their connection is wirespeed (100 mbps) they often exceed that contract limitation.
The question is what is the best practice for SP to work out this situation? I mean, how to limit the rate for customers?
Applying service-policy with flow average limit doesn't work on subinterface for an ingress flow (from customer).
>> The case is - "customer is interconnecting different company sites."
>> I still can hardly guess the meaning of burst and max-burst fields in mls qos aggregate-policer command.
These are buffers expressed in bytes not bytes/sec instead the rate is in bps.
Actually a policer uses a token bucket algorithm to compare packets with the presence of tokens in buffers:
if enough tokens for the packet are present in the buffer the packet is considered conforming and sent out/accepted.
What counts is packet size and interarrival time between this packet and the previous one sent/accepted.
in this case The burst and max-burst buffers allow to accomodate a burst of B bytes over the stated rate allowing to handle the variable nature of data traffic.
exceed burst size is used at startup after long time of inactivity to allow to send more traffic during first time interval.
So these are parameters used to tune the policer behaviour and old rules used with CAR was to allow at least 250 msec of traffic at peak rate to dimension the normal burst size and to use a double value for exceeding burst size.
These buffers are refilled of tokens at the specified bit rate and no more and allows to use later up to B to max-B "credits"
Hope to help