Access your Pro+ Content below.
Desktop virtualization network challenges: A primer
This article is part of the June 2011 Vol. 2, No. 3 issue of Network Evolution
Why you need to know about desktop virtualization network requirements Desktop virtualization is becoming a reality after years of being touted but rarely used. For networking teams, implementing virtual desktop infrastructure will mean moving swiftly to optimize networks for delivering high-performing desktops and applications, a challenge they've never had to deal with before. The signs of desktop virtualization uptake are everywhere. While the technology played second fiddle to server virtualization at VMworld 2008, it took center stage at this year's show. That's partially because a number of desktop virtualization pilot projects have moved into actual production, and VMware launched its own virtual desktop infrastructure product, View. Desktop virtualization and the network Desktop virtualization network requirements Nemertes Research expects significant enterprise uptake in 2010-2011 -- a marked difference from 2008, when only 22% of companies were deploying desktop virtualization, and 62% of them were still in the ...
Access this Pro+ Content for Free!
Features in this issue
Virtual desktop infrastructure is seeing speedy uptake, but desktop virtualization network challenges mean investing in load balancing, traffic prioritization and even more bandwidth to support real-time applications to the desktop.
vSphere VLANs have requirements different from those of VLANs in physical environments because VMs are fluid and can't be assigned to one physical NIC. So 802.1Q VLAN tagging offers a new approach to configuring and managing VLANs in vSphere.
Running network diagnostics for virtualization requires a new set of strategies that involve virtual switches, virtual network probes and rerouting traffic for analysis.
News in this issue
In order to implement virtualization, enterprises must go beyond old-school network documentation for a full IT infrastructure audit that shows resources across silos.
One virtualization architect explains the miscommunications between systems and network engineers and how his teams worked together toward managing virtualization more effectively.