8/22/2019 c 00814156

1/15

Technical white paper

Overview of HP Virtual Connect technologies

Table of contents

Introduction 2Virtual Connect components 2Virtual Connect virtualizes the LAN andSAN connections 3

Server profiles and server identity 3Configuring the network and serverprofiles 4LAN-safe 5SAN-safe 6

FlexNIC capabilities 6Convergence with Virtual ConnectFlexFabric adapters 7Direct-Attach Fibre Channel for 3PARStorage Systems 9Management capabilities 10

Virtual Connect Manager 11

Virtual Connect Enterprise Manager 11Enterprise-wide HP managementconsoles 11Integration with third-party tools 12

Virtual Connect provides high levels ofsecurity 13Data center traffic flow and VirtualConnect 14Conclusion 14For more information 15Call to action 15

Click here to verify the latest version of this document.Created August 2012.

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

8/22/2019 c 00814156

2/15

2

Introduction

HP developed Virtual Connect technology to simplify networking configuration for the server administrator using an HPBladeSystem c-Class environment. The baseline Virtual Connect technology virtualizes the connections between theserver and the LAN and SAN network infrastructure. It adds a hardware abstraction layer that removes the directcoupling between them. Server administrators can physically wire the uplinks from the enclosure to its networkconnections once, and then manage the network addresses and uplink paths through Virtual Connect software. Using

Virtual Connect interconnect modules provides the following capabilities:

Reduces the number of cables required for an enclosure, compared to using pass-through modules. Reduces the number of edge switches that LAN and SAN administrators must manage. Allows pre-provisioning of the networkso server administrators can add, replace, or upgrade servers without

requiring immediate involvement from the LAN or SAN administrators.

Enables a flatter, less hierarchical network, reducing equipment and administration costs, reducing latency andimproving performance.

Delivers direct server-to-server connectivity within the BladeSystem enclosure. This is an ideal way to optimize forEast/West traffic flow, which is becoming more prevalent at the server edge with the growth of server virtualization,cloud computing, and distributed applications.

Without Virtual Connect abstraction, changes to server hardware (for example, replacing the system board during aservice event) often result in changes to the MAC addresses and WWNs. The server administrator must then contact theLAN/SAN administrators, give them updated addresses, and wait for them to make the appropriate updates to theirinfrastructure. With Virtual Connect, a server profile holds the MAC addresses and WWNs constant, so the serveradministrator can apply the same networking profile to new hardware. This can significantly reduce the time for aservice event.

Virtual Connect Flex-10 technology further simplifies network interconnects. Flex-10 technology lets you split a 10 GbEthernet port into four physical function NICs (called FlexNICs). This lets you replace multiple, lower-bandwidth NICswith a single 10 Gb adapter. Prior to Flex-10, a typical server blade enclosure required up to 40 pieces of hardware (32mezzanine adapters and 8 modules) for a full enclosure of 16 virtualized servers. Use of HP FlexNICs with VirtualConnect interconnect modules reduces the required hardware up to 50% by consolidating all the NIC connections ontotwo 10 Gb ports.

Virtual Connect FlexFabric adapters broadened the Flex-10 capabilities by providing a way to converge network andstorage protocols on a 10 Gb port. Virtual Connect FlexFabric modules and FlexFabric adapters can (1) converge

Ethernet, Fibre Channel, or accelerated iSCSI traffic into a single 10 Gb data stream, (2) partition a 10 Gb adapter portinto four physical functions with adjustable bandwidth per physical function, and (3) preserve routing information for alldata types. Flex-10 technology and FlexFabric adapters reduce management complexity; the number of NICs, HBAs, andinterconnect modules needed, and associated power and operational costs. Using FlexFabric technology lets you reducethe hardware requirements by 95% for a full enclosure of 16 virtualized serversfrom 40 components to twoFlexFabric modules.

The most recent Virtual Connect innovation is the ability to connect directly to HP 3PAR Storage Systems. You can eithereliminate the intermediate SAN infrastructure or have both direct-attached storage and storage attached to the SANfabric. Server administrators can manage storage device connectivity and LAN network connectivity using VirtualConnect Manager. The direct-attach Fibre Channel storage capability has the potential to reduce SAN acquisition andoperational costs significantly while reducing the time it takes to provision storage connectivity.

In writing this paper, we assume that you are somewhat familiar with BladeSystem architecture. If not, the HPBladeSystem c-Class architecture technology brief provides helpful background information. This paper provides an

overview of the Virtual Connect technologies. For details about the capabilities of specific modules and adapters, see theVirtual Connect website.

Virtual Connect components

Virtual Connect is a portfolio of interconnect modules, adapters, embedded software, and an optional managementapplication:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://www.hp.com/go/virtualconnecthttp://www.hp.com/go/virtualconnecthttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdf

