Hi!
To be more specific, queuing will be applied to the traffic only when the interface is congested. If the interface has enough bandwidth to send the traffic, there is no point in queuing; is it? But any policying marking/classification will take place irrespective whether the interface is congested or not.
In your case, the parent policy will shape the Traffic to 2M. Now, if the total traffic for that interface is not exceeding 2M, there is no point in queueing. So if 1.5M of vlan2X traffic is coming and only .3M of other vlans, all traffic will be sent through, as there is no congestion and so no necessity to drop traffic.
So traffic from one class can use the bandwidth of other class if it is available. But if traffic from both classes is coming exceeding the bandwidth reservations of the class, then the mun. b/w comes into the picture. So the bandwidth specified in the class, is actually the min. bandwidth guaranteed for the class, which can be exceeded if unused bandwidth is available in other class.
So if you want to restrict your vlan2X traffic only to 1M, so that it never exceeds 1M even if bandwidth is available in outher class, you would have to police the traffic to 1M in addition to giving the bandwidth statement which will guarantee the bandwidth for the class.
Hope this makes things clear.
Regards,
Niranjan.
(Please rate helpful posts)
