Automation

Extends Control to Virtual

Computing Environment

Mainstreaming the vSwitch: HP Network

Event

HP recently announced availability of a driver for their long-fielded HP Network Automation product which

delivers integrated support of virtual switches (vSwitches) – virtual network elements that exist within

VMWare’s ESX virtual server platform. This introduction marks the first third-party extension of network

change and configuration management technology to incorporate support for and address the specific needs

of operations teams that are trying to fully embrace, operationalize, and standardize virtual server

architectures into mainstream production, and apply the same best practices for reliable, low-risk, secure

networking that is standard operating procedure in the non-virtual production network.

Context

Virtualization within IT has been around in many shapes and forms for many years, but the recent wave of

interest has focused on bringing virtualization concepts to the traditionally dedicated server environment of

Windows-based servers. Such virtual computing offers highly compelling operational cost advantage by

improving use of existing computing resources as well as lower power and cooling cost via server

consolidation – especially popular during the current period of economic stress.

What many shops don’t fully appreciate, often until they are well into the production rollout process, is that

within each ESX system is a virtual network, complete with multiple virtual network interface cards (vNICs),

and multiple virtual network switches (vSwitches), that come with a

variety of security and performance settings. The way in which these

elements are configured and deployed has a direct effect on the ability

of the newly commissioned virtual machines (VMs) to deliver the

applications and services that will be running as a guest on the physical

appreciate is that within

host system. Configuration options and issues include definition and

type of VLANs, load balancing, and redundancy; and, in order for many

vSwitch options to function properly, the physical switch to which the

virtual network.

host physical server is connected must be configured to support certain

capabilities, such as VLAN trunking.

While most experienced network engineers and administrators are fully familiar with these types of

configurations and settings, system administrators are typically not. And yet, since virtual servers are a server

phenomenon, in most IT shops the system administrators are responsible for configuration, deployment, and

support of virtual servers, including the virtual network elements within.

Recent ENTERPRISE MANAGEMENT ASSOCIATES® (EMA™) research into virtual server operations1

indicates that while the majority of organizations globally are deploying this technology, only a third of IT

teams felt that they had all of the tools they needed to fully manage and support their deployments. Clearly, as

with any technology, there is a maturation process for management practices that typically lags the first waves

of deployment. In this case, the long term viability of virtual servers requires that they be accorded the same

attention in management technology and practice as their more physically-manifested predecessors, both in

terms of systems management as well as network management.

EMA IMPACT BRIEF

- 1 -

©2009 Enterprise Management Associates

What many shops don’t fully

each ESX system is a

1

http://www.enterprisemanagement.com/research/asset.php?id=1104, January 2009