8/22/2019 c 00814156

3/15

3

Virtual Connect interconnect modulesFlexFabric, Flex-10/10D, or Fibre Channel modules plug directly into theinterconnect bays in the rear of the HP BladeSystem c Class enclosure. The modules connect to the server bladesthrough the enclosure midplane. The Ethernet-based modules support 1 or 10 Gb uplinks and downlinks, allowingcustomers to purchase 1 Gb SFPs and upgrade to 10 Gb SFP+ transceivers when the rest of their infrastructure isready to support it.

Flex-10 and FlexFabric adapters are available as either LAN-on-motherboard (LOM) devices or mezzanine cards.Virtual Connect technology also works with 1 GbE adapters and FlexibleLOM devices for ProLiant BL Gen8 servers. A

FlexibleLOM uses a special slot/connector on the motherboard and lets you choose the type of NIC that is "embedded"on the ProLiant Gen8 server.

Virtual Connect Manager (VCM) firmware is embedded in the Virtual Connect Flex-10/10D and FlexFabric interconnectmodules. VCM manages a single domain of up to four enclosures.

Virtual Connect Enterprise Manager is an optional software application that lets you manage up to 250 VirtualConnect domains and up to 1000 enclosures within those domains. The VCEM software provides automation andgroup-based management capabilities beyond what VCM offers.

Figure 1 shows a BladeSystem enclosure with the server blades and Virtual Connect modules.

Figure 1: An internal midplane in the BladeSystem c-class enclosure connects the server blades in the front to the Virtual Connectinterconnect modules at the back of the enclosure.

Virtual Connect virtualizes the LAN and SAN connections

The baseline Virtual Connect technology adds a virtualization layer between the edge of the server and the edge of theexisting LAN and SAN. As a result, the external networks connect to a shared resource pool of MAC addresses and WWNsrather than to MACs/WWNs of individual servers.

Server profiles and server identity

Using the concept of a server profile, Virtual Connect links information assigned to a specific server bay to the serverhardware and its network connections. A server profile lets you manage the servers internal identity (server serialnumber, UUID, BIOS settings, SAN boot parameters, and PXE boot parameters) and a servers external identity (MACs,WWNs, VLAN assignments, and SAN fabric assignments).

Virtual Connect manages the servers internal identity by presenting the managed serial numbers and a managed UUIDto the OS image and applications, rather than the serial numbers and UUID assigned by HP at manufacture. When youinclude managed serial numbers within a server profile, you can migrate any software that is licensed to a particularserver, based on either the serial number or UUID value, to new server hardware without a new software license. Thisprevents having to reinstall software associated with a specific serial number after a system recovery.

Server blades

Front of enclosure Rear of enclosure

Virtual Connect

interconnect modules

8/22/2019 c 00814156

4/15

4

For the external server identity, Virtual Connect creates and manages new WWNs and MAC addresses, not the addressesassigned at manufacture. Although the hardware ships with default MAC addresses and WWNs, Virtual Connect resetsthe MAC addresses and WWNs prior to boot, so PXE/SAN boot and all operating systems will see only the valuesmanaged by Virtual Connect. Assigning the addresses before OS boot is important because other methods in theindustry require OS and network switches to be aware of virtual WWNs and MAC addresses. This requires extra overheadby the network switches and server CPUs, increases complexity of troubleshooting, and increases l icensing complexities.

Configuring the network and server profilesConfiguring the network and server profiles consists of simple steps. First, the LAN and SAN administrators define theavailable networks, or VLANs, that they want the servers to communicate on (Figure 2).

Figure 2: Administrators can configure the network in three basic steps.

Then the administrator configures the server profile (Figure 3). The administrator defines Virtual Connect networks(vNets) based on the pre-defined VLANs. Internal to Virtual Connect, we use standard IEEE 802.1 VLAN Q-in-Q tagging tocorrelate the vNets to the external LAN connections and send the network packets to the correct server.

Step 1:

Create a Shared Uplink Set (SUS)

SUS = 802.1q trunk

Step 2:

Assign physical ports to the trunk

LACP automatically enabled

Step 3:

Add VLANs in the trunk

8/22/2019 c 00814156

5/15

5

Figure 3: Administrators can configure the server profile in three basic steps.

After the administrator assigns a server profile, which includes the MAC address and WWN, to a specific server bay,Virtual Connect holds these parameters constant for that server bay. Even if you exchange one server in a server baywith a different server, the LAN and SAN connections remain constant. Virtual Connect preserves the identity of thenetwork connections into the data center. This means that you can pre-assign profiles to server bays, add servers, movethem, or replace at willwithout affecting the external LAN and SAN environments. Network and storageadministrators can establish all LAN and SAN connections once during deployment and dont need to make connectionchanges later to swap servers.

