Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member


Hi friends,

Any body have good idea about QoS if have plz. provide me like the purpose, use, advantages.

It will be great thankful.



Super Bronze

Re: QoS

In brief, QoS (quality of service) tries to provide some assurance for network traffic handling beyond just best effort. When there's congestion, it treats different types of traffic differently; often treating some traffic better at the expense of treating other traffic worst.

A good example would be a VoIP (voice over IP) traffic sharing the same link with a FTP file transfer.

Assume you have two hosts connected switches at 100 Mbps, but those switches are interconnected by a 10 Mbps link. FTP will try to drive up to 100 Mbps, but at the 10 Mbps link, traffic will queue. When the queue fills, packets will drop. This will tell TCP to back off its transmission rate. What you should see is a classic saw tooth pattern of transmission rate.

Now while FTP was doing the above, you also send 80 Kbps of VoIP traffic across the same 10 Mbps link. VoIP tends to be very sensitive to delay, drops and even jitter. VoIP packets intermixed with the FTP packets are very likely to suffer delay, drops and jitter; result a very poor, if usable at all, voice call.

With QoS, we classify or identify we have VoIP traffic and treat it better than other traffic. Usually, for real-time traffic like VoIP, we'll guarantee the 80 Kbps it needs from the 10 Mbps. This, though, reduces the bandwidth available to FTP by 80 Kbps. FTP will take longer to transfer its data, but VoIP will perform the same regardless of whether FTP is using the link or not. We've provided a quality of service for the VoIP traffic.

QoS can encompass even more. For just the FTP alone, it's rather wasteful that it keeps overrunning the 10 Mbps link, which causes packet drops, which makes for a effective transfer rate often less than the full link capacity and/or wastes bandwidth. To improve the quality of the FTP transfer (goal exactly 100% bandwidth utilization; no waste), you might adjust the TCP receive window size, clock ACKs, or set the ECN bit. (NB: advanced techniques like these are not usually found on most ordinary network devices, but are some of techniques used by some traffic optimizing appliances.)

The "easy" alternative to using quality of service is to insure there's never congestion. If the switch interconnection link was 1 Gbps, instead of 10 Mbps, we could run both the 100 Mbps FTP and the 80 Kbps VoIP without issue.

Where bandwidth is "cheap", such as on LANs, then QoS might not be needed. On WANs, where bandwidth isn't so "cheap", QoS might be necessary if you're trying to guarantee service (or performance).

New Member

Re: QoS

Hi Joseph,

It's very nice & very clear explaination thank you so much.

I understood about QoS very clearly with your info. One more thing how we should use it means as a application software and how and where we have to configure it, what are the steps and commands.



Super Bronze

Re: QoS

Often where to use QoS is whenever applications are adversely impacted by having insufficient bandwidth that can be obtained from other applications whose needs are not as stringent. What to use sometimes is as simple as insuring FQ is enabled on a router's outbound interface.

I don't believe I can truly well answer your question in a short response. You might review the information off the hyperlinks here:

CreatePlease to create content