HP Proliant, Oneview and 3par Deployment Guide With Microsoft Hyper-V and SCVMM 2012 R2

Technical white paper
HP ProLiant, OneView and 3PAR Deployment

Guide with Microsoft Hyper-V and SCVMM
2012 R2
Updated: 9/15/2015
Hongjun Ma, HP DCA
HP Proliant, OneView and 3PAR Deployment Guide with Microsoft Hyper-V and SCVMM 2012 R2
Table of contents
Introduction ............................................................................................................................................................................................... 3
Hyper-V Storage Configuration with 3PAR ........................................................................................................................................ 4
MPIO ..................................................................................................................................................................................................... 4
SCVMM 3PAR SMI-S Integration ..................................................................................................................................................... 5
Hyper-V 2012 R2 Networking Configuration with HP OneView ..................................................................................................11
Hyper-V 2012 R2 Converged Networking .................................................................................................................................11
SCVMM 2012 R2 Logical Switch ...................................................................................................................................................14
SCVMM Bare-metal Deployment with HP ProLiant Servers .........................................................................................................21
Importing PXE Server .....................................................................................................................................................................21
Configuring DHCP Scope Option ...................................................................................................................................................21
Configuring Windows Deployment Server .................................................................................................................................22
Preparing WinPE images with ProLiant Drivers ........................................................................................................................23
Configuring Physical Computer Profile .......................................................................................................................................25
Bare-Metal Hosts Deep Discovery ...............................................................................................................................................30
HP OneView for Microsoft System Center ........................................................................................................................................35
HP SCVMM 2012 Console Integration .........................................................................................................................................35
HP ProLiant SCVMM 2012 Integration ........................................................................................................................................40
HP Storage SCVMM 2012 Integration .........................................................................................................................................42
Conclusion ...............................................................................................................................................................................................44
Page 2
Introduction
This document describes the deployment and design options for configuring Microsoft Hyper-V 2012 R2 clusters using HP
OneView, ProLiant Gen9 servers and 3PAR StoreServ storage. It also demonstrates the integration of HP OneView and 3PAR
integration with Microsoft System Center Virtual Machine Manager (SCVMM) 2012 R2.
The paper will focus on Hyper-V and SCVMM 2012R2 configuration in related to HP OneView and 3PAR storage array. The
document along with other Microsoft Hyper-V and SCVMM design and implementation papers will help customers to build HyperV and SCVMM in HP server and storage environment.
The hardware and software of components tested includes the following:
Infrastructure
Components
Products
Version
Blade server H/W
HP BladeSystem C7000 Chassis with ProLiant BL460 Gen9 servers
SPP 2015.06
Blade server I/O
HP Virtual Connect FlexFabric-20/40 F8 Module for c-Class BladeSystem
SPP 2015.06
Server
Microsoft Hyper-V Server
2012 R2
Storage
HP 3PAR StoreServ 7400 system
3.2.1(MU2)P12
Networking
Cisco Nexus 6001 Switches
NX-OS 7.0(2)N1(1)
SAN Fabric
Cisco MDS 9148 Fibre Channel switches
NX-OS 6.2(7)
Management S/W
Products
Version
Virtualization
Management
Microsoft System Center Virtual Machine Manager
2012 R2 3.2.8071.0
Infrastructure
Management
HP OneView infrastructure management virtual appliance
1.20
Page 3
Hyper-V Storage Configuration with 3PAR