Virtual Connect complies with IEEE and ANSI standards to allow full interoperability with traditional network equipmentvendors. Virtual Connect modules do not conflict with products from standards-based networking or storage vendors.Virtual Connect is edge-safe for both your LAN and SAN network.

LAN-safe

From the external networking view, Virtual Connect FlexFabric, Flex-10, or Ethernet uplinks appear to be multiple NICson a large server. Virtual Connect ports at the enclosure edge look like server connections. This is analogous to aVMware environment that provides multiple MAC addresses to the network through a single NIC port on a server. See theHP Virtual Connect for the Cisco administrator paper for the full explanation of how Virtual Connect is analogous to avirtual machine environment.

Virtual Connect works seamlessly with your external network:

Does not participate in Spanning Tree Protocol (STP) on the network uplinks to the data center. This avoids potentialSTP configuration errors that can negatively affect switches in the network and the servers connected to thoseswitches.

Uses an internal loop prevention algorithm to automatically detect and prevent loops inside a Virtual Connect domain.Virtual Connect ensures that there is only one active uplink for any single network at one time.

Allows aggregation of uplinks to data center networks (using LACP and fail-over). Supports VLAN tagging on egress or pass-thru of VLAN tags in tunneled mode. Supports Link Layer Discovery Protocol (LLDP) and Jumbo Frames.

Step 1:

Create a server profile

Step 2:Assign VLANs to server NICs

- Select a single VLAN for untagged NIC

- Select Multiple Networks for tagged NIC

Step 3:Assign server profile to real

server

Networks previously

defined for uplink

connectivity

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

8/22/2019 c 00814156

6/15

6

SAN-safe

Virtual Connect Fibre Channel uplinks appear to be multiple HBAs connecting to the SAN by using N_Port ID Virtualization(NPIV) technology. NPIV is an industry-standard Fibre Channel protocol that provides a method to assign multiple FibreChannel addresses on a single physical link. Each Fibre Channel connection has its own N_Port ID and WWN.

Virtual Connect works seamlessly with the external storage fabrics:

Supports industry standard NPIV on both uplinks and downlinks. Doesnt consume Fibre Channel Domain IDs; therefore Virtual Connect doesnt affect the total number of devices that

you can connect to an individual SAN Fabric.

Compliant and compatible with SAN switches from any standards-based vendor. Transparently supports Cisco virtual storage area network (VSAN), Cisco inter VSAN routing (IVR), and Brocade Virtual

Fabric features.

Virtual Connect modules supporting Fibre Channel must attach to NPIV-capable SAN switches. Most enterprise class SANswitches today support NPIV. You can also connect VC FlexFabric modules directly to HP 3PAR Storage System arraysusing the Virtual Connect 3.70 firmware (see theDirect-Attach Fibre Channel for 3PAR Storage Systemssection).

Depending on the module, Virtual Connect-Fibre Channel modules can aggregate up to 255 physical or virtual serverHBA ports through each of the modules uplink ports. This aggregation method is especially important to SANadministrators who struggle with SAN fabric segmentation and Fibre Channel Domain ID consumption.

Virtual Connect Fibre Channel modules make it easier to provision virtual machines by facilitating multiple HBA WWNs onthe physical server. Each virtual machine can have its own unique WWN that remains associated with that virtualmachine even when you move the virtual machine. Now SAN administrators can manage and provision storage to virtualHBAs, up to 128 per server blade, with the same methods and quality of service as physical HBAs.

FlexNIC capabilities

Flex-10 and FlexFabric adapters allow you to partition a 10 Gb link into several smaller bandwidth FlexNICs. Virtualmachine applications often require increased network connections per server, increasing network complexity whilereducing the number of server resources. Virtual Connect addresses this issue by letting you divide a 10 Gb networkconnection into four independent FlexNIC server connections (Figure 4). A FlexNIC is a physical PCIe function (PF) thatappears to the system ROM, OS, or hypervisor as a discrete physical NIC with its own driver instance. It is not a virtual NIC

contained in a software layer.

Figure 4: Flex-10 adapters allow administrators to partition bandwidth based on application requirements.

Simple Dual Port 10 GbE Mezz 10 GbE Ports Partitioned by VLANs

10 Gb

10 GbPCIe

NIC

1

NIC2

0.5

2.0

3.5

4.0

0.5

2.0

3.5

4.0

PCIe

FlexNIC4

FlexNIC3

FlexNIC2

FlexNIC1

FlexNIC4

FlexNIC3

FlexNIC2

FlexNIC110 Gb

port 110 Gb

port 1

10 Gb

port 2

10 Gb

port 2

