QoS

I understand the concepts of QoS I think.... but what exactly uses QoS? and just to make sure I got it right another explaination is always good. I basically understand it as "quality of service" which sorta reserves 20% (normally) of network bandwidth for programs that use it IF they need it but otherwise the 20% is used normally for everyday traffic.... am I right? Again, what uses a service like this?

Quote:

---

Originally Posted by arch0nmyc0n

I understand the concepts of QoS I think.... but what exactly uses QoS? and just to make sure I got it right another explaination is always good. I basically understand it as "quality of service" which sorta reserves 20% (normally) of network bandwidth for programs that use it IF they need it but otherwise the 20% is used normally for everyday traffic.... am I right? Again, what uses a service like this?

---

Voice Over IP is the one I know. I'm sure there are others, but when we were investigating VOIP one of the things were were going to have to do was get QOS installed on all our routers

You can set up cisco devices (not sure but might be a router add on, not sure) so that one application or traffic gets service before another. I know where I work we wish we had it as PC's going to the internet wil often cause slow downs to devices accessing a telnet session and it causes all sorts of havok. You use them to ensure that the devices or applications that really need to use the circuit bandwidth really get what they need when they need it. Otherwise it's 1st come 1st serve.

We have sites on our WAN with a 128k frame circuit where one dingus downloads a 40mb file and hoses up 20 terminals with telnet sessions. Or, one doof uses internet radio utilizes bandwidth to the point where no one can log on to the remote servers. We wish we had a way to do QoS jus so we didn't get all the stupid calls we get about sites being slow because dingus A ate up all the bandwidth surfing for porn.


To experiment, you might want it put multiple file sharing machines on your network and let them upload and see how fast your regular internet browsing goes. It's awful. Turn off the file sharing machines and everything returns to normal.

Quote:

---

Originally Posted by ilovetheusers

You can set up cisco devices (not sure but might be a router add on, not sure) so that one application or traffic gets service before another. I know where I work we wish we had it as PC's going to the internet wil often cause slow downs to devices accessing a telnet session and it causes all sorts of havok.

We have sites on our WAN with a 128k frame circuit where one dingus downloads a 40mb file and hoses up 20 terminals with telnet sessions. r, one doof uses internet radio utilizes bandwidth to the point where no one can log on to the remote servers.


To experiment with why you might want it put multiple file sharing machines on your network and let them upload and see how fast your regular internet browsing goes. It's awful. Turn off the file sharing machines and everything returns to normal.

You use them to ensure that the devices or applications that really need to use the circuit bandwidth really get what they need when they need it. Otherwise it's 1st come 1st serve.

---

that's a really good explanation. https://forums.windrivers.com/images.../2005/03/1.gif

This is every freakin day for me and the sad thing is techs with 5 or more years of experience can't understand why sites get slow when you download 50mb files on 56k lines. Sigh.