Hyper-V 2012 R2 supports the use of block-level storage devices that expose logical unit numbers (LUNs) for storage, by using
Fibre Channel, iSCSI, and Serial Attached SCSI (SAS) connection mechanisms.
In addition, Hyper-V 2012 R2 also supports the use of network shares for storage. Network shares that support the Server
Message Block (SMB) 3.0 Protocol can reside on a Windows-based file server or on a network-attached storage (NAS) device.
SMB3.0 introduced the concept of SMBMultichannel, which increases the network performance and availability of file servers
comparing to MPIO in iSCSI and Fibre Channel contexts.
The test was conducted using HP BladeSystem C7000 servers with FCOE connections from onboard CNA adapter. HP
BladeSystem C7000 Virtual Connect IO modules communicate with servers using FCOE and with SAN switches using external FC
connections. FC switches implement FC zoning for blade server and 3PAR storage array.
MPIO
With the configuration of FC zoning and 3PAR volume creation/export, users should also make sure MPIO feature is installed and
configured on Hyper-V hosts.
Besides Hyper-V server role pre-installed during OS setup, users should also add Windows Failover Clustering for virtual machine
high availability and Multipath IO (MPIO) features to SAN FC/iSCSI LUN redundant path access.
After MPIO feature is installed, users need to configure the new MPIO devices being discovered. This task should be implemented
after users set up 3PAR virtual volume and configured zoning on FC switches.
Without setting up MPIO, windows will see multiple presentations from a single LUN.
Page 4
Users can use the traditional mpclaim cmdlets as below to configure MPIO devices. Windows 2012 R2 also offers the new
Powershell cmdlets including Get|New-MSDSMSupportedHW to configure MPIO devices. After the correct MPIO configuration
shown below, 3PAR volume should be presented with single entity.
Microsoft Multipath I/O (MPIO) is a framework that allows you to develop multipath solutions that contain the hardware-specific
information needed to optimize connectivity with your storage arrays. Microsoft MPIO supports different policies such as Fail Over
where the policy does not perform load balancing and Round Robin whereDevice Specific Module (DSM) will use all available paths
for MPIO in a balanced way.
HP 3PAR recommends Round Robin MPIO policy. Windows Server 2012, Windows Server 2012 R2, or Windows Server 2008 R2
servers do not need to change the multipath policy, as it defaults to Round Robin already.
SCVMM 3PAR SMI-S Integration

SCVMM can add and discover external storage arrays that are managed by Storage Management Initiative Specification (SMI-S)
or Store Management Provider (SMP) providers. You can assign storage classifications for the discovered storage pools. For
example, you can assign a Gold classification to solid-state drive (SSD) storage and a Bronze classification to slower drives.
On 3PAR side, users need to make sure CIM server is running at the related HTTP/HTTPs ports. If CIM server is not started,
startcim CLI can be used to start CIM server.
The following steps highlight the procedure of adding 3PAR storage devices inside SCVMM.
Note:
Users should upgrade to latest SCVMM 2012R2 rolling update before trying to import 3PAR. As of today, the latest SCVMM
rolling update is up to patch 7. SCVMM version should be displayed as 3.2.8071.0 after the upgrade. SCVMM rolling
updates involved with applying patching to SCVMM server and console components. Some earlier patches need to apply
query scripts on the SQL server also. The detailed procedure is documented by Microsoft and out of the scope of this
white paper.
Page 5
In SCVMM 2012 R2 GUI Fabric view, click Add Resources to add storage devices
Select the option of SAN device managed by SMI-S provider.
Page 6
Users should provide 3PAR controller node management IP or hostname and choose the corresponding Run As account for
SCVMM to authenticate with 3PAR.
Users can create Run As Account as needed or go to SCVMM Settings section to review or create Run as accounts. The account
username and password should be one of 3PAR administrator accounts.
Page 7
3PAR array information will be displayed upon discovery. Users can also create SCVMM storage classification to apply for different
3PAR CPGs.
The following example shows the same task in Powershell cmdlets.
Page 8
With 3PAR array fully imported, Users can directly select storage pools and create logical units inside SCVMM.
Page 9
Finally users can assign or create the logical units under SCVMM Host Group or Cluster configuration so the LUN can be formatted
as cluster shared volume.
Page 10
Hyper-V 2012 R2 Networking Configuration with HP OneView

