Premium Content

Access "Why are network engineers so bitter about managing virtualization?"

Rivka Gewirtz Little, Executive Editor Published: 10 Oct 2012

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 going on. In traditional data ... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

What's Inside

Features
    • Desktop virtualization network challenges: A primer

      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.

    • Network diagnostics that see through virtualization by SearchNetworking Staff

      Running network diagnostics for virtualization requires a new set of strategies that involve virtual switches, virtual network probes and rerouting traffic for analysis.

    • vSphere VLAN: Understanding 802.1Q VLAN tagging by Eric Siebert

      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.

More Premium Content Accessible For Free

  • Hybrid Cloud networking falls short, but not for long
    evolution_cover_april_2013_landscape.PNG
    E-Zine

    As if network management isn’t hard enough, now engineers must find ways to manage physical networks, virtual networks and SDN environments. In this ...

  • BYOD challenges that lurk beyond network security
    Evolution_Jan_2013_cover_lg.jpg
    E-Zine

    Every access network now must be engineered to enable, manage and secure BYOD. In this edition of Network Evolution, we offer insight into ...

  • The new network: SDN gets real
    0213_NetworkEvolution_EZineSupplement_landscape.PNG
    E-Zine

    As the software-defined networking (SDN) hype is replaced by real products, this edition of The New Network will look at the current state of SDN ...