TER1105004 Issue 2-PCoIP Protocol Virtual Desktop Network Design Checklist

7m ago
993.92 KB
10 Pages
Last View : 7m ago
Last Download : n/a
Upload by : Audrey Hope

PC-over-IP Protocol Virtual DesktopNetwork Design ChecklistTER1105004Issue 2

PCoIP Protocol Virtual Desktop Network Design ChecklistTeradici Corporation#101-4621 Canada Way, Burnaby, BC V5G 4X8 Canadap 1 604 451 5800 f 1 604 451 5818www.teradici.comThe information contained in this document represents the current view of Teradici Corporation as of the date of publication. Because Teradicimust respond to changing market conditions, it should not be interpreted to be a commitment on the part of Teradici, and Teradici cannotguarantee the accuracy of any information presented after the date of publication.This document is for informational purposes only. TERADICI MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THEINFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of thisdocument may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Teradici Corporation.Teradici may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in thisdocument. Except as expressly provided in any written license agreement from Teradici, the furnishing of this document does not give you anylicense to these patents, trademarks, copyrights, or other intellectual property. 2011 Teradici Corporation. All rights reserved.Teradici, PC-over-IP, and PCoIP are registered trademarks of Teradici Corporation.The names of actual companies and products mentioned herein may be the trademarks of their respective owners.TER1105004 Issue 23

PCoIP Protocol Virtual Desktop Network Design ChecklistRevision HistoryVersionDateDescription1Jun 02, 2011Initial release2Jun 20, 2011Added requirement for PortFast, updated bandwidthguideline tablesTER1105004 Issue 24

PCoIP Protocol Virtual Desktop Network Design ChecklistPCoIP Protocol Virtual Desktop Network DesignChecklistThe PCoIP protocol provides a real-time delivery of a rich user desktop experience in virtual desktopand remote workstation environments. To ensure a responsive desktop, the PCoIP protocol must bedeployed across a properly architected virtual desktop network infrastructure that meets bandwidth,QoS, latency, jitter, and packet loss requirements.For more detailed information see techsupport.teradici.com.PCoIP Protocol Overview PCoIP Protocol uses UDP packets similar to other real-time protocols (VOIP, videoconferencing)PCoIP protocol implements packet reliability and flow control similar to TCP, however thisis done in an intelligent manner consistent with real-time requirements (ie USB alwaysresent, imaging may be resent, but stale imaging/audio not resent).PCoIP protocol performs traffic shaping on the PCoIP packet traffic and will dynamicallyadapt image/audio quality depending on the available network resourcesPCoIP protocol will fairly share the available network resources with other PCoIP sessionson the network.WAN optimizations already built into the PCoIP protocolNetwork RequirementsNotesConsider QoS options such as Class-based Weighted Fair Queuing(CBWFQ) or Low Latency Queuing (LLQ) on switch uplinks and onLayer 3 WAN/LAN links.TER1105004 Issue 2Mark and classify PCoIP traffic the same as real timeinteractive traffic according to your QoS marking scheme. (i.e.below VoIP RTP but above all other traffic).This is necessary for the real timeresponsiveness of the protocol.If using DSCP markings, PCoIP traffic should be marked toDSCP AF41 or AF31 to ensure low drop probability inside eachqueue if WRED must be configured per the queue servicing thePCoIP protocol.Choice of which DSCP value to use isinfluenced by the presence of possible videoand/or VoIP control packets.Avoid using low-latency queueing (LLQ) for PCoIP packets onlinks that carry VoIP traffic and are have less than 1.544Mbpsof bandwidth.The PCoIP packets can adversely delay theVoIP packets in the priority queue on lowbandwidth links.Consider using low-latency queueing (LLQ) for PCoIP packetson links that do not carry VoIP and have greater than1.544Mbps available. Consider the 33% LLQ rule.The strict priority queue should only beconsidered if there are many different typesof traffic competing with PCoIP andperformance is suffering.Avoid adjusting the MTU on low bandwidth links to decreaseserialization time for VoIP packets as the PCoIP protocolIt may be difficult to guarantee high qualityconversations with both VoIP and PCoIP onNot all switches support the same number ofpriority queues; work with Service Providersto ensure proper end-to-end prioritymapping.5