Hyper-V 2012 R2 Converged Networking
A Hyper-V host can have many virtual switches. There are three types of virtual switches available: External, Internal and Private.
External virtual networks are bound to a physical network card in the host so virtual machines can communicate with outside
world through physical network.
Internal virtual networks are not bound to a physical network adapter so virtual machines cant access anything beyond the
physical host. Internal network is available to the host and the VMs inside the host so they can communicate with each other.
Private virtual networks are visible only to the virtual machines, not the host so only VMs inside the same host can communicate
with each other.
In Windows server 2008 R2 Hyper-V, each Hyper-V network such as Live Migration requires dedicated physical network interface.
This design will require lots of physical NICs for a clustered Hyper-V host.
In Windows Server 2012, its possible to create multiple virtual network adapters in host management partition. This introduced
another network design option named converged networking. Users can create multiple virtual network adapters over physical
NICs.
HP OneView can be configured for both of the above Hyper-V networking design options. If users need to present servers with
multiple physical NICs, users can configure OneView server profile to have up to eight connections for each onboard or Mezz
adapter. Each connection will be presented to server OS as physical NIC. Users define corresponding Hyper-V networks like MGMT,
Live Migration in OneView network configuration and present them within OneView Logical Uplink Template. Each HP
BladeSystem C7000 enclosure Logical Interconnect will inherit the uplink configurations from the template to provide data access
for Hyper-V host and virtual machine traffic.
Another unique design option with HP OneView is to use Tunnel network to tunnel all host and virtual machine traffic through HP
Virtual Connection module to the TOR or leaf/spine DC switches. In this option, users only need to define networks and VLANs in
DC switches and Hyper-V hosts. There is no need to define these networks inside HP OneView configuration. Instead, users will
define a pair of tunnel networks in OneView for tunneling the traffic and redundancy. The design greatly simplifies the Hyper-V
converged networking design where typically only one virtual/logical switch is defined on Hyper-V hosts for all traffic.
HP ProLiant Gen9 servers also support 20G CNA adapters capable of providing high performance Ethernet and FCOE/HW iSCSI
storage access at the same time so users can achieve convergence and performance at the same time.
The following sample HP OneView server profile for HP ProLiant BL460 Gen9 server provides two NICs and two FCOE HBAs for the
server blade leveraging the onboard 20G CNA adapter (Broadcom or Emulex). With OneView server profile, users can define the
network and SAN connections even before inserting server hardware to acquire logical NIC MACs and HBA WWPNs for PXE booting
and SAN FC zoning.
Page 11
The enclosure virtual connect module uplink going to DC switches only have one tunnel network defined instead of many
separate host and VM VLANs. All host and VM traffic will be tunnel through this tunnel network.
Page 12
One single HP OneView Tunnel network below can carry all Hyper-V host and virtual machine traffic. Users dont need to spend
extra administrative time to make sure Blade I/O VLAN configuration matching TOR and host configuration.
Currently HP offers Flexfabric 650 adapter based on Emulex and Flexfabric 630 adapter based on Broadcom for 20G CNA options.
Hyper-V servers will show Ethernet adapter of 20G bps with teamed NIC of 40Gbps. Network traffic can use up to all these
bandwidth if FCOE is not consuming the physical link.
Page 13
SCVMM 2012 R2 Logical Switch

