I've been reading up on Cisco QOS and reviewing some sample configurations. I've noticed that some people configure it on the Router and some configure in on the switch. What are the advantages of doing it on either device?
We mark traffic (set the dscp value) at the perimeter of the network, the closest point to the client. Then as packets traverse the network we prioritize at each switch or router hop.
By marking the traffic at the edge, it allows shaping policies to be implemented immediately, before the packet even leaves its first switch hop. The downside of this approach is more configuration points in your network.
Marking the traffic at the router would potentially leave the initial communication from the client to router in a "best effort" scenario, potentially being dropped along the way.
When marking the traffic it is possible to attach a policy to either physical interface or virtual. Attaching the policy to a vlan interface should consume less resources.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Generally, QoS is used to manage congestion, which can happen on either a switch or router. However, as routers often have LAN links on "inside" and WAN links on "outside", with the latter often having much less bandwidth than the former, the latter is also much more likely to congest so you'll often see QoS implementations there before you'll see them on switches.
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...