More than likely this will be a series of post about QOS. Around a year ago I worked on a Enterprise wide QOS WAN design for a DOD agency that went pretty well. Some guys senior to me worked them out and it was a good learning experience for all of us. One of them recently got his CCIE and the other is working on another attempt. Since then I have left the WAN world and become focused on UC. QOS has reared its ugly head again. While working with a credit union we had some quality problem going across the WAN which was a big deal as there call center was on the other side. Turns out no QOS on the wan which was MPLS VPN service from a provider , and instead they trusted there fate with a packet shaping device which turned out to be painful for all us involved. Ok enough back story lets break down this QOS thing with the Who, What, When, Where and Why?
WHO? QOS
WHAT? From Cisco Enterprise QOS SRND nov 2005(oldie, but goodie)
QOS is the mesure of transmission quality and service ability of a network or internetworks.
When? When do we need QOS. This is the big debate that happens all the time. "If I have Phat links I dont need QOS" is the argument I hear all the time. While this is true most of the time those times when your link gets congested, the time that worm attacks your network, or when your users get around your security and light off peer to peer apps, or legit traffic gets in front of your voice traffic you will run into trouble.
Where? You can put QOS on your LAN/WAN and even wireless networks.
Why? QOS will allow your to classify, Mark, Policing, and Schedule your traffic to allow you to get the best use out of your link. Now with that said QOS will not make your T1 be 2 T1's, but you will decide who gets to use the wire 1st, which according to newtons 3rd law there is a consequence of you will also decide who goes to the bit bucket.
No comments:
Post a Comment