Flex-10 Device

8/22/2019 c 00814156

7/15

7

You can configure each FlexNIC from 100 Mb up to 10 Gb, and dynamically adjust the bandwidth in 100 Mb incrementswithout requiring a server reboot. You can provide just the right amount of bandwidth based on application needs. Youno longer need to over-provision or under-provision bandwidth.

Virtual Connect tells the network adapter how to configure each of the four physical functions. Then the adapter defineseach of those physical functions, provisions them into the OS as individual NICs, and allocates the appropriatebandwidth. We work with each NIC vendor to ensure that they meet our Virtual Connect requirements for splitting thePCIe function and allocating bandwidth to each physical function.

Traffic moves from the Flex-10 NIC device (LOM or mezzanine card) to the Flex-10/10D module on a single physicalpathway. Although FlexNICs share the same physical port, traffic flow for each is designated by its own MAC address andVLAN tags (Figure 5).

Figure 5: FlexNICs share a physical link but isolate the traffic using VLAN tags.

Currently available Flex-10 NIC devices are dual-port LAN-on-motherboard NICs (LOMs) or mezzanine cards that supportup to four FlexNICs per port. You can also use Flex-10/10D interconnect modules with traditional (not Flex-10) 10 Gband 1 Gb NIC devices.

Because Flex-10 technology is hardware-based, FlexNICs eliminate the processor overhead required to operatevirtualized NICs in virtual machines and with traditional operating systems. You can present up to eight FlexNICs withoutadding more server NIC mezzanine cards and associated interconnect modules.

Prior to Flex-10, a typical server blade enclosure required up to 40 pieces of hardware (32 mezzanine adapters and 8modules) just to give 16 servers the best practice connections they require to support a virtualized environment (3redundant NICs and a redundant HBA per server). HP Flex-10 NICs and Virtual Connect Flex-10/10D modules reduce thathardware up to 50% by consolidating all of the NIC connections onto two 10 Gb ports.

Convergence with Virtual Connect FlexFabric adapters

Virtual Connect FlexFabric adapters can converge Ethernet, Fibre Channel, or accelerated iSCSI traffic into a single 10 Gbdata stream. A FlexFabric adapter provides more functionality than an off-the-shelf converged network adapter (CNA): Itprovides standard NIC functions, FlexNIC capabilities, and Fibre Channel or iSCSI FlexHBA capability.

Each FlexFabric adapter contains two 10 Gb Ethernet ports that you can partition into four Flex-10 physical functions(PFs) per porteither FlexNICs or FlexHBAs. You can adjust the bandwidth of the PFs manually or by using scriptingtools.

VC Flex-10/10D Ethernet Module

BladeSystem Server

Flex-10 LOM or Mezz Card

Flex-10 NIC (port 2)

Single lane of 10Gb/s

Ethernet for each port

VLAN

TAG

VLAN

TAG

VLAN

TAGFlexNIC FlexNIC FlexNICFlexNIC

Flex-10 NIC (port 1)

vNET vNET vNET vNET

VLAN

TAG

8/22/2019 c 00814156

8/15

8

A FlexHBA is an actual PCIe physical function on the FlexFabric adapter that you can configure to handle storage traffic.The server ROM, OS, and hypervisor recognize the PCIe function as an HBA device. You can assign storage traffic (FibreChannel or SCSI) as a FlexHBA only to the second PF of each FlexFabric adapter port. We use the second PF of each portas the storage function because in a traditional CNA this is the PF used for storage access. If you do not need blockstorage access, you can disable the FlexFabric adapter storage function and configure the second PF as another FlexNICfunction. The first, third, and fourth PFs work only as FlexNIC devices. However, a FlexFabric adapter will support eitherFibre Channel or iSCSI with TCP off-load engine (TOE) and iSCSI boot functionality on physical function 2.

The FlexFabric adapter encapsulates Fibre Channel packets as FCoE and consolidates the Fibre Channel and Ethernettraffic into one 10 Gb data stream. The FlexFabric interconnect module separates the c onverged traffic. Fibre Channeland Ethernet traffic continue beyond the server-network edge using the existing native Ethernet and Fibre Channelinfrastructure (see Figure 6). For more details about how traffic flow works with Virtual Connect FlexFabric, see thepaper HP Virtual Connect traffic flow.

Figure 6: FCoE traffic travels only between the FlexFabric adapter and the FlexFabric interconnect module. Standard Fibre Channeltraffic travels from the server edge to the external network.

FlexFabric technology significantly reduces cabling, switches, and required ports at the server edge. With the VirtualConnect FlexFabric modules and adapters, you have the flexibility to provision from two to eight connections on eachhalf-height server (using the embedded LOMs) and even more on full-height servers. Thats ideal for virtualized

