Traffic shaping increases PCoIP packet latency and can impact user experience. Shaping works to smooth traffic bursts and achieve a defined committed access rate (CAR) by buffering packets. Often PCoIP packets are treated as scavenger class traffic, which can negatively impact desktop performance.Īvoid traffic shaping unless absolutely necessary. By default, these enforce WRED for all but trunked packets marked with class of service 5 (generally VoIP packets from a hardphone). When using the AutoQoS feature, SRR queues are automatically configured on many access layer platforms. Consider adding Layer 2 uplink bandwidth before applying Layer 2 quality of service, if possible.Īvoid the use of AutoQoS features at the Layer 2 layer for devices that do not explicitly support AutoQoS for PCoIP packets, as this may result in WRED being applied at the switchport layer through the use of Shared/Shaped Round Robin (SRR) queues. Only use Layer 2 quality of service class of service prioritization if there is noted congestion at the access layer or between the access and aggregation (distribution) layer. Configuring WRED on the physical interface overrides all other quality of service queuing configurations.Ĭonsider segmenting PCoIP traffic via Layer 2 VLAN and/or class of service types at the access layer of your network. If a Tail Drop scheme is deployed, large bursts of PCoIP data may be suddenly dropped by the network before PCoIP protocol has time to adapt to congestion.Ĭonfirm that the network interface is not configured for WRED if you have selected WRED for the service policy on that interface. When an WRED algorithm causes packet loss PCoIP protocol adapts to network congestion with minimal impact on the user experience. Unlike most NDP traffic, PCoIP protocol benefits from WRED mechanics. The Neighbor Discovery Protocol (NDP) is a protocol in the Internet protocol suite used with IPv6. Keep in mind that network devices may add additional encapsulation and increase the PCoIP packet size.ĭo not use per-packet load balancing for any load balancing decisions along the path of traffic, including but not limited to EIGRP load balancing, static route load balancing, and MPLS load balancing. Increase router maximum transition unit before reducing PCoIP packet maximum transition unit, as lower PCoIP protocol maximum transition unit can impact desktop performance.
#PCOIP PROTOCOL CISCO SOFTWARE#
Defaults are 1200 or 1300 bytes for PCoIP software (depending on the vendor), and 1400 bytes when connecting PCoIP zero clients to PCoIP remote workstation cards. This will show as packet loss in the PCoIP session logs, but not in network device logs.Įnsure that PCoIP packets are not fragmented at any point in the network path.Įnsure that the maximum transition unit in network devices is not below the PCoIP packet maximum transition unit size. PCoIP packets that arrive excessively out of order may be considered as lost packets by the PCoIP protocol. Users typically notice performance degradation if the session packet loss is greater than 0.1%, although higher loss may be tolerated. Packet loss within a single PCoIP session should target less than 0.1%. Packet loss should be zero for properly configured LAN/WAN deployments. If you are near the maximum recommended queue depths, consider optimizing PCoIP for lower bandwidth or increasing the link bandwidth. Increase the queue depth settings in the PCoIP queue if tail drops are experienced. This should not be done in most cases as proper CBWFQ usage will allow for acceptable guaranteed session quality.
Large pack serialization can sometimes cause high amounts of jitter. The choice of which DSCP value to use is influenced by the presence of possible video and/or VoIP control packets. This ensures low drop probability inside each queue if weighted random early drop (WRED) must be configured for the queue servicing the PCoIP protocol.
If using DSCP markings, PCoIP traffic should be marked to DSC AF41 or AF31. This is necessary for the real-time responsiveness of the protocol. (namely, below VoIP RTP but above all other traffic). Mark and classify PCoIP traffic the same as real-time interactive traffic according to your quality of service marking scheme.Consider quality of service options such as Class-Based Weighted Fair Queuing (CBWFQ) or Low Latency Queuing (LLQ) on switch uplinks and on Layer 3 WAN/LAN links.The following sections outline the important network requirements and guidelines to take into consideration when setting up a PCoIP session. Session Planning for PCoIP Ultra Enhancements
Workload Characterization and Network PlanningĮnhanced Audio/Video (A/V) Synchronization
0 kommentar(er)