PCoIP Protocol Virtual Desktop Network Design Checklistpackets should not be fragmented.links with less than 1.544Mbps of bandwidth.Consider tuning the hardware transmit ring to 1 to ensure thatsoftware queuing takes place if LLQ is not possible and PCoIPor VoIP are experiencing high jitter.Large packet serialization can sometimescause high amounts of jitter. This should notbe done in most cases as proper CBWFQusage will allow for acceptable guaranteedsession quality.Increase the queue-depth settings in the PCoIP queue if taildrops are experienced. If near maximum recommended queuedepths, consider optimizing PCoIP for lower bandwidth orincreasing the link bandwidth.On a Cisco device look for the drop rate onthe 'show policy-map interface' command.Ensure that your classification and QoS schemes work withyour WAN Carrier's QoS schemes. This is especiallyapplicable to MPLS networks.Most WAN Carriers only offer 3 or 4different classes of traffic on MPLSnetworks.Configure Weighted Random Early Drop (WRED) in the path of allPCoIP conversations. On Cisco Routers this is the 'random-detect'command.PCoIP protocol incorporates rate limiting andflow control mechanisms optimized forvirtual desktops. Unlike traditional UDPapplications, WRED will work with PCoIPprotocol and gradual packet loss allows timefor PCoIP protocol to adapt.Tail drop does not allow time for PCoIPprotocol to adapt and alleviate the congestionbefore user experience is impactedConfirm that the network interface is not configured for WREDif you have selected WRED for the service policy on thatinterface.Note that configuring WRED on the physicalinterface overrides all other QoS queuingconfigurations.Consider segmenting PCoIP traffic via Layer 2 VLAN and/or COStypes at the access layer of your network.Only use Layer 2 QoS COS prioritization if there is notedcongestion at the access layer or between the access andaggregation (distribution) layer.Consider adding Layer 2 uplink bandwidthbefore applying Layer 2 QoS if possible.Carefully consider the use of auto-qos features at the layer 2layer as this may result in WRED being applied at theswitchport layer through the use of Shared/Shaped RoundRobin (SRR) Queues.SRR Queues are automatically configured onmany Cisco access layer platforms whenusing the auto-qos feature. By default theseenforce WRED for all but trunked packetsmarked with COS 5 (generally VoIP packetsfrom a hardphone).Avoid Traffic Shaping unless absolutely necessary. Shaping works tosmooth traffic bursts and achieve a defined CAR by buffering packets– increasing the latency.Traffic shaping will increase PCoIP packetlatency and can impact user experience. Ifnecessary, consider Traffic policing as analternative.Ensure a full-duplex end-to-end network link is usedNote: Older switches may incorrectly defaultto half duplex when connected to a link withauto-negotiation. In this case, explicitly setthe switch link to full duplexEnsure network ports are open for PCoIP protocol and VMware ViewSee VMware View Architecture Planningdocument (EN-000524-00)See knowledge base techsupport.teradici.comEnsure that PortFast is enabled on all network ports that PCoIP ZeroClients or VMware View Clients are connected to.TER1105004 Issue 2This ensures that the port is immediatelyconfigured to forward traffic in the event of a6

