HP Virtual Connect

This article has multiple issues. Please help or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations. (July 2012) (Learn how and when to remove this template message) This article needs additional citations for verification. Please help by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources:  –  ·  ·  · scholar · JSTOR (July 2012) (Learn how and when to remove this template message) This article contains content that is written like an advertisement. Please help by removing promotional content and inappropriate external links, and by adding encyclopedic content written from a neutral point of view. (June 2014) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

HP Virtual Connect brings virtualization to the blade server edge. It picks up where virtual machine technology stops. Virtual machine technology can only move workloads across virtual machines on a single server. It becomes a challenge when moving virtual machines from one physical machine to another or between data center locations, because changes to the LAN and SAN environments require manual intervention by network and storage administrators. By pooling and sharing multiple network connections across multiple servers and virtual machines, Virtual Connect extends Data Center^[1] capability by allowing physical setup and movement of Virtual Machine workloads between servers and Virtual Machines, transparently from the LAN and SAN infrastructure.^[2] Another name for Virtual Connect is PowerConnect Switches (old name of the series).

Virtual Connect is a new Virtualization technology from Hewlett-Packard (HP) that de-couples fixed blade server adapter network addresses^[3] from the associated external networks so that changes in the blade server infrastructure and the LAN and SAN environments don’t require a complex choreography among server, LAN, and SAN teams for every task. Using the built-in HP Virtual Connect Manager for small configurations or the HP Virtual Connect Enterprise Manager for larger environments, administrators can define a server connection profile for each blade server bay before a server is installed. This profile establishes the Media Access Control (MAC) addresses for all network interface controllers (NICs), the World Wide Names (WWNs) for all host bus adapters (HBAs), and the Fibre Channel SAN boot parameters along with their associated network uplink connections, and then associates them to a blade server bay so that even if the server is changed, the configuration and connection profile stay constant. When a new server takes its place, the same profile is associated and used by the new server.

The technology behind the latest Virtual Connect FlexFabric adapters and modules, part of the HP FlexNetwork Architecture, takes Virtual Connect further with unique capabilities. Virtual Connect FlexFabric^[4] provides up to four physical functions for each blade server adapter network port, with the unique ability to fine-tune bandwidth to adapt to virtual server workload demands on the fly. All four connections can have their hardware personalities defined by the System Administrator as FlexNICs to support only Ethernet traffic as before with Virtual Connect. In addition however, one of the physical functions can also be defined as a FlexHBA for Fibre Channel protocol support or an iSCSI initiator for iSCSI boot protocol support. Each function has 100 percent hardware-level performance and provides the I/O performance needed to take full advantage of multi-core processors and to support more virtual machines per physical server.^[5] Each server can support many connections—up to 24 per half-height blade—with less investment in expensive adapter cards on the server, fewer interconnect modules in the blade enclosure and fewer expensive uplink switch ports in the corporate network.^[6] Virtual Connect as one of the technology foundations for HP CloudSystem and Converged Infrastructure allows the abstraction of the blade server infrastructure from the LAN and SAN infrastructure. This allows resources to be allocated to services in a dynamic Cloud Environment.^[7]

References[]