Shaping using the 'shape' cli defines the max rate for a class; whereas, the 'bandwidth' cli defines the minimum bandwidth guarantee for that class under functional congestion.
shape average percent 20
bandwidth percent 10
bandwidth percent 30
- Traffic through class A will *always* get shaped to 20% of intf bandwidth. Doesn't matter whether the interface is congested or not.
- Traffic through class B and Class C will get a *minimum* guarantee of 10 and 30% of intf bandwidth when the interface is congested. When the interface is not congested, then there is really no need for a queueing policy (~ bandwidth cli) and the queueing part of the policy won't kick in. So, class B / class C can basically use the entire intf bandwidth if there is no traffic through the other (bandwidth) classes. However, should the physical interface be congested (tx_ring is full) then queueing kicks in and each class is given a minimum guarantee that's configured. The remaining bandwidth is shared amongst the bandwidth classes in the ratio of guarantees.
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.