Access your Pro+ Content below.
Virtualization demands a full IT infrastructure audit
This article is part of the June 2011 Vol. 2, No. 3 issue of Network Evolution
If virtualization demands a unified IT organization without separate teams for applications, systems, networking and storage, then the first step is a full IT infrastructure audit that goes well beyond old-school network documentation. Today’s network engineers have a tough challenge before them: They've got to provide high-availability network infrastructure that can handle traditional applications, as well as virtualized multihost systems and access by smart devices. Both virtualization and smart device management demand an IT organization that is not broken into separate camps for applications, systems, storage and networks. What most people don't realize is that this type of unified organization starts with an IT infrastructure audit and network documentation strategy that reaches across all of these camps. A unified IT organization isn't a new concept Oddly enough, there was a time when application, systems and networking engineering were considered joint tasks that were conducted by so-called IT generalists. The separation...
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.