infrastructures such as those using the VMware recommendation of six NICs and two HBAs for virtualized servers.If you were going to implement a virtualized server blade infrastructure without Virtual Connect, you would need a dual-port LOM, an extra quad port NIC mezzanine, a dual-port HBA, six Ethernet switch modules, and two Fibre Channel switchmodules. As shown in Figure 7, the typical server blade solution requires 40 components compared to the VirtualConnect FlexFabric solution. The Virtual Connect FlexFabric solution requires only embedded dual-port FlexFabricadapters on servers (no mezzanine cards) and two Virtual Connect FlexFabric modules. In addition to the reducedqualification, purchase, and installation requirements, youll require fewer spares and fewer firmware updates.

HP BladeSystemenclosure

EthernetFCoE

EthernetEthernet

HPVCFlexFabric

In

terconnectModule

Midplane

FC

Ethernet

Ethernet

Serveredge

VM

VM

VM

Blade server

VM

1

2

3

4

Ethernet

FC

Ethernet

Ethernet

Ethernet

FC

Ethernet

Ethernet

Ethernet

10 Gb/s downlinks

FC

Ethernet

Ethernet

Ethernet

Port1

Hypervisor

FlexFabric adapter ports

EthernetFCoE

EthernetEthernet

FlexFabric adapter provideslocal VLAN tagging andmerges traffic into single

10 Gb/s uplink

Virtual Connect module separatestraffic into original traffic class and

steers it based on tag

Hypervisor uses VLAN tags andFlexFabric adapter profiles to

steer traffic

HPVCFlex

Fabric

InterconnectModule

Adapter

Port2

4

3

2

1

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

8/22/2019 c 00814156

9/15

9

Figure 7: Virtual Connect FlexFabric solutions reduce cost and components compared to a traditional switch solution.

Direct-Attach Fibre Channel for 3PAR Storage Systems

In an enterprise data center, traditional Fibre Channel disk storage has many shortcomings. A total solution has a highcapital acquisition cost, including the SAN fabric switches and the management software/licenses required for theswitch and the disk storage management. There are also high operational costs, with multiple management points (HBA,enclosure edge switches, SAN core switches, target systems) that often require manual and complex coordinationamong these systems.

HP solves these problems by collapsing the storage network and removing the edge-core architecture. The Direct-

Attach Fibre Channel solution provides an enterprise storage solution without requiring an expensive external SANfabric. The Direct-Attach Fibre Channel solution combines the scalability of HP 3PAR Storage Systems with the simplicityof Virtual Connect (see Figure 8).

Traditional switch solution

1Gb

LOM

40parts

95%reduction

50%reduction

Flex Fabric

LOM

VC FlexFabric

2parts

VC Flex-10 & VC FC

Flex-10

LOM

20parts

8/22/2019 c 00814156

10/15

10

Figure 8: Direct-Attach Fibre Channel for 3PAR Storage Systems reduces cost and components compared to a traditional SAN fabricsolution.

Highly scalable 3PAR Storage Systems provide connectivity to up to 192 Fibre Channel host ports and 1.6 PB of storageusing a single P10000 V-800 storage system. Combined with 3PAR advanced features such as adaptive and dynamicoptimization, thin provisioning, peer motion, and space reclamation, this direct-connect technology provides anotherway for Virtual Connect to simplify your environment.

Also as shown in Figure 8, your network can have both direct-attach and fabric-attach storage simultaneously. TheVirtual Connect FlexFabric modules will continue to support traditional fabric connectivity but will be enhanced tosupport direct-attach Fibre Channel storage with only minimal changes to Virtual Connect firmware. You simply choosethe Direct-Attach mode when configuring Virtual Connect, and the firmware will allow 3PAR storage arrays to connect toFibre Channel uplinks of the Virtual Connect FlexFabric module. Now you can have data center-wide connectivity throughVCM. You wont need separate licenses for the SAN/storage fabric or training on different management tools. You canmanage your LAN and your storage from VCM or higher-level CloudSystem Matrix management and orchestration tools.

Management capabilities

The primary management tools for Virtual Connect are Virtual Connect Manager (VCM) and Virtual Connect EnterpriseManager (VCEM). Beyond that, Virtual Connect uses SNMP to integrate with other management tools such as HP SystemsInsight Manager, HP Intelligent Management Center, HP Network Node Manager, and other third-party SNMP-basedconsoles. Virtual Connect supports enterprise management tools from partners such as Brocade SAN Network Advisor.HP has developed the Insight Control extension for VMware vCenter that allows administrators to use Virtual ConnectManager directly from the vCenter console. HP also provides you tools to develop your own utilities based on the VCEMCLI and the published VCEM APIs.

EnclosureUID

