Shapers can drop packets when there's too much traffic. You have 242 drops across 173428 packets, which equals a cumulative drop percentage of (about) .14. This is offen acceptable. If these drops are due to transient congestion, you might be able reduce these drops by: increasing the queue depth, use peak shaping, or increase Bc (as Paolo suggests).
Paolo notes the Bc is setting a Tc of only 4 ms. I think I've noticed this now might be the default for the later 12.4 "T" software (previously default, I believe, usually was 25 ms). If it is a late 12.4T version (e.g. 12.4.2xT), I believe I've also noticed, what to me appears to be, a bug with shapers dropping traffic way below CIR rate (haven't reported it yet, but doesn't seem to behave that way if you back down a couple of T releases [i.e. at or before 12.4.15Tx]).
Excellant point! I believe I've read that recommendation too. Primary reason, I recall, something about the token bucket(s) would never have enough tokens to forward a packet larger than Bc. I would hope, though, if Cisco is now defaulting to a 4 ms Tc, that's this is no longer an issue. The low overall drop percentage, perhaps, might so indicate. If it doesn't, then you would want Bc to be large enough to handle largest packet size you might pass through the shaper.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.