PCoIP Protocol Virtual Desktop Network Design ChecklistSpanning-tree recalculation.Ensure Intrusion Protection Services have been disabled or configuredto allow PCoIP protocol and VMware View network portsIPS can block some/all network ports and/orthrottle bandwidth for PCoIP protocolEnsure that the round trip network latency is within specificationExcessive latency will impact desktopperformanceLess than 250ms round trip for VMware View 4.x hostsLess than 150ms round trip for PCoIP Host CardsEnsure the latency variation is less than 30msAbout 1 frame for 30 fps (HD video anddefault for PCoIP Software in VMwareView.Minimize link packet lossPacket loss should be zero for a properly configuredLAN/WAN deployments. Packet loss within a single PCoIPsession should target less than 0.1%Users will typically notice performancedegradation if the session packet loss isgreater than 1%.PCoIP packets which arrive sufficiently out of order may beconsidered as lost packets by the PCoIP protocol. Avoid packetre-ordering in the networkThis will show as packet loss in the PCoIPsession logs, but not in network device logsAvoid gaps in PCoIP protocol traffic, PCoIP sessions willdisconnect after 30 seconds of loss in traffic in either networkdirection or PCoIP port (4172 UDP/TCP)Intrusion protection services (IPS) orintrusion detection services (IDS) should bedisabled, or configured to allow (4172UDP/TCP).Ensure that PCoIP packets are not fragmented at any point in thenetwork pathEnsure MTU in network devices is not below the PCoIP packetMTU size - defaults - 1300 bytes VMware View Host, and 1400bytes when connecting PCoIP Zero Clients to PCoIP HostCardsIncrease router MTU before reducing PCoIPpacket MTU as lower PCoIP protocol MTUcan impact desktop performance. Keep inmind that network devices may addadditional encapsulation and increase PCoIPpacket sizeEnsure that packet order is maintainedDo not use per-packet load balancing for any load balancingdecisions along the path of traffic, including but not limited to:EIGRP load balancing, Static Route load balancing, or MPLSload balancing.Out of order packets adversely affect thequality of the PCoIP protocol.For load balancers – ensure affinity (or related) is set to 1Ensure same SA/DA sent on the same path.Configure WAN optimization devices to bypass PCoIP packetsCurrent WAN Optimization products canimpact PCoIP packets causing increasedlatency and packet loss and packet reordering.Ensure that small packets are not prioritized over larger packets.This can cause PCoIP packet reordering assmall PCoIP packets to jump ahead of largerones.VPN considerationsTER1105004 Issue 27

PCoIP Protocol Virtual Desktop Network Design ChecklistIf a VPN is used, confirm that UDP traffic is supported (IPSEC, orDTLS-enabled SSL solutions)Do not route PCoIP traffic through TCPbased SSL tunnelsAvoid VPN overhead if possible, consider a VPN-less secureremote access solution such as VMware View Security Server 4.6(or newer) which supports PCoIP protocolUse QoS Pre-Classify if CBWFQ or LLQ is necessary on theoutgoing interface of the VPN device.This may not be available on many platformsor in many designs.Confirm the VMware ESX virtual switch traffic shaper is turned off.Network BandwidthNotesPerform detailed network health checkDetermine other protocol traffic that exists on the network – especially otherhigh priority traffic that could impede PCoIP packet forwardingDetermine network characteristics key for a successful real-time protocoldeployment including latency, jitter (latency variation) and packet loss.Ensure there is sufficient bandwidth allocated to PCoIP trafficPlan for 200-250 kbps average for standard office applications with Windowsexperience settings optimized, orSee Table 1 and Table 2 formore detailsPlan for 80-150 kbps when optimizing the Windows experience settings andalso optimizing PCoIP session variables.Consider bandwidth required for audio input/outputSee Table 1 and Table 2Consider bandwidth required for USB trafficPCoIP Zero Clientbandwidth limit will limitUSB traffic (not the casewith a VMware ViewClient).Plan a minimum of 1Mbps per simultaneous user watching 480p video windowMore bandwidth may berequired depending on videoresolution/user qualityrequirementsEnsure network bandwidth analysis includes following network loadingguidelines (ie 60%-80%)Hardware interfaces runningat over 80% utilization tendto have problems queuingpackets due to networkburstiness resulting in packetdrops.Ensure there is sufficient bandwidth headroom for bursts of PCoIP protocol trafficPlan for a minimum bandwidth headroom of 500kbps to 1Mbps per session forVMware View hostsTER1105004 Issue 2The actual burst bandwidthrequired will depend on theuser and applications(considering the number ofpixels changing, the level8

PCoIP Protocol Virtual Desktop Network Design Checklistand complexity ofcompression, and the displayframe rate).Plan for a minimum of 1 Mbps per session burst bandwidth for PCoIP HostCards in remote workstationsMany workstationapplications will require ahigher burst bandwidth thatvaries per user and imagingworkload.Oversubscription analysis (optional) can enable efficient link sizing whilemaintaining a reasonable expectation that burst bandwidth is available persessionUse of enterprise networkloading guidelines is areasonable basic planningalternativeConsider bandwidth reduction options when operating in a known constrainednetwork environmentOptimize desktop Windows experience settings (implement this first)Optimize PCoIP Session variablesSee PCoIP Session VariablesOptimize display resolution/number of displaysPCoIP Session VariablesPCoIP Maximum Bandwidth Limit – sets a limit on the bandwidth a PCoIP session can use. Be careful not to set amaximum bandwidth limit too low since the PCoIP protocol needs to burst. Consider setting when operating in anetwork with known link congestion. The limit set can vary across useage scenarios such as: Single user on a link (i.e. home user on an internet connection) – set bandwidth limit to 90% of the link rate Consider setting the maximum bandwidth to [(Available bandwidth for PCoIP packets)/(n users)] 500kbps The minimum bandwidth limit should be set between 500kbps and 1Mbps, however, this may need to beincreased depending on the user requirements (see examples in Table 1 and Table 2)PCoIP Bandwidth Floor – the minimum bandwidth that will be transmitted when the session is attempting to transmitat a rate above the minimum. Consider only if operating on a network with known packet loss (ie Wireless)Ensure sufficient bandwidth is available: (n users) * (minimum bandwidth) available link bandwidthPCoIP Audio Playback Bandwidth Limit – configures audio compression. Resulting audio bandwidth will be near orbelow the limit setPCoIP Imaging: Minimum Image Quality – trades off display image quality vs. display frame update rate (lower imagequality for a higher frame rate etc)PCoIP Imaging: Maximum Initial Image Quality – a lower maximum initial image quality will reduce the peakbandwidth during large screen changes and reduce the initial display qualityPCoIP Imaging: Frame Rate Limit – sets a limit on the display update rate. Reduces average and peak bandwidth forhigh frame rate display content. Only useful when the native frame rate is above the limit.PCoIP Session MTU – option to adjust the PCoIP packet MTU to ensure is lower than the network MTUPCoIP Client PCoIP UDP port – option to adjust the PCoIP UDP port used at the client.TER1105004 Issue 29

PCoIP Protocol Virtual Desktop Network Design ChecklistConfiguration Example:Marking and CBWFQ with LLQ for VoIP, SIP traffic not treated. Assuming aLAN Ethernet interface and a WAN Serial T1 interface. QoS is configured toguarantee the following: Strict Priority for four G.729 VoIP calls marked as EF Reserved bandwidth for 2 Task Worker PCoIP sessions marked as AF41(500kbps minimum peak bandwidth, limited ability for oversubscription) The default class gets all the remaining bandwidth and is fair queued!match PCoIP packetsaccess-list 100 permit tcp any any eq 4172access-list 100 permit udp any any eq 4172class-map match-all VOIP-INmatch ip rtp 16384 16383class-map match-all PCOIP-INmatch access-group 100class-map match-all VOIP-OUTmatch ip dscp EFclass-map match-all PCOIP-OUTmatch ip dscp AF41policy-map ETH-INclass VOIP-INset ip dscp EFTER1105004 Issue 2Configuration Example Continued:class PCOIP-INset ip dscp AF41policy-map SERIAL-OUTclass VOIP-OUTpriority 128class PCOIP-OUTbandwidth 1000class class-defaultfair-queueinterface Serial 0/1bandwidth 1544no fair-queueservice-policy output SERIAL-OUT!trust dscp markings coming into thisrouter from across the WAN!do this if you need Layer 2 COS QoSand have a DSCP-COS map defined or setCOS on e0/1mls qos trust dscpinterface Ethernet 0/1service-policy input ETH-IN10

PCoIP Protocol Virtual Desktop Network Design ChecklistDue to variance in user perception, bandwidth guidelines are intended to provide a starting point – moreor less bandwidth may be needed to satisfy user performance requirements.Table 1 Mainstream Office Desktop ScenariosNote:Bandwidth – actual average and peak bandwidth required can vary greatly across user and enterpriseenvironments and may be more or less than the values shownPCoIP Bandwidth Limit – recommend that this is not set unless operating in a known constrained networkPCoIP Bandwidth Floor – recommend not setting this in View 4.5 or newer, unless operating on a network withknown packet loss (ie wireless networks)Windows Experience optimization – limited refers to basic optimization of desktop background, removing menufading etc. Full optimization includes additional steps such setting visual affects to best performance etc.Table 2 Power users and Designer (ie CAD) Desktop ScenariosNote:Power User and Extreme User categories assume the use of a PCoIP Host Card in a remote workstationImage Quality – adjustments may be needed for operation at lower bandwidths and/or constrained networksTER1105004 Issue 211

Ensure that the round trip network latency is within specification Excessive latency will impact desktop performance Less than 250ms round trip for VMware View 4.x hosts Less than 150ms round trip for PCoIP Host Cards Ensure the latency variation is less than 30ms About 1 frame for 30 fps (HD video and default for PCoIP Software in VMware

Related Documents:

The Cirrus LT is based on Teradici's high performance TERA2321 processor, which uses the PCoIP protocol. PCoIP compresses, encrypts, and encodes the entire computing expe-rience at the data center and transmits it as pixels across the IP network to a zero client.

Using PCoIP Zero Clients or PCoIP Software Clients (including Android, ChromeOS, and iOS) in dispersed locations, users can run the Maya application . rate at the remote client is what is important to the artist. 3. Interactive latency - the delay measured from a user input, such as a mouse . Horizon View were designed to deliver the .

The gold image used for testing was configured using VMware's PCoIP best practices. These settings are shown on page 20 in the "VMware Horizon View Best Practices Performance Study" white paper found here. The settings are intended for VMware Horizon View environments, but also apply to VMware Horizon DaaS desktop images using PCoIP.

VMware View from VMware, Inc. This Security Policy describes how the PCoIP Cryptographic Module for VMware View (software version: 3.5.0) meets the security requirements of FIPS 140-2 and how to run the module in a secure FIPS 140-2 mode. This policy was prepared as part of the Level 2 FIPS 140-2 validation of the module.

5- Wyse ThinOS 8.6 is ready to connect to Citrix , Microsoft and VMware environments. Wyse ThinOS 8.6 with PCoIP is required for accessing Amazon Workspaces and VMware environments using PCoIP. Wyse ThinOS 9.0 provides exclusive access to Citrix Workspace including Citrix Virtual Apps and Desktops Wyse ThinOS 9.0 requires Wyse Management .

EGP Exterior Gateway Protocol OSPF Open Shortest Path First Protocol IE-IRGP Enhanced Interior Gateway Routing Protocol VRRP Virtual Router Redundancy Protocol PIM-DM Protocol Independent Multicast-Dense Mode PIM-SM Protocol Independent Multicast-Sparse Mode IGRP Interior Gateway Routing Protocol RIPng for IPv6 IPv6 Routing Information Protocol PGM

SNMP V1/V2/V3 Simple Network Management Protocol SNTP Simple Network Time Protocol RFC RFC 768 UDP (User Datagran Protocol) RFC 783 TFTP (Trivial File Transfer Protocol) RFC 791 IP (Internet Protocol) RFC 792 ICMP (Internet Control Message Protocol) RFC 793 TCP (Transmission Control Protocol) R

of general rough paths. However, in this paper, we will focus on the case where the driving signal is of bounded variation. Following [6] we interpret the whole collection of iterated integrals as a single algebraic object, known as the signature, living in the algebra of formal tensor series. This representation exposes the natural algebraic structure on the signatures of paths induced by the .