QoS Vlan Tagging

[svenmontgomery]

Just started to experiment with VOIP handsets which has meant my organisation has finally found the money for Procurve managed switches.

Have managed to teach myself the basics of VLANs but am a little confused on best practices for QoS.

Is there any reason I shouldn't just use VLAN prioritising? Got an interesting QoS chart from wikipedia (

http://en.wikipedia.org/wiki/Quality_of_service#QoS_priority_levels)

which I was going to use to model my vlan priorities on.

Anyone apply any QoS to any of their other VLANs ie management, printers etc

Any thoughts appreciated,

 

[cajuntank]

Get yourself a HP "My Procurve" account and read over these two documents:

http://cdn.procurve.com/downloads/docs/SolutionGuides/Convergence/VoIP/IPTelephonyDesign.pdf

http://cdn.procurve.com/downloads/docs/SolutionGuides/Convergence/VoIP/IPTelephonyImplementation.pdf

Now that being said, these documents are a little older and HP hasn't updated them for a few years as their software has been improved, but it still gives you a solid foundation on syntax to implement manually QoS. The reason I say manually is because when talking about VoIP, all you have to do is tag the designated voice VLAN with the "Voice" command and your set. It will take whatever QoS tags it's being given from the handsets and use that to prioritize that traffic throughout.

In regards of applying QoS to any other VLANs, it all depends on your layout and needs. Besides Voice, would you also need to define QoS for Video? Is your network large enough where you might see the need to create completely separate VLANs for administration, for finance, for engineering, for IT, etc... And/Or you could have separate VLANs for servers/printers/wireless/etc... Invariably, "the sky's the limit".

Except for Voice and Video that don't like to get out of order, all other classes of data won't suffer coming over the default priority of 0 unless your network experiences high levels of utilization. Over slower WAN circuits, this tends to happen, but over 100Mb or faster LAN connections, not near as much.

 

[PeterHurst]

Probably worth looking at the VOIP documentation for your voice switch - some have default tagging whhc may help (or hinder) in your planning.

 

[svenmontgomery]

Thanks for your replies Will take a look at those readings.

Your right should only be my voice/video-conference vlans that require any QoS as I dont think there is any saturation.

Have decided to do the vlan priorities being the most straight forward solution.

 

[veenstrahiem]

Here's a very simple programming of a HP switch which is probably enough for your needs at first:


hostname "hp-sw01"
time daylight-time-rule Western-Europe
qos dscp-map 101100 name "Mitel-VoIP"
qos dscp-map 101100 priority 6
vlan 1
name "DEFAULT_VLAN"
untagged 1-23
no ip address
exit
vlan 240
name "Mitel_VoIP"
ip address 10.240.10.251 255.255.255.0
qos priority 6
untagged 24
tagged 1-23
voice
exit
qos type-of-service diff-services
spanning-tree
spanning-tree bpdu-protection-timeout 120
password manager