Agree with jwdoherty.
1. Yes, it will be available for other VLANs. That's how CBWFQ work (unless you use policing/shaping in connection with class-maps)
2. It's not that easy for inbound. All the congestion management systems work with software queues that are inside the router. For input traffic, the queues are different, since all data is sent at LINESPEED and queues are created only in case of abnormal router utilization and/or Multiaccess medium.
The best way would be to create same QoS setup on the other side. You would have to contact your ISP and ask about applying QoS maps on their output interfaces. ISPs sometimes do that for a not-too-high fee. You cannot even use shaping on input, and your available choices will be very dependent on your router model.
EDIT:
As a rule of thumb, your primary control point is output, and input control work mostly as support. Some platforms have interesting options, like 2 priority queues, where you would put your important VLAN in one queue and all other VLANs into other queue.
What box do you have?
E.G. 2851 cannot have input priority queue. But it can police (hard-limit) the incoming traffic, which is probably not what you want.
Here is one possible setup:
OUT:
ip access-list extended out-vlan
permit ip VLAN_SUBNET VLAN_MASK any
class-map match-any important
match access-group out-vlan
policy-map control-out
class important
bandwidth 2500
class class-default
fair-queue
IN:
ip access-list extended in-vlan
permit ip any VLAN_SUBNET VLAN_MASK
class-map match-any unimportant-in
match not access-group in-vlan
policy-map control-in
class unimportant-in
police XXX (XXX is the maximum rate all other VLANs will be able to use)
Then apply it to the interface:
service-policy input control-in
service-policy output control-out
You would be much better off contacting the ISP and persuading them to apply output map.
Hope this helps.
Please rate all helpful posts.