Enclosure Interlink

PS

3

PS

2

PS

1

PS

6

PS

5

PS

4

OA1 OA2

Remove management modules before ejecting sleeve

FAN

6

FAN

10

FAN

1

FAN

5

21

3

5

7

4

6

8

iLOUID

ActiveResetiLO

UID

ActiveReset

HP VCFlexFabric 10Gb/24-Port Mo d u l e

SHARED: UPLINK or X-LINKX3 X4X1 X 2 X5 X 6 X 7 X 8

UID

HP VCFlexFabric 10Gb/24-Port Mo d u l e

SHARED: UPLINK orX-LINKX3 X4X1 X 2 X5 X 6 X 7 X 8

UID

12Vdc 12 Vdc

HP StorageWorks4/32B SAN Switch

0 1 2 3 8 9 10 1 1 16 1 7 1 8 19 24 2 5 26 2 7 3130292823222120151413127654

1 2Vdc 12V dc

HP StorageWorks4/32B SAN Switch

0 1 2 3 8 9 10 1 1 16 1 7 1 8 1 9 24 2 5 2 6 27 3130292823222120151413127654

Fabric-1 Fabric-2

HP StorageWorks

P6300 EVA

SAN uplink

connections

(Fabric-Attach)

SAN Switch A SAN Switch B

HP BladeSystem c7000

HP 3PAR Storage System

SAN uplink

connections

(Direct-Attach)

HP StorageWorks

XP12000

8/22/2019 c 00814156

11/15

11

Virtual Connect Manager

VCM includes a web-based console integrated into the firmware of every Ethernet-capable module. You can use VCM tomanage single Virtual Connect domains (up to four enclosures). You can access VCM through a browser-based GUI orthrough the VCM Command Line Interface (CLI). VCM domain management makes it simple to set up and manage serverconnections because it includes control of networks, SAN fabrics, server profiles, and user accounts.

For example, you can use the VCM CLI to perform debugging and troubleshooting for the Virtual Connect system and

networking issues. VCM CLI telemetry commands let you monitor system health, resource utilization, MAC addresses andthe associated FlexNICs, uplink status, and NIC throughput data on all physical ports. For more details, see the paperEfficiently Managing Virtual Connect environments.

Virtual Connect Enterprise Manager

VCEM is the best way to manage Virtual Connect environments across the data center. VCEM is a highly scalablesoftware solution that centralizes network connection management and workload mobility for thousands of serversthat use Virtual Connect. VCEM is a plug-in for HP Systems Insight Manager (HP SIM) and benefits from the rich featureset HP SIM offers.

VCEM provides these core capabilities:

A single intuitive console that controls up to 250 Virtual Connect domains (up to 1000 BladeSystem enclosures and16,000 servers).

A central repository that administers more than 256K MAC addresses and WWNs for server-to-network connectivity.This simplifies address assignments and eliminates the risk of conflicts. The central repository removes the overheadof managing network addresses manually. With VCEM, administrators can use the unique HP defined addresses,create their own custom address ranges, and establish exclusion zones to protect existing MAC and WWNassignments.

Discovery and aggregation of existing Virtual Connect domain resources into the VCEM console and addressrepository.

Group-based management of Virtual Connect domains using master configuration profiles. You can use a group topush Virtual Connect domain configuration changessuch as network assignment or parameter modificationsto allmembers of the domain group simultaneously. This increases infrastructure consistency, limits configuration errors,and simplifies enclosure deployment.

GUI and a scriptable CLI that allow fully automated setup and operations. This lets you move server connectionprofiles and associated workloads between BladeSystem enclosures so that you can add, change, and replace serversacross the data center without affecting production or LAN and SAN availability.

For more details, see the paper Understanding the Virtual Connect Enterprise Manager.

Enterprise-wide HP management consoles

You can use other HP tools such as HP Insight Control, HP Intelligent Management Console, and the HP Matrix OperatingEnvironment (Matrix OE) software to perform inventory, monitoring, and troubleshooting functions beyond the VirtualConnect domains.

HP Insight Control

Insight Control discovers and monitors Virtual Connect from a system management perspective. VCM and VCEM feedserver and network configuration data into HP SIM and Insight Control so that you can access that data for management,

health monitoring, and coordination of your servers from a single management console that covers the data center.

HP Intelligent Management Console

The Intelligent Management Console (IMC) from HP Networking provides robust discovery, monitoring, and networktopology views of Virtual Connect and other HP and third-party network infrastructure. You can use IMC to monitormission-critical Virtual Connect networks across the data center. IMC reads Virtual Connect device SNMP MIBs andprovides visibility to information such as port count and statistics.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdf

8/22/2019 c 00814156

12/15

12

HP Matrix Operating Environment

