ABOUT THE AUTHOR


Terry Slattery
Terry Slattery, is a senior network engineer with decades of experience in the internetworking industry. Prior to joining Chesapeake NetCraftsmen as...
Read Full Bio >>
SHARE



Terry Slattery | January 01, 2013 |

 
   

The Twisted Path of Multimedia VDI

The Twisted Path of Multimedia VDI Monitoring and troubleshooting multimedia communications in a VDI environment is much more complex than in a peer-to-peer network model.

Monitoring and troubleshooting multimedia communications in a VDI environment is much more complex than in a peer-to-peer network model.

There is a big push in many organizations to move to Virtual Desktop Infrastructure (VDI). This brings a whole new level of complexity to deploying, managing, and troubleshooting multimedia applications. An audio and/or video application may be operating over multiple paths, each with different types of encoding and operational characteristics, as seen in Figure 1.


Figure 1: Multimedia VDI Communications Path

There are three major flows in each direction for a bi-directional multimedia session to function.

* Client A VDI path to VDI Server 1, using Client A's VDI protocol.
* VDI Server 1 to VDI Server 2, using the native multimedia streaming protocol.
* Client B VDI path to Server 2, which may use a different VDI protocol than Client A's VDI protocol.

In addition, the reverse direction for each of the above paths may be used if a bi-directional multimedia session is in use.

Note that the VDI protocol can be different for each client, depending on the VDI server in use (i.e., Citrix or VMWare) or depending upon the client itself (i.e., computer, thin client, or tablet). And the network infrastructure between each client and its VDI server may be substantially different. For example, one client may be remote, such as at a satellite medical facility that is connected by a T1 access line.

Conferencing between three or more endpoints will require the addition of a Multipoint Control Unit (MCU). Looking only at VDI Server 1 and VDI Server 2 conferencing paths, two additional paths would be added to the infrastructure for communication with the MCU. In this situation, the implementation may be made more complex if the protocol for each VDI server is different, such as when one of the clients is running a low bandwidth codec while another client is running a high bandwidth codec.

The quest for optimum performance and cost savings may further complicate the system. For example, if the organization is doing traffic engineering, asymmetric paths may result. Troubleshooting connectivity or performance problems in this type of environment can drive up the time and effort that it takes to diagnose problems.

The good news is that there are ways to tackle the complex task of diagnosing any potential problems. The bad news is that more advanced diagnostic tools will be needed to perform the troubleshooting within reasonable time frames. Simple packet capture tools can be used to look for specific symptoms, but the time required to perform the necessary analysis may make their use uneconomical.

Identify the Problem
You may learn that there is a multimedia problem because the people using the systems are reporting audio dropouts or jerky video. Proactive monitoring of the systems along the path can allow you to determine that there are problems, potentially heading off poor performance before it gets bad enough to have a big negative impact on the multimedia sessions.

When you are doing proactive systems monitoring, it is useful to configure the multimedia endpoints to report call stats to a central call controller for further analysis; the multimedia endpoints are the VDI Server 1 and VDI Server 2 (not the "Clients"). The ideal is getting RTCP info every 5 seconds, which allows you to determine how frequently the problem occurs. Without RTCP, obtain data about peak jitter and total packet loss from the server's multimedia-client application.

In the case of problems between each VDI client and its server, you'll need to monitor whatever performance measurement points are provided by the VDI software. It also makes sense to monitor network traffic statistics on both the VDI client and VDI server, looking for TCP retransmission counts and things like duplicate ACKs. A good network management product can help with basic network statistics monitoring.

Finally, the new generation of Application Performance Management (APM) products may be able to provide insight into a problem. These systems capture and analyze packet flows to identify application performance problems. They can typically measure jitter, packet loss, and server turnaround time to isolate the problem to the network, or to the server or the application.

Isolate the Path Components
Once you know that a problem exists, you can begin troubleshooting. You will need to isolate the source of the problem to one of the path components: 1) Client A to Server 1; 2) Server 1 to Server 2; or 3) Server 2 to Client B. Remember that the problem can be with the data flowing in one direction and not the other, so treat each direction separately for each path.

Once you think that you know the paths involved, check them thoroughly to confirm. I've seen a case where the video traffic was going to an MCU located on the Internet instead of to the corporate internal MCU. Traceroute between the two video systems took an entirely different internal path. The path via the Internet experienced a lot of jitter and loss while the internal path was clean. It took weeks of work before someone spotted the discrepancy in the configuration. Packet captures with a network analyzer or with an APM can verify that the endpoint addresses are correct. You may also need to look for network traffic engineering that may route the video traffic via a path that is different than what traceroute tells you.

The benefit of VDI is that all communications in the above scenario is routed through the data center. The installation of packet capture probes (e.g., Gigamon, Anue, etc) in the data center can significantly aid in the capture and analysis of multimedia and VDI flows.

Next Page: Troubleshooting Tips



COMMENTS


Who's Who at Enterprise Connect

NEC

Featured This Week:
Sponsored By


April 24, 2014
Small centers are both excited and nervous about the new wave of innovation converging on them as major disruptive forces - cloud, mobile, big data and social - rock the contact center world. They rea...
April 9, 2014
Recent advances in cloud technology have given rise to wide variety of new tools designed to support contact center performance, staffing and reporting. Join us for a live webinar focused on helping c...
March 26, 2014
As more organizations are focused on maximizing customer experience as a key differentiator to stay ahead of the competition and customer expectations, the focus needs to be on interactions across mul...

Sign up to the No Jitter email newsletters

  • Catch up with the blogs, features and columns from No Jitter, the online community for the IP communications industry. Each Thursday, we'll send you a synopsis of the high-impact articles, podcasts and other material posted to No Jitter that week, with links for quick access.

  • A quick hit of original analysis by the experts who bring you Enterprise Connect, the leading event in Enterprise Communications & Collaboration. Each Wednesday, this enewsletter delivers to your email box a thought-provoking, objective take on the latest news and trends in the industry.

Your email address is required for membership. For details about the user information, please read the UBM Privacy Statement

As an added benefit, would you like to receive relevant 3rd party offers about new products/services and discounted offers via email? Yes

* = Required Field

No longer instrested? Unsubscribe here.