Although users can create individual virtual switches on each host using Hyper-V Manager, itll become difficult to manage and
monitor all individual virtual switches when networking and hosts grow over time.
SCVMM introduced the concept of logical Switch to provide the powerful way of consistent networking configuration and
compliance check across Hyper-V hosts and sites.
Ideally users should only install Hyper-V hosts with Hyper-V role and no virtual switch and NIC teaming configured. After adding
Hyper-V hosts inside SCVMM, users should leverage SCVMM to perform all the configurations on the host.
The following steps highlight common configuration tasks for a typical Logical Switch configuration for HP ProLiant servers.
First, its recommended to disable the option of Automatic creation of logical networks in general setting. With this option
enabled, when SCVMM imports Hyper-V hosts with existing virtual switch defined, SCVMM will automatically create a logical
network if DNS suffix name of the network adapter not matching existing logical network. The newly created logical network
usually does not reflect users design.
To prepare creating a logical switch, users should start to define multiple Logical Networks for corresponding host MGMT, Live
migration, cluster and guest data traffic.
Page 14
To create a logical network, users can right click Logical Networks icon or use ribbon icon at the top left corner of the screen.
As shown in the next screen, when creating a new logical network, the option of One connected network was chosen to use
simple VLAN to segment different traffic. Leave the two options under One connected network unchecked as this is for host OS
traffic and no guest VM network virtualization (NVGRE) was planned for this demo. Also, a separate VM Network will be defined
later to map to this Logical Network.
Page 15
Users can add a single network site to match host group and define corresponding VLAN and IP subnet for the logical network.
VLAN 0 was chosen for mgmt as its defined on TOR switch as native VLAN. Since OneView tunnel network was in use, users
need to make sure the VLAN settings on Hyper-V/SCVMM matching the ones defined on TOR switches. If OneView mapped
networks are configured in logical interconnect and server profile instead of tunnel network, then SCVMM logical network VLAN
defined below need to match OneView server profile network connection VLAN setting and TOR switch VLAN settings need to
match OneView Logical Uplink network VLAN settings.
A static IP pool can be created so SCVMM can assign the static IPs from the pool for the Hyper-V hosts attached to the network.
Page 16
Live Migration, CSV and Guest data logical networks can also be defined. In the following example, we used VLAN 165 for Live
migration traffic.
With the logical networks and their associated network sites defined, users can create an uplink port profile to define which logical
networks will be included in a given uplink template. The default load balancing algorithm of Host Default and Teaming mode of
Switch Independent are recommended for HP OneView and Virtual Connect modules.
Page 17
Users can pick which network site will be used for this uplink port profile
With uplink port profile defined, users can finally create the logical switch, which will be used for configuring Hyper-V hosts or bare
metal deployment.
In the logical switch, users need to select the uplink port profile to associate with the uplink definition.
Page 18
For virtual port classification like host MGMT, Live Migration, uses should create or select the existing template classification.
Host management virtual port classification is shown below.
Page 19
Finally, users should define VM Networks mapping to previous defined Logical Networks. The VM Networks will be associated with
Host virtual network adapter and guest virtual machines.
Page 20
SCVMM Bare-metal Deployment with HP ProLiant Servers

Windows 2012 SCVMM added the feature of bare-metal deployment of Hyper-V hosts. It integrates with Windows Deployment
Server(WDS) for PXE booting.
SCVMM will require HP iLO administrator access in order to have the control during server PXE boot process.
Configuring DHCP Scope Option

For WDS installed on the same host as DHCP server, users need to add DHCP scope option 43,66 and 67. Option 60 should be
automatically configured when WDS is installed on the same DHCP server.
Note:
Boot\x86\wdsnbp is for tested BIOS booting of Gen9 servers instead of IEFI.
Importing PXE Server

To add WDS as PXE server inside SCVMM, users can right click PXE server item under Fabric->Infrastructure and type WDS server
hostname and select the Run as account with the right privilege for the option.
Page 21
Configuring Windows Deployment Server

During deployment testing, users may need to turn off Enable Variable Windows Extension in order for servers PXE client to
successfully negotiate with WDS server to boot up PXE image.
Without turning off the option, the PXE boot may fail with the error of Terminate transfer due to option negotiation in sniffer
capture.
Page 22
Preparing WinPE images with ProLiant Drivers