HP Matrix OE is an integrated infrastructure management stack containing the tools needed to build and manage cloudofferings such as infrastructure-as-a-service. Device data provided by VCEM and HP Insight Control provide thefoundation for logical server deployment and orchestration delivered with HP Matrix OE. For more information, see theHP Matrix Operating Environment 7.0 Logical Server Management User Guide.

Integration with third-party tools

HP works with other vendors to expose Virtual Connect information in consoles used by server, virtualization, storage,and networking teams. A great example is the HP Insight Control plug-in for VMware vCenter. This plug-in allowsvCenter to discover and display Virtual Connect status in a un ique topology view, from guest virtual machines all the wayto upstream networking devices (Figure 9). It allows you to monitor the relationship between VMware virtualizednetworking and Virtual Connect.

Figure 9: HP Insight Control for vCenter lets you view Virtual Connect status from your VMware console.

HP SAN Connection Manager offers similar functionality for Fibre Channel SANs and storage resources. The SANConnection Manager lets you do basic handling of SAN components such as HBAs, switches, and storage arrays in asingle wizard-based GUI. You can integrate SAN Connect Manager with VCEM to display the associations between theserver blades and storage hosts, as shown in Figure 10.

For more information about integrating Virtual Connect with SAN Connection Manager, see theHP SAN Connection

Manager User Guide.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02016931/c02016931.pdf?jumpid=reg_R1002_USENhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02016931/c02016931.pdf?jumpid=reg_R1002_USENhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02016931/c02016931.pdf?jumpid=reg_R1002_USENhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02016931/c02016931.pdf?jumpid=reg_R1002_USENhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02016931/c02016931.pdf?jumpid=reg_R1002_USENhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02016931/c02016931.pdf?jumpid=reg_R1002_USENhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdf

8/22/2019 c 00814156

13/15

13

Figure 10: The SAN Connection Manager lets you visualize the SAN and VC connections.

Finally, many third-party management tools can compile Virtual Connect SNMP MIBs. Management tools can then useSNMP to discover and monitor Virtual Connect modules. In addition to local statistics and SNMP polling of statistics,Virtual Connect provides SNMP traps for events that cause Virtual Connect domain status changes. Embedded SNMP v1,v2, and SMI-S agents allow network management applications to query Virtual Connect for statistics and trapinformation. Third-party tools that integrate with Virtual Connect include EMC Ionix, Solar Winds, and NAGIOS.

Virtual Connect provides high levels of security

Virtual Connect uses security practices that continue to improve as the Virtual Connect capabilities expand. For example,Virtual Connect includes the following capabilities:

Strong security across management interfaces with support for SSL and SSHincluding 2048-bit SSL certificates. Role-based security that offers authentication, authorization, and accounting (activity logging) based on assigned

roles. You can specify the VCM role as domain, network, server, or storage. These roles are configurable for all typesof authentication methods.

Authentication methods that include local authentication, Lightweight Directory Access Protocol (LDAP), TerminalAccess Controller Access-Control System Plus (TACACS+), and Remote Authentication Dial-In User Service (RADIUS).

Diagnostic and management technologies that match your established preferences and investment. Each data centerteam can use their preferred method on the same module with simultaneous multi-mode access.

Network Access groups that let you control which networks to allow into the same server profile. You can assign aVLAN to one or more groups. This prevents administrators from using networks from different security domains in thesame server profile.

Local accounts that are disabled when remote authentication is enabled and active. If a network team only allowsTACACS+ credentials, the Virtual Connect firmware disables local authentication if the network can connect to aTACACS+ server.

Increased minimum required length for the local account passwords.

8/22/2019 c 00814156

14/15

14

Security protection for SNMP access beyond the read community string. User can now specify authorized SNMPmanagement stations for SNMP access to Virtual Connect devices. All unauthorized management stations will bedenied access.

Data center traffic flow and Virtual Connect

The growth of virtual machines, cloud-computing models, distributed applications, and mobile access devices are allcausing shifts in data center networking traffic patterns toward more server-to-server (East-West) traffic flow. Industrysources indicate that more than 80 % of data center traffic will be East-West (E-W) by 2014. Read details atGartnerG00207476, Emerging Technology AnalysisandGartner G00175764, Key Issues for Communication EnterpriseStrategies, 2010.For example, VMware vMotion capability is one example of server-to-server communications, inwhich an entire VMs memory imagetypically at least 4 GBhas to be transferred rapidly from one machine toanother.

Implementing Virtual Connect technology is an ideal way to optimize for East/West traffic flow at the server edge. Unlikeother more hierarchical structures, Virtual Connect delivers direct server-to-server connectivity within an enclosure. Youcan also connect multiple Virtual Connect Ethernet modules to allow all server NICs in the Virtual Connect domain (up tofour enclosures) to communicate with each other without the traffic leaving the domain. This reduces the core switchtraffic, because internal communication stays inside the Virtual Connect domain.

