What type of traffic is mainly being transmitted within your class default? Is it UDP or TCP?
If it is mainly TCP then it is the bursty nature of the protocol that is being dropped. Although the traffic over the 5 minute period is not going above the 100kbps limit, the traffic is bursting above 100kbps in the policing sampling period and hence will be dropped. An alternative to this is to use traffic shaping on your default class, this will buffer up the excess traffic and then send it on when the bandwidth is available. It also has the advantage that it will improve performace for TCP streams as TCP will throtle back correctly whereas with traffic policing it has a habit of not doing so.
Thanks a lot for your answer. But when I replaced the police command with the shape average command, I couldn't apply the command at the pvc. When I applied it at the pvc, it didn't produce any error. But the subinterface configuration haven't changed. May bandwidth be a reason for this? Bandwidth is 256 Kbps for each pvc.
I was only able to apply it to the pvc as an inbound policy and not an outbound. Depending upon your network configuration you may be able to apply it to the remote end of the circuit if it is point-to-point.
As usual, I have a hub&spoke topology. At the center, I have 34 Mbps ATM and 256 Kbps Gshdsl lines at remote ends. I applied only priority queue to the output of each pvc at the center. The rest is default queue. But I see that the priority does not work. I mean that when there is a congestion (200 Kbps traffic), my critical traffic also have congestion. So my applications does not work. So I decided to put a limit for default class. The limit is 100 Kbps. As I said earlier, then the default class applications couldn't work. Because it drops at the 6000 bps output rate, not 100000 bps. How can I solve this issue?
It is dropping at the 100,000 bps rate, but because the load interval is over five minutes it averages out at 6000bps.
One option might be to deploy an inbound policy map at each of the 256k sites, traffic like TCP should respond correctly to being shaped. The values for the shaping should also be in multiples of 64000, ie 128000 not 100000.
Also use the "load-interval 30" command in the main interface, this will change the values that you see so that they are over 30 seconds not five minutes.
Give it a try on one of your sites that experiance the problems.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...