Its important to prep default WinPE images with the correct HP ProLiant drivers, especially network card drivers. Powershell and
DISM scripts launched from SCVMM server to build WinPE images will be discussed later in the section.
Without the right driver, the common symptom is that the PXE will boot but the WinPE process will fail due to some errors like the
following example of Synchronizing Time with Server. The root cause of the error actually has nothing to do with time or NTP. If
users open DOS prompt in stuck WinPE session, they may see either no any network adapter discovered (for HP Flexfabric 630
Broadcom 20G CNA) or the adapter is discovered with the wrong driver (for HP Flexfabric 650 Emulex 20G CNA).
The following capture shows one of failed WinPE sessions. The network card was seen however it was detected as general
Emulex OneConnect card instead of HP FlexFabric adapter.
With the right WinPE driver embedded, the same network card should show as HP Flexfabric 650 card and the deep discovery
process was successfully finished.
Page 23
To add ProLiant drivers into the WinPE image, users can manually download drivers from HP Enterprise support portal. The
following example show HP FlexFabric 650 network driver.
Note:
Users should use OneView server profile to apply the related HP Service Pack for ProLiant (SPP) packet to the server for
corresponding firmware level support of the drivers.
Windows DISM tool is used build the new image and publish-scwindowspe Powershell cmdlet on SCVMM server to publish the
image back to WDS server deployment directory.
For complete procedure, user can refer to the Thomas Maurers blog article . The following example captured whats used in the
demo test.
$mountdir = "c:\mount"
$winpeimage = "c:\temp\boot.wim"
$winpeimagetemp = $winpeimage + ".tmp"
$path = "C:\Drivers"
mkdir "c:\mount"
copy $winpeimage $winpeimagetemp
dism /mount-wim /wimfile:$winpeimagetemp /index:1 /mountdir:$mountdir
dism /image:$mountdir /add-driver /driver:$path
Dism /Unmount-Wim /MountDir:$mountdir /Commit
publish-scwindowspe -path $winpeimagetemp
del $winpeimagetemp
Page 24
Another Option is to leverage HP OneView SCVMM integration kit so all drivers are imported into SCVMM library and Powershell
scripts can match driver tag to import all related drivers into WinPE image. Please check the Mikael Nystroms blog article for
further details.
Note:
HP Insight Control for System Center product referred in the blog article was renamed to OneView for System Center
Configuring Physical Computer Profile

In order to add a bare metal host for SCVMM deep discovery and configuration, a Physical Computer Profile needs to be created
for Host H/W and OS template configuration.
Page 25
Users need to specify VHDX file will be used for system OS disk provisioning after WinPE process finished.
For converged networking configuration, the two CNA 20G ports would be teamed together using the Logical Switch and Uplink
Port Profile defined earlier.
In order for SCVMM to map Physical NIC #1 or #2 to the real hardware being discovered, users can leverage Consistent Device
Naming (CDN) if the servers support the feature (HP ProLiant BL460 Gen9 BIOS example below). Another option is to use NIC MAC
address and users should manually verify if SCVMM has mapped NIC correctly after SCVMM deep discovery if this option is chosen.
Page 26
Three virtual network adapters on the hosts would be created on the host to map MGMT, Live Migration and Cluster network and
the host virtual network adapters will get static IP addresses assigned from the logical network pools defined earlier.
The next two screens showed MGMT virtual network adapter configuration.
Page 27
The next two screens showed Live Migration virtual network adapter configuration.
Page 28
Another important component is driver options because the VHDX image is windows general OS image and users need to apply
HP drivers on top of the original windows OS image.
In order to import all related HP drivers, users should install HP ProLiant SCVMM 2012 Integration Kit into SCVMM library. The
integration kit will install all HP ProLiant windows drives along with tags so users can use driver tags available below to select the
right driver for the OS. HP ProLiant SCVMM 2012 Integration Kit will be discussed in more details in one of sections following.
Page 29
Bare-Metal Hosts Deep Discovery

