Server virtualization technologies for x86-based HP BladeSystem and HP ProLiant servers, 3rd edition

Figure 4. Virtual Connect abstracts the networking connections in a manner similar to networking in a

hypervisor environment.

For a more in-depth description of the similarities between the network abstractions of hypervisors and

those of Virtual Connect, see the paper titled ―HP Virtual Connect: Common Myths, misperceptions,

and objections‖ available at

http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01598869/c01598869.pdf.

With Virtual Connect firmware releases of v1.31and later, customers can define the logical server

abstractions within a VC server profile definition. These logical server abstractions go beyond the

physical server connection and node ID to include the container definition, itself, with dynamic

workload adjustments using Flex-10 technology. As a result, the VC server profile can reflect new

levels of mobility and flexibility of the system image to the OS.

With the server identity being held constant through Virtual Connect, the following results occur:

The underlying server networking hardware is transparent to the application/OS workload,

allowing hardware components to be replaced or the OS workload to be moved to a completely

different server blade. This improves flexibility for a physical or a virtual machine infrastructure.

Network resources are provisioned in bulk, whether connected to physical machines or virtual

machines.

Virtual Connect separates the server infrastructure from the network and storage infrastructure,

enabling a server administrator to add, move, or change servers without disrupting the external

LAN and SAN networks.

For more information about Virtual Connect technology, see the technology brief titled ―HP Virtual

Connect technology implementation for the HP BladeSystem c-Class‖:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00814156/c00814156.pdf.