VMware Horizon Community
KennyF
Contributor
Contributor

VMware View 5 PCoIP Qos Tagging

Hi,

We've successfully set up our DSCP to AF41 for PCoIP on our network, and the QoS tagging (binary 101110) shows in a Wireshark trace. However, in the Wireshark trace it shows that the VMware View 5 Client application does not tag the PCoIP protocol? Does the application not do this by default, or is there a setting that needs to be changed to do this?

Many thanks,

Kenny

Tags (3)
Reply
0 Kudos
5 Replies
iamxCPx
Enthusiast
Enthusiast

Hi Kenny,

Do you mind sharing how did you setup the QOS Tagging or if you have reference website that I can look at?

I have an open case with Cisco about implementing QOS for PCoIP traffic so they get priority after VoIP.

Thanks much.

Reply
0 Kudos
KennyF
Contributor
Contributor

CP,

This is what the network guys sent me:

policy-map PCoIP

class PCoIP

  set ip dscp af41

ip access-list extended PCoIP

permit ip any any

permit tcp any any eq 50002

permit udp any any eq 50002

class-map match-any PCoIP

match access-group name PCoIP

Uplink port:

interface GigabitEthernet0/24

description uplink to HP switch

switchport mode trunk

mls qos trust dscp

service-policy input PCoIP

I hope this makes a bit more sense to you than me. I only look after the VMware View server. I was also told by the network guys that because the PCoIP QoS tagging is not fully working as it should, hence my original query, they have not yet set up the priority after VOIP on the network.

Check the following tutorial that explains more in detail how to set this up - http://www.youtube.com/watch?v=p4mBJw-U3s8&feature=related

Once you get all this working, I hope you can explain why the client application does not tag the PCoIP traffic. Smiley Happy

Kenny

Reply
0 Kudos
iamxCPx
Enthusiast
Enthusiast

I'll get on it and will get back to you.

Thanks Kenny.

Reply
0 Kudos
KennyF
Contributor
Contributor

You're welcome CP. I still find it strange though that nobody else has experienced this issue? Well, I lood forward to any more responses.

Reply
0 Kudos
vedeht
Hot Shot
Hot Shot

I know this is an old thread but you need to change the ports to 4172 or this PCoIP won't work.  In View 4.6 and above they changed the default ports from 50002 to 4172.

This should read:

ip access-list extended PCoIP
permit ip any any
permit tcp any any eq 4172
permit udp any any eq 4172
Try our VMWare View Demo on www.virtualdojo.com
Reply
0 Kudos