With all previous preparation tasks done, users can start to add bare-metal hosts for OS provisioning.
The last option should be selected for bare-metal host provisioning.
Users need to provide a run as account for SCVMM to access HP iLO in order to issue IPMI commands for host rebooting and deep
discovery.
Page 30
For HP BladeSystem C7000, users can also utilize OA CLI and iLO RIBCL scripting to mass add/edit any iLO accounts. The following
OA CLI example adds an iLO user admin to all 16 blades.
HPONCFG all << end_marker
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="adminname" PASSWORD="password">
<USER_INFO MODE="write">
<ADD_USER
USER_NAME="admin"
USER_LOGIN="admin"
PASSWORD="your password here">
<ADMIN_PRIV value ="Y"/>
<REMOTE_CONS_PRIV value ="Y"/>
<RESET_SERVER_PRIV value ="Y"/>
<VIRTUAL_MEDIA_PRIV value ="Y"/>
<CONFIG_ILO_PRIV value="Yes"/>
</ADD_USER>
</USER_INFO>
</LOGIN>
</RIBCL>
end_marker
Next step is to provide server iLO IP addresses. Its a good practice to use IP range option even though users only have one host to
discover because IP range option will give users the option to confirm the right host to be reloaded.
Page 31
Page 32
If all previous DHCP, WDS and WinPE images are provisioned correctly, deep discovery should be successful and users should be
given the option to customize each host like hostname and verify network adapters mapping.
Because the server supports CDN, all NICs should have the correct mapping and SCVMM will team two physical NICs into the
logical switch configured and also created three virtual network adapters on the host for MGMT, Live Migration and Cluster.
Page 33
Note:
Users should pay close attention to SCVMM DNS entry for the discovered host throughout the discovery and deployment
process when using converged networking with multiple NICs inside the teaming configuration. The reason is that physical
NICs may get different DHCP IPs during PXE booting and MGMT virtual adapter will be configured later from MGMT logical
network static IP. However the DNS server and SCVMM DNS cache may still have the hostname mapping to the previous
physical NIC DHCP IPs. This may cause deployment job fail. Users may choose to only select one physical NIC to be in the
team in physical computer profile or in deployment customization phase for the consistent DNS mapping.
Users can monitor status in the SCVMM job view and HP OneView Integrated iLO remote console while deployment is in the final
process of provisioning server disk and networking settings.
Page 34
HP OneView for Microsoft System Center

HP OneView for Microsoft System Center (OV4SC) provides a comprehensive integration of HP Storage, HP ProLiant Servers, HP
Blade System and HP Virtual Connect with Microsoft System Center. It enables administrators to manage and monitor their HP
infrastructure running in Microsoft environment with a single pane-of-glass view for health monitoring, events/alerts, detailed
inventory and HP fabric visualization. Administrators can gain greater control of their technology environments reducing the risk
of downtime and enabling a faster response.
HP OneView for Microsoft Virtual Machine Manager (SCVMM) Integration provides end-to-end HP fabric visualization for virtualized
environments using HP Virtual Connect to view from the VM to the edge of the network configuration information. It also provides
SCVMM library with HP ProLiant driver kits for WinPE and bare-metal deployment.
HP OneView for Microsoft System Center Operations Manager (SCOM) integration prevents problems from occurring by
proactively monitoring and managing hardware health and intelligently responding to hardware events on servers running
Windows and Linux, as well as BladeSystem Enclosures, HP Virtual Connect, and HP Storage.
HP OneView for Microsoft System Center Configuration Manager (SCCM) integration provides quick and reliable Windows
deployment to bare metal HP servers, including pre-deployment hardware and BIOS configuration, and post-OS HP driver and
agent installation. You can verify consistency and improve uptime with simplified Windows driver and firmware updates using the
HP ProLiant Updates Catalog. Provides detailed component level inventory of every managed HP Windows server using the HP
ProLiant Inventory Tool.
HP Storage SCVMM 2012 Integration enables enhanced integration of SCVMM and HP Storage and provides a single pane-of-glass
monitoring view of physical, virtual and cloud environments. It automates HP Storage management and provides an integrated
view of VMs and associated storage resources.
HP SCVMM 2012 Console Integration

