Access your Pro+ Content below.
Why are network engineers so bitter about managing virtualization?
This article is part of the June 2011 Vol. 2, No. 3 issue of Network Evolution
Network engineers are tired of being viewed as plumbers—especially when it comes to managing virtualization. After all, the job of supporting virtualized traffic goes so much deeper than providing an always-available pipe. Systems teams understand the complexity of a virtualized environment, but don't always see the network admin's role in the virtual network management process. The split results in ineffective troubleshooting strategies and network architectures that don't always better a virtualized environment. Virtualization architect Bob Plankers recognized that problem amongst his own ranks at a large Midwestern university and set out to change things by opening up conversation—and management tools— between the two teams. The result? A new network architecture and an effective approach to managing virtualization. Is there really a disconnect between networking and systems folks when it comes to managing virtualization? Bob Plankers: Absolutely. Virtualization or systems people don't include the network guys in what's ...
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.