For more information about how Virtual Connect compares to other hierarchical structures, see the paper Comparisonof HP BladeSystem servers with Virtual Connect to Cisco UCS .

Conclusion

HP Virtual Connect architecture boosts the efficiency and productivity of data center server, storage, and networkadministrators: It virtualizes the connections between the server and the network infrastructure (server-edgevirtualization) so networks can communicate with pools of HP BladeSystem servers. This virtualization lets you move orreplace servers rapidly without requiring changes or intervention by the LAN and SAN administrators.

Virtual Connect is standards-based and complies with all existing and emerging standards for Ethernet, Fibre Channel,and converged networks. The Virtual Connect modules connect seamlessly with existing network infrastructure.

HP Virtual Connect Flex-10 technology is a hardware-based solution that lets you simplify network I/O by splitting a 10Gb/s server network connection into four variable partitions. Flex-10 technology and products give you more NICs, yet

they minimize the number of physical NIC and interconnect modules required to support multi-network configurations.HP Virtual Connect FlexFabric modules and HP FlexFabric adapters extend the Flex-10 capabilities to include convergednetworking. This technology allows HP BladeSystem customers to connect servers to network and storageinfrastructure with a single server connection and a single Virtual Connect interconnect module supporting Ethernet andFibre Channel or iSCSI networking. Virtual Connect FlexFabric requires up to 95% less hardware to qualify, purchase,install, and maintain in blade enclosures. You can reduce costs by converging and consolidating server, storage, andnetwork connectivity onto a common fabric with a flatter topology and fewer switches.

With Direct-Attach capabilities to 3PAR Storage Systems, HP takes another step forward in flattening and simplifying thedata center architecture. You can now move the storage network from an edge-core implementation to an edgeimplementation directly to storage.

Virtual Connect management tools provide the framework that allows administrators to easily set up and monitor thenetwork connections, the server profiles, and even how the networks map into virtual machines (with VMware).

http://www.gartner.com/id=1470341http://www.gartner.com/id=1470341http://www.gartner.com/id=1470341http://www.gartner.com/id=1470341http://www.gartner.com/id=1331716http://www.gartner.com/id=1331716http://www.gartner.com/id=1331716http://www.gartner.com/id=1331716http://www.gartner.com/id=1331716http://www.gartner.com/id=1331716http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://www.gartner.com/id=1331716http://www.gartner.com/id=1331716http://www.gartner.com/id=1470341http://www.gartner.com/id=1470341

8/22/2019 c 00814156

15/15

15

For more information

Visit the URLs listed below if you need additional information.

Resource description Web address

HP BladeSystem c-Class architecture technologybrief

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

HP Virtual Connect for the Cisco administrator http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf

HP Virtual Connect traffic flow http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03154250/c03154250.pdf

Efficiently Managing Virtual Connectenvironments

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

Understanding the Virtual Connect EnterpriseManager

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

HP Matrix Operating Environment 7.0 LogicalServer Management User Guide

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

HP Virtual Connect: Common Myths,Misperceptions, and Objections, Second Edition

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

Effects of virtualization and cloud computing ondata center networks http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03042885/c03042885.pdf

Comparison of HP BladeSystem servers withVirtual Connect to Cisco UCS

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

Call to action

Send comments about this paper toTechCom@HP.com

Follow us on Twitter:http://twitter.com/ISSGeekatHP

Get connectedhp.com/go/getconnected

Current HP driver, support, and security alertsdelivered directly to your desktop

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The onlywarranties for HP products and services are set forth in the express warranty statements accompanying such products and servi ces. Nothing hereinshould be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omiss ions contained herein.

Trademark acknowledgments, if needed.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03154250/c03154250.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03154250/c03154250.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02058339/c02058339.hires.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02058339/c02058339.hires.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03042885/c03042885.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03042885/c03042885.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfmailto:TechCom@HP.commailto:TechCom@HP.commailto:TechCom@HP.comhttp://twitter.com/ISSGeekatHPhttp://twitter.com/ISSGeekatHPhttp://www.hp.com/go/getconnectedhttp://www.hp.com/go/getconnectedhttp://www.twitter.com/HPISSTechCommhttp://twitter.com/ISSGeekatHPmailto:TechCom@HP.comhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03094466/c03094466.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03042885/c03042885.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03042885/c03042885.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02058339/c02058339.hires.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c02058339/c02058339.hires.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03132774/c03132774.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03314921/c03314921.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03028646/c03028646.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03154250/c03154250.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c03154250/c03154250.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c00810839/c00810839.pdf