HP SCVMM provides end-to-end HP fabric visualization for virtualized environments using HP Virtual Connect to view from the VM
to the edge of the network configuration information.
It also provides enhanced provisioning using HP OneView server profiles to deploy Hyper-V hosts consistently and reliably,
including configuration of Windows networking, HP Virtual Connect, and shared SAN storage.
After HP SCVMM 2012 Console Integration Kit installation .exe file execution, users need to use add-pssnapin and addhponeview cmdlet to add HP OneView Appliance into console integration kit. Please check HP SCVMM 2012 Console Integration
user guide for more details.
In Fabric cluster view, HP Fabric management provides cluster summary information.
Page 35
Users can also check individual host inventory details.
Users have the option to view all hosts inside C7000 enclosure and can launch server iLO directly from SCVMM.
Page 36
Host LAN and SAN connection information are provided including MAC/WWPN and the network configured inside OneView.
End-to-End network topology from server to virtual connect to data center switches is provided using Fabric Diagram feature.
Page 37
Working together with SCVMM bare metal deployment, OneView console integration provides a Deploy Server wizard to stream
line OneView profile and Hyper-V host deployment.
In deployment wizard, users can provision OneView server profile using server profile template and map OneView profile
connection settings with SCVMM Physical computer profile.
Page 38
Page 39
HP ProLiant SCVMM 2012 Integration

Compared with HP ProLiant SCVMM 2012 console integration, SCVMM 2012 integration kit provides driver kits for HP SCVMM
Library for bare-metal deployment.
The installation exe file will extract all driver kits to the local disk. Users will then execute hpproLiantscvmmkit-install.ps1 to
import the drivers into SCVMM library.
The following capture showed SCVMM library was updated with the drivers and each driver also has meta-data attached like
custom tags. The drivers imported enable user to build up WinPE and system OS disks during SCVMM bare-metal host
deployment.
Page 40
Page 41
HP Storage SCVMM 2012 Integration

HP Storage SCVMM 2012 Integration Kit enables enhanced integration of SCVMM and HP Storage and provides a single pane-ofglass monitoring view of physical, virtual and cloud environments. It automates HP Storage management and provides an
integrated view of VMs and associated storage resources.
The installation process involves the execution of integration kit exe file.
The following capture shows the summary of cluster/host storage mapping information with 3PAR. The integration kit also
provides access link to HP StoreVirtual, StoreOnce and 3PAR management console.
Page 42
Users can view individual volume details and have the option to expand the volume size.
Page 43
Conclusion
The paper demonstrates that HP OneView and 3PAR has tight integration with Microsoft SCVMM and hyper-V.
Multiple plugins are available for users with different administrative roles to configure and monitor Microsoft Hyper-V and SCVMM
environment.
Page 44

HP Proliant, Oneview and 3par Deployment Guide With Microsoft Hyper-V and SCVMM 2012 R2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP Proliant, Oneview and 3par Deployment Guide With Microsoft Hyper-V and SCVMM 2012 R2

Uploaded by

Copyright:

Available Formats

Technical white paper

HP ProLiant, OneView and 3PAR Deployment

Blade server H/W

HP BladeSystem C7000 Chassis with ProLiant BL460 Gen9 servers

Blade server I/O

HP Virtual Connect FlexFabric-20/40 F8 Module for c-Class BladeSystem

Microsoft Hyper-V Server

HP 3PAR StoreServ 7400 system

Cisco Nexus 6001 Switches

Cisco MDS 9148 Fibre Channel switches

Microsoft System Center Virtual Machine Manager

HP OneView infrastructure management virtual appliance

Hyper-V Storage Configuration with 3PAR

SCVMM 3PAR SMI-S Integration

Select the option of SAN device managed by SMI-S provider.

The following example shows the same task in Powershell cmdlets.

Hyper-V 2012 R2 Networking Configuration with HP OneView

SCVMM 2012 R2 Logical Switch

Host management virtual port classification is shown below.

SCVMM Bare-metal Deployment with HP ProLiant Servers

Configuring DHCP Scope Option

Boot\x86\wdsnbp is for tested BIOS booting of Gen9 servers instead of IEFI.

Importing PXE Server

Configuring Windows Deployment Server

Preparing WinPE images with ProLiant Drivers

Configuring Physical Computer Profile

Bare-Metal Hosts Deep Discovery

The last option should be selected for bare-metal host provisioning.

HP OneView for Microsoft System Center

HP SCVMM 2012 Console Integration

In Fabric cluster view, HP Fabric management provides cluster summary information.

Users can also check individual host inventory details.

HP ProLiant SCVMM 2012 Integration

HP Storage SCVMM 2012 Integration

You might also like